Phone won't boot past boot HTC Screen - AT&T HTC One (M7)

Hi everyone, I just unlocked my bootloader via the All in one Kit, flashed the recovery, and then flashed a custom rom (Clean Rom). After it was installed, I tried to boot my phone, and it loaded the HTC Quietly Brilliant screen, and then went blank, showed the screen again that said "developer edition" or something and booted me into recovery. If I try and boot my phone again, it does it again. Am I completely screwed? Is there a way I can flash back to a stock rom via fastboot or recovery? Help would be much appreciated, I just bought this phone 4 days ago and have already seemed to mess it up.

GeorgioC123 said:
Hi everyone, I just unlocked my bootloader via the All in one Kit, flashed the recovery, and then flashed a custom rom (Clean Rom). After it was installed, I tried to boot my phone, and it loaded the HTC Quietly Brilliant screen, and then went blank, showed the screen again that said "developer edition" or something and booted me into recovery. If I try and boot my phone again, it does it again. Am I completely screwed? Is there a way I can flash back to a stock rom via fastboot or recovery? Help would be much appreciated, I just bought this phone 4 days ago and have already seemed to mess it up.
Click to expand...
Click to collapse
If you still have access to recovery, you're fine. I'm not huge on development so I can't tell you exactly what to do right now, but I can assure you that your new phone isn't a paperweight...yet
Sent from my iPad using Tapatalk HD

Related

HELP Rooted and Installed ARHD Now Phone Hangs at Quietly Brilliant

Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.

[Q] Stuck on boot screen, no recovery, and now just stock 4.4.2

I have a massive issue...
Somehow I lost my TWRP recovery and when I tried to reflash it, I got the "software unauthorized by Verizon error" each time I started my phone.
I thought, no biggy, I'll just reflash back to VRALJB and all will be well with the world. Did it. No problem.
I then tried to unlock the bootloader. This is when all hell broke loose. I had to reflash VRALJB again and since then, I started getting stuck on the "Samsung Galaxy Note 2" screen (the first one, immediately after the phone turns on). I could not enter recovery using the (Volume UP + PWR + HOME) key combo. I could only enter download mode and use odin.
I tried everything. The only thing that worked was downloading the stock 4.4.2 Verizon image released a few days ago from sammobile.com
(I605VRUFND7_I605VZWFND7_VZW).
Now, I do not have root and my bootloader is locked, but at least I have a working phone and KitKat.
Hopefully the above helps someone, but, my question is, where do I go from here?
How do I go about installing a custom recovery and getting root? I would like to keep stock 4.4.2 as well and before anyone asks why, I want custom recovery for the sole purpose of managing my TWRP backups. Stock OS though.
Since you updated to 4.4.2, there isn't much you can do. No root, no recovery, no safestrap...yet. The only thing you can do is wait for developers to find a way to root this version of android.
Hi my friend, I have met the same problem, so could you tell me how to get that I605VZWFND7_VZW rom~
Please~~

[Q] Stuck at Boot Splash after Installing custom ROM

