Database Users

My DHD is nearly bricked. Please help.

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.

you cant just flash rom via ADB. you need recovery. Do you have clockwork mod recovery?

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

20mark said:
you cant just flash rom via ADB. you need recovery. Do you have clockwork mod recovery?
Click to expand...
Click to collapse
I used to but it's been wiped as part of the the failed RUU installation. Power On/Vol Down now does nothing
ghostofcain said:
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
Click to expand...
Click to collapse
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.

I've just tried jkolo's easy S-Off tool but I get an error message pop-up "Module or hboot fail. Aborting."

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.

EmprtArea said:
So what happenes when you choose the recovery option?
Click to expand...
Click to collapse
I don't have a recovery option on the Phone.

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

EmprtArea said:
So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
Click to expand...
Click to collapse
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

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.

EmprtArea said:
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
Click to expand...
Click to collapse
No luck
Code:
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

Everytine you try writing it fails what else can you do?
Sent from my Desire HD using XDA App

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

If you lost s-off while flashing the 1.32 rom then I also suspect you lost root.
Sent from my Desire HD using XDA App

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
Would T-Mobile exchange or repair under warranty, despite the mods I'd made?

Aamir.Badat said:
If you lost s-off while flashing the 1.32 rom then I also suspect you lost root.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'm starting to regret trying that as a solution now

I remembered something similar being posted on these forums a few months ago, so I had a search and found this thread:
http://forum.xda-developers.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.

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.

this sort of thing doesnt happen if you are flashing custom roms though right? its making me nervous now!

preacher65 said:
I remembered something similar being posted on these forums a few months ago, so I had a search and found this thread:
http://forum.xda-developers.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.
Click to expand...
Click to collapse
Thanks for the tip. I'll have a read and may give that a go.
KamikaZeeFu said:
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.
Click to expand...
Click to collapse
I don't get errors, the RUU just freezes and I have to pull the plug.
danrobz said:
this sort of thing doesnt happen if you are flashing custom roms though right? its making me nervous now!
Click to expand...
Click to collapse
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.

[Q] nexus 7 wont update, fastboot fails, recovery no go

When i had my nexus 7 i updated to 4.2.1 and then did a factory reset. Upon booting my nexus was back on android 4.1.2(i thought this shouldnt have happened?)
Now the OTA update wont install - i get the dead android with an exclamation mark.
I have downloaded the nexus 7 toolkit to try and unlock the bootloader and flash stock 4.2.1 but i get an error when trying to unlock - FAILED (command write failled (unknown error))
anyone able offer some help please?

ive tried fastboot oem unlock using nexus toolkit and direct through the command line with same results

is this guide any good?
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html

Otherwise you have this GUIDE
Phone:I9100P
Kernel:Dorimanx
ROM:4.2.1 Vanilla RootBox
Tablet:Nexus 7
Kernel:M-Kernel
ROM:4.2.1 AOKP PUB
MOD:JusTunBean

