Hello everyone,
Well I'm a novice to the whole rooting and flashing scene. I had an X2 with cm10 on it, but it was dropped too many times and sadly passed on to the beyond. I decided to get myself a nice razr m.
I've had my phone for a few weeks now. I did the safestrap thing and tried out energy for a while. I liked it a lot, ran fast with good batery llife and all that, but the theme wasn't exactly my thing. Next I tried out flying jelly. It was great and I used it in RomSlot1 for a good few days, eventually swapping it into the stock slot. Everything was great and fine until after having been up for work for 28 hrs, I read about some glorious app called razr m toolbox. I got it and swiftly went through the warnings with no regard for my phone's safety.
In the end I had a nice looking screen(sarcasm) with no softkeys or nav bar. I tried to delete and reflash, but that put me to a place where it would boot to the safestrap splashscreen but the continue and recovery keys wouldnt work. This baffled me until I came and saw that it's sort of a common(known at least) issue. Holding down the vol and power keys didnt work, but four seconds after letting them go it would boot into the SS spllash again. I eventually found that if I started holdingdown the three keys AT the SS splash, than I could go into fastoot.
I RSD'd and it went through that whole process, and now I'm sitting at the stock M boot animation. There's a yellow light with red light spikes coming from it with some lightning going around it. Quite a storm. The issue is that it's been stuck at this animation for a solid ten minutes now.
Should I wait? should I try to reset it and start anew?
Let it sit for a while longer, it takes a while after restoring to stock. If it doesn't work, use Matt's utility. IMO, it's the easiest method to fastboot a M.
http://www.droidrzr.com/index.php/topic/13427-droid-razr-m-utility-110-windowsmaclinux/
Always factory reset after rsd to stock. This is most likely why you are bootloooping
Sent from my XT907 using Xparent BlueTapatalk 2
yes , I agree with upstares, after flashing the stock rom with RSD, it's alwayse reconmend to wipe data/factory reset ,try it if you can go in the recovery pressing the vol up button and power at the same time.
Make sure you go to stock recovery and clear cache as well as factory reset. I had the same issue and it worked for me!
sy0120 said:
Make sure you go to stock recovery and clear cache as well as factory reset. I had the same issue and it worked for me!
Click to expand...
Click to collapse
always clear cache when flashing anything
Sent from my XT907 using Tapatalk 2
Related
Ok, so I was playing around with the new Root Tools app and made a few, what I thought were safe, tweeks to the system and rebooted the phone. It gets past the M screen, runs the boot animation and then starts the boot animation again. No way out except to pull the battery.
How can I get it out of this endless bootloop? If I have to factory reset and start again from scratch, so be it. I would just like to know how.
I've tried holding down different button combinations on boot but haven't come up with the right sequence I guess.
I've also tried pulling the battery as the animation starts, then putting it back in and rebooting which is supposed to call up the recovery mode, but it doesn't. I'm not sure what to try next? I wish these things had a reset button
It's a Droid 2 Rooted with the stock rom running Froyo 2.2. I have the Bootstrap recovery loaded and did a backup with the clockwork recovery. I also have, and use, Titanium Backup Pro for Root.
After bootlooping pull the battery and put it back in. Then plug the droid 2 in with the cable either wall or USB will work. Then turn it on and it should get you recovery. The phone has to be completely off when you plug it in though.
Sent from my DROID2 using XDA App
EDIT: I tested it and USB won't work (at least for me) better off just using the wall plug.
Thanks, but that not working either. When I plug in the cable after the battery pull it starts up automatically and goes to the battery charge screen. I then shut it off and start it back up with no battery but plugged in and it goes right back into the boot loop after the M screen.
The batter charge screen is what you want. Just press the power button after you get the charge screen and you'll be booted into clockwork.
But in order to factory reset from a bootloop you have to flash an .sbf theres a few different tutorials. One in Windows, Another in linux/mac, and another in linux but for windows machines through an Ubuntu livecd(that I made).
Oh, OK I thought it was going to go right into recovery mode. Good to know.
I finally figured out how to get into the stock recovery and bootloader, so I tried to run the stock restore but after it wiped the data, it couldn't find the recovery file! So then I read in another post about using RSDlight 4.9 to do an sdf restore so I used that method. Of course while it was flashing I did come across your Ubuntu method and that does look like it would be a simpler process. I'm going make one of those CD's to have for next time.
Anyway, I was able to get it back to stock. It looks like most of my stuff is still on the SD card, so that's a bonus! I'll have to re-root before I can restore everything via Titanium, but that's going to be tomorrow's project. As for now just happy to to have my phone back. Especially before the wife (who has been telling me for weeks to stop F'in with it) found out .
I really appreciate that you took the time to help, thanks again!
No problem.
Could you change your Thread title to include [SOLVED]. Thanks
Can you please explain to me how you fixed this problem? I am currently having this problem now.
Please do not open/post in multiple threads for the same issue. This is a waste of time as we can see you have an open thread. Please reply to my response in your original thread for further assistance. (http://forum.xda-developers.com/showthread.php?t=824254)
newk8600 said:
Could you change your Thread title to include [SOLVED]. Thanks
Click to expand...
Click to collapse
Ok, your wish is my command! ;-)
Sent from my DROID2 using XDA App
Can I close this?
Yes. This issue has been resolved.
theecho said:
Yes. This issue has been resolved.
Click to expand...
Click to collapse
Ok, thanks
I have been running on stock 2.2 for a week or so now (SBF'd and was running with no issues)...not rooted or modified in any way. I did the OTA update for 2.3 and now my phone boots to the droid boot animation, and hangs. The boot animation completely freezes up, and the phone is unresponsive. Tried SBFing the 2.3 over and according to RSD that was completed successfully...but got the same thing on startup.
I got my phone the week it came out and have SBF'd many times, had rooted, ran all sorts of roms (as long as your counting different versions)...and of all things...an OTA update bricked it. Awesome.
I'll be heading to my local Verizon store in a few hours. Just thought I'd let you guys know.
That sucks Let us know how it goes at the store
With all the bootloader lockdown crap motorola put on these phones its just a matter of time before their own updates cause problems... anything strong enough to keep out hackers is also strong enough to cause serious problems when legit updates mess up...
Boot into stock recovery (power and hold X, then press the search key at the ! In the triangle)
Wipe data and cache
Reboot
karnovaran said:
Boot into stock recovery (power and hold X, then press the search key at the ! In the triangle)
Wipe data and cache
Reboot
Click to expand...
Click to collapse
^+1 this. Quite often when restoring the phone via an SBF it results in a bootloop which is corrected by performing a cache and data wipe through the stock recovery on the phone. It seems this can happen because the SBF doesn't actually wipe or replace /data and /cache
Another WIN for karnovaran!
karnovaran said:
Boot into stock recovery (power and hold X, then press the search key at the ! In the triangle)
Wipe data and cache
Reboot
Click to expand...
Click to collapse
Wow. Thanks! Worked like a charm.
Anybody that might have my same issue after installing the OTA, follow above steps, and wipe data in the stock recovery. My phone booted right up afterwards.
Thanks guy!
scsione889 said:
Wow. Thanks! Worked like a charm.
Anybody that might have my same issue after installing the OTA, follow above steps, and wipe data in the stock recovery. My phone booted right up afterwards.
Thanks guy!
Click to expand...
Click to collapse
Can I close this???
I have a pro rooted, running gingerbread, flashed cm7 902 build.
it works great, having nothing to compare it too as this is my first custom rom flash (long story if you would like to hear it to learn from my mistakes just ask), one minor issue i have seen is if you choose to let battery die till it suts down when you power back up you will not have data. Easy fix is just restoring to stock rooted and re flashing 902 and voila data is back, and oh yeah dont let battery die completely
thanks to dutchbastard, CrackMonkey91, jackpotclavin (for the build), and motorolaoneclick root method Pete Souza (spelling)
any question just ask i am an open book
when i installed newest 9-02 update the phone gets stuck in bootloop whats up with that
aymanfoa said:
when i installed newest 9-02 update the phone gets stuck in bootloop whats up with that
Click to expand...
Click to collapse
I had the same issue with a bootloop, just in a different situation. Go to recovery (Take out battery, hold Power+R+M, wait for the green Android and the ! in a triangle, then let go, then press both volume keys at once(Gingerbread) or the @ key(Froyo), use volume buttons to scroll up and down) and wipe the phone. It should say something like wipe, factory reset, restore, you get the point. Wait for it to finist, then reboot. If it shows an error, dont mind that. Mine did too but its fine.
Just installed newest version of TWRP with Loki pre-installed. When I boot to recovery and try to do a full wipe, it gets stuck while wiping the cache partition. The progress bar below the script window is still animated, but I left it sitting for a good solid 10 minutes to nno avail. I can hold the power button and it will reboot and everything is normal once it boots up. Anyone have this problem or have any ideas? Thanks y'all.
nicktheqwik82 said:
Just installed newest version of TWRP with Loki pre-installed. When I boot to recovery and try to do a full wipe, it gets stuck while wiping the cache partition. The progress bar below the script window is still animated, but I left it sitting for a good solid 10 minutes to nno avail. I can hold the power button and it will reboot and everything is normal once it boots up. Anyone have this problem or have any ideas? Thanks y'all.
Click to expand...
Click to collapse
Yeah, it has a problem with clearing partitions, you would want to pick "Use -rm rf method" in settings. It works though, it just takes a long time, >10min is certainly not unthinkable.
Running the same version of twrp here.. for some reason it takes quite a long time, as long as you see those gray bars moving just let it do its thing... it could possibly be the version of twrp that makes this take so long but it does this with a full factory reset to id suggest letting it sit for alittle longer and see what happens!
It will eventually go through. Like others have said, it takes a really, really long time. 10+ minutes for sure.
The answer is in the second post. Change that setting and you're golden.
Sent from my LG-G2 using Tapatalk
I'm running a completely stock nexus 10. yes, it has been rooted before, but it got the full wipe/load from factory image for 4.4.3.
I am able to flash twrp and cwm touch for recovery.. which I'd normally not care about BUT it needs to go in for warranty work.. its battery draw is faster than the charger can push (expect it to be hardware failure.. same issue with 4.4.2)
I am unlocked. After I do my fastboot.exe flash recovery recovery.img ... and then I try to boot into recovery.. I just get that droid laying on his back with a red triangle with a ! in it..
suggestiona?
scythefwd said:
I'm running a completely stock nexus 10. yes, it has been rooted before, but it got the full wipe/load from factory image for 4.4.3.
I am able to flash twrp and cwm touch for recovery.. which I'd normally not care about BUT it needs to go in for warranty work.. its battery draw is faster than the charger can push (expect it to be hardware failure.. same issue with 4.4.2)
I am unlocked. After I do my fastboot.exe flash recovery recovery.img ... and then I try to boot into recovery.. I just get that droid laying on his back with a red triangle with a ! in it..
suggestiona?
Click to expand...
Click to collapse
I am thinking that is the stock recovery, let me look into this but im pretty sure that is the OEM recovery....
Thx Josh
lj50036 said:
I am thinking that is the stock recovery, let me look into this but im pretty sure that is the OEM recovery....
Thx Josh
Click to expand...
Click to collapse
I dont believe so unless they changed it from 4.2 that it shipped with. That recovery (which I also tried) allowed me to install stuff from .zip while in recovery (how the nexus was rooted..), wipe cache, wipe device, wipe delvik, etc... It was ugly, but it worked. I dont go into recovery very often, but I know this dead android isn't what I should be seeing on this device... or it wasn't the same one that I saw when I first got it. After sitting at the dead droid for a bit, it then continues to boot into the system and that works all fine.
I gave up for the time being.. I just flashed 4.4.2 on it, left recovery dead, and re-locked the bootloader. I'm shipping it off to samsung for charging issues, and they said first and foremost they'll flash it.. I'll let them discover the issue for themselves. IF they dont just swap out the device all together. I first noticed my charging issue with 4.4.3, so I flashed back to 4.4.2 (never had problems using this image before...) and the problem persists using different charging bricks.. so I think its a hardware issue. WAS plugged in during some power flickers.. wonder if that passed through to the device.
I'm assuming Samsung will use a proper flash vs. what we're trying to use.. and they should be able to do it with a locked bootloader.
scythefwd said:
I dont believe so unless they changed it from 4.2 that it shipped with. That recovery (which I also tried) allowed me to install stuff from .zip while in recovery (how the nexus was rooted..), wipe cache, wipe device, wipe delvik, etc... It was ugly, but it worked. I dont go into recovery very often, but I know this dead android isn't what I should be seeing on this device... or it wasn't the same one that I saw when I first got it. After sitting at the dead droid for a bit, it then continues to boot into the system and that works all fine.
I gave up for the time being.. I just flashed 4.4.2 on it, left recovery dead, and re-locked the bootloader. I'm shipping it off to samsung for charging issues, and they said first and foremost they'll flash it.. I'll let them discover the issue for themselves. IF they dont just swap out the device all together. I first noticed my charging issue with 4.4.3, so I flashed back to 4.4.2 (never had problems using this image before...) and the problem persists using different charging bricks.. so I think its a hardware issue. WAS plugged in during some power flickers.. wonder if that passed through to the device.
I'm assuming Samsung will use a proper flash vs. what we're trying to use.. and they should be able to do it with a locked bootloader.
Click to expand...
Click to collapse
FYI, as @lj50036 said, that is the stock recovery for 4.4. When you see that screen, you have to hit Power + Volume Up (or Volume Down) simultaneously to bring up the recovery menu. like factory wipe, clear cache, etc.
charesa39 said:
FYI, as @lj50036 said, that is the stock recovery for 4.4. When you see that screen, you have to hit Power + Volume Up (or Volume Down) simultaneously to bring up the recovery menu. like factory wipe, clear cache, etc.
Click to expand...
Click to collapse
Like hit them and let go, or till it reboots again?
scythefwd said:
Like hit them and let go, or till it reboots again?
Click to expand...
Click to collapse
Just push them both at the same time and let go. It usually takes a few taps before they show, but they eventually do. There's no reboot or anything. The blue words just show up in the top left corner of that screen with the Android laying on it's back with the exclamation mark over it. This was how it is on my N5 and N7 (2013) as well, or was before I flash Philz Recovery on all my devices.
charesa39 said:
Just push them both at the same time and let go. It usually takes a few taps before they show, but they eventually do. There's no reboot or anything. The blue words just show up in the top left corner of that screen with the Android laying on it's back with the exclamation mark over it. This was how it is on my N5 and N7 (2013) as well, or was before I flash Philz Recovery on all my devices.
Click to expand...
Click to collapse
Hrmm, no blue text on mine.. but I'll give it a shot when I get home.
scythefwd said:
Hrmm, no blue text on mine.. but I'll give it a shot when I get home.
Click to expand...
Click to collapse
Well, the blue text shows up after successfully pushing the buttons. Before you push the buttons, all you'll be seeing is the Android laying on his back with the red exclamation mark over it.
charesa39 said:
Well, the blue text shows up after successfully pushing the buttons. Before you push the buttons, all you'll be seeing is the Android laying on his back with the red exclamation mark over it.
Click to expand...
Click to collapse
well I'll be danged if it do...
Thanks gents. Last time I entered into recovery it was the original rom.. 4.2. I rooted, installed cwm, and hadn't returned. Odd that they made this change, but I'm cool with it lol. actually, I may have never actually gotten into the recovery mode before I flashed cwm to it now that I think about it.
Its there. I found that if I hit power , held it down, and then hit VOL- it let me in... just had to be quick bout it.. like less than a 1/2 second. sweet.. she's all factory fresh and ready to run at samsung. Yall rock.
cant imagine why they would do that..
She's only charging from 23-25% in 2 hours, at idle, no use on a vanilla install.. so something is definitely wrong! We'll see if its the brick or the device, either way I'm good to go.
scythefwd said:
well I'll be danged if it do...
Thanks gents. Last time I entered into recovery it was the original rom.. 4.2. I rooted, installed cwm, and hadn't returned. Odd that they made this change, but I'm cool with it lol. actually, I may have never actually gotten into the recovery mode before I flashed cwm to it now that I think about it.
Its there. I found that if I hit power , held it down, and then hit VOL- it let me in... just had to be quick bout it.. like less than a 1/2 second. sweet.. she's all factory fresh and ready to run at samsung. Yall rock.
cant imagine why they would do that..
She's only charging from 23-25% in 2 hours, at idle, no use on a vanilla install.. so something is definitely wrong! We'll see if its the brick or the device, either way I'm good to go.
Click to expand...
Click to collapse
No problem. Hope your issue gets fixed quickly.
Sent from my Nexus 5 using XDA Free mobile app
charesa39 said:
No problem. Hope your issue gets fixed quickly.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ran it charging and idle from 6 till a little after 3pm today.. 25% more on the charge meter.. using the micro usb and the factory wall brick...
she's all boxed up and ready for ups though, should get her back like new in a couple weeks.. Thank GOD samsung will back their product.
Dont know whats the deal.. but its gonna be all good. Thanks again folks for educating me on why the stock recovery sux lol.
scythefwd said:
ran it charging and idle from 6 till a little after 3pm today.. 25% more on the charge meter.. using the micro usb and the factory wall brick...
she's all boxed up and ready for ups though, should get her back like new in a couple weeks.. Thank GOD samsung will back their product.
Dont know whats the deal.. but its gonna be all good. Thanks again folks for educating me on why the stock recovery sux lol.
Click to expand...
Click to collapse
Thx for taking the time to learn mate, Let us know when you get it back
Thx Josh