Having trouble rooting on Windows 7 64bit - G2 and Desire Z General

I am having a bit of difficulty rooting my g2. I am not sure if its related to my os or not but i can not get it to work.
I have followed this and tried it all kinds of different ways.
addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/[/url]
I can get to my run command after doing all of that and it shows my serial number after typing adb devices but after that i can't enter any info in the sdk run command promt.
I have not been able to gain temp root yet because it won't let me enter the commands. I went to try to re-install java/sdk manager yet again and now it says java is not in the right path.
Any help?

If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.

martonikaj said:
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
Click to expand...
Click to collapse
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible

901-Memphis said:
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
Click to expand...
Click to collapse
Yep let me grab a link for you (theres actually a video tutorial I wanna try and find). But basically instead of using ADB to push the files to the correct location, you just have to manually put the files in the right locations on the SDcard, which is where ADB pushes them anyways.
K so I followed this method: http://www.youtube.com/watch?v=tU9zn_BEth4
The files he refers to are in this thread: http://forum.xda-developers.com/showthread.php?t=833965
Now different people have had different issues with this. I personally had some issues where it tells you to run #sync, because my perm root wouldn't stick properly after reboot. If this doesn't work properly, I'm sure someone can help you with your drivers to get ADB working.
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.

If you got the adb devices command to work you are actually in good shape. You are supposed to enter all of the commands from what you are calling the "run command" prompt anyway (the one you used for adb devices).

martonikaj said:
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
Click to expand...
Click to collapse
Unfortunately this won't work (if you don't want to use ADB, Visionary must be used to get temp root). ADB is needed in order to push the files directly to the phone. If you try copying the files to the SD card first, you won't have the correct permissions to copy the files to the phone in Terminal. You are also not allowed to execute programs directly from the SD card (mounted as noexec), so you can't try to obtain temp root from there. If you want to use the gfree method of rooting without using ADB, I made a guide using Visionary for the temp root here: http://forum.xda-developers.com/showthread.php?t=928160.
But the OP actually has ADB working, so he should be able to use any of the guides.

This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Uploaded with ImageShack.us

901-Memphis said:
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Click to expand...
Click to collapse
You are supposed to be using the regular command prompt (I think you referred to it as the "run command prompt" earlier). It is the prompt in which you successfully ran the "adb devices" command. That is the only prompt you need to use.

Do i enter commands 1 at a time or all at once?

901-Memphis said:
Do i enter commands 1 at a time or all at once?
Click to expand...
Click to collapse
First off, Yes you enter each line as you see it.
Second just to make sure you are in the right area to enter these commands, to get to command prompt you can either search for it from the start menu or hold the "windows button + R".
That opens your run command from there type in "cmd" and that opens command prompt.
Next make sure your current directory is the one you installed adb into. To get to that you can type "cd C:/...... whatever folder you installed it to."
To make sure my adb is working I usually type "adb devices" and see if my phone shows up.
Good luck

Glad to see someone else from the good ole 901 around here =)
Sent from my HTC Vision using XDA App

Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file

901-Memphis said:
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
Click to expand...
Click to collapse
try pushing the file to that folder again

Re-Tried everything at least 3 times, including pushing the files that didn't go.
I give up Ive spent so much time on this only to have it fail at the most unlikely times.
Will wait for another method to root come available

You could try downloading and installing Droid Explorer. It installs adb and fastboot files in its install folder.

Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).

ianmcquinn said:
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
Click to expand...
Click to collapse
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything

901-Memphis said:
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
Click to expand...
Click to collapse
You are supposed to do that command from your computer. (The instructions state "On the computer, open terminal and type the following commands".) Here, terminal means the command prompt that you've been running all of you other ADB commands from.
If you wanted to run the command from terminal on your phone, you would just type "chmod 777 /data/local/gfree".

You don't need ADB for G2s.