welly_59 said:
When i had my nexus 7 i updated to 4.2.1 and then did a factory reset. Upon booting my nexus was back on android 4.1.2(i thought this shouldnt have happened?)
Now the OTA update wont install - i get the dead android with an exclamation mark.
I have downloaded the nexus 7 toolkit to try and unlock the bootloader and flash stock 4.2.1 but i get an error when trying to unlock - FAILED (command write failled (unknown error))
anyone able offer some help please?
Click to expand...
Click to collapse
It is possible (albeit very slightly) that the file didn't flash correctly, but did corrupt the bootloader just enough to stop it being unlocked/booting into recovery.
If you can't issue the 'fastboot oem unlock' command then it could be for 2 reasons:
1. It is already unlocked (try typing 'fastboot oem lock' and see if it re-locks')
2. The bootloader is slightly corrupt.
Hopefully it is the first one

liamwli said:
It is possible (albeit very slightly) that the file didn't flash correctly, but did corrupt the bootloader just enough to stop it being unlocked/booting into recovery.
If you can't issue the 'fastboot oem unlock' command then it could be for 2 reasons:
1. It is already unlocked (try typing 'fastboot oem lock' and see if it re-locks')
2. The bootloader is slightly corrupt.
Hopefully it is the first one
Click to expand...
Click to collapse
i managed to get it working after erasing everything as in the guide above. I had to keep unplugging the device and trying again though and after a few attempts it worked

when encountering this error i simply cycled through the options (using volume) and said boot into bootloader, familiar windows device dis/connect and then tried the fastboot flash boot boot.img cmd again, worked a treat, currently flashing the system part.
hope this helps!

Can't flash firmware, HELP!!!

At one point in time the capacitive buttons ceased to respond to any kind of interaction so I decided to flash a custom rom, which did not solve the problem so I flashed a stock image. Now whenever I boot the phone it loops "Unfortunately, Setup Wizard has stopped working". I tried to reflash countless times the stock firmware, both Marshmallow and Lollipop via fastboot, but everytime I execute "fastboot flash partition gpt.bin", "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" in command prompt, it says "(bootloader) Preflash validation failed FAILED (remote failure)" and the phone remains in the same state as before. I've tried everything that got through my head and I don't know what to do....please HELP!!!!!

adrianglont said:
At one point in time the capacitive buttons ceased to respond to any kind of interaction so I decided to flash a custom rom, which did not solve the problem so I flashed a stock image. Now whenever I boot the phone it loops "Unfortunately, Setup Wizard has stopped working". I tried to reflash countless times the stock firmware, both Marshmallow and Lollipop via fastboot, but everytime I execute "fastboot flash partition gpt.bin", "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" in command prompt, it says "(bootloader) Preflash validation failed FAILED (remote failure)" and the phone remains in the same state as before. I've tried everything that got through my head and I don't know what to do....please HELP!!!!!
Click to expand...
Click to collapse
Moto x pure edition doesn't have capacitive buttons... But anyway, motos don't like to be flashed to an older firmware. Your going to need to flash what firmware that you had or newer. I'll edit with a link to a thread with nearly all the released firmwares. Just follow the instructions and it should work. Keep in mind that the command erase userdata completely wipes internal storage.
Edit: excellent thread to save from @gokart2
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833/page28

ffejy462 said:
Moto x pure edition doesn't have capacitive buttons... But anyway, motos don't like to be flashed to an older firmware. Your going to need to flash what firmware that you had or newer. I'll edit with a link to a thread with nearly all the released firmwares. Just follow the instructions and it should work. Keep in mind that the command erase userdata completely wipes internal storage.
Edit: excellent thread to save from @gokart2
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833/page28
Click to expand...
Click to collapse
I suppose there is no problem in flashing a Pure firmware on a Style as long as I flash the Style modem right?

adrianglont said:
I suppose there is no problem in flashing a Pure firmware on a Style as long as I flash the Style modem right?
Click to expand...
Click to collapse
I'd search for the proper firmware rather than hoping that it'll work. It would have been helpful to include your model in the op.

adrianglont said:
I suppose there is no problem in flashing a Pure firmware on a Style as long as I flash the Style modem right?
Click to expand...
Click to collapse
It doesn't work, the boot partition (kernel) and radio firmware must match with the EFS or no service.
You should find the correct firmware package and flash as a whole, most people who try to cobble together a working firmware with parts of various models wind up with a soft-brick condition or no service.

Cannot flash twrp?

So i can get the phone detected by fast-boot just fine now but I cannot flash anything it keeps giving me errors like "To many links" or "FAILED (Write to device failed (Unknown error))" ?
Am I missing something that I should've done first, the errors are obviously not very descriptive of what the issue could be.
So the bootloader is already unlocked and I am trying to use "fastboot flash recovery twrp.img"

Fixed here: https://android.stackexchange.com/q...e-failed-no-link-unknown-error-too-many-links

General Help - My Nothing is stuck in a boot loop after attempting to root it

I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?

Did you try this? https://forum.xda-developers.com/t/how-to-unbrick-nothing-phone-1-fastboot-bootloop.4501439/

@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?

nike1 said:
@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?
Click to expand...
Click to collapse
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant

itsTarec said:
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant
Click to expand...
Click to collapse
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully

nike1 said:
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully
Click to expand...
Click to collapse
Is your device rooted now? Or did you just fixed the issue?

nike1 said:
I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?
Click to expand...
Click to collapse
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.

lucy1983 said:
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.
Click to expand...
Click to collapse
Aha, I see. That wasn't clear to me. I thought i needed a full package and not just an incremental one, that's why I went for 1.1.7. I did patch it with Magisk though, just the wrong version i guess. But all is well now, the phone's fully working afaict. Thank you for clarifying what went wrong!