Fully working Samsung Galaxy S - Using 16GB External Micro SD to run OS and function as External SD!!
Ok so to set the scene I will quickly explain the issue I had with my Samasung Galaxy S.
One day it worked....
Next day it didn't...from then on it would only boot to first screen then continually repeat this step.....
After day two of having no luck at fixing the issue I got an S3...great phone!
BUT DONT GIVE UP JUST YET! It can be fixed!!!
Overall I think I would have spent somewhere in the ballpark of about 40 hours trying to fix the Galaxy S...stubborn? Yes....and my Galaxy S was such a good phone I hated the idea of binning it.
I wont waste your time listing the hundreds of methods I tried or posts I read, but in the end all things pointed to a dead internal SD.
I should be able to run the OS off an external SD... shouldn't I? The answer is Yes!
Many hours were spent on this stage and for about a week I had a working pone with OS running on External SD, but no access to the camera or anything which required an external SD.
I now have a perfectly working phone, using a 16gb External SD to run the OS and remaining space on it recognised as the external SD.
I can't promise this will work for everyone but here is the last of WAY TO MANY methods I used which completely solved this problem for me.
Let me know if this works for you & GOOD LUCK!
Step 1:
Your phone must be rooted!
The best, easiest and only way I was able to do it is with the following guide, big thank you to the person who put it up. As my Internal SD was dead! my external SD was to be my new internal SD...so the standard add to zip method for rooting on external SD... would obviously not work for me! yes I worded that perfectly!
BIG IMPORTANT NOTE IN CAPITAL LETTERS! - Make sure you have your external SD inserted during the below process!
http://forum.xda-developers.com/show....php?t=1852546
NOW! You should have your phone booting as it used to back in the good old days! However.....some of you wont...if this is the case please follow Step 1B.
Step 1B:
If the above did not work for you then you need a way to connect your Micro SD to your PC (I did this using a USB adaptor).
1. Download and install EaseUS partition master
2. Insert Micro SD in PC
3. EaseUS partition master
4. Wipe all partitions/data.
5. Create EXT4 partition approx 2gb
6. Create FAT32 partition with remaining space.
7. Remove battery from phone
8. Insert SD, Battery back in.
9. Turn on, you should have your phone booting as it used to back in the good old days!
IF NOT THEN.....Start with Step 1B then do Step1 then if all looking as it should move to step 2. If not...sorry...I have failed you!
Step 2:
You phone should now have booted like the good old days....but if you go into SD/Storage on android OS, you will notice it does not recognise the remaining space on the External SD as an external SD...it must be very confusing for the green robot!
So next steps as follows!
1. Install script manager app and mount r/w app from Google Play (market)
2. Use mount r/w to Mount the system partition in r/w mode.
3. Browse using script manager app as root (change setting in config).
4. Go to /system/etc folder and change file permission for vold.fstab to rwxrwxrwx (This means tick all the 9 boxes on the left not the 3 on the right.....such a technical explanation)
5. Then edit the vold.fstab file as text and change the following
Change:
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.0/mmc_host/mmc0
to
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
Change:
s3c-sdhci.0
to
s3c-sdhci.2
Change:
mmc0
to
mmc2
Save the file and reboot the phone!
If all has gone well then your sdcard partition will be mounted and old faithful is ready to ride once again!
I hope this worked for you, if it didn't...gutted and I guess you have moved onto the next post...good hunting!
Please note this solution was created from a pile of posts I trawled through to get a solution. The above vold.fstab solution was taken from the following post. Unfortunately this posts overall solution didn't work for me, but I would not have been able to mount remaining External SD Space as well...you know THE EXTERNAL SD! without his post, which is the best part!
http://forum.xda-developers.com/show....php?t=1193010
I9000 Internal Stogare
dear sir,
Please Help me..
MY Galaxy s i9000, the usb storage(internal memory) 13.4 gb is write protected(i dont know how).
cant wipe, format, past on it is failed. but some files in it (1.4 gb used, free 12 gb) are ok with photos, music files also ok. but i cant delete all those files and do not exist pasted files after past.
For this, i flashed my Android with GB(2.3.4, 2.3.6), Froyo(2.2.1)(pit, pda, phone and csc) by odin several times, also tried with Heimdall method.
no result. FORCE close issues and sometime restarting my device.
can u help me how can be fixed my problem issues.
Please help me
reganstott said:
Fully working Samsung Galaxy S - Using 16GB External Micro SD to run OS and function as External SD!!
Ok so to set the scene I will quickly explain the issue I had with my Samasung Galaxy S.
One day it worked....
Next day it didn't...from then on it would only boot to first screen then continually repeat this step.....
After day two of having no luck at fixing the issue I got an S3...great phone!
BUT DONT GIVE UP JUST YET! It can be fixed!!!
Overall I think I would have spent somewhere in the ballpark of about 40 hours trying to fix the Galaxy S...stubborn? Yes....and my Galaxy S was such a good phone I hated the idea of binning it.
...
Click to expand...
Click to collapse
Hi reganstott i have similar problem but a little different. my galaxy i9000 stuck in boot loop too but the difference is that my phone do not enter into recovery mode and has boot loop even in download mod. therefore i can install no rom's. Do you know what is the exact problem of my phone? i try your solution but step 1A can't be done because my phone continue boot loop even in download mode. please help me
Related
Ok this is extremely annoying. I got the g1 and rooted with 1 click rooting cyanogen 4.0.4 rom. It was so simple and worked BTW. Later I used the hardspl so that I could do apps to sd. I have had the phone for 7 months and have used custom roms since I’ve gotten it.
Following this tutorial http://forum.xda-developers.com/showthread.php?t=535232 I tried to partition my 8g sandisk micro sd card. Now I probably destroyed my sd card (Nothing to big). And I am stuck at the g1 screen (pretty big). When ever I try to flash a different rom with a different or even the same rom I get an error acout the sd card “E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
With around 8 hours of digging around on forums I have decided that I might have to get a replacement unless someone could help me revert with access that I have to the recovery to allow my sd cards to be recognized.
Note: I didn’t install the Cyanogen ROM - Download v4.0.2 or Cyanogen Recovery 1.4 - Download as I had a better one. Hince my problem, and did use the apps2sd.apk. Things didn’t go wrong until I typed in “upgrade_fs” . After doing so my phone would not boot up after I restarted it.
Something tells me that I changed something in the phone to allow apps to sd partition 2 and I need to be changed back to the default, as I can’t even flash another rom to fix this problem. Any help would be greatly appreciated .
willl your phone boot when you remove the sdcard
My phone will not boot after removing the sd card.
One thing that I forgot to mention above is. While using the phone after my uncessful attemp to partition my sdcard, the top notification bar was displaying "The SD card is blank or using an unsupported file system." After messing with it a bit i decided to reboot but it froze. Being impatient I pulled the battery from the back of the phone.
Looks as if files are missing from the Cyanogen 4.0.4 rom. As when I type “mount sdcard” is displays “mount: mouting /dev/block/mmcblkop1 on /sdcard failed: No such file or directory” Sounds like I am missing mmcblkop1 from my phone now? Apps2sd.apk doesn’t change this file does it? I'm also wondering if you change a file to look somewhere else for the partition part of the sd card? And if so how would you tell it to look for the default?
Tried this "flash_image recovery /sdcard/update-cm-4.0.4-signed.zip" and it displayed this "usage: flash_image [-d] partition file.img" does this delete the partition of the sd card or what is this referring to?
I think you 'bricked' your sd card.
Try format it with SD Formatter.
Worked for me.
Because you did use App2SD, you have erased app data, so setting up your G1 from scratch is your best option.
Ok first of all using that guide to install apps2sd on cyanogen's rom is what messed up your phone. Cyanogen has clear warnings about this in his thread. Now that the damage is done lets fix it. Can you boot into recovery by holding home and pressing power? Is there an option to flash any zip file?
After rereading your post i see that you don't have recovery 1.4.
You need to do step 4 HERE when you're done do step 5 to install cm-recovery-1.4
After trying different things with the console as I posted above the phone allowed me to install the Cyanogen 4.0.4 from the 2gb sd card. For some reason the phone would not allow me to do this before. As it wouldn't recognize the sd card, or that it had 1 for that matter. What would cause this problem? Maybe a faulty sd card? But I swapped to the 2 gb sd card that came with the phone and tried this numerous times before. Glitch? Why work now? I'm so lost.
I'm so glad that this worked this time though..... another save for this g1. Its taken a licking and it keeps ticking. I have dropped it 14 feet from the top of a railcar. I have crippled it 3 times now as it wouldn't allow me to get past the g1 screen. A simple flash from the sd card allowed me fix that problem. I have also dropped it in water. It was submerged for around 6 seconds in a leather carrying case that clips on your belt. Fast thinking allowed me to remove it from the water, pull the back off, and pull out the battery. I allowed it to dry in the car for around 4 hours and then put it in a bag full of those "do not eat" packets that come in most shoes for 24 hrs. Thanks to Walmart for the donation. Probably the best phone that I have ever gotten.
Well looking over the history of the phone I understand now why it may have done this to me. However it shows that by being persistent you can figure out most things. I appreciate all who have made these guides that make my g1 ownership so much fun.
Now go to get that apps2sd working. Another method probably.
I did have recovery 1.4 installed at the time the g1 quit working. I never downgraded and was able to access the recovery the entire time. But I kept getting the error “E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
I did change the sd card at this point but had the same results.
As you may have noticed i didn't read Cyanogen thread discussing this.
I found the guide for apps 2 sd here: http://forum.xda-developers.com/showthread.php?t=535232 and read through it. Sounded easy enough and well tried. With failure of course.
I was under the inpression that apps2sd already is included in cyanogen 4.0.4 all i needed is to partition my sd card.
Jnewell05 said:
I did have recovery 1.4 installed at the time the g1 quit working. I never downgraded and was able to access the recovery the entire time. But I kept getting the error “E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
I did change the sd card at this point but had the same results.
As you may have noticed i didn't read Cyanogen thread discussing this.
I found the guide for apps 2 sd here: http://forum.xda-developers.com/showthread.php?t=535232 and read through it. Sounded easy enough and well tried. With failure of course.
I was under the inpression that apps2sd already is included in cyanogen 4.0.4 all i needed is to partition my sd card.
Click to expand...
Click to collapse
Unfortunately that guide is still a sticky and someone uses it at least once a week and we end up with your problem every week. ivanmmj added a warning to the guide a few mins ago. I'm glad you are working now. You are correct about apps2sd being included in cyanogen roms. In post 3 HERE I've made a script that will partition your sdcard for you.
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
I'm having the same problem How did you delete the fsck_msdos from the bin?
theinstagator said:
I'm having the same problem How did you delete the fsck_msdos from the bin?
Click to expand...
Click to collapse
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
I was having this same issue..it would typically take up to 5 minutes or more to "check for errors" after a boot.
To fix this I backed up my sdcard, reformatted, copied everything back, then reflashed. Everything was fine after that.
i have somewhat the same problem but in my case it sometimes say blank sdcard or damged sd card it read fine when plugged into an sd card reader any help
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
hmaxos said:
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
Click to expand...
Click to collapse
Well, after getting other errors such as "no enough space" from Platinum Backup (there was a space on SD Card), I had to go to Format the SD after copying everything. Then I copied back the important folder the SD. I also had to reinstall SwiftKey. Now everything is fine and no data loss.
SD card Checking for errors
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Well I will try to backup and format it.... If it works then good if not then I will have to root my LG P880 .
My Problem is "preparing external sd card checking for errors" now that error is not showing while following above steps but now when i click my memory card that is not opening and after opened my memory card my internal device memory also not opening .
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
Simple fix, Difficult decision. Remove SD Card from slot then Factory reset phone. Once it comes too just go through all steps to setting up device then reinsert the SD Card into the slot. BOOM!
thank you very very much it worked for me
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
thank you so much but it is read only please help
yeah...
supremeteam256 said:
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
Click to expand...
Click to collapse
i am having same issue i always changes roms please can you halp me..
still not working mine is lenovo K3 Note And my Phone is rooted. It is showing Preparing SD card checking for errors
Didn't work for me.
Hard reset don't work.
Delete the fsck.msdos but don't work.
The fsck.msdos file comes on every wipe back.
I think this is a cm issue.
On stock no problems with my external sd card on my HTC One M8.
I'm going crazy...
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Anitha Sivakumar said:
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Click to expand...
Click to collapse
ive deleted the fcsk file on bin
the notif "preparing sd card" was gone but another problem occured, i cant even open my storage, ext sd card and even internal card ive tried your solution, ive put my sd card on another device, i cant find any fcsk files that you mention i cant even delete any file from my card using another mobile :crying::crying::crying:
It worked.... Thanks bro..
:good:
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Bloody Brilliant. I have no idea why I could not find this solution two years ago. I have spent several hours searching for this solution, several times. In my case, I needed to remove the fsck.exfat file in the /system/bin folder.
My attention span is extremely short. I have been living with a 3 to 4-minute card scan for a 256GB microSD in my Samsung Note 3 for two and a half years. For all of the reboots I have done (which must be near a thousand, if that's not severely underestimated) I have had to deal with waiting to use my phone. I can't tell you how discouraging it has been to have such a powerful, useful device crippled by such a stupid flaw: that of checking the SD card that you rarely remove, for errors, every single time the phone is rebooted, even after graceful reboots called by the "proper" methods.
I can't tell you how many times I have rebooted my phone, only to forget the reason I rebooted it, because my phone took 4 minutes to reboot.
Productivity to the cubed-root.Pisses me off.
Someone who has more voice than me please get the Android People to change this. As of Nougat, this is still the default behavior. How can an organization be so stupid...? I have no doubt that just this flaw has sent many people to the Apple camps. Who the cuff in their right mind would want to deal with such a hassle?? Are they seriously unaware of the trend for people to actually believe that their devices, machines and technology ought to be doing things faster than previous generations?
(Please just take the following cynicism with a grain of salt. I just learned the above fix, something I really should have figured out a long time ago/kicking myself!!) :crying:
For the anally-inverted who might bring up the obvious argument that your phone will no longer be able to detect or fix corruption, all that needs to be done is the following:
1) move the fsck.exfat (or whatever the formatting) file to a different folder. In my case I moved it to the /data folder
2) use some delay scripting program that will symlink the fsck.exfat file to a tmpfs location say, 30 seconds after boot; or longer if needed. This intermediary step is necessary in order to create a temporary symlink, which will be nonexistent upon reboot.. If we didn't create a temporary symlink, the fsck.exfat command would be immediately available after each reboot (which we don't want) because symlinks are normally permanent. Therefore, this step will need to be run after every reboot (but again, time-delayed).
3) the last command is to create another symlink, linking the tmpfs fsck.exfat symlink created in the last step back to the /system/bin folder (or wherever it originally resided). So this is a symlink of another symlink. This step actually should only need to be done once, since this symlink should remain after reboot, even though it is initially broken upon reboot until the previous command recreates the intermediary symlink. It should become effective again when the previous step is run by the time-delayed scripting program.
Now your phone has the ability to check the card upon you calling the fsck.exfat routine through normal means, one of which can just be a simple unmount -> mount request from the Android system settings . Your card won't be needlessly fsck-checked to death every bloody time you reboot your phone.
(If you found this tutorial helpful and desire to quote or improve upon it, please cite/credit me for the inspiration! It came through much effort and learning!)
I have an international i9000 that seems to be pretty solidly soft-bricked. I've recently moved back to Canada from the Middle East and was trying to enable to 850 band so I could use it with Bell. I was under the impression that the Bell SGS and the international SGS were basically the same hardware so I flashed (ODIN) a PDA/PHONE/CSC designed for the i9000m. At the time I was on the teamhacksung ICS.
Now, regardless of what I do I always end up in basically the same spot. After my most recent flash through Heimdall, following the first reboot I end up in 3e recovery with the following errors...
---------
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI menu for format and reboot actions
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Data wipe failed
---------
I've been at this for 2 days and tried pretty much everything. Flashed through Odin and Heimdall as well as from recovery off an external SD. I tried 1-click de-brick. I tried to re-partition through ADB. I get various messages in ADB depending on what I'm doing. Sometimes it's I/O errors and sometimes it says "unrecognized disk label".
I can get to recovery and download so it seems like it should be solvable. My impression is that the partition table or structure on the internal SD card has been corrupted.
Sorry if there is already a thread for this with a simple answer, I've been through a ton and couldn't find anything that worked for me. Any suggestions would be appreciated. I'm not an expert in shell but I can follow instructions. Happy to try anything at this point.
Thanks
Exactly the same issue here, so I'll just wait for a solution here.
I think I saw this problems before. Have u backed up all your data? If yes then do this 3 ways below. If you haven't backed up yet, try to do Nandroid backup from recovery mode and restore it later.
Now try this:
1. On recovery mode: wipe data/factory reset, wipe cache, in advance-wipe Dalvik cache.
2. Remove your external sd card ( put it back later if everything's fine ).
3: Set the USB debugging ON, settings-applications-development.
Hope this helps. If it does, please consider 'THANKS' button
At this point it doesn't boot into Android. It was looping for a while but now the boot animation will start, then the screen will go black and the back/options LEDs at the bottom come on. Anything on the phone is long gone after multiple wipes/flashes/etc. I'm not worried about that.
I'm pretty sure it's a problem with the partition on the internal SD. Does anyone know how to reset/repair the partition table and rebuild the partitions from ADB? Why doesn't that happen automatically when I flash from Odin/Heimdall? Isn't that the point of the "partition" toggle?
Or, could I try to convert the file system as if I were moving from a stock ROM to something like CM7 (ie...RFS to EXT4)? Would that recreate the partitions and fix this?
Thanks
Have you tried to flash a stock samsung firmware for your phone (i9000) and re partition using a 512 pit file via Odin? Have a read of the following thread below to get the latest Stock firmware for (i9000).
http://forum.xda-developers.com/showthread.php?t=1102881
Yep, I've tried several of these across froyo/gingerbread and always end up with an unmountable internal SD card. Just for fun I went and picked another one basically at random (JV6 2.3.3) and it flashed as normal and dumped me at recovery with the mounting sd card/storage not prepared error.
Are there really no takers on this? I keep reading that these are un-brickable if they still start up.
This might be worth a try, failing that you might have to take the phone to a Samsung repair agent.
http://forum.xda-developers.com/showthread.php?t=984140
i read about this problem before on darkyrom i think there was a way to bypass corrupt internal sd and use external one go check there its worth a try
Fallen04 said:
This might be worth a try, failing that you might have to take the phone to a Samsung repair agent.
http://forum.xda-developers.com/showthread.php?t=984140
Click to expand...
Click to collapse
Kiaora mate, it's a good thread to try to . Just another thread I found that may help the idea as well:
http://forum.xda-developers.com/showthread.php?t=1442684&highlight=md5+sums
Hope this helps
Hi!
I had the same problem with my i9000. I have moved /data to external SD card and everything is working now (on ICS).
I have created a manual for solving this issue. Please click "helped" and/or ads, if this helped at least a bit.
www youtube com/watch?v=zdMhYYdMB08
Best regards
fteller said:
Hi!
I had the same problem with my i9000. I have moved /data to external SD card and everything is working now (on ICS).
I have created a manual for solving this issue. Please click "helped" and/or ads, if this helped at least a bit.
www youtube com/watch?v=zdMhYYdMB08
Best regards
Click to expand...
Click to collapse
I've the same problem and I've tried everything. Not I'm sure that the internal memory is broken, so I want to use the external sd as internal memory. I'm following your manual but I can't get it to work. I tell you what I've done:
1) I've formated the external sdcard with two partitions: one of 6 GB in vfat format and the other of 8GB in reiserfs. It seems to be ok.
2) I've tried to flash with odin the JVU 2.3.6 version. Here I've some questions: Shall I check re-partition? And apply the PIT file? I've tried all combinations but I still doesn't use the external memory and I get the mmcblk0p2 error...
Any help?
Here I have posted how I have solved my problem of corrupt internal memory. Look at it and I hope someone will help.
This guide install rom to SD Card, but still have question, how to repair internal memory? i`l boot`ed rom from SD Card, but cant see internal memory, use camera, etc. who need internal memory...
Maybe are any app to fix internal memory, when android boot`ed?
In most cases I have met (including Galaxy Tab P1000 and GT-i9003) with internal memory failure or corrupted memory, the only solution is to replace the chip. If you've booted your terminal and can not use the camera or see the internal storage, you have to modify the file vold.fstab according to your android version.
Hello. This is my first post, but I have been a reader for a while. I recently bought Samsung Galaxy Note. Rooted it using the ZergRush exploit and installed CriskeloROM v0.6.
It worked perfect for a week, but then something wierd happened.
On my way to work I got out of the door and opened spotify as usual, but the screen just blinked and the app didn't start. When I looked into this it seems as if the phone won't recognize the SD card.
Saying that the phone won't recognize the SD card isn't entirely true. The phone know the card is there, but it appears as full.
USB storage: Total space 11.08GB - Available space - 0.00B, not even a single byte.
When I hook the phone to a pc, I can see that I in fact have about 8GB of free space. I can also without problem browse all the files as if nothing was wrong.
The things I know I have done that might interfere with it is that the other day I was going to copy some wallpapers into my phone. To do this I was required to encrypt the disk station using BitLocker. I have also by accident disconnected my phone without dismounting.
I have done alot of searches in google and on this site, but I have yet to find someone with the exact same problem as me.
I have tried to take out the battery and leaving it out for 15 minutes.
I excuse the wall of text and my poor english.
Thank you
Dagnit said:
Hello. This is my first post, but I have been a reader for a while. I recently bought Samsung Galaxy Note. Rooted it using the ZergRush exploit and installed CriskeloROM v0.6.
It worked perfect for a week, but then something wierd happened.
On my way to work I got out of the door and opened spotify as usual, but the screen just blinked and the app didn't start. When I looked into this it seems as if the phone won't recognize the SD card.
Saying that the phone won't recognize the SD card isn't entirely true. The phone know the card is there, but it appears as full.
USB storage: Total space 11.08GB - Available space - 0.00B, not even a single byte.
When I hook the phone to a pc, I can see that I in fact have about 8GB of free space. I can also without problem browse all the files as if nothing was wrong.
The things I know I have done that might interfere with it is that the other day I was going to copy some wallpapers into my phone. To do this I was required to encrypt the disk station using BitLocker. I have also by accident disconnected my phone without dismounting.
I have done alot of searches in google and on this site, but I have yet to find someone with the exact same problem as me.
I have tried to take out the battery and leaving it out for 15 minutes.
I excuse the wall of text and my poor english.
Thank you
Click to expand...
Click to collapse
When you boot into recovery and mount internal SD is the info correct there?
Thanks for the answer!
When I boot into recovery, witch I thought was CWM but witch turns out to be HyperDroid RedPill Recovery, probably changed when I installed the ROM (?), I can choose
- Mount internal SD
Witch leads me away from the menu and into a new little menu.
"USB Mass Storage device. Leaving this menu unmount your SD card from you PC.
-Unmount
-+++++Go Back+++++
And that's it.
However when I try to actually do a recovery (the recovery file is in the internal SD) I get the message:
"HyperDroid RedPill Recovery
E: Unable to write to usm lunfile (No such file or directory)Error mounting /sdcard!
E:Can't mount /sdcard"
do you have an external sd card in the phone? some kernels seem to swap the internal and external about
No I do not. Thanks for the answers guys!
Hello,
I figure someone here might be able to help since most of where I found information regarding my issue came from this subforum. My phone is i897 (Captivate), but I think it should be similar; I posted there as well but no luck .
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2
PMrjn83 said:
Hello,
I figure someone here might be able to help since most of where I found information regarding my issue came from this subforum. My phone is i897 (Captivate), but I think it should be similar; I posted there as well but no luck .
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2
Click to expand...
Click to collapse
Have you looked over this guide ? or this ?
Höhenheim said:
Have you looked over this guide ? or this ?
Click to expand...
Click to collapse
Thanks. I'll try when I get home to my desktop. For some reason, my laptop does not recognize the phone through adb. It shows "SGH-i897" in device manager with an exclamation mark. And yes, I have tried quite a few drivers, etc... :/
I might need to try this...
http://forum.xda-developers.com/showthread.php?t=1761968
Höhenheim said:
Have you looked over this guide ? or this ?
Click to expand...
Click to collapse
I just had a chance to look at it more thoroughly. The biggest problem for me is that my phone does not have an OS, and it's on semaphore kernel where I cannot access download mode nor fastboot. I have tried to install gingerbread kernel to try to recover download mode/fastboot (speedmods), but I kept running into error 0. I have also tried to modify the su.binary, but that didn't work :/. Any idea how to start? Thanks.
PMrjn83 said:
I just had a chance to look at it more thoroughly. The biggest problem for me is that my phone does not have an OS, and it's on semaphore kernel where I cannot access download mode nor fastboot. I have tried to install gingerbread kernel to try to recover download mode/fastboot (speedmods), but I kept running into error 0. I have also tried to modify the su.binary, but that didn't work :/. Any idea how to start? Thanks.
Click to expand...
Click to collapse
Based on your earlier comments on the partitions failing to mount, you should format: system, data, datadata, cache.
gsstudios said:
Based on your earlier comments on the partitions failing to mount, you should format: system, data, datadata, cache.
Click to expand...
Click to collapse
Well, I tried. If it doesn't mount at all, how can you format?