Database Develop

[Q] URGENT! Did I just brick my phone?

TOTAL NOOB HERE.
I went ahead and unlocked the bootloader and rooted my device using the toolkit. Everything went well and I got SU on my phone. However, when I tried to flash the Revolution 7.0 ROM I must of forgotten to check the wipe data option. So now my phone is stuck on the boot animation and it just keeps looping. I can load the bootloader but can't seem to get into recovery! Please help!
Cheers !

Izconcept said:
TOTAL NOOB HERE.
I went ahead and unlocked the bootloader and rooted my device using the toolkit. Everything went well and I got SU on my phone. However, when I tried to flash the Revolution 7.0 ROM I must of forgotten to check the wipe data option. So now my phone is stuck on the boot animation and it just keeps looping. I can load the bootloader but can't seem to get into recovery! Please help!
Cheers !
Click to expand...
Click to collapse
open cmd
do the fastboot stuff
type fastboot erase cache

expertzero1 said:
open cmd
do the fastboot stuff
type fastboot erase cache
Click to expand...
Click to collapse
EDIT: Nvm, worked like a charm. Reflashed and it's all good. Damn I gotta learn this stuff. THANKS

[Q] I done screwed up big time - the mystery of the unflashable recovery

Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.4.2, TWRP 2.7.0.0 recovery
Objective: wipe everything and flash back to a (rooted) stock for device retail
Why I'm screwed: everything is wiped - phone has no OS, recovery, etc. It simply hangs out on the Motorola M at boot and doesn't move. fastboot loads and will flash recovery (seemingly successfully) but rebooting to recovery always gets stuck at the logo
How I got there:
1. Backed up with TWRP, then flashed new recovery CWM (the one here) and backed up again. Saved both folders of nandroid backups to my PC (yay)
2. Flashed back to TWRP (but this time the new one v2.8.0.1 here, which I downloaded and flashed via that fancy new TWRP app [I selected the "ghost" model]) clicked about every type of wipe option I could get my grubby little fingers on, then adb pushed the ROM and kernel/radio combo from here.
3. Attempted to flash the new ROM via TWRP. It failed. something about an "Error executing updater binary in zip". I sighed, said "meh", googled the problem a bit and figured I'd reboot the recovery and try again. This is where things get weird.
4. Phone hangs out at boot logo (that kaleidoscope "M"). Fine, I accidentally did a normal boot, and there's no OS installed. I go into fastboot and boot to recovery. SAME SCREEN. TWRP has apparently disappeared. No matter. I go into fastboot and flash it again, then boot to recovery. SAME SCREEN. Flash back to CWM. SAME SCREEN. Back to TWRP one more time just for giggles? SAME SCREEN.
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot? Restore either my CWM or TWRP nandroid backups without access to the recovery? Any guidance would be appreciated.
Attachments:
a) boot logo I'm stuck on
b) command line log of commands from flashing recoveries

From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.

VerneVerne said:
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
Click to expand...
Click to collapse
Perhaps I didn't make that clear - that's exactly what I've been doing.

PHP:
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman
Click to expand...
Click to collapse
That is what I have.
gerodive said:
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot?
Click to expand...
Click to collapse
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.

Wansanta said:
PHP:
That is what I have.
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Click to expand...
Click to collapse
Could you elaborate a little more on this? How do I get the system.img file to flash? I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check? Deleting the system partition was definitely what I did. Also, why mfastboot as opposed to just fastboot?

gerodive said:
Could you elaborate a little more on this? How do I get the system.img file to flash?
Click to expand...
Click to collapse
mfastboot flash system system.img
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
In bootloader mode it will tell you on the second line. 30:B7 is the 4.4.4 bootloader version.
gerodive said:
Deleting the system partition was definitely what I did.
Click to expand...
Click to collapse
As long as you can get into bootloader mode you can flash it back.
gerodive said:
Also, why mfastboot as opposed to just fastboot?
Click to expand...
Click to collapse
because the moto x system images are too large to flash with fastboot, you have to use mfastboot.

gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.2.2, TWRP 2.7.0.0 recovery
Click to expand...
Click to collapse
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
4.2.2 or 4.4.2?

nhizzat said:
4.2.2 or 4.4.2?
Click to expand...
Click to collapse
yeah he really needs to check b/c it really matters what version of the bootloader he is on.

Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.

Sorry, meant 4.4.2.

gerodive said:
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Click to expand...
Click to collapse
So glad!! If you are unlocked, as long as you can get into a functioning bootloader mode and have access to the sbf for your version of the OS you haven't bricked.
I about near had a heart attack when I deleted my system, but no biggie to restore it. I think I only paid $35 to unlock b/c I did it straight through tao bao, but it was the best $35 I have spent in a long time. I drop $35 every time I go for sushi, so I can't imagine not paying to unlock if you have the option.

SOLUTION those stuck in a bootloop with locked bootloader & TWRP

Hi All
Got into a bit of a situation when I re-locked my bootloader and got stuck in a loop, unable to unlock it because of the developer settings option. I had nothing but the TWRP screen bootlooping.
Anyway, sorted it out for those who want to know how. In the bootloader run the commands "fastboot format cache" and "fastboot format userdata"
Then choose to boot into recovery, it'll work and you'll be in TWRP. From there you can flash a ROM, enable the setting in developer options & unlock the bootloader!
Credit goes to geologic in this thread here: http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page5

Good news to anyone having alternative recovery. Unfortunately will not work with stock recovery

