Database Develop

[Q] HTC White Screen - Bricked?

I have searched here and Google but can't seem to find the exact problem that I am having. Most similar issues are with different phones and I haven't found any solutions for the HTC Hero. I have been rooted for a couple of months and using CM6 (stable and nightlys) without any problems whatsoever. I have (had?) Clockwork recovery. My phone was running perfectly this morning and the battery was pretty low (down to 10%) so I pulled it and put in a fully charged battery. Now my phone won't boot past the HTC white screen. I can boot into HBoot ONLY (three skateboarding androids) and the screen shows:
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Mar 1 2010, 16:02:39
I have tried all the options on HBOOT and can get into FASTBOOT but am unable to reset device, go into recovery, etc. It just goes back to the white HTC Screen after choosing one of these options and never boots up. I've tried with the SD card in and with it out. I even tried to RUU with the .5 Sprint official release but when I run it, the program said my phone was not found and told me to make sure it was plugged into the computer which of course it was. I also tried to run the RUU in FASTBOOT USB mode but still receive the same error.
When I run adb shell on my PC it says the device was not found. When I'm stuck on the white HTC screen if the phone is plugged in to the computer and I unplug the usb from the phone it vibrates 5 times quickly and the screen goes off, but the green notification light is blinking. From this state I am unable to power up the phone at all without a battery pull.
I just don't understand how my phone can go from being PERFECT to FUBAR when the only thing I did was replace the battery. I'm hoping someone can help me. I am eligible for an upgrade but really don't want to spend the $$ right now for an EVO or Epic when my area will never see 4g and the extra $10 is ridiculous.
My setup prior to this morning when I pulled the battery:
Clockworkmod Recovery
CM 6 nightly (Full-73)
BFS #11 kernel
FireRat custom data partitions
And I was rooted with Universal Androot

Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?

chromiumleaf said:
Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?
Click to expand...
Click to collapse
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!

debh945 said:
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!
Click to expand...
Click to collapse
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App

rulyskull said:
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.

debh945 said:
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.
Click to expand...
Click to collapse
Try the one click root(forget What section in here) but ima wait to get the epic or something better
Sent from my HERO200 using XDA App

Have you tried ruu'ing it?
Sent from my HERO200 using XDA App

Vandelay007 said:
Have you tried ruu'ing it?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Yep, I was finally able to RUU while the phone was in FASTBOOTUSB mode and the program on the PC said the ROM was updated successfully but it still never got past the HTC white screen. When I boot into HBoot by holding the volume down/power button the screen flashes a bunch of things so fast I can't read them but it seems like it says something about HCERMG Image Not Found.
The Sprint tech(?) hooked it up and tried to diagnose, install the software but couldn't either. Anyway, since it is under warranty I get a new Hero on Tuesday. I am just baffled at how this happened when all I did was change the battery. You don't realize how much you love something until it's gone. I'm currently using my old Instinct and I find myself constantly turning the screen sideways and wondering why the display won't turn.

Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?

SportsPT said:
Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?
Click to expand...
Click to collapse
Do you mind telling me what you did (twice lol) that put your phone in this unusable state? Like I said I'm not sure how this happened and don't want to repeat it with a replacement phone!

Ok, I put the HERCIMG.zip on the root of my SD Card (found it through Google and had updated 1.47 HBOOT). I booted up holding the volume down and power and the blue progress bar filled up on the right side and when it was finished it went back to the HBOOT screen. I rebooted the system and still have the white screen of death. I'm convinced there's really nothing else I can do to get it running again and must painfully wait until my new phone comes in on Tuesday.

Couldn't tell you how it happened, may have to do with the battery completely dying, but not sure. I tried what you did but got the same results. I think what we need as an updated HERCIMG.zip that works with HBOOT 1.47

While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img

unCoRrUpTeD said:
While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
Click to expand...
Click to collapse
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.

debh945 said:
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.
Click to expand...
Click to collapse
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.

unCoRrUpTeD said:
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.
Click to expand...
Click to collapse
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!

debh945 said:
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!
Click to expand...
Click to collapse
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?

