[Q] Sprint HTC ONE stuck on white boot screen - Sprint HTC One (M7)

Hello,
I've just installed this ROM after wiping Cache/Delvik Cache and system wipe.
Now the phone is stuck on the boot screen and I can not get back into recovery to sort it out.
I held down power & vol+ buttons to get into recovery but nothing happens. The Home & Back buttons flash after 3 seconds then nothing happens.
Any thing else I should do to get into recovery ( TWRP)
My friend whop is a member asked this question on the Developers forum and so far no luck.
we have tried the following:
This is suggested by chogardjr: Plug your phone in to charge. Don't use a USB port for power. After you plug it in try the hard reboot again.
PLEASE HELP
Just for the sake of testing... Have him hold power without holding the volume. It should force reboot, not to the bootloader, so he can get a feel for how the reboot works. It can be finicky during a bootloop cause there are processes trying to run in the background. But it should do it if you hold power long enough.
Edit:
Also find out if the charge light comes on when he plus it in.
Tried and no joy.......

rking786 said:
Hello,
I've just installed this ROM after wiping Cache/Delvik Cache and system wipe.
Now the phone is stuck on the boot screen and I can not get back into recovery to sort it out.
I held down power & vol+ buttons to get into recovery but nothing happens. The Home & Back buttons flash after 3 seconds then nothing happens.
Any thing else I should do to get into recovery ( TWRP)
My friend whop is a member asked this question on the Developers forum and so far no luck.
we have tried the following:
This is suggested by chogardjr: Plug your phone in to charge. Don't use a USB port for power. After you plug it in try the hard reboot again.
PLEASE HELP
Just for the sake of testing... Have him hold power without holding the volume. It should force reboot, not to the bootloader, so he can get a feel for how the reboot works. It can be finicky during a bootloop cause there are processes trying to run in the background. But it should do it if you hold power long enough.
Edit:
Also find out if the charge light comes on when he plus it in.
Tried and no joy.......
Click to expand...
Click to collapse
I had a similar problem with a bad kernel flash and could not get the device to shut all the way off - thats why the keys are blinking. I plugged it in to a charger, left it like that for a few seconds, then unplugged, held it under a bright light and waited. After a few more seconds, it shut all the way down and I was able to boot to recovery in the usual way (power+down). You may have to try combinations or maybe not. But, you won't get to recovery until the phone shuts all the way down. High light under in the 'eyes', plugging and unplugging, and holding the power button for up to 30 seconds are all known ways to do this, but as was said before a bootloop has processes trying to run, so the machine can be 'confused' and have difficulty shutting down. Hope you are successful...

Thanks. I actually got it going with one of the answers posted for me, by powering it off under a bright light.
Sounds daft, but it works.

Related

[Q] Problem booting into Recovery