trance2315 said:
You don't need ADB for G2s.
Click to expand...
Click to collapse
Can someone link me a better guide for my G2 so that i can try this 1 more time ?
Maybe a link to the top choices for versions of android to run once i get it rooted?

Related

How to push files through ADB

Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556
Great post, very easy to follow, thank you.
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
this also works for the samsung Galaxy S in recovery mode.
mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.
Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App
Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey
Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA
Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons
Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !
Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination
Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...
rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?

Best Guide Online on how to Root your X

I don't feel like reformatting it to make it look good. You can find my post at AllDroid.org or by following this link http://alldroid.org/Default.aspx?tabid=40&g=posts&t=554 let me know if this helped you out. If you follow it to a tee you should have no problems at all.
This is what the link that they OP posted says.
This is a walk-through of how to root your Droid X using the Birdman's method. This walk-though is based off of Rainabba's walk-though but I am going to go into a little bit more detail on some sections to make it more understandable for newer people to rooting.
Before starting this walk-through make sure you do not have any Server Applications running on your computer. This includes stuff like PDAnet's or Some Bluetooth server apps. I noticed that PDAnet will close the adb.exe so you can't do anything. It has also come to my attention that bit-torrent and U-torrent applications may interfere with this process shut those down to.
First you will need to download 3 files, just put these files onto your desktop.
Download the DroidXRoot_v2.zip file from http://alldroid.org/default.aspx?g=posts&t=493
Download the ADBDriver_v3_Google.zip from http://alldroid.org/Defa...40&g=posts&t=495
Download the correct SDK for your OS (Operating System) from http://developer.android.com/sdk/index.html
Now that you have all 3 files downloaded and put onto your desktop its time to do stuff with them.
Extract the DroidXRoot_v2.zip to drive "c:" and just name it "DroidXRoot" so it will look like "c:/DroidXRoot"
Extract the SDK folder into your "DroidXRoot" it doesn't matter what the name of this folder is I used the preset name. This should not look like "c:/DroidXRoot/android-sdk-windows"
Open the "android-sdk-windows" folder and then open the "Tools" folder. From here copy ALL of the files from this folder.
Back out of the "Tools" folder and then out of the "android-sdk-windows" folder. You should now be in "c:/DroidXRoot" Paste those files in here.
Right now Bookmark this page, doing the ADB driver install requires a reboot. This way you can find this post instantly.
Time to install the ADB drivers. For these instructions go to http://alldroid.org/Defa...40&g=posts&t=495 and follow the instructions.
Assuming that the installation went through with no problems, its time to move on.
(Where you see the "Run" at type the command in the quotes ("") but with out the quotes. You should also be able to just copy and past whats inside the quotes if your lazy)
Go to the phone it should still be plugged in from doing the ADB driver install if not plug it in now.
Go to your phone: Home, Menu Button, Settings, Applications, Development: Make sure the "USB debugging" option is enabled/checked.
Hit your Home Button and pull down the Status Bar and click on USB connection: Make sure its set to PC MODE.
Open a command prompt (On Windows 7 and Vista: Start, then type cmd, Right click the cmd and make sure you run as admin. Linix just open the terminal and make sure your running Root through it. If you don't know how to get that good terminal root.)
Ok now that you have your command prompt open Run "cd c:\DroidXRoot"
Run "adb devices" you should see your device listed with a whole bunch of numbers. If you get the message "No devices found" you didn't copy and past the files correct from the tools folder to the "DroidXRoot" folder or you didn't install the driver right from the previous post. If you get the message "adb is not recognized as an internal or external command" you may still have a server file running, make sure there all exited since you rebooted while installing the "adb" drivers. Well if you see your device your doing great keep moving.
Run "adb push Superuser.apk /sdcard/Superuser.apk"
Run "adb push su /sdcard/su"
Run "adb push busybox /sdcard/busybox"
Run "adb push exploid /sqlite_stmt_journals/exploid" If you have any problems with the pushing as in getting the "access denied" response then you did not start in an admin or root and need to restart...
Run "adb shell"
Run "cd sqlite_stmt_journals"
Run "chmod 755 exploid"
Where doing great if you didn't have any problems. From here pick up your phone, and navigate to a screen where you can turn on/off your WiFi with a widget, turn your WiFi on. You will need to turn it off then back on instantly after the following command.
Run "./exploid" turn your Wifi off then turn it back on. Now follow the directions on your command prompt. When that completes you will be back at a shell prompt.
Run "rootshell" You will be prompted for a password enter "secretlol" and press Enter. You are now root but you still have more to do. (You will know that you are in root because your prompt will be a "#" instead of "$")
Run "cp /sdcard/Superuser.apk /system/app/Superuser.apk"
Run "cp /sdcard/su /system/bin/su"
Run "cp /sdcard/busybox /system/bin/busybox"
Run "chmod 4755 /system/bin/su"
Run "chmod 4755 /system/bin/busybox"
Run "rm /system/bin/rootshell"
Run "exit" to drop from root to a non-root user, you will still be logged into the phone.
Run "exit" again to drop back from your phone to your computer command prompt, you should be at "c:\DroidXRoot"
Now you need to confirm that you have established Root:
Run "adb shell"
Run "su" you should now see the "#" sign which indicates you are root)
WATCH YOUR DROID X SCREEN SO YOU CAN ALLOW SUPERUSER ROOT ACCESS!!!
Credits
Sebastian Kramer for this blog post - http://c-skills.blogspot...07/android-trickery.html
Birdman - for editing Sebastians work for the droidx
[mbm] - for answering birdmans many questions while root was tried (and failed xD)
Rainabba - for the original post located at http://alldroid.org/default.aspx?g=posts&t=493
The blog list
Birdman - @mrweeeedbirdman - http://stevenbird.info
Rainabba - @rainabba - http://rainabba.blogspot.com
Videos
Evidence of root: http://tiny.cc/DroidXRootProof
Video tutorial for root: http://tiny.cc/How2RootDroidXVideo
As is always the case with this sort of activity, you do this completely at your own risk. AllDroid, Rainabba, Birdman, and myself take NO responsibility for the outcome.
Edited 7/27/10
Added the section about shutting down the Bit-torrent and U-torrent applications - Thanks sanzy for finding that out.
Fixed a typo in line 21 - Thanks kdkinc fo noticing that.
Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App
ksidirt said:
Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own
MrDanger said:
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own
Click to expand...
Click to collapse
Awesome. Thank you.
I ended up using the following:
http://alldroid.org/default.aspx?g=posts&t=553
Worked first try.
If you're going to update to 2.2, you will need to run some additional commands prior to the update via adb or Root Explorer.
I've not had any issues with 2.2 - and I upgraded the day I got my X. No complaints here.
I'm also not really concerned with getting the official OTA -- chances are it (or a version of the update that is compatible with the leaked 2.2) will be found in the wild before long.

