Develop Bugs

Having trouble with drivers while trying to root..

Trying to use the http://forum.xda-developers.com/showthread.php?t=829045
Like a Boss Hboot 2.02 root but got the $ instead of # sign after i went into the shell and its telling me "You Should see a "#". This means you have root if you see a "$" or some other error message. Reboot your phone, check your drivers, usb debugging and cable and start over. If you got a "#" You can Proceed. You should still be in the shell at a "#" If not start over.." and at the beginning it tells me to "Make sure you have the drivers installed for your phone (recommend: SDK Drivers, unrevoked hboot drivers" but im not sure exactly what that means or how to do it, i thought i was doing alright but i dont think i have it all quite figured out, anyone know the next step i should take to keep from bricking this thing?

Nothin? I ran Unrevoked3 and put everything into the C:/android-sdk-windows folder so hopefully it put the right drivers in there, if im doing this entirely wrong someone say something please!

try typing SU then enter after the $ prompt, if that gives you the # prompt proceed, also be sure to run unrevoked forever to permantly unlock nand and get s-off, ok so i just also read a little more carefully, this method listed in your OP is not unrevoked3, maybe a little more info on exactly what you did would help.

ifly4vamerica said:
try typing SU then enter after the $ prompt, if that gives you the # prompt proceed, also be sure to run unrevoked forever to permantly unlock nand and get s-off
Click to expand...
Click to collapse
Permission denied on the SU im afraid to run the wrong unrevoked because of the damn HBoot 2.02 think itll be straight if i do it regardless?

its gotta be the drivers, what am i missing here? this is driving me nuts, i spent 3 hours earlier 2 of which were to turn it back into a phone, it was a brick...

ifly4vamerica said:
try typing SU then enter after the $ prompt, if that gives you the # prompt proceed, also be sure to run unrevoked forever to permantly unlock nand and get s-off, ok so i just also read a little more carefully, this method listed in your OP is not unrevoked3, maybe a little more info on exactly what you did would help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=829045 Im using this guide and ive made it up to step 6, if i go to the device manager i have Android USB Devices and when its plugged in it says My HTC and down lower i have portable devices and its just named G:/ but when i tried to update the drivers it says theyre all up to date, any idea if i need to uninstall the ones i have and use a different set of drivers? like installing HTC Sync then uninstalling it? just not sure whats going on..

Not to sure on this one, what did it do when you typed SU? Also what version of hboot do you have, are you sure it is 2.02? if not just keep trying sometimes the exploit doesnt work the first time.

Yeah def. got 2.02 when i typed SU it said Permission Denied I believe its a problem with not having all the drivers on the computer itself, should i install HTC Sync then uninstall it to get its drivers at least?

you can try that for sure, you did use adb to push all of those files in the zip to your sd card right? or did you just drag and drop them?

Used the adb push method to the absolute T but didnt figure out the right drivers at the beginning so im starting over there, what does it mean by the Unrevoked HBoot drivers, i did the unrevoked3 install and that worked out fine but dont think thats what it meant.

So now the phones labeled differently in the device manager, im supposed to delete the actual HTC Sync program before i begin but leave the driver installer and everything right? and i have all the unrevoked folders and SDK ones together in the file i pushed from like it told me to so im going to try to update all those and make sure the drivers are all correct then start the command prompt over again, its in charge only and debug mode of course.

Any idea if the DIAG drivers have anything to do with it? http://forum.xda-developers.com/showthread.php?t=766374 as said in here where you have to actually pick them through the phone?

uhh i may of been retarded by not clicking the SDK Setup.exe file and running it.. wow... snuck that one right by me >_<

Tried to Root G2 (S-ON)

If on Recovery, it says S-ON, is that a Problem?

triumphantpower said:
If on Recovery, it says S-ON, is that a Problem?
Click to expand...
Click to collapse
If it says S-ON, you don't have permaroot. Did you follow the guide in the wiki?
Sent from my T-Mobile G2 using XDA App

