I have searched high and low for a solution to this problem that I have not seen anyone else have. I have installed CWM and a custom rom(ginger volt) I had issues with the rom so I erased and restored my original. Now, everytime I start my phone when it does the initial Internal memory scan it gets to about 13% and the phone restarts. I reinstalled gingervolt rom and the same thing is happening. The phone is also running very slow. I have tried all day to resolve this issue to no avail. PLEASE help.
Related
When I try to enable WIFI on my G1, for a couple of seconds it says: enabling WIFI, but then the phone becomes unresponsive (for about 1 second) and it reboots.
IIRC the problem started when I upgraded to the new CynogenMod ROM (4.1.99, but not sure), but it doesn't seem to be linked to the ROM.
I have always used CyanogenMod and update with every new version.
I tried to go back to the default HTC rom, but this doesn't solve the issue.
Does anyone know what may cause this or give me some tips on how to debug this?
I tried to run 'adb logcat' but it shows no info.
The exception browser in the CyanogenMod is also empty.
I don't know what else I could try.
Some extra info:
HSPL 10.95.3000
Radio 2.22.19.26I
CynogenMod ROM 4.1.99 is not the newest. Wipe, flash the htc image, flash cyan's newest and try wifi again.
No, I know, but I think that's when the problems started.
Latest version I installed was 4.2.13
I have installed the RC7 dreaimg.nbh now (used to root the G1), and when I try to enable WIFI on this rom, the phone doesn't reboot, it keeps working, but I get an error saying that WIFI could not be started.
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
mattb3 said:
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
Click to expand...
Click to collapse
This is consistent with my experience as well. By far, the VAST majority of spontaneous reboots that have occurred on my phone have been when using wifi. Some of the older Cyan ROMs were really bad about this, but this continues to occur (although much less frequently) regardless of the ROM. I am presently using SuperD and have had one reboot in the past week.
This seems to happen most often when using the wifi heavily; for instance, I get a reboot probably every 3rd or 4th time when I'm doing my weekly podcast downloads. I don't remember any reboots when just surfing the web or downloading apps, though.
I have never had this happen when I was running cyan.
Are you wiping everything? Even EXT and dalvick?
Are you using any other apps when this is running and rebooting? Perhaps an offending app?
You should also open ADB and run ADB Logcat and try to replicate the issue and try to get a log submitted so the dev can help determine what is causing this issue.
I wiped everything and even without any apps installed, it just reboots.
adb logcat doesn't show a thing when the phone reboots, it just exits.
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
I have an AT&T Nexus One. Got it since it was first released for AT&T never had any problems untill now.
I can do anything without problems except when I receive a text message my phone reboots. I tried factory reset no luck. I formatted my sd card wiped my phone and updated my rom from cm6 to the stable version of cm7 and it still reboots after I receive a text message. I searched google and found other people with the same problem with various android phones but I haven't found a fix yet.
I was hoping some of the genius here at xda dev could help me out with this.
My phone is out of warranty and it's unlocked/rooted.
Please help if you can.
Thanks,
Rick
*********************************************************
EDIT: Just found out that it restarts when I receive phone call aswell.
*********************************************************
This exact problem is happening with my Droid Incredible. I ran CM7 for quite a while and was just living with the problem... it doesn't happen every time I receive a text, but maybe half of the times it triggers my phone to reboot.
I have tried the following, but the phone continues to reboot on receiving texts:
- moved data off of SD card and formatted card.
- wiped data/did factory reset of CM7.
- installed MIUI rom
- wiped data/factory reset of MIUI
- deleted all backups
I'm currently running a completely wiped MIUI phone and it still reboots. I am at a loss as to what to try next. Did you ever solve your problem? Does anyone else have any suggestions?
You could try a new SIM...?
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.
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I'm sure there are several possibilities that could be software related. However, I've had this issue on a couple of my older phones and it just turned out that the power button was sticking. Just had to pull the phone apart and clean it.
If nothing else seems to work for you, it wouldn't hurt to check this.
PS: I have 4 boys who like to play on the devices with sticky fingers.