Hello guys
(this is my first post and not that familiar with the thread, so sorry for that)
So here's the thing: I was trying to increase my system partition to install the GApps pico, then I resized the data partition at
Code:
/dev/block/mmcblk0p29
found that it couldn't merge the space I shrunk to the system partition at
Code:
/dev/block/mmcblk0p27
, then I accidentally deleted the partition using
Code:
rm /dev/block/mmcblk0p29
and now it's gone.
I have tried to use
Code:
mknod /dev/block/mmcblk0p27 b 0 27
to rebuild a block device, however nothing could detect the device including mke2fs and e2fsck. Then I'm pretty clueless about what should I do.
That's all.
Thanks.
Deleting a block dev file won't affect the actual partition. It will be recreated every time the system reboots.
You tried to create the block dev with the MAJOR number of 0? How did you know that number? Maybe you should try ls -l /dev/block/mmcblk0* first, to find out the correct MAJOR number.
If you want to edit the partition table, the gdisk/sgdisk should be the correct tool usually.
---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------
gdisk/sgdisk doesn't provide filesystem resizing function - you must do it with the corresponding filesystem utility like resize2fs, or alternatively, you must delete&recreate the entire partition.
Anyway, manually editing the partition is generally considered DANGEROUS, backup your data, rather than risk your data of permanent loss.
linuxnoobbbb said:
Deleting a block dev file won't affect the actual partition. It will be recreated every time the system reboots.
You tried to create the block dev with the MAJOR number of 0? How did you know that number? Maybe you should try ls -l /dev/block/mmcblk0* first, to find out the correct MAJOR number.
If you want to edit the partition table, the gdisk/sgdisk should be the correct tool usually.
---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------
gdisk/sgdisk doesn't provide filesystem resizing function - you must do it with the corresponding filesystem utility like resize2fs, or alternatively, you must delete&recreate the entire partition.
Anyway, manually editing the partition is generally considered DANGEROUS, backup your data, rather than risk your data of permanent loss.
Click to expand...
Click to collapse
Thanks for replying, I didn't do the rebooting after deleting that, now it's back.
And I just having literally no idea about the major number, what's that for? In my case I just found the /system is mounted on /dev/block/mmcblk0p27 so I tried to use with major number 0 and minor number 27 to create a new one.
This phone is just an old phone, have freshly installed android 9, so there's no data losses worrying, but thanks for the advise anyway.
I have used resize2fs, it'll be successful when I shrink the data partition, but it's not working when I trying to expand the system partition, and it just saying "You requested a new size of 204810 blocks" then refuse to get a bigger block amount that I set. Seemed like the data and system partition are in the different devices(but it's not apparently). And I'm stuck with it right now.
About delete and recreate the partition, I kinda didn't get it. In my understanding, the partition is in those block devices, and you can edit the partition with tools like gdisk/fdisk etc, but now I found the /system and /data these two partitions are in the different block devices, so I can't simply modify the partition, even I was trying delete the block device, it doesn't work.
nonefffds said:
Thanks for replying, I didn't do the rebooting after deleting that, now it's back.
And I just having literally no idea about the major number, what's that for? In my case I just found the /system is mounted on /dev/block/mmcblk0p27 so I tried to use with major number 0 and minor number 27 to create a new one.
This phone is just an old phone, have freshly installed android 9, so there's no data losses worrying, but thanks for the advise anyway.
I have used resize2fs, it'll be successful when I shrink the data partition, but it's not working when I trying to expand the system partition, and it just saying "You requested a new size of 204810 blocks" then refuse to get a bigger block amount that I set. Seemed like the data and system partition are in the different devices(but it's not apparently). And I'm stuck with it right now.
About delete and recreate the partition, I kinda didn't get it. In my understanding, the partition is in those block devices, and you can edit the partition with tools like gdisk/fdisk etc, but now I found the /system and /data these two partitions are in the different block devices, so I can't simply modify the partition, even I was trying delete the block device, it doesn't work.
Click to expand...
Click to collapse
The black screen is EDL mode so unless the device has a programmer to flash to it it's just a paperweight
nonefffds said:
Thanks for replying, I didn't do the rebooting after deleting that, now it's back.
And I just having literally no idea about the major number, what's that for? In my case I just found the /system is mounted on /dev/block/mmcblk0p27 so I tried to use with major number 0 and minor number 27 to create a new one.
This phone is just an old phone, have freshly installed android 9, so there's no data losses worrying, but thanks for the advise anyway.
I have used resize2fs, it'll be successful when I shrink the data partition, but it's not working when I trying to expand the system partition, and it just saying "You requested a new size of 204810 blocks" then refuse to get a bigger block amount that I set. Seemed like the data and system partition are in the different devices(but it's not apparently). And I'm stuck with it right now.
About delete and recreate the partition, I kinda didn't get it. In my understanding, the partition is in those block devices, and you can edit the partition with tools like gdisk/fdisk etc, but now I found the /system and /data these two partitions are in the different block devices, so I can't simply modify the partition, even I was trying delete the block device, it doesn't work.
Click to expand...
Click to collapse
You must specify the major number when you do mknod.
It should be "/dev/block/mmcblk0p27 is mounted on /system".
You may try this:
https://forum.xda-developers.com/android/general/mounting-internal-storage-usb-mass-t2843152
Related
Hi,
I used to know a way to dump a raw range of data (i.e. specifying start/end in hex address) from a block device which I used to do from data recovery days, but I can't remember what it is. I have been googling for about an hour and it's driving me nuts! Can anybody help?
FYI, I am trying to grab data from an unknown range of data on the nand layout for the Xperia Play but this is a general linux/busybox question. For details on what I'm doing check here.
Thanks so much in advance.
EDIT: Nevermind, I've discovered that the range I'm trying to read is a protected area. Mods please close if possible.
cat is more like a parser, dd is capable of dealing with raw data.
http://www.linuxquestions.org/questions/linux-newbie-8/learn-the-dd-command-362506/
http://linux.die.net/man/1/dd
Yeah I figured it would be done with dd, though I can't find any device that represents the "entire" mtd/nand - only mtd# for existing partitions exposed by the kernel. If i could find a "root mtd" device I could use skip and count parameters of dd to read what I want.
Regardless, I don't really need help with this specifically anymore - my problem seems to be specific to the Xperia Play. I am basically trying to resize the partitions (which I did previously on the X10) and I have exposed an unknown ~100MB+ that goes between userdata and cache, but I can't read or write to it at all no matter what I do.
I think what I'm trying to get is a protected area for DRM or something which I want to shift (so I can give space from cache to userdata). I/we need to make kernel or bootloader changes for the device.
Thanks for the help anyway.
I have a Samsung and Samsung is the probably the only one brand that adopt a different partition system for mtd; but remember that dd just copies everything, free space included, if with dd you are copying a filesystem with a total of 100MB and only 40MB are in use, you end up having a 100MB image file with dd.
Yeah I know it's a raw by-sector mirror/dump tool. Well what I did was edit the kernel to only create one entire partition taking the complete nand storage and then tried to dd from that, it works for a long time then once it hits this special "protected" area around ~800MB offset it spams a lot of "I/O Error" messages but doesn't fill these with zero's or anything (using conv=noerror), then once it passes the protected area it successfully dumps the rest (which is where the cache partition for the zeus would go).
OK, I have another question now. I found that this unknown 133MB has about 53MB of data in there, somewhere in the middle, which grabs fine. But the resulting file is not 133MB so I don't know the offset. Can I use dd or another tool to grab this partition while filling I/O errors with zero's? I have googled a lot and couldn't find anything.
Nevermind *facepalm* I use conv=noerror,sync. http://www.mkssoftware.com/docs/man1/dd.1.asp
Hi
Since ever I noticed a weird thing on XMP: /cache partition is always almost empty.
Yes, I checked many times during a long time, it's like is never used.
Code:
$ df
/cache 101.5M 1.1M 100.4M 4096
I have only an empty lost+found dir and two files under recovery dir:
Code:
# ls
-rw-r--r-- root root 105 2012-12-15 02:07 last_install
-rw-r----- root root 3214 2012-12-22 10:36 last_log
For example, in a previous phone /cache was actively used by market for downloading packages before installing them.
Here on XMP I can't upgrade also small packages (40+ megs free on /data) 'cause they're downloaded in /data and fill it before being upgraded, and /cache remains always empty.
In addition, if for some reason playstore crashes while downloading a big app (30megs+), it leaves my /data (almost)full and I must remove by hand a large temporary file from /data/system.
Well, /data is used instead of /cache, 100mb wasted in this way.
Someone else finds experiences the same behaviour?
I was thinking about a linking trick to use that space (for dalvick or swap...), but I'd prefer it would be correctly used by system.
Infos: SK17i, stock .587, root, locked BL, link2sd.
Thanks, bye.
Same in Xperia Mini
Well, this isn't nice...
some ideas
Hello! I was doing several searches and come to some results:
Note: I will not try it on my phone (Xperia Mini Pro) because I'm still an apprentice to flash and modify it, and secondly I have no resources to change my phone if something goes wrong. Finally, sorry for the grammatical errors, I do not speak English natively.
The following are links taken from different forums / blogs (neither is my property).
The general idea is the same, use parted (or any similar app) to edit the partitions inside the phone.
One of the problems that arise and I have doubts about is, what is the file system of internal partitions? ext3?. is something that I have to keep reading.
This is the first blog I found where it gives a possible procedure to follow:
http://aarondiep.blogspot.com.ar/2011/11/resize-partition-on-android.html
Here's a post where one of the users that modify his partitions and, later, returned to stock status.
http://www.droidforums.net/forum/htc-droid-eris/78650-internal-storage-partitions-screwed-up.html
Here is a guide on how you use parted (includes screenshots) BUT IT DOES WITH THE SD CARD
http://mobilecon.info/how-to-partition-sdcard-using-parted-partition.html
Finally, a tool for YAFFS2 file system:
http://forum.xda-developers.com/showthread.php?t=1645412
I hope these links are useful. I really would like to use optimally all the hardware of the phone.
Exitos!! :laugh:
Hi!
Thanks for your interest!
Resizing partitions, I read time ago, is a really critical operation.
I expect to have /cache partition as it has been made, the problem is that apps do not use it!
Resizing that block device to, let's say, zero, would give space to other partitions, but we'd lack a cache.
I definitely believe one of master questions is: where the hell does playstore download packages before installing?
During a big upgrade (let's say angry birds Rio 30+ megs) with df I only see /data growing (and /cache always empty), but after a lot of searching for newest and biggest files (busybox ls -ltrh, busybox ls -Shl) I could not find where they are put.
Once found this download location (no, it's not /data/data/com.android.vending/cache/main), would be easy to bind /cache to this dir.
Apk files from Google Play is downloaded to: data/data/com.android.providers.downloads/cache/
Wysyłane z mojego SK17i za pomocą Tapatalk 2
Hi
Many thanks for this tip!
Well, it's true apk are downloaded there.
BUT I see a strange behaviour: when I recieve the "low memory" (space on /data partition) notification, the apk suddenly disappears! :what:
In logs I see a lot of "couldn't openat chache: no such file or directory" immediately before low space notification log line...
You can use cache as swap if your kernel support it..
Sent from my Walkie'Talkie
Hi
Well, i symlinked /data/data/com.android.providers.downloads/cache to /cache/cache, and the partition is now correctly used by play store.
Is really strange that this is not a system default, btw.
EDIT: the /cache/cache was regularly erased by system, I symlinked /data/data/com.android.providers.downloads/cache to /cache and all is ok now.
EDIT2: you must previously remove (rmdir) the existing /data/data/com.android.providers.downloads/cache!
Could you put the exact command?
luchoz said:
Could you put the exact command?
Click to expand...
Click to collapse
Code:
ln -s /data/data/com.android.providers.downloads/cache /cache
:good:
thank you!!
would use XD
New info!!
http://forum.xda-developers.com/showthread.php?t=1959691
Really interesting
I've been running SHOstock3 for a few days to get comfortable with it. Tonight, I decided to encrypt the device. It rebooted, encrypted itself, then rebooted again and asked me for the password. For over half an hour now, it's been playing the SHOstock3 boot animation over and over again. The SAMSUNG screen doesn't show up between loops.
Is that normal behavior? Should I just give it more time?
The power button was able to turn it off. After restarting, it would ask for the password and do the same thing. I should point out that entering the wrong password would make it ask again, so it was working "properly". I decided it was toast and tried wiping it. However, it still asked for the password. Repeatedly entering the wrong password to force a wipe didn't work properly either. It still remembered that it had a password, but forgot what it was.
To fix it, I had to go back to stock Jelly Bean (flash stock Gingerbread then use Kies to upgrade; Gingerbread doesn't know about encryption). When the newly flashed Jelly Bean asked for a password, but as soon as I entered something, it rebooted. I presume that it wiped whatever encryption information was left because it rebooted properly.
I'm still trying to decide where to go from here. I keep work stuff on my phone, so encryption is fairly important to me.
I found this information regarding encryption on Android:
http://source.android.com/tech/encryption/android_crypto_implementation.html
It's for Honeycomb, but I'm going to assume that it hasn't changed significantly. It looks like all the encryption information is stored at the end of the /data partition. However, it's not part of the filesystem itself. If init can't mount /data, it assumes that it's encrypted and takes appropriate action.
As such, I would assume that completely erasing the entire /data partition would take care of it. Note that the /data partition needs to be erased, not just the filesystem. Based on what I've read, I think that the /data partition needs to be wiped/erased/formatted in such a way that the last 16KB of the partition is erased. After that, a new filesystem would need to be created to keep it from asking for a non-existent password.
So, does anyone know what the wipes actually do in recovery?
A couple of observations.
I don't think it is advisable to work at this level of the file system while making assumptions. In my view, you make two very questionable assumptions in your remarks.
I don't have any information on the workings of wipe and format in recovery. You can, however, work with eMMC blocks using Linux commands. For instance, if you use the dd command to make a copy of the data partition, you will get the whole partition, not just the file system. You could then use reverse engineering to see what is contained in the last 16 kb of the partition. This would require a skill set that is certainly way beyond me, and I suspect beyond you. You could also use dd to write to just the last 16 kb as well.
Well, at this point, I'm not really trying to find a "solution", I'm just trying to understand why it's so hard to wipe the phone after it's been encrypted. The only reliable method I've found is to put on the stock firmware, then repeatedly enter the wrong password until it wipes itself.
I was poking around in the jeboo github (SHOstock3 uses the jeboo kernel) to see if I could figure out what's going on. I found the following line in fstab.smdk4210:
Code:
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=/efs/metadata
I'm currently running stock 4.1.2 and I found the same file with that line. After doing some research, I found that the encryptable flag tells the system to allow encryption for that particular filesystem. Its argument says were to keep the encryption metadata. In this case, it's kept in /efs/metadata. That file exists on my encrypted stock JB system and the file happens to be exactly 16KB. The first part of the file is plain-text and it appears to be encryption related. After further research, I found that "footer" is an acceptable value for encryptable. In that case, it stores the metadata in the last 16KB of the partition (but the filesystem can't extend into it for obvious reasons).
Given the behavior I've seen, my guess is that if init sees /efs/metadata, it asks for the password. This would explain how wiping /data would cause the system to still remember the password. Even if you were to erase everything in /data, /efs/metadata would still exist. I also suspect that certain methods of "wiping" /data don't actually do so because they attempt a check before doing the wipe. I'm far from an Android expert, most standard methods of checking a filesystem in linux would fail if said filesystem were encrypted.
So, I think I've figured out why wiping an encrypted phone is so hard, but I still haven't figured out why SHOstock3 doesn't boot after it encrypts the phone.
Jebo knows a lot about the kernel. You could probably get into a meaningful discussion with him on encryption. I don't know if he has a chat channel of his own, but he is probably in Shoman94's chat channel quite a lot. You can find that in the OP of the SHOstock3 thread.
Hello everybody, I'm Dejan and I could use some help please.
I have Samsung Galaxy SII GT 9100 with broken screen and I have some very important stuff in it. Screen is totally broken and I cant see a thing. Long story short i used Fuzzy Meep's app but I'm stuck deep in the mud so thats off. I booted phone in my custom recovery , installed ADB on PC and managed to connect to the device. But I can't make my way thru the sdcard. Here is what I did:
G:\ADB>adb.exe shell
~ # cd etc
cd etc
/etc # ls
ls
recovery.fstab
/etc # cat recovery.fstab
cat recovery.fstab
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options
> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime
wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,j
ournal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,j
ournal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,d
iscard,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,j
ournal_async_commit wait
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0 auto auto defaults voldmanaged=sdcard0:
11,nonremovable,noemulatedsd
/devices/platform/s3c-sdhci.2/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:
auto
/devices/platform/s3c_otghcd/usb auto auto defaults voldmanaged=usbdisk0
:auto
# recovery
/dev/block/mmcblk0p5 /boot emmc defaults recovery
only
/dev/block/mmcblk0p6 /recovery emmc defaults recovery
only
How do i mount internal memory and pull out my data? Any help is appreciated. Thanks
It's a CM LInaro Kitkat 4.4.2 with custom kernel. With older versions of Android I was able to do what I was attempting to do but I've read somewhere about certain change when mounting storage on 4.4.2.
Thanks in advance.
Noone? Reallu? At least some info about device reading out data directly from the storage chip?
denkodenko said:
Noone? Reallu? At least some info about device reading out data directly from the storage chip?
Click to expand...
Click to collapse
That isn't even remotely possible for an end user. The only people who might be able to do that is a company which specialises in recovery of data from dead HDDs'. If it is possible, expect it to be very very expensive. I've never seen a single person post here in 2.5 yrs saying they've had this done successfully. Even if this is was possible, fixing your screen would be cheaper.
Very few people here have attempted to do what you're doing with ADB (me included; frankly, if the data was that important to me, I'd pay $120 for a new screen to save myself hassles, but I wouldn't be in that situation to begin with because I back stuff up). Unfortunately, you're going to be in for a rather long wait if you don't manage to work this out on your own, many people who may have been able to help you don't post here anymore, they've moved onto other phones given it's been 3 yrs since this phone was released.
MistahBungle said:
That isn't even remotely possible for an end user. The only people who might be able to do that is a company which specialises in recovery of data from dead HDDs'. If it is possible, expect it to be very very expensive. I've never seen a single person post here in 2.5 yrs saying they've had this done successfully. Even if this is was possible, fixing your screen would be cheaper.
Very few people here have attempted to do what you're doing with ADB (me included; frankly, if the data was that important to me, I'd pay $120 for a new screen to save myself hassles, but I wouldn't be in that situation to begin with because I back stuff up). Unfortunately, you're going to be in for a rather long wait if you don't manage to work this out on your own, many people who may have been able to help you don't post here anymore, they've moved onto other phones given it's been 3 yrs since this phone was released.
Click to expand...
Click to collapse
Well at least I gave it a shot but yeah... you are probably right I shouldn't have bothered posting and I was pretty sure someone somewhere might have asked the exact same question unfortunately I couldn't find it. I know how annoying these questions can be and I'm very sorry if I made someone angry. Long story short - I managed to get my pictures and videos back, as well as contacts. I do back those stuff up. however I had some .bin files for work that I lost but I've been living with that. It just might take some time browsing on the Internet finding them again but I'd rather do that than trying to do anything with the phone. I bought it $100 last year, the screen alone is that much, there's no point in fixing it. And at last but not least, thanksfor the reply.
Nah, they're not annoying It's just a very unusual situation, and as I said, if you want help with that sort of stuff with this phone on here, because so many people have moved on, you need to be really patient, that's all.
Same story
Shortly broken display no touch input. I had custom KitKat rom.
I had almost given up trying to mount the internal sd card with ADB, following numerios forum post instructions
here is my solution using windows pc and ADB
I rebooted in recovery (I think it was 6,0xx)
Using command prompt (you also need adb.exe) :
adb remount
adb root
adb usb
Those 3 command somehow mounted the internal storage and I was able to use the "adb pull" comand to copy the whole internal sd card to my hard drive
After that I went with "adb shell" to check how the sd card was mounted and here is what I found:
"
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noe
xec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=c
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/mmcblk0p11 on /emmc type vfat (rw,dirsync,relatime,uid=1023,gid=1023,
fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortn
ame=mixed,utf8,errors=remount-ro)
"
Okay so here it goes. I had missing IMEI problem in a custom ROM when not on a samsung base. I had a neatefs (app on android) backup which I tried to restore using HC ktool (Bad idea, I know). It gives me a successfully done message and tells me to reboot. Now my phone is stuck in bootloop no matter what (Stock firmware, wipe data, factory reset nothing works) and the recovery gives the error mentioned in the title.
/efs is unmountable for me. I tried various methods mentioned for S3 and Note such as connecting the phone in ADB mode and following the steps but none of that works.
Have you tried formatting /system, /boot, /preload /storage/sdcard0 ? From a rooted kernel, of course.
And then trying reflashing the original stock rom.
hope this helps http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
AKAndrew41 said:
Have you tried formatting /system, /boot, /preload /storage/sdcard0 ? From a rooted kernel, of course.
And then trying reflashing the original stock rom.
Click to expand...
Click to collapse
I have tried formatting /system and I don't think that formatting /sdcard0 is going to help, it will just increase the burdon of data transfer. As for others, I was afraid it will make more mess than solve any. Are you sure formatting those will not affect anything?
ruleh said:
hope this helps http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Click to expand...
Click to collapse
I've tried all that, none helps. I've even installed a busybox as mentioned somewhere else which said that the syntax mke2fs is not available without a busybox. Nothing worked. Still unable to mount efs afterwards.
pHraiL^ said:
I have tried formatting /system and I don't think that formatting /sdcard0 is going to help, it will just increase the burdon of data transfer. As for others, I was afraid it will make more mess than solve any. Are you sure formatting those will not affect anything?
Click to expand...
Click to collapse
I'm pretty sure it won't damage anything, or at least to me didn't. Because whenever I want to reinstall a new ROM I always format everything I've mentioned earlier so I don't find it harmful for the device, as long as you don't have data worth backing up.
Also, wipe dalvik.
If you installed busybox, make sure you uninstall the previous version prin pressing uninstall, and them installing 1.23.1 because for me sometimes it says it's intalled, but after reboot I still have the old one.
After you do that, connect phone to PC and try running
adb shell
Once you do that, give a try to the command
umount -f /efs
even if it says it's umounted, then type
mount /dev/block/mmcblk0p3 /efs
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
Click to expand...
Click to collapse
These two are the commands everyone is talking about the S3 phone having same issue. I tried everything. The first command works and it shows something like:
"The filesystem will be automatically checked every 35 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override."
For the second line of code when I try, this is what I get:
"It says "mount: can´t find /dev/block/mmcblk0p3 in /etc/fstab"
Now I have also tried adding space and /efs to the second command. It gives me nothing, not even any error. So I presume it works but then when I reboot efs is still messed up. I have no idea what these commands does actually. I think it has something related to re partitioning. Shouldn't the second command line give the same output as the first one? Its been a whole day searching for this thing. I got my phone messed up real bad.
EDIT: One more thing, when I hit the # df command on ADB, it shows 3 drives (/dev, /cache, /emmc) when not in su and 4 when in su (/dev, /cache, /emmc, /system). No where it shows any efs partition. Is there suppose to be any?
EDIT2: After the second line command. Using mount -t following someone's guide I get the efs partition but I think it is way too small. See the attachment. This partition is gone again after reboot.
OH GOD I got it working. After more searching, I found out the the block used for efs storage in S2 is mmcblk0p1 not mmcblk0p3. Phew!
Follow the same commands to make it work. Just rename the block.
Here is a guide which helped me figure out the block: http://www.usoftsmartphone.com/t306464.html
Thanks everyone
im having same trouble now with the S7. the page you share not there anymore. please share me how to figure out the block