SGN2 N7100 contents of efs - Galaxy Note II Q&A, Help & Troubleshooting

Using root explorer what are the files located within efs can anyone list it with its values, for example :- efs.tar 2MB
Just double checking to know wheather i still have the efs in my device after corrupting the efs when flashing back to stock 4.1.2 and this today after doing a cwm backup was reading the recovery log:
Recovery.log - (truncated)
Starting recovery on Sun Dec 8 01:26:19 2013 (UTC)
framebuffer: fd 4 (720 x 1280)
PhilZ Touch 5
CWM Base version: v6.0.3.7
I:Build version: 5.11.1 - n710x-i317M-T889
recovery filesystem table
==================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /devblock/mmcblk0p3 (null) 0
2 /boot emmc /dev/block/mmcblk0p8 (null) 0
3 /recovery emmc /dev/block/mmcblk0p9 (null) 0
4 /cache ext4 /dev/block/mmcblk0p12 (null) 0
5 /system ext4 /dev/block/mmcblk0p13 (null) 0
6 /data ext4 /dev/block/mmcblk0p16 (null) -16384
7 /preload ext4 /dev/block/mmcblk0p14 (null) 0
8 /modem emmc /dev/block/mmcblk0p10 (null) 0
9 /sdcard datamedia /dev/null (null) 0
10 /external_sd auto /dev/block/mmcblk1p1 (null) 0
11 /sd-ext ext4 /dev/block/mmcblk1p2 (null) 0
and it goes on and on.......
But the above is the one bothering me showing null null and null..
Am able to use the phone now of course after flashing mf1 modem but the question is do i still have my efs.

Related

file system of sgs3?

Out of pure curiousity, what kind of file system is run on the SGS3. my last phone, the epic 4g was of course on RFS and had to be converted over into a MTD/ext4 format to get more preformance in the end. Is the Sgs 3 natively MTD ready? or will there be a conversion for Cyanogen mod at some point over to MTD.
metalblaster said:
Out of pure curiousity, what kind of file system is run on the SGS3. my last phone, the epic 4g was of course on RFS and had to be converted over into a MTD/ext4 format to get more preformance in the end. Is the Sgs 3 natively MTD ready? or will there be a conversion for Cyanogen mod at some point over to MTD.
Click to expand...
Click to collapse
Mtd is the partition not the file system.. BTW its mtd/yaffs2.
Sent from my SPH-L710 using xda app-developers app
The stock filesystem of most new Android devices is ext4.
From
Code:
cat /proc/mounts
Code:
/dev/block/mmcblk0p14 /system ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p15 /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0

[Q] Very Broken Note II - partitions, init.d, the works

