Database Info

resolved problem after flashing efs partition

hello
i have this cel i9003 , i have before the kpu clean ..
i flash like stock ...
now i dont have efs folder , or partition problem
see my terminal ...:
Code:
# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/mmcblk0p3 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/ui
d/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/
rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
debugfs /debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,no
diratime,uid=1000,gid=1015,fmask=0002,dmask=0002,a llow_utime=0020,codepage=cp437
,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
how i can to repair that issue?

You said you want to go to stock rom from clean kpu?

my firm was kpu clean , i make root , cmw , and ext4 internal sd card
i wanted installing this firm :
http://forum.xda-developers.com/showthread.php?t=1449649
i couldn t installing this firm getting many error
so i downgrade my cel with this firm stock kpe with odin
with this tut:
http://www.wuala.com/bees/KPE%20-%20KPU?lang=es
after my cel flashing , i lost my imei , base band ,for that reason i post my termimal
i dont understand why i lost my efs partition ...
i have backup of nv_data.bin
the partition of efs is stl3 ?
thank you to help me

no body know?

i repair this issue my self !!!!
i repair this issue myself :
i find in the web this file efs.tar , just with odin i put in pda and i have back imei general and base band .
now i have this fake imei : Fake IMEI (usually 004999010640000)
after just to replace your backup nv_data.bin with root explorer to get back your imei original
tut here :http://forum.xda-developers.com/showthread.php?t=859914
have fun !!!!!
after make that you must have backup the st3 bloc
like that :
HTML:
su
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img (OR)
busybox cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
this is the partition of efs.rfs

i have almost similar problem. my phone is showing blank IMEI number . now i have flashed your efs.tar but the IMEI field is still completely blank. i dont understand what i did wrong. can you please tell me what was your firmware version when you flashed the efs.tar ?

tamoghno said:
i have almost similar problem. my phone is showing blank IMEI number . now i have flashed your efs.tar but the IMEI field is still completely blank. i dont understand what i did wrong. can you please tell me what was your firmware version when you flashed the efs.tar ?
Click to expand...
Click to collapse
hello !!!
can you show your mount ?
su and mount ...with terminal
if you haven t the line with efs so your particion is bad ...
if you have the line so your nv_data.bin is here but corrupt
use adb shell with your computer if you can
maybe better to flash back with firm kpe
do you have backup of nv_data.bin ?
and when you get mode downloading did you put this file efs.tar in pda ..?
hope i can to help you

this is output of my mount command :
export PATH=/data/local/bin:$PATH
$ $su
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
debugfs /debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
#
i can see the efs partition in root explorer also so i guess the partition is ok.
i also have backup of efs folder .
i have downgraded to XXKB3 2.2 to try to restore the IMEI .
i put the efs.tar in pda and flashed as usual . should i tick the "phone efs clear" option ?
did your phone show completely blank imei or did it show "null" ?

cool you have efs particion good
oki you have partition good !!!
so i sugest you flash again with kpe push case efs clear
i give you the file : http://www.wuala.com/bees/KPE%20-%20KPU?lang=es
you flash pit first , when you have blank screen , you take of the batery .
after you flash firm like we make all time
boot loader = apboot
pda = code
phone =modem
csc=csc
push case efs clear
reboot
when you see all done and the cel is oki
get mode download again
put the most important file : efs.tar in pda odin
you should to reboot , and now you have generic imei ...0049
you put this file with odin to get root and cmw:
http://forum.xda-developers.com/showthread.php?t=1351056
install root explorer
after you need to replace you nv_data.bin and delete nv_data.bin.md5 dont worry the systeme make it again !!!!
i know its very difficult to find info about efs particion or other thing for that reason i share that for all , you dont need expensive machine you can make all with odin only with the possibility to get mode download ...
dont mess your bootloader ...
have fun

