Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
kernco said:
Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
Click to expand...
Click to collapse
Just don't use ART for now, stay with Dalvik. Much stable atm.
alray said:
Just don't use ART for now, stay with Dalvik. Much stable atm.
Click to expand...
Click to collapse
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
kernco said:
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
Click to expand...
Click to collapse
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
zelendel said:
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
Click to expand...
Click to collapse
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
kernco said:
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
Click to expand...
Click to collapse
I would just to be safe. Mainly with the pre-Alpha tag of the ART compiler. I mean it may not even make it to be official.
Related
Hello everyone. Im having this really odd issue where the phone wont power off. I press and hold the power button down, and choose "POWER OFF" and it does the animation of powering off, then it goes dark....then in about 2-3 seconds it powers back on. Now i do have Fast Boot unchecked. Im also rooted and running the Dev edition of the HTC One. If i boot into recovery and choose the option to shutdown, it still reboots on its own. Very odd. Anyone care to help me out? Thanks
seems like cache error. try to clear cache in recovery.. if nothing happens .. clear data .. . yup then you will lose all data. but u will get into system atleast
jags_the1 said:
seems like cache error. try to clear cache in recovery.. if nothing happens .. clear data .. . yup then you will lose all data. but u will get into system atleast
Click to expand...
Click to collapse
I did all that as well. Same thing. I even wiped the phone and am now reverting back to stock to see if i can get it to power off correctly.
serialtoon said:
I did all that as well. Same thing. I even wiped the phone and am now reverting back to stock to see if i can get it to power off correctly.
Click to expand...
Click to collapse
Strange. Good luck. Does reverting back to stock mean you are running the RUU?
nugzo said:
Strange. Good luck. Does reverting back to stock mean you are running the RUU?
Click to expand...
Click to collapse
Yea. But im having a bit of an issue even with that. I consider myself a seasoned vet at this kind of stuff, but seem to be having a hard time with it. I tried to flash the RUU and it failed about 25% thru it, and now im at an HTC logo with exclamation signs on each corner. Kind of at a loss...but ill keep in screwing with it.
ok, so i reverted back to stock using the RUU and it STILL DOESNT TURN OFF!! I dont know what to do anymore. Faulty hardware? Kind of weird when everything else works fine.
serialtoon said:
ok, so i reverted back to stock using the RUU and it STILL DOESNT TURN OFF!! I dont know what to do anymore. Faulty hardware? Kind of weird when everything else works fine.
Click to expand...
Click to collapse
Nothng else you can do on your end. You've done it all. Tell them you installed the ruu and that didnt work. If its from a carrier, ATT, t-mobile.. Just take it to a corporate store, they should replace it. If its a Dev edition, gotta send it in. For me it wouldnt be much of an issue because i never turn my phones off.. But if you do turn them off, this is a major issue lol. They should replace it no problem.
nugzo said:
Nothng else you can do on your end. You've done it all. Tell them you installed the ruu and that didnt work. If its from a carrier, ATT, t-mobile.. Just take it to a corporate store, they should replace it. If its a Dev edition, gotta send it in. For me it wouldnt be much of an issue because i never turn my phones off.. But if you do turn them off, this is a major issue lol. They should replace it no problem.
Click to expand...
Click to collapse
Yea it is a developer edition phone. Ive done evrerything i can think of and i think i may need to send it in. What sucks is that i have already added my zagg on the back and added an SGP screen protector and i would hate to waste them. I also normally dont turn my phone off (if ever) but i dont want to end up with more hardware issues down the line. Im contemplating sending it back to HTC and ordering the Google edition when that is available..but im kind of happy with it as is. I have HTC on the phone now...lets see what they say. At this point im kind of curious as to why its doing this.
Hello everyone,
My HTC One M7 is stuck on the boot screen and I really don't know what to do anymore. Yesterday I deleted some music and 4gb of pictures from my phone to make some space. After that I checked for updates It said an update was available regarding some bugfixes and other issues. I let it download and install. At the end of the install process, I think I saw just the normal updating screen, but with the red pyramid exclamation mark icon. After that, it rebooted just like normal, first the white HTC screen, then the startup sound, and then the white HTC One screen. Only this time it didn't go further than that. My phone is not rooted or tampered with in any way. The only thing I did is download some cracked apps. Also I think I didn't update most of my apps for 2/3 weeks because I didn't have enough 'memory space' apparently.
I know a factory reset is the easiest thing to do, but if it's possible, I'd really like to fix the problem with all my data intact. My pictures etc are all back upped, and I have the HTC backup thingy (I think), but still, there's some things like WhatsApp messages I'd really like to keep.
I tried to just let it boot, maybe taking a little longer, but after 2 hours, the device gets pretty hot, and I'm afraid to let it overheat. However, after maybe half an hour/hour the white screen gets a bit brighter, indicating that there's still maybe something happening inside.
I'd be very happy if someone could help me with this!
Jugoslavija said:
Hello everyone,
My HTC One M7 is stuck on the boot screen and I really don't know what to do anymore.
Yesterday I deleted some music and 4gb of pictures from my phone to make some space. After that I checked for updates It said an update was available regarding some bugfixes and other issues. I let it download and install. At the end of the install process, I think I saw just the normal updating screen, but with the red pyramid exclamation mark icon. After that, it rebooted just like normal, first the white HTC screen, then the startup sound, and then the white HTC One screen. Only this time it didn't go further than that. My phone is not rooted or tampered with in any way. The only thing I did is download some cracked apps. Also I think I didn't update most of my apps for 2/3 weeks because I didn't have enough 'memory space' apparently.
I know a factory reset is the easiest thing to do, but if it's possible, I'd really like to fix the problem with all my data intact. My pictures etc are all back upped, and I have the HTC backup thingy (I think), but still, there's some things like WhatsApp messages I'd really like to keep.
I tried to just let it boot, maybe taking a little longer, but after 2 hours, the device gets pretty hot, and I'm afraid to let it overheat. However, after maybe half an hour/hour the white screen gets a bit brighter, indicating that there's still maybe something happening inside.
I'd be very happy if someone could help me with this!
Click to expand...
Click to collapse
In your phone's present state if you can not get back to Android OS, then your best option is a factory reset. You will lose your personal data on the phone.
Performing a factory reset using hardware buttons
If you can’t turn HTC One on or access settings, you can still perform a factory reset by using the hardware buttons on HTC One.
Press and hold the VOLUME DOWN button and then press and hold the POWER button.
Wait for the screen with the three Android images to appear, and then release the POWER and VOLUME DOWN buttons.
Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button.
Jugoslavija said:
Hello everyone,
My HTC One M7 is stuck on the boot screen and I really don't know what to do anymore. Yesterday I deleted some music and 4gb of pictures from my phone to make some space. After that I checked for updates It said an update was available regarding some bugfixes and other issues. I let it download and install. At the end of the install process, I think I saw just the normal updating screen, but with the red pyramid exclamation mark icon. After that, it rebooted just like normal, first the white HTC screen, then the startup sound, and then the white HTC One screen. Only this time it didn't go further than that. My phone is not rooted or tampered with in any way. The only thing I did is download some cracked apps. Also I think I didn't update most of my apps for 2/3 weeks because I didn't have enough 'memory space' apparently.
I know a factory reset is the easiest thing to do, but if it's possible, I'd really like to fix the problem with all my data intact. My pictures etc are all back upped, and I have the HTC backup thingy (I think), but still, there's some things like WhatsApp messages I'd really like to keep.
I tried to just let it boot, maybe taking a little longer, but after 2 hours, the device gets pretty hot, and I'm afraid to let it overheat. However, after maybe half an hour/hour the white screen gets a bit brighter, indicating that there's still maybe something happening inside.
I'd be very happy if someone could help me with this!
Click to expand...
Click to collapse
To be honest some of those cracked apps (which I wouldnt admit to use here) most likely changed things in the system which caused the update to fail. I would do a full wipe and stay away from cracked apps unless you like things like this happening.
zelendel said:
To be honest some of those cracked apps (which I wouldnt admit to use here) most likely changed things in the system which caused the update to fail. I would do a full wipe and stay away from cracked apps unless you like things like this happening.
Click to expand...
Click to collapse
It's just the standard 'a friend told me it was a good idea', only I didn't know it could screw up the system so hard.
I just tried wiping the cache partition in recovery mode, which unfortunately didn't help.
Is there any program out there that can still backup my files in some way or make me atleast access them? Or was it necessary for me to root the phone beforehand?
So, there's no program to still backup my files in any way?
Jugoslavija said:
So, there's no program to still backup my files in any way?
Click to expand...
Click to collapse
Unfortunately there's nothing you can do, If you had a Custom Recovery you'd have some options but not with stock. Flashing a custom recovery requires an Unlocked bootloader. Unlocking the bootloader will wipe the device
At best you may be able to use an RUU to restore your device (depending on you CID, MID and current version Main) But that also will wipe all personal data including the sd card.
Well I realized that the only thing I could do is doing a factory reset. After resetting my phone, the problem persisted. It was still stuck on the boot menu. So unfortunately, I'll have to send it for repairs. Thanks anyways for all the help and have a happy 2015.
Jugoslavija said:
Well I realized that the only thing I could do is doing a factory reset. After resetting my phone, the problem persisted. It was still stuck on the boot menu. So unfortunately, I'll have to send it for repairs. Thanks anyways for all the help and have a happy 2015.
Click to expand...
Click to collapse
Did you send your device for repair already? Does it have warranty? If there's no warranty you can still unlock your bootloader and fix this fairly easily.
Danny201281 said:
Did you send your device for repair already? Does it have warranty? If there's no warranty you can still unlock your bootloader and fix this fairly easily.
Click to expand...
Click to collapse
Yeah I sent it already. Well it should have warranty anyway, since they give you 2 year warranty with the phone, and the HTC One isn't even out for 2 years. It should be okay. I just wanted to let them fix it, so I don't have to bother. Thx anyway. :good:
So, I was clean flashing Titan Prime back into my XT1064 after testing CM12.
Everything went well, same apps, same configurations as always, no major changes.
I was about to reboot the phone when it did it by itself.
The boot screen (you know, the white one that burns your eyes) showed up, then it went away, and then oh surprise!, it came back again.
So the phone was in this bootloop within the boot screen.
I tried to enter to the Bootloader and the key presses (Power + Volume Down) did not work.
Every time I would try that, the phone screen would stay off for as long those keys were pressed down, and then, Bootloop.
After many tries I was about to let the phone stay in the bootloop until I find a solution here on XDA.
But I tried one more time, and lo and behold, it went into the Bootloader.
From there everything went as normal.
Now, the question is, could I have bad sectors?, could the Bootloader be corrupted?, could I have a ghost trapped?.
Thank you for answers and/or ideas.
And if any of you happens to be in my same situation, do not give up, let it be, try many times, and it finally will work (hopefully)
Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.
Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.
Tel864 said:
Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.
Click to expand...
Click to collapse
You do everything right, the phone gets screwed, it gets fixed, and the problem is something no one else has had so you have no freaking idea of why or what it was.
It is not my power button, the only times I use it is when I turn the screen on, and it would not be the reason because it made a difference when it was pressed.
I will try some fastboot commands to scan sectors, but I need to remember how they worked. The last time I used them it was when I had a Galaxy Note 1.
Lars124 said:
Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.
Click to expand...
Click to collapse
As noted on the first post, I did not do anything out of the ordinary. Same apps, same configuration as always.
The good thing is that I now can say I have every app that I need, with the configurations that I need, so I almost never need to change.
Let's hope it will not happen again.
Hey all, I recently got my nexus 6, and out of the box it worked fine. I started trying it out, and realized things were crashing quite often, like google play, and gmail. Then it prompted me to install the Android 5.1 update, which is when all this started.
Upon finishing the upgrade my nexus 6 cannot get past the Optimizing Apps screen, as soon as it gets onto the "Starting Apps" state, it will simply crash, and start over, booting again. This has been very frustrating since I just got this device and want to enjoy it. I have not rooted it, I have not tampered with it and the bootloader is locked. I tried cleaning the cache partition but that didn't help. So is anyone else experiencing this with their nexus 6? I really need a way to fix this, and if I have to flash the stock image onto it, then I will. But since the bootloader is locked is that even possible?
Please help me, I don't want to send it back in and wait another eternity.
Yes it's possible. However. Try a factory reset from recovery first.
graydiggy said:
Yes it's possible. However. Try a factory reset from recovery first.
Click to expand...
Click to collapse
I've done that a zillion times. It's not working, my phone refuses to get past the "Android starting..." screen. So if you could walk me through how to flash, since I couldn't find a guide online.
I called google support, and they want to replace it. So I'm gonna do exactly that.
I'm now on my third phone from google and they all do this. easily the worst customer service experience I've ever had in my entire life.
[email protected] said:
I'm now on my third phone from google and they all do this. easily the worst customer service experience I've ever had in my entire life.
Click to expand...
Click to collapse
third? that makes it seem as you are the one thats not doing something right. just saying. one, ok, it happens. two, chances are very slim, but it can happen, mist likely wont. three, you are doung something wrong. if you factory reset, then it boots without android is upgrading. when you add apps, change apps, or change things in your system, or wipe dalvik, then android is upgrading happens.
[email protected] said:
I'm now on my third phone from google and they all do this. easily the worst customer service experience I've ever had in my entire life.
Click to expand...
Click to collapse
DEFINATELY operator error...
they don't "all do this", otherwise the THOUSANDS of us here on XDA who flash things constantly without issue every day would be experiencing the same thing..
Hi, recently I've followed the guide here to root my tab s2 8" with android 6. All went well, if it wasn't for this little problem. I can't actually say if it showed up after or before the root, but I'm starting to think it's not something software.
Does anybody have any ideas on how to solve?
https://m.imgur.com/a/EFuuX
Eh, you activated those.. just turn them off..
Niii4 said:
Eh, you activated those.. just turn them off..
Click to expand...
Click to collapse
That's not my point, I activated those option to show that there a v3rticwl band where the touchscreen won't work properly
The right side (vertical area), aye?!
Well, the last thing you did was *root*.. thus I'd presume something wrong with the software.
Niii4 said:
The right side (vertical area), aye?!
Well, the last thing you did was *root*.. thus I'd presume something wrong with the software.
Click to expand...
Click to collapse
I actually done it a couple weeks ago
*up
I've noticed that I does the problem even in the twrp recovery
Did you try to restore your stock ROM image?
Niii4 said:
Did you try to restore your stock ROM image?
Click to expand...
Click to collapse
No, is there a guide?
https://www.howtogeek.com/240582/how-to-back-up-and-restore-your-android-phone-with-twrp/
update
i've tried everythink i could think of. First just formatted data from recovery, nothing happened (it still does it in the recovery itself)
then i've installed the stock nougat rom, nothing again, not even in recovery...
but i've noticed that each time i reboot the tablet the problem goes away and comes back progressively, at first is just a little jump from left to right and it keep getting worst and worst untill it grows to its normal width.
i really think that the problem is something physical about the tablet.
now the question is about how i can prepare the tablet before sending it in to get fixed.
What can i do?
just to point it out, the tablet never had an accident, alway in the cover, i does not present a single scratch or dent!
suggestions?
I'd say, it is time to consult a technician. Someone like Rossmann,
https://m.youtube.com/channel/UCl2mFZoRqjw_ELax4Yisf6w
Good luck.
DShot92 said:
update
i've tried everythink i could think of. First just formatted data from recovery, nothing happened (it still does it in the recovery itself)
then i've installed the stock nougat rom, nothing again, not even in recovery...
but i've noticed that each time i reboot the tablet the problem goes away and comes back progressively, at first is just a little jump from left to right and it keep getting worst and worst untill it grows to its normal width.
i really think that the problem is something physical about the tablet.
now the question is about how i can prepare the tablet before sending it in to get fixed.
What can i do?
just to point it out, the tablet never had an accident, alway in the cover, i does not present a single scratch or dent!
suggestions?
Click to expand...
Click to collapse
Use the factory code to enter the touch options and ensure the firmware versions match for the touch driver. If not tap the general update button.