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.
Related
I took my tablet to the beach. It never went to the beach just from my car to the house. My TF201 died on the ride home. The night before was the last time i used the keyboard.
When I got home I plugged in the tablet and began trying to install CM9. I had already rooted my prime and downloaded the bootloader unlock. I had Clockwork installed but that was not working so I uninstalled it and installed GooManager and TWRP. I made a backup then tried to flash CM9 I thought it worked but my tablet just got stuck in the CM9 boot screen for about 20 mins. I restarted the tablet and tried doing a factory reset than flashing the rom that did not work. I got a MD5 file missing error. I restored my backup and tried DLing another copy of CM9. I have tried flashing it a bunch and now it just restarts with nothing changed.
Now when I try to plug the dock in the screen turns off and will not turn on while docked unless the tablet restarts while docked. None of the keys work but the touchpad does.
If I try to open the camera I get unfortunately the camera has stopped working.
android version: 4.0.3
GPS Version: V6.9.20
Wi-Fi version: V6.01.24
Bluetooth version: 9.29
Camera Version: tf201-0x9900
touch panel version : mxt-2.0 bulid-170
Kernel version: 2.6.39.4-g37d06fc [email protected] # 1
build number iml7k.usepad-9.4.2.28-20120525
Pad EC version: TF201-Pad-2015
MobileDock version: TF201-DOCK-0206
PLEASE HELP ME. I USE THIS THING EVERY DAY AND NO KEYBOARD IS KILLING ME.
after looking at the specks I am assuming that having the cyanogenmod kernel and not CM9 is causing the problem but I dont know what to do from here.
I took my tablet to the beach. It never went to the beach just from my car to the house. My TF201 died on the ride home. The night before was the last time i used the keyboard.
When I got home I plugged in the tablet and began trying to install CM9. I had already rooted my prime and downloaded the bootloader unlock. I had Clockwork installed but that was not working so I uninstalled it and installed GooManager and TWRP. I made a backup then tried to flash CM9 I thought it worked but my tablet just got stuck in the CM9 boot screen for about 20 mins. I restarted the tablet and tried doing a factory reset than flashing the rom that did not work. I got a MD5 file missing error. I restored my backup and tried DLing another copy of CM9. I have tried flashing it a bunch and now it just restarts with nothing changed.
Now when I try to plug the dock in the screen turns off and will not turn on while docked unless the tablet restarts while docked. None of the keys work but the touchpad does.
If I try to open the camera I get unfortunately the camera has stopped working.
android version: 4.0.3
GPS Version: V6.9.20
Wi-Fi version: V6.01.24
Bluetooth version: 9.29
Camera Version: tf201-0x9900
touch panel version : mxt-2.0 bulid-170
Kernel version: 2.6.39.4-g37d06fc [email protected] # 1
build number iml7k.usepad-9.4.2.28-20120525
Pad EC version: TF201-Pad-2015
MobileDock version: TF201-DOCK-0206
PLEASE HELP ME. I USE THIS THING EVERY DAY AND NO KEYBOARD IS KILLING ME.
after looking at the specks I am assuming that having the cyanogenmod kernel and not CM9 is causing the problem but I dont know what to do from here.
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)
Hi
My s2 int touch screen become freezed and I can move some some part of the touch screen. The apps keep running. So the fix is u press thr the power button and screen goes off press it again and the touch is working perfectly. Same thing happens after phone go to sleep. All buttons are working and lcd test is passed. What do I do ? Can this be due bricking?
Tip 1: I have no idea why n00bs think using a title like 'Urgent Help' somehow either entitles them to, or will result in them receiving said help. Many people here (me included) will ignore threads like this & not help you at all because we've seen millions of threads like this before & none of them were/are urgent (we're not paid employees of XDA, you know ?)
Tip 2: You've told us nothing about the phone ;what firmware it's running, if you've modified it in any way, how long you've had the phone, etc. How would anyone here possibly be able to guess at what the issue might be without any information whatsoever ?
Its stock firmware ics upgraded to jelly bean. Xwlss. Previouly the cygan mode 10.1 was installes. The software got currpt and the guy installed stock rom ics which I upgraded to jelly bean.
Tell me what else I need to tell you. I purchased this s2 from a friend he had a custom rom installed.
s2
please rewrite the mobile imei 100% resolved
dhinesh3004 said:
please rewrite the mobile imei 100% resolved
Click to expand...
Click to collapse
how do i do that ??
IMEI Number is same as that on the box.
Android Version: 4.1.2
Base Band Version: I9100XXMS2
Kernel Version: 3.0.31-1156082 [email protected]#3SMP PREEMPT Mon 22 April KST 2013
Build Number: J2054KI9100XWLSS
Some one please help.
The issue is that.
1. Touch Screen Stops Working
2. Power Button, Volume Up/Down Working.
3. When i press power off an than again I wake the device, touch screen doesnot freeze
4. When I am done, the screen times out, the same problems occurs again
5. All apps are running (music plays, games continue to run)
6. Factory reset didnt solve the problem.
How did u factory reset? Try doing wipe data and wipe cache from recovery and see if the issue persists. If it does, flash another stock firmware and check again.
"To err is human, to forgive is divine."
Sent from my SGS II
Reflash ROM with factory reset...see my signature.If that doesn't help,then it's a battery failure.
did a clean install and factory rest/cache rest. the problem is still there. any help ????
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.