Stuck rebooting - G1 Q&A, Help & Troubleshooting

I was looking through the Dev Tools app this morning and was in Development Settings. As I was scrolling down looking at stuff I accidentally checked "Show Running Processes".
My phone stopped responding and then a few seconds later did a quick reboot (it only went to the Android loading screen). It came back up but only for a few seconds then it went back to the Android loading screen. It hasn't stopped.
I did a Nandroid backup of it (unfortunately I didn't have a recent backup to restore too) so that if someone can help me fix this I'll be able to reload it. I ended up having to do a wipe to restore functionality to my phone.
I'm guessing that it's running out of memory trying to do what ever the "show running processes" does and ends up reloading due to that. Only problem is it keeps doing it again and again and again...
When the phone reboots I don't have any functionality, all I see is the lockscreen. Sometimes I can hit menu and it'll take me to the home, but there is nothing on the home screen and I can't move the launcher tray.
I'm in the process of moving, so I can't find a USB cord to hook to my computer to get an ADB logcat of what is happening.
Any help?

Is this on CM 4.2.13? If so, it is a known reproducable bug, that happens when you tinker with settings you shouldnt be
Try flashing down to 4.2.12.1 via recovery, you should not get the loop in this version. Then disable the 'display all running processes' and flash to 4.2.13, then re push the Contacts.apk

I just found that interesting feature with SuperD 1.9.2 last night. (I was heading for "Show CPU usage" and got curious).. word of advice, don't check the "show running processes" box..
interesting thing though, I noticed on each of the successive reboots it started at the android boot anim, skipping the T-Mobile G1 boot screen. Anyway, I ended up wiping and reinstalling. Weeeee......

Related

[Q] HELP: 'the application logs provider' force close loop after instalin'2.2

Help!
I upgraded to froyo via Kies then all hell broke loose.
On first reboot after installation..a "new user menu" comes up asking for the user's preferences, once that pops up I start getting the following force close loops one after the other, force close one...another pops up:
The application logs provider
Gmail something
Media something
And keeps going on and on.
Decided to do a factory reset, since everything is backed up by google, did 3br clicked on factory reset...phone gets into "Downloading, do not turn off targett!!!" screen....I let it sit there for 30 minutes, no action. So disconnected the battery.
Booted normally, same issue as above.
Then decided 3br, and the "downloading" screen immediately came up after reboot without giving me the options of recovery mode.
So now, my phone boots into two forms only, and gets stuck there:
1. force close loop on user data entry page
2. with 3br, phone gets stuck on "Downloading' screen.
Any solutions for a non-developer like me?
FYI, running ryanZa one-lick lagfix. So phone is rooted.
Help...really need my phone back
Its easy!!! go to app manager and clear data!
Did you undo lagfix before updating ??.
jje

[Q] Phone on Doc's ROM suddenly locks up and upon reset apps go crazy.

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.

[Q] SGS on DOC rom suddenly hangs, then upon battery pull and reboot..apps go crazy.

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.

Ridiculously easy to corrupt settings - Normal?

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

Losing Hope, my phone suddenly becomes Corrupted

This is one of the weirdest problems I've had. I'll try to be very specific. I'm running Android 6.0 on a Moto G 2014. I was just using my phone, on YouTube, when it decides to randomly reboot. Ok, just an error. Then I noticed that my phone's lockscreen never shows up anymore, and I can't pull down the quick settings. I thought it was just an error from the unexpected reboot it had, so I do a full reboot. No change. Okay, maybe clearing cache and dalvik will solve this. Cleared, reboot, Android is Upgrading, and no change. Okay, now I'm worried. So I restore a system backup from a month ago, reboot, and no change. I also tried uninstalling xposed framework, and no change. Now I don't know what else there is to do before factory resetting, because I really don't want to do that. By the way, here's all of the problems I've noticed since that reboot:
Can't pull down notifications.
Lockscreen will not show up at all.
Home button does not work at all, pressing it does nothing. I have to press back if I want to get to the homescreen.
"Developer options are not available for this user" error screen, even though I'm the only user
adb won't respond (probably for the reason above)
I get no notifications at all
I can't receive calls
Any tips or steps I should take to find this problem? Any help is appreciated.
Solved
Restoring System, Data, and Boot from early June took the problem away. But it bothers me that I'll never know what the problem was.

Categories

Resources