I have a DHD recently. it's repaired from HTC factory.
Backgroud:
In order to break it, I've upgrated it from 2.36 to SoftBank_JP 2.37. and rooted with gingerbreak already.
I connect to the mobile under "adb shell" and got the "#".
the system was remounted with RW.
Boot was remounted with RW.
sdcard was writable.
I tried to set the version with the tool "misc_version -s 1.31.707.1" it displayed successful. but failed in the bootloader with " the mail version is older".
so I tried to rewrite the partition misc (/dev/block/mmcblk0p17), but no luck.
I remount the system with RW, push Superuser.apk, busybox, su in sysytem, granted with proper permission. but they will missed after the mobile reboot.
So I need a special help me to unlock the partition. since the phone now is ship s-on rl. I think if we have a way just like "insmod wpthis.kp" I think that will be much easier.
look forward a super expert can help me this. I am a ROMer in the Chinese too,
I wrote lots of guide to root DHD, no matter its version is 1.32 or 1.78 or 1.84 even 2.36 and 2.37, I write the guide too. But this time is really hard to me. it's beyond my capability. need help!!! greatly help...
What I need finally? I need to downgrade to 1.32 or s-off the mobile directly.
still no one can helps. why....
So you want to root your dhd? No one replied probably due to various guides on here.
Downgrade to 1.32 then use visionary + tool.
Sent from my HTC Desire HD using xda premium
Related
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
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
i have been reading up on getting s-off on so many threads. My situation is that i have had perm root since visionary r14 has been launched but i still do not have s-off. what do i need to do to get this done since im already perm rooted. i am missing out on all the roms and overclocking. i just want to take my phone to the next level. i have a desire z thats rooted but no s-off. realy appreciate this if anyone can point in the right direction.
you need android sdk from here
http://developer.android.com/sdk/index.html
read this to learn how to use adb shell
http://forum.xda-developers.com/showthread.php?t=865685
then follow this, basically you need to gain super user access by temp rooting with visionairy (thats what i did) then push the files to the destinations given in the link below, then you just follow the rest and youll be fully unlocked, rooted and s-off'ed lol
http://forum.xda-developers.com/showthread.php?t=843014
if you get stuck report back but if you read up on adb you should be fine look at the stickies thread for more info, hope this helps thank me if it did!
Thanks very much I'm going to start reading up on adb. One quick queation. You mentioned that I will have to perform another temp root, does it matter that I am already perm rooted.? Do I have to unroot first using visionary one click unroot?
Sent from my HTC Vision using XDA App
No need to temproot. Just follow the instructions in the Wiki: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Unlock_the_Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF.
You don't need ADB either. You can do everything in Terminal on your phone (though instead of pushing the file with ADB as instructed in the Wiki, you can stick the file on your SD card and then copy it to the correct location).
Wicked Thanks so much illgive it a go. I'll message back to let you know it worked. Thanks again.
Sent from my HTC Vision using XDA App
yeah its probabally easier doing it ianmcquinn's way matey
but it wont hurt to learn adb if your into that sort of thing its quite fun!
anyway if ya get stuch just post back, someone will be here to help
Good Luck!
remember when you have s-off, get rom manager from the market and get the premium one cus its always nice to donate
then download clockwork mod from rom manager ! you can perform nandroid backups and all sorts of coool stuff!
hi ianmcquinn you mentioned to stick the gfree file in my sd card and then copying it to the location. im not sure in which location your talking about. i tried using the commands thru the phones terminal but when i type chmod 777 gfree it tells me "unable to chmod gfree no such file directory".? do i have to make a folder chmod gfree and stick the files in there ?
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
thanks for your time everyone. i really feel that im close and im just missing a step.
just setup adb and i got s-off :0
thanks very much for posting these threads now its time to play with my desire z. overclocking here we come and some new roms
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.
I have a rooted G2 with ENG S-OFF and when I log into shell via "adb shell", it starts as user ($) as opposed to root user (#). Once I'm running in adb shell, su won't work until phone is fully booted and permission is granted from superuser app. This seems like I don't have eng boot and/or S-OFF, but I do according to HBOOT and gfree_verify.
I did perm root a while back and I think S-OFF at the same time, and then later on I used gfree to do the other options (sim unlock and super CID). Doing some searching I came accross the command getprop ro.secure ... if I run this from adb shell as user ($), it returns 1, as (#), it returns 1, and from terminal on phone as root (#) it also returns 1. From my light understanding, this should be 0.
Does anyone have any thoughts as to what is going on? A potential fix is to redo everything with gfree (?) ... not sure what else to try. Any help/advice would be appreciated. Thanks much.
Are you running a custom rom.... because I know the stock rom doesn't stick root very good....
I am running stock rom...sorry I forgot to mention that. Since root doesn't stick well with stock, does that mean I should try process again? Thanks.
It seems that what I described as my problem is actually expected behavior since I am running stock rom. The ro.secure flag located in the default.prop file at / is typically 1 for stock roms where as if someone were to customize a rom, they would set that flag to 0 most likely. Changing it from the OS won't do anything since it gets loaded from the boot.img image at startup. One could extract boot.img, modify, and re-flash, but I'm OK with it for now.
I wanted to give an update on my findings in case anyone else was curious about this. I had recently rooted a Thunderbolt and as a result of that method, ro.secure = 0, so I was confusing myself as to why it was 1 on my G2...but now I know.
Thanks needs to go to Guhl over at #G2Root on Freenode for helping explain this to me.