So.... Been playing with this for the last two days trying to root this phone.
I've rooted a few other phones, so I do have experience with the overall process, but I am unable to even boot this phone into Recovery. I have tried booting into recovery by holding down both volume buttons + power and from adb terminal "adb reboot recovery."
Neither method works. The phone will boot (or reboot from adb) and brings up the "at&t World Phone" screen and then nothing else appears. The first time I tried this it actually wouldn't boot up even after pulling the battery and trying to start normally, it still sat at the same screen. I let it sit all day today at the screen until the battery died. I was finally able to get it to boot up earlier.
If anyone can help, that'd be greatly appreciated. Let me know what info I need to add.
I usually just press and hold both volume buttons and power then release just the power button and keeping the volume buttons still pushed on the 2nd time the white at&t screen pops up... Works for me every time.
Sent from my SAMSUNG-SGH-I897 using XDA App
hold volume up+down and power key btw this is wrong section to post supposed to be in general
Oh sorry, didn't realize it was supposed to be posted in general.
I've tried the Volume Up/Down + Power and this does not work, as I stated originally.
I've also tried to do it from the adb shell, which also does not work.
Does anyone have any idea why I can't access recovery?
I"m having a similar issue. Holding volume up+down and power and releasing in any combination just boots the phone up. If I just hold volume up+down and power the phone alternates between the AT&T World Phone screen endless.
Yes u have to let go of the pwr button when the phone screen turns on
Sent from my SAMSUNG-SGH-I897 using XDA App
I've tried just about every combination of the Volume Up/Down + Power and no luck.
I've also tried the following ADB commands, with no luck, it just reboots the phone:
adb reboot recovery
adb reboot-boatloader
When I hold Volume Down + Power I get the a Yellow Triangle with a Android guy with a shove with the text "Downloading... Do not turn off Target!!!"
When I hold Volume Up + Power I get an Android guy with the following text: "POWER RESET or UNKNOWN UPLOAD MODE"
For kicks, I tried to to flash a rooted update.zip via the Volume Down + Power way with the Samsung update software, the same way I have done with the Samsung Moment. Wasn't sure if it'd work, but worth a try.
Any one else have any ideas or suggestions?
Phishie, do you have a final release version? Or anything special about the phone you have?
I just press the two volume buttons first (to make sure theyre pressed before you hit power), then press the power button, as soon as the screen turns on, I let go of everything and it works just fine, no need to have ridiculously complicated instructions.
The trick is to make sure both volume buttons are pressed BEFORE you hit power. Then release. Easy as pie
Also, if you guys are having too much trouble, just download the one click root/unroot. It will run, boot your phone into recovery, then all you have to do is scroll to install packages with volume key and hit power. Done.
Trust me, I am making sure I'm pretty the keys completely. I've literally tried it fifty times by now.
And I've also tried the One Click Root. This does not boot the phone into recovery either. It just sits at the AT&T World Phone screen forever and will actually get stuck here and will not boot up normal even by pulling the battery and powering it back up. It'll just get stuck at the for-mentioned screen. I have to connect it to adb and reboot it there to get it out of the loop it's stuck in.
that doesnt sound good. Maybe you need to try a factory reset? are you running stock rom and everything?
When I first got the phone I did a factory reset.
Yea, it's completely stock to my knowledge. But I have a different ROM than the final release version that everyone else has. This is a pre-production device.
same problem
I try all the combos as well, no luck, would the combos be different for 2e vs 3e recovery?
I try combo, it powers on, the same thing happens, the at-t comes up, goes for a second, then screen brightens, wait a bit and then the home row buttons light up, hangs there... doesnt matter which kernel or which rom I flash, same thing, adb and other stuff wont work as they need usb debugging enabled, which mine isn't.
Is there a way to mod the phone files and flash to enable usb debugging? Anyway to remap the buttons to 2 button vs 3 button?
Everyone post your methods for entering recovery please?

Captivate is freezing after trying to disable voodoo lagfix

