Hi there,
So I was on Skype to my friend on my i9300, running stock 4.3, rooted, with yank555 kernel and with PhilZ 5 recovery. All these modifications were done about four weeks ago and the phone has served me perfectly well until today.
The flashing Samsung logo that comes up just before the phone boots appeared and the keys stayed lit, when nothing happened for a minute, I held the power button until it reset. Next, the phone took a good two or three minutes to boot and seemed to have forgotten all the information I inputted into it. I still had most of my apps but all the sign in information was gone and all the Google Apps had to reinstall themselves.
There seems to be no cause for the break down, and I don't have a recent backup as I haven't planned to flash anything until 4.4 is officially released. Does anybody know what could have caused this or if there is a way to recover my data?
Cheers.
Unplanned system shut down can partition corruption, reasons for it can be various -battery voltage suddenly dipped, kernel panic etc.
Data on your internal sd should still be there, as on the external sd. Anything else will be gone as it sounds like your data got wiped.
Related
Hello,
Basically, my phone works. I can call, sms, photograph and so on, but:
When I try to flash new rom, via Kies, Odin or other tool everything goes smoothly, blue progress bars advance and complete, phone reboots, and ... I have old rom, nothing is changed, no data is deleted.
When I install new apps they work until I power off phone. After power on new and updated apps are gone, deleted SMS are back, it looks like the phone inside was frozen in time some time ago and all that is going on is going in ram or some virtual machine, and vanishes.
It happened some weeks ago, I cannot recall when exactly. Something I installed was suddenly missing and SMS after reboot came back, but I ignored it then like a sporadic glitch.
I just discovered, that I also can't do factory reset. System recovery <3e> shows, but doing wipe data or wipe cache has no effect. Nothing gets wiped, apps and data remain intact. The only unusual thing I see in the recovery console is:
Can't access to '/system/csc/PLS/system/'
Is it a virus or is it just broken or what?
zieloniak
I suggest doing a deep clean...
Hello xda!
Well, I have a problem, yesterday my phone was working great, but today when I woke up, I found my phone in the CM9 boot screen and it never pass through it. Sometime during the night I woke up and checked the time with the phone and everything was FC'ing, calendar, contacts, and many other system and non-system app were crashing, then I rebooted to fix that crazyness and here I am, stuck in the boot screen. :/
I don't know what's wrong, yesterday everything was fine! I did not fiddle with anything this night! Did I sleepwalk?
The phone is a SGS2 i9100 with CM 9.1 (and the boot animation of CM10).
So far, I tried wiping the dalvik cache, but I'm still stuck. I hope we can fix this without having to wipe everything... It was long ago since I did the last backup.
You could try a dirty flash of whatever CM9 build you're currently running without wiping. To be honest though, this probably won't work (but it won't make things 'worse'). Then try a wipe. And if none of that works, back to stock via Odin & either restore your backup or start from scratch (re-flash whatever rom/kernel you want, restore your apps & contacts, etc, etc).
But what it puzzles me is what happened tonight that the SO broke.
And the upper part of the phone, around the camera (where the main board is placed) gets extremely hot, I even left the phone 5 minutes in the refrigerator stuck at the boot screen to see if waiting long enough would do something, but it didn't.
I guess I'll try doing what you said, and if that doesn't work I'll start from scrath. Anyway I wanted to update to JB. I'll lose some pulled apps from the Play Store but... meh
Could be something hardware on the fritz, or the heat could be related to the firmware problems you're seeing. Don't put the phone in the fridge; fridges tend to be a bit moist, you don't want to expose the phone to moisture like that.
I guess you'll find out if it's hardware or not when you fix it; if the heating issue remains once you've got it running 'normally', then there might well be something hardware-related going on.
pealery ito
Deses said:
Hello xda!
Well, I have a problem, yesterday my phone was working great, but today when I woke up, I found my phone in the CM9 boot screen and it never pass through it. Sometime during the night I woke up and checked the time with the phone and everything was FC'ing, calendar, contacts, and many other system and non-system app were crashing, then I rebooted to fix that crazyness and here I am, stuck in the boot screen. :/
I don't know what's wrong, yesterday everything was fine! I did not fiddle with anything this night! Did I sleepwalk?
The phone is a SGS2 i9100 with CM 9.1 (and the boot animation of CM10).
So far, I tried wiping the dalvik cache, but I'm still stuck. I hope we can fix this without having to wipe everything... It was long ago since I did the last backup.
Click to expand...
Click to collapse
Just try to flash CM9 again without wiping data, wipe only cache partition and dalvik cache, you will not lose data.
I tried reflashing CM9.1, but it's still not working... I'm starting to get worried.
This night I will try to flash a stock rom with odin and wipe everything. And if that don't works... well, damn.
I did say it probably wouldn't work. You're getting in a tizz over nothing, to be honest. You're acting as if your phone's busted (it isn't). Go back to stock & start from there.
Man, I guess it's normal to get a little worried when your phone doesn't get through the boot if I didn't do anything to it... but I wasn't THAT desperate, I was pretty sure it was something software related. Sorry if I gave that impression. D:
I just tried to load a backup that I did back in January and the phone booted, so I guess my only option is start from scratch (and leave my phone far away from me during night).
Thanks for the help!
You are not the 1st person for things going "bump in the night",and you wont be the last.
Seems mostly to happen when cm10 is mentioned.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
Hey Everyone,
I am having an issue with my screen turning on randomly on my phone. Its a Verizon Note 2 (hence me posting in this section). I'd like to think I've done some troubleshooting but I want somebody else to tell me that I am not insane.
So far what I've done:
1. Flashed Custom Rom - CM11 in this case. Screen turning on and off is persistent between stock and CM leading me to believe hardware problems.
2. Took phone apart, unplugged power button from motherboard. Booted phone back up and disconnected. With the cable disconnected it still persisted.
3. Taking a page from some other threads on XDA I have tried the key test in CWM. My screen was turning on every 1-2 minutes and right now its been sitting for 15 minutes with no key presses registered (with the cable re-connected).
So with all of that being done I'm assuming its an issue with something that Google is restoring to my phone? Does that sound like a logical conclusion? Before I factory reformat and not have anything restore I just wanted to post up and verify.
As a second question - is there a good way to clear all the internal memory before I do a fresh format of CM11 (if i go that direction tonight?) I still have folders on the internal SD card from my stock install that i would like wiped out.
Thank you all in advance: I love this site. I've been flashing every phone i've owned from the guidance here but very rarely post.
TheDigitalSlacker said:
Hey Everyone,
I am having an issue with my screen turning on randomly on my phone. Its a Verizon Note 2 (hence me posting in this section). I'd like to think I've done some troubleshooting but I want somebody else to tell me that I am not insane.
So far what I've done:
1. Flashed Custom Rom - CM11 in this case. Screen turning on and off is persistent between stock and CM leading me to believe hardware problems.
2. Took phone apart, unplugged power button from motherboard. Booted phone back up and disconnected. With the cable disconnected it still persisted.
3. Taking a page from some other threads on XDA I have tried the key test in CWM. My screen was turning on every 1-2 minutes and right now its been sitting for 15 minutes with no key presses registered (with the cable re-connected).
So with all of that being done I'm assuming its an issue with something that Google is restoring to my phone? Does that sound like a logical conclusion? Before I factory reformat and not have anything restore I just wanted to post up and verify.
As a second question - is there a good way to clear all the internal memory before I do a fresh format of CM11 (if i go that direction tonight?) I still have folders on the internal SD card from my stock install that i would like wiped out.
Thank you all in advance: I love this site. I've been flashing every phone i've owned from the guidance here but very rarely post.
Click to expand...
Click to collapse
To format the internal SD card, reboot into recovery (sounds like you use cwm), go to 'mounts and storage' and wipe 'sdcard' or 'data/media.' I havent used cwm in a while so I cant remember the exact wording.
While in mounts and storage go ahead and wipe 'system' and wipe 'data' as well before installing the new rom. Before installing a new rom you should always wipe system and data.
As far as the screen randomly turning on it does sound logical that it could be google restoring to your phone. Im guessing that you don't see new notifications in the status bar? How long did you let the phone sit after installing a new rom?
Whichever way I doubt it's hardware.
If you format and reinstall dont choose to restore from Google servers. If the problem still persists then there are ways to know what's waking up your phone.
Hälftebyte said:
To format the internal SD card, reboot into recovery (sounds like you use cwm), go to 'mounts and storage' and wipe 'sdcard' or 'data/media.' I havent used cwm in a while so I cant remember the exact wording.
While in mounts and storage go ahead and wipe 'system' and wipe 'data' as well before installing the new rom. Before installing a new rom you should always wipe system and data.
As far as the screen randomly turning on it does sound logical that it could be google restoring to your phone. Im guessing that you don't see new notifications in the status bar? How long did you let the phone sit after installing a new rom?
Whichever way I doubt it's hardware.
If you format and reinstall dont choose to restore from Google servers. If the problem still persists then there are ways to know what's waking up your phone.
Click to expand...
Click to collapse
Thanks,
I'll be doing that today. How can i tell whats waking it up? The wakelock detector i have been using isn't ready for 4.4 yet.
Turns out it was noon walk that was doing it
Sent from my SCH-I605 using xda app-developers app
Haha good. How'd you find out?
Sent from my SCH-I605 using Tapatalk
My i9300 seems to have lost control on (soft?) boot:
- I flashed a 5.1 omni ROM that made me very happy because really stable enough for me to use multiple apps at same time.
- One week after, I started getting unwanted soft reboots (skips Samsung boot screen), leaving me approx 40s of system use before 5s freeze followed by reboot.
- These soft reboots are weird: if I force shutdown (power menu OR removing battery), the phone boots anyway, by itself!! And I think this is still soft boot because it still skips Samsung boot screen.
Additional info:
- I wondered if my power button was messed up but I don't think so: I would not have this freeze before reboot, plus I have no reboot while in recovery.
- I saw some SMS problems: received one from my provider, and I kept receiving it again at each reboot (same one 50+ times). Any link possible?
What I tried without success:
- Remove SIM and SD card
- Remove battery for a day
- Change battery
- Re-flash recovery
- Wipe System + Data + Dalvik/Cache then install paranoid android (now I can't even boot in anything else than recovery btw)
I'm lacking android system knowledge but it looks like there is a location in "soft reboot zone" that is locked, and the phone keeps reading it and rebooting infinitely. Is there a way to clean this? To forbid soft reboot maybe? Note that I've been flashing various roms for 3 years on this phone and I never saw anything alike.
Any advice is welcome, thank you for caring !
blint6 said:
My i9300 seems to have lost control on (soft?) boot:
- I flashed a 5.1 omni ROM that made me very happy because really stable enough for me to use multiple apps at same time.
- One week after, I started getting unwanted soft reboots (skips Samsung boot screen), leaving me approx 40s of system use before 5s freeze followed by reboot.
- These soft reboots are weird: if I force shutdown (power menu OR removing battery), the phone boots anyway, by itself!! And I think this is still soft boot because it still skips Samsung boot screen.
Additional info:
- I wondered if my power button was messed up but I don't think so: I would not have this freeze before reboot, plus I have no reboot while in recovery.
- I saw some SMS problems: received one from my provider, and I kept receiving it again at each reboot (same one 50+ times). Any link possible?
What I tried without success:
- Remove SIM and SD card
- Remove battery for a day
- Change battery
- Re-flash recovery
- Wipe System + Data + Dalvik/Cache then install paranoid android (now I can't even boot in anything else than recovery btw)
I'm lacking android system knowledge but it looks like there is a location in "soft reboot zone" that is locked, and the phone keeps reading it and rebooting infinitely. Is there a way to clean this? To forbid soft reboot maybe? Note that I've been flashing various roms for 3 years on this phone and I never saw anything alike.
Any advice is welcome, thank you for caring !
Click to expand...
Click to collapse
That SMS thing is strange
Have you tried another recovery version? Or perhaps changing recovery? This isn't a normal issue, since you already tried installing another ROM.... You can try another Kernel either
If none of this works, consider flashing the original Samsung's ROM or some samsung-based ROM (they usually do a nice clean-up, at least for me these ROMs fixes the majority of my problems)
@blint6:
1. Maybe the hardware though. This you can test by flashing actual firmware and running it under normal conditions for 1d.
2. Reboot is a known reaction to RAM-lack on LP, too. Flash Omni cleanly and run it for 1d without GApps and bigger apps.
My phone (Nexus 4) appears to be soft-bricked, and will not boot up. When I turn on the device, it appears to get part way through the boot process but it never completes, and the bootsplash just keeps spinning forever. The top of the phone where the radios/gps/etc are gets very hot during this time.
I've tried: clearing caches within TWRP, factory reset, loading a couple new ROMs, wiping all partitions and reformatting, updating TWRP. Nothing seems to help.
I'm starting to think it's a hardware problem, but I'm hoping that someone might be able to give me some ideas that I haven't tried yet. I can get into TWRP and can load ROMs.
Some background: My phone is a Nexus 4 (mako) and had Cyanogenmod 13.1 prior to the issues, which has been running fine since last year. Recently my phone was acting glitchy/slow, so I decided to clear the cache and dalvik cache a couple weeks ago. This worked great and got things working well again. When I set things up again I also decided to start using DroidWall, which was the only app on my phone using root. About a week ago I also replaced the battery inside the phone since my old battery was shot and could barely keep a charge. The new battery has been working well, and does not appear to be the part of the phone heating up when the phone is stuck booting.
An update. I found that with the Slim ROM loaded, I can run `adb logcat` while the phone is booting to see what's happening. Lineage OS does not seem to ever get far enough to be seen by adb.
When viewing the Slim logcat, there are a lot of logs generated. Within, there are some DEBUG and backtraces displayed. And, I think the phone may be stuck trying the same thing over and over again as I've seen a section appear about the camera several times.
Earlier today I opened up my phone again, and noticed some pressure contacts on the back cover of the case. I cleaned them all to make sure they were making good contact, but it hasn't helped.