[GUIDE] Root Your EVO 3D: a step-by-step for the average user [v2.1][UPDATING NOW]

[GUIDE] Root Your EVO 3D: a step-by-step for the average user [v2.1][UPDATING NOW] - HTC EVO 3D

** I've been away for some personal health issues. Please excuse my absence, back in action now. **
** in association with **
** presents... **
Root Your EVO 3D
a step-by-step for the average user
[v2.1 08/07/11 12:33 AM]
** READ FIRST **
INTRODUCTION AND DISCLAIMER:
DO NOT POST IN THIS THREAD UNTIL YOU HAVE READ EVERY WORD OF THE GUIDE AND AT LEAST THE LAST FIVE PAGES OF REPLIES. DO NOT EXPECT HELP IF YOU DON'T READ THE THREAD. YOU WILL BE IGNORED.
** Let me start of by saying I did not program, edit, modify or contribute to the files collected here. I made this thread to be a TRUE step by step for everybody, of all skill levels, and the directions need to be followed closely to avoid confusion. There's a lot of work to be done, but it's coming along. !!BEFORE YOU EVEN THINK ABOUT DOING ANYTHING, READ THE WHOLE GUIDE!! If, at the end, you feel like you might not be able to do it, don't. A more user friendly version of the exploit will come soon, I'm sure. And you can read about how to use it here when it does **
** Stuck? Confused? Check the Troubleshooting and FAQ section. Still need help? !!BEFORE YOU POST AN ISSUE, BE SURE YOU READ EVERY WORD OF THE TUTORIAL!! And it doesn't help to check the last few pages before you. A lot of common problems have already been addressed in detail. **
TABLE OF CONTENTS:
1: BACKUP YOUR APPS/SETTINGS AND CLEAN UP TEMP ROOT
2: OBTAIN AND WRITE DOWN YOUR SPRINT ID SETTINGS
3: INSTALL THE REVOLUTIONARY DRIVER PACK AND ANDROID SDK
4: GET YOUR PHONE CONNECTED AND READY TO FLASH
5: APPLY S-OFF, WRITE RECOVERY IMAGE, AND FLASH ROOT ZIP
6: AFTER THE DUST CLEARS
7: TROUBLESHOOTING AND FAQ
8: THANKS AND SOURCES
99: MIRRORS AND OTHER USEFUL LINKS
Click to expand...
Click to collapse
CHANGELOG:
v2.1 08/07/11 12:33 AM
Put off doing useful things to edit the disclaimer.
Changelog Archive
Click to expand...
Click to collapse
Let's get started!
1: BACKUP YOUR APPS/SETTINGS AND CLEAN UP TEMP ROOT
Temp-root your phone, install Titanium Backup (if you don't already have it), back up EVERYTHING. This isn't the thread for a tutorial on that, though I will answer PMs as best I can on the subject. A solid, reliable temp-root solution by eugene373 can be found here. Titanium Backup's official site can be found here. It has QR codes for both the free and donate versions and a link to its wiki if you don't know how to use it.
** DO NOT SKIP THIS STEP! To clear any traces of temp root and ensure your phone is ready for the next steps, go to Menu>Setting>SD & phone storage>Factory data reset. Your phone will reboot, clean and almost ready to go. When your device reboots, press cancel on any updates or anything, hit skip skip skip on the HTC Setup Wizard til you get to homescreen. Ensure USB Debugging is enabled on your phone! Factory reset will disable this! **
2: OBTAIN AND WRITE DOWN YOUR SPRINT ID SETTINGS
Dial ##3282# and look under profile for an @sprintpcs.com email address. Write it down. When you're finished if you are unable to update your profile, go back in to the same menu under Edit and replace the email address. After a reboot and a profile update your data should be working again.
3: INSTALL THE REVOLUTIONARY DRIVER PACK AND ANDROID SDK
First, download the android SDK from here. Install the SDK for your OS. Should be pretty easy, and link provided will always be the latest SDK. Then you need to download the driver pack from the unrevoked documentation page here. I've provided a mirror here.
** Make sure your phone IS NOT plugged in to the computer. If you have HTC Sync installed on your computer, before you proceed you should uninstall it completely, as it interferes with some other applications and has little use (at least to me). If you use HTC Sync and want to keep it installed for whatever reason you can right click and exit it from the taskbar, or ctrl+alt+delete to bring up the task manager and force the program to close. Uninstalling is your best bet. Then you can proceed with installing the revolutionary driver pack. **
Just double click the .exe and continue from there. The driver should install fine as long as your phone is not plugged in and HTC Sync is removed (preferred) or disabled. When you plug your phone in now, Windows should ask where you want to install the drivers from. Select install drivers automatically and let it finish all drivers.
4: GET YOUR PHONE CONNECTED AND READY TO FLASH
Extract the revolutionary exploit zip, which can be downloaded here by clicking on your OS name. Extract the zip file. Leave this page open. It should be expecting a serial number. We'll be back later. Download this mirror of the TWRP 1.0.2 image and rename it to "PG86IMG.zip" (without the quotes). Place this on the root of your SD card. The source is this thread.
Take a deep breath, get ready!
5: APPLY S-OFF, WRITE RECOVERY IMAGE, AND FLASH ROOT ZIP
1: Apply S-Off: Double click the revolutionary.exe file. It will start the script to apply S-Off. You will need the beta key from the website we left open earlier. The serial number is labeled S/N and starts usually with HT. It can found under the battery, labeled S/N, usually starting with HT) or on the outer sleeve of your EVO 3D box, on a sticker. Go back to the site and put your serial number in and click generate key. In the command prompt opened by the revolutionary file, type or paste your key when asked for it. Type y to continue when prompted. The script will run and apply the exploit. Give it time and be patient, just let it do it's thing. Your phone should reboot one or three times. When all is said and done, you can pat yourself on the back. You now have S-Off. You will end up back at the fastboot screen. At the top it should now say Revolutionary, and beneath that should be S-OFF. If all appears sound so far, it's time to update your recovery partition.
2: Write recovery image: Turn your phone off, take your battery out for ten seconds, then turn it back on while holding volume down. This will take you to your HBOOT menu. Select update PG86IMG.zip, then follow the prompts til it starts to flash. After the flash is complete you MUST delete the zip from your SD card. Now you have a custom recovery menu.
** Before you continue, select RECOVERY from the fastboot menu using the volume up/down and power keys. Your phone should reboot and show the recovery menu. Select Toggle USB and press the power button. On your computer, delete the recovery image. On your phone, remain mounted. **
3: Flash root zip: Download the superuser file from this mirror. Put it on your phones SD card. Press power to unmount, select Apply update from zip and press power. Select Choose zip from SD card and press power. Find the superuser zip and press the power button. After the zip is applied you will be returned to the previous menu. Select Reboot System and wait for your phone to boot back up.
6: AFTER THE DUST CLEARS
You now have S-Off, root access and a custom recovery menu. When your phone reboots, it will do a PRL update. This is normal, let it proceed. It will likely attempt a Software update as well, but thanks to the exploit the update should fail on its own. Sign back in to your Google account, reinstall Titanium Backup if you used it earlier, restore your apps and data with it, and continue on with your happily rooted life.
7: TROUBLESHOOTING AND FAQ
** If your issue isn't covered here yet, check the replies to the thread. They contain much wisdom **
Q: I lost my Sprint ID!! AND I lost the paper I wrote it down on!!!
A: If, somehow, you lose this information, Sprint Customer Service can be reached at *2 or 888-211-4727 from your Sprint phone.
Q: I get an error saying my superuser package isn't signer properly!!!
A: Some people were having issues with the mirror I originally provided and the superuser from goo-inside.me. The guide has been updated and is now correct, download from my mirror here and try again.
Q: I'm stuck on "Acquiring Root (Method 3)"!
A: Remove "HTC sync" and "HTC driver Install" from Control Panel\Programs\Programs and Features. Verify that the driver is removed by plugging in the phone (install should fail). If it does not fail, unplug the phone and browse to C:\windows\system32\drivers\ANDROIDUSB.sys and delete this file.
Reinstall HTCDriver3.0.0.007.exe, then run Revolutionary.exe again
Q: My phone won't call or text or anything anymore! I get an 'error 16'!!!
A: Did you perform the factory reset? Make sure you followed the directions to a tee. If this happens to you, keep trying to place a call. You'll be connected to Sprint and they'll fix you right up. This should take no more than a few minutes, just tell em you encountered an error 16.
8: THANKS AND SOURCES
Thanks for help with guide, moral support, or offering support in this thread: xHaus, housry23, TrevE, the_scotsman, imadork8317, Myn, LiquidSolstice (got more, not done...)
Special thanks: All the devs and skilled members here who tirelessly fought to the end to root our devices. Collaboration is necessary for a community to survive. TeamWin for their awesome recovery menu, and for making it easy to use and install.
Sources: The source of this exploit is a collaboration between unrevoked and AlphaRev. So just thank them and be sure to give them your feedback. They made this for YOU, and worked hard to keep it a secret from HTC, and to package it in a convenient way.
99: MIRRORS AND OTHER USEFUL LINKS
Revolutionary 0.3pre7 Beta: http://revolutionary.io
HTC Drivers: MIRROR | http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
** Other drivers you may already have installed could work, but this is straight from the Revolutionary documentation page. **
SU-2.3.6.3-efgh-signed.zip: MIRROR | http://goo-inside.me/superuser/su-2.3.6.3-efgh-signed.zip
** This is the Superuser zip that gives you root. The original file seems to be signed incorrectly. The guide links to my correctly signed mirror (provided below as well). I suggest using that over the original goo-inside.me file. **
TWRP 1.0.2: MIRROR | http://forum.xda-developers.com/showthread.php?t=1192077
** This link is to the TWRP thread. I'll try to keep this mirror updated with the newest version of the recovery project, but it wouldn't hurt to check out the thread for updates. Be sure to thank them while you're there! **

