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

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).

Related

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

** 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!

[GUIDE]Complete Guide to Obtain S-OFF, Flash Recovery, and Install ROOT for the EVO3D

Hello everyone,
I wanted to take some time today to make a very clear and concise guide on how to complete the root process for the EVO3D. I understand that there is at least one other floating around at this point. If you don't have a firm grasp of how all of this works though, you may run into problems or have questions. I commissioned my guide to try and add clarity to the process and to also teach our communities newest members some of the ins and outs of modding our phones. The guide is far too large to post in a thread, therefore I've created a PDF of it and am offering it for download.
Feel free to mirror my guide and provide me with the link so that I can add it below.
Below is a Preface and Contents of the Guide. Feel free to ask questions or address any concerns you may have as I will be revising the guide.
The Complete Guide to Obtain S-OFF, Flash Recovery, and Install ROOT for the EVO3D
Authored by: sidepart of the
XDA-Developers Forum
Revision 1.1 - Published July 30, 2011​
Preface
Prior to reading this document, please be aware that as a disclaimer, I am not responsible for anything that goes wrong in this guide. Some people will run into issues that others do not. This is especially true with the differing versions of the Android-SDK. Some advanced users are using an older version which uses different commands than are offered by the latest Android-SDK. I encourage you to ask questions and keep an open mind. Try to understand the commands that are given here, and how you might have to be flexible in changing them to work for your situation. If at any time you are not comfortable with this process I highly recommend seeking out assistance from a more knowledgeable friend.
What this Guide Assumes
I assume that you will be downloading the latest version of the Android SDK which at the time of this document’s creation is R12. I also assume that you are using Windows 7, but this translates very easily into Windows Vista or XP.
Disclaimer
I am not responsible for any problems or fatal errors that may or may not occur through the process of performing the instructions of this guide. If at any time you are not comfortable with this process I highly recommend seeking out assistance from a more knowledgeable friend.
Contents of this Guide
What is S-OFF, Recovery and Root?
It’s not Just “ROOT”. Getting Past Outdated Nomenclature.
When I Say, “Do this”, Perform the Following Steps
Going to HBOOT
Booting into Recovery
Enabling USB Debugging
Install the Android-SDK
Obtaining S-OFF Status
Obtaining “unrevoked & AlphaRev’s: Revolutionary S-OFF & Recovery Tool”
Common Questions
Running “unrevoked & AlphaRev’s: Revolutionary S-OFF & Recovery Tool”
Common Questions
Flashing a Recovery Program
Flashing the TeamWin Recovery Project Recovery Program
Flashing or Installing the Superuser Management Program (Root)
Conclusion
Acknowledgements
Click Here to Download
Changelog
Revision 1.1 - July 30, 2011
Fixed some glaring grammatical and spelling errors.
Added a Common Questions section under item 4b.
Added a common question to 4b,i. It instructs users on how to paste their Beta key-code into the Revolutionary EXE program.
Fixed some formatting.
Used your guide and had no problems thank you!
Have not used it yet but this is very helpful... will be rooting my wifes e3d tonight... wasn't going to do it off of the other thread... I had no idea what it was talking about. Thanks for taking the time to put this together
Sent from my SPH-D700 using XDA App
Kind of hilarious to see my access.log right now. Lots of people looking at the guide interspersed with a few people discovering my site's index.html.
Used your guide and almost worked flawlessly The only problem I had was flashing the TeamWin recovery with the following command: ..\tools\fastboot.exe flash recovery recovery-twrp-shooter-1.0.0.img
The img that I downloaded through the site was like 1.0.1, but the error was on my end. Otherwise awesome guide!
So much info!!! love it.. nice
Sent from my PG86100 using www.psvitahacks.co app
bryangene said:
Used your guide and almost worked flawlessly The only problem I had was flashing the TeamWin recovery with the following command: ..\tools\fastboot.exe flash recovery recovery-twrp-shooter-1.0.0.img
The img that I downloaded through the site was like 1.0.1, but the error was on my end. Otherwise awesome guide!
Click to expand...
Click to collapse
I think they may have updated since I first published. I might see if I can emphasize that you're supposed to use the downloaded filename in the command.
Excellent guide!
Sent from my PG86100 using XDA Premium App
Lovely guide! for those who get
E:Error in /tmp/sideload/package.zip
(status 0)
just reflash su >_>
zander145 said:
Lovely guide! for those who get
E:Error in /tmp/sideload/package.zip
(status 0)
just reflash su >_>
Click to expand...
Click to collapse
I actually tried to load the zip from http://goo-inside.me/superuser and it wouldn't work. Retried it quite a few times and got the same error. I found an unsigned version of it in clark44's guide and that one worked just fine. Not sure what the problem was, hence my recommendation to grab superuser from the market and follow it's instructions instead. Seems to be working out well.
I think I might add something about this to the guide if too many people are running into the problem.
Any problems with not being able to send/recieve calls/texts with this? Haven't really messed around too much with the girlfriend's phone b/c she's terrified of not being able to get calls and what not..
I know this is a beta setup for now, so i'm assuming it'll turn into a simple one click type of thing when it gets to that point..?
Edit: I went through all this on my phone and had no problems really except having to call Sprint ..
Followed the guide as instructed...revolution wont recognize my device...it just hangs on waiting for device. I double checked to ensure usb debugging was enabled but it just hangs there.. Again i did follow the guide from step 1 and this is where im at...any suggestions?
SBERG117 said:
Followed the guide as instructed...revolution wont recognize my device...it just hangs on waiting for device. I double checked to ensure usb debugging was enabled but it just hangs there.. Again i did follow the guide from step 1 and this is where im at...any suggestions?
Click to expand...
Click to collapse
I would take a look at the documentation for the Revolution EXE, it could shed some more light on the situation that you're experiencing. Off hand though, I do have some recommendations.
Do you have HTC sync installed? I was reading around and found that this was causing an issue with the revolution program. Try removing that first.
If that's not the case and this still isn't working, there could be a driver conflict with some previously installed android drivers on your system. To clear that up, I would recommend grabbing the latest HTC drivers mentioned in the Revolution documentation. This is the most recent link that I've found: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
The process may require you to manually remove the old drivers and manually install the new ones. If you're not certain of how to do this, it's beyond the help of my guide. I would encourage you to look up the process online or ask a friend to show you.
Hope this helps!
Neogenx said:
Any problems with not being able to send/recieve calls/texts with this? Haven't really messed around too much with the girlfriend's phone b/c she's terrified of not being able to get calls and what not..
I know this is a beta setup for now, so i'm assuming it'll turn into a simple one click type of thing when it gets to that point..?
Edit: I went through all this on my phone and had no problems really except having to call Sprint ..
Click to expand...
Click to collapse
The only related issue that I've come across is the "Error 16" when provisioning the phone after s-off. As you found, this usually fixed with a call to Sprint. I'll never say, "never" though. Be aware that making modifications to the phone always carries with it an inherent risk, however small or unlikely. The risk of course is part of what makes it fun, but girlfriends (mine) seem to seldom understand this.
If the root method is ever released, there is potential for it to become more of a one-click procedure, but I don't think there's a guarantee of course.
Thanks for the guide!
I'm stuck though!
The Revolutionary Command Window says:
"Waiting for fastboot..."
And my phone rebooted into the HBOOT screen but it shows: S-ON
What should I do?
Is this in your guide?
1. Install drivers: http://www.multiupload.com/2OFYWZFCCR
2. Put phone in full boot, usb debugging on , charge only.
3. Uninstall HTC Sync if installed.
4. Profit.
sidepart said:
I would take a look at the documentation for the Revolution EXE, it could shed some more light on the situation that you're experiencing. Off hand though, I do have some recommendations.
Do you have HTC sync installed? I was reading around and found that this was causing an issue with the revolution program. Try removing that first.
If that's not the case and this still isn't working, there could be a driver conflict with some previously installed android drivers on your system. To clear that up, I would recommend grabbing the latest HTC drivers mentioned in the Revolution documentation. This is the most recent link that I've found: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
The process may require you to manually remove the old drivers and manually install the new ones. If you're not certain of how to do this, it's beyond the help of my guide. I would encourage you to look up the process online or ask a friend to show you.
Hope this helps!
Click to expand...
Click to collapse
Updating the driver worked..im good to go now.. thnx..

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!
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
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
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.

