Database Info

[Kernel] Siyah_I9305 Discussion..

As per some comments by G.K i thought it was going to be ported by now but things change , not sure whats
Happening ill leave it open incase we have some news regarding it.

btemtd said:
I spoke to Gohkan regarding porting his kernel to I9305 he said the only reason -not likely- is because he tried this before without owning the device and it was quite hard as he could not test it, especially when bugs arise it got quite frustrating for him. But he was more then happy to give a helping hand to any dev that would like to port his kernel. I guess the best way also is if there is a bug the Dev that ported the Kernel will need to Liase with Gohkan instead of all the users flooding him with bug reports. He mentioned Devs from US variant ported his kernel no problem. So if any of our devs would like to help, Let me know and I can speak to him or just message him and say "you are a dev and want to port his kernel where do we start". I am willing to help with what ever is needed, just let me know
I mean Perseus is 1 AWESOME kernel if you ask me , only thing is there is no interface to tweak it like Siyah's Stweaks. I was told he is working on something tho. Anyways Its always good to have a variety to choose from
Click to expand...
Click to collapse
Please contact me. We are willing to work on this port. Ordering device tomorrow. Talk me: [email protected],

Just checked out liquid smooth for nexus. Looks amazing. Cant wait!!!
Sent from my GT-I9305 using xda premium

The first version is allways difficult!
Congratulations to all equipo.(GT I9305 LTE SiyahKernel)

has one been made?

Amplified said:
Please contact me. We are willing to work on this port. Ordering device tomorrow. Talk me: [email protected],
Click to expand...
Click to collapse
I have Emailed You and I have also PM'd you, I have not received any reply. So evryone Its still in the air at the moment Its up for grabs who ever wants to start, If I knew what to do I would of started already. I myself need some guidance especially with kernels..

I didn't know that 9300 and 9305 was almost identical, even the partition sizes and layout.
I just have to reconfirm that but if it is so I will release i9305 version by simply editing the config file a little + some merges with 9305 kernel sources.
but it will not be so easy if the partition layout is different.

gokhanmoral said:
I didn't know that 9300 and 9305 was almost identical, even the partition sizes and layout.
I just have to reconfirm that but if it is so I will release i9305 version by simply editing the config file a little + some merges with 9305 kernel sources.
but it will not be so easy if the partition layout is different.
Click to expand...
Click to collapse
It would be great to have another choice of kernel

This is what Andreilux wrote before he ported his kernel
The I9305 is almost Identical kernel to the i9300 one. Only difference is:
CMA device memory allocation is gone as we don't need the hacks used in it for larger memory, 2GB with the default setting will suffice. <<< Although if it doesnt hurt and just gives us more then feel free to leave it in there, the more the better I say, But you are the dev so you can decide.
LCDFreq might not work [WIP]
You apparently have no FM radio. <<<<< Although these devices have the hardware and he said he is going to make a kernel with FM support... We havent seen one yet as he is working with Note 2 at the moment. So feel free to try yourself
The port is trivial and everything else should work flawlessly.
Also this helped him create a CWM flash hope this helps you these are the partition locations on the I9305
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6

btemtd said:
This is what Andreilux wrote before he ported his kernel
The I9305 is almost Identical kernel to the i9300 one. Only difference is:
CMA device memory allocation is gone as we don't need the hacks used in it for larger memory, 2GB with the default setting will suffice. <<< Although if it doesnt hurt and just gives us more then feel free to leave it in there, the more the better I say, But you are the dev so you can decide.
LCDFreq might not work [WIP]
You apparently have no FM radio. <<<<< Although these devices have the hardware and he said he is going to make a kernel with FM support... We havent seen one yet as he is working with Note 2 at the moment. So feel free to try yourself
The port is trivial and everything else should work flawlessly.
Also this helped him create a CWM flash hope this helps you these are the partition locations on the I9305
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
Click to expand...
Click to collapse
I also need the partition sizes.
so please post "df" and "mount" outputs from adb shell.
it seems that the layout is different but if the formats are the sizes are similar I can get dual boot feature work as well.
and also please post "ls -l /dev/input /dev/block" output

Ok I will get it done now, If somebody is quicker feel free to post for Gohkan

I hope this is right

btemtd said:
I hope I did it right for you Gokz please confirm
Click to expand...
Click to collapse
exactly what I needed.
but it will not be that easy. I will have to make some modifications in the recovery and dual-boot related parts because partition layout is not the same.
so, it will not be released together with tonight's 9300 release.

gokhanmoral said:
exactly what I needed.
but it will not be that easy. I will have to make some modifications in the recovery and dual-boot related parts because partition layout is not the same.
so, it will not be released together with tonight's 9300 release.
Click to expand...
Click to collapse
Bro Not a problem at all.. Do not rush, and thank you so much. I am here if you need anything