Will running factory data reset from the SD & phone storage settings option work instead of booting into fastboot?
Sorry for the noobish question...

I appreciate your guide, but I just plugged in my phone, ran the program, and installed the su zip through CWM recovery. I did make a phone call and got forwarded to CS but they did their thing and all is well.
I also have htc sync installed.

mattbiegner22 said:
Will running factory data reset from the SD & phone storage settings option work instead of booting into fastboot?
Sorry for the noobish question...
Click to expand...
Click to collapse
Yeah it should do the same thing but I just feel more secure being in the fastboot environment. Updating OP

phatmanxxl said:
I appreciate your guide, but I just plugged in my phone, ran the program, and installed the su zip through CWM recovery. I did make a phone call and got forwarded to CS but they did their thing and all is well.
Click to expand...
Click to collapse
If only I had got this up a little earlier lol I think it'd have helped more
EDIT: I might be assuming here but the wipe seems to be saving that little hassle of calling CS

If the root goes through correctly you shouldn't have to re install any app.
Sent from my Transformer TF101 using Tapatalk

Erm. What do we need to do in order to back up WiMax stuff?

LiquidSolstice said:
Erm. What do we need to do in order to back up WiMax stuff?
Click to expand...
Click to collapse
Navigate to settings/wireless and networks/4g settings and write everything there down lol
Silly, I know, but paper still has a use in this world.
EDIT: Clarified in OP

huh, WiMAX keys?
My WiMAX settings stayed intact (keys are something completely different ), but I did have to reenter my account name before I could update my data profile. Dial ##3283# and look under profile for a @sprintpcs.com email address, right it down. When you're finished if you are unable to update your profile go back in to the same menu under Edit and replace the email address. After a reboot and a profile update your data should be working again.

"EDIT: Would anybody like to see a comprehensive guide from absolute scratch to root? We already have a post detailing how to do this but it's not as in depth as people PMing me have needed."
YES, please... the more steps and detailed guide the better... THX!

xHausx said:
My WiMAX settings stayed intact (keys are something completely different ), but I did have to reenter my account name before I could update my data profile. Dial ##3283# and look under profile for a @sprintpcs.com email address, right it down. When you're finished if you are unable to update your profile go back in to the same menu under Edit and replace the email address. After a reboot and a profile update your data should be working again.
Click to expand...
Click to collapse
Added to OP, thanks xHaus

Bentenrai said:
Navigate to settings/wireless and networks/4g settings and write everything there down lol
Silly, I know, but paper still has a use in this world.
EDIT: Clarified in OP
Click to expand...
Click to collapse
Uh. That's not going to help you with your WiMax stuff whatsoever. What you want to backup is the WiMax partition when using CWM or TWRP.
Knowing your IP Address from the 4G section of the settings will not help you at all.

MILH0U5E said:
"EDIT: Would anybody like to see a comprehensive guide from absolute scratch to root? We already have a post detailing how to do this but it's not as in depth as people PMing me have needed."
YES, please... the more steps and detailed guide the better... THX!
Click to expand...
Click to collapse
I'll be updating all night!

ok im not a noob but right now i am i havent found out or have i seen ne one ask how to check what version of hboot u r and how the heck to get this serial

When you say uninstall HTC sync do you mean from the phone or computer?
Sent from my PG86100 using Tapatalk

Anon9mouz said:
ok im not a noob but right now i am i havent found out or have i seen ne one ask how to check what version of hboot u r and how the heck to get this serial
Click to expand...
Click to collapse
pull/reinsert battery, hold volume down button, press and hold power, phone will come on
when it boots to the white screen look at the top, and you'll see the hboot#
Serial, either run the revolution exe and it will tell you what it is if it finds your phone, or look behind the battery

Anon9mouz said:
ok im not a noob but right now i am i havent found out or have i seen ne one ask how to check what version of hboot u r and how the heck to get this serial
Click to expand...
Click to collapse
Serial # can be found behind the battery.
Hboot version can be found on the hboot by powering the phone off and then.powering back on by holding the volume button down and power at the same time.
Edit I was beat!
Sent from my PG86100 using XDA App

Bentenrai said:
Added to OP, thanks xHaus
Click to expand...
Click to collapse
Its ##3282# ##3283 doesn't pull anything up.

wrapkgb said:
Serial # can be found behind the battery.
Hboot version can be found on the hboot by powering the phone off and then.powering back on by holding the volume button down and power at the same time.
Edit I was beat!
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
hey well the serial be on the box bc im all otterboxed up and i would hate to take this ***** off bc otterbox sucks and the corners is starting to bow out

spookytay said:
pull/reinsert battery, hold volume down button, press and hold power, phone will come on
when it boots to the white screen look at the top, and you'll see the hboot#
Serial, either run the revolution exe and it will tell you what it is if it finds your phone, or look behind the battery
Click to expand...
Click to collapse
Thanks, thread's moving fast and I'm working on the tutorial so I can definitely help answering questions soon, just filling out the guide now.
jes24cap said:
When you say uninstall HTC sync do you mean from the phone or computer?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Computer
Sorry, struggling to keep up with OP, new info and PMs. Keep em comin, i love it!

Related

[INFO] From the MT3GS Forum: method SHOULD ROOT THE N1 W/O TOUCHING THE BOOTLOADER

Its been done on the Incredible and Evo, now the Slide. This SHOULD BE IT. Here is their post with exact method. Adjust for the N1 and test on an unrooted phone. ASAP. This should be it!!!!!
QUOTED FORM EUGENE373 @ MT3GS FORUM:
Originally Posted by brokensanity
How-TO Root the Slide
First!! - Go to Settings > Application > Development and turn on USB Debugging. This should save you headaches.
NOW… Power Off the Slide
Download This Package > Slide Root.zip
kingofyo1's Video How-to > http://www.youtube.com/watch?v=sVjoKvy-YZg
Step 1.
Place the Contents of "Slide Root.zip" into your Android SDK Tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK/Tools Directory.
Step 3.
Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button )
Step 4.
Now run your loop file from the prompt (either type "loop" in windows or "./loop.sh" in a *nix like)
Step 5.
Once your loop is running in your prompt, select Recovery from the bootloader menu.
Step 6.
When recovery loads, you should Have an Offline Device. You can use ctrl+c to stop your script & see.
If this doesn't happen, Power Off and try again..
Step 7.
Un-plug your USB cable from the back of your phone & Plug it back in for it to Detect ADB Correctly!!! This is an important step. At this point you can adb devices to see if you can see your device and that it is in recovery mode.
Step 8.
Select Update.zip from the menu. (This will fail, but we already know that! Select it anyway).
Step 9.
adb push ota.zip /sdcard/update.zip (*nixlike users add a ./ in front of all terminal commands please.)
Step 11.
adb push slideroot.zip
Step 12.
This is Very important!! Have this Command ready in your prompt before applying update.zip again!!
adb push update.zip /sdcard
step 13.
Hit run update.zip, as soon as you see a Little Bar appear under the text push Enter to execute the command in your prompt (adb push update.zip /sdcard )
Step 14.
In successful, you should see Clockwork Recovery. If unsuccessful, repeat steps 12 & 13.
Step 15.
Now, go to the Partitions menu and Mount System
step 16.
Go back one level & select install any zip from sdcard. Select slideroot.zip & apply update from zip (This will finish the Root process).
Step 17.
Reboot your phone & wait for it to load completely. To confirm that your slide is connected as a device use the command adb devices. If this works, you will see it as a device. Your prompt will say something like:
$ ./adb devices
List of devices attached
HT05YUP12710 device
Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root.
Congrats.
Special Thanks to:
Paul O'Brien:
Koushik K. Dutta:
&
The Guys using the Incredible OTA Spoofing Method

Why don't you test it out and let us know the results? ;-)

why do we care about the bootloader since both HTC and Google are ok with us unlocking it?

Im waitn for someone to try this out... hahaahah

b9nez said:
why do we care about the bootloader since both HTC and Google are ok with us unlocking it?
Click to expand...
Click to collapse
If people don't unlock the bootloader they get to keep their warranty

PhantomRampage said:
If people don't unlock the bootloader they get to keep their warranty
Click to expand...
Click to collapse
Most of the time, they'll replace our equipment. It's been done before, i'm witness to that.
I don't argue this would be a good idea but it's not THAT necessary. :\
Edit: only real upside i can see is getting rid of that annoying unlock icon but since i'm already unlocked there's no point.

This would be pretty good for people like me, who has an unrooted Nexus One

whorehay said:
This would be pretty good for people like me, who has an unrooted Nexus One
Click to expand...
Click to collapse
The key is that we need a DEV with an unlocked phone in hand. I can switch my purple-tinted screen out and get it over to a good one, but that could take a few weeks, anyone else have the tools ready?

I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?

Santoro said:
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Click to expand...
Click to collapse
If it is messing with just the image then im 99% sure yeah you can.

I have a mytouch slide also and this method works. Were having problems getting a recovery to stick on the phone though. I have no idea if this works on n1. Id try but my bootloaders already unlocked.

Santoro said:
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Click to expand...
Click to collapse
I can say that it wont hurt the phone. I tried a process similar to this before I had the details with one of the better known devs from XDA this weekend for a few hours. Even though we couldn't get the timing right, at the end of the day, I still had my original Rom, and it haven't even been hit with a recovery.

i have exchanged my N1 with an unlocked bootloader without any issues. and many other people have as well. if its a hardware issue they will ALWAYS honor warranty. if your phone is bricked by something you flashed they won't honor that

