Develop Bugs

[HOW-TO] Simplified Root + Recovery + Custom ROM

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.

[SGH-T999] CF-Auto-Root

Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) !
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 8 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Stock recovery
Installation and usage
Flash the CF-Auto-Root package as PDA in ODIN (details on how to do that are in next post), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home).
Using this root increases your flash counter. You should run Triangle Away (see below) after rooting to reset the counter. Note that if you want to run custom kernels or custom recoveries, your flash counter will be set to 1 at every boot. Either configure Triangle Away to reset the counter at every boot (Play version only) or only reset the counter when you need to go into warranty.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
No CWM and such ?
I have personally moved away from permanent custom recoveries, and I am no longer supporting them. On newer devices they cause flash counter and OTA flashing issues. If you really want one, others do provide versions of CWM and TWRP for most devices. Personally I just use Mobile ODIN to install ZIPs and Titanium Backup for my backup/restore needs. I do always want root though, and as such I'm still supporting CF-Auto-Root as quick way to root.

ODIN Installation (detailed)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
- NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
You may now optionally want to install and run Triangle Away to reset the flash counter.

Download
2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download:
SGH-T999: CF-Auto-Root-d2tmo-d2tmo-sght999.zip
--- History ---
2013.05.20: SuperSU v1.30
2013.02.20: SuperSU v1.05
2012.12.02: SuperSU v0.98
2012.10.30: SuperSU v0.96

Wow this should make it very easy to root for some. I appreciate the idea of straying away from custom recoveries and just using Odin. That is the safest bet. With all the problems with partitions being messed up etc. It's a great idea. I'm a crackflasher so I appreciate my backups.... and being untethered.
Sent from my SGH-T999 using xda premium

This is Awesome!
Thanks for bringing this over for us!
You can never have too many CF-apps!!! :good:
BTW, Mobile Odin is easily the most useful app I have!
Thank you for all of your work!

wow this is gonna help a ton of new peeps to the world of rooting, thanx op.

