Develop Bugs

[GUIDE] *Rooting the Xoom for Dummies*

***Xoom Rooting Guide for N00bs***​
Hello Xoom Dev community! Sorry. I know you're thinking, "Man! Not another Xoom root guide?!". Lol. But I wanted to make this, so, here ya go...
***WARNING***
-This will erase everything on your xoom. Its like flashing flashing back to stock because of the unlocking process. So BACK everything up before continuing via USB, or your preferred backup app-
**Also, this Tutorial is for the 3G version ONLY. The Wifi model is different and uses an incompatible boot.img. Once again, ONLY FOR 3G MODEL**
Ok. So, rooting the Xoom isn’t really that “hard” of a task. I’m a n00b as well, so I did have a little difficulty doing it. Only because this method requires you to use adb, the command prompt, etc…
Well, I wanted to make a guide that should be ‘n00b-proof’. LOL. It’s really super simple.
**Bofore you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development --> USB Debugging**
Alright, you’re going to need some tools to get it done. First of all, download the Xoom USB drivers. Either get them from motodevs.com --> http://developer.motorola.com, which requires a free membership; or get them from the Motorola/Support site --> http://www.motorola.com/Support/US-EN/Consumer-Support/TABLETS/MOTOROLA_XOOM, and download the ‘motohelper’ program. I prefer the drivers from the dev site because they’re just stand-alone drivers. Motohelper is an actual app that “keeps your drivers up-to-date”. Both will have the same version of drivers, i.e. 4.9.0.
Now that we have the drivers installed plug in your Xoom to make sure all drivers/services were detected/installed properly. If you’re good, next we will need the Android SDK, if not already installed. To properly install it though, you must download the Java JDK from --> http://www.oracle.com/technetwork/java/javase/downloads/index.html, and click the “Download JDK” button. Choose your OS, and install.
**NOTE** If you’re running Vista/7 x64, Android SDK will not detect the REQUIRED Java kit installation. Yes, JDK has been properly installed, but the Registry doesn’t read the installation right. So, to get around this issue, either go here --> http://codearetoy.wordpress.com/2010/12/23/jdk-not-found-on-installing-android-sdk/, for a tutorial that gets it detected by modifying the Registry. Or, do what I did, and just download the .zip installer of Android SDK. I’m writing this guide based on the ‘zip type’ of installation, but I’m sure the directories are identical besides having SDK installed in your Program Files folder.
Whew! Now, either extract the SDK to a directory of choice, or point your mouse to the Program Files\Android SDK\ directory. There will be some folders like platforms, platform-tools, tools, etc…
Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
**NOTE** When I first installed SDK, I ran the emulator.exe from within the ‘tools’ directory. This updated everything, but I’m not sure if it matters for this tutorial?
Ok. The “hard” part is over. We should be all setup, and ready to type some commands! What you’ll need to do now is, open up a command prompt i.e. cmd. And do a cd --> to whatever path the ‘tools’ folder is in. For example, mine is in a Xoom folder from my documents. So the command would be “cd C:\Users\%name%\Documents\Xoom\android-sdk_r10-windows\android-sdk-windows\tools”. Without quotes of course.
You should now be pointed at the ‘tools’ folder from cmd, and next we can start the commands!
CHECKPOINT
- Xoom drivers installed, xoom is plugged in, & detected properly. To make sure, open Device Manager to see if the “ADB Interface” is there. **Sorry, I’m not sure ADB is in Device Manager before, or after rooting** Can’t remember! As long as you don’t have any ‘device is not properly installed’ pop-ups, you should be good!
{
"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"
}
- Android SDK is configured right, and cmd is pointed at the correct location.
-USB Debugging option is checked. Check above for instructions
***This is obviously, from Koush’s site, so give him some kudos please ***
***I will bold all commands, and try to put in ‘n00b’ terms***​
Type the following commands in CMD… after you have moved the “XOOM root” files.
1. Download the XOOM root zip.
2. Unzip the package, and
3. put the 3 files inside the same ‘tools’ folder we’re running cmd from!
4. adb reboot bootloader (skip the next 3 steps if you have already unlocked your Xoom via fastboot, which is another guide on XDA that just lets you unlock the Xoom. It’s not rooting.)
5. fastboot oem unlock
-You have to accept the terms by pressing the vol - down key, and then select 'accept' by pressing the vol + up key.
6. -wait for the Xoom to reboot completely.
**You may have to re-enable USB Debugging mode again for the next command**
7. adb reboot bootloader
8. fastboot flash boot rootboot.img
9. fastboot reboot
10. -wait for the Xoom to reboot completely.
11. adb remount
12. adb push su /system/bin/
13. adb shell --> You will now be mounted within adb shell…
14. ln –s /system/bin/su /system/xbin/su
15. chmod 4755 /system/bin/su
16. exit --> This gets you out of adb shell…
17. adb push Superuser.apk /system/app/
That is all! Now, unplug the Xoom and reboot it.
To verify your root is working properly, download an app such as, Cachemate, or any other that requires Superuser access. Open up Superuser to see if that apps’ rights were saved successfully.
Yay! Root access! But honestly, this tutorial will be outdated and inefficient, once the source code is out and then we’ll have a oneclickroot method. Which is way better! Until then, I hope anybody who is a little confused about the process benefits from this guide.
Happy moddin’!

