yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] baum01:
I got the same error (maybe with a few different values) except for the last two lines. Stock, 3UK branded (if you can call a bookmark a branding) without having changed anything but having rooted my phone before to install a few (non-system-changing except for Adfree) apps before doing what this guide showed.

The bootloader shows:

ACE PVT SHIP S-OFF

HBOOT-0.85.0007

MICROP-0438

RADIO-26.03.02.26_M

eMMC-boot

Oct 11 2010

Any idea what the problem could be?
[Desire HD Android Development] uniqs:
I've updated the ROM and kernel, but when I try to reboot in recovery mode nothing happens - waiting cursor appears, but the device is not rebooted. I have a latest version of ROM manager installed.

Could somebody help? Thank you.
[Desire HD Android Development] hamdir:
be careful custom kernels will break the microphone or WiFi, I tried buzz v1.0.6 plus its modules WiFi worked but the mic stopped working, make a clockwork backup before trying kernels or it will be hard to go back

we will need to wait for updated kernels
[Desire HD Android Development] makbil:
Did you follow the guide carefully?

Try this: start phone normally, then press the power button and select restart, after pressing yes, press vol- + power and see if you can get to the recovery mode.
[Desire HD Android Development] uniqs:
Thank you for help. In the guide (in the restore su section) written: "boot to Clockwork recovery". I tried to do that via the ROM manager but not succeeded. The way you suggested to use is a way to get to the regular bootloader (fastboot and other options). It is also a way to get to the Clockwork recovery mode or regular recovery mode is also good?

UPDATE: I've tried your suggestion and found that when the regular recovery mode is chosen, actually clockwork recovery is arisen, so I continue with restoring su. Thank you very much for help.

UPDATE2: su is restored and all works as expected. I would suggest to the topic starter to add to the 1st post some more details about booting to recovery, so ppl will not be confused like me and also - installing HTC sync is a prerequisite, otherwise adb does not find connected device (HTC driver installation fails).
[Desire HD Android Development] ErMeglio:
hamdir, I've just read about the WAL improvements of the new sw. If I understand, we are "disabling" the new system completely due to the fact we did't flash the new bootloader, correct?

Is there some way to have both the things, or there is still no way to s-off the new boot? Not that the phone isn't snappy and amazingly fast and stable now, just curious!!!

Also, I see the devs are updating su to make it work ok, do we need it? What "version" is yours?

Sent from my Desire HD
[Desire HD Android Development] makbil:
Clockwork recovery replaces normal bootloader, so yes, it's good.

I have clarified that procedure a little in my guide.
[Desire HD Android Development] hamdir:
i

where did you read wal is disabled without bootloader. If it's disabled then why Su stopped working, can you offer a link?

no in my method its an old Su, chainsDD will update the superuser app soon then we can update it from the market
[Desire HD Android Development] ErMeglio:
Well, I could have misunderstood.

I've read these posts http://xdaforums.com/showpost.php?p=10093173&postcount=221 http://xdaforums.com/showpost.php?p=10093173&postcount=222 http://xdaforums.com/showpost.php?p=10093173&postcount=223 and this thread http://xdaforums.com/showthread.php?t=886999 .

And, to sum up, I've come to understand that:

*WAL works with the new hboot instructions

*we didn't flash the new hboot

*known SU can't work with wal due to the exclusive access to sqlite db.

I supposed we used an older su because of other kind of problems, as with no wal there should not be the problem mentioned. But I definitively miss something, that's why I am asking clearances :o
[Desire HD Android Development] hamdir:
ok u gave me a link to three same posts that I wrote :l

as for the patch thread nothing mentions passing instructions to hboot

I think ur definitely missing something in here, I really doubt a journaling system needs to communicate with hboot
[Desire HD Android Development] mossywell:
ENG and Radio S-Off, permroot

Odd, I'm also getting the apply_patch_error("/system/build.prop", "<long hex code>", "<another long hex code") error.

(Status 7)

I tried both the OTA update.zip in /download and tried the one available for d/l, but both give the same error. Any ideas?
[Desire HD Android Development] makbil:
OK, I know I'm still new to Android but why would the OS need to access hboot which initializes the OS? From what I understand, the whole process takes place within the OS so hboot version should not make a difference.
[Desire HD Android Development] randomdud:
Isnt it easier if we replaced Files inside PD98IMG.zip and flash? [Clean Rooted version of 1.72.405.3]