FishFan319 said:
I can say that it wont hurt the phone. I tried a process similar to this before I had the details with one of the better known devs from XDA this weekend for a few hours. Even though we couldn't get the timing right, at the end of the day, I still had my original Rom, and it haven't even been hit with a recovery.
Click to expand...
Click to collapse
So I know just enough to be dangerous. I need to understand a little more before I try this on my N1.
This slide_root.zip, are it's contents phone-specific? You said we should modify the process for the N1, are you saying that the contents of the file need modification? Or just the navigation around the recovery?
I am pretty leery until I understand what the slide_root file does and if it is compatible with my phone. Anyone know?
If I do it and it fails, does anyone have a link to how I would reinstall a stock image via USB?
edit: grammar

I developed a screen problem and had to pay to get it repaired because the bootloader was unlocked. Nothing to do with ROM or anything, a section accross the top of the screen went unresponsive to touch. So I know for a fact that they DON'T always honor warranty after unlock. I guess I must've gotten the a*hole operator/technician then for my call...

Jr33 said:
i have exchanged my N1 with an unlocked bootloader without any issues. and many other people have as well. if its a hardware issue they will ALWAYS honor warranty. if your phone is bricked by something you flashed they won't honor that
Click to expand...
Click to collapse
That really is a matter of interpretation by the tech you get at HTC. Based on the poster just above this, the warranty is not ALWAYS honored. Right?

Santoro said:
That really is a matter of interpretation by the tech you get at HTC. Based on the poster just above this, the warranty is not ALWAYS honored. Right?
Click to expand...
Click to collapse
right. I could not get mine repaired for the dusts under screen problem with unlocked bootloader.
I think most of them slipped through since they could swap in US

kaiser_tytnii said:
right. I could not get mine repaired for the dusts under screen problem with unlocked bootloader.
I think most of them slipped through since they could swap in US
Click to expand...
Click to collapse
I stupidly got mine etched. Had I thought about the fact that it would preclude me from getting cross-shipped warranty work, I'd have reconsidered.

I WISH I COULD TYPE IN ALL CAPS IN TITLES TOO...
Anyway....
I'm assuming the OP didnt intend for yet another thread to devolve into the warrantly debate.

bobtentpeg said:
I WISH I COULD TYPE IN ALL CAPS IN TITLES TOO...
Anyway....
I'm assuming the OP didnt intend for yet another thread to devolve into the warrantly debate.
Click to expand...
Click to collapse
yep, i agree. let's stop the warranty debate here.
i probably will find someone who has a unrooted phone to try it out

[GUIDE] Super-noob guide to unlocking, rooting, and flashing Ziggys kernel

This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
As of the time I'm writing this, there is no way to get the phone back to "Locked" once you've "Unlocked" it. The phone will show "Re-locked" if you relock it so know that until someone figures something out, Verizon WILL KNOW that you've unlocked your phone once you do it IF they bother to check and know how. It's your gamble, but to date, I've not heart of Verizon detecting root/unlock and refusing service to one person I can confirm. Said another way, you can "un-root" your phone (remove su and SuperUser), but that won't hide the more important fact that you've unlocked it. Consider this before continuing. Unlocking VOIDS YOUR WARRANTY. You accept responsibility for following this guide. Myself and other devs only provide information.
In general, here is what you will be doing:
Using the HTCDev.com site to submit your phones key and get an unlock.bin that you can use with fastboot to unlock your phone. NOTE: This WILL WIPE YOUR PHONE. I suggest using a temp-root method to first install Titanium or similar app, and do a app/data backup. This way when you're done, you can restore apps/data and be just about where you were when you started, only better.
Use the zergrush perm-root method to obtain permanent root and install SuperUser.
Install a customer recovery that will allow you to do a nandbackup and then install other roms/kernels (needed for the next step also).
Install Ziggys custom kernel which addresses some important issues for this phone and provides some other nice features.
NOTE: If you intend on flashing one of the newer ROMs ("newer" as of 2012-03-24) that require the 3.11.602.22 firmware, use Scott's directions HERE then come back and continue.
Now for the actual steps:
UNLOCKING - First visit THIS post for detailed instructions on how to unlock your device. This is required for permanent root and just about everything else following. This WILL VOID your warranty as the post says. This will also WIPE your device so again, I suggest first using THIS temp-root method so you can install an app like Titanium Backup to backup your apps/data.
PREPARING ADB - Once you have unlocked and your phone has rebooted, hit the home key to skip HTC Setup (no point doing it just yet really). Now hit, menu, settings, Applications, and check "Unknown Sources" (for good measure), then "Development" and check the box "USB debugging". I recommend then backing up a screen and un-checking "Start automatically", but that's my preference, not a requirement.
CONFIRMING ADB - At this point, I'm going to assume you already have ADB installed and known how to invoke the command because there are at least 9,999,999 tutorials online explaining this. Go ahead and open a cmd prompt and run "adb kill-server" and then "adb devices" and ensure that your device (if you see one, then you should be fine) shows up.
ROOTING - Now visit THIS thread and hit the less-than-obvious link titled "Download - OneClickRoot" to download the zip containing the tool. Follow the directions in that thread to permanently root your phone.
Boot fully into Android before proceeding.
RECOVERY
PREPARE RECOVERY.IMG - Visit THIS thread and download the attachment. Extract "recovery.img" from the zip and place it in a folder from which you can successfully run ADB. NOTE: If you haven't already, putting the adb.exe files folder in your PATH will let you run adb from anywhere. Same goes for fastboot. This makes life with Android tweaking/hacking MUCH easier.
FLASH RECOVERY 1/2 - Now "CD" into the folder (HERE you can find more about the CD command) with recovery.img and run the following command: "adb reboot bootloader". Once the phone has rebooted into the bootloader (a white screen with text menu, should say "*** UNLOCKED ***" at the top now). In white with a red background you should see "FASTBOOT USB". If so continue, if not, ask for help
FLASH RECOVERY 2/2 - The moment you run the following command, you should see a vertical bar on the upper-right hand corner of your phones screen. If so, it's working as expected. In your CMD window, run the following command "Now "CD" into the folder with recovery.img and run the following command: "fastboot flash recovery recovery.img"
REBOOT TO RECOVERY - If you have't touched the volume keys, "BOOTLOADER" is selected and pressing power will take you to the bootloader where you can then use the arrow keys to select "RECOVERY" and again press the power button to get into recovery. Otherwise, reboot any way you see fit and once running, use "ADB reboot recovery" to get into recovery easily.
KERNEL
DOWNLOAD FILES - First download the two files from THIS post (NOTE: The OP most may end up with more updated files, but as of the time I'm writing this, these are the way I suggest).
PUSH FILEs 1/2 - If you haven't already rebooted into recovery, review the previous steps and get your phone into recovery ("ADB reboot recovery" is my preference). Now "CD" into the folder containing the two files downloaded in the previous post. From here, I will use the file names as they were when I downloaded. Yours could be slightly different so adjust accordingly. In the recovery use the volume keys to navigate to the "Mounts" menu and then "Mount /sdcard". Use the Power button each time to select the menu option.
PUSH FILEs 2/2 - Now from your CMD window (the one in the folder containing the two kernel files), run the following commands: "adb push FlashMeInRecovery.zip /sdcard/" and then "adb push PH98IMGZIGGYUNSIGNED.zip /sdcard/PH98IMG.zip".
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 2/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
If you get the notorious "MainVer Error", use one of the following guides to get past the error. NOTE: Neither of these are for the faint-of-heart and the first I consider easier, does carry some real danger if done incorrectly.
Option 1 - Follow the guide HERE <-- Requires the use of a HexEditor and one is recommended if you don't have a preferred one yet.
Option 2 - Follow the guide HERE <-- Requires modification of the PH98IMG.zip you're trying to flash and sometimes this can be problematic. Either way, it provides an excellent description of why the error occurs.
FINISH - Once the 2nd kernel file is flashed and you're prompted, press power to reboot. After your phone is running again, use the following command to rename the kernel file so it doesn't cause you trouble later in the bootloader (but still keep it handy): "adb mv /sdcard/ext_sd/PH98IMG.zip /sdcard/ext_sd/PH98IMGZIGGYUNSIGNED.zip"
If this guide has helped you and you want to show thanks, just hit the "Thanks" button at the bottom of this post. It's not a donation or anything like that, just a counter used here on XDA
I will try to keep this post refreshed as newer files become available, as things get easier, or things change. If you see an error/typo/concern with these directions, PLEASE PM me and don't muddy up the thread. If YOU will do this, "I" will not only try to maintain the post, but I will also try to add/maintain an FAQ post as needed.
Btw, in case you recognize me and are wondering why I've posted here, it's because my site is dead due to childish drama, I still want to help the community and this seems the most reasonable way to do so for now.
EDITS:
20111230_1804 - Added a hint and link about the "CD" command for users who aren't familiar with "DOS" like commands.
20120101_1923 - Added a direction to boot into Android after rooting.
20120101_2325 - Added warning about unlock/relock and warranty in BIG RED text.
20120208_1709 - Added instructions on how to handle the "MainVer" error.
20120324_1636 - Added note about using 3.11.602.22 based ROMs and linked to Scott's (CleanROM) directions.

Great guide, thanks! Worked just fine and wow this thing is fast as BALLS
Using SetCPU to tweak and monitor, any clue on what the best governor is for this kernel?
EDIT: Reading original post about kernel from Ziggy, "lagfree" governor is available, using that now.

Thanks!!!!!

may i flash kernels on custom rom
or has to be stock rooted?

qudwis said:
may i flash kernels on custom rom
or has to be stock rooted?
Click to expand...
Click to collapse
this kernel is based off of the one made for gingerbread, so as long as the ROM you're running is a Gingerbread ROM, you can, or should be able to use this kernel with it.
*EDIT* I believe it may matter whether the ROM is Sense or AOSP based as well. currently we only have sense roms so it doesnt much matter, but it will down the road.

one more question.
i have cwm for recovery. since cwm don't have developer menu,
do i need to change to Amon Ra recovery?
and if i do, how do i change?

The guide is clear, succinct, and accurate. Everything worked perfectly - thanks so much.

I could've got so much more work done over the last two days if I had a tutorial like this! Untold hours have been spent combing these boards to piece together this whole process. Thanks for taking the time to do this for everyone.

Seemed to work!
I only did the recovery / kernel part since I had done the rest previously. For some reason it partially wiped my phone storage and SD card. Directories are there, but nothing is in them. No idea what happened, but oh well.
At least now I can start messing with stuff.

How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett

bal1985 said:
How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett
Click to expand...
Click to collapse
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).

