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
Related
What's the deal? I'm rooted on the stock ROM. I rooted with the toolkit. I'm using ROM Manager to reboot into recovery.
did you install a custom recovery? rooting does not install a custom recovery
munchy_cool said:
did you install a custom recovery? rooting does not install a custom recovery
Click to expand...
Click to collapse
Yes I did. I just used CWM to run a nanroid. Interestingly, I just reflashed through ROM Manager and now I'm in!
resrevni said:
Yes I did. I just used CWM to run a nanroid. Interestingly, I just reflashed through ROM Manager and now I'm in!
Click to expand...
Click to collapse
cool...enjoy the n4 then buddy.
munchy_cool said:
cool...enjoy the n4 then buddy.
Click to expand...
Click to collapse
Thanks. So is there a way to have CWM survive reboots? Or does it have to be reflashed all the time?
^ This must've been a problem when running stock I seem to be able to reboot to CWM with no problem that I'm running a custom ROM.
All is well in the world.
Sometimes you may need to delete or rename the stock recovery first. Use a file explorer with root access and rename /system/etc/install-recovery.sh to /system/etc/install-recovery.bak
Once this is done, you can use ROM Manager or TWRP to reflash your custom recovery and it will survive a reboot without problem.
resrevni said:
Thanks. So is there a way to have CWM survive reboots? Or does it have to be reflashed all the time?
^ This must've been a problem when running stock I seem to be able to reboot to CWM with no problem that I'm running a custom ROM.
All is well in the world.
Click to expand...
Click to collapse
there is a revert recovery disabler in the dev forum. here http://forum.xda-developers.com/showthread.php?t=1995440
I had this exact problem earlier too. After you have re-flashed CWM recovery, boot into CWM and then pick the option it gives you to make the custom recovery survive and not get replaced by stock recovery.
Sent from my Nexus 4 using xda premium
just flash TWRP better than CWM. flashed TWRP and never had this problem of recovery not sticking but do what
rod said,
Sometimes you may need to delete or rename the stock recovery first. Use a file explorer with root access and rename /system/etc/install-recovery.sh to /system/etc/install-recovery.bak
Click to expand...
Click to collapse
Hi all,
I saw somewhere that lfashing CWM through ROM manager is unstable.
is this still the case? or can I safely flash CWM from ROM manager and have it stick through reboots?
also, do I need to factory reset when flashing custom recovery for good measure?
(currently I'm rooted with busybox only, stock ROM)
thanks
I'm not sure if it still does a "fake flash" of recovery through Rom Manager (?) The best way to install a recovery is through fastboot.
You could also install TWRP just as easily with the Goo Manager app as an alternative.
ap1618 said:
Hi all,
I saw somewhere that lfashing CWM through ROM manager is unstable.
is this still the case? or can I safely flash CWM from ROM manager and have it stick through reboots?
also, do I need to factory reset when flashing custom recovery for good measure?
(currently I'm rooted with busybox only, stock ROM)
thanks
Click to expand...
Click to collapse
I haven't had any problems installing it through ROM Manager. Installed an update to CWM about a month ago this way and it works fine. Also just reinstalled CWM this way last night after messing around going back to stock and it boots into recovery just fine. I don't flash custom ROM's just do backups and installed su so haven't thoroughly tested it out.
If I have CWM flashed, if I do an OTA update, would I lose recovery? or worse does it cause any conflicts?
thanks
ap1618 said:
If I have CWM flashed, if I do an OTA update, would I lose recovery? or worse does it cause any conflicts?
thanks
Click to expand...
Click to collapse
You won't lose recovery. an ota will not complete without the stock recovery. You'd have to reinstall your stock recovery for an ota to be successful
Sent from my Nexus 4 using xda premium
ap1618 said:
If I have CWM flashed, if I do an OTA update, would I lose recovery? or worse does it cause any conflicts?
thanks
Click to expand...
Click to collapse
It's easy enough to adb sideload an OTA zip via CWM and you have the option to retain root IIRC.
Just search for adb+sideload+OTA.
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
Maybe before you even answer, I'm sure I'll find a link on here to show me how?
One issue I have though, is that when I manually updated to 4.2.1 on my Nexus 7, I still got an OTA update a few days later, that actually ran.
I don't ever plan on flashing roms to any of my devices. Do I need to keep a custom recovery on my Nexus 4 or 7? If not, how to I revert back to the stock recovery?
If you saved the offical stock 4.2.1 images, to revert back to stock recovery, just use the 'fastboot flash recovery recovery.**************.img' command. If you haven't, you might have to flash the whole 4.2.2 rom which you can find on the google dev website. After this, if you only want to root then you don't need to flash a custom recovery, just use the 'boot' command instead of the 'flash' one.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
I flashed the OTA sideload file through TWRP and it installed succesfully.
jvbferrer said:
I flashed the OTA sideload file through TWRP and it installed succesfully.
Click to expand...
Click to collapse
How did you do that? Did you sideload wrinkle's file from this thread: http://forum.xda-developers.com/showthread.php?t=2145848?
I should let you know, that while I'm not afraid to install via the custom recovery, it doesn't mean I've done it via commands. I've always used toolkits, or one click methods of rooting and installing custom recoveries.
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
wvcadle said:
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
Click to expand...
Click to collapse
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
MacHackz said:
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
Click to expand...
Click to collapse
Yes, stock rom, rooted and unlocked. I did install Beats today. Could this be the problem? If so, I found a revert zip that I'm assuming is supposed to revert me back to stock audio codecs.
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
MacHackz said:
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
Click to expand...
Click to collapse
Flashing the revert zip failed. I'm starting to think that flashing anything with TWRP will fail.
How about this. I made a backup of all system data + apps with Titanium earlier today. Could I just reset my phone back to factory defaults, restore my apps + some system data, then re-root (*without a custom recovery*) and wait for the update again? Or will it come again?
Also, I've used Wugfresh's Nexus Toolkit. I don't remember checking the custom recovery button, but ended up with TWRP anyway. What's the easiest way to root without installing a custom recovery?
You could try that, and the update will come straiht away. You can root without flashing a custom recovery, just use the 'boot recovery' instead of 'flash recovery'
MacHackz said:
flash cwm and see if there's any difference
Click to expand...
Click to collapse
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
wvcadle said:
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
Click to expand...
Click to collapse
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
MacHackz said:
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
Click to expand...
Click to collapse
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
wvcadle said:
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
Click to expand...
Click to collapse
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
MacHackz said:
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
Click to expand...
Click to collapse
Where in that thread does it show me how to flash the stock recovery back onto my device?
wvcadle said:
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
Click to expand...
Click to collapse
The same thing happened to me. I was rooted running stock ROM with TWRP recovery (used wugfresh toolkit). The problem was I forgot I was using a modified kernel (for color correction) by molesarecoming. I flashed the stock kernel back, downloaded and flashed the OTA file from the help desk thread (http://forum.xda-developers.com/showthread.php?t=2145848&highlight=beats), and it worked. Oh, and I flashed the Superuser file immediately after the OTA did it's thing (while still in TWRP) to regain root. I didn't really like how after the initial failed install of the OTA, it took my into TWRP with no error message showing or anything.
I don't think TWRP is your problem -- I think beats is your problem. It may have modified something. Try searching the above-linked thread for answers. Honestly, there's no rush to get 4.2.2, so take your time finding the answer. It's better than wiping the phone just to install a small android update and having to redo everything on your phone again.
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
wvcadle said:
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
Click to expand...
Click to collapse
I need some help here - I have nexus 7 with 3G and Google (takju) with 4.2.1 installed.
I had it 'rooted" and installed TWRP .
AT the time I followed instructions to chand extension of some file to .bak - to prevent 'unrooting"
I do not remember which file I unfortunately changed.
Now I cannot install the 4.2.2 upgrade - the OTA fails because it boots into TWRP and after that I rrid several selections from TWRP screen (flash, reboot, etc) - but all attempts failed.
I have the upgrade files (bot .tar and .zip) on /sdcard directory but have no idea how to update to 4.2.2.
Tried manual flashing using adb command - all fails.
I do not have beats drivers installed
Can someone tell me how to uninstall TWRP? If the CWM recovery works with this upgrade, I would like to change from TWRP to CWM.
Or any other suggestion wold be appreciated.
I am really struggling with Android operating system the way it configured on Nexus 7 by Google - any simplest is a major pain!
Hope I can get out of this and operate the device instead of continuously meddling with operating system.
Thanks in advance
[email protected]
I do not have any back ups because i backed up on clockwork and i now have twrp. I have 3 roms on my phone but 2 say failed and aokp just puts me in bootloop. I cant do anything .please help. Thank you!
So nobody can help or what???????
kkurtz78 said:
I do not have any back ups because i backed up on clockwork and i now have twrp. I have 3 roms on my phone but 2 say failed and aokp just puts me in bootloop. I cant do anything .please help. Thank you!
Click to expand...
Click to collapse
Have you try to do a full wipe? In any case, yoy can download other rom that works sure and put in the sdcard using adb when you are in recovery mode...
Check if when you flash the rom, you are getting an error related with loky-... (Something like this)...
Why don't you try to install back cwm if you still have your cwm backup. Then after that restore your backup.
Sent from my LG-D802 using Tapatalk
mrm43 said:
Why don't you try to install back cwm if you still have your cwm backup. Then after that restore your backup.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
How can i install back to CWM? if i cant get out of Recovery?? I would just download another rom but computer wont show my phone since stuck in recovery, As you can tell i have limited access to computer privileges due to using a work computer, so I do not have any of the tools on the computer.
lomunet said:
Have you try to do a full wipe? In any case, yoy can download other rom that works sure and put in the sdcard using adb when you are in recovery mode...
Check if when you flash the rom, you are getting an error related with loky-... (Something like this)...
Click to expand...
Click to collapse
Yes i did a full wipe, when i flash AOKP 2/16 its successful but stays boot looping, but PA and CM11 says failed, but nothing mentioning loki.
Can you not mount in twrp? Or go into download mode and adb push another ROM onto the phone? If your in a bootloop just wipe everything twice. Mount or adb push a new ROM AFTER checking md5. Both those have worked for me :$
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
Is your TWRP out of date? You can update TWRP while in TWRP. Or just adp sideload another ROM.
How do you update twrp while in recovery? When flashing the other two roms its saying something about binary?? And how do you side load, yes im real new to the g2 root game, my nexus's were so much easier and never delt with adb sdk really, ill have more luck tomorrow when im on computer i can actually download stuff , when i flash aokp i see all the files through file manager but just won't boot
kkurtz78 said:
How can i install back to CWM? if i cant get out of Recovery?? I would just download another rom but computer wont show my phone since stuck in recovery, As you can tell i have limited access to computer privileges due to using a work computer, so I do not have any of the tools on the computer.
Click to expand...
Click to collapse
By using ADB. If your pc does not detect phone. Try installing lg drivers or those on pdanet drivers.
Link for universal drivers to get ADB working.
http://koush.com/post/universal-adb-driver
Sent from my LG-D802 using Tapatalk
Adb is the way to go if your stuck in recovery. And even if you're a newb its easy to learn as there are countless tutorials out there. Just read up on it and then you can either push a new ROM or push cwm and restore your old backup
Sent from my LG-G2 using Tapatalk
Hey guys, i'm kinda new to rooting(had iphone previously) and i'm having some trouble. The phone is rooted already(4.4.2), i installed ROM manager and now i dont know how to boot it to cwm recovery, every tutorial i follow it goes to stock recovery. I tried installing cwm with odin but it doesn't get through setup connection, or it does but it fails. I wanted to get the google edition ROM. Thanks in advance
Hetfield88 said:
Hey guys, i'm kinda new to rooting(had iphone previously) and i'm having some trouble. The phone is rooted already(4.4.2), i installed ROM manager and now i dont know how to boot it to cwm recovery, every tutorial i follow it goes to stock recovery. I tried installing cwm with odin but it doesn't get through setup connection, or it does but it fails. I wanted to get the google edition ROM. Thanks in advance
Click to expand...
Click to collapse
Have you tried the below app? Supposed to be good for flashing things.
https://play.google.com/store/apps/details?id=neldar.sgs.kernel.flasher
Sent from my GT-I9505 using Tapatalk
what is exactly flashing kernel? is it the same as flashing cwm recovery? so confused atm
Hetfield88 said:
what is exactly flashing kernel? is it the same as flashing cwm recovery? so confused atm
Click to expand...
Click to collapse
You don't need flash any kernel for have a custom recovery. Take a look:
~ For i9500: HERE
~ For i9505: HERE
Joku1981 said:
You don't need flash any kernel for have a custom recovery. Take a look:
Click to expand...
Click to collapse
Thanks a lot man!
Edit:ahem i think i messed up, i got the custom recovery to work, then i did a wipe to install the google rom, but it failed for some reason, what do i do now?
You sound like you really don't know what you're mate.
I think the best advice anyone can give you is to put your phone down and read some more.
If you have successfully flashed CWM then all you need to do is flash a ROM of your choice then wipe data / factory reset.
Also before you even think about flashing anything to your phone you NEED to back up your EFS partition.
Sent from my GT-I9505 using XDA Premium HD app
Obagleyfreer said:
You sound like you really don't know what you're mate.
I think the best advice anyone can give you is to put your phone down and read some more.
If you have successfully flashed CWM then all you need to do is flash a ROM of your choice then wipe data / factory reset.
Also before you even think about flashing anything to your phone you NEED to back up your EFS partition.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
you're right but now, since it's in recovery mode i have to fix this asap. i entered the recovery and did wipe data/factory reset like the tutorial said, then proceeded to install zip(the ROM) but it fails E/... status 7 installation aborted.
and i did backup data and sd card but the backups are in my pc and i cant get to them in recovery mode :/
Hetfield88 said:
you're right but now, since it's in recovery mode i have to fix this asap. i entered the recovery and did wipe data/factory reset like the tutorial said, then proceeded to install zip(the ROM) but it fails E/... status 7 installation aborted.
and i did backup data and sd card but the backups are in my pc and i cant get to them in recovery mode :/
Click to expand...
Click to collapse
Don't panic bad it's just down to the version of recovery ?
Just go back into recovery & try flashing again once you get status 7 go back & second line from bottom where you chose zip you will see "allow update old binary" tick the box if not ticked or until if it's selected then select zip to flash & it'll go straight through