obsanity said:
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?
Click to expand...
Click to collapse
All Heros have a 12 month warranty, I didn't pay extra. I first called Sprint Customer service and since it wouldn't boot for them to troubleshoot on the phone she gave me an Eticket number and the location of the nearest Sprint store with a repair center. I took it in and the tech (?) hooked it up to his computer and could not fix it either so he said he would order me another and it would be here on Tuesday. This was Saturday evening. I received a call today (Monday) from the Sprint Store that my replacement phone was in. Picked it up and rooted it in 5 minutes with Universal Androot, installed Clockwork Mod Recovery, Nandroid restored a backup from the old phone's SD card and I was back in business in 1/2 an hour! Probably TMI, I realize you only asked how I got a new phone but I'm thrilled to have my Froyo back!

Awesome! Makes me feel better trying different ROMs

Funny thing I found this thread, this exact same thing happened to me today.. Hero is completely done.. Getting a replacement tomorrow... I was running firerats also which I can't blame but I'm not running firerats on my new device... Since I installed firerats I've lost 2 8gb sd cards and a phone...
Weird thing is, I had applied the unrevoked-forever and eng spl mod/hack, now when I boot into bootloader it says s-on like what the hell happened? How did I lose s-off and root all together after restarting my phone.

[Q] Optimus black stuck on firmware update screen

The story so far...
Bought a new Optimus Black and gave it to my girlfriend for her birthday a couple of days ago. After playing with it for about an hour she put it down, I picked it up and decided to have a tinker. I installed Cyanogen mod 3.5.1 after rooting it with Gingerbreak. So far so good but I didn't really like the look of the ROM and the absence of a Market seemed like hassle so I used ClockworkMod to restore the backed up stock ROM.
It's still working fine but now I see there is an official update from inside the phone. I presume it's the upgrade to Android 2.3 so run it and reboot the phone. That's when it all goes wrong. I'm now stuck in the CWM recovery screen. I try all the options, following any online guides I can find that were supposed to have worked for people. I try restoring the backup, restoring cyanogen, clearing the cache, dalvik, everything but nothing happens and I keep booting back into the CWM recovery screen.
Next day I try the LGUnitedMobileDriver and the phone recovery option but despite trying several times I can get no further. A friend tried to use Odin to restore it but got no success. Finally, we tried restoring with a KDZ file with
KDZ_FW_UPD_EN, Windows Enabler and LG B2CTool and now the phone got stuck in yet another loop - a black screen with 'updating firmware'. The LEDs flash for a minute and it reboots and does the same again.
What's more, the phone will now no longer charge or turn on without being connected to the mains.
What are my options here?

Follow the tutorial given below.
http://forum.xda-developers.com/showthread.php?t=1275315

Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.

pickarooney said:
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
Click to expand...
Click to collapse
have you tried the CS_EMERGENCY option in R&D TOOLS? Wait I'll find the link..
Here >>> http://forum.xda-developers.com/showpost.php?p=18841596&postcount=8
http://forum.xda-developers.com/showpost.php?p=18740082&postcount=45
The CS_EMERGENCY is the only thing worked, he used a german V10A ROM. If you managed to unbrick it, you can flash it again with your desired KDZ, or use CS_EMERGENCY and flash directly your desired KDZ. TRIAL AND ERROR.

Emergency c-section... nope, I will try that now!

Said that it will get stuck at 4% but it is still flashing. Just wait for the phone to reboot by itself.

It just crashes with a fatal error as soon as it gets to the second tab (downloading) on both PCs I tried it on. I tried several KDZ files with the same result.

Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?

pickarooney said:
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
Click to expand...
Click to collapse
Does it have warranty? Why not RMA it, I think it has a hardware problem now since you mentioned it doesn't charge anymore. Also, have you tried a different USB cable?

The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.

pickarooney said:
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
Click to expand...
Click to collapse
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.

gabwerkz said:
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
Click to expand...
Click to collapse
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..

darkzorn said:
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
Click to expand...
Click to collapse
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge

pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
Fingers crossed for you !!!

pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
IT will mostly work..Good luck though and please do reply here and let us know if it worked..

Can't update Google Glass by using the XE16.1 boot.img?

