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

Backup and Restore Galaxy Nexus without root (Mac)

UPDATED 2/3/12
Thanks to @copkay for writing this! http://forum.xda-developers.com/showthread.php?t=1420351 (windows version)
copkay said:
Like a lot of you, I have been putting off unlocking the bootloader on my Nexus because I didn't want to have to go through the hassle of backing up everything manually and restoring individual application data; logging back into apps; saving settings; etc. I found an undocumented (at least as far as my googling was able to find) feature in the latest version of the ADB platform tools (for Android 4.0+) that allows you to create a full system backup, including app apks, their respective data, as well as the internal storage.
This guide assumes you have already installed the Android SDK, and updated the Android SDK Platform Tools to the latest version (currently Rev 10) using the SDK Manager.
Click to expand...
Click to collapse
1. Connect your device via USB, and open Terminal.
2. In Terminal, type "cd " with the space and then drag your "platform-tools" folder in the android sdk where the space is, it should look like this "cd /where ever you put the folder/name of you computer/android-sdk-mac-osx/platform-tools". Drag and drop will do this for you, then hit enter.
{
"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"
}
3. In the same terminal window, type "./adb" and hit enter. A lot of stuff with come up that you really dont need to worry about.
4. Optionally, type the command "./adb devices" to ensure that your device is properly recognized. If you're comfortable with ADB already, just skip this.
The command parameters format is:
./adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|nosystem] [<packages...>]
Click to expand...
Click to collapse
The most basic command you can use is simply:
./adb backup -all
Click to expand...
Click to collapse
This will use the defaults to backup only app and device data (not the APKs themselves) to the current directory as 'backup.ab'
To explain the parameters:
./adb backup -f <file>
Click to expand...
Click to collapse
Use this to choose where the backup file will be stored, e.g. '-f /backup/mybackup.ab', which will save it at the root of your drive (C:\ for Windows, etc.) in a folder called backup, as a file named 'mybackup.ab'. I recommend using this flag to set a location manually, as with my first backup test, it said that it completed successfully, but I was unable to locate the backup file. I have no idea where it was saved, but it wasn't where it should have been located.
./adb backup -apk|-noapk
Click to expand...
Click to collapse
This flags whether or not the APKs should be included in the backup or just the apps' respective data. I personally use -apk just in case the app isn't available in the Market, so that I don't have to go hunt it down again. The default is -noapk.
./adb backup -shared|-noshared
Click to expand...
Click to collapse
This flag is used to "enable/disable backup of the device's shared storage / SD card contents; the default is noshared.", which for the Nexus I would certainly flag to -shared, but from my test, it did not restore all of the contents of my internal storage, so I recommend backing up music, pictures, video, and other internal storage items manually, just to be on the safe side. The default is -noshared.
./adb backup -all
Click to expand...
Click to collapse
This flag is just an easy way to say to backup ALL apps. The packages flag (further on) can be used to choose individual packages, but unless you're just wanting to backup a specific application, use -all for a full system backup.
./adb backup -system|-nosystem
Click to expand...
Click to collapse
This flag sets whether or not the -all flag also includes system applications or not. I used -system, but this is probably unnecessary, and I would almost guess that it is safer to use -nosystem, but use your own judgment on this. The default is -system.
./adb backup <packages...>
Click to expand...
Click to collapse
Here you can list the package names (e.g. com.google.android.apps.plus) specifically that you would like to backup. Use this only if you're looking to backup a specific application.
3. Once you've made your decision on how to perform the backup, simply type the command as you would like it; in my case, this is the command that I used:
./adb backup -apk -shared -all -f /c/backup20111230.ab
or
./adb backup -apk -shared -all -----------and then just search for it in finder.
Click to expand...
Click to collapse
4. You will see a screen like the following:
5. Enter a password (if desired) for encryption of the backup file. RETAIN THIS PASSWORD FOR RESTORING LATER.
6. This process will take several minutes to complete, depending on the settings you've chosen, but when completed, you should get a toast on-screen saying 'Backup Complete', or if you miss that, you'll know once your command line has returned.
7. Now go unlock your bootloader (not going to go into the process for this guide, but you probably know how already, and if not, there are several guides a search away).
8. Once you're booted back into Android, you can choose to add your account now, or skip that for later. I skipped it for later, but I think it might make the process more smooth to sign in before the restore. YMMV.
9. To restore, with your device connected open your command prompt again, and type:
./adb restore /backup/mybackup.ab
Click to expand...
Click to collapse
replacing '/backup/mybackup.ab' with the location of your backup file.
10. You will see a screen like the one below:
11. Simply type in your current encryption password (if you've set one), and the password with which the backup was encrypted (if you chose to set a password), and the restore will begin. It again will take several minutes depending on the size of the backup and the options chosen.
12. You're back to normal, short of possibly some widgets on the home screen. My wallpaper was even restored, my app folders remained just as I had them before, my alarms remained, and for most applications, I didn't even have to log back in; it kept everything.
________________________
NOTE: I did have an issue with not all files being restored to the Internal Storage; in particular, the Gallery still displayed all the folders and files that it had cached (which it expected to be there) as only gray boxes, and would not display the images, nor would it rescan the media. I simply copied the files back to the Internal Storage directory manually, and all was well again. Again, YMMV.
NOTE : Also to note, this will not back up SMS messages, so if you're concerned about those, you may want to look into an alternative application to back up SMS.
Hope this is able to help! If so, give me a thanks )) and let me know how your experience goes.
- Sean

