I decided to do a reboot just to have a fresh start after adjusting some app. The phone was stuck at the flashing Darky logo for indefinite amount of time. After a minute or so of flashing logo, phone vibrates shortly and continues flashing the logo. That repeats each minute.
Taking out the battery and retrying didn't help, same thing.
In the past 48h since last boot, I've installed a bunch of apps, mostly games, so it's natural to look for a culprit among them. However, right now I can hardly do anything with the phone. I can access the recovery menu, download mode probably as well and that's it.
I'm ready to flash the Resurrection Edition, but first I'd like to exhaust other options for fixing the problem or at least backing up everything I can. I have partial backups but would very much like to access the latest changes that weren't backed up.
My questions are:
1) Is there some kind of boot logging that I could turn on, access and which would point to the problem? I'm comfortable using ADB if it's needed.
2) I did a CWM backup. What did it backup? Primarily, what about contacts, SMS messages?
3) The most important question: If I reflash the ROM and then use CWM restore, will the problem repeat itself? (If an app is the source of the problem and all apps are backed up and then restored, I'm afraid the problem won't go away. I see few big image files in the backup folder which suggests that everything will be restored as it was. Bootloop too?)
Additional hints for experts on what might be causing the problem:
There are only two incidents that come to mind.
First is that I did a wipe flash of darky 9.1, then a regular flash of 9.2. After I discovered my GPS simply doesn't work on 9.2, I did a regular flash back to 9.1. This was about 2 weeks ago. Is there something in this procedure that might leave some problems that would show up in the future?
Second thing is a incident I had 2 days ago (the time last reboot was done and last time I've had a successful boot).
I left the phone ON over night, and in the morning found it turned off. I thought it might be a dead battery so I plugged it in. It wouldn't start for few minutes but then booted normally.
During that day I found it OFF one more time, for no apparent reason. This time battery was nowhere close to low. It turned off while in standby/locked screen mode so I can't say that it was doing anything in particular.
(Even the turning off during the night is suspect. It had sound on, it was near my head, and I'm sure that low battery warnings would wake me up. It might just be the case it turned off for no apparent reason like it did during the day.)
i think, that when you flashed 9.1 over 9.2, it could leave some weird things, because everyone is talking bout updating, and no-one even think about downgrading rom.
Answer 1. If you used SpeedMod kernel, I think you can turn Logging in Tweaks Menu at RM, and start phone with plugged USB cable to computer (running adb).
Dunno bout other kernels.
Darkyy normally turned off logging, because ROM was bit faster without it.
Answer 2. Probably contacts were synced to Google (contacts.google.com) <--- try it
I think SMS messages are backed up together with whole ROM (contacts too).
Answer 3. Probably yes, problem will repeat. I don't know but maybe there is some way you can restore only some things, not whole system.
I think you should make "Backup Everything" in CWM, then try flashing 9.2 again.
Weird that GPS were not working there.
It seems something bad was happening that caused random reboots.
What apps that require root, you were using? Swapper, Galaxy Tuner, Overclocking?
Related
So I've been lurking around this forum ever since the G1 first came out. Messed up on the rooting procedure once, got a replacement a few months ago.
Worked fine so far. A while ago, I flashed the latest SuperD rom. I am using an 8gig SD card. I've overcharged my battery several times by accident, so the health isn't exactly up to out-of-the-box standards.
I noticed the phone entered a random reboot when I turned the music on for a while. As time passed, the random reboots became more and more frequent. Since I couldn't keep the phone on for more than 20 seconds without a reboot, I decided to wipe and flash a new rom today.
I chose Pays 1.6 Rom and flashed that. Didn't wipe my ext4, just wiped and flashed. I figured ext4 wouldn't cause such a problem, so I ignored it for now. Problem not solved.
I turn the phone on, and in the few seconds, I noticed the following:
the apps all show up, meaning the phone reads the ext4 apps (right?.)
The sd card itself displays an error - I can't access music, pics, etc.
Phone service is fine, all apps are normal.
Buuuut there's still that random reboot issue. It reboots, enters a G1 screen, then reboots quicker. In other words, after I take the battery out and reboot, it might take maybe 1 minutes before it auto-reboots. I wait, then it reboots in maybe 30 seconds. And faster and faster, until it doesn't respond anymore and I have to take the battery out again.
I'm not sure what I do causes random reboots. Sometimes it's when I press a button while in the music app. Sometimes it's when I open the keyboard. Sometimes it's just when the screen goes to sleep. It's fairly random.
I can go into recovery (once I take the battery out once.) Fastboot also works.
Running the danger SPL and the second to latest radio (I believe a new one came out recently? Mine's the one with 26)
Help please? What part of my phone is broken?
I'll give additional information if asked. Not sure what parts are relevant.
Sound's like Kernel panic. Wipe everything and install soemthing stable like cyanogens 4.2.15.1 or dwangs rom. Didn't know there was anything worng with SuperD's kernel though.
jaekim708 said:
So I've been lurking around this forum ever since the G1 first came out. Messed up on the rooting procedure once, got a replacement a few months ago.
Worked fine so far. A while ago, I flashed the latest SuperD rom. I am using an 8gig SD card. I've overcharged my battery several times by accident, so the health isn't exactly up to out-of-the-box standards.
I noticed the phone entered a random reboot when I turned the music on for a while. As time passed, the random reboots became more and more frequent. Since I couldn't keep the phone on for more than 20 seconds without a reboot, I decided to wipe and flash a new rom today.
I chose Pays 1.6 Rom and flashed that. Didn't wipe my ext4, just wiped and flashed. I figured ext4 wouldn't cause such a problem, so I ignored it for now. Problem not solved.
I turn the phone on, and in the few seconds, I noticed the following:
the apps all show up, meaning the phone reads the ext4 apps (right?.)
The sd card itself displays an error - I can't access music, pics, etc.
Phone service is fine, all apps are normal.
Buuuut there's still that random reboot issue. It reboots, enters a G1 screen, then reboots quicker. In other words, after I take the battery out and reboot, it might take maybe 1 minutes before it auto-reboots. I wait, then it reboots in maybe 30 seconds. And faster and faster, until it doesn't respond anymore and I have to take the battery out again.
I'm not sure what I do causes random reboots. Sometimes it's when I press a button while in the music app. Sometimes it's when I open the keyboard. Sometimes it's just when the screen goes to sleep. It's fairly random.
I can go into recovery (once I take the battery out once.) Fastboot also works.
Running the danger SPL and the second to latest radio (I believe a new one came out recently? Mine's the one with 26)
Help please? What part of my phone is broken?
I'll give additional information if asked. Not sure what parts are relevant.
Click to expand...
Click to collapse
Since the rom relies on apps to sd I would guess the ext is borked and maybe the fat32 as well. I would reformat the whole thing to fat 32 then reformat to ext2 or 3. Load Dwangs rom for testing (easier to get running just as a test).
So I wiped my SD (ext4, dalvik, fat32) and tried cyanogen. Then I tried Pays. Reboot problem's gone, but neither of them is reading my SD card.
I'm assuming its just a matter of backing up the SD and repartitioning? I'll try that next when I have time.
Thanks for the help guys! Lastly, any ideas on why this happened? It'd be hard to pinpoint the exact reason, but I'm assuming I'm not the only one who had this problem - how did other people get to the situation I'm in?
I wiped all of my SD, repartitioned, wiped the phone, flashed AOSP 1.6. w/ root and "expansion" pack.
Reboots are less frequent, but they still occur too often. They don't occur by themselves - its always when I'm using my phone.
It seems that it reboots more when its connected to my computer. The SD isn't mounted, but the simple fact that its connected seems to trigger reboots more frequently. Is this a coincidence or can a USB cord trigger reboots?
Help please
EDIT: The phone just made an audible cracking sound as it rebooted - like someone stepping on gravel. Hardware issue?
Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.
This is not a reason to start a new thread in the Development forums.
Support and Q&A for custom roms should take place in their appropriate threads. Use a bit of common sense, courtesy, and patience -- people will help you.
Please read the rules of posting new threads again here: http://forum.xda-developers.com/showthread.php?t=788800
anoneemooz said:
Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.
Click to expand...
Click to collapse
1) Lock ups most likely due to removing drm file from system apps.
2) Your using lagfix (I assume) and when you pull battery data corruption is very likely on some configs.
3) Read rules before posting.
I was just getting over the initial buyers remorse phase for my galaxy (or in my case, flashers remorse, even though I run stock JPY and it's fine, I have this urge to re-exchange it for a SLOWER stock Vodaphone Australia 2.2 version that's probably more buggy, but at least truly stock), when I drained my battery to 1% to test battery life, and shut it off manually.
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) left right and center then went straight back into default first-boot menu, like the very day I received the phone, or after a hard reset. The funny thing was, instead of having default values selected, it had the ones I had already put in. I thought it would be fine after that. Wrong.
I tried rebooting it again to see if it fixed itself, and it does the same with the forced closes. I uninstall my background and re-install it, and save some settings. When it boots it restores the live background back to it's stock settings (the live wallpaper I chose is still there, but the settings for it are not).
At this point I'm scratching my head so I uninstall all apps. This time on boot it doesn't throw up "force close" errors, but instead force-closes a single app or service for me on boot, with the one buzz, then three quick buzzes. Sigh... I have to factory reset my phone. One thing that particularly annoyed me was the fact I moved all my apps (AngryBirds ) to my external SD card, yet miraculously, after the reset my phone doesn't seem to think it's there anymore! Another thing I'm pondering is that if I didn't reset my phone like this, would this still have occurred?
Runs perfectly fine after the factory reset, with no errors or anything on boot as of yet. I have been compulsively rebooting it ever since just to find out, LOL!
Is this a 'normal' sort of thing to happen on the SGS, or is just through shear coincidence the combination of me restarting the phone in it's booting phase + the low battery life screwed up some boot settings while the phone was writing to it, or is it some hardware error? I can see this as particularly annoying if it were to happen every month or so. Coming from an old brick phone with something like 8000 messages on it, it'd be inconvenient to say the least to start deleting everything periodically... I guess I can use apps to back-up data when this occurs, but some apps don't even work after it's been erroring out on me. *Pulls hair out*
TL;DR:
Reset my phone while it was booting (still on the GT-I9000 screen) on a low (1%) battery and it broke my phone settings. Forced closes unknown app/service on boot with no 3rd party apps installed, but still boots to home. Force closes 3rd party apps frequently if they're installed. Factory Reset/Wipe. Problem Solved. Annoyed. RAGE.
next time something like this happens use adb logcat to figure out what is actually going wrong
exclamationmark said:
...
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) ...
Click to expand...
Click to collapse
you are not alone . after draining battery , starting it accidently up (drained) in middle of booting , killed it for me, well not killed but wouldnt boot for me and I had to the the factory reset. oh and since the nice bzz ... bzz bzz bzz I hear more often I would like to ( here was I ignored crying about it http://forum.xda-developers.com/showthread.php?t=937938 )
Yeah I'll definitely boot up logcat if it happens again. I'm just hoping this isn't a regular occurrence . As long as I don't do anything stupid like this again, I'm thinking it should be fine.
The third time this happens, it's going back to the service center, so it's got two chances left! Another thing I failed to mention was that it was chewing up like 200mb~ ram with level 1+2 ram cleared, without loading back into the homescreen, before the factory reset. Probably the stupid forced close app/service leaking >.>
Pagot, if that were me and continual factory resets were the only way to fix it (or didn't fix it) I'd flash it back to stock (or just remove root) and return it to the service center if that's an option. Sounds like something got corrupted or didn't get flashed properly. Either way I'd let THEM waste their time sorting it out because no amount of flashing is going to solve a hardware issue if it turns out to be one.
exclamationmark:
(had stock, so just root removing) but I know how our service centers work (and I would have to bring it even to our carrier) they wouldnt even talk to me if I didnt do the factory reset and the first thing they would do "reflash and factory reset"
right now I am not playing on the phone so much anymore. no lust or time so no idae if my apps are still fcing so often . And I installed speedmod and made a backup so I can revert back if something happens. So will see.
Wanted to just write about the battery down +(or) not full boot = corruption
I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.
stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues
Hello everyone,
This is my first post on XDA so please forgive me if I'm doing something wrong.
So my story, I got a refurbished unit at Swappa, I updated to the newest version directly (G920TUVU3DOI1) and it was working fine for the first week or so. Then the reboots started happening, I didn't give it too much thought but looked into it anyways.
At first I thought it was a problem with the WiFi and I tried to keep it off for a while, and it did work for a day but again the restarts kept happening, and now with the phone turning off during the night (no apparent loss in battery mind you).
Then I went to rooting and custom kernels.
I installed unikernel v8-0002 through Odin3_v3.10.6 and I tried removing some Samsung apps with TitaniumBackup in case there was some conflict happening but the restarts kept happening.
Then I installed a custom ROM, "XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S" to be more specific.
And to my surprise it worked great, no restarts or shutdowns for about 2-3 weeks, it was great!
But then out of the blue the restarts started happening, they started slow, about 2-3 a day.
But after a few days they went to 10-20 and after that 100-200 a day.
Something was definitely wrong. So I installed the original firmware again (G920TUVU3DOI1_G920TTMB3DOI1_G920TUVU3DOI1_HOME) and booted to the stock firmware, restarts kept happening of course (didn't expect them to stop).
So I retreaded my steps and installed multiple other kernels (Unikernel V9, Vindicator, multiple different flavors of them). Also I installed multiple ROMs (Arrow_ROM_v6.0.0, and DN5 - S6 FLAT - EDGE v4 OJ5 - deodex) but nothing seems to work;
I did multiple wipes, storage wipes, cache wipes, factory resets (from GUI and twrp-2.8.7.2-zeroflte) but every time the same thing happens.
I did notice that the phone stutters and freezes, a behavior that I have not experienced before.
I installed CatLog and got multiple log files when the phone restarts but all of them are different and there is no "pattern" to be found (at least in first inspection). I want to upload them but my post count prohibits it.
Please let me know what can I do, I will reply to your questions ASAP so at least I can get some light into what is happening.
Thank you!
I'm in the same boat. Never had a problem before. Received my phone back from Samsung after a screen repair and now, doesnt matter what rom, kernel, patch, it always ends in random reboots. Most often when I'm scrolling or if a page is loading something in the background. It does a lot of hot reboots (not full shutdown and start ups) so its quick but infuriating. Tried everything, slowly losing my patience.
Any idea what it could be? Something related to Knox? Bootloader/Modem?
#3
Hello, I am too having the same problem. Even after a factory reset