yashsingh1/xdaforums huggingface dataset:
[Nexus One General] Andrewtst:
Hi, I follow exact the what it suppose to do until the part during flashing the custom firmware, it said successful, so I choose restart the phone. During before reboot, the screen got message mention writting boot loader somethign like that.

I wait till it finish and it restart and appear a icon in the middle, I seen this before during I entering the recovery, I though it is something wrong as it stop there quite long.

So I unplug the battery, when insert back the battery, the phone is totally cannot on at all. Help!

I try below few step also not working:

- Power on = not working

- Power + low volume button = not working

- Power + Track Ball = not working

- Power + low volume button + track ball = not working

- Plugin to PC, no indicator light

- Charge using charger, no indicator light.

What shall I do now

** The phone already root, success run the Amon-Ra recovery image, I am using this Amon-Ra recovery image to flashing the ROM.
[Nexus One General] Worsty:
Your phone is not bricked if you can get to Amon-Ra. Just wipe and reflash the custom rom again. If same issue persist, download a new copy to try. The earlier file could be corrupted.
[Nexus One General] mattyboy247:
That sounds to me like a brick. If it won't turn on at all, then it be dead. Are you sure you put the battery in right?
[Nexus One General] superGOAT:
Ouch, I personally want to know exactly what you were doing before the phone bricked, and subsequently NEVER DO THAT TO MY PHONE.
[Nexus One General] Worsty:
The Nexus One wouldn't brick unless he flashed the wrong radio right? If he's just messing with the roms, regardless of what he did, there should always be a fix. Especially if he can get to Amon-Ra, although he did say he can't get the phone to power on..
[Nexus One General] mattyboy247:
I can tell English isn't his first language (I hope)... but it sounds to me like he can't power it on at all. Nothing works to turn it on. No lights turn on when he plugs it in. Sounds like the makings for a brick. Only thing I can think of that might make it work is if the battery is somehow in wrong. But I could be wrong about that too. For his sake, I hope its something simple like that.

And he said he was in the middle of flashing something and pulled his battery while it was showing it was flashing . The way he described it (if I am reading him right) sounds like when the radio was being flashed.
[Nexus One General] Andrewtst:
Sorry for my bad English, I understand what the instruction write, this is the 1st time I facing such issue after so many times break the wall, I have done before for friend iPhone 3G, my iPod touch, OMNIA II, K750 and etc, never fail before.

Below is the step I have done:

1. Root the phone - success.

2. Play around with fake US Operator for Market - success

3. Flash the Amon-Ra v1.62 recovery image - success

4. Logon to Amon-Ra recovery and do nandroid backup - success

5. Flash the ERE36B ROM - success

6. Flash the ERE36B / 32.26.00.24U_4.04.00.03_2 radio - FAIL, my phone die here.
[Nexus One General] kingklick:
this is why i didnt flash the radio :(
[Nexus One General] komos:
i ve flashed this radio and work just fine

how did you flashed it

i mean through recovery(apply zip)

or adb,fastboot?
[Nexus One General] Andrewtst:
How I know it could be until cannot on at all. Haizz................

I just buy on 26/Feb/2010 = 4 days! :confused:
[Nexus One General] Andrewtst:
through recovery, apply zip and it show success flash. After that when reboot, it hang a second then mention written bootloader. I have no idea about that.
[Nexus One General] seraph1024:
The only time N1 can be bricked is by

a) flashing a radio that is either wrong (all radios are ok at this point to flash)

b) flashing a bad radio (check md5 before flashing)

c) or power died while radio flash.

It is HIGHLY recommended that you have a full battery charge AND powered up the phone via power/usb while flashing radio.

Seem like a bad radio flash (either md5 is bad) or you restarted while radio is still flashing (it take a while for radio to flash).

If it is truly bricked, you can send it in and HTC CAN reflash the phone for a fee.
[Nexus One General] seraph1024:
Its normal. Did you reboot that phone again? That's a no no. The phone will reboot after it is done writing radio image.
[Nexus One General] Andrewtst:
After success, it reboot and appear "!" screen and hanging there. I wait for around maybe 10mins..then I unplug the battery and after that, it no longer able to on.
[Nexus One General] briangnyc:
Usually after I flash a new radio, the phone will reboot back into recovery and have a message on the bottom and I believe it says writing boot image or something like that. I go back up to the recovery menu and select reboot and it reboots and the phone is backup and running.

