So last night for no apparent reason to my knowledge while my phone, my phone restart to the boot screen, the one with the "HTC one" and the disclaimer in red font at the bottom. And it just kept starting right back to that screen without ever getting passed it. So basically, it would just sit there and vibrate like every two minutes. I can get it to stop by doing the "hold power volume up + volume down" restart method, but that only grants be about a hour before it does it again, even if I am not using my phone. I changed nothing on my phone all of yesterday.
Android version
5.0.1
Htc sense version
6.0
Software number
ViperoneM8 4.3.0
Htc SDK
6.55
Kernel
3 4.0_g6af28ec
[email protected] #1
SMP PREEMPT
Related
I have a pulso tablet, model number is p10c, android version 4.0.3, kernal version 3.0.8 [email protected]#1, build number 20120618-A723A
One day i turned it on and its just stopped working comes up with the android robot, then boots up with android written on it then boots up white screen with the pulso logo, then it turns off and just keeps going through the same process. Anybody know how to fix this
Below is my info from my main thread int he HTC One Q and A section thought I should post here since I wasn't getting anywhere with help.
I
have succesfully gained s-off and super cid between now and then also updated my firmware to the latest and still keep getting the sleep of death on CM based roms. i've tried vanilla rootbox and cm 10.1 nightlies, tried Ady's MIUI and illusion rom and a few others all keep on giving me the Sleep Of Death right after the screen goes off when not in use.
I can note that I can use the roms without a single problem at all if I do not let the screen go off...
So i've posted on a number of threads and I thought I'd sum up everything or all the information here and hope I can get some more help.
So here's the info
- - - -
Logs from rootbox
LOG CAT - http://www.mediafire.com/download/7b.../important.txt
KERNEL LOG/dmesg - http://www.mediafire.com/download/hh...toql/dmesg.txt
- - - -
It is an Australian OPTUS HTC One with the Optus_001 CID or whatever it is exactly.
Bootloader - Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.020
eMMC-boot
Mar 11 2013,22:16:05:-1
ClockworkMod Recovery v6.0.3.2 installed
The back of my device says its Model is an PN07140
On stock rom (only rooted and unlocked bootloader) My software info is as follows:
Android Version 4.1.2
HTC Sense is 5.0
Software Number is 1.29.980.2
The HTC SDK API level is 5.12
The kernel version is: 3.4.10-g42e6c45
[email protected] #1
SMP PREEMPT
Baseband: 4A.14.3250.13_10.33.1150.01L
Build number: 1.29.980.2 C:164689 release-keys
Browser version: WebKit/534.30
Phone name - HTC_PN071
- - - - - - - - - -
I have talked with codeworkx about the issue being CM based and gave logcat and kernel logs to him from rootbox rom in which he thinks the sleep of death is caused by a kgsl derp (honestly have no clue what the hell it really is at all)
I've attempted Clean installs, Patches if any and attempts at clearing the cache, dalvik etc etc to try and get the rom to work.
- - - - - - -
I have come across a weird factor while running Ady's MIUI rom that if I set the theme to the Superman theme with the animated Lockscreen I can SOMETIMES wake the phone within 3-5 or so seconds of pressing the power button.
I haven't been able to actually re-produce the rare occasion firmly but I found it happened with that theme applied.
I've tried the swipe2wake things without any luck.
- - - - - - - - - - -
So I'll keep this thread going to try and get help. I was told to update my firmware or try to but I search for optus firmware and find none, not to mention there hasn't been an update as of yet (that I have received or know off) from optus yet for my HTC One.
Hopefully I will be able to get this fixed and Use CM based roms...
- - - - -
ADDITIONAL INFO I FORGOT - I don't mess with CPU/performance settings and leave them all stock/default.
It's possible that you have more problems, but I'd try doing the battery pull while plugged into the PC again. Be sure to not put it back in until after the notification/charge light turns off. If it starts blinking red and green, start over again. If it doesn't work then you'll need to send the phone into htc.
CyanogenMod has the "trackball wake" and volume rocker wake" already on it.
Diablo67 said:
It's possible that you have more problems, but I'd try doing the battery pull while plugged into the PC again. Be sure to not put it back in until after the notification/charge light turns off. If it starts blinking red and green, start over again. If it doesn't work then you'll need to send the phone into htc.
CyanogenMod has the "trackball wake" and volume rocker wake" already on it.
Click to expand...
Click to collapse
You can't remove the battery from an HTC one...
Bump
Bump!
If anyone cares to help
this is part of a logcat http://i.imgur.com/f5ERkQI.png
from me running MIUI
while trying to wake from sleep of death...
Anything you can see in it that could help? (I have no idea what I'm looking for or how to fix)
Hardware : -----
Model : 11_gq2000s_fwvga
Build number : 11_gq2000s_fwvga_20130606
Build date UTC : 20130606-081832
Android v : 4.2.1
Baseband v: MOLY.WR8.W1248.MD.WG.MP.V6.P4, 2013/05/08 18:36
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #6 SMP Thu Jun 13 17:41:18 CST 2013
I have had this delivered from DHGate today. I have NOT flashed it, rooted it or anything. Its as it came out of the box!
I set up the phone from scratch logging on to my network, setting up Google and as soon as it says the phone is ready to use, the phone j reboots, and reboots over and over and over.I have been through this 5 times now each time doing a hard reset and trying again.
It also reboots when recieving a call or an SMS.
if I skip the Google Set Up, and Do not connect to wifi or have a SIM card in and skip through all the set up steps till I get to the home screen it works fine and does not crash and go through the reboot cycle.
So basically i have found it crashes after attempting to log into Google Accounts like Playstore, Gmail and the like.
It crashes when receiving an SMS or a Phone Call.
I dont want to send it back if possible, just make it work with a different OS or ROM to fix it. Either another 4.2.1 or 4.2.2.
Is there anyone that can help at all? I would be so thankful!
It seems that I may not have charged the battery up long enough for the initial charge.. The seller suggested 8hours so going to go for 12 or 13 hours charge and see what that does.
Ads1969 said:
It seems that I may not have charged the battery up long enough for the initial charge.. The seller suggested 8hours so going to go for 12 or 13 hours charge and see what that does.
Click to expand...
Click to collapse
That didn't work. I still have the same problem, no one has come up with any suggestions so far. *sigh*
fix it yet?
Ads1969 said:
That didn't work. I still have the same problem, no one has come up with any suggestions so far. *sigh*
Click to expand...
Click to collapse
Hi,
I have similar phone did you manage to get it fixed?
I have a droid razr that was on 2.3.5 and i wanted to put the JB on it. so i got the bat utility and put the phone into fastboot, did the software on there with the wipe. Now when the phone screen is one it goes crazy, it flickers and the bottom half of the screen has like these checkered things on it. if i click the home key or the back key it will go away for a second then come back.
I have a feeling when i did the update maybe something was not compatible with the SW? maybe the radio vs the boot? or radio vs the S/W? but the bat utility installed the new radio on there. Has anyone has this issue?
another weird thing i notice is that the volume down + power key does not force a shut down, but it takes a screen shot instead. And i know its not the screen issue, because in fastboot mode, the phone does not freak out.
System Version - 98.72.16.xt912.Verizon.en.US
Android - 4.1.2
Baseband - CDMA_N_05.21.00RLTEDC_U_09.1D.00
webtop version - wt-3.0.0
Kernel - 3.0.8gbacb1cf / [email protected] #1
build number - 9.8.2O-72_VZW-16
thanks
eric303 said:
I have a droid razr that was on 2.3.5 and i wanted to put the JB on it. so i got the bat utility and put the phone into fastboot, did the software on there with the wipe. Now when the phone screen is one it goes crazy, it flickers and the bottom half of the screen has like these checkered things on it. if i click the home key or the back key it will go away for a second then come back.
I have a feeling when i did the update maybe something was not compatible with the SW? maybe the radio vs the boot? or radio vs the S/W? but the bat utility installed the new radio on there. Has anyone has this issue?
another weird thing i notice is that the volume down + power key does not force a shut down, but it takes a screen shot instead. And i know its not the screen issue, because in fastboot mode, the phone does not freak out.
System Version - 98.72.16.xt912.Verizon.en.US
Android - 4.1.2
Baseband - CDMA_N_05.21.00RLTEDC_U_09.1D.00
webtop version - wt-3.0.0
Kernel - 3.0.8gbacb1cf / [email protected] #1
build number - 9.8.2O-72_VZW-16
thanks
Click to expand...
Click to collapse
Have some issue on NorthEU phone (XT910). But on previous one (XT910 DE) do not have this issue. It looks like hardware issue.
eric303 said:
I have a droid razr that was on 2.3.5 and i wanted to put the JB on it. so i got the bat utility and put the phone into fastboot, did the software on there with the wipe. Now when the phone screen is one it goes crazy, it flickers and the bottom half of the screen has like these checkered things on it. if i click the home key or the back key it will go away for a second then come back.
I have a feeling when i did the update maybe something was not compatible with the SW? maybe the radio vs the boot? or radio vs the S/W? but the bat utility installed the new radio on there. Has anyone has this issue?
another weird thing i notice is that the volume down + power key does not force a shut down, but it takes a screen shot instead. And i know its not the screen issue, because in fastboot mode, the phone does not freak out.
System Version - 98.72.16.xt912.Verizon.en.US
Android - 4.1.2
Baseband - CDMA_N_05.21.00RLTEDC_U_09.1D.00
webtop version - wt-3.0.0
Kernel - 3.0.8gbacb1cf / [email protected] #1
build number - 9.8.2O-72_VZW-16
thanks
Click to expand...
Click to collapse
You should flash 4.1.2 full fastboot package with rsd lite. It will be fine if it's software issues.
I've been troubleshooting this issue for a few days now and haven't had any luck.
The issue started after I updated to Android Revolution HD 7.1 by mike1989 -- which had issues because I hadn't upgraded my firmware yet -- so I attempted to upgrade to HTC One 1.40.401.5 (WWE) firmware, however I couldn't get the firmware to flash, so I reverted back to Android Revolution HD 5.2 by mike1989, and now I have this issue.
Here's the issue step by step:
Phone is off, turn on and boot to home screen
Hit power button to turn display off, display turns off
Hit power button to turn display on, display turns on
Hit power button to turn display off, phone reboots
And here's what I'm running:
android version: 5.0.2
rom: Android Revolution HD 5.2 by mike1986
kernel version: 3.10.49-g4ee4c46 [email protected] #1 SMP PREEMPT
baseband version: 01.01_U11440221_60.04.50305G_F
build number: 1.32.401.17.CL506785 release-keys
cid: 11111111
mid: PJA11000
S-OFF
OS-1.32.502.9
Hopefully someone on XDA can point me in the right direction. Thanks.
chardy52 said:
I've been troubleshooting this issue for a few days now and haven't had any luck.
The issue started after I updated to Android Revolution HD 7.1 by mike1989 -- which had issues because I hadn't upgraded my firmware yet -- so I attempted to upgrade to HTC One 1.40.401.5 (WWE) firmware, however I couldn't get the firmware to flash, so I reverted back to Android Revolution HD 5.2 by mike1989, and now I have this issue.
Here's the issue step by step:
Phone is off, turn on and boot to home screen
Hit power button to turn display off, display turns off
Hit power button to turn display on, display turns on
Hit power button to turn display off, phone reboots
And here's what I'm running:
android version: 5.0.2
rom: Android Revolution HD 5.2 by mike1986
kernel version: 3.10.49-g4ee4c46 [email protected] #1 SMP PREEMPT
baseband version: 01.01_U11440221_60.04.50305G_F
build number: 1.32.401.17.CL506785 release-keys
cid: 11111111
mid: PJA11000
S-OFF
OS-1.32.502.9
Hopefully someone on XDA can point me in the right direction. Thanks.
Click to expand...
Click to collapse
It looks like to me that you are running the new kernel (3.10.49-g4ee4c46) from the new firmware with the older version of the rom that is causing your reboots. You should start from the beginning and try to flash the 1.40 firmware and then install the new rom version and you shouldn't have any problems.
Ended up having the exact issue, but on a different ROM and upgrading to a newer firmware but the issue is the same, the fix is just to flash the firmware you were on previously
kash20 said:
Ended up having the exact issue, but on a different ROM and upgrading to a newer firmware but the issue is the same, the fix is just to flash the firmware you were on previously
Click to expand...
Click to collapse
What if I want to upgrade the firmware? Should I wipe down to scratch and start over in that case¿?
rpimentel1 said:
What if I want to upgrade the firmware? Should I wipe down to scratch and start over in that case¿?
Click to expand...
Click to collapse
If you want to upgrade the firmware, you just need a ROM that supports it, the issue is some custom ROMs use a different kernel meaning there are issues like the one mentioned above, upgrading firmware is a really easy process, just grab one from the following threads
http://forum.xda-developers.com/one-m9/development/ota-1-32-401-15-firmware-noredtext-t3072571
http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678
Make sure your device is S-OFF and you've got the right firmware for your device, then it's just a matter of running two commands (both of which are found in the threads linked)
kash20 said:
Make sure your device is S-OFF and you've got the right firmware for your device, then it's just a matter of running two commands (both of which are found in the threads linked)
Click to expand...
Click to collapse
Brilliant! Thanks a lot - I was really scratching my head at this problem.