Had my phone 2 years, installed ROMs without any issues before.
Was running CM10.1 daily, when yesterday I thought I'd go and encrypt the phone (using the system menu).
Phone encrypted, rebooted, but immediately I started getting 'google play store crashed' errors in an infinite loop. It was usable enough to push the latest neatrom to the phone via USB connectivity, so I did a full wipe (clear data/factory reset, clear cache, clear dalvik, format /system, install rom in CWM) and installed neatrom.
Phone reboots, looks OK at first except for a 'usb storage is blank or unsupported' message in notification center. I try to format it, no dice, just stops displays the notification again.
Of course, without what is seen by the sgs2 as usb storage I can't install any app and everything crashes to desktop (camera, etc).
I'm not sure what to do next, and could use some advice! Thank you!
Right, so now I've bricked it. Odin, GB phone, csr and pda, then black screen, then nothing. Won't reboot either. Just... great.
Ok, thanks for sharing.
Sent from the little guy
I got an iPhone now. Wondering why I spent 2 years of my life with a battery that last 1/2 day and constant issues. Problem solved for good!
Alright! Now you got so many things to do with it.
Sent from the little guy
reflash back to stock rom first, but first make a back up for your current rom. that happened to my tab before. the internal memory is not working and saying something blank/unsupported, really cannot remeber. i couldnt install apps. i contacted the support of the tab (NOMADNINE) and i was adviced to flash it back to stock since it will copy files and put the chipset to write mode and will erase everything... you can try to flash it through ODIN.
He went iOS.
Sent from the little guy
gastonw said:
He went iOS.
Sent from the little guy
Click to expand...
Click to collapse
Yup, plus the SGS2 is hard bricked: no power on, tried various ways to address that but no dice. Off to ebay for spare parts.
Related
Hello, guys. First of all, I'd like to apologize in advance for my bad english. If there is any part of the message that isn't very clear, please inform me so I can correct it.
Here's the deal: I've been using for some time the Jelly Bean Ressuction Remix Rom from Westcrip.
Since about a month and a half (since version 3.9, I believe), I've been getting some weird and random signal drops. Back then, I had to manually reboot my phone so the data connection would come back. At the time I thought it was because the rom was still a nightly build, not very stable, so I coped with it.
This problem has worsen considerably since one or two weeks ago: those "signal drops" have become more and more regular. And following the signal drop, the screen would flicker a little and then the phone would automatically turn off. When I turn the phone back on, the battery is almost depleted, even tho it was full right before the crash. Again I'd blame the RR from Westcrip (by the time I was using the version 3.1.0). When version 3.1.2 came out, I did a clean installation (wipe data/factory reset/format system partition/wipe cache and dalvik, etc), even changed the kernels (used both Dorimanx and Siyah), a lot of modems, and still got this same problem: signal drop (usually when the phone is under a relative amount of stress, like playing Angry Birds, browsing the web, and even while using whatsapp!!!) followed by the phone turning itself off.
I then thought: what the hell, the problem has to be with the rom, not my phone. Then, I tried installing different roms (Paranoid Android and Slim Bean), and still got the same results. If anything, the phone is rebooting even more often now than before. I can't use it for 15 straight minutes and I get that problem,
Since this has happened with all these different roms I dont believe its related specifically to any of those.
Another strange thing: this "signal drop" followed by the rebooting only happens when the phone is disconnected from any power source and being actively used by me. If I'm recharging it, for example, the phone wont reboot at all. Also, if it is over my desk but I'm not using it, the phone also wont reboot. However, if I take it out from the power source and starting using it, I'll get another reboot in about 5-10 minutes of use.
I searched the forum and didnt find anyone with a similar problem... have any of you guys seem this happen before? I'm beggining to think that my phone is gonna die on me anyday now.
Regards!!
Daimao1984 said:
Hello, guys. First of all, I'd like to apologize in advance for my bad english. If there is any part of the message that isn't very clear, please inform me so I can correct it.
Here's the deal: I've been using for some time the Jelly Bean Ressuction Remix Rom from Westcrip.
Since about a month and a half (since version 3.9, I believe), I've been getting some weird and random signal drops. Back then, I had to manually reboot my phone so the data connection would come back. At the time I thought it was because the rom was still a nightly build, not very stable, so I coped with it.
This problem has worsen considerably since one or two weeks ago: those "signal drops" have become more and more regular. And following the signal drop, the screen would flicker a little and then the phone would automatically turn off. When I turn the phone back on, the battery is almost depleted, even tho it was full right before the crash. Again I'd blame the RR from Westcrip (by the time I was using the version 3.1.0). When version 3.1.2 came out, I did a clean installation (wipe data/factory reset/format system partition/wipe cache and dalvik, etc), even changed the kernels (used both Dorimanx and Siyah), a lot of modems, and still got this same problem: signal drop (usually when the phone is under a relative amount of stress, like playing Angry Birds, browsing the web, and even while using whatsapp!!!) followed by the phone turning itself off.
I then thought: what the hell, the problem has to be with the rom, not my phone. Then, I tried installing different roms (Paranoid Android and Slim Bean), and still got the same results. If anything, the phone is rebooting even more often now than before. I can't use it for 15 straight minutes and I get that problem,
Since this has happened with all these different roms I dont believe its related specifically to any of those.
Another strange thing: this "signal drop" followed by the rebooting only happens when the phone is disconnected from any power source and being actively used by me. If I'm recharging it, for example, the phone wont reboot at all. Also, if it is over my desk but I'm not using it, the phone also wont reboot. However, if I take it out from the power source and starting using it, I'll get another reboot in about 5-10 minutes of use.
I searched the forum and didnt find anyone with a similar problem... have any of you guys seem this happen before? I'm beggining to think that my phone is gonna die on me anyday now.
Regards!!
Click to expand...
Click to collapse
Hey,
pls backup ur apps and then do this:
0) Do a nandroid Backup via recovery
-- backup and restore
-- backup to internal (or external) sd card
1) Download Rom
2) Put it on internal sd card
3) Go into recovery mode
4) DO A FULL WIPE!! (U won't loose ur backup on sd card [but u can copy it to PC, too, if u want])
-- wipe data/ factory reset
-- wipe cahe partition
-- advanced > wipe dalvik cache
-- mount and storage > format data/system/cache
5) Then flash Rom
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
6) Then flash Gapps
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
7) Recovery > wipe cache partition
8) Recovery > advanced > wipe dalvik cache
9) Then flash Dorimanx
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
6) Reboot and u r done!
Links:
ROM: U should have already the newest one, or at least u know, where u find it.
Dorimanx Kernel
Gapps
Much success,
CHEERS
Hi, thanks a lot fot the help.
I did all the steps above and I'm still getting the same results...
Another thing to notice is that yhe phone gets really hot for apparently no reason at all (like booting up, running aLogcat and other minor apps), and when that happens, I usually get a signal drop (if the phone is plugged in it wont reboot, if its not, it will reboot).
Is there anything else I can try?
Updating: I've been restoring my old nandroid backups for the whole day to see if the problem had anything to do with Jelly Bean. Well, I've gone back to the old ICS days and every version of it had the same random and constant rebooting. Even versions that didn't have any problem before.
I'm beggining to think I have a hardware failure of some sort. Do any of you guys know what could cause this kind of hardware failure? Since the phone has been getting hot for no apparent reason, it seems to me its a problem with the SGS2 cooler. Is that even possible?
OK so I have this problem but only when using my backup battery. (Not official). When It gets around 30% it begins to make my screen flicker and loose signal and just die.
So maybe you haven't got an original (official) battery in your s2?
Sent from my Galaxy SII
I dont think I have an unofficial battery. Its the same battery that came with the phone (bought from Amazon), and also, mine says Samsung on the back. Dunno if its enough to assume its official. Is there another way to check if my battery is official?
Daimao1984 said:
Hi, thanks a lot fot the help.
I did all the steps above and I'm still getting the same results...
Another thing to notice is that yhe phone gets really hot for apparently no reason at all (like booting up, running aLogcat and other minor apps), and when that happens, I usually get a signal drop (if the phone is plugged in it wont reboot, if its not, it will reboot).
Is there anything else I can try?
Click to expand...
Click to collapse
Do u check if u r using the correct Roms for u phone? (i9100, i9100p, i9100g,etc)
CHEERS
Send from my SGSII-i9100, running RootBox nightly with Dorimanx Kernel.
Hi I am also facing the same problem. Mobile is getting hot near the camera lens.
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
------------------------------------------
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
hackkpo said:
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
Click to expand...
Click to collapse
You should try custom rom. Try to Flash Neatrom or any stock custom rom.
Hope it solves your problem.
Sent from my iPhone using Tapatalk
Firstly, you need to verify that it's a genuine S2. Turn the phone off, take the battery out and post on here EXACTLY what you see on the sticker in the battery compartment.... Just don't post the IMEI number...
Sent from my GT-I9100 using xda app-developers app
Model: GT-I9100
SSN: -I9100GSMH
RATED: 3.7V ------- : 1000 mA
FCC ID: A3LGTI9100
MADE IN KOREA BY SAMSUNG
IMEI: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
S/N: R5XA73828F1
That's all, its seems original, right?
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
hackkpo said:
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
Click to expand...
Click to collapse
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Jeetu said:
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
hackkpo said:
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
Click to expand...
Click to collapse
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Jeetu said:
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Why would i reflash again? i dont get it
hackkpo said:
Why would i reflash again? i dont get it
Click to expand...
Click to collapse
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Jeetu said:
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Click to expand...
Click to collapse
No is not, the cellphone starts normal, and while im using it nothing wear happens, but when i left it the screen goes black and the device reboot itselfs. But now im seeing that doesnt happen anymore, i dont know why.
Still with cyanogenmod rom, i connected the phone to charge the battery, and i saw a tendency of reboots and turnings off while the percentaje comes to 100% and a increasing overheat on the left-top of the phone, i suspect that the problem may be related with the amount of charge from battery and the overheating... Hardware problem?
Well... After all this time my cellphone went through the argentinean official service of samsung and the tech guy told me that he couldn't do anything on my device because he tried installing a lot of samsung official roms and the device was still malfunctioning. So he gave up on it, so i'd tooked it to another service (non official this time) and that guy told me that it may be a non official device, so he wouldnt do nothing on it, because i couldnt get the hardware that possible was malfunctioning. So here im now, with the all money spent for nothing.
My question is, what can i do to know if is or isnt an ORIGINAL samsung device? Knowing that i'll choose how to proceed. Txs!
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
TL;DL: Phones 16gb storage changed to 128mb overnight. None of my files/apps/pics accessible.
I have the international version for the S3 (GT-i9300) with 4.3 stock firmware installed (rooted)
I woke up this morning and looked on my phone to see that my primary launcher, nova launcher, had been reset to the original layout when you first install it. I was confused so I restarted my phone and it went back to touch wiz. But now none of my apps, files, pictures, etc. from the internal memory on the phone are accessible. It seems like it went back to an old backup I once had due to the lack of my newer contacts on board.
When I connected the phone to my PC it only shows 127mb/128mb where as on the storage settings it shows available space of 5.75gb/16gb where all the non system memory are labeled as miscellaneous.
In application manager it shows all my apps i used to have but now they all have the android logo and 0b of storage.
The phone also prompts a message every couple seconds saying clock is not responding.
No idea where to go from here seeing as i can't even access all of my internal storage... Would appreciate some help on my situation, thanks in advance!
EDIT: Tried factory reset, tried installing play store apk, tried flashing an updated firmware, tried booting into clockwork recovery.... all with no luck
Flash full stock firmware with Odin then factory reset.
boomboomer said:
Flash full stock firmware with Odin then factory reset.
Click to expand...
Click to collapse
Thanks for the suggestion. I flashed stock firmware and ended up doing a factory reset through the recovery menu. All seemed well as my phone stopped heating up like it used too, battery lasted longe and all the symptoms I was facing stopped. Unfortunately when I woke up this morning the phone factory reset itself again. Same symptoms as before but this time I can view files, even though everything got deleted...
My question is now should I just flash a different rom like cyanogenmod? So far for the past 2 years I've only stuck to the stock rom and I've faced nothing but troubles. Wondering if I might face the same thing once I convert.
Thanks!