is it like.. replacing hboot and modding the system.img?

wonder if its plausible :)
[Desire HD Android Development] Eddie1506:
That was my idea too (sortof), but I guess it's not plausible since my thread asking if it would work was deleted for God know why.

I theorised, since we have Radio S-OFF, why not just offload PD98IMG.zip with modified recovery.img (or with only recovery.img in it, if OTA was already applied) to SD card and let bootloader do it's work.
[Desire HD Android Development] randomdud:
ye, exactly. lookin for a way to open up the img files ;x the darn magicIso wont open it so i guess ima go read abit and find a way to open them all up and finger them alittle :) maybe might get some honey juice ;p
[Desire HD Android Development] Eddie1506:
We probably need ENG S-OFF for it to work, not just Radio S-OFF. Having ENG S-OFF and Radio S-OFF is not a problem, because we have a way to root with both of them, only having Radio S-OFF or no S-OFF at all is a problem.
[Desire HD Android Development] RichardFHTC:
Step 2

I sucessfully installed update.zip from recovery console

I have been trying for a while now and read through forums and I cant find an answer.

sending 'boot' (2928 KB)... FAILED (status malformed (1 bytes))

Can anyone help ?

Resolved was not in fastboot mode correctly
[Desire HD Android Development] spookamiester:
Would I be able to use this update and the buzz 1.06 kernel?

I just installed it and am loving the speed/battery improvements.

Is it the new kernel in this update that is improving the battery?
[Desire HD Android Development] ErMeglio:
Thanks for the clearances, you're completely right :-)

The only fact I miss, so, is why our "old" su is working if it is supposed not to with the new WAL system...

Sent from my Desire HD
[Desire HD Android Development] hamdir:
sadly no, installing the 1.06 buzz kernel will kill the microphone, both CM based kernels and old 1.32 based kernels are not compatible with this update

we need to wait for new updated kernels

seriously disappointed with this since 1.06 is the best kernel

anyway the new battery performance and 720p are worth the sacrifice :)
[Desire HD Android Development] hamdir:
for all of you suggesting creating an update.zip file be my guest :D

i have no clue how to do such stuff, i'm not smart enough ;)

i think you can find rooted 1.72 roms in the development thread

this guide is about how to use the OTA file and trying to update without wiping and it was written when everyone was trying to find a way to flash it mantain root and still have a working wifi
[Desire HD Android Development] dr.m0x:
I had this problem too. Used this method instead, followed by the superuser package posted by the OP.
[Desire HD Android Development] spookamiester:
Only problem is 1.06 is the older and best version and an updated version may not be as good still.

I'm gonna hold out for the next OTA update I reckon. I've seen alot of problems reported with this one and am happy with what I have so not gonna risk it until there's stable confirmation or fixes. Would be nice if one of the geniuses here could just extract the 720p and whatever is improving battery (my guess is the kernel though lol) and release as more of an add-on/patch than an update. :)
[Desire HD Android Development] hamdir:
well we need to convince Apache14 to give us a new kernel with his mods based on the 1.72 kernel for sense ROMs, instead of relying on the CM tree
[Desire HD Android Development] golokipok:
so I need to do these things 1st before applying the OTA?
[Desire HD Android Development] cubitusclaudius:
Why isn't this thread in "Desire HD Android Development"?

should be sticky there. no?
[Desire HD Android Development] dr.m0x:
No instead of flashing the OTA. Here is a quick guide.

- Extract system.img, boot.img, and radio.img from the ota

- Reboot into bootloader

- Fastboot flash radio radio.img

- Fastboot flash boot boot.img

- Download system_flash_cw.zip from the link

- Put system.img and system_flash_cw.zip on the root of your sdcard

- Reboot into CWM

- Install system_flash_cw.zip

- Install superuser file from post #1 of this thread

- Done.
[Desire HD Android Development] lemat1:
excellent guide, thankyou, working perfectly...inc wifi

Mat
[Desire HD Android Development] duncan_mccloud:
In -s command

have tried running this command about 50 times now and nothing

ln -s /system/bin/su /system/xbin/su

keep getting

/sbin/sh: In: not found

after executing

not a clue what I'm doing wrong..
[Desire HD Android Development] capt_harlock77:
Ahem... silly question... are you typing "In" (with a capital "i") or "ln" (with a lower case "L")? The correct one is the second.
[Desire HD Android Development] duncan_mccloud:
yes I am using capital I
[Desire HD Android Development] Andy:
Use a lower case "L"
[Desire HD Android Development] falmc:
Tried to first flash the OTA zip from #1 - failed

