Hello, i just got my new samsung 7 plus with honeycome 3.2 and im loving it
I want to know what is the step by step instruction to rooting my device using adb?
the root.zip i found on here dont work for me. when i save the file to /sdcard and n reboot n go into wher i applie the zip from sdcard it shows no files at all on my card. i bought the 16gb version of this tab so i dont have the externel sdcard. i thought that i read one the forum you can only use the externel card not the interel. i believe they added the folder /sdcard to the internel drive and thats why it not viewing.
The rooting instructions say to put it on an "external" sdcard for a reason as recovery will not recognize the internal storage. Do you have adb installed on your computer and at least know how to use it? If not it is going to be way easier for you to just go and spend the $10 for an 8 GB sdcard and install it that way.
I can at least get you part way, installing the sdk and jdk. Here are the instructions for installing the android sdk (adb) direct from google. You also need the java jdk installed on your commputer and google has a link in their instructions.
http://developer.android.com/sdk/installing.html
You first need the proper usb drivers installed and not exactly sure on how to do that. I already had the android usb drivers installed on my computer for my phone and I just let the compter install whatever else it needed the first time I connected my tab to it.
You will need usb debugging turned in your settings and then power the tab off. You would then plug the usb cable into the tab and computer then boot it into recovery. Once into recovery Mount/System. You then run adb in a command window and change the drive to the platform-tools directory where adb resides. It would look something like this in a command window (c:\android-sdk-windows\ is how I set my computer up yours may be different):
cd c:\android-sdk-windows\platform-tools
To check and see if your device is recognized by adb run the command:
adb devices
If nothing is listed then adb isn't recognizing the device and you would need to troubleshoot your installation or boot method.
As far as installing the root.zip file I'm not sure as I've never had to do that before as I've always had an external sdcard on my devices. Maybe someone else can take you thru the last step. I believe all you would do is push the file inside the zip folder over to the tab. The su file inside the root.zip folder needs to be in the same directory as adb, platform-tools directory.
adb push su /system/bin
I'm not sure if you need to change permissions on this file or not and that is done thru a chmod command in adb shell but not sure of the proper code to use for the GTab to do this. For my phone setting permissions looks like this:
adb shell
cd /system/bin
chmod 0644 Su
exit
Do not use this chmod as I'm not sure it will work on the GTab or what it will do to it, it just an example.
In summary these are the basic steps you are trying to accomplish:
1. Install Java JDK
2. Install Android SDK
3. Install USB drivers
4. Turn USB debugging on in Tabs settings
5. Boot Tab into recovery while connected to PC
6. Mount/System in recovery
7. ADB push su file to system/bin
8. Set permissions of su???
9. Exit adb
10. Reboot phone and install superuser and busy box from market
Thanks im rooted now. I took the sdcard out of my droidx & it works on my galaxy tab & i used the root.zip file.
Sent from my GT-P6210 using Tapatalk
ronlsjr said:
Thanks im rooted now. I took the sdcard out of my droidx & it works on my galaxy tab & i used the root.zip file.
Sent from my GT-P6210 using Tapatalk
Click to expand...
Click to collapse
Yes any sdcard will do and that is the easiest way. Though I think everyone should learn how to use adb anyways as it is useful especially if you get into modding.
Yes i do want to learn how to use adb. My desire is to become a developer.
Sent from my GT-P6210 using Tapatalk
Just follow the link I provided previously to the android developers site and follow the instructions. You will first have to have Java JDK installed and a link to that is provided on the android developers website in the link. Once JDK is installed download and install the SDK. It will only put the basic functions onto your computer and you will have to install the rest through SDK Manager, this can take a while, up to an hour or so depending on what packages you want to install. At the minimum you would want the Android 3.2 API (GTab 7+ uses this) and the Google USB drivers and then any other API's for phones you may have. I myself installed all the API's as my first phone had Donut (Android 1.6).
I know this may be a stupid question but why root? what special features does it give you? I am not sure If I want to or not.
Anyone? I'm just curious if I should flash a ROM on here or not I just don't know why because it works fine now after the SwiftKey x and other little apps
Sent from my SGH-T869 using XDA Premium App
don't get confused by the lingo...
Noah321 said:
Anyone? I'm just curious if I should flash a ROM on here or not I just don't know why because it works fine now after the SwiftKey x and other little apps
Sent from my SGH-T869 using XDA Premium App
Click to expand...
Click to collapse
There's a difference between "flashing a ROM" and "adding root access".
A custom ROM implies someone has taken the stock software infrastructure, altered/tailored/customized it, and packaged it for others to easily use.
"Rooting" a device just simply gives you access to certain folders, permissions, files, etc.
It's like giving yourself Admin Rights to your work computer (assuming you're over 18 and/or working).
It allows you to do things that the manufacture probably didn't want you to do - like delete "bloatware" (unwanted apps).
If helpful, click "Thanks"
Related
Sorry about the post but I cannot find the post were it tells me how to install custom boot animations. I also need to be able to do the sounds. As far as I understand I have to put it in the media folder. I found the original one but it does not allow me to move it. I'm assuming I have to do it from recovery but I don't know how. Detailed instructions would be appreciated. I have a cold and the old brain is doing so well. Thanks
s-off your dinc and you can do it while booted
I was trying to avoid that because they do not have a way to undo s-off yet. Just incase my phone dies I dont want verizon to say I voided the warranty. Any way to do it without?
You can flash some of them from rom manager...that's how I did mine.
If you have rooted your phone, which you must have in order to install a custom ROM, you've already voided your warranty.
Adding S-OFF wouldn't change anything in the eyes of Verizon, and you can always drop your phone until it's physically broken if you need to take it in.
rom manager -> download rom -> Ihtfp69 -> boot animations -> download -> pick one
thats where i got mine from
MMBosstones86 said:
rom manager -> download rom -> Ihtfp69 -> boot animations -> download -> pick one
thats where i got mine from
Click to expand...
Click to collapse
When I try to install from Rom manager it doesn't load it says verification failed or something. Does anyone know how to manually install Droid 2 boot screen.
HTC incredible
SR sense 2. 5. 2
Radio 2. 15
Sent from my ADR6300 using XDA App
Did mine 'manually', since I'm rooted I have clockwork mod installed.
1. Boot into recovery (clockwork mod)
2. launched android SDK adb daemon
3. moved file from 'tools' folder of sdk to the proper destination on the phone.
4. Done.
Doctor Butts said:
Did mine 'manually', since I'm rooted I have clockwork mod installed.
1. Boot into recovery (clockwork mod)
2. launched android SDK adb daemon
3. moved file from 'tools' folder of sdk to the proper destination on the phone.
4. Done.
Click to expand...
Click to collapse
I'm not sure how to do step 2 your referring to. If you have a link to a thread that explains how to do that, it would be greatly appreciated.
Sent from my ADR6300 using XDA App
Well, you have to go to the android website and download the android SDK. Install it somewhere on your computer that's easy to access, preferably put the folder at the root of one of your hard drives.
You'll go into command prompt after that to do a lot of the work to transfer files.
So, make sure USB debugging is enabled (just in case) and boot your phone into cwm recovery. Connect the phone to your computer via USB.
in command prompt, cd to the android sdk's tools directory. From there, you can use the adb commands to transfer files.
So, for me, after connecting the phone I do the following in command prompt:
cd G:
cd androidsdk/tools
and then I use ADB to communicate with phone, first by verifying the phone is connected:
adb devices
(if adb is on your pc, it will auto run the daemon if it is not running)
If your phone shows up in recovery mode, you're set.
You may need to go into cwm and mount your system/sd card before transferring the file.
From there, you use adb shell to acess the phone's file systems.
If you put the boot animation to the phone you'll do something like (while in shell) mv bootanimation.zip system/somethingorother/bootanimation.zip
But don't take the above line as gospel. I dont remember the exact command line to use. Check the thread on "How 2 - ADB, Rooting...." for a list of commands in ADB shell and search for a webpage that gives basic linux commands.
Doctor Butts said:
Well, you have to go to the android website and download the android SDK. Install it somewhere on your computer that's easy to access, preferably put the folder at the root of one of your hard drives.
You'll go into command prompt after that to do a lot of the work to transfer files.
So, make sure USB debugging is enabled (just in case) and boot your phone into cwm recovery. Connect the phone to your computer via USB.
in command prompt, cd to the android sdk's tools directory. From there, you can use the adb commands to transfer files.
So, for me, after connecting the phone I do the following in command prompt:
cd G:
cd androidsdk/tools
and then I use ADB to communicate with phone, first by verifying the phone is connected:
adb devices
(if adb is on your pc, it will auto run the daemon if it is not running)
If your phone shows up in recovery mode, you're set.
You may need to go into cwm and mount your system/sd card before transferring the file.
From there, you use adb shell to acess the phone's file systems.
If you put the boot animation to the phone you'll do something like (while in shell) mv bootanimation.zip system/somethingorother/bootanimation.zip
But don't take the above line as gospel. I dont remember the exact command line to use. Check the thread on "How 2 - ADB, Rooting...." for a list of commands in ADB shell and search for a webpage that gives basic linux commands.
Click to expand...
Click to collapse
THANK YOU SIR. MUCH APPRECIATED.
Sent from my ADR6300 using XDA App
For Droid 2's on Gingerbread, click link below to find info to Root your phone
http://www.droid-life.com/2011/09/0...roidx2-droidx-and-droid3-running-gingerbread/
One Click Root Version for Linux and Works for Mac, too!
This is still a work in progress! Gonna call it 3.3 (I went through 3 previous versions). It takes the 2.2.1 version and adds a user interface. Nice, easy, clean. In order to run this script, you need to chmod (change permission) of the .sh file, and then execute it.
Download the file here: http://kimete.com/droid/beta/dorootv3.sh
It is good for both Linux and Mac. All you have to do is execute it and the script will download all the appropriate files for you!
How to run this in Ubuntu/Linux
How-to video here: http://www.youtube.com/watch?v=gvlB3e_UE8I
Note: General idea. You no longer need to update android-sdk, though.
1. Download the file.
2. Right-click the file, choose properties, choose the permission tab, and check executing file as program, close window
3. Double-click the file, choose Run in Terminal, and it'll start.
4. Choose 1 for install and root. Choose 2 for root process only. Only good if you've rooted using this method before, or you need to reroot your phone. Choose 3 to unroot. Choose 4 for credits/donation information. Choose 5 to exit. Choosing other numbers...
How-to for Mac
How-to video here: http://www.youtube.com/watch?v=d7s8dtfYyHI
Note: General idea. You no longer need to download and install android-sdk anymore.
1. Download dorootv3.sh. Best to put it on your desktop.
2. Open a terminal. Go to the magnifying glass and type in terminal, and then select it.
3. Next, you need to change permissions. Type in the terminal chmod 0755 followed with a single space. Then drag the dorootv3.sh into terminal.
You should see something like this chmod 0755 /user/(file path)/dorootv3.sh. Press enter.
4. Now run your file by dragging the file into the terminal again and pressing enter!
5. Now choose and option...
New version of rooting for Linux and Mac! Version 2.2.1!
Linux 2.2.1: http://www.kimete.com/droid/beta/DoRootLinux_221.zip
Mac 2.2.1: http://www.kimete.com/droid/beta/DoRootMac_221.zip
General Instructions:
1. Extract the files.
2. Change the permissions on the doroot.sh file
3. Run doroot.sh file.
Instructions for Linux and Mac
1. Extract the respective files to somewhere accessible. Your home directory or desktop is idea. The file comes in a .zip file. Just open it up and drag and drop the DoRootMac or DoRootLinux folder.
2. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
3. Navigate to the folder in terminal.
example: [cd /DoRootMac or cd /DoRootLinux]
4. enter [chmod 0755 doroot.sh] then run it [./doroot.sh]
5. Let it run.
6. That's it, you are done.
One Click Root for Windows
Here's the Windows version. Facelessuser pushed this through and worked his magic. Give it a try. Very exciting stuff. I haven't used it yet, but according to him, it should work!
Download here, Ver. 2.1.4:
http://www.kimete.com/droid/beta/DoRootWin_2.1.4.zip
Instruction for Windows:
How-to video here: http://www.youtube.com/watch?v=B7RGVikpQ8o
1. Extract the folder from the DORoot zip file to your desktop. You should be moving 7 or 8 files into the tools folder.
2. Install Motorola Drivers
(Tip, to stop the launching of the Verizon/Motorola site, go to the MotoConnect icon in the bottom righ, right click, when phone connects, nothing.)
3. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
4. Double-click and run doroot.bat
5. Let it run.
6. That's it, you are done.
Motorola Drivers (if you are using Windows) which can be found here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Many thanks to facelessuser for working his magic!
====
====
How-to Videos
Video of the Rooting Process for D2 and DX by [email protected]
For Windows/Mac/Linux
http://www.youtube.com/watch?v=u5l3MDomDSc
Video of the Rooting Process for D2 and DX by DarkOnion
For Windows
New: http://www.youtube.com/watch?v=B7RGVikpQ8o
Old: http://www.youtube.com/watch?v=gzlg9a-H42w
How to use the ADBDL.sh file by DarkOnion
For Mac and Linux
http://www.youtube.com/watch?v=9cHpGXfEudM
=====
=====
Frequently Asked Questions
Why does my anti-virus tell me that the files contain Trojan's?
The files are exploits and hack your phone. Don't worry, they are clean. However, to be safe, do not download from any other source than the ones linked in this post.
I've gotten countless hate mail and comments on Youtube users about rageagainstthecage-arm5.bin being detected as a trojan. It is an EXPLOIT. If you are scared that the files I hosted are going to give your computer a virus. Look else where, like Z4Root, though, my understanding is that Z4Root also uses rage.
http://forum.xda-developers.com/showthread.php?t=853704
What is do these files/programs/scripts do?
These scripts will root your Droid 2 or Droid X phone with the least amount of user input as possible.
Why should we use this method and not another method?
All the methods are based off the same process/procedure. If you feel like doing MORE work, we can't stop you. The reason why we wrote all these scripts is to expedite the process, make the procedure easier, and to reduce human input which reduces the chance of human error.
Is there anything I need to know in order to successfully root my phone?
Yes. READ THE DIRECTIONS. Read the directions first. A lot of people make errors because they don't read the directions. I've also provided links to my video and another video which outlines the root process. Both are only a few minutes long.
Root failed! What do I do?
Run the script again! Most people succeed on the first or second try. Usually the rest by the third try.
Do I have to install Android SDK and update it?
It depends. The new Linux/Mac version does not require you to. The windows one, we are still working on.
Does this work on other phones?
I can't answer that. I know it works for Droid 2 and Droid X.
Wait a minute, this isn't really one-click! What's the deal?
Deal with it. Don't like it, try the 25+ step process.
When I open up the Superuser app, I get a blank screen.
That is NORMAL. Superuser lists the processes/applications that you've allowed superuser access to. If you haven't allowed anything, then it will be blank.
How do I test if I have root or not?
Try downloading an app like Wireless Tether (published by Google), and running it.
What USB connection mode do I set my phone to?
PC Mode or Charge Only. Choose the one that comes up with USB Debugging.
I am not very good with computers. Is this something I can do?
Oh yes! The key to success is following the directions.
How do I update Android SDK?
On Windows, you just need to double click the SDK Manager.exe. On Linux/Mac, you need to go into terminal, navigate to the tools folder in the android sdk folder, and run this command ./android update sdk. More information can be found in the SDK Readme text file. On Windows, double-click and run the SDK Manager.
I am getting stuck at the "daemon not found/daemon is starting" part. What do I do?
You need to fumble with the settings on your phone. You don't need to close the terminal. Change between PC Mode and Charge Only mode until it starts to continue. If that still doesn't work, also try disabling then enabling USB debugging for each mode.
=====
=====
Reporting an Error or a Problem
You can report errors right here in this thread. Make sure you give us as much information as possible. List what operating system you are on, what phone you have, at what part of the script you had errors, and anything else you may have tried or done. The more information you provide us, the better we understand situations. Posting up pics or logs of the terminal is extremely helpful.
=====
=====
Change log for 1-2-3 Root
Version 0.0 - 25+ step tutorial on how to root D2 on Windows and Mac
Version 1.0 - Initial scripts to streamline processes and reduce user error in Ver. 0.0.
Version 2.0 - Streamline of multiple scripts into 1 script. Minimal commands. Minimal work. With error checking and reporting.
Version 2.1 - addressed issue where remnants of a previous root would not allow root to complete
Version 2.1.1 -
-Cleanup code.
-Address issue where I thought I was killing a hanging rage, but I wasn't (It was a syntax thing)
-Fix for ERROR6 or ERROR5 (this was drastically different than what I did in windows. I wasn't returning exactly a string in format I thought when doing the check, so I had to do some ridiculous stuff to process it.)
-Better error resolution. (more error checking)
-Refined unroot.
-Reboot if you had files from a previous root
-Now the script will automagically download needed root files if they are not in your folder. (If you are behind a proxy, make sure your mac or linux has curl or wget configured for proxies respectively)
-Longer wait before remount (I had it not remount because it was busy once)
Version 2.1.2 -
Linux and Mac
Contains everything windows 2.1.1
Unroots non bootstrapped phones too
All
Contains option to unroot
Version 2.1.3 - Added dounroot.bat
Vesion 2.1.4 -
-Fix bug where people were getting a false ERROR5 because they already had Superuser.apk
-Hide killing of busybox before unroot
Version 2.1.4 - Files are standalone. No need to download Android SDK anymore.
Version 2.2.0 -
-adb included, no SDK needed
-abort if cannot find adb
-remove alternate busybox at /system/xbin and /system/bin when unrooting
-remove alternate busybox at /system/xbin when rooting and installing busybox at /system/bin
-No more hang in exploit...I hope
-Clean up code
Version 2.2.1 - minor revision to code (curl related)
DarkOnion's DoRootv3
Version 3.0 - set-up menu's, added error checking, will detect which OS you are on
Version 3.1 - fixed issues with ADB SDK User interfaces
Version 3.2 - adapted to DoRoot 2.2.1
Version 3.3 - edited code for easier understanding and modifications
=====
=====
References:
Original procedure produced by Sebastian Krahmer
http://forum.xda-developers.com/showpost.php?p=7838000&postcount=1
Tutorial/How-to Root Droid 2 on Windows by DarkOnion
http://forum.xda-developers.com/showpost.php?p=7865824&postcount=164
Tutorial/How-to Root Droid 2 on Linux/Mac by DarkOnion
http://forum.xda-developers.com/showpost.php?p=8103311&postcount=340
====
====
Appreciate my work and/or help, feel free to send donations my way! Poor college student here who just got a speeding ticket! Doh!
This is outdated information and should be used as a reference only! All updated versions have moved to POST #1.
Hi all. Made it to the front page of XDA Developers.
http://www.xda-developers.com/android/easy-rooting-method-for-droid-2/
I just want to make sure credit is given where due. First of all, the original procedure was produced Sebastian Krahmer. From there I wrote an indepth tutorial to root the Droid 2. I took a vague instruction set and help it grown into something that the average person could understand. Understanding the need to simplify the process, I decided to write scripts to further streamline the process. What started out as a 3 part script that involved 8 or 9 commands eventually became a two part script that involved 3 or 4 commands. I have no programming background, by the way. Having trouble getting the process down into one part, facelessuser volunteered to take my work, and put a bunch of neat things into it to get it to work as one thing with error checking! So, with that said, I'd like to thank everyone that had a part in the project, especially facelessuser for his dark magic arts that made the script run, matt4542 for constantly testing my various scripts, and everyone who directly or indirectly ran the scripts!
We are moving forward!
===
Hi all.
We (me), facelessuser, and a few others are working furiously to get an easy one step program out for you guys. In the mean-time, I have a pretty safe, and clean, and easy 2 step method for Windows, Mac, and Linux. I am still cleaning stuff up, but for the most part, it all runs well.
What you need:
Android-SDK for your operating system which can be found here:
http://developer.android.com/sdk/index.html
Motorola Drivers (if you are using Windows) which can be found here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
And the files/scripts/programs to root for your OS:
Want to try the one step process, go down to post #2!
Windows [1.0]: http://www.kimete.com/droid/DORootforD2Windows.zip
Mac/Linux [1.0]: http://www.kimete.com/droid/DORootforD2Linux.zip
Instruction for Windows:
GO DOWN TO POST #2 AND DOWNLOAD THE ONE STEP
1. Extract and Update Android SDK package to your computer. The file comes in a zip file. Just open it up and drag and drop the android-sdk-windows folder to your C drive. Next, extract the files from the DORoot zip file to the tools folder of Android SDK. You should be moving 7 or 8 files into the tools folder.
2. Install Motorola Drivers
(Tip, to stop the launching of the Verizon/Motorola site, go to the MotoConnect icon in the bottom right, right click, when phone connects, nothing.)
3. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
4. Double-click and run doroot1.bat
5. Follow the instructions. You will enter into the shell and be prompted with a $.
6. enter [./data/local/tmp/rageagainstthecage-arm5.bin] and let it run. Can take up to 15 minutes before it boots you out.
6a. To check if rageagainstthecage worked it's magic, enter the shell with adb shell. You should see a # sign. If you don't, you need to run rageagainstthecage again by entering the command from step six.
6b. If you see the #, exit the shell by typing exit.
7. After being booted from shell and back to DOS, enter or double click doroot2.bat
8. That's it, you are done.
Instruction for Linux and Mac:
GO DOWN TO POST #2 AND DOWNLOAD THE 1-STEP!
1. Extract and Update Android SDK package to your computer. The file comes in a .tar.gz file. Just open it up and drag and drop the android-sdk-linux folder to your home directory or desktop. Next, extract the files from the DORoot zip file to the tools folder of Android SDK. You should be moving 7 or 8 files into the tools folder.
2. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
3. Navigate to the tools folder of your android-sdk
[cd /android-sdk-linux_x86/tools]
4. enter [chmod 0755 doroot1.sh] then run it [./doroot1.sh]
5. Follow the instructions. You will enter into the shell and be prompted with a $.
6. enter [./data/local/tmp/rageagainstthecage-arm5.bin] and let it run. Can take up to 15 minutes.
6a. To check if rageagainstthecage worked it's magic, enter the shell with adb shell. You should see a # sign. If you don't, you need to run rageagainstthe cage again by entering the command from step six.
6b. If you see the #, exit the shell by typing exit.
7. After being booted from shell and back to command prompt, [./doroot2.sh]
8. That's it, you are done.
Enjoy my works? Want to show your gratitude? Just want to help a poor college student out, donate via PayPal to: [email protected]. All donations are greatly appreciated. Money will be spent on escorts, food, adult beverages, higher education and its bs fees, paying off my phone, and the wonderful speeding ticket I got this week!
Hey Thanks alot for writing this! I just tried it out and ran until completion.
A few things I found.
In the dos prompt, part2 the program asks user to input a few commands. Commands 2 and 3 should end in .sh. The program dosent mention this.
Thanks again
Typo in the 3rd step. You forgot to add '.sh'.
lockdownx1x said:
Typo in the 3rd step. You forgot to add '.sh'.
Click to expand...
Click to collapse
Doh. Good catch y'all. I will take care of that now!
Problem
Everytime i type: $ ./doroot2.sh
i get:
./doroot2.sh
./doroot2.sh: not found
thank for the help!
The " ./ " before doroot.sh tells linux to look in the current directory for the file to run. Make sure you in the tools directory of the sdk and that the script is there as well.
Sent from my DROID2 using XDA App
Yep i definitaly made sure of that but same error. It doesnt matter though i have rooted my droid 2 through the manual proccess
NiteSite said:
Everytime i type: $ ./doroot2.sh
i get:
./doroot2.sh
./doroot2.sh: not found
thank for the help!
Click to expand...
Click to collapse
Did you do cd data/local/tmp in adb shell before doing the chmod and ./doroot2.sh?
Yeah the chmod doroot2.sh worked without a problem. ./doroot2.sh did not tried it several times though
Sent from my DROID2 using XDA App
NiteSite said:
Yeah the chmod doroot2.sh worked without a problem. ./doroot2.sh did not tried it several times though
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Weird. I am going to send you a PM. Hit me up on Google Talk.
-Kevin
Should turn this in to a one click root app for D2. Couldn't you essentially do some modifications and run it from the phone?
mjones1052 said:
Should turn this in to a one click root app for D2. Couldn't you essentially do some modifications and run it from the phone?
Click to expand...
Click to collapse
I am working on it. Hahaha. I don't have any programming background. So I am learning on the fly, but progress is being made.
Though, I have to say that the process is much much much easier than what it originally began as. So... moving in the right direction.
I'm not much of a programmer. I'm on Windows. Do I need to chmod the files, and if so, how would I do that?
Kenny Strife said:
I'm not much of a programmer. I'm on Windows. Do I need to chmod the files, and if so, how would I do that?
Click to expand...
Click to collapse
Just follow the instructions. Launch the doroot1.bat file. The .bat file will launch you into ADB shell. chmod the doroot2.sh file, then run it. adb shell again. chmod the doroot3.sh file and run that. Hope that helps. I am on google talk if you need help.
I'm stuck on the second step. Attempting to contact you through Google Talk...
Thanks, by the way.
please help!
i rooted manually and when i try to open superuser permissions icon i get a black screen...should i follow your steps to root now and will that work ??
chrismouro said:
i rooted manually and when i try to open superuser permissions icon i get a black screen...should i follow your steps to root now and will that work ??
Click to expand...
Click to collapse
You are okay. Superuser lists the program you've allowed superuser access to. You haven't given any apps access, therefore blank!
Kenny Strife said:
I'm stuck on the second step. Attempting to contact you through Google Talk...
Thanks, by the way.
Click to expand...
Click to collapse
Kenny, did you get this resolved? I am experiencing the same issue.
I'm getting kicked the ./doroot2.sh: not found as well. Anyone get past this point?
Sorry to sound pig ignorant about phones but I am ... my expertise is in PCs. So anyway I want to upgrade the Hero with CyanogenMod.
I backed up my contacts, apps, etc and rooted the phone with unrevoked ... lost everything in memory in the process, but that's OK -- the important stuff is backed up.
Rebooted into stock 21. ROM and skipped all the new user stuff ...
OK, here's where I'm lost ... to load the CyanogenMod ROM I apparently need something like Amon-RA, but to load Amon-RA image file I need to install the SDK pack.
So I downloaded the SDK pack, but it is nothing like what is described in all the install SDK posts I've been able to find. What I have found are instructions about running ASroot and other files that don't exist in the SDK version I have.
So like what do I do now, more important ... is there an A to B thread for doing this mod starting from a stock phone, going to unlocking, than loading SDK, than installing Amon-RA (or equivalent) and than installing CyanogenMOD.
I know all this info is out there, but it seems like most of the files I've found don't interface well in the sense that the ones that talk about doing step one aren't terribly relevant to ones that talk about step 2, etc.
Thanks
Yes. Its a sticky at the top of the page. Search "guides" lol...
Sent from my HERO200 using XDA App
All you need to do with the sdk is download it and extract it. I just put it in the root of my C: drive. Then open a cmd prompt in windows by going to Start > Run > cmd (press enter). Then in the command prompt you need to change directories to the sdk folder you extracted. For example, mine is in C:\android-sdk-windows. I just type "cd c:\android-sdk-windows" then "cd tools" to get into the directory where you can run the adb program. Make sure your phone is in debugging mode by going to settings > applications > development > check the USB Debugging box. Then you can hook the phone up to the usb and run the command "adb devices". If everything is working correctly then you should see a device serial number show up. If that doesn't work make sure you have the htc drivers installed by downloading htc sync from their website and installing it.
Once adb can see the phone then you should run the command "adb shell" and then when you get a $ prompt type su in order to elevate to root. Make sure you put a recovery image on the phones sd card using step 4 from this guide: http://forum.xda-developers.com/showthread.php?t=694572 I think he has a link to download the recovery in that guide but just in case here is a direct download link for the recovery: http://www.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-heroc-v1.6.2.img Feel free to rename it to recovery.img so that the commands in the guide can be used as is.
Now you should be able to start at step nine from the guide in that thread (you should be in an adb shell when you start). It should be the adb command to flash a recovery image. Once you do that installing roms is as simple as putting them on your sd card and booting into recovery to select the flash option.
how do u root with z4root with out being able in install any 3rd party apps
!!
please help!!!!
Do alittle more research on the whole root process. 2.2 is a little weird but instructions are out there. I would not use any app to root Basically you need to find the right zip and install that with the button recovery.
Also don't expect an immediate response. Just because no one respond in 5 minutes does not mean they won't
Sent from my SAMSUNG-SGH-I897 using XDA App
I had to use a side loading app to get z4root installed on my phone and then rooted it from there.
Google "captivate side loading" and you should be able to find the app you need the name escapes me at the moment.
Sent from my SAMSUNG-SGH-I897
Sideload Wonder Machine from Android Central worked great for me.
http://forum.androidcentral.com/and...40770-ac-sideload-wonder-machine-windows.html
Watch this... http://www.youtube.com/watch?v=LFHLVF1aA0Q
If you can get an app to load and work on your machine to side load the apps you are ready to go. If not, i.e. Vista 64bit is an issue for DroidExplorer, you can use simple adb commands.
Like the video says... assuming you have the SDK and drivers installed. This is also assuming a computer running windows, if you are running Linux well... if you are running Linux you should be able to translate
1. Open a command prompt
2. change directories to the platform-tools directory where ever you installed the 3. SDK. i.e. C:\android-sdk\platform-tools
4. Turn usb debuging On via the phone Settings->Applications->Development and check Usb debuging
5. connect your phone to the PC with the usb cable
6. type adb devices
If you then see something like this you are ok to continue, if not you need to figure out what is wrong with either your SDK install or your driver install
List of devices attached
100049b90495 device
7. type adb install <location of your z4root.apk file> i.e. adb install c:\apks\z4root.apk
8. You will see adb copy the file and install to the phone. (If it fails start reading more in the dev section here. All the answers are there)
9. Disconnect your phone and open up z4Root on the phone and root it.
That should help. All of the steps above and A LOT more are in the dev section here, as posted above search and read and ye shall have all the fun you want.
+1 Sideload wonder machine
Follow the rooting guide on youtube from mobiletechvideo(?), he has a bunch of videos, one is how to flash cognition based rom onto your phone (but the first step is rooting, so you could skip the rest if you didn't want to flash a rom).
Hope it helps
http://capfaq.com/w/Root
I have a B90 TF101 and I am able to get into recovery mode. I have no ROM on my internal SD card and have wiped and formatted everything. I have read that it is possible to push a file using ADB while in recovery.
However I am not able to see my device when I use the adb devices command. I noticed that the drivers for the transformer are not installed. So I tried to install them and it tells me that windows can't install. I am pointing the installer to the MTP devices driver folder.
How do I get the drivers to work so I can use ADB or can I set up ADB in Linux and not have to worry about the drivers?
edit: I forgot to mention I am running windows vista.
Hi! Search in transformer's support page, you can find the drivers there
Are you saying that the drivers in the MTP folder are not the right ones? I got them right from Asus' website. Which drivers should I be using?
Ageesaman, did you ever get the drivers working? I had the exact same problem (got adb working as far as listing devices, but then it returned with a blank line after "adb devices" in cmd window). I downloaded the ASUS site's USB drivers download as well as every other utility from that site; I also tried external sources; finally, I tried manually updating by pointing to the unzipped MTP folder - nothing worked. I used both 64 and 32 bit Windows 7 machines. I am stuck in the cwm recovery loop so I can't do much troubleshooting. I tried searching dozens of sites for several hours but came up short.
Thanks in advance for any help offered.
Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.
Ageesaman,
Unfortunately I know nothing about Linux, but what finally got it working for me was starting the installation of PDANet for Android. I saw it look for and install the driver, then I got a ADB confirmation. I then canceled the PDANet install. If you decide to go this route and get error messages in the cmd window, retry "adb devices" up to 3 times. In the meantime, I hope you get your Linux answer. Good luck.
I will give that a try. Is PDAnet something from Asus? I will do a search and see if I can find it.
ageesaman said:
Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.
Click to expand...
Click to collapse
Yes, I can confirm the TF101 works with ADB without drivers on Ubuntu linux [I am on 11.04]. The current [stable, with 12.04 betas] Ubuntu version is 11.10, and you can download it to a live CD and run it off the CD without installing it.
I just got my tf101 the other day and I tried using adb [and older version], and it did not show up. Then I downloaded the tf101 root.zip file, and tried the adb within that folder, and it worked.
I've uploaded it to mediafire:
adb-1.0.29 http://www.mediafire.com/?hqwxbljs2gbpfxe
md5 64c4afbab6d2f769ddbb229f0247cf8a
update: newest adb is 1.0.31 http://www.mediafire.com/download.php?vcvc4dxkdd57695
md5 ed5c8f9a221cae0cb24d6cdc8b76d396
download, and run
chmod +x ./adb-1.0.29
to make it executable
That worked! I can now connect to my device with ADB. Thanks for that pdanet advice.
Now I just need to figure out how to push the file. Can't seem to get it to work. Here is what I am typing in the cmd line.
adb push rom.zip /sdcard
The rom I am trying to push is in the Platform tools folder that I am using to access adb. Does anybody know what I am doing wrong? Any help would be awesome.
is the rom.zip in the same directory as you are in (cd <path>)?
What does it say when you try to transfer it?
You can also try to push it to the full path (/mnt/sdcard/)
The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.
ageesaman said:
The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.
Click to expand...
Click to collapse
It's probably because /sdcard is a soft link to /mnt/sdcard/
if you did /sdcard/, I think it should probably work.
You sir are the man! Thanks for your time.
To get the process all in the same place for anyone else who may need this here you go. Just to make it clear.... This is what I did on my device and it worked. It may or may not work for you but maybe it's worth a try.
1. Downloaded SDK and Java JDK.
2. Used PDAnet to force windows to install the correct ADB device drivers.
3. When the drivers where installed and ADB was working I used this command to push the .zip file to the internal sd card.
adb push rom.zip /sdcard/
Just a few notes for this.
ADB was not working well at first because I had Asus sync running in the background. Make sure this is off.
Also make sure you put the file you are trying to push in the same directory you are using for ADB. For instance I used C:/android-sdk/platform-tools/ to access ADB so the file had to be in that folder in windows explorer.
To make it easier to type (I had to do this a lot while troubleshooting) I changed the name of the rom I was trying to push to rom.zip. This made typos less of an issue.
Make sure that you put the file extension (.zip in my case) in the ADB command even if it doesn't say it when you look at the file in windows explorer.
I think that is it in a nutshell. I hope this helps anyone else who needs to push a rom.
Good Luck
This method in this post didn't work for me, but this one did: http://forum.xda-developers.com/showthread.php?t=1689193
I set Windows to look for driver in c:. After a while one was installed and worked.
What I did on windows 7
Go to Device manager
Find transformer , right click on faulty marked unit.
Select properties
go to tab driver
update driver
Select browse
select path to the subfolder ANDROID ( containing usb drivers from asus )
include subfolders
Windows will find to alternatives , choose xxxx ADB
Windows will complain, ignore
done
/Claes R
W