rainabba said:
This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 1/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
Click to expand...
Click to collapse
This looks very clear and helpful. I'm not ready to use it yet, still need to study up on all this root stuff but thanks for posting.
Just wanted to point out that there may be a small and not so important typo. Both flash files are 1/2, shouldn't the second one be 2/2?

I have downloaded both files into my sd card, flashmeinrecovery.zip worked fine. The pmhimg.zip keeps saying aborted. I am running cwm, should I be running a different rom? What can I do to get the pmh zip to work?
I downloaded them via the qr codes, and they are in the download folder on my sd card. I did change the name on the second zip.

You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound

pwned3 said:
You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?

Just reboot normally after flashing
sent from my cm7 rooted fire

And move the file. It will read it every time you go into the bootloader
sent from my cm7 rooted fire

Followed instructions and kernel would not flash. All steps completed without errors and still has same kernel. Any advice?

rainabba said:
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).
Click to expand...
Click to collapse
so I just unistall SU from the Market? Or do I have to go in with Root Explorer and delete the file? once that is done don't I have to lock the bootloader using that htcdev guide again?

remmy5r said:
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?
Click to expand...
Click to collapse
Following step 7 specifically prevents you from having to deal with that. So long as the PH file exists in your sdcard root, when you go into bootloader, you will be prompted. Once your running normally, just go follow step 7 and you'll be good to go.

A journey into the bowels of S-OFF - A guide for the professional semi-noob

