Database Users

Nexus One Bricked :(

I was updating my Nexus One and it gave me an error that looked like an Android being taken out of a box it was at this screen for atleast 30 mins before I decided to pull the battery and restart. Tried to turn on and it wouldn't do anything at all. I've tried charging it,pulling battery out overnight, soft and hard resets nothing at all no signs of life. Any other methods I can try or is it a brick?

Can you boot into fastboot or recovery?
Were you trying to flash a recovery.img?

None can't do anything no boot no nothing

sty3x said:
None can't do anything no boot no nothing
Click to expand...
Click to collapse
I believe it was in the process of flashing the radio maybe, if you pulled the battery during this process then I think your N1 is done.

I think the last thing I saw was writing radio.img then it gave me an error that looked like a box with an Android coming out with a arrow pointing to the Android

I don't think that was an error icon. It was showing you it was installing something. Taking out of the box onto your android phone. But it shouldn't have taken that long...

did you flash the wrong radio?

sty3x said:
I think the last thing I saw was writing radio.img then it gave me an error that looked like a box with an Android coming out with a arrow pointing to the Android
Click to expand...
Click to collapse
Yeah that explains it. Sometimes it takes awhile when updating. It wasn't an error it was going through the process of flashing the radio. It is water under the bridge now, but in the future never pull the battery while it is flashing the radio. Almost certain that you will brick your phone if you do.

Ah, anything I can do to it?

Hum.....let me buy it for $100 or send it to HTC For a new motherboard for $200 of they determine its not under warrenty

What is HTC warranty phone number I'm only getting there technical support

help! Defy wont boot, white light at top, rsdlite doesnt recognise

Deleted by user

I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App

Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.

Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse

Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App

Guess what, it works!!!
Deleted by user

Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse

I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure

Deleted by user

got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable

To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...

Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd

I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do

Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave

Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder

I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.

Last try to make my dead Note 3 un-dead

Well it's been almost a month now my Note 3 is in coma, and I gave up and ordered a Note 4 but I have not totally given up, not yet.
It started with this problem I mentioned earlier, http://forum.xda-developers.com/galaxy-note-3/help/phone-wont-boot-please-help-t3295416
And even now its still same, worse actually, cause most times the display won't even turn on now! Anyway, the phone does go into download mode, I mean I can feel it, but can't see it, Odin flashed the latest TWRP successfully too, but then again I can't enter Recovery, or rather I can't see it, but I can feel that recovery is being accessed cause when I touch on the display I feel the vibration here and there.
Anyway, I just want to do one more thing before I totally give up, try to connect the phone via ADB and flash the Norma ROM, the ROM which started all these problems. Now I have forgotten everything about it, how to run it, what files to download and all that, so could someone please redirect me to that? Last time no one replied, but please do this time. Its common sense to realise how much pain a dead phone causes.
Thanks in advance.

Have you tried to install official firmware via Kies or flash with Odin ? If odin detects phone, you should try.

Kies can't detect phone unless its on right? Well mine isn't on. It just goes into download mode and recovery that's all. Of course I flashed stock ROM via Odin several times, even with additional options like NAND erase all, Phone EFS clear etc. checked, but no benefit.

Is the phone recovery is working ?
Odin is best option to flash it.
Flash custom recovery first. You don't need Pc to install firmware after that just copy Firmware in sd card put it in your phone go to recovery Install the Firmware

Like I said, Recovery might be working fine, cause I can feel the vibrations on the screen when I touch it, but the display just won't come up!

Have you tried flashing on odin with a pit file for your model?

Mustafa Jafri said:
Have you tried flashing on odin with a pit file for your model?
Click to expand...
Click to collapse
Yep, that's done, did it only few hours ago. On the positive side, the ROM was flashed without any error at all and the phone rebooted successfully after the ROM flash, which was until now a rarity, a successful reboot without any loop I mean, the Samsung boot sound was there too, and even the capacitive hardware buttons were lighted up, I can also hear the water droplet sound when I touch the screen, but the screen is dark, there is nothing on it! From this point, anyone will say the display is dead, but if previous experience accounts for something then the display will come back, maybe after few hours or few days, but it did come back before from what it looked like a completely dead display.
I remain clueless!

ithehappy said:
Yep, that's done, did it only few hours ago. On the positive side, the ROM was flashed without any error at all and the phone rebooted successfully after the ROM flash, which was until now a rarity, a successful reboot without any loop I mean, the Samsung boot sound was there too, and even the capacitive hardware buttons were lighted up, I can also hear the water droplet sound when I touch the screen, but the screen is dark, there is nothing on it! From this point, anyone will say the display is dead, but if previous experience accounts for something then the display will come back, maybe after few hours or few days, but it did come back before from what it looked like a completely dead display.
I remain clueless!
Click to expand...
Click to collapse
Might be a faulty LCD then.

ithehappy said:
Well it's been almost a month now my Note 3 is in coma, and I gave up and ordered a Note 4 but I have not totally given up, not yet.
It started with this problem I mentioned earlier, http://forum.xda-developers.com/galaxy-note-3/help/phone-wont-boot-please-help-t3295416
And even now its still same, worse actually, cause most times the display won't even turn on now! Anyway, the phone does go into download mode, I mean I can feel it, but can't see it, Odin flashed the latest TWRP successfully too, but then again I can't enter Recovery, or rather I can't see it, but I can feel that recovery is being accessed cause when I touch on the display I feel the vibration here and there.
Anyway, I just want to do one more thing before I totally give up, try to connect the phone via ADB and flash the Norma ROM, the ROM which started all these problems. Now I have forgotten everything about it, how to run it, what files to download and all that, so could someone please redirect me to that? Last time no one replied, but please do this time. Its common sense to realise how much pain a dead phone causes.
Thanks in advance.
Click to expand...
Click to collapse
Have you tried different software version ?
Try install different software version it may be bad rom ?

My galaxy on5 refuses to take rom flash.

Heres the deal. I have flashed, virtually,every stock and custom rom via odin or recovery .zip flash. Flash install completes every time. It reboots goes to samsung logo then black but slightly illuminated screen. What the hell am i doing wrong? Sorry! I hope im posting in the proper location. Digi-slap me if i am. Thanx! Any input would be greatly appreciated. Helpful or not. Its already bricked so i dont think a shot in the dark could do much harm. Im willing to try just about anything at this point. Wits end!!!!

matthewmalah said:
Heres the deal. I have flashed, virtually,every stock and custom rom via odin or recovery .zip flash. Flash install completes every time. It reboots goes to samsung logo then black but slightly illuminated screen. What the hell am i doing wrong? Sorry! I hope im posting in the proper location. Digi-slap me if i am. Thanx! Any input would be greatly appreciated. Helpful or not. Its already bricked so i dont think a shot in the dark could do much harm. Im willing to try just about anything at this point. Wits end!!!!
Click to expand...
Click to collapse
How long are you waiting before you are giving up on the flash? It almost sounds like you don't have a bootanimation or the binary to play it? I would think that flashing new firmware would take care of that. After you flash the rom or firmware, maybe try going into recovery and do a factory reset, then bit into the system and wait at least 15 minutes. My screen looked like that when I was fooling around with doing my own boot animation that didn't work. It did exactly what you described for a long time into it went into the green screen with the Android working on apps.

tmobile s8 boot loop-ish

hey all,
Saturday morning a wake up to my alarm on my phone (SM-G950U T-Mobile Stock since new) and turn off the alarm and proceed to check email and scroll social medias. A few minuted later phone turns off and starts boot looping. Occasionally it would boot to home screen and i could unlock it but then maybe 30 seconds later it would start boot loping again. Now it either just boot loops or boots straight to recovery . I have tried flashing current firmware in case it was corrupted and i have tried accessing it through ADB. I know for a fact USB debugging is on because I just used abd to pull wifi passwords 2 weeks ago, but when I try to [ abd devices] if comes up as unauthorized and I cannot proceed. I know everyone will suggest a factory reset, but I am hoping someone has a trick for extracting files. I dont care about most on my phone, but I would like to save the pics from my GF and I trip this past august. Apparently I didnt have my photo library set to sync to cloud -_-
thanks
-chip
update: it appears there is a pattern. it boot loops or boots to recovery (after a blue failed system update screen) 99% of the time. the 1% it boot fully and then crashes is only when battery is 0% . it for some reason is only trickle charging and isnt getting enough juice when it does boot fully to stay on . But if i leave it charging a while it will then only boot loop or boot to recovery. Strange...any way I had enough time this past boot to reauthorize usb debug.....wish me luck with adb
....nevermind. still shows up as unauthorized

chip102 said:
hey all,
Saturday morning a wake up to my alarm on my phone (SM-G950U T-Mobile Stock since new) and turn off the alarm and proceed to check email and scroll social medias. A few minuted later phone turns off and starts boot looping. Occasionally it would boot to home screen and i could unlock it but then maybe 30 seconds later it would start boot loping again. Now it either just boot loops or boots straight to recovery . I have tried flashing current firmware in case it was corrupted and i have tried accessing it through ADB. I know for a fact USB debugging is on because I just used abd to pull wifi passwords 2 weeks ago, but when I try to [ abd devices] if comes up as unauthorized and I cannot proceed. I know everyone will suggest a factory reset, but I am hoping someone has a trick for extracting files. I dont care about most on my phone, but I would like to save the pics from my GF and I trip this past august. Apparently I didnt have my photo library set to sync to cloud -_-
thanks
-chip
update: it appears there is a pattern. it boot loops or boots to recovery (after a blue failed system update screen) 99% of the time. the 1% it boot fully and then crashes is only when battery is 0% . it for some reason is only trickle charging and isnt getting enough juice when it does boot fully to stay on . But if i leave it charging a while it will then only boot loop or boot to recovery. Strange...any way I had enough time this past boot to reauthorize usb debug.....wish me luck with adb
....nevermind. still shows up as unauthorized
Click to expand...
Click to collapse
Ive had similar cases happen with older models. May be time for a battery. They will do crazy **** when the battery crashes. When you flashed stock firmware you lost adb authorisation. Need to get the system back first for that.

TheMadScientist said:
Ive had similar cases happen with older models. May be time for a battery. They will do crazy **** when the battery crashes. When you flashed stock firmware you lost adb authorisation. Need to get the system back first for that.
Click to expand...
Click to collapse
thank you very much. my battery life was greatly suffering and the USB-c port was worn pretty bad. Ill grab a new battery and hope that works.

chip102 said:
thank you very much. my battery life was greatly suffering and the USB-c port was worn pretty bad. Ill grab a new battery and hope that works.
Click to expand...
Click to collapse
Cheapest fix in my opinion. I saw another thread a guy dropped his. Now detects 9008 how to fix. More than likely a phone wont just not boot. Or lose programming unless a hardware issue. So if it was just running and quit. Not modding stuff really. More likely than not its gonna be some form of software. But hardware.

TheMadScientist said:
Cheapest fix in my opinion. I saw another thread a guy dropped his. Now detects 9008 how to fix. More than likely a phone wont just not boot. Or lose programming unless a hardware issue. So if it was just running and quit. Not modding stuff really. More likely than not its gonna be some form of software. But hardware.
Click to expand...
Click to collapse
Replaced Daughter board and battery. No improvement :/ bummer

the only time i can get it back into recovery is after a "successful" flash with odin. by successful i mean that it says it worked but it just continues to boot loop or boots to recovery. attached is a picture of the info i get in recovery every time. hope someone can shed some light in the issue. im using my old phone so i dont feel pressured to call the data a loss and try a factory reset just yet....my old phone is a POS though

chip102 said:
the only time i can get it back into recovery is after a "successful" flash with odin. by successful i mean that it says it worked but it just continues to boot loop or boots to recovery. attached is a picture of the info i get in recovery every time. hope someone can shed some light in the issue. im using my old phone so i dont feel pressured to call the data a loss and try a factory reset just yet....my old phone is a POS though
Click to expand...
Click to collapse
Yea some one tried to root it using the edl safestrap thread. Only wsy to fix it is filled the steps and reflash jrkruses pie rom. One of my mother boards are in the same state. That's the only way dm verity fails. Is his rom method.
There's some easy to flash a cache wipe in Odin but I hadn't found it yet. I have 2 mother boards and one is identical. I flash this stock and lose download or recovery. but the errors you show are only from doing that edl safestrap

Ill be honest..i have no idea what you are talking about. Ive messed with the software with previous devices and never heard of safe strap. This one has been bone stock since I got it from Tmobile and i haven't attempt to flash anything until i had this issue. never tried to root it
TheMadScientist said:
Yea some one tried to root it using the edl safestrap thread. Only wsy to fix it is filled the steps and reflash jrkruses pie rom. One of my mother boards are in the same state. That's the only way dm verity fails. Is his rom method.
There's some easy to flash a cache wipe in Odin but I hadn't found it yet. I have 2 mother boards and one is identical. I flash this stock and lose download or recovery. but the errors you show are only from doing that edl safestrap
Click to expand...
Click to collapse

chip102 said:
Ill be honest..i have no idea what you are talking about. Ive messed with the software with previous devices and never heard of safe strap. This one has been bone stock since I got it from Tmobile and i haven't attempt to flash anything until i had this issue. never tried to root it
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/development/root-t3904613. This thread can help you at least get pie back up and running. I wouldn't mess with no more. I haven't had much luck with mine. But I did get it booting again