Related
Sorry guys, I thought I could handle this, but I just tried to update to Hakuro's new rom, but I think my problem is something else. Let me explain.
I used to have H's Cupcake build and I just wiped, installed the radio, installed the SPL and installed the new firmware. I used a Linux machine for format my 4gb memory card with 3gb fat and 1gb ext2 and I extracted the zip file into its own folder.
I have tried doing an "adb shell ls /system" and it shows there are no files there. Have I lost root access? Is that what would make that folder vanish for me?
if you're booted into recovery, /system isn't mounted.
is that the case?
Ah, yes. I guess I was getting a little over worried about nothing. So at least I don't have to worry about 'that' being the problem of why my phone keeps rebooting.
I can wait until the main thread gets unlocked... Unless anyone wants to share some ideas?
madelk said:
Ah, yes. I guess I was getting a little over worried about nothing. So at least I don't have to worry about 'that' being the problem of why my phone keeps rebooting.
I can wait until the main thread gets unlocked... Unless anyone wants to share some ideas?
Click to expand...
Click to collapse
if you didn't wipe, i'd def try that
I did. I expect that doing "adb shell ls /sdcard" should work in recovery, correct?
madelk said:
I did. I expect that doing "adb shell ls /sdcard" should work in recovery, correct?
Click to expand...
Click to collapse
/sdcard isn't mounted in recovery, either.
if you do:
adb shell
...then...
mount /sdcard
you can read / write to the card just fine
Ahh, I thought a messed up the Apps-SD step. I'm getting a message saying:
"mounting /dev/block/mmcblk0p1 on /sdcard failed: Invalid argument"
Hmm, my Linux machine sees the partitions just fine.
/dev/sdb2 fat32 2.74GiB
/dev/sdb1 ext2 1.00GiB
Both appear to be primary partitions.
I tried doing a "busybox df -h" in ADB and it didn't list my SD card.
Sorry if this has been asked before...
I'm on stock 2.1 rooted. In order for me to access /system or /data, I must mount it manually via recovery. Is there any way that they may be accessed (from the phone preferably, but at the very least from the computer) while the phone is booted?
Thanks In Advance
in short, no. Phones that can do that are S=OFF, whereas the Aria is S=ON. You have to be in Recovery to mess with the /system or /data stuff
It's helpful to know what its called.
So, would AlphaRev 2 work?
Hmmm, I installed Darktremor Apps2SD 2.7 Update 3r1 and now i can see /system in astro
NuNinja said:
Sorry if this has been asked before...
I'm on stock 2.1 rooted. In order for me to access /system or /data, I must mount it manually via recovery. Is there any way that they may be accessed (from the phone preferably, but at the very least from the computer) while the phone is booted?
Thanks In Advance
Click to expand...
Click to collapse
NuNinja said:
Hmmm, I installed Darktremor Apps2SD 2.7 Update 3r1 and now i can see /system in astro
Click to expand...
Click to collapse
When the phone is booted normal, the /system and /data partitions are mounted in readonly mode, that is why you see them in Astro. In order to write or modify these partitions, you need to have the phone in recovery mode and mounted as read/write.
I should have considered that.
It just seemed odd because I couldn't see it before and still cannot see /data...
NuNinja said:
I should have considered that.
It just seemed odd because I couldn't see it before and still cannot see /data...
Click to expand...
Click to collapse
When I fire up Astro, I can select the Up button and that will take me to / on the phone and I can see /acct, /cache, /data, etc. I have to scroll the screen, but all of the directories show up.
But if you open them, are they empty?
NuNinja said:
But if you open them, are they empty?
Click to expand...
Click to collapse
Astro doesn't run as a rooted application, therefore it can't see the contents of readonly folders. If you open up a terminal emulator window and type 'su' at the $ prompt to gain root access, then you could do a 'ls /data' and see the contents.
so.. internal storage on my a501 is mounted as /sdcard
i ve just installed a new rom after full format and i cant use the /sdcard directory anymore.
all files and folders are there, but their attributes have been reset. folders show up as 0kb files and i cant access nor delete them.
i tried every format option available in cwm. i tried deleting them in windows after connecting the tablet with usb, nothing works
/sdcard mounts /dev/fuse. this is confusing. its as if i m stuck with corrupted inodes and no data.
what can i do to recover a functional internal storage ? :'(
mr.bryce said:
so.. internal storage on my a501 is mounted as /sdcard
i ve just installed a new rom after full format and i cant use the /sdcard directory anymore.
all files and folders are there, but their attributes have been reset. folders show up as 0kb files and i cant access nor delete them.
i tried every format option available in cwm. i tried deleting them in windows after connecting the tablet with usb, nothing works
/sdcard mounts /dev/fuse. this is confusing. its as if i m stuck with corrupted inodes and no data.
what can i do to recover a functional internal storage ? :'(
Click to expand...
Click to collapse
Part of your internal storage is recognized as SD Card. Your SD should be recognized as External SD. This you should already know.
Now, to totally clear your internal memory, boot back to CWM
If you use the most recent CWM;
If you really want to remove EVERYTHING in Internal Memory, at this point, go to Backup and Restore. Select "Toggle backup and restore of internal storage (/data/media). Enable this setting by selecting it. By default, it is disabled. Then proceed to the formatting steps. This will format the Entire Internal Memory when you proceed. (if you use an older version of CWM, you should be able to find this option)
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
This should get you going with the format, then reflash your rom.
Also, which rom were you trying to flash?
Thanks
i was flashing Alexandra precisely ^^;
edit: ok nvm this is the link i was missing to update cwm :
http://forum.xda-developers.com/showthread.php?t=1426617
ongoing
mr.bryce said:
Thanks
i was flashing Alexandra precisely ^^;
i dont have this option under backup and restore.
i m on cwm 5.0 from thor 1.3.4
i tried installing rom manager, but because my default download folder /sdcard is corrupt, it doesnt seem to install anything (says download failed check connection)
i m searching for an update.zip of 5.0.2.7 for manual update but i m not sure if its ok to use any on the A500, is it device specific ?
Click to expand...
Click to collapse
You should have the option to do a complete format in your CWM (toggle option) Even on the older version.
I'll suspect the download may have gotten corrupted somehow.
Go to Tegraowners, and get the update zip for the recovery. Just copy to SD, boot and flash it. Simple process.
DO NOT USE ROM MANAGER!!!!! If you do, I can't help you.
---------- Post added at 09:21 PM ---------- Previous post was at 09:09 PM ----------
mr.bryce said:
Thanks
i was flashing Alexandra precisely ^^;
edit: ok nvm this is the link i was missing to update cwm :
http://forum.xda-developers.com/showthread.php?t=1426617
ongoing
Click to expand...
Click to collapse
Well, you can do it that way, but it's the same recovery I think you have now.
(it's a long story behind that)
I would still suggest you just copy the update.zip to your sd from Thor (ver 1.6), and flash it.
yep... so i did this... and still got corrupted data :'(
here s what i did step by step :
- manual update and reboot to thor recovery 1.6rev2
- toggle internal storage
(i read "backup and restore /data/media: Enabled)
- went to mounts and storage and formatted system, cache and flexrom
- went to wipe menu and wiped cache and dalvik-cache
then install zip from sdcard and alexandra rev4
Moscow Desire said:
Select "Toggle backup and restore of internal storage (/data/media). Enable this setting by selecting it. By default, it is disabled. Then proceed to the formatting steps. This will format the Entire Internal Memory when you proceed. (if you use an older version of CWM, you should be able to find this option)
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
This should get you going with the format, then reflash your rom.
Click to expand...
Click to collapse
it doesnt work --; i still cant use any file/folder listed under /sdcard
You formatted all 4, including Flexrom, correct?
Because I've never heard of this happening before.
i also tried the following :
toggle internal storage : enabled
use internal storage as /sdcard
format /sdcard
i read E:cant format_volume "/sdcard"Error formatting /sdcard!
mr.bryce said:
i also tried the following :
toggle internal storage : enabled
use internal storage as /sdcard
format /sdcard
i read E:cant format_volume "/sdcard"Error formatting /sdcard!
Click to expand...
Click to collapse
Hang on, asking for advice. I'm lost with this one right now.
---------- Post added at 10:02 PM ---------- Previous post was at 09:58 PM ----------
What's strange, is that the rom flashed normally? Up and running? Because I am puzzled to say the least. You may want to try flashing another rom. Basically, the rom should not have messed with the stuff you had installed there. It usually doesn't. Try flashing another rom, and see what happens. Try Harkon. It's a stock based like mine, with only a kernel to kick it.
Also, which rom did you have before this?
Moscow Desire said:
You formatted all 4, including Flexrom, correct?
Because I've never heard of this happening before.
Click to expand...
Click to collapse
only system, cache and flexrom in mounts and storage,
then cache and dalvik cache in wipe menu
so i tried again with all 4, and it gives me an error on format /data
i read "Formatting /data..."
"Skipping erase of /data/media."
"Done."
then i wiped all 3 in wipe menu (including factory reset)
and did all this again without switching to internal storage because i m clueless at this point.
flashed back the rom.
i m stuck --;
is there a way to mount /sdcard from another location ? or format /dev/fuse from a terminal ?
i tried with another rom i dont think alexandra had anything to do with it.
ok nvm i messed up
i did a chmod on /data earlier in the afternoon kind of retarded i know.
i chmod it to 777 now and got my files back.
sorry i wasted our time --; and thanks for helping
The formats should have been all 4; (with toggle enabled)
System
Data
Cache
Flexrom
According to all reason, this should have formatted your complete internal memory.
Still waiting to hear word, but I might not get anything tonight. We're in a way different time zone, and we have day jobs.
I would hate to say return to a stock status (run the stock acer rom ), as I would like to try and work this out. The problem, is with all the flashes, and all the downloads, this is the first I heard of this issue. Sort of makes it "my turf".
---------- Post added at 10:36 PM ---------- Previous post was at 10:25 PM ----------
mr.bryce said:
ok nvm i messed up
i did a chmod on /data earlier in the afternoon kind of retarded i know.
i chmod it to 777 now and got my files back.
sorry i wasted our time --; and thanks for helping
Click to expand...
Click to collapse
Dude, I am just glad it's working now
And damn glad it wasn't something I did.
Most Rom Mod's will tell you, when something happens with their installs, we take it personally, and like to see things working.
Anyhow, it's my turf, as it is with most Mod's.
Glad it's working now, and in the future, LEAVE SH_T ALONE!!!
I'm an old guy, and my heart can't take it
Be good, Any issue, drop in my thread.
mr.bryce said:
ok nvm i messed up
i did a chmod on /data earlier in the afternoon kind of retarded i know.
i chmod it to 777 now and got my files back.
sorry i wasted our time --; and thanks for helping
Click to expand...
Click to collapse
Hi,
How could you make a chmod on files?
I have a strange problem similar to you and suspect the same issue.
Thanks
gerardpuducul said:
Hi,
How could you make a chmod on files?
I have a strange problem similar to you and suspect the same issue.
Thanks
Click to expand...
Click to collapse
adb shell chmod 777 [path][filename]
Example;
adb shell chmod 777 /system/xbin/su
MD
Stuck on Skipping erase of /data/media
mr.bryce said:
ok nvm i messed up
i did a chmod on /data earlier in the afternoon kind of retarded i know.
i chmod it to 777 now and got my files back.
sorry i wasted our time --; and thanks for helping
Click to expand...
Click to collapse
Hey, I did everything that was going on on this thread and I had no luck. Can you explain what is a chmod or send me a link of what it is? I am stock at the recovery which the 321 euu installation provides.
Can't format on custom 321 EUU installation recovery, nor 1.7.3, nor 1.8.1 Thor version. I don't want to imagine that data partition is bad as hardware.
Thanks in advance
gatito89 said:
Can you explain what is a chmod or send me a link of what it is?
Click to expand...
Click to collapse
Moscow Desire said:
adb shell chmod 777 /system/xbin/su
Click to expand...
Click to collapse
i used android terminal at the time, in which case you just have to type chmod 777 /system/xbin/ORWHATEVER
https://en.wikipedia.org/wiki/Chmod
Note: This guide is geared toward the Samsung Captivate. If you have a different device, try your device's forum, or search this thread.
Are you using ICS and pulled your phone out of your pocket only to find that it had this screen, saying "Encryption unsuccessful" and your only option a button that said "Reset Phone"? Don't press it! Try rebooting a few times with your external sdcard out first. Sometimes that will fix the issue. If not, take a deep breath and follow the guide below to get your phone usable again:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Too late? Already hit the button? Then you know this screen:
Here's the bad news:
Your partitions for /data and /sdcard are no longer accessible. Latest news points to a bug in the firmware for the memory card in your phone. ICS uses a new function that doesn't work correctly with the affected phones.
Good news:
I found a *workaround* to get my phone to at least work again. Note: You will need to perform steps 9-11 every time you flash a ROM or ROM update, because flashing overwrites the vold.fstab file.
Here were my steps to get your phone working again:
Realize that you may have just lost whatever was on your sdcard and it's your own fault. For me, this was acceptance that *I* installed ICS on my phone and now CWM backups, photos, and more were gone. Once your realization has set in, move forward.
Acquire an micro SD card that you will put into your phone. This will contain your new /data partition as well as your new /sdcard partition. I recommend at least 8GB. If you already have a card, backup whatever is currently on your micro SD card - you *WILL LOSE* everything on this card in the next few steps.
Boot into clockwork mod, using either 'adb reboot recovery', or some other combination of buttons.
Partition your mircosd card through CWM. This will be 'advanced' then 'Partition SD Card'. The first size you choose will be the size of your /data partition. I have a 16GB card and chose 2GB for /data. This will leave me with (16GB-2GB) 14GB for /sdcard. You can choose a different size if you like, depending on how big you want your internal data partition to be. Choose 0M for swap. This process will take a few minutes, so keep waiting, you impatient jerk.
Download the latest build of ICS for your phone and put it on your micro SD card. (You can mount it to your computer at this point in CWM with 'mounts and storage' 'Mount USB storage')
Create a full backup. Just in case. Put it on a computer, dropbox, whatever. Your phone isn't a safe place for backups.
Wipe user data, cache, & system. Now install the ICS package you just put on your card and reboot.
The first boot will take a while, as all first boots do, but after a while you should be back in ICS. Exhale (If you're not exhaling at this point, post something in this thread and I or someone else will help get you running)
Check Settings > Storage and see if your new /sdcard partition (For me it was about 14GB) shows up as 'USB Storage' or 'SD Card' If it's USB storage, then your micro sd mounted to /sdcard successfully and you're done. You should be able to take a picture and have it save. If not...
Edit etc/vold.fstab with whatever you use personally (root explorer for me) and swap paths for /emmc and /sdcard (the part that starts with /devices/platform...). Someone more intelligent than me can probably make this a CWM zip. This step is telling ICS to swap your /sdcard (broken internal sdcard) and your /emmc (working external sdcard). It will probably look like this when you're done:
Code:
# internal sdcard that is no longer working
dev_mount emmc /mnt/emmc 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
# external sdcard
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
Reboot with your new vold.fstab and check your storage amount in ICS and test your camera (easy test to see if Android can write to the sdcard). Hopefully now this is working for you.
Let me know if you have any questions or (hopefully not) problems!
Notes for myself and devs:
ICS is a lot pickier about mounting filesystems, and if it can't mount /data correctly, it assumes it is encrypted. It really isn't, firing off https://source.android.com/tech/encryption/android_crypto_implementation.html an misleading encryption message.
In ICS and in CWM, when I look at /dev/block/platform/ I only see s3c-sdhci.2 and s5pc110-onenand. The s3c-sdhci.0 block is missing completely. I'm not sure how to even touch the /data or /sdcard filesystem at *ALL*
Oh well.
the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?
edecan said:
the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?
Click to expand...
Click to collapse
#1 dont quote a post that is un-related (especially huge 1st posts)
#2 dont ask unrelated questions in a thread
#3 dont ask questions PERIOD in development threads.
edecan said:
the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?
Click to expand...
Click to collapse
This is happening because your phone is still trying to use your internal sdcard, but it isn't accessible. You will need to trick your phone to use the external sdcard as if it was the internal.
You will need ADB working and your phone in USB Debugging mode (Options>Development) for this part:
Code:
adb pull /system/etc/vold.fstab
This will put your vold.fstab file in the directory you have command prompt running. Open this file and swap the references of 'mmc2' with 'mmc0' and 's3c-sdhci.2' with 's3c-sdhci.0'. It should look something like the example in step 10 of post #1 when you're done. Save and close the file.
Now use these commands:
Code:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
Code:
adb push vold.fstab /emmc/vold.fstab
adb shell
su
mount -o remount rw /system
cp /emmc/vold.fstab /system/etc/vold.fstab
chmod 644 /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
adb reboot
TRusselo said:
#1 dont quote a post that is un-related (especially huge 1st posts)
#2 dont ask unrelated questions in a thread
#3 dont ask questions PERIOD in development threads.
Click to expand...
Click to collapse
Actually, the question he asked is extremely relevant to my post, specifically step 9. I agree with you #1, though.
cgugino said:
This is happening because your phone is still trying to use your internal sdcard, but it isn't accessible. You will need to trick your phone to use the external sdcard as if it was the internal.
You will need ADB working and your phone in USB Debugging mode (Options>Development) for this part:
Code:
adb pull /system/etc/vold.fstab
This will put your vold.fstab file in the directory you have command prompt running. Open this file and swap the references of 'mmc2' with 'mmc0' and 's3c-sdhci.2' with 's3c-sdhci.0'. It should look something like the example in step 10 of post #1 when you're done. Save and close the file.
Now use these commands:
Code:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
Code:
adb push vold.fstab /emmc/vold.fstab
adb shell
su
mount -o remount rw /system
cp /emmc/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
adb reboot
Click to expand...
Click to collapse
Thank you! Everything is working now thank you.
ICS currently using 4.0.3 version of the Onecosmic's ROM version 2.1.
I want to use version 3.1 or CM9 KANG, this time when the boot screen remains. Have his solution
when i follow the steps to pull the file through adb, i get "remote object '/system/etc/void.fstab' does not exist"
phone boots, but when changing via root explorer, the files revert back when I reboot
kwhee07 said:
when i follow the steps to pull the file through adb, i get "remote object '/system/etc/void.fstab' does not exist"
phone boots, but when changing via root explorer, the files revert back when I reboot
Click to expand...
Click to collapse
Make sure you're using vold and not void, as in VOLume Daemon.
OR
Make sure you're remounting the file system with Root Explorer (press the button to change R/O to R/W)
roms kernel glitch does not work.
Boot screen does not turn on the device remains.
edecan said:
roms kernel glitch does not work.
Boot screen does not turn on the device remains.
Click to expand...
Click to collapse
What ROM are you on?
Did you flash a ROM update? If so, this overwrites the vold.fstab and you'll have to fix it. If you're on CM9, try reinstalling the latest update package, then perform steps 9 and on from the first post.
cgugino: i tried again via root explorer(both of the things I did wrong, you called out perfectly, thanks for keeping me in check!), but now the phone wont leave boot animation. I guess I'll flash again, and try to edit the document on my computer via adb
kwhee07 said:
cgugino: i tried again via root explorer(both of the things I did wrong, you called out perfectly, thanks for keeping me in check!), but now the phone wont leave boot animation. I guess I'll flash again, and try to edit the document on my computer via adb
Click to expand...
Click to collapse
Let me know if it doesn't work. Did you partition your external sd card?
no, have not understood me.
Just set up onescomics rom. Install another rom.
Thanx!! I was starting to think i was the only person in the world i have this issue.
In my case, I found several weeks ago my first "encrypted unsuccessful" screen and of course, I push de button. However, I didnt loose all the information in the internal sd card, only system one. I did all wipes and factory reset, but issue continued there. I fixed it connecting the phone to PC during boot.
Nowadays, the problem happens always the phone boots and conecting to the PC is enough to fix it and restart normally.
I understand your guide is in the case you have lost TOTALLY your access to internal Sd Card, isnt it?
However, this is not a permanent solution.
edecan said:
no, have not understood me.
Just set up onescomics rom. Install another rom.
Click to expand...
Click to collapse
The only way I know how to make this work is with the CM9 ROM -- I don't know what onescomics is and if you can't get your phone working, I would recommend staying on ICS.
iperezru said:
Thanx!! I was starting to think i was the only person in the world i have this issue.
In my case, I found several weeks ago my first "encrypted unsuccessful" screen and of course, I push de button. However, I didnt loose all the information in the internal sd card, only system one. I did all wipes and factory reset, but issue continued there. I fixed it connecting the phone to PC during boot.
Nowadays, the problem happens always the phone boots and conecting to the PC is enough to fix it and restart normally.
I understand your guide is in the case you have lost TOTALLY your access to internal Sd Card, isnt it?
However, this is not a permanent solution.
Click to expand...
Click to collapse
That is the case for me where the internal sdcard and data partition is totally lost.
I cannot say for sure how the guide would affect you if you followed it. If CWM thinks that your partitioned external sdcard has the /data partition on it (you could use the mount command and see), when you install ICS, it would install to your actual external sdcard. You may have to edit the vold.fstab in the installer zip file before you install, so that on the first boot, the phone won't try to boot to your internal partitions. Honestly, if you're still under warranty, I'd just flash to stock and try and exchange it.
I know that the 'Encryption unsuccessful' message is triggered because the phone has trouble mounting the /sdcard partition, and with ICS, it assumes that the partition is encrypted. It may be that your partition is taking too long to load, or that it is having issues reading. Either way, I'd make regular backups of *everything* onto your computer, in case one day the whole thing craps out.
As for me, even after I went back to stock Eclair, up to Froyo, and up to GB, I could never get the /sdcard or /data partitions to recognize.
See the section on 'Booting an encrypted system' here for more about how ICS detects 'encrypted' filesystems: https://source.android.com/tech/encryption/android_crypto_implementation.html
cgugino said:
I found a *workaround* to get my phone to at least work again. Note: You will need to perform steps 9 and on every time you flash a ROM or ROM update, because flashing overwrites the vold.fstab file.
Click to expand...
Click to collapse
Do you mean to say that the phone will thereon permanently have to use a microSD when updating ROMs?
raz123 said:
Do you mean to say that the phone will thereon permanently have to use a microSD when updating ROMs?
Click to expand...
Click to collapse
Sadly, yes. You will have to use a microSD card for *everything.* With my phone, I basically don't have an internal SDcard anymore. Completely inaccessible.
I keep a modified vold.fstab file in my /backup folder, and whenever I update CM9, I replace the one that is included and installed in the update with my modified one. This weekend, I might make a CWM-flashable zip file that does this as a side project.
cgugino said:
Sadly, yes. You will have to use a microSD card for *everything.* With my phone, I basically don't have an internal SDcard anymore. Completely inaccessible.
I keep a modified vold.fstab file in my /backup folder, and whenever I update CM9, I replace the one that is included and installed in the update with my modified one. This weekend, I might make a CWM-flashable zip file that does this as a side project.
Click to expand...
Click to collapse
Hmm.
How strange.. Just a few hours ago, this phone was rocking under ICS and the internal SDcard was great.
EDIT: Do you think using AdamOutler's (HW) unbricking method could help?
http://forum.xda-developers.com/showthread.php?t=1242466
raz123 said:
Hmm.
How strange.. Just a few hours ago, this phone was rocking under ICS and the internal SDcard was great.
EDIT: Do you think using AdamOutler's (HW) unbricking method could help?
http://forum.xda-developers.com/showthread.php?t=1242466
Click to expand...
Click to collapse
I agree with you on the strangeness! I wish I could offer a solution to get your internal sdcard files back, but there doesn't seem to be one at the moment. The other interesting thing is that the encryption guide for 3.0 says that encryption isn't even usable with the YAFFS file system, which I believe the Captivate uses.
If your phone is under warranty...there may be another option for you. I contacted about 3 other people that had threads related to this issue and everyone that responded said that Samsung replaced the motherboard.
What's your phone build? Mine is 1012 Rev 0.4
Edit: I haven't tried Adam's unbricking mod, and don't think I will. For me, the phone is now working perfectly and has full functionality, outside of the loss of the original /data and /sdcard partitions. I'm not going to crack it open and start soldering. However, if you do try his mod, please let us know the results!
My phone was taking too long to boot up yesterday after installing latest franco kernel so I have decided to format and clean flash rastapop. After everything's up and running, I tried to access my internal storage via USB on Windows 8 but when I click into the drive it was completely empty. I checked the storage space on my phone to make sure that I didn't accidentally wiped the internal storage and it showed 5.1GB out of 12.92GB. I've also used ES File Explorer to see if I can access storage directly from the phone but it showed the same thing - completely empty. Wifi sharing didn't help either. One weird thing was that I could see the files when I booted into the recovery mode. I have tried almost everything including clean flashing the rom again. I really don't want to format my internal storage. Please help. Thanks!
Found the solution: http://forum.xda-developers.com/showpost.php?p=56782014&postcount=7
Simply just type in these in adb:
adb shell
su
restorecon -FR /data/media/0
For a permanent solution flash stock boot.img again. Otherwise you face the same problem when flashing any other custom kernel again.
brownmonkey300 said:
For a permanent solution flash stock boot.img again. Otherwise you face the same problem when flashing any other custom kernel again.
Click to expand...
Click to collapse
What? Not true
Sent from my Nexus 9 using XDA Free mobile app