So I was about to flash a ROM (viperone), and while I was in aroma I went to the "flash stock kernel" setting and did that, because I felt it probably wouldn't hurt. Well, turns out it broke my phone's ability to boot into recovery, from what I can tell. I can enter fastboot and I tried reflashing the recovery but it still won't go to it when I select that setting. What happens instead is it flashes to the HTC screen then it goes black for a few seconds, then it goes to the bootloader screen (where it has the red message) and it just sits there forever. Did I just completely brick my phone by doing this?
Actually scratch that, I managed to fix it by flashing the GPE RUU. Now I just hope I can figure out how to switch it back to stock at some point.
Related
My One X was working perfectly on Leedroid 5.1. I downloaded 6.2, put it on the SD card, held the power button and went to reboot into recovery, but it got stuck on the HTC ONE boot screen and wouldn't go any further. I thought it was a little odd but ignored it. Then I realised I needed to flash the boot.img anyway, so I turned the phone off then booted into bootloader, fastboot, flashed the boot.img. At the end of the process the phone was sent to recovery again, but again, the same thing happened, it wouldn't go past that screen.
I figured my recovery was corrupted, so I went back into bootloader and flashed CWM touch through fastboot.
Rebooted into recovery again, exact same problem. What gives?
Furthermore, every time I turn the phone off from that screen, it turns itself back on. I finally rectified that by turning it off, then holding vol- and powering down from bootloader.
What can I do?
EDIT: RESOLVED
fastboot erase cache fixed the whole thing!
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
bevnet said:
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
Click to expand...
Click to collapse
1.) Your phone is far from bricked at all. You have access to the boot loader (i.e. the screen with the options). The recovery you're seeing is stock recovery. All you need to do is go into boot loader and fastboot flash recovername (CWM) and you will have your custom recovery back to wipe data and reinstall a rom or restore a nandroid backup
Mine is doing the same thing, weird thing is, it was working since yesterday on jellybean, it just randomly froze this morning and and now won't boot..
im currently at work so i don't have admin rights to do a fastboot flash..
any idea why it would randomly stop working when i havn't flashed anything on it besides the jb rom?
Sorted..
Thanks for the comments.. yeah i was over-reacting a bit there..
I downloaded the Galaxy Nexus Toolkit, got a stock rom form gopogle, flashed it.. back to normal, well, it will be after i restore the CWM backup i took.. phew..
Thanks again
Ian.
Still stuck
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
this has happened twice today and i think it from using volume+
Steelbully said:
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
Click to expand...
Click to collapse
Boot into recovery, wipe cache, Reboot
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
Hey everyone, I have a T-Mobile M8, Unlocked, rooted, S-ON and I installed {4.4.4} AxxionKat~1.6.0 {Linaro} 9-13-14. Everything booted as normal, I restored all my apps, etc. I decided to change the DPI settings (which Ive done in numerous other ROMs in the past) to 460 from 480. I made the change, saved the build.prop, and restarted my phone. Instead of booting up and going to the boot animation, its getting hung up at the white HTC screen (where is says "this build is for developmental purposes only" Etc.) then it goes dark. Holding power does nothing. Holding power+vol down does nothing. Holding Power+Vol up will bring it to the white HTC screen again but then it just loops. Any ideas on how to get this thing back in recovery so I can restore a Nandroid? Thanks.
EDIT: Im good now. Back in recovery!
First of all, it's not bricked. If it was, you wouldn't be able to turn it on in the first place. You're thinking of a soft brick.
If you can get into the bootloader, you can just enter recovery (or boot custom) via ADB/fast boot
blazevxi said:
First of all, it's not bricked. If it was, you wouldn't be able to turn it on in the first place. You're thinking of a soft brick.
If you can get into the bootloader, you can just enter recovery (or boot custom) via ADB/fast boot
Click to expand...
Click to collapse
Soft bricked ya. Well I had it up and running and now I find myself in the same situation I was in on Tuesday. I cant get it into the bootloader in order to enter recovery mode. I hit PWR+VOL UP until the white HTC screen comes on, as soon as the screen goes dark I hold PWR+VOL DOWN which should bring me to the bootloader. The first time, this method worked like a charm. This time around it wont do anything. PWR+VOL UP will get me to the HTC screen but then once the screen goes dark PWR+VOL DOWN does nothing....
Phone seems fine when in recovery, acts totally notmally. Can flash any ROM without issue, but when you go to boot it will just stay on the boot screen indefinately. The result is the same regardless of which ROM I use. I decided to flash the RUU in the end as I was getting nowhere, but the same result... just stuck on the boot screen (relocked bootloader and flashed stock recovery beforehand)
Anyone seen this before or have any ideas what might be wrong?
Finally fixed. For whatever reason, reseating the battery connector kicked it into action