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
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
Having a few issues getting the temp root part to work in this guide
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
I am following the steps and have copied everything over to the phone but when I run rage on the phone itself I get permission denied over and over, read most the search results I could but have not found anything.
ionic7 said:
Having a few issues getting the temp root part to work in this guide
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
I am following the steps and have copied everything over to the phone but when I run rage on the phone itself I get permission denied over and over, read most the search results I could but have not found anything.
Click to expand...
Click to collapse
You mean you get something like "rage : permission denied" ? Or something else ?
Did the "chmod 0755 /data/local/tmp/*" work ok, i.e. return no error message ?
as far as i know it did work properly it did not show any errors or confromations just went to a new line of adb, and the phone says /data/local/tmp/rage : permission denied.
FIXED, it was my fault i missed a / in the chmod command the one seperating tmp and *, redid it with that and boom it went.
think I got perm root going to leave it be or play with the miui now
Hi all,
I have had my htc desire z for about two weeks now, But since i have had my phone i've been having a few problems.
I had rooted my phone using visionary +. And all was going well untill i was trying to install setcpu to overclock my cpu. After installation my phone rebooted and now every thing that i need root access for is showing up as not accessable.
Busybox installer error message:
Your phone is roote
Busybox not found
The application failed, either because your device is not nand unlocked or we were unable to remount.
Rom manager error message:
An error occured while attempting to run priviledged commands!
Is it possible(if yes, how) to unroot and flash my desire back to stock settings including the permissions back to stock.
If not how can i root my phone so i can use all of the fuctions
Regarding the phone info the spaces are actually . but the system will not allow me to enter these as of yet
Thanks in advance
All the best
Gaz
I forgot to mension in the last post that i have expiriance with mobile phone's and flashing so i'm not affraid to tackle big complicated ways of undoing the process.
It sounds like maybe you only had temp root.
Did you also do gfree? I did Visionary and gfree, and perm rooted just fine.
However, many on here believe the rage + gfree method is safer, as Visionary has been known to create some semi-bricks. I don't THINK there is any harm in doing rage + gfree at this point, but others on here can probably enlighten.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I tried using root checker to find the issue. It came back with an error message telling me the SU binary was not found in the correct path. I used terminal emulator to try to locate the file but with no success. Any ideas on how to find and move the binary su???
What's displayed on your screen after reboot in recovery?
As in; remove battery, insert battery, hold volume down and power button.
It will not reboot in to root. It runs Visionary and nothing happens.
And when i try to open an app that need root access it fails because it cannot gain permission from superuser. At this point i have tried to unistall all apps that had anything to do with rooting my phone but still no succes. I need to find the stock SU Binary
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.
Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...
I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
skyraven83 said:
Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...
Click to expand...
Click to collapse
it seems in the end that it was all in xprivacy problem....
solved and now it is functional
skyraven83 said:
I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
Click to expand...
Click to collapse
Just so you know
The reason you probably did not get responses to this is because you posted it in Galaxy Nexus section and not Nexus 4 forums