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
Related
Sorry for making you read this if I made a nooby mistake.
So I rooted my Slide, and flashed the Eng-release to it. When I use ROM Manager to install the CM6 onto it, I can't get past touching reboot into Clockwork Recovery. I already flashed the Clowckwork into it (I think; you just need to push the Flash ClockworkMod Recovery button right?), but when I push the reboot into it button, nothing happens.
I tried the Fix Permissions button, and it says "An error occurred while attempting to run privileged commands!" That means that the app doesn't have root access, right? How do I give the app root access? I tried two superuser apps, one from the Market and one from this website, the one with a Ninja. When I choose preferences on the superuser app, it just hangs until I get the Force Close error.
How do I grant my app root access? I know I rooted my Slide because when I connect it to my phone and use adb shell, the pound sing comes up.
What method did you use? Did the phone have the 1.35 OTA Update?
Try this: download terminal emulator from the market, its free.
Turn on: you will see a "$" symbol type "su" (w/o qoutes)
if you see this "#" you are rooted..
Im sure there are easier other ways to check, thats just what I do. I know you didn't install the rom, so don't worry about that yet.
Chances are you arent rooted, I dont what adb shell would say, since I didnt have to use it directly, I just used my windows cmd prompt.
After looking at the other post a few below this one about the exact same problem that I had, I did what he did and copied the update.zip to my phone and booted into recovery. Thanks for the help, though I'm ok now.
Btw, I did have the terminal, and it did have the # sing
Sent from my T-Mobile myTouch 3G Slide using XDA App
I know this might sound stupid, but I've never done this with a Z before and I'm a bit scared about bricking my new phone, so...
Got my Z about a week ago, used Visionary+ (yeah, I know, boo) to temproot and restore my apps with TitaniumBackup. Unrooted with the button in the app and haven't used Visionary since. Until last night, when I wanted to take some screenshots using drocap2. Temproot failed at first, so I rebooted and tried again. This time it worked and when I was done I used Unroot again.
Only this time after rebooting my weather info was gone. Readded the clock, that didn't fix it. The weather app just said "Current City" - it wasn't showing any weather info.
I figured that's not biggie, but I found another bug which is: if I power the phone off and then back on while "Fast Boot" is on I lose access to my phone app and contacts (both show a black screen) until I do a full reboot.
So now I decided to reinstall everything and start afresh (this time I'm using rage to root ).
Right now I'm running everything stock (ROM, recovery, SPL are untouched). If I have one of the CIDs contained in the android-info.txt inside the official 1.34.405.5 RUU (HTC__032), is it okay to just run the RUU? Or should I stick to a hard reset from fastboot or recovery?
Thanks!
Try hard resetting first, this will erase all data in your phone, and if that is not working go in your device to settings>aboutphone>Softwareinformation and check there if your build number is:
1.34.405.5
if it is then let me know and I can give you a PC10IMG.zip (I have done this method before), and simply you will copy the zip to your sd card, turn on the phone into bootloader, and the phone will do the rest.
Or simply flash one of those exe RUU jsut be sure is the same build number.
My build is 1.34.405.5. The RUU I have is RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
Isn't the PC10IMG.zip a renamed rom.zip from inside the RUU?
keinengel said:
Isn't the PC10IMG.zip a renamed rom.zip from inside the RUU?
Click to expand...
Click to collapse
Yes, it is.
Both methods i.e. zip or ruu will do what you are asking for so is up to you to choose one.
I rather the zip one, since to me the ruu kind of did not work, and then I needed to install htc syn and stuff (I am a mac user, no needs for drives just as linux )
Anyhow hope I helped
Okay, I'll transfer the rom.zip to my SD card and rename it, thanks!
Which reminds me, I used Visionary because rage only seemed to be giving me shell root. TitaniumBackup couldn't seem to get root rights. I followed the steps, I'm very well accustomed to adb and fastboot commands and also shell commands, but couldn't get it up and running. I'll try again after restoring my phone.
keinengel said:
Which reminds me, I used Visionary because rage only seemed to be giving me shell root. TitaniumBackup couldn't seem to get root rights. I followed the steps, I'm very well accustomed to adb and fastboot commands and also shell commands, but couldn't get it up and running. I'll try again after restoring my phone.
Click to expand...
Click to collapse
If you had permanent root in the shell (i.e. could successfully do an "su" after a reboot"), then you had permanent root alright. If there was a problem with another app getting root rights, then it may have been something to do with the Superuser app, because that pops up and asks for permission the first time an app asks to run as root.
keinengel said:
Okay, I'll transfer the rom.zip to my SD card and rename it, thanks!
Which reminds me, I used Visionary because rage only seemed to be giving me shell root. TitaniumBackup couldn't seem to get root rights. I followed the steps, I'm very well accustomed to adb and fastboot commands and also shell commands, but couldn't get it up and running. I'll try again after restoring my phone.
Click to expand...
Click to collapse
you should not rename the zip file, unless it has other name, but it should be called PC10IMG.zip
steviewevie said:
If you had permanent root in the shell (i.e. could successfully do an "su" after a reboot"), then you had permanent root alright. If there was a problem with another app getting root rights, then it may have been something to do with the Superuser app, because that pops up and asks for permission the first time an app asks to run as root.
Click to expand...
Click to collapse
I never got permanent root, because I didn't want it. I did all the rooting, flashing radios/spls/recoveries and custom ROMs I'd ever need with my trusty old Magic. Now I'm trying to stay clean
I just needed temproot for TitaniumBackup and drocap2 - that's it. Don't need supercid, s-off or anything else - and that's what made Visionary so attractive. Too bad it's hit-and-miss.
My problem with rage was that I had root access from the terminal, but couldn't run those two apps without permanently rooting. Besides, I'm not quite sure how to unroot, should I ever need to. Would flashing the stock PC10IMG.zip from fastboot be enough? I see it overwrites most partitions, but would it also overwrite the radio config one?
keinengel said:
I never got permanent root, because I didn't want it. I did all the rooting, flashing radios/spls/recoveries and custom ROMs I'd ever need with my trusty old Magic. Now I'm trying to stay clean
I just needed temproot for TitaniumBackup and drocap2 - that's it. Don't need supercid, s-off or anything else - and that's what made Visionary so attractive. Too bad it's hit-and-miss.
My problem with rage was that I had root access from the terminal, but couldn't run those two apps without permanently rooting. Besides, I'm not quite sure how to unroot, should I ever need to. Would flashing the stock PC10IMG.zip from fastboot be enough? I see it overwrites most partitions, but would it also overwrite the radio config one?
Click to expand...
Click to collapse
Jut put the PC10IMG.zip in the root of your sd card. Then turn completly off the phone, and turn it on into bootloader (down key volume + power button), and the device shall recognize the zip.
I attempted to root my friend's G2 first using Visionary+ R14 and temp root would work (the SU.apk is in the app drawer), so I attempted the perma-root and as soon as I granted it root access it would immediately reboot. Once I rebooted SU was still in the app drawer but rom manager kept saying the SU apk wasnt found in /system/bin or /system/xbin. I looked for it manually and searched for it but it couldnt be found anywhere, yet it was in the app drawer after a reboot.
I tried it a few more times and couldnt get it to work, I booted into the bootloader and saw that S-on wasn't off. After feeling competent enough I decided to push the hboot.img and the wpthis-OTA.ko to the sdcard (since I didnt have adb handy) and then copied them both to /data/local via the terminal. When I tried to insert the kernel module it gave me the expected error so I proceeded to flash the new hboot and that was also successful. I ran visionary again (guide doesnt say temp or permanent method, so i did temp), and once it was finished I typed sync into the terminal, waited a minute and rebooted.
Once android was fully loaded up again, I loaded up rom manager and it still complained that it couldnt find su.apk, I searched for it and it still wasnt there, yet it was still in the app drawer. I rebooted into the bootloader and saw that the protection was finally S-OFF, yet root access didnt seem to be (fully) available.
It also mentioned at some point that my su.apk was out of date and it downloaded the most up to date one for me but I had no way to flash it.
Whats wrong here?
This should either be in an existing thread about the rooting methods you're talking about, or in one of the other forums, such as Q&A
Hi, I've got a Motorola Defy in Argentina (Carrier: Personal, means telecom). Well, I want to Root it, I've tryied z4mod, the ADB Method, 1 click, etc, and I still got the message "The application xxxx needs root user permissions", btw I have the Root (#) console in "adb shell", but I can't move files to /system/media (whit "AndExplorer" from mobile). Do I have to mount the FS there??
I've got the "Superuser" app working, and some applications whit "Root permissions" (because I've checked Remember my answer on the Popup when the app needs root privilegies)
Im a little bit confused because the version is not similar that you use here.
Version Number: JORLA_U3_6.14.7
Firmware version: 2.1-update1
So, I want to root it, and maybe upgrade to Froyo, but that questions make me scared (specially if i brick it).
What should I do?
PS: I've made a "Backup" with SystemRecovery app. This backup will work if I want to back my firmware to the stock one? (forgive the apps, I don't care).
Nobody can guarantee your backup will work, but it's a risk you'll have to take if you want to hack.
According to my search, your carrier uses UMTS 850 / 1900. This means you could have a different baseband firmware than the T-Mobile users here, and definitely different from the European users. The problem is, the only SBF files available are for European 900/2100.
So first things first, take a nandroid backup from the custom bootstrap recovery if you can get that working. Back up those files somewhere safe.
Read about the "3g fix". There is a folder containing the baseband firmware files, and you'll want to back those up in case you lose 3g on a custom ROM.
If your phone becomes unbootable, you'll have to flash an SBF to boot it, *then* root it again, install custom recovery again, and finally restore the nandroid backup.
Sent from my Nexus One using XDA App
Ok, thanks for the info. I've tryied to do a "nandroid backup" with the upgrade.zip stuff, but it just restarts and do nothing. I can't see any changes on my SDcard.
BTW, how I can run a .apk as root? (I want the AndExplorer to be root so I can copy some stuff to /system). I've got actually a root (#) terminal in adb shell and in Terminal emulator (via command su).
Thanks
cocus said:
Ok, thanks for the info. I've tryied to do a "nandroid backup" with the upgrade.zip stuff, but it just restarts and do nothing. I can't see any changes on my SDcard.
BTW, how I can run a .apk as root? (I want the AndExplorer to be root so I can copy some stuff to /system). I've got actually a root (#) terminal in adb shell and in Terminal emulator (via command su).
Thanks
Click to expand...
Click to collapse
How are you attempting to do this backup?
You need to download the bootstrap custom recovery, and use that to boot into the recovery menu. From there you go into backup/restore.
If you have successfully rooted your phone, then all apps have the opportunity to run as root. They should be able to make the request via Superuser Permissions, which would then prompt you.
Ok, but the bootstrap custom recovery is for 2.51 or similar firmware numbers, I've got 6.14. So, I really didn't test because I don't have experience with this things and I don't want to screw up all.
I tell you, for example, the Terminal Emulator runs on root when I run "su": Android requested Superuser permissions to me, and I ticked remember option, and now I can run "su" without the Superuser request.
BTW, I've got a root shell on adb (when I reboot the phone, I loose the root ). That means that is rooted??? (Got it using RATC)
Well, either it's compatible or it's not. If the bootstrap makes your phone unbootable... I guess you'll have to try for a warranty claim
Sent from my Nexus One using XDA App
Hahaha, I like to flash things and understand how it works, but in this case, I would prefer not screw nothing. Btw, I've buyed it on 15/jan.
So, for my other question the Terminal Emulator runs on root when I run "su": Android requested Superuser permissions to me, and I ticked remember option, and now I can run "su" without the Superuser request.
But when I restart the phone, I loose the # on "adb shell".
BTW, I've found the open source code of an earlier version of my defy on
opensource.motorola.com/sf/go/projects.moto_defy/frs.defy_latam
Anyone knowns how to compile this? I've got Debian lenny, Ubuntu 10.04, Ubuntu 10.10.
Thanks
Compiling a ROM yourself won't help if you can't sign it with Motorola's key. Yay locked bootloader...
Sent from my Nexus One using XDA App
Cocus,
I got the same phone as yours. Also from Personal.
And I am on the same situation, want to flash it, but not to brick it.
Let me know if you find out something ...
Hi, yes you can contact me via PM & I will send all the stuff that I've got. But I only get the rootshell via RageAgainstTheCage. When you reboot it you loose it, but you can use "su" or "rootshell" to get it again.
Now Im playing with C and C++ native code, with the ndk and sdk (no java ). Contact me
z4root worked in argentine (Latin American) defy.
Hi
I have a Motorola Defy like yours , (in Argentina - Carrier: Personal ).
I have rooted successfully using z4root 1.3.0 , that you can get from this post (look attached file at end ):
http://forum.xda-developers.com/showthread.php?t=833953
With z4root 1.3 you have the option of get root temporarily or permanent. The first one doesn't works for me ( no errors but no root ). The permanent root yes, works like a charm .
Hi, It seems that is not working for me... I've touched the permanent option, it restarted and the z4root says that is rooted, but I haven't the root console in adb shell, neither the apps run as root.
Edit: If I try to run "su" on the non-root console($) it says "Permission denied". But, running "rootshell" from RATC, it gives me a root shell.
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