I see this issue around but no one seems to quite solve it. I want to.
I have my old G1 and a MyTouch 3g and would like both phones to work so I have back ups when I get my G2. Currently, I have fixed most problems with my G1 except for one: The fact that it reboots randomly, seemingly nothing on my end to cause it.
I am running CM 5.08 and Clockwork Recovery 2.5.0.1
Things I've tried:
-Switching ROMs (It appears to have nothing to do with the ROM)
-Wipe, Cache Clear, Dalvik Cache cleared, Battery Stats, etc.
-Replacing the battery
-Updating SPL, Radio, changing recoveries, etc.
Is there anything else you guys would suggest trying to see if I can solve this problem?
P.S. I apologize if there is a thread on this already, or this is the wrong section for this question.
i used to have this problem on my g1...it would rebbot on stand by when disconnected from the power supply it narrowed the problem to memory card
try this
1)use recovery to format it in the file system recomended by you rom dev. ext2 3 4
2)buy a new Memory card and do step 1
it worked for me
good luck
Related
In addition to the home and talk buttons not working. The phone will not lock when I hit end, it just puts into a sleep mode.
Holding end only gives a reboot and shut down option. This problem surfaced after installing the new SuperD mod. I did a wipe and reinstalled it two nights ago and the problem was resolved, but it has resurfaced tonight.
Anyone have any thoughts on the matter? Should I go back to the old version?
Which new version? The beta or 1.10.2? If it's beta - then you def should go back to stable. If it's 1.10.2 - then you most likely have a hardware problem. A lot of people run Super-D with no problems.
Further more, sometimes your trout-keypad-v3.kl (located in /system/usr/keylayout/) can get corrupted and cause that. It's extremely rare but you may try either re-flashing or just pushing that specific file.
Word of advice (which you may already know): if anything goes wrong and you want to rule out software problem - install a base rom (like the defanged from Cyan's wiki), complete wipe and min options (no Apps2sd, no swap, etc) and see if it fixes the problem. If the problem is gone - you're in lock and something went wrong with the rom. If problem is still there- start looking for a new phone.
Good luck.
I did a fresh install. I repartitioned the sd card, reinstalled all apps. did a factory wipe, reinstalled the base defanged, then did super D. It wasn't the beta, i had upgraded to 1.10.2 and experienced the problems.
It would work fine for two days, then if my phone would shut off (battery has weird contacts) then it would boot back up and my settings would be all messed up, and the keys would work. I would try re installing the ROM, but no fix.
A wipe remedies the problem. I went back to cyanogen last night to see if the problem appears on this rom, so far it hasn't.
I never had this problem until i upgraded from 1.9.3
Im having problems with my Nexus
1. phone randomly reboots especially when using camera or with charger plugged in
2. when it reboots it stays on the x sreen
i rooted the phone and put the desire rom on there but the problem has got worse.
Is there a RUU file for the nexus?
How can i get it to work - please reply in simple mode and with links instructions
its originally on vodafone uk but imm sure it wasnt branded or sim locked.
There are no RUUs. It's Nexus.
Wipe data, cache and Dalvik-cache on your phone (it erases ALL the data) through recovery, and test it again. If it still fails with no apps installed - you have a hardware problem, send it for replacement. If not - put on it a custom ROM of your choice, wipe everything, and enjoy.
All the relevant guides are in Nexus One Wiki.
Sorry, I know this is beaten to death. With all the SD card issues that this phone had, it's not easy to search.
Running CM7 for almost a year now and happy. Starting to get constant Force Closes. Tapatalk, Youtube, Outlook calender....things that I would guess are memory intensive. Having a hard time even launching a YouTube video these days without force close.
Wondering if the SD is dying and it's time to go get a Nexus?
Cheers.
Of all the SD card failure cases I've seen over the forums for the Bell Vibrant, most of them result in a sudden irreparable boot loop out of nowhere (happened to me the same way). If I were you, I'd make a backup in CWM, save it on your computer, and just wipe and format everything on your phone so you can flash on a clean system for test running to see if you still get FCs. If so, then something is probably wrong with your hardware, if not, then I guess your SGS is still good to go
I've tried searching on this issue as well, but there is too much info on it.
Does anyone know from what point the issue was fixed on new phones? (i.e. phones manufactured after X date should not see the SD failure issue)
I think it was the froyo build "JL2 " that had a bootloader update that fixed the problem. I got mine on release day and have had no issues.
Sent from my GT - I9000M running Team Hacksung's ICS build 12
Well, flashed team hacksung ICS, and force closes continue.
Don't know if that is unstable ROM or dying phone. I'll report if the sd does die.
Try reverting back to stock. Clear cache, Dalvik, Data.
I was one of the unlucky one with the SD Card failure. The failure happens very quickly. Became unusable very fast. I tried to reboot but it went into bootloop because it could no longer reach the SD card anymore.
Your FC are most probably due to a some bugs and your phone need to restart fresh.
Hello guys,
I was looking for the answer for a long time, but I didn't find a solution for my case. My problem is a serious battery drain AFTER making a call. When i finish a call, the battery starts to lose about 7-10% of the energy per hour, even though the phone is not used and is in the same place as previously (so its not a problem with the poor gsm signal). The only solution is to restart my phone - it helps immediately, but onlyas long as there is no new phone call made.
I have installed Better Battery Stats, what I could notice is:
- in "CPU states" before the call the processor stays in "Deep sleep" for most of the time, after a call it remains at 100MHz
- in "Kernel wakelock" a gpsd process appears and takes most of the time
GPS is switched off all the time.
I think that the problem had appeared after one of the CM 11 update, however during the last month i thing i have installed really many different ROMs - CM 9, several CM 10 versions (10, 10.1, 10.1.3 etc), finally i came back to the stock 2.3.6, unfortunatelly - nothing has changed. Before each ROM installation i did factory reset and cache wipe. Yesterday i alsohad formatted internal SD card, after that i installed CWM 2.7.4 with CM 10.1.3 (this was working well couple of months ago) and completely nothing has changed.
Could you please work out the reason and a solution? Its obvious for me that the problem comes after making a call and now I really can't work out any ideas how to solve the problem. Yesterday I changed the radio ROM - no change at all...
Hope you guys can help me
Strange issue. Did you recently try to format /system before installing any of those ROMs? It is usually not required in the i9000 threads, but for all other devices formatting /system is a substantial step to insure that the next installation will be fine.
tetakpatalked from Nexus 7 flo
tetakpatak said:
Strange issue. Did you recently try to format /system before installing any of those ROMs? It is usually not required in the i9000 threads, but for all other devices formatting /system is a substantial step to insure that the next installation will be fine.
Click to expand...
Click to collapse
Thanks for reply. As far as i remember - I did it last time (as well as I formatted /boot, /data, /cache and rest of the format options from Mount and Storage in CWM).
I was trying to post my post, but it was flagged and blocked by the system, probably because I kept previewing it, so until I can post it, I'm going to be really brief about the latest news on my problem.
I have a T-Mo US HTC One that's now S-Offed, running CWM recovery, and running 4.19.531.10 firmware+radio. It's running Android Revolution HD 91.1, and the first error from before I did any of this was "Failed to powerup external modem!" The phone would randomly reboot and such. Now, it's running normally except for the fact that I can't get the phone part of it to work. I also don't think I can warranty it because I already opened it up because I managed to break the back and also changed the frame color, screen, and camera. In the settings, Baseband read as "Unknown." I'm hoping you guys here can help me fix my problem as I hope it's software related, but think it might be hardware related.
Is there any hope for this? At one point, running the ElementalX kernel and the Android Revolution HD ROM with it still S-On and running latest Radio from 7.18.531.2, if I wiped dalvik cache and kept power saver off, the radio would start and it would work fine until I turned power saver on (even if the turn mobile network off part was off).
aruaour said:
I was trying to post my post, but it was flagged and blocked by the system, probably because I kept previewing it, so until I can post it, I'm going to be really brief about the latest news on my problem.
I have a T-Mo US HTC One that's now S-Offed, running CWM recovery, and running 4.19.531.10 firmware+radio. It's running Android Revolution HD 91.1, and the first error from before I did any of this was "Failed to powerup external modem!" The phone would randomly reboot and such. Now, it's running normally except for the fact that I can't get the phone part of it to work. I also don't think I can warranty it because I already opened it up because I managed to break the back and also changed the frame color, screen, and camera. In the settings, Baseband read as "Unknown." I'm hoping you guys here can help me fix my problem as I hope it's software related, but think it might be hardware related.
Is there any hope for this? At one point, running the ElementalX kernel and the Android Revolution HD ROM with it still S-On and running latest Radio from 7.18.531.2, if I wiped dalvik cache and kept power saver off, the radio would start and it would work fine until I turned power saver off (even if the turn mobile network off part was off).
Click to expand...
Click to collapse
seems like you went to a lot of trouble for a $100 phone
you can find a decent replacement on eBay cheap
Meanwhile you can update your firmware to the latest it will match the rom that way
I'm a little reluctant to change anything now. I just finished flashing the ElementalX kernel and did a dalvik-cache wipe and the phone service is working again. Assuming it's just like before, power saver should cause it to fail again.
I'm busy now, so I'll do a nandroid backup when I can later and try the RUU for the firmware again. The RUU kept failing on me before and htc_fastboot.exe would crash. I don't know how to decrypt the rom zip to manually flash it.
Edit: Any idea why using the ElementalX Kernel and wiping Dalvik-Cache makes the radio work again? It seems relatively stable right now (Powersaver off, it's not very stable with it on).