good guide.

Thanks, I like this guide and made rooting my xoom super easy.
One other important initial step is to make sure USB debugging is enabled:
Settings>>Applications>>Development>>USB debugging

Hey, thank you guys for your kudos. I appreciate the feedback.
@jtseidner, Man you are a genius! That is a very important step that I left out! You couldn't root the Xoom without that option. I'll add it to the tutorial.
Thanks!

14. ln –s /system/bin/su /system/xbin/su
Its saying In: not found.. help

Hey. The command is all lower case so it would be "LN" not "IN". Just type it in all lower case. The rest of your command is ok. Simple syntax error, that's all. Let me know if it works and if you have any other concerns.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

ok i got to step fastboot oem unlock #5 and the screen shows choices. i accidentally chose device unlock operation aborted, the down arrow. now it wont go off this text screen. how can i reboot this xoom?

disregard, i pressed the volume UP and power, tablet is rebooting now.

Hey worked great for me only problem is that it wiped my xoom...probably said that somewhere in the instructions and i just missed it. Anyway Thanks.

Yeah sorry. I should put that on the tutorial. But im pretty sure any method of rooting the xoom will wipe it. Only because you have to unlock the device. Until we receive clockwork, this is the only way. Im glad you were successful with my guide though!
Thanks.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

Screen Stuck At Starting FastBoot Protocol Dont Know How Long This Screen Stays Up Or Have I Done Something Wrong I Downloded FastBoot Already And Put It In My Sdk Folder Can Someone Pleas Help Me

You shouldn't be stuck at fastboot. It probably means that your xoom wasn't fully rebooted into the bootloader. Fastboot is a program located in the tools folder and ran from your command prompt. So have your xoom loaded up and connect the usb. Make sure usb debugging is on. Open your cmd and point to that tools folder. Type the first command from step 4, adb reboot bootloader. This will restart your xoom and I believe you'll see the 'dual core technology' logo. Just wait a minute after step 4. Now try the remaining commands, but be sure to wait for reboots before typing the next commands. I have a note after each step that says wait for reboot. Please let me know if you have any further issues.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
This is utterly confusing.. can you explain in-depth please. Don't copy, but leave it as is; copy but replace the file, or replace it completely. Only three options.
for example... it will show adb.exe and adb.exe(2) - is that what you wanted?

misdirection said:
Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
This is utterly confusing.. can you explain in-depth please. Don't copy, but leave it as is; copy but replace the file, or replace it completely. Only three options.
for example... it will show adb.exe and adb.exe(2) - is that what you wanted?
Click to expand...
Click to collapse
Nevermind.. I was able to root my Xoom!!

Great! Sorry if it was misleading. Im not the best writer at times. All I meant was just to copy everything from the platform folder over to the tools folder without replacing, or writing duplicate files. Hope that makes sense?
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

Is this the stock .img or is it the tiamat one? I used other root guide but I'm interested in flashing this .img if it contains the stock kernel.
Sent from my Xoom using Tapatalk

This is the stock .img and this guide will work for the original stock firmware, along with the new 3.01. But this guide is ONLY for the 3g version of the Xoom. If you have any further questions please ask away.
EDIT: Sorry. I didn't fully understand your post. This guide doesn't include any kernels. It assumes you are coming from a stock system. If you are already rooted, and want to return to stock, you would probably have to do a complete restore, and re-lock your device. Then, if you just want the stock kernel; root with this guide, or similar. You can't flash the tiamat kernel unless you're already rooted. This tutorial just gives you root access. Im sure there is a way to go back to the original kernel, without having to restore, but I don't know where those instructions are? Poke around and you may find it. But you'll probably have to start over. Hope this helps!
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

Thanks. I have a WiFi only version and used another root method which included tiamats kernel. Currently having some reboot issues with the kernel so I was hoping to find a stock kernel that I can use.

Ok. Well, you can use this method to root, but the xoomroot files are different. This tutorial was based off the 3g only, and maybe ill add the wifi option as well.
Here's are great guide from xaositek for the wifi version...
http://forum.xda-developers.com/showthread.php?t=1010568
And I'm pretty sure it doesn't include the overclocked kernel.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

