Develop Bugs

[Q] Bootloader Not Unlocking?

I got a m8 yesterday after switching to T-mobile and I would really like to unlock/root/mod it. I've rooted other phones before and haven't had this much trouble with them.
I get through all of the steps, run fastboot flash unlocktoken Unlock_code.bin which runs fine (gives option to unlock or not, I select yes with the power button) and reboots the phone. The phone is wiped as it's supposed to be, and I turn off the fast boot and turn on usb debugging in the options after the basic set up. When I boot it into fastboot to install the recovery, it still says *** LOCKED *** at the top of the screen, and I get this when I try to install it
XXX-Inspiron-N5010:~/Downloads/fastboot$ sudo fastboot flash recovery Recovery.img
[sudo] password for XXX:
target reported max download size of 1830608896 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.635s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.169s
I've tried this on two different computers and with different recovery files, one running Windows 8 and the other Ubuntu five times and I can't find anyone else that has had the same problem. I would appreciate any help with this as it's getting quite frustrating

Ditt0 - I have the same problem
Kittycatpenut said:
I got a m8 yesterday after switching to T-mobile and I would really like to unlock/root/mod it. I've rooted other phones before and haven't had this much trouble with them.
I get through all of the steps, run fastboot flash unlocktoken Unlock_code.bin which runs fine (gives option to unlock or not, I select yes with the power button) and reboots the phone. The phone is wiped as it's supposed to be, and I turn off the fast boot and turn on usb debugging in the options after the basic set up. When I boot it into fastboot to install the recovery, it still says *** LOCKED *** at the top of the screen, and I get this when I try to install it
XXX-Inspiron-N5010:~/Downloads/fastboot$ sudo fastboot flash recovery Recovery.img
[sudo] password for XXX:
target reported max download size of 1830608896 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.635s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.169s
I've tried this on two different computers and with different recovery files, one running Windows 8 and the other Ubuntu five times and I can't find anyone else that has had the same problem. I would appreciate any help with this as it's getting quite frustrating
Click to expand...
Click to collapse
I'm experiencing the same thing. Can't flash recovery. Have followed instructions to Unlock bootloader through HTCdev and have gone through the process numerous times on different machines without any apparent error. Please help!
target reported max download size of 1830608896 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.479s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.093s

Dumb question #1
Have you tried different USB ports just to zero out all variables
---------- Post added at 07:07 AM ---------- Previous post was at 07:07 AM ----------
Either of you two
---------- Post added at 07:54 AM ---------- Previous post was at 07:07 AM ----------
@Kittycatpenut
@andersonwittekind
I would ask in the T-Mobile forum only cause you might find an answer faster
http://forum.xda-developers.com/showthread.php?t=2725099

Hard Bricked Kindle Fire HD 8.9 jem BC09

Hello,
I've hardbricked a Kindle Fire HD 8.9 jem BC09 which was running 8.5.1 before it became a paperweight.
I successfully rooted the device with Bin4rys method, at which point I followed cyanogenmod's directions on installing the bootloader(otter2 CM install instructions on their website)
I verified the MD5 checksum for the bootloader before proceeding.
Here's the results of my mishap:
Volume in drive C is Windows7_OS
Volume Serial Number is 3A6D-6FAB
Directory of C:\Users\User\Downloads
10/10/2015 03:17 PM <DIR> .
10/10/2015 03:17 PM <DIR> ..
10/10/2015 02:29 PM <DIR> Old DLs
10/10/2015 03:17 PM 8,349,292 otter2-freedom-boot-10.4.6.img
10/10/2015 03:17 PM 8,349,292 otter2-twrp-2.6.3.1-recovery.img
10/10/2015 03:13 PM 232,908 otter2-u-boot-prod-10.2.4.bin
04/29/2007 06:12 AM 591,872 WinMD5.exe
10/10/2015 03:15 PM 268,376 winmd5free.zip
5 File(s) 17,791,740 bytes
3 Dir(s) 370,367,225,856 bytes free
C:\Users\User\Downloads>fastboot -i 0x1949 flash bootloader otter2-u-
boot-prod-10.2.4.bin
< waiting for any device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (227 KB)...
OKAY [ 0.020s]
writing 'bootloader'...
OKAY [ 0.040s]
finished. total time: 0.060s
C:\Users\User\Downloads>fastboot -i 0x1949 flash recovery otter2-twrp
-2.6.3.1-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8153 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 1.014s
C:\Users\User\Downloads>fastboot -i 0x1949 flash boot otter2-freedom-
boot-10.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8153 KB)...
OKAY [ 0.452s]
writing 'boot'...
OKAY [ 0.562s]
finished. total time: 1.014s
C:\Users\User\Downloads>fastboot -i 0x1949 oem recovery
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\User\Downloads>fastboot -i 0x1949 getvar product
< waiting for any device >
Click to expand...
Click to collapse
At the point where I attempted to reboot into recovery, the device became completely bricked. No response to power on, etc.
As I've been browsing for the past hour it seems to me that this device is virtually unbrickable aside from sending it to Amazon. I have contacted "Chris" at [email protected] and am awaiting his response. In the meantime, if anyone else has any ideas of how to proceed please let me know!
Regards,
siriu5

