Database Info

[Q] 4.4.4, Rooted. How to flash the 5.0-ota.zip? Tried but failed.

After seeing the article:"[INFO] Nexus 5 OTA Help-Desk", I did the following things:
1. downloaded the ota.zip from the article above, and copied it to the / of Nexus5.
2. restart to Recovery mode(TWRP), click "Install", and select the zip
3. Failed, It said that
"E:Error executing updater binary in zip '/sdcard/c1a33......zip'
Error flashing zip '/sdcard/c1a33......zip'"
Did anyone else met this problem? When update from 4.4.2 to 4.4.4, I did it in the same way, anything different?

Can you elaborate what the "blablalba" is? Odds are you have made some modifications to /system and that's what's causing it, but without knowing what that error is, it's kinda difficult to say for sure.

DodouWang said:
After seeing the article:"[INFO] Nexus 5 OTA Help-Desk", I did the following things:
1. downloaded the ota.zip from the article above, and copied it to the / of Nexus5.
2. restart to Recovery mode(TWRP), click "Install", and select the zip
3. Failed, It said that "flash error blablalba..."
Did anyone else met this problem? When update from 4.4.2 to 4.4.4, I did it in the same way, anything different?
Click to expand...
Click to collapse
You need stock recovery! Only stock has that said option
called update via adb sideload

_MetalHead_ said:
Can you elaborate what the "blablalba" is? Odds are you have made some modifications to /system and that's what's causing it, but without knowing what that error is, it's kinda difficult to say for sure.
Click to expand...
Click to collapse
Thanks, The Error message is :
E:Error executing updater binary in zip '/sdcard/c1a33......zip'
Error flashing zip '/sdcard/c1a33......zip'

gamer.11 said:
You need stock recovery! Only stock has that said option
called update via adb sideload
Click to expand...
Click to collapse
Incorrect. You do not need stock recovery to flash an OTA.
---------- Post added at 12:55 AM ---------- Previous post was at 12:53 AM ----------
DodouWang said:
Thanks, The Error message is :
E:Error executing updater binary in zip '/sdcard/c1a33......zip'
Error flashing zip '/sdcard/c1a33......zip'
Click to expand...
Click to collapse
What version of TWRP are you on?

gamer.11 said:
You need stock recovery! Only stock has that said option
called update via adb sideload
Click to expand...
Click to collapse
Do you mean that I should return to stock? According to the article "http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701", it will erase all my data.
Is there any method to update to 5.0 without my data erased?

_MetalHead_ said:
Incorrect. You do not need stock recovery to flash an OTA.
---------- Post added at 12:55 AM ---------- Previous post was at 12:53 AM ----------
What version of TWRP are you on?
Click to expand...
Click to collapse
I have just update TWRP to 2.8.1.0, the newest.
Did the update need more than 1G stroage left ? I have only 900M left.

DodouWang said:
Do you mean that I should return to stock? According to the article "http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701", it will erase all my data.
Is there any method to update to 5.0 without my data erased?
Click to expand...
Click to collapse
You don't need stock recovery. What KK build are you on? It's under settings > about phone. And which OTA file are you trying to flash?

_MetalHead_ said:
Incorrect. You do not need stock recovery to flash an OTA.
---------- Post added at 12:55 AM ---------- Previous post was at 12:53 AM ----------
What version of TWRP are you on?
Click to expand...
Click to collapse
NOTE: Starting with Android 5.0 (LRX21O) you MUST sideload the OTA in a STOCK RECOVERY. No exceptions. .
DodouWang said:
Do you mean that I should return to stock? According to the article "http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701", it will erase all my data.
Is there any method to update to 5.0 without my data erased?
Click to expand...
Click to collapse
Flash the stock recovery from previous system image and then download the zip file,(what you are mentioning is the factory images) from here and then flash without loosing data as a normal android update.

_MetalHead_ said:
You don't need stock recovery. What KK build are you on? It's under settings > about phone. And which OTA file are you trying to flash?
Click to expand...
Click to collapse
Build number is KTU84P
and the zip is : 5.0 LRX21O-from-4.4.4 KTU84P:android.clients.google.com/pa...P.c1a33561.zip. I cannot post urls as a newbie of the forum.
seemed right.