http://mirror1.kanged.net/motorola/stingray/xoomroot.zip
seems link are broken

help with unlocking bootloader...

I have a LTE gnex. I am having problems getting my bootloader unlocked.
If I attempt to use fastboot commands at all I get the error 'fastboot is not recognized as an internal or external command, operable program or batch file.'
If I attempt to use adb devices while I am in fastboot it says "List of devices attached." If I use the adb devices command when my phone is turned on it lists my device like normal.
I feel like I am so close, but yet so far. Any ideas?
EDIT: I'm attempting this on XP, and I am on 4.0.2

I am no expert in these matters, but a few things come to mind:
1) have you got all the proper drivers installed?
2) in the cmd prompt, are you in the directory where fastboot.exe is located?
Have you followed this thread? I'd recommend downloading superboot, extract the contents, go into that folder, and then use: 'fastboot-windows oem unlock'. That should definitely do the trick. Good luck.
EDIT: I don't specifically know all the differences for the GSM/LTE/CDMA versions, but the above should be okay for all versions. To root, and install recovery, on CDMA versions, check out this google+ post.
EDIT2: Also, this thread may be worth looking into.

Assumptions:
- your drivers are loaded properly
- file names are: adb.exe and fastboot.exe
1) open the folder w/ ADB and Fastboot located in them.
2) shift + right click in any open space in the folder - choose: "open command window here"
3) type in (minus the quotes): "adb reboot bootloader"
4) the phone will reboot in the bootloader screen
5) type in: "fastboot oem unlock"
6) phone will ask you are you sure? - use the volume buttons to make the selection say "yes" and press the power button.
7) the phone will unlock and restart. the restart can take as long as 10 minutes or a tad bit longer... do NOT be alarmed!
if this doesnt work for you... either your drivers arent fully installed or your adb/fastboot programs are duds.

aldouse said:
Assumptions:
- your drivers are loaded properly
- file names are: adb.exe and fastboot.exe
1) open the folder w/ ADB and Fastboot located in them.
2) shift + right click in any open space in the folder - choose: "open command window here"
3) type in (minus the quotes): "adb reboot bootloader"
4) the phone will reboot in the bootloader screen
5) type in: "fastboot oem unlock"
6) phone will ask you are you sure? - use the volume buttons to make the selection say "yes" and press the power button.
7) the phone will unlock and restart. the restart can take as long as 10 minutes or a tad bit longer... do NOT be alarmed!
if this doesnt work for you... either your drivers arent fully installed or your adb/fastboot programs are duds.
Click to expand...
Click to collapse
^^^^^^This.....beat me to it LOL. This should work for ya just fine. Just make sure tour fast boot file is in the same as tour adb file. Hope ya her it man. It can def get frustrating
Sent from my Galaxy Nexus using Tapatalk

When I shift + right click I don't have any option to open a command window...well this is frustrating.

twiz0r said:
When I shift + right click I don't have any option to open a command window...well this is frustrating.
Click to expand...
Click to collapse
just open command prompt manually and then go to folder. Eg 'start' -> 'run' -> type 'cmd' and hit enter. Then cd c:\path to folder\ etc.
edit: plus, i gave you a few links to other threads. I really recommend to follow the steps described there if you haven't so far...

[Tut] Preparing Your One X for Custom Roms (For Dummies) [Mac OS X]

