Hi, I just flashed Virtuous Fusion MT4G v1.1.8 and after restoring some data and playing with new rom I thought i need to restart it. Now phone keeps rebooting itself, I'm getting error message and it goes into reboot and all over again. I'm trying to reboot into recovery but nothing happens. Can anyone help with this issue? I hope i didn't killed the phone. Thanks.
Related
I recently bought a rooted Nexus s (GSM), and everything was fine until I powered off the phone. When I re-powered the phone, the mobile data didn't work, and the phone kept harassing me with the notification "sorry! the process com.android.phone has stopped unexpectedly" and made me force close it. and when I do press force close, the notification would pop up again instantaneously until I got tired of it and ripped the battery out.
The phone is currently running on NSCollab-1.0.35 ROM.
I tried hard-resetting the phone, but when I try to do it (via hard key reset and through settings->privacy-> etc) it would get stuck on the black google boot page and wouldn't budge. I can't even get to the recovery page.
I also tried to flash clockworkmod, then fix the permissions, and then reboot the phone, but that also failed.
The only way to stop the phone from harrassing me with the sorry notifications is to put it in airplane mode.. which certainly does not help my case. Please help! I will be eternally grateful.
Ok the reason this is happening is because you used the "switch from 3G to 2G" widget. You should've read the bugs when you downloaded the nscollab. Btw I use nscollab and I love it.
I fixed it by just wiping cache and just reinstalling the ROM.
acesofbelkan said:
Ok the reason this is happening is because you used the "switch from 3G to 2G" widget. You should've read the bugs when you downloaded the nscollab. Btw I use nscollab and I love it.
I fixed it by just wiping cache and just reinstalling the ROM.
Click to expand...
Click to collapse
yes, wow. I did do that. I see, I screwed up. Thank you so much!
acesofbelkan said:
Ok the reason this is happening is because you used the "switch from 3G to 2G" widget. You should've read the bugs when you downloaded the nscollab. Btw I use nscollab and I love it.
I fixed it by just wiping cache and just reinstalling the ROM.
Click to expand...
Click to collapse
well, I'm trying to wiping cache, but I can't even get to the recovery mode...
I love everything about the SK4G but the constant reboots is it's only Achilles Heel. I've tried installing the Glorious Overdose V2 ROM on it, and the phone has seen overall improvement but the reboot problem has not been fixed and everytime I open an application or playing games it will freeze and then reboot. Can anyone suggest a ROM they're using that has helped with the reboots occurring all the time?
Try GingerClone, it's one of the lighter roms.
trying a different rom might help, but chances are if you flashed a rom and the problem persists, then flashing another rom may not help. I had the same problem with the stock rom. my phone rebooted every 15 minutes to a half hour for almost a whole working day. finally I shut the phone off, booted into CWM recovery, clicked on advanced, and ran fix permissions. I suggest that you not use a program or script to boot into CWM, because I have tried that and it doesnt work. after I ran fix permissions, the endless rebooting stopped. if you like the rom you're on, try fix permissions and see if it works. you really dont have anything to lose. if it doesnt work, just flash another rom. I recommend fix permissions a lot, because it has worked for me many times.
Im really hoping someone can help me please...
ever since viper 1.6.x sometimes my phone will shut down, or if my phone battery runs completely dead of battery, and then when i try and turn the phone on again it will go into a boot loop where is gets stuck on the senasation splash screen...
can someone tell me why this is happening and how i can turn my phone back on after this happens...?
info
i am on vipers had this problem since 1.5.x - 1.6.x with multiple kernels, but the last kernel i was on when this happen was faux 10b9
this most often happens when the battery run completely dead, but has occasionally happened on a random reboot swell
things i have tried...
pulled battery...
clearing dalvik and cache - this will get me past the splash screen once, to the android is upgrading page (as i have cleared dalvik and cache) only to reboot at the end and finally get stuck on the htc sensation splash screen again
formated system
installed the rom again with the restore option (the last of the 3 options stating to use it if you have a corrupt operating system)
reflash the kernel
install same rom without wiping
the only thing i know i can do and that ail work is going back and restore an old backup via 4EXT but i no longer have any back ups (dont ask why i did this! i thought it was working now!)
is my only option a full format?
why is this happening?
anyone know a way around it?
does this mean i can never go back to ViperS as i will always have this problem or is the problem from somewhere else??
thanks so much in advance...
i suggest to format all partitions except sdcard
flash viperS rom
see then if your issue exists
otherwise try different rom
also if you are S-ON enable smartflash from 4ext before flashing the rom
I rooted my phone back in December and have been using it without problems since then. I've rebooted it tons of time, haven't installed anything unusual or tried to modify anything. I just followed the normal instructions for rooting and flashing a custom rom. Today, I rebooted my phone and now it's hanging at the Galaxy SIII logo screen. Taking out the battery didn't help. I have no idea why it would do this out of the blue. What are my options for fixing this? Can I recover my data?
blueintegral said:
I rooted my phone back in December and have been using it without problems since then. I've rebooted it tons of time, haven't installed anything unusual or tried to modify anything. I just followed the normal instructions for rooting and flashing a custom rom. Today, I rebooted my phone and now it's hanging at the Galaxy SIII logo screen. Taking out the battery didn't help. I have no idea why it would do this out of the blue. What are my options for fixing this? Can I recover my data?
Click to expand...
Click to collapse
Should be easy to fix. Common issue.
Try booting into recovery. If you can then clear cache and dalvik. Try rebooting then.
If that doesn't work try re flashing the rom,
If you can't reboot into recovery but can get into download mode then you can easily fix it at the cost of losing all your data.
Let me know how it turns out.
At this point, my phone is just one big tweak.
Wiping the caches didn't work, so I ended up having to reflash the rom. Everything seems to be back to normal now though, thanks!
I've been having spontanious reboot problems where my charge would reboot and get stuck in a boot loop freezing on the droid eye animation and rebooting. In the past I've been able to clear the delvic cache and regular cache and get the phone to boot and go back to working order. Today however, clearing cache didn't work. Thinking this was a software problem, I connected the phone to oden and flashed the stock software ED1. I was planning to install back to EP5 and redo Tweaked 3.2 since the phone had developed a lot of lag.
Now the phone gets to the droid eyebll and stays there. Every so often the animation freezes for a second or two then continues. Is the phone dead? Can it be brought back to life so that I can use it while I figure out a new phone. I'm asking because this is my only smartphone and I'm now stuck activating my old chocolate flip
Mike
Why all the way back to ED1? Do you have everything backed up in case you need to flash with the pit file?
Sent from my SM-N900V using XDA Premium 4 mobile app
beavermjr said:
I've been having spontanious reboot problems where my charge would reboot and get stuck in a boot loop freezing on the droid eye animation and rebooting. In the past I've been able to clear the delvic cache and regular cache and get the phone to boot and go back to working order. Today however, clearing cache didn't work. Thinking this was a software problem, I connected the phone to oden and flashed the stock software ED1. I was planning to install back to EP5 and redo Tweaked 3.2 since the phone had developed a lot of lag.
Now the phone gets to the droid eyebll and stays there. Every so often the animation freezes for a second or two then continues. Is the phone dead? Can it be brought back to life so that I can use it while I figure out a new phone. I'm asking because this is my only smartphone and I'm now stuck activating my old chocolate flip
Mike
Click to expand...
Click to collapse
No, the phone is not dead, it is a bit lag.