Hovatek Forum MOBILE Android [Please help] fastboot not detecting despite installed driver
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


[Please help] fastboot not detecting despite installed driver

[Please help] fastboot not detecting despite installed driver

Pages (3): Previous 1 2 3 Next
X3non
X3non
X3non
Recognized Contributor
22,062
16-04-2020, 08:23 PM
#11



(16-04-2020, 12:24 PM)pythonenthusiast Thanks for your help so far. Appreciate.
Here's what i got when i tried the three codes(remote: oem unlock is not allowed)
https://i.postimg.cc/MTm0Z0p9/image.png

already replied to this before, see https://www.hovatek.com/forum/thread-335...#pid191006
ham_samm
ham_samm
ham_samm
Senior Member
283
17-04-2020, 09:31 PM
#12
(16-04-2020, 08:23 PM)X3non
(16-04-2020, 12:24 PM)pythonenthusiast Thanks for your help so far. Appreciate.
Here's what i got when i tried the three codes(remote: oem unlock is not allowed)
https://i.postimg.cc/MTm0Z0p9/image.png

already replied to this before, see https://www.hovatek.com/forum/thread-335...#pid191006

I understand,
Here's what i got when i tried "strings aboot.img | findstr /i oem" command from https://www.hovatek.com/forum/thread-21403.html STEP 3 No.5.
what does it mean?
https://i.postimg.cc/vTcDvZM4/image.png

Not sure if this might help in helping me out
https://i.postimg.cc/W1HLGVny/image.png
This post was last modified: 18-04-2020, 03:48 AM by ham_samm.
X3non
X3non
X3non
Recognized Contributor
22,062
18-04-2020, 11:57 AM
#13
(17-04-2020, 09:31 PM)ham_samm I understand,
Here's what i got when i tried "strings aboot.img | findstr /i oem" command from https://www.hovatek.com/forum/thread-21403.html STEP 3 No.5.
what does it mean?
https://i.postimg.cc/vTcDvZM4/image.png

Not sure if this might help in helping me out
https://i.postimg.cc/W1HLGVny/image.png

it's either the aboot.img isn't in the same folder location as the strings executable
OR the command used, you can try "strings aboot.img | findstr oem" or replace oem with unlock
ham_samm
ham_samm
ham_samm
Senior Member
283
18-04-2020, 12:54 PM
#14
(18-04-2020, 11:57 AM)X3non
(17-04-2020, 09:31 PM)ham_samm I understand,
Here's what i got when i tried "strings aboot.img | findstr /i oem" command from https://www.hovatek.com/forum/thread-21403.html STEP 3 No.5.
what does it mean?
https://i.postimg.cc/vTcDvZM4/image.png

Not sure if this might help in helping me out
https://i.postimg.cc/W1HLGVny/image.png

it's either the aboot.img isn't in the same folder location as the strings executable
OR the command used, you can try "strings aboot.img | findstr oem" or replace oem with unlock
It same thing    https://i.postimg.cc/ZRrm6Jxm/image.png

I want to let you know that the aboot file i'm using is from my firmware which i recently backed up
which name is "aboot" and not "aboot.img", i had to rename it and add ".img" as suffix to "aboot".
Please kindly check the Image below  https://i.postimg.cc/d1XS3H0g/image.png
Hope that isn't where the problem's coming from?

Here's firmware i download before i backed up my device, it doesn't have a "aboot" file in it.
https://i.postimg.cc/VkktdYb0/image.png
X3non
X3non
X3non
Recognized Contributor
22,062
18-04-2020, 10:08 PM
#15



(18-04-2020, 12:54 PM)ham_samm ...

zip and attach your aboot.img and abootbak then post it here
meanwhile what's the outcome of the following 4 commands
Code:

adb version
fastboot oem device-info
fastboot oem unlock_supported
fastboot oem get_unlock_ability
This post was last modified: 18-04-2020, 10:10 PM by X3non.
ham_samm
ham_samm
ham_samm
Senior Member
283
19-04-2020, 12:45 AM
#16
(18-04-2020, 10:08 PM)X3non
(18-04-2020, 12:54 PM)ham_samm ...

zip and attach your aboot.img and abootbak then post it here
meanwhile what's the outcome of the following 4 commands
Code:

adb version
fastboot oem device-info
fastboot oem unlock_supported
fastboot oem get_unlock_ability
Here's the outcome for the above commands https://i.postimg.cc/50gD3kS2/image.png
Kindly find attachment for zipped (aboot.img and abootbak)
Attached Files
.zip
Aboot and Abootbak.zip
Size: 642.83 KB / Downloads: 2
X3non
X3non
X3non
Recognized Contributor
22,062
20-04-2020, 11:38 AM
#17
(19-04-2020, 12:45 AM)ham_samm Here's the outcome for the above commands https://i.postimg.cc/50gD3kS2/image.png
Kindly find attachment for zipped (aboot.img and abootbak)

