i updated to 1.28. Pre update my phone worked 100% fine. After the update my phone had developed the screen flicker, so i adjusted the screen brightness, put it onto auto then back again and now it has gone! any ideas how this has happened ??
Never happened to me. 1.28 removed my screen flicker, but I full wiped and then flashed the RUU over 1.26. Try that first.
just find it bizarre an have no idea why it would start after a update then go again!
Related
Hello,
Everything started when I did OTA update to Froyo...
My Desire reboot randomly when I use Nav, Maps, Browser, etc...
I tried to downgrade the HBOOT to 0.80 with a PB99IMG.zip package in order to get a clean place to do again the update.
The OTA update did not available after that...
So, I root it with Unrevoked, put a 2.2 official Froyo from Modaco with associated radio rom, install all my usual applications (Task killer, Reminder, Calendar, etc...) and try to use my phone again... with random reboots again
I made a swip of all that I could, re-install official Froyo ROM with radio, without anny application... and then, try it again... with random reboots !!!
Sometimes, it reboot in loop and then stay on the first HTC screen.
The back of the handset is hot when it reboot (but was more hot without any problem before, when I was under Android 2.1 and Nav activated).
The phone is not branded... and I use it with Bouygues Telecom.
I not use my gel case since I had the problem, as I though it could be an overheat issue.
And I have already read other topics about Froyo and reboots but not find something that could help me
Anybody could help me ?
i have the same issue. The only way to fix it is to underclock the cpu or open the back cover and blow at the bottom on the phone where the cpu is located.'
Or you can always return it to htc service (remember to flash original rom,radio and hboot and unroot)
The issue is that the phone got very hot and actually burned some stuff in there making a shortcircuit, before my phone could withstand over 50'C, Now it reboots at 40'C. I seriously think the phone has been fried!
I have exactly same problem.. it's very annoying!!! Anybody can help??
Maybe some app do it?
First it happened only in browser on some websites (after debrand + FROYO). I suspected Flash plugin.
But then it starts happened randomly everywhere - when reading PDF, use Navigation...
Even if i downgrade with PB99IMG_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed_txt.zip and then receive new OTA 2.10.405...
bug is still there!
Hey guys,
I've bought Desire Z recently and today a problem occured: when I start the camera app (either via SW shortcut or HW key) I get just backlit black screen and all I can do is to press Home.
Does anyone know a solution?
Thanks.
You're using the stock ROM, right ?
I would try a factory reset. If that doesn't fix the problem, then it sounds like it has a faulty camera, return it.
Yes, I'm using stock ROM. I've tried factory reset for 2 times and it didn't help, so I guess returning the phone is my only option.
The wierd thing is that the camera worked just fine and then it started to show only a black screen.
Move your finger???
Tried, not helping
Now when I think about it I come to conclusion that the problem occured after the last update (the one supposed to enhace camera performance). Could it be the cause? Can it be undone?
If I perform factory reset I still have this update installed (OS version 2.2.1).
All.Os said:
Now when I think about it I come to conclusion that the problem occured after the last update (the one supposed to enhace camera performance). Could it be the cause? Can it be undone?
If I perform factory reset I still have this update installed (OS version 2.2.1).
Click to expand...
Click to collapse
Do you still have S-OFF or are you back to S-ON now ? If you are S-ON then there is no way currently for you to downgrade if you're on the new 1.72 ROM, since right now it is not rootable.
I haven't had S-OFF so I don't have now as well.
But it doesn't matter to me anymore, I'm returning the device (already have bought a new one - so far didn't update to the 1.72 ROM and camera works fine). Now I don't know if I should perform the update.
Anyway, thx everybody for trying to help.
I recently RUU'd from ViperX to my CID's 2.17 then upgraded via OTA to 1.36 hboot and the Jellybean Sense 4+ update. My cid is 044. I then rerooted, full wiped and flashed Insert Coin 13. I soon after noticed a problem that I get on every reboot. It will reboot up till the part where it starts to load Sense and then it pops up a message along the lines of htcdialer has stopped and then I get a black screen (I can only see the top status bar) and I'm unable to do anything with my phone from there. I'm able to flash any of the JB custom ROMs and use them fine until I reboot. I've tried this with IC 13 and Maximus 8.5 so far, and I have performed a superwipe as well as a full wipe via their Aroma installers. I was going to try ARHD 15 next but the download times on both mirrors are just outrageous. Has anyone experienced anything similar to this or have any idea what I could do to fix it? Thanks a lot in advance.
Hey guys, its my first post on here and I was hoping to get some help with my device. (Yes, I've searched extensively over the internets. No, I can't find anything related to this issue for the One X)
So let me start from scratch. About a month or so ago, my phone started rebooting randomly, I have been using ViperX 2.7.1 by Team Venom since day one of getting my phone and only started experiencing these issues after upgrading my hboot to 1.31, switching to MaXimus and returning back to ViperX. If it was the occasional reboot, I wouldn't be half as annoyed as I am this very moment. Unfortunately, my phone does not ring when I get a call. Does not ring, screen doesn't even turn on, does not notify, nothing. I called it from another number, did not ring, tried turning the screen on, did not turn on, just rebooted. This does not happen all the time, but has been happening a lot recently. So far, I have fresh installed ViperX numerous times, (wiped cache, factory reset, wiped dalvik cache and full wiped from the ViperX aroma installer) thought maybe an app was misbehaving so fresh installed from the play store instead of Titanium Backup. Even tried switching ROMS but I can't for some reason. Tried installing CM10 the other day, didn't go past the white screen. The good people on androidforums.com told me that I need a different boot.img for newer hboots so I got that, but the CM ring at startup freezes followed by a reboot. Switched to ViperX 3.2 (JB) couple days back hoping this issue wouldn't follow me here as well, but alas, it still has. Then yesterday, I thought upgrading my hboot and wiping my phone the way up'ing the firmware does might fix it, so I up'ed my hboot to 1.39. (strangely though, I still have my files on my sdcard) I followed this guide: http://forum.xda-developers.com/showthread.php?t=1920060 Only step I couldn't follow was the adb reboot oem-78, I got some strange error (did not happen when I up'ed to 1.31) After getting 1.39, I flashed ViperX 3.2 again but I still have this error.
I'm completely out of ideas and am really close to giving up and selling my phone. Any help/advice on what I could do would be greatly appreciated!
Original post: http://androidforums.com/international-tegra-3-one-x-all-things-root/667919-random-reboots.html
Disable AOSP lockscreen in tweaks.
stifler05 said:
Disable AOSP lockscreen in tweaks.
Click to expand...
Click to collapse
Woah, no way. Is that it? It worked perfectly fine before I up'ed my hboot to 1.31 (always used the AOSP lockscreen). Have you encountered a similar issue? I'm trying this out now, will keep you posted.
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.