A300FU E:failed to mount /efs (Invalid argument) - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

A few days ago I was having some problems with my phone and lineage 14.1 so I decided to reflash the ROM, only to notice it wouldn't boot. I then decided to install the stock 6.0.1 firmware through odin, but when I rebooted the device, it just stayed on the samsung galaxy a3 screen. I managed to boot the device with a 4 part 5.0.2 polish firmware, which is bloated and doesn't remember wifi passwords, so I decided to try to reinstall the 6.0.1 firmware, thinking I had fixed my phone. I just ran into the same problem as the first time.
This time I noticed that when I booted into recovery, there was an error mounting /efs ("E:failed to mount /efs (invalid argument)"). Going through the internet I found many ways to fix the problem but none worked for me. The one I saw most people had success with was one that involved using some commands in adb, which failed for me.
The commands where:
adb shell
su
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1
reboot
all the commands up to "mount -w -t ext4 /dev/block/mmcblk0p1" worked fine, but this one got the error: can't find /dev/block/mmcblk0p1 in /etc/fstab
Does anyone have any idea how I can fully fix the device and mount /efs to be able to install a fully working firmware?

btw, I was using this tutorial:
http://www.selftechgenius.com/how-t...nvalid-argument-in-all-samsung-galaxy-phones/
and at the end it says that if you're not sure which particular mmcblk0p* EFS mount point to use, you should use the command mount to see which one is he EFS mount point, but I can't seem to find which one to use after using 'mount'.
The mount commant prints:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=700004k,nr_inodes=153395,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=700004k,nr_inodes=153395)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p24 on /system type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p27 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p27 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk1p1 on /external_sd type ext4 (rw,seclabel,relatime)
How am I supposed to know which one to use?

You can't just use any old block device, it needs to be the specific one the EFS partition mounts to, which you would find with the command below.
ls -laR /dev/block
However I would think your problem is that you just need to install the stock firmware then format(Factory Reset) the /data partition.

ashyx said:
You can't just use any old block device, it needs to be the specific one the EFS partition mounts to, which you would find with the command below.
ls -laR /dev/block
However I would think your problem is that you just need to install the stock firmware then format(Factory Reset) the /data partition.
Click to expand...
Click to collapse
Is there a specific reason why the repair firmware works but other stock firmware or rom flashed after that don't. Shouldn't the repair firmware fix the problem?
I think I already tried formating the data partition after flashing a stock firmware, but I'll give it another try in a few days as I have a lot of stuff to do right now.
If this method doesn't work, using the same commands I stated previously on the block I get from -laR /dev/block should work right?
Sorry, I don't know that much about partitions, blocks and all that deep and advanced android stuff, I had never run into a problem like this when flashing roms and kernels previously, I don't even know what caused tha problem on the first place...
Thanks for helping!

ashyx said:
You can't just use any old block device, it needs to be the specific one the EFS partition mounts to, which you would find with the command below.
ls -laR /dev/block
However I would think your problem is that you just need to install the stock firmware then format(Factory Reset) the /data partition.
Click to expand...
Click to collapse
I found the block for the efs partition (/dev/block/mmcblk0p13) with your command, but when running the previous commands on it, I still get the "mount: can't find /dev/block/mmcblk0p13"
I already factory data reset my phone a couple of times after the problem occured the first time, and it didn't do anything. Any other ideas why something like this would happen?
EDIT: When I rebooted my phone I noticed my wifi was working (before this, all my wifi passwords would get erased on reboot) and when I checked the /efs folder on root explorer I noticed it was full, not like before. Seeing this I decided to try and install the stock firmware again and it worked!
Thank you so much for your help, looks like I just had to find the right block all along...

Result

Related

Crippled G1 (Not Bricked) **SOLVED**