You can check following options:
1. Send back to Amazon (If it's under warranty).
2. Replace the mother board (You can get at $50 online).
3. Follow this thread: http://forum.xda-developers.com/showthread.php?t=2581124 . (only if you are good at SMD soldering).

You reported this as a bug on the cyanogenmod wiki ( https://jira.cyanogenmod.org/browse/WIKI-194 ) and though the text mentions 'jem' several times, you linked to the otter2 install page.
https://wiki.cyanogenmod.org/w/Install_CM_for_jem has files for the jem (as kfhd8) in 'step 2'...
I don't know how to fix the device but perhaps knowing that the files flashed were for the "Kindle Fire 2nd gen (otter2)" instead of the "Kindle Fire HD 8.9 (jem)" will help someone else in the debugging process.

PsychoI3oy said:
You reported this as a bug on the cyanogenmod wiki ( ) and though the text mentions 'jem' several times, you linked to the otter2 install page.
x has files for the jem (as kfhd8) in 'step 2'...
I don't know how to fix the device but perhaps knowing that the files flashed were for the "Kindle Fire 2nd gen (otter2)" instead of the "Kindle Fire HD 8.9 (jem)" will help someone else in the debugging process.
Click to expand...
Click to collapse
Yeah, I just caught this. Definitely my own mistake. My problem was I google searched "cyanogenmod install kindel hd fire gen 2" and tried the first link that showed up. Dope.
Anyone want a bricked KFHD2? I'll send if you pay for shipping. Cheers!

honor 6x rolling back to marshmallow from official site relocks boot loader

With great help.from.the xda friends I somehow from the bricked device of nougat rolled back to Marshmallow from official site ....post update of the marshmallow then updated it to nougat using the firmfinder method the following things Happened after that I'll list down them as follows
1.the boot up had a start message that device has failed verification and won't work properly in red color
2 you have to manually press the power button on to proceed to the system boot up
3 now the phone works fine as usual with all the developer option enabled
4 the when I tried to install the twrp using reboot boot loader the screen shows phone is unlocked in fastboot mode (technical it's unlocked boot loader)
5 when I tried to install the twrp it flashed fine but later when. I tried to reboot on recovery it didn't show up on twrp screen
6 only Huawei factory reset emui 5 stock page came
To have a successful twrp installed
Just unlock the boot loader again with oem unlock
Since the mobile is relocked after we roll back to Marshmallow
Still we get our usual warning message in yellow colour doesn't means the phone is unlocked neither the fastboot screen as well
Another good news is when u roll back to Marshmallow official site itself mentions that only the usual yellow color warning.message will be your start up screen (technically warranty is not void :good::fingers-crossed
Once you unlocked your device proceed with twrp Berlin file and all goes greAt and smooth from there on
The red color warning message of device verification failed no.more appears
Happy rooting guys :good:
Cheers

That's a great and comprehensive guide :good:

same problem here ..
Bootloader showing Bootloader unlocked but no commands working
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
---------- Post added at 03:30 PM ---------- Previous post was at 03:29 PM ----------
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-b
erlin.img
target reported max download size of 471859200 bytes
sending 'recovery' (25254 KB)...
OKAY [ 0.793s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.793s

aamszia said:
same problem here ..
Bootloader showing Bootloader unlocked but no commands working
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
---------- Post added at 03:30 PM ---------- Previous post was at 03:29 PM ----------
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-b
erlin.img
target reported max download size of 471859200 bytes
sending 'recovery' (25254 KB)...
OKAY [ 0.793s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.793s
Click to expand...
Click to collapse
you must get your unlocking code from honor to do s

(remote:unlock failed) Bootloader

Hi, Yeah I tried to flash the unlock image,
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.053s
Now I am in latest version Nougat

I fixed it ....
Solution ..just try one more time get new unlock_bootloader.IMG then flash it ...Enjoy

viknesh war said:
Hi, Yeah I tried to flash the unlock image,
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.053s
Now I am in latest version Nougat
Click to expand...
Click to collapse
Yup i was also facing the same problem a new bootloader image will fix it just request for a new bootloader image from zuk.

viknesh war said:
I fixed it ....
Solution ..just try one more time get new unlock_bootloader.IMG then flash it ...Enjoy
Click to expand...
Click to collapse
Thanks a lot bro.. I downloaded a new unlock_bootloader. Img file, and it worked just fine.
Actually I entered wrong serial number in zuk website while downloading the img file maybe because of that it didn't work at first

BND-L24 8.0 Root

Can my model be rooted, and if so, could someone link me a tutorial?

CitrusMei said:
Can my model be rooted, and if so, could someone link me a tutorial?
Click to expand...
Click to collapse
Is your bootloader unlocked? Private message me and I can explain how to root with magisk. I just did it today so I know exactly what to do.

allrockedout said:
Is your bootloader unlocked? Private message me and I can explain how to root with magisk. I just did it today so I know exactly what to do.
Click to expand...
Click to collapse
Could you help me as well, I have the mate se so I believe it should work as well. Thx.

MadGoogler78 said:
Could you help me as well, I have the mate se so I believe it should work as well. Thx.
Click to expand...
Click to collapse
Sure are you on oreo? Is your bootloader unlocked?

It is. Verified unlocked bootloader and 8.0

Just as a note using the twrp_p10 image files does not work... on my mate se
C:\Users\Bryan\Desktop\Minimal ADB and Fastboot>fastboot flash recovery twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery' (24952 KB)...
OKAY [ 0.988s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 1.010s

madgoogler said:
Just as a note using the twrp_p10 image files does not work... on my mate se
C:\Users\Bryan\Desktop\Minimal ADB and Fastboot>fastboot flash recovery twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery' (24952 KB)...
OKAY [ 0.988s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 1.010s
Click to expand...
Click to collapse
If your on oreo thats the wrong command you should do (fastboot flash recovery_ramdisk )

dcraffam said:
If your on oreo thats the wrong command you should do (fastboot flash recovery_ramdisk )
Click to expand...
Click to collapse
i was able to successful in flashing the ramdisk but still no twrp will show up.
C:\Users\Bryan\Desktop\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 0.979s]
writing 'recovery_ramdisk'...
OKAY [ 0.210s]
finished. total time: 1.194s
what am i missing here
---------- Post added at 08:49 PM ---------- Previous post was at 08:26 PM ----------
madgoogler said:
i was able to successful in flashing the ramdisk but still no twrp will show up.
C:\Users\Bryan\Desktop\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 0.979s]
writing 'recovery_ramdisk'...
OKAY [ 0.210s]
finished. total time: 1.194s
what am i missing here
Click to expand...
Click to collapse
ok like an idiot i forgot to hold the volume up button on reboot. Now im in with twrp recovery
thanks guys. might want to make this a sticky?

please share the file to works in honor 7x BND-L24 8.0
when entering with vol + and power the green android comes out and says recovery error

gusta2322 said:
please share the file to works in honor 7x BND-L24 8.0
when entering with vol + and power the green android comes out and says recovery error
Click to expand...
Click to collapse
Flash in fastboot. It's stock recovery
https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=drivesdk
Fastboot flash recovery_ramdisk recovery_ramdis.img
---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------
allrockedout said:
Flash in fastboot. It's stock recovery
https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=drivesdk
Fastboot flash recovery_ramdisk recovery_ramdis.img
Click to expand...
Click to collapse
If you rooted also need kernel.
https://drive.google.com/file/d/1hYHlyNpJUfvYzM9EOli2ASKp3cnx98_L/view?usp=drivesdk
Fastboot flash kernel kernel.img

allrockedout said:
Flash in fastboot. It's stock recovery
https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=drivesdk
Fastboot flash recovery_ramdisk recovery_ramdis.img
---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------
If you rooted also need kernel.
https://drive.google.com/file/d/1hYHlyNpJUfvYzM9EOli2ASKp3cnx98_L/view?usp=drivesdk
Fastboot flash kernel kernel.img
Click to expand...
Click to collapse
thx men but a need twrp recovery please share

gusta2322 said:
thx men but a need twrp recovery please share
Click to expand...
Click to collapse
Fastboot flash ramdisk_recovery complete_twrp_ramdisk.img make backups in twrp you will need micro SD card because internal storage is not accessible.
https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Than in twrp click install image and install p 10 lite twrp. Everything's working in there better.
https://drive.google.com/file/d/1-dx_fQltWmIMcAFrJsuWtgHnhqVM22n4/view?usp=drivesdk
This is instructions if your coming from stock to twrp for first time.