gamer.11 said:
NOTE: Starting with Android 5.0 (LRX21O) you MUST sideload the OTA in a STOCK RECOVERY. No exceptions. .
Flash the stock recovery from previous system image and then download the zip file,(what you are mentioning is the factory images) from here and then flash without loosing data as a normal android update.
Click to expand...
Click to collapse
I stand corrected. I didn't know it changed with 5.0.

gamer.11 said:
Flash the stock recovery from previous system image
Click to expand...
Click to collapse
How to do that? Is there any article for me to follow?
Thanks.

DodouWang said:
How to do that? Is there any article for me to follow?
Thanks.
Click to expand...
Click to collapse
It's just a simple fastboot command- "fastboot flash recovery [recovery name].img" with no quotes.
Do you know how to use fastboot?

DodouWang said:
How to do that? Is there any article for me to follow?
Thanks.
Click to expand...
Click to collapse
If you have any other factory images with you, let it be anything like 4.4.4 or .4.42 or anything, unzip the image-hammerhead-xxxxx.zip and you will find a recovery.img file.
flash this recovery like you flashed twrp
Code:
fastboot flash recovery recovery.img
and you will get the stock recovery boot into that and you will see, "apply update from adb"
choose that option and then when asked use adb to push the update.zip into the phone.
_MetalHead_ said:
I stand corrected. I didn't know it changed with 5.0.
Click to expand...
Click to collapse
No problems :highfive:

_MetalHead_ said:
It's just a simple fastboot command- "fastboot flash recovery [recovery name].img" with no quotes.
Do you know how to use fastboot?
Click to expand...
Click to collapse
You used to be able to boot into a custom recovery without flashing it with: fastboot boot namerecovery.img. Don`t know its possible with stock recovery though.

gee2012 said:
You used to be able to boot into a custom recovery without flashing it with: fastboot boot namerecovery.img. Don`t know its possible with stock recovery though.
Click to expand...
Click to collapse
You can still boot into a custom recovery via fastboot... but what does that have to do with what we're talking about? I'm confused...Are you suggesting he try that instead of actually flashing it?

