Database Develop

HTC One being reboot loop and unable to get through recovery or factory reset

hi all, im writing my very 1st post here after reading and searching many articles involving into my issue. sorry for my non - native english as well
i got this HTC One 4 days ago and did a unlocked boot loader and root a custom room (ARHD 9.2). everything was fine till i pressed install button and the installation was stuck at 30% for a long while (i have never seen this problem with my Samsung s3). Then I restarted the phone and it went through to the new OS. Today I tried to upgrade new room with the new version 9.3 and again it was stuck at 30%. I restarted the phone and tried another room but this one was stuck when choosing the opponents to install. Then, I came back to ARHD room and it was suddenly collapsed during installation. The phone now becomes reboot loop and when i choose the recovery, it will appear the CWM icon in 1 sec and become reboot loop infinitely. Also when the phone in bootloader status, the pc cant recognize it....
I recorded my issue here:
youtube . com / watch?v=Fx_yxMUKp4Q (im new and cant post a link here, so i tried to take some space bar here, hope mod/admin forgive me)
Hope u guys can help me out this problem. thank all

Had same error.
You forgot to flash boot.img after flashing your rom.
1. boot to your bootloader (hold volume down key and wait)
2. go to fastboot
3. extract boot.img from your rom's zip
4. in command line use this:
fastboot flash boot boot.img
and
fastboot erase cache
5. restart
this should fix your bootloop.
optional, you can reflash recovery (in fastboot):
fastboot erase cache
fastboot flash recovery name_of_the_recovery.img

mendozinas said:
Had same error.
You forgot to flash boot.img after flashing your rom.
1. boot to your bootloader (hold volume down key and wait)
2. go to fastboot
3. extract boot.img from your rom's zip
4. in command line use this:
fastboot flash boot boot.img
and
fastboot erase cache
5. restart
this should fix your bootloop.
optional, you can reflash recovery (in fastboot):
fastboot erase cache
fastboot flash recovery name_of_the_recovery.img
Click to expand...
Click to collapse
yeahh it worked like charm
the most important i think we should clear the cache then factory reset.
but after all, my phone now gets stuck when i choose the tweak or apps during installation with whatever room. My resolution was to click next and next without installing some good apps or tweaks ... any idea?

Recovery Loop
ricky_chuoi said:
yeahh it worked like charm
the most important i think we should clear the cache then factory reset.
but after all, my phone now gets stuck when i choose the tweak or apps during installation with whatever room. My resolution was to click next and next without installing some good apps or tweaks ... any idea?
Click to expand...
Click to collapse
I have a similar problem but fastboot is unable to detect my device after I have booted the device into bootloader and then fastboot.
Any help will be greatly appreciated

A bizarre series of events and my desperate recovery attempt [cliffhanger!]

So I started having trouble after flashing a rom. The old infinite htc boot logo. The troubling part was when I tried to reboot to recovery and TWRP blackscreened and device turned off.
I tried re-flashing recovery.img with identical results.
Now my phone locked while attempting a fastboot flash boot.img with a known working boot.img just in case the rom I flashed had a corrupt boot image.
I left the cmd window open and its been "sending boot.img" for about forty-five minutes now. I am terrified to ctrl+c the command or restart my device.
So boned or no boned?
On a scale of one to boned how boned where do I fall on the bonage spectrum?
Any ideas on what to do next, or if rebooting to fastboot is safe?

You have to wait the final of the sending.
Probably your USB cable is *****d up, and i'm advising you because i had the same issue.
A flash of a boot.img was of 15 mins.

Tried fastboot erase cache to get back into twrp?
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 9.1.0
Bulletproof 4.3

Afraid to stop the current fastboot operation to try to clear cache. Tried running from another window and it just sits there, cursor blinking, like its waiting for the other operation to complete.
Waiting for it to complete seems fruitless as its been almost two hours now for a 5836kb flash.
-update-
Okay so I took a couple valium and quickly switched out the usb cable. The cmd window running the flash operation crashed, but fastboot on the device became responsive again. I feel like this is a fact that might be useful to others in the future.
Fastboot stalls out--don't panic, just disconnect the usb cable...
I'm still scared to reboot it, even to reboot to fastboot. Is fastboot part of boot.img? If this botched op boned up my boot.img is it possible that fastboot might not work after a reset?
Gonna give cache erase a shot and report results.

Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?

hypocritelecteur said:
Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?
Click to expand...
Click to collapse
After the cache's erase you can boot in recovery.

Guich said:
After the cache's erase you can boot in recovery.
Click to expand...
Click to collapse
Phone still reboots right after TWRP logo is displayed!

