Database Info

Bootloop help

So I was cruising around the Nexus S forums and found a rom I liked after I unlocked and rooted my phone.
I flashed Paranoid Android and then flashed the Matr1x kernel. Thus putting me in a neverending bootloop.
No ability to go back to CWM so I can't restore. And I can't put it in download mode so no ODIN.
What the heck do I do?
Can anyone help?
BTW if this is actually called a soft brick I'm sorry my terminology might be off.
Also I did this because the last phone I did extensive flashing with was an HTC Inspire 4G and it was easy to flash stuff just clear everything and flash what you wanted no bootloops. Sadly this phone not so much.

Hmm... No recovery...I've been stuck in a bootloop but I had recovery!
Sorry for the useless post, I cant help you..

Are you able to get into bootloader?

Usually when a bootloop occurs you should still be able to go in recovery.
When you say "no ability to access CWM" do you mean ROM Manager? Or the recovery mode?
What happens when you try to access the recovery mode?

same issue like urs
http://forum.xda-developers.com/showthread.php?t=1775933
try clean install;
flash Rom-Wiper.zip
flash Dalvik-Wiper.zip
then;
factory reset,
Format the system, data, cache, boot & partitions of your device.

I mean no access to recovery. CWM is Clock Work Mod Recovery. I have no access to fastboot either. The only thing my phone can do is bootloop.

You have to be mistaken.
Press power and volume up to get into fastboot ( bootloader). Then pick recovery....
That rom or kernel will not erase recovery. If your phone is in a bootloop it is making it past the bootloader

So it appears it as if I was mistaken. I got into fastboot and booted into CWM I'm still confused as to what I did, but I think I corrupted the Kernel.
It was the weirdest thing though. I tried it at least a dozen times, then I tried to run down the battery and try it again afterwards, and it didn't work so I gave up. Then I tried it again about 5 minutes ago and it worked. I'm sorry I cause you guys so much confusion. I've been doing this for so long I guess I just didn't doubt I was doing it right.

[Q] RAZR HD system corrupt after flash.

Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?

ShiningRaven said:
Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.

tzlot said:
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
Click to expand...
Click to collapse
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.

ShiningRaven said:
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
Click to expand...
Click to collapse
Can you get back into fastboot now? If so
Use fastboot to flash a custom recovery (CWM, TWRP or OUDHS)
use the recovery to factory reset, wipe cache/dalvic, AND format system (sometimes in the advanced menu)
then flash rom of your choice.
If you can't get fastboot working you'll need smarter help than I can give you... but the format system step clears out all kinds of gremlins.

I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.