Big thanks to bagofcrap24 for his great original guide here.
This one is for OS X users with an administrator account, I did it in OS X (Lion) because I haven't got the Android SDK installed on Windows at the moment and didn't want the hassle of downloading it just for the USB drivers.
If you get the [Waiting For Device] message in Windows Command Prompt and have access to a Mac instead, you might also want to try this guide.
If you get 'Permission Denied' in Terminal try this.
If I made any errors let me know and I'll correct it.
UPDATE: If you see any errors on HTC-dev such as "We are sorry, but this section of site is temporarily closed." just be patient, wait a little while and try again.
Unlocking Your Bootloader
Before we can even think about doing anything the first port of call is unlocking your bootloader.
As of the time of writing this there is currently no S-OFF method available so this is the only method of flashing a new recovery or boot image.
I'm going to keep this as simple as possible.
1. Go Here "http://www.htcdev.com/" and create yourself an account on HTCDEV.
2. Download this fastboot file for Mac.
3. Make a new folder on your desktop called 'fastboot'.
4. Extract the file 'fastboot-mac' from the .zip downloaded in step 2 to this folder.
5. Go here http://www.htcdev.com/bootloader/ and select "All Other Supported Models" and "then begin unlock bootloader".
6. Yes, tick both boxes, proceed.
7. Skip up to step 8 as we have all we need for the first 7 steps.
8. Power off your phone by holding the power button down for 10 seconds.
9. Power your phone on by holding power and volume down.
10. Highlight Fastboot with volume +/- then press power.
11. Plug your phone into your Mac and open a Terminal window.
12. Type this into your Terminal window:
sudo -s (then type your password and press enter)
cd /volumes/"your OSX drive name"/Users/your-username/Desktop/fastboot
./fastboot-mac oem get_identifier_token
Click to expand...
Click to collapse
13. Select & copy the text as per step 9 on the HTCDev website.
Terminal will add some characters to the left of the token, compare yours with the HTC example token, copy your token into the Textedit application and remove the text along the left to make them match, then copy the token again.
14. Paste your identifier token into the box at the bottom and submit.
You will receive an e-mail shortly from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached.
15. Download the "Unlock_code.bin" from the e-mail and save it to the same folder that we extracted fastboot files to in step 2.
16. Type this into your Terminal window:
./fastboot-mac flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
17. The Display Will change on your phone, press Vol + to accept and power to confirm.
Congratulations, you have successfully unlocked your bootloader.
Now to the good stuff..
Installing A Recovery
This one is very simple to do once you have your bootloader unlocked.
A thing to note; at present there is no USB-Mass Storage in recovery so if you are planning to install a custom rom i would get it put on the internal memory of your phone now rather than messing things up later and been unable to install it.
(if you have follwed my unlocking guide skip to step 4)
1. Download this fastboot file for Mac.
2. Make a new folder on your desktop called 'fastboot'.
3. Extract the file 'fastboot-mac' from the .zip downloaded in step 2 to this folder.
4. At Present The Latest Recovery is an Interim made by Paul O'Brien from Modaco, you can grab it HERE
P.S. its the top one out of the two, the bottom is stock recovery.
Update: Latest official touch and non-touch recovery versions by Koush are available here.
5. Download the custom recovery and save it in the same folder as you did the fastboot files.
6. Power the phone off by holding the power button for 10 secs.
7. Select Fastboot with volume + or - then press power.
8. Plug your phone into your Mac and open a Terminal window.
10. If you still have the Terminal window open from installing your bootloader then skip to the next step, if not then type this into your Terminal window:
sudo -s (then type your password and press enter)
cd /volumes/"your OSX drive name"/Users/your-username/Desktop/fastboot
Click to expand...
Click to collapse
11. Type this into your Terminal window:
./fastboot-mac flash recovery name_of_recovery_image.img
in my case it was ./fastboot-mac flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
Click to expand...
Click to collapse
Congratulations, you now have a custom recovery.
Flashing A ROM
1. Select reboot bootloader with volume +/- then power to select
2. Select HBOOT with volume +/- then power to select
3. Select recovery with volume +/- then power to select
You are now on your custom recovery.
4. First things first - do a Nandroid Backup of your current ROM in case anything bad happens.
5. Make sure you already have your shiny new ROM .zip on your internal memory as you cannot enable mass storage in the current recovery builds.
6. Wipe then flash your new custom ROM.
(You can flash the Super Wipe .zip from here to easily wipe your system partition and prepare it for the fresh ROM, thanks mike1986.)
OR you can download the latest SuperSU binaries from HERE and install them Via Recovery to just root the stock ROM.
Hope this helps some of you.

You can use Homebrew to install the Android tools if you want. It will also update them for you if you ask it to, via a simple command. Pretty convenient.
http://mxcl.github.com/homebrew/

thanks looking to try it but the dev web in htc it's down

Thanks for the guide....was helpful

./fastboot-mac oem get_identifier_token
'sudo ./fastboot-mac flash recovery name_of_recovery_image.img'
i use this two commands and say sudo: ./fastboot-mac: command not found

Terminal needs to be navigated to the same folder as the fastboot-mac file you extracted earlier, you can do this automatically in Lion (not sure about older versions) by right-clicking the folder and going to 'Services' then selecting 'New Terminal at Folder'.
You can navigate manually either by using the 'cd' command, for example:
cd /volumes/"OS X"/fastboot
Note the importance of quotes for a drive name with spaces.
You can also activate root before you do anything by typing sudo -s

i don't find that option new terminal at folder not showing it mmm
Sent from my HTC One X using xda premium

x.Orville.x said:
i don't find that option new terminal at folder not showing it mmm
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Just use the cd command then instead:
cd /volumes/"your OSX drive name"/fastboot
Sent from my HTC One X using xda premium

i have lion and i click it the folder and i don't see this
Services > New Terminal at Folder)
---------- Post added at 06:52 PM ---------- Previous post was at 06:29 PM ----------
i have the folder on the desktop and no here the error
No such file or directory
---------- Post added at 06:57 PM ---------- Previous post was at 06:52 PM ----------
that's my name of the hd
cd/volumes/"Orville HD"/fastboot
---------- Post added at 07:02 PM ---------- Previous post was at 06:57 PM ----------
any one can help me i put the folder on desktop or in the hd and the commands not work

Hmm it might not be there by default.
If the fastboot folder is on your desktop use this:
cd /volumes/"Orville HD"/users/your-user-name/Desktop/fastboot

i got the key but when i paste the other key on terminal have a error

When you get your key from Terminal you need to compare it with the example key HTC have on their site, theres some stuff you need to remove on the left to make them look the same.
Copy it into the Textedit app to remove them then select the whole key and paste it into the HTC site.

got it have unlocked and clockword thanks

No problem, have fun

Thank you so much for a clear guide.

Might be worth mentioning that the official CW recovery is available in basic and touch formats from here: http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Great and concise guide, by the way. Hope this helps someone.

hmm i get permission denied even after sudo.. any ideas?

visor said:
Might be worth mentioning that the official CW recovery is available in basic and touch formats from here: http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Great and concise guide, by the way. Hope this helps someone.
Click to expand...
Click to collapse
please note that there is an error in the coding of device.id on the official CW recovery and any rom that uses the aroma installer will not work at present, that is the reason i have left my guide with the links to the interim

x.Orville.x said:
i have lion and i click it the folder and i don't see this
Services > New Terminal at Folder
Click to expand...
Click to collapse
Just for the records...to get the "services" option after you right click, go to system preferences and then select keyboard and then choose "services" on left there is a option on the right panel where you can check for the "new terminal at folder" (do not remember exactly where)
{
"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"
}
EDIT: Screenshot added

MrGarak said:
Terminal needs to be navigated to the same folder as the fastboot-mac file you extracted earlier, you can do this automatically in Lion (not sure about older versions) by right-clicking the folder and going to 'Services' then selecting 'New Terminal at Folder'.
You can navigate manually either by using the 'cd' command, for example:
cd /volumes/"OS X"/fastboot
Note the importance of quotes for a drive name with spaces.
You can also activate root before you do anything by typing sudo -s
Click to expand...
Click to collapse
I keep getting denied permission, even with the password, and "operation not supported." Is this guide for use in Snow Leopard or Lion?

DPI Changed and now no Boot!!!

Hey I changed my DPI settings to 180 and the Phone only shows the Google Screen with that lock Icon
and then turns black.
What can I do to revert this? can someone please help?

You did make backup before doing that RIGHT?

It had nothing too important that I needed on it. So no, I didn't

Well I would say just reflash your current ROM on top of your setup now. You should still be able to get into recovery just fine.

NYYFan325 said:
Well I would say just reflash your current ROM on top of your setup now. You should still be able to get into recovery just fine.
Click to expand...
Click to collapse
Unfortunately the .zip file isn't on the internal memory
I tried to mount the USB to transfer a .zip rom over
But it keeps saying
E:can't mount /sdcard/
is this normal? Did the internal memory get warped?
Could ODIN be used to help me out?
I shouldnt have gone along with this post I saw that suggested that 180 DPI would send the User Interface into "Tablet mode" because I really wanted the Notification/ Status Bar in the same bar as the on screen "Back, Home and Task" buttons
And that would have been the only mod that I have done. and look what happens.

throwback1718 said:
Unfortunately the .zip file isn't on the internal memory
I tried to mount the USB to transfer a .zip rom over
But it keeps saying
E:can't mount /sdcard/
is this normal? Did the internal memory get warped?
Could ODIN be used to help me out?
I shouldnt have gone along with this post I saw that suggested that 180 DPI would send the User Interface into "Tablet mode" because I really wanted the Notification/ Status Bar in the same bar as the on screen "Back, Home and Task" buttons
And that would have been the only mod that I have done. and look what happens.
Click to expand...
Click to collapse
If you go to the bootloader and redo the command fastboot oem lock and then fastboot oem unlock it will lock and unlock your boot loader also reformatting your scard. Once you do that go back to recovery and try putting the zip file on again

throwback1718 said:
Unfortunately the .zip file isn't on the internal memory
I tried to mount the USB to transfer a .zip rom over
But it keeps saying
E:can't mount /sdcard/
is this normal? Did the internal memory get warped?
Could ODIN be used to help me out?
I shouldnt have gone along with this post I saw that suggested that 180 DPI would send the User Interface into "Tablet mode" because I really wanted the Notification/ Status Bar in the same bar as the on screen "Back, Home and Task" buttons
And that would have been the only mod that I have done. and look what happens.
Click to expand...
Click to collapse
you cant mount the sd card because there is no sd card.
use adb
adb push locationofrom /data/meda

