yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Themes and Apps] byrong:
If you are comfortable pulling your own framework-res.apk, you can use UOT Kitchen to make your own custom circle battery icon. If you are just using the stock framework, check to see if UOT already has it. If they do not, pull it out of the ROM's zip file.

If you have already modified your framework-res in some way (like flashed a theme) then pull it directly from your phone to use on UOT kitchen.

Make a nandroid backup, of course, but so far I've had 100% success using UOT Kitchen.
[Droid Incredible Themes and Apps] byrong:
Here are some of the PNG files being used by g00gl3's attachment.

If you're ever curious, you can always explore an .apk file using a zip program. I opened g00gl3's attached zip, navigated to system/framework, then opened framework-res.apk

Inside of framework-res, look for the .png files that start with "stat_sys_battery"

In this case, they can be found under res/drawable-hdpi-v4
[Droid Incredible Themes and Apps] AgentJz:
Awesome!! And it fixed the clear background in just the ongoing area so now I cab see the temp!
[Droid Incredible Themes and Apps] g00gl3:
Oh yeah, forgot I included that too. Makes it easier to read that way.

Glad you like it.
[Atrix 4G Accessories] kenio8185:
http://www.mophie.com/juice-pack-air-iPhone-4-Verizon-battery-case-p/1145_JPAXP4-VZ.htm
[Atrix 4G Accessories] jwhited:
Not yet, but I imagine that the shape of the case would be a little odd, since the USB and HDMI connectors are on the side.
[Atrix 4G Accessories] hotleadsingerguy:
Not really...they'd just use 90-degree connectors in the case so it wouldn't stick out much at all. Good chance on the exterior of the case they'd move the USB and HDMI connectors to the bottom so it would stick out a bit on bottom, but the side wouldn't be very thick
[Atrix 4G Accessories] Fixter:
As you can see they only make Juicepacks for Apple products.
[Desire HD General] stuart0001:
I have a T-Mobile UK DHD that I'd fully rooted, Eng-Off, Radio S-Off & SuperCID

I was running a LeeDroid ROM but yesterday it began frequently locking up so I tried to do a wipe and reinstall the ROM but at the end of the ROM installation after "Writing boot.img" it said:

assert failed: write_raw_image ("/tmp/boot.img","boot")

E:Error in /sdcard/LeeDrOiD_HD_V2.0.0.zip

(Status 7)

Installation aborted.

I also kept getting the messages E:Can't mount CACHE:recovery/log & E:Can't open CACHE:recovery/log

I then tried to install the stock 1.32 RUU but that stuck at the Updating User Data stage at 40%.

I'm now stuck with the bootloader options and simply have a white screen with the below and warning triangles bottom left & right.

ACE PVT SHIP S-OFF

HBOOT-0.85.0007

MICROP-0438

RADIO-26.04.02.17_M2

eMMC-BOOT

Oct 11 2010, 12:47:02

RUU (This is highlighted yellow)

I have tried ADB but the device isn't shown as attached. However, Fastboot shows it attached but I've had no success pushing the ROM this way either. Below is copy of the cmd window:

C:\AndroidSDK\tools>fastboot boot PD98IMG.zip

creating boot image...

creating boot image - 301006848 bytes

downloading 'boot.img'...

OKAY [ 47.302s]

booting...

FAILED (remote: not allowed)

finished. total time: 47.302s

Can anyone offer any assistance as I've run out of ideas and fear I've bricked it.
[Desire HD General] 20mark:
you cant just flash rom via ADB. you need recovery. Do you have clockwork mod recovery?
[Desire HD General] ghostofcain:
The message you get about being unable to write boot suggests you are no longer S-off, whilst bootloader suggests you have s-off, l would start from scratch and s-off again and then try reinstalling the rom
[Desire HD General] stuart0001:
I used to but it's been wiped as part of the the failed RUU installation. Power On/Vol Down now does nothing

Do you mean Eng or Radio off? Can I do that with no bootloader options or recovery?

How would you suggest installing the ROM and which one?

Thanks for any advice.
[Desire HD General] stuart0001:
I've just tried jkolo's easy S-Off tool but I get an error message pop-up "Module or hboot fail. Aborting."
[Desire HD General] EmptyArea:
So what happenes when you choose the recovery option?