So, where to start...
I rooted my Samsung Note II, and installed Frosty Jellybean. I was really hoping for the longpress back -> app kill like on cyanogen mod, and started switching roms, till I came across Omega. Not realizing how incompatible it was, I flashed anyway and lost radio. I immediately Odin'd back to stock and got radio back (efs / iemi fine). Then moved on to MyRom. Loved it, it was great, but then noticed duplications on my internal sd card....
the whole /0/ dir for 4.1.2, which at the time I thought was an error on my part from modding.... this is where I take a series of stupid moves
1) formatted the internal sd card with cwm.
2) reflashed odin using the pit file from SGH-t889V from this thread
This significantly hosed my phone, so I spent the weekend trying to understand how I could fix it without paying the warrenty deductible. I did a nandriod restore to a point right before I started modding, and finally got 4.1.1 to come up and not endlessly bootcycle. However, my internal SD card isn't mounting correctly (really at all), and I couldn't figure out how to use the fuse thing to get the vfat partition back and pointed to the right point in /dev/block/mmcblk3p?
So, I've triangled-away, now its a stock piece that
1) has no bluetooth
2) has no radio
3) will not come up as a usb device - the usb doesn't even see its there
-- UNLESS its in download mode, then comes up as a serial device
This leads me to believe that all the instancing scripts / settings that are supposed to run when the device powers on aren't coming up, though the init.d and fstab thingie look right(ish)
So, is this a lost cause - should I just make my claim, or is there some easy Heres-a-raw-dump-of-the-phone thing I have missed, that could get me back up and running?
Thanks,
** UPDATE **
I ran the firmware update through KIES and resolved this.,
So you have tried restoring the stock image?
Carbon 1.5 | Kroz Hue Brown Theme | Crack Flasher
odin restore
RonnieRuff said:
So you have tried restoring the stock image?
Carbon 1.5 | Kroz Hue Brown Theme | Crack Flasher
Click to expand...
Click to collapse
if I flash KIES_HOME_T889UVALL4_T889TMBALL4_598701_REV04_user_low_ship.tar.md5
it gets caught in a bootloop, I have to flash cwm to do a nandriod restore to before I started modding. that's where its at now.
fireupFront said:
if I flash KIES_HOME_T889UVALL4_T889TMBALL4_598701_REV04_user_low_ship.tar.md5
it gets caught in a bootloop, I have to flash cwm to do a nandriod restore to before I started modding. that's where its at now.
Click to expand...
Click to collapse
Try flashing that rom and then going into recovery mode [stock] and factory resetting before you boot into Android
Sent from my SGH-T889 using xda premium
ktetreault14 said:
Try flashing that rom and then going into recovery mode [stock] and factory resetting before you boot into Android
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Tried that as well...
if you went from a 4.2.x rom back to a 4.1.x rom u might need to flash the "restore sdcard after downgrade.zip" script. its a mandatory step
from reading your post it doesn't seem you have tried flashing that yet.
---------- Post added at 08:24 PM ---------- Previous post was at 08:16 PM ----------
restore sdcard after downgrade.zip link
look at the very bottom of the post under ATTACHED FILES
script
rlee008 said:
if you went from a 4.2.x rom back to a 4.1.x rom u might need to flash the "restore sdcard after downgrade.zip" script. its a mandatory step
from reading your post it doesn't seem you have tried flashing that yet.
---------- Post added at 08:24 PM ---------- Previous post was at 08:16 PM ----------
restore sdcard after downgrade.zip link
look at the very bottom of the post under ATTACHED FILES
Click to expand...
Click to collapse
You're right, I should have run that script then, but now... not so helpful:
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/mmcblk0p13 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p10 /firmware vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:17 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/dev/block #
>> no ramdisk <<
wifi
Keep in mind, I can't actually get to the device via usb, the only way I've even been able to adb to the device is wirelessly over wifi...
fireupFront said:
Keep in mind, I can't actually get to the device via usb, the only way I've even been able to adb to the device is wirelessly over wifi...
Click to expand...
Click to collapse
can you mount via recovery?
you said you were able to nandroid back to 4.1.1, but your internal sdcard wasn't mounting correctly ... try flashing the restore-sdcard. zip first, then nandroid back to your working 4.1.1 then flash the restore-sdcard.zip again and boot...
script
rlee008 said:
can you mount via recovery?
you said you were able to nandroid back to 4.1.1, but your internal sdcard wasn't mounting correctly ... try flashing the restore-sdcard. zip first, then nandroid back to your working 4.1.1 then flash the restore-sdcard.zip again and boot...
Click to expand...
Click to collapse
THe script can't run, /data/media is not writeable
I was able to get parted on the device and got this info:
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB TOMBSTONES
12 432MB 1774MB 1342MB ext4 CACHE
13 1774MB 3653MB 1879MB ext4 SYSTEM
14 3653MB 3674MB 21.0MB ext4 HIDDEN
15 3674MB 3683MB 8389kB OTA
16 3683MB 15.8GB 12.1GB ext4 USERDATA
the closest thing to this I've found on the web is here:
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB ext4 TOMBSTONES
12 432MB 1774MB 1342MB ext4 CACHE
13 1774MB 3653MB 1879MB ext4 SYSTEM
14 3653MB 3674MB 21.0MB ext4 HIDDEN
15 3674MB 3683MB 8389kB OTA
16 3683MB 15.8GB 12.1GB ext4 USERDATA
so it looks like my tombstones are messed up, which makes these logcat msgs make sense
Error kickstart 2029 Requested ID 16, file "/tombstones/qcks/efs1.bin"
39:35.2 Error kickstart 2029 ERROR: function: open_file:80 Unable to open input file /tombstones/
So I re partition ed the tombstone drive and got the vfat back up, but still no radio or bluetooth
Sent from my SGH-T889 using xda app-developers app

[Q]kitchen setup

need help here to setup dsixda kitchen.how to configure edify_defs in kitchen directory?here the mounting.my device smt211
# mount point fstype device device2
/system ext4 /dev/block/mmcblk0p14
/cache ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p17 length=-16384
/efs ext4 /dev/block/mmcblk0p6
/misc emmc misc
/boot emmc /dev/block/mmcblk0p9
/recovery emmc /dev/block/mmcblk0p10
/bootloader emmc /dev/block/mmcblk0p5
/modem emmc /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/preload ext4 /dev/block/mmcblk0p16
/custom ext4 /dev/block/mmcblk0p12

CyanogenMod how to download and install?

CyanogenMod how to download and install? anyone tell me how to install it on note 3 neo
You can install cyanogemod 13 of note 3 in your note 3 neo my friend said it supports
Has anyone tested this?
DhilipKumarIN said:
You can install cyanogemod 13 of note 3 in your note 3 neo my friend said it supports
Click to expand...
Click to collapse
are u sure??
trying this I think you have big chances to break your phone
Note 3 Neo mount points
/dev/block/mmcblk0p3 /efs
/dev/block/mmcblk0p9 /boot
/dev/block/mmcblk0p10 /recovery
/dev/block/mmcblk0p19 /cache
/dev/block/mmcblk0p18 /system
/dev/block/mmcblk0p21 /data
/dev/block/mmcblk1p1 /sdcard
/dev/block/mmcblk0p13 /modem
/dev/block/mmcblk0p20 /preload
Note 3 mount points
/dev/block/ mmcblk0p14 /boot
/dev/block/ mmcblk0p24 /cache
/dev/block/ mmcblk0p11 /efs
/dev/block/ mmcblk0p2 /modem
/dev/block/ mmcblk0p15 /recovery
/dev/block/ mmcblk0p23 /system
/dev/block/ mmcblk0p26 /data
Click to expand...
Click to collapse
+ the note 3 is a totally different device, different processor, different chipset, different display....
My frd said it supported,he as my note 3 neo now i sold it too him let u give it a try

Failed to mount '/odm' (Invalid argument)

Hey
I'm trying to install LineageOS 17.1 (or actually anything…) on my RM5G. But no matter what I do, it fails. Even directly directly after starting unofficial TWRP 3.4.1b-0324, I get an error message:
Code:
Updating partition details...
Failed to mount '/odm' (Invalid argument)
...done
Is it because of the broken (?) /odm line in /etc/fstab?
Code:
$ adb shell cat /etc/fstab
/dev/block/sda17 /data f2fs rw 0 0
/dev/block/sda10 /cache ext4 rw 0 0
/dev/block/dm-2 /system_root ext4 rw 0 0
/dev/block/dm-1 /vendor ext4 rw 0 0
/dev/block/dm-0 /product ext4 rw 0 0
/odm ext4 rw 0 0
/dev/block/sde4 /firmware vfat rw 0 0
/dev/block/sda2 /persist ext4 rw 0 0
/dev/block/sde5 /bt_firmware vfat rw 0 0
/dev/block/sde9 /dsp ext4 rw 0 0
/dev/block/sda13 /metadata ext4 rw 0 0
/dev/block/sde51 /spunvm vfat rw 0 0
/usb-otg vfat rw 0 0
I get that "Failed to mount '/odm' (Invalid argument)" all the time… Even after deleting /data or after a wipe and so also when trying to install a ROM.
I'm also attaching my "recovery.log" after I tried to install LineageOS.
Thx.
I get the failed to mount /odm but everything still flashes. I'm on Pixel Experience Plus ROM right now.
same here
i got the same error on RM5S for installing resurrection remix. It is not working. Anyone know what to do?
i fixed, i don't know how but i still try to root

Categories

Resources