I went through the S-OFF, etc process from scratch last weekend (soup to nuts from stock GB), and decided to share my notes.
There is no original information posted here, just a re-organized walkthrough to reference & accommodate what's already out there.
Hopefully a few find it helpful (I know I woulda )
Disclaimer:
this is a Windows-centric walkthrough, that assumes (in parts) that this isn't your first day at the rodeo. Never be scared to use Google or the IRC chat (sorry dsb9938 for the newb flood :laugh
This walkthrough is just an end to a means. You'll find people mention different ways they've accomplish the full process - this post is just a historical document on how I accomplished the same goal.
My methods were definitely successful, though my technique was admittedly ghetto at times. If any uber-pro's notice areas where this is the case, feel free to chime in & i'll update that chunk with credit to you.
I take no responsibility for anything you were inspired to do as a result of reading this post... unless it made you happy, I will take credit for that
The full process in a chronological nutshell:
HTC Unlock
Flash recovery
Root
Juopunutbear S-OFF
Flash latest firmware
Re-flash recovery
Flash ROM
Things to do beforehand:
disable fast boot // settings > power > uncheck
-- this is a universal truth throughout this process, if you have problems booting into the bootloader, check into this.
enable USB debugging - settings > applications > development > check USB debugging
-- this is another universal truth, if something isn't able to communicate with your device, check into this
verify your bootloader / system status
-- power down
-- hold down power & vol- at the same time while booting up
-- it should say Locked & S-ON at the top
backup SD card
backup anything on the internal storage that you care about
*Optional - wipe SD card
*Optional - install an MD5 checker (if you don't already have one)
-- Windows: http://download.cnet.com/MD5-Checker/3000-2092_4-10410639.html?tag=mncol;1
-- Android (for later): https://play.google.com/store/apps/details?id=com.fab.md5
BE PATIENT. seriously. I know you want to get back to MW3, but this can take a while. Your device will go through several lengthy processes. If something looks unresponsive and it starts to scare you, just wait it out for a few minutes before going willy nilly with the power button. At times, you will end up having to manually power on again, but give it time before getting antsy. If your ADD is driving you crazy, just bite your lip and power through it.
Steps 1, 2, & 3)
Unlock, Recovery, & Root:
go to htc dev
sign up / confirm from email / log in
install the stuff they tell you to, listed on the right of the page
Install / use the Rezound All-In-One Toolkit on your PC to accomplish the rest
for recovery, I chose Amon RA
The more you know ✩....
-- a dude doing recovery the manual way - http://youtu.be/AvSeLmXSjVI
-- the recovery is accessed through the bootloader menu
Step 4)
S-OFF:
Charge battery full
Make sure fast boot is still off
Make sure USB debugging is enabled
Download the latest juopunutbear for rezound here (Windows, Latest ICS)
*Optional - Verify the MD5
Follow juopunutbear instructions - here, then here
*Optional - Do a backup via recovery
The more you know ✩....
-- controlbear was randomly having a hard time seeing my device, I solved this by:
---- closing controlbear command prompt
---- toggling on HTC Sync as the USB connection type (on the rezound)
---- this caused the device to be recognized differently in windows & installed a driver
---- I started controlbear again, but it hung at "Searching for device"
---- I closed it & ran it again
---- then it worked
-- for the rooting part of this, when it boots you into recovery, check both SD card locations for SuperSU.zip
-- this process froze on me many times, closing and restarting controlbear seemed to fix it
---- seriously did this at least 10 times - it happened randomly at seemingly scary places. (each time getting me further than the last)
-- juopunutbear hboot? - I said yes
-- SD card issues? do a factory reset.
-- Still have SD card issues? you just need to update the firmware, move along.
-- USB debugging path has changed in ICS, you can enable it here: settings > developer options > check USB debugging
-- ATTENTION: Not getting any reception/ signal? put the case back on, broseph
more info:
-- S-off is Official!!! With Instructions...
-- S-OFF FAQ
Step 5)
Latest firmware:
Download the latest RUU (3.14.605.10 as of July 16) to update the firmware to ICS - http://bit.ly/KlRfKZ
-- *Optional - Verify MD5
Rename the RUU to "PH98IMG.zip"
Copy the renamed update to the root of your external SD Card.
Power down / reboot into bootloader / wait 5-10 minutes for it to finish
Step 6)
Fastboot flash recovery:
After s-off and firmware update, you need to re-flash recovery via fastboot, this process is described here -- # < anybody have a link? #
-- *Optional - Do a backup via recovery
The more you know ✩....
-- flashing recovery via fastboot is only necessary if you want to keep the top of the bootloader reading as "Locked" (even though it's already S-OFF'd).
-- I did not want this, (mine reads "Unlocked") so if you don't want that, then just re-unlock using the same method as you did the first time, and then re-flash recovery the same way again.
REPEAT: Not getting a reception/ signal? put the case back on.
Step 7)
ROM
Download ROM of your choice (I used Nils' Business ICS, Sense 4.0, v1.2)
-- *Optional - Verify MD5
Copy the zip to the root of your external SD Card.
Follow the ROM installation instructions (Wipe, etc) & install via recovery
-- *Optional - Do a backup via recovery
Hooray!
-- credit where it's due & thanks to all who came before me.

i came here because the title said BOWELS! 0.o

^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative

Wrote up a similar guide last week at TeamBAMF's site:
http://www.teambamf.net/topic/4122-generic-guide-to-root-and-install-roms-on-the-rezound/

AshtonTS said:
^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative
Click to expand...
Click to collapse
ha, might have been the reason controlbear failed so many times (still ended up working though).
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.

dustintheweb said:
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.
Click to expand...
Click to collapse
Yeah makes sense.

dustintheweb said:
ha, might have been the reason controlbear failed so many times (still ended up working though).
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.
Click to expand...
Click to collapse
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..

Divine_Madcat said:
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..
Click to expand...
Click to collapse
Just to add on to that, a noob who can't use adb and fastboot fully probably has no need for s-off

So no fast boot Ehhh?
I just checked, mine is on, so is that why my 8 hours of s-off attempts failed?
Sent from my ADR6425LVW using Tapatalk 2

Divine_Madcat said:
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..
Click to expand...
Click to collapse
meh, maybe i've just had good luck, but I've personally found over the years (and reiterated from others) that HTC phones are fairly hard to brick. I mean, yeah, people should read up on stuff and not be idiots when going down this road, but there's no reason to treat it as delicate of a process as some do.
I like to think of it more as training a dog, rather than walking on egg shells. Take your time, be patient, but don't forget to make it fun.
-- and if at any point you're unsure on how to do something, don't panic - just post your question in the forums or in the chat and be prepared to wait. Someone will help you eventually.

AshtonTS said:
^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative
Click to expand...
Click to collapse
First, this is exactly what I was looking for so thank you. I've read just about every post for unlocking and s-off, but I'm glad you put it all together!
Second, so step #5 should really be #4?
Third, flame me if you want, but I don't have the developer tools menu to enable USB debugging. Does that show after using unlocking via HTC dev?
Thanks again!

dustintheweb said:
meh, maybe i've just had good luck, but I've personally found over the years (and reiterated from others) that HTC phones are fairly hard to brick. I mean, yeah, people should read up on stuff and not be idiots when going down this road, but there's no reason to treat it as delicate of a process as some do.
I like to think of it more as training a dog, rather than walking on egg shells. Take your time, be patient, but don't forget to make it fun.
-- and if at any point you're unsure on how to do something, don't panic - just post your question in the forums or in the chat and be prepared to wait. Someone will help you eventually.
Click to expand...
Click to collapse
This is how it should be but not all people think like that most just wanna put people on blast
Sent from my ADR6400L using xda app-developers app

BSquaredB2 said:
Second, so step #5 should really be #4?
Click to expand...
Click to collapse
It worked for me, but AshtonTS says there is a better way. Search through the S-OFF FAQ thread (or similar) and see if you can get a consensus of what other people did.
BSquaredB2 said:
Third, flame me if you want, but I don't have the developer tools menu to enable USB debugging. Does that show after using unlocking via HTC dev?
Click to expand...
Click to collapse
If you're on GB, go to settings > applications > development > check USB debugging
Sorry about that, I had the ICS path in the guide (now fixed).

Noob questions regarding Hasoon2000's All-in-one toolkit and rooting/installing ICS

Before I get bashed for not posting in Hasoon2000's All-in-one toolkit thread (http://forum.xda-developers.com/showthread.php?t=1493905), I would just like to say that I just joined the forum and wasn't allowed to post in the thread for questions/problems. With that out of the way, I'll start by saying that I have a HTC Amaze 4G (T-Mobile USA) on android version 2.3.4 and software number 1.36.531.6, not rooted and completely stock.
Background info: The reason why I want to root is because for some odd reason my amaze didn't get receive the OTA ics update. I checked for it manually just about everyday and I also did not receive a notification for a new software update. I also contacted customer service and they were no help. I would just like to root my phone and install ICS for now and later in the future install a stable custom rom that has sense 4.0.
Questons:
1. Does the Amaze have to be connected to the PC before the start of the first step(Install HTC Drivers)? If so, what is the screen on the phone supposed to be on(Is the phone supposed to be turned off or on? Is it supposed to be in disc drive mode? bootloader? etc..)?
2. Which recovery should I use after my bootloader is unlocked? and also what is the phone supposed to be on (bootloader, regular screen, other)?
3. How do I install ICS after successfully rooting?
I apologize for the long post and noob questions. I had an iPhone before getting the htc amaze and jailbreaking/unlocking was very easy whereas this seems to be a bit more tricky. If there is a thorough and detailed STEP-BY-STEP tutorial anywhere else, please let me know.
Thank You!

Flipnfr3ak said:
First welcome..I use to be an iPhone user also...before even starting update to ics. It should be available ota. Yes it has to be connected to you pc make sure usb debugging is on. Hasoon has the instructions in his post. But you have to be in bootloader screen. Use 4ext for recovery. Then root....you should be good to go. Make sure you make a nandroid backup
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply! Every time I manually search for the OTA update, it says "There are no updates available for your phone.", so I unfortunately can't update it OTA. I'm very new to all of this, so I don't know the terminology for a lot of the things on the forum. How do I make sure usb debugging is on and also what is a nandroid backup? Also, am I supposed to be on the bootloader screen the entire time?

Kashif92k said:
Before I get bashed for not posting in Hasoon2000's All-in-one toolkit thread (http://forum.xda-developers.com/showthread.php?t=1493905), I would just like to say that I just joined the forum and wasn't allowed to post in the thread for questions/problems. With that out of the way, I'll start by saying that I have a HTC Amaze 4G (T-Mobile USA) on android version 2.3.4 and software number 1.36.531.6, not rooted and completely stock.
Background info: The reason why I want to root is because for some odd reason my amaze didn't get receive the OTA ics update. I checked for it manually just about everyday and I also did not receive a notification for a new software update. I also contacted customer service and they were no help. I would just like to root my phone and install ICS for now and later in the future install a stable custom rom that has sense 4.0.
Questons:
1. Does the Amaze have to be connected to the PC before the start of the first step(Install HTC Drivers)? If so, what is the screen on the phone supposed to be on(Is the phone supposed to be turned off or on? Is it supposed to be in disc drive mode? bootloader? etc..)?
2. Which recovery should I use after my bootloader is unlocked? and also what is the phone supposed to be on (bootloader, regular screen, other)?
3. How do I install ICS after successfully rooting?
I apologize for the long post and noob questions. I had an iPhone before getting the htc amaze and jailbreaking/unlocking was very easy whereas this seems to be a bit more tricky. If there is a thorough and detailed STEP-BY-STEP tutorial anywhere else, please let me know.
Thank You!
Click to expand...
Click to collapse
Not sure if this helps...but this is what I did. I originally posted it on T-mo forum. At the very least it will put you in the ballpark...good luck. Just trying to help. These other guys know a lot more than myself. I'm sure the community will get you through it.
"Re: Leaked ICS in the wild!
Okay. Got it. Long story short:
1. Download file onto PC http://www.filefactory.com/f/40bba0821a54f264/
2. Put file on SD card (I recomend different SD card.)
3. After it is on SD card, rename file "PH85IMG" *** No ".zip." ***
4. Power down phone
5. Remove/replace SD card
6. Remove battery
7. Replace battery
8. Power up the phone hold "power button and volume down" at the same time.
9. Hboot will appear...let go of buttons. the phone will then start reading the SD card. "Checking PH85IMG"
10. After that instructions will appear. At the bottom of the info you will see the prompt: "Do you want to start update?" Now Volume up for "Yes."
11. Once you volume up for yes it will begin checking the files. (After some time it updated a few files and the screen went black. I hit the power button and and it started updating all files.
In closing you "WILL" lose all info, contacts, text, email and any other setting on the phone. It will be just like when you pulled it out of the box for the first time."

badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT requiring root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.

yes so first before rooting or unlcoking anything download your carriers ruu but it in you sd card and boot to boootloder (vol down + power button) it will install then use hasoon tool kit to unlock boot loader then flash 4ext recovery then root then flash rom

Crashdamage said:
badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.
Click to expand...
Click to collapse
Crashdamage:can I use the same process to go back to the original stock ROM prior to any OTAs? And here is why I want to do that.
I got my phone in January 2012. I received a message about an OTA. I did the update. My Plantronics Voyager Pro and 2-Explorers came in. I tried them out on the phone and the reception and range were completely horrible. 1-2 Ft. the Explorers had slightly better sound quality.
After some research on t-mo forum I found that there were others with the same problem. (The first Product Review that complains about Bluetooth issue was December 17, 2011. The first OTA was released on December 12, 2012. Coincidence?) Some of the people said their BT worked fine prior to the first OTA. T-mo's corporate line was "ICS will fix everything." I waited for ICS as long as I could and did the "Leaked ICS."
ICS did not fix the problem....but it did improve it from 1-2 Ft. to 8-10 Ft. It still has quite a bit of static. Therefore because ICS did improve the problem, I want to test the theory that everything was fine with the original ROM. Kind of a "test the theory" and "process of elimination."
Any help form you and the community will be greatly appreciated. I hope at the end of this I can take my findings back to the others that are having this same problem...some of them that have done multiple handset exchanges and still have the problem. -THANKS-

My question to you guys is, why root if you want to update to ICS? You do know all the OTA files are available and I wrote a tutorial to update your device manually using them, right?
I want to say it, but I won't, I'm not up for the rants, etc.
badgerdave, if I remember correctly, you're from the tmo community fora, right? You had an issue with your BT and someone posted saying theirs worked great when they rooted their device. You can try a few custom roms, but nobody is definite on your end result until you do it.
Also you guys need to quit using those slow filefactory uploads, devs, RC's, myself included uploaded those files to dev-host accounts for faster, easier downloads, those links can be found in the stock ruu/ota thread, use those and PLEASE READ the dev section, there's updated post and links on the very first threads, I don't get why there's a need to dig up older threads with outdated files/info for something so simple.

Dark Nightmare said:
My question to you guys is, why root if you want to update to ICS? You do know all the OTA files are available and I wrote a tutorial to update your device manually using them, right?
I want to say it, but I won't, I'm not up for the rants, etc.
badgerdave, if I remember correctly, you're from the tmo community fora, right? You had an issue with your BT and someone posted saying theirs worked great when they rooted their device. You can try a few custom roms, but nobody is definite on your end result until you do it.
Also you guys need to quit using those slow filefactory uploads, devs, RC's, myself included uploaded those files to dev-host accounts for faster, easier downloads, those links can be found in the stock ruu/ota thread, use those and PLEASE READ the dev section, there's updated post and links on the very first threads, I don't get why there's a need to dig up older threads with outdated files/info for something so simple.
Click to expand...
Click to collapse
Yes DN that is me. But...I'm am not an anomaly where this BT issue is concerned. I have dated it back to the first posted product review
(December 17, 2011) that listed the BT as an issue...others came after. December 17 is 5 days after the first OTA. There are no bad BT reviews prior to that date.
I am not trying to be difficult. I actually downloaded the PDF for the Amaze Bible and installed it onto my rooted HP Touchpad. I read what you are talking about. (Keep in mind that you guy do this stuff all the time with multiple devices. This comes easy to you. Not so much for those of us that get directed to this forum because our questions and problems surpass the T-mo site.)
That being said..I'll just try my hand at using this link: http://d-h.st/8pm to get what I think I need and then try installing it like I did the first "Leaked ICS"
Thanks for your help.
New motto: Believe in oneself...because no else does.

badgerdave said:
Yes DN that is me. But...I'm am not an anomaly where this BT issue is concerned. I have dated it back to the first posted product review
(December 17, 2011) that listed the BT as an issue...others came after. December 17 is 5 days after the first OTA. There are no bad BT reviews prior to that date.
I am not trying to be difficult. I actually downloaded the PDF for the Amaze Bible and installed it onto my rooted HP Touchpad. I read what you are talking about. (Keep in mind that you guy do this stuff all the time with multiple devices. This comes easy to you. Not so much for those of us that get directed to this forum because our questions and problems surpass the T-mo site.)
That being said..I'll just try my hand at using this link: http://d-h.st/8pm to get what I think I need and then try installing it like I did the first "Leaked ICS"
Thanks for your help.
New motto: Believe in oneself...because no else does.
Click to expand...
Click to collapse
Not that no one believes in you, but think about this for a minute, many contributors, devs and regular users alike here saw the issue many were having, saw how complicated getting things done were, so we put as much time into making this all simple, I'm talking months of work, endless hours of typing and research to simplify things here, so for you to say you're unable to find things here, that kinda hurts, I myself worked on making the ICS update as simple as possible, I've posted multiple times, more than I can count on how to fix soft bricks and how to restore to complete stock, so you can tell how hard it is to believe when people say we're not helpful and we don't make things simple, if you have a question, ask it flat out, I'll be straight with you that I know what you read and did not read, I can tell you exactly where everything can be found for this device and I've been here a mere month or two, you know what? It's pointless, no point in me saying anything anymore, I guess I should just follow suit of every other contributor around here and just move on to another device like they all did/doing.
So have a nice day, if you can find what you're looking for in the amaze bible thread, PM one of the writers, sure they'd be glad to help, they always have been and always will be very nice helpful individuals.
New motto: I am officially out of the amaze forum.

badgerdave said:
Not sure if this helps...but this is what I did. I originally posted it on T-mo forum. At the very least it will put you in the ballpark...good luck. Just trying to help. These other guys know a lot more than myself. I'm sure the community will get you through it.
"Re: Leaked ICS in the wild!
Okay. Got it. Long story short:
1. Download file onto PC
2. Put file on SD card (I recomend different SD card.)
3. After it is on SD card, rename file "PH85IMG" *** No ".zip." ***
4. Power down phone
5. Remove/replace SD card
6. Remove battery
7. Replace battery
8. Power up the phone hold "power button and volume down" at the same time.
9. Hboot will appear...let go of buttons. the phone will then start reading the SD card. "Checking PH85IMG"
10. After that instructions will appear. At the bottom of the info you will see the prompt: "Do you want to start update?" Now Volume up for "Yes."
11. Once you volume up for yes it will begin checking the files. (After some time it updated a few files and the screen went black. I hit the power button and and it started updating all files.
In closing you "WILL" lose all info, contacts, text, email and any other setting on the phone. It will be just like when you pulled it out of the box for the first time."
Click to expand...
Click to collapse
Crashdamage said:
badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT requiring root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.
Click to expand...
Click to collapse
I tried the steps given and everything was going fine until step number 10. I never got a prompt asking to update my phone. Instead it just took me back to the hboot screen with the three androids skating at the bottom with the options: fastboot, recovery, factory reset, clear storage, simlock, image crc. I already had an ICS file downloaded from previous trials to install it, so I didnt use the link you posted, not sure if that matters or not. Anyways, I tried to hit recovery and then a picture of a phone with a red exclamation mark showed up. I then hit the volume up button and power at the same time. Then i went to "apply update from sd card" and then i got an invalid operation and the phone just rebooted normally without applying any update. Any ideas?

Kashif92k said:
I tried the steps given and everything was going fine until step number 10. I never got a prompt asking to update my phone. Instead it just took me back to the hboot screen with the three androids skating at the bottom with the options: fastboot, recovery, factory reset, clear storage, simlock, image crc. I already had an ICS file downloaded from previous trials to install it, so I didnt use the link you posted, not sure if that matters or not. Anyways, I tried to hit recovery and then a picture of a phone with a red exclamation mark showed up. I then hit the volume up button and power at the same time. Then i went to "apply update from sd card" and then i got an invalid operation and the phone just rebooted normally without applying any update. Any ideas?
Click to expand...
Click to collapse
First of all before getting to a solution, you need to point out your device info, that way nobody would be guessing, so provide the following and we'll work from there:
hboot version:
software version currently:
s-on or s-off:
bootloader unlocked: yes or no
carrier:
from there solving your problem would be very much more simple.

Dark Nightmare said:
First of all before getting to a solution, you need to point out your device info, that way nobody would be guessing, so provide the following and we'll work from there:
hboot version:
software version currently:
s-on or s-off:
bootloader unlocked: yes or no
carrier:
from there solving your problem would be very much more simple.
Click to expand...
Click to collapse
this is what is see on the hboot screen:
" ***LOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0004
eMMC-boot
Sep 15 2011, 18:13:11 "
The bootloader is locked, The carrier is T-Mobile USA. Im running on Android version 2.3.4 and the software version is 1.36.531.6. I also took a look at your tutorial for installation before I tried to do it myself.

Kashif92k said:
this is what is see on the hboot screen:
" ***LOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0004
eMMC-boot
Sep 15 2011, 18:13:11 "
The bootloader is locked, The carrier is T-Mobile USA. Im running on Android version 2.3.4 and the software version is 1.36.531.6. I also took a look at your tutorial for installation before I tried to do it myself.
Click to expand...
Click to collapse
And what exactly was your result of attempting to manually update via the OTA files? Answer asap, I'll just move you on to the next method of getting it done via the latest leaked file if you can't get it done via the ota file.

Dark Nightmare said:
And what exactly was your result of attempting to manually update via the OTA files? Answer asap, I'll just move you on to the next method of getting it done via the latest leaked file if you can't get it done via the ota file.
Click to expand...
Click to collapse
Whenever I would manually search for the ICS update OTA, it would just say that my phone was already up to date (even though I am running on GB). Should I try to re-download the T-Mobile OTA file on 4shared that is on your tutorial? And then rename it to "PH85IMG.zip"? If not, please guide me to the next option/step. I really appreciate the help!! :good:

Kashif92k said:
Whenever I would manually search for the ICS update OTA, it would just say that my phone was already up to date (even though I am running on GB). Should I try to re-download the T-Mobile OTA file on 4shared that is on your tutorial? And then rename it to "PH85IMG.zip"? If not, please guide me to the next option/step. I really appreciate the help!! :good:
Click to expand...
Click to collapse
Redownload the ota file from here: http://d-h.st/tdM
Once you download it, place the file on your external sd card, not in any folders, just on the sd card.
Turn your device off
volume down and power on to boot into hboot
select recovery and wait for it to reboot
it should give you a red triangle error, ignore it and press volume up then power button
a recovery menu should pop up, once you see that menu, use the volume buttons to scroll down to the install update from external and hit power to select
it should give you a list of all the files on your sd card, use the volume buttons to highlight the file you downloaded and hit power to select, it should begin updating your device.

Dark Nightmare said:
Redownload the ota file from here: http://d-h.st/tdM
Once you download it, place the file on your external sd card, not in any folders, just on the sd card.
Turn your device off
volume down and power on to boot into hboot
select recovery and wait for it to reboot
it should give you a red triangle error, ignore it and press volume up then power button
a recovery menu should pop up, once you see that menu, use the volume buttons to scroll down to the install update from external and hit power to select
it should give you a list of all the files on your sd card, use the volume buttons to highlight the file you downloaded and hit power to select, it should begin updating your device.
Click to expand...
Click to collapse
ok, I followed the steps and tried it just now and I get an error message like this:
E:Can't open /cache/recovery/command
-- Invalid operation. --
Success Rebooting by reason: oem-00...
Also the the background is black with the red triangle error and the text is in yellow.

Kashif92k said:
ok, I followed the steps and tried it just now and I get an error message like this:
E:Can't open /cache/recovery/command
-- Invalid operation. --
Success Rebooting by reasonem-00...
also the the background is back with the red triangle error and the text is in yellow.
Click to expand...
Click to collapse
Yeah I expected that, seems only s-off users can proceed with that method.
This one should work fine though.
Download this file here: http://d-h.st/3VD
rename it PH85IMG and place it on the root of your sd card the same way you did the last file, it has to be named exactly that and in caps
reboot into bootloader, volume up when the file finishes loading, it's gonna install the update and reboot itself, let it boot properly, first boot may take a few minutes.

Dark Nightmare said:
Yeah I expected that, seems only s-off users can proceed with that method.
This one should work fine though.
Download this file here: http://d-h.st/3VD
rename it PH85IMG and place it on the root of your sd card the same way you did the last file, it has to be named exactly that and in caps
reboot into bootloader, volume up when the file finishes loading, it's gonna install the update and reboot itself, let it boot properly, first boot may take a few minutes.
Click to expand...
Click to collapse
The file is downloading right now. When I put the ICS file on the microsd card, do I rename it to "PH85IMG" or "PH85IMG.zip"? I'm also assuming that I have to follow the same steps you gave me on my last attempt to install?

Kashif92k said:
The file is downloading right now. When I put the ICS file on the microsd card, do I rename it to "PH85IMG" or "PH85IMG.zip"? I'm also assuming that I have to follow the same steps you gave me on my last attempt to install?
Click to expand...
Click to collapse
just PH85IMG, don't worry about the .zip part, it's already there, just not visible, no do not use the same steps, follow the steps I outlined above when I specified the file and what to do with it.

[GUIDE]: ROOT / BL-Unlock / Install Custom Recovery - LG Optimus G E970/1/3

INTRODUCTION
THIS IS A DETAILED GUIDE TO SHOW YOU HOW TO ROOT, BOOTLOADER-UNLOCK AND INSTALL CUSTOM RECOVERY AND ROMS ON YOUR LG OPTIMUS G E970/1/3 with a Windows PC. I will add to/edit it as necessary, and will probably beautify it a bit soon enough as well.
Disclaimer: This has worked successfully for many people on these devices, including myself on the E971. Having said that, I’m not responsible for any explosions or any other form of destruction you may end up with as a result of using this guide!
Click to expand...
Click to collapse
The Dropbox files I’ve linked here are from my own account, so rest assured everything is safe. I will be posting mirrors soon (or replacing if necessary).
A full list of “thanks” will be at the end.
PLEASE follow all the instructions carefully. I will try to help as much as I can, but I am in no way a developer. Just a guy who loves messing with stuff, especially these awesome devices. The #lg-optimus-g IRC chanel is always great help along with great folks here.
---
PRE-GAME CHECKLIST
COMPUTER PREP – Install the following before proceeding any further. If you know for sure you’ve got these taken care of, go ahead to the next section.
1) ADB/FASTBOOT/APX DRIVER - DOWNLOAD: https://www.dropbox.com/s/v7duwo5l09dky8n/Universal_Naked_Driver_0.72.zip
- This driver, in part, is needed for your phone to properly communicate with the PC for our needs. That goes for any Android device, so this is definitely a must have. For more details and discussion/help > http://forum.xda-developers.com/showthread.php?t=19960512) LG DEVICE DRIVER - DOWNLOAD: https://www.dropbox.com/s/dho1z4hdkyezkgp/LGUnitedMobileDriver.zip
- Just like most USB devices, your phone relies on this to communicate with your PC.3) Make sure you have 7Zip, WinRAR, WinZIP or another similar application installed on your computer to be able to extract archives.
- Download 7zip here: http://www.7-zip.org/download.html
PHONE PREP - you will need the USB cable, and your phone needs to have internet connection for the bootloader unlock section. I recommend having JellyBean installed already, the OTA upgrade method is fine with stock before you use this guide. I haven't tried or had any info on anyone else trying this with stock Ice Cream Sandwich, so I'm not sure about the compatibility there.
MEAT AND POTATOES
-ROOT-
1) Download the root package here > https://www.dropbox.com/s/fib80m6q9jzcj4t/ZV9-ZVB-Universal-Root.zip > and extract it to a folder.
2) Connect your phone to your computer with the USB cable and CHANGE THE CONNECTION TYPE TO “CHARGE ONLY” IN NOTIFICATIONS. This is important for the next step.
3) Open the folder you extracted to and double click the batch file “CurrentRoot” or “CurrentRoot.bat”.
4) The on-screen instructions are pretty clear for this part. To sum it up:
a. You’ll need to wait for the phone to be recognized, then you’ll be asked to change the USB mode to “MTP” - you must do this in order to proceed. Press Enter.
b. You may see some error and “daemon” messages along the way here. Don’t be alarmed by those, focus on the prompts.
c. Once you see “uid=0(root) gid=0(root)” you will be prompted to press Enter again. If you don’t get that, reboot your computer and repeat from step 2.
d. At the end, you should see a message that says you’ve been properly rooted. Press any key to continue, your phone should automatically be rebooted (if not, manually do so).
e. Open your app drawer and run the app called SuperSU and ensure it runs with no errors. *IF YOU DON'T HAVE SuperSU IN YOUR APP DRAWER, DOWNLOAD/INSTALL/RUN IT FROM THE PLAY STORE!*
f. You can download any root-required app from the Play Store (Root Checker is easy if you can’t think of one) to verify that you are properly rooted. Congratulations!
-UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-
This section is done through an app, right in the Play Store thanks to Project FreeGee (XDA thread for thanks - http://forum.xda-developers.com/showthread.php?t=2001655). If you can, make sure to go there and give thanks to thecubed (and Shellnutt2) for this amazing app and all their efforts. Please get the $1 version if you can as well, it’s beyond worth it.
Head on over to the Play Store and download the app “FreeGee **ROOT Required**” or do it on your PC - https://play.google.com/store/apps/details?id=edu.shell.freegee&hl=en ($1 – if you can this would be the one to go for) OR https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en (free version). Run the app and grant it root permissions. FOLLOW THESE INSTRUCTIONS CAREFULLY!
1) In the app, ignore the main buttons and click Menu > SBL Unlock method.
2) Click “Get Unlock Code” – a browser window will open up. Here will be a hardcore disclaimer by Shelnutt2, and it should be taken seriously since there IS a possibility of something going wrong. The chances are EXTREMELY SLIM, but the disclaimers have to be put in place.
3) Enter your name (username for forums is the best way to go), click the checkbox, enter the CAPTCHA, and click “Submit”.
4) The next page will have your code. Copy it and go back to the FreeGee app.
5) Paste the code into the field and click “ok”. You should get a confirmation message that you’ve enabled the SBL Unlock method.
6) On the app’s main screen, click “Unlock my phone” and wait for the download to finish.
7) You’ll be asked to choose a recovery version. I personally use ClockworkMOD, but many people like TWRP. It shouldn’t make a difference at the end of the day, you can look into both and decide if you’d like. Choose one, and proceed through all the dialogue boxes, accepting everything. Your phone will eventually reboot.
8) To verify this was done properly, after the reboot you can reboot again into recovery mode. The easy way to do this is to download QuickBoot from the Play Store and use that. Otherwise:
a. Power off your phone
b. Press and hold the PWR button, while holding down the VOL-UP/VOL-DOWN buttons at the same time (I’ve seen VOL-UP/PWR as instructions, I haven’t been able to get it to work myself like that but YMMV).
c. You’ll see a black screen with some small writing in the bottom-left corner. Nothing will actually respond on-screen at this point, don’t worry.
d. Press VOL-DOWN twice, then press PWR.
e. Your custom recovery should now boot up. Here, you can backup your current software (DO THAT RIGHT AWAY), reboot the phone into whichever mode you want, and install custom ROMs (more and that after the break).
JOB WELL DONE. NOW WHAT DO YOU DO?
The very first thing I recommend you do is BACKUP YOUR EFS PARTITIONS!! Head over to this thread by autoprime on XDA: http://forum.xda-developers.com/showthread.php?t=2161611&highlight=efs - this is important to have in case things go wrong down the road.
Now you have the freedom to do quite a bit, most notably install custom ROMs. It’s important to read through the entire original post of a ROM’s thread. The developer has put everything there for a reason, follow it to the tee! Methods of installation for ROMs may slightly vary. Use the files they link only and don’t stray from their installation instructions.
A loose reference to the most common method is:
a. Wipe data/factory reset
b. Wipe cache
c. Wipe dalvik cache
d. Install ROM file
e. Install GApps file
f. Wipe data/factory reset again (usually good measure regardless)
g. Reboot system
USEFUL INFO AND LINKS (more to come)
I cannot stress how crucial backups are. Back EVERYTHING up, and keep them in more than one place. Much, much better safe than sorry. Titanium Backup is your best friend, check it out.
https://www.dropbox.com/s/cbxid5abrqwkqe5/fix_nfc.zip - NFC fix for CANADIAN phones (E971/3) - this is important as pretty much any ROM you flash that was made for the E970 onto an E971/3 (which is not an issue) will have NFC problems. Simply flash this through recovery AFTER the initial reboot of the ROM.
http://forum.xda-developers.com/showthread.php?t=2010624 - Guide to unbrick your phone! This worked well for me when I bricked back in the day!
http://forum.xda-developers.com/showthread.php?t=2230994 - Another (awesome) method of restoring your phone if it gets messy (can only vouch for E970 based on the thread there) - has had much success.
http://forum.xda-developers.com/showthread.php?t=2181103 - Thread for original root method, good for help.
---
THANKS!
- carrett (original guide that, in part, inspired this one)
- 1wayjonny (original thread for ADB/FB/APX driver)
- fiddy619 (original thread for root method)
- thecubed (project FreeGee - enough said)
- Shelnutt2 (project FreeGee - enough said)
- kentek (source for awesome LG driver)
- autoprime (author of the EFS backup guide and general LG OG God status)
- Paulicat (responsible for much of my (yet limited) wisdom regarding this device)
+ Anyone directly or indirectly responsible for anything in that list who I've left out.
+ Sorry to anyone else I've missed, please send me a quick message and I'll add you in, and I will add in as I go if I remember more.
+ The awesomeness of the #lg-optimus-g IRC channel and everyone in it - check it out on http://webchat.freenode.net!