Oh and btw don't worry too much about the void warranty, I've read of a few people who've had to send phones back to HTC without being able to revert to stock first and they've been successful - obviously this is a last resort.
[Desire HD General] stuart0001:
I don't have a recovery option on the Phone.
[Desire HD General] EmptyArea:
So can you use fastboot to do this successfully?

fastboot erase recovery

fastboot flash recovery clockwork-recovery.img

If you need the image it here: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.6-ace.img
[Desire HD General] stuart0001:
I haven't tried that yet but fear the 1st line may wipe my only way of communicating if the 2nd part doesn't work :confused:
[Desire HD General] EmptyArea:
well you say you haven't got the recovery option anyway, so you could leave that line out I only put it because that's what I'd do.

HOWEVER: I'm no expert.

Question after Re-reading your post: Are you worried you'll delete fastboot? I'm sure that's not what I'm suggesting. But as it's your £500 device wait for someone else to confirm.
[Desire HD General] stuart0001:
No luck :(

C:\AndroidSDK\tools>fastboot flash recovery recovery-clockwork-3.0.0.6-ace.img
sending 'recovery' (3334 KB)...
OKAY [ 0.560s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.562s
[Desire HD General] Aamir.Badat:
Everytine you try writing it fails what else can you do?
[Desire HD General] EmptyArea:
I'd jump to thinking you're not ENG S-Off anymore (got to say probably the failed 1.32 flash that did it. And you can't use that tool so look for an alternative description of how to get there.

If you can't use ADB I don't know how to get there.

If somehow ADB does start working then the CyanogenMod wiki might be useful.

http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Root_Guide
[Desire HD General] Aamir.Badat:
If you lost s-off while flashing the 1.32 rom then I also suspect you lost root.
[Desire HD General] stuart0001:
I've got backups of:

hboot_original.bin & part7backup-1294609557.bin

Are they of any help?

I can't see any way to gain Eng-Off without root so I'm at a loss.

The frustrating thing is I don't know what happened in the 1st place that froze my phone and kicked all this off. I'm guessing I have a hardware fault of some sort :confused:

Would T-Mobile exchange or repair under warranty, despite the mods I'd made?
[Desire HD General] stuart0001:
I'm starting to regret trying that as a solution now :(
[Desire HD General] preacher65:
I remembered something similar being posted on these forums a few months ago, so I had a search and found this thread:

http://xdaforums.com/showthread.php?p=9139950

I'm not an expert on these things, so I don't know if this would work for you. I would suggest waiting for someone with a bit more experience than me to join the discussion, as I don't know how similar your circumstances are to the ones in that thread. Do you get any error messages on your PC when you run the RUU? I take it that it finds your phone, whereas in the thread above the RUU wasn't seeing the phone.

However I thought reading that might give you some hope. Worth reading the thread all the way through.
[Desire HD General] KamikaZeeFu:
I think what disabled most of your options was flashing a stock ruu. It overwrites hboot and the recovery.

Edit: since the ruus fail installing, maybe someting is off with your device, NAND error or someting.
[Desire HD General] danrobz:
this sort of thing doesnt happen if you are flashing custom roms though right? its making me nervous now!
[Desire HD General] stuart0001:
Thanks for the tip. I'll have a read and may give that a go.

I don't get errors, the RUU just freezes and I have to pull the plug.

The errors started when I was on a Custom ROM but my suspicion is that it's a hardware fault to blame. If I can't fix this then whilst the custom ROM probably didn't cause the damage, the general unlocking etc may have voided my warranty.
[Desire HD General] danrobz:
Ouch! Well good luck, I hope you sort it :)
[Desire HD General] preacher65:
If your phone is responding to fastboot commands via usb cable, try this

fastboot oem listpartition

This will list all the partitions on your phone's nand memory. If you have a faulty block in one of the partitions, the size may have decreased, which I believe could prevent the image from being written to that partition.

Output from my phone is attached, particularly compare the sizes of the recovery and boot partitions.

Again, I'm not an Android expert, just piecing things together I've read in other threads.
[Desire HD General] turbo_d:
Can you do fastboot boot filename.img

Don't know if it will work. Sorry your still stuck.
[Desire HD General] stuart0001:
Thanks but I only got the following:

C:\AndroidSDK\tools>fastboot oem listpartition
...
(bootloader) [ERR] Command error !!!
OKAY [ -0.000s]
finished. total time: 0.010s
[Desire HD General] stuart0001:
Tried that with CWM img but got an error (see a few posts above) :(
[Desire HD General] turbo_d:
Ash sorry, I thought that was with the flash I was thinking if you can do just the boot. Fastboot boot xyz.img

I will keep searching.
[Desire HD General] stuart0001:
I've only tried flashing the recovery partition, not the boot yet.
[Desire HD General] turbo_d:
Sorry, I was thinking this cmd should boot recovery.img don't flash boot yet if at all.
[Desire HD General] stuart0001:
Ahh. I see. Tried but again no dice:

C:\AndroidSDK\tools>fastboot boot recovery-clockwork-3.0.0.6-ace.img
downloading 'boot.img'...
OKAY [ 0.555s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.556s
[Desire HD General] turbo_d:
Worst case you could try telling t-mobile an its killed the phone, worked for me with Vodafone when mine just died, wouldn't power on... :( they sent me a reconcile but at least it worked.
[Desire HD General] henv:
Just some ideas you can think of:

1) If I go to the bootloader i see short appear messages that search for a PD98IMG.zip. I dont know if you see them also. If so maybe its possible to put a PD98IMG.zip to youre storage card. Then boot to bootloader and then try to install this zip. You can download PD98IMG.zip in the thread downgrade 1.7x/1.8x. its just a idea. Dont know if it will work. I used this PD98IMG.zip to downgrade my brothers dhd to 1.32

2) Did you use the alternative fastboot.exe? I download a alternative fastboot.exe a time ago. Dont know why it was.

3) Also saw this thread (http://xdaforums.com/showthread.php?t=939982). I saw next comment "these ROMs are simply debranded and rooted stock roms including an unsecure boot.img", this trigger me with youre error that it hangs when download boot.img
[Desire HD General] preacher65:
Possibly the command's not available in the stock bootloader then. Sorry.

If you have Radio S-Off but the stock bootloader (which "Ship S-OFF" seems to indicate), I don't think you will be able to flash with fastboot, as I think that needs the custom bootloader (Eng S-OFF).

I assume you've tried putting the PD98IMG.zip on the root of your sd card and rebooting?
[Desire HD General] turbo_d:
Stupid auto correct I meant ota over the air update. Or just tell them its dead explain when you switch on it goes to triangle screen. Sorry the boot didn't work.

I will keep thinking
[Desire HD General] stuart0001:
I can't boot to bootloader

Yep, again no dice.

That may be my only option at this stage.

I'm going to give the trick suggested earlier of using the test RUU to install the 1.32 released ROM. I'm having to wait an hour for the slow download.
[Desire HD General] ghostofcain:
I suspect an hardware issue here, now as the last thing you tried to flash was an ruu I would think you'll get away with returning it as non functional
[Desire HD General] Aamir.Badat:
But tthat flash failed there like half a rom on the device you could say the ota crashed
[Desire HD General] henv:
Just saw this thread (http://xdaforums.com/showthread.php?t=894998). Same error as you only he has ship on. He send it back to htc
[Desire HD General] stuart0001:
I'd seen that but assumed it was a SD card mounting error, which I've never had an issue with.

For info I ran the "fastboot getvar all" command and got:

C:\AndroidSDK\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0007
(bootloader) version-baseband: 26.04.02.17_M2
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 1.39.110.1
(bootloader) serialno: HT0CGRX16182
(bootloader) imei: ************
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4194mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-7eafc656
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.018s
[Desire HD General] makbil:
I've been following your issue sice last night. Seems to me the only thing you haven't tried yet is to try flashing the original T-Mobile ROM for your locked device, I'm pretty sure this will fix the problem. I still don't think there is a hw problem there. The problem is, I looked around and couldn't find such a ROM. One solution may be for someone with the same ROM to extract the ROM and make it available to you. Unfortunately, I have no idea how to do that in Android but I'm pretty sure there has to be a way to do it. Maybe someone who knows this can type out the exact instructions and a kind soul would do that for you.

I've also read a number of users suggesting a gold card which I haven't done either. HAve you tried that?
[Desire HD General] stuart0001:
Thanks. I've made a gold card but that didn't seem to make any difference. Also, if you look at my post above my CID is unbranded so I don't think a T-mob ROM is the answer, although I'd happily give it a go.
[Desire HD General] stuart0001:
I just want to say a big thank you to everyone that's trying to help me. It's a fantastic helpful community here. :D
[Desire HD General] stuart0001:
I'm now trying to update by using the 1.15 test ruu to install the 1.32 ROM but looks like it's stuck at 40% again.
[Desire HD General] makbil:
You should delete the full IMEI number from your post, not a good idea to publish it ;)
[Desire HD General] makbil:
One more thing. Since nothing seems to work so far and it looks like nothing new to try, why don't you give a shot to flashing a kernel only. Get "kernel update utility" and a stock kernel and just give it a go. It will definitely not make things worse for you.

Also, at this point I wouldn't really trust everything I see on the boot screen as things seem to have messed up and there is really no way to tell which is true and which is false.
[Desire HD General] stuart0001:
I've nothing to lose at this point so will give it a go. I've found the utility but any recommendations for the Kernal to try?
[Desire HD General] preacher65:
hboot_original.bin is the stock bootloader, but I have no idea how to get it back on your phone without adb - jkoljo (or others) might. It would be good to know what 40% means - i.e. has it actually flashed anything at that point, or is it just preparing to flash. Is there anything helpful in c:\ruu_log?

I hate to say it, but it seems more and more likely there's a hardware fault - especially given the error that started this whole thing off.
[Desire HD General] preacher65:
Clutching at straws here, but have you tried the 1.72 RUU?
[Desire HD General] Aamir.Badat:
that will definetly break root and s-off it has done before
[Desire HD General] dr.m0x:
So you can get into fastboot but not bootloader? This seems bizarre as you would normally have to go into bootloader first and then select fastboot from there if you aren't launching commands from a terminal on your pc.

It is possible to attempt a direct write of the backup hboot but I think not without adb shell access, so in your case it's probably off the menu.

Sent from my super slick Android device.
[Desire HD General] preacher65:
Hmm, but if he doesn't have a working OS on his phone, surely he doesn't have root anyway... and I didn't think it would overwrite Radio S-Off, just Eng H-Off, which he doesn't have...? There's a working downgrade path from 1.72 to 1.32 isn't there?

As I said, though, it's clutching at straws.
[Desire HD General] Aamir.Badat:
but i doubt it, he will get a write error or it will crash at 40%
[Desire HD General] makbil:
Try Default_kernel_1.72.405.3, it should be available somewhere on Lee's thread or his mini site.

At this point we are aiming to see if we can get it to boot somehow.
[Desire HD General] GurliGebis:
Let me see if I'm getting this right?

It goes into fastboot, correct?

If it does, shouldn't you be able to select BOOTLOADER, and there by get it to read the zip file? (sorry if this has been asked before, just thinking aloud)
[Desire HD General] henv:
So I say that your commando fastboot getvar works. There is also a fastboot commando to go into bootloader.

Have you tried fastboot reboot-bootloader. Maybe then its possible to flash by PD98IMG.zip

Also did you try to downgrade radio to 26.03.02.26_M, that was my original radio when i bought it. Upgrade to the one you also use
[Desire HD General] henv:
This is the thread mentioned by Makbil http://xdaforums.com/showthread.php?t=842802
[Desire HD General] stuart0001:
Also tried 1.72 RUU but that also sticks at the "Updating User Data" stage

Opened the tool, selected the kernal but the next button stayed greyed out.

tried fastboot reboot-bootloader. The phone restarted but just to a Black HTC screen with a warning triangle in each corner.

I haven't downgraded radio but not sure how I could now.
[Desire HD General] leith51:
Just inboxed you go back to white screen with phone plugged in download the zip file from my thread double click start here type adb devices and report back what it reads

E=Mc2
[Desire HD General] henv:
this is the commando fastboot flash radio radio.img
[Desire HD General] stuart0001:
I get this:

D:\Stuart\Documents\Android\Desire HD Fix\Radio flash\Radio flash>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

D:\Stuart\Documents\Android\Desire HD Fix\Radio flash\Radio flash>
[Desire HD General] leith51:
So it could be you do have adb commands after all i read further back about pushing via adb the root and engs-off as you actually don't have fastboot commands I'm sure someone here will be able to give you list of commands on how to achieve that as I don't know how to

You can use that zip for most adb commands as far as I'm aware

E=Mc2
[Desire HD General] leith51:
If you didn't have adb it would have come back device error not found I should know it happened to me when I rebooted my laptop from scratch I had to wipe all the drivers to get it to the point your at now

So I would say try the adb commands instead of fastboot

E=Mc2
[Desire HD General] GurliGebis:
Just a crazy idea - do you get a shell if you type this?: adb shell
[Desire HD General] preacher65:
Ah, I thought it probably would, but someone in another thread with similar sounding problems had better luck with the later RUU. I'm out of ideas, but I'll keep an eye on the thread and chime in if I think of anything else.
[Desire HD General] makbil:
If the phone is locked to T-Mobile, non of the stock ROMs will work. The only option (apart from finding and flashing a T-Mobile ROM) would be to use the adb and try to correct the corrupt (or overwritten) areas. We need an adb expert.
[Desire HD General] robE9:
Hm, :) did you tried this ?

http://xdaforums.com/showthread.php?t=829780&highlight=t-mobile
[Desire HD General] stuart0001:
No :(

C:\AndroidSDK\platform-tools>adb shell
error: device not found

Thanks. I gave it a go but gets stuck at 40% again (at "Updating User Data" stage) :(
[Desire HD General] kudoboi:
i also bricked my prev motorola milestone.. thts y im nt gunna root my dhd
[Desire HD General] leith51:
Try using the zip file from my thread and type adb shell

E=Mc2
[Desire HD General] makbil:
Rooting is done at system level so it has nothing to do with this specific problem.
[Desire HD General] stuart0001:
Same as before

D:\Stuart\Documents\Android\Desire HD Fix\Radio flash\Radio flash>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
[Desire HD General] robE9:
well, did you installed htc sync?
[Desire HD General] ghostofcain:
Where are you trying to issue ADB commands to? It won't work whilst phone is in fastboot, just clutching at straws
[Desire HD General] stuart0001:
Yes

I can't change modes on the phone so I'm trying to connect as-is.
[Desire HD General] stuart0001:
I think I'm looking at damage limitation now as oppose to recovery.

I'm intending to give T-mobile a ring later and blame the OTA update. Is there anything more I can do to make the phone appear 'unhacked'?
[Desire HD General] robE9:
Well, usually clockworkmod recovery makes a folder on sdcard, so if you give them the phone take out the sdcard :D

btw, did you tried to flash a really old RUU? like 1.24.405.1 ?

http://xdafil.es/DesireHD/RUU/RUU_A....14b_26.02.00.29_M4_release_151852_signed.zip
[Desire HD General] stuart0001:
I'll give that a go tonight.

Can anyone confirm that T-Mobile have issued OTA updates for the DHD because I might look silly if I blame that and they haven't?
[Desire HD General] ToneyEricsson:
Probably safer to sound like a clueless consumer and say I switched on my phone this morning and get this error, its just not working ;)
[Desire HD General] ghostofcain:
Yeah appear clueless, don't admit to flashing anything, although as it does appear to be a hardware issue the flashing shouldn't really be an issue.
[Desire HD General] stuart0001:
I've phoned T-mobile and played dumb and they said they would send a pre-paid bag to send my phone back and they'll send it to HTC for repair.

Now whilst I could probably fool T-Mobile I'm worried that HTC will see it's been rooted/hacked and charge me for repair.
[Desire HD General] dr.m0x:
Just out of interest has anyone actually had a warranty claim denied because of hacking?

Sent from my super slick Android device.
[Desire HD General] ToneyEricsson:
I would just continue to play dumb even then, your still the consumer that's bought their product and might or might not be buying future handsets so I would expect a bull**** free level of service from them ;)

Back to this though modding with ROMs bothers me, I'm new to it and so far have only rooted and got S-OFF on my DHD just purely to get things like Adfree etc working. I'm happy with the stock Sense UI so that's my reason for not going further with ROMs and plus my DHD is new. This has confirmed my thoughts as to what could go wrong though.
[Desire HD General] leppie:
As I said before. There is no warranty on software on this phone. Read the EULA.

The fact the software messed up, whether it was you or by HTC, should not affect your warranty status on the hardware, if indeed it is a hardware issue (which IMO, sounds likely).

Good luck.
[Desire HD General] Basil3:
Just clutching at straws here, but what version of HTC sync do you have installed? I had all sorts of connection problems trying to root my phone with the latest version of HTC sync, had to be the version that came on the SD card.
[Desire HD General] oschlegel:
I was reading the last posts and with most stuff you where taking i had no ideea because im just starting with rooting etc.

I just wanted to say what a great community this is!

edit:

Oh and sry for the little off topic, but it had to be said...
[Desire HD General] audiavant:
stuart0001 I notice that jkoljo not have been involved in this thread, I would have send a PM to jkoljo and ask him for advice if you not have tryed that...

Good luck