Hey guys.
I ran into some problems the other day installing a theme and after a reboot it was hanging on the Splash Screen T-Mobile G1 Screen. I thought I bricked my phone but I had the ENG SPL and someone suggested to reflash and start over with RC29 and reroot the phone. I did and it booted right up into the home screen like I just bought the phone. Now I was trying to flash the modified recovery partion but I noticed some stuff going wrong. Telnet was not downloading from the market, much less any of the apps. Telnet was neither installing from the browser nor downloading from the market. So i tried forwarding a port from my computer and connecting my G1 to Telnet via ADB from my computer which worked. I then flashed the modified recovery partition and after rebooting twice and going into the recovery utility it reads.
Android system recovery utility
E:Can't mount CACHE:recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
From this I cannot tell whether the modified recovery was flashed or not.
Now every time I try one of these options in the recovery utility, it always spit out another
E:Can't mount CACHE:recovery/log
The only thing that works is Alt+L which toggles the text but still gives me an error despite being the only option that works.
Am i screwed here or is there some way I can get my phone back on track and get it rooted and updated from RC29
NOTE: My phone still works but just in a watered down state where my phone doesn't download any apps at all
EDIT: Confirmed that I am now using test keys. It now reads:
Android system recovery utility
Using test keys.
E:Can't mount CACHE:recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
EDIT AGAIN: Here is a solution http://forum.xda-developers.com/showthread.php?p=3345258#post3345258
Just preform a whipe. I had the same issues last night.
I tried that I forgot to say too.
I can't do it in the recovery utility since it just pits out the same error everytime and when trying it from the phone itself from SD Card & Phone Storage it says something like "No reset performed because the System Clear service is not available.
Any other way from those two options to wipe my phone???
hmm I havent had this issue
just hang in there I know theres something with info or someone around who can help you. I wish i could though. good luck
I did the same (reflashed RC29) and got the same error. Thought, "Oh crap, now I've really done it." Turns out, I flashed JF 1.42 RC33 and the error went away. Of course, I was still able to download everything so it's not exactly the same issue. But the error message itself was the same. Have a backup from the outstanding Nandroid utility?
Well I do have some nandroid backups but flashing RC29 also restored the original bootloader so that means I'm not really able to flash those backups. I can't update to anything using the recovery utility so I don't know what my next move is.
Have you tried flashing rc29 again?
I hope this solves your problems. This is without the nandroid backup btw. If you dont care about backing up(or don't have astro/appsinstaller) what you have now, just skip to the *
I hope you either have appinstaller or Astro installed.
I would recommend using MyBackup, download it onto your sdcard from ur computer from http://www.mediafire.com/download.php?qmyztn0mndz. Use appinstaller/astro to install it from your SD, backup all your goodies. (for astro, the mybackup apk needs to be in backups/apps folder)
*Go back to RC29 (follow the steps here http://forum.xda-developers.com/showthread.php?t=442480)
Get hard SPL as suggested in that thread.
Install RC33/ADP1.1h (http://forum.xda-developers.com/showthread.php?t=475381)
Don't forget to upgrade your radio too (links in above thread)
Perform a wipe.
Boot to the home screen and check if everything works to your expectations. (Now is when you install Astro/appinstaller from the market)
Now install the engineering SPL.
Try instaling your nandroid backup.
NOTE: Next time you try a theme and find you are stuck at the splash screen, just reinstall the latest/greatest JF/personal image u were using.
Keep in mind themes for RC33 etc use more space so get rid of the ringtones & notifications from the system folder before installing most themes.
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm -r /system/media/audio/ringtones
rm -r /system/media/audio/notifications
Click to expand...
Click to collapse
Yes I have tried reflashing RC29 two times to no avail.
And MrBurrito I wish I was able to update my phone with any update.zip. packages but the recovery utility is not able to update with any of the packages. It just spits back out the error
E:Can't mount CACHE:recovery/log
I wish it was that easy to get it working
Any other suggestion for updating my phone without the recovery utility and fastboot?
Is there a partition called CACHE that may be causing the problem?
hey, not sure if this is any help or not but im wondering if you moved your cache to the sdcard so save room on the system memory? if so is your sdcard actually seated properly. I occasionally can't run my apps that i moved onto my sdcard cause the phone is not reading the sdcard. I take out the sdcard and reseat it and that usually does the trick. sometimes i have to reseat it 2 or 3 times before it will read. it's annoying when it happens. Other than that i'm sorry im a minnow in the ocean when it comes to linux stuff.
good luck with your phone.
Well I moved some of my cache's to my sdcard back when I had rooted RC30. Like browser, market, and a few more but I never tried moving my apps to the sdcard.
i moved everything but my cache to my sdcard. im wondering if something in the cache was moved that the phone needs but can't read cause of the sdcard not being seen. just a shot in the dark, but i've been in a place where i couldn't use my old wizard phone cause of a corrupt rom and can understand your frustration. you might try sending a private message to some of the more astute members like jesusfreke. I know he answers private messages as soon as he can and is very patient with newbs like me
I will try doing that but I'm still open to the community's answers.
I can now confirm that I am using the modified recovery.
But it is still giving the error. So it now looks like
Android system recovery utility
Using test keys
E:Can't mount CACHE:recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
I am also pretty sure the error given has to do something with the CACHE partition found in /dev/block/mtdblock4.
Every time i try to edit or modify a directory called /cache it tells me its a Read only file system
Well depending on all the signs I think there is something wrong with the cache of my phone. Market apps not downloading, Browser downloads not successfully downloading and the errors about Can't mount CACHE:recovery/log in the recovery utility. It also says says Read only file system whenever trying to do anything with a folder called /cache.
So if somebody has any suggestions on CACHE, I would appreciate it.
My last resort is a cache.img from anybody since mine seems to be corrupt or something since everytime i try to flash it from my NAND backup it keeps tell me there was an error reading the file.
If anybody has a NAND backup of cache.img file or if anybody backed up there /dev/mtd/mtd4 file from either RC29 or RC30. Preferably RC29. Please post. Thank You
the rooted .nbh
id look into flashing the nbh bassiclly treating the phone like a stock RC30, it sounds like your recovery stuff ain't playing well with others and that may reinstall all of the pooched apps and stuff.
I dunno but it don't sound good, but the rooted .nbh that freed the peeps trapped without root, uses the bootloader to re flash everything, im not an android expert but there is a holiday inn express just down the street...
bhang
I tried flashing both of the RC29 and RC30 DREAIMG.nbh to no avail either. I have to say it has to do with something the cache partition (mtdblock4). The only thing that does not get flashed when using the DREAIMG.nbh is the cache. That partition is a read only file system on my phone and I dont know how to change it to a read write so that the recovery and everything else can access it. Anybody knows how to???
i dont know what sort of console you have if any but the mount command if you can execute it will list the mounted filesystems and their current states (ro = read only rw = read/write) thats assuming you can type said command though, if you can through the output on here and i may be able to get cache writable
Here it is.
Code:
$ mount
rootfs / rootfs ro 0 0
tmpfs /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat rw,dirsync,nosuid,nodev,noexecuid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
$
Okay guys i got it fixed. Thanks for all your help, especially DJ_Steve. The thing was having to mount the mtdblock4 partition (cache partition) and restarting in recovery and doing a wipe (which finally worked).
I did:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /cache
Restart into recovery and wipe.
I think i did this before and it didnt work. O well it worked this time.
Now it shows.
Code:
$ mount
rootfs / rootfs ro 0 0
tmpfs /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat rw,dirsync,nosuid,nodev,noexecuid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
$

cannot mount \cache

Hey all.
Firstly please forgive me it this seems pretty basic however i seem to have lost the ability to mount the cache partition on my JF1.5 Dev Phone.
The upgrade process went fine, had been using it for a week, then i installed an animated splash screen made for non-cupcake builds and it bricked my phone. i got the black screen of wait in place of an animated load screen. luckily, anticipating such problems, i had just done a full nandroid backup.
now here's the problem. while backing up from nandroid, i was informed that the cache partition does not exist.
looking in the filesystem, there is a /cache folder but nothing in it and i have lost the ability to install apps via the market.
running mount shows:
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/loop0 on /system/modules type cramfs (ro)
/dev/block/loop1 on /system/xbin type cramfs (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on /system/sd type ext2 (rw,errors=continue)
/dev/block//vold/179:1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=
1000,gid=1000,fmask=0711,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=is
o8859-1,shortname=mixed,utf8)
and the partitions table shows:
major minor #blocks name
7 0 204 loop0
7 1 1936 loop1
31 0 256 mtdblock0
31 1 5120 mtdblock1
31 2 2560 mtdblock2
31 3 69120 mtdblock3
31 4 69120 mtdblock4
31 5 76544 mtdblock5
179 0 3872256 mmcblk0
179 1 3349521 mmcblk0p1
179 2 522112 mmcblk0p2
please help, i have tried mounting it manually to mtdblock4 with the command:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /cache
mount: mounting /dev/block/mtdblock4 on /cache failed: Invalid argument
If any more information than this is needed i can supply logcat file etc...
twoolie said:
Hey all.
...
please help, i have tried mounting it manually to mtdblock4 with the command:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /cache
mount: mounting /dev/block/mtdblock4 on /cache failed: Invalid argument
Click to expand...
Click to collapse
wouldn't the command be:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /cache
??
but I fail to see why you are doing this, care to explain so i can understand?
ok maybe i should explain better. there are 3 major blocks set aside for the use of the filesystem. mtdblock3 is set aside for the /system partition, mtdblock4 is set aside for /cache and mtdblock5 is set aside for /data. cache is important because it caches objects for the dalvic VM, web pages for the browser and most importantly, it stores apks from the market while downloading. now the first two are not so bad because the dalvic vm will run, just a little slower and the browser will browse, ablight will not be able to cache pages and will only have access to what is in ram. but because the market will wait to be able to place a file in /cache before downloading it, this effectively means i will never be able to download/install from the market.
Now what happened was when i created my nandroid backup it backed up system.img, cache.img and data.img
i then bricked the system and wanted to restore from nandroid backups. first i put back the system, then data but the phone wouldnt accept a cache image. fastboot is unable to mount it, jf recovery is unable to mount it, and the android OS is unable to mount it.
also i tried your suggestion but mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /cache returns the same error message:
mount: mounting /dev/block/mtdblock4 on /cache failed: Invalid argument
also, mount -a returns:
mount: mounting /dev/block/mtdblock4 on /cache failed: Invalid argument
mount: mounting /system/modules/modules.cramfs on /system/modules failed: No such file or directory
mount: mounting /system/xbin/xbin.cramfs on /system/xbin failed: No such file or directory
i'm hoping that this means something to somebody. does this just mean i am missing cramfs modules i need?
any help would be GREATLY appreciated.
It would be a roundabout way, but DREAIMG.NBH will restore partitions. Of course you'd have to then do the rooting process all over again.
Wait... but to do nandroid, don't you want to just restore
system.img
data.img
boot.img
so the commands would be
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
I guess I'm failing to see why cache needs to be restored. won't the OS just clear it out an write over it eventually anyways?
Or am I missing something?

[Q] Anyone use AdFree on CM7?

Got AdFree installed, but it says it can't find space to write the hosts file.
Using CM7 final on SD card installed with verygreen's method.
Same here
Sent from my PC36100 using XDA App
danbutter said:
Using CM7 final on SD card installed
Click to expand...
Click to collapse
There's your problem.
AdFree probably freaks out when it sees how you have Android setup on your sd card.
It runs flawlessly for me with CM7 emmc.
Paul22000 said:
There's your problem.
AdFree probably freaks out when it sees how you have Android setup on your sd card.
It runs flawlessly for me with CM7 emmc.
Click to expand...
Click to collapse
+1
Agreed, works perfect on emmc
Works fine on my uSD. It just copy the host file to /system/etc/ so running on SD or emmc makes no different.
Confirmed Functional
I used adfree on nightlies in the SD card...decided to install final release on emmc and also didn't have problems.
I'm running CM7 off SD card. Adfree can't find the right mount point to remount.
1) I pulled the Adfree hosts file off another Android device (I attached it in a zip).
2) I then made the NC system partition writeable by using 'adb remount'
3) I pushed the hosts file to the NC: 'adb push hosts /system/etc/hosts'
if step 2) doesn't work, here are manual instructions. You need adb or terminal emulator with root permissions (hence the # that precedes each command):
# alias mount="busybox mount"
# mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,mode=755,gid=1000)
/dev/block/mmcblk0p2 on /rom type vfat (rw,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro)
/dev/block/mmcblk1p2 on /system type ext4 (ro,barrier=1,data=ordered)
/dev/block/mmcblk1p3 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw)
/dev/block/vold/179:20 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:20 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000)
/dev/block/vold/179:8 on /mnt/emmc type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-0 on /mnt/asec/dk.logisoft.aircontrol-1 type vfat (ro,dirsync,nosuid,nodev,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)​
The red line is the one we care about. DO NOT PROCEED IF YOURS IS DIFFERENT.
To make it read-write:
# mount -o rw,remount -t ext4 /dev/block/mmcblk1p2 /system
To make it read-only:
# mount -o ro,remount -t ext4 /dev/block/mmcblk1p2 /system
joobu said:
I'm running CM7 off SD card. Adfree can't find the right mount point to remount.
1) I pulled the Adfree hosts file off another Android device (I attached it in a zip).
2) I then made the NC system partition writeable by using 'adb remount'
3) I pushed the hosts file to the NC: 'adb push hosts /system/etc/hosts'
Click to expand...
Click to collapse
Yep, this should work... I still see ads all over though. Same places I don't see them on my Nexus One.
Did this actually work for you? Although really I can't imagine why it wouldn't.
I replaced my hosts file the harder manual way.
Maybe check to see if the hosts file was actually replaced. The hosts file should be around 700 kB
I'm encountering a problem with adfree and the nook color running cm7. I see others have it installed and running fine. First time using this app.
I have downloaded adfree and when i try and download and install hosts by clicking the button it gives me an error stating" unable to locate a partition to remount to write the host files to"
Anybody know whats wrong and how to solve?
Look at my post with the manual instructions.
don't need to, its on my evo that I tether from and I see no ads on the nook or my pc
Fix Permisions
I ran "Fix Permissions" from TWRP touch recovery and that did the trick for me.

