Related
i flashed the CWM update zip, booted into CWM, wiped, and now im trying to install the EOS rom
it goes smoothly and i get no errors, but it boots into CWM every single boot now.,,
Pushed the older 6006 cwm and flashed, no errors, still boots into 6010.. ?
http://forum.xda-developers.com/showthread.php?p=22897771
Found this thread. For transformer Prime but hopefully it fixes my issue. If this is a bad idea lmk.
If not, Will try around midnight when I get back home
Woops,
Found this too
http://forum.xda-developers.com/showthread.php?t=1781250
Did you flash the CWM.zip in TWRP? I ask because there was a known issue when flashing CWM from TWRP you would get stuck in a recovery loop. I had the same issue and had to flash the stock .img to get out of it. Good luck.
i flashed the CWM zip that was posted in the CWM thread, bout to try and get myself free..
::success.
booted into bootloader
flashed bootloader, restarted, booted into my rom...
rebooted back into bootloader
flashed recovery
wipe/flash normally
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Vektor67 said:
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Click to expand...
Click to collapse
Press volume down when it boots (right before and while the Google logo shows up)
jamesst20 said:
Press volume down when it boots (right before and while the Google logo shows up)
Click to expand...
Click to collapse
Thanks for the reply, I've tried that many times. It's not working. I wish I had read this thread carefully and learned that it might be dangerous to flash cwm zip from TWRP, I had no idea.
The thing is is that it never really shuts down properly(thought I remembered a power off option on one of my epic 4g cwm) So when I press the power button while on the reboot system now option, that is what it does but back to recovery. I tried the volume button as you suggested as well as every other combination I could think of. :~(
Well in messing with drivers(uninstalling old drivers/devices installing universal naked driver) I had the nexus 7 q3 tool waiting for adb to enter fastboot and reflash TWRP so I could restore) and the tool suceeded in kicking me into fastboot(with an error in the toolkit) The toolkit stopped communicating though. I want to use the toolkit to reflash back to stock now that I'm in the bootloader screen.
I'm a bit nervous though, some warning about flashing asus stock blobs being a sure way to HardBrick. I think I'll wait until I get better information. I am on the bootloader screen, but I'm certain my bootloader as it sits is messed up from flashing CWM.
*Edit* Success!! I used this ; "[Guide] Returning to Stock and/or Unbricking your device"located here, http://forum.xda-developers.com/showthread.php?t=1781250 (not sure how to go about inserting a descriptive link sry :~( I'm now back to stock and ready to brick it again...umm, I mean, root and flash like there's no tomorrow. hehe Thanks for the input.:good::good:
Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Zouk18 said:
Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Click to expand...
Click to collapse
try flashing stock recovery via adb
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
ijustzeke said:
try flashing stock recovery via adb
Click to expand...
Click to collapse
So you are suggesting that I erase and flash to stock recovery via adb and then flash custom recovery again?
EddyOS said:
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
Click to expand...
Click to collapse
CWM comes up as the recovery because it's the latest one I flash. I know it might now matter but this really bugs me.
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Mine was gone when i unrooting the device
Sent from my Nexus 4
EddyOS said:
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Click to expand...
Click to collapse
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
curtzxion said:
Mine was gone when i unrooting the device
Sent from my Nexus 4
Click to expand...
Click to collapse
Is there a way just to unroot but keep my ROM, kernel and data intact?
Zouk18 said:
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
Is there a way just to unroot but keep my ROM, kernel and data intact?
Click to expand...
Click to collapse
My rom, kernel, and data doesn't change, when i was unrooting the device(as i remember)
Sent from my Nexus 4
That's normal. I have it too. Just choose cwm on recovery already installed and leave it like that.
Sent from my Nexus 4 using xda premium
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?
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.
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