yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] gvink:
hi, just used the terminal emulator on my Desire HD to try to get the S-off etc. I got the SU root through Visionary's app. GReat work by the way!

Inside the terminal I entered the first two commands and it gave me the notion that "This means it has worked and you can now continue"

Whilst trying to enter the next command I got the popup the the android.process.acore (if I'm correct) process had stopped and that I had to push the 'close now' button. This kept on popping up while I tried to type in the next command.. (same as above post)

I couldn't get it in so I tried to exit the emulator to start over again. Before I knew it it entered into a reboot (I only pressed the home button) and now it's continuously rebooting...

I read all the comments before starting out and saw the notice about not turning the phone off, so I didn't.. :)

Can someone help me out? I need this phone.. :)

Thanks in advance for any help! I hope I didn't brick it..?

UPDATE: Took the battery out, put it back in, rebooted and it now runs okay. it rerooted (Visionary) will try again one more time and post back later..
[Desire HD Android Development] noxiuz:
I got the same type of errors. After a while the errors didnt pop up anymore and i quited the terminal. Nothing happened since then, i will try another method of S-OFF, maybe i try easy S-OFF it! again.
[Desire HD Android Development] htc_mi5:
Hi all,

I am not sure if this has been asked before, I have looked through this thread and tried the search option to no avail. I have just received my new DHD and am looking at rooting it and S-OFF to allow a custom recovery image to be loaded, BUT it is already on Build Version 1.75.110.2 CL301245 release-keys and has a t-mobile boot screen (but no other obvious t-mobile branding). The Kernel Version is: 2.6.32.21-g1e30168

Can anybody tell me if it is possible to use visionary+ to root and this method to S-OFF this version of the handset please?, or do I have to downgrade to a 1.3x rom (possibly having to use a goldcard?) to get this to work?

Thanks in advance.
[Desire HD Android Development] kia1349:
hi

if my phone branded , can i root it , or first i must debranded it?
[Desire HD Android Development] Xene55:
Sorry, just to confirm, does this include radio s-off?
[Desire HD Android Development] jkoljo:
Nope, it does not.
[Desire HD Android Development] bratboo:
Is this going to work if I use it on Desire Z? I can't find an easy S-Off on Desire Z forum >.>
[Desire HD Android Development] Denil Wong:
Can it do for 2.3.2?
[Desire HD Android Development] Moffasin:
Just tried this on a co-workers phone, after running Visionary+ R14 and everything went fine except for the HBOOT,

The first and second md5 match, but the third does not I guess this is okay?

:D
[Desire HD Android Development] adrianyujs:
can I use this to S-OFF desire HD running 2.37 software?

mine currently OTA 2.3 gingerbread with S-ON...
[Desire HD Android Development] Sybregunne:
Sadly no. Waiting for the devs here on this topic.
[Desire HD Android Development] sfjuocekr:
Thats strange, can you try the following and report back please:

su

find / |grep md5sum

And what happens if you type just md5sum at the command prompt?
[Desire HD Android Development] Bobblot:
Ok I've tried that and this what it comes up with...
[Desire HD Android Development] sfjuocekr:
Hurr, that shouldn't happen at all :s

Try this, in Android Terminal Emulator press the menu button, goto preferences, then hit initial command and remove whatever is there. Then close the terminal with back button, open it again and try md5sum again (just the bare command).

Or try

/system/bin/md5sum

/system/bin/md5sum

/system/xbin/md5sum

Does any of those work? Might just be a path problem on your ROM.
[Desire HD Android Development] bginders:
Hi, can anyone tell me if the below is correct/succesful as it is showing md5sum: can't open

"954ee123699488613c5e0afd2d703c43 /sdcard/DHD/hboot_check.nb0

df4fd77f44993eb05a4732210d2eddc6
[Desire HD Android Development] Bobblot:
Nope, none of them are found?
[Desire HD Android Development] sfjuocekr:
Is this after running the hboot script? If so something went wrong, don't reboot just yet!
[Desire HD Android Development] sfjuocekr:
Do you have the Android SDK at hand? If not download it and open a shell by invoking in the tools directory:

adb shell

Then su again and try to invoke md5sum again.
[Desire HD Android Development] bginders:
Yes this is after running hboot what do you suggest should i try the recover

Sent from my Desire HD
[Desire HD Android Development] sfjuocekr:
Can you do the following please:

su

cd /sdcard/DHD

ls

Does it show:

hboot_check.nb0

hboot_orig.bin

MD5sums_orig.txt
[Desire HD Android Development] Bobblot:
Not at hand at the moment. Tomorrow ill you know what happens when back at the computer.