Reserved.
Sent from my Optimus G using xda app-developers app

How does this differ from carrett's thread that's been stickied at the top of this forum for 10 months or so?
http://forum.xda-developers.com/showthread.php?t=2006946

dbgeek said:
How does this differ from carrett's thread that's been stickied at the top of this forum for 10 months or so?
http://forum.xda-developers.com/showthread.php?t=2006946
Click to expand...
Click to collapse
It was initially written to be put on the CM wiki to have the instructions there. I made it very detailed and specific with everything contained within it, so I figured it would be good for beginners and other users alike. Another reason is that I noticed the Canadian E971/3 didn't have a guide in that section. Since it applied to the E970 as well, I thought I'd share it.

hv6478 said:
It was initially written to be put on the CM wiki to have the instructions there. I made it very detailed and specific with everything contained within it, so I figured it would be good for beginners and other users alike. Another reason is that I noticed the Canadian E971/3 didn't have a guide in that section. Since it applied to the E970 as well, I thought I'd share it.
Click to expand...
Click to collapse
Solid post dude, your attention to detail is top notch!!! Thanks for taking the time to help people out, keep up the great work!!!
Sent from my Nexus 4 Pimpin AOSPA 3+

Thank you sir!
Sent from my Optimus G using xda app-developers app

Great job on the write up. I never got a chance to check it out since the casa is loco when I get home (weekend night drinking is the only time I get and at "work", I'm on irc). Thanks for taking the time detailing everything for the noobies and for those of us that have the occasional brain fart.
Sent from my Optimus G using xda app-developers app

Does this mean
ATT Optimus G Roms work on Canadian Optims Gs?

jnhsd0319 said:
Does this mean
ATT Optimus G Roms work on Canadian Optims Gs?
Click to expand...
Click to collapse
Yup. They seem to be identical except for NFC. YMMV of course but all should be well. Just always back up! Make sure you flash the NFC fix after installing an AT&T ROM to make it work and to ensure you don't get bad battery drainage.
Sent from my Optimus G using xda app-developers app

mikeylikey said:
Great job on the write up. I never got a chance to check it out since the casa is loco when I get home (weekend night drinking is the only time I get and at "work", I'm on irc). Thanks for taking the time detailing everything for the noobies and for those of us that have the occasional brain fart.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Thank you for the feedback, much appreciated!
Sent from my Optimus G using xda app-developers app

Hello guys,
Thanks for the guide. However I am having trouble getting my device recognized by the program. I have downloaded the files in order, including the LG drivers. I have only rooted phones the old school way on a g1 and a g2x from t-mobile.
EDIT: Sorry, I had forgot to have USB debugging enabled. Brand new phone and I forgot to enable it.

hv6478 said:
Yup. They seem to be identical except for NFC. YMMV of course but all should be well. Just always back up! Make sure you flash the NFC fix after installing an AT&T ROM to make it work and to ensure you don't get bad battery drainage.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Hello, sorry to bother you again
I was just wondering if international optimus G roms can be flashed or is it just AT&T roms?
Also do you have a link to NFC fix?
Thank you so much!

jnhsd0319 said:
Hello, sorry to bother you again
I was just wondering if international optimus G roms can be flashed or is it just AT&T roms?
Also do you have a link to NFC fix?
Thank you so much!
Click to expand...
Click to collapse
Not a bother at all!
Make sure you do NOT flash any international ROMs, made for E975 for example. They are not compatible.
NFC fix is here. I have added it to the OP.

hv6478 said:
Not a bother at all!
Make sure you do NOT flash any international ROMs, made for E975 for example. They are not compatible.
NFC fix is here. I have added it to the OP.
Click to expand...
Click to collapse
Thank you so much for the answer.:good::good:
Ive been looking thoroughly in the forum to root/install custom roms for my phone. Just being really careful before hand because Im worried about my warranty.
Anyways
May I ask you another question? you seem to know your stuff and helpful :laugh:
If its ok, I was wondering if I can remove root and relock the bootloader if i flash a kdz file for my phone.
Is flashing kdz only changing the ROM or does it literally reset the device back to original factory option? (for warranty service)
Thank you and have a nice day!

hv6478 said:
Not a bother at all!
Make sure you do NOT flash any international ROMs, made for E975 for example. They are not compatible.
NFC fix is here. I have added it to the OP.
Click to expand...
Click to collapse
No problem!
The KDZ method WILL relock everything and bring it back basically to a factory phone. Just make sure you are using the correct KDZ file for your phone and you follow all instructions fully.
Sent from my Optimus G using xda app-developers app

When I'm in the freegee app I click menu and select sbl. In your instructions it says click get unlock code. I do not see this any where. After selecting sbl.
Sent from my LG-E970 using xda app-developers app

right now i am on e97011c software .,..
now i want to update to jellybean so i have downloaded jellybean rom from here ..
http://forum.xda-developers.com/show....php?t=2158144
it's a SnowJB v1.1 [2/20/13][STOCK][DEODEX]
So what will i have to do?
I have touch CWM install so i have to flash directly by going into recovery or not?
I am on ICS version e97011c rooted...
please help guys

hv6478 said:
INTRODUCTION
-UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-
This section is done through an app, right in the Play Store thanks to Project FreeGee (XDA thread for thanks - http://forum.xda-developers.com/showthread.php?t=2001655). If you can, make sure to go there and give thanks to thecubed (and Shellnutt2) for this amazing app and all their efforts. Please get the $1 version if you can as well, it’s beyond worth it.
Head on over to the Play Store and download the app “FreeGee **ROOT Required**” or do it on your PC - https://play.google.com/store/apps/details?id=edu.shell.freegee&hl=en ($1 – if you can this would be the one to go for) OR https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en (free version). Run the app and grant it root permissions. FOLLOW THESE INSTRUCTIONS CAREFULLY!
1) In the app, ignore the main buttons and click Menu > SBL Unlock method.
2) Click “Get Unlock Code” – a browser window will open up. Here will be a hardcore disclaimer by Shelnutt2, and it should be taken seriously since there IS a possibility of something going wrong. The chances are EXTREMELY SLIM, but the disclaimers have to be put in place.
3) Enter your name (username for forums is the best way to go), click the checkbox, enter the CAPTCHA, and click “Submit”.
4) The next page will have your code. Copy it and go back to the FreeGee app.
5) Paste the code into the field and click “ok”. You should get a confirmation message that you’ve enabled the SBL Unlock method.
6) On the app’s main screen, click “Unlock my phone” and wait for the download to finish.
7) You’ll be asked to choose a recovery version. I personally use ClockworkMOD, but many people like TWRP. It shouldn’t make a difference at the end of the day, you can look into both and decide if you’d like. Choose one, and proceed through all the dialogue boxes, accepting everything. Your phone will eventually reboot.
8) To verify this was done properly, after the reboot you can reboot again into recovery mode. The easy way to do this is to download QuickBoot from the Play Store and use that. Otherwise:
a. Power off your phone
b. Press and hold the PWR button, while holding down the VOL-UP/VOL-DOWN buttons at the same time (I’ve seen VOL-UP/PWR as instructions, I haven’t been able to get it to work myself like that but YMMV).
c. You’ll see a black screen with some small writing in the bottom-left corner. Nothing will actually respond on-screen at this point, don’t worry.
d. Press VOL-DOWN twice, then press PWR.
e. Your custom recovery should now boot up. Here, you can backup your current software (DO THAT RIGHT AWAY), reboot the phone into whichever mode you want, and install custom ROMs (more and that after the break).
/QUOTE]
My big ass question is why we have to download this project thing and pay money! when you can just download clockwork recovery.apk and just adb install it. and plus im not signing up for crap because i just don't feel like haveing to type my stupid google info. and plus it anoys the hell out of me the phone is totaly mirrored of samsung with the default os.
Is there a way to network unlock the phone?
Click to expand...
Click to collapse