first, you should update your adb and fastboot ; download the latest platform tools @ https://www.hovatek.com/forum/thread-17104.html use the fastboot from within

BTW, my mistake as the last command should be "fastboot flashing get_unlock_ability" and not "fastboot oem get_unlock_ability"

outcome of strings on your aboot file

PS C:\Users\X3non\Desktop> ./strings.exe aboot.img | findstr /i unlock
Code:

Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system on this phone.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from your phone(a "factory data reset").
Unlock bootloader(may void warranty)
Do not unlock bootloader and restart phone
unlocked
creating unlock keys detect thread
Can't lock and unlock in the same desc
Device unlocked: %s
Device critical unlocked: %s
get_unlock_ability: %d
Device is unlocked! Skipping verification...
use_signed_kernel=%d, is_unlocked=%d, is_tampered=%d.
unlocked!
oem unlock is not allowed
unlock device to use this command
unlock device to erase keystore
frp-unlock
unlock device to flash keystore
oem unlock
oem unlock-go
flashing unlock
flashing unlock_critical
flashing get_unlock_ability

PS C:\Users\X3non\Desktop> ./strings.exe aboot.img | findstr /i oem
Code:

04 0000 OEM_ID1
General OEM rootca1
General OEM rootca1
General OEM rootca1
OEM panel override:%s
Verification with oem keystore failed. Use embedded certificate for verification
oem unlock is not allowed
oem unlock
oem unlock-go
oem lock
oem device-info
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge
oem select-display-panel
ham_samm
ham_samm
ham_samm
Senior Member
283
20-04-2020, 01:16 PM
#18
(20-04-2020, 11:38 AM)X3non
(19-04-2020, 12:45 AM)ham_samm Here's the outcome for the above commands https://i.postimg.cc/50gD3kS2/image.png
Kindly find attachment for zipped (aboot.img and abootbak)

first, you should update your adb and fastboot ; download the latest platform tools @ https://www.hovatek.com/forum/thread-17104.html use the fastboot from within

BTW, my mistake as the last command should be "fastboot flashing get_unlock_ability" and not "fastboot oem get_unlock_ability"

outcome of strings on your aboot file

PS C:\Users\X3non\Desktop> ./strings.exe aboot.img | findstr /i unlock
Code:

Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system on this phone.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from your phone(a "factory data reset").
Unlock bootloader(may void warranty)
Do not unlock bootloader and restart phone
unlocked
creating unlock keys detect thread
Can't lock and unlock in the same desc
Device unlocked: %s
Device critical unlocked: %s
get_unlock_ability: %d
Device is unlocked! Skipping verification...
use_signed_kernel=%d, is_unlocked=%d, is_tampered=%d.
unlocked!
oem unlock is not allowed
unlock device to use this command
unlock device to erase keystore
frp-unlock
unlock device to flash keystore
oem unlock
oem unlock-go
flashing unlock
flashing unlock_critical
flashing get_unlock_ability

PS C:\Users\X3non\Desktop> ./strings.exe aboot.img | findstr /i oem
Code:

04 0000 OEM_ID1
General OEM rootca1
General OEM rootca1
General OEM rootca1
OEM panel override:%s
Verification with oem keystore failed. Use embedded certificate for verification
oem unlock is not allowed
oem unlock
oem unlock-go
oem lock
oem device-info
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge
oem select-display-panel

I updated ADB and Fastboot then got this https://postimg.cc/DJ6JMWGF when i ran the command "fastboot flashing get_unlock_ability".
For both String Commands i got exact same output you got
https://postimg.cc/w1sQ1kCr
https://postimg.cc/pmXtxp3y
X3non
X3non
X3non
Recognized Contributor
22,062
20-04-2020, 03:50 PM
#19
(20-04-2020, 01:16 PM)ham_samm ...

it's either you didn't enable oem unlocking or you did but it trips back to disabled state upon reboot or there's no bootloader unlock support
when you tried unlocking bootloader, did you enable oem unlocking in developer options in settings? then reboot directly into fastboot
i.e
enable oem unlocking then send the "adb reboot-bootloader" command to boot straight into fastboot mode then send "fastboot flashing unlock"
ham_samm
ham_samm
ham_samm
Senior Member
283
21-04-2020, 03:01 AM
#20



(20-04-2020, 03:50 PM)X3non
(20-04-2020, 01:16 PM)ham_samm ...

it's either you didn't enable oem unlocking or you did but it trips back to disabled state upon reboot or there's no bootloader unlock support
when you tried unlocking bootloader, did you enable oem unlocking in developer options in settings? then reboot directly into fastboot
i.e
enable oem unlocking then send the "adb reboot-bootloader" command to boot straight into fastboot mode then send "fastboot flashing unlock"

"when you tried unlocking bootloader, did you enable oem unlocking in developer options in settings? then reboot directly into fastboot".          YES I DID ALL AND WAS 100% SURE
Aren't some devices bootloader not unlockable? ?
Pages (3): Previous 1 2 3 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram