Related
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
Code:
cat /proc/partitions
major minor #blocks name
8 0 62480384 sda
8 1 4096 sda1
8 2 4096 sda2
8 3 20480 sda3
8 4 4096 sda4
8 5 4096 sda5
8 6 4096 sda6
8 7 8192 sda7
8 8 28672 sda8
8 9 34816 sda9
8 10 8192 sda10
8 11 77824 sda11
8 12 1024 sda12
8 13 1024 sda13
8 14 768 sda14
8 15 256 sda15
259 0 9216 sda16
259 1 15360 sda17
259 2 3829760 sda18
259 3 307200 sda19
259 4 46080 sda20
259 5 58060800 sda21
8 16 4096 sdb
8 32 4096 sdc
~ # ls -al dev/block/platform/15570000.ufs/by-name
ls -al dev/block/platform/15570000.ufs/by-name
drwxr-xr-x 2 root root 460 May 8 23:56 .
drwxr-xr-x 4 root root 560 May 8 23:56 ..
lrwxrwxrwx 1 root root 15 May 8 23:56 BOOT -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 May 8 23:56 BOTA0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 May 8 23:56 BOTA1 -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 May 8 23:56 CACHE -> /dev/block/sda19
lrwxrwxrwx 1 root root 16 May 8 23:56 CARRIER -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 May 8 23:56 DNT -> /dev/block/sda13
lrwxrwxrwx 1 root root 15 May 8 23:56 EFS -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 May 8 23:56 OTA -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 May 8 23:56 PARAM -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 May 8 23:56 PERSDATA -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 May 8 23:56 PERSISTENT -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 May 8 23:56 RADIO -> /dev/block/sda11
lrwxrwxrwx 1 root root 15 May 8 23:56 RECOVERY -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 May 8 23:56 SBFS -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 May 8 23:56 STEADY -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 May 8 23:56 SYSTEM -> /dev/block/sda18
lrwxrwxrwx 1 root root 16 May 8 23:56 TOMBSTONES -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 May 8 23:56 USERDATA -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 May 8 23:56 m9kefs1 -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 May 8 23:56 m9kefs2 -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 May 8 23:56 m9kefs3 -> /dev/block/sda6
~ #
Thanks alot for this : ) Cant wait for people to start creating ROMs in this Forum
Can,someone pull the MODEM plz? I need a radio/baseband or whatever itvos,called that shows a,basand on the phone. Please and thank you. Also would like it in the form of a,md5 or twrp flaahable.
Check this out..... Whos gonna be the Guinea pig!!!!! http://forum.xda-developers.com/g4/general/info-lg-g4-korea-variant-rooted-anable-t3163925
Wow, I hope it will work on our sexy phone.
kramnod said:
Wow, I hope it will work on our sexy phone.
Click to expand...
Click to collapse
No kidding.. I have mine on ebay now....gotta end the auction!!! Bc i like the feel of the flex 2
Google~Android said:
Check this out..... Whos gonna be the Guinea pig!!!!! http://forum.xda-developers.com/g4/general/info-lg-g4-korea-variant-rooted-anable-t3163925
Click to expand...
Click to collapse
I think only experienced users-devs should try it first.... It is a little bit "dangerous' lol
kutulu32 said:
I think only experienced users-devs should try it first.... It is a little bit "dangerous' lol
Click to expand...
Click to collapse
They have root.. Now im goona go talk to autoprime about makin it compatible wit flex 2
Look at this... Now we wait for further instructions
Google~Android said:
Look at this... Now we wait for further instructions
Click to expand...
Click to collapse
Keeping fingers crossed !!!
kutulu32 said:
Keeping fingers crossed !!!
Click to expand...
Click to collapse
codefire just stated we shud be patient one of their team member is comin back from vaction and he'll have root for us wit just a simple app.....
Whooooo. Starting up the hype train
Google~Android said:
No kidding.. I have mine on ebay now....gotta end the auction!!! Bc i like the feel of the flex 2
Click to expand...
Click to collapse
Yeah. Me too I like the display and feel of this sexy beast.
Sent from my LG-H959 using Tapatalk
This is amazing news. Hopefully we can get something within the next few days. I have my G Flex 2 listed on Swappa. But if we can get root then I will stay with it.
I have talked to vn within the last few days, I even attempted hitting up these commands.
Code:
cat /proc/partitions
Code:
ls -l /dev/block/platform/f9824900.sdhci/by-name
first command lists out all partitions as expected, but second command leaves me with a "Permissions denied" message. even when done through ADB and terminal emulator. not sure why yet
bmxerkid954 said:
I have talked to vn within the last few days, I even attempted hitting up these commands.
Code:
cat /proc/partitions
Code:
ls -l /dev/block/platform/f9824900.sdhci/by-name
first command lists out all partitions as expected, but second command leaves me with a "Permissions denied" message. even when done through ADB and terminal emulator. not sure why yet
Click to expand...
Click to collapse
Is this bad news? we have been waitin good news for rooting 5.1.1 so long, hopefully its possible, I like this phone more and more, but it has to be rooted. 5.0.1 and rooted its quite ok but not perfect...
bmxerkid954 said:
I have talked to vn within the last few days, I even attempted hitting up these commands.
Code:
cat /proc/partitions
Code:
ls -l /dev/block/platform/f9824900.sdhci/by-name
first command lists out all partitions as expected, but second command leaves me with a "Permissions denied" message. even when done through ADB and terminal emulator. not sure why yet
Click to expand...
Click to collapse
Johnny can you post up what the first command gives you?
justinswidebody said:
Johnny can you post up what the first command gives you?
Click to expand...
Click to collapse
this is what i got on 5.0.1
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 28204 loop0
179 0 30535680 mmcblk0
179 1 81920 mmcblk0p1
179 2 512 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 512 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 1536 mmcblk0p23
179 24 1536 mmcblk0p24
179 25 1536 mmcblk0p25
179 26 512 mmcblk0p26
179 27 512 mmcblk0p27
179 28 512 mmcblk0p28
179 29 2048 mmcblk0p29
179 30 512 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 8 mmcblk0p33
259 2 4096 mmcblk0p34
259 3 49152 mmcblk0p35
259 4 40960 mmcblk0p36
259 5 40960 mmcblk0p37
259 6 8192 mmcblk0p38
259 7 8192 mmcblk0p39
259 8 32768 mmcblk0p40
259 9 40960 mmcblk0p41
259 10 47104 mmcblk0p42
259 11 10240 mmcblk0p43
259 12 4096 mmcblk0p44
259 13 4096 mmcblk0p45
259 14 4177920 mmcblk0p46
259 15 1261568 mmcblk0p47
259 16 24616960 mmcblk0p48
259 17 12271 mmcblk0p49
179 32 4096 mmcblk0rpmb
253 0 923980 zram0
179 64 61766656 mmcblk1
179 65 61745508 mmcblk1p1
254 0 28204 dm-0
[email protected]:/ $ ls -l /dev/block/platform/f9824900.sdhci/by-name
ls -l /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-06-04 03:22 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-06-04 03:22 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-06-04 03:22 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-06-04 03:22 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-06-04 03:22 boot -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-06-04 03:22 cache -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 1970-06-04 03:22 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-06-04 03:22 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-06-04 03:22 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-06-04 03:22 drm -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-06-04 03:22 eksst -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-06-04 03:22 encrypt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-06-04 03:22 factory -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-06-04 03:22 fota -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-06-04 03:22 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-06-04 03:22 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-06-04 03:22 grow -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 1970-06-04 03:22 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-06-04 03:22 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-06-04 03:22 keystore -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-06-04 03:22 laf -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-06-04 03:22 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-06-04 03:22 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-06-04 03:22 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-06-04 03:22 modemst1 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-06-04 03:22 modemst2 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-06-04 03:22 mpt -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-06-04 03:22 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-06-04 03:22 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-06-04 03:22 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-06-04 03:22 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-06-04 03:22 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-06-04 03:22 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-06-04 03:22 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-06-04 03:22 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-06-04 03:22 recovery -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-06-04 03:22 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-06-04 03:22 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-06-04 03:22 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-06-04 03:22 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-06-04 03:22 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-06-04 03:22 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-06-04 03:22 sec -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-06-04 03:22 sns -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-06-04 03:22 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-06-04 03:22 system -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 1970-06-04 03:22 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-06-04 03:22 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-06-04 03:22 userdata -> /dev/block/mmcblk0p48
randrew87 said:
this is what i got on 5.0.1
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 28204 loop0
179 0 30535680 mmcblk0
179 1 81920 mmcblk0p1
179 2 512 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 512 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 1536 mmcblk0p23
179 24 1536 mmcblk0p24
179 25 1536 mmcblk0p25
179 26 512 mmcblk0p26
179 27 512 mmcblk0p27
179 28 512 mmcblk0p28
179 29 2048 mmcblk0p29
179 30 512 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 8 mmcblk0p33
259 2 4096 mmcblk0p34
259 3 49152 mmcblk0p35
259 4 40960 mmcblk0p36
259 5 40960 mmcblk0p37
259 6 8192 mmcblk0p38
259 7 8192 mmcblk0p39
259 8 32768 mmcblk0p40
259 9 40960 mmcblk0p41
259 10 47104 mmcblk0p42
259 11 10240 mmcblk0p43
259 12 4096 mmcblk0p44
259 13 4096 mmcblk0p45
259 14 4177920 mmcblk0p46
259 15 1261568 mmcblk0p47
259 16 24616960 mmcblk0p48
259 17 12271 mmcblk0p49
179 32 4096 mmcblk0rpmb
253 0 923980 zram0
179 64 61766656 mmcblk1
179 65 61745508 mmcblk1p1
254 0 28204 dm-0
[email protected]:/ $ ls -l /dev/block/platform/f9824900.sdhci/by-name
ls -l /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-06-04 03:22 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-06-04 03:22 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-06-04 03:22 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-06-04 03:22 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-06-04 03:22 boot -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-06-04 03:22 cache -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 1970-06-04 03:22 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-06-04 03:22 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-06-04 03:22 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-06-04 03:22 drm -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-06-04 03:22 eksst -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-06-04 03:22 encrypt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-06-04 03:22 factory -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-06-04 03:22 fota -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-06-04 03:22 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-06-04 03:22 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-06-04 03:22 grow -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 1970-06-04 03:22 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-06-04 03:22 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-06-04 03:22 keystore -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-06-04 03:22 laf -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-06-04 03:22 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-06-04 03:22 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-06-04 03:22 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-06-04 03:22 modemst1 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-06-04 03:22 modemst2 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-06-04 03:22 mpt -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-06-04 03:22 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-06-04 03:22 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-06-04 03:22 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-06-04 03:22 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-06-04 03:22 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-06-04 03:22 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-06-04 03:22 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-06-04 03:22 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-06-04 03:22 recovery -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-06-04 03:22 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-06-04 03:22 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-06-04 03:22 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-06-04 03:22 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-06-04 03:22 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-06-04 03:22 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-06-04 03:22 sec -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-06-04 03:22 sns -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-06-04 03:22 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-06-04 03:22 system -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 1970-06-04 03:22 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-06-04 03:22 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-06-04 03:22 userdata -> /dev/block/mmcblk0p48
Click to expand...
Click to collapse
Yup mine was the same... I might update to 5.1....and try to inject root i to system.... Trying to build up courage... ... Ivd got the img injected wit root... Bt not brave enout to flash yet
Send me the img then i can try.
Sent from my LG-H955 using XDA Free mobile app
Feltox said:
Send me the img then i can try.
Sent from my LG-H955 using XDA Free mobile app
Click to expand...
Click to collapse
Its only for sprint... Pull ur system. Img and upload.. I might be able to inject root and reupload it
Google~Android said:
Its only for sprint... Pull ur system. Img and upload.. I might be able to inject root and reupload it
Click to expand...
Click to collapse
can you explain me how you inject root to the 5.1 system.img, maybe i can try to flash it, i asume that is the same lg G4 method.
randrew87 said:
can you explain me how you inject root to the 5.1 system.img, maybe i can try to flash it, i asume that is the same lg G4 method.
Click to expand...
Click to collapse
Try this...http://forum.xda-developers.com/showpost.php?p=62072444&postcount=906
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?
Hi,
This is my first project that I'm currently working on.
I recently bought a android dashcam which UI I would like to change based on my personal preferences. Unfortunately I'm struggling to setup an environment where I can test the changes I make before replacing the original UI on the device itself. I identified the SystemUI.apk to be the place where the manufacturer made customization. I will be using the SystemUI.apk built from AOSP and making my changes based on that. I had no luck trying to decompile the SystemUI.apk in a way that I could build it again.
I was thinking that I could use an android emulator to use the same ROM as the device itself. The manufacturer did not provide any support in providing stock firmware images in any way. So I used the following steps to 'export' the firmware.
1. Unlocking the bootloader using the Identifier Token so I can flash images using fastboot. TWRP was not an option here because I could not find any images for my device nor could I port an TWRP image myself.
2. Enable ADB debugging over usb
3. Enable ADB root privileges using the password: 2846 (if i remember correctly)
4. Use ADB remount and ADB root to gain privileges over the partitions
5. Gain information on partition data
6. Use ADB pull to export images based on partitions
After following the above steps the next thing was to import the images into an emulator. I used the following steps to do this:
1. Create a new device within Android Studio that has the same screen size and os.
2. Replace the system.img, ramdisk.img with the exported variants in ~/Android/Sdk/../arm64-v8a
3. Turn off EncryptUserData inside advancedFeatures.ini to prevent errors like partitions that are unable to encrypt
4. Use the command below to start the emulator
Code:
~/Android/Sdk/emulator/emulator -avd Junsun_A104_API_27 -verbose -show-kernel
5. After running the emulator I receive the error below and the screen of the emulator stays black.
Code:
Please append a correct "root=" boot option; here are the available partitions:
fe00 2867200 vda driver: virtio_blk
fe10 67584 vdb driver: virtio_blk
fe20 819200 vdc driver: virtio_blk
fe30 409600 vdd driver: virtio_blk
fe40 524288 vde driver: virtio_blk
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
My assumption is that the emulator does not contain the same partition model used on the device. I could try to export each partition but I wouldn't know how to let the emulator know how to use these partitions. I tried to export the kernel and import it inside the emulator without luck. I did not receive any errors that way.
So my main question is:
- Is there any way I can import the device's rom inside an android emulator
Spoiler: Emulator Config
AvdId=Junsun_A104_API_27
PlayStore.enabled=false
abi.type=arm64-v8a
avd.ini.displayname=Junsun A104 API 27
avd.ini.encoding=UTF-8
disk.dataPartition.size=800M
fastboot.chosenSnapshotFile=
fastboot.forceChosenSnapshotBoot=no
fastboot.forceColdBoot=no
fastboot.forceFastBoot=yes
hw.accelerometer=yes
hw.arc=false
hw.audioInput=yes
hw.battery=yes
hw.camera.back=virtualscene
hw.camera.front=emulated
hw.cpu.arch=arm64
hw.cpu.ncore=4
hw.dPad=no
hw.device.hash2=MD5:7834f5e80eb849ceb46ce01cd4c704f7
hw.device.manufacturer=User
hw.device.name=Junsun A104
hw.gps=yes
hw.gpu.enabled=no
hw.gpu.mode=off
hw.initialOrientation=landscape
hw.keyboard=yes
hw.lcd.density=120
hw.lcd.height=320
hw.lcd.width=1480
hw.mainKeys=no
hw.ramSize=2560
hw.sdCard=yes
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images/android-27/default/arm64-v8a/
runtime.network.latency=none
runtime.network.speed=full
sdcard.size=512M
showDeviceFrame=no
skin.dynamic=yes
skin.name=1480x320
skin.path=_no_skin
skin.path.backup=/home/dangelo/Android/Sdk/skins/tv_1080p
tag.display=Default Android System Image
tag.id=default
vm.heapSize=48
Spoiler: Partition data
$ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
254 0 1572864 zram0
179 0 30670848 mmcblk0
179 1 5120 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 35840 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 6144 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 1024 mmcblk0p8
259 1 1024 mmcblk0p9
259 2 1024 mmcblk0p10
259 3 4096 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 1024 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 1024 mmcblk0p17
259 10 1024 mmcblk0p18
259 11 1024 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 2048 mmcblk0p21
259 14 25600 mmcblk0p22
259 15 1024 mmcblk0p23
259 16 10240 mmcblk0p24
259 17 20480 mmcblk0p25
259 18 1024 mmcblk0p26
259 19 35840 mmcblk0p27
259 20 2867200 mmcblk0p28
259 21 153600 mmcblk0p29
259 22 409600 mmcblk0p30
259 23 1024 mmcblk0p31
259 24 1024 mmcblk0p32
259 25 27059183 mmcblk0p33
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 27059167 dm-0
output using the ls command with arguments that I forgot
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 boot -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 cache -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 fbootlogo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsbd -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsgl -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_deltanv -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_gdsp -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_ldsp -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_modem -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv1 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv2 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 pm_sys -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 recovery -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml_bak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 system -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos_bak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 uboot -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_log -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 userdata -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta_bak -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vendor -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 wcnmodem -> /dev/block/mmcblk0p20
Spoiler: Device information
Device name: Junsun A104
Android: 8.1. Oreo API level 27
CPU:
64bit
ARM64-V8A
Spreadtrum SC9832e
Memory: 2GB
Kernel architecture: aarch64
Kernel version: 4.4.83-00001-g213b4e3
dangelob said:
Hi,
This is my first project that I'm currently working on.
I recently bought a android dashcam which UI I would like to change based on my personal preferences. Unfortunately I'm struggling to setup an environment where I can test the changes I make before replacing the original UI on the device itself. I identified the SystemUI.apk to be the place where the manufacturer made customization. I will be using the SystemUI.apk built from AOSP and making my changes based on that. I had no luck trying to decompile the SystemUI.apk in a way that I could build it again.
I was thinking that I could use an android emulator to use the same ROM as the device itself. The manufacturer did not provide any support in providing stock firmware images in any way. So I used the following steps to 'export' the firmware.
1. Unlocking the bootloader using the Identifier Token so I can flash images using fastboot. TWRP was not an option here because I could not find any images for my device nor could I port an TWRP image myself.
2. Enable ADB debugging over usb
3. Enable ADB root privileges using the password: 2846 (if i remember correctly)
4. Use ADB remount and ADB root to gain privileges over the partitions
5. Gain information on partition data
6. Use ADB pull to export images based on partitions
After following the above steps the next thing was to import the images into an emulator. I used the following steps to do this:
1. Create a new device within Android Studio that has the same screen size and os.
2. Replace the system.img, ramdisk.img with the exported variants in ~/Android/Sdk/../arm64-v8a
3. Turn off EncryptUserData inside advancedFeatures.ini to prevent errors like partitions that are unable to encrypt
4. Use the command below to start the emulator
Code:
~/Android/Sdk/emulator/emulator -avd Junsun_A104_API_27 -verbose -show-kernel
5. After running the emulator I receive the error below and the screen of the emulator stays black.
Code:
Please append a correct "root=" boot option; here are the available partitions:
fe00 2867200 vda driver: virtio_blk
fe10 67584 vdb driver: virtio_blk
fe20 819200 vdc driver: virtio_blk
fe30 409600 vdd driver: virtio_blk
fe40 524288 vde driver: virtio_blk
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
My assumption is that the emulator does not contain the same partition model used on the device. I could try to export each partition but I wouldn't know how to let the emulator know how to use these partitions. I tried to export the kernel and import it inside the emulator without luck. I did not receive any errors that way.
So my main question is:
- Is there any way I can import the device's rom inside an android emulator
Spoiler: Emulator Config
AvdId=Junsun_A104_API_27
PlayStore.enabled=false
abi.type=arm64-v8a
avd.ini.displayname=Junsun A104 API 27
avd.ini.encoding=UTF-8
disk.dataPartition.size=800M
fastboot.chosenSnapshotFile=
fastboot.forceChosenSnapshotBoot=no
fastboot.forceColdBoot=no
fastboot.forceFastBoot=yes
hw.accelerometer=yes
hw.arc=false
hw.audioInput=yes
hw.battery=yes
hw.camera.back=virtualscene
hw.camera.front=emulated
hw.cpu.arch=arm64
hw.cpu.ncore=4
hw.dPad=no
hw.device.hash2=MD5:7834f5e80eb849ceb46ce01cd4c704f7
hw.device.manufacturer=User
hw.device.name=Junsun A104
hw.gps=yes
hw.gpu.enabled=no
hw.gpu.mode=off
hw.initialOrientation=landscape
hw.keyboard=yes
hw.lcd.density=120
hw.lcd.height=320
hw.lcd.width=1480
hw.mainKeys=no
hw.ramSize=2560
hw.sdCard=yes
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images/android-27/default/arm64-v8a/
runtime.network.latency=none
runtime.network.speed=full
sdcard.size=512M
showDeviceFrame=no
skin.dynamic=yes
skin.name=1480x320
skin.path=_no_skin
skin.path.backup=/home/dangelo/Android/Sdk/skins/tv_1080p
tag.display=Default Android System Image
tag.id=default
vm.heapSize=48
Spoiler: Partition data
$ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
254 0 1572864 zram0
179 0 30670848 mmcblk0
179 1 5120 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 35840 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 6144 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 1024 mmcblk0p8
259 1 1024 mmcblk0p9
259 2 1024 mmcblk0p10
259 3 4096 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 1024 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 1024 mmcblk0p17
259 10 1024 mmcblk0p18
259 11 1024 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 2048 mmcblk0p21
259 14 25600 mmcblk0p22
259 15 1024 mmcblk0p23
259 16 10240 mmcblk0p24
259 17 20480 mmcblk0p25
259 18 1024 mmcblk0p26
259 19 35840 mmcblk0p27
259 20 2867200 mmcblk0p28
259 21 153600 mmcblk0p29
259 22 409600 mmcblk0p30
259 23 1024 mmcblk0p31
259 24 1024 mmcblk0p32
259 25 27059183 mmcblk0p33
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 27059167 dm-0
output using the ls command with arguments that I forgot
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 boot -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 cache -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 fbootlogo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsbd -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsgl -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_deltanv -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_gdsp -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_ldsp -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_modem -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv1 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv2 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 pm_sys -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 recovery -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml_bak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 system -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos_bak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 uboot -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_log -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 userdata -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta_bak -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vendor -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 wcnmodem -> /dev/block/mmcblk0p20
Spoiler: Device information
Device name: Junsun A104
Android: 8.1. Oreo API level 27
CPU:
64bit
ARM64-V8A
Spreadtrum SC9832e
Memory: 2GB
Kernel architecture: aarch64
Kernel version: 4.4.83-00001-g213b4e3
Click to expand...
Click to collapse
All you should need is the system.img and the kernel, then extract the system.img untill you find the /system/app and/or the /system/priv-app(whichever folder contains your UI.apk), extract a copy of the UI.apk. Then use APKtool to remove the signature on the apk file then decompile the apk file then make your modifications then recompile and re-sign the apk file. Then place the newly modified UI.apk in the system folder where you extracted it from(overwrite/delete the old version of the apk). Then compress all the files back into the system.img like it was originally and then try to use your newly modified system.img in your emulator.
Try using Bluestacks or one of the other leading android emulators instead of using Android Studio.