I have a sprint htc one (m7) - rooted clockwork mod
I flashed CyanogenMod 10.2 and google apps. using clockwork mod
Got the nightly with goo manager
Then I restarted my phone, and CM starts loading.
Except it has been on the boot load screen (Blue circle chasing itself) for over an hour.
I read on forums that it may have been the i didnt wipe cache (thought i did, but maybe not)
So it say i should restart and redo it all, the only problem, I CANT RESTART.
When i try to restart, nothing happens except after 4-5 seconds the home and back button blink in sync as log ans i am hold the power button.
Tried just the power button, tried power and volume down, all the same
I cant even get to the battery to do a batt pull.
Any idea, and i apologize in advance if there is something easy i am not thinking of, I am getting flustered.
ASpeirs21 said:
I have a sprint htc one (m7) - rooted clockwork mod
I flashed CyanogenMod 10.2 and google apps. using clockwork mod
Got the nightly with goo manager
Then I restarted my phone, and CM starts loading.
Except it has been on the boot load screen (Blue circle chasing itself) for over an hour.
I read on forums that it may have been the i didnt wipe cache (thought i did, but maybe not)
So it say i should restart and redo it all, the only problem, I CANT RESTART.
When i try to restart, nothing happens except after 4-5 seconds the home and back button blink in sync as log ans i am hold the power button.
Tried just the power button, tried power and volume down, all the same
I cant even get to the battery to do a batt pull.
Any idea, and i apologize in advance if there is something easy i am not thinking of, I am getting flustered.
Click to expand...
Click to collapse
To simulate a "battery pull", hold the POWER + VOL DOWN buttons with the sensor under a bright light (not kidding), when the buttons start to flash, it will take about 30sec to a minute to reboot. Keep pressing VOL DOWN to enter bootloader.
Is CyanogenMod 10.2 compatible with Sprint? I've not used it so I wouldnt know, but I do know Sprint has a completely different partition table than all the other Ones, and is only compatible with ROMs specifically for Sprint.
I thought that goo manager automatically checked for compatibility.
and thank you did not know about the bright light part will try that now.
ASpeirs21 said:
I thought that goo manager automatically checked for compatibility.
and thank you did not know about the bright light part will try that now.
Click to expand...
Click to collapse
I was "messing around" with my phone today and got stuck, but had to do the POWER+VOL DOWN + bright light about 4 or 5 times till it finally worked. The good thing is the lights are blinking, so you know it's recognizing your input.
and I just looked at the thread, it says "CyanogenMod 10.2 to your HTC One (GSM)", Sprint is not a GSM variant as far as I know. I could be wrong, but before you flash any ROM, make sure it says Sprint compatible.
ASpeirs21 said:
I thought that goo manager automatically checked for compatibility.
and thank you did not know about the bright light part will try that now.
Click to expand...
Click to collapse
I would avoid using apps like goo manager or Rom manager to download flash roms. I'd recommend doing everything manually to avoid things like this. As far as a fix I think there's a few posts about this on the sprint section
Sent from my HTCONE using xda premium
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.
:/