Worked
I couldn't get it to work no matter how much I tried. I could connect and see the device but when I ran the command, all I would get was a list of commands. I finally found a way upgrade the sdk by:
./android update sdk --no-ui
Then it worked perfectly!!

bosshoss16 said:
I couldn't get it to work no matter how much I tried. I could connect and see the device but when I ran the command, all I would get was a list of commands. I finally found a way upgrade the sdk by:
./android update sdk --no-ui
Then it worked perfectly!!
Click to expand...
Click to collapse
Ya in the beging when I said you need the sdk package, I forgot to say for all to be updated, whoops. Was that your problem?

Hipe0ples555 said:
Ya in the beging when I said you need the sdk package, I forgot to say for all to be updated, whoops. Was that your problem?
Click to expand...
Click to collapse
Yeah, after I updated the sdk, it worked perfectly! Thanks!!

I'm completely new to this. I downloaded the SDK manager and the Platform tools.
Terminal opened automatically with the manager. Then I did number 2 which worked fine.
After that when I type the commands from number 3 and 4 nothing happens when I hit enter. Any help would be appreciated.
Is it possible my Mac doesn't see the Nexus. Is the Nexus supposed On or Off by the way, I had it On.

ivoniko said:
I'm completely new to this. I downloaded the SDK manager and the Platform tools.
Terminal opened automatically with the manager. Then I did number 2 which worked fine.
After that when I type the commands from number 3 and 4 nothing happens when I hit enter. Any help would be appreciated.
Is it possible my Mac doesn't see the Nexus. Is the Nexus supposed On or Off by the way, I had it On.
Click to expand...
Click to collapse
Code:
./adb devices [enter]
Will tell you if its connected (per #3).
If #2 works properly and it navigates to your platform-tools folder, then you should be able to type ./adb [enter] and have all of th ADB commands come up. If not, you haven't properly updated/installed the SDK, or you haven't navigated to the folder properly.

martonikaj said:
Code:
./adb devices [enter]
Will tell you if its connected (per #3).
If #2 works properly and it navigates to your platform-tools folder, then you should be able to type ./adb [enter] and have all of th ADB commands come up. If not, you haven't properly updated/installed the SDK, or you haven't navigated to the folder properly.
Click to expand...
Click to collapse
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.

ivoniko said:
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.
Click to expand...
Click to collapse
when you type ./adb , does it run a long command line?

Hipe0ples555 said:
when you type ./adb , does it run a long command line?
Click to expand...
Click to collapse
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.

ivoniko said:
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.
Click to expand...
Click to collapse
Probably not, I would just try to delete the whole android_sdk folder and re-download it, even though it may take some time, it will be worth it if it works!

ivoniko said:
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.
Click to expand...
Click to collapse
Probably not, just delete the whole Android_SDK folder and re-install everything! You know to go into the folder, go to tools and click android to updated all 6 things right?

Probably not, just delete the whole Android_SDK folder and re-install everything! You know to go into the folder, go to tools and click android to updated all 6 things right?

ivoniko said:
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.
Click to expand...
Click to collapse
Did you see my other post, it is not showing up for some reason, is it working yet?

ivoniko said:
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.
Click to expand...
Click to collapse
One thing that I noticed, I had my Nexus plugged in through a USB hub, and I was seeing the same behavior you described. I then plugged it in directly into my laptop and I was able to see it. May or may not apply to your situation.

Alright so an update to my previous comment.
I was able to follow this guide and create a backup, unlock the boot loader and root the phone successfully. I am now in the process of restoring my backup, however when I type in:
./adb devices
in the terminal, nothing is listed. Therefore, I am unable to restore my back up. Any ideas on what may be going on?
EDIT: Figured it out, I forgot to re-enable USB debugging after my phone was wiped

Hipe0ples555 said:
Probably not, just delete the whole Android_SDK folder and re-install everything! You know to go into the folder, go to tools and click android to updated all 6 things right?
Click to expand...
Click to collapse
Yes, I went to tools, clicked on android, updated 6 things and after that when I entered the commands nothing happened.
In any case I will listen to your advice and download everything again.

Entering commands in terminal doesn't work. Even before having to conect the phone just entering the update commands in terminal doesn't do anything. I have no clue.
Here it is how it looks -
Last login: Tue Jan 31 00:53:34 on ttys000
/Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
Name-MacBook-Pro:~ name$ /Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
tools/android update sdk --no-ui
./android update sdk --no-ui

ivoniko said:
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.
Click to expand...
Click to collapse
Ok, so it is not literally; cd /Users/name/Desktop/android-sdk-macosx/platform-tools if thats not where it is; in terminal just type "cd " then just drag the platform-tool folder into the terminal and you should get something that LOOKS like cd /Users/name/Desktop/android-sdk-macosx/platform-tools but if thats not where it is, it will have a different path. Does that help?

ivoniko said:
Entering commands in terminal doesn't work. Even before having to conect the phone just entering the update commands in terminal doesn't do anything. I have no clue.
Here it is how it looks -
Last login: Tue Jan 31 00:53:34 on ttys000
/Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
Name-MacBook-Pro:~ name$ /Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
tools/android update sdk --no-ui
./android update sdk --no-ui
Click to expand...
Click to collapse
You forgot to type cd*space*, "cd " before draging the folder into the terminal.

Just updated everything! Does the change help?

[ROOT, CWM] JXD S18-03-xxxx RK2926 mini pad [Guide]

In this guide i will show you how to root a JXD S18 03-xxxx device.
This method was tested on the following device:
OS: Android 4.1.1
Kernel: 3.0.36+ Feb 2
Soc: Rk2926
Model: S18-03-201304-4GB-00727
Root:
0. Download files.zip(from here) extract it and open it in explorer.
1. Connect your device to your computer (micro-usb)
2. Unmount all storage devices (TF/SD card, onboard TF/SD, etc..)
3. Enable USB Debugging (Under settings > Options for developers > Enable USB Debugging)
4. Open ''AdbDriverInstaller.exe'' and install the universal ADB driver
5. Automated process for rooting the device ''ROOT ME.bat'' Press any key and just wait and let the tablet reboot.
6. Manual root:
Code:
adb shell
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb shell
chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/su
mount -o remount,ro -t rfs /dev/block/st19 /system
exit
adb reboot
And now you have root.
{
"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"
}
Make sure to update su(super user) after rooting. Because it is outdated.
You can either use adb push for this or you can use the Google Play store to download the latest bin.
CWM-recovery
Download: http://files.androtab.info/rockchip/rk2928/20130425/S18-03_CWM.zip
From adb root shell
1. extract flash_image and recovery.img from CWM.zip
2. put flash_image and recovery.img into device, e.g.
adb push flash_image /dev/
adb push recovery.img /dev/
3. enter root shell (adb shell)
4. flash recovery.img into recovery partition with flash_image, e.g.
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
Read this when you have any issues
CWM installation problems, please try another method if this doesn't work for you.
Link: http://androtab.info/clockworkmod/rockchip/install/
If you have any issues while rooting please try:
adb kill-server
adb devices
And see if the devices is listed after killing the server.
If it is not than u may have another soc (older version does have other rockchip and the adb driver wont work properly).
This guide is for the latest version as if 1st May 2013: S18-03-XXXX (4.9.2013)
If you still have no output from adb devices you can try one more thing!
By editing android_winusb.inf in C:\Windows\System23\Drivestore\Filerepository\android_winusb.inf_amd64_neutral_<random_chars>
You will see two of those folders.
Open it with a text editor like notepad++ or notepad make sure you have nt authority rights
android_winusb.inf:
Code:
;------------------------------------NTx86------------------------------------
[Google.NTx86];
For loopback testing
And add this after the first space of declaring hardware ids;
Code:
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
Tested and working on the following devices:
Audiosonic T-17B 7" tablet (Kmart webshop version) ✓
S18-03-XXXX (4.9.2013) ✓
S18-03-201302 (4gb-00905) ✓
S18-02-XXXX (x.x.2012) ?
Credits: me, icood70pro, fun_ for modding CWM for rockchip, all credit goes to original CWM author koush and all its contributors.

How about S18-02-xxxx ?
I got myself a S18-02-xxxx, The ADB drivers behave oddly for this gadget. The driver installs, but SuperOneClick can't locate the device.
It does have SuperUser installed, but only the .apk file, not the permissions required to run it.
Think you can setup something?

macrat said:
It does have SuperUser installed, but only the .apk file, not the permissions required to run it.
Click to expand...
Click to collapse
Can you get access to adb shell and what os are you running? Modified adb doesn't seem to work properly on windows 8 you need to change this in order to make it work for windows 8 i think (at least you can try).
Start -> Run -> Type: "gpedit.msc" (Without quotes) -> Computer Configuration -> Administrative Templates -> Windows Components -> Application Compatibility -> Turn off Application Compatibility Engine <- Disable this
It might be the S18-02-xxxx. Model 02 has another soc i think, can you download a app in the play store for me? Type in: "Cpu info", download and install -> "CPU / RAM / DEVICE Identifier". And tell me what soc you have in it. Because the older versions may have a a9 amlogic 8726-m3l soc in it.
Please try that and verify if that worked for you or if you get adb shell access. Thanks,
and sorry for the late reply.

Just wanted to confirm I have successfully rooted my Audiosonic T-17B &" tablet (AUS KMart version) using your guide!
Although I'll note that the BAT file didn't succeed for some reason. Manually following the commands worked fine though, but I didn't bother with CWM as yet.
EDIT: Figured it out. It's the 'exit' commands you've stuck in there, it terminates the whole batch command instead of just restarting ADB. Can you edit that and re-upload the zipfile?

switchblade88 said:
Just wanted to confirm I have successfully rooted my Audiosonic T-17B &" tablet (AUS KMart version) using your guide!
Although I'll note that the BAT file didn't succeed for some reason. Manually following the commands worked fine though, but I didn't bother with CWM as yet.
EDIT: Figured it out. It's the 'exit' commands you've stuck in there, it terminates the whole batch command instead of just restarting ADB. Can you edit that and re-upload the zipfile?
Click to expand...
Click to collapse
Yes i can and sorry for that mistake. Thanks for confirming that it did work for you on another device with the same soc.

Resquest download password
NiTrOwow said:
0. Download files.zip(from) extract it and open it in explorer.
Click to expand...
Click to collapse
I not success download the zip file because ask me for a password. It's possible obtain this password please?

Stef20 said:
I not success download the zip file because ask me for a password. It's possible obtain this password please?
Click to expand...
Click to collapse
Seems like a bug.. in the forum software handling the bbcode..
Just remove the <br /> at the end of the url and it works.
And my content does not even include <br /> == space/enter ...
FYI. PROBLEM IS SENT TO FORUM ADMIN.

Oh yes I not viewed this... Normaly I take care :silly:
I edit manually the link and work good. Thank you for the reply!

Stef20 said:
Oh yes I not viewed this... Normaly I take care :silly:
I edit manually the link and work good. Thank you for the reply!
Click to expand...
Click to collapse
Alright man good luck and let me know if it works for you and let me know the model number

I will for sure. I wait a new tablet S18 from China just I'm not sure if I will have a s03 or s02 model. I suppose is a S03.

NiTrOwow said:
Seems like a bug.. in the forum software handling the bbcode..
Just remove the <br /> at the end of the url and it works.
FYI. PROBLEM IS SENT TO FORUM ADMIN.
Click to expand...
Click to collapse
Thanks. This problem is now fixed. it will not ask for a password now.
Mike

Alright then, only thing that i miss on this tab is a uhm extra ogt support and a good data sheet of the soc. Else would have made a small shell/nas/webserver from out of it.. But modding requires me a data sheet or else i have to reserve engineer the soc and then try to mod it with luck(?)
MikeChannon said:
Thanks. This problem is now fixed. it will not ask for a password now.
Mike
Click to expand...
Click to collapse
Thanks Mike that was fast :')
Sent from my HTC Sensation using xda app-developers app

NiTrOwow said:
Alright then, only thing that i miss on this tab is a uhm extra ogt support and a good data sheet of the soc. Else would have made a small shell/nas/webserver from out of it.. But modding requires me a data sheet or else i have to reserve engineer the soc and then try to mod it with luck(?)
Click to expand...
Click to collapse
If I receive a S03 and I hope is this, I will try your tutorial, if is a S02 I will try other thing because I suppose is not the same CPU and this risk not work?
About the OTG, I have read a guy success use it on the S18 with a external power on the OTG. He say it's a power problem only. Just I lost the link where is this message.
I hope my english is OK because is not my language.

Stef20 said:
If I receive a S03 and I hope is this, I will try your tutorial, if is a S02 I will try other thing because I suppose is not the same CPU and this risk not work?
About the OTG, I have read a guy success use it on the S18 with a external power on the OTG. He say it's a power problem only. Just I lost the link where is this message.
I hope my english is OK because is not my language.
Click to expand...
Click to collapse
No i understand you if you get your S03 or 02 you will have to open it up and have a look at it yourself i made some close up images of the board.
They can be found right here
http://forum.xda-developers.com/showthread.php?t=2253706
So you can look at your device and mine from the inside and look what is diffrent
:good:

NiTrOwow said:
No i understand you if you get your S03 or 02 you will have to open it up and have a look at it yourself i made some close up images of the board.
They can be found right here
http://forum.xda-developers.com/showthread.php?t=2253706
So you can look at your device and mine from the inside and look what is diffrent
:good:
Click to expand...
Click to collapse
It's fun view the inside without open it I view have a little more space for a bigger battery

Stef20 said:
It's fun view the inside without open it I view have a little more space for a bigger battery
Click to expand...
Click to collapse
Forgot to say that this battery for the S18-03 has a pcb on the battery (fail safe, anti-overvolt). It did surprise me because most cheap china products don't have that and it is a risk if you want to use it a lot because it may someday explode if you don't have this haha .. Battery looks like a BL-5B/BLC-2 from nokia without the plastic housing.

Finaly I received my S18 today and it's a S03, just a big trouble... after only few hours of use, the power button refuse work now... It's a cra* product I received...

I'm a little sad not success try your tutorial because my S18 are dead before... Now I not able start my tablet... I will return it!
I purchase a Asus Me172v and success root it . I used this tutorial http://forum.xda-developers.com/showpost.php?p=42047570 , just I'm not able write in this section because I suppose I'm new or I need have more messages.

Stef20 said:
I'm a little sad not success try your tutorial because my S18 are dead before... Now I not able start my tablet... I will return it!
I purchase a Asus Me172v and success root it . I used this tutorial http://forum.xda-developers.com/showpost.php?p=42047570 , just I'm not able write in this section because I suppose I'm new or I need have more messages.
Click to expand...
Click to collapse
Oke that sucks to have a DOA.
I hope they will resort this, and that you will be able to try my guide.
Good luck man.

NiTrOwow said:
Oke that sucks to have a DOA.
I hope they will resort this, and that you will be able to try my guide.
Good luck man.
Click to expand...
Click to collapse
I wait a new S18, just it's very long to receive it with the cheap post chipping.
I want root it because I hate not have the control

[Q] Can't figure out how to flash CWM via Mac OS X

Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks

Orange_furball said:
Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks
Click to expand...
Click to collapse
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel

Re-Mi said:
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel
Click to expand...
Click to collapse
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
{
"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"
}
Ps: I'm not Paul.. The guy I bought this Mac off of left his info and I never took the time to take t off..

Orange_furball said:
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
Click to expand...
Click to collapse
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file

Re-Mi said:
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file
Click to expand...
Click to collapse
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/

Orange_furball said:
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/
Click to expand...
Click to collapse
I pm-ed you.

Re-Mi has helped me solved my issue! Thank you so much!

Here is more detail on what I did, First of all I followed Re-Mi's instructions. Here they are:
So first things first Root
http://forum.xda-developers.com/show....php?t=2387507
Sideload the app and run the apk
second install the xposed installer (latest apk file at the end of the first post) make sure it's installed (Launch the Xposed Installer and click on "Install/Update" ,Reboot ,Done!)
http://forum.xda-developers.com/show....php?t=1574401
Then install mod collection for Ouya and install CWM from there
http://forum.xda-developers.com/show....php?t=2359390
It's a long detour but i think it will work. After that just install stockplus rom and you got everything you wanted (otherwise you would not even bother to install cwm )
Click to expand...
Click to collapse
Now let me go into more detail. What you do is type the first link into your OUYA's web browser (It is under Make>Software>Web Browser I believe) Then download the file. Now go to Manage>Settings>Advanced>Storage>Downloads and hit the file you just downloaded. Install that APK, hit open, then hit root. Now accept the SU request. After this is done repeat the steps until you have the other file downloaded. Now install that APK for the Xposed Installer and hit "Install/Update" then reboot. Now download the mod collection from the third link.
Install it and install CWM from there. It will take you to a download link, wait a few seconds, then hit install CWM again. Now it'll be installed.
Plug your Ouya into your computer, If its a Mac you will need the program from www.android.com/filetransfer . If its Windows you wont need that. Go in XDA and download whatever ROM tickles your fancy. Drag and drop that into your Ouya's storage. Now on the Ouya reboot to recovery (Via the Mods app)
Now im CWM hit the install zip from SD card, select the .zip of the ROM you chose, and install. Now wait until its all done, reboot, and enjoy!
*IF YOUR OUYA GETS BRICKED, NEITHER I NOR RE-MI NOR ANYONE EXCEPT YOURSELF ARE RESPONSIBLE!*
Good luck! If this helps be sure to thank Re-Mi!!!

[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