Had my Note Edge for a really long time and felt this was overdue. Here's some useful information for developers.
Code:
1|[email protected]:/ # cat /proc/partitions
major minor #blocks name
253 0 1048576 vnswap0
179 0 30535680 mmcblk0
179 1 19456 mmcblk0p1
179 2 66464 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 64 mmcblk0p5
179 6 32 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 6144 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 14336 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 4 mmcblk0p16
179 17 17408 mmcblk0p17
179 18 19456 mmcblk0p18
179 19 4084 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 8 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 9216 mmcblk0p23
179 24 3891200 mmcblk0p24
179 25 512000 mmcblk0p25
179 26 25935852 mmcblk0p26
179 32 4096 mmcblk0rpmb
Code:
1|[email protected]:/ # ls -al dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2014-01-07 14:48 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-07 14:48 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-07 14:48 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-07 14:48 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-01-07 14:48 dbi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-07 14:48 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-07 14:48 efs -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-07 14:48 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-07 14:48 mdm1m9kefs1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-07 14:48 mdm1m9kefs2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-07 14:48 mdm1m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-07 14:48 mdm1m9kefsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-07 14:48 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-07 14:48 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-07 14:48 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-07 14:48 param -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-07 14:48 persdata -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-07 14:48 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-07 14:48 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-07 14:48 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-07 14:48 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-07 14:48 sbl1bak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-07 14:48 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-07 14:48 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-07 14:48 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-07 14:48 userdata -> /dev/block/mmcblk0p26
Hopefully this helps some of you guys
Waitning for a rom from you hehe
eterno13 said:
Waitning for a rom from you hehe
Click to expand...
Click to collapse
Working on it
Amazing!!
Hero said:
Had my Note Edge for a really long time
Click to expand...
Click to collapse
Wait... what?
Nothing yet?
eterno13 said:
Nothing yet?
Click to expand...
Click to collapse
Sorry, I had to return the Note Edge due to the previous owner having missed payments (meaning the phone was locked to the previous owner unless he paid his dues - which he refused to do).
Sorry, again
Sent from my A0001 using XDA Free mobile app
Thanks! Helped me fix my internal SD, used restorecon and /dev/block/mmcblk0p26
Sent from my SM-N915T using XDA Free mobile app
Q&A for [ROOT] LG G FLEX 2 (LS996-ZV6/Sprint) 5.1.1 Rooted!!!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT] LG G FLEX 2 (LS996-ZV6/Sprint) 5.1.1 Rooted!!!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I have the H955P. these are the codes...
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
254 0 462032 zram0
179 0 15267840 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 512 mmcblk0p33
259 2 2048 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 47104 mmcblk0p41
259 10 10240 mmcblk0p42
259 11 4096 mmcblk0p43
259 12 4096 mmcblk0p44
259 13 3670016 mmcblk0p45
259 14 262144 mmcblk0p46
259 15 1261568 mmcblk0p47
259 16 9625600 mmcblk0p48
259 17 14319 mmcblk0p49
179 32 4096 mmcblk0rpmb
179 64 15558144 mmcblk1
179 65 15557120 mmcblk1p1
Code:
[email protected]:/ $ ls -l /dev/block/platform/f9824900.sdhci/by-name
ls -l /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 1969-12-31 19:00 DDR -> /dev/block/mmcblk0
p29
lrwxrwxrwx root root 1969-12-31 19:00 aboot -> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 1969-12-31 19:00 abootbak -> /dev/block/mm
cblk0p14
lrwxrwxrwx root root 1969-12-31 19:00 apdp -> /dev/block/mmcblk
0p18
lrwxrwxrwx root root 1969-12-31 19:00 boot -> /dev/block/mmcblk
0p36
lrwxrwxrwx root root 1969-12-31 19:00 cache -> /dev/block/mmcbl
k0p47
lrwxrwxrwx root root 1969-12-31 19:00 cust -> /dev/block/mmcblk
0p46
lrwxrwxrwx root root 1969-12-31 19:00 devinfo -> /dev/block/mmc
blk0p17
lrwxrwxrwx root root 1969-12-31 19:00 dpo -> /dev/block/mmcblk0
p20
lrwxrwxrwx root root 1969-12-31 19:00 drm -> /dev/block/mmcblk0
p38
lrwxrwxrwx root root 1969-12-31 19:00 eksst -> /dev/block/mmcbl
k0p32
lrwxrwxrwx root root 1969-12-31 19:00 encrypt -> /dev/block/mmc
blk0p31
lrwxrwxrwx root root 1969-12-31 19:00 factory -> /dev/block/mmc
blk0p41
lrwxrwxrwx root root 1969-12-31 19:00 fota -> /dev/block/mmcblk
0p42
lrwxrwxrwx root root 1969-12-31 19:00 fsc -> /dev/block/mmcblk0
p26
lrwxrwxrwx root root 1969-12-31 19:00 fsg -> /dev/block/mmcblk0
p25
lrwxrwxrwx root root 1969-12-31 19:00 grow -> /dev/block/mmcblk
0p49
lrwxrwxrwx root root 1969-12-31 19:00 hyp -> /dev/block/mmcblk0
p6
lrwxrwxrwx root root 1969-12-31 19:00 hypbak -> /dev/block/mmcb
lk0p12
lrwxrwxrwx root root 1969-12-31 19:00 keystore -> /dev/block/mm
cblk0p28
lrwxrwxrwx root root 1969-12-31 19:00 laf -> /dev/block/mmcblk0
p35
lrwxrwxrwx root root 1969-12-31 19:00 limits -> /dev/block/mmcb
lk0p16
lrwxrwxrwx root root 1969-12-31 19:00 misc -> /dev/block/mmcblk
0p21
lrwxrwxrwx root root 1969-12-31 19:00 modem -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1969-12-31 19:00 modemst1 -> /dev/block/mm
cblk0p23
lrwxrwxrwx root root 1969-12-31 19:00 modemst2 -> /dev/block/mm
cblk0p24
lrwxrwxrwx root root 1969-12-31 19:00 mpt -> /dev/block/mmcblk0
p40
lrwxrwxrwx root root 1969-12-31 19:00 msadp -> /dev/block/mmcbl
k0p19
lrwxrwxrwx root root 1969-12-31 19:00 persist -> /dev/block/mmc
blk0p22
lrwxrwxrwx root root 1969-12-31 19:00 persistent -> /dev/block/
mmcblk0p34
lrwxrwxrwx root root 1969-12-31 19:00 pmic -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1969-12-31 19:00 pmicbak -> /dev/block/mmc
blk0p10
lrwxrwxrwx root root 1969-12-31 19:00 raw_resources -> /dev/blo
ck/mmcblk0p43
lrwxrwxrwx root root 1969-12-31 19:00 raw_resourcesbak -> /dev/
block/mmcblk0p44
lrwxrwxrwx root root 1969-12-31 19:00 rct -> /dev/block/mmcblk0
p33
lrwxrwxrwx root root 1969-12-31 19:00 recovery -> /dev/block/mm
cblk0p37
lrwxrwxrwx root root 1969-12-31 19:00 rpm -> /dev/block/mmcblk0
p7
lrwxrwxrwx root root 1969-12-31 19:00 rpmbak -> /dev/block/mmcb
lk0p13
lrwxrwxrwx root root 1969-12-31 19:00 sbl1 -> /dev/block/mmcblk
0p3
lrwxrwxrwx root root 1969-12-31 19:00 sbl1bak -> /dev/block/mmc
blk0p9
lrwxrwxrwx root root 1969-12-31 19:00 sdi -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 1969-12-31 19:00 sdibak -> /dev/block/mmcb
lk0p15
lrwxrwxrwx root root 1969-12-31 19:00 sec -> /dev/block/mmcblk0
p30
lrwxrwxrwx root root 1969-12-31 19:00 sns -> /dev/block/mmcblk0
p39
lrwxrwxrwx root root 1969-12-31 19:00 ssd -> /dev/block/mmcblk0
p27
lrwxrwxrwx root root 1969-12-31 19:00 system -> /dev/block/mmcb
lk0p45
lrwxrwxrwx root root 1969-12-31 19:00 tz -> /dev/block/mmcblk0p
4
lrwxrwxrwx root root 1969-12-31 19:00 tzbak -> /dev/block/mmcbl
k0p11
lrwxrwxrwx root root 1969-12-31 19:00 userdata -> /dev/block/mm
cblk0p48
yes yes yes
LG-H955
5.1.1
V15a-eur-XX
Yes i want root !!
cat /proc/partitions
major minor #blocks name
7 0 21936 loop0
7 1 21936 loop1
7 3 24024 loop3
7 4 71028 loop4
7 5 2092 loop5
7 6 49092 loop6
7 7 8356 loop7
254 0 462032 zram0
179 0 15267840 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 512 mmcblk0p33
259 2 2048 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 47104 mmcblk0p41
259 10 10240 mmcblk0p42
259 11 4096 mmcblk0p43
259 12 4096 mmcblk0p44
259 13 3670016 mmcblk0p45
259 14 262144 mmcblk0p46
259 15 1261568 mmcblk0p47
259 16 9625600 mmcblk0p48
259 17 14319 mmcblk0p49
179 32 4096 mmcblk0rpmb
179 64 62717952 mmcblk1
179 65 62701568 mmcblk1p1
253 0 21936 dm-0
253 1 21936 dm-1
253 3 24024 dm-3
253 4 71028 dm-4
253 5 2092 dm-5
253 6 49092 dm-6
253 7 8356 dm-7
7 8 3136 loop8
253 8 3136 dm-8
7 9 27160 loop9
253 9 27160 dm-9
7 10 34468 loop10
253 10 34468 dm-10
7 11 40736 loop11
253 11 40736 dm-11
7 12 6268 loop12
253 12 6268 dm-12
7 13 9404 loop13
253 13 9404 dm-13
7 14 2092 loop14
253 14 2092 dm-14
$ ls -l /dev/block/platform/f9824900.sdhci/by-name
ls -l /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-05-28 20:39 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-05-28 20:39 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-05-28 20:39 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-05-28 20:39 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-05-28 20:39 boot -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-05-28 20:39 cache -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 1970-05-28 20:39 cust -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 1970-05-28 20:39 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-05-28 20:39 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-05-28 20:39 drm -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-05-28 20:39 eksst -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-05-28 20:39 encrypt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-05-28 20:39 factory -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-05-28 20:39 fota -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-05-28 20:39 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-05-28 20:39 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-05-28 20:39 grow -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 1970-05-28 20:39 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-05-28 20:39 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-05-28 20:39 keystore -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-05-28 20:39 laf -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-05-28 20:39 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-05-28 20:39 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-05-28 20:39 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-05-28 20:39 modemst1 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-05-28 20:39 modemst2 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-05-28 20:39 mpt -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-05-28 20:39 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-05-28 20:39 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-05-28 20:39 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-05-28 20:39 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-05-28 20:39 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-05-28 20:39 raw_resources -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-05-28 20:39 raw_resourcesbak -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-05-28 20:39 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-05-28 20:39 recovery -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-05-28 20:39 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-05-28 20:39 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-05-28 20:39 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-05-28 20:39 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-05-28 20:39 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-05-28 20:39 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-05-28 20:39 sec -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-05-28 20:39 sns -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-05-28 20:39 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-05-28 20:39 system -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-05-28 20:39 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-05-28 20:39 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-05-28 20:39 userdata -> /dev/block/mmcblk0p48
LG-H955
5.1.1
V15a-eur-XX
Yes i want root too!!
Code:
1|[email protected]:/ $ cat /proc/partitions
major minor #blocks name
7 2 10448 loop2
254 0 462032 zram0
179 0 15267840 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 512 mmcblk0p33
259 2 2048 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 47104 mmcblk0p41
259 10 10240 mmcblk0p42
259 11 4096 mmcblk0p43
259 12 4096 mmcblk0p44
259 13 3670016 mmcblk0p45
259 14 262144 mmcblk0p46
259 15 1261568 mmcblk0p47
259 16 9625600 mmcblk0p48
259 17 14319 mmcblk0p49
179 32 4096 mmcblk0rpmb
179 64 62367744 mmcblk1
179 65 62351360 mmcblk1p1
253 2 10448 dm-2
Code:
[email protected]:/ $ ls -l /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-05-21 21:28 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-05-21 21:28 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-05-21 21:28 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-05-21 21:28 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-05-21 21:28 boot -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-05-21 21:28 cache -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 1970-05-21 21:28 cust -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 1970-05-21 21:28 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-05-21 21:28 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-05-21 21:28 drm -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-05-21 21:28 eksst -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-05-21 21:28 encrypt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-05-21 21:28 factory -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-05-21 21:28 fota -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-05-21 21:28 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-05-21 21:28 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-05-21 21:28 grow -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 1970-05-21 21:28 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-05-21 21:28 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-05-21 21:28 keystore -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-05-21 21:28 laf -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-05-21 21:28 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-05-21 21:28 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-05-21 21:28 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-05-21 21:28 modemst1 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-05-21 21:28 modemst2 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-05-21 21:28 mpt -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-05-21 21:28 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-05-21 21:28 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-05-21 21:28 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-05-21 21:28 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-05-21 21:28 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-05-21 21:28 raw_resources -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-05-21 21:28 raw_resourcesbak -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-05-21 21:28 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-05-21 21:28 recovery -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-05-21 21:28 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-05-21 21:28 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-05-21 21:28 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-05-21 21:28 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-05-21 21:28 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-05-21 21:28 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-05-21 21:28 sec -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-05-21 21:28 sns -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-05-21 21:28 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-05-21 21:28 system -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-05-21 21:28 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-05-21 21:28 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-05-21 21:28 userdata -> /dev/block/mmcblk0p48
We can only encourage developers to find method to root flex2....and pay them a beer afterwards!
Poslano z mojega LG-H955 z uporabo Tapatalk
Bravo to all of you!!!
xjoncastx said:
I have the H955P. these are the codes...
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
254 0 462032 zram0
179 0 15267840 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 512 mmcblk0p33
259 2 2048 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 47104 mmcblk0p41
259 10 10240 mmcblk0p42
259 11 4096 mmcblk0p43
259 12 4096 mmcblk0p44
259 13 3670016 mmcblk0p45
259 14 262144 mmcblk0p46
259 15 1261568 mmcblk0p47
259 16 9625600 mmcblk0p48
259 17 14319 mmcblk0p49
179 32 4096 mmcblk0rpmb
179 64 15558144 mmcblk1
179 65 15557120 mmcblk1p1
Code:
[email protected]:/ $ ls -l /dev/block/platform/f9824900.sdhci/by-name
ls -l /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 1969-12-31 19:00 DDR -> /dev/block/mmcblk0
p29
lrwxrwxrwx root root 1969-12-31 19:00 aboot -> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 1969-12-31 19:00 abootbak -> /dev/block/mm
cblk0p14
lrwxrwxrwx root root 1969-12-31 19:00 apdp -> /dev/block/mmcblk
0p18
lrwxrwxrwx root root 1969-12-31 19:00 boot -> /dev/block/mmcblk
0p36
lrwxrwxrwx root root 1969-12-31 19:00 cache -> /dev/block/mmcbl
k0p47
lrwxrwxrwx root root 1969-12-31 19:00 cust -> /dev/block/mmcblk
0p46
lrwxrwxrwx root root 1969-12-31 19:00 devinfo -> /dev/block/mmc
blk0p17
lrwxrwxrwx root root 1969-12-31 19:00 dpo -> /dev/block/mmcblk0
p20
lrwxrwxrwx root root 1969-12-31 19:00 drm -> /dev/block/mmcblk0
p38
lrwxrwxrwx root root 1969-12-31 19:00 eksst -> /dev/block/mmcbl
k0p32
lrwxrwxrwx root root 1969-12-31 19:00 encrypt -> /dev/block/mmc
blk0p31
lrwxrwxrwx root root 1969-12-31 19:00 factory -> /dev/block/mmc
blk0p41
lrwxrwxrwx root root 1969-12-31 19:00 fota -> /dev/block/mmcblk
0p42
lrwxrwxrwx root root 1969-12-31 19:00 fsc -> /dev/block/mmcblk0
p26
lrwxrwxrwx root root 1969-12-31 19:00 fsg -> /dev/block/mmcblk0
p25
lrwxrwxrwx root root 1969-12-31 19:00 grow -> /dev/block/mmcblk
0p49
lrwxrwxrwx root root 1969-12-31 19:00 hyp -> /dev/block/mmcblk0
p6
lrwxrwxrwx root root 1969-12-31 19:00 hypbak -> /dev/block/mmcb
lk0p12
lrwxrwxrwx root root 1969-12-31 19:00 keystore -> /dev/block/mm
cblk0p28
lrwxrwxrwx root root 1969-12-31 19:00 laf -> /dev/block/mmcblk0
p35
lrwxrwxrwx root root 1969-12-31 19:00 limits -> /dev/block/mmcb
lk0p16
lrwxrwxrwx root root 1969-12-31 19:00 misc -> /dev/block/mmcblk
0p21
lrwxrwxrwx root root 1969-12-31 19:00 modem -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1969-12-31 19:00 modemst1 -> /dev/block/mm
cblk0p23
lrwxrwxrwx root root 1969-12-31 19:00 modemst2 -> /dev/block/mm
cblk0p24
lrwxrwxrwx root root 1969-12-31 19:00 mpt -> /dev/block/mmcblk0
p40
lrwxrwxrwx root root 1969-12-31 19:00 msadp -> /dev/block/mmcbl
k0p19
lrwxrwxrwx root root 1969-12-31 19:00 persist -> /dev/block/mmc
blk0p22
lrwxrwxrwx root root 1969-12-31 19:00 persistent -> /dev/block/
mmcblk0p34
lrwxrwxrwx root root 1969-12-31 19:00 pmic -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1969-12-31 19:00 pmicbak -> /dev/block/mmc
blk0p10
lrwxrwxrwx root root 1969-12-31 19:00 raw_resources -> /dev/blo
ck/mmcblk0p43
lrwxrwxrwx root root 1969-12-31 19:00 raw_resourcesbak -> /dev/
block/mmcblk0p44
lrwxrwxrwx root root 1969-12-31 19:00 rct -> /dev/block/mmcblk0
p33
lrwxrwxrwx root root 1969-12-31 19:00 recovery -> /dev/block/mm
cblk0p37
lrwxrwxrwx root root 1969-12-31 19:00 rpm -> /dev/block/mmcblk0
p7
lrwxrwxrwx root root 1969-12-31 19:00 rpmbak -> /dev/block/mmcb
lk0p13
lrwxrwxrwx root root 1969-12-31 19:00 sbl1 -> /dev/block/mmcblk
0p3
lrwxrwxrwx root root 1969-12-31 19:00 sbl1bak -> /dev/block/mmc
blk0p9
lrwxrwxrwx root root 1969-12-31 19:00 sdi -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 1969-12-31 19:00 sdibak -> /dev/block/mmcb
lk0p15
lrwxrwxrwx root root 1969-12-31 19:00 sec -> /dev/block/mmcblk0
p30
lrwxrwxrwx root root 1969-12-31 19:00 sns -> /dev/block/mmcblk0
p39
lrwxrwxrwx root root 1969-12-31 19:00 ssd -> /dev/block/mmcblk0
p27
lrwxrwxrwx root root 1969-12-31 19:00 system -> /dev/block/mmcb
lk0p45
lrwxrwxrwx root root 1969-12-31 19:00 tz -> /dev/block/mmcblk0p
4
lrwxrwxrwx root root 1969-12-31 19:00 tzbak -> /dev/block/mmcbl
k0p11
lrwxrwxrwx root root 1969-12-31 19:00 userdata -> /dev/block/mm
cblk0p48
Click to expand...
Click to collapse
Lolipop 5.1.1
V15a claro Perú
Enviado desde mi LG-H955 mediante Tapatalk
Root for LS996zv6 and LS996zv7 is relased!!!!
How to root H955 5.1.1?
Wysłane z mojego LG-H955 przy użyciu Tapatalka
here : LGH959 V15A Taiwan
C:\LG_Root>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
254 0 462032 zram0
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 512 mmcblk0p33
259 2 2048 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 47104 mmcblk0p41
259 10 10240 mmcblk0p42
259 11 4096 mmcblk0p43
259 12 4096 mmcblk0p44
259 13 3670016 mmcblk0p45
259 14 262144 mmcblk0p46
259 15 1261568 mmcblk0p47
259 16 24870912 mmcblk0p48
259 17 45039 mmcblk0p49
179 32 4096 mmcblk0rpmb
179 64 62652416 mmcblk1
179 65 62636032 mmcblk1p1
[email protected]:/ $
Thanks for all the work on the root!
Now that we have root on 5.1.1, is there any chance of a bootloader unlock in the future, or is that still impossible to do?
Sent from my LG-H955
please backup dump file zv6
---------- Post added at 02:26 PM ---------- Previous post was at 02:13 PM ----------
please backup dump file zv6 help me
HTML:
adb shell
su
dd if = / dev / block / mmcblk0 of = / sdcard / dump.img bs = 1024 count = 2.048 million
Is there any chance someone can make a step by ststep guide of how to do the root and put it on a different thread, its very difficult to navigate and follow instructions on this one.
Hello everyone and thanks for that tuto!
I followed it but I kind of bricked my phone. I only have access to the Download / Firmware update mode.
I dropped the image in my phone executed the command being on port COM4. Not sure when it went wrong.
I am/was using a LS996 ZV6 5.0.1 STOCK but Rooted.
So I wanted to follow the 5.1.1 guide, but now I have this boot issue 'SECURITY ERROR'. Any chance you guys could give me a lead?
Thank you!
Rick!
RICK! said:
Hello everyone and thanks for that tuto!
I followed it but I kind of bricked my phone. I only have access to the Download / Firmware update mode.
I dropped the image in my phone executed the command being on port COM4. Not sure when it went wrong.
I am/was using a LS996 ZV6 5.0.1 STOCK but Rooted.
So I wanted to follow the 5.1.1 guide, but now I have this boot issue 'SECURITY ERROR'. Any chance you guys could give me a lead?
Thank you!
Rick!
Click to expand...
Click to collapse
zv6 is 5.1.1...zv5 is 5.0.1 ..on which were you when u tried root
Damn!
I was pretty sure I saw SV6 on my version before starting the whole process.
Would you say that: http://forum.xda-developers.com/g-flex2/general/guide-lg-g-flex-2-stock-firmware-to-t3037593 would get me out of my bootloop?
Finally root in 5.1.1, now just wait for it
xjoncastx said:
Finally root in 5.1.1, now just wait for it
Click to expand...
Click to collapse
are you on H955 5.0.1 if the answer is yes we need oyur help.
randrew87 said:
are you on H955 5.0.1 if the answer is yes we need oyur help.
Click to expand...
Click to collapse
Im sorry, already updated to 5.1.1
---------- Post added at 07:50 AM ---------- Previous post was at 07:17 AM ----------
H955P is same that H955 ???
I am on 5.0.1 with root (H955)
Hi, is it possible to inject root (5.1.1) by myself (H955) now, like G4?
I am trying to take an image of my Android phone. Specifically I have tried to image the system and boot partitions. The imaging process appears to work correctly when using dd. However, when I attempt to mount the image in a loopback device the image appears to be empty. I also tried to see file contents by piping through cpio. Basically, I am trying to validate the image that I took. What am I doing wrong? Is there a problem with how I took the image or validation or both? Here are the steps to took (you'll see only the system partition below but I used the same process for boot)
[[email protected] platform-tools]# ./adb devices
List of devices attached
99000421100783 device
[[email protected] platform-tools]#./adb shell
[email protected]:/ $ su
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 4096 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 819200 mmcblk0p21
179 22 658432 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 6144 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1024 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 5120 mmcblk0p28
179 29 4718592 mmcblk0p29
179 30 1048576 mmcblk0p30
179 31 8192 mmcblk0p31
259 0 20480 mmcblk0p32
259 1 4096 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 16384 mmcblk0p35
259 4 1024 mmcblk0p36
259 5 1024 mmcblk0p37
259 6 1024 mmcblk0p38
259 7 1024 mmcblk0p39
259 8 20480 mmcblk0p40
259 9 20480 mmcblk0p41
259 10 4096 mmcblk0p42
259 11 4096 mmcblk0p43
259 12 95215 mmcblk0p44
179 32 512 mmcblk0rpmb
179 64 30183936 mmcblk1
179 65 30182912 mmcblk1p1
254 0 4718592 dm-0
254 1 1048576 dm-1
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC 8WMB3R (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 71.3MB 67.1MB fat16 modem
2 71.3MB 72.4MB 1049kB sbl1
3 72.4MB 73.4MB 1049kB sbl1bak
4 73.4MB 74.4MB 1049kB sdi
5 75.5MB 76.5MB 1049kB DDR
6 79.7MB 80.7MB 1049kB aboot
7 80.7MB 81.8MB 1049kB abootbak
8 81.8MB 82.8MB 1049kB rpm
9 82.8MB 83.9MB 1049kB rpmbak
10 83.9MB 101MB 16.8MB boot
11 101MB 102MB 1049kB tz
12 102MB 103MB 1049kB tzbak
13 103MB 104MB 1049kB pad
14 104MB 105MB 1573kB modemst1
15 105MB 107MB 1573kB modemst2
16 107MB 109MB 2097kB reserve1
17 109MB 117MB 8389kB dnand
18 117MB 122MB 4194kB bfss1
19 122MB 130MB 8389kB bfss2
20 130MB 138MB 8389kB ext4 persist
21 138MB 977MB 839MB ext4 system
22 977MB 1652MB 674MB ext4 cache
23 1652MB 1668MB 16.8MB recovery
24 1668MB 1675MB 6291kB misc
25 1678MB 1686MB 8389kB fsg
26 1686MB 1687MB 1049kB fsc
27 1687MB 1688MB 1049kB ssd
28 1688MB 1693MB 5243kB reserve2
29 1693MB 6525MB 4832MB userdata
30 6525MB 7599MB 1074MB internalstorage
31 7599MB 7607MB 8389kB ext4 sysprop
32 7607MB 7628MB 21.0MB ext4 carrier
33 7628MB 7633MB 4194kB fotamng
34 7633MB 7649MB 16.8MB fota
35 7649MB 7666MB 16.8MB fotabk
36 7666MB 7667MB 1049kB sdibk
37 7667MB 7668MB 1049kB abootbk
38 7668MB 7669MB 1049kB rpmbk
39 7669MB 7670MB 1049kB tzbk
40 7670MB 7691MB 21.0MB log
41 7691MB 7712MB 21.0MB logwork
42 7712MB 7716MB 4194kB bootwork
43 7716MB 7721MB 4194kB rom
44 7721MB 7818MB 97.5MB reserve3
(parted) q
q
[email protected]:/ # cd /dev/block/platform/msm_sdcc.1/by-name
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
lrwxrwxrwx root root 1969-12-31 19:17 DDR -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 19:17 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 19:17 abootbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 19:17 abootbk -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1969-12-31 19:17 bfss1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 19:17 bfss2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 19:17 boot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 19:17 bootwork -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1969-12-31 19:17 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 19:17 carrier -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1969-12-31 19:17 dnand -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 19:17 fota -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1969-12-31 19:17 fotabk -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1969-12-31 19:17 fotamng -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1969-12-31 19:17 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1969-12-31 19:17 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1969-12-31 19:17 internalstorage -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1969-12-31 19:17 log -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1969-12-31 19:17 logwork -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1969-12-31 19:17 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 19:17 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 19:17 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 19:17 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 19:17 pad -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 19:17 persist -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 19:17 recovery -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 19:17 reserve1 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 19:17 reserve2 -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1969-12-31 19:17 reserve3 -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1969-12-31 19:17 rom -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1969-12-31 19:17 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 19:17 rpmbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 19:17 rpmbk -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1969-12-31 19:17 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 19:17 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 19:17 sdi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 19:17 sdibk -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1969-12-31 19:17 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1969-12-31 19:17 sysprop -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1969-12-31 19:17 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 19:17 tz -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 19:17 tzbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 19:17 tzbk -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1969-12-31 19:17 userdata -> /dev/block/mmcblk0p29
[email protected]:/ # dd if=/dev/block/mmcblk0p21 of=/mnt/media_rw/sdcard0/firmware-img/kyocerasystem.img bs=4096 conv=noerror,sync
204800+0 records in
204800+0 records out
838860800 bytes transferred in 40.461 secs (20732577 bytes/sec)
[email protected]:/ # exit
[email protected]:/ $ exit
[[email protected] jeremy]:/ # losetup /dev/loop0 /home/jeremy/kyocerasystem.img
[[email protected] jeremy]:/ # mkfs.ext4 /dev/loop0
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: 4096/204800: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
51296 inodes, 204800 blocks
10240 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=209715200
7 block groups
32768 blocks per group, 32768 fragments per group
7328 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: 0/7: done
Writing inode tables: 0/7: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7: done
[[email protected] jeremy]:/ # mount -t ext4 /dev/loop0 /mnt
[[email protected] jeremy]:/ # cd /mnt
[[email protected] jeremy]:/ # ls
lost+found
[email protected] jeremy]# dd if=kyocerasystem.img | cpio -ictv > kyocerasystem.txt
1638400+0 records in
1638400+0 records out
838860800 bytes (839 MB) copied, 25.1643 s, 33.3 MB/s
cpio: premature end of file
[[email protected] jeremy]:/ # less kyocerasystem.txt
(no contents to display - empty)
Just found my answer, I should not have done a mkfs (thus formatting/wiping my data in the image)
Do... what, now?
Would you be so kind as to walk me through what you did here? with
red comments/ descriptions?
and
[green command inputs
Or something like that?
So Retroid recently came out with the RP3+.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-It runs Android 11
-Has an option in developer settings for OEM unlocking
-Easy access to adb and fastboot
AND you can run shell scripts as ROOT from within the settings.
For now I'm simply trying to make a backup boot.img
The typical command would be:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
But the file does not exist.
Ive been able to run some basic scripts successfully from the run shell script as root option leading to a complete file list of everything on the system.
Here is a list of all the files in ./dev/block/
./dev/block./dev/block/loop27./dev/block/dm-13./dev/block/dm-12./dev/blo - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
Any help with rooting this device or simply backing up the system would be greatly appreciated.
ApatheticEuphoria said:
So Retroid recently came out with the RP3+.
-It runs Android 11
-Has an option in developer settings for OEM unlocking
-Easy access to adb and fastboot
AND you can run shell scripts as ROOT from within the settings.
For now I'm simply trying to make a backup boot.img
The typical command would be:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
But the file does not exist.
Ive been able to run some basic scripts successfully from the run shell script as root option leading to a complete file list of everything on the system.
Here is a list of all the files in ./dev/block/
./dev/block./dev/block/loop27./dev/block/dm-13./dev/block/dm-12./dev/blo - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
Any help with rooting this device or simply backing up the system would be greatly appreciated.
Click to expand...
Click to collapse
It's always difficult when the firmware isn't readily available for download. But it sounds like you're on the right track - dump the boot image, patch in Magisk, unlock the bootloader, and flash the patched image for root.
Try this guide, it sounds like you just need to establish where the boot partition is mounted
V0latyle said:
It's always difficult when the firmware isn't readily available for download. But it sounds like you're on the right track - dump the boot image, patch in Magisk, unlock the bootloader, and flash the patched image for root.
Try this guide, it sounds like you just need to establish where the boot partition is mounted
Click to expand...
Click to collapse
Thank you very much for the guide. It is indeed a start.
Here are the results from Ways #1,2:
Code:
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
7 0 888 loop0
7 1 24676 loop1
7 2 84832 loop2
7 3 5152 loop3
7 4 111128 loop4
7 5 1904 loop5
7 6 888 loop6
7 7 24676 loop7
7 8 6564 loop8
7 9 8608 loop9
7 10 5020 loop10
7 11 736 loop11
7 12 740 loop12
7 13 19040 loop13
7 14 18372 loop14
7 15 3784 loop15
254 0 2222624 zram0
259 0 64 pmem0
179 0 122142720 mmcblk0
179 1 10240 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
259 1 1024 mmcblk0p8
259 2 1024 mmcblk0p9
259 3 4096 mmcblk0p10
259 4 8192 mmcblk0p11
259 5 8192 mmcblk0p12
259 6 2048 mmcblk0p13
259 7 2048 mmcblk0p14
259 8 2048 mmcblk0p15
259 9 2048 mmcblk0p16
259 10 2048 mmcblk0p17
259 11 2048 mmcblk0p18
259 12 1024 mmcblk0p19
259 13 1024 mmcblk0p20
259 14 10240 mmcblk0p21
259 15 10240 mmcblk0p22
259 16 2048 mmcblk0p23
259 17 25600 mmcblk0p24
259 18 25600 mmcblk0p25
259 19 1024 mmcblk0p26
259 20 1024 mmcblk0p27
259 21 10240 mmcblk0p28
259 22 10240 mmcblk0p29
259 23 20480 mmcblk0p30
259 24 20480 mmcblk0p31
259 25 6144 mmcblk0p32
259 26 6144 mmcblk0p33
259 27 1024 mmcblk0p34
259 28 1024 mmcblk0p35
259 29 1024 mmcblk0p36
259 30 1024 mmcblk0p37
259 31 1024 mmcblk0p38
259 32 1024 mmcblk0p39
259 33 10240 mmcblk0p40
259 34 10240 mmcblk0p41
259 35 65536 mmcblk0p42
259 36 65536 mmcblk0p43
259 37 102400 mmcblk0p44
259 38 102400 mmcblk0p45
259 39 8192 mmcblk0p46
259 40 8192 mmcblk0p47
259 41 8192 mmcblk0p48
259 42 8192 mmcblk0p49
259 43 6500352 mmcblk0p50
259 44 102400 mmcblk0p51
259 45 76800 mmcblk0p52
259 46 76800 mmcblk0p53
259 47 25600 mmcblk0p54
259 48 25600 mmcblk0p55
259 49 1024 mmcblk0p56
259 50 1024 mmcblk0p57
259 51 16384 mmcblk0p58
259 52 10240 mmcblk0p59
259 53 1024 mmcblk0p60
259 54 1024 mmcblk0p61
259 55 1024 mmcblk0p62
259 56 1024 mmcblk0p63
259 57 1024 mmcblk0p64
259 58 1024 mmcblk0p65
259 59 1024 mmcblk0p66
259 60 1024 mmcblk0p67
259 61 1024 mmcblk0p68
259 62 1024 mmcblk0p69
259 63 1024 mmcblk0p70
259 64 1024 mmcblk0p71
259 65 8192 mmcblk0p72
259 66 8192 mmcblk0p73
259 67 16384 mmcblk0p74
259 68 16384 mmcblk0p75
259 69 114635759 mmcblk0p76
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179 24 125173760 mmcblk1
179 25 125157376 mmcblk1p1
253 0 1266204 dm-0
253 1 370464 dm-1
253 2 1733700 dm-2
253 3 595004 dm-3
253 4 1160912 dm-4
253 5 113704 dm-5
253 6 1244960 dm-6
253 7 1246136 dm-7
253 8 364532 dm-8
253 9 1706256 dm-9
253 10 585532 dm-10
7 16 6084 loop16
7 17 84832 loop17
7 18 10184 loop18
7 19 5152 loop19
7 20 264 loop20
7 21 7948 loop21
7 22 4732 loop22
7 23 2812 loop23
7 24 111128 loop24
7 25 1904 loop25
7 26 3732 loop26
253 11 75508 dm-11
253 12 25116 dm-12
253 13 114635756 dm-13
7 27 153600 loop27
Code:
total 0
drwxr-xr-x 2 root root 1560 2023-01-11 05:33 .
drwxr-xr-x 3 root root 1640 2023-01-11 05:33 ..
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 avbmeta_rs_a -> /dev/block/mmcblk0p70
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 avbmeta_rs_b -> /dev/block/mmcblk0p71
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 boot_a -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 boot_b -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 cache -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 common_rs1_a -> /dev/block/mmcblk0p72
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 common_rs1_b -> /dev/block/mmcblk0p73
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 common_rs2_a -> /dev/block/mmcblk0p74
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 common_rs2_b -> /dev/block/mmcblk0p75
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 dtb_a -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 dtb_b -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 dtbo_a -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 dtbo_b -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 fbootlogo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 gnssmodem_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 gnssmodem_b -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 hypervsior_a -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 hypervsior_b -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_agdsp_a -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_agdsp_b -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_cdsp_a -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_cdsp_b -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_deltanv_a -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_deltanv_b -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_fixnv1_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_fixnv1_b -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_fixnv2_a -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_fixnv2_b -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_gdsp_a -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_gdsp_b -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_ldsp_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_ldsp_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_modem_a -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_modem_b -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_runtimenv1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_runtimenv2 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 metadata -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 misc -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 odmko_a -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 odmko_b -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 pm_sys_a -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 pm_sys_b -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 sml_a -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 sml_b -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 socko_a -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 socko_b -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 super -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 sysdumpdb -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 teecfg_a -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 teecfg_b -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 trustos_a -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 trustos_b -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 uboot_a -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 uboot_b -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 uboot_log -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 userdata -> /dev/block/mmcblk0p76
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_a -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_b -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_odm_a -> /dev/block/mmcblk0p68
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_odm_b -> /dev/block/mmcblk0p69
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_product_a -> /dev/block/mmcblk0p66
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_product_b -> /dev/block/mmcblk0p67
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_system_a -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_system_b -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_system_ext_a -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_system_ext_b -> /dev/block/mmcblk0p65
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_vendor_a -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_vendor_b -> /dev/block/mmcblk0p63
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vendor_boot_a -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vendor_boot_b -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 wcnmodem_a -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 wcnmodem_b -> /dev/block/mmcblk0p22
ApatheticEuphoria said:
Thank you. Its a start. Tried Way #1 and got some info. Way #2 isnt working (Removed the color code*)
Code:
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
7 0 888 loop0
7 1 24676 loop1
7 2 84832 loop2
7 3 5152 loop3
7 4 111128 loop4
7 5 1904 loop5
7 6 888 loop6
7 7 24676 loop7
7 8 6564 loop8
7 9 8608 loop9
7 10 5020 loop10
7 11 736 loop11
7 12 740 loop12
7 13 19040 loop13
7 14 18372 loop14
7 15 3784 loop15
254 0 2222624 zram0
259 0 64 pmem0
179 0 122142720 mmcblk0
179 1 10240 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
259 1 1024 mmcblk0p8
259 2 1024 mmcblk0p9
259 3 4096 mmcblk0p10
259 4 8192 mmcblk0p11
259 5 8192 mmcblk0p12
259 6 2048 mmcblk0p13
259 7 2048 mmcblk0p14
259 8 2048 mmcblk0p15
259 9 2048 mmcblk0p16
259 10 2048 mmcblk0p17
259 11 2048 mmcblk0p18
259 12 1024 mmcblk0p19
259 13 1024 mmcblk0p20
259 14 10240 mmcblk0p21
259 15 10240 mmcblk0p22
259 16 2048 mmcblk0p23
259 17 25600 mmcblk0p24
259 18 25600 mmcblk0p25
259 19 1024 mmcblk0p26
259 20 1024 mmcblk0p27
259 21 10240 mmcblk0p28
259 22 10240 mmcblk0p29
259 23 20480 mmcblk0p30
259 24 20480 mmcblk0p31
259 25 6144 mmcblk0p32
259 26 6144 mmcblk0p33
259 27 1024 mmcblk0p34
259 28 1024 mmcblk0p35
259 29 1024 mmcblk0p36
259 30 1024 mmcblk0p37
259 31 1024 mmcblk0p38
259 32 1024 mmcblk0p39
259 33 10240 mmcblk0p40
259 34 10240 mmcblk0p41
259 35 65536 mmcblk0p42
259 36 65536 mmcblk0p43
259 37 102400 mmcblk0p44
259 38 102400 mmcblk0p45
259 39 8192 mmcblk0p46
259 40 8192 mmcblk0p47
259 41 8192 mmcblk0p48
259 42 8192 mmcblk0p49
259 43 6500352 mmcblk0p50
259 44 102400 mmcblk0p51
259 45 76800 mmcblk0p52
259 46 76800 mmcblk0p53
259 47 25600 mmcblk0p54
259 48 25600 mmcblk0p55
259 49 1024 mmcblk0p56
259 50 1024 mmcblk0p57
259 51 16384 mmcblk0p58
259 52 10240 mmcblk0p59
259 53 1024 mmcblk0p60
259 54 1024 mmcblk0p61
259 55 1024 mmcblk0p62
259 56 1024 mmcblk0p63
259 57 1024 mmcblk0p64
259 58 1024 mmcblk0p65
259 59 1024 mmcblk0p66
259 60 1024 mmcblk0p67
259 61 1024 mmcblk0p68
259 62 1024 mmcblk0p69
259 63 1024 mmcblk0p70
259 64 1024 mmcblk0p71
259 65 8192 mmcblk0p72
259 66 8192 mmcblk0p73
259 67 16384 mmcblk0p74
259 68 16384 mmcblk0p75
259 69 114635759 mmcblk0p76
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179 24 125173760 mmcblk1
179 25 125157376 mmcblk1p1
253 0 1266204 dm-0
253 1 370464 dm-1
253 2 1733700 dm-2
253 3 595004 dm-3
253 4 1160912 dm-4
253 5 113704 dm-5
253 6 1244960 dm-6
253 7 1246136 dm-7
253 8 364532 dm-8
253 9 1706256 dm-9
253 10 585532 dm-10
7 16 6084 loop16
7 17 84832 loop17
7 18 10184 loop18
7 19 5152 loop19
7 20 264 loop20
7 21 7948 loop21
7 22 4732 loop22
7 23 2812 loop23
7 24 111128 loop24
7 25 1904 loop25
7 26 3732 loop26
253 11 75508 dm-11
253 12 25116 dm-12
253 13 114635756 dm-13
7 27 153600 loop27
Click to expand...
Click to collapse
So you just need to figure out which partition is /boot. There's a way to do this but I forget how.
I did find this on Stack Exchange:
Run find /dev -name 'by-name' 2>/dev/null to find the by-name directory. It should list one, though if there are a couple, it shouldn't be a problem and both should work.
Take the directory name and run ls -la <by-name-directory> (replacing the place holder with the actual directory name)
Find the name of the partition you are interested in - if you want just the kernel, the name is boot, or if your device has multiple slots, it is probably boot_a - and record the physical partition path listed for it. It should be something like /dev/block/mmcblk0p22 (this is on my Mi A1 device - if you have a different one, the number after "p" will be different and possibly even the number before "p").
Click to expand...
Click to collapse
There's also this guide. At least you're able to run shell as root, that's a huge advantage.
V0latyle said:
So you just need to figure out which partition is /boot. There's a way to do this but I forget how.
I did find this on Stack Exchange:
There's also this guide. At least you're able to run shell as root, that's a huge advantage.
Click to expand...
Click to collapse
Right?! I seen that as an option and just had to see what I could do with it.
So to see the partitions I put in
Code:
ls -al /dev/block/platform/soc/soc:ap-apb/71400000.sdio/by-name/ > /sdcard/info.txt
Saved as info.sh and ran from the run root script option.
(The output file will be stored in Internal Storage for whatever reason.)
To backup the boot images I put in
Code:
dd if=/dev/block/mmcblk0p42 of=/sdcard/boot_a.img
dd if=/dev/block/mmcblk0p43 of=/sdcard/boot_b.img
and again saved as getboot.sh and ran from the setting.
So according to this guide:
Patch Stock Boot Image via Magisk and Flash it using Fastboot
If you want to root your Android device then you can check out how to Patch Stock Boot Image via Magisk and Flash it using Fastboot method.
www.getdroidtips.com
It seems to have an A/B partition.
Ive backed up my boot.img files.
Patched them with Magisk.
They're ready to flash.
Code:
sending 'boot_a' (65536 KB)...
OKAY [ 1.478s]
writing 'boot_a'...
FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)
finished. total time: 1.498s
As expected.
To unlock Bootloader, I am hesitant to try anything yet.
With help from some kind and knowledgeable members of the official Discord I got the bootloader unlocked.
However they advised me NOT to flash the magisk patched boot.img until it is "resigned with avbtool to match what the keys are in vbmeta."
They said if I try and flash as is I will likely brick or get stuck in bootloop.
So I'll need help with that part. No idea how to do that.
Here's what I did to get the bootloader unlocked:
Back up Internal Storage (User data will be erased).
Install the drivers from here https://androiddatahost.com/dsa6h
Boot the RP3+ into the Bootloader by powering off the device, Pressing and holding the PWR and VOL + buttons until it boots to recovery and then select reboot to bootloader from the recovery options.
Connect the device to the PC and go to https://turtleletortue.github.io/subut-rehost/ on Google Chrome.
Click Connect.
Click "fastboot gadget" and connect.
Click Unlock.
On the device there will be a warning "Warning: Unlock device may erase user data. Press volume down button to confirm that. Press volume up button to cancel."
Press volume down.
Wait for it to complete.
Then reboot by pressing and holding PWR and Vol down.
There is a warning everytime I reboot but it goes away shortly and boots normally.
ApatheticEuphoria said:
With help from some kind and knowledgeable members of the official Discord I got the bootloader unlocked.
However they advised me NOT to flash the magisk patched boot.img until it is "resigned with avbtool to match what the keys are in vbmeta."
They said if I try and flash as is I will likely brick or get stuck in bootloop.
So I'll need help with that part. No idea how to do that.
Here's what I did to get the bootloader unlocked:
Back up Internal Storage (User data will be erased).
Install the drivers from here https://androiddatahost.com/dsa6h
Boot the RP3+ into the Bootloader by powering off the device, Pressing and holding the PWR and VOL + buttons until it boots to recovery and then select reboot to bootloader from the recovery options.
Connect the device to the PC and go to https://turtleletortue.github.io/subut-rehost/ on Google Chrome.
Click Connect.
Click "fastboot gadget" and connect.
Click Unlock.
On the device there will be a warning "Warning: Unlock device may erase user data. Press volume down button to confirm that. Press volume up button to cancel."
Press volume down.
Wait for it to complete.
Then reboot by pressing and holding PWR and Vol down.
There is a warning everytime I reboot but it goes away shortly and boots normally.
Click to expand...
Click to collapse
I have the regular RP3. Every time I try going into bootloader, it directs me straight to the RP3 boot and it stays that way till I press Boot again. Nothing happens.
A video on how to do it would be better.
If anyone knowledgeable could help me get avbtool installed properly on either Linux or Windows , it should be simple to get the keys from the vbmeta images and resign my patched boot images. I just need help with that part and I'll be rooted.
ApatheticEuphoria said:
If anyone knowledgeable could help me get avbtool installed properly on either Linux or Windows , it should be simple to get the keys from the vbmeta images and resign my patched boot images. I just need help with that part and I'll be rooted.
Click to expand...
Click to collapse
Do you think it is possible, by unlocking the boot, to install a custom firmware on the retroid pocket 3+ ? (JelOS, AmberElec, Batocera, etc.) ?
gremen said:
I have the regular RP3. Every time I try going into bootloader, it directs me straight to the RP3 boot and it stays that way till I press Boot again. Nothing happens.
A video on how to do it would be better.
Click to expand...
Click to collapse
I'm Sorry. I don't own an RP3 so the process may be different.
SoPlissken77 said:
Do you think it is possible, by unlocking the boot, to install a custom firmware on the retroid pocket 3+ ? (JelOS, AmberElec, Batocera, etc.) ?
Click to expand...
Click to collapse
Yes, Definitely.
----
Slowly trying to get avbtool working on my own. (Im honestly not very good at this stuff).
For now I'll share the code for extracting the vbmeta images:
dd if=/dev/block/mmcblk0p56 of=/sdcard/vbmeta_a.img
dd if=/dev/block/mmcblk0p57 of=/sdcard/vbmeta_b.img
Saved as getvbmeta.sh and ran from the run root script option.
(The output files will be stored in Internal Storage)
So I've been collaborating with OP on Discord and made a set of scripts to do the dirty work for me... I had to fix avbtool and make a script to extract the vbmeta keys automatically... as well as add a neat little wrapper!
They wanted me to make a full writeup but tbh I'm too lazy so I made a 1-click solution instead!... Now I'd say THIS is a worthy Valentines day gift!
GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and boot images for RP3+
A set of python scripts that will autosign modified vbmeta and boot images for RP3+ - GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and ...
github.com
ApatheticEuphoria said:
I'm Sorry. I don't own an RP3 so the process may be different.
Yes, Definitely.
----
Slowly trying to get avbtool working on my own. (Im honestly not very good at this stuff).
For now I'll share the code for extracting the vbmeta images:
dd if=/dev/block/mmcblk0p56 of=/sdcard/vbmeta_a.img
dd if=/dev/block/mmcblk0p57 of=/sdcard/vbmeta_b.img
Saved as getvbmeta.sh and ran from the run root script option.
(The output files will be stored in Internal Storage)
Click to expand...
Click to collapse
I really like the RP3+ but I find Android unsuitable for retrogaming. On the Retroid discord or the Reddit, there are many requests for a linux port or a dualboot
UPDATE: There is now a successful public root available for the RP3+
GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and boot images for RP3+
A set of python scripts that will autosign modified vbmeta and boot images for RP3+ - GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and ...
github.com
Make backups and use at your own risk.
ApatheticEuphoria said:
UPDATE: There is now a successful public root available for the RP3+
GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and boot images for RP3+
A set of python scripts that will autosign modified vbmeta and boot images for RP3+ - GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and ...
github.com
Make backups and use at your own risk.
Click to expand...
Click to collapse
Can you help me with the backups. Been trying to figure it out but having a tough time because I'm not great at linux
Irishdude5280 said:
Can you help me with the backups. Been trying to figure it out but having a tough time because I'm not great at linux
Click to expand...
Click to collapse
Try this:
[GUIDE] How to do a FULL low level backup of your Android Device
This Guide is simple and is straight the point, but is helpful and may come in handy for those who experience a hard-bricked phone or missing file in your phone like I did. Basically, nandroid is not a FULL backup, it only backs up your system...
forum.xda-developers.com
Rather than a terminal emulator you just save the command as backup.sh and run from within the handheld's run script as root setting.
ApatheticEuphoria said:
Try this:
[GUIDE] How to do a FULL low level backup of your Android Device
This Guide is simple and is straight the point, but is helpful and may come in handy for those who experience a hard-bricked phone or missing file in your phone like I did. Basically, nandroid is not a FULL backup, it only backs up your system...
forum.xda-developers.com
Rather than a terminal emulator you just save the command as backup.sh and run from within the handheld's run script as root setting.
Click to expand...
Click to collapse
I will give this a shot! Thank you I found all of the info you put here very helpful!
So I took a full system backup to my SD card using
dd if=/dev/block/mmcblk0 of=/mnt/media_rw/D873-812D/mmcblk0.img
saved as backupSD.sh
I am assuming that the mnt point "/mnt/media_rw/D873-812D/" is just for my SD but not sure on that, I found it by running OP's info.sh with the card mounted.
EDIT: thought about it and I actually might have found it by running mount command in termux. Been a long day sorry.
It made a .img of 125 GB, which seems to be a block level backup of the entire internal storage like I wanted. I extracted it with 7zip and see individual .img files for each of the partitions shown in the info.txt
Trying to extract those I get
Cannot open file as archive
Tried mounting them in WSL with
sudo mount -t drvfs V: /mnt/v To mount my windows drive where image is
sudo mount -o ro,loop /mnt/v/mmcblk0.img /mnt/android
mount: /mnt/android: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
It honestly looks like it worked perfectly im just trying to figure out forsure i have a good backup before going forward. that is why I was trying to mount it somehow.
also ran OP's commands for backing up boot a and b and vbmeta a and b
So I am ready to try and root it just want some confidence in my backups first. Any thoughts would be appreciated.
Irishdude5280 said:
So I took a full system backup to my SD card using
dd if=/dev/block/mmcblk0 of=/mnt/media_rw/D873-812D/mmcblk0.img
saved as backupSD.sh
I am assuming that the mnt point "/mnt/media_rw/D873-812D/" is just for my SD but not sure on that, I found it by running OP's info.sh with the card mounted.
EDIT: thought about it and I actually might have found it by running mount command in termux. Been a long day sorry.
It made a .img of 125 GB, which seems to be a block level backup of the entire internal storage like I wanted. I extracted it with 7zip and see individual .img files for each of the partitions shown in the info.txt
Trying to extract those I get
Cannot open file as archive
Tried mounting them in WSL with
sudo mount -t drvfs V: /mnt/v To mount my windows drive where image is
sudo mount -o ro,loop /mnt/v/mmcblk0.img /mnt/android
mount: /mnt/android: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
It honestly looks like it worked perfectly im just trying to figure out forsure i have a good backup before going forward. that is why I was trying to mount it somehow.
also ran OP's commands for backing up boot a and b and vbmeta a and b
So I am ready to try and root it just want some confidence in my backups first. Any thoughts would be appreciated.
Click to expand...
Click to collapse
Interesting. Thank you. I was wondering why it was saving files to internal storage and not the SD card. That seems to be the proper way to do it. As for why you can't extract the individual partitions, maybe it has something to do with 7zip, have you tried different software to explore the .img files? Maybe extract the main .img and then the partitions with something like Power ISO or WinRAR.
I tried your suggestion and PowerISO apparently likes adware so my AV blocked it. I threw the exe in Virus Total and it too says its full of Adware. WinRar by memory is full of adds for itself, tried it anyways with no luck.
I then found this https://www.sleuthkit.org/sleuthkit/ which is basically forensic tools for examining DD images from android devices. I was able to determine with those tools that the data is in fact there, but encrypted.
In theory a restore should still work if restored to the same device so I feel a little bit better, but still not sure i have a rock solid backup. Not even sure how I could verify at this point considering its encrypted
So did you successfully root your device? I want to try it but I am nervous without knowing if i can restore. One thing I wanted to clear up on too is with what I have read about devices with the a/b partitions, my understanding is I only need to patch 1 set of boot and vbmeta images right? Then I just flash the patched images to both the a and b partitions?
Full Root Guide for Retroid Pocket 3+
USE AT YOUR OWN RISK!!! I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE!!! ALWAYS ENSURE YOU HAVE A BACKUP!!!
-----------------
1. Doing a full partition backup to your SD Card. (You'll need 128gb or greater)
To get the path to your SD enter the following command in a text editor and save as SDNAME.sh
Code:
ls /mnt/media_rw/ > /sdcard/SDNAME.txt
To run the script, copy the .sh file to your RP3+, go to the Settings of your device, then Handheld Settings > Advanced > Run Script as Root. Navigate to the .sh file and run it.
The SDNAME.txt will be found on Internal Storage.
The output should be in this format: ####-####
Next enter the following command in a text editor and save as BACKUP.sh
Code:
dd if=/dev/block/mmcblk0 of=/mnt/media_rw/####-####/backup.img
Replace ####-#### with the result from SDNAME.txt
To run the script, copy the .sh file to your RP3+, go to the Settings of your device, then Handheld Settings > Advanced > Run Script as Root. Navigate to the .sh file and run it.
The recovery image will be saved as backup.img on your SD Card and will include ALL partitions of the RP3+.
-----------------
2. Unlocking the bootloader.
On your Windows PC go to:
https://androiddatahost.com/wp-content/uploads/SPD_Driver_R4.20.4201.zip
Download and extract the zip file and Install the driver specific to your OS.
Power off your RP3+.
Press and hold the POWER and VOLUME UP buttons until it boots to recovery mode.
Select reboot to bootloader from the recovery options.
Connect the device to the PC and go to:
Spreadtrum / Unisoc Bootloader Unlock Tool
on Google Chrome.
Click Connect.
Click "fastboot gadget" and connect.
Click Unlock.
On the device there will be a warning:
"Warning: Unlock device may erase user data. Press volume down button to confirm that. Press volume up button to cancel."
Press volume down.
Wait for it to complete. It may take awhile so be patient and do not interrupt the process*
When its complete reboot by pressing and holding POWER and VOLUME DOWN.
There is a warning everytime you reboot now but it goes away shortly and boots normally.
-----------------
3. Dumping your boot_a and vbmeta_a partitions.
Enter the following commands in a text editor and save as getbootandvbmeta.sh
Code:
dd if=/dev/block/mmcblk0p42 of=/sdcard/boot_a.img
dd if=/dev/block/mmcblk0p56 of=/sdcard/vbmeta_a.img
To run the script, copy the .sh file to your RP3+, go to the Settings of your device, then Handheld Settings > Advanced > Run Script as Root. Navigate to the .sh file and run it.
The boot_a.img and vbmeta_a.img files will be stored on Internal Storage.
-----------------
4. Patching the boot_a.img file with Magisk.
Go to:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Scroll down to Assets and download, then install the latest Magisk.apk
Open Magisk.
Tap "Install" Next to Magisk at the top.
Tap "Select and Patch a File"
Navigate to your boot_a.img file and tap it.
Tap "LET'S GO -->"
The patched boot_a.img file will have an output similar to magisk_patched-26000_Lf8IC.img and will be stored in the Download directory on Internal Storage.
-----------------
5. Resigning the keys for boot_a.img and vbmeta_a.img
Boot up a 64-bit Linux OS.
Open a terminal and enter:
Code:
git clone https://github.com/skompc/retroid-pocket-3-plus-autoroot
Navigate to the downloaded retroid-pocket-3-plus-autoroot folder.
Right click patch.sh and go to properties.
Click Permissions.
Change Access to Read & Write for all.
Tick the "Allow this file to run as a program" box
Click Close.
Open a browser and go to:
https://repo.anaconda.com/archive/Anaconda3-2023.03-Linux-x86_64.sh
To download Anaconda3.
Go to your downloads folder, Right click Anaconda3-2023.03-Linux-x86_64.sh and click properties.
Click Permissions.
Change Access to Read & Write for all.
Tick the "Allow this file to run as a program" box
Click Close.
Right click in the Download folder and Click "Open Terminal Here".
Drag Anaconda3-2023.03-Linux-x86_64.sh into the terminal and press Enter.
Press Enter to review the license agreement. Then press and hold Enter to scroll.
When you see ( END ) type yes then yes again.
Press Enter to Install Anaconda3 to your root directory.
The installer prompts you to choose whether to initialize Anaconda Distribution by running conda init. Anaconda recommends entering “yes”.
The installer finishes and displays, “Thank you for installing Anaconda3"
Connect your RP3+ to the system and copy your vbmeta_a.img and magisk_patched-26000_Lf8IC.img files to the retroid-pocket-3-plus-autoroot directory on your Linux OS.
Rename vbmeta_a.img to vbmeta.img
Rename magisk_patched-26000_Lf8IC.img to magisk.img
Right click in the retroid-pocket-3-plus-autoroot folder and Click "Open Terminal Here".
Drag patch.sh into the Terminal and press Enter.
"Extracting keys from vbmeta
Creating custom key for boot
Creating custom vbmeta and signing
Signing magisk.img
DONE!!!
Press any key to continue"
Press the Any Key.
-----------------
6. Flashing the Signed Images.
Copy the vbmeta_custom.img and magisk.img files over to your Windows OS.
Download and extract Minimal adb and fastboot:
Minimal ADB and Fastboot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Run openCMDhere.bat
Power off your RP3+.
Press and hold the POWER and VOLUME UP buttons until it boots to recovery mode.
Select reboot to fastboot/bootloader from the recovery options.
Connect the RP3+ to your PC.
On the CMD Terminal, Enter:
Code:
fastboot devices
You should see the device listed.
To flash the 4 necessary boot and vbmeta partitions enter the following commands:
Code:
fastboot flash vbmeta_a /YOUR PATH HERE/vbmeta_custom.img
Code:
fastboot flash vbmeta_b /YOUR PATH HERE/vbmeta_custom.img
Code:
fastboot flash boot_a /YOUR PATH HERE/magisk.img
Code:
fastboot flash boot_b /YOUR PATH HERE/magisk.img
Code:
fastboot reboot
-----------------
You now have Magisk ROOT!!!
!!!!WARNINGS!!!!
NEVER UPDATE MAGISK THROUGH THE APP! ALWAYS REPATCH YOUR ORIGINAL BOOT IMAGE!
IF BY ANY CHANCE YOU RECEIVE A PROMPT TO DO AN OTA UPDATE, DON'T DO IT! YOU WILL BOOTLOOP! (Go into settings and disable all automatic updates, Enable Developer options and Disable OTA updates)
MAKE SURE TO HAVE MULTIPLE BACKUPS ON HAND IN CASE OF A BRICK! WHILE SOMEONE IS MAKING AN UNBRICKING TOOL IT WILL NOT WORK WITHOUT BACKUPS!
-----------------
Credits to skompc AKA SquirrelHurtz AKA u/FoxyCatDogThing for the avb patch script.
Credits to Turtle and hartleysch for the bootloader unlock.
Credits to ApatheticEuphoria for the comprehensive guide.