Thanks for the help so far though.
[Desire HD Android Development] AndyCr15:
Sorry to throw another problem in while you're still helping someone else, but...

I have used VISIONary+ (r13) to apparently get permroot. When I restart, apps are allowed root access no problem.

I run the first two scripts, everything seems great, which I do sh /sdcard/DHD/hboot the very first line says -

insmod: init_module 'data/local/wpthis-blah blah.ko' failed (function not implemented)

later I notice it also says -

md5sum: can't open 'sdcard/DHD/hboot_orig.bin': No such file or directory

I'm thinking I've still not got proper write access? If so, why doesn't VISIONary+ not work for me :(
[Desire HD Android Development] bginders:
right done that and it shows "hboot_eng.nb0

hboot

backup

check

RTFM.txt

restore

hboot_orig0.bin

hboot_orig1.bin

recovery_orig0.bin

recovery_orig1.bin

hboot_check.nb0
[Desire HD Android Development] sfjuocekr:
Well the module worked atleast, thats good.

But I just noticed a fail I had over looked from old files :s

Let me fix this asap, dont reboot Ill upload a new archive with a proper hboot script as it is checking for a number that isnt there...

Just hold on please!
[Desire HD Android Development] sfjuocekr:
@AndyCr15 and bginders:

Please download the file and extract it into the DHD directory overwrite the two files (hboot and restore).

Now run it again:

su

sh /sdcard/DHD/hboot

It shouldnt throw up file not found anymore.
[Desire HD Android Development] afrcom15:
So if I am seeing this:

sh /sdcard/DHD/check#

df4fd77f44993eb05a4732210d2eddc6 /sdcard/DHD/hboot_eng.nb0

df4fd77f44993eb05a4732210d2eddc6

Then I reboot?

I've not tried this yet, after my recent experience I want to absolutely crystal clear on what I'm supposed to be seeing
[Desire HD Android Development] bginders:
Sent from my Desire HD

it now shows the below is this correct

"#sh /sdcard/DHD/hboot

insmod: can't open '/data/local/wpthis-lovinglymadeforyoubymodaco.ko'

2048+0 records in

2048+0 records out

1048576 bytes transferred in 0.328 secs (3196878 bytes/sec)

2048+0 records in

2048+0 records out

1048576 bytes transferred in 0.110 secs (9532509 bytes/sec)

954ee123699488613c5e0afd2d703c43 /sdcard/DHD/hboot_check.nb0

df4fd77f44993eb05a4732210d2eddc6 << correct MD5

954ee123699488613c5e0afd2d703c43 /sdcard/DHD/hboot_orig0.bin
[Desire HD Android Development] sfjuocekr:
No it should have told you that if both MD5 sums match you should continue with:

sh /sdcard/DHD/backup

Please make sure you download v0.2 or the new.zip (if you have v0.1) in my previous post and replace hboot and restore with the new files.
[Desire HD Android Development] sfjuocekr:
Your module failed to load, so there has no writing been done to HBOOT.

You can double check this by opening MD5sums_orig.txt inside DHD it should show 954ee123699488613c5e0afd2d703c43 as being your original HBOOT so no harm has been done.

/edit: From your previous post 954ee123699488613c5e0afd2d703c43 /sdcard/DHD/hboot_check.nb0

What version of Visionairy+ did you use to permroot?

Can you do the following in a console:

su