When I tried to disable the voodoo lagfix my phone froze, after about 20 minutes i decided to pull the battery and now the phone freezes when trying to boot and even after plugging in the charger, it freezes on the battery load symbol. Unfortunately, the 3 button way to get to the recovery menu doesn't work. help me please??
I'm having the same problem - phone just hung on the kernel load screen (firebird 2) after trying to shut off lagfix - although I can get to a red recovery mode menu. Not that it's helping at this time. It would be nice if I could recover without a clean wipe of the phone.
Anyone have any ideas. I'll be scouring the threads...
You could try making a jig and flashing to stock http://forum.xda-developers.com/showthread.php?t=841512
how are you getting to the red recovery menu?
i have the same kernel and i'm running the firefly 1.5 rom
I can't boot into anything and the only solution i have so far is to make a jig or buy one and not have a phone for a little bit, which is going to suck..
I've tried the following combinations, just because I know people are going to ask.
1. take out battery, sim, etc.
2. leave out for about 15 seconds
3. plug in the battery, plug in usb and hold two volume buttons-> freezes while trying to load battery status
3.b same precedure as above except plug in usb first hold volume buttons then battery-> still frozen
3.c hold volume buttons, battery, then power button, let it cycle atleast 2 times and let go of power at att logo while holding the volume-> frozen at kernel loader
3.d same as above but with only one volume button at a time, both up and down-> no cigar
3.e all the precedures above while wildly pressing all the soft keys (home, search, yadda yadda) out of frustration -> thinking, gosh i'm screwed
did i miss out any secret other combinations or methods known to work?
I'd really like to do this without hardware, but making a jig kinda sounds like a fun project and i do have a soldering iron in storage somewhere...
xsamxoxo said:
how are you getting to the red recovery menu?
i have the same kernel and i'm running the firefly 1.5 rom
I can't boot into anything and the only solution i have so far is to make a jig or buy one and not have a phone for a little bit, which is going to suck..
I've tried the following combinations, just because I know people are going to ask.
1. take out battery, sim, etc.
2. leave out for about 15 seconds
3. plug in the battery, plug in usb and hold two volume buttons-> freezes while trying to load battery status
3.b same precedure as above except plug in usb first hold volume buttons then battery-> still frozen
3.c hold volume buttons, battery, then power button, let it cycle atleast 2 times and let go of power at att logo while holding the volume-> frozen at kernel loader
3.d same as above but with only one volume button at a time, both up and down-> no cigar
3.e all the precedures above while wildly pressing all the soft keys (home, search, yadda yadda) out of frustration -> thinking, gosh i'm screwed
did i miss out any secret other combinations or methods known to work?
Click to expand...
Click to collapse
I'm afraid not. This happened to someone I know and they told samsung the OTA update bricked it and AFAIK they fixed it for free. They never tried using a jig though, so if you don't want to wait to replace it or anything you could try a jig since it might work and the parts are pretty easy to get (and if you'd be replacing the phone, a jig is ALWAYS good to have anyway)
Just another note to throw in there, the computer recognizes the phone, but strangely my computer freezes while trying to read the media storage drives. I can't tell if the internal sd is mounted because of the ever-lasting wait but i'm almost positive its not.
Do adb commands work?
Sent from my SGH-I897 using XDA App
Thnikk said:
Do adb commands work?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
nope, it says "error device is offline"
You could try ... when the phone is booting and trying to catch it before it freezes is spam the heck out of the command adb reboot download then after hitting the enter button hit the up arrow and keep repeating until either the phone a) hopefully goes into download mode or b) freezes and throws the error.
Who knows.. might get lucky.
avgjoegeek said:
You could try ... when the phone is booting and trying to catch it before it freezes is spam the heck out of the command adb reboot download then after hitting the enter button hit the up arrow and keep repeating until either the phone a) hopefully goes into download mode or b) freezes and throws the error.
Who knows.. might get lucky.
Click to expand...
Click to collapse
it connects even though the phone is frozen. I'm heading over to "The Shack" pretty soon and just making a jig.
Thanks for all your help everyone.
Edit: Just confirming that with much dedication and a steady hand I finally have my captivate up and running with the help of the resistors. I also flashed the 3 button fix stock rom.
Well, I kept trying the least invasive methods first. Tried to reflash Firebird. Then went adb and such. In the end, it was pretty clear that it had hung at the lagfix correction, and I was dealing with a file system error. I was eventually able to get into download mode. The hardest discovery was finding that I had gotten the wrong drivers from samsung. The ones in the [stock rom] odin master clear page were what I should have been using. When I loaded those, the computer recognized that I had a phone and not a "serial gadget" and then I knew I was close. Odin finally saw the phone, and a couple tries at "light" re-stocking failed at file analysis, so I did the repartition (aha, file system error), and it shot through the whole process and I had my phone back and flashed to Serendipity in about 20 minutes.
But I would like to know about the red menu. That was unexpected (blue for standard, green for cwm).
No need for a jig. I had access to some phone functions, most importantly, download mode.

Soft Bricked HTC One (URGENT)

Hey, a fellow XDA member has managed to soft brick his One. He flashed a bad zip file, and his phone boot loops. He cannot access the boot loader as he has Fast Boot turned on in Settings - Power, however he can't turn this off as he can't turn the phone on. Has anyone got any advice?
MacHackz said:
Hey, a fellow XDA member has managed to soft brick his One. He flashed a bad zip file, and his phone boot loops. He cannot access the boot loader as he has Fast Boot turned on in Settings - Power, however he can't turn this off as he can't turn the phone on. Has anyone got any advice?
Click to expand...
Click to collapse
power + volume down try that
dirtbikerr450 said:
power + volume down try that
Click to expand...
Click to collapse
It doesn't work because Fast Boot is turned on in Settings
im just guessing here but plug it into a computer and then try power + volume down. a couple of times
dirtbikerr450 said:
im just guessing here but plug it into a computer and then try power + volume down. a couple of times
Click to expand...
Click to collapse
No the LEDs just flash forever
put the phone under a bright light.
hold down power, lights will flash and phone will shut down in about 15-20 seconds
then hold volume down and power to get back to bootloader
gunnyman said:
put the phone under a bright light.
hold down power, lights will flash and phone will shut down in about 15-20 seconds
then hold volume down and power to get back to bootloader
Click to expand...
Click to collapse
hello,
actually it's my problem. thanks MacHackz for all the help he already has done for me.
I tried that with a bright light. it worked in this way that phone really turns off, but as soon as I remove the light, it turns on again. I cannot get it into bootloader.
EDIT: I flashed the phone with MAG-light from the start of charging. screen was black, but buttons started to blink. it went into hboot, and from there I went into recovery. I went to a reboot and press power off. I'll recharge it fully, and then I'll try to sideload a new ROM.
EDIT II: I tried to charge it, but it simply wont stay off. as soon as I plug the cable in, it turns on! I manage to enter HBOOT so I went into recovery and there phone is charging. so, I'll recharge it there and upload a RUU.
does anyone has right RUU? I have EU version from UK.
Did you not make a backup before flashing ??, there is a list of roms on Mikes Android Revolution Rom post - have a look at his guide
Heres another list also http://forum.xda-developers.com/showthread.php?t=2194707
gunnyman said:
put the phone under a bright light.
hold down power, lights will flash and phone will shut down in about 15-20 seconds
then hold volume down and power to get back to bootloader
Click to expand...
Click to collapse
many thanks man indeed, you helped me like anyone before !!!!!!!!!!!!!!!!!!!!
wow...i've been sitting in my dark bedroom for the past 90 minutes trying everythign to wake up my damn phone after it crashing and not coming back to life. ADB was still responsive but none of the reboot commands would do anything. FINALLY found this, went in the bathroom, held the phone up to the light with the power button help down and 10 seconds later it's back to life. double you tee eff...

