I did a restore of my One-X to stock rom according to this tutorial.
http://design-extreme.net/restore-ht...-to-stock-rom/
This all went well and without problems. The RUU I flashed is this one.
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed
When I now startup the phone it all works perfect. Then the phone says there is an OTA (to 3.20 I believe)
I download and install the OTA and the phone restarts, but after restarts the phone's touchscreen does not work anymore.
I solved this for now by installing the 3.14RUU again, then it works again. But of course I would like to be able to install the OTA's
To me it sounds like a driver problem in the new version that prevents the touchscreen from working. Anyone have idea how to solve this?
I tried different boot.img after the OTA update but none of them solved the problem. Somebody here who has a good idea?
Xanion said:
I did a restore of my One-X to stock rom according to this tutorial.
http://design-extreme.net/restore-ht...-to-stock-rom/
This all went well and without problems. The RUU I flashed is this one.
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed
When I now startup the phone it all works perfect. Then the phone says there is an OTA (to 3.20 I believe)
I download and install the OTA and the phone restarts, but after restarts the phone's touchscreen does not work anymore.
I solved this for now by installing the 3.14RUU again, then it works again. But of course I would like to be able to install the OTA's
To me it sounds like a driver problem in the new version that prevents the touchscreen from working. Anyone have idea how to solve this?
I tried different boot.img after the OTA update but none of them solved the problem. Somebody here who has a good idea?
Click to expand...
Click to collapse
Kicking my own question. No-One who has an idea or thought? I've tried everything I could think off and would appreciate some fresh thoughts.
I have almost the same problem now. I was running CWM 10.2 with the TWRP recovery and reverted back to stock using a backup from this thread: http://forum.xda-developers.com/showthread.php?t=1975140
The installation went fine, but touch isn't working anymore. What could be wrong? I would like to have my phone back to stock and use the OTA from HTC.
Related
to those who have recently upgraded their one-x OTA to 1.28, if you have your stock rom rooted (not custom rom), can I check if you have problem with your GPS?"
I tried to use Google map, it causes my one-x to reboot. I thought it's Google map problem, but realize that with my runkeeper it's the same, the moment it got GPS fix, and try to run, it freezes the system and causes it to reboot.
I did a clean RUU flash then update 1.28 OTA and it looks ok. Problem happened when I root the ROM (using the insecure boot image)
nobody has the problem?
no issues with gps here on my stock rom.
sr1ks said:
no issues with gps here on my stock rom.
Click to expand...
Click to collapse
+1
why don't you put on the original 1.28 recovery ? You'll still be rooted.
No problems here to on rooted 1.28.Try to reflash.
I flashed stock recovery and RUU and upgrade with the same problem >.<
Let me try again ...
No problems here too on stock ROM (1.28.980.10 Optus handset). I actually used the GPS today and it worked like a treat.
shadowboy23 said:
No problems here too on stock ROM (1.28.980.10 Optus handset). I actually used the GPS today and it worked like a treat.
Click to expand...
Click to collapse
damn ... it didn't work. the moment the apps start to use the GPS (after acquiring a fix), e.g. during navigation or runkeeper starts logging my distance, the device will hang and reboot.
no problem if I do a cwm recovery back to the rooted 1.26
going to do ruu 1.28.707 flash directly to see if it helps.
just to be sure, all of you who reported to haven o problem, are you using rooted stock 1.28.707.10 and not custom rom?
Didn't have any problems on the 1.28. Altough I must say when I upgraded to 1.29 the GPS works better. Faster fix and more accurate location. Maybe a try?
Hi, I recently flashed a jellybean in Rom on my HTC one x and the rotation stopped working. So then I decided to return to factory settings with an ruu. So I did that and it was functioning again. So I reinstalled jb still worked.I then decided to try the 4.2 camera on my one x and it stoped working again, I then tried the ruu but this time it did not work. Next day I go home from class decide to unlock and relock the bootloader and it worked again, I then tried to install a in Rom ( once again) but this time it did not work. So I tried the ruu again, didn't work, tried unlock and relock bootloader, factory reset, wipe cache, everything and yes screen rotation is on. I alsotried the app android sensor and it showed my accelerometer/gyro not working. Can someone explain how to fix because its hard for me to believe that its hardware since it happens after I install a Rom or flash something. Please help.
dyslecix said:
Hi, I recently flashed a jellybean in Rom on my HTC one x and the rotation stopped working. So then I decided to return to factory settings with an ruu. So I did that and it was functioning again. So I reinstalled jb still worked.I then decided to try the 4.2 camera on my one x and it stoped working again, I then tried the ruu but this time it did not work. Next day I go home from class decide to unlock and relock the bootloader and it worked again, I then tried to install a in Rom ( once again) but this time it did not work. So I tried the ruu again, didn't work, tried unlock and relock bootloader, factory reset, wipe cache, everything and yes screen rotation is on. I alsotried the app android sensor and it showed my accelerometer/gyro not working. Can someone explain how to fix because its hard for me to believe that its hardware since it happens after I install a Rom or flash something. Please help.
Click to expand...
Click to collapse
take a look right here, contact shinigamikris he solved this problem
dyslecix said:
Hi, I recently flashed a jellybean in Rom on my HTC one x and the rotation stopped working. So then I decided to return to factory settings with an ruu. So I did that and it was functioning again. So I reinstalled jb still worked.I then decided to try the 4.2 camera on my one x and it stoped working again, I then tried the ruu but this time it did not work. Next day I go home from class decide to unlock and relock the bootloader and it worked again, I then tried to install a in Rom ( once again) but this time it did not work. So I tried the ruu again, didn't work, tried unlock and relock bootloader, factory reset, wipe cache, everything and yes screen rotation is on. I alsotried the app android sensor and it showed my accelerometer/gyro not working. Can someone explain how to fix because its hard for me to believe that its hardware since it happens after I install a Rom or flash something. Please help.
Click to expand...
Click to collapse
That can happen from time to time with gyros. Even if you get it to work with the right RUU, then you reset the device, it might stop functioning again. I'd say your motherboard needs to be replaced. You can always try with different ROMs and stuff but my thought: your HW is problematic
miHah said:
That can happen from time to time with gyros. Even if you get it to work with the right RUU, then you reset the device, it might stop functioning again. I'd say your motherboard needs to be replaced. You can always try with different ROMs and stuff but my thought: your HW is problematic
Click to expand...
Click to collapse
don't think so, every person who encountered errors like this were on cm10 and its kernel ncx, theres should be something wrong with those things... or people don't flash it correctly
I have this problem as well, but I'm using ARHD rom, right now.
Although I also think it's more a hardware fault, I'm not really 100% sure about it.
Sometimes a new Rom flash or a reset can fix it.
But after a few reboot it gets stuck again :-/
So confused about this problem too
Although, my phone is unlocked now and got Hboot 1.33. I'm gonna wait till the official RUU is out and reset my phone fully (with locked bootloaders) before sending it to HTC for repair.
Maybe you should do that too
I had this problem too. It was fixed for a while after I flashed stock rug but then I clashed another recovery and wham they got knocked out again. Then I installed viper, cm 9 still not working. Installed latest paranoid android 2.53 and they are working again oh and I have latest twrp recovery installed. I really can't say if it is hardware or software. Maybe a mixture of both. I dunno. Only just flashes pa this morning but I have rebooted and they still work. Usually it will get knocked out if I reboot so I'll see what they are doing after a week or so. I'll probably keep pa on here until my official j b OTa is released. I think it did have something to do with either that ncx kernel or a recovery I tried. As that what knocked them out each time. Good luck in fixing it as different people gave had different things that fix the problem. For me it was reverting back to stock ruu. It was 4.03. 1.29..... something. But it also was fixed when I flashed latest paranoid android. Just a fee things to try....
Sent from my HTC One X using xda premium
Edit - sorry for the spelling mistakes....
one x gyro sensor probs
I also hv same probs. in one x.
sometimes reboot can fix d probs. of gyro sensor. n when u restart d device it stop again n smtime u restat device its working again. i dnt knw its a hardware probs. or software probs. ??? Plzz help me guys.
also give me a rpl in my mail id. [email protected]
Hi I pretty much know nothing about custom roms etc but I was forced to go for a custom ROM due to a friend wiping my phone but when I flashed Viper 3.2.1 everything was fine except the wifi button was greyed out, I also tried android revolution and the same problem occured. However it was fine when i tried candy5 but once i flashed google play the wifi stopped working again.
Does anyone know what the problem is and how i should fix it? thanks.
Hope you are on latest 4.4.4 firmware , link for the same should be in OP/FAQ of Viper.
fandam said:
Hi I pretty much know nothing about custom roms etc but I was forced to go for a custom ROM due to a friend wiping my phone but when I flashed Viper 3.2.1 everything was fine except the wifi button was greyed out, I also tried android revolution and the same problem occured. However it was fine when i tried candy5 but once i flashed google play the wifi stopped working again.
Does anyone know what the problem is and how i should fix it? thanks.
Click to expand...
Click to collapse
If you are only unlocked and not s-off you will need to manually flash the corresponding boot.img for each rom each time you flash a new rom. If you can get s-off you won't need to do this anymore.
Firmware needs to be updated. Confirmed on OP's other thread here: http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-bricked-t2989202/page2
Also its not necessary to manually extract and flash boot.img on the M8, even when s-on. Folks giving this advice may be carrying over knowledge from an older HTC device.
Hi, Ive not long had my m9. When i got it it updated straight away and got the charging bug.
Since then I have s-off'd and tried various roms with not too much luck.
I now have a bug that occurs when i flash a new rom. This has happened when i flashed 3 different roms. Leedroid, Viper and android revolution. the rom flashes ok, then starts to boot, and builds art. It then finishes building art and starts to complete the boot process, and then it reboots and tries to build art again.
I flash back to my stock backup and everything is fine again. (apart from the damned charging bug)
Has anyone else experienced something similar?? am i missing something??
Go in twrp and make factory reset
just tried that, didnt work
Did you update your firmware? if you're still on 1.x firmware, those 2.x roms will reboot.
yeah. have tried matching roms to firmware and still get the same result. trying viper one currently. in a massive bootloop again. It boots enough to say "nfc service has stopped working" and thats what made me think it might be firmware, but it seems to make no difference.
cant even adb whilst its booting.. getting waiting for device.
What version of twrp are you using?
2.8.6.1
philicibine said:
2.8.6.1
Click to expand...
Click to collapse
Update to 2.8.7.0 and see if it continues.
I've solved this, and my charging issue. Finally!!
I decided to flash the earliest ruu I could find and then let it do all of the ota updates itself.
I then rerooted, flashed updated firmware and am now running leedroid.
Thanks for the help guys.
I purchased a second hand One M8 which had CyanogenMod installed on it. My aim was to revert it to stock (either on O2 UK or standard HTC ROM) with the abillity to get OTA updates.
I checked the CID (O2__001) and got a stock recovery image and nandroid backup for it. I then used fastboot to flash TWRP as the recovery image, and used that to restore the nandroid backup. That worked fine and it was working with the O2 ROM, so I flashed the stock recovery image as well.
After this it prompted for an OTA update so I thought all was going well. I installed the update and that all worked as expected until it booted up. All the functionality is there, but the Wifi won't turn on at all. If I tap the option to turn it on, it just hangs in the "off" position. It's the same whether I do it through the settings menu or from notification bar. I tried doing a factory reset but it makes no difference. It's very frustrating because other than this, everything is working the way I would like to.
What could cause the Wifi to stop working after an OTA update?
Why ? Low version backup for high version hboot.
You need correct backup for your hboot version.
What's hboot no. ?
Never mind, I managed to sort it out.
The first few OTA updates had a Wifi firmware update which stopped it working. I used mobile data to continue updating and once it got to Android 4.4.4 it all worked as it should.