Hi,
I have ClockworkMod Recovery v5.8.0.2. on my Galaxy Nexus. I'm running on XenonHD, but now I want to flash the latest 4.2 rom of Xenon.
Is my recovery outdated and should I update?
If so how do I update a recovery?
According to the cwm recovery page, the latest version for the gnex is 6.0.1.5
I can't remember which version added support for 4.2 (older versions would recursively create the /0 folder...), so you probably want to update it.
To update the recovery, just follow the same steps you did for install.
Your old backups may no longer work properly, although I think there might be a couple solutions mentioned in these forums on how to keep them.
meisanerd said:
According to the cwm recovery page, the latest version for the gnex is 6.0.1.5
I can't remember which version added support for 4.2 (older versions would recursively create the /0 folder...), so you probably want to update it.
To update the recovery, just follow the same steps you did for install.
Your old backups may no longer work properly, although I think there might be a couple solutions mentioned in these forums on how to keep them.
Click to expand...
Click to collapse
Thanks for the reply. I used a one click for all method, so I am not sure how I should install a recovery.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1757146 can I just flash this flashable zip with CWM?
I can't post in the development section that is why I am asking about this here.
Sorry, I do not know if you can just flash the zip over it, as I just did the "fastboot flash recovery cwm.img" method.
If your original method was just clicking on a .bat file, you might be able to replace the .img file that was included with it with the latest img file for cwm, as chances are the bat file just executes the command I listed above. If the script also installed XenonHD, though, I would probably avoid using it as it might overwrite your existing install.
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en
There you go OP. Install that app, hit the "flash CWM" button, grant root permission (set to remember), when it finishes I would hit the "flash CWM" button again and have it run w/o asking for root permission. You should be on the new CWM, it will show the # for the version you are on. :good:
Okay I will try the Rom manager app.
Just so you know Rom Manager is the official app from Koush, the dev behind CWM.
WiredPirate said:
Just so you know Rom Manager is the official app from Koush, the dev behind CWM.
Click to expand...
Click to collapse
Ooh okay, I heard about the app before but I never used it.
If you search here on the forums I believe you will find the "touch" version of CWM, or you can purchase it within the Rom Manager app and get the updates. I purchased it and I prefer it to the old method of using the volume buttons.
Related
This is a simplified guide for those new to rooting & flashing a custom ROM on the Optimus V. No need to type complex commands that are hard to follow and prone to mistakes. Basically there are 3 main steps: Root, Install custom recovery, & flash custom ROM.
Windows Drivers for the Optimus V (Optional but suggested):
http://www.lg-phones.org/wp-content/uploads/LG-Optimus-V.zip
Rooting
Rooting is the process of gaining administrative rights to the phone so one can do customizations that aren't normally allowed. Root by itself doesn't do anything interesting, unless there's an app that needs it. The fancy stuff comes from custom ROMs. Just remember Virgin Mobile Activation only works on Froyo ROMs, so do it before going to Gingerbread. The easiest way to root nowadays is to use GingerBreak. It can be found here:
[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers
Instruction Steps:
1. Turn on USB Debugging (Settings - Applications - Development)
2. Copy the GingerBreak.apk to a /sdcard dir, then using a 'file manager' app (search for one in Android Market) install it like a regular app.
3. It can take up to 10 minutes, and will reboot automatically when complete (rooted), if attempt fails, reboot manually & run it again.
Install custom recovery image
The recovery image is an alternative bootup instead of normal Android Operating System. It allows low-level operations such as backup/restore a ROM, wipe partitions, and flash ROMs.
4. Download and copy the recovery image VM670NH_recovery.img (works with new & old OV screens) onto your /sdcard.
5. Install the Flash Image GUI app (save the .apk to a /sdcard directory, then open it with file manager) Run the app & select 'Recovery Image' option with the file above.
Flash Custom ROM
I.H.O CyanogenMod 7 ROM (Gingerbread)
6. Copy the unextracted ROM .zip that you wish to install to the /sdcard dir. Also if installing a CyanogenMod Gingerbread ROM, the unextracted gapps.zip also needs to be placed in the same dir to flash right after the ROM .zip.
7. Boot into Clockworkmod recovery mode (From powered off state, hold vol-down, home, and power button until the LG logo appears).
8. FIRST, BACKUP ORIGINAL ROM! Don't continue until this is successful. Use vol-up/down, camera, & back keys to navigate in recovery.
9. Wipe Data/Factory Reset, wipe cache partition. Under Advanced submenu, wipe dalvik-cache. Then uner Mounts & Storage submenu, format all partitions EXCEPT /sdcard.
10. Flash the custom ROM.zip from sdcard and gapps.zip too if going to a CyanogenMod ROM
11. Reboot and enjoy the new ROM, the first boot takes longer than usual, also some problems may disappear after rebooting.
NOTES:
- NEVER use Android Settings 'Factory Reset' from now on, only do factory reset & wipes from within recovery mode. Most ROMs should have this option removed from the Android settings.
- Some newer Optimus V screens hardware changed, see link: [FIX]Black screen with custom recovery and custom roms (BobZHome's IHO recovery from the Wiki binary -> recovery page also works with newer screens.)
- If restoring a backed up ROM in CWM recovery gives 'MD5 mismatch' error (likely caused by renaming a ROM backup). Try this fix:
# cd /sdcard/clockworkmod/backup/<name_of_backup>
# rm nandroid.md5
# md5sum *img > nandroid.md5
- If you ever want to restore to original stock ROM (ONLY on OV's with older screen), with original recovery and UNrooted:
http://www.prepaidandroid.org/index...e_your_Optimus_V_to_almost_original_condition
titanium backup?
Excellent guide for the likes of me (noob), you might wanna mention titanium backup too
help
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Zachary droid said:
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Click to expand...
Click to collapse
What is the exact error you're getting? I believe you have to keep retrying, maybe up to 10 times.
Thanks a lot.Real helpful
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
KidGusto said:
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
Click to expand...
Click to collapse
the windows drivers and gingerbreak will work.
you'll need an optimus S custom recovery and rom, though. If you use optimus V software, your home and menu keys will be backwards, and there may be other little issues with the network.
look on android central forums for optimus S development and you'll find roms and recoveries no problem.
Thank you for this. The Rom manager method is great, i was afraid not to brick my optimus one with the adb shell crap and pc connection. They should make a nici sticky like this in the euro section, not with adb crap.
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
cobraextreme said:
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
Click to expand...
Click to collapse
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
bigsupersquid said:
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
Click to expand...
Click to collapse
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
cobraextreme said:
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
Click to expand...
Click to collapse
Updated original post with link for the new OV screens.
lamenramen said:
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
Click to expand...
Click to collapse
ROM Manager is only supposed to be use to flash the Clockworkmod recovery image, then everything else is done by booting into the recovery mode. ROM manager's other features should not be used on the OV.
Whyzor said:
Updated original post with link for the new OV screens.
...
Click to expand...
Click to collapse
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
bigsupersquid said:
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
Click to expand...
Click to collapse
I think there's about an 85% chance that this contains the kernel that you're looking for; not sure if you have some way to deal with that 15% uncertainty but hopefully it's helpful.
Questions about ROM Manager
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
luwizwiz said:
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
Click to expand...
Click to collapse
This thread is under the Optimus V development section, you should ask questions about the p500 in this forum section:
http://forum.xda-developers.com/forumdisplay.php?f=839
Thanks, i didn't notice that its for Optimus V, i have a Optimus One. many thanks
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
ct200 said:
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
Click to expand...
Click to collapse
If you go into 'adb shell' from the PC with phone connected, or open the app 'terminal emulator' to get a unix prompt, and type 'busybox', you should see a list of commands. If you get a no command found, then it's not installed. It's suggested to install so you can run unix commands, but not really needed. Root & custom recovery are the important ones. You're probably safe to continue, just make sure to make a backup in recovery mode before doing anything else.
NOTE: If anyone has any further questions about recoveries on the S3, please note that I have moved on to another device. Sorry!
So you've got your device rooted, and you want to install a custom recovery? Great! Don't just follow any guide you stumble across though, as some of the early recovery packages for the "AT&T" model were actually just copies of the custom Sprint recovery, and then you'll have all sorts of fun trying to install ROMs. ("Status 7" errors anyone? )
I'd like to talk about 4 ways to get the custom recovery of your choice onto your device.
Using mskip's Toolkit CWM [link]
Follow the instructions posted in his thread, and if you have any problems, direct them there as well!
Using ROM Manager CWM [link]
For some reason, ROM Manager doesn't always offer the correct list of devices to flash a recovery for and you won't see the SGS3 (AT&T) in the list. If that happens, force-close the app from Settings > Applications and try again. If this method just won't work for you, move on to option 4.
Using GooManager TWRP [link]
If you've been looking at ROMs, you may have noticed Goo.IM is a popular hosting website for Android developers. It's so popular, in fact, that they have produced an Android app that searches their website for updates for your ROM, and can even install TWRP with only a few simple clicks! Just open up GooManager, tap Menu, and tap "Install OpenRecoveryScript". You will be guided step-by-step from there by the app.
Note: Some people (myself included) have reported issues with this method, where the app claims to have installed the recovery, but when you reboot into recovery mode, nothing has changed. This issue may have been resolved in newer versions; I was able to successfully install TWRP using this method on Sept 26 2012.
Manually via ADB or Terminal Emulator CWM or TWRP [Terminal Emulator link]
If the other options just won't work for you, or if you would rather do an install by hand to ensure you're getting the latest version, read on...
Manually Installing a Recovery
While this may seem difficult, it's really not. Grab a recovery image (these files end in ".img") such as ClockWork Mod (CWM) or Team Win Recovery Project (TWRP) for your device. Most ROM developers say to use CWM, but they both work equally well.
In our case, we need an image for the Samsung Galaxy S3 AT&T. Telus, Rogers, Bell, and SaskTel phones are (almost*) the exact same phone as AT&T, if you have one of these devices, you will be installing the AT&T recovery.
Now, transfer the ".img" file you downloaded onto your device. I'd suggest somewhere with a nice short path, like "/sdcard/<file>.img" (you'll thank me later, especially if you're using terminal emulator on the device)
Now, let's back up your existing recovery. If things go wrong, you can use this backup to get back to where you started.
Code:
$ su
# dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery-backup.img
That should have created a "recovery-backup.img" on your phone's internal storage.
Here's the part you've been waiting for: Flashing the new image, which installs it as your recovery system. You do this from either an ADB shell or inside Terminal Emulator.
Code:
$ su
# dd if=/sdcard/[B]<file>[/B].img of=/dev/block/mmcblk0p18
You're done. Reboot into your new recovery by holding VolUp and Home while you power on your device.
If you need to return to the stock recovery, that IMG can be downloaded here: stock-recovery.img - 10.00 MB
*NOTE: While we're on the topic, let's take a second to talk about what makes the Canadian I747M different from the AT&T I747.
The short version is... The modem. AT&T is using completely different and incompatible modem firmware in their phones when compared with the Canadian models. Rogers, Bell, Telus, and any other Canadian I747M are the same device (Samsung worked some strange voodoo and got all the Canadian carriers to agree on the same hardware!) which means that if Rogers releases a new modem firmware update, a SaskTel user could install it without issue. AT&T modem updates will not work on Canadian models, nor will Canadian updates work on AT&T phones! I've tried it. Trust me. You don't want to deal with the hassle of fixing it.
Please remember to click/stick/lick/kick the "Thanks" button if you found this guide helpful!
How bout a 4th method for TWRP?
This should come in handy for some of the newer users
Well, the other TWRP method assumes that you already have a custom recovery installed to flash the ZIP from... If you've gotten that far already, I don't think you should need me to tell you how to flash a ZIP.
theres also GooManager from the market. its how I installed TWRP just download the app open it hit menu you'll see some options come up hit "install Open Recovery Script" it will ask if your sure hit ok and your done the whole process will take 30secs
Moved to General so new members can post questions
and stuck
FNM
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
dhostetter said:
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
Click to expand...
Click to collapse
Where'd you get it from? I'll add it to the OP.
There is a touch CWM for d2att available for manual installation.
http://www.clockworkmod.com/rommanager
tonymtl said:
There is a touch CWM for d2att available for manual installation.
http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
There sure is! One of the benefits of manual installation is that you can find exactly what you want to use, and not rely on ROM Manager or other tools to make the decision for you!
Sent from my SAMSUNG-SGH-I747M
dstruct2k said:
Where'd you get it from? I'll add it to the OP.
Click to expand...
Click to collapse
+1. I am also looking for stock recovery...
Sent from my SAMSUNG-SGH-I747 using xda premium
I rooted my phone just after I bought it but was holding off on installing recovery due to how many hours I spend at work. Haven't had the time. I was also waiting on clear instructions on doing it manually, as it's easier for me since I'm not home often enough to use my PC and can't use the USB cord at work. Thank you SO much! Worked perfectly!
Edit: Spoke a little too soon. I'm seeing my backup dated 1970....
nekkidtruth said:
I rooted my phone just after I bought it but was holding off on installing recovery due to how many hours I spend at work. Haven't had the time. I was also waiting on clear instructions on doing it manually, as it's easier for me since I'm not home often enough to use my PC and can't use the USB cord at work. Thank you SO much! Worked perfectly!
Edit: Spoke a little too soon. I'm seeing my backup dated 1970....
Click to expand...
Click to collapse
That's a known issue with any recovery on the SGS3, it seems that the hardware clock cannot be accessed by the recovery no matter which recovery you use.
Did you happen to make a backup of your stock recovery? If so, I'd like to get a copy of it to add to the OP.
Nice HowTo, but the glaring omission is using the GooManager app to flash TWRP.
A lot of people are moving on from the old CWM to "something better".
zmore said:
Nice HowTo, but the glaring omission is using the GooManager app to flash TWRP.
A lot of people are moving on from the old CWM to "something better".
Click to expand...
Click to collapse
I could never get that to actually work in the past, so I guess I forgot about it. I just tested it now, and it worked fine, so I've updated the OP. Thanks!
dhostetter said:
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
Click to expand...
Click to collapse
See my Index for flash back to stock. There is a great vid tutorial.
PS dstruct2k I have added this thread to the INDEX. Nice work
Thanks, just flashed latest CWM Touch. External SD Card support rocks
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
HAVOK83 said:
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Then you're skipping a step, or typing something incorrectly. Once DD is done its work, you should get a response saying "Copied 10MB OK" or something similar. If it says that, then the stock recovery no longer exists.
HAVOK83 said:
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Please visit this post and follow from step 11-15. Shows kind of messed up on the XDA app so view it on your desktop. Very detailed guide for those who are confused. Thank you.
http://forum.xda-developers.com/showthread.php?t=1912335
Sent from my T&K Blessed SGH-I747
I followed those same steps but from a different thread and it still wasn't upgrading my clockwork recovery and kept getting status 7 when trying to flash cm10. Now I installed touch version hoping I would be able to get cm10 installed but still getting status 7. Any help appreciated
Sent from my SGH-I747M using xda app-developers app
So for some reason, I catch an error everytime I try to flash a rom to my phone. Then I am forced to restore my backup.
I have it rooted with CWM v5.5.0.4.
i747.
Not sure what other information you guys would need to assist. Would I need to re-root it? Different version of CWM?
Are you wiping data before you flash any new roms? That could be it..
Yep, always wipe data/factory.
.... i'm pretty sure that telling us what the error message says would help, too....
I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.
jethro650 said:
I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.
Click to expand...
Click to collapse
Agreed, almost undoubtedly...in every recovery flashable .zip there is an update-binary file which is the actual executable that is commanded by the update-script on what operations to perform. The newer versions of this binary are incompatible with older versions of the recoveries. This effect is not necessarily one way either, an older recovery trying to flash a new .zip or vice versa can produce this error but as a general rule using the newest recoveries should minimize this problem. The only time the reverse is a problem is when there is an update to the recovery api and there hasn't been an updated update-script built into a .zip. The easiest way to check is download the appropriate rom manager for your recovery, Clockwork Rom Manger for CWM or Goomanager for TWRP.
To install a custom rom of course, I was trying to find twrp for this tablet.
SysAdmNj said:
To install a custom rom of course, I was trying to find twrp for this tablet.
Click to expand...
Click to collapse
Look in original android development sub forum...
SysAdmNj said:
To install a custom rom of course, I was trying to find twrp for this tablet.
Click to expand...
Click to collapse
I too was searching for twrp after having rooted with CF-Autoroot, and I found it at their website. But I have not had any success in installing it. Odin3 v3.09 comes back with nothing, regardless of using the .img, .md5, or .zip extension of the recovery. Same as with philz cwm recovery. It must be me, because others have installed these recoveries just fine. I’ll have to check that my anti-virus sw is disabled and that the usb drivers are compatible with my OS. I’m still researching. I’ll post back if I succeed. Here are the links below. Whichever recovery you choose make sure you download the correct one for the model you have. (SM-T800 vs T801 vs T805, etc…) Good luck!
twrp: http://teamw.in/project/twrp2/239
Philz: http://forum.xda-developers.com/galaxy-tab-s/development/sm-t700-tab-s-definitive-rom-nf9-t2839989
.
Hal Seaman said:
I too was searching for twrp after having rooted with CF-Autoroot, and I found it at their website. But I have not had any success in installing it. Odin3 v3.09 comes back with nothing, regardless of using the .img, .md5, or .zip extension of the recovery. Same as with philz cwm recovery. It must be me, because others have installed these recoveries just fine. I’ll have to check that my anti-virus sw is disabled and that the usb drivers are compatible with my OS. I’m still researching. I’ll post back if I succeed. Here are the links below. Whichever recovery you choose make sure you download the correct one for the model you have. (SM-T800 vs T801 vs T805, etc…) Good luck!
twrp: http://teamw.in/project/twrp2/239
Philz: http://forum.xda-developers.com/galaxy-tab-s/development/sm-t700-tab-s-definitive-rom-nf9-t2839989
.
Click to expand...
Click to collapse
It was easier than I thought. If you are rooted, just download twrp manager from playstore, and find your device name chagallwifi in my case I have the t800. And once it downloads recovery, install it.
SysAdmNj said:
It was easier than I thought. If you are rooted, just download twrp manager from playstore, and find your device name chagallwifi in my case I have the t800. And once it downloads recovery, install it.
Click to expand...
Click to collapse
I did download twrp manager from playstore and tried it, before trying Goo manager, and ROM Toolbox pro. All said that there was no compatible recovery for the device. Maybe at that time (Sun Aug 31) twrp had not officially sanctioned it for wide release, since none of those managers were able to find it for download. That's when I went to TeamWin and downloaded it directly. So if it now works for you, I'll try twrp manager again. I'll keep you posted. Thanks for the tip.
Hal Seaman said:
I did download twrp manager from playstore and tried it, before trying Goo manager, and ROM Toolbox pro. All said that there was no compatible recovery for the device. Maybe at that time (Sun Aug 31) twrp had not officially sanctioned it for wide release, since none of those managers were able to find it for download. That's when I went to TeamWin and downloaded it directly. So if it now works for you, I'll try twrp manager again. I'll keep you posted. Thanks for the tip.
Click to expand...
Click to collapse
Great news! I got home and removed twrp manager + data from my Tab and installed it again from playstore. I remembered you mentioned device name "chagallwifi". Before I had been searching for SM-T800 and couldn't find it in the list of available devices. Thanks for including chagallwifi in your comment, otherwise I would have been lost again. This time it worked just as you said. One very import note: within the twrp manager app you are also able to fix the kitkat 4.4 extSDcard -ro issue, where kitkat 4.4 won't let you write to the extSDcard. so for anyone else reading this I suggest you select that while you have the chance. Some people may not want to install a recovery or a custom ROM, they just want to be able to write to their external SDCard. You can download the app "NextApp SDFix" from the playstore and run it to get around the kitkat issue. Thanks again for your help and speedy reply.
Hello,
I am wondering if it is possible to install TWRP over top of CWM? When I initially rooted my phone CWM was installed, however to install a new rom I need TWRP. Is this possible?
Thanks,
Skyty said:
Hello,
I am wondering if it is possible to install TWRP over top of CWM? When I initially rooted my phone CWM was installed, however to install a new rom I need TWRP. Is this possible?
Thanks,
Click to expand...
Click to collapse
Yes. It's been a loong time. Best I can recall, I did the following:
1. Flash'd a ZIP of an old TWRP (couldn't find latest in ZIP file)
2. Rebooted into Recovery
3. Used old TWRP to flash IMG file of new TWRP
Just to make sure I understand (as it's been a while since I rooted a phone or done anything like this).
1.) When you say flashed, do you mean in the TWRP app on the screen where you select your phone model?
2.) So if I flash TWRP (in the manner I described above assuming that's what you meant) and reboot into recovery it will overwrite Clockworkmod and then I'll be in TWRP recovery?
3.) If I do this with the most recent TWRP version I'm assuming this step will be unecessary?
My apologies if I misunderstood what you were trying to say! Thanks for taking the time to respond!
Skyty said:
...
1.) When you say flashed, do you mean in the TWRP app on the screen where you select your phone model?
2.) So if I flash TWRP (in the manner I described above assuming that's what you meant) and reboot into recovery it will overwrite Clockworkmod and then I'll be in TWRP recovery?
3.) If I do this with the most recent TWRP version I'm assuming this step will be unecessary?...
Click to expand...
Click to collapse
Quick answers: No, no, and maybe.
It appears that you may be confusing the TWRP app (which is basically useless bloat) with the actual TWRP recovery. You need to find and download the latest TWRP recovery for your device model. If you can find a ZIP of it, great; because CWM can then install TWRP recovery for you (so that when you reboot into recovery, you'll see TWRP instead of CWM). In my case, there was no ZIP available for the latest TWRP; it was available only as an IMG file. An old version of TWRP recovery, however, was and likely still is available in a ZIP file. So use CWM to install that ZIP of older TWRP, which can then install newer TWRP as an IMG file. I'm just a struggling noob myself, but I'm pretty sure CWM is not able to install an IMG file. Good luck!
MrGoodtunes said:
Quick answers: No, no, and maybe.
It appears that you may be confusing the TWRP app (which is basically useless bloat) with the actual TWRP recovery. You need to find and download the latest TWRP recovery for your device model. If you can find a ZIP of it, great; because CWM can then install TWRP recovery for you (so that when you reboot into recovery, you'll see TWRP instead of CWM). In my case, there was no ZIP available for the latest TWRP; it was available only as an IMG file. An old version of TWRP recovery, however, was and likely still is available in a ZIP file. So use CWM to install that ZIP of older TWRP, which can then install newer TWRP as an IMG file. I'm just a struggling noob myself, but I'm pretty sure CWM is not able to install an IMG file. Good luck!
Click to expand...
Click to collapse
Ahhhh, okay that makes sense. I think I follow. Now in another thread you mentioned that if I need to go back and restore I'd use TWRP to flash CWM, hen I can use CWM to recover my old nandroid backups.
A couple final questions. Will I need to do a wipe when I flash the old TWRP zip (side note, do you know a good place to find those)? If I need to go back to CWM is there any place I can find it to flash with TWRP?
Thanks for all your help!
Skyty said:
... if I need to go back and restore I'd use TWRP to flash CWM, hen I can use CWM to recover my old nandroid backups ...
Click to expand...
Click to collapse
Correct. That is IF you can find TWRP and CWM as ZIP files. I used to switch back and forth frequently, but that was years ago. TWRP is so much more useful, I no longer have anything CWM related nor the ZIPs; and can't even find where I got them. I'm pretty sure they were here on XDA. Spent some time searching, no luck. Then I tried Google. The first snippit nail'd it, here:
https://forum.xda-developers.com/galaxy-s4-mini/development/recovery-cwm-twrp-philz-t3182207
Skyty said:
.... Will I need to do a wipe when I flash the old TWRP zip...
Click to expand...
Click to collapse
I never wiped. I seem to recall that when installing to the recovery partition, one of the steps I saw in the log was a wipe or maybe even a reformatting of that partition taking place along the way.
Skyty said:
.... (side note, do you know a good place to find those)? If I need to go back to CWM is there any place I can find it to flash with TWRP?
Click to expand...
Click to collapse
They're both in the link (above).
Skyty said:
.... Thanks for all your help!
Click to expand...
Click to collapse
That's what the [Thanks] button is for, here on xda.
MrGoodtunes said:
Correct. That is IF you can find TWRP and CWM as ZIP files. I used to switch back and forth frequently, but that was years ago. TWRP is so much more useful, I no longer have anything CWM related nor the ZIPs; and can't even find where I got them. I'm pretty sure they were here on XDA. Spent some time searching, no luck. Then I tried Google. The first snippit nail'd it, here:
https://forum.xda-developers.com/galaxy-s4-mini/development/recovery-cwm-twrp-philz-t3182207
Click to expand...
Click to collapse
I appreciate the link, however, I think those zips are for a different model of phone than mine. However, I think I possibly found versions that will work for me... Is there any real way to confirm?
The serranoltexx CWM Zip
https://forum.xda-developers.com/showthread.php?t=2364980&page=99
The serranoltexx TWRP Zip
https://androidfilehost.com/?fid=24052804347768468
However, I'm not 100% certain either of these will work, and I'm not sure how I'd figure that out.
MrGoodtunes said:
That's what the [Thanks] button is for, here on xda.
Click to expand...
Click to collapse
Done!
Skyty said:
... those zips are for a different model of phone ...
Click to expand...
Click to collapse
OMG! You're right, those are for the Value Edition. I completely miss'd the "ve" in them. Sorry.
Skyty said:
... I think I possibly found versions that will work for me..
The serranoltexx CWM Zip
https://forum.xda-developers.com/showthread.php?t=2364980&page=99
The serranoltexx TWRP Zip
https://androidfilehost.com/?fid=24052804347768468 ...
Click to expand...
Click to collapse
I remember using that very CWM zip version 6.0.5.1, so it should work okay. Good find.
I'm not familliar with that particular TWRP zip. It does clearly indicate being for the i9195 model; I'm just not sure about what "open" means at beginning of zip's filename. Still, worth a try. (If it fails, you can more easily find a TAR file of the most recent TWRP and use Odin to install it.)
MrGoodtunes said:
OMG! You're right, those are for the Value Edition. I completely miss'd the "ve" in them. Sorry.
I remember using that very CWM zip version 6.0.5.1, so it should work okay. Good find.
I'm not familliar with that particular TWRP zip. It does clearly indicate being for the i9195 model; I'm just not sure about what "open" means at beginning of zip's filename. Still, worth a try. (If it fails, you can more easily find a TAR file of the most recent TWRP and use Odin to install it.)
Click to expand...
Click to collapse
So, just thought I'd let you know that I'm up and running with LineageOS and I tested reverting back and forth to CWM and TWRP. Eveything seems in working order! I appreciate you help and have clicked the thanks button on your messages! All the best!
Skyty said:
... I tested reverting back and forth to CWM and TWRP. Eveything seems in working order!
Click to expand...
Click to collapse
That's excellent. It's really amazing how much we can do with this little S4mini device; thanks to the work of devs, several of whom are still providing updates. After all there's never been a more powerful device (other than S4mini VE) that weighs under 4 oz.
MrGoodtunes said:
That's excellent. It's really amazing how much we can do with this little S4mini device; thanks to the work of devs, several of whom are still providing updates. After all there's never been a more powerful device (other than S4mini VE) that weighs under 4 oz.
Click to expand...
Click to collapse
Yeah, its amazing! I've been able to breath new life into my old phone, I'm shocked at how well it runs on the S4; not as well as my newer phones, but better than before. Funnily enough, its actually running a newer version of Android than my S8 and S10e haha. Now onto those phones... been trying to get them both rooted but it's looking like a no go haha.