Related
THIS IS STRICTLY A GUIDE TO PRE-PARE YOU ON HOW TO SET-UP ANDROID SDK AND ADB DEVICES(DRIVERS), IF YOU ALREADY HAVE THAT SET-UP YOU CAN SKIP TO EUGENE'S POST ON HOW TO ROOT MYTOUCH SLIDE.
Last Updated:6/29/2010 at 11:36PM
Any other issues to deal with the actual process to root your mytouch slide should be directed toward his thread. Thank you for reading.
Okay so after about 4 hours of reading and asking questions I finally got my device rooted. My biggest problem doing this was that the guide in this forum was basically showing you how to root the phone if you had previous experience with androids and android SDK which I did not.
Note: If you have SDK installed already on your pc please delete your SDK folder and start from scratch for best results with my guide.
1. download Android SDK.(You will not have to use Android SDK physically but you will need it installed on your pc to root your phone) Save it to your PC where you can find it.
2.Extact the .zip file, do not rename just yet for the sake of my guide you also may delete the .zip file of it to keep clean.
3a. Move android-sdk-windows* out of the android-sdk_r06-windows folder onto the root of your C:/ drive.
*=the name of the folder may be different if you use a different operating system but since I do not own the other systems I cannot really tell you what the folders name.
3b.Now that you have the folder in the correct place you can rename the folder from "SDK-Anroid-Windows" to something easier such as "SDK" "Android" or something else which you will remember has to do with SDK.
This next part is not required, if you do not feel comfortable doing this, then don't, there is other ways around this.
3c.You also have the option to change your the path of your directory on your system. To do this, follow the instrustion here on step 2.( I would like to thank fermunky for his input)
My directory was pointed to the C:/Program files so I switched it to C:/android/tools , for those who do not know what this does it simply makes it so you do not have to change directory in step 7 (CD), you will only have to open your command prompt and then your ready to enter "ADB devices" .
4.Install the correct ADB drivers from pdanet . Select the proper download based on your OS if you do not know what bit you are using click start, right click computer, click properties, the system type will show you the proper file to download. and save it to your computer where you can find it.
5.Start the installation process for the ABD drivers, Follow the on-screen directions to install the drivers ( make sure your phone is not plugged into the pc at this time)
6.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools**
**=your file directory might be different than this, it depends what you renamed your folder
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.***
***=If it is correctly connected you will see a device listed and under attached it should say device.
After you have this all set up you are ready to root your phone via the guide from Eugene.****Remember you need to add the contents from his root.zip file into the tools of your SDK folder in order to root your phone.
****=Eugene's guide has changed since I wrote this but you still are ready to follow his steps. I plan on rooting someones slide soon based off his steps and will edit here if I need to add anything)
Thanks for reading.
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
the other guide mentions to create a new variable such as:
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Click to expand...
Click to collapse
so would i follow this? or list that directory under the already-enabled PATH variable?
Yeah just use the existing PATH variable, and only need the path, no need to include variable names.
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
For the uninitiated, and yes it's common sense
When I was using Windows (as I'm using Ubuntu now), and reading all the adb guides, for ease of use and to prevent people from getting confused, they name the sdk as "android-sdk-windows", which is fine for a newcomer (it's the same for Ubuntu except the "windows" part and the slash direction \ vs. /). However, you can name it whatever you want. You just need to make sure to have the same name in your path. For example, I'm lazy and my typing skills aren't that great. I don't want to type 19 characters (yes, I counted). So I just named it simply "android". 7 characters from 19. Its way more efficient for me. I've contemplated naming it "andy" or something to shorten it further. But, again, you don't even need to name it anything android related. You can choose to name it r2d2 (see what I did there?) if you want! Just my 2 cents. Thanks!
Yeah I could of renamed it something different but I didn't think about that til after it was written, I will fix it as soon as I am on an actual pc. I will also include how to do it via mac and ubuanta(sorry if I miss spelled)
kingofyo1 said:
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
Click to expand...
Click to collapse
Thanks kingofyo. Glad I could give back to this forum after all it has done for me. And if I find any other helpful tips to help make rooting easier I'll be sure to include it.
Sent from my T-Mobile myTouch 3G Slide using XDA App
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
I will leave that as an option for others to pick if they want to do that, as some might not want to change their directory to follow that path.
oo, this cleared up a few things for me! thanks!
eff0rtless said:
oo, this cleared up a few things for me! thanks!
Click to expand...
Click to collapse
ah what pat of seattle do you live in? I live up in mukilteo.
rlacsamana1989 said:
7.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools (your file directory might be different than this, it depends what you renamed your folder)
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.
Click to expand...
Click to collapse
when typing in 'adb devices', i get this message:
Code:
adb server is out of date. killing...
* daemon started successfully *
however, it does continue to list my device as attached.
the full message is:
Code:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HTxxxxxxxx device
*the x's do represent a valid serial number
-------------------------------------------------------
is this a problem? and will i run into any problems trying to successfully root?
note: i have done a search on this and the results returned as the program DroidExplorer being the culprit, however, i do not have that program installed.
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
rlacsamana1989 said:
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
poetik517 said:
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
Click to expand...
Click to collapse
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
cdt82002 said:
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Okay my guide is to set you up to root, you need to download slideroot.zip from eugene's how to guide. It will download a folder so you need to save it somewhere you will find it. Once you have it saved extract the files and the files within that folder you need to put in the tools of the sdk directory. Do not just drop the folder as that would change the directory even more to another folder. A file in that folder is what actually makes the loop feature work and there are other things you will need from that folder to root.
And to this. %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
you just need to delete "Program Files (x86)\QuickTime\QTSystem\"
and then replace it with your directory to your C:/
rlacsamana1989 said:
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Click to expand...
Click to collapse
a successful uninstall & reinstall of the sdk worked for me. i no longer get the 'adb server is out of date' message when trying to list devices.
when reinstalling all of the packages in sdk, i did note this message:
Code:
'Downloading Usb Driver package, revision 3
Installing Usb Driver package, revision 3
Installed Usb Driver package, revision 3
Updated ADB to support the USB devices declared in the SDK add-ons.
'adb kill-server' succeeded.
ADB: * daemon not running. starting it now *
ADB: * daemon started successfully *
'adb start-server' succeeded.
but its a good thing =]
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
poetik517 said:
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
Click to expand...
Click to collapse
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
usbdeview
rlacsamana1989 said:
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I think the program you're trying to remember may be "usbdeview"? This program allows you to disconnect or uninstall drivers.
*****To all newebies(as quite a few new people are at this forum because they got their first device! (TFP)) any anyone who wants to learn, let’s get educated about our devices!*****
ADB (Android Debug Bridge) is an extremely useful tool that WILL help you in all of your customizing needs! You may see the need to use ADB commands to help root your device, change ROMS, or send your device a fix. Without the knowledge here, you could easily be left in the dark.
ADB is a necessity for developers and general consumers alike. Knowing this tool is a great advantage to you to help your device at the best quality possible.
Installation
Download Google SDK
Choose the correct operating system and install!
The installation REQUIRES Java JDK which can be downloaded from Here
If during installation it asks for JDK (and you have installed it) Press the back button and next again, sometimes that will fix the error.
**Note** The SDK installs to C:\Program Files (x86)\Android\android-sdk standard, chose any directory for you
Start the SDK and immediately, you will notice a few checkboxes. For the standard user, just make sure Android SDK Platform-tools (under Tools) and Google USB Driver package (under Extras) – the drivers are always good to have, latest ADB drviers.
Click install 2 packages and wait. Once installed go to your installation directory and find the platform-tools folder. This directory is your ADB and will be your lifeline!
**Do you want ADB accessible through any command prompt directory?**
You are in luck. (For Windows 7)
Right click on My Computer > Properties > Advanced System Settings >Advanced (Tab) > Environment Variables > Under System Variables scroll and dbl click on Path
TO THE END of the Variable value line add
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Or whatever the directory you installed to + platform-tools
Open CMD and type ADB, if you did it right, you will see proper ADB jargon regardless if you are in the correct directory or not!
Congratulations! ADB is installed!
**Make sure your device is using the latest drivers (that you just downloaded) or other ADB drivers provided by ASUS to access ADB. When connected in Debugging mode, device manager will have: ASUS Android Composite ADB Interface**
ADB Usage
**I will be talking mainly about commands/arguments that the general end-user may use or come across**
**Make sure your tablet is in USB Debugging Mode to be able to connect to ADB (Settings > Applications)**
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
ADB start-server : This command will start the server if the server is off or killed. (Normally server will auto-start when ADB command is used)
ADB kill-server : This command will close ADB server. Useful if ADB server is acting up or not connecting to any devices.
ADB remount : This command will mounts the /system/ partition Read/Writable pending the device is allow to. Stock TFP will NOT.
ADB root : This command will restart ADB with root permissions if the build allows for it. Stock TFP will NOT.
ADB usb : This command will restart ADB on device to use USB connection for ADB communication.
ADB tcpip [port] : This command will restart ADB on device to use TCPIP connection for ADB. Standard port is 5555. Again, this connect not recommended for file transfers.
ADB reboot [recovery/bootloader] : This command will restart your device. If either of the two options are given, the device will boot into that mode (sadly TFP does not support the two options.. yet)
ADB Tips/Tricks
When following ADB instructions, follow them WORD-BY-WORD in the EXACT ORDER GIVEN. If copy and pasting their commands (one line at a time) makes it easier, then do so.
If you have root access, do not mess around in ADB shell unless you know what you are doing
Connecting over IP can be beneficial for you for quick ADB access, but for file transfers, speed is slow and you ALWAYS risk corruption (check the md5!) One bad file and you have boot-loops!
ADB Logcat is an amazing command. If anything is wrong with your device, 9/10 you can see it in logcat. If you can find the exact problem, fixes can happen much easier. USE LOGCAT TO YOUR ADVANTAGE!
ADB reboot can be a quick reboot, sometimes you don’t feel like waiting!
Use the environmental variables! It helps exponentially, and keeps from having multiple instances of ADB running.
When multiple instances of ADB are running (different directories) ADB can get messed up! (ADB not up-to-date restarts, and connect problems). ASUS Sync service has and ADB setup. Turn it off if you are not using it. Try to stick to only ONE instance of ADB
Eventually, we may have root access in our recovery kernel. Then and only then can our devices be truly customizable!
The GUIDE is not finite. Please post anything you feel should be added/corrected to the guide. Please take notice from this, as the understanding of these simple commands could help save your device(s)!
Thanks and 5 star would make me feel good inside too!
Wow... Nice post. Lots of time went into this lol. Thanks can't give the five stars in the app though:-(
Sent from my Transformer Prime TF201 using xda premium
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Lock-N-Load said:
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
biggem001 said:
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
Click to expand...
Click to collapse
before you fixed it, it was trying to use this http://http://developer.android.com/sdk/index.html"
note the extra parens at the end and the double http call
i noticed that too, all i did was re-save and it worked. how weird.
Thanks! I've seen a few tutorials on this but this one was by far the easiest to follow and best organized. Short and sweet. Worked on my desktop great, I've never managed to install it right D:
Re posting to give 5 stars. Thanks again OP
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
cmat1120 said:
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
Click to expand...
Click to collapse
i can do either at once.. thats weird
GPS, Wifi and BT Testing
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Thanks - Great Info
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
theandies said:
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
Click to expand...
Click to collapse
i wont add it to the guide, because adb install is pretty self explanatory but this
make sure you can install non-market apps
Code:
adb install app.apk
jonalisa said:
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Click to expand...
Click to collapse
for GPS, use GPS Test app on the market
for BT and wifi testing, i'll just connect my device via BT or adhoc wifi and do the testing on my PC itself, more accurate and better programs
Excellent howto, thanks
I have trouble connecting to my prime with adb. In the Win7 Device Manager the correct device shows up, no exclamation mark at all, but adb just won't see the Prime.
USB debugging mode is on, no Asus Sync software on the PC. I have no clue why ADB won't see my device.
Now many of us can really shoot ourself in the foot.
by far the best and quickest adb install/setup ever. thanks OP!
neo1738 said:
by far the best and quickest adb install/setup ever. thanks OP!
Click to expand...
Click to collapse
aw shucks!
THANKS!
biggem001 said:
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
Click to expand...
Click to collapse
Just a small suggestion, adb won't accept commands if they are capitalized.
For example "ADB devices" will work perfectly, but "ADB Devices" won't.
So, in order to help the newest of newbies, you might want to put the commands in lowercase in the first post.
I've got a droid razr; rooted, stock rom
I broke the screen accidentally and now the screen isn't showing anything and touch isn't working.
I'd like to recover all the data off my device, but since it's locked, it won't budge. Drives won't mount when I plug it into my PC.
I've got a previous backup which is a little older, but i'm interested in backing up the actual databases (texts, call logs, etc) and system data too, along with my images and personal data.
Is there any way I can perform a whole backup while the system is locked like this?
I've already searched the forum for previous threads with similar issues, but I couldn't find one with a viable solution.
Any help is appreciated, thanks in advance.
Partial Update
Hey all-
I've partially solved my problem.
I was able to get ADB working miraculously. I downloaded the Motorola Device Manager and installed it, also downloaded the Android SDK/Java SDK;
Using the sdk manager i installed the google usb drivers (im not sure it helped any way, but just in case)
after that I ran through the process of adb
Code:
adb kill-server
adb start-server
**plug in device**
adb wait-for-device
adb get-serialno
From there I was able to use "adb shell" and navigate around the file system; used su, went to /data/system/ and did "mv gesture.key gesture.key.bak"
I then restarted my phone and did a repeat of wait-for-device, and get-serialno just to verify the phone was connecting properly.
I then browsed to my computer and amazingly, the drives mounted, my sdcard, and sdcard-ext as removable drives and I was able to view the contents.
-------
So now, I'm stuck here with a device that's NOT locked, I can view my files, and I can navigate the file system.
My end goal is to be able to copy everything from /data/ to /etc/ /system/ /root/ /sdcard*/ /vendor/ /xbin/ and any other system file that's not available through the mounted drives.
I'll keep this thread updated, and if anybody has any help or clue on how I'd do this, it'd be greatly appreciated.
So far I've tried variations on "adb pull" using / as a root dir; trying to find a way to use the shell to invoke scp, ssh, or some other file transfer, but I get no network connection. While in the adb shell and doing any file operations, I get an error stating that it's a read-only file system as well.
Fixed
I just wanted to let you all know that I've resolved my problem.
Let me state the issue again.
- Screen and touch broke.
- Device locked with pattern
- Rooted
- ICS - Stock Verizon ROM
- USB Mode was UMC, not PTP/MTP
- USB Debugging enabled
I used ADB to delete /data/system/gesture.key and rebooted, effectively removing the device lock, and allowing drives & data on my SD cards to show up in explorer after a reboot of the phone.
After futzing around for a bit, I realized the phone was tied to my Google account, and I remotely installed "Droid VNC Server" (app name org.onaips.vnc)
From there I found a way to activate the VNC server through the ADB command line
Source: android.stackexchange.com/a/31957
Code:
Application located in
/data/data/org.onaips.vnc/files
With a root shell, run this
chmod 766 /data/data/org.onaips.vnc/files/androidvncserver
Then you can execute the vnc server from the command line
/data/data/org.onaips.vnc/files/androidvncserver
Run this to forward the port
adb.exe forward tcp:5901 tcp:5901
On your VNC client, connect to localhost:5901
From there I was able to get access to my home screen and pulled the notification drop down and changed from USB Mass Storage to Camera/Media Mode
Rebooted the phone, started the vnc server again, connected to it and moved some files around to my SD Card
In another adb shell as root, I was able to copy files from /data/data/ (or anywhere else I wanted) and write them to anywhere on /sdcard-ext/
From there in another command shell, I ran adb pull /sdcard-ext/datafolderfile
=========================================================================
I believe this to be the overall gist of things, though I ran into hiccups along the way, while I was messing around, I changed some permissions which caused my su executable to break and only be allowed to run shortly after booting the phone; and also because of the broken screen, something would cause the phone to reboot every so often, breaking my connections, backups, file transfers, and etc
There's also a cool option in adb
Run
"adb backup" and it'll give you all the switches, you'll have to confirm the backup on your phone, so be sure to be running VNC and confirm it, but adb backup should be able to grab everything you need. Like I said it didn't work for me because my phone would reboot;
I hope everybody that sees this can benefit from it
Annafunny said:
So did you extract your data from your Razr with adb finally?
Click to expand...
Click to collapse
This thread is really old (4 years)... and the answer was provided.
To avoid further issues, closed.
Your problem: You have a Nook Tablet running CM10.1 or above, and have been trying to get ADB working on Linux with no results. Android 4.2.2+ OSes have security measures (such as RSA fingerprint matching) that disallows unknown computers to use ADB. On the one hand this is good, but on the other, it's a major pain in the ass. What's even more retarded is, the POPUP SHOWING IF YOU WANT TO ALLOW YOUR COMPUTER TO USE ADB DOES NOT SHOW UP, but only on Linux for some reason. The majority of Windows users using ADB on the NT have no problems at all.
Your issue: I'm having problems getting ADB to work with the Nook Tablet on a Linux distribution! HALLLP!
Your issue: Hallp! My device shows as being "unauthorized"!
SOLVED! Here is the simplest solution I have found.
So, I spent literally weeks looking for a solution, tearing my hairs out, to this problem and I found absolutely NOBODY who knew the answer, except this ONE person, who is apparently the only one besides me that is using Linux. This person DESERVES a medal for a short and simple answer. http://stackoverflow.com/questions/...ed-nexus4-device-in-the-adb/18542792#18542792
Noob friendly version below:
Step one: Copy over your adbkey.pub located in your .android (hidden) folder, located in your home directory most likely (unless you use a root account all the time like a mad man), and put it onto your Nook Tablet's SD card somehow (for example, you can use an FTP server if you do not have an external SD or a card reader around).
Step two: On your Nook Tablet, open a terminal and "cd" to your sdcard's location.
For the internal SD, it's usually /storage/sdcard0 ; for external /storage/sdcard1
(ex: you would type in: cd /storage/sdcard0 )
Step three: Gain superuser access. Type in "su" and allow once.
Step four: Remove the previous adb key located on your Nook Tablet
Type in: rm /data/misc/adb/adb_key
Step five: Append your key, located on your sdcard, to the following location
Type in: cat adbkey.pub >> /data/misc/adb/adb_keys
(Make sure you type in ">>" instead of one ">" because a ">>" means "to append/add" but a ">" means "to replace")
(For each additional computer you want to use adb with, you would simply copy over the adbkey from that computer and follow the same steps)
Easiest and last step: Reboot your Nook Tablet.
Kill the adb server on your computer: adb kill-server
After the Nook Tablet reboots, plug in the USB cable to your Nook and PC, now type in "adb devices. It will be recognized at last!
(I don't really think the reboot was necessary, but oh well).
TL;DR version below (for experienced users):
Code:
rm /data/misc/adb/adb_key
Send adbkey (adbkey.pub in ~/.android/) from computer to device
adb kill-server
cat adbkey.pub >> /data/misc/adb/adb_keys
adb devices
adb shell
Rejoice! ADB finally works!
Don't forget to leave thanks! Press the damn thanks button, how lazy are you guys?!? :victory::victory:
Bump
BUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUMP
Seriously? not a single one of you brainy people know what's going on? and not a single one of you run Linux and happen to have a Nook Tablet?
sagirfahmid3 said:
BUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUMP
Seriously? not a single one of you brainy people know what's going on? and not a single one of you run Linux and happen to have a Nook Tablet?
Click to expand...
Click to collapse
The vast majority of people here have no need whatsoever to use ADB with their Nooks. I think many with an interest of developing (that are the only ones that have a real need for ADB) have moved on to other devices and probably don't check in here much. Sorry to be the barer of bad news.
Out of curiousity, why do you need ADB? I suspect you are fiddling with something fun and intersting. Anything you want to share? If it's interesting enough maybe you'll get more attention! One can always hope...
Yuh huh, I plan on installing Debian on the Nook Tablet and Nook Color following this guy's directions. Since they both have an unlocked bootloader, I'm hoping it wont be too difficult.
http://whiteboard.ping.se/Android/Debian
He also posted the tutorial on this site as well: http://forum.xda-developers.com/showpost.php?p=28943303
BUMP (wanted to push this up the thread in case someone using Linux is having trouble getting ADB working).
SOLUTION IS LISTED AS THE FIRST POST!
Are you sure to delete
"/data/misc/adb/adb_key"
and recreate
"/data/misc/adb/adb_keys"
?
/////
Ok, for me adb_key didn't even exist, and inserting my public key into the /data/misc/adb/adb_keys file worked (despite having bugs shown in dmesg!)
Now, I just need working mtp or usb storage....
/////
Wow, and even this seems to work now, it was just a question of setting/changing the settings when looking at the options for "storage" - maybe there is an initial setup problem in CM10.1, hmmm...
Thank you very much!
bluesock said:
Are you sure to delete
"/data/misc/adb/adb_key"
and recreate
"/data/misc/adb/adb_keys"
?
/////
Ok, for me adb_key didn't even exist, and inserting my public key into the /data/misc/adb/adb_keys file worked (despite having bugs shown in dmesg!)
Now, I just need working mtp or usb storage....
/////
Wow, and even this seems to work now, it was just a question of setting/changing the settings when looking at the options for "storage" - maybe there is an initial setup problem in CM10.1, hmmm...
Thank you very much!
Click to expand...
Click to collapse
No problem! Thanks for your feedback. If there is any way I can make this small guide better, please let me know :victory:
Hi, I hope I am posting in the right section? I found the site really difficult to navigate having never used the site before. If its in the wrong place please can a mod move it.
Ok so I have an Android Set Top Box (STB) and I am trying to extract all the data from it. It is an mxp pro 4k. I don't want a backup of the data I want to extract full images of the device for analysing with forensic tools. The problem is I can't seem to communicate with it. I have the full SDK that is up to date, once navigated to the platform tools folder I opened a command line and typed
Code:
adb devices
after plugging in a USB cable to the OTG port. No prompts appeared on the screen to trust any connections like my iPhone does when I connect it. Adb devices returns no results. So I tried wireless adb, I typed
Code:
adb connect 192.168.x.x
and it said connected. Then when running the devices command I had the ip and port then the word device. I then get a shell by using
Code:
adb shell
Which i then elevate to root by using
Code:
su
. Then when i try an adb pull or adb backup I get a message saying error device offline.
Im new to Android so not even sure I am doing it right. I have done a lot of reading and research but seem to be stuck with the basics. To confirm USB debugging is turned on.