Develop Bugs

Life after simpleroot?

Hey guys I just finished runny simple root OTA edition. Everything went well and now I'm rooted. I am running into a couple of questions now.
1. Whats happens now? I'm rooted now how do i get those nice custom roms onto my phone?
2. I purchased ROM Manager because baked snacks rom says it was necessary for install but i can't get it to install clockwork mod, it keeps saying something about error running privileged commands.
3. How do I go back to stock ROM I'm starting to feel like I might be over my head at this point.
Thanks for your help guys.

I'm in the same boat. The two main reasons for rooting was for a new ROM and to use it as a hot spot (which so far I haven't been able to do.)
ROM Manager gives me the same error message about clockwork. Also, I would like to stop paying the $30 a month for the hot spot, so any help in that area would be appreciated.
Darrell

Keep at it!
loztboy said:
Hey guys I just finished runny simple root OTA edition. Everything went well and now I'm rooted. I am running into a couple of questions now.
1. Whats happens now? I'm rooted now how do i get those nice custom roms onto my phone?
2. I purchased ROM Manager because baked snacks rom says it was necessary for install but i can't get it to install clockwork mod, it keeps saying something about error running privileged commands.
3. How do I go back to stock ROM I'm starting to feel like I might be over my head at this point.
Thanks for your help guys.
Click to expand...
Click to collapse
0. Please read everything before doing anything. My post is a little chaotic, but you should be fine if you read everything first.
1/2. The usual disclaimer: I'm not telling you to do anything. I'm just providing information. I'm not liable for anything you do to you phone.
1. ROM Manager is definitely the easiest way, though the "real way" is to load your ROM of choice on the SD card and then flash it from Recovery (more on recovery later).
1 & 1/2. By the way, you should install Titanium backup from the market five minutes ago. Yes, it is that important. When jumping ROMs, you often have to wipe everything out. Without Titanium Backup, you could end up having to repurchase apps and redownload all of your free ones, losing progress in games and settings in apps, etc. The free version of Titanium Backup lets you back up easily enough, but you want the donate version to prevent restores from taking a few hours of user interaction (Yes, I said user interaction, meaning sitting there and pressing buttons for hours). Once you throw $4.00-$50.00 (you can pick within that range, you get the same product regardless of amount) at Titanium Backup (and wait a day or so to get the license key file), you can do a restore in 15 min without any interaction beyond hitting start (or, more accurately, begin batch process). This app has saved my life time and time again. I literally did my first backup out of curiosity for the app and then totaled my phone in the next five minuets. It even backs up your home screen layout. GET IT NOW!!! YOU WILL HATE YOURSELF IF YOU DO NOT GET IT!!! At least get the free version, because, as stated above, it does backups fine. You (like me) will be scared into paying when you realize that you just wreaked everything and really don't want to spend the next few hours restoring. However, Titanium backup will not function until you get Superuser app working, as detailed in point 2 below.
***EDIT: I forgot to mention that Titanium Backup should work after running this program. It should even fix clockwork for you***
2. There are three possibilities for that error: 1: You don't have the superuser app installed. It dishes out the privileges. If you don't have it (if you do go on to potential issue number two and be grateful), you can install it by downloading this file and putting it on the root of the SD card. Then boot into recovery (I'm sure there is a tutorial for getting into recovery floating around here somewhere, just search the EVO section) and flash the .zip Presto! Superuser app is installed. If you prefer not to go around flashing random packages recommended by strangers on the internet, you can research and download superuser app at the source 2: If you found the Superuser app in the app drawer (the screen with all the applications where you scroll down in alphabetical order and pick the one you want to use), open it. You may have bumped "never give superuser access to this app" (or words to that effect) the first time you opened ROM Manager. If so, it will be listed in the Superuser app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as red. Just have the superuser app forget ROM Manager and then try to flash custom recovery from within the ROM Manager again, being sure to say "Yes!" when it asks for superuser privileges. 3: If you have no recovery to flash superuser from or superuser is installed and ROM Manager is green inside and it still fails, the SimpleRoot failed. If you skipped a step in the rooting process, go back and do that step. If not, just start over and run all the steps from the beginning, Also note that if you accepted the over the air update, you need the OTA version of SimpleRoot, not the original one.
3. Now, about total reversal. I'll be honest: There is probably a way to go back to stock that works without finishing the root process (probably something to do with PC36IMG.zip) files, but I don't know it. The way I would do it would be picking the OTA Stock ROM from this page and flashing it after getting recovery installed at the end of a successful root process. However, then you would have succeed in your original endeavor and would have no need to go back. There is a program here that supposedly does just enough tweaking to the phone to give you the recovery you need to flash back to the stock ROM, but I have not used it myself and therefore cannot vouch for it.
dws51 said:
I'm in the same boat. The two main reasons for rooting was for a new ROM and to use it as a hot spot (which so far I haven't been able to do.)
ROM Manager gives me the same error message about clockwork. Also, I would like to stop paying the $30 a month for the hot spot, so any help in that area would be appreciated.
Darrell
Click to expand...
Click to collapse
If you both succeed in the root process (and I encourage you to persevere, the reward is spectacular), I personally recommend Cyanogen Mod 6. I believe that you can get the nightly builds of CM6 from ROM manager, but the release candidate is likely more stable. I use the RC myself and have never looked back. My battery lasts forever and my phone is never unresponsive. And because the CM6 ROM is based of of Android 2.2 (Froyo), free tethering is built in to the OS and done so rather elegantly, meaning no more dirty hacks for tethering. Just know that if you go that route, though you have the best of the best, you will need to tinker a bit to get everything working. Also, 4G, the FM Radio, and HDMI output are flat out not working in the RC (I'm sure they will be fully functional in the final release, and the not-workedness is a software thing, meaning that the hardware is fine and will come online when you again install a ROM that supports it). On the other hand, with this ROM you can force the phone to roam on Verizon's network when Sprint's 3G speeds are less than desirable.
I'm not sure where to put this, so I'm sticking it here. As soon as you get custom recovery working, you want to backup with Nandroid. The easiest way is from ROM Manager. Just hit "Backup ROM". This backs up not only your setup (like Titanium Backup), but also all the crucial bits that lie underneath and keep your EVOs humming, bits very very difficult to replace. HOWEVER, this is NOT a replacement for Titanium Backup, because it can only restore to the same ROM. If you attempt to restore to a different one, it will put the one you had at the time of the backup back on.
Whichever way you go, I wish the both of you luck. You're entering into the wild and wonderful world of devices that you actually own!

that was a great post im in the same boat as those guys above and im sure we are not the only ones, when you say put the file on the root of the sd card what is the root of the sd card? if i dont know that should i just not even be rooting?
edit
I just downloaded rom manager and i get the same response " an error occurred while attempting to run priviliged commands" i went through the root process and it said i was rooted, i read earlier that to check it i was rooted and nand unlocked that if i checked my hboot and it was 0.76 i was rooted and nand unlocked if i was 0.79 the root didnt work i was .76. Is there a different way to check if my root went through

The root of the SD card is the 'directory' you're in when you plug the card into the computer & you see folders like ".Mail" "Android" "DCIM" etc.
It's up to you if you think you can handle rooting. I used SimpleRoot & it was incredibly easy, but i have been familiar with modding phones for awhile now.

jdjozwia said:
that was a great post im in the same boat as those guys above and im sure we are not the only ones, when you say put the file on the root of the sd card what is the root of the sd card? if i dont know that should i just not even be rooting?
edit
I just downloaded rom manager and i get the same response " an error occurred while attempting to run priviliged commands" i went through the root process and it said i was rooted, i read earlier that to check it i was rooted and nand unlocked that if i checked my hboot and it was 0.76 i was rooted and nand unlocked if i was 0.79 the root didnt work i was .76. Is there a different way to check if my root went through
Click to expand...
Click to collapse
The root of something simply means not in a folder, e.g. on your computer it would be just G:/ (or whatever letter your SD card is mounted to). Just open the SD card and put whichever file you are referencing right there, not in any folder.
By the way, anyone can root, so long as you are willing to learn and willing to take a few risks. As long as you stay well informed, you usually don't break anything. And there is usually a way out, even if you make a train wreak, though it may be ugly. Independent developers (not me; smart people like Cyanogen and Toast who actually make these awesome ROMs and roots) have a better track record for keeping dangerous stuff out than some corporations. ***Cough***McAfee antivirus broke thousands of computers with a defective update***Cough*** Scientia est vox. Knowledge is power. Know what you're doing, and you'll be fine. You will make mistakes (I know I have), but stay sharp and know the consequences, how to go back, who to ask when things go South, and you'll do alright. The community here at XDA is one of the best and most helpful I have ever seen. If you're not totally hosed, someone will pull you out of the fire. It probably won't even be me. I'm no pro. But there is no shortage of pros here at XDA.

so what would you guys say the next step for me is, should i just do the simple root over? how can i check to see if im rooted? and what should i do about this rom manager giving me trouble with flashing the clockwork mod

See Above
jdjozwia said:
so what would you guys say the next step for me is, should i just do the simple root over? how can i check to see if im rooted? and what should i do about this rom manager giving me trouble with flashing the clockwork mod
Click to expand...
Click to collapse
If titanium backup works, you have root. As for Clockwork, please see my first post, where I went over it in detail.

OK well i installed titanium back up and busy box and it looks like im rooted? Im going to try to flash that superuser app tmw i left my usb cord at work so in about 12 hours ill probly be back with more questions
thanks for the encouragement the answers and most of all your time

Cut the cord
jdjozwia said:
i left my usb cord at work
Click to expand...
Click to collapse
It's personal preference, but there is a throughly cool free app called Awesome Drop that lets you send files without a cable. When you use it, files end up in the /drop directory on your phone. If necessary, you can move them out with a program like Astro File Manager.
By the way, Titanium backup shouldn't work without SU app, so I'm wondering if you do in fact have it. Have you looked through the S section of the App Drawer?

Techrocket9 said:
It's personal preference, but there is a throughly cool free app called Awesome Drop that lets you send files without a cable. When you use it, files end up in the /drop directory on your phone. If necessary, you can move them out with a program like Astro File Manager.
By the way, Titanium backup shouldn't work without SU app, so I'm wondering if you do in fact have it. Have you looked through the S section of the App Drawer?
Click to expand...
Click to collapse
I just went through my S' and all i have are the ones that came with the phone no super user but when u say it shouldnt work what should happen when i open the app?

jdjozwia said:
I just went through my S' and all i have are the ones that came with the phone no super user but when u say it shouldnt work what should happen when i open the app?
Click to expand...
Click to collapse
It should complain about being unable to acquire root privileges.
___
An army of pacifists can be defeated by one man with the will to fight.

yeah when i open it it doesnt say that and it says my root access is ok,
I DL astro and when i open it one of the folders is clockwork mod and if i search i find super user app on my sd card when i reboot my phone by holding the down volume it goes to the hboot screen and askes me if i want to update my phone i say no and then when i go to recovery it does not give me the option to flash the super user app. it takes me to android system recovery with four options. At the very bottom it says E: cant open/cache/recovery/command
?

Is one option to flash zip from SD card?
___
An army of pacifists can be defeated by one man with the will to fight.

How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
As for CM6, don't get me wrong, I LOVE CM6, but, Fresh 1.0.1 or the latest Damage Control might be a safer bet. For your first rom CM6 needs more coaxing than you might like. Also tethering is installed by default in the 2.1 roms from those guys and it's (imho) easier and more obvious to use.
Keep at it, there will be times you feel like giving up even after you get past this point, just don't take it too seriously and remember that as long as you are still getting phonecalls your phone is still doing it's primary job, the rest is just icing. Icing that gets more delicious with time, like beer, mmmmmm beer.
Where was I?
Oh yeah, good luck!

Crap, forgot, when someone says "put it on the root of the SD card" the easiest way to do that is hook it up via USB, hit the status tray that says "usb connected" and check the Hard Drive option. Then just copy your file to the new drive that will show up in windows (might pop up automatically depending on your windows settings) and boom, it's on the root of the SD card.
As for the "real" way to flash. Do the above, putting the .zip file containing whatever rom you want (for instance CM6, or Fresh 1.0.1 which you can obtain over in Development forum from their respective posts) on the root of the SD card. Safely remove the device (on windows it will be in your status bar, usually looks like a plug with a green arrow, click it, choose Mass Storage Device and then hit Stop, it will tell you when its done, make sure you have the folder closed before you do this or it will grump at you) and switch back over to Charge Only on your phone. Then power off the phone (hold the power button with the phone unlocked, choose Power Off, then Ok) and hold the volume down button. Then press power, don't let go of volume down but you don't have to hold power, just press it to turn it on. A white screen should come up, let go of the volume button, and one option will be Recovery. Use volume up and down to select it and press the power button to select. It should then boot you into recovery which should have an option to "wipe", you want to wipe dalvik cache, then cache, then factory defaults. Then go back up (in AmonRA that means hitting vol-up and vol-down at the same time), then goto "Flash .zip from sdcard" select it, hit power, select the zip file, power again, power one more time to confirm.
Once it's done you hit Reboot System Now and viola, first boot takes FOREVER so don't fret.

alcaron said:
How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
QUOTE]
where exactly do i type adb shell? when i did the simple root i do not remember replacing my recovery with a recovery of my choice so thats probly where my problem is and i do not know how to check my superuser permissions
Click to expand...
Click to collapse