My google glass won't update normally, so I had to download the update zip from the google developers site. I am trying to update using the instructions below the download. However, when I reach "fastboot flash boot boot.img", nothing happens. Terminal says fastboot is doing something, and the white led on my Glass flashes periodically. However nothing appears in the Terminal.
It has been like this for around 15 minutes and nothing has happened since.

bob7up said:
It has been like this for around 15 minutes and nothing has happened since.
Click to expand...
Click to collapse
Same exact thing happened to me yesterday. Fastboot would not work.
I thought it was trashed. But it came back to life on its own!
Basically, I left the unit running after I manually turned it of and back on. Then, sometime within the following 1/2 hour, I picked up my Glass and it was at the "ok glass" screen.
Give it time, forget fastboot for now. Good luck!
Update: I re-read your post and I now understand that your glass wont take the update automatically, so you are trying to use fastboot to install it. At this point I do not understand why fastboot is failing, unless there exists a new version that we don't have.
Updated2: After reading http://forum.xda-developers.com/showpost.php?p=51976005&postcount=28 perhap this is an issue? I'll answer myself, no, its a different symptom.

rotohammer said:
Same exact thing happened to me yesterday. Fastboot would not work.
I thought it was trashed. But it came back to life on its own!
Basically, I left the unit running after I manually turned it of and back on. Then, sometime within the following 1/2 hour, I picked up my Glass and it was at the "ok glass" screen.
Give it time, forget fastboot for now. Good luck!
Update: I re-read your post and I now understand that your glass wont take the update automatically, so you are trying to use fastboot to install it. At this point I do not understand why fastboot is failing, unless there exists a new version that we don't have.
Updated2: After reading http://forum.xda-developers.com/showpost.php?p=51976005&postcount=28 perhap this is an issue? I'll answer myself, no, its a different symptom.
Click to expand...
Click to collapse
I just tried doing the fastboot update (glass xe16.1 zip), and the same thing happened. It says "Device product is 'notle' Update requires 'glass_1'"

bob7up said:
I just tried doing the fastboot update (glass xe16.1 zip), and the same thing happened. It says "Device product is 'notle' Update requires 'glass_1'"
Click to expand...
Click to collapse
In that case, it is the same symptom as http://forum.xda-developers.com/showpost.php?p=51976005&postcount=28 , and the fix was simply editing the android-info.txt file inside the .zip so the line
board=notle
instead of
board=glass_1
Im surprised Google posted the firmware such that it would only flash on the older units.

[Q] Can't boot (FOTAFS_Open... Error)

I just got a used LG L90 to see if I could get it running, so far I can't.
When I turn it on it displays the LG logo for a few seconds then flashes to a green screen that says "Updating software (2/2)" for a fraction of a second before showing a black screen with the following white text:
FOTAFS_Open /cache/fota/log/FSUA_LOG_000.txt, 0, No such file o
FOTAFS_Create /cache/fota/log/FSUA_LOG_000.txt, 66, No such fil
FOTAFS_Close 0
Click to expand...
Click to collapse
I searched around and found that this phone had a system update that didn't complete correctly and now is stuck like this. I have no idea how to fix it though. I tried the "Flash Stock KDZ Offline LG L90" process, which was apparently successful but it didn't change what is happening.
Notes:
* If I restart with power+volume down it goes to the factory data reset page, but when I select yes it just does the reset, so no recovery is installed.
* If I hold volume up and plug in USB I can get to the software upgrade screen, that's how I did the KDZ flash. Can I do anything from that screen?
Please let me know, or point me in the direction of useful posts. I haven't done anything like this in a couple of years, so I'm a little out of the loop on most things.

