Is there anybody out there that can help?
I've had a SGN for over two years and it seems like I have always had problems with it. I've been through mulitple SIMS, devices, ROMS, and various apps. Most recently, I had to get a new device. It took several steps of troubleshooting, but I finally rooted the phone. Got Rootchecker Pro and was able to confirm with no errors. For a while now, when I wipe, CWM skips over Android_Secure because it can't be found. About a month, after rooting the phone, I flashed the CRDroid (based on Cyanogenmod) ROM. It was then that I would get bootloops after checking on the Mobile Networks setting. It didn't always do it right away. When it didn't restart immediately, I wouldn't be able to make phone calls. Shortly after, I went through the Developer Options and updated to CM 10.2. The Mobile Network Bootloops stopped and I thought everything was great. But, there has been about three times that the phone will randomly restart and go into a bootloop at the CM splash screen. It's happened a couple times randomly and yesterday after taking about 45 pictures over a 45-minute span.
Luckily, I've been much better about making Nandroid backups and it hasn't been a big deal to restore. You can imagine, though that it is incredibly annoying and critical sometimes. I've been trying to rack my brain about what is consistent about the bootloops and can't figure it out.
It's a Toro with CM 10.2 on 4.3 Android. I flashed Golden Kernel and PA 4.0 GAPPS.
I would love to see what everybody thinks the problem could be. Thanks again.
Related
Well, this sucks. Upgraded from the Hero to the Desire Z 1.5 weeks ago. Downgraded it, rooted it, tried out a few ROMs, settled on Virtuous Unity and all was happy.
I used the phone in the car this morning as a GPS, 3G data connection was working fine, etc. I had a couple of client meetings, after which I pulled out my phone to check for messages. I noticed there was no mobile signal at all. I figured it was building interference, so I went outside. Still nothing. Wifi was working fine, GPS was working fine. I enabled airplane mode, then disabled it again to see if that would kickstart things. Still no go.
I decided then to power cycle the phone to see if that would help. It went through the usual reboot cycle, displayed the lock screen, then the SIM unlock screen. Then no matter what I do or don't do, about 5 or 6 seconds later, the screen suddenly goes black and the phone reboots.
Now it just does the same thing over and over again. The phone boots up fine, displays the lock screen briefly, then the SIM unlock screen, then it crashes and reboots. Whether I unlock the SIM or not doesn't matter. Within 5 or 6 seconds, the phone will reboot. I can see notification icons popping up, so everything appears to be working fine otherwise.
I have not changed anything on the phone this morning: it was sitting in my pocket the entire time. Same ROM, same radio firmware. I restored last night's nandroid backup just in case, but it didn't help. I thought perhaps it was VU's built-in overclocking that wasn't agreeing with the phone, so I restored a MIUI-based backup. No go. I went all the way back to the stock (but rooted) Bell Desire Z image I took when I first got the phone. Still no go.
I've tried booting up without the SIM card, and without the SD card. Nothing works. I'm guessing the phone suddenly developed a hardware problem. It would be something that is triggered soon after the OS has successfully loaded. Maybe something to do with the 3G radio?
There are no obvious errors or kernel panic messages in logcat. Everything appears to be proceeding normally, until it just comes to a dead stop. Anyone have other suggestions I can try?
Search this forum for "boot loop" and you'll find some things to try.
Thanks, burtcom, but none of the threads I checked apply here. Other boot loop problems more often have to do with the phone rebooting while the boot animation is still playing. My phone successfully boots and is in the process of loading user apps when it crashes. Also, most reports come as a result of something attempting to root their phone and then installing a ROM. I've already made it past that stage. I am able to boot into CWM, do my nandroid backups and restores, etc. The ROMs have all been working fine up until some point this morning. The fact that several different ROMs now all have the same problem makes me suspect a hardware issue.
Moved my SIM and SD card back over to my Hero, and everything works fine there, so I strongly suspect some hardware just broke on the DZ this morning. I'll try flashing a new radio firmware, but I can't see how that would fix anything, since the old version was working just fine all along.
taob;15238893I'll try flashing a new radio firmware said:
Huh... so I flashed the latest Bell Canada 26.06.02.25_m2 radio.img, (up from my old 26.03.02.18_m3 firmware), and now the phone no longer crashes. I'm thinking maybe it isn't an issue with old vs new firmware, but that the old firmware was somehow corrupted during the course of the day. Re-flashing the original radio probably would have worked too, but now I have the latest one...
Hopefully this will help someone in the future with the same problem.
Click to expand...
Click to collapse
The phone no longer reboots, but I still had the problem of not picking up any signal whatsoever (voice or data), even though wifi and GPS work just fine. APN settings were verified to be correct. It turns out I had to go into Settings -> Wireless & networks -> Mobile networks -> Network operators -> Search network and manually re-register my phone on TELUS. Bizarre.
I had the same problem, update your radio and flash this zip on the Unity Thread
"For people experiencing random phone Freezes, this is due to overclocking, it's solved by lowering max speed.
Just flash this patch over: (link is on the thread)"
That's a different kind of problem, sengalang. My phone was working just fine overclocked to 1.2 GHz for over a weeks, so why would it suddenly start crashing like this? Problems due to overclocking tend to result in reboots at random times, and not at 100% predictable times like my problem. I did also boot with the MIUI and stock DZ ROMs, which do not overclock... same problem. Thus the root cause was not CPU speed.
Short version:
Use CWM or TWRP to (1) format sdcard, (2) erase dalvik cache, (3) erase cache and (4) factory reset. This seems to resolve at least one source of random reboots. If installing a new ROM, do that first and then followed by the four steps, then boot into the new ROM. Step (1) may be the important one (in which case it might, in principle, be possible to solve the problem while saving userdata), but I don't know.
UPDATE: It was working fine and I had to spoil it all by installing MIUI, just for kicks. Now, the old problem is back and the solution above doesn't seem to work. Looks like this is not a completely reliable solution...
* * * * *
Long version:
My wife's GNex was in a very bad way. It is entirely stable in Android 4.0.2. But if either upgraded or flashed to anything else, will randomly reboot. Actually, it's not even that random--it will reboot on its own within a couple of minutes of idle with the screen off. I tried all sorts of things--flashed different ROMs, radios, etc.--factory reset multiple times. Googling turns up lots of chatter about random reboots but little by way of viable solution. I figured that the problem may be hardware related. But all Samsung's servicing did for me is to return the unit to 4.0.2. At that time, 4.0.4 was just released and the local servicing centre hadn't even received their copy of the ROM (for yakjuwx). In the end, I 'solved' the problem by rooting and disabling the OTA update notification. (My wife wasn't bothered by the fact that she wasn't running the latest Android version. And the phone works fine in 4.0.2 otherwise.) Work and life caught up and I didn't think much of the matter after that.
That was about a year ago.
Recently, I migrated my wife to a brand new GNex, and took the opportunity to try my hand at solving the problem again. I flashed the latest 4.3 ROM, the latest stable CM10.1, Paranoidandroid, etc. But no matter what I tried, somehow, the phone is stable only with Android 4.0.2 (ICL53F). A chance find online mentioned something about data corruption on the sdcard as a source of problem, and that the usual factory reset doesn't actually reformat the sdcard (it only marks it as empty). Putting 1 and 1 together, I used CWM to do the things listed above (see "short version") and now, the phone is running stock 4.3 (JWR66V), stable CM10.1 and Paranoidandroid without random reboots so far. So now, I am a happy camper, though with one extra, fully functional white GNex.
Footnote: If you don't understand what I said in the short version, it's best you don't try doing anything yourself without first reading up on fastboot commands. This is one place to start. I am not responsible for anyone bricking their device fooling around.
Thanks for reading.
Update to my adventure.
Just about resigned to the fact that the phone is back to its old ways. The old tricks no longer work. What happened next?
1. Left off for more than a day (I gave up).
2. Installed AOSPA PARANOIDANDROID 3.96--using CWM, installed ROM, GApps, wipe dalvik, wipe cache, format sdcard.
Weirdly, the phone now seems fine. It hasn't rebooted by itself after 30+min in sleep. The old problem was that it will invariably reboot by itself in within 2 minutes from screen off so even if there are other problems, the old one is not there anyway.
Something in the steps above seems to have made a difference.
Still monitoring.
Hi all. My finicky T989 is stuck at the Android 4G screen and will not boot past it. Some background on the phone, about a year ago it was dropped in water. Immediately place in rice and after a couple of days it worked fine, with a few odd quirks. Initially the camera LED stayed on all the time, so i didn't use the phone for a couple pf months and when I went back to it, it worked fine. It doesn't like any roms other than TouchWiz, CM or AOKP versions give me all sorts of errors when running, normally I cannot access any of the phones memory.
So.....on to my current issue. The phone has been running fine, but last week told me the headphones were plugged in when they were not. I rebooted to see if it would fix the issue, but the phone is stuck on the Android 4G screen. I can access recovery (TWRP) and download mode, I have reflashed the installed ROM, which is a stock rom titled "UVMC6_HERCULES_TR_STOCK_-IQ_RIPPL-H20" and the phone still sticks at the 4G screen.
I have a backup, but it's a couple of months old. This is my wifes phone, so the lost apps are no big deal, she doesn't use too many to begin with. The big loss are the text messages. Since I can still access recovery and download mode, is there any way to pull the messages from there? My TWRP version is 2.6.0.0. I've tried to backup the data portion of my current rom, to save the messages, but it fails.
twism50 said:
Hi all. My finicky T989 is stuck at the Android 4G screen and will not boot past it. Some background on the phone, about a year ago it was dropped in water. Immediately place in rice and after a couple of days it worked fine, with a few odd quirks. Initially the camera LED stayed on all the time, so i didn't use the phone for a couple pf months and when I went back to it, it worked fine. It doesn't like any roms other than TouchWiz, CM or AOKP versions give me all sorts of errors when running, normally I cannot access any of the phones memory.
So.....on to my current issue. The phone has been running fine, but last week told me the headphones were plugged in when they were not. I rebooted to see if it would fix the issue, but the phone is stuck on the Android 4G screen. I can access recovery (TWRP) and download mode, I have reflashed the installed ROM, which is a stock rom titled "UVMC6_HERCULES_TR_STOCK_-IQ_RIPPL-H20" and the phone still sticks at the 4G screen.
I have a backup, but it's a couple of months old. This is my wifes phone, so the lost apps are no big deal, she doesn't use too many to begin with. The big loss are the text messages. Since I can still access recovery and download mode, is there any way to pull the messages from there? My TWRP version is 2.6.0.0. I've tried to backup the data portion of my current rom, to save the messages, but it fails.
Click to expand...
Click to collapse
It looks like its stored in /data/data/com.android.providers.telephony/databases/mmssms.db
I just tested TWRP's Advanced / File manager on my t889 and i was able to copy it to my external SD
Hope that helps ya out man. If so, dont forget to hit thanks
http://minhdanh2002.blogspot.com/2012/02/raw-access-to-sms-database-on-android.html
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
twism50 said:
Hi all. My finicky T989 is stuck at the Android 4G screen and will not boot past it. Some background on the phone, about a year ago it was dropped in water. Immediately place in rice and after a couple of days it worked fine, with a few odd quirks. Initially the camera LED stayed on all the time, so i didn't use the phone for a couple pf months and when I went back to it, it worked fine. It doesn't like any roms other than TouchWiz, CM or AOKP versions give me all sorts of errors when running, normally I cannot access any of the phones memory.
So.....on to my current issue. The phone has been running fine, but last week told me the headphones were plugged in when they were not. I rebooted to see if it would fix the issue, but the phone is stuck on the Android 4G screen. I can access recovery (TWRP) and download mode, I have reflashed the installed ROM, which is a stock rom titled "UVMC6_HERCULES_TR_STOCK_-IQ_RIPPL-H20" and the phone still sticks at the 4G screen.
I have a backup, but it's a couple of months old. This is my wifes phone, so the lost apps are no big deal, she doesn't use too many to begin with. The big loss are the text messages. Since I can still access recovery and download mode, is there any way to pull the messages from there? My TWRP version is 2.6.0.0. I've tried to backup the data portion of my current rom, to recover the messages, but it fails.
Click to expand...
Click to collapse
Hey! How was it going on finally? Did you try pyraxiate's suggestion?
If it works for you please let me know coz I don't want to try the complicated method that turns out not applicable.
so here's the deal
i've been using my One X for a year or two now, half of the time with cyanogenmod on it, the other with Paranoid Android
but one day, the launcher crashed.
I rebooted it, thinking it was a temporary problem, and everything went fine for a few hours
after which multiple apps started crashing, then the launcher again.
I rebooted it again, hoping the problem would magically vanish, but my phone wouldn't boot, it'd stay on the bootloader screen
for a while now if I stood in the Phone app i'd be fine until the end of the day
since then, every time I install a ROM on my phone, it would go fine for a few hours, even a day or two, but then the problems come back, though I haven't been stuck in the bootloader since
i've tried formatting the SD card, i've tried restoring my phone from a clockworkmod backup and i've tried installing over 10 ROMs now, both sense-based and AOSP
HELP, PLEASE, I DON'T KNOW WHAT TO DO ANYMORE
I've recently started having trouble with my N7100 freezing/locking up.
I bought it shortly after launch, so it's a little over 1 1/2 years old. I had flashed one of the first rooted 4.1.2 firmware that was available, and never bothered updating because it was stable and got great battery life and I didn't feel like dealing with ROM stuff. But recently with the official 4.4.2, I decided to finally update, and decided on trying out DN3. So I flashed the latest TWRP, did the usual backing every thing up, flashed the MJ5 bootloader, and flashed it. It kept bootlooping, so I figured something went wrong, so I restored my 4.1.2 backup. This was where the freezing began. It was to the point where I couldn't use it. Tried rebooting a few times, but every time it would freeze as soon as it booted or shortly after. I assumed something just went wrong with the backup, so I tried flashing DN3 again. This time it booted successfully, but would occasionally freeze, most often when loading an app, but sometimes just randomly. After a couple days it seemed to subside. Then I decided to try out OmniRom. Same thing -- it would occasionally freeze up, then after a while would be fine. (Note: these were both clean installs.) Seems like every time I'd flash an updated version of Omni, the freezing issue would flare back up. Just now, I flashed the latest homemade build, and the freezing was really bad again, to the point where I can't even use it. Sometimes it'll freeze the instant it finishes booting, sometimes it'll freeze a few seconds after, sometimes it'll finish booting and will be fine until I load an app, then would freeze, and sometimes it would be fine for a couple minutes and the just freeze randomly. What's odd about it is that the screen is still responding to touch. Every thing's locked up, but when I touch the screen, the capacitive buttons light up as though it's still working fine, but nothing else works. I've even had a couple times where I let it sit for about 10 minutes and then it started responding again.
What's really frustrating is that I can't find a common cause here.Started on 4.1.2 (which had never had any issues beforehand), continues on a clean install of DN3, and continues on a clean install of OmniRom. Disabling Xposed and removing my SD card had no effect. It boots fine into recovery and download modes.
Does anyone know what the issue could be here?
EDIT: And now I've done a complete wipe, again, and reflashed DN3, again, and it appears to be working fine. Go figure.
It's not suddenly death?
see this: http://forum.xda-developers.com/showthread.php?t=2093599
sorry my english