Techrocket9 said:
Is one option to flash zip from SD card?
___
An army of pacifists can be defeated by one man with the will to fight.
Click to expand...
Click to collapse
no the option i get is update to zip and when i click that it does stuff for me and i cannot choose a file i think my problem lies to not choosing what recovery i wanted?

jdjozwia said:
no the option i get is update to zip and when i click that it does stuff for me and i cannot choose a file i think my problem lies to not choosing what recovery i wanted?
Click to expand...
Click to collapse
It is possible. The program I mentioned earlier (unrEVOked) should install a custom recovery for you. I can't put a link in this post because I'm on my phone, but a quick google search should find it.
An army of pacifists can be defeated by one man with the will to fight.

jdjozwia said:
alcaron said:
How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
QUOTE]
where exactly do i type adb shell? when i did the simple root i do not remember replacing my recovery with a recovery of my choice so thats probly where my problem is and i do not know how to check my superuser permissions
Click to expand...
Click to collapse
If you just did SimpleRoot (i.e. didn't download the android SDK) you probably don't have ADB installed on your PC. So then you'd want to go the terminal route. Search the market for Better Terminal Emulator
Click to expand...
Click to collapse

DISCONTINUED noobs guide to unlocking/locking bootloader, rooting, returning to stock

DISCONTIUED PLEASE READ THE END POST!
FIRST THINGS FIRST I TAKE NO RESPONSABILITY FOR YOU BRAKEING OR BRICKING YOU HARDWARE OF ANY KIND! THIS IS A noob's GUIDE
TO UNLOCKING/LOCKING YOUR XOOM'S BOOTLOADER, ROOTING AND ALSO A GUIDE TO GOING BACK TO STOCK. ALL WHAT I HAVE WROTE HERE
IS THANKS TO ALOT OF PEOPLE ON XDA AND VERIOUS OTHER XOOM FORUMS. THERE IS ALOT OF THREADS OUT THERE WHAT ARE VERY CONFUSING
AND THE IS A SIMPLE GUIDE AND I CHOSE TO WRITE IS TO HELP PEOPLE THAT ARNT USED TO THIS KIND OF ANDROID DEV. THIS IS A WAY FOR
WINDOWS OLY AS I DONT AND WONT HAVE A MAC SORRY
THESE STEPS ARE VERY SIMPLE FOR PEOPLE THAT KNOW HOW TO FIND THINGS ON WINDOWS AND I KNOW IT ISNT VERY EASY BUT IT EXPLAINS ALOT
IN A LOT LESS WAY AS THE OTHERS SO ITS SIMPLE.
(<> = SPACE NOT TO CONFUSE PEOPLE)
NEEDED - MOTODEV DRIVES
TIAMAT UNIVERSAL ROOT
TIAMAT 2.2.2 ROM
ORRIGINAL XOOM 3.0 FILES
THANKS TO EVERYONE - okantomi (ORIGINAL HEL FROM HIS GUIDE)
TIAMAT (FOR ALL THE FILS ROOT, ROMS, ETC)
+ EVERYONE ELSE WHO HAS HELPED
LETS GET TO IT THEN
UNLOCKING/LOCKING MOTOROLA ZOOM BOOTLODER:
1. open files from c:/USER/ android or what ever its under for android SDK/AVD (mine was in programfiles x86)
2. open command prompt
3. copy the adress of platformtools.OR.tools from SDK
4. type in cd<>the paste address
5. then type adb + enter
6. then type fastboot<>oem<>unlock or (lock to re-lock the bootloader)
7. should boot into protocal to ask if u accept all the t&c's
8. accept it all (WARNING THIS WILL FACTORY RESET AND ALL DATA WILL BE LOST)
9. it should reboot with bootloader unlocked!
10. then root!
ROOTING:
A. BEFORE WE START DO NOT FLASH A .ZIP FILE THROUGH COMMAND PROMPT AS THIS WILL CAUSE PROBLEMS!
B. GET THE UNIVERSAL ROOT FILE FROM THE TIAMAT FORUM (http://forum.xda-developers.com/show....php?t=1242241)
c. MAKE SURE U HAVE THE TABLET ON CHARGE!
d. copy the tiamat recovery to your tool files
1. open command prompt as before
2. type fastboot<>reboot<> bootloader
i. when in fastboot you may need to unplug and plug the usb back in
3. type fastboot<>flash<>recovery<>then the name of the file wich is either the name it was of download or i suggest
rename it as 3.2 root.img
4. after this is done the device can be re-started and there you have a rooted motorola xoom
RETURNING TO STOCK:
A. BEFORE WE START YOU WILL NEED THE ORRIGINAL FILES FROM THE MOTODEV SITE
(http://developer.motorola.com/products/software/)(COPY THESE TO THE TOOLS OR PROGRAM TOOLS WICH EVER YOU DIRECTED FROM
ORRIGINALY!)
1. open command prompt and navagate to the tools.or.program tools as before
2. TYPE FASTBOOT<>FLASH<>BOOT<>BOOT.IMG
3. TYPE FASTBOOT<>FLASH<>SYSTEM<>SYSTEM.IMG
4. TYPE FASTBOOT<>FLASH<>RECOVERY<>RECOVERY.IMG
5. TYPE FASTBOOT<>FLASH<>USERDATA<>USERDATA.IMG
6. TYPE FASTBOOT<>ERASE<>CACHE
7. TYPE FASTBOOT<>OEM<>LOCK
THIS WILL ONLY GIVE YOU ANDROID 3.0.1 YOU WILL HAVE TO UPDATE MANUALY AS I HAD TO IT ISNT VERY HAD EVEN THO IS TOOK ME A WHILE
TO LEARN IT.... THIS GUIDE IS FOR noob's AS IT SAYS COZ THERE ARE ALOT OF GUIDES OUR THERE WHAT ARE VERY DIFFRENT AND THIS WAY
WORKED FOR ME SO HOPE IT HELPS
if anyone needs more info just get in touch
EDIT: this has not been updated due to the fact i dont have a XOOM anymore! still pease feel free to contact me via PM if you need any help and i will try my best to help! thanks all

Thanks you for this.

I like it...I'll refer peeps to it.
Edit: Yeah, well, reading it over with the questions from scsa20 especially, who I know is very experienced, leads me to see that perhaps this guide needs a bit more work. But I really like that you wanted to share what you have learned and I agree that there are some big holes in all of the available guides. Maybe you could address the issues and incorporate scsa20's recommendations...then you'd have a really useful guide and help a lot of people.

Thanks for this, but you have to fix some links, as the are now they don't work

RETURNING TO STOCK:
A. BEFORE WE START YOU WILL NEED THE ORRIGINAL FILES FROM THE MOTODEV SITE
(http://developer.motorola.com/products/software/)(COPY THESE TO THE TOOLS OR PROGRAM TOOLS WICH EVER YOU DIRECTED FROM
ORRIGINALY!)
1. open command prompt and navagate to the tools.or.program tools as before
2. TYPE FASTBOOT<>FLASH<>BOOT<>BOOT.IMG
3. TYPE FASTBOOT<>FLASH<>SYSTEM<>SYSTEM.IMG
4. TYPE FASTBOOT<>FLASH<>RECOVERY<>RECOVERY.IMG
5. TYPE FASTBOOT<>FLASH<>USERDATA<>USERDATA.IMG
6. TYPE FASTBOOT<>ERASE<>CACHE
7. TYPE FASTBOOT<>OEM<>LOCK
THIS WILL ONLY GIVE YOU ANDROID 3.0.1 YOU WILL HAVE TO UPDATE MANUALY AS I HAD TO IT ISNT VERY HAD EVEN THO IS TOOK ME A WHILE
TO LEARN IT.... THIS GUIDE IS FOR noob's AS IT SAYS COZ THERE ARE ALOT OF GUIDES OUR THERE WHAT ARE VERY DIFFRENT AND THIS WAY
WORKED FOR ME SO HOPE IT HELPS
Click to expand...
Click to collapse
Will these steps flash back stock kernel ? I using tiamat custom kernel such as Odachi. relock bootloader with a custom kernel will make xoom bricked so these step would flash back stock kernel ???

How about turning off caps lock? Oh, and learning how to spell "break"

I'm going to nitpick this as a person who've done this a few times over (but honestly, not too bad of a guide).
TIAMAT 2.2.2 ROM
Click to expand...
Click to collapse
Although the Tiamat ROM is awesome, this guide is supposed to be for rooting only from what I can see and so pointing out to download 2.2.2 (not knowing if the user is really on the LTE version which 2.2.2 won't do they'll need 2.3.0). Sticking to just rooting is best and talk about the varies of ROMs as an extra if that's something they wish to proceed with.
UNLOCKING/LOCKING MOTOROLA ZOOM BOOTLODER
Click to expand...
Click to collapse
I think you mean "XOOM" and not "ZOOM"
1. open files from c:/USER/ android or what ever its under for android SDK/AVD (mine was in programfiles x86)
Click to expand...
Click to collapse
hmm.... what? Thinking of this from a "newb" standpoint, this step doesn't make sense. In fact, how do we even get to this first step?
4. type in cd<>the paste address
Click to expand...
Click to collapse
lol wat? For starters, you can't simply "paste" in a command prompt. If a newb has never used the command prompt, they'll be wondering how to paste, so might want to better explain how (right click and choose paste or click the little C:\ icon on the top left, go to Edit, choose Paste).
5. then type adb + enter
Click to expand...
Click to collapse
What exactly are you trying to have us achieve here?
6. then type fastboot<>oem<>unlock or (lock to re-lock the bootloader)
Click to expand...
Click to collapse
That came out of left field when the last step said to just type adb without anything else... oh, wait, you want us to type adb reboot recovery, is that right? gez, you should of made yourself clear on that.
7. should boot into protocal to ask if u accept all the t&c's
8. accept it all (WARNING THIS WILL FACTORY RESET AND ALL DATA WILL BE LOST)
9. it should reboot with bootloader unlocked!
Click to expand...
Click to collapse
I lump those both into 1 because they don't actually explain what's going on. What you need to do is press the volume down key to change the selection the volume up to select the selection then repeat
1. open command prompt as before
Click to expand...
Click to collapse
You should already be in a command prompt, if not, reopen.
2. type fastboot<>reboot<> bootloader
Click to expand...
Click to collapse
Don't you mean adb and not fastboot? You can't use fastboot if you're not in the bootloader you know.
i. when in fastboot you may need to unplug and plug the usb back in
Click to expand...
Click to collapse
I have yet to see anyone having to do this tbh
3. type fastboot<>flash<>recovery<>then the name of the file wich is either the name it was of download or i suggest
rename it as 3.2 root.img
4. after this is done the device can be re-started and there you have a rooted motorola xoom
Click to expand...
Click to collapse
This steps is all so wrong, plus the link's broken (http://forum.xda-developers.com/showthread.php?t=1242241 is the real link btw).
Simply flashing the recovery from the Universal Xoom Root won't get you rooted, the proper steps is as follows:
1) Boot into the bootloader (adb reboot bootloader)
2) Flash the recovery to the recovery partition (fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img)
3) Once recovery is flashed, reboot (fastboot reboot)
4) When you get the M logo for the reboot, start pressing the volume down key until you get the option that says Recovery and press the volume up key
5) Flash the zip file containing the root files (choose "Install ZIP from SDCARD" then "Choose ZIP from SDCARD", from there, find the zip file that has the root files that you downloaded from the link posted just above)
I'm not going to touch the restoring to stock, I think I made my point that you should clean up your posts and maybe even checked it (or had someone checked it) before posting it?
(yes, I know I was hard on you but someone gotta do it)
So, yeah, looking over this, it's not really that great of a guide at all because you don't really have anything explained and just have more questions....
And to answer luyenbichta's question, the system.img image will take you out of custom kernel and rom and put you back to stock, once you flash all the images needed you can then issue the fastboot oem lock. Issuing that commend before you have the original images back on will caused you to get an error about the images not being signed, no harm, no foul.