Another Note:
On the Firmware Update screen there's a box at the bottom that says:
USER B40
ROOTED
Click to expand...
Click to collapse
Not sure if that will help any with the diagnosis. I've been trying to get ADB to connect but I can't get it to see the device. (Running adb with the
Code:
adb devices
command and it doesn't show anything).

can anyone had solution to this............??
My phone also struck at same mode.....
fake fota test error

I had no responses to this in any of the forums I posted in. I tried everything I could think of and eventually just contacted LG support. They took the phone in and yesterday I got it back. Looks like they switched it out for a new one, and the problem is obviously solved.
Not a very XDA solution, but an effective one nevertheless.

futhamucka said:
I had no responses to this in any of the forums I posted in. I tried everything I could think of and eventually just contacted LG support. They took the phone in and yesterday I got it back. Looks like they switched it out for a new one, and the problem is obviously solved.
Not a very XDA solution, but an effective one nevertheless.
Click to expand...
Click to collapse
Yaa.
I contacted LG too .
they wanna replace motherboard..
I think I am missing something...??
because, when I flashed new KDZ it again boots into the same ..
I am trying to get adb access,
If I got the access I can remove laf.img so i can enter into fastboot mode. where I can flash rom/ recovery
otherwise wiping cache and fota partition might work...
still doing some experiments..
But in G2 forums,
one member mentioned that it can't solved until u go to LG service..
but I saw some guides in G2 to unbrick ..
I'll try....

The notes from the repair said something about a "bad language" and that they replaced the motherboard.
It's definitely a new phone though, there were scuffs on the corners of the one I sent in that are not there now, it's scratch free!

New phone, bricked within 15 minutes!

Hey there fellow OP 3T owners,
I just received my brand new OP 3T and after painstakingly going through the Android / Google setup options, only then could I update the OS.
But it didn't. It bricked my phone within a minute of updating. Buttons and the screen are totally unresponsive.
When connected to my desktop PC, my OP 3T is not recognized. The phone is brand new and was in use only 15-20 minutes before I went for the official software update provided to me by OnePlus.
I just went and opened a service ticket to RMA the phone, though I hope I can somehow avoid this by unbricking the phone.
I don't mind losing all my data, but I hope I will be able to unbrick my phone without going through 12+ steps and using half a dozen unverified 3rd party firmware files?
I just want the official OS back, as I'm content already with Nova Launcher...
*edit* I solved the problem by using the official build OnePlus 3T OxygenOS 4.0.2, "Minimal ADB and Fastboot", the deletion of all other ADB drivers in the Device Manager (such as "LeMobile Android Device" > Android ADB Recovery interface), one restart and otherwise lots of unnerving, long button presses on my OP3T.
Conclusion: This is not what I expected how my first experience with OP would go !!

https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try out this unbrick process, I've bricked my phone twice (put into bootloop into twrp), this put me back to stock and up and running again.

If you can get to fastboot or recovery, you are not bricked.

SlimJ87D said:
If you can get to fastboot or recovery, you are not bricked.
Click to expand...
Click to collapse
I don't know what that is? I just care about how to be able to recover.
Right now I managed to restart, but it only shows the OP logo and the "powered by android" signage, both in white...

Mine did the same thing after 3 weeks. Couldn't get it to turn on. Sent it back to Oneplus on an RMA, turned out the motherboard was bad. Once I got it back, there hasn't been an issue. Working great now. That might be the your problem.

My phone doesn't turn on at all now meanwhile. I managed to install that Qualcomm driver somehow, but it went downhill from there fast!

I have the exact problem the OP has while trying to upgrade the OS, 100% stock. I downloaded the OTA and tried to install the new OS, but it froze seconds into installing it. Just would not go forward. "ADB devices" doesn't recognize the phone. Was able to get into fastboot but bootloader and firmware are both blank. I did a factory reset, but still nothing. I can see the OnePlus logo when I turn the phone on but that's it. Is there anyway I can push something to the phone to make it work again? Thanks.
https://goo.gl/photos/fCNGtautw2uiEeyq6

The biggest issue I have right now with unbricking my phone is, that I simply do not have "USB debugging" activated, nor anything else, as I never even had the chance to do so, as I unfortunately applied the update right away after my first startup.

Thank you.
Haunt3r said:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try out this unbrick process, I've bricked my phone twice (put into bootloop into twrp), this put me back to stock and up and running again.
Click to expand...
Click to collapse
I tried the link you provided and it worked like a charm. I had exactly the same problem as the OP with the phone freezing while doing an OTA update and the ToolKit provided was able to unbrick my phone.
After unbricking the phone, I was able to upgrade the ROM to 7 using OTA with oneplus3toxygen_28_170114, download size was 1434MB.
Thanks.

Warranty..?

Hamiltoe said:
Warranty..?
Click to expand...
Click to collapse
What's it matter? OnePlus customer service is abysmal. The worst customer service I've ever experienced.