I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)

triumphantpower said:
I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)
Click to expand...
Click to collapse
YouTube *really* shouldn't be the go to for things like this, unless you like bricks. This guide is by the folks who actually engineered the hack: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my T-Mobile G2 using XDA App

oh alright, Thank You OriginalGabriel.
But is rage an adb command or an app from the Market?

and where would the HTC G2 Drivers have to be installed?

triumphantpower said:
and where would the HTC G2 Drivers have to be installed?
Click to expand...
Click to collapse
If you've used adb (eg. you have the SDK installed on your computer), then you have the drivers already installed. Otherwise, unzip the file and when you plug your computer into your phone, point the hardware wizard to the folder that you unzipped
Rage is an included binary in gfree_temp-root.zip

Got it Thank You.
I got to where I have to use ADB, and while trying to $ adb push su /sdcard/su
It won't let allow me, it'll say access denied. (I've even put adb shell before that command)

I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied

triumphantpower said:
I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied
Click to expand...
Click to collapse
on your phone be sure you have menu>settings>applications>development>usb debugging checked (on)

I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON

triumphantpower said:
I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON
Click to expand...
Click to collapse
After you do the temp root, shut down adb (I am using a windows machine so I ctrl alt del and find it in task manager and shut it down that way) It should restart by itself when you do the perm root commands. ( you probably know this, but don't enter the # sign, it should be there by itself)

Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before

triumphantpower said:
Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before
Click to expand...
Click to collapse
Download ROM manager from the market, spend the few bucks for the upgrade and then install clockworkmod recovery through ROM Manager (if you haven't done this already). Then, do some more reading about doing a Nandroid backup and you're ready to go! Now, the fun begins....lol!

I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?

triumphantpower said:
I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?
Click to expand...
Click to collapse
do you have the superuser app now in your applications drawer?
edit: Also, disconnect the phone from the USB. That might give ROM manager a problem accessing your sd card if you're still connected.

yeah I have Superuser Permissions but it FC's when you try to open it

triumphantpower said:
yeah I have Superuser Permissions but it FC's when you try to open it
Click to expand...
Click to collapse
Try uninstalling ROM Manager and after that see if you still get a force close when you try to open Superuser.

Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]

triumphantpower said:
Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]
Click to expand...
Click to collapse
what happens when, in ROM Manager, you select "fix permissions"?

[Q] Have I managed Perm Root with this much ease? Visionary+ Question

About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?

Arconaught said:
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Click to expand...
Click to collapse
Having the SuperUser icon just means the app is installed, open up terminal and type 'su' to see if it throws up any errors
Sent from my HTC Vision using XDA App

I should have mentioned that I did that and got the # symbol, am I good to go?

Arconaught said:
I should have mentioned that I did that and got the # symbol, am I good to go?
Click to expand...
Click to collapse
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Sent from my HTC Vision using XDA App

OriginalGabriel said:
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Click to expand...
Click to collapse
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).

redpoint73 said:
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
Click to expand...
Click to collapse
This is my understanding as well, though I'd probably still use GFREE to get S-OFF if I were OP.