Great thanks
Sorry for my poor english (I'm french). Great thanks for your solution. It works fine for me... I was afraid during a few hours to be forced to throw away my Nexus 6....

Thank you for that information. I was in the same position and your instructions helped me get my device working again. That Check 'Allow OEM Unlock' in Developer Options flag is a real game changer for those of us who are used to flashing our devices and one must be very careful.

freeman_g said:
Good news to anyone having alternative recovery. Unfortunately will not work with stock recovery
Click to expand...
Click to collapse
Shouldn't you be able to adb side load a stock ROM?

Thank You
ixa20 said:
Hi All
Got into a bit of a situation when I re-locked my bootloader and got stuck in a loop, unable to unlock it because of the developer settings option. I had nothing but the TWRP screen bootlooping.
Anyway, sorted it out for those who want to know how. In the bootloader run the commands "fastboot format cache" and "fastboot format userdata"
Then choose to boot into recovery, it'll work and you'll be in TWRP. From there you can flash a ROM, enable the setting in developer options & unlock the bootloader!
Credit goes to geologic in this thread here: http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page5
Click to expand...
Click to collapse
Thank You so much you saved my day , I thought their is no solution for this but you saved me. :good::laugh::laugh:

Thanks a million!!
ixa20 said:
Hi All
Got into a bit of a situation when I re-locked my bootloader and got stuck in a loop, unable to unlock it because of the developer settings option. I had nothing but the TWRP screen bootlooping.
Anyway, sorted it out for those who want to know how. In the bootloader run the commands "fastboot format cache" and "fastboot format userdata"
Then choose to boot into recovery, it'll work and you'll be in TWRP. From there you can flash a ROM, enable the setting in developer options & unlock the bootloader!
Credit goes to geologic in this thread here: http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page5
Click to expand...
Click to collapse
Thank you so much, I owe you a life debt. haha now i can take one step closer to freedom.

How can you use fastboot format cache and fastboot format userdata when the bootloader is locked? I'm on an N6, but I've had 0 luck with that.

mrkmrk said:
How can you use fastboot format cache and fastboot format userdata when the bootloader is locked? I'm on an N6, but I've had 0 luck with that.
Click to expand...
Click to collapse
You just can. It allows it.

Just went through the same thing and can confirm that fastboot format cache and fastboot format userdata got me back into recovery.
However, Recovery was showing 0MB storage space so I couldn't push anything to the SDcard for install. @rootSU recommended that I go into wipe and perform a full format (the one that requires you to type "yes"). I did this and my storage was back to normal and I was able to push a ROM to the SD card and flash it.
Problem solved!

sn0warmy said:
Just went through the same thing and can confirm that fastboot format cache and fastboot format userdata got me back into recovery.
However, Recovery was showing 0MB storage space so I couldn't push anything to the SDcard for install. @supersu recommended that I go into wipe and perform a full format (the one that requires you to type "yes"). I did this and my storage was back to normal and I was able to push a ROM to the SD card and flash it.
Problem solved!
Click to expand...
Click to collapse
That's nice to give credit to the guy that helped you. But it was @rootSU

cam30era said:
That's nice to give credit to the guy that helped you. But it was @rootSU
Click to expand...
Click to collapse
Haha whoops! Thanks!

sn0warmy said:
Haha whoops! Thanks!
Click to expand...
Click to collapse
Know how I know?
Because I did it too.

cam30era said:
Know how I know?
Because I did it too.
Click to expand...
Click to collapse
There are too many "SU" screen names to keep track of. Either that, or my brain is fried from all the trouble shooting this morning.

sn0warmy said:
There are too many "SU" screen names to keep track of. Either that, or my brain is fried from all the trouble shooting this morning.
Click to expand...
Click to collapse
Maybe I need name change.

rootSU said:
Maybe I need name change.
Click to expand...
Click to collapse
ACE!

Htc butterfly s 9060 bootloop
ixa20 said:
Hi All
Got into a bit of a situation when I re-locked my bootloader and got stuck in a loop, unable to unlock it because of the developer settings option. I had nothing but the TWRP screen bootlooping.
Anyway, sorted it out for those who want to know how. In the bootloader run the commands "fastboot format cache" and "fastboot format userdata"
Then choose to boot into recovery, it'll work and you'll be in TWRP. From there you can flash a ROM, enable the setting in developer options & unlock the bootloader!
Credit goes to geologic in this thread here: http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page5
Click to expand...
Click to collapse
my phone is bootlooping and locked bootloader and not have twrp recovery....xda is very big site for android development after that no buddy help m... so plz help i m crying now..

abby1996 said:
my phone is bootlooping and locked bootloader and not have twrp recovery....xda is very big site for android development after that no buddy help m... so plz help i m crying now..
Click to expand...
Click to collapse
You can try >
fastboot format cache
fastboot format userdata
Note that if this works, it will wipe your SDcard.
If it doesn't work, you have no other options. Return it for repair or replacement.

Thank you soo much for reply
cam30era said:
You can try >
fastboot format cache
fastboot format userdata
Note that if this works, it will wipe your SDcard.
If it doesn't work, you have no other options. Return it for repair or replacement.
Click to expand...
Click to collapse
yes, this commnd works but what i do after that please tell ..i m new ....but i have recovery.zip and boot.img .i find these from other threats...how i flash this in locked bootloader..please tell in brief. Thanks

abby1996 said:
yes, this commnd works but what i do after that please tell ..i m new ....but i have recovery.zip and boot.img .i find these from other threats...how i flash this in locked bootloader..please tell in brief. Thanks
Click to expand...
Click to collapse
fastboot reboot

[Q] Bricked Nexus 6 PLEASE HELP!!

Trying to sell my Nexus 6 I believe I bricked it. After rooting the device I used Chainfire 3d program and it made me stuck on google sign. I tried literally everything. I can boot into teamwin TWR recovery. I tried factory resetting wiping cache and delvic. Problem is my bootloader is coming up locked. Tried using fastboot many times to flash everything back keep getting remote failure. Need help, is it possible im just screwed at this point. Ive used about everything it is just stuck saying Google. PLEASE HELP!!!!

chainfires 3d program hasnt worked on a nexus in years. and you do need to boot back up to enable unlocking the bootloader in the developer options. have you tried wiping data in twrp recovery?

zacrivera24 said:
Trying to sell my Nexus 6 I believe I bricked it. After rooting the device I used Chainfire 3d program and it made me stuck on google sign. I tried literally everything. I can boot into teamwin TWR recovery. I tried factory resetting wiping cache and delvic. Problem is my bootloader is coming up locked. Tried using fastboot many times to flash everything back keep getting remote failure. Need help, is it possible im just screwed at this point. Ive used about everything it is just stuck saying Google. PLEASE HELP!!!!
Click to expand...
Click to collapse
Relax, deep breath. You need to use fastboot from bootloader. Issue these commands:
fastboot format cache
fastboot format userdata
That should get you into TWRP and from there you can transfer a ROM to internal, flash it and go from there.

Evolution_Freak said:
Relax, deep breath. You need to use fastboot from bootloader. Issue these commands:
fastboot format cache
fastboot format userdata
That should get you into TWRP and from there you can transfer a ROM to internal, flash it and go from there.
Click to expand...
Click to collapse
well, he wrote that he can boot into twrp recovery already. wiping data should fix his use of chainfires app. but flashing a new rom would do the same

simms22 said:
well, he wrote that he can boot into twrp recovery already. wiping data should fix his use of chainfires app. but flashing a new rom would do the same
Click to expand...
Click to collapse
Yeah, guess I missed that part.

Evolution_Freak said:
Yeah, guess I missed that part.
Click to expand...
Click to collapse
thinking about it now.. with the bootloader locked, would twrp let you flash anything?

simms22 said:
thinking about it now.. with the bootloader locked, would twrp let you flash anything?
Click to expand...
Click to collapse
Yes, it has been done to fix the soft brick I thought we were dealing with here. Only if TWRP is installed though.

Doesn't chainfire 3d modify system? I though it did. May need to flash a rom zip after a factory reset.

rootSU said:
Doesn't chainfire 3d modify system? I though it did. May need to flash a rom zip after a factory reset.
Click to expand...
Click to collapse
honestly, i dont remember. its been about 3-4 years since last thinking of that app. if it does, a rom flash would be needed.

[Q] Possibly bricked N6, bootloop, no recovery, locked bootloader . Help me

Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks

Segnale007 said:
Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks
Click to expand...
Click to collapse
Do you have TWRP or stock recovery?

cam30era said:
Do you have TWRP or stock recovery?
Click to expand...
Click to collapse
Nope I do not. I don't even have access to the stock recovery. For some reason when I select the stock recovery the recovery menu does not appear. It just comes up a dead android with a question mark and nothing else..

Segnale007 said:
Nope I do not. I don't even have access to the stock recovery.
Click to expand...
Click to collapse
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.

cam30era said:
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.
Click to expand...
Click to collapse
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..

Segnale007 said:
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..
Click to expand...
Click to collapse
You have nothing to loose by contacting them and asking.

What 5.0.1 factory stock file did you flash?

Mega Montana said:
What 5.0.1 factory stock file did you flash?
Click to expand...
Click to collapse
This one right here https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz

Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?

Mega Montana said:
Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?
Click to expand...
Click to collapse
Depends if he had a 5.1 bootloader before or not. Attempts to downgrade the BL from 5.1 will result in a loop.
If it appears when connecting to the PC as qhsusb mode, then it's fixable. If it appears normally as a fastboot device, then it needs repairing.

Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help

Segnale007 said:
Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help
Click to expand...
Click to collapse
How did you do that with a locked bootloader?

cam30era said:
How did you do that with a locked bootloader?
Click to expand...
Click to collapse
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.

Segnale007 said:
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.
Click to expand...
Click to collapse
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.

cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm

rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
Aahh. That makes sense. I'm still amazed that recovery was this easy.

cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.

Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
Btw I was surprised to see the phone booting with a userdata and cache files from a newer version of android.
Click to expand...
Click to collapse
Most of those who were able to successfully format cache and userdata still had TWRP installed. You are very lucky. Should buy a lotto ticket today.

Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.
Click to expand...
Click to collapse
You can format cache and userdata with a locked bootloader. You cannot flash cache or userdata with a locked bootloader... Unless your bootloader is "bricked" as per the thread you linked to ultimately.
FYI formatting has the exact same result as flashing userdata and cache. So the options are:
1) you formatted which fixed it
2) you were bootloader bricked and had to use a gpt.bin to fix it.