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
Related
Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
CWM NANDROID
Unzip then place in your CWM folder sub folder backups then boot to clockwork mod and restore
Stock Recovery Image
use this while in fastboot mode (hold vol up + down + power while phone is off) then on your computer issue cmd fastboot flash recovery recovery.img (search for how to setup adb)
Need Help Rooting? How To Videos Thanks to QBking77!
Need More Help? Join the IRC channel!
Coming Soon:
Radio Fix (if you flashed a verizon radio)
If this helped Donate To Me
Updated with CWM Nandroid and Stock Recovery Image
Sweet thanks
Sent from my Galaxy Nexus using Tapatalk 2
thanks to raiderep for giving me the stock recovery
Well Thanks Let the flashing begin ;P
Here is a link for the drivers from Samsung as well maybe helpfull
http://www.samsung.com/us/support/owners/product/SPH-L700ZKASPR
its the exe file and works well
thanks.. ill get how to videos up soon
qbking77 said:
thanks.. ill get how to videos up soon
Click to expand...
Click to collapse
You a good guy, so is OP.
added thanks to all the guys over on the IRC channel
shabbypenguin said:
thanks to raiderep for giving me the stock recovery
Click to expand...
Click to collapse
Glad to help when I can as always, go android!
Sent from my Galaxy Nexus
Im using twrp rec.
I dont like/trust twrp recovery, where can i get a sprint compatible cwm recovery?
Sent from my Xoom using XDA Premium HD app
malibu_23 said:
Im using twrp rec.
I dont like/trust twrp recovery, where can i get a sprint compatible cwm recovery?
Sent from my Xoom using XDA Premium HD app
Click to expand...
Click to collapse
We do the CWM for the verizon version is the one that works......
What if...
Wordlywisewiz said:
Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
Click to expand...
Click to collapse
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!
turbo2125 said:
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!
Click to expand...
Click to collapse
same here...says "no sim card"...WTF...
Try doing a factory data reset. Just a shot in the dark...
turbo2125 said:
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!
Click to expand...
Click to collapse
same thing has happened to my phone but not with this immage what happened is i accidently flashed a image from a verizon phone to the sprint phone and now is all kinds of messed up
my friend is currently trying to fix it for me (hes a hell of a lot smarter than i am)
ill let u know the results
Same Song.. Several Verses Later
I would really like to find out if any of you figured this out??
I find myself in the same position as I'm finding that many have on here as well. I found this thread interesting because it is dealing with the Sprint Galaxy in particular. I have hosed the radio and the baseband on the Galaxy - likely the EFS parition, not sure.. at this point. It needs to be made very clear to everyone that even has a thought of flashing with this phone to make triplicate backups of the EFS partition before they turn the phone on (exxageration for affect).
That being said - I don't think that gets the rest of us anywhere. I'm a OG owner and a Bionic owner - and the first 72 hours of Samsung ownership has felt like non-stop triage to me..
I have this here.. but this really isn't the specific image for the Sprint the phones...
The link below points to a post for the IMM761 GSM+HSPA - which I believe these phones to be identical.. and since Sprint had locked code for the CDMA versions - is this one the same - in other words, is there an image out there that can be downloaded, flashed, and from there we can we can either fix the EFS and restore IMEI folder and baseband function or at least call warranty?
At this point - I can't reset the counter on the phone, I can't take it to the store (as if the 7 iployees would know what I was talking about) and I'm not about to pay $800 to learn that the EFS partition is the "short" in the term "got you by the short hairs"..
androidforums -
Heat57 says:"
It sounds as so you are on the GSM "maguro" device. In that case I suggest you download the complete ICS 4.0.4 factory image from Google at ... file. Beware! if you have a Windows PC the original download with a .tgz extension will be renamed by Windows automatically to a .tar file, which means that you'll have problems extracting it. In that case simply rename the file by changing the extension to .tgz and all will be well. Note: you'll need the Galaxy Nexus bootloader unlocked in order to flash a factory image and at the end of the procedure you can leave it unlocked and flash a Superuser file to root, if so desired. You'll need the Android SDK installed on your PC and then copy the bootloader, radio and image .img files to your ...android-sdk\platform tools-tools folder and run the adb commands in the windows command shell (note: you must flash each image in this order and wait until each image is flashed completely >bootloader >radio > image). Finally, flash the "image-soju-imm76d.zip" through your cwm recovery. You should end up with a healthy Galaxy Nexus on ICS 4.0.4 and everything working"
Wordlywisewiz said:
Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
CWM NANDROID
Unzip then place in your CWM folder sub folder backups then boot to clockwork mod and restore
Stock Recovery Image
use this while in fastboot mode (hold vol up + down + power while phone is off) then on your computer issue cmd fastboot flash recovery recovery.img (search for how to setup adb)
Need Help Rooting? How To Videos Thanks to QBking77!
Need More Help? Join the IRC channel!
Coming Soon:
Radio Fix (if you flashed a verizon radio)
If this helped Donate To Me
Click to expand...
Click to collapse
I think you are right but I do have cwm Also when I followed techfanatic's vid to unroot it said my phone was unrooted but the radio failed error came up. Also I am still on codeandroid. can I actually be unrooted and still be on that? Must I root again? Thanks.
Teamwin Recovery Project for A100 version 2.2.2.1 -godmachine81 release-
SOURCES: Available via Github
Download and Install via the official supported method by TWRP
Install Goo Manager app from Play Store, Open Goo Manager, In the Menu in top right corner go to "Install OpenRecovery Script" Follow Instructions On screen
Download Automated Installer (Windows / Linux):
Linux Installer - 2.2.2.1
Windows Installer - 2.2.2.1
Download IMG:
TWRP v2.2.2.1 main mirror
Download Flashable Zip: (Upgrade Only)
TWRP 2.2.2.1 Flashable Upgrade
Updated TWRP release features:
Uses a custom recovery kernel based off of my v1.5 standard kernel with most unneeded features taken out, i.e. governors, schedulers, networking, misc devices, and most things not needed for recovery operations
Kernel and TWRP includes patches aimed at brick prevention
Resolution is set at native 1024x600
Very fast actions and touch response
Backward compatibility with previous releases of TWRP
Compatibility with all Ice Cream Sandwhich and Jelly Bean ROMs for the A100(HoneyComb should be compatible too, however currently untested)
All previous features from TWRP that you may be familiar with are included
Mount Point Information:
External Storage - mountpoint= /external_sdcard
Internal Storage - mountpoint = /sdcard
Instructions:
Automated Installation (Windows/Linux):
Most importantly you need to have all drivers required for adb and fastboot working on your OS, this shouldn't be a concern for linux users, however it may be for Windows users as it is picky about adb drivers.
Download the above Automated Install .zip file for your operating system
Extract the contents of the Zip to a location on your PC's hard drive
Change to the extracted directory's contents.
Run the installer; On windows you may just double click the install-windows.bat file, on linux you need to run the install-linux.sh script
example linux installation commands:
Code:
cd a100_twrp_installer_linux
Code:
bash ./install-linux.sh
Read the on screen information of the progress. If you get any errors you will need to resolve the issue or try one of the following alternative install methods.
If you need more detailed installation instructions please read the INSTALL file included inside the .zip
Manual installation:
Download the .img file for the recovery
Connect your A100 device to USB on your PC
While your A100 is booted in either Android or Recovery just enter the following into your PCs command prompt/shell:
Code:
adb reboot bootloader
Now flash the image - at the command prompt/shell enter:
Code:
fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img
Reboot the device - again from the command prompt/shell:
Code:
fastboot reboot
Enter Recovery mode - While tablet shuts off, hold the Vol - (down) button until you see the screen saying "loading recovery kernel"
Checkout the new TWRP build and enjoy!
Flashable Upgrade Instructions: (flash just like you would any other .zip, but here are instructions anyway)
Download the Flashable ZIP above
Save to a location on your tablets internal or external memory
Boot to recovery
Choose the file a100_twrp_upgrade_2.2.2.1.zip in the install menu
Swipe to install
Wait and DO NOT Disconnect your A100!
When finished, go back to Main menu - choose Reboot - and Reboot Recovery
Enjoy the Official 2.2.2.1 TWRP Release!
If you would like to help out with the continuance of my kernel development and other goodies for your Acer Iconia Tab please consider a small donation to help out with bills, baby formula, wipes, diapers, etc. All donations are very appreciated by my family and I! Thanks
.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6
pio_masaki said:
.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
And don't forget that i forgot the download link!! lol **fixed haha
Broken links, so you can correct it.
Fransis88 said:
Broken links, so you can correct it.
Click to expand...
Click to collapse
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone
linuxsociety said:
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone
Click to expand...
Click to collapse
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.
Fransis88 said:
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.
Click to expand...
Click to collapse
So let me know how you like it. Also if you happen to be a linux user, I have wrote an automated installer script for linux, Xbow59 is currently writing a windows batch script for installation, I currently have the Linux installation working though if you'd like to test/try it out just let me know. Windows users can look forward to an automated solution within a day or so
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.
nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
Click to expand...
Click to collapse
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!
linuxsociety said:
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!
Click to expand...
Click to collapse
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)
nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.
Click to expand...
Click to collapse
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
nim.whit said:
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)
Click to expand...
Click to collapse
yep what pio said:
pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
I had forgot all about this, even though it is in my unreleased linux auto installer. If by chance you are using linux, I have an installer that will do this all for you the right way, I just haven't posted it yet because I don't have the windows installer fixed
you can either download the linux installer git repo and just extract it to a directory named twrp_install or similar; just run sudo bash ./install-linux.sh after you are in the install directory. https://github.com/godmachine81/Acer-A100-TWRP-Installer/zipball/linux <<current linux installer for a100 twrp
Or you can clone the repo
Code:
git clone https://github.com/godmachine81/Acer-A100-TWRP-Installer.git
then checkout the linux branch:
Code:
git checkout linux
then install:
Code:
sudo bash ./install-linux.sh
The git method requires you have git installed, you will probably just want to install from the zipball method if you don't already have git
pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause
nim.whit said:
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause
Click to expand...
Click to collapse
Once that's removed or renamed it will stop, one time deal.
Tapatalked from my A100 - Jellytime X B6
Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.
linuxsociety said:
Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.
Click to expand...
Click to collapse
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3
pio_masaki said:
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3
Click to expand...
Click to collapse
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol
linuxsociety said:
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol
Click to expand...
Click to collapse
The ics Acer zips are known brickers but it happens for a reason I'm not very clear on. HC will also brick it.
Basically there's a chance it will run the zip, attempt to flash everything, however for some reason it will fail to flash system or boot correctly, but does replace the bootloader. What I'm not clear on is why it fails on system or boot but succeeds on bootloader, or why recovery doesn't error flashing it.
Once this situation occurs you get locked out of both recovery and system by the bootloader, no adb or fastboot access to correct it.
Using the information I've gathered on this I've been working on a method to restore to stock if needed, but its going slow as I have to triple check everything before I even test it. Its a long and annoying process but should result in a 100% factory stock system.
Tapatalked from my Galaxy S II.
Installed and working perfectly!
Fransis88 said:
Installed and working perfectly!
Click to expand...
Click to collapse
Great Francis88, mind I ask which method of installation you chose?
Hi, i have this problem:
Two Galaxy Nexus, one is mine one of my friend 4.1.1 Yakju Maguro both.
I make the procedure with GNex TOOLKIT 7.8.
Install Drivers
Unlock Bootloader
Root
Flash CWM Touch
Download TWRP 2.2.2.0 through site and flash with adb in bootloader.
All works fine! ( mine)
For my friend same procedure, but flashed TWRP Recovery instead CWM
Install BusyBox. ( both with GNex TOOLKIT 7.8)
Recovery start only first time, then i get the Android with triangle and exclamation mark.
Made unroot, unloock and flashed stock Google rom.
Made same procedure as mine, and worked... Since i installed GooManager, and flashed TWRP.
Phone get super slow, Cpu at 90-100%!!!
Android System App doesn't show any threads that makes the cpu goes crazy.
Now i don't know what maybe the problems!!!
Partitioning problems with GNex TOOLKIT 7.8???
TWRP bugs?
My phone works fine, my friends install stock JB another time, root, unlock, but after flashing TWRP through GooManager, same problems...
What could it be?
Thank you very much!!! :good:
19blacktiger77 said:
Hi, i have this problem:
Two Galaxy Nexus, one is mine one of my friend 4.1.1 Yakju Maguro both.
I make the procedure with GNex TOOLKIT 7.8.
Install Drivers
Unlock Bootloader
Root
Flash CWM Touch
Click to expand...
Click to collapse
...
19blacktiger77 said:
Download TWRP 2.2.2.0 through site and flash with adb in bootloader.
Click to expand...
Click to collapse
ADB doesn't flash anything in bootloader, adb is not even available there, only fastboot.
19blacktiger77 said:
All works fine! ( mine)
For my friend same procedure, but flashed TWRP Recovery instead CWM
Install BusyBox. ( both with GNex TOOLKIT 7.8)
Recovery start only first time, then i get the Android with triangle and exclamation mark.
Click to expand...
Click to collapse
stock rom has a file (/system/recovery-from-boot.p) that overwrites the recovery if it finds something else instead of stock recovery (the "Android with triangle and exclamation mark" - pressing vol up+power here opens the recovery menu). delete or rename it.
19blacktiger77 said:
Made unroot, unloock and flashed stock Google rom.
Made same procedure as mine, and worked... Since i installed GooManager, and flashed TWRP.
Phone get super slow, Cpu at 90-100%!!!
Android System App doesn't show any threads that makes the cpu goes crazy.
Now i don't know what maybe the problems!!!
Partitioning problems with GNex TOOLKIT 7.8???
TWRP bugs?
My phone works fine, my friends install stock JB another time, root, unlock, but after flashing TWRP through GooManager, same problems...
What could it be?
Thank you very much!!! :good:
Click to expand...
Click to collapse
can't help you since you didn't do it manually through fastboot official steps. post your question in that toolkit's thread.
don't install a custom recovery from android, flash it from bootloader with fastboot. no need for root to flash it, you see. then just flash (with the recovery you just flashed, of course) a su.zip with su binary/apk and you'll be rooted. mount /system rw in recovery through adb, delete /system/recovery-from-boot.p, and you're done. reboot.
bk201doesntexist said:
ADB doesn't flash anything in bootloader, adb is not even available there, only fastboot.
Click to expand...
Click to collapse
Sorry, fastboot.
bk201doesntexist said:
stock rom has a file (/system/recovery-from-boot.p) that overwrites the recovery if it finds something else instead of stock recovery (the "Android with triangle and exclamation mark" - pressing vol up+power here opens the recovery menu). delete or rename it.
Click to expand...
Click to collapse
I read this, but i remember that with my phone i use a option with Galaxy Nexus ToolKit or Nexus Root Tolkit to prevent the recovery from be rewritten.
bk201doesntexist said:
can't help you since you didn't do it manually through fastboot official steps. post your question in that toolkit's thread.
don't install a custom recovery from android, flash it from bootloader with fastboot. no need for root to flash it, you see. then just flash (with the recovery you just flashed, of course) a su.zip with su binary/apk and you'll be rooted. mount /system rw in recovery through adb, delete /system/recovery-from-boot.p, and you're done. reboot.
Click to expand...
Click to collapse
My phone works fine, i can't understand why in phone's friend after installing GooManager and flash TWRP recovery, system got crazy...
If you did not use the toolkit I may get around my last arse helping you......
Beamed from Maguro
When going through the options before you install your twrp use option 5 to change the name and then use option 5 after you install twrp again... then the recovery will stick. It's all in the tool kit to read. Read everything that's in the instructions. It's right there when you go to install your recovery.
This is meant to be a friendly suggestion, so hopefully I won't get trounced but here goes. In the Sprint GNEX android development section, there are two stickies that explain the GNEX toolkit method of rooting, one by QBKing77 and the other by MSkip., two smart guys. A new guy or gal might think because there's no other way presented here that using a toolkit is the way to go. Maybe a correct, long form rooting guide could be placed along side these two guides in the development section.
In the Q and A section there is a stickie by Jobakuba that explains how to root the "right", long way. It might help new people and even people that have been around a while, if her guide or something similar was along side the QBKing videos and MSkips toolkit guide.
BTW, the QBKing video is new. He added the toolkit method fairly recently with the jellybean OTA. His new video replaces a video that showed the adb, fastboot method. When you go to the old video, you get redirected to the toolkit video.
// rant
// oh please, there's threads to teach how to use a toolkit? :good:
// :sarcasm:
bk201doesntexist said:
// rant
// oh please, there's threads to teach how to use a toolkit? :good:
// :sarcasm:
Click to expand...
Click to collapse
Two threads to teach people how to use the brainless toolkits... vs the 6 or 7 step guide by Jubakuba on how to actually do it yourself and know what's going on.
This is what's wrong with today's Android community.
OP. See here:
http://forum.xda-developers.com/showthread.php?t=1469909
Sent from my Galaxy Nexus using xda premium
El Daddy said:
OP. See here:
http://forum.xda-developers.com/showthread.php?t=1469909
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
EDIT - deleted
Sent from my Galaxy Nexus using Tapatalk 2
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.
Looked at ALL the referenced similar threads, and none applied to my device. So, with your permission, I would like to ask for information.
I bought a used, off-contract T-Mobile variant of Galaxy S3, SGH-T999. It IS SIM-unlocked, as I am using a Straight Talk-provided AT&T SIM without any problems. Also, it is rooted, as confirmed by Root Checker and running Terminal--I get the "#" prompt. SuperSU is installed and appears functional. However, neither CWM nor TWRP recovery programs are on the device.
How can I tell if my bootloader is unlocked? If it is not, what would you suggest to use to accomplish unlocking? I would like to be able to flash a custom ROM such as CyanogenMod.
Thank you for your help and patience.
Its not locked
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Many thanks to you both, Serio22 and Tonytien! I had no idea that the T999 had an unlocked bootloader; just another good reason to buy it vs. the AT&T variant.
I have read (MANY TIMES!!!) the procedure for using Odin to root the device and install a recovery program. There is one in particular on androidcentral forums (can't post the link just yet!) that uses GalaxyS3RootSprint.zip to root either the Verizon or the T-Mobile variants. The second step uses GalaxyS3RootSprint to flash CWM; then, a third step uses CWM-SuperSU-v0.87.zip to flash a super user program. Since my phone is already rooted and has a working SuperSU program, I wonder if I could use Odin just to flash CWM?
Have either of you ever used Flashify? That was mentioned in another thread on androidcentral as a way to flash with Odin or entering download mode.
I'm kind of spoiled: my last two Samsung smartphones have both had CyanogenMod already installed, with CWM, and I got used to entering recovery mode via the Restart menu.
Anyway, thanks again, and best retards to you both.
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Oh, one other question. My phone has stock T-Mobile Android 4.3, the "*MJC" software. I have read a number of cautions concerning the MJC software, and that one might not be able to flash CWM or custom ROM's to it. Might that be a problem for installing CWM?
Incidentally, Knox is installed on the phone, but NOT running.
stahlwird said:
Many thanks to you both, Serio22 and Tonytien! I had no idea that the T999 had an unlocked bootloader; just another good reason to buy it vs. the AT&T variant.
I have read (MANY TIMES!!!) the procedure for using Odin to root the device and install a recovery program. There is one in particular on androidcentral forums (can't post the link just yet!) that uses GalaxyS3RootSprint.zip to root either the Verizon or the T-Mobile variants. The second step uses GalaxyS3RootSprint to flash CWM; then, a third step uses CWM-SuperSU-v0.87.zip to flash a super user program. Since my phone is already rooted and has a working SuperSU program, I wonder if I could use Odin just to flash CWM?
Have either of you ever used Flashify? That was mentioned in another thread on androidcentral as a way to flash with Odin or entering download mode.
I'm kind of spoiled: my last two Samsung smartphones have both had CyanogenMod already installed, with CWM, and I got used to entering recovery mode via the Restart menu.
Anyway, thanks again, and best retards to you both.
Click to expand...
Click to collapse
You can flash CWM through Odin, but it'll take some repackaging (.img to .tar.md5) or you can search for one to download since CWM comes in .img form. Again, you could use ADB on a computer to install CWM in its .img form since your phone is already rooted. You could also just download TWRP or some other recovery that comes in .tar or .tar.md5 form, which will already be ready to flash in Odin. I haven't used Flashify, but some of the screenshots on the app listing show some kind of recovery install feature. I can't personally recommend it since I've never used it before.
stahlwird said:
Oh, one other question. My phone has stock T-Mobile Android 4.3, the "*MJC" software. I have read a number of cautions concerning the MJC software, and that one might not be able to flash CWM or custom ROM's to it. Might that be a problem for installing CWM?
Incidentally, Knox is installed on the phone, but NOT running.
Click to expand...
Click to collapse
The latest software version causes some weird things indirectly. I haven't noticed any issues with the latest CM12.1 nightlies, but you may run into issues when trying to flash a custom ROM in recovery. It seems the updater_script (a part of custom ROM zip files that tells the phone what to do when flashing in recovery) doesn't include the latest version in the line that determines if the ROM will work with the phone or not (a simple software version text comparison to make sure you won't brick your phone). This can be easily fixed since it's just a text file inside a custom ROM that can be easily modified. The software itself doesn't cause issues with system modification other than some interference with root (which, since you've told me your phone is already rooted, I assume you've figured it out). Keep in mind that the stock ROM could replace your custom recovery upon reboot (I think), which could be fixed by deleting the files 'install-recovery.sh' and 'recovery-from-boot.p' located in /system/etc/. If you're installing a custom ROM, you won't need to worry about that. Also, your Knox Warranty Bit will be tripped (your phone now definitely has a void warranty) but I'm sure you know since you're rooting and stuff. Sorry about the late response, let me know if you have any questions on anything I missed, I'm kind of jumping around with things that come to mind.
I have used flashify and do recommend it. Very easy to use and can select from different recoveries. MJC is not a problem as far as flashing recoveries or roms. Probably one of the only problem is as the poster above stated, but it may be fixed by now by developers
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Hope you two guys (Serio22 and tonytien) don't mind if I pick your brains a bit more. Flashing via phone download mode and Odin doesn't look too bad, but I keep reading all these posts about guys bricking their phones. I CAN'T do that--- this is my PHONE, not a PC I can play around with! Seems you have to have a version of Odin that matches your installed OS AND your particular phone variant, then the CWM version must match both of those. If anything doesn't match, it's brick city! I did finally find a site that lists the current version of Odin (3.07) for the T-Mobile SGH-T999 running the MJC version of 4.3 JellyBean, and it lists the matching version of CWM (6.0.1.2). So, using that site as a guide, I think I might get brave and try to flash CWM that way rather than use Flashify. But, thanks for your comments on it as well.
Far cry from flashing the next nightly on CM using CWM! There was usually a natural path of progression---CM 9.1 to 9.2, then to 10.0, 10.1, etc. There was never a need to jump around and risk bricking. AND, going into Recovery for CWM was a simple option in the Reboot menu, not having to hold down 3 keys and release one at just the right time. I lived thru two phones with CyanogenMod and ClockworkMod, and only went backwards once: I flashed a nightly that I didn't really like. It was a simple matter to go into CWM and restore from the previous Nandroid backup.
Anyway, thanks for your suggestions, help, encouragement, and your ears (eyes?).
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Oh, one more thing I forgot to mention, and ask about.
When I boot my phone into download mode, the items on the screen are these:
Product name: SGH-T999
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secure Boot: Enable
Warranty Bit: 0
Bootloader RP Swrev: 1
Not sure how to interpret these, as I've not found anywhere they are defined, other than the presence of the "Warranty Bit" line indicates I'm on 4.3, JellyBean. I'm assuming the Status of Custom is because I'm rooted.
stahlwird said:
Oh, one more thing I forgot to mention, and ask about.
When I boot my phone into download mode, the items on the screen are these:
Product name: SGH-T999
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secure Boot: Enable
Warranty Bit: 0
Bootloader RP Swrev: 1
Not sure how to interpret these, as I've not found anywhere they are defined, other than the presence of the "Warranty Bit" line indicates I'm on 4.3, JellyBean. I'm assuming the Status of Custom is because I'm rooted.
Click to expand...
Click to collapse
Yes and yes. Warranty Bit was introduced in 4.3 bootloader
serio22 said:
Yes and yes. Warranty Bit was introduced in 4.3 bootloader
Click to expand...
Click to collapse
Well, successfully flashed CWM 6.0.1.2 non-touch to my phone (I think--more below). Used the Odin/TAR method, and it was painless.
When I boot into Recovery mode, the line at the top of the screen does say "ClockworkMod Recovery v6.0.1.2", but the rest of the options on that screen look just as they did before. Went to "Advanced" and chose "Show log", and I saw some lines that concern me, to wit:
Checking for extendedcommand
Skipping execution of extendedcommand. file not found...
Can't partition non-vfat: datamedia
Can't partition unsafe device: /dev/block/mmcblklpl
Can't format unknown volume: /emmc
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
Then, when I run my X-plore File manager, I see NO ClockworkMod folder, either on my Internal or External SD cards. Do I really have it?
One last point: while looking around for the procedures to do this, I came across a video that showed using ROM Manager to load CWM. Even tho the Odin procedure seemed to work, I wonder...... Any opinions on that?
Thanks again for your reading this.
stahlwird said:
Well, successfully flashed CWM 6.0.1.2 non-touch to my phone (I think--more below). Used the Odin/TAR method, and it was painless.
When I boot into Recovery mode, the line at the top of the screen does say "ClockworkMod Recovery v6.0.1.2", but the rest of the options on that screen look just as they did before. Went to "Advanced" and chose "Show log", and I saw some lines that concern me, to wit:
Checking for extendedcommand
Skipping execution of extendedcommand. file not found...
Can't partition non-vfat: datamedia
Can't partition unsafe device: /dev/block/mmcblklpl
Can't format unknown volume: /emmc
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
Then, when I run my X-plore File manager, I see NO ClockworkMod folder, either on my Internal or External SD cards. Do I really have it?
One last point: while looking around for the procedures to do this, I came across a video that showed using ROM Manager to load CWM. Even tho the Odin procedure seemed to work, I wonder...... Any opinions on that?
Thanks again for your reading this.
Click to expand...
Click to collapse
Did you flash recovery and then reboot straight into recovery without it letting boot the system? If not, do so. You shouldn't need any app to boot recovery, but you can use one if you like. Just a preference
serio22 said:
Did you flash recovery and then reboot straight into recovery without it letting boot the system? If not, do so. You shouldn't need any app to boot recovery, but you can use one if you like. Just a preference
Click to expand...
Click to collapse
No. I checked the restart box in Odin, and it did restart the system normally into JB. Then, I shut down completely and did the 3-button boot into Recovery.
Got an update, however. Since I saw those entries in the log, I decided to try the ROM Manager flash of CWM. Downloaded ROM Manager from the Play Store, and started it. It said it needed to update the recovery, and I let it update to CWM v. 6.0.4.5, and everything looked good. Checked the log, and no entries for concern. BTW, it offered the "Touch" version of CWM, but I declined that, going with the old fashioned side-button version.
Got one other question, however. On my CyanogenMod phones, when I got into CWM, the backup option was for Nandroid backup. But, the version I have on this phone doesn't even mention that. Is that an add-on of some sort?
Thanks again for your help!
Best regards,
Stahlwird
stahlwird said:
No. I checked the restart box in Odin, and it did restart the system normally into JB. Then, I shut down completely and did the 3-button boot into Recovery.
Got an update, however. Since I saw those entries in the log, I decided to try the ROM Manager flash of CWM. Downloaded ROM Manager from the Play Store, and started it. It said it needed to update the recovery, and I let it update to CWM v. 6.0.4.5, and everything looked good. Checked the log, and no entries for concern. BTW, it offered the "Touch" version of CWM, but I declined that, going with the old fashioned side-button version.
Got one other question, however. On my CyanogenMod phones, when I got into CWM, the backup option was for Nandroid backup. But, the version I have on this phone doesn't even mention that. Is that an add-on of some sort?
Thanks again for your help!
Best regards,
Stahlwird
Click to expand...
Click to collapse
Not sure, I use twrp. Haven't used cwm in ages