my hh was imei unknown n baseband also...
how to fix it...
# su
su
# mount
mount
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=111)
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)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/stl9 on /system type rfs (rw,relatime,vfat,llw,check=no,gid/uid/rwx,i
ocharset=utf8)
/dev/block/mmcblk0p3 on /data type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=
no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl10 on /dbdata type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no
,gid/uid/rwx,iocharset=utf8)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
debugfs on /debug type debugfs (rw,relatime)
/dev/block/stl11 on /cache type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,
gid/uid/rwx,iocharset=utf8)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,n
oatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codep
age=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard)
/dev/block/vold/179:17 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,n
odev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_uti
me=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-r
o)
/dev/block/vold/179:17 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,no
exec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020
,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k
,mode=000)
#
what should i do ?

i still dont have the imei after i flashed efs.tar
what should i do ?
i already flashed xxkpe firmware and flashed efs.tar.

celica7 said:
oki you have partition good !!!
.....
put the most important file : efs.tar in pda odin
you should to reboot , and now you have generic imei ...0049
Click to expand...
Click to collapse
Hey dude, after flashing efs.tar there is no generic imei..
Any idea? :crying:

cheeyeen said:
Hey dude, after flashing efs.tar there is no generic imei..
Any idea? :crying:
Click to expand...
Click to collapse
Me too

I too flashed this. But nothing has happened

Same issue
C:\Program Files (x86)\Android\android-sdk\platform-tools>sets
'sets' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Android\android-sdk\platform-tools>sets android
'sets' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Android\android-sdk\platform-tools>su
'su' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Android\android-sdk\platform-tools>/system/bin/sh
The system cannot find the path specified.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # /system/bin/sh
/system/bin/sh
# sets diag mode
sets diag mode
sets: not found
# mount
mount
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=111)
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)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/stl9 on /system type rfs (ro,relatime,vfat,log_off,check=no,gid/uid/r
wx,iocharset=utf8)
/dev/block/stl3 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid
/uid/rwx,iocharset=cp437)
/dev/block/mmcblk0p3 on /data type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=
no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl10 on /dbdata type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=or
dered,noauto_da_alloc)
/dev/block/stl11 on /cache type rfs (rw,relatime,vfat,llw,check=no,gid/uid/rwx,i
ocharset=utf8)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
debugfs on /debug type debugfs (rw,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,n
oatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codep
age=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard)
/dev/block/vold/179:17 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,n
odev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_uti
me=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-r
o)
/dev/block/vold/179:17 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,no
exec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020
,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k
,mode=000)
#
I have efs folder. But my IMEI is missing.
Did any resolve this issue.

Testing for A.I

Thread now changed to testing for a.i
http://sourceforge.net/projects/team...r.zip/download
test on any rom, buildprop and init.d tweaks ONLY!

Ok, now that we are talking about time management, you are wasting mine. If this is not something that you can provide OP, then don't respond.
Thread Cleaned. Let's try this again.