if it helps i have dumped a text version of the shell outputs:
Code:
mount
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/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,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p13 /system ext4 ro,noatime,barrier=1,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
/dev/block/mmcblk0p11 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.suffick.node-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.uberdroidstudio.ubermusic-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 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
df
Filesystem Size Used Free Blksize
/dev 896M 84K 896M 4096
/mnt/asec 896M 0K 896M 4096
/mnt/obb 896M 0K 896M 4096
/efs 19M 4M 15M 4096
/cache 1007M 17M 990M 4096
/system 1G 1001M 510M 4096
/data 11G 6G 4G 4096
/firmware 199M 45M 154M 4096
/tombstones 251M 18M 233M 4096
/storage/sdcard0 10G 6G 4G 4096
/mnt/asec/com.suffick.node-1 2M 256K 1M 4096
/mnt/asec/com.uberdroidstudio.ubermusic-1 3M 1M 1M 4096
/storage/extSdCard 29G 28G 1G 32768
ls -l /dev/input /dev/block
crw-rw---- root input 13, 64 2012-10-18 11:10 event0
crw-rw---- root input 13, 65 2012-10-18 11:10 event1
crw-rw---- root input 13, 74 2012-10-18 11:10 event10
crw-rw---- root input 13, 66 2012-10-18 11:10 event2
crw-rw---- root input 13, 67 2012-10-18 11:10 event3
crw-rw---- root input 13, 68 2012-10-18 11:10 event4
crw-rw---- root input 13, 69 2012-10-18 11:10 event5
crw-rw---- root input 13, 70 2012-10-18 11:10 event6
crw-rw---- root input 13, 71 2012-10-18 11:10 event7
crw-rw---- root input 13, 72 2012-10-18 11:10 event8
crw-rw---- root input 13, 73 2012-10-18 11:10 event9
crw-rw---- root input 13, 63 2012-10-18 11:10 mice
brw------- root root 254, 0 2012-10-18 11:10 dm-0
brw------- root root 254, 1 2012-10-18 11:10 dm-1
brw------- root root 7, 0 2012-10-18 11:10 loop0
brw------- root root 7, 1 2012-10-18 11:10 loop1
brw------- root root 7, 2 2012-10-18 11:10 loop2
brw------- root root 7, 3 2012-10-18 11:10 loop3
brw------- root root 7, 4 2012-10-18 11:10 loop4
brw------- root root 7, 5 2012-10-18 11:10 loop5
brw------- root root 7, 6 2012-10-18 11:10 loop6
brw------- root root 7, 7 2012-10-18 11:10 loop7
brw------- root root 179, 0 2012-10-18 11:10 mmcblk0
brw------- root root 179, 1 2012-10-18 11:10 mmcblk0p1
brw-rw---- system radio 179, 10 2012-10-18 11:10 mmcblk0p10
brw-rw---- system radio 179, 11 2012-10-18 11:10 mmcblk0p11
brw------- root root 179, 12 2012-10-18 11:10 mmcblk0p12
brw------- root root 179, 13 2012-10-18 11:10 mmcblk0p13
brw------- root root 179, 14 2012-10-18 11:10 mmcblk0p14
brw------- root root 179, 15 2012-10-18 11:10 mmcblk0p15
brw------- root root 259, 0 2012-10-18 11:10 mmcblk0p16
brw------- root root 179, 2 2012-10-18 11:10 mmcblk0p2
brw------- root root 179, 3 2012-10-18 11:10 mmcblk0p3
brw-rw---- system radio 179, 4 2012-10-18 11:12 mmcblk0p4
brw-rw---- system radio 179, 5 2012-10-18 11:10 mmcblk0p5
brw-rw---- system radio 179, 6 2012-10-18 11:10 mmcblk0p6
brw-rw---- system root 179, 7 2012-10-18 11:11 mmcblk0p7
brw------- root root 179, 8 2012-10-18 11:10 mmcblk0p8
brw------- root root 179, 9 2012-10-18 11:10 mmcblk0p9
brw------- root root 179, 16 2012-10-18 11:10 mmcblk1
brw------- root root 179, 17 2012-10-18 11:10 mmcblk1p1
lrwxrwxrwx root root 2012-10-18 11:10 param -> /dev/block/mmcblk0p7
drwxr-xr-x root root 2012-10-18 11:10 platform
brw------- root root 1, 0 2012-10-18 11:10 ram0
brw------- root root 1, 1 2012-10-18 11:10 ram1
brw------- root root 1, 10 2012-10-18 11:10 ram10
brw------- root root 1, 11 2012-10-18 11:10 ram11
brw------- root root 1, 12 2012-10-18 11:10 ram12
brw------- root root 1, 13 2012-10-18 11:10 ram13
brw------- root root 1, 14 2012-10-18 11:10 ram14
brw------- root root 1, 15 2012-10-18 11:10 ram15
brw------- root root 1, 2 2012-10-18 11:10 ram2
brw------- root root 1, 3 2012-10-18 11:10 ram3
brw------- root root 1, 4 2012-10-18 11:10 ram4
brw------- root root 1, 5 2012-10-18 11:10 ram5
brw------- root root 1, 6 2012-10-18 11:10 ram6
brw------- root root 1, 7 2012-10-18 11:10 ram7
brw------- root root 1, 8 2012-10-18 11:10 ram8
brw------- root root 1, 9 2012-10-18 11:10 ram9
drwx------ root root 2012-10-18 11:10 vold
im running stock XXALI5 on my Optus i9305

i got my s3lte today and lol when using phone actually missed the features of ur kernel cnt wait for port
Sent from my GT-I9305 using Tapatalk 2

His working on a few things with other phones this weekend so i am hoping we should have this by next week some time . (Hopefully) his a busy man
Sent from my GT-I9305 using xda app-developers app

anyone up for porting will pm dev bwt this. cnt wait to gt this kernel on i9305. best kernel ever
Sent from my GT-I9305 using Tapatalk 2

No need as gohkan is going to do it he is still working on some s2 sttuff when he finish then its s3, we will get duaL booting feature but there is some bad news to follow. Gohkan is leaving the s3 so updats will be slow. Reason for leaving is because samsung wont release the exynos sources. On other note if they do he might return.
I did here some news on sammobile saying they are going to soon apparently.
Sent from my GT-I9305 using xda app-developers app

Im happy to be kernel Guinni Pig
btemtd said:
No need as gohkan is going to do it he is still working on some s2 sttuff when he finish then its s3, we will get duaL booting feature but there is some bad news to follow. Gohkan is leaving the s3 so updats will be slow. Reason for leaving is because samsung wont release the exynos sources. On other note if they do he might return.
I did here some news on sammobile saying they are going to soon apparently.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse

[Q] How to extract boot.img from Zopo C7 ( MTK6589T)

First how to find location of boot image in device? I want to take current boot image. Do modifications and later flash that boot image back to device.
I have searched correct block device and did some image files with dd command but they were not boot images. I tried with several tools.
Here is some listing from the phone with adb shell commands.
Code:
[email protected]:/proc # cat partitions
major minor #blocks name
179 0 30512256 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 665600 mmcblk0p5
179 6 129024 mmcblk0p6
179 7 1572864 mmcblk0p7
179 8 28077696 mmcblk0p8
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
Code:
[email protected]:/ # ls -l /emm*
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p7
[email protected]:/ #
Code:
[email protected]:/dev/block # ls -al
brw------- root root 7, 0 2014-03-12 12:54 loop0
brw------- root root 7, 1 2014-03-12 12:54 loop1
brw------- root root 7, 2 2014-03-12 12:54 loop2
brw------- root root 7, 3 2014-03-12 12:54 loop3
brw------- root root 7, 4 2014-03-12 12:54 loop4
brw------- root root 7, 5 2014-03-12 12:54 loop5
brw------- root root 7, 6 2014-03-12 12:54 loop6
brw------- root root 7, 7 2014-03-12 12:54 loop7
brw-rw---- root system 179, 0 2014-03-12 12:54 mmcblk0
brw------- root root 179, 32 2014-03-12 12:54 mmcblk0boot0
brw------- root root 179, 64 2014-03-12 12:54 mmcblk0boot1
brw------- root root 179, 1 2014-03-12 12:54 mmcblk0p1
brw-r----- root system 179, 2 2014-03-12 12:54 mmcblk0p2
brw------- root root 179, 3 2014-03-12 12:54 mmcblk0p3
brw------- root root 179, 4 2014-03-12 12:54 mmcblk0p4
brw------- root root 179, 5 2014-03-12 12:54 mmcblk0p5
brw------- root root 179, 6 2014-03-12 12:54 mmcblk0p6
brw------- root root 179, 7 2014-03-12 12:54 mmcblk0p7
brw------- root root 179, 8 2014-03-12 12:54 mmcblk0p8
drwxr-xr-x root root 2014-03-12 12:54 platform
[email protected]:/dev/block #
/dev/block/mmcblk0boot0 looked promising but I made image of it by by command dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot.img
But the image was not boot image.
Code:
[email protected]:/ # mount
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/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
[email protected] /data ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /storage/sdcard0 vfat rw,dirsync,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
[email protected]:/ #
I can make full image by dding /dev/block/mmcblk0 but it would be better to get the parts separately.
Is there easy way to find where the boot image is located?

I checked block device sizes
/dev/block/mmcblk0p8 is the internal flash area for user, about 28G. Boot image boot loader etc must be in mmcblk0p1 - mmcblk0p7
Size of the block devices
Code:
/dev/block/mmcblk0 31244550144
/dev/block/mmcblk0boot0 2097152
/dev/block/mmcblk0boot1 2097152
/dev/block/mmcblk0p1 1024
/dev/block/mmcblk0p2 10485760
/dev/block/mmcblk0p3 10485760
/dev/block/mmcblk0p4 6291456
/dev/block/mmcblk0p5 681574400
/dev/block/mmcblk0p6 132120576
/dev/block/mmcblk0p7 1610612736
/dev/block/mmcblk0p8 28751560704
/dev/block/mmcblk1 8178892800
I got these with script
Code:
#!/system/bin/sh
command="/sdcard/busybox blockdev --getsize64"
for f in /dev/block/mm*
do
result=`$command $f`
result="$f \t $result"
echo $result
done

Via Terminal Emulator:
"su
cat /proc/partitions"
When again other command: dd if=/dev/block/(boot_partition_which_showed under /proc/partitions) of=/sdcard/boot.img

Root your device and try MtkDroidTools.
Use MTK SP_Flash_tool to flash image back.

In proc partitions there were two boot related devices listed
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
I made images from both of those but there was nothing inside the images which looked like boot image.
I found that there is /dev/bootimage
Code:
[email protected]:/ # ls -l /dev/boo*
crw-r----- root system 234, 10 2013-01-01 06:30 bootimg
I made image from that. The image is 4.3G. Very large. Anyway I found bootimage inside that. Then I made another smaller one with
Code:
# dd if=/dev/bootimg of=/sdcard/testboot.img count=12000
I can unpack that image in linux with tool unpack-MT65xx.pl. I tried to repack the exact same files without modifying. But repacking the image with repack-MT65.pl generates file which is different.

cnexpat said:
Is there easy way to find where the boot image is located?
Click to expand...
Click to collapse
Looking for same

Creating a flashable ODIN file

