I have a Motorola Razr M XT 907 on Verizon, which had been rooted for a long time. I wanted to update the software, hoping to get better reception and battery life. I made the mistake of installing the latest update, KDA20.62-15.1, which can't be rooted. I did, however, unlock the bootloader beforehand.
I have tried to flash a new recovery, hoping to downgrade the android build afterwards. Each time I try, I get confirmation of success in the command window, but I can never boot into recovery.
Any ideas? Or am I stuck staying unrooted?
Once you get recovery flashed, all you need to do is flash a SU.zip in recovery to gain root access. What recovery file are you trying to flash? Also, after recovery, immediately power off the phone and then boot straight into recovery so the update script can finish.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Once you get recovery flashed, all you need to do is flash a SU.zip in recovery to gain root access. What recovery file are you trying to flash? Also, after recovery, immediately power off the phone and then boot straight into recovery so the update script can finish.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks for answering. I tried to flash Clockwork recovery and clockwork touch. After flashing, I turned off and tried to boot into recovery, but the phone wouldn't boot into recovery mode.
joedp2 said:
Thanks for answering. I tried to flash Clockwork recovery and clockwork touch. After flashing, I turned off and tried to boot into recovery, but the phone wouldn't boot into recovery mode.
Click to expand...
Click to collapse
Ensure you are using the recovery built for our device this thread does have the proper recoveries for our device linked within the op...
We cannot teach people anything; we can only help them discover it within themselves.
It worked.
joedp2 said:
It worked.
Click to expand...
Click to collapse
Woot!
Sent from my HTC6525LVW using Tapatalk
issues
Okay so i pulled this phone out to mess with it.. Rooted, Bootloader unlocked and installed CWM Recovery because i cant seem to install any of the twrp versions.... I am able to backup and restore my system without issue but cant flash a custom rom in recovery. Is there something i am missing?
On stock kit Kat 4.4.2 and using cwm 6049razor-hd_m-kit Kat sorry left that out...
Which error?
Starts to flash then fails with droid on his back
I have same issu e!
Successfully flashed clockwork recovery...
But after boot into recovery mode is starting normally instead of recovery mode...
What can I do????
Don't let it reboot.. Hold down power and volume to go into recovery manually. If you allow it to restart it will load stock recovery back onto the device.
Related
So my friend and I last night decided to unlock, root and flash recovery using the nexus 7 toolkit. Everything seemed to work ok, but now we have a major issue. It seems last night he flashed phandroid rom or whatever its called, but didnt wipe, so now he lost clockwork somehow, and the rom just boots and doesnt do anything.
We tried using the toolkit again to push recovery, it says it sent it, but we can only access fast boot. If you hit volume keys to get into recovery mode, and select it, it wont go into clockwork, just tries to boot the rom
Any suggestions?
chugger93 said:
So my friend and I last night decided to unlock, root and flash recovery using the nexus 7 toolkit. Everything seemed to work ok, but now we have a major issue. It seems last night he flashed phandroid rom or whatever its called, but didnt wipe, so now he lost clockwork somehow, and the rom just boots and doesnt do anything.
We tried using the toolkit again to push recovery, it says it sent it, but we can only access fast boot. If you hit volume keys to get into recovery mode, and select it, it wont go into clockwork, just tries to boot the rom
Any suggestions?
Click to expand...
Click to collapse
Do you have the N7 connected to your computer via USB? For some reason it won't boot into recovery if it's not connected via USB, I had this problem when flashing the Paranoid Android rom.
Cmon chugger you have the gnex for god sakes why the hell did you use a toolkit.
Secondly If you can fast boot flash a recovery. And boot into recovery and reflash the ROM.
Sent From My Toro+ via White Tapatalk
So a while back I went through the process to root my phone and went with safestrap. Now it appears the new roms aren't compatible with safestrap (is it because of 4.3 gapps?).
How would I go about switching over to CWM? Is there anything fancy? Is there a guide? Any help appreciated.
Thank You.
Is your boot loader unlocked?
If so, flash CWM through fastboot (there are a few guides on XDA of how to do so). Flashing a new ROM through CWM will remove safestrap.
Sent from my XT907 using xda premium
Leraeniesh said:
Is your boot loader unlocked?
If so, flash CWM through fastboot (there are a few guides on XDA of how to do so). Flashing a new ROM through CWM will remove safestrap.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Yes unlocked. I will look it up. Thanks.
I believe you can also use backups made in Safestrap in TWRP (/data/ only)
Sent from my XT907 using xda premium
You'll need to uninstall recovery through the actual SafeStrap app. Then, you'll need to delete the app and all the SS folders.
So I am getting the "cannot load cwm.img" on the command prompt.
cwm.img is in the same folder as fastboot and adb.
not sure what is up. Currently searching for solution....
EDIT: Typed full path. Seems to have worked....
RikRong said:
You'll need to uninstall recovery through the actual SafeStrap app. Then, you'll need to delete the app and all the SS folders.
Click to expand...
Click to collapse
Booted back into safestrap. I'm assuming this is why?
jagsfan82 said:
Booted back into safestrap. I'm assuming this is why?
Click to expand...
Click to collapse
Yep that's why. SafeStrap works seperate from your recovery. If you actually boot into recovery do you get CWM? If not, you'll probably need to re-flash it. When you re-flash, boot back into recovery prior to booting into OS. This will assure that the install script is complete. Otherwise, your stock recovery will override CWM.
RikRong said:
Yep that's why. SafeStrap works seperate from your recovery. If you actually boot into recovery do you get CWM? If not, you'll probably need to re-flash it. When you re-flash, boot back into recovery prior to booting into OS. This will assure that the install script is complete. Otherwise, your stock recovery will override CWM.
Click to expand...
Click to collapse
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
jagsfan82 said:
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
Click to expand...
Click to collapse
Just saw your last post... too tired. You mentioned deleting the app and folders. Is this most likely the issue?
jagsfan82 said:
Just saw your last post... too tired. You mentioned deleting the app and folders. Is this most likely the issue?
Click to expand...
Click to collapse
I don't think that's the issue. Deleting the app and folders just frees up some space. I'll have re-read your other post and then I'll get back to you on it.
jagsfan82 said:
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
Click to expand...
Click to collapse
Do "fastboot flash recovery cwm.img" and open up the power menu via three button press, then select recovery.
Sent from my XT907 using xda premium
Leraeniesh said:
Do "fastboot flash recovery cwm.img" and open up the power menu via three button press, then select recovery.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
This is more or less what I did except the only difference is I hit power first, phone went off, then quickly did keypress. Went strait to OS.
Seriously appreciate help btw
RikRong said:
I don't think that's the issue. Deleting the app and folders just frees up some space. I'll have re-read your other post and then I'll get back to you on it.
Click to expand...
Click to collapse
My first thought is I need to strip down the system.. maybe i didn't wipe something properly or what have you.
jagsfan82 said:
This is more or less what I did except the only difference is I hit power first, phone went off, then quickly did keypress. Went strait to OS.
Seriously appreciate help btw
Click to expand...
Click to collapse
Yeah unfortunately there's no command to boot recovery from fastboot.
You can try running "fastboot reboot" while holding the volume buttons right after flashing cwm. That should do the trick. It should boot to the boot selection menu, then you can choose to boot to recovery.
Also, thought you killed yourself when I read your other post...
fastboot boot cwm.img is one argument away from a very, very bad day... If you put "flash" before boot, you'd be in trouble... Lol
Maybe I should write up a root app that will rename install-recovery.sh... That's not a bad idea...
Sent from my XT907 using Tapatalk
I always just power down the phone after flashing recovery and then manually reboot into recovery.
And done. Here's a link...
ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
I forgot to declare superuser in the manifest... I know, shoot me. Needs root access and all that jazz. Run the app before flashing recovery
Oh and rikrong, stole your avatar for the app icon
Sent from my XT907 using Tapatalk
sloosecannon said:
And done. Here's a link...
ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
I forgot to declare superuser in the manifest... I know, shoot me. Needs root access and all that jazz. Run the app before flashing recovery
Oh and rikrong, stole your avatar for the app icon
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Haha, nice.
RikRong said:
Haha, nice.
Click to expand...
Click to collapse
Thankee
So, if someone on stock who wants to flash custom recovery could test this, that would be great. It should work, but as I have no stock RAZR Ms, I can't confirm it will work
Sent from my XT907 using Tapatalk
sloosecannon said:
Thankee
So, if someone on stock who wants to flash custom recovery could test this, that would be great. It should work, but as I have no stock RAZR Ms, I can't confirm it will work
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Installed on phone. Says found but disabled. Tried flashing cwm.img and rebooting into recovery. Still goes straight to OS...
Enable install-recovery doesn't work
this all seems very straightforward of a process that should be working...
Do I need to try wiping everything down as bare as possible?
Is this the process that works for others? Take safestrapped, rooted, bootloader unlock device on an old pre-bootloader-unlocked rom. Uninstall safestrap. Flash cwm.img using fastboot comand. Boot into recovery. Then you should be in CWM?
Hey all, trying to flash CM10.2 on my G2 and I'm not able to boot into a custom recovery. Here's how I did everything.
Rooted - all was successful as far as I can tell. Was able to install Titanium backup and backup files and allow root.
I downloaded ROM Manager and installed CWM. When I went to boot into recovery, i get the error with the Android a red triangle exclamation point above him. So I tried to switch to TWRP through Rom manager, no luck. I tried to 'flash' TWRP through the command prompt and download of the recovery file, no luck.
I saw somewhere to download SuperSU, so I did that and tried again, and same issues. When I 'cleaned' SuperSU, uninstalled and reinstalled it but this time chose 'use custom recovery' - it tied to reboot into recovery, saw a standing up right android with a spinning icon, but then went to the same error.
Obviously I'm missing something somewhere. Can't figure out what.
Thanks for any help!
Don't use rom manager. Either use adb and push the recovery or use the app flashify to install the recovery. There are many threads ids the development sections on how to install recoveries
Sent from my LG-D800 using Tapatalk
tdevaughn said:
Don't use rom manager. Either use adb and push the recovery or use the app flashify to install the recovery. There are many threads ids the development sections on how to install recoveries
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Thanks, Is there a way to undo what I've done from rom manager? Because I used adb to push the recovery and still had the same issue, and using flashify to flash the image doesn't seem to work. Booting into recovery just gets me to stock recovery asking 'do you want to factory wipe your device'
Edit: When I boot to recovery from within flashify, it gives a 'boot certification error' upon booting
goldenmonkey1 said:
Thanks, Is there a way to undo what I've done from rom manager? Because I used adb to push the recovery and still had the same issue, and using flashify to flash the image doesn't seem to work. Booting into recovery just gets me to stock recovery asking 'do you want to factory wipe your device'
Edit: When I boot to recovery from within flashify, it gives a 'boot certification error' upon booting
Click to expand...
Click to collapse
Are you using a recovery that has been Loki'd. The G2 needs this to by pass the bootloader. By that error it does not seem you used the correct recovery file.
Jimi Mack said:
Are you using a recovery that has been Loki'd. The G2 needs this to by pass the bootloader. By that error it does not seem you used the correct recovery file.
Click to expand...
Click to collapse
I used the one from here - http://forum.xda-developers.com/showthread.php?t=2449670 - 2.6.3.3 and just flashed it with flashify most recently. But I was having the same issue when I installed it via adb and 'option 1' as shown there.
Yeah, when flashing that recovery image using option 1, I still get "secure booting error - boot certification verify" after I reboot into recovery
Huh, I got it.
Reading this post here - http://forum.xda-developers.com/showpost.php?p=48118278&postcount=567
Someone else was having the same issue as me. The newest recovery gave him that same error. Flashed 2.6.3.2 and it worked fine. (So far)
Glad to hear. Good Luck.
I tried booting into recovery via quickboot and now I"m in a boot loop. Battery pull just starts the process again -- phone trying to go into recovery but does so unsuccessfully.
I guess i have to odin back to stock and start over. argh just restored everything perfectly, xposed and everything.
samklee said:
I tried booting into recovery via quickboot and now I"m in a boot loop. Battery pull just starts the process again -- phone trying to go into recovery but does so unsuccessfully.
I guess i have to odin back to stock and start over. argh just restored everything perfectly, xposed and everything.
Click to expand...
Click to collapse
Same happened to me, but flashing stock firmware using odin kept everything intact. Didn't have to start over again. But I did have to flash root again.
Yeah I just downloaded the new Firmware to Odin and tried to boot into recovery using the button method to wipe data before Odining - didn't work. Booted back did a factory reset via the menu options and the phone tried to reboot into recovery, the phone restarted and just flashed the android icon but wouldn't boot into recovery to wipe data.
Just now I flashed the new Firmware via Odin and it of course dirty flashed. Once the phone was completely booted up. I shut it down properly. Then booted into recovery using the button method and that worked. Wiped all and starting fresh.
What were you all doing when this happen? all rooted i presume? so are you saying if you are rooted you can't go into recovery without going through bootloops? someone please clarify
re: reboot recovery
glensta said:
Yeah I just downloaded the new Firmware to Odin and tried to boot into recovery using the button method to wipe data before Odining - didn't work. Booted back did a factory reset via the menu options and the phone tried to reboot into recovery, the phone restarted and just flashed the android icon but wouldn't boot into recovery to wipe data.
Just now I flashed the new Firmware via Odin and it of course dirty flashed. Once the phone was completely booted up. I shut it down properly. Then booted into recovery using the button method and that worked. Wiped all and starting fresh.
Click to expand...
Click to collapse
I don't know what to say, my phone was rooted so I had to I odin flash cf-autoroot
again to regain root after odin flashing the new firmware from Sammobile.com
but I had no issues or problems going into recovery, bootlooping or getting stuck
when trying to reboot or boot into recovery.
For me it was the same old same old, odin flash new firmware, odin flash cf-autoroot
to gain root access, check everything out including reboot to recovery & reboot into
download mode... No different than what I always did using the Note 3 phone.
Good luck!
This is what happens after I rooted (mind you I forgot to check prior to root if booting to recovery works. and tried to boot into stock recovery - watch video:
Pulled batter, reinstalled and phone starts up just fine though, no bootloop
https://www.dropbox.com/s/yy149do5f0b5ggc/Note 4 Recovery Issue.mp4?dl=0
mgbotoe said:
What were you all doing when this happen? all rooted i presume? so are you saying if you are rooted you can't go into recovery without going through bootloops? someone please clarify
Click to expand...
Click to collapse
They trying to find a magical recovery when none exist.
NOTE 4
BACARDILIMON said:
They trying to find a magical recovery when none exist.
NOTE 4
Click to expand...
Click to collapse
Well there is stock recovery
mgbotoe said:
Well there is stock recovery
Click to expand...
Click to collapse
Yeah but they looking for cwm or twrp features
NOTE 4
re: custom recovery
BACARDILIMON said:
Yeah but they looking for cwm or twrp features
NOTE 4
Click to expand...
Click to collapse
There has been a lot of chat going on today in the twrp irc channel
about custom recovery for the Note 4 N910T and they are getting
closer to finding a solution..
In fact it looks like bigbiff, koush and philz are having a race to see
who develops a N910T custom recovery first. LOL
Misterjunky said:
There has been a lot of chat going on today in the twrp irc channel
about custom recovery for the Note 4 N910T and they are getting
closer to finding a solution..
In fact it looks like bigbiff, koush and philz are having a race to see
who develops a N910T custom recovery first. LOL
Click to expand...
Click to collapse
Last I read philz gave up on doing cwm. I hope he had a change of heart. I dunno koush.
NOTE 4
Yep don't go onto recovery or u will bootloop
Sent from my SM-N910T using XDA Free mobile app
re: bootloop going into recovery
raw2000j said:
Yep don't go onto recovery or u will bootloop
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
What's all this about not going into recovery because of bootloops?
I never seen any such thing, the original firmware with or without
root the phone never bootlooped when I went into recovery.
The same holds true for the new updated firmware, it never goes
into bootloops either when I go into recovery rooted or not.
In fact I never yet seen my note 4 going into any bootloops for any reason.
Hmmm.. I must be doing something wrong! LOL
mgbotoe said:
What were you all doing when this happen? all rooted i presume? so are you saying if you are rooted you can't go into recovery without going through bootloops? someone please clarify
Click to expand...
Click to collapse
In my case, I was just being experimental and wanted to see what happens if I delete every file that had to do with Knox. It ended up boot looping. I guess cause it couldn't find Knox when booting
Are you guys that are getting bootloops when going into recovery using the 4 way mod in wanam. If so, then i recommend not trying to access it thru 4 way reboot. Do it the old fashion way till wanam fixes the files need to do that. I know that if you try thru 4 way you get bootloop so you will have to odin back and start over. This time dont use 4 way reboot. Iam sure someone will come out with a fix.
Misterjunky said:
What's all this about not going into recovery because of bootloops?
I never seen any such thing, the original firmware with or without
root the phone never bootlooped when I went into recovery.
The same holds true for the new updated firmware, it never goes
into bootloops either when I go into recovery rooted or not.
In fact I never yet seen my note 4 going into any bootloops for any reason.
Hmmm.. I must be doing something wrong! LOL
Click to expand...
Click to collapse
Must be cause I wanted to go to stock recovery and hit recovery on quick boot I didnt shut it down to press buttons guess trying to go to recovery that way messed it up
Power down phone. Volume up + Home + Power will get you into stock recovery on a rooted Note 4. Just did it no problem.
BACARDILIMON said:
They trying to find a magical recovery when none exist.
NOTE 4
Click to expand...
Click to collapse
Lmao...
Sent from my SM-N910T
I've been using fastboot to install updates & flash twrp per the guide in the general section. I'm rooted with SU also. No problems with any of that.
Out of curiosity, I tried to flash the stock recovery with fastboot. When I try to boot into the stock recovery, I get the android with red ! triangle. Any ideas what might be keeping the stock recovery from working after flashing over twrp? Thanks.
docj said:
I've been using fastboot to install updates & flash twrp per the guide in the general section. I'm rooted with SU also. No problems with any of that.
Out of curiosity, I tried to flash the stock recovery with fastboot. When I try to boot into the stock recovery, I get the android with red ! triangle. Any ideas what might be keeping the stock recovery from working after flashing over twrp? Thanks.
Click to expand...
Click to collapse
I think you just need to press volume up to get through that. That is the stock recovery.
Sent from my Nexus 5X using Tapatalk
I believe it's power button then volume up.
Yup, that is the stock recovery..... It baffled me before I researched as well. Not exactly sure why you would want stock recovery as opposed to TWRP though.
oh yeah, duh. shows how long it's been since I've used the stock recovery! Thanks.