Galaxy s3 internal SD not formatting appropriately - Galaxy S III Q&A, Help & Troubleshooting

So, while trying to install cyanogenmod in my s3 and after wiping the cache and preforming a factory reset in clockworkmod recovery both music and photo data wasn't removed, tried again but nothing happened! What should I do this is very confusing ?

Castdeath97 said:
So, while trying to install cyanogenmod in my s3 and after wiping the cache and preforming a factory reset in clockworkmod recovery both music and photo data wasn't removed, tried again but nothing happened! What should I do this is very confusing ?
Click to expand...
Click to collapse
me too, as a matter of fact i`m now in great trouble because the device won't recognize my ex-sd, cwm won't mount it, there is no way to re flash ROM ( odin doesn't support installing CM ). When i go to setting-> storage the phone simply crashes. so anyone know how to just wipe out everything, make the internal mem back to its original???

Use the cyanogen mod installer
Sent from my GT-I9300 using xda app-developers app

Maybe you can try the Mega wipe script at this link http://forum.xda-developers.com/showthread.php?t=1983489
Use at your own risk, and keep a backup somewhere because it will erase everything ..

Brother,
Only stock recovery gets crazy and erase everything in your internal memory and resets the rom and wipes the app datas …
Custom recovery does't do that it protects your personal data and only wipes app data and resets the rom …
If your issues is with a buggy rom try a different one …
External sd not mounting is an rom issue not with factory reset …
If you want to go back to stock, data wipe isn't going to do it, you will have to download the stock rom from sammobile.com and flash it using Odin …
Ps: get the correct stock rom or you'll brick your phone!!
If I helped hit thanks …

i think the 4.3 stock is the problem... it prevents any cook rom to get access to sd but i'm not sure why this is possible... all i know is i use odin to install stock 4.3 and it works without problem but switching to any rom cook then the sd just simply gets lost...

vutranloc said:
i think the 4.3 stock is the problem... it prevents any cook rom to get access to sd but i'm not sure why this is possible... all i know is i use odin to install stock 4.3 and it works without problem but switching to any rom cook then the sd just simply gets lost...
Click to expand...
Click to collapse
Only for you ???

Related

[Q]I want to completely wipe my phone. Ofc recovery must stay on my phone. s3 INT.

Hello, i have a galaxy s3 i9300.
I have rooted my phone tryd out many roms and kernels. I had siyah kernel but switched to an other kernel, i had dual boot with the siyah kernel. And the 2nd rom files from dual boot are still on the phone, i tryd formating system etc, wiping caches, wiping dalvik, factory reset.
I just want complete wipe, all personal stuff can wipe to music etc. IDC just that my phone is like brand new and i can start over.
Can you help me guys?
Simple, format external sdcard and internal sdcard, format system partition in recovery, wipe cache and data (factory reset ) .
What I am talking about is formatting in recovery, after you formatted 2 sdcards, system, data and cache.
You now can:
1. Pull out external sdcard, insert it into card reader or other external sdcard capable devices, copy stock ROM , flash it, done
2. Simply use sideload in recovery to flash new stock ROM.
3. Odin, I don't have explain any further, do I?
Sent from my GT-I9300 using xda premium
I'm trying to do the same thing. I'm currently running on Cyanogenmod 10.1 NIGHTLY Build and want to revert back to Stock ROM in order to return my phone for technical audio jack problems. Basically I don't want to trigger the flash counter, does the sideloader option do that?
Sent from my SGH-T999 using Tapatalk 2
JohnDidThat said:
I'm trying to do the same thing. I'm currently running on Cyanogenmod 10.1 NIGHTLY Build and want to revert back to Stock ROM in order to return my phone for technical audio jack problems. Basically I don't want to trigger the flash counter, does the sideloader option do that?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Count is only for Odin, not recovery.
So do what I said and avoid Odin way, or use Mobile Odin which doesn't increase count
Sideload just as normal as you use recovery to install, except the zip file isn't stored in your sdcard but be pushed from computer by using adb command
Sent from my GT-I9300 using xda premium
My external sd card doesnt need a wipe. I also dont need the stock rom i just want my device clean. There is 9 gb in the path "0". So is it possible to not wipe my extern sd card and put rom in it what i can install after super wipe?.
Can it be done without odin to erase all my date without erasing cwm recovery and such away? With the steps you said i needed to do.
Im scared of odin btw. I only did it once and thats when i rooted my phone. I can format my sd card in win 7 so.
Sorry a bit nooby.

[Q] moving between roms

hello
well I rooted my galaxy s3 and have an aokp rom
Lets say I ll want to move to a different rom not from aokp will I have to do a full wipe meaning in cmw factory reset ? will it erase any trace of the old rom ?
does factory reset delete the sd card if so I ll just put the rom at the ext card
highwar said:
hello
well I rooted my galaxy s3 and have an aokp rom
Lets say I ll want to move to a different rom not from aokp will I have to do a full wipe meaning in cmw factory reset ? will it erase any trace of the old rom ?
does factory reset delete the sd card if so I ll just put the rom at the ext card
Click to expand...
Click to collapse
Usually when moving from one rom type (e.g. aokp) to another (e.g. Samsung TW) you always should do a factory wipe, which, and please correct me if I am wrong, also deletes your internal SD.
On my side, I always do a mega wipe moving between ROMs as it gives me a 100% clean slate and my backups (Titanium) are on the external SD anyway.
Its always best to do l full wipe especially coming from a different rom. The sd card will not be deleted unless you tell it to be deleted.
You could try to flash it over your other rom and see if it causes issues but as said its always best to full wipe. You will lose all your apps in a full wipe
tmobile s3 running wicked. I still use a t9 text app so excuse the errors
ok thanks
for now I wont move between roms but I always have a stable rom of two kinds so if something gets wrong and I am on the roads I could flash a stable rom

Problems on I9300 after updating to CM SNAPSHOT M4

Hey guys,
I have been having problems with some CyanogenMod roms lately. My I9300 was working perfectly using one of the nightly CM 11 ROM's released in early March, until I installed the latest M Snapshot. From there on in my phone has gone insane.
From time to time, during the day the phone gets blocked without any apparent reason. My first thought was that has something to do with the RAM, maybe its getting low somehow, but no, that wasn't the case. Most of the time I have at least 160-180 free ram, usually more than that.
Anyway, then I thought maybe the problem was the installed ROM, so I did a re-install but still,with no effect. Then I downloaded 17th of march nightly ROM, wiped clean the cache and reset the phone. Still with no effect.
My next solution is: Download the newest nightly, currently 18th of March, install the latest Clockworkmod Recovery, which is 6.0.4.6., reset and wipe the phone again (backing of course) and install the latest ROM. What do you guys think?
Also, does anyone else has this problem after installing the latest M-Snapshot from the CM download page.
I would much appreciate your help. Thanks a lot.
Gent
Yes. You definitely should install the latest CWM. And when you wipe, make sure that you (from the CWM menu ofc):
wipe data/factory reset
mounts and storage -> fromat system
mounts and storage -> format /data and /data/media (/sdcard)
advanced -> wipe dalvik cache
then flash the rom etc
If you didn't do this in the first place when you tried flashing the ROMs the flashes were dirty and that may be the reason why they didn't work.
Doing the above will give you a real fresh start with your ROM and problems should not appear.
So, I don't think the problem is in any of the ROMs you tried.. I'm just guessing, so correct me if you did all the above
I have been doing just fine with CM 11 M3 and M4 builds and now I'm on the latest nightly and everything is working perfectly! :highfive:
Hey Man,
I did that, but now the problem is that I cannot install the rom because it has wiped all the data that were there. Now I cannot transfer the rom into the phone. I transfered it into the external sd card but it does not let me to install it, it shows an error.
What to do now???
henkkaize said:
Yes. You definitely should install the latest CWM. And when you wipe, make sure that you (from the CWM menu ofc):
wipe data/factory reset
mounts and storage -> fromat system
mounts and storage -> format /data and /data/media (/sdcard)
advanced -> wipe dalvik cache
then flash the rom etc
If you didn't do this in the first place when you tried flashing the ROMs the flashes were dirty and that may be the reason why they didn't work.
Doing the above will give you a real fresh start with your ROM and problems should not appear.
So, I don't think the problem is in any of the ROMs you tried.. I'm just guessing, so correct me if you did all the above
I have been doing just fine with CM 11 M3 and M4 builds and now I'm on the latest nightly and everything is working perfectly! :highfive:
Click to expand...
Click to collapse
gent.b said:
Hey Man,
I did that, but now the problem is that I cannot install the rom because it has wiped all the data that were there. Now I cannot transfer the rom into the phone. I transfered it into the external sd card but it does not let me to install it, it shows an error.
What to do now???
Click to expand...
Click to collapse
You should always put roms on ext sd card before you are ready to flash not internal for situations like this! Flash back to stock with odin and start again.
Connect the phone via USB cable, go to recovery, Mounts and Storage, and then click Mount USB Storage. Then, transfer the ROM. Have you thought about having the Cm instaler?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Andr3y29 said:
Connect the phone via USB cable, go to recovery, Mounts and Storage, and then click Mount USB Storage. Then, transfer the ROM. Have you thought about having the Cm instaler?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I think my reply might have confused you..I was suggesting that he should have transferred his rom to ext sd card before he started to flash and wipe system..It looks like he wiped the system in recovery and could not transfer rom to internal sd so he managed to transfer the rom to external sd where it would not let him install please correct me if I am wrong ..
I know there are other options he can try but in this situation I recommend flash to stock to give him a clean system and minimize any errors he might have and then he can try again the correct way.
tallman43 said:
You should always put roms on ext sd card before you are ready to flash not internal for situations like this! Flash back to stock with odin and start again.
Click to expand...
Click to collapse
Unfortunately that was my only choice. I did it, and I succeeded...
tallman43 said:
Sorry I think my reply might have confused you..I was suggesting that he should have transferred his rom to ext sd card before he started to flash and wipe system..It looks like he wiped the system in recovery and could not transfer rom to internal sd so he managed to transfer the rom to external sd where it would not let him install please correct me if I am wrong ..
I know there are other options he can try but in this situation I recommend flash to stock to give him a clean system and minimize any errors he might have and then he can try again the correct way.
Click to expand...
Click to collapse
That was the exact situation I was in. I tried mounting the ext/sdcard and transferred the rom to it, but it didn't let me to install it, it said installation failed.

[Q] Wiping to install Rom?

Hello everyone,
So im not new to teh whole custom rom scene and whatnot, I had a galaxy Nexus which i raped with ROM Installs .
Anyway I got a new phone, and wanted to install a custom rom on it
However It is required to wipe the phone before installing and the thing is I have alot of valuable pictures on this phone. Now I know i could back them up to the computer, however when I switched from the nexus to the new phone, i backed them up to the computer and then put them on the new phone, some pictures the order got messed up. Like the first picture wasn't the firs tpicture anymore etc..
Also on my Galaxy nexus when I wiped it, my images did not get deleted, they were still there, does wiping not delete all of this?
(Im talking about wiping from Recovery
Bump
BUMP
Ridwan Sameer said:
BUMP
Click to expand...
Click to collapse
Most custom recoveries are made to not wipe /data/media (also known as internal storage or what the phone recognizes as /sdcard) unless told to when you go to wipe to install a rom. This can vary by phone/recovery/rom/etc but as a general rule, that's how it works.
es0tericcha0s said:
Most custom recoveries are made to not wipe /data/media (also known as internal storage or what the phone recognizes as /sdcard) unless told to when you go to wipe to install a rom. This can vary by phone/recovery/rom/etc but as a general rule, that's how it works.
Click to expand...
Click to collapse
Im currently not running on any Custom Recovery
Im using custom firmware Galaxy S4 Mini GT I9195
What are my options to Install Cyanogen mod WITHOUT loosing Pictures? I dont mind loosing apps , app data etc..And I can backup Messages some other way
Ridwan Sameer said:
Im currently not running on any Custom Recovery
Im using custom firmware Galaxy S4 Mini GT I9195
What are my options to Install Cyanogen mod WITHOUT loosing Pictures? I dont mind loosing apps , app data etc..And I can backup Messages some other way
Click to expand...
Click to collapse
Well you can't install CM without a custom recovery. Just make sure it isn't set to wipe the internal storage and all will be fine. You might have to move your stuff into the /sdcard/0 folder after CM is installed if it doesn't do it automatically and you don't see the stuff from internal storage after you get into CM.
es0tericcha0s said:
Well you can't install CM without a custom recovery. Just make sure it isn't set to wipe the internal storage and all will be fine. You might have to move your stuff into the /sdcard/0 folder after CM is installed if it doesn't do it automatically and you don't see the stuff from internal storage after you get into CM.
Click to expand...
Click to collapse
So Install Custom recovery, Set it not to wipe internal storage, And tehn wipe and install rom?
Ridwan Sameer said:
So Install Custom recovery, Set it not to wipe internal storage, And tehn wipe and install rom?
Click to expand...
Click to collapse
Bumpity bump

[Q] "Unfortunately, (apps) has stopped..."

The problem is, its not one or specific app that crash, its almost all.. the error massage overlapping the other error massage! its almost impossible for me to navigate through my phone. Each time I click "OK", other errors pop up.. usually its not happen to the apps I install, the error happen on android service app.. like phone, contact, calendar, google service, etc.. etc.. the only solution I did is to wipe everything (since I root it). I have to wipe everything for it to work.. if I wipe internal only, and install other custom rom.. its not working.. I have to wipe everything.
my question is how to fix this "Unfortunately, (apps) has stopped..." error without wiping everything???
If you are using custom ROM then download exactly the SAME version of the ROM you currently have and reflash it without doing factory reset (make sure you wipe out dalvik and regular cache after flashing). Also this sounds like corrupt internal storage, best solution involves losing ALL of your data (yes, even ROM). I suggest you to do hard reset (completely format /system partition). After doing that be aware that no OS will be installed on your phone and you should flash one using recovery like you do with regular ROM installation (with cache cleaning and Gapps flashing). Your phone will work like charm again. Make sure your backup all your important stuff before doing it. Also if you use SD card I would recommend formatting it as well because it contains (probably) broken application data and obbs.
Or, try reinstalling the google services app.. If that fails reflash the rom twice via recovery. If that fails, as above, backup, reset to stock and start over.
Beamed in by telepathy.
Forcellrus said:
If you are using custom ROM then download exactly the SAME version of the ROM you currently have and reflash it without doing factory reset (make sure you wipe out dalvik and regular cache after flashing). Also this sounds like corrupt internal storage, best solution involves losing ALL of your data (yes, even ROM). I suggest you to do hard reset (completely format /system partition). After doing that be aware that no OS will be installed on your phone and you should flash one using recovery like you do with regular ROM installation (with cache cleaning and Gapps flashing). Your phone will work like charm again. Make sure your backup all your important stuff before doing it. Also if you use SD card I would recommend formatting it as well because it contains (probably) broken application data and obbs.
Click to expand...
Click to collapse
Thanks for the reply.. :good::good: When you say "corrupt internal storage".. do you mean hardware? so, in the future it might happen again? what trigger this error? its happen so sudden.. haha.. sorry for a lot of question.. this error happen to me twice.. on difference phone! one Samsung S3.. the other one Asus Zenfone 5 LTE.. luckly for S3, I manage to restore it, but for asus..... well.... Damn you asus!!
shivadow said:
Or, try reinstalling the google services app.. If that fails reflash the rom twice via recovery. If that fails, as above, backup, reset to stock and start over.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thanks for the reply!! :good::good: I will try to reflash gapp if that happen again..
KhairJhonny said:
Thanks for the reply.. :good::good: When you say "corrupt internal storage".. do you mean hardware? so, in the future it might happen again? what trigger this error? its happen so sudden.. haha.. sorry for a lot of question.. this error happen to me twice.. on difference phone! one Samsung S3.. the other one Asus Zenfone 5 LTE.. luckly for S3, I manage to restore it, but for asus..... well.... Damn you asus!!
Click to expand...
Click to collapse
By Corrupt Internal Storage I mean software way, it gets formatted to RAW instead of exFAT or NTFS or whatever format it is by default. This was happening quite a lot with my SD card, Android system was reading/writing something on it in the background, I was playing some game and suddendly phone restarted because of Low memory killer. And what happened is that SD card operation suddendly stopped which most probably made it virtually corrupt (formatted from NTFS to RAW) and made it unable to read on phone and PC. Only solution was to format is using Windows' Disk Managment tool and format it freshly. Same thing rarely happens to internal storage which means your ROM won't boot and your phone will be booted into recovery or you will get bootloop. That being said maybe some of your segments from OS are virtually damaged which prevents apps from functioning properly making them crash. Another reason could be "optimizing" apps such as Greenify, Battery Boosters etc which can crash other apps as well.

Categories

Resources