This was down to me being a T-Mobile UK user so I think its best to point out to anyone else with the same situation why it is failing.

I used to system update option on the settings menu and then located the downloaded T-Mobile OTA from my downloads folder>renamed to update.zip> flashed

As expected and told in #1 wi-fi error ed so I went ahead and downloaded the boot.img linked>fastboot flash boot c:/ etc etc and flashed it in fastboot usb.

However it appears to have done nothing for my wi-fi and I have now had to revert back to a backup I made before attempting to update.

Just curious that you guys may have an idea of how I can flash successfully a boot img to get my wi-fi working again after flashing my T-Mobile OTAas checking peoples locations on posts, not everyone is US located and therefore must be doing something different (i assume)

I wouldnt say im an advanced android user but ive had a G1 for 2 years and have modded the life out of it so im pretty familiar with terms and methods. My DHD is rooted and S-off if you need that info to help.

Cheers in advance guys.
[Desire HD Android Development] Andy:
The new update requires the new radio also. Thats probably why your WiFi doesn't work.

You will need to Radio S-OFF your DHD and flash that.
[Desire HD Android Development] falmc:
Ah seems I might have missed that. Just got radio s-off from the easy root guide and ill give this another shot.
[Desire HD Android Development] falmc:
Ok ive got everything ready as required radio s-off, eng-off and rooted. OTA updates fine in clockwork recovery but this boot.img just doesnt isnt bringing my wi-fi back to life

d.

C:\Users\#####>fastboot flash boot C:/android-sdk-windows/tools/boot.img

sending 'boot' (2928 KB)... OKAY [ 0.594s]

writing 'boot'... OKAY [ 0.605s]

finished. total time: 1.200s

everything above is correct right?

logcat confirms that its failing to load wi-fi

any ideas?

thanks again
[Desire HD Android Development] Andy:
You need to flash the radio not boot.
[Desire HD Android Development] dman2266:
comand promt

could somebody tell me what i rite in the command promt plz so i cud jus copy and paste thanks
[Desire HD Android Development] dman2266:
help

could somebody help me plz????? am stuck
[Desire HD Android Development] dman2266:
error cannot load boot img

gettin error cannot load boot image help
[Desire HD Android Development] DcBexter:
I always get an "FAILED (remote: not allowed)" error when trying to "Fastboot flash radio radio.img"

dhd s-off & rooted

what am i doing wrong?

edit:

followed this: http://xdaforums.com/showthread.php?t=835746 to do ENG S-Off and now it works
[Desire HD Android Development] compi_hu:
Why can't one just flash system.img the same way as flashing boot and radio (via flashboot)? I'm trying to implement a similar procedure to Desire Z, so this is the reason behind my question.
[Desire HD Android Development] CodeJACK:
Hi,

Everything was working great untill i tried to use Rom Manager.

The version of Superuser provided in the link does not seem to work with Rom Manager.

Once I run Rom Manager for the first time, i get com.noshufou.android.su stopped unexpectedly for any subsequest request for any root app.

I tried clearing the app data cache and this allows root to run again but once Rom Manager is run, it stops working once again.

Not a show stopper but would be nice to have a fix :-0

Cheers

Rob.
[Desire HD Android Development] makbil:
No, it has nothing to do with the radio. You just need to flash the new kernel.
[Desire HD Android Development] baum01:
Anyone?

And, if not, could I do the following as an alternative:

Thanks for your help!
[Desire HD Android Development] FletchNZ:
I had the same problem, I re-read the guide and realised that there is a difference between Radio S-off and Eng S-off and you need to use 2 different tools. I only had Radio S-off. Use the tool via the link below to get Eng S-off, reboot your phone and give it another go, it worked for me.

Eng S-off

http://xdaforums.com/showthread.php?t=855403

Radio S-off

http://xdaforums.com/showthread.php?t=857537
[Desire HD Android Development] baum01:
Thank you so much, it worked! :)
[Desire HD Android Development] compi_hu:
Anyone any info on this please?
[Desire HD Android Development] FletchNZ:
I have finished Flashing my phone with the latest Rom, Kernel and Radio but it is still offering me the OTA upgrade, Have I missed something???

* Andorid version: 2.2.1