I made a stupid mistake when unlocking my DNA and flashing a custom ROM (ViperDNA 4.1). I ran the rumrunner S-OFF which seemed to go without flaw. The mistake I made was checking to see if root installed which I'm assuming now it didn't. I installed Clockwork Recovery on it and booted into recovery and installed ViperDNA which gave errors. When I rebooted I was stuck at the boot splash. I tried an unbricking method posted on YouTube that required going into Fastboot USB and running an OEM Lock command and then using HTC's ROM update utility to reflash stock back to it which failed. I've rooted and flashed recovery to a lot of devices so I wouldn't consider myself to be a total noob but I'm at a loss here. Any help would be greatly appreciated! :fingers-crossed:
Black htc screen with triangles on each corner
Man I really need help. ...I tried to flash and something went wrong to where I erased the entire os and I continued to fix this issue because all I had access to was twrp(custom rom) and bootloader. then what was crazy is that it appeared that based on the fact that I was on 4.4.2 kit kat that I was unable to fix it. after researching I found a ruu that didn't have the boot image so I flashed the factory ruu with no boot image and my htc scrren with the status bar filled all the way up but it never moved off of that screen I assume because that ruu didn't have the boot image so I thought that common sense would be to at one of the boot images that I had to the zip file of the ruu without the boot image....that's when I made things worst and now im stuck on this htc screen with the four triangles...my pc wont detect my device and im in need of some serious help....can you help? can anybody help?
I believe i can help!!!
jazoon said:
i made a stupid mistake when unlocking my dna and flashing a custom rom (viperdna 4.1). I ran the rumrunner s-off which seemed to go without flaw. The mistake i made was checking to see if root installed which i'm assuming now it didn't. I installed clockwork recovery on it and booted into recovery and installed viperdna which gave errors. When i rebooted i was stuck at the boot splash. I tried an unbricking method posted on youtube that required going into fastboot usb and running an oem lock command and then using htc's rom update utility to reflash stock back to it which failed. I've rooted and flashed recovery to a lot of devices so i wouldn't consider myself to be a total noob but i'm at a loss here. Any help would be greatly appreciated! :fingers-crossed:
Click to expand...
Click to collapse
look at my situation (right below yours) i just got myself out of that situation everything is back to stock and at least i have a fresh start...whats your current status?
CHRIST STARZ said:
look at my situation (right below yours) i just got myself out of that situation everything is back to stock and at least i have a fresh start...whats your current status?
Click to expand...
Click to collapse
I had the same problem last night. I couldn't get fastboot to work properly and thought I was screwed. Here is what I did:
I downloaded a stock rooted rom and put it on a flash drive. I used my USB OTG cable and booted into recovery. I then mounted the external drive and flashed the stock 4.1 rom back on it and that cleared it up. I haven't re-tried to flash the ROM I tried, but I think my issue was an old recovery version.
Once you get back to stock, update or change your recovery to a new one and then try again would be my suggestion.
If you don't have an OTG cable, I'd suggest at a minimum order one for when it happens again

[Q] Stuck in what appears to be boot loop with no ROM

Hi everybody, I just got my HTC One M8 today and after rooting it, I tried to flash Android Revolution onto it. Needless to say, this failed, and I've since been struggling for hours to try to get my phone into a workable state. The boot loader seems to be unlocked, but whenever I try to install any ROM, I get an error 7 and the install is aborted. I'm currently using CWM with Philz. Whenever I try to reboot the phone, it just gives me the white HTC screen, and freezes there. Any help would be very much appreciated! Thanks ahead of time!
davha0 said:
Hi everybody, I just got my HTC One M8 today and after rooting it, I tried to flash Android Revolution onto it. Needless to say, this failed, and I've since been struggling for hours to try to get my phone into a workable state. The boot loader seems to be unlocked, but whenever I try to install any ROM, I get an error 7 and the install is aborted. I'm currently using CWM with Philz. Whenever I try to reboot the phone, it just gives me the white HTC screen, and freezes there. Any help would be very much appreciated! Thanks ahead of time!
Click to expand...
Click to collapse
***** UPDATE *****
I did a complete factory reset, then flashed a stock ROM on and made sure everything mounted. After a terribly long load time, everything came up and worked just fine.

[Q] Can't boot into recovery after flashing TWRP 2.8.4.0

Hi everyone, so this is my first post here on Xda, heard a lot of good things though
Anyways, I just re-rooted my HTC One M8 at&t model for the second time, I have rooted before, but had some issues so I decided to unroot and relock it, that is until today, when android 5 came out for the developer edition I decided I would try to convert mine so I could install the official ota.
So I unlocked my bootloader and flashed
./fastboot flash recovery openrecovery-twrp-2.8.4.0-m8.IMG
Said it wrote it successfully, so I tried to boot into recovery to flash super su.
When I tried however, it just sat and hung at the "entering recovery" screen.
I held down the power and volume up to get back to my home screen and retried after booting back into the bootloader.
Same thing. Not sure what I did wrong. I installed TWRP for gsm models (like I should have, right?).
Is it possible that somehow the old version of TWRP from my previous rooting experience is creating conflict with the one I just flashed? I'm really new to all this, so thanks for putting up with my uneducated self
Any ideas?
Thanks in advance!-Z
PR4X15 said:
Same thing. Not sure what I did wrong. I installed TWRP for gsm models (like I should have, right?).
Click to expand...
Click to collapse
Right, as long as its not meant for CDMA or the dual SIM version, you are good to go.
Failure to boot into recovery from bootloader can usually be solved by fastboot erase cache, and install TWRP again. Probably just a problem with TWRP not being properly installed the first time around.
Or even try an older version. TWRP 2.8.4.0 is really new, so maybe there are issues.

Categories

Resources