ShiningRaven said:
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.[/QUOTE
If you can get into fastboot then you should be able to unlock b/l with this toolkit I used it and it worked for me you can also flash rom with it its in the orginial development thread
http://forum.xda-developers.com/showthread.php?t=2154995
Click to expand...
Click to collapse

ShiningRaven said:
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Had the same problem after a fastboot via the utility. Try powering your phone down completely and leaving it off for about 5-10 min. This can be tricky with the hardware buttons so if you have access to TWRP that will help as it has a power off option. You might also try flashing again via the utility. I believe that's what I had to do, but the power down method is what a friend suggested based of his experience with the same exact problem you documented.

FIXED!!!
OK first I want to thank everybody who responded. I got tied up with work and kind of forgot about this project for a few days.
Repeated uses of the Utility and RSD both left me stuck with the phone freezing every time it tried to load the system into memory.
I had checked out the toolbox before but I didn't think I could do much from a locked bootloader.
After your suggestion jmcdonald I tried it again. It says my device isn't available to be unlocked so I tried downgrading back to ICS.
The toolbox says that it failed but it must have fixed something because the phone booted back up to android 4.1.2 stock!
So far I have bricked a lot of phones and learned a lot about ADB in the process of fixing them but I've never had one I was so certain was bricked permanently. But now it seems to be working fine, I'm scared to try rebooting in now.
Definatly going to unlock the bootloader pronto.
Thanks again jmcdonald!

help! can't boot and twrp asking for pword

so i have been using multirom and reflashed a rom to my internal rom. then i rebooted it and it is stick with a blank screen after the "google" logo and stuck there. when i go to twrp, it prompts me for a password that i have not set. I have read that this happens if you dont reboot after unlocking but i did that when i first unlocked the bootloader and have never ran into any problems flashing many roms till now. any ideas???

onecrzyasian said:
so i have been using multirom and reflashed a rom to my internal rom. then i rebooted it and it is stick with a blank screen after the "google" logo and stuck there. when i go to twrp, it prompts me for a password that i have not set. I have read that this happens if you dont reboot after unlocking but i did that when i first unlocked the bootloader and have never ran into any problems flashing many roms till now. any ideas???
Click to expand...
Click to collapse
Did u try to wipe "format data" as explained by Dess_Troy?

This happened to me too when I flashed a kernel without making sure it was correct for the rom I was running. I just forced it to reboot into recovery and it turned out fine. Have you tried that?
Sent from my Nexus 5 using Tapatalk

If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP. If you boot TWRP first before booting normally, you will be prompted for a password. Hit cancel and got to Wipe -> Format Data. Type yes at the prompt and hit the "enter" key. Hit the home button at the bottom and Reboot -> Recovery. Unlocking the device will cause you to lose all userdata, apps, pictures, downloads, etc.
Click to expand...
Click to collapse
Source: http://www.teamw.in/project/twrp2/205
It'll be ok

This has happened to me a couple times, all I had to do was hit cancel and it went into recovery, no password needed. Just needed to reflash Multirom.

hmm wonder if i could have reflashed the multirom. cuz when i tried to reflash roms or try to flash another roms or anything, it wouldn't work. said the files were all encrypted. under the file manager, there was no accessible or viewable files. completely locked out. I ended up doing a back up by going into bootloader and pulling files to my desktop then did a stock flash.
as for the reformatting, i've shouldn't/wouldn't want to do that because i have already unlocked the bootloader, did the fastboot reboot and flashed countless roms and kernels. I think there was some sort of corruption that screwed with something. And i really didn't want to lose all my data be reformatting it.
only booting into recovery and clicking cancel when prompted password made me completely locked out. said that everything was encrypted so i was out of luck.

IT WAS THE FINAL STEP... and it did not work. (Stuck on boot loader warning screen)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.

I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you

I have almost the same problem as if the fastboot not install anything despite not display errors

great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.

do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom

Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!

ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors

angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.

ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.

Root = bootloop on 5.0.1

Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.

No, but could you try the previous version of SuperSU? Just to rule out the new version that I haven't tested please?

I updated to 5.0.1 earlier
Flashed all the img files exact userdata and then booted in to Android.
I then flashed TWRP 2.8.1.0 and used that to flash SuperSU 2.37
All that worked fine.. I then did a play update and SuperSU updated to 2.40
All working fine as far as I can tell. Apps needing root are working!

iowabeakster said:
Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.
Click to expand...
Click to collapse
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?

BirchBarlow said:
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?
Click to expand...
Click to collapse
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.

iowabeakster said:
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.
Click to expand...
Click to collapse
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.

BirchBarlow said:
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.
Click to expand...
Click to collapse
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.

iowabeakster said:
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.
Click to expand...
Click to collapse
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.

Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.

snappycg1996 said:
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.
Click to expand...
Click to collapse
I just backed the /sdcard, to my PC. I just re-ran titanium.
I can deal with "/sdcard issues" from updating to lollipop easy enough. That's a 30 second fix. I can deal with setting up my email accounts to my email client app. I can deal with launcher settings, and all the other apps, widgets, etc. Those are things that I can slowly get back to where I want. They aren't critical. But yeah, very tedious.
I think "starting over" may be much more tedious for me than most people though. I run ssh servers and clients on all PCs, servers, and phones (disabling passwords and using rsa encryption keys for security). It's very nice, once I get it all set up in that I can access everything (from anything) very easily. I do need root for that though also.
But if I can't just hit a "restore" to get it all my ssh addresses, keys, fingerprits, etc back to where it was and then I have to: reverify new fingerprints, generate new keys, re-enable passwords to transmit new keys for everything, then disable passwords (for all machines) ... well... I just get very very grumpy.

anactoraaron said:
Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.
Click to expand...
Click to collapse
I'll check that out. Thanks.