ls /data/local/*.ko

And report back please.
[Desire HD Android Development] oldskool73:
I'm getting the same as the others,

* first off you've changed the backup names in the backup script but forgotten to change them in the actual hboot script, I guess this is what the new zip you just uploaded fixes? This is why you get the file not found md5 error.

* More importantly, I'm getting :

insmod: init_module '/data/local/wpthis-lovinglymadeforyoubymodaco.ko' failed (Exec format error)

...and the hboot_check matches the hboot_orig so it appears not to have been written

(I used Visionary+, v12, straight off the modaco site about half an hour ago to perm root)
[Desire HD Android Development] bginders:
it was r12 also there is no file called MD5sums_orig.txt in the DHD folder

I also got exactly the same error message as above and got visionary from the same place
[Desire HD Android Development] sfjuocekr:
Yes this is the failsave more or less module won't load no writing will be done, but indeed I failed adding the proper hboot and restore to the v0.1 zip refering to added 0.

Did permrooting your device work in the first place? Because that module is used to permroot, if that worked the script should have worked too.
[Desire HD Android Development] oldskool73:
yup, appears to be rooted fine, I'm using adb and have root there too.
[Desire HD Android Development] sfjuocekr:
I saw from your previous post that the MD5 sum is the same as the original, so no harm has been done.

And noticed that MD5sums_orig.txt is written to the wrong directory ... fail fail fail. Uploading a fix asap for that!
[Desire HD Android Development] sfjuocekr:
Can you do this in terminal:

su

ls /data/local/*.ko
[Desire HD Android Development] bginders:
Great thank you. So im safe to reboot. Thanks again for your help

Sent from my Desire HD
[Desire HD Android Development] oldskool73:
# ls /data/local

vision_oc.ko

wpthis-lovinglymadeforyoubymodaco.ko

rights

tmp

(the vision_oc is just sitting there from the earlier overclocking stuff, not loaded)

same error if I try it manually:

# insmod /data/local/wpthis-lovinglymadeforyoubymodaco.ko

insmod: init_module '/data/local/wpthis-lovinglymadeforyoubymodaco.ko' failed (Exec format error)

...why do I need this, can I not just do the dd manually in adb?
[Desire HD Android Development] sfjuocekr:
This is needed to remove write protection from eMMC, without it permroot should have failed too...

Does Visionairy+ temp root at boot by chance?
[Desire HD Android Development] sfjuocekr:
If you want to be 100% sure you can do the following:

su

dd if=/dev/block/mmcblk0p18 of=/sdcard/DHD/hboot_sanity.bin

md5sum /sdcard/DHD/hboot_sanity.bin

md5sum /sdcard/DHD/hboot_orig.bin

And both MD5 sums should match.
[Desire HD Android Development] oldskool73:
hmm, appears it was, had the 'temp root on boot' ticked anyway. have unticked and rebooted with the perm root option, still appear to have root in adb but now I get:

$ su

# insmod /data/local/wpthis-lovinglymadeforyoubymodaco.ko

insmod: init_module '/data/local/wpthis-lovinglymadeforyoubymodaco.ko' failed (Function not implemented)

I have both 'run visionary.sh after boot' and 'set system r/w after boot' ticked still, should I try without them?
[Desire HD Android Development] sfjuocekr:
Yes run without any options, but

insmod: init_module '/data/local/wpthis-lovinglymadeforyoubymodaco.ko' failed (Function not implemented)

is correct and the module worked, you can check with dmesg.
[Desire HD Android Development] oldskool73:
oh ok, looked like an error still :) (turning the options off & rebooting made no difference)

If that errors ok I'll give it another try...
[Desire HD Android Development] oldskool73:
yup, that appears to have worked now.

I'd add to your instructions 'make sure the temproot on boot option is unticked', for other doofuses like me that just tick everything :)
[Desire HD Android Development] sfjuocekr:
Noted :)

10char
[Desire HD Android Development] zomfgwtfbbq:
Don't mind the noob in me, but what is S-OFF? Ok it's security off. nvm found it but what does it do?
[Desire HD Android Development] capychimp:
it is so we can flash from recovery ;) once there is one
[Desire HD Android Development] sfjuocekr:
It means security off, as in you can write to normally locked parts of the phone.

This means you can mount /system read-write, modify the hosts file to block adds, delete unused apps from /system and use fastboot to flash a new recovery when it becomes available. But there are lots of other things you can do.

Hopefully psfMod will be made for the DHD, that would make the phone complete ><
[Desire HD Android Development] bginders:
I think i to may have made that mistake and ticked all options oops will try again.

Sent from my Desire HD
[Desire HD Android Development] bginders:
Sent from my Desire HD
[Desire HD Android Development] :
function NOT implemented GOOD

any other error BAD

geeez guys, we try so hard to make it as foolproof as possible and sfjuocekr even wrote it in his OT

insmod: init_module '/data/local/wpthis-lovinglymadeforyoubymodaco.ko' failed (Function not implemented)

Is the only error you should get, this is correct and the module worked because without it permrooting should have failed too.

I mean seriously. Do you guys simply NOT care to read, or ignore what he and the rest of us "trainers" write for you, or do you simply think "i just ask, someone else will tell me"?!?!
[Desire HD Android Development] no1male:
Im having the exact same issue.

I have installed the SDK and got ADB working on my PC. When i type ADB Devices it does not detect my Phone.

I have tried deleting the drivers but i am having no success :(

Can anyone help?

Im guessing at this stage i can not restart my phone for whatever reason?
[Desire HD Android Development] AndyCr15:
I've written an all in one guide, would someone with better knowledge than me, read through and check it's correct? I'd really appreciate it -

http://hemorrdroids.net/overclock-undervolt-your-desire-hd/
[Desire HD Android Development] mike1986.:
Type

before and confirm root access on the device.
[Desire HD Android Development] no1male:
Ive got root access, when i typed su the first time in terminal emulator superuser popped up and i clicked allow
[Desire HD Android Development] jonata:
with this root, we lost the OTA update from htc ?

tks
[Desire HD Android Development] Birba:
Hi

I'm getting my DHD on monday!

So 2 questions:

- i thought there are to different hboot versions. why does your method only offer one hboot

- can i first apply ota updates and then root the device?
[Desire HD Android Development] afrcom15:
right, all done here now following this method.

Painless and trouble free, cheers:)
[Desire HD Android Development] Bobblot:
I've tried that and it's coming up Permission denied? I'm running ubuntu 10.10
[Desire HD Android Development] no1male:
I'm getting same issues as bobblot could do with some help
[Desire HD Android Development] afrcom15:
EDIT:

Couple of things I've noticed, when I boot into bootloader and it does it's check for PD98IMG it is extremely slow when doing so.

Android commander (if anyone uses it) says "Root Access NO"

Any ideas?
[Desire HD Android Development] sfjuocekr:
At what step were you, still check right?

As to the drivers you can download them with Android SDK or install then uninstall HTC Sync but leaving the drivers.
[Desire HD Android Development] sfjuocekr:
That error means the module worked ;)
[Desire HD Android Development] sfjuocekr:
The bootloader is always "slow" reading those files, don't bother with it.

Not sure why it tells you no root, the bootloader shows S-OFF? If so there should be root or are you in recovery? You need another recovery with adb root.
[Desire HD Android Development] sfjuocekr:
Link me to the second please, if there is one.
[Desire HD Android Development] sfjuocekr:
Permission denied usually means not found or not su.

You were at the check step still too iirc. If you are, check Visionairy+ options and make sure no options are checked. Maybe permroot again just to be sure and reboot to double check... But only if you didn't invoke the hboot script yet.

Same counts for others with the same problem.

Can those people also cat /proc/version and report back please?

Also you might need to run adb as root (sudo adb shell) if you get permission denied on you PC instead of phone. If you get permission denied on your phone inside the adb shell it looks like some files are missing, but I doubt that even find and grep are missing... Must be something todo with path setup incorrectly if you can post the output of env here that would help.
[Desire HD Android Development] mohit1234:
hi

i did the visionary part

now i tried doing the s-off

but im getting the error:-

md5sum not found

im unable to post a screenshot cos i dont know how to (im a noob)

wat do i do??

can i reboot?? will rebooting brick the device??
[Desire HD Android Development] sfjuocekr:
If you are still at the check or backup scripts nothing harmful had been done and you are still safe to reboot.

Also did you check any options in Visionairy+? Did you permroot and reboot instead of temp root?

Also please post the following output, you can make a screenshot with ShootMe from the market.

su

env

cat /proc/version
[Desire HD Android Development] mohit1234:
oh good phew!!

i just typed

su

sh /sdcard/DHD/check

and i got

md5sum: not found

i hvnt gone further than that, so im safe, right?

and y am i getting this error??
[Desire HD Android Development] mohit1234:
yeah i made sure that i didnt check any options, and i permrooted

plus ive uninstalled visionary also

my output is:-

env: not found

Linux Version 2.6.32.21-gf3f553d (htc-kernel@and18-2) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Thu Oct 28 13:24:11 CST 2010
[Desire HD Android Development] sfjuocekr:
Err just saw your second post.

Could you install Visionairy+ r12 again, do the permroot again and leave Visionairy+ installed.

During the permroot step it will reboot, after that goto settings > applications > turn off fastboot and turn off your phone.

Power your phone back on and try to invoke md5sum again from terminal, does that work?
[Desire HD Android Development] mohit1234:
umm ok

ill do that and tell you tomorrow (its getting kinda late where i live)

anyways

thanks for all your help :)
[Desire HD Android Development] sfjuocekr:
No problem, sofar I have just encountered this md5sum not found myself once and a reboot fixed this. I highly doubt HTC removed basic commands like env, grep and find :s

Just make sure auto temp root on boot is not checked, better yet check nothing just do permroot. Leaving Visionairy+ installed or not shouldn't make any difference as the permrooting should have succeeded and the module it used should still be in place at /data/local/.
[Desire HD Android Development] Bobblot:
That's really weird because I just booted into bootloader and it says S-OFF already?
[Desire HD Android Development] sfjuocekr:
Well if it tells you S-OFF already thats fine, but you did continue after check threw up md5sum not found this is bad. Could you explain to me the steps you took after check? Backup then hboot and they all threw up md5sum not found?

Also could you do something for me in the terminal?

su

env

ls /system

Does env show you PATH? If so please post PATH and post what ls /system shows you, it should show you a bin and xbin folder and can you then check what the contents are of the bin and xbin folders?

ls /system/bin > /sdcard/bin.txt

ls /system/xbin > /sdcard/xbin.txt

And attach both text files to your post here please they will be in the root of your sdcard.
[Desire HD Android Development] jonata:
sorry if repeat :

if rooting desire lost the OTA update ?

tks for reply
[Desire HD Android Development] berek9999:
I'm getting this problem of md5sum not being found as well. I've done a search for it and it appears to be in /system/xbin, but if I try and run it from there with "/system/xbin/md5sum" it still says it's not found.

I've done all the Visionary stuff and have permaroot.

Any suggestions?
[Desire HD Android Development] sfjuocekr:
You mean if you can still use OTA updates? It should be possible to use them, but give it a few days and more custom ROMs will surface and hopefully CyanogenMod too.

I'm not sure if OTA updates will include a new HBOOT, but I doubt that will happen tho.
[Desire HD Android Development] Bobblot:
No, after the checks came up saying Md5sum not found, I just pushed back on terminal and exited.

Heres the other things you wanted,
[Desire HD Android Development] sfjuocekr:
Can you try this:

export PATH=/system/xbin:/system/bin:$PATH

And then invoke md5sum again.

If that doesn't work, please turn off fastboot, powercycle the phone (off and then on, not a reboot) and try again starting with md5sum.
[Desire HD Android Development] sfjuocekr:
How does your bootloader show S-OFF when you had only run the check script baffles me.

Can you try this too:

export PATH=/system/xbin:/system/bin:$PATH

md5sum

And report back if it worked.
[Desire HD Android Development] Bobblot:
I did root with the evostance maybe that did it? Otherwise I have no idea?
[Desire HD Android Development] berek9999:
Thanks for the help, but I've done all that and still get the "not found" message. Weird that my phone does this when others don't - it's not like I've modified anything other than running Visionary.

Any other suggestions? Can I download a copy of md5sum from somewhere and run it from the DHD folder - would that work?

How frustrating :confused:
[Desire HD Android Development] sfjuocekr:
If you followed Evostance guild you have already done the S-OFF too, which covers dd'ing hboot to the correct partition. There is no need for you to continue here.

Altho I'm still wondering as to why md5sum etc don't work for you and a few others. It should be in /system/xbin and you did export PATH correctly, so the shell should be able to find it. Does the same happen in an adb shell?

Do you have fastboot turned off and USB debugging enabled? If so did you do a powercycle?
[Desire HD Android Development] no1male:
i am getting

env: not found

:(

TBH Im a tad scared about powercycling my phone.

Is there any way of checking i wont kill it before doing so?
[Desire HD Android Development] no1male:
just tried

export PATH=/system/xbin:/system/bin:$PATH

md5sum

and still getting md5sum: not found
[Desire HD Android Development] berek9999:
At least I'm not alone!
[Desire HD Android Development] sfjuocekr:
If you have NOT run the hboot script no harm has been done.

The check and backup scripts don't do anything harmful to your devices.
[Desire HD Android Development] sfjuocekr:
What happens if you do this:

su

cd /system/xbin

./md5sum md5sum

/edit: I have to goto the shop real quick, will be back in 30 minutes.
[Desire HD Android Development] Bobblot:
Yes I've have powered the phone off with fastboot and usb debugging enabled. Maybe it's something in evostance root that makes the md5sum not found?
[Desire HD Android Development] sfjuocekr:
I highly doubt it, did the other people who have this problem use Evostance guide?

When I get back from the shop I will make a small test archive to test a few things like including a working md5sum myself see if that works out.
[Desire HD Android Development] berek9999:
I've been doing a bit of digging around, and I'm wondering if this is something to do with the fact that I've got Titanium backup installed, which installs busybox. If I run "busybox md5sum <filename>" then I do get an MD5 sum shown.

Apologies if I'm talking rubbish, I'm very much fumbling in the dark here!
[Desire HD Android Development] no1male:
I get md5sum not found still

For what guy above says I have titanium backup installed
[Desire HD Android Development] sfjuocekr:
I have Titanium Backup installed myself too, so that shouldn't cause issues.

It's very strange tho that if you do cd to /system/xbin and do ./md5sum there it say's not found either ... it's the SAME directory as md5sum should be in.

But it might be an idea to invoke md5sum trough busybox indeed, if that works a unmodified phone.
[Desire HD Android Development] no1male:
I'm getting nothing when typing

Su

Busybox md5sum

Just a blank line.

Dunno what the hell is wrong :(