I have updated all the CF-Auto-Root downloads. The scripts have been slightly improved, the roboto font is now used, and SuperSU has been updated to v0.98 !
There is no need to flash the updated version if you are currently successfully rooted (you'll have gotten the latest SuperSU from Google Play updates already).

Chainfire said:
I have updated all the CF-Auto-Root downloads. The scripts have been slightly improved, the roboto font is now used, and SuperSU has been updated to v0.98 !
There is no need to flash the updated version if you are currently successfully rooted (you'll have gotten the latest SuperSU from Google Play updates already).
Click to expand...
Click to collapse
Thanks for your support to our device.
Sent from my SGH-T999 using xda premium

Thanks!
This worked perfectly, thank you so much. Since this was a free app and I bought the SuperSU Pro version to say thanks

Root in under a minute, why is this not pinned?? I was having some issues with WiFi calling so I ODIN'd back to ICS and it resolved them. Did the OTA update to JB from Tmo's servers but was missing root horribly. Can't believe how easy it was.

Thank You Chainfire
scrim said:
This worked perfectly, thank you so much. Since this was a free app and I bought the SuperSU Pro version to say thanks
Click to expand...
Click to collapse
Ditto on the Thank You,
I got the older version of Root and bought the Odin Pro for a thank you to Chainfire!
As we all KNOW, Chainfire Rocks! Props to him man, Major Props!
Aloha from Hawaii

Just used on the Stock Canadian JB update and as everything else chainfire does worked perfectly. Absolutely amazing work, I have tried to buy the pro version of all your software is that better then directly donating?
You rock, saved me a massive headache rooting 3 guys at work phones!

Chainfire Always comes through with the best gear. Everytime I need something from Chainfire, I always buy it. My way of saying thanks.
R2142

Rooted my S3 in about 27 seconds from start to finish. Wow, pretty simple.
Now what I'm understanding is you guys are suggesting NOT to install a CWM or TWRP recovery? and just flash the roms from Odin?
---------- Post added at 10:51 PM ---------- Previous post was at 10:07 PM ----------
Sorry quick question: I know you don't support custom recovery modes like CMW and TWRP, and I notice CF AUTO ROOT flashes stock recovery... so as a noob, am I to understand that correctly, if I were to install TWRP (for example) and decide its not for me or simply want to go back to stock recovery, I could simple re-run CF AUTO ROOT? and it would re-write the stock recovery mode?

Should Auto Reboot be checked in Odin? Its checked by default and it is not mentioned to uncheck it unless one runs into problems.
Sent from my SGH-T999 using xda premium

Chainfire said:
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
- NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
You may now optionally want to install and run Triangle Away to reset the flash counter.
Click to expand...
Click to collapse
Thank you Chainfire
Sent from my SGH-T999 using xda premium

LoopDoGG79 said:
Should Auto Reboot be checked in Odin? Its checked by default and it is not mentioned to uncheck it unless one runs into problems.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Did you end up leaving it or unchecking it?

ticojpunk said:
Did you end up leaving it or unchecking it?
Click to expand...
Click to collapse
I left it. Strange though, I used the provided odin and those options were greyed out, and auto reboot was checked. It was really straight forward. It was so well made, I was compelled to help out chainfire and bought triangle away.
Sent from my SGH-T999 using xda premium

Just used this method to root a brand new T999. Fresh out of the box I did the OTA update to Jellybean, checked it out for a few hours as-is, then just rooted it now. I have Titanium Backup installed and I'm already freezing bloatware. Thanks so much for this method! Worked fantastic. Chainfire rules, but you all know that already.

Does this work on the latest 4.1.1 jb os?
Sent from my Nexus 4 using xda app-developers app

[Q] Recovery doesn't work or not installed?

I'm not sure why but my recovery mode doesn't work, it just show me a little Android with a red signal and no one letter...
My phone is already rooted but I dont remember if I installed a recovery mode or if it was part of the root process, I need to install a "sound fix" zip, but I can't right now...any ideas??? Can I fix it without lose my data?

I think you don't have a custom recovery yet... Flash one and good to go.
Sent from Google Nexus 4 @ crSimple

Yes, you can install or flash and update recovery without losing data.
If proper USB drivers are installed and you can use ADB with the GNexus while is in developer mode, then you are ready.
Download latest CWM Recovery or TWRP Recovery.
Reboot the phone to bootloader mode. If your ROM has it in power option, you can use that to boot into bootloader.
Otherwise with adb: adb reboot-bootloader
On your computer, put above the recovery .img file in same folder as adb and fastboot executables.
then: fastboot flash recovery name-of-recovery-file.img
You will get an OK, success confirmation if all done properly. Now you can boot to recovery. Done.

Is there a simpler way? I'm not very "acquainted" with ADB :/, something more, ADB for X64 is about 480mb! Is that normal or Am I downloading another thing???

Jerber said:
Is there a simpler way? I'm not very "acquainted" with ADB :/, something more, ADB for X64 is about 480mb! Is that normal or Am I downloading another thing???
Click to expand...
Click to collapse
If you have never used ADB tools or ever attempted bootloader commands, it is probably not recommended for you to change stuff around because there may be a chance something can go wrong and you might not have immediate help to restore your phone. Doing these changes are permanent to your phone, so just keep that in mind if you still want to attempt it (eg you don't know how to return it to stock yet).
Personally, I don't recommend all-in-one tools because of the same reason as above, you don't learn anything if you need to do something command related or mess up.
It sounds like your phone is still bootloader locked to stock version of android but you may have have used SuperSU or some root exploit to get root previously.
All you need are 4 things:
Read and understand the guide @efrant posted for newbies: http://forum.xda-developers.com/showthread.php?t=1812959
Universal Naked Driver
ADB lite - ADB with less stuff, around 2MB
CWM or TWRP recovery img file (previous post)
When you think you are ready just post back.

kaijura said:
If you have never used ADB tools or ever attempted bootloader commands, it is probably not recommended for you to change stuff around because there may be a chance something can go wrong and you might not have immediate help to restore your phone. Doing these changes are permanent to your phone, so just keep that in mind if you still want to attempt it (eg you don't know how to return it to stock yet).
Personally, I don't recommend all-in-one tools because of the same reason as above, you don't learn anything if you need to do something command related or mess up.
It sounds like your phone is still bootloader locked to stock version of android but you may have have used SuperSU or some root exploit to get root previously.
All you need are 4 things:
Read and understand the guide @efrant posted for newbies: http://forum.xda-developers.com/showthread.php?t=1812959
Universal Naked Driver
ADB lite - ADB with less stuff, around 2MB
CWM or TWRP recovery img file (previous post)
When you think you are ready just post back.
Click to expand...
Click to collapse
Thanks, I'm gonna read it now!
My GN is on 4.3, with bootloader unlocked and rooted (of course) my intention with CWM is install a soundfix cuz GN has a VERY low sound and I'm missing some calls and sms all time :/
I used to have a Xperia device and I remember that root process and the installation of CWM are very easy in comparison with my GN, I thought it will be easy too.

Jerber said:
Thanks, I'm gonna read it now!
My GN is on 4.3, with bootloader unlocked and rooted (of course) my intention with CWM is install a soundfix cuz GN has a VERY low sound and I'm missing some calls and sms all time :/
I used to have a Xperia device and I remember that root process and the installation of CWM are very easy in comparison with my GN, I thought it will be easy too.
Click to expand...
Click to collapse
Should be simple for you from what is mentioned above.
After installing the drivers and adb, phone connected via usb, Steps 1-3
1. Set your phone to bootloader mode. 2 ways to do it:
A. Turn phone off, VOL+ and - and power button at same time until you see it.
B. Using PC: after adb is installed, use command terminal and go to folder it is installed in and type adb reboot-bootloader
2. In bootloader mode, flash the CWM recovery.
With your recovery .img file located in the same folder as adb and fastboot executables: in the terminal type fastboot flash recovery recovery-clockwork-6.0.4.3-maguro.img (or the toro or toroplus with the CWM image depending on your Galaxy Nexus type).
3. Boot to recovery.
Hit Vol button a few times until you see recovery on the screen while in bootloader mode, press power button to continue.
Don't forget to make a backup of stuff, including your EFS/radio folder.

Try this www.youtube.com/watch?v=foLQCNxroHw&app=desktop&persist_app=1&hl=en-GB&guid=&client=mv-google&gl=RO it's a complete guide but it's for nexus 10. Same thing with the gnex

Thanks a lot guys! I will try to do it!, something more
*I saw another option but I'm not sure if it work with the GN, some people say that a easy way is just download the app "Rom manager" from the Play Store and install the CWM from the app, what do you think about it?
*I have some little problems with stock 4.3 (for example, my bluetooth is useless :S), Do you recommend me switch to a stable CM rom (like the last official 10.2.0)?
Im not hurry for 4.4 or CM11, but I'm not sure if 10.2.0 has some bugs, anyways seems like a better option than the stock 4.3.

[Q] Restore to Stock and Root Methods

Hi everyone.
I recently got a used Note 2. I've been doing a bit of reading in this section and just wanted to confirm a couple of things.
First off my phone's description:
Carrier: Sprint
Model Number: SPH-L900
Android Version: 4.3
Baseband Version: L900VPUBMK4
Kernel Version: 3.0.31-2106854 [email protected] #1 Mon Nov 11 20:33:03 KST 2013
Build Number: JSS15J.L900VPUBMK4
SE for Android Status: Enforcing SEPF_SPH-L900_4.3_0010
Hardware Version: L900.09
(1) Even though the phone came wiped of all previous data I would like to do a factory reset. Billard412's guide is mentioned several times. Is this the option to go with for my phone?
(2) The phone is not rooted at the moment. Should I use the CF-Auto Root method by Chainfire first and then proceed to install TWRP and then restore back to stock using Billard412's guide?
Thanks for your help in advance.

To start with you have the 100% KNOX on your phone so Billard412's back to stock will be the option you want to use.
You will need to download
TWRP recovery (recommended because billards zip works best with it)
Billards back to stock mc2 with counter reset
The root file located in billards thread
Prep steps
Backup everything you want from your internal sdcard (this will get wiped)
place billards rom and root files on your external sdcard
1. boot phone into download mode
2. use odin to flash twrp recovery (any version but 2.7) make sure you uncheck the reboot option in odin
3. once finished remove cable and battery
4. hold the recovery boot key sequence (vol up, home, and power keys) then insert battery (while holding keys)
5. once in recovery wipe everything
6. flash billards rom (do not wipe anything else after this step)
7. flash the root file
8. reboot and dont get worry when things get funky this is normal
9. the phone will take a bit to boot
10. now you have stock mc2 with root
11. install your recovery of choice (if flashing touchwiz 4.3 or aosp 4.4 roms use Philz 6.07.9) this can be done with odin or an image flashing app
12. now you can flash whatever rom you want
FYI -- when going from touchwiz 4.1x to 4.3 or aosp 4.4 you should format your internal sdcard. The newer roms use a different location for your internal sdcard and without proper formatting you will end up with issues (mostly random reboots and apps force closing) -- Same goes if you go from 4.3 TW/aosp 4.4 to 4.1x TW/4.3 or lower aosp

jlmancuso, thanks for the reply. Couple of things to clarify from your post:
- Regarding the Prep steps.
- I don't have anything on this phone yet so I don't think I need to back anything up. Even if if did the "Android system recovery <3e>" recovery menu does not have an option to back anything up
- Regarding using Odin to flash TWRP
- The 2.7 version to avoid is for TWRP correct? I went to TWRP's Sprint Note 2 page and I cannot seem to find a different version. Where should I get the version of TWRP that actually works?
- From the XDA page on Odin, which version should I use 3.09 or 1.85?
- All of the boxes must be unchecked including the reboot option? If not which ones need to be checked?
- I click on the "PDA" button to load the TWRP zip file correct?
- Regarding step 8:
- What do you mean "dont get worry when things get funky"? Funky as in the phone takes long to reboot or the screen flashes weird colors/patterns?
- Also, I came across Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread. That one seems pretty easy to follow through. Would that option work for me given that I have the KNOX update?
Thanks again for your help.

Well, I've done a bit more reading into the Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread and it seems that might be the way to go. Mark mentions the KNOX update in his changelog. I don't have the necessary posts to post a question in that thread so hopefully someone sees this that's familiar with that method. Does this method apply to a phone that has already undergone the KNOX update?
From what I can understand, Mark has made a recovery as well as a root tool. I bought this phone second hand so any warranty issues (e.g. flash counts, etc.) don't really apply to me. I'm just looking to get the phone to a clean state where I can start fresh and then add TWRP and Root. As far as the version of TWRP, Billard412 says (in post #604) that "Version of twrp doesn't matter as far as I know."
My second question is, using the Unified Toolkit, will i be able to restore my phone to stock and then root it with the least amount of problems?

roofus1218 said:
Well, I've done a bit more reading into the Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread and it seems that might be the way to go. Mark mentions the KNOX update in his changelog. I don't have the necessary posts to post a question in that thread so hopefully someone sees this that's familiar with that method. Does this method apply to a phone that has already undergone the KNOX update?
From what I can understand, Mark has made a recovery as well as a root tool. I bought this phone second hand so any warranty issues (e.g. flash counts, etc.) don't really apply to me. I'm just looking to get the phone to a clean state where I can start fresh and then add TWRP and Root. As far as the version of TWRP, Billard412 says (in post #604) that "Version of twrp doesn't matter as far as I know."
My second question is, using the Unified Toolkit, will i be able to restore my phone to stock and then root it with the least amount of problems?
Click to expand...
Click to collapse
I belive your best option is billard412s thread. You are correct with your Odin steps. Flash TWRP and follow thread you should be golden

Awesome thanks a bunch!

Root & bootloader unlock.

-=Disclaimer I am not responsible for any bricking or you using these applications on the wrong devices=-
This tutorial is made for E980 AT&T, using this on other devices mayhave undesirable results
G PRO KitKat Recovery Works on 4.1.2 kitkat and 4.4.2 KitKat
Okay so as most of you know, twrp is buggy and doesn't work on some E980 AT&T phones, so I recently found a on phone application to unlock bootloader and install a CWM based recovery. You don't need to use towel root but I made this a two in one.
Part 1 - Instructions for towel root
Make sure you have unknown sources on
1. Open settings
2. Go to General
3. Under Personal find Security and open that section
4. Find Phone Administration
5. If unknown sources isn't on, turn it on
Installing Towel Root And Using It To Root
1. Download the tr.apk from the attached files or towelroot.com
2. Navigate to the downloads folder
3. Find the tr.apk file then hit it once
3.5. Hit install - if it doesn't open up the menu when you hit it the first time
4. Hit install again
5. The application should be installed hit open.
6. Hit the "make it ra1n" button - If your phone reboots the root process failed.
7. If your phone didn't reboot, Congrats! You're now rooted.
8. Download SU from https://play.google.com/store/apps/details?id=eu.chainfire.supersu to manage root permissions
9. Install the new binaries than reboot.
9. Move onto the next Part
\\If it fails I am not aware of fixes as I never had to fix them nor do I know of any when installing them :crying:
Part 2 - Instructions for G PRO Recovery
1. Download GPRO_Recovery_6.0.4.4.apk
2. Install it - use steps 2-5 from "Installing Towel Root And Using It To Root"
3. Hit "Flash Kitkat recovery for G PRO"
4. You should get the following alert : "Recovery has been flashed completed, please reboot recovery" In other words it succeeded if you got that message if you didn't get this message re-read the steps and see what you did wrong. Reboot recovery from that app to test your recovery.
Enjoy your Optimus G Pro rooted with a recovery! :laugh:
If you have any questions unrelated to this, feel free to PM me, I will do my best to answer if I know a solution .
Confirmed working on
Towel Root seems to work on kernals from : < June 2 2014
Using the G Pro recovery installer to my knowledge only works on E980 models.
Credits
koush -clockworkmod- for the ClockworkMod Recovery
GeoHot for making towel root
hoangnova for G PRO Recovery
Conclusion
Did I miss anything? let me know below. I am still new to xda so if I'm doing anything wrong or if I'm posting in the wrong place tell me or Mods move me to the right area

Thanks alot for sharing.

You can also root your E980 with ioroot or roottool both confirmed working. Roottool is preferred, it installs busybox and su. BLURP!

You are a lifesaver! I thought I was doomed having waited to long to root/unlock. I used the old roottool and that worked fine on my updated 4.4.2 install but freegee and all of the old unlocks were not working. This worked like a champ on the latest "20i" software. Thanks!

p4cket said:
You are a lifesaver! I thought I was doomed having waited to long to root/unlock. I used the old roottool and that worked fine on my updated 4.4.2 install but freegee and all of the old unlocks were not working. This worked like a champ on the latest "20i" software. Thanks!
Click to expand...
Click to collapse
@p4cket no problem Amigo! There is a Thanks button at the end of each post though.
Hey, Im currently running 20i also and its a pain in the a** to initially install recovery.
But, what you want to use is the GPRO_recovery_6.0.4.4 then Freegee to lokify the bootloader
then you can flash TWRP or Philz recovery. Like I said it's a royal pain in the A** but it can be done.

Thank you TnT.