Database Users

Bricked - help needed

OK, so I was trying to flash the Minimal Matte theme onto my N1, and I seem to have bricked the phone.
The phone now just sticks at the "X" logo when trying to boot.
I cannot access recovery - I get the exclamation mark.
I've tried download the Nexus One FRG83 system image from HTC and put it on the SD card and renamed it passimg.zip to try and get it up and running again - it did the update on the bootloader screen, but it hasn't helped.
Any ideas?

If your getting the exclamation mark, I would say the recovery has been lost somehow, and its on standard again.
Try re flashing recovery via fastboot, amon ra or clockwork, which ever one. Then re flashing whatever rom
Rellikzephyr
Sent from my Nexus One using Tapatalk

OK I've tried this and get the following
Code:
C:\AndroidSDK\tools>fastboot flash recovery d:\recovery.img
sending 'recovery' (2906 KB)... OKAY [ 0.415s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.813s
Any ideas?
ETA: I've tried several different recovery images to no avail.

tameracingdriver said:
OK I've tried this and get the following
Code:
C:\AndroidSDK\tools>fastboot flash recovery d:\recovery.img
sending 'recovery' (2906 KB)... OKAY [ 0.415s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.813s
Any ideas?
ETA: I've tried several different recovery images to no avail.
Click to expand...
Click to collapse
Did you unlock the bootloader?

Also, have you tried:
Code:
fastboot boot recovery.img

Try the nandroid back up in the recovery.

I've just unlocked the bootloader, and ran the command again and I can now get into recovery, and am now trying the CM6 ROM... so we'll see what happens...

And that has worked
Thanks very much for your help

tameracingdriver said:
And that has worked
Thanks very much for your help
Click to expand...
Click to collapse
Glad it worked out for ya ^_^

What size was the image that you've downloaded from HTC?
If it was ~5MB rather than ~90MB - you've downloaded an update, and not a full system image. That would explain why your phone wasn't working after applying it.

Jack_R1 said:
What size was the image that you've downloaded from HTC?
If it was ~5MB rather than ~90MB - you've downloaded an update, and not a full system image. That would explain why your phone wasn't working after applying it.
Click to expand...
Click to collapse
It was about 80ish Mb IIRC.

Hmm.. FRG83 Passimg.. Could you share it or a link to it?

Jack_R1 said:
Hmm.. FRG83 Passimg.. Could you share it or a link to it?
Click to expand...
Click to collapse
http://developer.htc.com/ 2nd link...
http://dl3.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip
That what you are looking for?

Yep Thanks. I'll try to see, why didn't this flash the system clean.

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] can't boot to recovery and can't charge when turned off

Hi everyone! here's my situation, my phone is turned off and when I try to charge it, it would have a solid orange light on the LED which is alright. But when I unplug the charger, the orange LED stays lighted and the only way for orange light to go away is to take out the battery.
Also, I cannot boot to recovery. It hangs on the T-mobile mytouch splash screen. I have a stock rom with 3.0.2.4.
Thanks in advance for answering!
EDIT: 3.0.2.4 is the clockwork recovery version and I can boot normally. just wanted to go to recovery and be able to charge while phone is off..

blue_algae said:
Hi everyone! here's my situation, my phone is turned off and when I try to charge it, it would have a solid orange light on the LED which is alright. But when I unplug the charger, the orange LED stays lighted and the only way for orange light to go away is to take out the battery.
Also, I cannot boot to recovery. It hangs on the T-mobile mytouch splash screen. I have a stock rom with 3.0.2.4.
Thanks in advance for answering!
Click to expand...
Click to collapse
Can you boot into HBoot/Bootloader/fastboot/Engineering Screen?
Do you have the Engineering Screen on the phone or the stock one?

thanks for the assistance! will try that now..

neidlinger said:
Can you boot into HBoot/Bootloader/fastboot/Engineering Screen?
Do you have the Engineering Screen on the phone or the stock one?
Click to expand...
Click to collapse
I can go to HBoot then fastboot and the selection at the bottom changes to bootloader, reboot, reboot bootloader and power down. if I select bootloader, it goes back to the initial screen.

blue_algae said:
I can go to HBoot then fastboot and the selection at the bottom changes to bootloader, reboot, reboot bootloader and power down. if I select bootloader, it goes back to the initial screen.
Click to expand...
Click to collapse
do you see an option for recovery?

yes, though selecting that would display the t-mobile my touch 4g screen and will just hang. same thing happens if I boot to recovery using rom manager.

blue_algae said:
yes, though selecting that would display the t-mobile my touch 4g screen and will just hang. same thing happens if I boot to recovery using rom manager.
Click to expand...
Click to collapse
Okay do you have the Engineering bootloader?
you top few lines of the Hboot screen should look like
Code:
GLACIER PVT ENG S=OFF
HBOOT-O.85.2007 (PD150000)

I have a slightly different one:
Code:
GLACIER PVT ENG S-OFF
HBOOT-O.85.2007 (PD1510000)
or was it a typo error? thanks again for the help!

blue_algae said:
I have a slightly different one:
Code:
GLACIER PVT ENG S-OFF
HBOOT-O.85.2007 (PD1510000)
or was it a typo error? thanks again for the help!
Click to expand...
Click to collapse
are you talking about the - / = deal?
Then yes it was typo.
okay we need to flash you a recovery...
this is a simple process.
make sure you have ADB installed on your computer
[use the link in my signature if you don't]
once you have it up and running plug your phone into the computer
boot in hBoot
then download the attachment and store just the recovery.img to the tools folder of your SDK if you have the entire SDK, or the c:\adb folder if you use True_blue's
once you have done that change your target folder to the folder where you stored the recovery.img and type
Code:
fastboot devices
you should see your serial number
if you do see it type
Code:
fastboot flash recovery recovery.img
you should see something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if you do navigate to "recovery" and select it.

This is what I have:
Code:
GLACIER PVT ENG S-OFF
HBOOT-O.85.2007 (PD1510000)
Regarding the typo, I was pertaining to hypen (mine) against an equal sign (yours) and PD151000(mind) to PD150000(yours).
do I have the correct values?

blue_algae said:
This is what I have:
Code:
GLACIER PVT ENG S-OFF
HBOOT-O.85.2007 (PD1510000)
Regarding the typo, I was pertaining to hypen (mine) against an equal sign (yours) and PD151000(mind) to PD150000(yours).
do I have the correct values?
Click to expand...
Click to collapse
Yes you do. you can flash a recovery image like i mentioned above.
I was going off memory, i didn't physically boot in HBoot.

Thanks mate! That worked! I can now boot to recovery. will try charging while phone is off in a bit.
btw, what went wrong? my new recovery file (3.0.2.4) was not supported?

blue_algae said:
Thanks mate! That worked! I can now boot to recovery. will try charging while phone is off in a bit.
btw, what went wrong? my new recovery file (3.0.2.4) was not supported?
Click to expand...
Click to collapse
I have no idea what went wrong. I do no trust flashing recoveries via Clockwork ROM manager for that very reason i typically download the recovery then flash it via ADB commands. to risky in my way of thinking.
just make sure to update your recovery that version is 3.0.0.6.

ok, will update it now as well. can I use any recovery version 3.0.2.4? I mean that version can be found on various threads for different phones on this board. do I just pick one or it should be made for mt4g?

blue_algae said:
ok, will update it now as well. can I use any recovery version 3.0.2.4? I mean that version can be found on various threads for different phones on this board. do I just pick one or it should be made for mt4g?
Click to expand...
Click to collapse
Here. this is the one i pulled off my my phone.
just flash it like you did the other one and you'll be a-okay.

cool! thanks mate for the updated recovery. I've just tried charging my phone while turned off and I was able to. really great.
btw, where do you get the recoveries? I don't want to get it from rom manager moving forward.

blue_algae said:
cool! thanks mate for the updated recovery. I've just tried charging my phone while turned off and I was able to. really great.
btw, where do you get the recoveries? I don't want to get it from rom manager moving forward.
Click to expand...
Click to collapse
well i have ROM manager on my phone, but i use it to download the ROM to my SDcard then flash manually from their. it's a little more work but it's worth to me.
From what i've been putting together i think Koush is putting a web site together and we can just snag them from there. But that is just rumors as of now.

Same Phone But......
neidlinger said:
are you talking about the - / = deal?
Then yes it was typo.
okay we need to flash you a recovery...
this is a simple process.
make sure you have ADB installed on your computer
[use the link in my signature if you don't]
once you have it up and running plug your phone into the computer
boot in hBoot
then download the attachment and store just the recovery.img to the tools folder of your SDK if you have the entire SDK, or the c:\adb folder if you use True_blue's
once you have done that change your target folder to the folder where you stored the recovery.img and type
Code:
fastboot devices
you should see your serial number
if you do see it type
Code:
fastboot flash recovery recovery.img
you should see something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if you do navigate to "recovery" and select it.
Click to expand...
Click to collapse
Hi brother,
hi have the same phone with same problem but boot is different.
GLACIER PVT SHIP S-OFF
HBOOT-0.89.0005
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Apr 14 2011,13:18:22
but when i put recovery i get this error.
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (3426 KB)... OKAY [ 1.156s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.172s
Where is my falt or what else i can do
Need please help
Thanks
Br, Raja

You have the 2.3.4 gingerbread update which there is no official way to root it yet...what you must do is downgrade to froyo 2.2.1 and then root from there. Seeing as how you found this thread, I know you are one of the few who know how to search-there are several threads about downgrading and think it is in the wiki as well...
Edit: Just noticed you were s=off-were you rooted before?

Cant flash recovery

My Hero come from service center clean and updated to latest RUU so i trying to get custom bootloader.
First i try to downgrade Hero to 2.73.405. But on my computer with Win7 fails with error 171. Then i tried on friend machine with Win XP and there i got error 140. I tried RUU from xda ftp and one from HTC and after this fails i tried other RUU from xda ftp. (i created and have gold card)
After that i try different approach. I rooted Hero using one click apk and then use latest flashrec. Flashrec gives me error "Flash FAILED: Could not run command."
After that i tray this:
Code:
C:\and\platform-tools>adb shell reboot bootloader
C:\and\platform-tools>fastboot boot rec.img
and i got this error
Code:
downloading 'boot.img'... FAILED (remote: not allow) finished. total time: 0.000s
if i try
Code:
C:\and\platform-tools>fastboot flash recovery rec.img
sending 'recovery' (3972 KB)... FAILED (remote: not allow) finished. total time: 0.000s
I maybe do i very very stupid thing and extracted flash_image from some Hero ROM and using cat put it in /system/bin/
I am desperate and i don’t know what to do next.
Hero:
3.36.405.1
HBOOT 1.76.0007 (HERO 1000)
Radio 6.35.15.11

try this
run cmd
cd C:\and\platform-tools>
fastboot boot rec.img
i am not sure about it

Try place recovery on your SD card, name it recovery img. Then run via terminal or adb:
su
flash_image recovery /recovery.img
reboot recovery
Press enter after each line
sent with love from me to you

Habarug said:
Try place recovery on your SD card, name it recovery img. Then run via terminal or adb:
su
flash_image recovery /recovery.img
reboot recovery
Press enter after each line
sent with love from me to you
Click to expand...
Click to collapse
It says ran out of memory :/ It's very annoying I've had the same problems as op and still can't do it.

Did you use goldcard to downgrade? AFAIK all bootloaders from 1.5 were locked down. Is error 140 mismatched. CID? If it is, you need a goldcard.
EDIT: just noticed you said you made a goldcard. Are you sure it stuck? Some sdcards aren't suitable for being a goldcard.
Sent from my GT-I9100 using XDA App

[I9020] cannot flash stock firmware anymore

Hi all,
I have a samsung nexus s GT-I9020 ( no rooted , no custom recovery ) and 1 week ago I received the OTA update for Ice Cream Sandwich. I updated but, after 1 week usage, I noticed serious issues with the battery. So I decided to revert back to gingerbread, by downloading a stock firmware 2.3.2-GRH78C nandroid backup and trying to do
fastboot flash boot boot.img
fastboot flash system system.img
and so on.
But I do have a problem here. When, in fastboot, I first ran fastboot flash boot boot.img I got an error on the terminal
sending 'boot' (8192 KB)...
OKAY [ 1.185s]
writing 'boot'...
FAILED (remote: Write Fail)
finished. total time: 1.191s
Click to expand...
Click to collapse
and on the phone screen I can see
FAILED exceed blocks 0x0000001e > 0x0000001c
Click to expand...
Click to collapse
Similar error happens if I try the system partition, with the following error on the terminal
sending 'system' (151476 KB)...
OKAY [ 22.184s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 22.189s
Click to expand...
Click to collapse
and on the phone screen
Invalid Magic Code 0x00000003
The phone now has a recovery image ( clockwork ) which I have been able to install, but this is not able to browse any of the filesystems available. So I was looking at some stock img files I could flash via fastboot, At the moment the phone just hangs at fastboot mode saying no boot image is available.
I am using a ubuntu oneiric 32 bit and I have the latest android sdk tools.
This is not the first time I flash images using fastboot and I really have no idea why this is happening. It might be because my android version was icecream ? I have never had issues when flashing different versions of gingerbread. Also I used the encryption feature of icecream sandwich, if this is useful for you to know.
Thank you very much, hope someone can help me with that.
Click to expand...
Click to collapse

Maybe u got bad downloads try redownloading the files and make sure u have the boot loader unlocked first.
Sent from my Nexus S 4G using xda premium

I would suggest trying to fastboot boot cwr and flashing a zip.
Sent from my Nexus S using xda premium

I cannot use CWR to flash it.
The reason is: I can start CWR but the nandroid backup I got from xda developers is not on the nexus s itself. Moreover CWR cannot browse the contentes of the sd, it says cannot open device.
Regardig the files, I have issued md5sum and they seem all right.
I am really struggling with it.