okay so im rooting my brothers g2, and im coming across alot of really odd issues ive never encountered before with rooting. i've followed all the steps for temp and perm root for this phone, but it still doesnt give me su. i have superuser on the phone from pushing it via adb, but it doesnt work. the phone in hboot says its the eng build with s-off. but again i dont get any su in cmd so i cant do anything. superuser doesnt work so i cant install clockwork via rom manage, and su doesnt work in cmd so i cant manually push the image. any idea or tips would be nice because im so lost. i have rooted several phones before and none had this issue.
twilightvanquisher said:
okay so im rooting my brothers g2, and im coming across alot of really odd issues ive never encountered before with rooting. i've followed all the steps for temp and perm root for this phone, but it still doesnt give me su. i have superuser on the phone from pushing it via adb, but it doesnt work. the phone in hboot says its the eng build with s-off. but again i dont get any su in cmd so i cant do anything. superuser doesnt work so i cant install clockwork via rom manage, and su doesnt work in cmd so i cant manually push the image. any idea or tips would be nice because im so lost. i have rooted several phones before and none had this issue.
Click to expand...
Click to collapse
Have you tried just downloading it from the Market? http://market.android.com/details?id=com.noshufou.android.su
Sent from my T-Mobile G2 using XDA App
yeah and i dont see how that makes it any different than when its put on during the root process. the problem seems to be that it doesnt wanna let me write things to the phone.i get errors like "cannot create /system/bin/su': input/output error" "unable to chmod /system/bin/su: no such file or directory" when i push the /data/local/tmp/root_psn.
just cuz this blows my mind...
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
thats how my phone reads for the gfree verify, im fully s-offed, but i cant do su from adb shell it says
su
su: not found
twilightvanquisher said:
yeah and i dont see how that makes it any different than when its put on during the root process. the problem seems to be that it doesnt wanna let me write things to the phone.i get errors like "cannot create /system/bin/su': input/output error" "unable to chmod /system/bin/su: no such file or directory" when i push the /data/local/tmp/root_psn.
Click to expand...
Click to collapse
Unless you set up a system path to adb, you need to have both su and adb in the same folder to be able to push it, sounds like what your problem is
Sent from my T-Mobile G2 using XDA App
everything is in the same folder in androidsdk. but i got it working, just in a much different fashion. since i already had eng build and s-off but no su functioning i decided to format the phone which still had superuser but i installed visionary gained temp access to root and flashed cwr from rom manager and installed cm7, and now its fully functioning as perm root and s-off.
Related
This is the 5th g2 tmobile has sent me. Been having build quality issues. Anyways, I was able to root them all without any problems. But this one is a toughie. I got s off. But the latest visionary won't temp root for me after I push wpthisOTA n the hboot.img.
Even removing visionary and resetting the phone n trying gfree n rage hasn't helped. Any advice?
I have the superuser app but no su rights at all. I discovered this cuz rom manager tells me I'm not rooted hence can't flash cwr
try using the rage method instead of visionary
tazz9690 said:
try using the rage method instead of visionary
Click to expand...
Click to collapse
I tried to rage temproot then perm. But no dice
I'm helping someone with their phone that has the same problem.
What we're going to do tomorrow is downgrade the rom using this...
http://forum.xda-developers.com/showthread.php?t=831398
then redo the root with rage.
I think the problem occurs when you use visionary to root then try rage. The person I'm helping keeps having problems after code # /data/local/tmp/root, so I'll report back tomorrow.
Don't use the eng hboot. That's not necessary any more, and is quite risky (e.g. if it goes wrong your phone will be bricked).
To get S-OFF after rooting, use this - http://forum.xda-developers.com/showthread.php?t=855764
With the rage method to get root, I believe that works 100% every time, *if* you follow the instructions very carefully and look out for error messages that indicate something has gone wrong. When rage "doesn't work", it's because the instructions haven't been followed or an error message cropped up and the user didn't notice and just carried on.
I'm going to return the phone to stock hboot and wipe it. Ill try rage next
Thnx for the help... this hexeditor crap makes me nervous lol
When I try to unroot it won't creat the darn misc file....
Any ideas what I can do? My s=off but rage method n visionary aren't woorking...
sheek360 said:
I'm going to return the phone to stock hboot and wipe it. Ill try rage next
Thnx for the help... this hexeditor crap makes me nervous lol
Click to expand...
Click to collapse
Gfree does all the hex editing for you and even backs up your origonal first! Very safe way to do it.
Sent from my HTC Vision using XDA App
ok, as soon as i run
/data/local/tmp/root
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
any ideas guys?
ddgarcia05 said:
I'm helping someone with their phone that has the same problem.
What we're going to do tomorrow is downgrade the rom using this...
http://forum.xda-developers.com/showthread.php?t=831398
then redo the root with rage.
I think the problem occurs when you use visionary to root then try rage. The person I'm helping keeps having problems after code # /data/local/tmp/root, so I'll report back tomorrow.
Click to expand...
Click to collapse
That's not an option for me.
I can't #su @all =(
sheek360 said:
ok, as soon as i run
/data/local/tmp/root
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
?
Click to expand...
Click to collapse
Did you reboot the phone after doing the temp root steps of rage ? Because that's kinda how it looks there.
You are also missing busybox, and an "adb push" for busybox is one of the steps in the temp root part of rage.
Also, when you did the "insmod" command, what error message did it come up with ? This is critical. It must come up with the error message shown in the procedure, if it comes up with a different error message then it hasn't worked.
steviewevie said:
Did you reboot the phone after doing the temp root steps of rage ? Because that's kinda how it looks there.
You are also missing busybox, and an "adb push" for busybox is one of the steps in the temp root part of rage.
Also, when you did the "insmod" command, what error message did it come up with ? This is critical. It must come up with the error message shown in the procedure, if it comes up with a different error message then it hasn't worked.
Click to expand...
Click to collapse
Came up with a diff error message....
Before rage I pushed wpthisOTA n the eng build. Then using visionary I tried to get perm root.
I think by using visionary I f'd up my chances of rooting. I assumed the root procedure didn't change. O well. Doesn't really matter. My camera is now taking pics backwords. Tmobile is swapping my g2 for another lol
So I'm trying to get into su to run gfree_verify to make sure my permaroot S-off/SIM card unlock/SuperCID was successful, but I'm getting a permission denied error.
What happens is, I type adb shell, then I type su, there's a really long delay, then it tells me Permission Denied. However, when I run the Terminal Emulator from my phone and type in the su command, I get root access just fine.
I used the "official" method that is on the HTC Vision Wiki that is located here. The only thing, however, is that my Android SDK install wasn't installed using any type of installer. I just extracted a zip file and shoved it in a random folder. I did make sure to run the Command Prompt as Administrator before issuing the adb shell command, but I'm still unable to get superuser access through the PC. Trying to use the adb root command gives me an "adbd cannot run as root in production builds" error.
Did I do something incorrectly?
adb kill-server
adb start-server
See if that works. If not, try rebooting your computer.
Sent from a Western Union telegram.
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
steviewevie said:
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
Click to expand...
Click to collapse
I rebooted the daemeon, computer, and also the phone. No dice.
The Superuser app is correctly installed. When I ran Adfree and attempted to go into SU in Terminal, I got the usual Allow Superuser access dialog. Both worked without any problems; like I said, I can get root access from the on-the-phone terminal, it's when I attempted to get root access from the adb shell command on my computer where I have problems.
No special ROMs, completely stock post-November OTA update. The only thing I flashed after permarooting was the Clockwork Recovery mod, but adb shell SU wasn't working before this. I initially used some outdated instructions (involving the use of the dd command, and the wpathis.ko or something). I read some more and learned these were out of dated, so I unrooted. I then used the instructions that are on the wiki using gfree to permroot.
gfree_verify works without any problems if I run it from the Terminal Emulator on my phone. Returns the proper values to indicate I'm SIM Unlocked, SuperCID, and S-off. I'm glad it works, but I still don't like the fact I can't use the adb shell. Typing characters on the G2 is a pain in the ass.
I still want to know why I can't enter superuser from the PC adb shell. Am I doing something incorrectly?
Thanks a lot for your help!
Try clearing data for the SuperUser app?
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
dietotherhythm said:
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
Click to expand...
Click to collapse
This worked perfectly! When I entered su from the command prompt, the SuperUser app popped up on the phone's side and I hit allow. It then let me through.
What exactly was broken though? Why did mounting everything from the Clockwork Recovery menu fix this?
I can't find a solution to this from searching the forums so i'm just gonna ask.
I'm using the gfree method via adb. i'm getting all the way through it without any problems untill i get to the "lock in" root section.
I get the error message that the wiki says should get and then ignore, but i also get another message that says something like
"cp: can't stat '/sdcard/su' : no such file or directory"
any help with this would be appreciated.
also, are all the bad things i've heard about visionary true? should i go ahead and root with visionary, or keep trying this way? thanks
I just checked and it says I'm s-off. I'm very confused.
Sent from my T-Mobile G2 using XDA App
Well first ill tell u Visionary worked for me in like 10 minutes time. Very easy n very fast. Not true what they say. If u got s-off, good. Ur almost there. Have to check out gfree method quik in order to help u. Hold up
G2 with ExtraHotSauce v0.2!!
What guide are you using, the one on the Wiki doesn't have you copy (cp) anything.
is this the command where you run into the problem?
/data/local/tmp/root
Click to expand...
Click to collapse
This is running a script to lock in root, you already ran gfree while you were temp rooted so that's why you are S-OFF.
Do you have the "su" file on the root of your SD card?
You should be able to retry everything but the gfree part.
As for Visionary, some people report success but other have reported big problems. I found the gfree method to work pretty well, even though I used Visionary when I was temp-rooting (when I just got my phone) when I permarooted I used the gfree method.
raitchison said:
What guide are you using, the one on the Wiki doesn't have you copy (cp) anything.
is this the command where you run into the problem?
This is running a script to lock in root, you already ran gfree while you were temp rooted so that's why you are S-OFF.
Do you have the "su" file on the root of your SD card?
You should be able to retry everything but the gfree part.
As for Visionary, some people report success but other have reported big problems. I found the gfree method to work pretty well, even though I used Visionary when I was temp-rooting (when I just got my phone) when I permarooted I used the gfree method.
Click to expand...
Click to collapse
yes, that is the command that is giving me problems. i checked my sd card and superuser.apk is at the root of it.
when you say retry everything what exactly would i retry? i'm at work, and don't have access to adb. do i need adb to "retry"
so, there are two different guides that perm root. the first is the wiki and this is the one that i was following. the other has almost the exact same steps except it has the wpthis file. i guess when i get home i'll try the other method and see if it works. thanks for everone's help
no its a 2 step procedure maybe you should go ahead and unroot and s-on then go ahead and re root. if not you can still re run everything start off with temp root then go ahead and lock in the perma root
thenaut said:
yes, that is the command that is giving me problems. i checked my sd card and superuser.apk is at the root of it.
when you say retry everything what exactly would i retry? i'm at work, and don't have access to adb. do i need adb to "retry"
Click to expand...
Click to collapse
You should have both Superuser.apk and su on the root of your SD card. Either push it from your computer again (first command in the wiki):
Code:
adb push su /sdcard/su
Or just copy it to your SD card (be sure to unmount the card when done). Then re-run the root script in terminal.
that totally did it. I pushed the su file and re ran the script and i got root. it's wierd because i thought i pushed it the first time but i guess not. anyway, thanks
Hey! So I got my G2 from a member on here last night (woohoo!) but I can't seem to root it. I tried every method on here including visionary and gfree. I had some success with gfree since I was able to sim unlock it. When in bootloader I get 's-off' on the first line. But when I go into Rom Manager it tells me I'm not rooted and when I type 'su' into terminal I get 'suermission denied'. Any help here? I really need to flash a new ROM due to ORD.
And just some info from System Info in the boot loader even though I think it's not needed here.
OS ver.-1.22.531.8
eMMC- unknown 2151MB 4407295sectors
Also under IMAGE CRC
hboot: 0x6570c0db
boot: 0x1b87420d
recovery: 0xd4af6ad9
system 0x9f52fea6
Any Update???
OK so you were able to get S-OFF via gfree but not permanent root, when you followed the gfree method, the last step (before the verify) of the gfree rooting guide on the wiki (not sure if that's the one you used) has you run a command to "lock in" root:
You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:
Code:
# /data/local/tmp/root
# sync
Click to expand...
Click to collapse
I suspect this is where it went wrong.
You should be able to use the same method again to get perm root, just skip the gfree parts. Summary:
1. Get all the files on your phone (they are probably already there)
2. Get temp root using rage
3. Run the command (script) that I listed above
Link to the full instructions: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#How_To_Get_R.2FW_Access_.28Permanent_Root_.2F_.22Permaroot.22.29
I tried the wiki method three times, making sure I typed everything correctly. After I type the line you put up I get a series on lines that show that some files can't be shown (I dont remember the exact ones off the top of my head, I'll redo it soon so I can tell you which ones). I also tried it with two different SD cards.
SO I found the errors in another thread started today:
Code:
/data/local/tmp/root
mkdir failed for /system/xbin, File exists
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
Strange, /data/local/tmp/root is just a script that does all of the stuff to get you permanent root, not sure why it shouldn't be working for you.
I think once you are temp rooted you should be able to install CWM recovery and use that to install a new (pre-rooted) ROM. If you are not ready to or don't want to jump into a custom ROM you can load the stock pre-rooted ROM and should not even have to wipe (would advise a nandroid backup of course)
http://forum.xda-developers.com/showthread.php?t=836042
raitchison said:
Strange, /data/local/tmp/root is just a script that does all of the stuff to get you permanent root, not sure why it shouldn't be working for you.
I think once you are temp rooted you should be able to install CWM recovery and use that to install a new (pre-rooted) ROM. If you are not ready to or don't want to jump into a custom ROM you can load the stock pre-rooted ROM and should not even have to wipe (would advise a nandroid backup of course)
http://forum.xda-developers.com/showthread.php?t=836042
Click to expand...
Click to collapse
I should try temprooting again and flashing CWM. And The only reason I want to root is to flash custom roms. lol.
EDIT: Well that didn't help. I followed the guide for temproot. I did get the root prompt (#) in terminal, but when testing with 'su' gives me 'su:not found'. And CWM still tells me I'm not rooted and wont let me flash the recovery.
Try using visionary to temp root, that may yield more success.
You may want to use ADB to pull out the remnants from your previous attempts.
If you have # in the terminal you should not need to su.
If you can't flash CWM using ROM manager try this method instead http://forum.xda-developers.com/showthread.php?t=902493
With visionary I push temp root, it makes me wait for like 10 minutes, and does nothing. I was just doing su to see what it does. I'll try removing everything with adb and redownloading all the files. Anyway, what's the command to remove with adb? lol
Open an ADB shell and use the rm command to remove individual files, I would remove everything you ADB pushed originally.
Code:
rm /sdcard/su
rm /sdcard/Superuser.apk
rm /data/local/tmp/rage
rm /data/local/tmp/busybox
rm /data/local/tmp/root
Will only run if you have root access (a # prompt) and you may get errors with some since clearly something isn't as it should be on your system.
Did you try using the flash_image utility to flash CWM?
Also if you can flash the engineering hboot you should be able to load CWM from fastboot.
So I removed the files, redownloaded, and redid the wiki root method.
Still no luck. Same error as posted before. This is getting on my nerves. lol
Did you try to install recovery using this method?
If that didn't work did you try to install the engineering HBOOT?
raitchison said:
Did you try to install recovery using this method?
If that didn't work did you try to install the engineering HBOOT?
Click to expand...
Click to collapse
I will attempt these methods soon and report back.
I am having a terrible time trying to root my HTC Desire Z. The phone is running 2.2 (Not 2.2.1!) and I'm just wanting to rip my hair out.
First crack I tried was using Visionary and rage, which quickly failed after flashing hboot, running /data/local/tmp/root etc and rebooting it would be
su: permission denied
Second time around I tried rage + gfree which has seemingly got me into a bigger mess, when I try run su now it comes up with "su: unknown user root", and whoami returns "whoami: unkown uid 10096"
The last thing I could remember seeing error wise is I think the root binary said "couldn't stat /sdcard/su and couldn't stat /sdcard/Superuser.apk"
I mean, I've already got Superuser.apk installed, but everytime (this goes right back to the start of my problems) I can't adb push anything to /sdcard/, So I just placed them in the root of my sd card when I mounted it.
And yeah. I've got a really f**ked up phone right now I suppose.
Please help me.
EDIT: Fixed. Put the mode into HTC Sync rather then Disk mode! everything worked flawlessly from then on!
Hi,
I have the same issue. "su: unknown user root" . Did you resolve it ?
Thanks