manojcitc said:
right now i am on e97011c software .,..
now i want to update to jellybean so i have downloaded jellybean rom from here ..
http://forum.xda-developers.com/show....php?t=2158144
it's a SnowJB v1.1 [2/20/13][STOCK][DEODEX]
So what will i have to do?
I have touch CWM install so i have to flash directly by going into recovery or not?
I am on ICS version e97011c rooted...
please help guys
Click to expand...
Click to collapse
So sorry for late reply.
In your case, you actually need to follow the entire method in the original post as it seems. If you're still on stock firmware, you need to unlock before you can install any custom software.

HelmetDoe said:
hv6478 said:
INTRODUCTION
-UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-
This section is done through an app, right in the Play Store thanks to Project FreeGee (XDA thread for thanks - http://forum.xda-developers.com/showthread.php?t=2001655). If you can, make sure to go there and give thanks to thecubed (and Shellnutt2) for this amazing app and all their efforts. Please get the $1 version if you can as well, it’s beyond worth it.
Head on over to the Play Store and download the app “FreeGee **ROOT Required**” or do it on your PC - https://play.google.com/store/apps/details?id=edu.shell.freegee&hl=en ($1 – if you can this would be the one to go for) OR https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en (free version). Run the app and grant it root permissions. FOLLOW THESE INSTRUCTIONS CAREFULLY!
1) In the app, ignore the main buttons and click Menu > SBL Unlock method.
2) Click “Get Unlock Code” – a browser window will open up. Here will be a hardcore disclaimer by Shelnutt2, and it should be taken seriously since there IS a possibility of something going wrong. The chances are EXTREMELY SLIM, but the disclaimers have to be put in place.
3) Enter your name (username for forums is the best way to go), click the checkbox, enter the CAPTCHA, and click “Submit”.
4) The next page will have your code. Copy it and go back to the FreeGee app.
5) Paste the code into the field and click “ok”. You should get a confirmation message that you’ve enabled the SBL Unlock method.
6) On the app’s main screen, click “Unlock my phone” and wait for the download to finish.
7) You’ll be asked to choose a recovery version. I personally use ClockworkMOD, but many people like TWRP. It shouldn’t make a difference at the end of the day, you can look into both and decide if you’d like. Choose one, and proceed through all the dialogue boxes, accepting everything. Your phone will eventually reboot.
8) To verify this was done properly, after the reboot you can reboot again into recovery mode. The easy way to do this is to download QuickBoot from the Play Store and use that. Otherwise:
a. Power off your phone
b. Press and hold the PWR button, while holding down the VOL-UP/VOL-DOWN buttons at the same time (I’ve seen VOL-UP/PWR as instructions, I haven’t been able to get it to work myself like that but YMMV).
c. You’ll see a black screen with some small writing in the bottom-left corner. Nothing will actually respond on-screen at this point, don’t worry.
d. Press VOL-DOWN twice, then press PWR.
e. Your custom recovery should now boot up. Here, you can backup your current software (DO THAT RIGHT AWAY), reboot the phone into whichever mode you want, and install custom ROMs (more and that after the break).
/QUOTE]
My big ass question is why we have to download this project thing and pay money! when you can just download clockwork recovery.apk and just adb install it. and plus im not signing up for crap because i just don't feel like haveing to type my stupid google info. and plus it anoys the hell out of me the phone is totaly mirrored of samsung with the default os.
Is there a way to network unlock the phone?
Click to expand...
Click to collapse
You don't need to pay. There is a fee version of FreeGee available as indicated.
LG released the device with their own software - it was not the work of anyone here - if you don't like it, that is what XDA is here for! Welcome!
You need to first be able to access recovery and adb properly to push recovery.apk. Not to mention I'm not sure of any steps prior to that to make your phone ready to do so. That is a totally different guide. If you wish to use THIS method, everything you need is here.
Click to expand...
Click to collapse

Better Mobile App

welcome