hypocritelecteur said:
Phone still reboots right after TWRP logo is displayed!
Click to expand...
Click to collapse
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.

Yeah, I tried that before posting but for sake of thoroughness I did it again.
erased cache
reflashed m7 twrp
erased cache
Going to try CWM now.
Really appreciate the guidance and support in a problem you have no personal stake in. Being on the receiving end of the goodwill of strangers makes me all warm and tingly.
Also switched USB cables and did a fastboot reboot to make sure commands were being passed on... nothing wrong on that front.

Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Aaaand CWM worked for whatever reason.
Odd, since I've never had a problem with TWRP before but plenty with CWM... Every duck has its day I guess.
---
Well... CWM loads properly but executing any command that touches phone data causes a reboot.
Factory reset -> reboot
Install zip from sdcard -> reboot
Trying sideload next... it goes into sideload mode fine. I'm guessing that as soon as it tries to write something it will reboot, but I'll have to wait till I've re-downloaded and double checked md5s like a paranoid bastard first.
adb sideload ohdeargod.zip
---
Hmm, wiping cache partition alone works.
--
Noticed that on booting into CWM it displays the message:
Warning: No file contexts.
--
formating /system alone works
formatting dalvik causes reboot
formatting data causes reboot
--
sideload seems to have worked although its taking a long time to boot. I'll give it another 15 minutes.

Which firmware are you running?

Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Guich said:
Which firmware are you running?
Click to expand...
Click to collapse
Aaaand bingo gringo. It's booted.
Its a tmo m7. I haven't touched firmware afaik.
Resolved just in time for me to take it sailing today and drop it into lake Huron.

hypocritelecteur said:
[snip]....drop it into lake Huron.
Click to expand...
Click to collapse
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4

altimax98 said:
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Okay so I have a brand new HTC TMO One I got last week and its waterlogged. I drilled a hole in the back of the case to drain it and then left it on the radiator to make sure all that moisture is gone. I can't get it to post to TWRP.
Please help.
Deciding after recent events that XDA can be a dangerous place for sarcasm. So--thanks all, problem solved, no, no phone was damaged during the making of this thread. It was just my business partner, Lloyd, who fell in and became waterlogged. No amount of drilling or radiator baking could revive him.
Please help.

[Q] HARD Bricked Nexus 6 PLEASE HELP!!

My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.

can you get a custom recovery on successfully.........?
did you flash the stock image manually?

mediaman123 said:
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
Click to expand...
Click to collapse
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.

jeromechrome1 said:
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
Click to expand...
Click to collapse
Please! Anyone!

by manually do you mean flashing all the separate parts of the stock image separately, system, boot, recovery, cache and so on..........
I don't know what else to do after going through with that process.....

Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.

I'm a total newb here so take what I tell you with a grain of salt. I had your exact same problem on my Nexus 5. Every single thing you just described is what happened to my N5. And just like your N6...I was able to boot up into recovery (stock and TWRP), I was able to flash all the things manually and even used Wug's NRT. But then whenever I tried to actually boot up the device it could never pass the Google logo....basically EVERYTHING THAT IS HAPPENING TO YOU.
What I did to fix everything? Changed my battery. Sounds stupid and totally irrelevant but that did the trick. When I opened up my phone I noticed my battery had a nasty bulge and realized it was defective. Bought a new one for $25 and have never had any issues ever since. I suggest you look at your battery and see if that is the root of your problem. I have heard of the N6 having some batteries expanding and causing the back covers to pop off...this could be related to your problem.
Like I said I am a newb and thought I'd share my experience in the hopes it solves your problem.
Good luck buddy! :good:

my N6 is actually away getting repaired for the exact issue you described, expanding battery [assumed], and cover coming away from the bezel.....
I believe though that if you keep the device plugged into the wall when trying to boot up with this battery defect it will get through the boot, at least in the beginning anyway....
I believe also that if it was a battery issue the device would power off first, as opposed to just sticking on the Google logo.........

ldkud50 said:
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
Click to expand...
Click to collapse
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.

jeromechrome1 said:
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
Click to expand...
Click to collapse
Thats too bad. Maybe the device is hosed. RMA for a new one.

Same thing happened to me. As soon as I updated to the newest version of fastboot on my computer, everything worked...

jeromechrome1 said:
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I know, it's been a long time, but coud you tell me what happened to the phone?

Won't boot, stuck at Intel screen