* Baseband version: 12.28e.60.140fU_26.04.02.17_M2

* Kernel version: 2.6.32.21.-g3d0aaff / htc-kernel@and18-2#1 / Wed Dec 1 17:09:51 CST 2010

* Build nuber: 1.72.405.3.CL296490 release-keys

* Software number: 1.72.405.3

* Browser version: WebKit 3.1

Radio: Radio_12.28e.60.140f_26.04.02.17_M2

Edit:

I know there is the tick box to disable the check but shouldn't it recognize that it is up to date???
[Desire HD Android Development] dstenc:
Thanks for great tutorial.

Did everything as written and it works! :)
[Desire HD Android Development] dstenc:
Have you checked which update is offered? Is it 1.72.405.3 or maybe some higher version?

I've done everything as written and when I check for OTA updates, I get message that there are no updates.

Prior the process I had possibility to download and install OTA update.
[Desire HD Android Development] FletchNZ:
I played around and found when i cleared the cache of "updater" and searched again for any new updates it didn't find any, so it must have just been some old data hanging around
[Desire HD Android Development] golokipok:
OK I did the stuff but I don't know why my froyo is still on 2.2. I can't seem to find the system.img inside the OTA zip. I've also observed that my wifi doesn't work after I've flashed the original kernel from the 1st post and I got no sound!:eek:
[Desire HD Android Development] crypticc:
Because I had edited build.prop and had non-standard kernel I needed to bypass the assert-failed checks by replacing the updater-script in META-INF\com\google\ directory with this file. Can then follow OP instructions. Use with care !

From one semi-delighted customer who didn't break wife's Desire HD :) Just need to get the wifi working. fastbooting boot.img doesn't fix that !

Just one question - with eng S-off and radio S-off. Does flashing updated radio.img bring any significant benefits. Is it mandatory to get wifi?

Update: I notice there's two different methods kicking about. 1 uses OTA update.zip, the other uses .exe. This forum is OTA update.zip, and I'm not sure it flashes the updated wlan kernel fully (the difference in radio is one has d version whereas the other is e). I am just about to try extracting system.img from the exe approach and nabbing matching boot.img from that.
[Desire HD Android Development] maurei:
Your reply was just the thing I was looking for!

Thanks alot for this! Hope it works properly :rolleyes:

------------------

Works perfect! thx~!
[Desire HD Android Development] crypticc:
I can confirm that the radio in the Radio_12.28e version fixes wifi broken in d version. You can get the radio, boot and system.img fromin the rom.zip made available in the .exe download) I installed using this method >

http://xdaforums.com/showthread.php?t=879375&page=10

But I installed SU using method in this thread.
[Desire HD Android Development] maurei:
I have some problems with reflashing the kernel...

At first I moved AdbWinApi.DLL and boot.img to /tools and I browsed there using the PATH command in CMD.

Next, I put my phone in Fastboot mode and connected it to my PC which turned it into Fastboot USB.

Now, i tried to use the command:

fastboot flash boot boot.img

leaving me nothing but:

error: cannot load ''boot.img''

Perhaps it has something to do with the way I flashed update.zip: I replaced updater-script in \META-INF\com\google\android with the one from crypticc's attachment.

Can anyone please assist me on this one?
[Desire HD Android Development] crypticc:
Fastboot doesn't look at anything you flashed as update.zip. It just looks at the boot.img, or radio.img.

You sure you installed sdk? Have eng s-off?

Regardless once fastboot sorted, try the clockwork system.img method

.you get the system.img and matching boot.img from I inside %temp%/[some folder]/rom.zip when you run the .exe version when it starts but before selecting to flash, and important you DON'T let.exe flash phone

You cannot fastboot flash system but person on post #91 The link I attached kindly has a skeleton clockwork updater.zip which flashes the system.img it finds on your sdcard.

You then fast boot the boot and if radio so-off the radio too.

The most difficult bit is getting the ruu .exe. Someone mirrored it as a zip on first page of the linked thread. Seemed faster than the other link to me. See # or #4

regards
[Desire HD Android Development] maurei:
In the phase I got stuck I thought only the wifi wouldn't work, but I've managed to break my microphone as well? It does work with voice recorder and other apps, but when calling it does not. And, I lost my root, prompting SU in terminal emulator gives permission denied. Do I need root in order to successfully use the "fastboot flash boot boot.img" Command? Because that would explain the fails... After crypticc's post, Its still not understandable to me.. Me is not that familiar yet:(

