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.
Related
I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?
Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk
I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.
You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk
Alright, tried wiping the Dalvik Cache after flashing, problem still persists.
You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache
Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...
Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App
Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?
Hey guys,
i have a problem, well 2 problems with my Desire.
First thing i had was permanently rebooting after installing InsertCoin Sense 2.1.
I tried everything that came to my mind (redownloaded, wiped multiple times, repartitioned SD card, different recoveries, and so on) problem was still there. It booted until the lockscreen appears, and after some seconds rebooted again.
Then i switched back to Oxygen, which i was using before.
Everything went well, but then Camera doesn't work. Just starts a black screen, and nothing happens after that.
i have to reboot the device after camera fail, because it drains my battery even after stopping service, i don't know why.
I wiped, reflashed, but still the same problem. I also changed to CM7 to test it, but same problem there
tried some radios, and different kernels...nothing works.
Here some information : HTC Desire amoled, s-off, radio 32.54.00.32U_5.14.05.17
I hope someone can help me.
Thanks in advance
JohnForte said:
Hey guys,
i have a problem, well 2 problems with my Desire.
First thing i had was permanently rebooting after installing InsertCoin Sense 2.1.
I tried everything that came to my mind (redownloaded, wiped multiple times, repartitioned SD card, different recoveries, and so on) problem was still there. It booted until the lockscreen appears, and after some seconds rebooted again.
Then i switched back to Oxygen, which i was using before.
Everything went well, but then Camera doesn't work. Just starts a black screen, and nothing happens after that.
i have to reboot the device after camera fail, because it drains my battery even after stopping service, i don't know why.
I wiped, reflashed, but still the same problem. I also changed to CM7 to test it, but same problem there
tried some radios, and different kernels...nothing works.
Here some information : HTC Desire amoled, s-off, radio 32.54.00.32U_5.14.05.17
I hope someone can help me.
Thanks in advance
Click to expand...
Click to collapse
Try going back to stock with proper RUU.
It sounds like a hardware problem, but try the stock way first, just to be sure
Thank you.
It definitely was a hardware problem.
changed to ruu, but was still the same.
i sent it in now, and am on a nokia n86. So funny to see how much changed since then
Having trouble with the latest LeeDroid HD ROM have flashed many LeeDroid roms before without issue but for some reason aftering clearing all caches and running the latest rom it will install ok but on reboot it just hangs on the White HTC screen and won't boot in.
Any Ideas what could be causing it?
Currently Running LeeDroid HD v3.0.1, LeeDroid Kernel v3.1.1 radio 12.54.60.25_26.09.04.11_M2
Make sure you're deleting all data do a full factory reset (deletes all data does not actually restore to factory condition) then clear the dalvik cache, re apply the ROM make sure its CLEAN and you haven't modified it, don't apply any themes or anything, then let it boot and be patient.
Try downloading it again also it could be a corrupt download.
m3t4lh34d said:
Having trouble with the latest LeeDroid HD ROM have flashed many LeeDroid roms before without issue but for some reason aftering clearing all caches and running the latest rom it will install ok but on reboot it just hangs on the White HTC screen and won't boot in.
Any Ideas what could be causing it?
Currently Running LeeDroid HD v3.0.1, LeeDroid Kernel v3.1.1 radio 12.54.60.25_26.09.04.11_M2
Click to expand...
Click to collapse
I had similar issue few days back. But i had the Leedroid rom (same rom,kernel as urs) already runing flawlessly for a few days. It decided just to hangs at the same HTC Screen... tried to clear caches(all), hard reset, reflash same rom... still stuck same place. I finally had to flash stock 1.32 image, root all over again, etc. ... and flash Leedroid (same) again... works fine now
I got the feeling that I made my friends with their stock DHD and Iphone users drooling and jealous of my phone(csutomised with sense 3.0 stuffs), and they collectively jinxed my phone, and had this crash! lolz
btw. i flashed SAME rom i had on my sdcard, so I think the rom fine(mine at least). just something triggered that crash!
all the best...
Yea i tried reflashing from stock rom the other day loaded up one of the RUU exe's and rerooted etc and tried to reflash with no luck so i'm all out of ideas
raidenxl said:
Make sure you're deleting all data do a full factory reset (deletes all data does not actually restore to factory condition) then clear the dalvik cache, re apply the ROM make sure its CLEAN and you haven't modified it, don't apply any themes or anything, then let it boot and be patient.
Try downloading it again also it could be a corrupt download.
Click to expand...
Click to collapse
Have also done factory reset and cleared dalvik cache etc. no joy
Just managed to find a copy of LeeDroid HD V3.0.2 have installed and found it also crashes but.... it gets to the LeeDroid Android screen, little further but unfortunately still crashes
Managed to get 3.0.3 working on my DHD turns out it was just down the cwm version i had, updated to 3.0.2.5 and boom worked first time =D only problem i have had with both 3.0.1 and 3.0.3 is the camera keeps dropping out, app doesn't force close but the screen keeps going black and all buttons dissapear then all comes back... =( Atleast i'm up to date though
Any Idea's on the Cam issue?
have run logcat and noticed the following in the log
W/mm-camera( 1400): config_proc_CAMERA_STOP_SNAPSHOT: state is not correct ctrl->state = 25 W/mm-camera( 1400): VFE_RESET_ACK illegal ctrl->state 24
dunno if that makes any sense to anyone
tinkered with it a little last night didn't seem to make a difference so left it over night and for some odd reason works fine this morning i think the issue was down the camera app itself but it looks to be working fine now thankfully
UPDATE:
Ok looks like the issue is still there found out what is causing it thought, the camera works fine but...only when wifi is off, if you turn wifi back on you get the same issue as before,
Please anyone got an idea on wtf?
UPDATE2: have worked out it must be the camera app due to the fact i download a different app which appeared to work fine. Not sure why there's a glitch though
Hi people!
My HTC Desire has a annoying problem, being that it reboots spontaneously.
Well, maybe not really spontaneously.
I believe that it reboots when I (should) receive a call or message, maybe also with push notifications, but that I don't know.
I tried but can't reproduce the problem by calling or texting myself with another phone. But I does happing when people call or text me, not always tho.
With 2G only of Wifi, I have not experienced the problem.
It began while being on MIUI (with a 3th latest radio or so/beta/nog directly after a update). Because MIUI began to irritate me with its speed and bug now and then, I wiped it all and flashed CM7.1 STABLE, incl latest radio, and installed my apps again.
Still reboots.
Flashed a way older radio. Still reboots.
Pretty important, it does NOT get hot.
Facts:
- 3G off, not experienced a problem
- when 3G off, sometimes no signal
- does not get hot
- different radio's, different roms
- slipt out of my hands and fell in a bath, got I out before it even hit the bottom. This happened two of three 2 days before the problems began
I read about HTC reboot problems on Vodafone NL a while ago.. I am on this network, but the posts are not recent..
I read about HTC Desire reboot problems while using the phone, after it's getting hot (2010 posts).
I did had reboots a few months earlier, but that was a bug on MIUI.
Anyone an idea what the problem is?
Make a complete backup and change rom. If problem persits, go back to stock. If desire still reboots, call HTC.
1ro said:
hi people!
My htc desire has a annoying problem, being that it reboots spontaneously.
Well, maybe not really spontaneously.
I believe that it reboots when i (should) receive a call or message, maybe also with push notifications, but that i don't know.
I tried but can't reproduce the problem by calling or texting myself with another phone. But i does happing when people call or text me, not always tho.
With 2g only of wifi, i have not experienced the problem.
It began while being on miui (with a 3th latest radio or so/beta/nog directly after a update). Because miui began to irritate me with its speed and bug now and then, i wiped it all and flashed cm7.1 stable, incl latest radio, and installed my apps again.
Still reboots.
Flashed a way older radio. Still reboots.
Pretty important, it does not get hot.
Facts:
- 3g off, not experienced a problem
- when 3g off, sometimes no signal
- does not get hot
- different radio's, different roms
- slipt out of my hands and fell in a bath, got i out before it even hit the bottom. :d this happened two of three 2 days before the problems began
i read about htc reboot problems on vodafone nl a while ago.. I am on this network, but the posts are not recent..
I read about htc desire reboot problems while using the phone, after it's getting hot (2010 posts).
I did had reboots a few months earlier, but that was a bug on miui.
Anyone an idea what the problem is?
Click to expand...
Click to collapse
what hboot u are using
Change rom to which one.. already had miui beta, now cm7 stable.
Alpharev
Hboot 6.93.1002
Partitioned for cm7 r2
Sent from my HTC Desire using XDA App
sachin.02 said:
what hboot u are using
Click to expand...
Click to collapse
how dis his HBOOT have anything at all to do with rebooting
@OP Try a different ROM.. try both AOSP and Sense, if you still get the issue try return it to stock (RUU) and see if problem persists.. if it does then it's a hardware problem and call HTC.
Change rom
1Ro said:
Change rom to which one.. already had miui beta, now cm7 stable.
Alpharev
Hboot 6.93.1002
Partitioned for cm7 r2
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Try this one: http://forum.xda-developers.com/showthread.php?t=768703
I was having reboot problems with LeeDroid. Installed Tristan202's kernel, fixed it right up.
Are you undervolting or overclocking? That can cause random reboots when the system can't distinguish the actual signals from the random noise and interference, wither because it's too fast (overclocked too high) or too weak (undervolted too low). Bump up the voltage and/or reduce the clock speed a little, and see if that helps.
I didn't do anything with the clockspeed or so. The max CPU frequency is adjustable in CM7, but left it on 998MHz. I'll try 1075 now?
The link to Leedroid is a froyo. But I like gingerbread. HTC even made a gingerbread rom (available on htc dev center).
And the phone had worked normally on gingerbread.
An other problem I had for a longer time.
Sometimes the phone only uploads and doesn't download (as I can see by watching the arrows). So I internet connection doesn't work then. Putting it on flightmode and back does solve the problem.
The tristan kernel:
http://forum.xda-developers.com/showthread.php?t=1276547
Which one do I need..?
Thanks folks for your help!
1Ro said:
Hi people!
My HTC Desire has a annoying problem, being that it reboots spontaneously.
Well, maybe not really spontaneously.
I believe that it reboots when I (should) receive a call or message, maybe also with push notifications, but that I don't know.
I tried but can't reproduce the problem by calling or texting myself with another phone. But I does happing when people call or text me, not always tho.
With 2G only of Wifi, I have not experienced the problem.
It began while being on MIUI (with a 3th latest radio or so/beta/nog directly after a update). Because MIUI began to irritate me with its speed and bug now and then, I wiped it all and flashed CM7.1 STABLE, incl latest radio, and installed my apps again.
Still reboots.
Flashed a way older radio. Still reboots.
Pretty important, it does NOT get hot.
Facts:
- 3G off, not experienced a problem
- when 3G off, sometimes no signal
- does not get hot
- different radio's, different roms
- slipt out of my hands and fell in a bath, got I out before it even hit the bottom. This happened two of three 2 days before the problems began
I read about HTC reboot problems on Vodafone NL a while ago.. I am on this network, but the posts are not recent..
I read about HTC Desire reboot problems while using the phone, after it's getting hot (2010 posts).
I did had reboots a few months earlier, but that was a bug on MIUI.
Anyone an idea what the problem is?
Click to expand...
Click to collapse
I've got same problems. After rooting my HTC Desire and installing Revolution ROM, it has worked well for about 24h, then i was surprised with disappearing all my data (contacts, messages, settings, was needed to log in back to google, sync was off), so i set up everything again, after few hours of normal work, i noticed that i have to enter SIM card PIN code. ok, done. After few more hours SIM card PIN code again. So i reflashed with another custom ROM and phone started to reboot each time at SIM card pin code enter screen, or after finishing booting. Few minutes ago i tryed to reflash with another ROM, which i used to have few months ago and which was pretty stable (Reflex), and now im stuck at HTC boot logo
HBOOT 0.93
Radio 5.11.05.27
Use a RUU, make sure it's the right one for your phone or that you have a goldcard.
I would try Oxygen Rom, it happened to me in the past but it was fixed a bunch of releases back.
Hmm,. running on 1075Mhz now and no reboots since.. while being on 3G and receiving a few calls and (whatsapp) messages.
I don't want to bump into conclusions to fast, but at least it's remarkable.
Or my phone is dryed up.
(@random_factor?) IF the 1075Mhz setting is the solution, how is that possible??
And I just hit the trackball to enter my phone and tadaaaa: reboot
RUU Bravo flashed.. First flashed hboot stock. Still on alpharev bootloader and S-OFF, so if phones still reboots, I must not forget to flash the stock bootloader... hehe. I will post the results ofcourse of the stock rom ofcourse.
[EDIT]
Being on stock rom/radio, I just had another reboot. Guess it's safe to say it's a hardware problem..
1Ro try to install non-A2SD Rom. it'd worked for me.
Funkypotatoe, I've installed the RUU for my phone. So I'm on the original froyo with original radio, so no a2sd and I'm not using android's original apps2sd now.
1Ro said:
RUU Bravo flashed.. First flashed hboot stock. Still on alpharev bootloader and S-OFF, so if phones still reboots, I must not forget to flash the stock bootloader... hehe. I will post the results ofcourse of the stock rom ofcourse.
[EDIT]
Being on stock rom/radio, I just had another reboot. Guess it's safe to say it's a hardware problem..
Click to expand...
Click to collapse
yeah, call HTC and request a pickup, hopefully you'll get a Desire S
also make sure your bootloader is back to stock (did you flash the downgrader before you ran the RUU?) if you've just got everything stock after the RUU, apart from the bootloader (if you're still S-OFF), go to my guide and there's a section about still s-off after RUU, do the 2nd method since it's quicker and safer..... and if you're already S-ON just ignore everything I've said and call HTC
Yes I'm still S-OFF.
I've checked your guide: Nice work!
I in doubt of if I should send it to HTC, because of the water incident. There are little white strips in the phone and on the battery that turn red when in contact with water.
The strip on the battery is redish, just from wiping it with a 'wet' towel (there were here and there little drops of water). The visible strip in the phone is still white. Don't know if there are more strips inside the phone. I would suck if I send to phone for warranty, and get as a result: waterdamage, 35 euro research costs.
Everything has been fine until yesterday morning, when at work I realised my phone was rebooting every 3 or 4 minutes.
I hadn't changed anything, I hadn't flashed anything, I don't O/C my phone. I'm usins AOKP Milestone 3 with Immoysen Kernel.
I've tried -
Reflashing AOKP with no custom kernel
Wipe & flashing CM9 Kang
Wipe & flashing MCR
When I tried to make a Nandroid of MCR (as it seemed to be okay for an hour or so) it gave an error when it got to backing up the data partition. Could their be a corrupt bit of memory there?
Also, at one point I think it might have reset while in recovery, which makes me think it's hardware, not software.
Today I've tried -
locking and unlocking the bootloader
Android_Revolution_HD_Super_Wipe_Lite
Wipe and flash AOKP B23
Generally it seems to be better after a wipe and a fresh install, for a little while, but then seems to start rebooting again later.
I locked and unlocked again around an hour and a half ago and all seems good at the moment, but I thought I'd post still to see if anyone else has had this happen or see if anyone has ideas of how to de-bug it should it come back?
I had this problem after upgraded to 4.0.2. Fresh install did solved this somehow but last week it came back again when dial starts...
Tho it seems un-checked all options in location services would not reboot during or after the call
Hope this info could help u
Thanks. Well, 6 hours since I locked the bootloader and unlocked it again (to wipe everything, including the SD storage) and it's not rebooted once. Looks like it's fixed *touch wood*
I have random turn offs... dunno if it relates. Its a little unnerving...and annoying. No roots, no unlocks, just vanilla 4.0.2.
Sent from my Galaxy Nexus using XDA App