[Q] Can I root and obtain S-OFF without ADB?

Ive just ordered a desire z and have been reading a bit on the uber root method.....
What i want to know is can I use a file manager to install the visinary.apk and then the terminal emulator from the phone to run all the adb commands?
Reason i ask is cos A) ADB freaks me out....just the install instructions make my head spin and B) i havent got any space on my even if i wanted to install it....
Im aware that you need to install the gscript to /data/local but can this be done just by dropping it into the relevant place rather than pushing it using ADB?
and assuming I can?
Which bits of the commands do i run ? looking at the following.....
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
do i just pick this up from the point of SU?
oh and errr if ive completely got the wrong end of the stick then please say.....id sooner look stupid than have a £420 brick
cheers peeps
Yes, if you want you can copy the gfree program to your SD card via some other method, and then pick up the instructions from the su onwards.
An alternative is to run the "rage" method of rooting, but if you don't like adb (it's a lot easier than it might look) then maybe that's not for you.
steviewevie said:
Yes, if you want you can copy the gfree program to your SD card via some other method, and then pick up the instructions from the su onwards.
An alternative is to run the "rage" method of rooting, but if you don't like adb (it's a lot easier than it might look) then maybe that's not for you.
Click to expand...
Click to collapse
TBH its not the ADB commands that i struggle with its the setup of ADB itself.....ADB, SDK, HBOOT drivers, issues with windows 7 etc....
Im happy running the commands and sort of understand what im asking my phone to do so if i can get by without ADB i will try
Thanks for clarifying though
rtorbs said:
TBH its not the ADB commands that i struggle with its the setup of ADB itself.....ADB, SDK, HBOOT drivers, issues with windows 7 etc....
Im happy running the commands and sort of understand what im asking my phone to do so if i can get by without ADB i will try
Thanks for clarifying though
Click to expand...
Click to collapse
I suggest you to read the Easy root / flashing tutorial and FAQ post located at android development subforum
And regarding ADB, if you daownload qpop's "uber root" package, everything required is inside the zip, even ADB is inside
i used gtrab's guide...
super easy and no adb necessary.
http://forum.xda-developers.com/showthread.php?t=835777
bradleymor said:
i used gtrab's guide...
super easy and no adb necessary.
http://forum.xda-developers.com/showthread.php?t=835777
Click to expand...
Click to collapse
Things evolve quicky, problem with this guide is hBoot step was very risky, and it was sort of a "false" S-OFF
The newer method is easyer, safer, and doesn't require manually flashing hBoot
The guide has been reestructurated accordingly
gtrab said:
I suggest you to read the Easy root / flashing tutorial and FAQ post located at android development subforum
And regarding ADB, if you daownload qpop's "uber root" package, everything required is inside the zip, even ADB is inside
Click to expand...
Click to collapse
I've already read them pal, that's why im here...I was just clarifying that I could use the terminal emulator rather than adb.....I'm pretty sure what i need to do now so its cool
Cheers peeps
Sent from my HTC Hero using XDA App
rtorbs said:
I've already read them pal, that's why im here...I was just clarifying that I could use the terminal emulator rather than adb.....I'm pretty sure what i need to do now so its cool
Cheers peeps
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
The reason the guide is all ADB is that its much easier to get right with adb...seriously there's no install needed, just open up a command prompt in windows seven (or use the packaged cmd.bat from my zip) and follow instructions. No install needed, no complexities, no messing around with a very limited terminal clone.
But yea, as long as you get the gfree file onto your phone it should be ok
qpop said:
The reason the guide is all ADB is that its much easier to get right with adb...seriously there's no install needed, just open up a command prompt in windows seven (or use the packaged cmd.bat from my zip) and follow instructions. No install needed, no complexities, no messing around with a very limited terminal clone.
But yea, as long as you get the gfree file onto your phone it should be ok
Click to expand...
Click to collapse
Ok cool....sounds a bit more promising....will give it a bash....at least I know I now have a plan b with the term emulator if I have problms
Cheers
Sent from my HTC Hero using XDA App
As someone who had never even heard of ADB and is on his first Android phone..believe me when I tell you that all these different instructions and methods made my head spin! What I ended up doing was (can't remember which "method" it was called) just downloading the VISIONary program onto my SD card, and then running it right from the phone to achieve my ROOT. Once I was rooted, I used the UBERROOT method for S-OFF. I simply downloaded the ADB program (and whatever else it was that came with it)..let it go thru it's updates and made sure the computer recognized my phone (by making sure drivers were installed). Plug your phone into the computer..open up the gfree program you downloaded...and inside there is two main programs..and exe and the cmd. I ran the exe, then simply opened up the cmd program..entered the necessary commands..and viola! It really was simple once I finished it.

Want to root my legend 2.2 ota... wwe_3.15.405.3-2

I read many thread but didn't find clear answer for this question.
I have a vodafone htc legend with froyo updated trought ota
I would, root it and install HTC rooted rom.
any body can help with the steps and tools need it?
thanks a lot
follow this http://android.modaco.com/content/htc-legend-legend-modaco-com/323201/downgrading-from-froyo-ota/
it is not rooting, it is downgrade, what's not same
rolks said:
it is not rooting, it is downgrade, what's not same
Click to expand...
Click to collapse
he have official froyo... then he must downgrade first or what??
FIRST HAVE TO DOWNGRADE
follow this http://android.modaco.com/content/htc-legend-legend-modaco-com/323201/downgrading-from-froyo-ota/
Click to expand...
Click to collapse
THEN U CAN ROOT
http://theunlockr.com/2010/06/07/how-to-root-the-htc-legend/
Great!
If I undertood right...
First downgrade (this is something we could not avoid) then root.
Let me try!
Ill back!
Thanks
MontseCat said:
Great!
If I undertood right...
First downgrade (this is something we could not avoid) then root.
Let me try!
Ill back!
Thanks
Click to expand...
Click to collapse
i followed these steps and now i have rooted legend with BlaYo ROM B 0.2...
GOOD LUCK
I tried yesterday and having some troubles with Android sdk, doesn't work I don't know if any trouble with its installation.
Need to read carefully the instalation process and try again.
The only issue is find time for ths... its chrismas so, some familiar meetings
I'll back!
Oh!
I tried once again with not succes.
when running "crackin"...
starts with...
"Copying tools"
"adb" is not recogniced as command internal or external
program or file executable...
And remainds with same message for serveral lines till finish!!
Nothing happens.
I installed the android sdk package and added the hack4legend-v5.zip contenst on android-sdk-windows\tootls folder
Obviously I am doing something wrong but I am not able to locate where the problem or mistake is!!
any idea?
thanks
I downgraded my Legend from the OTA 2.2.
Now the ROM version is 1.31 which should be correct, but the HBOOT version still is 1.00, which is according to this guide (http://forum.xda-developers.com/showthread.php?t=746454 ) the wrong one, it should be 0.43.... any ideas on this one?
Edit: @MontseCat: have you installed your USB drivers? The come with HTC Sync from the HTC homepage. Otherwise you can check adb functionality by opening a console window, running 'cd C:\Absolute\Path\containing\adb.exe\' (for Windows users, I guess Linux users know how to use cd) and then 'adb devices'. This should show a number refering to your device, opposed to simply nothing if it is not working.
nae64 said:
Edit: @MontseCat: have you installed your USB drivers? The come with HTC Sync from the HTC homepage. Otherwise you can check adb functionality by opening a console window, running 'cd C:\Absolute\Path\containing\adb.exe\' (for Windows users, I guess Linux users know how to use cd) and then 'adb devices'. This should show a number refering to your device, opposed to simply nothing if it is not working.
Click to expand...
Click to collapse
Sorry I don't follow you at all.
I currently have my legend working with HTC Sync, witout problems, so don't undesrtand, shall I remove an reinstal it after installed android sdk to?? or..
thanks
No, that was just my problem at first when I had to move to a Windows PC for the downgrade, adb requires HTC Sync. So you should be fine.
But now that I read your problem again, my solution would not even fit I guess your tools directory does not contain the adb.exe. But the directory platform-tools in the android-sdk folder does. I just copied over the contents of the hack zip to platform-tools and did it from there... what ever, now I am having the problem i described above...
nae64 said:
I downgraded my Legend from the OTA 2.2.
Now the ROM version is 1.31 which should be correct, but the HBOOT version still is 1.00, which is according to this guide (http://forum.xda-developers.com/showthread.php?t=746454 ) the wrong one, it should be 0.43.... any ideas on this one?
Edit: @MontseCat: have you installed your USB drivers? The come with HTC Sync from the HTC homepage. Otherwise you can check adb functionality by opening a console window, running 'cd C:\Absolute\Path\containing\adb.exe\' (for Windows users, I guess Linux users know how to use cd) and then 'adb devices'. This should show a number refering to your device, opposed to simply nothing if it is not working.
Click to expand...
Click to collapse
Hmm my HBOOT version is 1.01
Sent from my HTC Legend using XDA App
Okay, thank you very much, root completed successfully even with HBOOT v1.00
nae64 said:
... But the directory platform-tools in the android-sdk folder does. I just copied over the contents of the hack zip to platform-tools and did it from there... what ever, now I am having the problem i described above...
Click to expand...
Click to collapse
I done as you said and succed,
Now the problem is
CR--rw----
So fails
the message at the end is xxxx permision denied.
I don't konw how to put an image of the scren. sorry
what whall I do now?
MontseCat said:
I done as you said and succed,
Now the problem is
CR--rw----
So fails
the message at the end is xxxx permision denied.
I don't konw how to put an image of the scren. sorry
what whall I do now?
Click to expand...
Click to collapse
- Temproot with VISIONary r13 (install the downloaded file as per a normal APK)
- Once you are temprooted, connect via 'adb' and do 'su' (to get root) then '/data/local/flash_image misc /data/local/misc1-2.img'
You should then be able to downgrade in the normal way.
janarp said:
- Temproot with VISIONary r13 (install the downloaded file as per a normal APK)
- Once you are temprooted, connect via 'adb' and do 'su' (to get root) then '/data/local/flash_image misc /data/local/misc1-2.img'
You should then be able to downgrade in the normal way.
Click to expand...
Click to collapse
Ok I Istalled the Visionary and temorary root,
I don't know how to connect via 'adb' and do su...
so, just stoped here and waiting next instruction. Sorry work as neel!!
[HOW-TO] ADB for Dummies(How-To Learner's Guide)
janarp said:
[HOW-TO] ADB for Dummies(How-To Learner's Guide)
Click to expand...
Click to collapse
even with this guide I didn't succed!!!
What I done is just temporary root with visionary then run again the adb but remains the same,
sorry I don't see where lost!!
In the following I will assume a Windows-PC:
1. Restart your phone to start from scratch, make sure 'TempRoot on boot' (or sth along this line...) is NOT checked
2. Run the crackin.bat, which you put (along with all other files in that download) into the directory containing the adb.exe (which is, at least for me, the platform-tools directory)
3. when it fails (it will), TempRoot using VISIONary, leaving everything unchecked (no System Read Write, even if that seems like a good idea)
4. on your PC, go to a Terminal (Windowsbutton + R, enter 'cmd' without quotes, press enter) , navigate to the folder crackin.whatever is in using the cd command like in my following example, but with the correct, full path
Example: 'cd "C:\\Programm Files\Android\andorid-sdk\platform-tools"' (again, without the single quotes (preserve doublequotes))
5. in that same Terminal Window, enter 'adb shell' (again, without quotes). The prompt should change to a dollar sign. Then enter 'su' (you know, without quotes...), and when the prompt changes to a '#', the TempRoot was successful and we can resume. Make sure to leave that Terminal open, you can use it again when rooting.
6. On a Windos System (32bit preferred) run the RUU.something.exe and follow these steps.
7. follow the main rooting guide, in which you will have to open a Terminal Window in the directory you unzipped. This is done with the same method I described above (opening cmd, 'cd' command)
I hope this makes it more clear =)
Edit: btw, this is a full guide, feel free to pick out the stuff you need, because I really did not understand what your problem was =) as a rooting guide I used this: http://forum.xda-developers.com/showthread.php?t=746454
MontseCat said:
even with this guide I didn't succed!!!
What I done is just temporary root with visionary then run again the adb but remains the same,
sorry I don't see where lost!!
Click to expand...
Click to collapse
i belive u have same folder names like me...
first i connect my phone with pc then i open command (start and type cmd)
Code:
cd C:\android-sdk-windows-1.1_r1\tools
then
Code:
adb shell
and then
Code:
su
and then follow nae64 post
point 6 and 7

Trying to root but can't get ADB working

I've finally decided to try to root my G2 but can't get past the ADB setup. I downloaded the SDK, but when I open the manager and try to install platform tools it goes through the motions and then tells me nothing was installed. When I open a command prompt and type "ADB devices" it doesn't recognize anything. What am I doing wrong??
EDIT: specifically, when I try to install platform-tools it tells me it couldn't create a directory and nothing was installed.
66 people have read this and nobody has any suggestions to help?
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
I have a problem after rebooting my PC: <Java not found...> Reinstalling doesn't help, adding environment variables too. Any idea?
Just root using the rage/visionary method. No adb needed and very easy to do. Here is the linkhttp://forum.xda-developers.com/showthread.php?t=834228
Sent from my SilverBullet 'HTCDesireZ running CM7'
juvanni said:
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
Click to expand...
Click to collapse
I don't understand? I'm trying to root following the recommended wiki instructions, and I haven't been able to get adb to work so I haven't gotten past that step.
Are you running windows x64? Cause the android installer has issues detecting java on x64 systems.
When it says 'Can't find java' or whatever the error is, click back, then next again, it should find it the second time around. Well thats what happened for me anyway.
-Nipqer
If you're on froyo just use the app z4 root or universal androot
You can also use superoneclick root 2.11
Its very easy and it only take about 3 minutes
Stewie just said that!
I appreciate the help so far, but my problem is I have gingerbread and everything I've read requires froyo for root, and the only way I've read to downgrade uses ADB, so any non-ADB rooting method still won't work for me. I've followed the "ADB for dummies" thread and the other instruction thread and everything seems fine, but when I type in the first command for the downgrading it says adb isn't a recognized command. Am I in the wrong command prompt? I feel like its probably something really dumb I'm doing or not doing but for the life of me I can't figure it out.
Navigate to the folder adb is in.
Hold shift, right click in the folder (make sure nothing is selected)
select 'Open command window here' (or something along those lines)
Adb should work.
-Nipqer
OK, so I'm definitely in the right folder, I read and followed ADB for Dummies thread. Trying to follow this direction:
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
$ adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length"
When I type that in, should there be spaces between the "adb" and "shell"? Should there be a space after the command prompt and before "adb"? I've tried several variations of it and it keeps telling me "adb is not recognized as an internal or external operable program or batch file."
ok you need to run the command from the folder with adb.exe in it, type it as adb<space>shell<space>cat<space>/dev/msm_rotator
If you are getting an error search for adb.exe and once found try the command again from this folder,if as you say you are in the right folder then I think you will have to reinstall adb as I just ran the command in the form above and it works so if you still get an error then something has gone wrong with the install
P.S Another way to make sure that adb is working and recognises your phone is to type adb devices, if your phone is attached and recognised then it will return a number
Thank you! I had to uninstall and reinstall the package, I don't know what was wrong but it seems to be working now. Also, I knew I was probably doing something stupid, and I was. I wasn't in the platform-tools directory for my command prompt, I was in the TOOLs directory. Just so I'm clear, every command I type into the terminal should be in the Platform-tools directory, correct?
Now, assuming I can follow all the other directions with no problems, once I get to the downgrade pushing steps, I will lose all my current settings, right? It will be a fresh froyo 2.2 like it came to me originally? Other than using Appbrain to back up my current apps, how else should I make a backup?
Final question, do I need to follow the temp root directions and push the downgrade all at one time? Or can I do the temp root and come back at a later time to push the downgrade?
First problem solved then!
Yes but follow this 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 !)if you want to.
Once done you can use ADB from the command prompt in ANY folder,very handy IMO.
If I was you I would set aside enough time and see it through,no point to temp rooting alone.
Get Titanium backup from the market an absolute essential app with this you can backup,upload to dropbox(Another essential app) uninstall apps and a host of other useful tools.
Read the guide first as well,good luck.

Categories

Resources