All of this.... AND you can flash HLK75D and save yourself about three hours of manual slow updates!!
Which is available on Motodev, you shouldnt need the link to that by now. Also... no one post after me cause this thread should go buhbye.
scsa20 said:
I'm going to nitpick this as a person who've done this a few times over (but honestly, not too bad of a guide).
Although the Tiamat ROM is awesome, this guide is supposed to be for rooting only from what I can see and so pointing out to download 2.2.2 (not knowing if the user is really on the LTE version which 2.2.2 won't do they'll need 2.3.0). Sticking to just rooting is best and talk about the varies of ROMs as an extra if that's something they wish to proceed with.
I think you mean "XOOM" and not "ZOOM"
hmm.... what? Thinking of this from a "newb" standpoint, this step doesn't make sense. In fact, how do we even get to this first step?
lol wat? For starters, you can't simply "paste" in a command prompt. If a newb has never used the command prompt, they'll be wondering how to paste, so might want to better explain how (right click and choose paste or click the little C:\ icon on the top left, go to Edit, choose Paste).
What exactly are you trying to have us achieve here?
That came out of left field when the last step said to just type adb without anything else... oh, wait, you want us to type adb reboot recovery, is that right? gez, you should of made yourself clear on that.
I lump those both into 1 because they don't actually explain what's going on. What you need to do is press the volume down key to change the selection the volume up to select the selection then repeat
You should already be in a command prompt, if not, reopen.
Don't you mean adb and not fastboot? You can't use fastboot if you're not in the bootloader you know.
I have yet to see anyone having to do this tbh
This steps is all so wrong, plus the link's broken (http://forum.xda-developers.com/showthread.php?t=1242241 is the real link btw).
Simply flashing the recovery from the Universal Xoom Root won't get you rooted, the proper steps is as follows:
1) Boot into the bootloader (adb reboot bootloader)
2) Flash the recovery to the recovery partition (fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img)
3) Once recovery is flashed, reboot (fastboot reboot)
4) When you get the M logo for the reboot, start pressing the volume down key until you get the option that says Recovery and press the volume up key
5) Flash the zip file containing the root files (choose "Install ZIP from SDCARD" then "Choose ZIP from SDCARD", from there, find the zip file that has the root files that you downloaded from the link posted just above)
I'm not going to touch the restoring to stock, I think I made my point that you should clean up your posts and maybe even checked it (or had someone checked it) before posting it?
(yes, I know I was hard on you but someone gotta do it)
So, yeah, looking over this, it's not really that great of a guide at all because you don't really have anything explained and just have more questions....
And to answer luyenbichta's question, the system.img image will take you out of custom kernel and rom and put you back to stock, once you flash all the images needed you can then issue the fastboot oem lock. Issuing that commend before you have the original images back on will caused you to get an error about the images not being signed, no harm, no foul.
Click to expand...
Click to collapse

Have you guys seen the movie "Super 8"?
Yeah, in that movie there is a train wreck a little bit smaller than this guide.

graymulligan said:
Have you guys seen the movie "Super 8"?
Yeah, in that movie there is a train wreck a little bit smaller than this guide.
Click to expand...
Click to collapse
OK, stop piling on...at least he tried to give back...more than I've seen with a lot of people.

Hi guys thanks for all the comment al try help u all with what worked for me as not alot did work for me I'll answer all your questions one by one after each other so bare with me and thanks again for your posative feed back
Sent from my MZ604 using xda premium