How the hell did I lost root? I'm sure I had root + eng + radio s-off when I started. I still have the last two by the way. I installed the (modified) update.zip by loading it in clockwork recovery, and now I'm here, wifi- mic- and rootless, without working commands. Any thoughts about where it went wrong ?

Sent from my Desire HD
[Desire HD Android Development] CyberTod:
Installing update.zip is only the first step. Continue with reflashing the kernel to get wi-fi back. And getting root again is in the final step.
[Desire HD Android Development] makbil:
Wi-Fi and microphone problems are usually related to the kernel. You need to flash a compatible kernel.

Root is related to OS whereas S-OFF is related to flash area, it's normal to loose root, the trick is to be able to regain it.
[Desire HD Android Development] maurei:
Makbil, CyberTod, thanks for your reply.

I correctly understood that after installing update.zip I still had to reflash the kernel to make wifi work.

However, I wasn't sure whether it was normal for root to be gone, I thought only the app SuperUser would crash. And because of the errors caused when using the flashing commands with fastboot, and also my mic which stopped working unpredicted, it made me think I had made a profound mistake. Thanks for clarifying this for me

Though, there still rests a problem. Like I said; using the commands with fastboot gave an error. Therefore I cannot proceed to the next step that fixes my wifi and mic like you tell me to do... Hoping to get some help on this.

Doing :

Fastboot flash %partition% % Name%.img

Prompts :

Error; cannot load %name%.img

This, while the command fastboot devices does work: it lists a device (guess its my dhd). So it can be concluded that my usbdrivers are fine. Also, I moved AdbWinApi.dll to tools dir which I browsed to using the following commands in CMD:

PATH ;

PATH=c:\Program files\Android\android-sdk-windows\Tools

I don't understand why my command is failing..

At first I thought it only was with boot.img from this topic's guide, but trying to restore my nandroid backup failed exactly the same way: failing commands. My flashing is just not working?!

Wanted to start a new thread because of the restore that fails too, but decided to do it here.

Help would really be appreciated!

Sent from my Desire HD.

EDIT

Problem solved through some help at #desireHD on freenode :)
[Desire HD Android Development] jeRrRKKKK:
have you tried re-rooting again with visionary?

or try re-flashing clockworkmod?

also you might try to find the original stock rom and try to flash that too
[Desire HD Android Development] Stoffl_:
Was running into assertion errors but this worked for me, much appreciated.

I also had to manually flash clockwork mod recovery through fastboot, rom manager just failed repeatedly. vOv
[Desire HD Android Development] tarreltje:
I have installed the OTA update before i was getting to know about all this root stuff. Since i already have installed the OTA update can i still root my DHD? Maby reset the DHD to factory settings ect?
[Desire HD Android Development] dr.m0x:
Nope. Hate to break it to you but at this stage you're stuck with stock. You can root and then use a safe method like this one to get to 1.72 but you can't update to 1.72 and then root.

Maybe one day it will be possible but not right now.
[Desire HD Android Development] madindehead:
Delete post.
[Desire HD Android Development] madindehead:
I had an issue with the "File exists" when I executed ln -s /system/xbin/su

BusyBox has told me it has found 2 copies.

One in /system/bin and the other in /system/xbin.

Where should I be installing it? The other one will be removed. One final thing, the Superuser icon, should that be the little Ninja now, and not the skull it was before? I am assuming this is the old version of Superuser? Anyway we can update to the new one?
[Desire HD Android Development] CyberTod:
I posted about the file exists issue a few pages back. Before using the "ln" command to make a symbolic link use "rm" to delete the second copy :

rm /system/xbin/su

Then repeat the step that gives the error.
[Desire HD Android Development] madindehead:
Cool, thanks mate. Must have missed that post.

Where is it best to instal BusyBox? /system/bin or /system/xbin?

Or does it not really matter? I miss the new Superuser, but hey. Can't be helped. Anyone got any idea if the new one will work eventually?
[Desire HD Android Development] Eddie1506:
There's a hacked version of latest Superuser that works, that will eventually turn into official as the patches were submitted to ChainsDD's github repository.

The patched version can be found at http://xdaforums.com/showthread.php?t=886999
[Desire HD Android Development] snooffy:
Worked for me. Installed the zip from clockwork recovery. Finally after days of struggling I have the latest and stable superuser and su working.

Thanks!