What are most people using and does it matter that much?? What are the differences?? Cwm or twrp? I'm on twrp because I used qbkings root method and that's what his tutorial had used. I've also seen people say they r using cwm, if I wanted to use that instead, is it OK to use rom manager to flash the recovery? And is rom manager fully functional for the gnexus? I'm sure I could probably test most of this and figure it out with my backup if something goes wrong but sure would b a lot nicer I didn't have to do all that, and maybe this will help someone else too.
Sent from my Galaxy Nexus using Tapatalk 2
i use cwm touch on my gnex, have not tried twrp. i flashed it using fastboot. you can also just try/use it (or other recoveries) without flashing using "fastboot boot [image]". if you flash it be sure to rename/delete recovery-from-boot.p in system as it will otherwise overwrite your custom recovery again once you reboot.
stesmo said:
i use cwm touch on my gnex, have not tried twrp. i flashed it using fastboot. you can also just try/use it (or other recoveries) without flashing using "fastboot boot [image]". if you flash it be sure to rename/delete recovery-from-boot.p in system as it will otherwise overwrite your custom recovery again once you reboot.
Click to expand...
Click to collapse
Where can I find fastboot image for cwm or would it just b easier to rom manager?
Do u know of any differences in the 2, when u say "other recoveries" what else is available for the gnexus??? I've only seen the 2.
Sent from my Galaxy Nexus using Tapatalk 2
justen7723 said:
Where can I find fastboot image for cwm or would it just b easier to rom manager?
Do u know of any differences in the 2, when u say "other recoveries" what else is available for the gnexus??? I've only seen the 2.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
images can be found here: http://clockworkmod.com/rommanager
i have not tried the rom manager, i guess its a little bit easier if you dont want to use the command line.
since i have not tried twrp i cannot say exactly what the differences are. but i would guess both can do about the same things as the job for a recovery is quite well defined.
at least 4 for gnex : stock, cwm, cmw touch and twrp. don't really know if there are others...
Well, in my experience TWRP offers many benefits over CWR e.g. being able to be themed, having scripts, 'flashier' GUI, built-in file explorer but in the end I still swapped back to Touch CWR as it's simple, and it has everything that a recovery should do (flash, wipe, mount etc.). TWRP also has a few small bugs here and there but it's great if you want more options and features. Also that animation of booting into recovery bugs the hell out of me, along with the 'Swipe to continue' thing and touch response isn't that good in file lists (like when you have to choose what you want to flash).
It's all up to personal preference so that easiest way is to just flash both and try it yourself.
Twrp is awesome much quicker than cwm my only complaint right now is I can't find any themes for twrp 2.1.2
Sent from my Galaxy Nexus using xda premium
Related
Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
edit: CWM v5.5.0.4
do you try "wipe cache" and "advanced->wipe dalvik cache?"
Thanks, I just tried, it took quite a while to clear the cache. When I booted up it went through a whole Optimizing Apps process, I'm not sure if that was due to wiping the dalvik cache? But it still didn't fix the Rom Manager issue.
Its probably not yet compatible if you have the touch version of cwm installed, so it wants to flash the standard one. Or you could always just let rom manager just reflash cwm overtop and then you may be good to go.
EvanVanVan said:
Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk
I don't have the touch version installed (doesn't seem to be the touch version anyway). I should have said this in the first post but it CWM v5.5.0.4.
Herman76 said:
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Flashing CWM over CWM shouldn't wipe my phone right? It's only the stock bootloader that requires a full wipe?
I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...
Clancy_s said:
I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...
Click to expand...
Click to collapse
ah, that would probably do it...guess i'll just wait it out a little longer, thanks
I have the exact same issue as this Rom Manager refuses to see I have CWM installed so just keeps telling me I need to install it it also can't download and flash its own version and just freezes after download
So any updates on this or more users experiencing it ?
I think I've found the solution. In ROM Manager tap the menu button at the top and then tap Manual Flash Override. Next it'll ask you if you've flashed CWM manually so tap OK because that's what we've done. Next pick which GN you have and then choose CWM 3.x+. There you have it, it should work now.
Don't use ROM Manager - problem solved!!
Seriously, though, it's a TERRIBLE piece of software
I'm fairly new to using it but it seems decent, why is it so terrible? I had an eris before this and did everything manually through recovery, this seems like it's a lot better than that.
It's just more trouble than it's worth. Why not just manually flash CWM using fastboot and get your head around that as opposed to an app which can - frankly - break things?
Flashing it via fastboot is what causes the above issue. Since you flash it manually rom manager can't see it, that's why I posted the above steps to kind of "force" rom manager to see the manually installed version.
But if you're not using ROM Manager then what's the issue? Copy ROM to SD card, reboot to recovery, flash ROM...where is ROM Manager needed in that equation?
If you're not using it then there is no issue, but this thread isn't about using it or not, it's about getting it to work with the galaxy nexus when you manually flash CWM.
I like it for the backup and restore feature and being able to change the names used to backup
I installed the goodness as my first rom and following the guides it installed a modified CWM 5, the rogue version. I used Rom manager and installed the standard. WHen I reboot into recovery from the rom or using the pwr+up it boots into rogue, but when I reboot into recovery from rom manager it reboots into the standard cwm. I want to only use standard cwm, How do I get rid of and install it so when I boot into recovery manually it's the regular cwm.
Most don't recommend Rom manager, I would just stick with Rogue.. I had no problems with it..
Bobby O'S Epic Touch....
indigo0086 said:
I installed the goodness as my first rom and following the guides it installed a modified CWM 5, the rogue version. I used Rom manager and installed the standard. WHen I reboot into recovery from the rom or using the pwr+up it boots into rogue, but when I reboot into recovery from rom manager it reboots into the standard cwm. I want to only use standard cwm, How do I get rid of and install it so when I boot into recovery manually it's the regular cwm.
Click to expand...
Click to collapse
Get rid of ROM manager it doesn't flash recovery right on this phone..and koush doesn't care to fix it...don't ever use the touch one either... Get a kernel with cwm in it at use mobile Odin to install....if using a GB ROM use the el26 if using a ics ROM don't use any recovery unless u hate your phone and want to brick it
Sent from my SPH-D710 using Tapatalk 2 Beta-5
indigo0086 said:
I installed the goodness as my first rom and following the guides it installed a modified CWM 5, the rogue version. I used Rom manager and installed the standard. WHen I reboot into recovery from the rom or using the pwr+up it boots into rogue, but when I reboot into recovery from rom manager it reboots into the standard cwm. I want to only use standard cwm, How do I get rid of and install it so when I boot into recovery manually it's the regular cwm.
Click to expand...
Click to collapse
Just stick with Rogue's. ROM Manager has been the source of a TON if bricks lately (mostly to do with CWM Touch). If you absolutely can't use Rogue you can use the stock CWM from EL26.
http://db.tt/rBZNsGaj
But really I'd stick with Rogue...
And ROM manager doesn't actually install recovery on the phone. When you flash a recovery in it it creates a temporary recovery for you to boot into. But ya, don't even bother messing with ROM manager for all the reasons everyone else has stated.
Epix4G said:
Get rid of ROM manager it doesn't flash recovery right on this phone..and koush doesn't care to fix it...don't ever use the touch one either... Get a kernel with cwm in it at use mobile Odin to install....if using a GB ROM use the el26 if using a ics ROM don't use any recovery unless u hate your phone and want to brick it
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I totally agree here with the ROM Manager danger... When I had trouble in the past on a GB ROM, Koush didn't respond to any of my help requests.
I haven't had any issues lately, but in all fairness I do like the fact that ROM Manager will automatically reboot the phone into recovery, create a backup, and then boot back into Android. Also, I can delete or rename existing backups from right within Android with RM. I have restored the backed-up images with no issues too...
I've been on ICS since Calk's 1.0 FC06 ROM, and I have been fortunate enough to know to stay away from the touch recovery
You can delete or rename backups in android from any file manager app, most custom roms have the reboot mod to get to recovery and its a few clicks to backup and reboot to phone from recovery Rom Manager doesn't do anything special you can't do with your fingers and your trusting an app to do something for you instead of doing it yourself and making sure its done right
Sent from my SPH-D710 using xda premium
thanks for the feedback, I won't bother with rommanager anymore than lol. Also Can I use Rogue to flash Cyanogenmod and other roms, Some people are saying to use certain clockworkmod versions and saying rogue has caused bricks.
Hello all,
Who would I talk to about getting the stock takju/IMM76I image currently available from Google under ROM Manager and Goo Manager? I would feel better seeing it up there, being able to flash back to stock in a few clicks.
Thanks!
If you're going back to stock, you won't be using ROM manager anyways.
https://developers.google.com/android/nexus/images#yakju
Download. Flash with Fastboot. You'll actually get back to stock. And you can do it all yourself without asking someone else to do it for you...
Hello,
Thanks for replying. I already have the takju IMM76I image downloaded. I am assuming I can do this using adb if I need to in the future? I just ask as I have always reverted to stock ROM/bootloader through ROM Manager when I used my Nexus S. (They had a section for stock images on there) The only issue with your suggested method though is what if you're not near a computer with adb?
Sent from my Galaxy Nexus using xda premium
Use Fastboot to flash with command line (windows) / Terminal (osx). Requires computer.
BlindWolf8 said:
Hello all,
Who would I talk to about getting the stock takju/IMM76I image currently available from Google under ROM Manager? I would feel better seeing it up there, being able to flash back to stock in a few clicks.
Thanks!
Click to expand...
Click to collapse
I'll package up the zip for you and post it here later (maybe not today). All you'll have to do is drop the boot and system images into the zip.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
I'll package up the zip for you and post it here later (maybe not today). All you'll have to do is drop the boot and system images into the zip.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I really appreciate that. However, can we get it up on ROM Manager and Goo Manager so it benefits the whole development community? I don't want this just for me. I figured everyone should benefit. I can also do it myself if I'm given a link/how-to.
BlindWolf8 said:
I really appreciate that. However, can we get it up on ROM Manager and Goo Manager so it benefits the whole development community? I don't want this just for me. I figured everyone should benefit. I can also do it myself if I'm given a link/how-to.
Click to expand...
Click to collapse
I have no idea about how to get anything on ROM Manager (I don't use it at all) or Goo Manager (I've never heard of it).
Try the attached file. (Read notes before trying.)
It is essentially a script that will flash a boot image and a system image to your device. The boot image must be named boot.img and the system image must be named system.img. Both images must be in the root of the zip (and make sure they are compatible!). Use 7-zip to add whichever boot and system image you want to be able to flash it in CWM.
Notes:
1) I have not tried this, so someone will have to test it out. There shouldn't be any issues though. If there are, let me know and I'll sort them out.
2) As always, nandroid before flashing anything.
3) A wipe is recommended. Not sure if not wiping will cause any issues.
so i was running CM9 now with TWRP, then i odin to stock and odin CWM, then flashed TPR (With CWM).
I miss ICS a little, and may go back, but the question is, do i stick with CWM or should i switch to TWRP?
Also if i do switch to TWRP, what is the easiest way?
(I see a .zip to switch form TWRP to CWM, but not the otherway around)
Thanks
Nathan
Doesn't matter. Personal opinion.
Sent from my Samsung Epic 4G using Tapatalk 2
Certain kernels come with twrp. Just flash them. Then inject it back to keep it after flashing other roms or kernels.
I do like twrp but I have found files I couldn't flash in twrp. No idea why.I just use cwm cause all my backups are on there. I could change them over but it really doesn't matter to me.
Plus I don't have an Odin file for twrp.
Sent from my SPH-D700 using Tapatalk 2
An Odin file for TWRP would be nice.
nathan951 said:
so i was running CM9 now with TWRP, then i odin to stock and odin CWM, then flashed TPR (With CWM).
I miss ICS a little, and may go back, but the question is, do i stick with CWM or should i switch to TWRP?
Also if i do switch to TWRP, what is the easiest way?
(I see a .zip to switch form TWRP to CWM, but not the otherway around)
Thanks
Nathan[/QUOTE
I use TWRP mostly but its still up to you whether you want to use the TWRP buttons or use the keys for CWM.
Click to expand...
Click to collapse
Twrp is better, but it doesn't work as well for me. It doesn't flash all zips for me.
Sent from my GT-P7510 using Tapatalk 2
twrp - a promising future
tl;dr: What happens if I upgrade to CWM 6 after having used Darkside Superwipe on CWM 5?
And now the long explanation of what happened:
I have a Telus T989D, and I had installed the stock Telus JB ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2343748
I previously had CWM, but as per the instructions in the thread I installed TWRP, ran the Infamous Superwipe zip file, and then proceeded to flash the ROM.
Then today I decided to install CM 10.1. The first thing I did was flash CWM 6.x (I forget the exact version, but it was the latest one) from ODIN. Then I downloaded the latest stable build (CM 10.1.2). I then ran the Infamous Superwipe zip file again, and flashed CM 10.1. The result was that the phone would get stuck on the Cyanogenmod circle logo. I did some Googling and found out some people who had bootloops after installing Cyanogenmod, and it was suggested that this was due to a bad wipe, and that using Darkside Superwipe would fix the problem. So I proceeded to give Darkside Superwipe a try... Of course at the time I hadn't realized that 1) What I had was not actually a boot loop (it wasn't rebooting, it was just stuck at the logo), and 2) that Darkside Superwipe should not be used with CWM 6. After flashing the Darkside file, my CWM 6 would load up but would fail to flash ANY zip file that I selected (it would just get stuck on the first line, "Installing xxx.zip"). It would also fail to wipe the /cache partition (would freeze at "wiping /cache partition").
After soft-bricking my phone by trying to flash a different recovery from Heimdall, I ended up following a guide on this forum to flash the stock Gingerbread ROM from Odin. I then flashed CWM 5.0.2.7, did the Darkside Superwipe, installed CM 10.1, and now thankfully the phone works.
My question is... Does anybody know what happened here? And any ideas what will happen if I try to upgrade my CyanogenMod later on? Will I have any issues running CWM 5.x with CM 10.1 or 10.2? I'm a bit afraid of updating to CWM 6 since I have no idea what the result will be.
I later learned that Infamous Wipe is only to be used with TW-based 4.1.2 ROMs, since it adds a preload partition. Did I end up somehow messing up my partitions by using the Infamous & Darkside Superwipe files?
Sorry for the long post... I just figured I should give as much information as possible! I'd really appreciate it if anybody has an explanation for what happened (messed up partitions?) and how to fix it!
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Faruk88 said:
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Click to expand...
Click to collapse
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Faruk88 said:
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Click to expand...
Click to collapse
U can use goo manager if u want, but I will say this, sometimes too can cause soft bricks, in which case u would need Odin to recover , so in my professional opinion I would suggest using Odin from scratch
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app