luyenbichta said:
Will these steps flash back stock kernel ? I using tiamat custom kernel such as Odachi. relock bootloader with a custom kernel will make xoom bricked so these step would flash back stock kernel ???
Click to expand...
Click to collapse
This wont brick it I have recently returned to stock as I want a ics rom or official software. As fare as im aware you can flash all models with the stock files and it is is quite easy as it says just tips the command from the original folder and DONT type adb
Sent from my MZ604 using xda premium

scsa20 said:
I'm going to nitpick this as a person who've done this a few times over (but honestly, not too bad of a guide).
Although the Tiamat ROM is awesome, this guide is supposed to be for rooting only from what I can see and so pointing out to download 2.2.2 (not knowing if the user is really on the LTE version which 2.2.2 won't do they'll need 2.3.0). Sticking to just rooting is best and talk about the varies of ROMs as an extra if that's something they wish to proceed with.
I think you mean "XOOM" and not "ZOOM"
hmm.... what? Thinking of this from a "newb" standpoint, this step doesn't make sense. In fact, how do we even get to this first step?
lol wat? For starters, you can't simply "paste" in a command prompt. If a newb has never used the command prompt, they'll be wondering how to paste, so might want to better explain how (right click and choose paste or click the little C:\ icon on the top left, go to Edit, choose Paste).
What exactly are you trying to have us achieve here?
That came out of left field when the last step said to just type adb without anything else... oh, wait, you want us to type adb reboot recovery, is that right? gez, you should of made yourself clear on that.
I lump those both into 1 because they don't actually explain what's going on. What you need to do is press the volume down key to change the selection the volume up to select the selection then repeat
You should already be in a command prompt, if not, reopen.
Don't you mean adb and not fastboot? You can't use fastboot if you're not in the bootloader you know.
I have yet to see anyone having to do this tbh
This steps is all so wrong, plus the link's broken (http://forum.xda-developers.com/showthread.php?t=1242241 is the real link btw).
Simply flashing the recovery from the Universal Xoom Root won't get you rooted, the proper steps is as follows:
1) Boot into the bootloader (adb reboot bootloader)
2) Flash the recovery to the recovery partition (fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img)
3) Once recovery is flashed, reboot (fastboot reboot)
4) When you get the M logo for the reboot, start pressing the volume down key until you get the option that says Recovery and press the volume up key
5) Flash the zip file containing the root files (choose "Install ZIP from SDCARD" then "Choose ZIP from SDCARD", from there, find the zip file that has the root files that you downloaded from the link posted just above)
I'm not going to touch the restoring to stock, I think I made my point that you should clean up your posts and maybe even checked it (or had someone checked it) before posting it?
(yes, I know I was hard on you but someone gotta do it)
So, yeah, looking over this, it's not really that great of a guide at all because you don't really have anything explained and just have more questions....
And to answer luyenbichta's question, the system.img image will take you out of custom kernel and rom and put you back to stock, once you flash all the images needed you can then issue the fastboot oem lock. Issuing that commend before you have the original images back on will caused you to get an error about the images not being signed, no harm, no foul.
Click to expand...
Click to collapse
I didn't really want to explain how to flash a rom as that way you quoted didn't work for me. I no I have ****ty grammer and spelling but I did type up quick and step by step ifor noobs as this is very new to me. I have experiance with galaxy s and s2 but not in bootloaders and flashing with command prompt. Thanks anyway and I am gunna edit it shortly. But as I say I am happy to explain more to people
Sent from my MZ604 using xda premium

Tto be hoist all the people that have complain I don't no if its my english which yeah im english but I thinks its pritty straight forward that it how to unlock your bootloader, root your device and return to stock its pritty simple. I didn't add how to flash a custom rom as all the guides I found and used I flashed mine from internal memory not on and sd card. But like I say thanks for the possative comments quys
Sent from my MZ604 using xda premium

Out of curiosity, when you go from root back to stock, does the bootloader automatically lock back, or is that done seperately?
Sent from my ADR6300 using Tapatalk

300k said:
Out of curiosity, when you go from root back to stock, does the bootloader automatically lock back, or is that done seperately?
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
If you tips all the commands in u will need to accept it all again. Well that's what did anyway
Sent from my MZ604 using xda premium

I still can not make this model the root someone help me? Xoom 2 media edition MZ607 wifi 32gb.

Ok I've followed 2 guides which very much the same. I'm having a lot of trouble with this, I'm trying to hard reset my xoom because someone (I don't know who) decided to put on a password lock.
When I type "fastboot oem unlock" it fails.... Please view the images below and please please please help!
Cmd prompt
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Xoom display
Sent from my CM9 Flashed GT - I9100 XDA app-developers app

Bump
Sent from my CM9 Flashed GT - I9100 XDA app-developers app

Orkane1989 said:
Bump
Sent from my CM9 Flashed GT - I9100 XDA app-developers app
Click to expand...
Click to collapse
hey sorry for no reply as i havnt got a xoom anymore if you need any help feel free to inbox me if you need any help op will be updated!

[Guide] -The Ultimate Stock to Custom ROM Awesomeness thread - Noob friendly