[Q] Samsung Galaxy Exhibit II 4G (SGH-T679) Can't Boot

My Galaxy Exhibit II 4G is about a year old, rooted and i have CM11 installed. Everything was fine, I had it plugged in (charging) and i was downloading an app (Camscanner) from the Mobogenie store when suddenly the phone shut off and the battery icon appeared with the loading circle in the middle.
This did not stay on for long as the screen would go off and this would again appear. After pulling the battery and removing the charger, then reinserting the battery, the phone would just flash the SAMSUNG logo in this very same manner.
I am unable to get into either recovery or download modes and when i try this combination (VOL UP + VOL DWN) i get:
RAMDUMP MODE
Cause: Force Upload
I have been reading forums for hours and i have found nothing. Is my device bricked? What can I do to recover it? Please, any help would be greatly appreciated :crying:
What happens if you try vol. up + power, or vol. down + power?
jfbs said:
What happens if you try vol. up + power, or vol. down + power?
Click to expand...
Click to collapse
Thanks for replying. Nothing happens. It just continues to reboot like I'm not doing anything. The only way I'll get a reaction out of it is with vol up + vol down
It can be tricky. This post may be clear http://forum.xda-developers.com/showpost.php?p=32437850&postcount=6
The link you sent me to sounds similar to my problem, except I wasn't trying to update the firmware. The crash was spontaneous.
However, neither of those methods work. As soon as I put in the battery the SAMSUNG logo appears, then disappears and reappears and it continues like that... Pressing the power button does nothing, whether by itself or with the volume up/down button
I am beginning to panic
What happens when it's connected to power?
Adrian Gobourne said:
...battery icon appeared with the loading circle in the middle.
Click to expand...
Click to collapse
Anyway, after many hours of investigation I discovered it was a hardware problem. The power button was stuck and so it forced it to reboot repeatedly. It also explains why it (the power button) was unresponsive. Disassembling the phone and freeing up the power button solved the problem.
P.s. Your build of CM11 is boss
I have same problem with power button. Had to tweak it hard cause it was so sensitive.
It's the first time it's happened to me. Probably because I dropped it so many times
Strange, ...
Adrian Gobourne said:
My Galaxy Exhibit II 4G is about a year old, rooted and i have CM11 installed. Everything was fine, I had it plugged in (charging) and i was downloading an app (Camscanner) from the Mobogenie store when suddenly the phone shut off and the battery icon appeared with the loading circle in the middle.
This did not stay on for long as the screen would go off and this would again appear. After pulling the battery and removing the charger, then reinserting the battery, the phone would just flash the SAMSUNG logo in this very same manner.
I am unable to get into either recovery or download modes and when i try this combination (VOL UP + VOL DWN) i get:
RAMDUMP MODE
Cause: Force Upload
I also get ram dump mode error when trying to manually boot recovery.
I have been reading forums for hours and i have found nothing. Is my device bricked? What can I do to recover it? Please, any help would be greatly appreciated :crying:
Click to expand...
Click to collapse
OK so I'm no expert or anything but maybe my experience with this Model might be able to help you a little bit. I have the same model and it was doing the exact same thing however I haven't rooted it. And I've since corrected the issue on mind particularly it appeared that it was the charge port and/or USB that either had a bad connection or possibly it was boot looped. However with me not rooting the I didn't understand how it could be booted Looped so I started playing around with holding the power button playin with USB things of this nature and what I found was that if I hold the USB to one side either left or right, this allowed me to help a boot farther into it sequence at first to just show the Samsung logo over and over then I could get it to get to the boot sequence about halfway through the boot animation until I finally got to the exhibit screen where displays its model and 4G status. I accomplish this by holding the USB to one side and pushing and holding the power button intermittently throughout the boot. Once I hit the unlock screen unlock the device and I immediately factory data reset it. I'm under the impression that mine was possibly I think that mine was somehow a corrupted bootloader or software still I don't know what caused it to backed up to this day occasionally it'll shut itself down and reboot on me that's why I'm here today I've got all the parts and pieces I need to flash a new rom and hopefully new software the new work over I'll be good to go I also cleaned the USB port made sure that it was still snug to the board all of the good stuff. I don't know if it'll help you but I had the same situation I thought you'd like to know that it was probably not what you were doing with the phone it may just be the software itself with this particular phone see I done nothing that you didn't had the exact same problems. I hope it was somewhat helpful if you haven't gotten it unlocked or re-booted yet. Then maybe just play around with the power sources and power buttons. And see if you can get the same results I did

