I was trying out using a keyboard with a cheap USB OTG cable, and all was good. Then all of the sudden the screen went buggy, where ever other line of pixels was shifted to the left or the right, almost like some sort of corrupted video file. It started to reboot itself, and it got to the black screen with the Google logo and then the screen fuzzed in the same way as before. It then starts to reboot and does the same thing over and over again. I find that I can get to the recovery screen with the scroll arrows. From there, if I tell it to reboot into recovery it goes back into the same Google logo bootloop. I then went back to the original recovery screen and I decide to try out adb to see if it works. Sure enough it does, and I unwisely start flashing a stock 4.2 bootloader image. However, while it is flashing the screen does the same fuzz thing and and stays fuzzed. Then it doesn't respond to anything. I take out the battery, and try to restart and with will not turn on at all, no vibration, no light from the screen, nothing. I tried a unbricking methods from there, and nothing can make it come back alive. Any ideas?
Additional info:
GSM tajkju
Bootloader unlocked
Running stock unrooted 4.2 that I flashed manually
Stock recovery
So after a bunch of issues getting this KF back to usable using a factory cable I am still having issues. I have installed all versions of TWRP from 2.2 to 2.6. I have tried flashing the stock ROM on each TWRP version 3 times (just to be sure!). In every instance, the KF gets stuck on the stock boot screen. Sometimes it would come up with the stock message saying it needs to restore and press the power button. I then press it, and it goes back to it. Most of the time it just stays on the boot screen with no restore option. I have used KFU, fastboot, unbrick, and pretty much anything that was out there and still NOTHING but a boot screen. Does anyone have ANY options for this besides trying to convince Amazon to exchange it?
How long does it actually take to flash the ROM? No matter what I try, it seems the flashing process is takes less then 20 seconds, so I assume that is not flashing the entire ROM and that is why I get stuck at the logo screen only.
Make Sure you wipe Factory Reset, Wipe Cache and Dalvik before flashing Stock. After flashing wipe dalvik again. I would recommend flashing external storage then. After that revolt. You might wait like about a few 2-5 Minutes but it will eventually boot.
Sent from my Kindle Fire using xda premium
Thank you for your reply and help! I have done all that repeatedly, except the external SD wipe. Nothing worked! I have a bigger issue at hand now. I accidentally left the KF hooked to the PC overnight with the FC. When I came down in the morning, the KF would not power on. I left it charge from a wall adapter for 5 hours, and still won't power on. It is getting warm like its retaining a charge, but no screen light or charge light. I have tried all options I have found on here and other sites to reset the KF, no luck! Any thoughts on this?
Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
FoxyDrew said:
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
Click to expand...
Click to collapse
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
kenmoini said:
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
Click to expand...
Click to collapse
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
LiquidPlacidity said:
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
Click to expand...
Click to collapse
I tried Vol Up/Down + Power for at least 30 seconds, was just stuck at HTC logo screen and I could feel the phone getting hotter so instead of having it run down the battery I decided to pop off the top. The back is meant to be non-removable but starting at the SD/SIM slot...slot, a guitar pick works great to undo the clips. Used a credit card to separate the sticky pads from the back. Pulled out the battery cable from the mainboard and reseated it, started it back up in HBOOT.
I flashed some sorta ZIP that's used with the HTC One M8 phones, figured if they have BoomSound it'd help too but noooope, haha. Can't remember what it was called. Did a lot of searching, tried Viper4Android, that sucked, tried tweaking the DSP, nothing came close to the original.
Sharing my own bricking experience
I'm a newbie, but I wanted to share my own experience from a few days ago. I bricked my VM/USA 816 when I was restoring a ROM backup of CM12 over a stock ROM. I was stuck on the CM12 blue "alien head" boot screen. I tried to get into the recovery screen by holding down power & volume, but it would only reboot and load CM12 again and not TWRP.
After a couple of hours of trying to get into recovery and deciding not to wait for the battery to drain because I thought the blue CM12 logo might burn into the screen. I decided to try to remove the cover and unplug the battery. I started at the SIM/SD Card slot trying to pop the cover off a little with a small screw driver to get a credit card(CC) between the cover and phone. Once I got it started I moved clockwise(cover side up) around with either a bent CC or a smaller cut up piece of CC to pop the tabs. I wasn't very gentle since I knew I wasn't going to return the phone and I bought the phone from VM with account balance so I didn't feel like I was really going to waste $300. Thank HTC the plastic cover is very forgiving. Once you get past the HTC logo you have to worry about the sticky tape around the bottom half of the phone where the battery is located. The bent CC was the best tool here and as I said earlier I wasn't very gentle while pulling off the cover once the tabs were loose.
Once I had the cover off I didn't know how to unplug the battery connector so I decided to pry the battery out. Once I did that I could see that the connecter pops up. I plugged the battery back in but the phone tried to load CM12 again. I don't remember if I had to press power button to turn on phone or it started when I connected the battery. I got back into the same state as before with a boot loop with no way getting back into recovery. So I unplugged battery again and connected the phone to my PC. I could see the screen the flashing between the charging screen and TWRP, but I couldn't get into recovery with buttons or screen touches. I then went into a command window on my PC to try the adb command. First I did a "adb devices" then I did a "adb reboot recovery" to get into TWRP. Once in TWRP I did an advanced wipe and installed CM12, gapps and supersu again from my ext SD Card. I'm not sure but I may have done a format of the internal storage just to be safe. Once I was up and running again I replaced the cover starting again clockwise from the SIM/SD Card corner and all the way around the phone till you get near the SIM/SD Card slot and have to replace the flap which is held in place by the cover/phone.
I hope this helps anyone who runs into the same problem.
kenmoini said:
Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Click to expand...
Click to collapse
You have to flash and use CWM 6.0.5.1 and wipe the same partitions that were backed up in your STOCK nandroid backup.
Once you do this, reboot to hboot. Enter fastboot. Flash the stock recovery. Wipe the data/cache/dalvik. Reboot and go to hboot again. (Your device won't be able to boot yet.) Enter fastboot again.
Flash CWM (ONLY CWM) and make sure it flashes by flashing it twice back to back without leaving fastboot at any point.
Boot into recovery and once loaded reboot into hboot once more then go once again to fastboot and flash Philz Recovery with the same double flash process.
Now boot into it, mount as a USB and create a clockworkmod/backup folder on the device root directory since Philz Recovery doesn't use the buried part of the system like CWM.
Drag and drop your stock root nandroid backup. Use Philsz recovery to restore it. Boot up and your phone will boot after 3-5 minutes.
Flash back CM11/12 if you'd like.
Sent from my 710C using XDA Free mobile app
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Hello
Thank you for sharing your solution.
I have a problem which is described in this thread: http://forum.xda-developers.com/des...im-boots-fastboot-t3316255/page3#post65409302.
My questions to you:
1. My bootloader is locked. Is it possible to flash stock recovery on it?
2. I tried to flash official rom but I received the message "Partition update fail!". Can what you did, resolve this problem?
A few months ago, the display broke on my Moto Z Play. It took me awhile, but I finally got a replacement display.
During the time I was not using it (starting immediately after it broke) it would make the sounds for my calendar notifications as they would come up, and continued to do so until the battery died.
While the battery was dead, I carefully took off the remnants of the old broken LCD.
About two weeks before I got the new display, I plugged it into my computer to see if I could pull any of my information off of it. Unfortunately, I was unable to get it to show up as a drive on my computer so I couldn't pull anything off of it.
Since it had power, it once again made sounds for my calendar notifications until the battery died.
I got my new display in the mail a couple days ago. I set about installing it and after I was done, I charged the battery to 96%. The charging screen appeared perfectly normal. I had no indication that there was going to be any problem when I went to use it until I powered it on at 96%. It looked like it was going to boot up just fine and made it three screens (not counting the triangle screen) into the boot up process and restarted the process.
The last time the phone was fully functional (as well as while it was on with a broken LCD) it was running OmniROM and it has TWRP 3.2.1-0 recovery on it.
First I tried clearing the cache and dalvik cache. That didn't help. Then, as I keep a copy of the zip for that ROM on my SD card, I decided to reflash OmniROM and 8.1 gapps. That didn't help. So, I decided to do a nandroid backup. It got part of the way through the back up and failed at system image. So, I decided to try to backup my data so that I can at least hopefully restore some of it at a later date on my computer or something. Thankfully, I was able to successfully backup my data partition.
After the backup finished, I decided to attempt to dirty flash CosmicOS.
However, I experienced the same boot loop.
I then did a full wipe and did a clean flash of OmniROM.
Still: the triangle screen, 3 seconds of the boot process and then it starts over again.
I am lost as to what to do now.
Help!
Hello?...
Hi, my 5X got itself into a bootloop state I have no knowledge of and I would really appreciate some pointers.
I searched the forum but I'm still not sure what I'm looking at and more importantly what to do about it. My main concern is not losing my data on the device.
Short summary: unlocked bootloader and rooted, bootloops, difficult to power off, factory images flash successfully but still only bootloader boots. The phone is on the latest stock Android 8.1 and was rooted with Magisk. In the meantime I've reflashed all factory images except userdata with no luck.
Bootloops: the phone started bootlooping by itself overnight. It was on the charger for a top-up and running only a sleep monitoring app like any other night. It boots as far as the Google logo, pauses a bit and repeats.
Power off: if I leave the charger cable connected the phone powers off from the bootloader menu only as far as the charging display and then starts bootlooping. If I first disconnect the charger it does power off, but as soon as I reconnect the charger the phone turns on and starts bootlooping.
Reflashing doesn't help: all factory images reflash successfully but the phone still won't boot into anything other than the bootloader. Booting into either the standard recovery or TWRP goes straight into the same bootloop. FWIW I also obtained the latest cache image and erased and flashed that but no luck.
My main concern is not losing my data so I want to be careful with whatever I try next.
I'd be really grateful for some pointers on what I'm dealing with and what the options are, thanks.
In case some other lost soul with the same problem stumbles across this, the explanation and fix are here:
https://forum.xda-developers.com/nexus-5x/general/tool-bootloop-death-blod-workaround-t3819497