Related
This post will no longer be updated and is pretty much for the archives at this point. It detailed the rooting process for Linux users right after the Slide was first rooted. Since then, newer, more foolproof methods have been devised. For those rooting their phones today (or any point since T-Mobile's OTA update), please see this link: http://forum.xda-developers.com/showthread.php?t=780213. It says it's Ubuntu-specific, but the instructions there should apply to any GNOME desktop and any other desktop with slight modification. Thanks for the comments on this thread. I hope it helped.
Most of this is not new information, but it's all in one post for the first time. I post it in case Linux (and probably MacOS) users need clarification on the process. It should keep people from having to dig in deep threads to find all the info needed. I only added the loop.sh for Linux and the partitioning information.
For all the following, I assume that the reader knows how his computer works, but not necessarily Android rooting.
Preliminary Information
1. As always, make backups and take notes. You might want to make a list of installed apps you want to reinstall later, for example.
2. Install adb. Download it here: http://developer.android.com/sdk/index.html. adb is a little program distributed as part of the Android software development kit (SDK). Its job is to communicate with the phone from a shell (terminal). To install adb, I strongly suggest you copy the adb file from the tools directory into your system's /usr/local/bin directory. This way, it will always be in your path. If you don't intend to do development work on Android applications, feel free to delete the rest of the SDK after installing adb.
3. Start adb as root. In more traditional Linux distros, this can be done by typing "adb devices" in a root terminal ("su" then "adb devices"). In Ubuntu-based distros, "sudo adb devices" followed by your password should do the trick. You'll get a message about the adb daemon being started. If not, sometimes typing "adb root" or "adb start-server" as root will do the trick.
4. Make sure your phone has "USB Debugging" checked off in Settings > Application > Development
5. It may not make any difference, but I turn off the "disk drive" option, so that my SD card doesn't mount when the phone is plugged in via USB (unless I need it to).
Partitioning the SD Card (Optional)
This is an optional step, as ROMs are coming out now that allow swapsace (virtual memory) and apps2sd (installing applications to the SD-card rather than on the phone's internal memory). Right now, most Slide ROMs support apps2fat32, so the whole card can be left as is (one, big, fat32 partition). If your desired ROM supports apps2sd using an ext2 or ext3 partition, you can save some headache later by doing this step first. If you don't want it, just skip to the next section.
1. Using the package manager for your Linux distro, install parted. GNOME users have a great, graphical frontend to this utility called gparted. KDE users have the KDE Partition Manager available to them. I only have gparted, but the instructions should be similar for all variants. The graphical frontends take a lot of the pain away from using parted (automatically formatting for ext4, for example). For the braver souls, there is a much more detailed tutorial for using vanilla parted from the command line here: http://forum.xda-developers.com/showpost.php?p=4098568&postcount=1.
2. Mount your sd-card, either using the "disk drive" function of the phone, or in an external card reader.
3. Make a backup of your sd-card by simply copying and pasting to a new folder.
4. Start up the partition manager of your choice with root permissions (using gksu or kdesu).
5. Make sure your desktop environment (KDE or GNOME) or a terminal doesn't have a file manager window open to the sd-card partition. You can't unmount a partition that's being accessed.
6. Find out which device node is assigned to the partition by typing "dmesg" in a terminal. The last few lines should tell you how it's assigned. Mine was /dev/sdg1, for example.
7. Using the dropdown menu, select your sd-card partition in parted.
8. Right-click on the partition in the bottom pane of the window and select "unmount".
9. Delete the partition using the same, right-click menu.
10. Now you're left with free space to configure as you see fit. You use the same right-click menu to create partitions.
11. When done, click "apply" and the partition manager will create and format the partitions you've selected.
12. When done, the computer should mount two partitions from the card, one for apps, the other for user data. Copy your backed-up files to the larger partition.
NB: Android phones can work with a smallish ext* partition at the beginning of the card for apps (around 512MB should be more than enough for almost anyone), a super-small swapspace in the middle (no more than 32MB, if any at all--it's up for debate whether the Slide benefits from swapspace at all), and the rest of the card formatted as FAT32 for the "normal" partiton. I'll leave those decisions to those who have the need and desire. Also, whether to use ext2,3, or 4 for the apps partition is a matter for debate, and some kernels for other phones didn't support the newer versions at all. All that is beyond the scope of this howto, mainly because I won't be trying it out.
NB2: Eugene has released Koushik Dutta's recovery scripts that can help automate the partitioning process. It can be done directly from recovery, rather than on the computer. I much prefer the old way, as it gives more flexibility. For reference, the post with instructions is found here: http://forum.xda-developers.com/showpost.php?p=6993132&postcount=1.
Getting root (original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1)
The following instructions are "the old way" to gain root. There is a new method found at: http://forum.xda-developers.com/showpost.php?p=7658764&postcount=1 that seems to be a saner process, but I have not tested it as of yet.
1. Download the Slide Root package: http://outboundlink.us/anxo/dr_ta_1...ttp://www.4shared.com/file/IfrPbWG7/Root.html
2. Extract it somewhere convenient (I'm using the Desktop folder here. I'm also renaming the folder "slideroot" to keep things simple).
3. Open a terminal and cd to the slideroot folder you just created.
4. The "loop.bat" file here is of no use to you. Use a text editor to make your own loop.sh file, or edit loop.bat and rename it when you're done. It should contain the following:
Code:
#!/bin/sh
watch -n .50 adb devices;
done
5. Power on the slide while holding down the Volume-down button. This will bring you to the bootloader screen (three droids on skateboards). Plug the Slide in via USB.
6. Just to make sure everything is working correctly, type "adb devices" in the terminal to make sure the system is seeing your phone properly. If so, run your loop.sh by typing "sh loop.sh".
7. Use the Volume-down button on the phone to select "recovery" and press the power button to enter. The terminal will flash a few messages like "offline" and "recovery". When the phone's screen shows an icon of a phone with a red triangle, you know it worked.
8. Press Volume-up and Power together to enter the recovery menu on the phone.
9. Now, back in your terminal, hit "ctrl-C" to cancel the loop.sh script.
10. Type "adb push ota.zip /sdcard/update.zip" and hit enter.
11. Type "adb push update.zip /sdcard" but DO NOT hit enter yet.
12. This step requires some coordination and timing. On the phone, select "run update.zip" and press the power button. When you see a little greenish progress bar at the bottom in the background, hit enter in your terminal.
13. If it worked as planned, the phone will see the keys from the first file you pushed, and then use the file you're pushing now to run clockwork recovery. If not, don't worry. Just repeat. I haven't had to do it more than once yet.
14. Once this is done, reboot the phone from the menu system and wait. You can use "adb devices" in the terminal to see if the phone is detected.
15. Type "adb shell" and look for the "$" prompt. If you type "su" you should get a "#" (root) prompt. Give yourself a pat on the back.
Installing the Engineering ROM (original HOWTO at http://forum.xda-developers.com/showpost.php?p=6821968&postcount=1)
A. Now that your phone is rooted, you can "downgrade" it to the Engineering ROM. This gives a better recovery environment that allows other ROMs to be installed (custom ROMs are signed with the test keys; the original recovery will not install them since it looks for your carrier's keys.)
B. Download two files: http://outboundlink.net/anxo/dr_ta_1/goto.php?DR_id=1359&linkout=http%3A//www.4shared.com/file/OsmF_ZD7/ESPRIMG.html and http://www.4shared.com/file/sz0VO2TL/SlideEng-package.html.
C. I extracted the SlideEng-package.zip, copied the contents inside loose to the Desktop, and copied the ESPRIMG file to my sd card.
1. cd to the Desktop and type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.
3. Start an adb root shell as above ("adb shell" then "su")
4. Type "cd /data/local"
5. Type "chmod 04755 mtd0.img" and "chmod 04755 flash_image". I didn't change any permissions on the other files in that folder, just in case.
6. Type "./flash_image misc ./mtd0.img" and hit enter.
7. Power off the phone.
8. Holding Volume-down, power the phone back up. The recovery will scan the sd card and automatically detect the update file (from step "C" above) and prompt to install it. Hit Volume-up to install.
9. You're done. Just reboot the phone after the update and you're good to go. The boot process will be a little longer this time around.
Updating the Radio (May be optional) (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6856313&postcount=1)
I leave this section here for archive purposes. Since switching the ROM to ChiefzReloaded's OTA in the "Installing a custom ROM" section below, this step is no longer necessary, as it contains the newest radio. Unless you're installing a custom ROM released before the last T-Mobile over-the-air update, feel free to skip this section.
When we downgraded the system to the Engineering ROM, we downgraded our radio as well. The following instructions will bring us back to the stock radio version.
1. Download the following file: http://files.androidspin.com/downloads.php?dir=chiefzreloaded/ROM/&file=Newest_Slide_Radio.zip and copy it to your sd-card.
2. Remember that update.zip way back in the rooting section? The one found in the slideroot package? Copy it to your sd-card as well, if it's not already there. I deleted the one on my sd-card and re-copied it, just in case. It contains the clockwork recovery and can be left on your sd-card for future upgrades.
3. Reboot the phone into recovery (should be easy now.)
4. Select "apply update.zip from sd card" to start clockwork recovery. No looping necessary anymore!
5. From the clockwork menu system, apply the Newest_Slide_Radio.zip file you just copied over.
6. Once that's done, just reboot. The boot process will take longer and you'll see a few crazy icons before the system finally loads up. When all is finished and you're back to the home screen, the phone will pop up a dialog telling you the update was successful.
Installing a Custom ROM (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6827968&postcount=1)
For this install, I'm using the new OTA update rooted by ChiefzReloaded. Complete information on this ROM is here: http://forum.xda-developers.com/showpost.php?p=7534163&postcount=1. Like the older SLIDEMEROOT2 I had here before, I picked it because it's mainly the same, stock ROM the phone shipped with, but with root. I had way too many "fast, stable, feature-packed" custom ROMs on other phones that really weren't that fast or stable. I don't want to lose the use of my camera/camcorder to have live wallpapers, for example. These instructions will work for any custom ROM (adjusting for the new ROM in step 1 and 4.)
1. Download the following file: http://db.androidspin.com/androidspin_filedownload.asp?release=330&type=1 and copy it to your sd card.
2. Boot the phone into recovery mode.
3. From the recovery menu, select "apply update.zip from sd card". As stated earlier, this update.zip file contains the clockwork recovery. Applying it like an update will always load clockwork from now on.
4. In the clockwork menu, select "apply any zip from sd card" and select CR_Mod_1.35.531_OTA.zip.
5. Let the update take its course, reboot, wait, and enjoy.
Going Back to Stock (Just in case) (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6994424&postcount=1)
There may come a time when you might need your phone just the way it came from the store. It could be that you're tired of custom ROMs, a feature you find you can't live without is broken, or you need to return the phone for warranty purposes. If it gets to that point, here's how:
1. Download the following file: http://outboundlink.net/anxo/dr_ta_1/goto.php?DR_id=1359&linkout=http%3A//www.4shared.com/file/x7HRRsbM/ESPRIMG_2_.html and copy it to your sd-card.
2. Reboot the phone into recovery (just the regular one, not clockwork). The file will be automatically detected.
3. After checking the file, you'll have to hit Volume-Up to confirm the flash.
4. Once done, reboot and the Slide will be good as new.
Very nice!
I kind of wish I would have seen this before I rooted this morning!
I just rooted mine this afternoon. Figured I'd put it up while I still had it in my head.
Excellent summary!
I also wish I'd seen this before muddling through the other guides myself. Thanks for posting it!
Quick question. I plan on rooting my MyTouch Slide within the next couple days. I was just reading over your list and thought I'd try to move the adb file first. After I moved it to /usr/local/bin, and then opened a root terminal. I typed "adb", but nothing came up about a dameon being started. It looked like I had asked for the man page. Any idea why? Or if it started it anyway?
The first time you run adb, do so as root "sudo adb devices", "sudo adb root" or the equivalent. It will start the daemon. A normal user (ie, not superuser) will not have the permissions to start a daemon.
When you run just "adb" without any options, it shows you the command-line options you can use with adb. Most Linux command-line apps work the same way when run without options.
beartard,
huge props to you. this is, by far, the best guide for rooting anything that i have ever used, and certainly for the slide.
as mac osx is a *nix system, this worked great. none of the steps were missing, everything was a normal sized font, and left justified, and took me from the stock to a custom rom flawlessly.
thanks a bunch.
really.
I'm very glad it worked for you. Thanks! Did you have to do anything differently under MacOS? I used to use it before OS X came out. I know the newer versions are based on *nix, but I didn't know how similar they were underneath.
I didn't do very much differently.
I started with "How to get Root" section, as I didn't want to partition my sdcard and already had the SDK installed (obviously, though I really need to look into working with it more, as right now it scares the bejesus out of me).
I used a "do while [1]" style (I love accidentally rhyming) loop.sh file though, mostly because my terminal couldn't understand "watch" for some silly reason.
Your guide was just the one that felt the least like a tween myspace page (no offense to the other guides).
Ok, I am re-rooting my slide after having to get a replacement. I am trying to get it done using the newest ubuntu. I am a newb to ubuntu but I was able to get adb setup. When the device is booted up normally I can adb devices and recognize the device.
When I boot the phone into fast boot and adb it does not find anything. I went ahead and ran the loop.sh file and started recovery And saw the device pop up for a split second so I CTRL-C.
It does the same thing that it did when I rooted my old slide With XP. It saw the device but as soon as I CTRL-C its gone. I can do a battery pull, rerun the loop and boot into recovery and it wont find it.
Is this crap gonna be the same as on windows where you just gotta get lucky and get it to recognize? Sit here for hours on end every day until it gets recognized?????
By the way I am running everything as Root by typing sudo su in terminal before I start.
sultan.of.swing said:
Ok, I am re-rooting my slide after having to get a replacement. I am trying to get it done using the newest ubuntu. I am a newb to ubuntu but I was able to get adb setup. When the device is booted up normally I can adb devices and recognize the device.
When I boot the phone into fast boot and adb it does not find anything. I went ahead and ran the loop.sh file and started recovery And saw the device pop up for a split second so I CTRL-C.
It does the same thing that it did when I rooted my old slide With XP. It saw the device but as soon as I CTRL-C its gone. I can do a battery pull, rerun the loop and boot into recovery and it wont find it.
Is this crap gonna be the same as on windows where you just gotta get lucky and get it to recognize? Sit here for hours on end every day until it gets recognized?????
By the way I am running everything as Root by typing sudo su in terminal before I start.
Click to expand...
Click to collapse
I'm not sure what the problem is, man. I've never had to try more than once using the process above. You're using a new install of ubuntu. Do you have adb from the latest sdk?
Just added the link to a new method for rooting and updated a few minor points.
Updated partitioning info to reflect what's actually going on in the MT3GS world.
Changed custom ROM to ChiefzReloaded's OTA, eliminating the need for the "updating the radio" section.
Beartard, I want to say thank you for taking the time for typing this all out. It worked like a charm with not one problem. I have spread your link to others so they can get the same satisfaction I got from this thread. Thanks again
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
I bought the Motorola Bravo which is similar to the Flipside and an app on the market called Z4ROOT was able to root the phone. It works on many phones not just the Bravo. Give that try and see if it works.
z4root does work for permanent root i have tried and can confirm
jediskywalker said:
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
Click to expand...
Click to collapse
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Got my Flipside rooted and non market apps allowed
I followed the instructions given at modmymobile dot com forum. Look up "fully unlock 3rd party apps backflip" It allowed me to root my phone and install non market apps. I tried and tried to follow the instructions given here, but i guess they weren't idiot proof. It is for the backflip, but it worked perfectly for my Flipside. I couldn't post the link here.
Someone found some typos in my scripts. I have updated them so they are accurate. Should make things run better.
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
ishiiisbooyah said:
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
Click to expand...
Click to collapse
Lets say you installed your SDK in the default folder, you would need to type
Code:
cd c:\"Program Files"
cd Android
cd appinventor-extras
Now, I put mine in c:\SDK, so all I type is
Code:
cd c:\SDK
you either must add the SDK to your PATH, or find the directory that you installed it to, and then try running adb from there. If adb.exe isn't in the folder, you aren't in the right folder.
jonsjava said:
Rooting a Motorola Flipside
[/url]
Click to expand...
Click to collapse
hi
i m new in unlocking field
can i unlock this handset "flipside" by motorola came from usa at&T
if yes then plz explain
thanks in advance
RZ4root does not appear on the marketplace and when I click the link above it starts to download, then says the content is not supported on my phone.
Model num MB508 Motorola Flipside running Android 2.1 update 1.
You need to push it to the phone from a computer using adb to install z4root, now that it has been removed from the market.
Sent from my Liberty using Tapatalk
adb.exe not in the zip file
jonsjava said:
Rooting a Motorola Flipside
grab the ADB SDK files
android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
(...snipped...)
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Click to expand...
Click to collapse
adb.exe is not present in the SDK that you linked. Are you sure that is the SDK we need to root the Flipside?
You have to install it manually. It comes with the platform-tools.
how do i install adb.exe from platform-tools
lol, i may ask stupid questions but this one wasnt me, i shouldnt leave my laptop lying around haha
jonsjava said:
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Click to expand...
Click to collapse
Notice:
For anyone having trouble rooting the Motorola Flipside with these instructions, after much trial and error I managed to get my girlfriend's rooted. I'll provide the method I took.
Note: The easiest way to do this is to have downloaded and extracted "android-sdk_r08-windows" directly to your (C: ) drive. Not under programs or another system folder.
Once you have it extracted to (C: ), copy and paste z4root.1.3.0.apk into the "android-sdk_r08-windows" folder. ADB.exe will most likely not be in here. What you have to do now is click on SDK Manager within the SDK folder. A Black Command window will pop-up, ignore it. A secondary window will pop-up prompting you to install the packages I went ahead and installed all of them (better if you don't know which to install).
Now that they've all been installed, a command line will state that ADB has to be restarted. Let it restart and it should say completed.
Now -- here's where everything was messing up. When you click open the SDK-R08 folder, you should have the z4root.apk file right there amongst a list of folders. Go to the "platform-tools" folder and in there you should see the ADB.exe file. Ignore that for now. While in platform-tools press Ctrl+A so that everything is highlighted. Right click and select Cut, back out to the main directory of the SDK R08 folder and select Paste so that the ADB.exe, .dll, and all the other files from within platform-tools is out and listed alongside the z4root.apk.
Next - Follow all of the instructions up to "Plug in your phone, and have it set to "Charge only" Like JonsJava said, open up command prompt (type in CMD in the "search programs and files bar"). If you extracted the "android-sdk-r08-windows" file directly to the (C: ) drive, all you have to type in is...
(Note: Before I go into that, it'll be easiest to rename the file "SDK" instead of the whole "android-sdk, etc, name... I'll complete the instructions assuming you renamed it to SDK. Continued below... all you have to type in is...
cd C:\SDK
(The next line below will look like this)
c:\SDK>
Here, type in... adb install z4root.1.3.0.apk
Total should look like... c:\SDK>adb install z4root.1.3.0.apk
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Last note:
Uploaded with ImageShack.us
This is what the main directory of the SDK folder should look like before you enter anything in the command line.
I don't seem to be able to get this...
I'm using x64 windows 7, I have a Flipside MB508 on 2.1, and I can't get this to work.
I followed all the instructions, updated all the platform-tools stuff, and now my problem lies with the driver, I believe.
I installed those Motorola drivers that were linked, with my phone unplugged, successfully..
copied the apk to C:\SDK...
found adb.exe in the platform-tools folder..
...and this happened..
C:\SDK\tools>cd C:\SDK
C:\SDK>cd platform-tools
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
error: device not found
C:\SDK\platform-tools>_
"error: device not found" every time i try this
USB debugging is on, phone is plugged in set to charge only..
Windows even sees it, the taskbar eject icon says 'Eject MB508"
please please help me get adb to see my phone.. I really want to be able to root this thing!!
EDIT: I noticed the Motorola drivers are 32bit.. I'm going to try 32 bit windows 7 instead of 64 bit and see if I get more successful results
EDIT 2: Bazinga!! Installed Win7 32 bit on my other HDD, booted up, followed the steps again, worked flawlessly! Thanks a lot for the easy instructions, got z4root installed, and my phone worked with permanent root
ErebusRaze said:
Notice:
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Click to expand...
Click to collapse
You wrote in here that once rooted, thebphone would no longer have low memory issues...i rooted my wife's phone, was able to sideload applications (but for some strange reason I am now unable to, as adb command prompt states 'device not found')- but she still gets low memory issues at least 2-3 times a week...
I should just hold up a sign...
LINK2SD
Its in the market
Sent from my MB508 using XDA App
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
thehotrod11 said:
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
Click to expand...
Click to collapse
Link2sd makes installing to sd card possible on 2.1...
Sent from my MB508 using XDA App
A lot of people seem scared to use "adb" (Android Debug Bridge), or try it out and hit problems, then immediately give up.
I personally think that the method of rooting using adb (rage) is "better" than Visionary, because you have more control over the process and can see what it's doing. e.g. if there's an error message then you can see that, and ask for help.
But even if you don't use adb in rooting, it's still a very useful tool to have available. You can use it to run commands on your phone, copy files between your PC and phone, and to debug various issues that may occur at some point (plus lots more).
The guide in this first posting is for Windows, since I think this is what the majority of what people are using, and also it's what I use myself. Though you can use adb on Linux or Mac too. There's a Mac guide in the second posting, with a Linux guide "coming soon".
There are different ways to install adb. Below I list two methods, the first method I call "Complete", which involves installing the Android SDK (Software Development Kit), and the second "Quick" way. Either should be fine for rooting etc.
There's also a guide by gtrab in his useful FAQ posting (thanks !) HERE , which involves a very quick way to get it up and running (scroll down to the "Adb Mini Package" section).
INSTALLING ADB ON WINDOWS - METHOD A, THE "COMPLETE" WAY, USING THE SDK
Step 1
If you haven't done so already, then download and install HTC Sync from HTC's website.
You'll find it in the Support section for the Desire Z (works on the G2 too), e.g. at http://www.htc.com/www/help/htc-desire-z/#download.
This is HTC's software to sync various stuff from your phone to your PC, such as email, bookmarks etc. However, even if you don't need that stuff, HTC Sync has a bunch of USB drivers for your phone, and that's what we *do* need.
Step 2
Download and install the Android SDK (Software Development Kit) Starter package from http://developer.android.com/sdk/index.html
There are two choices for Windows there, a simple zip file which you can unzip somewhere appropriate on your PC (e.g. put it on C:\ if you like). Or there's an installer (which is the recommended option according to the Android website), though that forces you to download some Java stuff which we don't really need for adb and takes a lot longer to install (but there won't be any harm in getting). It doesn't really matter which one you pick though.
You can read all about how to install the SDK at http://developer.android.com/sdk/installing.html . Ignore all the stuff about Eclipse though, you don't need that unless you're going to start writing Android apps.
Step 3
Now we need to add the Platform Tools component to the SDK, because that contains adb.
Run "SDK Manager" on your PC. You will find that in the root directory of the SDK, so you can open up a file explorer window to find that, then double-click on "SDK Manager" to run it.
Wait for a few seconds while it checks on the Android website for updates etc, let it then pop up with a window showing you what is on offer.
Add the "Android SDK Platform Tools", you can "reject" (i.e. don't install) all the other things it offers you if you like, though there's no harm in installing them (just takes up disk space on your PC).
Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)
Step 5
On your phone, go into Menu->Settings->Applications->Development and make sure you have the entry "USB Debugging" ticked. adb will not work without this.
Step 6
Plug your phone into your PC using the original HTC cable. This is important, do not use a third-party cable since it might not work with adb (even though it might seem fine with other communication with your phone). If this is the first time you've done it since installing HTC Sync, you might have to wait while it installs additional drivers.
Step 7
Fire up a command prompt on your computer, e.g. "Run" then "cmd", or pick the "Command prompt" option from the menus, and type in the following (obviously the C:\> bit is your actual PC's prompt, not what you type). To emphasise, you are running this on your PC, not directly from your phone (e.g. terminal emulator) :
Code:
C:\> adb devices
This should display something like the following :
Code:
List of devices attached
XXX12345 device
... where the "XXX12345" bit is actually your phone's serial number. If the list is blank and the phone is plugged in ok, go back to Step 5 and make sure USB Debugging is enabled. If you can see your phone, then you're in business, adb can see your phone and communicate with it, and you're ready to start using adb !
By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output.
INSTALLING ADB ON WINDOWS - METHOD B, THE "QUICK" WAY, NO SDK
Thanks to amroush_1800 for the input on this.
Step 1
If you haven't done so already, then download and install HTC Sync from HTC's website.
You'll find it in the Support section, e.g. at http://www.htc.com/uk/supportdownloadlist.aspx?p_id=325&act=sd&cat=all.
This is HTC's software to sync various stuff from your phone to your PC, such as email, bookmarks etc. However, even if you don't need that stuff, HTC Sync has a bunch of USB drivers for your phone, and that's what we *do* need.
Step 2
Download this zip archive and unzip it somewhere memorable on your PC (e.g. into a folder on your desktop) - http://dl-ssl.google.com/android/repository/platform-tools_r04-windows.zip
Step 3
On your phone, go into Menu->Settings->Applications->Development and make sure you have the entry "USB Debugging" ticked. adb will not work without this.
Step 4
Plug your phone into your PC using the original HTC cable. This is important, do not use a third-party cable since it might not work with adb (even though it might seem fine with other communication with your phone). If this is the first time you've done it since installing HTC Sync, you might have to wait while it installs additional drivers.
Step 5
Fire up a command prompt on your computer, e.g. "Run" then "cmd", or pick the "Command prompt" option from the menus.
Use the "cd" command to change to the folder that contains the adb.exe and other files that you unzipped in Step 2.
Then type in the following (obviously the C:\> bit is your actual PC's prompt, not what you type). To emphasise, you are running this on your PC, not directly from your phone (e.g. terminal emulator) :
Code:
C:\> adb devices
This should display something like the following :
Code:
List of devices attached
XXX12345 device
... where the "XXX12345" bit is actually your phone's serial number. If the list is blank and the phone is plugged in ok, go back to Step 3 and make sure USB Debugging is enabled. If you can see your phone, then you're in business, adb can see your phone and communicate with it, and you're ready to start using adb !
By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output.
INSTALLING ADB ON MAC
The following excellent guide kindly provided by siedkins, please thank him and not me !
What you will need:
A Mac
USB cable
Android SDK for OSX- http://developer.android.com/sdk/index.html
At the time of writing this the version was "android-sdk_r08-mac_86" so please have a look at the above link and let me know if you can't find that same version.
So download the zip file and I would extract it to a folder where you are happy to keep it such as within your user home folder i.e. Macintosh HD/Users/{Your User Name} and for my mac it is Users/siedkins which is how I have my OSX set up.
Then open then still in Finder, open "android-sdk-mac_86" then "tools".
Now launch Terminal - ⌘ + space then type Terminal or Applications>Utilities>Terminal
Now drag and drop the file called "android" in the "tools" folder into your terminal window and you should see something like:
/Users/siedkins/android-sdk-mac_86/tools/android
Then hit enter - this should load Android SDK
Next go to Available Packages on the left and Android Repository > Android SDK Platform-tools, revision 1 -tick the box and hit "Install Selected"
It should download and install the Platform Tools which includes ADB !!!!
Now quit Android SDK after it has downloaded and go back into Finder. Now you should see a new folder "platform-tools" in the "android-sdk-mac_86" folder. Open that and you can now see a file called adb.
Now .... I am going to show you how to make your life a lot easier in Terminal to run ADB without having to navigate to the folder every time you want to launch it.
Go back to your Terminal window and type (or copy & paste):
Code:
cd ~
The screen should then look like
NAME_OF_YOUR_MACHINE:~ USERNAME$
For me I have:
Mac-Pro:~ siedkins$
Next, type
Code:
touch .bash_profile
to create your new bash / path file
Next, type
Code:
open -e .bash_profile
to open it in TextEdit.
Now into Text Edit please copy:
Code:
export PATH=${PATH}:
Then go into Finder and navigate your your "android-sdk-mac_86" folder. Then click on the "platform-tools" folder and drag and drop this into TextEdit at the end of the code above that you copied. Mine looks like:
export PATH=${PATH}:/Users/siedkins/android-sdk-mac_86/platform-tools/
Yours should look like:
export PATH=${PATH}:insert your path to the "platform-tools" folder in your Android SDK here
All you need is that one line. Then Save and exit TextEdit and then very importantly QUIT TERMINAL.
Now ........ to turn on USB Debugging in your handset Settings > Applications > Development > USB Debugging - ticked and also go to Settings > Connect to PC > Default connection type > Charge Only and also UNTICK "Ask me ..." there also. You can always go back here and change these settings back.
Now plug in your phone to a USB port. I noticed that if I plugged my phone into one of the standard USB ports on the front of my machine I couldn't see the phone further down the line and if I plugged it into a powered USB port on the front (I have an "akasa AK-ICR-08" which has a powered connector behind the 5 USB ports. But you guys will probably be using a MacBook or MacPro and there shouldn't be any issues with the power to your USB ports.
Now to launch ADB - re-open terminal (remember that you had quit it - very important!) then type in:
Code:
adb devices
And you should see:
List of devices attached
HXXXXXXXXXX device
where XXXXXXXX is your unique phone ID.
Now you can run all of your favourite ADB commands straight by typing:
adb shell
etc straight into Terminal. I won't go into that here as there are plenty of guides about what to do with ADB once it's installed!
Now you have ADB setup on your Mac and can run it without the need for installing HTC Sync - un-installing it - loading some modified drivers over the top !!!!
It all just works !!!!!!
INSTALLING ADB ON LINUX
Coming soon ...
USING ADB
There's a comprehensive guide to using adb, including all its commands, at http://developer.android.com/guide/developing/tools/adb.html
Here are a few example commands :
Code:
C:> adb push hello.txt /data/local/tmp
The above copies the file hello.text from the current directory of your PC (i.e. the directory shown in the command prompt) into the /data/local/tmp directory on your phone.
Code:
C:\> adb pull /sdcard/error.log error.log
The above copies the file /sdcard/error.log onto your PC.
Code:
C:\> adb install Superuser.apk
The above installs the app in the Superuser.apk file in the current directory of your PC, onto your phone.
Code:
C:\> adb shell
The above starts a command prompt session on your phone. So when you see the $ prompt, that's your phone and commands you type there will be executed on your phone.
Code:
C:\> adb shell ls
The above runs the command "ls" on your phone and displays the results. So it's a way of issuing one command at a time, without starting your own shell session. You can subsitute other shell commands for the "ls".
Code:
C:\> adb reboot
The above reboots the phone.
Code:
C:\> adb reboot bootloader
The above reboots the phone into the bootloader (hboot).
Code:
C:\> adb reboot recovery
The above reboots the phone into recovery.
USING ADB FOR DIAGNOSTICS (logcat)
Coming soon ...
Thank god! Lol thanks for all your hard work.
Sent from my HTC Vision using XDA App
Get a "how to logcat" section added.
Nice work. Can we elect you to be a mod?
Sent from my HTC Vision using XDA App
ddotpatel said:
Get a "how to logcat" section added.
Click to expand...
Click to collapse
Thanks for the suggestion, will do
Nice dude. Just what I needed
Sent from my HTC Desire using XDA App
+1 mod vote!
Sent from my HTC Vision using XDA App
Nice guide mate. Let me know if you need any more posts or help in any way
steviewevie said:
Using adb
Using adb for logcat
adb logcat
Or
adb lolcat
Click to expand...
Click to collapse
Also update it for Mac / Linux users.
Mainly different adb files (I had adb and fastboot for Win/Mac/Lin uploaded somewhere, if you want?) and they go in /system/bin instead of PATH.
Otherwise, good idea + well done.
DanWilson said:
Also update it for Mac / Linux users.
Mainly different adb files (I had adb and fastboot for Win/Mac/Lin uploaded somewhere, if you want?) and they go in /system/bin instead of PATH.
Otherwise, good idea + well done.
Click to expand...
Click to collapse
Thanks. I need someone to help me come up with the different steps for Mac/Linux users please ? Then I can add those in.
steviewevie said:
Thanks. I need someone to help me come up with the different steps for Mac/Linux users please ? Then I can add those in.
Click to expand...
Click to collapse
I'll do that.
I'll also hunt down my Mediafire adb and fastboot files, because not everyone wants the whole SDK
I don't know if you need any drivers for the phone (like HTC Sync for Windows). Someone else will need to tell you, or you can wait till Christmas.
INSTALLING ADB
Step 0
Drivers perhaps? XD
Step 1
Download these files;
Mac - http://www.mediafire.com/?z8myxs9941kz3gg
Linux - http://www.mediafire.com/?m62rt943mroxm4s
Or you can download and install the Android SDK (Software Development Kit) Starter package from http://developer.android.com/sdk/index.html
You can read all about how to install the SDK at http://developer.android.com/sdk/installing.html . Ignore all the stuff about Eclipse though, you don't need that unless you're going to start writing Android apps.
Now, from version 8 (Android 2.3) of the SDK onwards, adb has been taken out of this starter package. If you downloaded version 7 (Android 2.2), then you've already got adb and you can skip Step 3 and go straight to Step 4 below. Otherwise you need to proceed to Step 3 to add adb to the SDK.
Step 2
Extract the files and rename "adb-linux" ("adb-mac") to "adb" and "fastboot-linux" ("fastboot-mac") to "fastboot"
You could call it anything you like, like "cheese" and "bread", but that makes things difficult.
Step 3
Mac - Copy the files to the folder /bin
You will need to unhide the folder. Google it.
Linux - Copy the files to /system/bin *OR* /bin
I have not used Linux for ages so my folders are rotting away. I believe you will need root access to do this, I used Kongregate (I think) as an app to control my root copying needs.
Step 4
On your phone, go into Menu->Settings->Applications->Development and make sure you have the entry "USB Debugging" ticked. adb will not work without this.
Step 5
Plug your phone into your PC using the original HTC cable. This is important, do not use a third-party cable since it might not work with adb (even though it might seem fine with other communication with your phone). Or whatever.
Step 6
Open a Terminal window. On your PC/Mac. To emphasise, you are running this on your PC, not directly from your phone (e.g. terminal emulator) :
The part were it says "Dan-Wilsons-MacBook:~ danwilson$" will probably not be on your PC/Mac, unless you are called Dan Wilson, and have a MacBook.
Code:
Dan-Wilsons-MacBook:~ danwilson$ adb devices
This should display something like the following :
Code:
List of devices attached
XXX12345 device
... where the "XXX12345" bit is actually your phone's serial number. If the list is blank and the phone is plugged in ok, go back to Step 6 and make sure USB Debugging is enabled. If you can see your phone, YOU WIN A CHEESECAKE!
If you decided to be awkward and call "adb-linux" ("adb-mac") "cheese", replace the word "adb" in command lists (like the above) to "cheese". It looks cool but complicates things.
Example;
Code:
Dan-Wilsons-MacBook:~ danwilson$ cheese devices
-------------
I think this looks OK. Some bits are weird and I don't know about drivers, but still, better than nothing. It is rough, but I've not done it in ages. Sorry bout that.
Here is the adb and fastboot files for Windows. Check they work with the Z before throwing them in the first post. If you do.
http://www.mediafire.com/?zlbyfbaaf5lrj8i
I've updated this guide to flesh it out a bit more (still more to be done though).
Significantly, please note that in the latest version of the SDK (i.e the one for Android 2.3), they have taken adb *out* of the Starter version of the SDK. So now there's an additional step, which is downloading the "Platform Tools" component of the SDK. It's all in the guide though.
nice, this needs to be "stickied"..
steviewevie...
whatever you are on.. can i haz some?
you are poster of the year! wow, such effort.
this beeyotch must be stickied all over the world.
EDIT -- i dont see "adb pull /" so as to dump all your files from system data etc into your sdk folder. if i missed that nevermind!
@steviewevie:
My 2 cents for your great work:
I have tested and uploaded a Mini ADB package and the ADB USB drivers for Windows Vista / Windows 7, to the Resources Centre, easy tutorial + FAQs thread here:
http://forum.xda-developers.com/showthread.php?t=835777
I thought this would make things easier for newbies or people who don't want to download the whole SDK / Sync software
Also, setting the path is not required, since the "Runme" file is located inside the same folder within the ADB files
This could save some steps for newbies
If you find it helpful, feel free to link from your guide
Thanks for the input guys, I have some updating to do !
steviewevie said:
INSTALLING ADB - METHOD B, THE "QUICK" WAY, NO SDK
Step 2
Download the adb binary from ? * to be completed *
Click to expand...
Click to collapse
Direct Download Links for Android SDK Platform-tools, revision 1
ht*p://dl-ssl.google.com/android/repository/platform-tools_r01-windows.zip
ht*p://dl.google.com/android/repository/platform-tools_r01-windows.zip
It contains ADB.exe and needed dlls
size 3.06 MB
Also i recommend ADBMagic from Chainfire if you got tired of using ADB commands by hand for a lot of operations
ht*p://forum.xda-developers.com/showthread.php?t=746313
Have fun
if you add adb.exe to system32 folder is windows u can adb from anywhere in command prompt.. just in case adding the variables dont work
HOW-TO
**Easy ADB / APP Pushing / More Coming Soon**
**DISCLAIMER** I accept no responsibility if you brick, blow up or burn up your device, you are choosing to follow this and making your own decision**
I have been a long time android user and forum user. The goal here is to create a simple How-To guide for some of you new to android or just new to flashing. This stems from myself being on these forums and helping users fix and troubleshoot things. My goal is to give you some basics to help with testing or troubleshooting and to teach you a thing or two. There will be several sections and updates along the way. The Note 2 will be used as the device, but these can be done on most other devices as well.
Click to expand...
Click to collapse
**Easy ADB**Thanks @kennyglass123, @CNexus and @gruesomewolf
Code:
This was thought of the other night when kennyglass123 and CNexus
were trying to get recovery to mount storage. I had a idea, Why not
make a simple way to get a ADB log when trouble shooting, instead
of using an app from the market. Plus it will pull a log upon boot, ever
had it where your testing something and it wont boot and the Developer
wants you to get a log, but you either don't have ADB or know how to
use ADB. This is for you!! Thanks goes to Kenny Glass, CNexus for the
idea and Gruesomewolf for the bat file edit.
What you need
Windows PC
Android device
Easy ADB.zip attached to this post
Whats included
Your basic ADB parts to be able to run without needing the SDK installed
LOG.bat file
Reboot.bat (Reboots device)
Recovery.bat (Sends device to recovery)
Download mode.bat (Sends device to download mode (ODIN mode))
How to record log cat using LOG.bat
You will download the zip
Extract to your desktop for easy access
Plug your device in to your PC
Open the ADB folder
Right click the LOG bat file, select run as admin (might not need to)
It will open a command window
Select ANY key to continue or control-c to quit
Wait for it to return to press any key to continue
Now you will have a text file called LOG, that is you LOG cat using ADB
You are now done and can send it to whomever or read it over yourself.
**Pushing system apps (Root Needed) (Will be posting screencasts of this also)**
Have you come across someone posting something or telling you to push this app? I know I push them all the time. This can be used for MORE than just apps!! You can push just about everything. This will cover pushing a system app to the /system/app folder AND pushing a framework.jar to /system/framework folder. I will cover this using Root Explorer (paid) and ES File (free)
Click to expand...
Click to collapse
Code:
What you need
Android device
A file explorer with root access (Root Explorer, ES File or any others)
Whatever file, apk or etc you need to install
How to push a system app
Download Root Explorer or ES File from the store
(Root Explorer Instructions)
Open Root Explorer
Grant SU permissions
Navigate to the app you are going to be pushing (click + at bottom of screen to add EXT SD card tab)
Long press apk
Select copy
Top left tab says root, click and scroll to system folder, click and then click app folder
Bottom of screen says copy here, select that
Now scroll to the apk you just copied there and long press it
Select permissions, change them to only having the first vertical row and top of middle row checked (Attached Screenshot)
Click OK
Press home button
Now reboot to recovery and wipe cache and dalvik cache, then reboot.
(ES File Instructions)
Open ES File
Top left is a device/globe icon
Select tools, root explorer, Mount R/W
Grant SU permissions
Click device/globe
Select Local and then the SD card where the apk your wanting to install is located
Go to the folder when the apk is
Long press it and select copy
Now press the device/globe again and select local and then device
Scroll to system folder, click it
Now click app folder
Bottom of the screen, select paste
Scroll to the apk you just copied and long press it
Bottom right is more, select that then properties
Now you will change permissions to first vertical row and top middle checked only (attached Screenshot)
Click OK
Press home button
Now reboot to recovery and wipe cache and dalvik cache, then reboot.
Code:
Pushing System framework and other system files (Root Needed)
[Notice you will move to system folder and change permissions there, So if the device reboots or things lockup, you have already changed permissions and can just go to recovery and do your wipes]
(Root Explorer Instructions)
Open Root Explorer
Grant SU permissions
Navigate to the file you are going to be pushing (click + at bottom of screen to add EXT SD card tab)
Long press the file name
Select copy
Top left tab says root, click and scroll to system folder
Bottom of screen says copy here, select that (Place file here fist so you can change permissions now)
Now scroll to the file you just copied there and long press it
Select permissions, change them to only having the first vertical row and top of middle row checked (Attached Screenshot) (or if there is different permissions change accordingly)
Click OK
Scroll to the file you installing
Long press and select MOVE
Now open the folder or folders the file belongs in (framework for framework.jar for example)
Bottom left click move here
Press home button
Now reboot to recovery and wipe cache and dalvik cache, then reboot.
(ES File instructions)
Open ES File
Top left is a device/globe icon
Select tools, root explorer, Mount R/W
Grant SU permissions
Click device/globe
Select Local and then the SD card where the file your wanting to install is located
Go to the folder where the file is
Long press it and select copy
Now press the device/globe again and select local and then device
Scroll to system folder, click it
Bottom of the screen select paste
Scroll to the file you just copied and long press it
Bottom right is more, select that then properties
Now you will change permissions to first vertical row and top middle checked only (attached Screenshot)(or if there is different permissions change accordingly)
Click OK
Scroll to the file your installing
Long press it and select cut
Now open the folder or folders the file belongs in (framework for framework.jar for example)
Bottom of the screen select paste
Press home button
Now reboot to recovery and wipe cache and dalvik cache, then reboot.
**Coming Soon**
Code:
How to remove system apps before flashing (Debloating)
How to add your own apps to a rom before flashing
Some of you know me and that I have ported "Goodness Noteworthy" to Verizon, T-Mobile and AT&T on the Note 2, So I may do a guide on porting roms from or to other carriers. Although I have not tried a International rom yet.
If you have suggestions or things you would like to see here, please post or PM me.
[HOW-TO] ADB / APP Pushing / More coming [WIP]
Setting up JDK and SDK for ADB use.
Whats is ADB?
ADB or ANDROID DEBUG BRIDGE is a command-line utility that is often used to communicate over the debug channel with a connected phone or virtual device (emulator). ADB can control your device over USB from a computer, copy files back and forth, install and uninstall apps and more...
Click to expand...
Click to collapse
What is needed
Windows PC (using Win7 64bit as example)
Java JDK HERE
Android SDK HERE
Android device
Click to expand...
Click to collapse
**Setup for Java JDK**
Download the Windows x86 or x64 .exe from HERE . Run the exe and let it install to default location
**Error that SDK does not see Java installed**
Code:
I and many others have had to create a Enviroment Variable so the Android SDK will see the Java JDK.
After java has installed
Click start menu
Right click computer
Select properties
Top left at the bottom of the list is Advanced System Settings, select that
System properties will open and bottom right will be a Enviroment Variables button, select that
A popup will apper (Enviroment Variables)
Select New System variables (bottom section)
Variable name will be JAVA_HOME, case sensitive
Variable value will be C:\Program Files\Java\jre7
Select OK
Select OK again and it will close Environment Variables window
Now in the System Properties window, if the apply button on bottom right is not clickable, we need to make it clickable
So what I do is make a small change to the computer name tab, I just delete one letter from the name and the type the
same letter (you do not actually need to change the name) and the apply button is now clickable, do so.
Now you might want to reboot your PC
Now that's set for when you go to install SDK it will see Java.
**Now to install Android SDK**Download the SDK from HERE. Towards the bottom of the page is "Download other platforms", select that. Scroll to "SDK Tools Only" section and in the Windows section select the installer.exe. Now you double click and run the installer
**Setup Android SDK**
Code:
Open this file path C:\Program files (x86)\Android\android-sdk and double click SDK Manager
It will open, top left is a Tools folder which has "Android SDK Tools" and "Android SDk Platform-tools" in it, check mark all 3 boxes
Bottom right is Install packages button, click it and accept liscences
Now you can navigate to the platform-tools folder and you will see adb now
Make sure you have you device drivers installed which I hope you would have already
Open settings on your device, scroll to Developer options and enable USB debugging
Plug device into PC and let drivers update/install
Now in the window where adb is, press shift+right click and select "Open command window here"
Type adb devices, if you have a device connected and it does not return a device, you need to install again.
If it does return a device you now can use adb for a veritey of functions, some of which I will cover.
***Tomorrow I will add some ADB commands along with what their functions are***
Nice Thread, we be a huge help to many. :good:
Yea buddy good looking out
Sent from my SPH-L900 using Tapatalk 4
Nice...thx for sharing I also use android commander but will definitely give this a go.
Sent from my SPH-L900 using Tapatalk 2
Whoa, how did I miss this? Thanks for sharing.
Going to try to add some ADB commands tomorrow as is my next day off. I'll get the screen shots and screen casts done tonight.
Has anyone even used the easy adb or linked someone on how to push a apk?
Post 2 has been updated with how to setup ADB and going to add some commands and what their functions are.
Nice work BTR! Thanks for putting this together!
Awesome now even I can do it Thanks BTR
Sent from my SPH-L900
great resource
Thanks for a very helpful resource especially a newbie like me can use
Sir... where can I get the commands you talked about earlier???
How to enable ADB on ALLWINNER A13 9" - 4.2.2 - Windows 7 - error:device not found
Hi folks, my target is to do a full backup of my android tablet device without rooting nor installing app's on the device. It can be done just by the ADB tool and the simple command
Code:
adb backup -apk -shared -all
.
Basic information
PC: Windows 7, pro. USB 2.0 port. ADB Driver "Drivers-AllwinnerA10-32bits\32Bit_Win_7_Vista_XP" from 2011. ADB Platform-Tool, Android Debug Bridge version 1.0.31. Logged in as normal User, not Admin. The development kit is not installed, I just downloaded the Platform-Tool, unzipped it and started "adb" - I just want to make a f***ing backup :crying:
Tablet:
ALLWINNER A13 9". Android Version 4.2.2. USB Debugging enabled. Detail Info's:
Model number: JL902
Kernel Version: 3.4.0+ [email protected] #1 Mon 25.11.2013
Build-Number: full_gs702c-userdebug 4.2.2 JDQ39 eng.root.20131207
NOT ROOTED.
Problem:
I do not get a connection from the PC to the tablet. Also no RSA Key question comes up at the tablet. The adb tool just throws an error :"device not found". I tried several things, log in as Admin, "adb wait-for-device", plugging and unplugging ... nothing helped. The adb tool works fine, I tested it with a Samsung Galaxy S2. I'm not quite sure about the adb USB driver on windows, but there is no exclamation mark nor other problems reported. So this should be fine.
Anyone any hint, tip or solution? Would be great - gathering for hours with this problem - searching forum 'n stuff....
Thanks in advance
Juha
Try with uberizer or MTKDroid tools. Just connect and select adb terminal.
kramkumar said:
Try with uberizer or MTKDroid tools. Just connect and select adb terminal.
Click to expand...
Click to collapse
Thx 4 the hint, tried uberizer:
Code:
ERROR No useable device has been found
I think since in Android 4.2.2 the RSA Key authentication was introduced, something is wrong with the connection. Because I would expect the RSA Key question on the tablet, but the tablet does not show this dialog.
By the way, I recognized that the USB driver for the ADB interface is titled "Drivers-AllwinnerA10" but the tablet has a A13 core. But I do not find another driver at the moment and the vendor ID -VID_10D6&PID_0C02&REV_0202&MI_01- fits (otherwise, windows wouldn't install it anyway). Does it make sense to search for another driver?
hi from messing with various drivers and android devices i have found that installing PDA net for windows (theirs and android version too but not needed) once pdanet installs let the drivers for your phone be installed, if by any chance you have drivers already installed what you can do is go to device manager, click on your device uninstall the drivers, unplug your phone and then open pdaNET a window will come up waiting for you to connect your phone and the driver installation process will begin.
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !
abstractVoid said:
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !
Click to expand...
Click to collapse
Thanks for the tip. It really installed an USB driver as you said (I've deinstalled the other driver before). But sadly the result is the same. I can't access the ADB interface - same error "Device not found".
At this point I want to say thanks to all viewers of this thread, it seems really to be not an easy task. I'm still open minded in any direction and would be happy for any suggestion what I might try.
Even a hint, how I could reduce the possibilities for the root of my problem. I'm still not quite sure, if the driver is the problem or even if the tablet itself has some kind of software defect on this kernel version - By the way, does anyone have the same kernel version (posted at the beginning - 3.4.0+ [email protected] --- repeated for your convenience) of Jelly Bean (4.2.2)? Do you have experience with the ADB interface then?
How may I isolate the real problem? Any idea wellcome :cyclops:
I have nearly an identical tablet except mine has the PnP code of Vendor 10D6/Device 0C01 and it shows as P706 on the USB description.
I installed PDAnet, that actually was able to upload the Android version of PDAnet to the tablet, so I think that's a definite for the driver working. But I'm also having trouble getting ADB to list the device and I'm using the latest ADB from the SDK. Since ADB tries to setup a network server, I'm wondering if the ADB driver on windows has to be tethered as a NIC somehow?, just a theory.
I'm using a fresh install of XP and can do a complete rollback, so I'm certain it's not the OS.
There's also another quirk about this tablet. I wanted to do a backup of the firmware from this device. Techknow's utilities use ADB to issue several shell commands to copy "partitions" to the SD card, I thought I might as well try to do that manually only to find what would've been copied as /dev/block/nanda, nandb, etc. is named /dev/block/acta, actb, etc. instead. But lack of "root" means I can't read any of those partitions or even copy su into /sbin.
Uberizer isn't any good since as far as I can see that also uses ADB. Any known issues with versions of ADB? or even any other tools which do similar to ADB?, or even a way to "root" these devices just by Terminal and SD?
Regards
Ah, okey, soz I got the USB thing a bit mixed up. My tablet does have the same code, I assume the 0C01 is when it's in recovery mode (power on with volume + pressed)
I also realised the driver that was working wasn't one from PDAnet.
I've updated the working 32-bit driver with the version of ADB I'm using and included it in the attachment. Maybe you can try that and see if you have any progress.
I'll keep posted on this thread.
SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
You can check what the user directory is by DIR %USERPROFILE% in the "DOS" command line (%USERPROFILE% is case sensitive).
ADB should list your device when you do adb devices in the "DOS" command line.
Basically, adb_usb.ini with a custom identifier was missing.
Regards,
qUE
Right, I've made up a pack to automate putting SU on the device and setting up permissions on SU and BUSYBOX.
!!! This is only for the VID_10D6&PID_0C02 device, your mileage may very with other devices. !!!
DRIVER directory should contain the USB driver you need, otherwise try installing PDAnet and tell it to replace the driver.
Install USB driver, run SUME.BAT
to hopefully backup all the needed stock firmware to SD;
adb shell
su
cat /dev/block/acta > /mnt/sd-ext/acta.img
cat /dev/block/actb > /mnt/sd-ext/misc.img
cat /dev/block/actc > /mnt/sd-ext/system.img
exit
exit
adb kill-server
qUE
Confirmed solved
qUE-ARM said:
SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
<SNIP>
Basically, adb_usb.ini with a custom identifier was missing.
Click to expand...
Click to collapse
CONFIRMED SOLVED
Yes, that was it! I copied the adb_usb.ini file into the .android user directory (which only contains these ascii chars "0x10D6" - no CR no LF or anything else) and it worked out !!!
Thank you (Thanks meter will follow ) Some interesting things I discovered now:
There was no RSA-Key question at all on the tablet!!!
as I did the full backup with "adb backup -apk -shared -all" I was asked on the tablet to confirm this
So obviously something strange is going on here. Since it is claimed everywhere the with Android 4.2.2 the ADB interface should be generally RSA-Key protected. Okay, might be that I misunderstood something here :silly:
At least this problem is solved and I appreciated every comment in this thread. One question would be final to answer:
Who should have brought the adb_usb.ini to my PC. The ADB driver ? The ADB Platform-Tool package? So, whom to blame here - NO - just kidding :laugh:
I did briefly try the platform-tools (since I didn't mind the OS being trashed), they didn't add any adb_usb.ini and there isn't any real indication the file was needed/didn't exist, they could've simply put a note on the ADB utility when it didn't find any devices.
I'm not sure what ADB backup does. As far as I know the mounted partition images are differently named to various backup tutorials, so I get the feeling ADB backup just simply copies the user data and not much else. I recommend doing the backup I mentioned as well, it'll at least capture a copy of the boot partition, which if the device doesn't have that you'll probably need to revert to using live suite or some other firmware utility to restore it. Getting the firmware for that is another story, read a fair amount of posts here and other places on the net that don't sound fun.
I personally still can't get superuser to behave for using su on the terminal/term.apk (I want to remove useless "system" apps and make sure the device isn't talking back to anyone, i.e. google), but I'll keep tinkering.
My main aim for getting one of these tablets was to boot other firmware from the SD slot, but it looks as if the u-boot process is locked to internal NAND. So might have to modify it by adding "fatload mmc" to the script.
qUE
Quick Update;
Right the permissions thing turned out to be an issue with Superuser, dunno why. So replace the su binary from SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053) into my SUME pack and install the Superuser.apk by;
adb root
adb shell mount -o rw,remount /system
adb push Superuser.apk /system/app
as for stripping back the Applications, I've got it down to this as bare bones
adb pull /system/app backup\system\app
to backup system applications before you do anything
I found if you do delete any applications and then android gets stuck at the logo, just adb push them back and it'll boot without reboot when you've got the chain right.
minimum applications needed for boot are;
DefaultContainerService.apk
DefaultContainerService.odex
SystemUI.apk
SystemUI.odex
Launcher2.apk
Launcher2.odex
Settings.apk
Settings.odex
SettingsProvider.apk
SettingsProvider.odex
ActSensorCalib.apk
InputDevices.apk
InputDevices.odex
FusedLocation.apk
FusedLocation.odex
LatinIME.apk
LatinIME.odex
PackageInstaller.apk
PackageInstaller.odex
ApplicationsProvider.apk
ApplicationsProvider.odex
A few odds and sods missing will make settings close, but it's trivial stuff. Personally don't like the sound of Fused Location, but it won't boot without it and I haven't seen any dodgey traffic from it (yet).
I recommend installing Droidwall with adb push /system/app, before installing games.
And modifying /etc/hosts with 127.0.0.1 to certain you know whos and advertisers.
Some of my personal choice replacement applications (so far);
Total Commander over ES file explorer.
Opera Classic over the inbuilt browser (although I'm still trying to remove the default search engine).
qUE
More update;
Discovered some new things;
BACKUP FILES WITH "ADB PULL" BEFORE MODIFYING ANY FILES!!!
I think performancepolicy.apk needs to be added to the bare bones application list, afaics from looking inside the package it sets system performance stuff, so likely throttling to preserve battery power.
bin_cfg.xml in /misc which can be modified by
adb shell mount -o rw,remount /misc
then adb pull, edit and push the file back
the line in there for "backlight_brightness" 780;1020;780 can be changed to 240;1020;240 which dims the backlight substantially saving battery power. not sure if 240 is the absolute minimum, but 120 seems to be too low afaics. interestingly information on the settings is in the files named _userview.xml
build.prop in /system which can be modified by
adb shell mount -o rw,remount /system
then adb pull, edit and push the file back
and then chmod 644 /system/build.prop
the lines in there for ro.wifi.signal.level.# can all be set to 0, this theoretically cuts the wifi power usage to less than 1mW, again saving battery. if android doesn't boot fully on reboot it's because chmod hasn't been set, you should be able to adb back in and correct.
please be careful modifying either file as both seem to have safety limits imposed on certain device components (i.e. battery temprature), messing with those can make the tablet stop working.
qUE