Hovatek Forum DEVELOPMENT Android Bootloader refuses to unlock
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


Bootloader refuses to unlock

Bootloader refuses to unlock

Pages (2): Previous 1 2
Filip620
Filip620
Filip620
Enthusiastic Member
9
06-02-2021, 03:52 PM
#11



(05-02-2021, 07:32 PM)X3non
(05-02-2021, 10:24 AM)Filip620 You mean boot images or also other like recovery?
The boot image worked as we tested, but then I don't see a reason why I wouldn't be able to run a custom recovery.
The modified recovery images do not work, although the modified boot image does?

I am 100% positive that the recoveries are compatible with my model.

for your model yes but are they meant for the current build number of your device?
you can check the build number from the recoveries using method 7 @ https://www.hovatek.com/forum/thread-16005.html


(05-02-2021, 10:24 AM)Filip620 And by hardbrick 9008 mode you mean that I should be able to restore it with QFIL?

yes, you should

The build number from two custom twrp recoveries:

Code:

ro.build.display.id=lineage_A6020-eng 7.1.2 NJH47F 815636ce44 test-keys
ro.build.display.id=lineage_A6020-eng 7.1.2 NJH47F e43eb38251 test-keys

And stock firmware:
Code:

ro.build.display.id=A6020a41_S_S028_160922_ROW

I'm not sure why does this matter and if this is the expected output.

Thanks for help so far.
This post was last modified: 06-02-2021, 03:55 PM by Filip620.
X3non
X3non
X3non
Recognized Contributor
22,062
08-02-2021, 10:29 AM
#12
(06-02-2021, 03:52 PM)Filip620 I'm not sure why does this matter and if this is the expected output.
...

doesn't seem to match
found these, https://cloud.mail.ru/public/2uzu/aourh4zmD/ ; is this the same twrps you tried? if no, you can try both of them
Filip620
Filip620
Filip620
Enthusiastic Member
9
08-02-2021, 01:29 PM
#13
(08-02-2021, 10:29 AM)X3non
(06-02-2021, 03:52 PM)Filip620 I'm not sure why does this matter and if this is the expected output.
...

doesn't seem to match
found these, https://cloud.mail.ru/public/2uzu/aourh4zmD/ ; is this the same twrps you tried? if no, you can try both of them

The same result. I did try from the same author as these just a different version I think, and from a different author and with different versions. And the ro.build.display.id is not really that different.

I think the recoveries are not the problem here.
This post was last modified: 08-02-2021, 02:39 PM by Filip620.
X3non
X3non
X3non
Recognized Contributor
22,062
09-02-2021, 09:54 AM
#14
(08-02-2021, 01:29 PM)Filip620 The same result. I did try from the same author as these just a different version I think, and from a different author and with different versions. And the ro.build.display.id is not really that different.

I think the recoveries are not the problem here.

what's the kernel and android version of your device ; 3.10.49 and android 6?
post a link to your stock recovery.img
This post was last modified: 09-02-2021, 09:56 AM by X3non.
Filip620
Filip620
Filip620
Enthusiastic Member
9
13-02-2021, 12:00 PM
#15



(09-02-2021, 09:54 AM)X3non
(08-02-2021, 01:29 PM)Filip620 The same result. I did try from the same author as these just a different version I think, and from a different author and with different versions. And the ro.build.display.id is not really that different.

I think the recoveries are not the problem here.

what's the kernel and android version of your device ; 3.10.49 and android 6?
post a link to your stock recovery.img

I'm not sure what was your plan, but thanks for all help anyway.

I finally solved this problem.

Code:

fastboot oem unlock
will probably never work, at least on A6020a41.

But
Code:

fastboot boot twrp.img
or
Code:

fastboot flash recovery twrp.img
should work even though
Code:

fastboot oem device-info
shows that the bootloader is NOT unlocked.

This is the absolutely last resort, if it still doesn't, you can flash the attached aboot.img file to the aboot partition (probably also abootbak partition) with QFIL, and then it will work, the file is from an A6020a40 user, but it worked for my A6020a41.
Or if you have qfil flashable stock rom, and it is for the A6020a40, the emmc_appsboot.mbn file is the aboot partition image, if you flash that instead of the one I attached, it will also work with fastboot boot and fastboot flash but it doesn't boot to yourcustom recovery but is still stuck at the fastboot screen, try to reboot into system and then to fastboot mode and try again, if it is still stuck at the fastbot screen after fasstboot boot twrp.img also make sure you have completed the initial setup and enabled oem unlocking in the developer settings along with usb debugging and authorized access from your pc.

But again, you shouldn't need to flash the aboot image. Try the fastboot boot and flash commands first.
This post was last modified: 17-02-2021, 03:13 PM by Filip620.
Attached Files
.img
aboot.img
Size: 1 MB / Downloads: 2
hovatek
hovatek
hovatek
Administrator
49,570
15-02-2021, 08:53 AM
#16
(13-02-2021, 12:00 PM)Filip620 I'm not sure what was your plan, but thanks for all help anyway.

I finally solved this problem.

Code:

fastboot oem unlock
will probably never work, at least on A6020a41.

But
Code:

fastboot boot twrp.img
or
Code:

fastboot flash recovery twrp.img
should work even though
Code:

fastboot oem device-info
shows that the bootloader is NOT unlocked.

This is the absolutely last resort, if it still doesn't, you can flash the attached aboot.img file to the aboot partition (probably also abootbak partition) with QFIL, and then it will work, the file is from an A6020a40 user, but it worked for my A6020a41.

But again, you shouldn't need to flash the aboot image. Try the fastboot boot and flash commands first.

Thanks for sharing

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Pages (2): Previous 1 2
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram