A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Very nice..
wow seriously, didnt expected that..
good job mate!
btw wat did u do to cause the brick?
Just read the very first line of his post...
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
[...]
Click to expand...
Click to collapse
mgear356 said:
btw wat did u do to cause the brick
Click to expand...
Click to collapse
As I said above, I had been flashing the SPL, and when I rebooted following the flash it was bricked (stuck at first splash screen).
It's weird, because once I managed to get back into fastboot, I simply flashed the same SPL again and it worked fine.
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Never seen someone say the splash screen isn't coming up without blaming the hardware. I didn't think that flashing the wrong SPL would case the splash to not come up. I bricked my first phone by stupidly flashing the wrong SPL first before loading an OS. I thought the whole point of using the word 'brick' was when referring to the phone failing to enter 'fastboot' and 'recovery mode'. At that point, the phone would technically be a 'brick'. This has to be the first post I've seen with a possible fix but I could be wrong since I gave up on fixing that phone awhile ago.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
bricking means you can't get to fastboot or recovery no matter what you do.
so he counts as bricking.
this might be a fix for the haykuro spl bricked users..
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
No, You can still get to your splashscreen when the phone is bricked, If you cant turn on the phone then thats called the phone is dead not bricked. As stated already if you can't fastboot, or get to recovery then thats a brick.
Just tried it does not work and I was flash the death spl from haykuro,I am getting a new one but wanted to see if this works and I did not think it would which it didnt.
imfloflo said:
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
Click to expand...
Click to collapse
Posted the fix on the android community forums. I have none person in mind, bricked it applying a spl, but he hasn't relied yet. Keep you informed if he does.
Did you reflash ROM after applying spl..? If you did and it still didn't boot then that should most likely be a brick. Can you boot into recovery right now and tell us your SPL version and radio?
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
A bit of a personal opinion here:
"Dead" is when the phone doesn't respond to anything, at all.
The charging light does not come on, the power button does nothing, and there is not so much as a flicker in the screen. Also, it is completely inaccessible for hardware debugging (JTAG, serial, USB or otherwise). This usually happens from a hardware problem, or doing something stupid like zero'ing the IPL.
Examples:
- My brother dropped his Nokia N75 in water. It's dead.
- I dropped my Cingular 8125 (HTC Wizard) on the ground. It doesn't power on any more, and plugging it into the charger does nothing. Voltmeter shows a charge running through some areas of the device's motherboard once disassembled. It's dead.
Solutions: Replace, recycle or sell for parts.
"Bricked" is when a purely software problem causes the device to no longer respond.
This may happen on many levels, but usually results in the OS not booting, or booting and being completely unusable (e.g. stopped with kernel panic at OS splash). It may light up and/or show a splash screen, but it fails to enter the bootloader or recovery menus. Its recoverability may vary, but will usually involve a debugging tool and a computer, and likely a copmlete wipe of everything on the device. Even if it's heavily bricked, if it can be recovered via JTAG or similar, it's not "dead".
Examples:
- HTC Dream only goes as far as splash screen, and freezes there. Does not respond to ADB. Does not enter recovery, or bootloader, however fastboot responds.
- HTC Dream shows blank screen, but lights up as if it were powering on. Fastboot does not respond. I connect my HTC ExtUSB Serial dongle to it though, and I'm able to get a response to some commands.
- Western Digital MyBook World Edition NAS powers on, and spins up hard drive, but does not go any farther than that. Front lights do not light up, and no hard disk activity is heard. Networking is not yet enabled. Hard drive can, however, manually be connected to a PC with SATA, and the firmware image re-written to its partitions.
- XBOX (the original) was softmodded, but the dashboard.xbe (the OS shell) was overwritten. It now just stays at the Microsoft logo.
- iPhone was recently jailbroken and SIM unlocked, then Apple pushed an update on me, and my iPhone is in a state where it doesn't enter DFU/Recovery, and when it boots, it says "Emergency calls only."
Solutions: Be very careful not to further brick the device, but use any methods available. Be sure to check documentations, search forums, and then ask questions if unsure. Make sure you finish every process you start.
After this, might just be hardware "damage" (like a power button not working right) or software "errors", like the home screen failing to load because of "Process com.google.android.gapps quit unexpectedly." These are usually relatively easy to fix, or have fixed.
Again, this is just an opinion.
Back on topic though, I seriously wouldn't have probably thought of using fastboot while it's stuck at the G1 screen, unless mine were bricked. Kudos to you, and I hope this works on some other bricked G1's out there (At least ones with the Engineering/Hard/DangerSPL, the stock SPL doesn't support fastboot as far as I know.)
bonesy said:
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
Click to expand...
Click to collapse
Won't agree with that, what you describe as a brick is a DEAD mobile. A brick is a useless piece which wont get into any state of recovery. The only thing i will agree with is that if it'll turn on there is a way to get it fixed that's why we even got the word unbricking which is done with many other pieces than Android mobiles.
Hope this will get us closer to a unbricking method which works on all the BRICKED pieces out there.
Good job dude!
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
wow sweet news
fishman0919 said:
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
Click to expand...
Click to collapse
Very glad to hear that your dead or bricked or whatever-you-may-call phone is back to LIVE!!!
So I think this solution works for some certain people. So i think rather than arguing on terminology, better spread this good trick to people who had dead/bricked/whatevery-you-may-call phone. IMHO
Thanks for the solution.
Best,
Thihaz
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Click to expand...
Click to collapse
where were you 2 months ago dude? I paid 270€ to change the board on my magic
Good Job! Thanks for the info
I was rooting my phone last night and was successful. When trying to load a Cayanogen rom, it wouldn't get past the "Vodafone" splash screen. I noticed I did not have the proper radio installed, so, I installed the radio for Android 1.5 from the website.
Now, it is stuck in the red vodafone splash screen, and won't let me enter fastboot, bootloader, or recovery.
So, am I screwed, or is there a way I can fix this? I honestly searched for a VERY long time, and could not come up with much help.
Thanks. Also, I am using this on AT&T and it is unlocked.
if you can enter fastboot or recovery or anything than its not looking good, have you taken the battery out for a while and tried fastboot again?
I'll try leaving the battery out for a little while and try again. I just let it sit on the splash screen for about 15 minutes with no luck.
Left the battery out for 20 minutes, put it back in, tried to enter bootloader/fastboot/recovery, still with no luck.
Any other suggestions? I literally just bought this phone last week!
Also, since I am on at&t and this is a T-Mobile phone, and it is bricked, is there any way I would be able to send it in for a warranty replacement? I have no receipt of the original purchase, but still have the original packaging.
well i recently dropped my HTC wildfire in water. I took it to the service center a local shop
and get it cleaned. but right on the shop when the engineer repaired it; it keeps
on restarting again and again. i thought it was beacuse may be ROM get corrupted
and when i will return home i will boot into recovery and reflash it.
but when i came back to home i put the phone down and then tried to go to the
recovery , it again start rebooting again and again. i was unable to stay in recovery for a
few seconds. it shows the revolutionary recovery but again it reboot and shows the
HTC logo and then again reboot after few seconds. then i thought may be clearing the memory will
make any effect but still when i cleared memory from bootloader i managed to clear it and it
didn't gave me bootloop in bootloader. but as soon as i tried to again boot back to recovery from bootloader menu
it again start rebooting abnormally. well i thought there may be problem with the battery but when i put charger
in again the phone led shows orange color charging and then phone again start rebooting
when the charger was plugged in.
but it stays in bootloader on. battery checked it is working right.
now can somedbody tell me is it hardware fault or there is something wrong with software ??
i called the LOCAL HTC center they say that there is an IC in the motherboard of phone
it is responsible for making boot properly and may be water has runied it.
well as per them the repair is not possbile now because they just replace the whole board they
don't solder the IC'S and moreover in india HTC has halted the production of motherboards they
are not avaliable no more.
well is this the end of my little fellow phone ?
sachoosaini said:
well i recently dropped my HTC wildfire in water. I took it to the service center a local shop
and get it cleaned. but right on the shop when the engineer repaired it; it keeps
on restarting again and again. i thought it was beacuse may be ROM get corrupted
and when i will return home i will boot into recovery and reflash it.
but when i came back to home i put the phone down and then tried to go to the
recovery , it again start rebooting again and again. i was unable to stay in recovery for a
few seconds. it shows the revolutionary recovery but again it reboot and shows the
HTC logo and then again reboot after few seconds. then i thought may be clearing the memory will
make any effect but still when i cleared memory from bootloader i managed to clear it and it
didn't gave me bootloop in bootloader. but as soon as i tried to again boot back to recovery from bootloader menu
it again start rebooting abnormally. well i thought there may be problem with the battery but when i put charger
in again the phone led shows orange color charging and then phone again start rebooting
when the charger was plugged in.
but it stays in bootloader on. battery checked it is working right.
now can somedbody tell me is it hardware fault or there is something wrong with software ??
i called the LOCAL HTC center they say that there is an IC in the motherboard of phone
it is responsible for making boot properly and may be water has runied it.
well as per them the repair is not possbile now because they just replace the whole board they
don't solder the IC'S and moreover in india HTC has halted the production of motherboards they
are not avaliable no more.
well is this the end of my little fellow phone ?
Click to expand...
Click to collapse
The last thing i would suggest you is that to change recovery.try flashing some other recovery and see if it works.If the problem still persists,I'm afraid you'll have to give up on willy or buy a new second hand willy.Its pretty cheap these days.
Well i will definitely try to do that
Wasimk32 said:
The last thing i would suggest you is that to change recovery.try flashing some other recovery and see if it works.If the problem still persists,I'm afraid you'll have to give up on willy or buy a new second hand willy.Its pretty cheap these days.
Click to expand...
Click to collapse
well yeah i will try to do that i would be able to..can you tell me how to flash recovery from fast boot menu after connecting it with PC and re installing HBOOT drivers again. coz it was long ago that i had did it.:good:...
Download any recovery in pc49img format and put it on the root of your sd card. Then turn the phone on in bootloader mode, follow instructions and you're done. No need to connect to PC.
Donne
Wasimk32 said:
Download any recovery in pc49img format and put it on the root of your sd card. Then turn the phone on in bootloader mode, follow instructions and you're done. No need to connect to PC.
Click to expand...
Click to collapse
My phone is alive again and it is working one of my friend has repaired it.:good:
So just got the axon 7 mini yesterday and was so excited I decided to try to root it with my laptop while my girl was driving us home from Las Vegas..... Ell I got as far as unlocking the boot loader.... now i get this odd screen after i try to exit fastboot. (pic-1) and no matter what option I pick the only thing that will come up is this screen. The only time its different is if I try to chose start from this screen then I get (pic-2) The best thing about this is that I can still go back to fastboot anytime. And it shows up in fastboot devices. Do I need to reflash stock thru fastboot? If so How and Where can i find it. Can I just flash nougat? I'm new to ADB/Fastboot.... Thank you for your time and consideration ahead of time for any help.
Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.
Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.
William Guo said:
Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.
Click to expand...
Click to collapse
I tried the thing were saying over and over
MrWhite0429 said:
Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.
Click to expand...
Click to collapse
so I was stuck all day yesterday trying anything and everything. BY THE WAY...Im very knowledgable but im pretty much a newb in rooting dept. especially fastboot. Well it seems I erased everything including the bootloader then battery died and no I have NOTHING on screen, no vibrations. Pretty much looks bricked. But when I try to put it in my computer to charge it it still shows up in my devices. BUT its not being found in adb/fastboot. I've tried every key combo/and length of holding them which doesnt do nothing
Can you place the device in edl? It will not display any lights or images when it is in edl.
I am in need of serious help! I dropped my phone off a 2nd story, smashed the screen completely. So I took my wife's old stylo 2 plus (exact same phone) stuck my Sim and SD into it, registered through metro pcs, and it worked great.
I did software update because I was really excited (my old stylo 2 was rooted and had many problems along with being unable to update android software).
Update took about an hour, then said failed. After that it has been unable to boot up. I tried recovery mode, it offers to factory reset. Again reboots and stuck at logo screen. Says error device is corrupt, cannot be trusted, will not boot. I press power it says press power again to boot anyway. Restarts and sticks at logo screen. Device is basically untouched. No oem unlock, no debugging, no developer options, nothing has been touched ever, the phone is 100% stock. I even did factory reset before I started using the phone.
Can someone please help me at the least flash trip so I can fix this??
I am not new to this, but has been 5 years since I flashed anything. The problem is, is that it's still locked, and can't boot up. The phones bricked and never been touched!
If I can get twrp flashed I can go from there, I need a way to unlock it, or flash without unlocking.
Please help me I need my phone for work. I'd rather not switch back to an old smashed screen
Cecil12 said:
I am in need of serious help! I dropped my phone off a 2nd story, smashed the screen completely. So I took my wife's old stylo 2 plus (exact same phone) stuck my Sim and SD into it, registered through metro pcs, and it worked great.
I did software update because I was really excited (my old stylo 2 was rooted and had many problems along with being unable to update android software).
Update took about an hour, then said failed. After that it has been unable to boot up. I tried recovery mode, it offers to factory reset. Again reboots and stuck at logo screen. Says error device is corrupt, cannot be trusted, will not boot. I press power it says press power again to boot anyway. Restarts and sticks at logo screen. Device is basically untouched. No oem unlock, no debugging, no developer options, nothing has been touched ever, the phone is 100% stock. I even did factory reset before I started using the phone.
Can someone please help me at the least flash trip so I can fix this??
I am not new to this, but has been 5 years since I flashed anything. The problem is, is that it's still locked, and can't boot up. The phones bricked and never been touched!
If I can get twrp flashed I can go from there, I need a way to unlock it, or flash without unlocking.
Please help me I need my phone for work. I'd rather not switch back to an old smashed screen
Click to expand...
Click to collapse
You need to download the kdz(device firmware) and flash it in download mode using lg up.
Sorry for the super long delay. I did what you said, and was able to use my phone again in no time. Thank you very much!
LG Stylo 2 Plus
Cecil12 said:
Sorry for the super long delay. I did what you said, and was able to use my phone again in no time. Thank you very much!
Click to expand...
Click to collapse
Hey would you be able to tell me which firmware worked or possibly even a link. I am having issues with getting one to work on the lg stylo 2 plus using lg up.