_MetalHead_ said:
You can still boot into a custom recovery via fastboot... but what does that have to do with what we're talking about? I'm confused...Are you suggesting he try that instead of actually flashing it?
Click to expand...
Click to collapse
I said i have never tried booting into a stock recovery (but it would be nice to know it works) and i`am not even fully sure it will work

_MetalHead_ said:
It's just a simple fastboot command- "fastboot flash recovery [recovery name].img" with no quotes.
Do you know how to use fastboot?
Click to expand...
Click to collapse
I have used them when rooting my Nexus 5, several years ago...
Thank you.

gamer.11 said:
If you have any other factory images with you, let it be anything like 4.4.4 or .4.42 or anything, unzip the image-hammerhead-xxxxx.zip and you will find a recovery.img file.
flash this recovery like you flashed twrp
Code:
fastboot flash recovery recovery.img
and you will get the stock recovery boot into that and you will see, "apply update from adb"
choose that option and then when asked use adb to push the update.zip into the phone.
No problems :highfive:
Click to expand...
Click to collapse
I extract the recovery.img from KTU84P's factory image(Which is my current version), and then:
1. hold down Volume down + power, until I saw the bootloader.
2. connect my phone to PC
3. input "fastboot flash recovery recovery.img", and saw:
sending 'recovery' (9284 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.800s]
finished. total time: 1.330s
4. then goto "Recovery mode"
Then, I saw the robot dead, with a red ! on him.....
================================
Oh I knew that, it is the stock recovery , I can use volume up to select ..... Thanks

DodouWang said:
I extract the recovery.img from KTU84P's factory image(Which is my current version), and then:
1. hold down Volume down + power, until I saw the bootloader.
2. connect my phone to PC
3. input "fastboot flash recovery recovery.img", and saw:
sending 'recovery' (9284 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.800s]
finished. total time: 1.330s
4. then goto "Recovery mode"
Then, I saw the robot dead, with a red ! on him.....
================================
Oh I knew that, it is the stock recovery , I can use volume up to select ..... Thanks
Click to expand...
Click to collapse
That's the stock recovery. Press and hold power and press volume up to get the menu and then select 'apply update via sideload' (or whatever it says) and go from there. There are guides on how to do this on here already so I'm not going to list it all

Bricked XT1032

So I have a cousins XT1032 I'm trying to fix. What happens is that it doesn't want to boot. After the Motorola Bootanimation it goes to a Black screen, I've read about going into Recovery and Factory Resetting or Wiping Cache and I've done it hundreds of times now and it hasn't changed a thing. I've tried flashing the Stock ROM and everything flashes correctly but when I reboot it goes to the same Black Screen after the Boot animation. I've tried putting a custom recovery (CWM, TWRP, Philz) and it flashes, but when I press Recovery on the phone after flashing, it boots into the Stock Dead android recovery. I'm not sure what else to do. So any help would be great, thanks.

Hmm, so I found something weird... So I said that I had factory reset man times, using Fastboot and Android Recovery, well today I was trying to convert it to a GPE to see if it would work and it didn't. It still did the same thing (black screen after bootanimation) So I tried to Sideload a ROM through Android Recovery and it aborted the installation so I pressed on the android recovery. "Update from SD Card" or something like that and I saw that my cousins old files were still there, they haven't been erased...So I'm starting to think that this is a defect...
But anyways, If anyone knows the solution I would really appreciate it!

No one? :/

Gus194 said:
No one? :/
Click to expand...
Click to collapse
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.

NextGenGTR said:
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
Click to expand...
Click to collapse
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one

Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img

NextGenGTR said:
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery

Gus194 said:
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Click to expand...
Click to collapse
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?

NextGenGTR said:
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
Click to expand...
Click to collapse
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect

Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.

NextGenGTR said:
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
Click to expand...
Click to collapse
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang

Gus194 said:
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Click to expand...
Click to collapse
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.

NextGenGTR said:
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
Click to expand...
Click to collapse
It probably would work If the phone had USB Debugging on before it got bricked :/ I'm about to give up on this phone. I've tried everything lol.
I'm thinking that the Partitions are corrupted since none of them will format using fastboot. It just says it cant format Raw type partitions or something like that

You have not done ALL of the necessary fastboot commands when flashing the firmware image. Make sure you have an XT1032 4.4.4 image.
Do the following manually, report any errors. Use no other fastboot commands other than those stated below.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​

Honor 6 bricked.Is there any hope?

HI all, i own a Honor 6 L02 and i have the following brick problems.
1. in normal boot i get RESCUE MODE error! func no9 func_boot_kernel
2.when i try to boot in recovery i get RESCUE MODE error no 10 func_boot_recovery
3when i try 3 buttons i get the same as no2
4.when i try fastboot(my phone is unlocked) i cannot flash ANYTHING from pc because i get failed remote command not allowed.
which i think is the major problem
I think it all initiated when i was in 532 lollipop and flashed wrong recovery(recovery for L04) in order to flash superuser which i did and everything was okay indeed.Until i wanted to move back to 316 stable kitkat, but i couldnot flash stock recovery because of the fail command not alowed,so i Installed Flashify ,flashed TWRP and then tried to flash image through twrp.
After rebooting i got bricked.ANY solutions?

Nobody can suggest a solution ? smth to begin from?

pudup said:
Is your bootloader unlocked? If so then the fastboot commands should work. Does your phone show up when you type "fastboot devices"?
If all fastboot still doesn't work, try updating the drivers. Download the latest multi tool and use that. Just flash a stock rom with multi tool or flash all the individual img files with fastboot manually.
Click to expand...
Click to collapse
Thanks for the reply.My bootloader says phone unlocked ,so i supposse it is.My phone shows up when i type fastboot devices.
Im using the latest multitool (and also tried different versions) and have installed the drivers on a fresh formatted windows 8.1 laptop!
the disaster problem is that i cannot flash ANYTHING with fastboot flash commands.For example:
sending recovery okay
writing recovery Failed error remote command not allowed.im getting this error with every single image file(boot,cust , system,recovery stock or custom)

pudup said:
Can you try locking your bootloader? Lock your bootloader and then switch off. Then unlock it and try flashing a recovery.
Also try this command after placing, let's say the twrp.img file for kitkat, in the fastboot folder.
"fastboot boot twrp.img"
That boots directly into twrp without flashing it. See if that works.
Click to expand...
Click to collapse
This is what i get when i try to relock bootloader
* daemon not runnig.starting it now on port 5037
daemon started successfully
T2FDU1482900...... fastboot
...
Failed (remote:stat not match)
finished total time 0.003
If i try to unlock it (although it s written phone unlocked) i get
FAILED ( remoteassword wrong)
shouldnt i get smth like bootloader already unlocked?
The weird thing is im 100% sure that im using the correct bootloader password because i have gotten
it from 3 different sources(local huawei,chinese site huawei a year ago, and the tool a guy has posted here on xda)
Last i have copied twrp.img in the folder and tried the command
fastboot boot twrp.img
downloading 'boot.img'
OKAY [1.047s]
booting...
FAILED(remote:command not allowed)
Thank you for your help,i appreciate it

Using fastboot flash your rom recovery again and your rom recovery
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
dimikon said:
This is what i get when i try to relock bootloader
* daemon not runnig.starting it now on port 5037
daemon started successfully
T2FDU1482900...... fastboot
...
Failed (remote:stat not match)
finished total time 0.003
If i try to unlock it (although it s written phone unlocked) i get
FAILED ( remoteassword wrong)
shouldnt i get smth like bootloader already unlocked?
The weird thing is im 100% sure that im using the correct bootloader password because i have gotten
it from 3 different sources(local huawei,chinese site huawei a year ago, and the tool a guy has posted here on xda)
Last i have copied twrp.img in the folder and tried the command
fastboot boot twrp.img
downloading 'boot.img'
OKAY [1.047s]
booting...
FAILED(remote:command not allowed)
Thank you for your help,i appreciate it
Click to expand...
Click to collapse
you flash TWRP RECOVERY in your BOOT partition it is Wrong
in fast boot do that
for Boot.img (your rom num)
fastboot flash boot boot.img
for recovery (your rom num)
fastboot flash recovery recovery.img

adhamamar said:
Using fastboot flash your rom recovery again and your rom recovery
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
you flash TWRP RECOVERY in your BOOT partition it is Wrong
in fast boot do that
for Boot.img (your rom num)
fastboot flash boot boot.img
for recovery (your rom num)
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
My friend,,, every image i try to flash via fastboot (recovery,boot,system,cust) gives me FAILED error:remote command not allowed
what i did with the twrp.img was the thing that the other guy advised to see if it would work

do you have a TWRP backup of your rom? if yes try restore it ....
if not
Search on this site for TWRP backup for your build num and Change the serial number for the backup copy with your phone serial number (folder name and change inside recovery.log file) (http://4pda.ru/forum/index.php?showtopic=671958&st=920)

adhamamar said:
do you have a TWRP backup of your rom? if yes try restore it ....
if not
Search on this site for TWRP backup for your build num and Change the serial number for the backup copy with your phone serial number (folder name and change inside recovery.log file) (http://4pda.ru/forum/index.php?showtopic=671958&st=920)
Click to expand...
Click to collapse
Thank you very much , but how will i be able to restore it ??? i cannot boot into recovery ,i get error no FUNC_BOOT_RECOVERY

read this http://forum.xda-developers.com/showpost.php?p=56662843&postcount=2945

adhamamar said:
read this http://forum.xda-developers.com/showpost.php?p=56662843&postcount=2945
Click to expand...
Click to collapse
No luck,what this tool does is similar to the multitool unbrick,just tries to flash the images in an automated way,and gives me the
FAILED error remote command not allowed

pudup said:
Sorry but it seems your phone is hard bricked. Take it to a service center.
The "command not allowed" error usually comes up for locked bootloaders or in some cases when usb debugging is not switched on. There is nothing i can think of right now for you to do.
I suggest you lie to the people at the service center and tell them this happened while you were doing a normal update that was given to you OTA.
Click to expand...
Click to collapse
what do you think would be the cost for repairing? i have asked at the local Huawei but they wont repair it because it is not bought from E.U. ,is there any chance that somebody would repair it without sending it back to china(after all guarantee is lost ,i own it for 1,5 years)

Hard bricked? Can't get into recovery, can't unlock bootloader

Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!

How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.

sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,

rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,

man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there

therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...

rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?

therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!

DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..

therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.

rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?

heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,

Bump!
Does anyone have any other suggestion please?
Thanks,

Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!

Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.

I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?

I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..

Razer phone Android 9.0 Pie cheryl-P-Magisk-twrp-boot

This boot comes with twrp and Magisk
Fastboot command ：
fastboot flash boot_a cheryl-P-Magisk-twrp-boot.img
fastboot flash boot_b cheryl-P-Magisk-twrp-boot.img
fastboot reboot
download
https://drive.google.com/file/d/1VbmtVm3OGLxXYZ92YOOxsQkoyuOvi91_/view?usp=sharing
Thanks @将军和妓 Making a boot file

Twrp is working for me but not Magisk, I had to flash it via recovery. Thank you very much for sharing

MusTangKKK said:
This boot comes with twrp and Magisk
Fastboot command ：
fastboot flash boot_a cheryl-P-Magisk-twrp-boot.img
fastboot flash boot_b cheryl-P-Magisk-twrp-boot.img
fastboot reboot
download
https://drive.google.com/file/d/1VbmtVm3OGLxXYZ92YOOxsQkoyuOvi91_/view?usp=sharing
Thanks @将军和妓 Making a boot file
Click to expand...
Click to collapse
I tried with fastboot boot cheryl-P-Magisk-twrp-boot.img and nothing happened.
I'll try properly flashing the image when I have the time to make a backup.
Anyone has been able to backup the clean Pie boot.img ?
EDIT: Tried flashing the boot image and it bootloops. Maybe device encription has to be disabled for twrp to work?

thank you so much for this
I worked after I flashed my phone to 7.1.1 and updated to 9 but when I did it again and after updated did a wipe(just going into the setting and wiping) I couldn't flash part b of the boot just got an error
:tools root# ./fastboot flash boot_a cheryl-P-Magisk-twrp-boot.img
Sending 'boot_a' (26840 KB) OKAY [ 0.840s]
Writing 'boot_a' OKAY [ 3.657s]
Finished. Total time: 4.503s
:tools root# ./fastboot flash boot_B cheryl-P-Magisk-twrp-boot.img
Sending 'boot_B' (26840 KB) OKAY [ 0.659s]
Writing 'boot_B' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
(EDIT: I'm retarded didn't notice the uppercase B but it seem they really didn't care of Gen1)

If you can't get into the system, you can go in twrp to restore factory settings and then restart, you can enter the system

MusTangKKK said:
If you can't get into the system, you can go in twrp to restore factory settings and then restart, you can enter the system
Click to expand...
Click to collapse
No everything is working just notice it said Razer 2

Djcall11 said:
No everything is working just notice it said Razer 2
Click to expand...
Click to collapse
This boot only supports Razer phone 1

[/LIST]
[/LIST]
MusTangKKK said:
If you can't get into the system, you can go in twrp to restore factory settings and then restart, you can enter the system
Click to expand...
Click to collapse
MusTangKKK said:
This boot only supports Razer phone 1
Click to expand...
Click to collapse
My guy only Razer 1 has 7.1.1 I just seen this after I reset after updating to pie everything I fine thank or care doe

I made the mistake of trying to get into recovery after this update using the Volume + plug in USB-C. (Update removed root/Magisk of course). It then wiped my entire device!!! No warning. No recovery screen. Just a message saying wiping device.
I immediately wiped it to put Lineage on it.

waiflih said:
I tried with fastboot boot cheryl-P-Magisk-twrp-boot.img and nothing happened.
I'll try properly flashing the image when I have the time to make a backup.
Anyone has been able to backup the clean Pie boot.img ?
EDIT: Tried flashing the boot image and it bootloops. Maybe device encription has to be disabled for twrp to work?
Click to expand...
Click to collapse
You need to make a copy of the flash all batch file and edit it and take out the line that reads "erase userdata" save the file. What this will do is make the factory image skip factory reset if you want to keep your files but wanna restore to fix or whatever.
---------- Post added at 10:03 AM ---------- Previous post was at 09:59 AM ----------
MusTangKKK said:
This boot comes with twrp and Magisk
Fastboot command ：
fastboot flash boot_a cheryl-P-Magisk-twrp-boot.img
fastboot flash boot_b cheryl-P-Magisk-twrp-boot.img
fastboot reboot
download
https://drive.google.com/file/d/1VbmtVm3OGLxXYZ92YOOxsQkoyuOvi91_/view?usp=sharing
Thanks @将军和妓 Making a boot file
Click to expand...
Click to collapse
So i flashed this and i also even tried flashing twrp and magisk like normal but after i would boot, most apps would not load. Im currently reverted to 8 to figure this out. If you could help me figure out what is wrong, would be appreciated.

Guys am running android 9 on razer phone 1 and bootloader unlocked. However keep getting error write to device failed. Any advise please?

marvi0 said:
Guys am running android 9 on razer phone 1 and bootloader unlocked. However keep getting error write to device failed. Any advise please?
Click to expand...
Click to collapse
Any suggestions?

marvi0 said:
Guys am running android 9 on razer phone 1 and bootloader unlocked. However keep getting error write to device failed. Any advise please?
Click to expand...
Click to collapse
Do you have both parts of the bootloader unlocked?

iliais347 said:
Do you have both parts of the bootloader unlocked?
Click to expand...
Click to collapse
hello buddy. Aaa you might be onto something. I am afraid I don't have my phone with me now. How do I check though if I have both parts of the bootloader unlocked?

marvi0 said:
hello buddy. Aaa you might be onto something. I am afraid I don't have my phone with me now. How do I check though if I have both parts of the bootloader unlocked?
Click to expand...
Click to collapse
Try fastboot oem device-info
---------- Post added at 03:55 AM ---------- Previous post was at 03:29 AM ----------
marvi0 said:
hello buddy. Aaa you might be onto something. I am afraid I don't have my phone with me now. How do I check though if I have both parts of the bootloader unlocked?
Click to expand...
Click to collapse
But fyi, the razer phone has two parts to the bootloader. One is unlocked with
"Fastboot flashing unlock"
And the other is
"Fastboot flashing unlock_critical" i believe

iliais347 said:
Try fastboot oem device-info
---------- Post added at 03:55 AM ---------- Previous post was at 03:29 AM ----------
But fyi, the razer phone has two parts to the bootloader. One is unlocked with
"Fastboot flashing unlock"
And the other is
"Fastboot flashing unlock_critical" i believe
Click to expand...
Click to collapse
Oh so I need to unlock both? Thanks will check this tonight

After install can't open music file on extened memory, usb otg

iliais347 said:
Try fastboot oem device-info
---------- Post added at 03:55 AM ---------- Previous post was at 03:29 AM ----------
But fyi, the razer phone has two parts to the bootloader. One is unlocked with
"Fastboot flashing unlock"
And the other is
"Fastboot flashing unlock_critical" i believe
Click to expand...
Click to collapse
Please can someone else confirm this please before I go ahead as I don't want to risk it?

marvi0 said:
Please can someone else confirm this please before I go ahead as I don't want to risk it?
Click to expand...
Click to collapse
Yes you need to unlock both and each command will also do a factory reset so backup anything you may need on the internal storage.

This is working great for me. Thanks
Sent from my Phone using Tapatalk