Database Info

Tried to update to CM 11 / 4.4 KitKat and got "unrecoverable bootloader error"

Tried to update to CM 11 / 4.4 KitKat and got "unrecoverable bootloader error"
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o

ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
You can read this to see if it helps..good luck..:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2528313

ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
Sorry, but after reading your post 4 times I still have no idea what you actually did.....
If you still have access in ADB (since you can't access the bootloader??) the link LMK gave you may save your bacon.
If you don't have any kind of access: ADB or fastboot and you do not have nvFlash blobs - sorry, you bricked.

Can I access fastboot when I get the menu at RCK / Android / Wipe? Because if I click con any of these its says that bootloader is corrupted.
What's the Command to fix TWRP using a computer / or other Android device?

ANDROiD_eKa said:
Can I access fastboot when I get the menu at RCK / Android / Wipe?
Click to expand...
Click to collapse
Does it say something about fastboot in the upper left corner?
ANDROiD_eKa said:
What's the Command to fix TWRP using a computer / or other Android device?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)

_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Thanks _that for the advice...:good: You are the expert in this area... I am done with my job to bring you in here for helps..haha...

_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Yes it says
Code:
Starting Fastboot USB download protocol

Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?

ANDROiD_eKa said:
Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?
Click to expand...
Click to collapse
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:

LetMeKnow said:
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:
Click to expand...
Click to collapse
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....

berndblb said:
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....
Click to expand...
Click to collapse
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..

LetMeKnow said:
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..
Click to expand...
Click to collapse
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???

berndblb said:
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???
Click to expand...
Click to collapse
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...

LetMeKnow said:
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...
Click to expand...
Click to collapse
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image

berndblb said:
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image
Click to expand...
Click to collapse
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
buster99 said:
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer, as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
Click to expand...
Click to collapse
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?

ANDROiD_eKa said:
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?
Click to expand...
Click to collapse
Buster99 deserves a medal or something for this post. Dozens of people have recovered from a brick using his method!
Glad you got it going!

Updating to 6.0....and bricked

Stock, unrooted xt1540. Got the update notification this morning, so excited. After updating, it's boot looping and the M logo is the furthest it can go.
Tried to fastboot flash back to old 5.1.1 factory image, "image validation failed". Maybe because boot loader got updated and won't roll back?
All I can think of now is to wait for the 6.0 factory image and try that again, but I may end up waiting for it too long.
Any suggestions? Thanks!

What about the images at http://forum.xda-developers.com/2015-moto-g/general/ota-moto-g3-marshmallow-ota-links-t3284308

Try in fastboot clear the cache and data ...

have you tried using twrp to just install a cm rom or something similar?
worst case scenario you can use twrp to force the soak test images onto their respective partitions. if your bootloader was updated the soak test will run...even if it bootloops for any reason, then at least you've taken one step forward again.

MrTooPhone said:
What about the images at http://forum.xda-developers.com/2015-moto-g/general/ota-moto-g3-marshmallow-ota-links-t3284308
Click to expand...
Click to collapse
I wish I could resume the OTA, even manually, but right now I can only go to bootloader, not even the stock recovery....Thanks for the idea, though! Really appreciate it.

hp420 said:
have you tried using twrp to just install a cm rom or something similar?
worst case scenario you can use twrp to force the soak test images onto their respective partitions. if your bootloader was updated the soak test will run...even if it bootloops for any reason, then at least you've taken one step forward again.
Click to expand...
Click to collapse
I just tried flash in the twrp.img, got declined by bootloader again...
Now is there factory images for the soak test? Thanks!!

lexer98 said:
Try in fastboot clear the cache and data ...
Click to expand...
Click to collapse
clearing cache went through, but clearing data failed. Rebooting to bootloader mode and try returning to stock again, still no go...

In fastboot mode, I can flast logo, fsg, NON-HLOS, bootloader, recovery -- all from 5.1.1 factory image, but when I tried to flash boot or system chunks, it says:
D:\Desktop\g\Mfastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 10.573s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.042s
Is my only option to wait for the MM factory image....

alvin612 said:
I just tried flash in the twrp.img, got declined by bootloader again...
Now is there factory images for the soak test? Thanks!!
Click to expand...
Click to collapse
Well....yes and no.
http://forum.xda-developers.com/201...-devs-moto-g3-xt1540-soak-test-files-t3255643
The images all flash in fastboot except the system one, which requires using adb shell while booted to twrp. You have to use a dd command to force the system.img into the correct partition.

Earlier today I had to give up on this osprey because of limited bandwith for fix.
Thanks again for everyone's help!!

My phone got bricked after trying to downgrade from MM to LP
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?

JulesSDK said:
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?
Click to expand...
Click to collapse
I contacted Motorola. Warranty covers my situation. Going to ask for a replacement.

JulesSDK said:
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?
Click to expand...
Click to collapse
Unlock the bootloader and then try flashing. I was in a similar situation once, was getting failed messages when trying to flash official signed factory images. Unlocked the bootloader and then tried to flash and voila, everything flashed smoothly. No harm in trying unless you are worried about warranty.

Huawei Honor 6 H60-L12 bricked

Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos

janos666 said:
Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos
Click to expand...
Click to collapse
Instead of using the honor multi tool, why don't you use the Android SDK platform tools and connect to your phone through adb. You can solve any problem using that. You have to do everything manually but it works and never disappoints as long as you can enter fastboot mode.
Download android SDK and install it. Run the program and only choose platform tools to download. You don't need anything else
Download the latest firmware for your phone and unzip it to get dload folder which will have an update.app in it.
Download Huawei update extractor and open update.app in it.
Extract recovery, boot, Cust and system images from update.app and save them to the platform tools folder.
Flash them using adb and then do a forced update.
Will work wonders. If you need any help or need more info, please let me know.

Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos

janos666 said:
Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos
Click to expand...
Click to collapse
My expertise are quite limited but may be, just may be (wishful thinking), you can to flash the twrp recovery specific for your phone. Boot into that and flash a custom ROM from there.
It may not work as I guess, boot.img is needed before entering recovery but give it a try. It never hurts.

Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
Click to expand...
Click to collapse
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos

janos666 said:
Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos
Click to expand...
Click to collapse
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.

Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04

janos666 said:
Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04
Click to expand...
Click to collapse
Well, I have mentioned DigiGoon in the previous reply. May be he can help a bit.

@janos666
You can always put your desired boot.img in a flashable zip, and flash it via TWRP recovery.

Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery

janos666 said:
Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery
Click to expand...
Click to collapse
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.

muradulislam said:
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.
Click to expand...
Click to collapse
zinko_pt said:
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.
Click to expand...
Click to collapse
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.

janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
Sure. I would go from there as I sometimes mixed boot.img from LP or MM and always got bootloop. I would stick to IMG files from last installed ROM.

janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?

DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Hi DigiGoon !
Sorry, which one is the flash transition package?
Which parts to flash from it?
Which is notification LED? I can see only one red LED blinking sometimes, but only when battery is low.

DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Isn't there an option to flash all img files from fastboot?
P.S. I just got new info from the guy who flashed it first time. He says he tried to write version:
H60-L02-L12_emui3.1_android5.1_c00B535

Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Click to expand...
Click to collapse
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me

janos666 said:
Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me
Click to expand...
Click to collapse
Some threads mention of locking and unlocking your device again. Give that a try. May help...

muradulislam said:
Some threads mention of locking and unlocking your device again. Give that a try. May help...
Click to expand...
Click to collapse
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.

janos666 said:
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.
Click to expand...
Click to collapse
The info you are missing is device id, another user got his device id using Huawei hacker toolkit v 1.4, his model was h60-L02. May be you can give it a try.
You have to lock it before trying to unlock again.
Fastboot OEM lock xxxxxxxxxxxxxxxx...

Completely wiped phone

Well, I was messing around in TWRP without really knowing what I was doing, and selected all boxes in the Wipe section. Now, when I try to install the stock rom, I get an error telling me that gpt.bin can't be downgraded, and when I try to sideload a rom via TWRP, I get another error saying that the .zip file is invalid. Can't send pictures of anything on the phone since it is the only one I have. Sorry.

Are you using fastboot to flash stock ROM? Then simply leave the gpt.bin and bootloader.img and flash the rest. The phone should boot up fine.
For the Custom ROM, maybe the zip file is corrupted, have you compared SHA/MD5 hash sums if one is provided with the download? They are a good way to check that downloaded file is complete and not corrupted.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Are you using fastboot to flash stock ROM? Then simply leave the gpt.bin and bootloader.img and flash the rest. The phone should boot up fine.
For the Custom ROM, maybe the zip file is corrupted, have you compared SHA/MD5 hash sums if one is provided with the download? They are a good way to check that downloaded file is complete and not corrupted.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Already tried using fastboot and leaving the gpt out, but the phone keep getting stuck in a bootloop where it goes into recovery and tries to wipe something, and get an error(failed to mount /data). And the rom is not corrupted, since I tried a LOT of different sources, and nobody ever complained of it being corrupted or so.

ctcsilva said:
Already tried using fastboot and leaving the gpt out, but the phone keep getting stuck in a bootloop where it goes into recovery and tries to wipe something, and get an error(failed to mount /data). And the rom is not corrupted, since I tried a LOT of different sources, and nobody ever complained of it being corrupted or so.
Click to expand...
Click to collapse
i would suggest you to revert back to og firmware and then trying to flash twrp again then you can try to flash roms again
just go into fastboot and follow the instructions
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
i was too in this situation but in a different device hope this helps you

Amar 721 said:
i would suggest you to revert back to og firmware and then trying to flash twrp again then you can try to flash roms again
just go into fastboot and follow the instructions
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
i was too in this situation but in a different device hope this helps you
Click to expand...
Click to collapse
Can't actually install those firmwares too, since I keep getting the error followed by the bootloop.

ctcsilva said:
Can't actually install those firmwares too, since I keep getting the error followed by the bootloop.
Click to expand...
Click to collapse
you get errors on adb?
if no then just press the power and volume down button simultaneously then release the dont go into recovery wait there and follow the guide
let it be a side just after pressing the buttons dont go to recovery or anything just wait there and do relock the device bootloader using adb and fastboot you can get tutorials of it everywhere

Amar 721 said:
you get errors on adb?
if no then just press the power and volume down button simultaneously then release the dont go into recovery wait there and follow the guide
let it be a side just after pressing the buttons dont go to recovery or anything just wait there and do relock the device bootloader using adb and fastboot you can get tutorials of it everywhere
Click to expand...
Click to collapse
Yes, I do. Just tried right now.
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot oem lock begin
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.104s]
finished. total time: 0.105s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot flash partition zip/gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.168s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Along with version downgraded for primary_gpt on bootloader
The same thing with boot.img