Not sure if this has been posted before, so I apologize in advance if that's the case, but I was hoping I could get some insight on how to create a flashable tar file for ODIN.
I have been researching this for a few weeks, and this site is my #1 resource for information, so I would just like to give out a huge shout out to everyone that helps out on here with your tuts, files, and your knowledge.
Here is an overview of what I am working with.
I have a SM-G930T phone - Tmobile Carrier
It is unrooted using the eng boot file and "SuperSU-v2.76-S7QC"
I am running Android 6.0.1
Baseband: G930TUVU1APG1
Kernel: 3.18.20-7856276-eng
Build #: MMB29M.G930TUVU1APG1
What I'm trying to accomplish.
I am able to make a dump of the system through ADB shell using this information:
Code:
[email protected]:/ # ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 2016-01-08 10:35 aboot -> /dev/block/sdd10
lrwxrwxrwx root root 2016-01-08 10:35 apdp -> /dev/block/sdd17
lrwxrwxrwx root root 2016-01-08 10:35 apnhlos -> /dev/block/sda15
lrwxrwxrwx root root 2016-01-08 10:35 bluetooth -> /dev/block/sdd12
lrwxrwxrwx root root 2016-01-08 10:35 boot -> /dev/block/sda17
lrwxrwxrwx root root 2016-01-08 10:35 bota -> /dev/block/sda12
lrwxrwxrwx root root 2016-01-08 10:35 cache -> /dev/block/sda21
lrwxrwxrwx root root 2016-01-08 10:35 cmnlib -> /dev/block/sdd15
lrwxrwxrwx root root 2016-01-08 10:35 cmnlib64 -> /dev/block/sdd16
lrwxrwxrwx root root 2016-01-08 10:35 ddr -> /dev/block/sdd20
lrwxrwxrwx root root 2016-01-08 10:35 devcfg -> /dev/block/sda10
lrwxrwxrwx root root 2016-01-08 10:35 devinfo -> /dev/block/sdd11
lrwxrwxrwx root root 2016-01-08 10:35 dip -> /dev/block/sdd8
lrwxrwxrwx root root 2016-01-08 10:35 dpo -> /dev/block/sdd19
lrwxrwxrwx root root 2016-01-08 10:35 dsp -> /dev/block/sdd7
lrwxrwxrwx root root 2016-01-08 10:35 efs -> /dev/block/sda6
lrwxrwxrwx root root 2016-01-08 10:35 fota -> /dev/block/sda13
lrwxrwxrwx root root 2016-01-08 10:35 frp -> /dev/block/sda11
lrwxrwxrwx root root 2016-01-08 10:35 fsc -> /dev/block/sda3
lrwxrwxrwx root root 2016-01-08 10:35 fsg -> /dev/block/sdd4
lrwxrwxrwx root root 2016-01-08 10:35 hyp -> /dev/block/sdd3
lrwxrwxrwx root root 2016-01-08 10:35 keymaster -> /dev/block/sdd14
lrwxrwxrwx root root 2016-01-08 10:35 keystore -> /dev/block/sda9
lrwxrwxrwx root root 2016-01-08 10:35 lksecapp -> /dev/block/sdd13
lrwxrwxrwx root root 2016-01-08 10:35 mdtp -> /dev/block/sdd9
lrwxrwxrwx root root 2016-01-08 10:35 misc -> /dev/block/sda8
lrwxrwxrwx root root 2016-01-08 10:35 modem -> /dev/block/sda16
lrwxrwxrwx root root 2016-01-08 10:35 modemst1 -> /dev/block/sda1
lrwxrwxrwx root root 2016-01-08 10:35 modemst2 -> /dev/block/sda2
lrwxrwxrwx root root 2016-01-08 10:35 msadp -> /dev/block/sdd18
lrwxrwxrwx root root 2016-01-08 10:35 pad -> /dev/block/sdd21
lrwxrwxrwx root root 2016-01-08 10:35 param -> /dev/block/sda7
lrwxrwxrwx root root 2016-01-08 10:35 persdata -> /dev/block/sda19
lrwxrwxrwx root root 2016-01-08 10:35 persist -> /dev/block/sda5
lrwxrwxrwx root root 2016-01-08 10:35 persistent -> /dev/block/sda14
lrwxrwxrwx root root 2016-01-08 10:35 pmic -> /dev/block/sdd6
lrwxrwxrwx root root 2016-01-08 10:35 recovery -> /dev/block/sda18
lrwxrwxrwx root root 2016-01-08 10:35 rpm -> /dev/block/sdd1
lrwxrwxrwx root root 2016-01-08 10:35 sec -> /dev/block/sdd5
lrwxrwxrwx root root 2016-01-08 10:35 ssd -> /dev/block/sda4
lrwxrwxrwx root root 2016-01-08 10:35 system -> /dev/block/sda20
lrwxrwxrwx root root 2016-01-08 10:35 tz -> /dev/block/sdd2
lrwxrwxrwx root root 2016-01-08 10:35 userdata -> /dev/block/sda22
lrwxrwxrwx root root 2016-01-08 10:35 xbl -> /dev/block/sdb1
--------------------------------------------
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 32768 loop0
8 0 31178752 sda
8 1 1536 sda1
8 2 1536 sda2
8 3 4 sda3
8 4 8 sda4
8 5 32768 sda5
8 6 20480 sda6
8 7 10240 sda7
8 8 1024 sda8
8 9 512 sda9
8 10 128 sda10
8 11 512 sda11
8 12 12288 sda12
8 13 4096 sda13
8 14 1024 sda14
8 15 97280 sda15
259 0 87040 sda16
259 1 77824 sda17
259 2 77824 sda18
259 3 9216 sda19
259 4 5017600 sda20
259 5 307200 sda21
259 7 25417536 sda22
8 16 4096 sdb
8 17 3072 sdb1
8 32 4096 sdc
8 33 3072 sdc1
8 48 61440 sdd
8 49 512 sdd1
8 50 2048 sdd2
8 51 512 sdd3
8 52 1536 sdd4
8 53 16 sdd5
8 54 512 sdd6
8 55 16384 sdd7
8 56 1024 sdd8
8 57 32768 sdd9
8 58 2048 sdd10
8 59 4 sdd11
8 60 1024 sdd12
8 61 384 sdd13
8 62 256 sdd14
8 63 256 sdd15
259 6 256 sdd16
259 8 128 sdd17
259 9 128 sdd18
259 10 4 sdd19
259 11 1024 sdd20
259 12 572 sdd21
253 0 2097152 vnswap0
179 0 62685184 mmcblk0
179 1 62668800 mmcblk0p1
254 0 25417520 dm-0
-----------------------------------------
[email protected]:/ # blockdev --getbsz /dev/block/sda20
4096
[email protected]:/ # blockdev --getsz /dev/block/sda20
10035200
[email protected]:/ # blockdev --getsize /dev/block/sda20
10035200
[email protected]:/ # blockdev --getsize64 /dev/block/sda20
5138022400
-----------------------------------------
C:\s7\adb-setup-1.4.3\adb>adb shell
[email protected]:/ # su
[email protected]:/ # busybox df -h
Filesystem Size Used Available Use% Mounted on
rootfs 1.5G 8.6M 1.5G 1% /
tmpfs 1.6G 148.0K 1.6G 0% /dev
none 1.6G 12.0K 1.6G 0% /sys/fs/cgroup
tmpfs 1.6G 0 1.6G 0% /mnt
tmpfs 1.6G 0 1.6G 0% /mnt/secure
tmpfs 59.8G 30.2G 29.5G 51% /mnt/secure/asec
/dev/block/bootdevice/by-name/system
4.7G 3.3G 1.3G 72% /system
/dev/block/loop0 27.5M 972.0K 25.9M 4% /system/xbin/su
/dev/block/bootdevice/by-name/efs
15.7M 640.0K 14.6M 4% /efs
/dev/block/bootdevice/by-name/cache
290.6M 2.1M 282.5M 1% /cache
/dev/block/bootdevice/by-name/persist
27.5M 124.0K 26.7M 0% /persist
/dev/block/bootdevice/by-name/dsp
11.7M 4.1M 7.3M 36% /dsp
/dev/block/bootdevice/by-name/apnhlos
70.0M 27.9M 42.1M 40% /firmware
/dev/block/bootdevice/by-name/modem
95.0M 70.3M 24.7M 74% /firmware-modem
/dev/block/bootdevice/by-name/persdata
4.9M 96.0K 4.6M 2% /persdata/absolute
tmpfs 1.6G 0 1.6G 0% /storage
/dev/block/dm-0 23.9G 7.1G 16.8G 30% /data
/dev/block/loop0 27.5M 972.0K 25.9M 4% /su
/data/media 23.9G 7.2G 16.7G 30% /storage/emulated
/data/media 23.9G 7.2G 16.7G 30% /mnt/runtime/default/emulated
/data/media 23.9G 7.2G 16.7G 30% /mnt/runtime/read/emulated
/data/media 23.9G 7.2G 16.7G 30% /mnt/runtime/write/emulated
/dev/block/vold/public:179,1
59.8G 30.2G 29.5G 51% /mnt/media_rw/0123-4567
/dev/block/vold/public:179,1
59.8G 30.2G 29.5G 51% /mnt/secure/asec
/mnt/media_rw/0123-4567
59.8G 30.2G 29.5G 51% /storage/0123-4567
/mnt/media_rw/0123-4567
59.8G 30.2G 29.5G 51% /mnt/runtime/default/0123-4567
/mnt/media_rw/0123-4567
59.8G 30.2G 29.5G 51% /mnt/runtime/read/0123-4567
/mnt/media_rw/0123-4567
59.8G 30.2G 29.5G 51% /mnt/runtime/write/0123-4567
dd if=/dev/block/sda20 of=/sdcard/system.img
OR
dd if=/dev/block/bootdevice/by-name/system of=/sdcard/system.img
Both work great, but this img that is dumped isn't ODIN flashable if I put it into a tar file.
Now I was reading it has to be converted using "img2simg"
So I did that.
I tried several variation of that:
img2simg system.img system.img.ext4
img2simg system.img system.img.ext4 4096 <-- being the block size
I also tried using ext2simg
ext2simg system.img system.img.ext4
ext2simg -S system.img system.img.ext4
I've tried using the tools provided in "ANDROID_IMG_REPACK_TOOLS_CYGWIN_x64-86_6.0.1"
I have also tried doing it manually through CYGWIN directly.
At one point it looked like everything was going through properly in ODIN.
I created a tar file and then added the md5 checksum
and when I flashed it in ODIN, it was uploading the file and it got to the end and then I got a error. I can't remember what it was, I think it had something to do with wrong file version or something. My guess is that the system.img.ext4 file doesn't have the correct "header" or something in there that validates it properly.
Any way, I'm hoping someone can guide me through this. I know that there are roms available that are zip format, but I'd like to learn to do this on my own and ideally through an ODIN flashable file if possible.
Thanks in advance for your help.

