Related
I wanted to try the encrypt feature of android in my phone but now when I try to flash a new version on my rom can't mount my sdcard as it is encrypted. When I did it I imagined that it may was possible to decrypt within recovery and then flash a new rom but that's not possible.
What's the best way to decrypt my phone/flash a new rom on top, by losing as few as possible??
I googled and found a thread in the galaxy nexus forums that mentioned that the only way is via fastboot, is this possible with s2? any pointers to the s2 method?
I managed to flash another rom (miui specifically) by using adb and the commands below
./adb shell mount -t tmpfs none /sdcard
./adb push update.zip /sdcard
Click to expand...
Click to collapse
but now its not possible to decrypt the sdcard despite the fact i know the password, it doesn't even prompt me at boot
edit:
By doing factory reset I might have deleted the encryption keys rendering my sdcard inaccessible that's why I don't get prompted for password at boot. Is there anyway to fix this or create the certificates again as I know the password???
This has bin spoke about before with no results mate. Sorry. Seems its lost now. People I spoke to tried every thing with no success.
I9100/I9300
Hey flash gb firmware. A user did this and it has no encryption on it then flashed jb firmware and it was sorted :thumbup::thumbup: pls try it and see.
I9100/I9300
Hi, if you are using a 4.2.2 rom:
from CWM recovery, check your partitions for corrupted filesystem using the e2fsck utility (information here http://www.openfsg.com/index.php/Using_e2fsck._File_System_Check) from adb shell.
Command is:
adb shell e2fsck -n -f -v /dev/block/mmcblk0p9 (to check /system)
adb shell e2fsck -n -f -v /dev/block/mmcblk0p10 (to check /data)
If you start to see an endless flowing river of words, wait for it to end (it might take minutes) and then read:
I'm getting lots of multiply-claimed blocks, blocks shared among two or more files, after a CLEAN installation of many Rootbox 4.2.2 versions (i tried latest official and sabermod, Nico's 60), and Resurrection Remix 4.2.2
Steps to reproduce the problem: clean install latest Rootbox/Resurrection Remix, configure a bit the rom, play with it, INSTALL some apps from playstore, update some system apps. Then, REBOOT the phone. Play with it again if you wish and eventually go to recovery.
Even if you switched to another kernel (like Dorimanx) at some point, do the check as you might have problems (unless you have flashed the kernel right after the rom, without rebooting)
I'm just a simple user but i think the problem is related to default CM10.1 kernel ((usually CWM 6.0.3.x)
Possible (common) big problem related to corrupted filesystem: phone stuck at boot/kernel logo sooner or later, after a simple switch off or reboot.
Other problems: app errors
I'm not getting those errors with clean install of KitKat 4.4.2 roms.
Please, tell me if this is a wide-spread bug, and if you can, try to reproduce yourself the steps.
an update: after reading here http://forum.xda-developers.com/showthread.php?t=2508447
i tried some steps:
installed a KitKat compatible kernel CWM 6.0.4.7, rebooted to its recovery, wiped everything from there and then flashed Rootbox, gapps and Dorimanx kernel. Played with the phone, rebooted a few times, installed apps ecc... then went to recovery and used the e2fsck command.
No error neither on /data nor on /system partition.
I suppose there might be a problem with old CWM versions' wipe command, don't know if custom kernels are affected too
anyone else can confirm? I remember Dorimanx talking about problems of corrupted partitions in his thread
nopainwithme said:
an update: after reading here http://forum.xda-developers.com/showthread.php?t=2508447
i tried some steps:
installed a KitKat compatible kernel CWM 6.0.4.7, rebooted to its recovery, wiped everything from there and then flashed Rootbox, gapps and Dorimanx kernel. Played with the phone, rebooted a few times, installed apps ecc... then went to recovery and used the e2fsck command.
No error neither on /data nor on /system partition.
I suppose there might be a problem with old CWM versions' wipe command, don't know if custom kernels are affected too
anyone else can confirm? I remember Dorimanx talking about problems of corrupted partitions in his thread
Click to expand...
Click to collapse
I am not sure what can make the multiple block holdings as this is the main error.
90% of it is in /data/dalvik_cache folder!
so i guess it's some kind of ROM code for dalvik generation that write files with some strange block links to other files...
and when you run fsck you see that it's doing the block separation most of the time.
you can also test this, before you about to run the check and fix, wipe dalvik cache!
do
sync;
then wait for 30sec for all dirty memory to be written to disk.
and check,
you will see that it's a lot less mess now...
with KitKat source there was major rework for dalvik ROM code, so i guess it's better than was before and not mess the file system when generating dalvik for all app! /system and /data/app/
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)
"
Ive been searching for a while for a forum that explains how to root the new nabi 24" BIG TAB HD. trying to install clockworkmod on the tablet.. if anyone can point me in the direction of what I'm looking for that would be greatly appreciated.
jmmac said:
Ive been searching for a while for a forum that explains how to root the new nabi 24" BIG TAB HD. trying to install clockworkmod on the tablet.. if anyone can point me in the direction of what I'm looking for that would be greatly appreciated.
Click to expand...
Click to collapse
As far as I know nobody has talked about it on here except you.
Depending on what kernel patches or android security fixes it has you might be able to try some root programs. There certainly will not be a clockworkmod or TWRP for it yet.
If none of the root methods work it might be possible to use the Dreamtab TWRP.(http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917) If it's like the previous Nabi tablets the bootloader will be unlocked, and you could try booting from that TWRP. The screen and the landscape/portrait might be messed up but it could work. In the last software update to the dreamtab they locked the bootloader so the BIG TAB might be as well. It could be unlocked by
Code:
fastboot oem unlock
^^^ This will ERASE all the data on the tablet.
If you want to try the TWRP way let me know but of course there are dangers involved.
If you try it alone be aware that if you try the dreamtab TWRP load it by
Code:
fastboot boot recovery.img
and NOT
Code:
[STRIKE]fastboot flash recovery recovery.img[/STRIKE]
or you will overwrite your current stock recovery.
also interested! any further info would be great!
schlager said:
also interested! any further info would be great!
Click to expand...
Click to collapse
Do either of you have one? Or just asking?
aicjofs said:
Do either of you have one? Or just asking?
Click to expand...
Click to collapse
i plan to buy one in the next few weeks. mainly need it so i can have two sheets of music in front of me. if there is another tablet that can do that, let me know.
aic, I got one for the kids for Xmas. The Nabi2's have been good but wont last forever, I liked the multi user option and big ass screen on the big tab. Well see how it works out! Once they open and spend time with it I'll be interested in rooting for adaway and such.
codest3r said:
aic, I got one for the kids for Xmas. The Nabi2's have been good but wont last forever, I liked the multi user option and big ass screen on the big tab. Well see how it works out! Once they open and spend time with it I'll be interested in rooting for adaway and such.
Click to expand...
Click to collapse
I have no idea about the BigTab but if it's like the DreamTab it will update when you boot it up. It's hard to get around it. If it does it will likely patch a lot of the more recent exploits that can gain you root. There is the option to try the dream tab recovery like I said above but be really careful with that.
Also one of the Dreamtab updates locked the bootloader. This isn't a big deal as it was unlockable via fastboot. However, if you let the kiddoz, or you start installing a whole bunch of stuff, when you unlock the bootloader you will wipe the tablet back to factory(normal behavior). Best to unlock it as soon as possible.
I own the big tab 20" was able to root using http://forum.xda-developers.com/showthread.php?t=2473747
I did have to unlock the bootloader and tried booting the dream tab recovery from fastboot no dice there so wasn't gonna risk flashing it.
The process took about 20 mins maybe less fully automated it froze at some point so I reset the big tab and tried again at which point kingo program told me I was already rooted download SU was able to update the binary's normal method and been good to go since. Word of warning it does preform a factory reset when you unlock the bootloader so be prepared for that.
I have been working on compiling CWM for the Nabi big tab 20" I'm close but I can't seem to figure out the path for the sdcard currently the recovery boots but can't back anything up with out the correct path entered into the recovery.fstab. This particular tablet does not have a real sdcard nor does it have a slot for an external one. Any help on this would be appreciated when I get it sorted out will add a link for the recovery.
this is what I currently have in my recovery.fstab.
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <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
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=ordered,noauto_da_alloc,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/TRD /app ext4 defaults wait
/dev/block/sda1 /sdcard vfat defaults voldmanaged=sdcard:auto
When I boot into recovery and attempt to perform a backup to sdcard I get E:Can't mount backup path.
You could download and try a rooting apk like towelroot framaroot or z4root if it has a low android firmware like 2.3.6 or something but only for z4root
I already got it rooted using Kingo root, these tablets are new on the market running kitkat 4.4.4, the end goal I am trying to achieve is making a custom rom but a neassacery first step is to get a working custom recovery so I can backup my stock rom just in case I blow up my tablet =)
lmortal said:
I have been working on compiling CWM for the Nabi big tab 20" I'm close but I can't seem to figure out the path for the sdcard currently the recovery boots but can't back anything up with out the correct path entered into the recovery.fstab. This particular tablet does not have a real sdcard nor does it have a slot for an external one. Any help on this would be appreciated when I get it sorted out will add a link for the recovery.
this is what I currently have in my recovery.fstab.
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <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
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=ordered,noauto_da_alloc,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/TRD /app ext4 defaults wait
/dev/block/sda1 /sdcard vfat defaults voldmanaged=sdcard:auto
When I boot into recovery and attempt to perform a backup to sdcard I get E:Can't mount backup path.
Click to expand...
Click to collapse
Did you get that from pulling the stock recovery and extracting the recovery.fstab from the ramdisk?
The internal is likely on /data/media, or data/media/0 if it's like all the other Nabi's. Pretty sure /dev/block/sda1 to mount sdcard is not going to work. I'm not as knowledgeable at CWM as I enjoy TWRP so I'm not sure if there is a boardconfig.mk change you can do or if you need to symlink it in an init.rc file.
aicjofs said:
Did you get that from pulling the stock recovery and extracting the recovery.fstab from the ramdisk?
The internal is likely on /data/media, or data/media/0 if it's like all the other Nabi's. Pretty sure /dev/block/sda1 to mount sdcard is not going to work. I'm not as knowledgeable at CWM as I enjoy TWRP so I'm not sure if there is a boardconfig.mk change you can do or if you need to symlink it in an init.rc file.
Click to expand...
Click to collapse
There was something else there originaly but it didn't work either so I ended up using the following from cat /proc/mounts:
/dev/fuse/mnt/shell/emulated /sdcard fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permisions,allow_other nonremovable
Using the above line in the recovery.fstab allowed cwm to see the sdcard but was still unable to mount it. I have been playing around with different things but I am fairly new to this so my knowledge is limited.
lmortal said:
There was something else there originaly but it didn't work either so I ended up using the following from cat /proc/mounts:
/dev/fuse/mnt/shell/emulated /sdcard fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permisions,allow_other nonremovable
Using the above line in the recovery.fstab allowed cwm to see the sdcard but was still unable to mount it. I have been playing around with different things but I am fairly new to this so my knowledge is limited.
Click to expand...
Click to collapse
I'm not really sure without seeing any of your code(device tree), finished recovery or any of the stock recovery.
I haven't made CWM in so long. Something like?
/dev/null /sdcard datamedia defaults recoveryonly
dd the mmcblock0pX for the recovery and boot and we can make something work. How much space is the recovery partition?
aicjofs said:
I'm not really sure without seeing any of your code(device tree), finished recovery or any of the stock recovery.
I haven't made CWM in so long. Something like?
/dev/null /sdcard datamedia defaults recoveryonly
dd the mmcblock0pX for the recovery and boot and we can make something work. How much space is the recovery partition?
Click to expand...
Click to collapse
I sent you a pm with a drop box link with my files in the mean time gonna try compiling with your suggestion and see what happens.
---------- Post added at 04:17 PM ---------- Previous post was at 03:36 PM ----------
I tried compiling with:
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
/dev/null /sdcard fuse datamedia,recoveryonly defaults
It compiled successfully and I was able to flash it, the sdcard showed up in the mount menu but was not mountable still.
---------- Post added at 05:10 PM ---------- Previous post was at 04:17 PM ----------
Okay so my latest build using:
/dev/block/sda1 sdcard fuse defaults nonremovable
Allowed backup to the sdcard of everything with the exception of /data got "Error while making a backup image of /data!"
Also still unable to mount sdcard under the mounts and storage menu.
I believe the reason for the error while backing up data was due to available space when I restarted the tablet there was only 99.59MB available and I think the data would have needed more space then that.
I kept running into problems with CWM recovery but with the help of aicjofs I was able to compile a working TWRP with usb drive support, I don't yet have enough post to make an outside link so if some one can pm me I can give the link to be posted here with the recovery I made.
Working TWRP 2.8.1.0 for Nabi BigTab 20
Here is a TWRP recovery 2.8.1.0 for the Nabi BigTab 20" model
TWRP 2.8.1.0 for NV20A(BigTab20)
Built by @lmortal. We spent a lot of our Sunday sorting all the issue so click the thanks button for Imortal in the post above this one!
aicjofs said:
Here is a TWRP recovery 2.8.1.0 for the Nabi BigTab 20" model
TWRP 2.8.1.0 for NV20A(BigTab20)
Built by @lmortal. We spent a lot of our Sunday sorting all the issue so click the thanks button for Imortal in the post above this one!
Click to expand...
Click to collapse
Fixed an error where /addon was not mounting. re uploaded recovery image to the above link.
I can't unlock my bootloader.
lmortal said:
I own the big tab 20" was able to root using http://forum.xda-developers.com/showthread.php?t=2473747
I did have to unlock the bootloader and tried booting the dream tab recovery from fastboot no dice there so wasn't gonna risk flashing it.
The process took about 20 mins maybe less fully automated it froze at some point so I reset the big tab and tried again at which point kingo program told me I was already rooted download SU was able to update the binary's normal method and been good to go since. Word of warning it does preform a factory reset when you unlock the bootloader so be prepared for that.
Click to expand...
Click to collapse
I've ben trying to root my Big Tab 24". You said you had to unlock the bootloader. I can't get it into bootlad mode or unlock the bootloader. I tried fastboot. I tried every button combination I could think of. (not too many considering it only has three physical buttons) I tried rooting it with Kingo without unlocking the bootloader. Nothing is working. Please help. What am I doing wrong or not doing right?
Fastboot is the boot loader make sure you have USB debugging enabled and connect the tab to a PC you can then use the command "adb reboot-bootloader" the command to unlock is "fastboot OEM unlock"
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