[Q] Could anyone please confirm if it's totally bricked?...

Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.
Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.
KomuroXV said:
Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.
Click to expand...
Click to collapse
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.
Seanie280672 said:
Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.
Click to expand...
Click to collapse
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Fain11 said:
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.
Click to expand...
Click to collapse
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.
KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.
Click to expand...
Click to collapse
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again
Seanie280672 said:
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again
Click to expand...
Click to collapse
KomuroXV said:
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
If only I could find a way to the bootloader mode, I would be so happy.
q.q
KomuroXV said:
If only I could find a way to the bootloader mode, I would be so happy.
q.q
Click to expand...
Click to collapse
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.
KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)​
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN
Fain11 said:
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.
Click to expand...
Click to collapse
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
nkk71 said:
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)​
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN
Click to expand...
Click to collapse
Oh... yes, I've heard about the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.
KomuroXV said:
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
Oh... yes, I've heard abot the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.
Click to expand...
Click to collapse
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.
Seanie280672 said:
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.
Click to expand...
Click to collapse
Did just that, right at those two little spots,but now the trick's not working, even though it had before, only I'm not sure if it was flashing to the two-little-spots.
Phone was charged and off. I turned it on holding Power+ Volume Down, with the phone's two spots facing straight to the flashlight.
It went straight into the bootloop still.
Are you sure it is there, and not right in the front or back camera?
Is it bricked?
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.
hugof99 said:
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.
Click to expand...
Click to collapse
Well, unlike your case, my phone was actually 99.9% clean since I fixed it with the RUU. I don't think there's a ROM related issue with these reboots my phone has now.
Problem: Turned phone off while it was doing something inside stock's Recovery. Now got caught in an infinite reboot because of that,
It is actually something like this.
http://www.youtube.com/watch?v=85HtJYcVAos
http://www.youtube.com/watch?v=rai4nCciKBg
http://www.youtube.com/watch?v=W5PCJYKaCrE
Just that mine is HTC One, and, well, besides from that screen it's also rebooting on his own every 8-10 seconds.
When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?
iElvis said:
When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?
Click to expand...
Click to collapse
Just as it sounds. I pressed down the power button to turn it off while Recovery was starting, and soon after that, the infinite bootloop started.
The RUU was 100% good, and I tested everything I could before trying to flash a ROM again.
But, just in case, it was this one:
http://www.htc1guru.com/2013/11/verizon-ruu-zip-1-10-605-10-posted/
Anyway, as I said, after I checked everything around the phone, I went to bootloader, clicked recovery by accident, and on reflex turned it off pressing down the power button.
Since then, there's been an infinite bootloop, rebooting every 8 to 10 seconds.
Sadly, and I guess it's because it was freshly flashed from a RUU, I can't access through ADB either.
q-q
Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684
iElvis said:
Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
I've been trying to do this for days on my own (couldn't get help) but I finally managed to install a Unbuntu and run the sudo ./revive.sh
[email protected]:~$
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ chmod +x revive.sh
[email protected]:~/Downloads$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
The phone is actually connected to an USB 2.0 port, rebooting on his own still, but connected.
It's not detecting it though.
:/

Categories

Resources