Hi there and Welcome to my Ultimate Stock to Custom ROM Awesomeness Thread!
-----
There are still many of people out there who are thinking about Unlocking their Bootloaders, Rooting and installing a custom ROM onto their HTC One X.
I recently did so myself and although I've been a member on XDA for a while now and I rooted my old HTC Sensation I found the process to vary with my HOX.
Now there are many amazing Guides and "How-To's" already out there on XDA but I thought that I'd compile a lot of what's already in those threads and turn all of the yummyness that's already out there on XDA and write this from a first timers perspective.
Disclaimer:- Please note that I'm no expert when it comes to this stuff and I'm not amazing at trouble shooting, if you follow this guide it should turn out fine but if not then this is no fault of my own, you do all of this at your own risk! As I say, it should be fine and you should get through this guide fine. There may be better ways of doing what I'm showing you in this guide but this is how I did it and it worked out okay for me. If you know of a better way the please feel free to state so in the following thread.
-NOTE-
THIS GUIDE IS FOR ICS ROMS ONLY, NOT JB ROMS.
So after that disclaimer relax, read, re-read and take your time and hopefully by the end of this guide you'll have a Custom Rom running on your HOX and without too much panicking and worrying. It's a bit wordy and a bit lengthy but it's an in depth guide.
BEFORE WE START! Go to your HTC One X, Settings, Developer Options and make sure that you've got USB debugging checked! I also always have Fast boot checked in the Power options as well, it's not really important for this guide but I like to know that when I turn my HTC One X off that it is truly off!
Also if you wish you can pop into security and check on 'Allow installation of non-Market apps in Unknown Sources. Again, not really important for this guide but always good to have checked!
---NOTE---
In this guide I talk about using ARHD 9.2, this is because it's the latest version that's been released at the time of writing. Naturally ARHD will be updated but the guide will still be okay to follow.
Lets Get Started!
---
Installing HTC Sync and the Android SDK onto your PC:-
Before we start anything I personally think that it's a good idea to get these two steps out of the way as we're going to need to use these tools a bit later on.
HTC Sync
To install HTC Sync the best way to do this is to follow this LINK and click on the Download link on the right hand side. Follow the Set-Up wizard and get HTC Sync installed onto your PC. Now I'm sure that I don't have to talk you through this step so we'll leave this part now and move onto getting the Android SDK.
Thanks to EddyOS for this recommendation:
EddyOS said:
Better to recommend HTC Sync Manager as that's for the One Series phones...
http://www.htc.com/www/help/htc-one-x/#download
Click to expand...
Click to collapse
So feel free to download either HTC Sync (It's the only version I've personally used), or download HTC Sync Manager as it's designed specifically for the One Series.
Android SDK
Now that you've gotten HTC Sync set-up onto your machine we'll start with the Android SDK, you can find the installation files here: Android SDK For Windows, Click on the "Download the SDK For Windows link.". Let it download the Run the file.
Now to make life a bit easier for us later, when you get to the menu for choosing the Destination of the program we'll alter this for ease of use later. When I'm in set-up it automatically sets the location to
C:\Documents and Settings\James\Local Settings\Application Data\Android\android-sdk
Click to expand...
Click to collapse
We'll change this to:
C:\Android\android-sdk
Click to expand...
Click to collapse
Continue with the install.
Once installed the SDK 'should' open itself, if not then open it from the start menu.
You'll be shown a screen that has a load of options on it and a button at the bottom that says 'Install [X] Packages', Make sure that you have Android SDK and Android SDK Platform Tools checked (See Image).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The program will automatically select numerous other options, it's fine to leave these checked. the installation may take some time depending on your PC etc...
Now that's all finished we can move onto something a little more productive!
Backing Up Your Data:-
When I went to Unlock My Bootloader I read that I'd loose my data and I wasn't too happy about this, I came across this thread '[GUIDE] Full Phone Backup without Unlock or Root', which was a life saver, I'll talk you through some of it just so that we can get a backup made but if you want more concise instructions then make the jump to the thread and have a look!
Now, to backup!
Open your Command Prompt, for those of you who don't know how to do this it's Start > Run... > CMD > Okay. Now that you've got your Command Prompt open we'll need to find adb.exe, which should be at this location
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
as this is where we chose the Android SDK to be located when we installed it earlier!
So to find this in the command prompt type in
cd \Android\android-sdk\platform-tools
Click to expand...
Click to collapse
This will take you to that location. (See Image)
Now that we're in the platform-tools part of your PC in command prompt, it's the perfect time to plug in your HOX via USB to your PC, just choose 'Charge Only' for now.
Now back in CMD (command prompt) enter these values:
adb backup -apk -shared -all -f C:\backup\backup20111230.ab
Click to expand...
Click to collapse
Please note that this will create a folder in your C:\ called 'backup', this is where your backup will exist, also please not that you can call your backup whatever you like, it doesn't have to be 'backup20111230.ab' but I prefer to choose the days date, so mine today would be 'backup20082012.ab', 20th August 2012. Once you've typed this into CMD you'll be prompted to unlock your phones screen and continue backup (See Image)
So unlock your phone screen, choose a password (write this down somewhere as you'll need to to replace the backup onto your phone after we've put a custom ROM onto it) let it start to backup!
Now there is a common issue with the backup's freezing at
com.android.sharedstoragebackup
Click to expand...
Click to collapse
If this is the case for you, just unplug the phone, exit out of CMD, plug the phone back in, get back into cd \Android\android-sdk\platform-tools in the CMD and this time alter the backup command so that it reads:
adb backup -apk -noshared -all -f C:\backup\backup20111230.ab
Click to expand...
Click to collapse
All you've done now is change -shared to -noshared, let the backup continue, hopefully it'll complete!
Now that you've got your backup all safely stowed away on your PC it's time to get down to business! Unlocking your Bootloader!
---
Unlock the Bootloader:-
Did you install HTC Sync at the start? As now you're going to need it!
Navigate your web browser to www.htcdev.com/bootloader and click register at the top, complete the registration process, making sure that you use an email address that you have access to.
Once registered make your way back to www.htcdev.com/bootloader and sign-in.
Once signed-in at the supported devices drop down select 'All Other Supported Models' and click on Begin Unlock Bootloader.
Now before we move onto anything else we're going to want the Fastboot Files, which Cursed4Eva is kindly hosting here: Fastboot Files
Once downloaded, on your PC go to the folder C:\Android and inside that folder create a new folder called fastboot, so you'll have
C:\Android\fastboot
Click to expand...
Click to collapse
Now the fastboot files that I linked to earlier come in a Zip file, unzip it to C:\Android\fastboot, this makes it easier to find it in CMD.
Now back @ htcdev, you've registered and signed in? Good, you've chosen All Other Supported Models and clicked Begin Unlock Bootloader, it'll ask you if you wish to continue, click yes, then the Legal Terms will pop up, just click that you acknowledge both terms and continue with 'Proceed to Unlock Instructions'.
Now click through the instructions until Step 8, ignore everything else.
Now turn off your HOX, now we'll turn on the HOX into the Bootloader, so press and hold down the Volume Down Button and whilst pressing the Power Button, continue to hold this down, the phone may vibrate and bleep a bit but continue to hold it down until you are greeted with a screen that has some options on it, Fastboot, Recovery etc... Now the touch screen wont work so we navigate using the volume buttons & Power Button, press down on the Power Button wile you have Fastboot selected, you'll enter Fastboot Mode with the options HBoot, Reboot, Reboot Bootloader & Power Down. You'll see above these options it'll have Fastboot written and highlighted in Red, leave the phone as it is, just plug it into the PC via USB and that highlighted 'Fastboot' will become 'Fastboot USB'.
Now open CMD, enter
cd \Android\fastboot
Click to expand...
Click to collapse
This will access the fastboot folder in your C:
Now in CMD once you're in the fastboot folder enter this command:
fastboot oem get_identifier_token
Click to expand...
Click to collapse
Now it'll bring up the Identifier Token. (see Image)
Now using your mouse, right click in CMD where it says
<<<< Identifier Token Start >>>>
Click to expand...
Click to collapse
Highlight it to where it says
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
Now on your keyboard, once you've highlighted the Identifier Token press 'Ctrl + C' to copy the Identifier Token.
Now back at the HTC Dev website, scroll down to after Step 10, where it says My Device Identifier Token:, Click in that field and either press Ctrl + V or right click and paste your Identifier Token into that field.
Now Click Submit.
You'll now be taken to a page where you'll be informed to check your emails.
Open up your emails and you'll have an email from HTC and in that email will be an attachment, this will be called Unlock_code.bin.
Download it and place it in your fastboot folder at C:\Android\fastboot.
There will also be a link in the email which will say like "Continue with Bootloader Unlock Procedure" or something like that, Click it.
Back in CMD, you should still be at C:\Android\fastboot, now type in
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Please note the Capital 'U' in Unlock_token.bin, press Enter.
Now look back to your HTC One X screen, it'll have two options on it.
1. YES Unlock Bootloader
2. NO Do not Unlock Bootloader
Select Yes with the volume keys and press the power button, the phone will turn itself off and reboot,
CONGRATULATIONS YOU'VE UNLOCKED YOUR BOOTLOADER!
---
Installing a Custom Recovery (Clockwork Mod) and Superuser Access, ROOTING YOUR HTC ONE X:-
Now that we've unlocked the bootloader we're really close to finishing the whole procedure and getting a custom ROM onto our HTC One seX!
Please note that there will be no images or screenshots from here on as a majority of this is all done on the phone handset bar the flashing of the recovery.img onto the handset.
Follow these links:
SuperSU for Super User Access, download the CWM installable ZIP: http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip courtesy of ChainFire, Please donate to this guy so he can buy some beers
Clockworkmod Touch Recovery Thread: Download the latest Official Recovery
Again, please donate to broncogr and buy this guy a beer or at least hit Thanks.
So now that you've downloaded both files;
The CWM-SuperSU-v0.94.Zip file and the recovery-clockwork-touch-5.8.4.0-endeavoru.img
Right click on the recovery-clockwork-touch-5.8.4.0-endeavoru.img file and rename it to recovery.img, this makes it easier to work with later.
Connect your HTC One X to your USB cable and then to the PC, choose Disk Drive, next, copy and paste the CWM-SuperSU-v0.94.Zip file onto the root of the SD card for your HOX. Once that's on there, change the phones USB connection to charge only.
Open CMD, now get back into the fastboot folder in CMD, do you remember how to do this? It's C:\Android\fastboot then press Enter.
Now start the phone back up into the Bootloader, press and hold Vol Down and press Power Button, once in the Bootloader, once again, select Fastboot and then leave the phone as it is, running in Fastboot USB.
Back to CMD, type in this command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Press Enter. You've just flashed a custom recovery onto your HOX, Once that's finished, type 'exit' into CMD to close the CMD panel.
Back on your HTC One X, using the Volume buttons navigate down to Power Down, once the phone is off, with it still connected to the PC via USB, start it up again into the Bootloader (Vol Down + Power). Once in the Bootloader select Recovery, hit Power. You'll then load up into Clockwork Mod Recovery.
Now you can use either the touch screen or the volume buttons. Navigate to 'Install ZIP from SD Card', hit the Power Button, next select 'Choose ZIP from SD Card'. Now you'll need to scroll right to the bottom of the list to the CWM-SuperSU-v0.94.Zip you placed on the phone earlier.
Click it and it'll ask you if you want to install, select yes install, and let it do it's thing, Then select 'Go Back', Reboot System Now.
Once the phone has shut itself down and restarted, go to the Play Store / Google Market and Install Titanium Backup: Titanium Backup Root. Let it install, once that's finished, start the App on your HTC One X and it'll ask you for Super User Access, grant/accept it.
With the older versions of TiBu (Titanium Backup) You had to go to the problems section and install BusyBox but i believe that it does it automatically now (At least it did for me) So when you start up TiBu You'll see this on screen:
Root Access: OK
Click to expand...
Click to collapse
CONGRATULATIONS YOU'VE ROOTED YOUR HTC ONE X!
---
Making a Nandroid Backup:-
Now that you're rooted and have a custom recovery we'll make a Nandroid Backup, this is EXTREMELY IMPORTANT as it'll act as your fail safe if flashing the custom ROM goes 'Tits-Up'.
Nandroid:To backup the current running rom.
Click to expand...
Click to collapse
When you make a Nandroid backup you are essentially making a carbon copy of how the phone is at that point in time. It doesn't matter if it's a stock rom or a custom rom.
If you are flashing a custom rom onto a phone and it goes wrong or has bugs in it or you don't like it you can restore the Nandroid backup and turn back the clock so that the phone will be as it was when you made the Nandroid backup, as you can see, it's important to do this.
To make a Nandroid backup, turn off your handset, power up into the bootloader, go to recovery, once in recovery there will be the option Backup/Restore, choose backup, let the phone perform the backup - this may take a little time. Once it's finished, just choose restart/reboot phone.
There you have it your very first Nandroid backup!
If it makes you feel a little easier, before flashing a custom rom onto your phone you can transfer the Nandroid backup onto a PC.
Just connect your handset to a PC via USB cable, Disk Drive, then once you can get into the phone on the PC, enter the Clockworkmod folder and make a copy onto the PC of the 'backup' folder.
To restore a Nandroid backup, providing you have the Clockworkmod\backup folder on your phones SD card, enter recovery, and in the option Backup/Restore, just choose 'restore' and off it goes, you've restored the Nandroid backup.
Many people make Nandroid backups before the flash a custom rom onto their phone, even seasoned veterans do this as it's your one fail safe against a disastrous occurrence... messing your HOX up! Some people make them Monthly, Weekly and even a few make them daily!
-NB-
BEFORE PERFORMING A NANDROID RESTORE, PLEASE PLEASE PLEASE READ THIS POST!!!
http://forum.xda-developers.com/showpost.php?p=32084184&postcount=138
Now onto flashing ARHD!!!
---
Installing Android Revolution HD 9.2:-
We're so close to having a Custom ROM on our HTC One X, not far to go now!
Make sure you have at least 35% Battery when you do this! Preferably more, I cannot stress this enough!!!
Pop on over to Mike1986's ARHD Thread here: ARHD Thread Donate to Mike1986 if you like or Thank him as his work is brilliant!
Scroll down to the DOWNLOADS section and download Android Revolution 9.2, boot.img for 9.0.x and Super Wipe.
Next connect your phone to your PC and select Disk Drive, now copy the SuperWipe file and the ARHD 9.2 ROM onto your phones SD card at Root, no need to go any deeper.
Next take the boot.img for 9.0.x file (it's named Flash_boot_9.0.x.rar) and copy it to C:\Android, once the file is there, right click and Extract Here.
Now boot your HOX up into the Bootloader (Vol Down + Power) and then go into fastboot, connect your HOX to the PC to get Fastboot USB.
Now that you're connected, go back to C:\Android and click on the file called
install-boot-windows
Click to expand...
Click to collapse
In the CMD panel it'll ask you to hit any key, so just press Spacebar or whatever, it'll do it's thing, it might ask you to press any key again or it'll just finish.
Back over to your handset, Press the power button to get back into HBoot and then select Recovery.
Once Clockworkmod Touch Recovery has started once again choose the option 'Install ZIP from SD Card', then 'Choose ZIP from SD Card', now scroll down to the Superwipe ZIP, make sure you choose this and not the ARHD ROM, Anyway, choose the Superwipe script and select Yes when it asks you if you want to Wipe.
Once it's performed the wipe, select Go Back and now repeat 'Install ZIP from SD Card', then 'Choose ZIP from SD Card', this time select the ARHD ROM file.
The setup for ARHD will begin, on your handset select next, then select Agree, then next again.
You'll come across a screen that has two check boxes on it, one will say
Wipe Data Partition
Click to expand...
Click to collapse
Select this.
Tweeks: You'll be presented with a screen of Tweeks that can be included into the flashing of the ROM, I personally choose
Improve EXT4 Performance, Force GPU2, Improve Multitasking, Experimental Tweeks and the last option, I can't remember what it is
Click to expand...
Click to collapse
Click Install, It'll finish, then Reboot.
Now don't panic, the first reboot can take up to 5 Minutes to complete, this is why it's imperative to have over 35% battery life as a shut down now can be disastrous!
Once it's rebooted you just have to setup your phone like you would do if it was fresh from the box.
Restore data backup:-
Now all that's left is to restore your data that you backed up at the beginning!
Open CMD, enter
cd \Android\android-sdk\platform-tools
Click to expand...
Click to collapse
Now do you remember where you saved your backup? Good!
Now in CMD enter the location and file name of your backup
adb restore C:\backup\backup20082012.ab
Click to expand...
Click to collapse
Remember mine was todays date! On your HOX screen you'll be asked to enter your password that you chose when making the backup, it'll do it's thing Et Voila!
You've restored all your lovely data, remember, the stuff you had on the phone when it was stock? Nice!
CONGRATULATIONS!!!
YOU'VE MADE A DATA BACKUP, UNLOCKED YOUR BOOTLOADER, ROOTED & INSTALLED A CUSTOM ROM AND REINSTALLED YOUR DATA ONTO YOUR HTC ONE X!!!
I hope that you find this guide useful and that you've managed to fumble your way through it without too much trouble or many hiccups.
If you have any questions or hit any problems please feel free to ask, I'll try to help you if I can.
If this guide has helped you at all then please hit Thanks
GLHF!!!
The-Last-Hylian
---DISCLAIMER---
If I've said anything wrong or given out the wrong info, then please PM me and I'll make amendments.
Also, instead of donating to me or whatever, instead I'd just like to place a link to my site here: Tuffphones - The home of tough, rugged and waterproof mobile phones. (If I'm not allowed this link here please PM me and I'll remove it)

Reserved

nicely written. once my hox is replaced and finally working, i think i shall have to refer back to this

Would it be worth sticky-ing this thread to the top of General?

Great thread mate. I sincerely believe that it deserves to be stickies for everyone to see, because you did a very thorough and detailed Jacob that will surely be helpful to newcomers. You deserve your own praise too. I'm one of those holding back on unlocking my HOX since I'm waiting for an unofficial unlock method and contemplating if it's even worth holding on a HTC device and not just going back to my iPhone which was easier to hack and modify (imo).
Sent from my HTC One X using Tapatalk 2

Better to recommend HTC Sync Manager as that's for the One Series phones...
http://www.htc.com/www/help/htc-one-x/#download

Yes
Well done on this! Super site

Check back to this thread soon!
I'm going to write into my reserved #2 post about how to get the best out of your HOX for gaming!

EddyOS said:
Better to recommend HTC Sync Manager as that's for the One Series phones...
http://www.htc.com/www/help/htc-one-x/#download
Click to expand...
Click to collapse
I mainly choose HTC Sync as it's the only one I've used and I thought I'd only write about what I know so that way I know it's reasonably accurate.
Thanks for the tip + link EddyOS, I'll add that into the OP as an alternative.

Good one! Explained everything required. N00b friendly xD

death__machine said:
Good one! Explained everything required. N00b friendly xD
Click to expand...
Click to collapse
Thanks that was what I was aiming for
I figure that even if something is really complicated to do (which granted not much of what I wrote about is), if you write the instructions with proper and correct grammatical English then people will understand it a lot better.

Hi the last hylians, i currently new with hox, mine previous was sgs. It looks difficult to install custom rom with hox rather than sgs. First i want to know, mine software is 1.29.707.11, can i install all the custom rom or just a particular one with the same software. Thanks
Sent from my HTC One X using xda app-developers app

neoandresk said:
Hi the last hylians, i currently new with hox, mine previous was sgs. It looks difficult to install custom rom with hox rather than sgs. First i want to know, mine software is 1.29.707.11, can i install all the custom rom or just a particular one with the same software. Thanks
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hi there,
As long as you have a decent grasp of the English language and can follow instructions reasonably well then installing a custom ROM isn't too difficult, I'm sure you could muddle through
.707 is that Malaysia/Indonesia?
I believe that you could install a custom ROM that would be x.xx.401.xx as you'd be unlocking the bootloader so theoretically can install any OS on the phone that you like, the region for the OTA therefore wouldn't need apply as you wouldn't get FOTA's afterwards anyway.
It might be worth asking on the Android Revolution HD thread and posting a link to this thread so that way you can get a 2nd opinion.
Afaik you'd be fine however.
T-L-H

This isn't knocking the guide, as it's good, BUT everything you have here is already available online if people were bothered to search for it - especially the bootloader unlocking as HTC have a detailed guide on their own website
You should also highlight the importance of downloading the RUU for your phone before unlocking. If it's not available add a note to proceed with caution
Still, good work

EddyOS said:
This isn't knocking the guide, as it's good, BUT everything you have here is already available online if people were bothered to search for it - especially the bootloader unlocking as HTC have a detailed guide on their own website
You should also highlight the importance of downloading the RUU for your phone before unlocking. If it's not available add a note to proceed with caution
Still, good work
Click to expand...
Click to collapse
Thanks for that, I should mention about downloading the RUU for the phone in case you want to revert back, I was going to add that into the reserved #2 post at a later date, 'How to revert back to Stock'
Yeah I'm aware that there is a lot of info out here on XDA already but like I said at the start of my OP, it's all in different places, some of it is difficult to understand and it's quite fragmented in parts and there isn't really a 'Start-to-Finish' guide out there, or at least not one that I've seen. Even then, people can still find what they need, have access to all the relevant tools but still not be able to proceed, either due to lack of English skills or understanding, intelligence etc... So I thought I'd write it up in real 'laymans terms'.
But as you say, the info's already here for those who've learnt to use the search button

Thanks for repyling, fyi mine is indonesia.
Sent from my HTC One X using xda app-developers app

neoandresk said:
Thanks for repyling, fyi mine is indonesia.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
How did you get on?

Hi mate! at first, thanks for this "noob" tuturial! i think i'm going to try it later.. i have some questions i would like to know before i continue as i don't root/flash roms since my htc hero.. would be thankful if you cared to help me
i have just installed the ruu on mine with 4.0.4 and senses 4.1.
- Will i be able to make a complete rom backup of my actual rom (exactly as it is, with my configs, apps, etc. i user to do it everytime when i was flashing a new rom on my hero so i could revert if anything went wrong or i didn't like the new rom).
- if not, is there a way to reinstall the ruu or the official rom later if i decide for it so i can receive official updates? In other words, can i revert to an "original" state?
And finaly, is there anything that is not working on revolution rom?
thanks a lot!

Hey Porsche. V,
The answer to both of your questions is essentially 'Yes'.
You'll find in my OP one section called 'Backing up your data', depending on which instructions you decide to enter will depend on what gets backed up, take a look at that section and the forum thread that I linked to from that, that'll give you an idea on what to enter into CMD.
It'll be something like
Code:
adb backup -apk -shared -all -f C:\backup\backup21082012.ab
There's a good list of the factory ROMs here, download the relevant one for your handset, RUU etc... then put the phone in fastboot USB and enter into cmd from cd \Android\fastboot
Code:
fastboot oem lock
That'll relock the bootloader, I think that's correct anyway, never done it myself, I know many others have however but yes you can revert back to how the phone is stock, bar the Bootloader saying 'Relocked' instead of 'Locked'.
You can also make a Nandroid backup (always recommended, I should add that into my guide) before flashing any new ROMs, especially when coming from stock
Read these;
1:- http://forum.xda-developers.com/showthread.php?t=1660807
2:- http://forum.xda-developers.com/showthread.php?t=1543604
3:- DEFINITELY READ THIS http://forum.xda-developers.com/wiki/HTC_One_X#Total_recovery_-_flashing_a_RUU_to_completely_restore_your_phone
The ARHD ROM is the most stable ROM there is, everything works, it's the best!
Porsche.V said:
Hi mate! at first, thanks for this "noob" tuturial! i think i'm going to try it later.. i have some questions i would like to know before i continue as i don't root/flash roms since my htc hero.. would be thankful if you cared to help me
i have just installed the ruu on mine with 4.0.4 and senses 4.1.
- Will i be able to make a complete rom backup of my actual rom (exactly as it is, with my configs, apps, etc. i user to do it everytime when i was flashing a new rom on my hero so i could revert if anything went wrong or i didn't like the new rom).
- if not, is there a way to reinstall the ruu or the official rom later if i decide for it so i can receive official updates? In other words, can i revert to an "original" state?
thanks a lot!
Click to expand...
Click to collapse

instaling Revolution rom now! thanks for the tuturial!

[ROOT / TWRP][D851 ONLY][OSX/Linux/Windows] Root/TWRP your TMO G3 with PurpleDrake!

Howdy all!
What's this? Read on, dear reader, to discover the magic that is PurpleDrake.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is this?
This is a utility to easily root your LG G3 (specific models only). It's a fairly foolproof script that includes all the dependencies you'll need for getting your phone rooted easily.
This is the FULL version. This means that it will automatically root, and ask you if you want TWRP installed and a custom boot that doesn't trip the root checker!
Click to expand...
Click to collapse
Who made this?
This root is a collaboration between myself (IOMonster), jcase, and autoprime.
Special thanks also to beaups for some initial guidance looking at the vulnerable application.
Thanks to @Shelnutt2 for the security-disabled boot.img
Thanks to @Dees-Troy for the TWRP image!
Click to expand...
Click to collapse
Is my phone compatible?
The new LG G3 models each are slightly different with regards to rooting and unlocking.
To see a matrix of which LG G3 phones are compatible with this root, please see this Google Docs spreadsheet that we've compiled.
When you run this program, your phone will reboot and run a test to see if it's compatible. If the application succeeds, it'll let you know that it's able to permaroot you. If not, it'll fail gracefully and reboot you back to normal Android without having changed anything.
Please note that this version is currently only compatible with the T-Mobile D851 version of the LG G3. For other phones, we suggest you look for the LITE version of PurpleDrake.
Click to expand...
Click to collapse
How do I use this?
WE NOW SUPPORT WINDOWS! YAY ME
To start, for either platform you'll need to scroll down to the download section and get the file.
Ensure that your phone is in ADB mode (PTP Mode for everyone but Verizon. Verizon users need to be in "Internet"/"Ethernet" mode)
Linux Instructions (in a terminal!)
Extract the file you downloaded...
tar xvf ~/Downloads/PurpleDrake-TMO_VERSION.tar.gz
Mark the application as executable, and run it!
cd PurpleDrake-TMO
chmod +x purpledrake_linux.sh
./purpledrake_linux.sh
OSX Instructions (just a bit easier)
Extract the file you downloaded
Double-click on "purpledrake_osx"
Windows Instructions
Extract the file you downloaded
Double-click on "purpledrake_windows"
The application will guide you through all the steps you need.
You will still need to install SuperSU from the market after installing PurpleDrake. This pack does not include one.
If you choose to install the custom boot.img, your phone's root checker will not be tripped and your phone will show as UNROOTED.
After, be sure to check @autoprime's post for how to disable OTA upgrades! here : http://forum.xda-developers.com/showpost.php?p=54254111&postcount=2
Click to expand...
Click to collapse
But, what if I don't want to run your script to root?
Well then, I'd be a little hurt, but you can still do everything the script does manually.
Download the package, and extract it. Open a terminal in the main folder of the archive and run these commands:
Code:
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
That will perma-root you, however there's no protection from doing something stupid or the phone being incompatible. Please be careful!
Click to expand...
Click to collapse
Where do I get this?
WINDOWS/OSX/LINUX VERSION OUT NOW!
- Fixed Windows support
- Fixed OSX ADB issues not detecting phone first try
- Fixed race conditions leading to errors permarooting
- Added 64-bit Linux ADB
Code:
[url]http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-TMO_R03.tar.gz[/url]
Old version here... (OSX/Linux only)
Code:
[url]http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-TMO_R01.tar.gz[/url]
Please DO NOT mirror or re-upload the PurpleDrake software to your own site, or any other file host.
If you need drivers for Windows (thanks @autoprime for having these handy!):
Verizon Drivers: http://downloads.codefi.re/autoprime/LG/LG_G3/LG VZW_United_WHQL_v2.14.1.exe
Everyone Else: http://downloads.codefi.re/autoprim...leDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe
Click to expand...
Click to collapse
Help, it doesn't work!
Post here, let us know what happened and we'll try to help you. DO NOT private message us on XDA or on IRC asking for help. We will not assist privately.
Most questions if not answered here can be answered on #lg-g3 on IRC in Freenode.
Click to expand...
Click to collapse
Thanks so much! How can I show my appreciation?
Since this was a collaboration project, proceeds that are made from this root will be split between amongst us so we can purchase a Sprint test phone to root (as it's currently not rooted).
If you'd like to donate to us, click the "Donate to me" button on the left sidebar under my name, and be sure to enter a comment to let us know that you're donating towards the PurpleDrake project.
Thanks again!
Click to expand...
Click to collapse

FAQ:
Q: I'm running the Windows .bat as administrator and it's closing/not working.
A: There is no need to run the .bat as admin. Just double-click and run.
Q: I get the "Windows cannot find '.\assets\windows\bin\mintty.exe'." error.. watdo?
A: Try just double-clicking on the .bat instead of running as admin.
Also make sure the script is extracted properly first before running.
Q: I [used Flashify and] am stuck in fastboot.. how can I get out?
A: Be cautious using Flashify as it seems it's not working right.. or people are hitting the wrong buttons with it.
HERE are the stock TMO D851 partitions.
Use fastboot to flash recovery(TWRP or stock) and stock boot. This will install TWRP and fix booting into rom.
If on Windows you will need fastboot drivers. Use Google to find fastboot binaries and drivers.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
The commands to flash TWRP manually instead of using flashify is below.
Place TWRP on the root of your internal /sdcard/ using MTP, downloading it directly to phone or using ADB push.
Code:
adb push name_of_file.img /sdcard/
adb shell
su
dd if=/sdcard/name_of_file.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Disable OTA:
Open LG Hidden Menu (3845#*851#) --> WLAN Test --> OTA Setting --> OFF
*Replace "851" with your devices model number, 850, 852, 855 etc...
The first D851 update has been released (10M). Bootloader remained unlocked. It would appear future OTAs will be safe to take AS LONG AS YOUR PHONE IS NOT MODIFIED! If you have flashed TWRP or installed xposed or modified /system then you need to restore any changes made or flash stock firmware (tot/kdz) before taking OTA.
If using a non-tmobile g3 I would be hesitant about taking OTA updates. An OTA may update the boot stack to block Bump!
EFS Backup:
Code:
[FONT="Arial Narrow"][B]Backup EFS after jailbreaking your G3. EFS is split into 2 partitions modemst1 and modemst2.
img files will be on root of internal sdcard. Save the .img files somewhere else besides the sdcard... email, cloud, etc..[/B]
DO NOT FLASH OTHER PEOPLES EFS OR FLASH YOUR OWN BACKUPS ONTO ANOTHER PHONE.
THIS WILL BREAK EFS ON THE PHONE YOU ARE FLASHING TO. EFS BACKUPS ARE FOR THE PHONE THEY CAME FROM ONLY.
I have made a new thread on EFS backup and restore which can be found [URL="http://forum.xda-developers.com/lg-g3/development/efs-lg-g3-efs-backup-restore-t2907329"]HERE[/URL].
[/HIDE]
[B][SIZE="5"]Restoring Stock / Remove root flag:[/SIZE][/B]
[HIDE]
Download the tmo .tot file and use lg flash to restore it to stock. itll format everything on internal sdcard so backup anything u may need off it.
T-Mobile firmware can be found [URL="http://downloads.codefi.re/wolfgart/LG_G3/D851"]here[/URL]. Thanks to [user=608699]@wolfgart[/user] for the files and [user=1157052]@thecubed[/user] for codefire hosting.
*Step by step picture guide - [url]http://imgur.com/W83hMPE[/url]
install the drivers.
put phone into Download Mode (power off. unplug USB. pull battery. put battery back in. press/hold Volume Up then plug in USB cable.)
In Windows Device Manager set the phones serial COM port to #41. (*see picture guide for help)
Install [URL="http://downloads.codefi.re/autoprime/LG/LG_G3/Setup_LGFlashTool_1.8.6.527.zip"][B]LG Flash[/B][/URL]. In "C:\LG\LG Flash" folder delete megalock dll. Replace with .dll below.
new megalock dll - [url]http://bit.ly/1cQADXm[/url] (this site includes a "download manager.. UNCHECK THE BOX before downloading dll file.)
Run LG Flash in the "C:\LG\LG Flash" folder. Select korean factory if asked.
When LG Flash opens you will see a box to select firmware and dll.
Select [URL="http://downloads.codefi.re/autoprime/LG/LG_G3/LGUP_8974.dll"][B]LG Flash .dll[/B][/URL]
Select (.tot)
Hit OK (*see picture guide for help)
Hit yellow start button. If you get Milkyway error click ok. LG Flash will then run a crc check on the tot file. Takes a bit.
After crc check finishes unplug the phone. plug phone back in. it should now be seen in LG Flash and start flashing.
Phone will reboot when finished. You may end up on a screen with s "2"... let it sit there for a minute or two.
If stuck on "2" try unplugging the usb cable from the phone.. wait 10 seconds.. then plug the usb cable back in. now wait 30 seconds and hopefully it changes to a "3"
Once the phone says "3" you can unplug the USB.. remove the battery and plug back in.. boot back up... you are now 100% stock.
[/HIDE]
[B][SIZE="5"]PurpleDrake YouTube Videos:[/SIZE][/B]
[HIDE]
[url]https://www.youtube.com/watch?v=wJtz51KgxjM[/url]
[/HIDE]

And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855

Tectas said:
And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855
Click to expand...
Click to collapse
Hoax? What?
This pack is ONLY for the T-Mobile G3 which has an unlocked bootloader out of the box.
D855 support is NOT included in here. There will be a separate thread when we have an unlock for the bootloaders of the rest of the G3 family.

Tectas said:
And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855
Click to expand...
Click to collapse
There is no boot loader unlock..where ever you read this is misinformed...the T-Mobile variant ships boot loader unlocked, it is the only one so far to be shipping unlocked.

Sweet

thecubed said:
Hoax? What?
This pack is ONLY for the T-Mobile G3 which has an unlocked bootloader out of the box.
D855 support is NOT included in here. There will be a separate thread when we have an unlock for the bootloaders of the rest of the G3 family.
Click to expand...
Click to collapse
I'm aware of that and sry it wasn't meant offensive or to put this one down, autoprime, did imply at the bounty thread, that you as well managed to unlock the bootloader, at least at the beginning, that's what I'm referring to, sry that i said it the wrong way, was a bit disappointed, which for sure isn't your fault or the one of this tool, it's still great progress you made.
Gesendet von meinem LG-D855

I wish the international G3 D855 will be unlocked too
Sent from my LG-D855 using XDA Premium 4 mobile app

Great glad to see this released thank to all that is involved
LGG3 and beyond

All my family is sleep in the room with my Mac will be running asap bright and early. Thank you for your hardwork

Thecubed, autoprime, shelnutt2, jcase, and whoever else....thanks for this. Truly appreciated! Can't wait for Windows support. :Cheers:
Sent from my LG-D851 using XDA Premium 4 mobile app

Plans to support recovery for D855 in the near future?
Need to know to sell or not the G3 ?

What the hell software compatible with a mac that's a 1st whoop whoop well done guys and thanks for the hard work

Yeah great time to be a Mac owner

I have a feeling this treads about to turn in to a "when will this version be supported" topic :/
LGG3 and beyond

Success!
1. THANK YOU!
2. It didn't work the first time around, temproot worked but permaroot did not. Maybe it had to do with the fact that I was reading this forum while it was waiting for my input... I can't see how that would have made a difference but whatever. [[ Edit: It worked the second time running, I just followed the instructions immediately - no problems. /Edit ]]
3. Just a reminder for Linux users ... you have to add udev rules as described here: http://developer.android.com/tools/device.html ... and when you are done with that, also run:
$ sudo service udev restart; sudo killall -9 adb
4. My G3 would only connect to my laptop (Ubuntu 14.04) when it was in PTP mode. MTP or Charge Only did _NOT_ work... Only PTP.
5. THANK YOU AGAIN! You devs rock!
Frank.

Same as the guy above didn't work the first time but worked perfect the second! OSX here.

@ OP
http://forum.xda-developers.com/lg-g3/general/s-carrier-specific-g3-threads-t2818549

I keep getting no such file or directory, going to re download drivers and see

@thecuba not telling you what to do but maybe put this on T-Mobile thread as well http://forum.xda-developers.com/tmobile-lg-g3/development
Hope you don't take it the wrong way

My adventures with my ZenWatch over the weekend

I spent a lot of the weekend trying to root my Zenwatch (on 4.4.2w), or get a custom recovery working. Here's what I have tried and found out so far. They locked it down pretty damn well.
Unlocking bootloader and accessing recovery
Go to Settings -> About -> Press Build Number 7 times -> Swipe right, Developer Options now shows under About.
Theres a few different options including an Asus utility to check sensors and such.
To get into recovery or fastboot, you need to active ADB Debugging, unplug the watch than plug it back in, then run "adb reboot recovery" or "adb reboot fastboot"
To unlock bootloader, you need to push the reset button on the back to select.
In recovery, swipe right to left to show screen, up and down to select, and left to right to select.
My Findings so far
The kernel source and ROM source are not available anywhere.
There is no way that I can find to get root. I even went as far as loading towelroot onto the watch through adb install, but it just hangs and eventually closes.
There is no way I have found to build a custom recovery with CWM or TWRP.
There is no way I have found to dump the boot or recovery partitions.
There is no su binary preinstalled. Attempting to link a su binary has come up null.
dump_image binary is not installed, nor can you get it to install.
Trying to install any packages through stock recovery gives signature error.
Trying to use dd command to dump boot or recovery ends with "permission denied"
Trying to use "fastboot oem saveprt2sd recovery -n recovery.img -a" ends with "invalid page size". Same with trying to dump boot in this fashion.
Trying to boot either the LG G Watch or Samsung Gear Live unsecured boot images comes back with "(remote) dtb not found" (No surprise here, but it was worth a shot)
fstab is root only.
/dev tree is root only.
all init.asus scripts are root only.
You can install packages with "adb install" but all the standard root gaining apps stall or force close. Towelroot seems to try, but locks up after hitting "make it r4in." trying to change the modstring on v3 (with triple tap title) does not provide a field to change.
Kernel command line is root only.
I browsed EVERY file on my watch hoping to find a hole that I could build off of, but alas, I had failed.
Even trying to do "adb backup" results in "Confirm on Device," and closes immediately afterwards, with no confirm.
I believe that unless they release either the kernel source or the full ROM source, we are unable to root or modify any options.
Which really sucks, because the "OK Google" screen is REALLY F****** BRIGHT.
if anyone has success, please share

I thought I'd try installing one of my own apps and see what happened. It installs okay, but it crashes immediately. I'm guessing it's because I'm using something that's not supported, probably sound or Webkit (the app displays an HTML tutorial the first time it's run). I haven't had time yet to run it from the debugger and see what's going wrong.

I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/

dgjenkins said:
I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/
Click to expand...
Click to collapse
To build a custom recovery, you need to pull the existing recovery or boot partition off of the device and pull partition information (fstab, which is not readable by user on this device) and the build.config information (which is also not readable by user), or pull the fstab.anithias and build.config from the running system (which again is not accessible to the standard user account).
Without that information, you can't build a custom recovery. I've been attempt this for almost 2 weeks now, and its locked down pretty well. The G Watch and Gear Live allowed access to the needed files, but Asus did not with the ZenWatch.
If anyone is willing to risk bricking their watch (by getting past the dtb error when trying to boot the LG G Watch or Samsung Live recovery images, which is a long shot in itself) to get the openRecovery/CWM/TWRP to install and work to the point of getting ADB working through recovery mode, I can do the rest to build the recovery.
I just dont want to risk bricking mine quite yet, as the google play store was out of stock the last time I checked to purchase a "testing" watch.

@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip

CSX321 said:
@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip
Click to expand...
Click to collapse
Kernel source code
Sent from my SM-G900P

@z3nful And an ota? Would it be usefull?
OTA LWX48S

I haven't had a chance the last week to work on this with the holiday season going on and having to run my store. When I get a chance to get back to it, I'll let you guys know what I come up with

I started trying to build the kernel yesterday, but I'm not getting far yet. I've been a developer for over 30 years, but most of my Linux/other UNIX experience was over 10 years ago, and I've forgotten a lot.
I've tried a couple of different compiler versions, but I'm pretty quickly running into different issues with either one. I'm not sure what version Asus used, but it's apparently not either of the ones I've tried. Also not entirely sure what configuration to use. I'm using the 8226 configuration now, because there's no 8026 configuration in the source archive. I don't know if that's suitable or not.
All-in-all, I may not be out of my depth, but I'm out of my area of experience, at least. Any tips, @z3nful?
Edit...Is there any useful information in the OTA zip file? It's available. Partition info or a boot image or something?

@z3nful and @CSX321 - Any luck moving forward on this? I'm not a programmer, but I'd be glad to offer any assistance if needed!

btonetbone said:
Any luck moving forward on this?
Click to expand...
Click to collapse
No progress here, I'm afraid. I think I just don't know enough about this environment to do it, without devoting a lot more time to learning.
I've also lost some motivation, because there doesn't really seem to be anything I need root for on the watch. About the only thing I would do if I had it is delete a couple of apps, but since Mini Launcher lets me hide apps, I don't care so much about actually deleting them.

Has anyone had success with adb push? It seems the system is read only and doesn't allow for pushing files. Is root required?

Asus is good at locking down their devices, requiring you to register it with them to get an app to unlock it (you also acknowledge that by downloading the app you are voiding your warranty). I really wouldn't be surprised if they did the same thing with this watch and just haven't released the unlock app yet.
I am kinda disappointed to see this sort of thing from a device licensed by Google. It's like the exact opposite of the Nexus line.

@z3nful Just some helpful links, thought I could help a wear user out (I have the G Watch)
Kernel --> https://android.googlesource.com/kernel/msm/+/android-msm-anthias-3.10-lollipop-wear-release
Also, Gohma ROM for gwatch includes a boot img that auto roots android wear. (http://forum.xda-developers.com/g-watch/development/rom-gohma-2-0-12-15-2014-t2974052) Named rboot.img, I think it might be worth a shot to run "fastboot boot rboot.img" to see if it does anything.

Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.

I tried, no luck.. Gave the same "dtb not found" error.
Here is a thread related to DTB in boot images: XDA Topic 2428117
Attached is the rboot.img if anyone wants to see if they can modify it to pass whatever DTB issue is making it fail, if that's even possible. I will dig a little bit deeper once I get out of the office.
The error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rboot.img, zipped:
View attachment rboot.zip
Ignore my sig, it is several years out of date
Regards,
weasel5i2
Doc Ames said:
Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.
Click to expand...
Click to collapse