[Q] /data cannot be mounted

After installing new CM ROM: http://forum.xda-developers.com/showthread.php?t=1779324
Most things function fine, with a few hiccups. However, any time the phone is rebooted, it goes back to default settings. As if it cannot save anything.
So I pulled this out of dmesg:
Code:
VFS: Can't find ext3 filesystem on dev mmcblk1p25.
Which corresponds to /data in /system/etc/fstab.
Could anyone give some insight into this? Would it be safe to format to ext3?
t1nk_2 said:
After installing new CM ROM: http://forum.xda-developers.com/showthread.php?t=1779324
Most things function fine, with a few hiccups. However, any time the phone is rebooted, it goes back to default settings. As if it cannot save anything.
So I pulled this out of dmesg:
Code:
VFS: Can't find ext3 filesystem on dev mmcblk1p25.
Which corresponds to /data in /system/etc/fstab.
Could anyone give some insight into this? Would it be safe to format to ext3?
Click to expand...
Click to collapse
Not sure what the problem is, but do not format it to ext3. If you format it, there's a chance you'll brick since the key of the partition will change, and our locked bootloader requires them to be at a specific setting. All the format options in the recovery are really rm -rf commands (just deletes everything) and don't really format at all.
I'd wipe data\factory reset (from cwm) and reinstall the rom. If that doesn't work, then go here and download Quarx's latest build for the Bravo or over to my PA thread and download its latest. You can use PA exactly like CM10 by disabling PA's hybrid UI. I know for sure that PA version works cause I used if for a month before flashing a 7 port I'm started working on yesterday.
Good luck
skeevy420 said:
Not sure what the problem is, but do not format it to ext3. If you format it, there's a chance you'll brick since the key of the partition will change, and our locked bootloader requires them to be at a specific setting. All the format options in the recovery are really rm -rf commands (just deletes everything) and don't really format at all...
Click to expand...
Click to collapse
I did find in /default.prop:
Code:
# ADDITIONAL_DEFAULT_PROPERTIES (From bootmenu/config)
...
# Forbid format of these partitions in mount menu (use only rm -r)
ro.cwm.forbid_format=/misc,/devtree,/config,/boot,/recovery,/pds,/system,/logo
Most of those are mounted with an "emmc" filesystem/module I've never heard of in linux.
I'd wipe data\factory reset (from cwm) and reinstall the rom. If that doesn't work, then go ... and download Quarx's latest build for the Bravo or over to my PA thread and download its latest. You can use PA exactly like CM10 by disabling PA's hybrid UI. I know for sure that PA version works cause I used if for a month before flashing a 7 port I'm started working on yesterday.
Click to expand...
Click to collapse
Unfortunately, installing any ROM fails to fix the issue. Tried PA first, got stuck in a bootloop. That leads me to believe ROMs will always require a working file structure.
I did however 'factory reset/wipe cache' from stock recovery (which claimed to format /data), load ROM, reset/wipe, reboot.
This did appear to solve the absence of /data mount. But it did not resolve the userdata persistence between reboots.
I found in /data/system/uiderrors.txt:
Code:
11/2/12 5:19 PM: No settings file; creating initial state
I tried changing some permissions via adb shell, but these were reset on reboot.
I suspect something with the init scripts is reseting something (it shouldn't be) on boot, however this is an area unfamiliar to me. I know some of those files are readable, I guess I'll have to just go through them line by line and see what makes sense....
CM 10-20120912-NIGHTLY-mb520
Build: cm_mb520_userdebug 4.1.1 JRO03L eng. quarx.20120912.233429 test-keys
Bootmenu v2.0-beta + Bootmenu JB Recovery v5.7.0-kobe
Didn't find anything conclusive in the parsable sections of init.* files, however I did notice that they often mount partitions and setup permissions.
On further digging into my phone, I saw that my *original* /data mount was still failing to function. Even though it has been repopulated under rootfs.
My output of mount:
Code:
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk1p21 on /system type ext3 (rw,relatime,barrier=1,data=ordered)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/loop7 on /pds type ext3 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
ramfs on /tmp type ramfs (rw,relatime,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,cod
tmpfs on /mnt/sdcard/.android_secure type tmpfs (rw,relatime,size=0k,mode=000)
If someone could paste their output (working ROM) for comparison, please.
This might help explain why my internal storage reads as 0Gb available, preventing Play store installs (I can force copy backups via adb).
At least I can enjoy JB so long as I don't reboot/power off.
From Quarx CM10 Custom Kernel Defy Plus 11\04 (running on a Bravo)
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk1p21 on /system type ext3 (ro,relatime,data=ordered)
/dev/block/mmcblk1p24 on /cache type ext3 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered)
/dev/block/mmcblk1p25 on /data type ext3 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered)
/dev/block/loop7 on /pds type ext3 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
ramfs on /tmp type ramfs (rw,relatime,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
Here's one option you could try -- fsck to repair the filesystem of any damage.
reboot into recovery
start adbd (Advanced->Start adbd)
open a terminal\command prompt (on PC...)
adb remount
adb shell
su
umount /data
e2fsck -fv /dev/block/mmcblk1p25
reboot and hope it worked
While a crappy option, have you tried flashing the sbf yet? If flashing the sbf two or three time in a row doesn't fix your issues then (probably) nothing will.
Being that the fs was never mounted:
adb shell
su
e2fsck -fv /dev/block/mmcblk1p25
And output:
Code:
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk1p25
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Which made me want to simply format. I don't know about "signatures", is there a blkid-like function under /system/bin? AFAICK init scripts only refer to /dev fs when mounting.
...have you tried flashing the sbf yet?...
Click to expand...
Click to collapse
In the course of events, yes, I did. This is how it went: from Bandroidx recovery + BravoX ROM (working fine), installed CM10 (w/o clearing anything, I was excited) managed to get a mostly working system w/o gapps. Not knowing it came with its own bootmenu, tried installing Bandroidx again. Led to bootloader error. Flashed fixed_bravo_sbf.sbf. Got CM back. Not sure when /data was corrupted...
I also have p4_kobe_umts_kobe_user_3.4.2-125_KOB_FFW-4_product-keys-ATT-US_ATT-signed.sbf, and noticed a size difference. If I go this route, should I try this one? Or fixed_bravo_sbf.sbf again? Thanks again for the input.
The umount command is just for safety . Here's the output from a working /data from CM10
Code:
[email protected]:/system/bin # e2fsck -fv /dev/block/mmcblk1p25
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
662 inodes used (0.80%)
50 non-contiguous files (7.6%)
1 non-contiguous directory (0.2%)
# of inodes with ind/dind/tind blocks: 83/4/0
32693 blocks used (9.91%)
0 bad blocks
1 large file
329 regular files
320 directories
0 character device files
0 block device files
1 fifo
0 links
1 symbolic link (1 fast symbolic link)
2 sockets
--------
653 files
There is a major difference between the full and fixed sbf. The fixed sbf only contains the bootloader and devtree (maybe ramdisk as well). The full sbf contains the full stock system. The fixed is mainly for those that accidentally flash a Defy boot.img or devtree.img when flashing or porting Defy roms.
While it sucks, it sounds like you just need to flash the full sbf and start over from scratch. I usually flash the sbf once every other month even if nothing is wrong (just makes me feel better).
From what you said above, /data was probably corrupted when you flashed CM10 without wiping data. Unless I'm flashing the same rom over and over again (when testing ports out, etc) I always do a factory reset when flashing. Its the safest way to go and you'll get better support from devs when you flash onto a blank slate (easier to debug since /data not being wiped is usually the cause of random bugs). It may have been from installing BandroidX Recovery since it uses the stock init scripts. Never install BandroidX Recovery. It is very obsolete and only useful if you plan on using BravoX, and even then you can use Defy 2nd-init recovery (just set it to boot to stock). More than likely it was from the non-wiped flash.
Flashing original .sbf worked! :victory:
Rooted, installed 2ndInitDefy, and backed up everything from there to sdcard.
/data now mounts correctly, and userdata persistence in CM10 is functional. :highfive:
Learn something new every day.
t1nk_2 said:
Flashing original .sbf worked! :victory:
Rooted, installed 2ndInitDefy, and backed up everything from there to sdcard.
/data now mounts correctly, and userdata persistence in CM10 is functional. :highfive:
Learn something new every day.
Click to expand...
Click to collapse
Glad to here you're not screwed :victory:. The best thing about the Bravo is you can fix it just like you do Windows -- if it breaks, just reinstall -- if you can't reinstall then its time for an upgrade cause ya broke it .

[Q] Need to extract data from broken tablet

I have a nexus 7 16 GB tablet with a busted screen. There's some files I want to get off it but I can't figure out how to do it. I have several clockworkmod backups on the device that I was trying to get off it through adb but couldn't do it.
I tried adb pull /data/media/clockworkmod/backup but it says the folder doesn't exist
I also tried adb pull /sdcard/clockworkmod/backup and same result.
I also tried using holo backup but it requires me to unlock the device but since the screen is broken I can't do this without using an otg cable which I don't have.
What I'm really after are some songs I created using the autorap app by Smule. If there's another way I can retrieve these files I would greatly appreciate it.
Did you not have it set to connect to your computer as an mtp media device? If so, just pull what you want from there.
This seems overly obvious to me, so clearly there is something that I am missing, and I don't want to make it sound like I am being a complete tool or anything.
Sent from my Nexus 7 using Tapatalk
jma9454 said:
Did you not have it set to connect to your computer as an mtp media device? If so, just pull what you want from there.
This seems overly obvious to me, so clearly there is something that I am missing, and I don't want to make it sound like I am being a complete tool or anything.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It connects as a media device and it's rooted and has usb debugging enabled. When I go into the tablet on the computer there's no backup folder under clockworkmod. I can enter recovery mode and all my backups show up but I can't access the backups when it's connected to the computer. I read somewhere that clockworkmod puts their backups in /data/media to prevent people from messing things up I guess but the adb pull method gives me that error. I don't know what else to do besides buying an otg cable and hooking up a usb mouse.
OK, yeah, I can't think of anything. When you're in recovery mode, is there a way to push files to the computer within recovery? I have never dealt with CWM, as I used TWRP on my kindle fire, and haven't added a bootloader to my nexus 7 yet.
Sent from my Nexus 7 using Tapatalk
jma9454 said:
OK, yeah, I can't think of anything. When you're in recovery mode, is there a way to push files to the computer within recovery? I have never dealt with CWM, as I used TWRP on my kindle fire, and haven't added a bootloader to my nexus 7 yet.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Not that I know of. When the tablet is in recovery mode it won't connect to the computer.
You can use adb in cwm recovery so no problem to download everything to computer.
One more thing I can try to recommend, and I'll get more information on this, is that there was an "app" called terminal, and you might be able to push the files you want into your computer from that. Give me a few hours while I contact someone that knows about that app to see if it would work on the nexus 7 and where to find it.
--EDIT--
Never mind, that would require keyboard input from you. I don't know what I was thinking. If there isn't a way to mount everything from CWM then I don't know what else I can do for you. Sorry.
Sent from my Nexus 7 using Tapatalk
jkkk88 said:
You can use adb in cwm recovery so no problem to download everything to computer.
Click to expand...
Click to collapse
So you're saying even though the adb pull method won't work when the tablet's on it will mysteriously work when in recovery? I don't see why that would make a difference. I feel the files I'm looking for might be in a different folder than /data/media/clockworkmod/backup or /sdcard/clockworkmod/backup.
Boot into CWM recovery mode, connect n7 to computer with USB cable and do what do you need. Adb daemon is started in CWM recovery automatically without any user interaction and n7 setting. I didn't tried it yet but there is command "adb backup <switches>" you can try to put content of n7 to computer or use standard adb commands. As I don't use nandroid backups I can't say where they are located but when you issue
Code:
adb pull /sdcard
and
Code:
adb pull /data
you will find them in you computer.
On n7 GSM here is output of some commands in recovery mode (in my case twrp but cwm will be the same):
Code:
[[email protected] ~]$ adb shell
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)~ # mount /dev/block/mmcblk0p3 /system
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p10 on /data type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /sdcard type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p5 on /cache type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
# mount point fstype device
#/sdcard datamedia /dev/null
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
/radio ext4 /dev/block/platform/sdhci-tegra.3/by-name/RDO
/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
~ # ls -l /dev/block/platform/sdhci-tegra.3/by-name/APP
lrwxrwxrwx 1 root root 20 Nov 1 08:36 /dev/block/platform/sdhci-tegra.3/by-name/APP -> /dev/block/mmcblk0p3
~ # mount /dev/block/mmcblk0p3 /system
jkkk88 said:
Boot into CWM recovery mode, connect n7 to computer with USB cable and do what do you need. Adb daemon is started in CWM recovery automatically without any user interaction and n7 setting. I didn't tried it yet but there is command "adb backup <switches>" you can try to put content of n7 to computer or use standard adb commands. As I don't use nandroid backups I can't say where they are located but when you issue
Code:
adb pull /sdcard
and
Code:
adb pull /data
you will find them in you computer.
On n7 GSM here is output of some commands in recovery mode (in my case twrp but cwm will be the same):
Code:
[[email protected] ~]$ adb shell
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)~ # mount /dev/block/mmcblk0p3 /system
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p10 on /data type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /sdcard type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p5 on /cache type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
# mount point fstype device
#/sdcard datamedia /dev/null
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
/radio ext4 /dev/block/platform/sdhci-tegra.3/by-name/RDO
/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
~ # ls -l /dev/block/platform/sdhci-tegra.3/by-name/APP
lrwxrwxrwx 1 root root 20 Nov 1 08:36 /dev/block/platform/sdhci-tegra.3/by-name/APP -> /dev/block/mmcblk0p3
~ # mount /dev/block/mmcblk0p3 /system
Click to expand...
Click to collapse
Ok I figured it out. The folder I was trying to pull really didn't exist. I just did adb shell to find what files were in there but I can't find the autorap files I was looking for. They may have gotten deleted.

Categories

Resources