@ctcsilva : Flash TWRP
Code:
fastboot flash recovery twrp.img
where twrp.img is the name of twrp file. Now boot into TWRP, go to Mount and check that /data is selected, if not, then mark it and select back.
Now go to Wipe>Advanced Wipe. Select data and tap Repair or Change File System. Now select Repair File system and swipe to confirm. Now go to Wipe> Factory Reset and swipe to confirm. Then Reboot>bootloader.
Connect the phone to pc and flash stock recovery
Code:
fastboot flash recovery recovery.img
, and boot into it. Press and hold power and press volume up key once, you should see the options now. Select factory reset and confirm. Now reflash the stock firmware from fastboot and see if it boots.
Edit :- Use this guide, do not attempt to relock bootloader, it won't lock unless every file is flashed, which is again impossible because the firmware is older than the one present in the phone.
Broadcasted from Zeta Reticuli

ctcsilva said:
Yes, I do. Just tried right now.
Along with version downgraded for primary_gpt on bootloader
The same thing with boot.img
Click to expand...
Click to collapse
oem is not unlocked : ( you should try asking help from a senior member like ishubhamsingh or other i guess they can definetly help you

How to change the red boot warning back to the normal unlocked bootloader start warn.

To be clear im trying to bring back the old "boot loader is unlocked and software integrity cannot be guaranteed" boot message from the red one that says "Your device is corrupt. It can’t be trusted and may not work properly." Now I no this topic has already been on the forums but I read them, and made several attempts to fix the issue but was unsuccessful. every time I end up losing my all my **** and as soon as i upgrade to the latest pie ota it goes right back to the red boot message. One time I even hard bricked my phone and had to use the msmdownloadtool to get me back to hydrogen os and still the same thing happend when I upgraded to pie. Can anyone point me in the right direction on how to fix this problem.
p.s. I know its not a "problem" really but its one of those things that’s been pestering me for over a month. thanks for your concern.

Did you use in-built updater or flashed pie via twrp?
If you flashed by twrp, you may need to flash twice for both a and b bootslots.
You may try to lock bootloader, use msm again then update pie.
After that try to unlock it may fix

Linux_fart_18.3 said:
To be clear im trying to bring back the old "boot loader is unlocked and software integrity cannot be guaranteed" boot message from the red one that says "Your device is corrupt. It can’t be trusted and may not work properly." Now I no this topic has already been on the forums but I read them, and made several attempts to fix the issue but was unsuccessful. every time I end up losing my all my **** and as soon as i upgrade to the latest pie ota it goes right back to the red boot message. One time I even hard bricked my phone and had to use the msmdownloadtool to get me back to hydrogen os and still the same thing happend when I upgraded to pie. Can anyone point me in the right direction on how to fix this problem.
p.s. I know its not a "problem" really but its one of those things that’s been pestering me for over a month. thanks for your concern.
Click to expand...
Click to collapse
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter

abasba said:
Did you use in-built updater or flashed pie via twrp?
If you flashed by twrp, you may need to flash twice for both a and b bootslots.
You may try to lock bootloader, use msm again then update pie.
After that try to unlock it may fix
Click to expand...
Click to collapse
unfortunate for me ive tried all the above except locking bootloader before msm which i have also tried both separtatly but not in that order.

ab123pro said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
ill give it a try thanks also do you know the command to switch partitions when in fastboot? im stuck on a partion and stuck only rebooting to fastboot cant flash twrp img or boot img id really appreciate it any know the command

Linux_fart_18.3 said:
ill give it a try thanks also do you know the command to switch partitions when in fastboot? im stuck on a partion and stuck only rebooting to fastboot cant flash twrp img or boot img id really appreciate it any know the command
Click to expand...
Click to collapse
Run "fastboot boot twrp-3.3.1-3-enchilada.img" in command line https://androidfilehost.com/?fid=6006931924117908950
then from within twrp flash twrp installer - https://androidfilehost.com/?fid=6006931924117908949
and magisk if you want root

ab123pro said:
Run "fastboot boot twrp-3.3.1-3-enchilada.img" in command line https://androidfilehost.com/?fid=6006931924117908950
then from within twrp flash twrp installer - https://androidfilehost.com/?fid=6006931924117908949
and magisk if you want root
Click to expand...
Click to collapse
sudo fastboot boot ./twrp-3.2.3-x_blu_spark_v9.91_op6.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.924s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.939s
every time. thats why im in need of a command to get me back to the (b) partition and also
fastboot –set-active=_b just get me "waiting for device" and nothing more.

Linux_fart_18.3 said:
sudo fastboot boot ./twrp-3.2.3-x_blu_spark_v9.91_op6.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.924s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.939s
every time. thats why im in need of a command to get me back to the (b) partition and also
fastboot –set-active=_b just get me "waiting for device" and nothing more.
Click to expand...
Click to collapse
looks like your boot partition got corrupted some how im not sure tho
maybe try to flash one of those fastboot roms - https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665