Hi
I'm not too familiar with messing around with phones so please bear with me throughout!
Bootloader is locked and I'm running KitKat 4.4.2.
Screen froze the other day so I soft reset (Power + volume down), but it won't boot up and freezes at either the red M logo or at the Intel screen. Cleared the cache on Fastboot mode but this didn't make any difference. I have some really important photos that I'd like to keep, so I haven't cleared the user data.
Before upgrading to 4.4.2, on 4.1.2 I easily fixed this problem by flashing using RSD Lite and only having the "system signed" line in the XML code. This fixed it and I didn't lose any of my files. I'd have tried the same but have learnt that the 4.4.2 fastboot files aren't yet available.
Please help!
Thanks,
Sam

extons said:
Hi
I'm not too familiar with messing around with phones so please bear with me throughout!
Bootloader is locked and I'm running KitKat 4.4.2.
Screen froze the other day so I soft reset (Power + volume down), but it won't boot up and freezes at either the red M logo or at the Intel screen. Cleared the cache on Fastboot mode but this didn't make any difference. I have some really important photos that I'd like to keep, so I haven't cleared the user data.
Before upgrading to 4.4.2, on 4.1.2 I easily fixed this problem by flashing using RSD Lite and only having the "system signed" line in the XML code. This fixed it and I didn't lose any of my files. I'd have tried the same but have learnt that the 4.4.2 fastboot files aren't yet available.
Please help!
Thanks,
Sam
Click to expand...
Click to collapse
Sorry to say, but clearing userdata might be your only option. There is no way to recover data if it does not boot and the bootloader is locked.
If the bootloader were unlocked you could recover the photos via TWRP recovery. The big problem is that when you do the bootloader unlock process it erases your phone, so it won't help you now as it will erase everything.
There still isn't a 4.4.2 firmware file. We have to wait for it to be leaked, but that might never happen.
Sent from my XT1095 using Tapatalk

extons said:
Hi
I'm not too familiar with messing around with phones so please bear with me throughout!
Bootloader is locked and I'm running KitKat 4.4.2.
Screen froze the other day so I soft reset (Power + volume down), but it won't boot up and freezes at either the red M logo or at the Intel screen. Cleared the cache on Fastboot mode but this didn't make any difference. I have some really important photos that I'd like to keep, so I haven't cleared the user data.
Before upgrading to 4.4.2, on 4.1.2 I easily fixed this problem by flashing using RSD Lite and only having the "system signed" line in the XML code. This fixed it and I didn't lose any of my files. I'd have tried the same but have learnt that the 4.4.2 fastboot files aren't yet available.
Please help!
Thanks,
Sam
Click to expand...
Click to collapse
What @AGISCI is true. But if u can get to the Intel logo (part of the bootanimation) and have adb debugging enabled u could try to pull your important files from the phone. But if u don't have both adb debugging enabled than there is no chance. U could try to manually flash the system_signed from 4.1.2 firmware and see how far u can get as last resort. Hope that it boots and if possible u can extract the files.

I've got exactly the same problem today.
I have unlocked bootloader and I'm OK with erasing all data.
KitKat 4.4.2
What can I possibly do to make my phone working again? Is there any solution?
Many thanks.

Red_Man said:
I've got exactly the same problem today.
I have unlocked bootloader and I'm OK with erasing all data.
KitKat 4.4.2
What can I possibly do to make my phone working again? Is there any solution?
Many thanks.
Click to expand...
Click to collapse
With bootloader unlocked u can flash a custom recovery and wipe userdata through that. U can even wipe user data through the stock recovery if I am correct.
If that doesn't solve your problem, install a custom recovery and then restore the system partition of one of the KitKat twrp backups. And do a factory reset (data wipe) after that.

Hi everybody,
I do have the same problem with screen freezing on intel logo.
I'm ok to erase everything and I tried every options in the bootloader menu (recovery, factory,...) but it doesn't help.
Any idea?
Thanks,
Sylvain

I have the exact same problem since yesterday.
Already wiped cache and data, and still stuck. Any suggestions? :S

ybarrarubio said:
I have the exact same problem since yesterday.
Already wiped cache and data, and still stuck. Any suggestions? :S
Click to expand...
Click to collapse
Did you find a solution?

marty45 said:
Did you find a solution?
Click to expand...
Click to collapse
I had to wipe everything and start from scratch several times

Has anyone tried the XT907 files for a XT890 that won't boot, removing all the irrelevant lines from the xml? Worth a try maybe...?

xenonza said:
Has anyone tried the XT907 files for a XT890 that won't boot, removing all the irrelevant lines from the xml? Worth a try maybe...?
Click to expand...
Click to collapse
Doesn't work

i have the same problem with my xt890 please help mz

Issue returning N6 to stock - I've done it all

Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?

Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.

Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.

usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?

Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.