[UPDATED 3.16.13] [ROOT] [GUIDE] 6 Steps! [Works with all builds up to 3.16.651.3]

This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!

lg l9 p769 - droid 4.0.4 - i'm lost, could use help, linux user

i have been seeing a lot of threads about rooting this phone, but, they all have windows scripts, even the thread that is said to have a runme.sh does not have it in any of the links that i unzipped - only a runme.bat, but yet, people keep mentioning a runme.sh in it... also, i really don't see any one lying out the steps for doing this with linux.
i'm a noob, and dont really know much about this stuff, but i've done this ONCE before with a galxy exhibit, but it was very easy, i just copied a file to the phone (stock rom?), rebooted into recovery, told it to recover from that file, and i was done.
i have no idea how to do it with my new phone, and so i'm wondering:
1: where can i find the files i need to do this with linux - i just want root, nothing special
2: where can i find the steps necessary to do it - in the easiest manner possible?
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
any help is appreciated.
sentientsystem said:
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
Click to expand...
Click to collapse
Your phone is running ICS 4.0, that is the version which it shipped with. Pretty much everyone on here has upgraded to JB either with software update on the phone or they have manually updated with the offline KDZ flash method.
I dont have any experience in linux so I cant help. I hope you can get your phone rooted!
Sent from my LG-P768 using xda app-developers app
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
sentientsystem said:
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
Click to expand...
Click to collapse
You would need wine and then set it up...
Sent From My Xperia Themed P769
well, i tried that "LGpwn" and it didn't work, as well as a fake lg-recovery app. i figured out that i've got a "10g" phone (P769 V10G ICS). i'm not sure what the next step is. some one mentioned downgrading to JB... is there some where you can point me to for that???
i've GOT to get this t-mobile junk off my damned phone... i've even TRIED to install cyenogenmod, but i can't figure out how to get my phone to go into recovery mode (NOT factory rest) - i've tried volup+power+home and volup+power, and neither seem to be working.
Setup a sandbox, windows xp. LG uses windows, no other way to root as of right now for the t-mobile version.
Sent from my LGMS769 using xda app-developers app
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrade to a samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
sentientsystem said:
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrad to an samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
Click to expand...
Click to collapse
Option #1
If you are rooted on stock T-Mobile 10e or 10g ROM and have the CWM installed from this thread:http://forum.xda-developers.com/showthread.php?t=2095825 follow my instructions.
Place one of these CWM ROM images on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2136204
Place this JB radio firmware from T-Mobile 20d ROM on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2256350
Power off the device.
After power on the back/menu capacitive buttons will flash repetedly. Press Volume down while the lights are flashing and the phone should go into recovery.
Flash the ROM first.
Flash the radio second.
Reboot.
***Notes***
1.) 20d is the latest T-Mobile, 21b is the latest Wind Mobile. Both work.
2.) 21b is lighter/faster but has no wifi-calling.
3.) 21b will require you to manually enter your APN settings for cellular data and MMS. Be sure to write down your APN settings before flashing this ROM.
4.) Some users say battery life sucks on JB. I notice that 21b is better on battery life than 20d.
Option #2.
In Linux install a Windows VM and follow the standard instructions here:
http://forum.xda-developers.com/showthread.php?t=2173465
Use KVM with a GUI or even easier use VirtualBox.
I'm a die hard linux geek too. I even run linux at work while all of our msp software was written for windows. You are better off just running an old copy of xp inside virtualbox trust me its just easier that way. You can use adb if you like (its the same thing the windows users use in their batch files and just rewrite the bash script, but you will save yourself lots of headaches just using virtualbox. -- my .02
Sent from my LG-P769 using xda premium
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
# what's the difference between unlocked boot loaders and being rooted?
# do you have to unlock the bootloader to get root access?
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
My bad. I should have read through your original question all the way before posting. I see that you are not rooted.
If you are on 10e ROM you can root in Linux:
http://forum.xda-developers.com/showthread.php?t=1990705
It will require rewriting the batch script as a Linux shell script. It is possible but nobody has done it yet.
If you are on 10g you will need Windows. I have also answered your questions below.
sentientsystem said:
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
It allows you to boot an un-signed kernel. You can boot custom ROMs basically.
# what's the difference between unlocked boot loaders and being rooted?
Root allows you to `su -` to the root user and own the whole system.
# do you have to unlock the bootloader to get root access?
No.
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
Click to expand...
Click to collapse
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
sentientsystem said:
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
Click to expand...
Click to collapse
Welcome!
I know that a long time ago when I ran VirtualBox in Ubuntu there was something I had to do to allow USB access to the VM.
Here are the current instructions directly from Ubuntu:
https://help.ubuntu.com/community/VirtualBox/USB
Good luck.
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
sentientsystem said:
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
Click to expand...
Click to collapse
Yes you can flash a pre-rooted image. They are available. Use the search?
I posted instructions on the first page showing how to boot recovery.
that's great news - that's all i really needed - i didn't see them before, at least, not conspicuously, but i'll search around again.
and, i must have some how missed your instructions, i'll look again.
thanks!
kevev said:
I posted instructions on the first page showing how to boot recovery.
Click to expand...
Click to collapse
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @everyone for your help.
sentientsystem said:
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
Click to expand...
Click to collapse
I've decided to help you out This page will give you some more info on the P769 and several kdz (roms) for the P769
The fastest way to root is to flash the V21B kdz (this is the Jelly Bean version for Canada) using this guide, http://forum.xda-developers.com/showthread.php?p=36351786
The reason why you want this rom is because it has a vulnerability that is easy to exploit with Jcase apk
Once your followed everything (and rooted), install Super Su and Busybox
Next install artas182x second init CWM (in case you can't find it on his page, the link is here )
Note: you will see blinking led lights when you see the LG logo (booting up) appear after a couple of seconds. To enter the CWM press the vol (-) when the lights start flashing.
After you installed Artas182x CWM you can recover from someones clockworkmod backup.
following info from Cmahendra's thread
Note: only restore CWM backups from P769 versions or MS769!!!!
Or check out the V10B (MetroPCS "JellyBean") CWM backup
Now the only 2 reasons to unlock the bootloader are:
1. Install a safer and better CWM
The reason why is because Artas182x CWM is a second init (bootstrap), so if you mess around with a busybox apk and something goes wrong or you remove a file that is required (for CWM), it will stop operating. You will have to reflash the kdz or fix what you changed to get it working again.) I've had this problem several times while messing around with different busybox apps and etc.
2. Custom roms
(which you stated you are not looking for) not worth talking about right now.
Answer to questions
The only pre rooted roms are clockworkmod backups, lol
The default recovery is useless to us (unless you feel like solving the problem)
Flashing back and forth (ice to jelly) comes with risk, the program used on Windows to flash is buggy at times. The best way (in my opinion) is to flash only when really required and mostly restore from clockwormod backups. The device is actually hard to hard brick, but it will require at lot more knowledge to get your device running again.
---------- Post added at 07:23 PM ---------- Previous post was at 07:16 PM ----------
sentientsystem said:
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @all for your help.
Click to expand...
Click to collapse
So what version are you on right now
Ice? Jelly?
i'm still on ICS for the moment. still trying to understand what i need to do next. re-reading your post for the 2nd time, and all the threads it references. making sure i don't screw any thing up. thinking about upgrading to JB, and trying this CWM. and looking into this "cyanogenmod" some more, to understand why i never see any one on this site mention it, and what all these "other roms" are about. lmao, like i said, i'm way new to this . it's a lot to take in, even for a web developer .
thanks \m/ (>_<) \m/

Categories

Resources