That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.

Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
I used the wiki method myself, those that used other methods (like Visionary) and were told to root via the wiki seem to have all just started at the beginning, from what I've read.
Sent from my HTC Vision using XDA App

Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
Whoa the Wiki method is completely different, looks like it was rewritten on 04/01.
You can completely ignore the temp rooting steps and concentrate on the gfree steps
From the "Necessary Files" section you need gfree, flash_image and ClockWorkMod Recovery
I would use the latest ClockWorkMod recovery rather than the one listed on the Wiki:
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img (of course it's only the latest as of the time of this writing)
From step 2 you need to use:
Code:
$ adb push gfree /data/local/tmp/
$ adb push flash_image /data/local/tmp/
From step 2.a you need to use:
Code:
$ adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
Again note that the file name for CWM will depend on the version of CWM you are using.
Skip to step 4.b you need to use:
Code:
# cd /data/local/tmp
# ./gfree -f
# ./flash_image recovery recovery.img
# sync
Continue on as normal from here.
I skipped the temp root and perm root sections as you are already perm root.
I also skipped the ENG HBOOT parts, since that's not strictly necessary and the most risky part of the whole process (one mistake can result in a brick). If you want to flash the ENG HBOOT you would need to follow steps 4.a instead of 4.b, (you would also need the necessary HBOOT of course) the only command you need to omit from 4.a or 4.b is "# ./root_psn" which is the script which establishes permanent root.

Thanks a lot so far man, but I'm still stuck. I have adb, when I open it in the SDK, it flows for a bit, then closes. This is right, right? I'm meant to do all of these prompts via the cmd window?

OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.

Arconaught said:
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Click to expand...
Click to collapse
You say you've sorted adb, but can you be more specific please ? What works and what doesn't work exactly ?

Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?

There is a great write up here about getting adb working. It sounds like either you didn't set up a "path" to use those commands anywhere or if you don't want to do that make sure your files are in the same folder as your adb.
Sent from my HTC Vision using XDA App

Arconaught said:
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
Click to expand...
Click to collapse
You need to have the files (extracted from the ZIP files you downloaded) in the same folder you run the ADB commands, if your ADB is in your path you should be able to run ADB commands from any folder.
To summarize you need to extract all the zips you downloaded under necessary files, all to the same folder. The open a command prompt and CD to that folder before you start using your adb push commands.

shortlived said:
There is a great write up here about getting adb working.
Click to expand...
Click to collapse
Yeah, steviewevie wrote it:
http://forum.xda-developers.com/showthread.php?t=865685
But it looks like he is willing to give the OP some personalized help.

Right, thanks guys, I think I'm making some progress.
ADB is all set up, and as far as I'm aware, having:
program files > android sdk > platform tools
on my path should mean I can open adb from anywhere right? I have all of the extracted files in platform tools, where adb is, in my program files... is this right, or have I completely missed the point here?
I keep getting "cannot stat 'gfree':: No such file or directory"
Sorry, I seem really stupid concerning this whole thing, but I'm sure it's something equally obvious that I'm just not seeing.

New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?

Arconaught said:
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Click to expand...
Click to collapse
Remember you are running those commands (everything in that section) from an ADB shell, not from the Windows command prompt.

Excuse my ignorance, but what exactly do you mean by that? What should I do?

problem downgrading htc desire hd for rooting

Hi I have followed this guide exactly (http://forum.xda-developers.com/showthread.php?t=905003) and when i open command prompt and navigate to the downgrade folder i get stuck on the command:
"adb shell chmod 777 /data/local/tmp/GingerBreak"
I get the following error message "adb shell chmod 777 /data/local/tmp/GingerBreak: permission denied"
I have looked around for solutions but still cant find any way to fix it, help is very much appreciated!

Usually that would only happen to me if gingerbreak was already pushed to phone. Have you tried rebooting your phone and starting over?
Sent from my HTC Desire HD using XDA Premium App

hi, yes i have restarted my phone and now i get stuck on the command:
"adb push GingerBreak /data/local/tmp"
and get the error message "cannot open 'GingerBreak' : no such file or directory'
But when I go into my downgrade folder it is definetly there...

What software version are you currently using, is it one that can actually be downgraded at this time?
If GingerBreak is transfered try running it.
adb shell
./data/local/tmp/GingerBreak
what happens then?
alternatively try this guide instead, it helped me: http://forum.xda-developers.com/showthread.php?t=1152233

Hi thanks for the reply, when i do the command "adb shell /data/local/tmp/GingerBreak" i get the message "ermission denied"
hope this helps, will look at the link you posted

also my version of software is 2.36.405.8

Yeah follow the guide given above (http://forum.xda-developers.com/showthread.php?t=1152233)
also re-download the downgrade tools. If you running windows 7 make sure you dont extract them directly to the c drive. first extract to some d drive or so and then copy paste to c drive or directly given the d drive path in the cmd.
Also make sure you are logged in as admin in the system. and run the cmd after right clicking and selecting run as administrator .
and also you are deleting the older PD98IMG zip file and doing all the cmd stuff after downloading the stock PD98IMG zip file and putting it in the sd card.
Make sure you check the md5sum of the file you downloaded so that its integrity is intact.
See if it works after all this. Do post your results.
All the best
Cheers!

abhisahara said:
Make sure you check the md5sum of the file you downloaded so that its integrity is intact.
All the best
Cheers!
Click to expand...
Click to collapse
Hi how do you do this please ?
Thank you
Stephen

sbsshadow said:
Hi how do you do this please ?
Click to expand...
Click to collapse
Total Commander can do it under Windows. Else see http://www.google.com/search?hl=en&...=Google+Search&aq=f&aqi=g10&aql=&oq=&gs_rfai=

Hi thanks for the help, when i go to extract the downgrade folder into my D drive i get the following message:
"You need permission from the computers administrator to make changes to this file"
and underneath that it has displays the GingerBreak file and its details. The downgrade folder appears in the D drive but without the GingerBreak, misc version or psneuter file.
Your help is very much appreciated!

Lanky09 said:
also my version of software is 2.36.405.8
Click to expand...
Click to collapse
http://driphter.com/index.php?topic=3867.0
Start at step 2.

bump - still need help on downgrading!

Main Version is older! Update Fail!

Hi everyone, I`m getting the "Main Version is older! Update Fail!" message and have run into a brick wall. Can anybody help? Hopefully the screen grab of the cmd has attached correctly so one of you clever people may be able to see it and know what is wrong.... I have not got a clue!

Too bad you didn't scroll down before you took the screen shot.

Agoattamer said:
Too bad you didn't scroll down before you took the screen shot.
Click to expand...
Click to collapse
That was it dude! Below Exploiting Device, it just went back to the start C:Users...ect. There was nothing else of interest.
Anybody know what went wrong?

Dazblink said:
That was it dude! Below Exploiting Device, it just went back to the start C:Users...ect. There was nothing else of interest.
Anybody know what went wrong?
Click to expand...
Click to collapse
If i remember correctly fre3vo exploits and then exits the shell.
If you use "adb shell" again, you should have root on your phone.
I followed the guide in the cyanogenmod wiki and it worked, so maybe have a look at that:
http://wiki.cyanogenmod.com/wiki/HTC_Desire_HD:_Firmware_Downgrade_(Gingerbread)
Your error sound like you didn't use misc_version.

Dlog said:
If i remember correctly fre3vo exploits and then exits the shell.
If you use "adb shell" again, you should have root on your phone.
I followed the guide in the cyanogenmod wiki and it worked, so maybe have a look at that:
http://wiki.cyanogenmod.com/wiki/HTC_Desire_HD:_Firmware_Downgrade_(Gingerbread)
Your error sound like you didn't use misc_version.
Click to expand...
Click to collapse
yeah i think that's right, i think you will exit shell after the exploit. if you type adb shell and you get a # you're root. if you get a $, try typing su then hit enter and if you get a # you're root
i followed the guide that Dlog linked to and it worked well so i would definitely do that. but i guess that's what you're doing anyway?

it is because the update package in your sdcard is older than your device running right now,
that's why after fre3vo and got root in adb shell (the # sign), you run this command
./misc_version -s 1.31.405.6 , to make your DHD think the update package is newer, and do the update from the IMG file in your sdcard
after update complete (downgrade), you can now use visionary+ to root .
BTW, what's your build number ?

Sorted it cheers! Typed in abd shell again and got the #
Thanks for the replies!