Don't mean to bump this, but I wanted to update..
I'm attaching the error I get in ODIN
On my phone I get "SECURE CHECK FAIL : system"
Thanks in advance for any help.

[INFO] How To Get Partition Details Of Android With ADB

Sometime you need to build some mod or own custom ROM for a new device or the device which don't have much development on it.On these situations to flash any partition to the device we need to know it's actual block,size,path,user privilage.
This can typically done by a Root explorer or via ADB shell.
In this comprehensive info guide I will focous on getting partition details via ADB shell.
Let's Dive In:-
REQUIREMENTS
1. UNLOCKED BOOTLOADER.
2. SUPERSU/MAGISK FOR ROOT ACCESS.
3. ADB INSTALLED PROPERLY IN PC.
4. RESPECTIVE DEVICE DRIVERS. (e.g. for moto g5 plus,which i have,need motorola usb drivers to be installed.)
PROCEDURE
1. Using df lists the filesystem path alias and size info as seen below (total size, used, free and block size).
Example :
Code:
[email protected]:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1714040 3732 1710308 1% /
tmpfs 1819500 712 1818788 1% /dev
/dev/block/mmcblk0p53 3320680 1882092 1438588 57% /system
tmpfs 1819500 0 1819500 0% /mnt
/data/media 25782252 3489280 22292972 14% /mnt/runtime/default/emulated
/dev/block/vold/public:179_65 15640832 11533440 4107392 74% /mnt/media_rw/79D8-1EE2
/mnt/media_rw/79D8-1EE2 15640832 11533440 4107392 74% /mnt/runtime/default/79D8-1EE2
/dev/block/mmcblk0p54 25782252 3489280 22292972 14% /data
/dev/block/mmcblk0p52 253920 228 253692 1% /cache
/dev/block/mmcblk0p19 96688 69552 27136 72% /firmware
/dev/block/mmcblk0p29 2500 2492 8 100% /fsg
/dev/block/mmcblk0p22 12016 5052 6964 43% /dsp
/dev/block/mmcblk0p30 28144 520 27624 2% /persist
/dev/block/loop0 92656 996 91660 2% /su
2. Using cat /proc/mounts shows the partition file path, the alias, the filesystem type, the startnig inode, the number of blocks, read/write status (and other parameters of the individual partition that I'm not entirely sure of).
Example:
Code:
[email protected]:/ # cat /proc/mounts
rootfs / rootfs ro,seclabel,size=1714040k,nr_inodes=428510 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1819500k,nr_inodes=454875,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/cpuset cgroup rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tracefs /sys/kernel/tracing tracefs rw,relatime 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=1819500k,nr_inodes=454875,mode=755,gid=1000 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid 0 0
/dev/block/vold/public:179_65 /mnt/media_rw/79D8-1EE2 vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/mnt/media_rw/79D8-1EE2 /mnt/runtime/default/79D8-1EE2 sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6 0 0
/mnt/media_rw/79D8-1EE2 /mnt/runtime/read/79D8-1EE2 sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18 0 0
/mnt/media_rw/79D8-1EE2 /mnt/runtime/write/79D8-1EE2 sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18 0 0
none /config configfs rw,relatime 0 0
/dev/block/bootdevice/by-name/userdata /data f2fs rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,nobarrier,extent_cache,active_logs=6 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware ext4 ro,context=u:object_r:firmware_file:s0,nosuid,nodev,relatime,nobarrier,data=ordered 0 0
/dev/block/bootdevice/by-name/fsg /fsg ext4 ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,context=u:object_r:persist_file:s0,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/loop0 /su ext4 rw,seclabel,noatime,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=1819500k,nr_inodes=454875,mode=755,gid=1000 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/mnt/media_rw/79D8-1EE2 /storage/79D8-1EE2 sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6 0 0
tmpfs /storage/self tmpfs rw,seclabel,relatime,size=1819500k,nr_inodes=454875,mode=755,gid=1000 0 0
3.Using cat /proc/partitions you will get the actual partition name identifier and the number of blocks in the partition.
Example:
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 98304 loop0
254 0 524288 zram0
179 0 30535680 mmcblk0
179 1 512 mmcblk0p1
179 2 256 mmcblk0p2
179 3 1792 mmcblk0p3
179 4 64 mmcblk0p4
179 5 1536 mmcblk0p5
179 6 256 mmcblk0p6
179 7 256 mmcblk0p7
179 8 256 mmcblk0p8
179 9 192 mmcblk0p9
179 10 512 mmcblk0p10
179 11 256 mmcblk0p11
179 12 1792 mmcblk0p12
179 13 64 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 256 mmcblk0p15
179 16 256 mmcblk0p16
179 17 256 mmcblk0p17
179 18 192 mmcblk0p18
179 19 102400 mmcblk0p19
179 20 1 mmcblk0p20
179 21 8 mmcblk0p21
179 22 16384 mmcblk0p22
179 23 32 mmcblk0p23
179 24 16 mmcblk0p24
179 25 512 mmcblk0p25
179 26 512 mmcblk0p26
179 27 2048 mmcblk0p27
179 28 2048 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 512 mmcblk0p31
259 0 128 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 512 mmcblk0p35
259 4 8192 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 20580 mmcblk0p38
259 7 1024 mmcblk0p39
259 8 32 mmcblk0p40
259 9 512 mmcblk0p41
259 10 1024 mmcblk0p42
259 11 512 mmcblk0p43
259 12 2048 mmcblk0p44
259 13 256 mmcblk0p45
259 14 256 mmcblk0p46
259 15 8 mmcblk0p47
259 16 128 mmcblk0p48
259 17 8192 mmcblk0p49
259 18 8192 mmcblk0p50
259 19 671744 mmcblk0p51
259 20 262144 mmcblk0p52
259 21 3538944 mmcblk0p53
259 22 25784303 mmcblk0p54
179 32 4096 mmcblk0rpmb
179 64 15645696 mmcblk1
179 65 15644672 mmcblk1p1
Here comes a tricky part,
This folder in which by-name output is stored varies from devices to devices.
I will write the procedure to find this thing out.
Note : Here I am using MOTO G5 PLUS [POTTER] for demonstration.
As I change directory to /dev/block/bootdevice/ & ls to see the files & folders in this folder , i found that by-name folder which i was looking for.
Example:
Code:
[email protected]:/ # cd /dev/block/bootdevice/
[email protected]:/dev/block/bootdevice # ls -a -l
total 0
drwxr-xr-x 4 root root 1200 1970-08-14 04:53 .
drwxr-xr-x 4 root root 80 2018-03-22 09:08 ..
drwxr-xr-x 2 root root 1120 1970-08-14 04:53 by-name
drwxr-xr-x 2 root root 1120 1970-08-14 04:53 by-num
lrwxrwxrwx 1 root root 18 1970-08-14 04:53 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p24 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p25 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p26 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p27 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p28 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p29 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p30 -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p31 -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p32 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p34 -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p35 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p36 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p37 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p38 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p39 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p40 -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p41 -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p42 -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p43 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p44 -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p45 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p46 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p47 -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p48 -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p49 -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p50 -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p51 -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p52 -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p53 -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p54 -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p9 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 22 1970-08-14 04:53 mmcblk0rpmb -> /dev/block/mmcblk0rpmb
[email protected]:/dev/block/bootdevice #
Now i will enterby-name folder & see what's inside ?
...
Hola we nailed it !,I found exactly what i was trying to find,the detailed info of partitions.see below code.
Code:
[email protected]:/dev/block/bootdevice # cd by
by-name/ by-num/
[email protected]:/dev/block/bootdevice # cd by-name/
[email protected]:/dev/block/bootdevice/by-name # ls -a -l
total 0
drwxr-xr-x 2 root root 1120 1970-08-14 04:53 .
drwxr-xr-x 4 root root 1200 1970-08-14 04:53 ..
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]apdp -> /dev/block/mmcblk0p45[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]boot -> /dev/block/mmcblk0p37[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]cache -> /dev/block/mmcblk0p52[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 carrier -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cid -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 cmnlib -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 cmnlib64 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cmnlib64bak -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cmnlibbak -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 devcfg -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 devcfgbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dip -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dpo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dsp -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 frp -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 fsg -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]hw -> /dev/block/mmcblk0p50[/COLOR]
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 keymaster -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 keymasterbak -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 limits -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-08-14 04:53[COLOR="Magenta"] logo -> /dev/block/mmcblk0p33[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 logs -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 metadata -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 misc -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]modem -> /dev/block/mmcblk0p19[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 modemst1 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 modemst2 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mota -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 msadp -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]oem -> /dev/block/mmcblk0p51[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 padA -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="Magenta"]persist -> /dev/block/mmcblk0p30[/COLOR]
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 prov -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 provbak -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]recovery -> /dev/block/mmcblk0p38[/COLOR]
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 [COLOR="magenta"]rpm -> /dev/block/mmcblk0p2[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 rpmbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 sbl1bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]sec -> /dev/block/mmcblk0p24[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 sp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 syscfg -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]system -> /dev/block/mmcblk0p53[/COLOR]
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 tzbak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]userdata -> /dev/block/mmcblk0p54[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 utags -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 utagsBackup -> /dev/block/mmcblk0p26
[email protected]:/dev/block/bootdevice/by-name #
4. So for a particular device you can use ls -al /dev/block/platform/Your_Folder_Name/by-name to see the mapping between the partition alias and the path of actual partition file with owner & user.
Example:
Code:
[email protected]:/dev/block/bootdevice/by-name # ls - a -l /dev/block/bootdevice/b
ls: -: No such file or directory
ls: a: No such file or directory
total 0
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 apdp -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cache -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 carrier -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cid -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 cmnlib -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 cmnlib64 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cmnlib64bak -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cmnlibbak -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 devcfg -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 devcfgbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dip -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dpo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dsp -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 frp -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 fsg -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 hw -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 keymaster -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 keymasterbak -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 limits -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 logo -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 logs -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 metadata -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 misc -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 modem -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 modemst1 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 modemst2 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mota -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 msadp -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 oem -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 padA -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 persist -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 prov -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 provbak -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 recovery -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 rpm -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 rpmbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 sbl1bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 sp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 syscfg -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 system -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 tzbak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 userdata -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 utags -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 utagsBackup -> /dev/block/mmcblk0p26
1|[email protected]:/dev/block/bootdevice/by-name #
Now you must understand that before flashing anything do check the script of that file & make sure it is flashing to the right partition (mmcblk0xxx) according to your device.
IF your are happy & it helped you do hit the THANKS button. It always motivates when someone appreciate your work.
Thank You.
OFFICIAL COMMUNITY
Official Telegram Group
Official Telegram Channel
======== GEEKOFIA ========
VISIT​

RESERVED

Big thanks
Thank you very much! That really helped!

I have a Tissot (mi a1) with TWRP dual booted by separating vendor_a, vendor_b, userdata_a, userdata_b. It is dual booted by cosmicdan's twrp with Resurrection remix ( slot_a) official and Dotos official ( slot_b). I want to mount userdata_b in resurrection remix or vice verse.
I have already tried these steps but no result.
1. create a folder named 'data2' in " /data/local/tmp/data2" .
2. open terminal.
3. run su.
4. Enter " mount -o rw /dev/block/mmcblk0p52 /data/local/tmp/data2" (as 52 is my userdata_b partition).
5. no error showing but nothing mounted.
Is there any way to mount this?

Lenovo P90 boot unlock/flash problem

Hi guys,
does anybody knows the file system of Lenovo P90?
Android 4.4.4, the bootloader is locked of course, Developer menu is a joke - only 3 options, OEM unlock doesn't exist, most of fastboot command (all of OEM, getvar, getprop, etc.) is unknown or the output is nothing.. probably the "good fellows" renamed or removed those commands. I've tried to find the OEM commands in boot and droidboot.img with no luck.
With a temporary recovery I,ve ROOT-ed it at least. After modification (boot, etc.) I can't flash anything.. cmd error.
The partition scheme isn't exactly clear for me. The /reserved (mmcblk0p1 - 256Mb) must be the boot partition (?), with boot, recowery, droidboot,
everything is in one place, and the /panic (32Mb) is some log area for the kernel, or the /panic is the recovery, and.. or sooo whaaaat?
I don't really care any backup, data or the phone itself, so I've just written a modified boot.img to mmcblk0p1 straight with dd.
I know, this is a very good idea.. and safe! The phone booted up surprisingly, but the droidboot is gone!
All I can do is flash the ORIGINAL boot, recowery, droidboot img-s to somewhere with fastboot, without any modification, except the system.img. I modified the
the system.img (deodex, zipalign, removed more than 1Gb sh*t), but I can't get Signature Spoofing.. Tingle is failed, the manualy modified framework is failed, so I cant
destroy the Google.
I can't see eny restriction on mmcblk0 and mmcblk0p1, but I can't write any critical area with modified img, at least with fastboot.
Does enybody knows "whatta hack" is on the mmcblk0boot0 (4mb) partition, what is blocking every modification? I can modify the force_ro on mmcblk0boot0 to 0,
maybe I can write it with dd, but.. with what?!.
Here's the deal:
#
orginal:
[email protected]:/ # cat /sys/block/mmcblk0/force_ro
0
[email protected]:/ # cat /sys/block/mmcblk0/ro
0
[email protected]:/ # cat /sys/block/mmcblk0/mmcblk0p1/ro
0
[email protected]:/ # cat /sys/block/mmcblk0/mmcblk0boot0/force_ro
1
[email protected]:/ # cat /sys/block/mmcblk0/mmcblk0boot1/force_ro
1
#
recovery.fstab
#size_hint=256
/dev/disk/by-label/reserved /reserved hidden None length=0
#size_hint=32
/dev/disk/by-label/panic /panic raw None length=0
#size_hint=128
/dev/disk/by-label/factory /factory ext4 nosuid,nodev,noatime,barrier=1,data=ordered length=0
#size_hint=128
/dev/disk/by-label/misc /misc emmc None length=0
#size_hint=128
/dev/disk/by-label/config /config ext4 nosuid,nodev,noatime,barrier=1,data=ordered length=0
#size_hint=1536
/dev/disk/by-label/cache /cache ext4 nosuid,nodev,noatime,barrier=1,data=ordered length=0
#size_hint=24
/dev/disk/by-label/logs /logs ext4 nosuid,nodev,barrier=1,data=ordered length=0
#size_hint=2560
/dev/disk/by-label/system /system ext4 ro,noatime length=0
#size_hint=0
/dev/disk/by-label/data /data ext4 nosuid,nodev,noatime,discard,barrier=1,data=ordered,noauto_da_alloc length=-33
#size_hint=-1
/dev/block/mmcblk1p1 /mnt/sdcard1 vfat defaults length=0
#
[email protected]:/dev/disk/by-label # ls -l *
lrwxrwxrwx system system 2019-03-12 12:52 cache -> ../../block/mmcblk0p6
lrwxrwxrwx system system 2019-03-12 12:52 config -> ../../block/mmcblk0p5
lrwxrwxrwx system system 2019-03-12 12:52 data -> ../../block/mmcblk0p9
lrwxrwxrwx system system 2019-03-12 12:52 factory -> ../../block/mmcblk0p3
lrwxrwxrwx system system 2019-03-12 12:52 logs -> ../../block/mmcblk0p7
lrwxrwxrwx system system 2019-03-12 12:52 misc -> ../../block/mmcblk0p4
lrwxrwxrwx system system 2019-03-12 12:52 panic -> ../../block/mmcblk0p2
lrwxrwxrwx system system 2019-03-12 12:52 reserved -> ../../block/mmcblk0p1
lrwxrwxrwx system system 2019-03-12 12:52 system -> ../../block/mmcblk0p8
#
[email protected]:/dev/block # ls -l *
...
brw------- root root 179, 0 2019-03-12 12:52 mmcblk0
brw------- root root 179, 16 2019-03-12 12:52 mmcblk0boot0
brw------- root root 179, 32 2019-03-12 12:52 mmcblk0boot1
brw------- root root 179, 1 2019-03-12 12:52 mmcblk0p1
brw------- root root 179, 2 2019-03-12 12:52 mmcblk0p2
brw------- root root 179, 3 2019-03-12 12:52 mmcblk0p3
brw------- root root 179, 4 2019-03-12 12:52 mmcblk0p4
brw------- root root 179, 5 2019-03-12 12:52 mmcblk0p5
brw------- root root 179, 6 2019-03-12 12:52 mmcblk0p6
brw------- root root 179, 7 2019-03-12 12:52 mmcblk0p7
brw------- root root 179, 8 2019-03-12 12:52 mmcblk0p8
brw------- root root 179, 9 2019-03-12 12:52 mmcblk0p9
brw------- root root 179, 48 2019-03-12 12:52 mmcblk0rpmb
...
#
[email protected]:/ # busybox fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.2 GB, 31268536320 bytes
256 heads, 63 sectors/track, 3786 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 3787 30535679+ ee EFI GPT
[email protected]:/ # busybox fdisk -l /dev/block/mmcblk0p1
Disk /dev/block/mmcblk0p1: 268 MB, 268435456 bytes
4 heads, 16 sectors/track, 8192 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
#
original boot.img - default.prop (That's All)
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.allow.mock.location=0
ro.com.google.clientidbase=android-lenovo
persist.fwlog.enable=1
persist.stm.mid_disabled=punit
ro.opengles.version=196608
persist.dual_sim=none
sys.usb.vbus=normal
rw.log.tag.Mms:transaction=VERBOSE
rw.log.tag.Mms:app=VERBOSE
rw.log.tag.Mms:threadcache=VERBOSE
rw.log.tag.Mms:thumbnailcache=VERBOSE
rw.log.tag.Mms: pducache=VERBOSE
rw.log.tag.Mms:widget=VERBOSE
rw.log.tag.Mms:contact=VERBOSE
ro.secure=1
ro.adb.secure=1
ro.debuggable=0
persist.ril-daemon.disable=0
persist.sys.usb.config=mtp
persist.sys.emmc=storage/sdcar
#
I can change everything (ro.secure=0, etc.), or append it new line of course, but I can't flash it back.
Sorry if this is some trivial problem, but I'm lost. I'm interested in the X86 architecture, because I want to build a mini FOREX server on this phone..
Thanks for any advice!