Here's what I sent you back in October. I'll validate my current ICS (AOKPm6r5) mounts when I get home in an hour or two and give you that in another post.
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock2 /system yaffs2 ro,noatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/void/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/void/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Click to expand...
Click to collapse
The part the was problematic was that the sdcard mount wasn't the last... 179:1 is the sdcard, but there's a 179:2, per this:
[email protected]:/etc/init.d $ ls /dev/block/vold/*
ls /dev/block/vold/*
/dev/block/vold/179:0
/dev/block/vold/179:1
/dev/block/vold/179:2
Click to expand...
Click to collapse
Anyways, I'll check both of those again in another hour or two. If I remember.

Re: Need your mount ARGGGGHHHH
What exactly is this storage swap that you speak of.
Sent from my Nexus 4 using xda app-developers app

During boot:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell mount
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,mode=600 0 0
proc /proc proc rw,noatime 0 0
sysfs /sys sysfs rw,noatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock2 /system yaffs2 ro,noatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /radio yaffs2 rw,noatime 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,noatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
Click to expand...
Click to collapse
After boot is completed:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell mount
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,mode=600 0 0
proc /proc proc rw,noatime 0 0
sysfs /sys sysfs rw,noatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock2 /system yaffs2 ro,noatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /radio yaffs2 rw,noatime 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,noatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard 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 0 0
/dev/block/vold/179:1 /mnt/secure/asec 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 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Click to expand...
Click to collapse
Apparently wiping my sdcard yesterday fixed the extra partition issue though.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell ls /dev/block/vold/*
/dev/block/vold/179:0
/dev/block/vold/179:1
Click to expand...
Click to collapse
But that doesn't mean other people (like my wife) might not still have issues with an extra partition at the end.

Theraze said:
During boot:After boot is completed:Apparently wiping my sdcard yesterday fixed the extra partition issue though.But that doesn't mean other people (like my wife) might not still have issues with an extra partition at the end.
Click to expand...
Click to collapse
Thanks!!! what is the rom your using?

anoymonos said:
What exactly is this storage swap that you speak of.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
when your on ICS or JB your apps will automatically go to internal storage and it will fill internal up real quick
this script will make your phone think the sdcard is your internal storage and your internal storage your sdcard. problem solved
however because JB is moving onto multiuser devices i have to redo the script which is what im working

dsexton702 said:
Thanks!!! what is the rom your using?
Click to expand...
Click to collapse
That's AOKP milestone 6 revision 5.

wanna test the new tweaks from a.i for me? just select buildprop and init.d tweaks for this test
URL will be back up in 5 min
more than welcome to describe any details in this thread

dsexton702 said:
wanna test the new tweaks from a.i for me? just select buildprop and init.d tweaks for this test
http://sourceforge.net/projects/teamacid/files/dsexton702/A.I/Adrenaline-Injector.zip/download
more than welcome to describe any details in this thread
Click to expand...
Click to collapse
I see a multi core tweak in etc. Is this cross platform yet or still for the 4g only?

hechoen said:
I see a multi core tweak in etc. Is this cross platform yet or still for the 4g only?
Click to expand...
Click to collapse
its not only for the 4g, the multi core will be rebuilt in the next day or so to work for all multi core devices
as for the test package download the new link i post because its the real test package lol

Ok this link is the zip i need you to test http://sourceforge.net/projects/teamacid/files/dsexton702/A.I/Adrenaline-Injector.zip/download
remember just init.d and buildprop for now

Just flashed over CM 10.1. It boots and seems to be running fine. No problems with aroma either. Not the best ROM to run a full test on as wifi is borked, it doesn't deep sleep and my sim card is in my other phone . lol I'm most likely gonna flash the internal2sd just to see what it does. If that's a bad idea it's on me. Just to curious not too. When you get the multicore done let me know I'd be happy to flash it on my Skyrocket for you.

hechoen said:
Just flashed over CM 10.1. It boots and seems to be running fine. No problems with aroma either. Not the best ROM to run a full test on as wifi is borked, it doesn't deep sleep and my sim card is in my other phone . lol I'm most likely gonna flash the internal2sd just to see what it does. If that's a bad idea it's on me. Just to curious not too. When you get the multicore done let me know I'd be happy to flash it on my Skyrocket for you.
Click to expand...
Click to collapse
lol you can try the internal2external but because of the multi user options now the it will just output that its not a real file or directory
it will be fixed soon though and you will be the first i tell about the multi core, speaking of that, could you send me all the .txt files in /system/etc for me on your skyrocket

dsexton702 said:
lol you can try the internal2external but because of the multi user options now the it will just output that its not a real file or directory
it will be fixed soon though and you will be the first i tell about the multi core, speaking of that, could you send me all the .txt files in /system/etc for me on your skyrocket
Click to expand...
Click to collapse
Sub folders as well or just the two in system/etc ?

hechoen said:
Sub folders as well or just the two in system/etc ?
Click to expand...
Click to collapse
whatever .sh or .txt files in your etc folder i wanna look at please no folders just scripts in the etc folder

dsexton702 said:
whatever .sh or .txt files in your etc folder i wanna look at please no folders just scripts in the etc folder
Click to expand...
Click to collapse
PM sent.

Direction for this thread has changed refer to OP

[Q] Wiped /cache now unable to access /sdcard

I screwed up a bit here. I was using the stock recovery to format my /cache partition but about 5 minutes in it froze. Figuring that something had went wrong i hard rebooted the phone and now when I boot it appears that my internal sdcard partition has disappeared.
In adb I tried to cd into /sdcard and the directory is missing entirely
Code:
/system/bin/sh: cd: /sdcard: No such file or directory
same thing here
Code:
[email protected]:/ $ cd /storage/emulated/legacy
/system/bin/sh: cd: /storage/emulated/legacy: No such file or directory
My mountpoinits show no sign of sdcard anywhere
Code:
127|[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/dm-0 /mnt/asec/com.trueaxis.jetcarstunts-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.tribok.android.livewallpaper.nightflare.pro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.robbers.clock-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
If anyone has any suggestions I would appreciate them. I would really like to be able to recover my data from the device before I wipe it.

Alias.TDP said:
I screwed up a bit here. I was using the stock recovery to format my /cache partition but about 5 minutes in it froze. Figuring that something had went wrong i hard rebooted the phone and now when I boot it appears that my internal sdcard partition has disappeared.
.
Click to expand...
Click to collapse
Here you go, just flash cache.img on this thread (method 2)
http://forum.xda-developers.com/showthread.php?t=2513701
Your data may be lost at all so, if it does not work, then use flash-all method (method 1)

GUGUITOMTG4 said:
Here you go, just flash cache.img on this thread (method 2)
http://forum.xda-developers.com/showthread.php?t=2513701
Your data may be lost at all so, if it does not work, then use flash-all method (method 1)
Click to expand...
Click to collapse
Thanks dude that worked

Alias.TDP said:
Thanks dude that worked
Click to expand...
Click to collapse
Glad it's fixed. Keep that thread in the first aid kit:cyclops:

Remember - NEVER reboot your phone when it's trying to wipe. Some of these phones take an exceptionally long time to wipe depending on your recovery.

How to verify 'discard' flag working in fstab.cardhu?

I have TF700 running Crombi-KK F2FS on data, and added the 'discard' flag to fstab.cardhu to (hopefully) ensure trim of flash memory. Is there some way to verify that the discard function is working?

gc2712 said:
I have TF700 running Crombi-KK F2FS on data, and added the 'discard' flag to fstab.cardhu to (hopefully) ensure trim of flash memory. Is there some way to verify that the discard function is working?
Click to expand...
Click to collapse
The fstab,cardhu gets modified by my boot process depending upon what you chose. I intentionally remove the discard option as it cause me bootloops.
However to check if yours has persistd ( and it may have if you haven't been anywhere near data2sd or rom2sd) is run the following in a terminal
mount | grep /dev/block/*
look for the /data and you will see what options it has been mounted with, interested to see if discard has persisted and why it won't work on my device

sbdags said:
The fstab,cardhu gets modified by my boot process depending upon what you chose. I intentionally remove the discard option as it cause me bootloops.
However to check if yours has persistd ( and it may have if you haven't been anywhere near data2sd or rom2sd) is run the following in a terminal
mount | grep /dev/block/*
look for the /data and you will see what options it has been mounted with, interested to see if discard has persisted and why it won't work on my device
Click to expand...
Click to collapse
I tried running the above command in terminal. Without su just got 'permssion denied' on all. With su there was no response in terminal at all So just tried:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc 0 0
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
com.android.chrome_cache /data/data/com.android.chrome/cache tmpfs rw,relatime,size=102400k 0 0
mobi.mgeek.TunnyBrowser_cache /data/data/mobi.mgeek.TunnyBrowser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
Looks like the discard flag was just ignored? Any way to make it persist?

gc2712 said:
I tried running the above command in terminal. Without su just got 'permssion denied' on all. With su there was no response in terminal at all So just tried:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc 0 0
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
com.android.chrome_cache /data/data/com.android.chrome/cache tmpfs rw,relatime,size=102400k 0 0
mobi.mgeek.TunnyBrowser_cache /data/data/mobi.mgeek.TunnyBrowser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
Looks like the discard flag was just ignored? Any way to make it persist?
Click to expand...
Click to collapse
You can't edit the fstab directly as it gets replaced by the kernel on every boot.
so go to /system/boot/print.d
Open 30fstab-f2fs in a text editor
On this line change it from
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime,//;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
to
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime/discard/;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
Reboot but be prepared for a bootloop that you can only fix by undoing what you just did.... Have a nandroid ready to go

sbdags said:
You can't edit the fstab directly as it gets replaced by the kernel on every boot.
so go to /system/boot/print.d
Open 30fstab-f2fs in a text editor
On this line change it from
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime,//;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
to
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime/discard/;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
Reboot but be prepared for a bootloop that you can only fix by undoing what you just did.... Have a nandroid ready to go
Click to expand...
Click to collapse
Just a cautious check on syntax before I do this. Every other flag on that line is of the form: ;s/flagx,// , yet in this instance you suggest just forward slash after 'nodiratime', ending with just a forward slash instead of two forward slashes. Is this intentional or should the syntax be: //;s/nodiratime,//;s/discard,//;s/noauto_da_alloc, etc.
Although I've used linux for years (Since Red Hat 7!) and have just enough knowledge to follow instructions to edit scripts, I still don't grasp syntax very well. (Just enough to know if I get it wrong things screw up
Also, if I save a copy of the 30fstab-f2fs file to sdcard can I simply copy it back using TWRP (latest) instead of a full nandroid restore?
Sorry if these are dumb questions. Your help is greatly appreciated.

gc2712 said:
Just a cautious check on syntax before I do this. Every other flag on that line is of the form: ;s/flagx,// , yet in this instance you suggest just forward slash after 'nodiratime', ending with just a forward slash instead of two forward slashes. Is this intentional or should the syntax be: //;s/nodiratime,//;s/discard,//;s/noauto_da_alloc, etc.
Although I've used linux for years (Since Red Hat 7!) and have just enough knowledge to follow instructions to edit scripts, I still don't grasp syntax very well. (Just enough to know if I get it wrong things screw up
Also, if I save a copy of the 30fstab-f2fs file to sdcard can I simply copy it back using TWRP (latest) instead of a full nandroid restore?
Sorry if these are dumb questions. Your help is greatly appreciated.
Click to expand...
Click to collapse
Yes it is my correct - my edit will replace nodiratime with discard Your edit will look for discard (which isn't there) and replace it with nothing
Personally I'd do a full nandroid but yes as long as you can partially recover then that single file should be ok.

sbdags said:
Yes it is my correct - my edit will replace nodiratime with discard Your edit will look for discard (which isn't there) and replace it with nothing
Personally I'd do a full nandroid but yes as long as you can partially recover then that single file should be ok.
Click to expand...
Click to collapse
Many thanks (red face here). I'll give it a try today and do the full nandroid backup just in case. Will report back the result.

Well! That was a debacle.:crying:
Changed to:
"$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime/discard/;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu "
It didn't boot loop, but eventually booted into a screen which said, "Encryption Unsuccesful. Encryption was interrupted and can't complete. As a result your tablet is no longer accessible" etc....
Thank god for the nandroid! When I reflashed the nandroid, TWRP reported that it was formatting system to ext4 even though it was originally F2FS. However when I rebooted and checked in terminal it indicated that the FS on system was in fact F2FS.
# mount |grep /dev/block/mmcblk0p8
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
No idea why, but its all working again, but alas, no 'discard' option. Could this be the reason?
[email protected]:/ # fstrim -v /data
fstrim: FITRIM: Inappropriate ioctl for device
Don't know what that error means and google wasn't my friend this time.

gc2712 said:
I tried running the above command in terminal. Without su just got 'permssion denied' on all. With su there was no response in terminal at all So just tried:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc 0 0
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
com.android.chrome_cache /data/data/com.android.chrome/cache tmpfs rw,relatime,size=102400k 0 0
mobi.mgeek.TunnyBrowser_cache /data/data/mobi.mgeek.TunnyBrowser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
Looks like the discard flag was just ignored? Any way to make it persist?
Click to expand...
Click to collapse
Here is my /dev/block* information:
Code:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0
[COLOR="RoyalBlue"]/dev/block/mmcblk0p8 /datai ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0[/COLOR]
[COLOR="RoyalBlue"]/dev/block/mmcblk1p2 /data f2fs rw,noatime,background_gc=on,discard,user_xattr,acl,errors=panic,active_logs=6 0 0[/COLOR]
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
browser_cache /data/data/com.android.browser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:49 /Removable/MicroSD texfat rw,relatime,uid=1000,gid=1015,umask=0000,
allow_utime=0022,nls=utf8,min_prealloc_size=64k,readahead=4M,discard,errors=continue 0 0
[email protected]:/ #
It seems to stick with the "discard" mounting flag...

LetMeKnow said:
Here is my /dev/block* information:
Code:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0
[COLOR="RoyalBlue"]/dev/block/mmcblk0p8 /datai ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0[/COLOR]
[COLOR="RoyalBlue"]/dev/block/mmcblk1p2 /data f2fs rw,noatime,background_gc=on,discard,user_xattr,acl,errors=panic,active_logs=6 0 0[/COLOR]
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
browser_cache /data/data/com.android.browser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:49 /Removable/MicroSD texfat rw,relatime,uid=1000,gid=1015,umask=0000,
allow_utime=0022,nls=utf8,min_prealloc_size=64k,readahead=4M,discard,errors=continue 0 0
[email protected]:/ #
It seems to stick with the "discard" mounting flag...
Click to expand...
Click to collapse
What is the additional partition mmcblk1p2 for data? The partition mmcblk0p8 which on my system is my data partition has been located on /datai and is ext4 on yours. How does that happen? Are you using data2sd or something?

gc2712 said:
What is the additional partition mmcblk1p2 for data? The partition mmcblk0p8 which on my system is my data partition has been located on /datai and is ext4 on yours. How does that happen? Are you using data2sd or something?
Click to expand...
Click to collapse
Yes, you are correct. I am using Data2sd. I am running f2fs on my external data partition (/dev/block/mmcblk1p2) and leave my internal data partition as ext4 because it is just a backup data partition that I actually never use it.

LetMeKnow said:
Yes, you are correct. I am using Data2sd. I am running f2fs on my external data partition (/dev/block/mmcblk1p2) and leave my internal data partition as ext4 because it is just a backup data partition that I actually never use it.
Click to expand...
Click to collapse
Ah! Mystery solved then. sbdags was right then that with internal F2FS /data the discard option will bootloop, or, as in my case boot and trash the data partition requiring factory reset. Hopefully, the F2FS file system and KitKat manage garbage collection well enough without fstrim/discard as I don't want to reinstall again as ext4 at this point. Perhaps someone will make it work in the future.

gc2712 said:
Ah! Mystery solved then. sbdags was right then that with internal F2FS /data the discard option will bootloop, or, as in my case boot and trash the data partition requiring factory reset. Hopefully, the F2FS file system and KitKat manage garbage collection well enough without fstrim/discard as I don't want to reinstall again as ext4 at this point. Perhaps someone will make it work in the future.
Click to expand...
Click to collapse
Hmm, I did help one user using f2fs on internal data partition with discard flag on JB Rom. He had no issue until moving on with KK Rom. If I can have the tf700 long enough, I will test it out on the internal data so we can rule it out...
Garbage collection is to reclaim your locked up or old memory that old apps keeps holding on without using them. I believe that is what it is for but I may be wrong...

efs partition overridden

Hey xda-developers,
I got a new nexus 5 from Google (RMA) and tried to restore the nandroid backup (with twrp) from the old one to the new one. My problem is that I do not have backed up the efs partition of the new phone. So now my IMEI is 0 and I do not have a mobil connection. I read about efs but before handling this problem my first question is:
If I type 'mount' (as root via adb at run time) on the old nexus 5 there is nothing about a efs partition/mount point?
[email protected]:/ #
[email protected]:/ # mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nomblk_io_submit,nodelalloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/dm-0 /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Is it possible to use the old efs-partition and just replace the imei? I tried to mount the partition but that didn't work also...It's a paranoid android btw

bricked. said:
Hey xda-developers,
I got a new nexus 5 from Google (RMA) and tried to restore the nandroid backup (with twrp) from the old one to the new one. My problem is that I do not have backed up the efs partition of the new phone. So now my IMEI is 0 and I do not have a mobil connection.
Click to expand...
Click to collapse
I sent you a private message.

bitdomo said:
I sent you a private message.
Click to expand...
Click to collapse
Thank you so much bitdomo! #hero

bitdomo said:
I sent you a private message.
Click to expand...
Click to collapse
I have the same problem, my nexus 5 has returned from assistance and I restore a nandroid backup, but also the efs partition was restored and now the IMEI is 0 and there is no signal... Please help me :crying: