Develop Bugs

Mount points?

What are the mount point for the phone? Making a file to add capability to the Android kitchen so you guys can do the basics quicker.

hasoon2000 said:
What are the mount point for the phone? Making a file to add capability to the Android kitchen so you guys can do the basics quicker.
Click to expand...
Click to collapse
which one are you after? i have all the mount block points
---------- Post added at 08:11 PM ---------- Previous post was at 08:07 PM ----------
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p28
/data ext4 /dev/block/mmcblk0p26
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p25
/misc emmc /dev/block/mmcblk0p17
/devlog ext4 /dev/block/mmcblk0p29
/sd-ext vfat /dev/block/mmcblk1

Lloir said:
which one are you after? i have all the mount block points
---------- Post added at 08:11 PM ---------- Previous post was at 08:07 PM ----------
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p28
/data ext4 /dev/block/mmcblk0p26
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p25
/misc emmc /dev/block/mmcblk0p17
/devlog ext4 /dev/block/mmcblk0p29
/sd-ext vfat /dev/block/mmcblk1
Click to expand...
Click to collapse
Thanks. ro.product.device is primo, right?

hasoon2000 said:
Thanks. ro.product.device is primo, right?
Click to expand...
Click to collapse
PrimoU for the gsm version and PrimoC for the CDMA version

SGN2 N7100 contents of efs

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.

[Q] Partition table for i9250 (Data forensics / recovery)

What's the partition table layout for the i9250? Is it the same across different ROMS generally? I'm on Cyanogenmod11; 4.4.4 kitkat.
I accidently deleted more than I should of with factory wipe... I need to know the partition table layout to recovery data. Is it 512kb sectors or 4096kb? Cylinders? Heads?
Here's the rest of my investigations into this:
So far I'm using this guide:
http://www.df.lth.se/~jokke/androidfilerecovery/
Which references adb shell su -c "cat /dev/block/mmcblk0" | pv > mmcblk0.raw but running this from recovery (TWRP) results in a zero file. Running it from the system booted ends up with a ~16gb partition table that makes no sense to testdisk. Should I search for info on what the partition structure should be?
What should I be searching for for more info? Is a thread from July too old to bump:
http://forum.xda-developers.com/show...1503595&page=7
Should I be approaching it from a linux point of view, plugging the phone in a dd if= / of= as if it's a USB drive?
TWRP has the option to mount... but on that page there is no button to click to actually mount the partitions. Maybe I should search for help with TWRP recovery. Not sure where to start.
The linux dd command doesn't seem to be possible anymore as the phone doesn't seem to mount as a drive anymore - it isn't listed by sudo fdisk -l
Keywords for searching seem to be mmcblk0, maybe EFI GPT, testdisk? The guide is quite old... should I even be using testdisk these days? build is CM11, maguro 4.4.4 KTU84Q, 3rd aug 2014, kernel 3.0.101
cat /cache/recovery/last_log (summary)
Code:
I:Settings storage is '/data/media/0'
I:Processing '/misc'
I:Processing '/boot'
I:Processing '/recovery'
I:Processing '/sbl'
I:Processing '/xloader'
I:Processing '/radio'
I:Processing '/efs'
I:Processing '/usb-otg'
I:Created '/usb-otg' folder.
Updating partition details...
I:Data backup size is 325MB, size: 13648MB, used: 326MB, free: 13158MB, in data/media: 0MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Unmounting main partitions...
Partition Logs:
/system | /dev/block/mmcblk0p10 | Size: 643MB Used: 495MB Free: 147MB Backup Size: 495MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p10
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/cache | /dev/block/mmcblk0p11 | Size: 425MB Used: 10MB Free: 414MB Backup Size: 10MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p11
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/data | /dev/block/mmcblk0p12 | Size: 13648MB Used: 326MB Free: 13158MB Backup Size: 325MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media/0
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p12
Display_Name: Data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media/0
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/misc | /dev/block/mmcblk0p5 | Size: 4MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p5
Display_Name: misc
Storage_Name: misc
Backup_Path: /misc
Backup_Name: misc
Backup_Display_Name: misc
Storage_Path: /misc
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/boot | /dev/block/mmcblk0p7 | Size: 8MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p7
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/recovery | /dev/block/mmcblk0p8 | Size: 11MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p8
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl | /dev/block/mmcblk0p2 | Size: 3MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p2
Display_Name: sbl
Storage_Name: sbl
Backup_Path: /sbl
Backup_Name: sbl
Backup_Display_Name: sbl
Storage_Path: /sbl
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/xloader | /dev/block/mmcblk0p1 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p1
Display_Name: xloader
Storage_Name: xloader
Backup_Path: /xloader
Backup_Name: xloader
Backup_Display_Name: xloader
Storage_Path: /xloader
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/radio | /dev/block/mmcblk0p9 | Size: 16MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p9
Display_Name: radio
Storage_Name: radio
Backup_Path: /radio
Backup_Name: radio
Backup_Display_Name: radio
Storage_Path: /radio
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/efs | /dev/block/mmcblk0p3 | Size: 20MB
Flags: Can_Be_Wiped Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p3
Display_Name: EFS
Storage_Name: EFS
Backup_Path: /efs
Backup_Name: efs
Backup_Display_Name: EFS
Storage_Path: /efs
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/usb-otg | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
Primary_Block_Device: /dev/block/sda1
Alternate_Block_Device: /dev/block/sda
Display_Name: USB OTG
Storage_Name: USB OTG
Backup_Path: /usb-otg
Backup_Name: usb-otg
Backup_Display_Name: USB OTG
Storage_Path: /usb-otg
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
Code:
TestDisk 6.14, Data Recovery Utility, July 2013
Christophe GRENIER <[email protected]>
http://www.cgsecurity.org
Disk again-mmcblk0.raw - 15 GB / 14 GiB
CHS 1917 255 63 - sector size=512
>[ Analyse ] Analyse current partition structure and search for lost partitions
[ Advanced ] Filesystem Utils
[ Geometry ] Change disk geometry
[ Options ] Modify options
[ Quit ] Return to disk selection
Note: Correct disk geometry is required for a successful recovery. 'Analyse'
process may give some warnings if it thinks the logical geometry is mismatched.
I've tried a few apps to recover too. DiskDigger found a few files... I got excited... but when it wrote out the files they didn't appear on the drive...
it's a bunch easier when you can eject the sdcard that's for sure!

There already is a complete guide on how to do this. Might help to search in the future .
http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705

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