NYYFan325 said:
If you go to the bootloader and redo the command fastboot oem lock and then fastboot oem unlock it will lock and unlock your boot loader also reformatting your scard. Once you do that go back to recovery and try putting the zip file on again
Click to expand...
Click to collapse
My apologies... I literally just got this Nexus today. again, I was just trying to make a minor tweak...
Anyhow, I don't know too much about the phone. How is the command fastboot oem lock done?
I can't use the search button right now too much

It' s very simple to fix that, I asume that you did the "tweak" in /system/build.prop right? If so just boot into recovery, if you can't then use the GNex toolkit, once in recovery connect the phone to the computer and it should see your phone as an adb device, open from the toolkit a command prompt, start adb service and pull the modified build.prop to your computer then correct whatever you mess in it (DPI) and then push the fixed build.prop to the phone and finally your GNex will boot normally.
Sent from my Galaxy Nexus using xda premium

^^^ Actually I downloaded an app from the play store to do it... does this still apply to me ?
I'm mad at myself
Sent from my HERO200 using Tapatalk 2

throwback1718 said:
^^^ Actually I downloaded an app from the play store to do it... does this still apply to me ?
I'm mad at myself
Sent from my HERO200 using Tapatalk 2
Click to expand...
Click to collapse
Yes, because all that this app did is changed the value in your build.prop. What you want to do is go to this file and change ro.sf.lcd_density from 180 to 320, save and reboot.

ok I'm having difficulty here. I can't do any of the adb functions. Again like I said, I got this phone just yesterday. So drivers and such havent been installed. Apparently when using the toolkit to install the drivers to the computer, you need to enable USB debugging. Which I can't do. Because the phone isn't booting.
So is there a work around for this? Its the damn first step and I'm stuck already.
I literally haven't done anything to this phone. Clockworkmod was installed prior to me getting the phone, and so was Fastboot.
I have been looking online for Nexus USB drivers but its difficult .... Any suggestions?

Try this and see if you can install the drivers or if your pc detect the gnex: power off the phone, press and keep pressed volume down button while you turn on the phone, this should make you boot into fastboot or odin's mode I'm not pretty sure. Try it and let us know.
Sent from my Nook Tablet using xda premium

iferlive said:
Try this and see if you can install the drivers or if your pc detect the gnex: power off the phone, press and keep pressed volume down button while you turn on the phone, this should make you boot into fastboot or odin's mode I'm not pretty sure. Try it and let us know.
Sent from my Nook Tablet using xda premium
Click to expand...
Click to collapse
It goes into download mode. With "ODIN" in the top left corner.
So doing this should substitute the fact that I can't enable USB debugging because I can't boot the phone?

Ok now I'm home and I have my laptop here so I can help you more efficiently, mi computer also didn't recognized my gnex in odin mode, lets try something else, turn off your phone, and connect it to your pc and wait until you hear the windows sound of "new device attached" if so then proceed with the installation of drivers vie the toolbox, once done that and if we have look toolbox should see your device, let me know what happens, and tell me what app did you use and what density you did set so I can recreate the event in my phone
---------- Post added at 07:44 PM ---------- Previous post was at 07:01 PM ----------
Oh I got it dude, so you have already installer CWM Recovery right? ok Here is the solution so you can have adb, I assume that you have already installed the drivers wich is so simple and you don't need the phone to do that, turn off your phone and press volume up and volme down buttons keep them pressed while pressing the power button "KEEP ALL PRESSED" and you will boot into FASTBOOT Mode, if the installation of the driver was correctly made the ToolBox will detect your device in FastBoot (I recommend you to reboot your computer if it didn't recognize the phone), then use the volume keys to select "Recovery Mode" and press the power button, this will make your GNex boot into CWMR! wich means that you can use adb commands (CWMR has natively adb enabled) your pc should recognize the new device and prepare the drivers, after this just refres the ToolBox screen with option 25 and you will see your device number in the list of adb devices.
Ok once done that (that tricky part) in the ToolBox select option 14 adn select "no" to the secure image cuestion, this will reboot your phone, now put this do download the build.prop "/system/build.prop" with no quotes and hit "enter"
Now go to the ToolBox installation folder and go into the folder caller "pulled_files_are_put_here" ther will be your GNex build prop, open it with a text editor (WordPad) and edit this entry: ro.sf.lcd_density=320 you mess with this value so lets restore it to the default one which is 320, save the file.
Now move the recently corrected build.prop to the folder called "put_files_to_push_here" which is in ToolBox installation folder, and in the ToolBox windows select option 13, now put build.prop as the name of the file to push, it will say "file found" and nos put the directory where it goes which is: /system/
Reboot
And Voila! your GNex should now boot normally.
Good Look man, let me know if you could do it.

1) Reboot your device in CWM and plug into you computer.
2) Install these drivers. If you don't know how, have a read here.
3) Download the adb files from here and unzip them in to a directory.
4) Open a command prompt in that same directory.
5) In the menus on your device in CWM, mount /system.
6) In the command prompt, type: adb pull /system/build.prop
7) Open that file in a text editor and change the line that starts with ro.sf.lcd_density to have a value of 320. Close and save it.
8) In the command prompt, type: adb push build.prop /system/
9) In the command prompt, type: adb shell chmod 644 /system/build.prop
10) Reboot.

iferlive said:
Ok once done that (that tricky part) in the ToolBox select option 14 adn select "no" to the secure image cuestion, this will reboot your phone, now put this do download the build.prop "/system/build.prop" with no quotes and hit "enter"
And Voila! your GNex should now boot normally.
Good Look man, let me know if you could do it.
Click to expand...
Click to collapse
Stuck at this part. The phone tried to reboot and it didnt... Just black screen It kept saying "Waiting for adb Mode"
{
"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"
}
and it still does now. what now? I unplugged and went back to CWM but it still says waiting for adb mode.
Thanks for being patient with me BTW

efrant said:
1) Reboot your device in CWM and plug into you computer.
2) Install these drivers. If you don't know how, have a read here.
3) Download the adb files from here and unzip them in to a directory.
4) Open a command prompt in that same directory.
5) In the menus on your device in CWM, mount /system.
6) In the command prompt, type: adb pull /system/build.prop
7) Open that file in a text editor and change the line that starts with ro.sf.lcd_density to have a value of 320. Close and save it.
8) In the command prompt, type: adb push build.prop /system/
9) In the command prompt, type: adb chmod 644 /system/build.prop
10) Reboot.
Click to expand...
Click to collapse
I was looking at the instructions on installing those drivers and it appears that it requires that the phone be on and booted into Android.
I can't do that because I get no further than the black screen.

Don't panic I'm writing a new possible solution wait a few minutes

throwback1718 said:
I was looking at the instructions on installing those drivers and it appears that it requires that the phone be on and booted into Android.
I can't do that because I get no further than the black screen.
Click to expand...
Click to collapse
It can be booted in CWM instead. It makes no difference.
Sent from my Galaxy Nexus using Tapatalk 2

[GUIDE] Set up Android SDK (ADB) for Windows 8 / 8.1 / [ADB][Bootloader][Fastboot]

Android SDK - Powerful tool and easy to set up for use with your HTC One M8
{
"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 Reason that you would want to use Android SDK is because its very easy, it's well updated and it just WORKS! There is much more use with HTC devices with adb then with Samsung when it comes to the daily things like splash screens, radio updates, firmware. You will be dealing a lot with the bootloader and fastboot flashing. So to help out, I will post a helpful guide to help you get started for use with the HTC One M8.​
Click to expand...
Click to collapse
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
1. Download Android SDK For Windows
2. Click the
either the 32bit version or 64bit version
3. Create a folder in the C: and name it Android. See below
4. Place adt-bundle-windows in the Android Folder you just created. Use WinZip, WinRAR or 7-Zip to extract the contents inside the folder. See Below
5. Once extracted, Double click SDK Manager and instal all 4.4.2 and 4.3 items and under tools (SDK Tools and Platform Tools). See Picture Below
6. After all packages are installed and updated, download the latest HTC Sync Manager and install once download completes
7. Once Sync Manager completes installation process, go to control panel and uninstall HTC Sync Manager only, you will see HTC Driver in there as well (LEAVE IT THERE)
8. Important, make sure you enable developer options and turn on USB Debugging. Instructions Below if you are unsure how to do that
1. Go to Settings > About > Software information > More > Tap Build Number 5x
2. Once you get notification saying Developer options is unlocked go back to > settings
3. Click Developer options
4. Add check in the box USB Debugging
9. Plug phone into the computer and let it install all the drivers, you should see pop ups.
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\sdk\platform-tools
2. In Command prompt type
Code:
adb devices
3. If your output shows your device attached like below, then you are good to go!!!
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\sdk\platform-tools
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified

Reserved if needed
Sent from my HTC6525LVW using Tapatalk

Thanks for the guide!
Can you add instructions for how to add adb to the environment variables so it can be accessed without having to cd to the platform-tools folder?
Sent from my HTC One M8

VolcanicSkunk said:
Thanks for the guide!
Can you add instructions for how to add adb to the environment variables so it can be accessed without having to cd to the platform-tools folder?
Sent from my HTC One M8
Click to expand...
Click to collapse
I will look into it if I have some time, you can post it in here if you like if you think others will appreciate it. Thanks
Sent from my HTC6525LVW using Tapatalk

OP Updated
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks

bdorr1105 said:
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks
Click to expand...
Click to collapse
Will this work for Windows 7 as well? I have Windows 7, and every time I try to plug my phone in to start the unlocking process, and I click on "Get Token ID"
It just sits at that screen and does nothing. Any help would be greatly appreciated!

theimmortalone said:
Will this work for Windows 7 as well? I have Windows 7, and every time I try to plug my phone in to start the unlocking process, and I click on "Get Token ID"
It just sits at that screen and does nothing. Any help would be greatly appreciated!
Click to expand...
Click to collapse
It should work the same for windows 7, but keep in mind the guide was created on Windows 8....I do not know the path of your adb folder, also, the phone will prompt you to allow the computer to access it, YOU HAVE TO ALLOW IT, or it will never work!!!
What command did you type? I dont see anything except HTC' ????

bdorr1105 said:
It should work the same for windows 7, but keep in mind the guide was created on Windows 8....I do not know the path of your adb folder, also, the phone will prompt you to allow the computer to access it, YOU HAVE TO ALLOW IT, or it will never work!!!
What command did you type? I dont see anything except HTC' ????
Click to expand...
Click to collapse
Okay, well that is my problem then, every time I plug my phone in, and it never asks me to allow it or not. How can I fix that issue? IT does it on my XP, but that is slower then hell so I prefer not to use it.
And as far has the "HTC" part, it doesn't go past that folder. I thought the all-in-one root kit was supposed to do it automatically?

theimmortalone said:
Okay, well that is my problem then, every time I plug my phone in, and it never asks me to allow it or not. How can I fix that issue? IT does it on my XP, but that is slower then hell so I prefer not to use it.
And as far has the "HTC" part, it doesn't go past that folder. I thought the all-in-one root kit was supposed to do it automatically?
Click to expand...
Click to collapse
You may have already accepted it, lets resolve the steps in order to make sure thats the problem, if you follow the guide, you create a Android folder and then extract the bundle inside of that
the path should be C:\Android\sdk\platform-tools
I want to you to open Command Prompt and do the following:
1. Win+R or Start>Run>cmd Hit enter
2. cd c:\Android\sdk\platform-tools
3. type adb devices > Look for prompt on phone and allow it
If it shows your device connected you are good to go

bdorr1105 said:
It should work the same for windows 7, but keep in mind the guide was created on Windows 8....I do not know the path of your adb folder, also, the phone will prompt you to allow the computer to access it, YOU HAVE TO ALLOW IT, or it will never work!!!
What command did you type? I dont see anything except HTC' ????
Click to expand...
Click to collapse
bdorr1105 said:
You may have already accepted it, lets resolve the steps in order to make sure thats the problem, if you follow the guide, you create a Android folder and then extract the bundle inside of that
the path should be C:\Android\sdk\platform-tools
I want to you to open Command Prompt and do the following:
1. Win+R or Start>Run>cmd Hit enter
2. cd c:\Android\sdk\platform-tools
3. type adb devices > Look for prompt on phone and allow it
If it shows your device connected you are good to go
Click to expand...
Click to collapse
I honestly do not remember that pop up coming up on my phone. So I'm not sure what's up with that. But I will do what you said above, and report back.

theimmortalone said:
I honestly do not remember that pop up coming up on my phone. So I'm not sure what's up with that. But I will do what you said above, and report back.
Click to expand...
Click to collapse
Also make sure have USB debugging enabled.... It's part of the process
Sent from my HTC6525LVW using Tapatalk

bdorr1105 said:
You may have already accepted it, lets resolve the steps in order to make sure thats the problem, if you follow the guide, you create a Android folder and then extract the bundle inside of that
the path should be C:\Android\sdk\platform-tools
I want to you to open Command Prompt and do the following:
1. Win+R or Start>Run>cmd Hit enter
2. cd c:\Android\sdk\platform-tools
3. type adb devices > Look for prompt on phone and allow it
If it shows your device connected you are good to go
Click to expand...
Click to collapse
SUCCESS!!
I believe I should be good to go now right?
---------- Post added at 06:07 PM ---------- Previous post was at 05:59 PM ----------
theimmortalone said:
SUCCESS!!
I believe I should be good to go now right?
Click to expand...
Click to collapse
Holy **** I finally got it to work. Thanks for your help man! Appreciate it!

theimmortalone said:
SUCCESS!!
I believe I should be good to go now right?
Click to expand...
Click to collapse
Yes you should, you need to go to C:\Android and double click SDK Manager.exe and update Android 4.4.2 API by clicking the check box. See Attached Picture
If you do not want to have to change directories, then you need to add that path just as the instructions say to do!
C:\Android\sdk\platform-tools

theimmortalone said:
SUCCESS!!
I believe I should be good to go now right?
---------- Post added at 06:07 PM ---------- Previous post was at 05:59 PM ----------
Holy **** I finally got it to work. Thanks for your help man! Appreciate it!
Click to expand...
Click to collapse
No problem