Sounds like the process didn't complete and you pulled the battery while the radio was being written.

If you have no power to the phone and can't get into recovery then sounds like you are going to have to send it in for warranty or something. Will HTC really know if the phone is rooted or not since it's already a brick? They would probably just send you a new one if you say it won't turn on. Somehow I imagine a big pile of phones and it gets tossed on the pile, LOL....But I could be wrong :-)
[Nexus One General] shmigao:
you pulled the battery during flashing the radio. (as you mentioned in your

that's the biggest "no no" and probably has caused the failure

I always find flashing the radio quite intimidating, because it seems hanging for a moment, then restarts by itself, writes the radio, then hangs a little and restarts.... those frightening moments.

i think you have a brick there quite honestly - you may want to send it in and have it replaced (hope they will).

tell us how it went. good luck

An alternative would be to try to sell the phone/brick to someone who would like to by it for spare parts (via Ebay)

p.s. i hope nobody now will start a discussion whether or not HTC or Google will actually replace the phone because the bootloader was unlocked... this discussion is not what the OP needs now.
[Nexus One General] shmigao:
oh, seraph1024 said it already:

If it is truly bricked, you can send it in and HTC CAN reflash the phone for a fee.

you can try that
[Nexus One General] paratox:
i think it`s better to flash radio via fastboot. there you will see, if the flash is really finished. and always check md5 before flash!
[Nexus One General] Worsty:
Personally, i feel there's really no reason to flash the radio updates thus far unless one is based in the States.

Don't know anyone suffering from poor 3g reception elsewhere besides those over there. Not that it stopped me from flashing it just to see if there's any difference between them.

Hopefully you'll be able to have HTC fixing your bricked phone.

Good luck
[Nexus One General] martin0285:
painful, sounds like first real brick huh?
[Nexus One General] rotohammer:
I don't recall what my screens said when I flashed the radio, but for it to mention writing bootloader doesn't seem proper. The bootloader is one area you want to avoid flashing to.

Edit: seraph1024 notes earlier that its a normal message.

My suggestion is to give a few more folks here time to review your problem. If there is a solution, you don't want to make it any worse.
[Nexus One General] dehnhaide:
Welcome to the graveyard of ignorance!

Hi Andrew,

I am sorry for being harsh on you an your situation but your phone is BRICKED 100%. The only way to bring it back is to find smbd that's got a JTAG interface + the needed software + pray that he/she knows the JTAG pins on such a new phone as Nexus One (very, very feeble chances!) + directly access eprom and reprogram the boot-loader!

Ooooohhh yes! It is the boot-loader that you ****ed up with. I could bet my new Nexus One on that fact that, out of ignorance & haste, you've rushed in and (squeeze your memory and you'll see I am right!) did:

"fastboot flash boot radio.img" instead of "fastboot flash radio radio.img"

And that happened because you got used to flashing your recovery/system with Amon/Cyanogen and, as a plus, I could see a lot of places on forums where other dumb-heads rush in teaching the users to brick their phones by misleadingly typing "fastboot flash boot whatever_radio_firmware.img" instead of "fastboot flash radio ...".

I petty you but you phone is dead for good. Next time pay more attention to whatever you're typing in.
[Nexus One General] rotohammer:
I hate the solitude of the graveyard of ignorance :)

Being somewhat ignorant myself, I was wondering if the recovery system is still available to reflash the boot loader. Although, if the radio image was big enough, I guess it could have taken out the bootloader and recovery areas of the flash.

Does recovery mean "recover OS only"?
[Nexus One General] Gr8gorilla:
I would guess that he was using Amon Ra. I would also guess that while flashing the Radio he got Impatient. It takes maybe 3-5 minutes to flash the radio and like 1 min to flash anything else.

He thought the phone hung up and he pulled the battery during the radio flash.

You never, Never, Never, Never, let your phone power down when flashing a radio. Radios are brick territory, roms are safe.

I am very sorry to hear of your problem. When you get your device back from HTC after they charge you for reflashing it, be patient. Take your time.

You have learned a hard lesson.
[Nexus One General] Andrewtst:
Thanks for all the concern, wish me good luck, report back shortly.

I am flashing the Radio using Amon RA not the fastboot.

After reading all, I believe is my impatient and due to halfway taken out the battery, it make my phone sleeping now. :(

Can't believe it just brick like that. Sorry.........

The too earlier success message make me wonder it is finish. Wish HTC can save me for this lesson.
[Nexus One General] martin0285:
I'd call them, tell em you got the "OTA update" and while it was in the process the battery died....You maybe able to get a new phone or have them re-program it if you can convince them you flashed there "OTA" update.....
[Nexus One General] Gr8gorilla:
That is an interesting idea and it may work, I dont know. Does the OTA warn of not pulling battery and self check for battery status?
[Nexus One General] deprecate:
So take it one step further...

"I was in the process of updating my phone with some update that it said I had to have. I made sure to plug my phone into a wall outlet so there was no chance of it powering off. While the phone was updating (not sure what it was doing) we had a quick brown out followed by a total power loss in my house. Not sure what happened but when I looked at my phone it was off. I tried to turn it back on but nothing was happening. A friend suggested I contact you since my phone is less than a week old...help?"

Worth a shot...always play stupid and scared...
[Nexus One General] gIMpSTa:
+1 to this idea. It certainly can't hurt to try and the stupider you sound about it on the phone the better chances you probably have. Start mentioning OTA update, bootloader, radio, etc they are probably gonna laugh at you.
[Nexus One General] FettsVett:
You know, you say this but I think he _should_ have to pay to have it re-flashed. It's not HTC's fault, why should they have to pay someone to fix something that he broke & pay for shipping both ways?

For that matter, this was bound to happen - we have people who don't have any clue what they are doing or what the risks are skim over developers warnings all the time. I'm sure that there are notes EVERYWHERE about not removing the battery during a radio flash - some people just need to learn the hard way to read about what they are doing. Yeah it sucks, but there are going to be many more of these in the future and they should pay for their mistake.
[Nexus One General] martin0285:
You are right.... I was just sharing an idea I would do if I ever bricked this beast!! But like others have said, you play dumb you can get along way.
[Nexus One General] SiNJiN76:
I've read this warning before...but never asked how to check the md5...How do you check it?
[Nexus One General] sp00nfedem1:
ive had this same problem, pulled my battery for a few minutes, then put back in .. no problems after that, went into recovery mode PERFECTLY!
[Nexus One General] j2eubank:
Assuming you are in windows here (http://www.pc-tools.net/win32/md5sums/) this makes it pretty easy (I am sure there are plenty of other tools out there as well).

If running linux cd to the directory with the file and md5sum [file name]
[Nexus One General] deprecate:
I agree that if anyone bricks their phone, they should be held responsible for their actions; especially with something that was so easily avoided.

In all areas of the world though, people will rush to have the latest/greatest thing without reading any of the warnings or taking the few precious moments to ensure they are using correct syntax (radio instead of boot if that is in fact what he flashed the radio.img to).

Hopefully this is a lesson that everyone can learn from...just pay a little more attention and ask questions before it's too late. There may be some seriously grumpy-pants types on this site but deep down inside, they are willing to help as long as you have searched before asking a question asked a zillion times.
[Nexus One General] Amdathlonuk:
Hmmmm............

I've been flashing for 2 years and NEVER checked an MD5sum, just lucky I guess.
[Nexus One General] gtrplr71:
I agree I read for 2 months before rooting my g1 and still read everthing I can find before flashing anything.PERIOD
[Nexus One General] superg81:
i don't post much but gonna make a quick comment here.i have found there is an issue with the nexus "not recognizing "a power source.mine did it the first day,before unlocking bootloader and rooting.i had shut it off,it didnt wanna come back on--at all.i would plug to a 110v source and no light.plug into computer and no light.after a few minutes of profoundly swearing it decided to boot up.should have sent it straight back but didnt and rooted anyway.it has happened a couple of times since.i pull battery,sdcard and simcard per htc tech suggestion and it boots back up.this guys problem could possibly be unrelated to the radio flash and something else is going on.just my 2 cents...back to me corner :cool:
[Nexus One General] Gr8gorilla:
He clearly said that he pulled the radio while flashing the radio. What is the debate about?

What happens if you pull the battery while flashing the radio?

BRICK!
[Nexus One General] rotohammer:
I always thought the only way to brick a phone was to overwrite the bootloader, or pull the batter while writing the bootloader, and that if a radio fails to flash, you just give it another go, since you're flashing from the bootloader.
[Nexus One General] Gr8gorilla:
as far as I know, when flashing android, the radio and spl are when you get into "brick" territory. I believe, (and I may be wrong, likely in fact) that the radio is writing in the boot area.
[Nexus One General] FettsVett:
I'm pretty sure that the bootup process for the phone is Radio -> IPL/SPL -> OS

If you bork the radio the hardware doesn't even know how to initialize the IPL/SPL and if you bork the IPL/SPL you can't interact with the phone via fastboot which means that its basically a brick anyways. (Unless you have a JTAG interface so you can flash the images directly to hardware)

Flashing 'radio-*.img' to the boot partition shouldn't have any effect on the IPL/SPL. On production devices they are in protected memory and cannot be overwritten unless there is a signed update from HTC. (That's the issue the community is having with producing a 're-lock' for the boot-loader)

Basically, he couldn't have done anything to his boot-loader (and if he did, we'd want to know how!)
[Nexus One General] myplague:
New forum rules idea

off topic but this thread is in the wrong section anyway

How about XDA set up a limit on the development forum that anyone over 100 posts can add a thread. However if you are under 100 posts and want to add a thread you can submit it but will not appear until a mod accepts it first.

Just my two cents!
[Nexus One General] FettsVett:
You're not the first person to put this sort of plan out there. As others have said, it would be against the ideals of the community, and there have been many developers who have contributed big things that didn't have a large post-count when they did. Cyanogen is one example that's been brought up.
[Nexus One General] unchainedrssr:
The Nexus One has an issue with the power button breaking relatively easy.
[Nexus One General] elite67:
I've gotten the same issue as you only happens when bootloader was unlocked I was about to swap out my device looks like im not the only one with this problem.
[Nexus One General] Gr8gorilla:
I will only say this one more time:

NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER

EVER POWER OFF YOUR PHONE WHILE FLASHING THE RADIO!

IF YOU DO THIS, YOU WILL CRY!

IF YOU DID THIS. YOU BRICKED YOUR PHONE!

ALWAYS FLASH RADIO AT FULL POWER WITH IT PLUGGED IN TO THE WALL CHARGER!

IF YOU CANT FOLLOW THESE INSTRUCTIONS DO NOT FLASH THE RADIO!
[Nexus One General] carnegie0107:
Quoting for emphasis. Do not, ever, EVER pull the battery when you see that symbol. Even if it's on the screen for an hour. When writing the radio, let it finish. And make sure you have a full charge, or better yet, are plugged in to the charger, so your battery doesn't die. IPL/SPL and radio flashing are where you brick. That sounds like what the OP did. Can't get into recovery, fastboot, anything? That's a brick, and the best thing you can do is keep the battery as a spare for your new phone, because this one is a paperweight from now on. I'm very sorry.
[Nexus One General] karthikjr:
<Even if it's on the screen for an hour?>

I've been flashing radio updates since the G1 days, and have not run into

any problems with anything. But just the other day, on my NexusOne, post

flashing the radio update that came in around the ERE36B app update,

the phone stayed on the Nexus One -X- screen for 45 minutes. I just

let it sit there, and fretted away to glory, assuming that I'd killed the

phone. At the 45th minute, I figured no radio update can take this long,

and pulled battery (phone was on wall charger). Then I literally pulled

the plug. And rebooted.

I'm still here, with the very same Nexus One, rocking the latest Cyan update.

Either I was incredibly lucky back there, or I did the right thing.

So, yes, do NOT pull your battery/interrupt the phone just after you

flash a radio update. But waiting for an hour? Seems excessive to me.

_____________

Can anyone tell us why some phones, sometimes, tend to take so long

with the radio update? I'm guessing it's hardware specific, yes?
[Nexus One General] Gr8gorilla:
In your case, you pulled the battery after the phone had completed the install. It reboots twice during a radio flash I believe. He pulled his during the first reboot. Anyway, glad to see you didnt get a paper weight!
[Nexus One General] air2k57:
For me, I've had horrible texting issue on T-Mobile using stock radio. Half the time my phone would.freak out and refuse to send texts. Only solution wad reboot, very annoying. Radio update fixed that, I'm very happy!

As far as people saying he pulled the battery too soon, I doubt it. Heat it does hang on the ! Screen foot awhile, but it rarely take more than couple of minutes. It then reboot into recovery and whatnot. My guess is that the radio file was bad and something pricked it. If the Rom didn't flash well, he would still be able to power the phone on with trackball + power button combo. If he can't even get into that, nothing you can do.

I've had an issue where my phone refused to power on using that combo, had to pull the battery for few minutes, which solved it.
[Nexus One General] Jackasaur:
Well if the phone doesn't turn on then it's bricked. I had the same issue. I was updating and pulled the battery. The only thing you can do is call HTC and tell them that you think you bricked it. :P Sorry for your lost mate.
[Nexus One General] Andrewtst:
Did HTC charge you? How much it cost?

I already send over to HTC service center, now I am waiting (hope is good news) from them within this 3 - 4 days.
[Nexus One General] uansari1:
Agreed.

I'm one of these "grumpy-pants" types. I'm totally willing to help but can't STAND it when people post a new thread about something that's sitting on the next page and could have been found with a search. In fact, often times I'll ignore them at that point.
[Nexus One General] Andrewtst:
I open a new thread as I search around and never seen anyone facing the same issue as mine, where is totally cannot turn it on.

I notice some saying "I deserved and need to paid" If this case happen to you, I don't think you will saying this anymore. I do read and follow properly, maybe I am just unlucky enough make the phone brick. I am not purposely bricked it for fun.

I post just hope any genius knew the way to turn it on back before sending to HTC or any advise, and maybe some precaution to new user to prevent happen agains any phone being true brick.

I always believe "Helping each others" is a good manner. This is the reason of having such community, what the point if it just for talking un-helpful things, one day you may face also others difficulty and I believe you will feel great when someone holding a hand.
[Nexus One General] carnegie0107:
It's not that you deserve to be punished for your mistake. We're all very sorry for your loss. However, when you root, you accept the fact that you are voiding your warranty, and every ROM thread you find makes it clear that any harm done is YOUR fault. By rooting, you accept responsibility for any damage. If you brick, you should of course have to pay to have it fixed. That's the deal with unlocking the bootloader. If you lie to HTC, they will most likely discover it and charge you anyway. So just be honest. Trying to blame your damages on the hardware manufacturer hurts development--situations like that are why manufacturers lock down their devices and discourage hacking. So man up, pay for the repairs, and learn your lesson. And hopefully some other noobs can learn from it, too. Never, ever pull the battery during a radio flash.

And no, writing the radio won't ever take an hour. I was exaggerating for emphasis. But seriously, wait an hour before you give up, just in case. Letting the radio finish is so important I can't stress it enough.
[Nexus One General] Andrewtst:
I didn't even lie to HTC and not plan to, I just scared they are not willing to do it even I willing to paid.
[Nexus One General] meric04:
Surely the OP has had enough advice on the perils of flashing phones?

I for one hope that he gets his phone fixed with minimal pain/cost, and that the experience doesn't completely crush his interest in modding.

I'll close with this...
[Nexus One General] jakontil:
hi anything for the MAC to check md5sum?

sorry for the bricked N1 hope everything goes well
[Nexus One General] liam.lah:
So are you saying it could be possible to re-lock the bootloader if someone was able to get a 'leak' of a specific signed update from HTC?

I am not to worried about it anymore, i have unlocked mine and will accept the consequences, but i'd hate to be knocked back on a manufacturing fault, if one occured.
[Nexus One General] jackal2:
Just try the following:

- Unplug the wall charger (if plugged)

- Open the case, take out the battery.

- Keep pressed the power button (with the battery out) for 10-15 secs

- Replace the battery

- Close the case, plug the wall charger

This worked for me.
[Nexus One General] hampan:
md5 check can easily be done in osx with the built in command.

openssl md5 <filename>
[Nexus One General] zitseng:
Just md5 will do, no need for openssl. I.e.

md5 <filename>
[Nexus One General] j2eubank:
If you do it via fastboot you can see the radio flash complete.. I think pulling the battery there is "danger area" or whatever. On a reboot after the radio successfully flashed a batt pull shouldn't hurt.

That's been my experience anyway...