Ok, so I successfully rooted my H810 G4 via LER. I was impressed with being able to dump the system.img of my phone, inject root into it, then write it back to my phone. So, I thought, why can't we just back up ALL the partitions of our phones this way and if something goes wrong, those of us who do NOT have a KDZ or TOT file to flash back to original factory can just go into download mode and dd our phones back to factory!! Now I have followed this tutorial here:
http://forum.xda-developers.com/showthread.php?t=2450045
to learn how to dump partitions. HOWEVER, what I do NOT yet understand is why he does not use any of the bs,skip,count variables in the dd command. So I need help understanding these and I am doing more reading on it here and there. What I don't know is are these variables partition specific, or are they only PHONE specific and we can just use the same variables for each partition?
I have an ATT H810 running H81010b firmware. Here is all my partition info!
Code:
C:\Users\petermg\Downloads\G4>adb shell
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 721784 zram0
179 0 30535680 mmcblk0
179 1 88064 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 1536 mmcblk0p21
179 22 16384 mmcblk0p22
179 23 32768 mmcblk0p23
179 24 1536 mmcblk0p24
179 25 1536 mmcblk0p25
179 26 1536 mmcblk0p26
179 27 512 mmcblk0p27
179 28 512 mmcblk0p28
179 29 512 mmcblk0p29
179 30 2048 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 512 mmcblk0p34
259 3 2048 mmcblk0p35
259 4 4096 mmcblk0p36
259 5 49152 mmcblk0p37
259 6 40960 mmcblk0p38
259 7 40960 mmcblk0p39
259 8 8192 mmcblk0p40
259 9 8192 mmcblk0p41
259 10 32768 mmcblk0p42
259 11 8192 mmcblk0p43
259 12 4096 mmcblk0p44
259 13 4096 mmcblk0p45
259 14 16384 mmcblk0p46
259 15 40960 mmcblk0p47
259 16 8192 mmcblk0p48
259 17 47104 mmcblk0p49
259 18 2048 mmcblk0p50
259 19 10240 mmcblk0p51
259 20 6144 mmcblk0p52
259 21 4636672 mmcblk0p53
259 22 1261568 mmcblk0p54
259 23 24100864 mmcblk0p55
259 24 12271 mmcblk0p56
179 32 4096 mmcblk0rpmb
[email protected]:/ $
ls -al /dev/block/platform/f9824900.sdhci/by-name
[email protected]:/ $ ls -al /dev/block/platform/f9824900.sdhci/by-name
ls -al /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 2015-01-01 15:37 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-01 15:37 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-01 15:37 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-01 15:37 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-01 15:37 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-01-01 15:37 cache -> /dev/block/mmcblk0p54
lrwxrwxrwx root root 2015-01-01 15:37 carrier -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-01-01 15:37 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-01 15:37 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-01 15:37 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-01-01 15:37 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-01 15:37 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-01 15:37 eri -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-01-01 15:37 factory -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-01-01 15:37 felica -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-01-01 15:37 fota -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-01-01 15:37 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-01 15:37 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-01 15:37 grow -> /dev/block/mmcblk0p56
lrwxrwxrwx root root 2015-01-01 15:37 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-01 15:37 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-01 15:37 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-01 15:37 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-01 15:37 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-01 15:37 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-01 15:37 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-01 15:37 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-01 15:37 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-01 15:37 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-01-01 15:37 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-01 15:37 operatorlogging -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2015-01-01 15:37 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-01 15:37 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-01 15:37 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-01 15:37 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-01 15:37 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-01-01 15:37 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-01-01 15:37 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-01 15:37 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-01-01 15:37 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-01 15:37 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-01 15:37 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-01 15:37 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-01 15:37 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-01 15:37 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-01 15:37 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-01 15:37 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-01-01 15:37 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-01 15:37 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-01 15:37 spare3 -> /dev/block/mmcblk0p50
lrwxrwxrwx root root 2015-01-01 15:37 spare4 -> /dev/block/mmcblk0p52
lrwxrwxrwx root root 2015-01-01 15:37 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-01 15:37 system -> /dev/block/mmcblk0p53
lrwxrwxrwx root root 2015-01-01 15:37 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-01 15:37 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-01 15:37 userdata -> /dev/block/mmcblk0p55
[email protected]:/ $
Model: MMC 032G74 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 107MB 90.2MB fat16 modem
2 117MB 118MB 524kB pmic
3 118MB 119MB 1049kB sbl1
4 119MB 120MB 1049kB tz
5 120MB 121MB 524kB sdi
6 121MB 121MB 524kB hyp
7 121MB 122MB 524kB rpm
8 122MB 124MB 2097kB aboot
9 124MB 125MB 1049kB sbl1bak
10 125MB 125MB 524kB pmicbak
11 125MB 126MB 1049kB tzbak
12 126MB 127MB 524kB hypbak
13 127MB 127MB 524kB rpmbak
14 127MB 129MB 2097kB abootbak
15 129MB 130MB 524kB sdibak
16 130MB 131MB 524kB limits
17 131MB 131MB 524kB devinfo
18 131MB 132MB 524kB apdp
19 132MB 132MB 524kB msadp
20 132MB 133MB 524kB dpo
21 133MB 134MB 1573kB spare1
22 134MB 151MB 16.8MB misc
23 151MB 185MB 33.6MB ext4 persist
24 185MB 186MB 1573kB modemst1
25 186MB 188MB 1573kB modemst2
26 188MB 189MB 1573kB fsg
27 189MB 190MB 524kB fsc
28 190MB 190MB 524kB ssd
29 190MB 191MB 524kB keystore
30 191MB 193MB 2097kB DDR
31 193MB 193MB 524kB sec
32 193MB 194MB 524kB encrypt
33 194MB 195MB 524kB eksst
34 195MB 195MB 524kB rct
35 195MB 197MB 2097kB persistent
36 197MB 201MB 4194kB spare2
37 201MB 252MB 50.3MB laf
38 252MB 294MB 41.9MB boot
39 294MB 336MB 41.9MB recovery
40 336MB 344MB 8389kB ext4 drm
41 344MB 352MB 8389kB ext4 sns
42 352MB 386MB 33.6MB ext4 mpt
43 386MB 394MB 8389kB eri
44 394MB 398MB 4194kB raw_resources
45 398MB 403MB 4194kB raw_resourcesbak
46 403MB 419MB 16.8MB operatorlogging
47 419MB 461MB 41.9MB carrier
48 461MB 470MB 8389kB felica
49 470MB 518MB 48.2MB factory
50 518MB 520MB 2097kB spare3
51 520MB 531MB 10.5MB fota
52 531MB 537MB 6291kB spare4
53 537MB 5285MB 4748MB ext4 system
54 5285MB 6577MB 1292MB ext4 cache
55 6577MB 31.3GB 24.7GB ext4 userdata
56 31.3GB 31.3GB 12.6MB grow
(parted)
So if you guys can chime in and help get this figured out, also I will post updates for what I learn about it. Hopefully we can get this so that we can do backups this way until we get a custom recovery for the most of us with locked bootloaders!:good:
I too have been very interested in this... I made a backup of both the recovery and boot sectors on the phone. The ONLY problem I have is... HOW do I use a similar CWM or TWRP recovery, open those files, insert the required files into the STOCK recovery and dd it back to the recovery partition, so that I can flash my phone with custom Roms? There aren't too many Custom Roms for the LG G4 H810 (AT&T version) so, this isn't the most pressing thing... There might be more if I succeed at this. I am being very cautious as well too. I bricked one LG G4, and got the store to replace it. So now backing up everything is my #1 concern.
Peter, you sound quite knowledgeable about this... if you could point me in the right direction for HOW TO CREATE custom recovery images... I'd appreciate it. Not finding too much myself.
I am a linux admin for a big company. I am not happy that I don't have full Root on my phone. (Full root means SuperSU working and recovery image replaced with a custom image)
bigjohnman said:
I too have been very interested in this... I made a backup of both the recovery and boot sectors on the phone. The ONLY problem I have is... HOW do I use a similar CWM or TWRP recovery, open those files, insert the required files into the STOCK recovery and dd it back to the recovery partition, so that I can flash my phone with custom Roms? There aren't too many Custom Roms for the LG G4 H810 (AT&T version) so, this isn't the most pressing thing... There might be more if I succeed at this. I am being very cautious as well too. I bricked one LG G4, and got the store to replace it. So now backing up everything is my #1 concern.
Peter, you sound quite knowledgeable about this... if you could point me in the right direction for HOW TO CREATE custom recovery images... I'd appreciate it. Not finding too much myself.
I am a linux admin for a big company. I am not happy that I don't have full Root on my phone. (Full root means SuperSU working and recovery image replaced with a custom image)
Click to expand...
Click to collapse
I think we need unlocked bootloaders to use a custom recovery.
Great... Some more info would be nice... Is the boot loader found in the Boot.img section?
I haven't found too many HOW TO create an unlocked boot loader sites, I am just finding ones where they have the final product (Here flash this).
Have you seen any Warri?
bigjohnman said:
I too have been very interested in this... I made a backup of both the recovery and boot sectors on the phone. The ONLY problem I have is... HOW do I use a similar CWM or TWRP recovery, open those files, insert the required files into the STOCK recovery and dd it back to the recovery partition, so that I can flash my phone with custom Roms? There aren't too many Custom Roms for the LG G4 H810 (AT&T version) so, this isn't the most pressing thing... There might be more if I succeed at this. I am being very cautious as well too. I bricked one LG G4, and got the store to replace it. So now backing up everything is my #1 concern.
Peter, you sound quite knowledgeable about this... if you could point me in the right direction for HOW TO CREATE custom recovery images... I'd appreciate it. Not finding too much myself.
I am a linux admin for a big company. I am not happy that I don't have full Root on my phone. (Full root means SuperSU working and recovery image replaced with a custom image)
Click to expand...
Click to collapse
You know, I didn't even think about injecting files into the original boot.img. Wonder if that would work?
How did you back up your recovery and boot sectors? Was it with FlashFire? I've made a backup of my system partition from download mode using this command:
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
from THIS THREAD
http://forum.xda-developers.com/showpost.php?p=62028523&postcount=2
I have ALSO made a backup of my system partition by using this command:
Code:
dd if=/dev/block/mmcblk0p53 of=/sdcard/system.img
following the instructions on THIS THREAD
http://forum.xda-developers.com/showthread.php?t=2450045
HOWEVER.. they are ALMOST identital in file size, but not quite. So I don't know if I would brick my H810 G4 by trying to restore my system partition using the file created via the second method...?
What I've also not tried yet is making a backup of any partitions using FlashFire.
What I'm trying to figure out is what are the exact commands to backup each partition in a way that we can RESTORE them if something goes wrong. And in this case I'm thinking restore them from DOWNLOAD MODE via the dd command. I need to learn more about why the first method of backing up the image contains variables that the second method does not, for example, the first method from download mode uses the command dd with the variables "bs=8192 skip=65536 count=579584", whereas the second method does not use these variables. I'm no dev, but if I can get enough free time away from the kids and madness :silly: I'm hoping to research enough to understand not only why these variables are used, but if they need to be adjusted for each partition backup and to which parameters. Since we're on the AT&T version, we don't have a TOT file, so if we screw something up we can't go back to stock. Now some guys have HARD BRICKED their devices and can NOT get into download mode, in which case not even a TOT/KDZ file will be able to be applied. But I think that if we can learn how to dd backup all the partitions from download mode correctly, then we should be able to dd restore those partitions if we mess up our phones and need to go back to stock!!! :laugh::good: This is my goal for now!!! But I like your idea of injecting things into the stock recovery!!!!!!!!!!!!!! That's a great idea!!! Need to learn more about those variables and how to apply them to each partitions. IN THE MEANTIME, what I'm going to try to do is back up partitions one by one using the second method and MOUNT THEM in Linux/Ubuntu via this command
Code:
su -
mkdir -p /mnt/disk
mount -o loop yourImage.img /mnt/disk
cd /mnt/disk
ls -l
as shown in the thread here
http://forum.xda-developers.com/showthread.php?t=2450045
If I find anything interesting... I'll post my results.
bigjohnman said:
Great... Some more info would be nice... Is the boot loader found in the Boot.img section?
I haven't found too many HOW TO create an unlocked boot loader sites, I am just finding ones where they have the final product (Here flash this).
Have you seen any Warri?
Click to expand...
Click to collapse
Creating a bootloader it's something that is actually quite difficult to do typically you need the source code for every chip and I/O od peripheral on the on the board think of Arduino open sourcing everything in building your own board. LG probably won't release this since it would give away you know trade secrets. typically what we've seen in the past is that OEMs will provide unlock bootloader which allow people to custom flash open recoveries which allow writing to boot images and things along those lines however due to AT&T and Verizon restrictions we probably won't see an open bootloader released officially
warri said:
however due to AT&T and Verizon restrictions we probably won't see an open bootloader released officially
Click to expand...
Click to collapse
+1 THIS!! That's why I am hoping to figure out how to "backup" and "restore" our partitions via dd at this point for no other reason than to "return to stock". One thing I have found is that when I have root I start messing around and when I start messing around sometimes I break something With a custom recovery I don't worry about it because I can just restore a backup, however since we don't have a custom recovery I am trying to learn how to backup and restore the partitions via dd in download mode.
So according to this article: http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/ wiping the data partition is like doing a factory reset. I wanted to know if this was true or not so I went to my G3, backed up the data partition, then wiped it and rebooted and yes, it was just like I had done a factory reset on it. It worked fine. So... I guess for those of us who have made a backup of our system partition via the dd command in download mode, I guess we have all we need to go back to stock. This is so long as we don't flash the wrong KDZ/TOT file. I am not sure yet but I think the people who flash the wrong system.img file, like wrong firmware version, that end up getting the security error on boot up, I think all they need to do is just reflash the correct firmware system.img file and that takes care of it.. I'll have to double check the posts on that. So I guess just reflashing your original backed up system.img file then doing a factory reset will take the phone totally back to stock. It's sure looking this way as of right now. I am still reading up on partitions, etc..
I believe this to be true...EXCEPT the /persist partition where RCTD is found. Which seems to be preventing us from ugrading.
petermg said:
So according to this article: http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/ wiping the data partition is like doing a factory reset. I wanted to know if this was true or not so I went to my G3, backed up the data partition, then wiped it and rebooted and yes, it was just like I had done a factory reset on it. It worked fine. So... I guess for those of us who have made a backup of our system partition via the dd command in download mode, I guess we have all we need to go back to stock. This is so long as we don't flash the wrong KDZ/TOT file. I am not sure yet but I think the people who flash the wrong system.img file, like wrong firmware version, that end up getting the security error on boot up, I think all they need to do is just reflash the correct firmware system.img file and that takes care of it.. I'll have to double check the posts on that. So I guess just reflashing your original backed up system.img file then doing a factory reset will take the phone totally back to stock. It's sure looking this way as of right now. I am still reading up on partitions, etc..
Click to expand...
Click to collapse
So how far did you get on this? My G4 developed the boot loop issue and will need to be sent away to be repair/replaced. Luckily I was able to flash the disable BIG cores fix to get it stable enough that I should be able to back it up. Just wondering now as I have a locked boot loader what the best way to do this is.
Do I use
Code:
dd if=/dev/block/mmcblk0p53 of=/sdcard/system.img
and if so, on which partitions? I'd like to be able to just flash all the images back onto the phone when it's back from repair and have it be like it was before I factory reset it and give it to the courier.
Lg g4 h810
Hey guys! I have g4 h810 brick, Qualcomm HS-USB QDLoader 9008,
not included, help me please i need dump for h810, sorry my english, i maker :crying:
---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------
Hello , here you can share these files with all , I would be very grateful
Number Start End Size File system Name Flags
1 16.8MB 107MB 90.2MB fat16 modem
2 117MB 118MB 524kB pmic
3 118MB 119MB 1049kB sbl1
4 119MB 120MB 1049kB tz
5 120MB 121MB 524kB sdi
6 121MB 121MB 524kB hyp
7 121MB 122MB 524kB rpm
8 122MB 124MB 2097kB aboot
9 124MB 125MB 1049kB sbl1bak
10 125MB 125MB 524kB pmicbak
11 125MB 126MB 1049kB tzbak
12 126MB 127MB 524kB hypbak
13 127MB 127MB 524kB rpmbak
14 127MB 129MB 2097kB abootbak
15 129MB 130MB 524kB sdibak
16 130MB 131MB 524kB limits
17 131MB 131MB 524kB devinfo
18 131MB 132MB 524kB apdp
19 132MB 132MB 524kB msadp
20 132MB 133MB 524kB dpo
21 133MB 134MB 1573kB spare1
22 134MB 151MB 16.8MB misc
23 151MB 185MB 33.6MB ext4 persist
24 185MB 186MB 1573kB modemst1
25 186MB 188MB 1573kB modemst2
26 188MB 189MB 1573kB fsg
27 189MB 190MB 524kB fsc
28 190MB 190MB 524kB ssd
29 190MB 191MB 524kB keystore
30 191MB 193MB 2097kB DDR
31 193MB 193MB 524kB sec
32 193MB 194MB 524kB encrypt
33 194MB 195MB 524kB eksst
34 195MB 195MB 524kB rct
35 195MB 197MB 2097kB persistent
36 197MB 201MB 4194kB spare2
37 201MB 252MB 50.3MB laf
38 252MB 294MB 41.9MB boot
39 294MB 336MB 41.9MB recovery
40 336MB 344MB 8389kB ext4 drm
41 344MB 352MB 8389kB ext4 sns
42 352MB 386MB 33.6MB ext4 mpt
43 386MB 394MB 8389kB eri
44 394MB 398MB 4194kB raw_resources
45 398MB 403MB 4194kB raw_resourcesbak
46 403MB 419MB 16.8MB operatorlogging
47 419MB 461MB 41.9MB carrier
48 461MB 470MB 8389kB felica
49 470MB 518MB 48.2MB factory
50 518MB 520MB 2097kB spare3
51 520MB 531MB 10.5MB fota
52 531MB 537MB 6291kB spare4
53 537MB 5285MB 4748MB ext4 system
54 5285MB 6577MB 1292MB ext4 cache
55 6577MB 31.3GB 24.7GB ext4 userdata
56 31.3GB 31.3GB 12.6MB grow
Related
Hello everyone;
In recent days I have been following very closely the development that has been taking place on the root procedure for LG G4 and as they say that very probably transferable to the G Flex 2, I have started to work and apparently have found codes (see attachment) to dump and later flash our phone with a prerooted system image, this, having it on android 5.1.1.
i tested the spreadsheet on my 5.0.1 Ls996 (sprint) dev blocks, we need to test it on 5.1.1 and see what happens, for that reason anyone who have the phone on 5.1.1 can run the following commands on adb and post on here, it will help to development of our root:
Code:
cat /proc/partitions
Code:
ls -l /dev/block/platform/f9824900.sdhci/by-name
output
randrew87 said:
Hello everyone;
In recent days I have been following very closely the development that has been taking place on the root procedure for LG G4 and as they say that very probably transferable to the G Flex 2, I have started to work and apparently have found codes (see attachment) to dump and later flash our phone with a prerooted system image, this, having it on android 5.1.1.
i tested the spreadsheet on my 5.0.1 Ls996 (sprint) dev blocks, we need to test it on 5.1.1 and see what happens, for that reason anyone who have the phone on 5.1.1 can run the following commands on adb and post on here, it will help to development of our root:
Code:
cat /proc/partitions
Code:
ls -l /dev/block/platform/f9824900.sdhci/by-name
Click to expand...
Click to collapse
LG-H955
V15a-eur-XX
like this?
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
bobucom said:
LG-H955
V15a-eur-XX
like this?48
Click to expand...
Click to collapse
Yup... Thats what it shud read.. Is that on 5.1.1?? @randrew87 the next issue is how to find the commands like ( seek, bs, skip) .... I cudnt figure it out.. I gave up
Google~Android said:
Yup... Thats what it shud read.. Is that on 5.1.1?? @randrew87 the next issue is how to find the commands like ( seek, bs, skip) .... I cudnt figure it out.. I gave up
Click to expand...
Click to collapse
yes this is on 5.1.1
Google~Android said:
Yup... Thats what it shud read.. Is that on 5.1.1?? @randrew87 the next issue is how to find the commands like ( seek, bs, skip) .... I cudnt figure it out.. I gave up
Click to expand...
Click to collapse
i think i figured out look at the xlsx attach i find the 3 values please look at detail on the spreadsheet!
for example for my 5.0.1 should be:
dump --> dd if=/dev/block/mmcblk0 bs=8192 skip=58368 count=522240 of=/data/media/0/system.img
flash --> dd if=/data/media/0/rootedsystem.img bs=8192 seek=58368 count=522240 of=/dev/block/mmcblk0
the other thing is inject root on dump, i have a virtual machine with ubuntu running waiting for that, you can see the related steps on here:
http://forum.xda-developers.com/showpost.php?p=62097182&postcount=446
bobucom said:
LG-H955
V15a-eur-XX
like this?
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
Click to expand...
Click to collapse
yes just like that, many thanks, now the more models we have the more fast we can get root working!!
edit: the commands for this should be:
dump --> dd if=/dev/block/mmcblk0 bs=8192 skip=54272 count=458752 of=/data/media/0/system.img
flash --> dd if=/data/media/0/rootedsystem.img bs=8192 seek=54272 count=458752 of=/dev/block/mmcblk0
randrew87 said:
i think i figured out look at the xlsx attach i find the 3 values please look at detail on the spreadsheet!
for example for my 5.0.1 should be:
dump --> dd if=/dev/block/mmcblk0 bs=8192 skip=58368 count=522240 of=/data/media/0/system.img
flash --> dd if=/data/media/0/rootedsystem.img bs=8192 seek=58368 count=522240 of=/dev/block/mmcblk0
the other thing is inject root on dump, i have a virtual machine with ubuntu running waiting for that, you can see the related steps on here:
http://forum.xda-developers.com/showpost.php?p=62097182&postcount=446
Click to expand...
Click to collapse
Damn ur smart....so can i upgrade mine to 5.1.1 and upload my system img
Google~Android said:
Damn ur smart....so can i upgrade mine to 5.1.1 and upload my system img
Click to expand...
Click to collapse
if you are willing to work together to find our root, the answer is yes .
you are on sprint network ? or using GSM?, my problem is that, using the phone on int GSM, so I can not take the risk to run out of phone, until downgrade will brick my device.
randrew87 said:
if you are willing to work together to find our root, the answer is yes .
you are on sprint network ? or using GSM?, my problem is that, using the phone on int GSM, so I can not take the risk to run out of phone, until downgrade will brick my device.
Click to expand...
Click to collapse
its a sprint but i dont have it hooked up yet..cant get it to work a att...so im upgrading now....root or no root...ill get back to u with the cmd readout...give me an hour or so
edit....im out of "thanks" so ill catch up tomorrow
Google~Android said:
its a sprint but i dont have it hooked up yet..cant get it to work a att...so im upgrading now....root or no root...ill get back to u with the cmd readout...give me an hour or so
edit....im out of "thanks" so ill catch up tomorrow
Click to expand...
Click to collapse
ok, dont worry for "thanks", waiting for your commands ouputs. something bigger comes!!!
randrew87 said:
ok, dont worry for "thanks", waiting for your commands ouputs. something bigger comes!!!
Click to expand...
Click to collapse
C:\WINDOWS\system32>adb shell
[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 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
[email protected]:/ $ ls -l /dev/block/platform/f9824900.sdhci/by-name
ls -l /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-01-08 11:18 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-08 11:18 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-08 11:18 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-08 11:18 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-08 11:18 boot -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-08 11:18 cache -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 1970-01-08 11:18 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-08 11:18 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-08 11:18 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-08 11:18 drm -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-08 11:18 eksst -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-08 11:18 encrypt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-08 11:18 factory -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-08 11:18 fota -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-08 11:18 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-08 11:18 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-08 11:18 grow -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 1970-01-08 11:18 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-08 11:18 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-08 11:18 keystore -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-08 11:18 laf -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-08 11:18 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-08 11:18 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-08 11:18 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-08 11:18 modemst1 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-08 11:18 modemst2 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-08 11:18 mpt -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-08 11:18 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-08 11:18 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-08 11:18 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-08 11:18 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-08 11:18 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-08 11:18 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-08 11:18 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-01-08 11:18 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-08 11:18 recovery -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-08 11:18 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-08 11:18 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-08 11:18 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-08 11:18 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-08 11:18 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-08 11:18 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-08 11:18 sec -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-08 11:18 sns -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-08 11:18 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-08 11:18 system -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 1970-01-08 11:18 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-08 11:18 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-08 11:18 userdata -> /dev/block/mmcblk0p48
form LS996ZV6...get back with the proper commands so i can pull system...) im exciteded!!!!
Google~Android said:
C:\WINDOWS\system32>adb shell
[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 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
[email protected]:/ $ ls -l /dev/block/platform/f9824900.sdhci/by-name
ls -l /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-01-08 11:18 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-08 11:18 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-08 11:18 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-08 11:18 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-08 11:18 boot -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-08 11:18 cache -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 1970-01-08 11:18 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-08 11:18 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-08 11:18 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-08 11:18 drm -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-08 11:18 eksst -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-08 11:18 encrypt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-08 11:18 factory -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-08 11:18 fota -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-08 11:18 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-08 11:18 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-08 11:18 grow -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 1970-01-08 11:18 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-08 11:18 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-08 11:18 keystore -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-08 11:18 laf -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-08 11:18 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-08 11:18 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-08 11:18 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-08 11:18 modemst1 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-08 11:18 modemst2 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-08 11:18 mpt -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-08 11:18 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-08 11:18 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-08 11:18 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-08 11:18 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-08 11:18 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-08 11:18 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-08 11:18 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-01-08 11:18 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-08 11:18 recovery -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-08 11:18 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-08 11:18 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-08 11:18 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-08 11:18 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-08 11:18 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-08 11:18 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-08 11:18 sec -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-08 11:18 sns -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-08 11:18 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-08 11:18 system -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 1970-01-08 11:18 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-08 11:18 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-08 11:18 userdata -> /dev/block/mmcblk0p48
form LS996ZV6...get back with the proper commands so i can pull system...) im exciteded!!!!
Click to expand...
Click to collapse
ok seem not to be version dependant (ZV5, ZV6, etc) the number are the same for ZV5 and ZV6 so
dump --> dd if=/dev/block/mmcblk0 bs=8192 skip=58368 count=522240 of=/data/media/0/system.img
i updated the dev blocks archive on the OP with the last info obtained. waiting for your answer! superexcited too!
randrew87 said:
ok seem not to be version dependant (ZV5, ZV6, etc) the number are the same for ZV5 and ZV6 so
dump --> dd if=/dev/block/mmcblk0 bs=8192 skip=58368 count=522240 of=/data/media/0/system.img
i updated the dev blocks archive on the OP with the last info obtained. waiting for your answer! superexcited too!
Click to expand...
Click to collapse
dumping as we speak...i only have google drive...shud i zip the img and then upload or just upload the img??
Google~Android said:
dumping as we speak...i only have google drive...shud i zip the img and then upload or just upload the img??
Click to expand...
Click to collapse
you can zip it or rar it or 7zip it, no problem
randrew87 said:
you can zip it or rar it or 7zip it, no problem
Click to expand...
Click to collapse
its done dumping does 3.96 gb sound right??
Google~Android said:
its done dumping does 3.96 gb sound right??
Click to expand...
Click to collapse
its approximately the same size of G4 images after uncompress, so yes.
i have a sprint flex 2 on the latest ZV7 update, here is the data from running the 2 commands in the first post.
first command
Code:
7 0 142052 loop0
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 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
179 64 62513152 mmcblk1
179 65 62496768 mmcblk1p1
253 0 142052 dm-0
2nd command
Code:
lrwxrwxrwx root root 1970-05-18 18:25 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-05-18 18:25 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-05-18 18:25 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-05-18 18:25 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-05-18 18:25 boot -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-05-18 18:25 cache -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 1970-05-18 18:25 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-05-18 18:25 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-05-18 18:25 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-05-18 18:25 drm -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-05-18 18:25 eksst -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-05-18 18:25 encrypt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-05-18 18:25 factory -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-05-18 18:25 fota -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-05-18 18:25 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-05-18 18:25 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-05-18 18:25 grow -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 1970-05-18 18:25 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-05-18 18:25 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-05-18 18:25 keystore -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-05-18 18:25 laf -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-05-18 18:25 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-05-18 18:25 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-05-18 18:25 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-05-18 18:25 modemst1 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-05-18 18:25 modemst2 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-05-18 18:25 mpt -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-05-18 18:25 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-05-18 18:25 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-05-18 18:25 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-05-18 18:25 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-05-18 18:25 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-05-18 18:25 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-05-18 18:25 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-05-18 18:25 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-05-18 18:25 recovery -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-05-18 18:25 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-05-18 18:25 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-05-18 18:25 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-05-18 18:25 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-05-18 18:25 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-05-18 18:25 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-05-18 18:25 sec -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-05-18 18:25 sns -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-05-18 18:25 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-05-18 18:25 system -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 1970-05-18 18:25 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-05-18 18:25 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-05-18 18:25 userdata -> /dev/block/mmcblk0p48
i'm new to this stuff but am good at following directions. so if there is anything else you need me to do let me know (as long as it won't brick my phone, can't be without it! )
This is just what we needed, someone make a breakthru, somebody who can and have skills to do it thank you, wish you luck
dadaa1 said:
This is just what we needed, someone make a breakthru, somebody who can and have skills to do it thank you, wish you luck
Click to expand...
Click to collapse
with the help of all here we can do greater things, this is i believe!
Some more Info on LG-H955 - 5.1.1 - V15a-eur-XX
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
I'm creating this thread to regroup all that I know about the LG G Stylo H636, Fido carrier. I'm doing this because I could not achieve root on this device.
I have been able to get into download mode, using the Send_Command.exe file. I was able to dump the system and recovery partitions (5.0.2). Both are available here: https://mega.nz/#F!HFgTQSzI!NHBjp2bpqVL6T9fByMJQ0g
Here are the mounts:
Code:
#cat proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,resuid=1000,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/mmcblk1p1 /storage/external_SD vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
#
Here are the partitions:
Code:
#cat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 1536 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 512 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 24576 mmcblk0p17
179 18 24576 mmcblk0p18
179 19 24576 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 512 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 512 mmcblk0p25
179 26 512 mmcblk0p26
179 27 512 mmcblk0p27
179 28 8192 mmcblk0p28
179 29 32768 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 8192 mmcblk0p31
259 0 24576 mmcblk0p32
259 1 65536 mmcblk0p33
259 2 2048 mmcblk0p34
259 3 2048 mmcblk0p35
259 4 2621440 mmcblk0p36
259 5 921600 mmcblk0p37
259 6 11403264 mmcblk0p38
259 7 19951 mmcblk0p39
179 32 4096 mmcblk0rpmb
179 64 31267840 mmcblk1
179 65 31263744 mmcblk1p1
And here are the named partitions:
Code:
#ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-03 05:39 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-03 05:39 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-03 05:39 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-03 05:39 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-03 05:39 cache -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-03 05:39 drm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-03 05:39 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-03 05:39 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-03 05:39 factory -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-03 05:39 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-03 05:39 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-03 05:39 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-03 05:39 grow -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-03 05:39 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-03 05:39 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-03 05:39 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-03 05:39 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-03 05:39 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-03 05:39 modem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-03 05:39 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-03 05:39 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-03 05:39 mpt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-03 05:39 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-03 05:39 pad2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-03 05:39 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-03 05:39 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-03 05:39 rct -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-03 05:39 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-03 05:39 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-03 05:39 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-03 05:39 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-03 05:39 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-03 05:39 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-03 05:39 sns -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-03 05:39 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-03 05:39 system -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-03 05:39 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-03 05:39 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-03 05:39 userdata -> /dev/block/mmcblk0p38
#
Here is detailed gpt information
Code:
Disk gpt.img: 1953 sectors, 976.5 KiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 40 entries
First usable sector is 34, last usable sector is 30535646
Partitions will be aligned on 1024-sector boundaries
Total free space is 990 sectors (495.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 512.0 KiB FFFF sbl1
2 2048 3071 512.0 KiB FFFF tz
3 3072 4095 512.0 KiB FFFF hyp
4 4096 5119 512.0 KiB FFFF rpm
5 5120 9215 2.0 MiB FFFF aboot
6 9216 12287 1.5 MiB 0700 pad
7 12288 13311 512.0 KiB FFFF sbl1bak
8 13312 14335 512.0 KiB FFFF tzbak
9 14336 15359 512.0 KiB FFFF hypbak
10 15360 16383 512.0 KiB FFFF rpmbak
11 16384 20479 2.0 MiB FFFF abootbak
12 20480 53247 16.0 MiB FFFF misc
13 53248 86015 16.0 MiB 0700 persist
14 86016 87039 512.0 KiB 8301 metadata
15 87040 90111 1.5 MiB FFFF modemst1
16 90112 93183 1.5 MiB FFFF modemst2
17 93184 142335 24.0 MiB FFFF laf
18 142336 191487 24.0 MiB FFFF boot
19 191488 240639 24.0 MiB FFFF recovery
20 240640 243711 1.5 MiB FFFF fsg
21 243712 244735 512.0 KiB FFFF fsc
22 244736 245759 512.0 KiB FFFF ssd
23 245760 246783 512.0 KiB FFFF DDR
24 246784 247807 512.0 KiB FFFF sec
25 247808 248831 512.0 KiB FFFF encrypt
26 248832 249855 512.0 KiB FFFF eksst
27 249856 250879 512.0 KiB FFFF rct
28 250880 267263 8.0 MiB 0700 sns
29 267264 332799 32.0 MiB FFFF factory
30 332800 398335 32.0 MiB FFFF fota
31 398336 414719 8.0 MiB 0700 drm
32 414720 463871 24.0 MiB 0700 mpt
33 463872 594943 64.0 MiB 0700 modem
34 594944 599039 2.0 MiB 0700 persistent
35 599040 603135 2.0 MiB FFFF pad2
36 603136 5846015 2.5 GiB 0700 system
37 5846016 7689215 900.0 MiB 0700 cache
38 7689216 30495743 10.9 GiB 0700 userdata
39 30495744 30535646 19.5 MiB 0700 grow
I now have as a project to get TWRP working
It seems like flashing anything to the recovery partition caused the device to reject it. In the process of attempting to get xposed working, I bricked the device. I had shell access, but could not get root, as kingroot kept awaiting for a UI confirmation, but the UI was dead :/ I restored using http://pkg03.lime.gdms.lge.com/dn/downloader.dev?fileKey=FW76ZGG232C6AY1303926B9/H63610k_00.kdz and am no longer able to gain access using kingroot. This was a 5.0.2 rom. I will attempt to downgrade to http://pkg02.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=FW061AC1322UAS9A166DFZZ/H63610i_00.kdz and see if I have better luck
I used kingroot and got root. I had to reset the phone by doing a factory reset because i had apps to SD app and it made an error come up with the UIR. The kingroot method works but seems to be temporary because if you uninstall KR you will lose root. The main reasion for me to root was apps to sd and it seemed that it did not work on the fido model and it pretty much deleted the apps and i used LG bridge to do a restore. Best method would to restore it with that or flash the KDZ rom posted in the other thread but you will get back to stock rom with a locked boot loader.
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?
Hi, I had a working rooted ZTE Nubia Z5 NX501 with TWRP.
The userdata space is 2860MB while sdcard space is 25.4GB so i deciced to merge them using some adb commands in Windows
The memory details are as follow
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.2 GB, 31268536320 bytes
256 heads, 63 sectors/track, 3786 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 266306 2147483647+ ee EFI GPT
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 87536 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 15360 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 15360 mmcblk0p14
179 15 2097152 mmcblk0p15
179 16 2792912 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 122880 mmcblk0p18
179 19 153600 mmcblk0p19
179 20 780 mmcblk0p20
179 21 780 mmcblk0p21
179 22 780 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1 mmcblk0p24
179 25 24768494 mmcblk0p25
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-02-03 18:28 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-02-03 18:28 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-02-03 18:28 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-02-03 18:28 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-02-03 18:28 customfs -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-02-03 18:28 grow -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-02-03 18:28 m9kefs1 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-02-03 18:28 m9kefs2 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-02-03 18:28 m9kefs3 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-02-03 18:28 m9kefsc -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-02-03 18:28 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-02-03 18:28 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-02-03 18:28 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-02-03 18:28 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-02-03 18:28 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-02-03 18:28 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-02-03 18:28 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-02-03 18:28 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-02-03 18:28 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-02-03 18:28 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-02-03 18:28 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-02-03 18:28 splash -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-02-03 18:28 system -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-02-03 18:28 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-02-03 18:28 userdata -> /dev/block/mmcblk0p16
parted /dev/block/mmcblk0 print
Model: MMC MBG8FB (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 157MB 89.6MB fat16 modem
2 201MB 201MB 131kB sbl1
3 201MB 202MB 262kB sbl2
4 202MB 202MB 524kB sbl3
5 202MB 204MB 2097kB aboot
6 204MB 205MB 524kB rpm
7 268MB 284MB 15.7MB boot
8 336MB 336MB 524kB tz
9 336MB 336MB 1024B pad
10 336MB 339MB 3146kB modemst1
11 339MB 342MB 3146kB modemst2
12 342MB 343MB 1049kB misc
13 343MB 354MB 10.5MB splash
14 403MB 418MB 15.7MB recovery
15 418MB 2566MB 2147MB ext4 system
16 2566MB 5426MB 2860MB ext4 userdata
17 5426MB 5434MB 8389kB ext4 persist
18 5434MB 5560MB 126MB ext4 cache
19 5560MB 5717MB 157MB ext4 customfs
20 5771MB 5772MB 799kB m9kefs1
21 5772MB 5773MB 799kB m9kefs2
22 5838MB 5839MB 799kB m9kefs3
23 5839MB 5839MB 8192B DDR
24 5906MB 5906MB 1024B m9kefsc
25 5906MB 31.3GB 25.4GB fat32 grow
As you can see in order to all the space in the "grow" partition for the "userdata" partition i figured i had to delete partitions 16-25 and create them again with different calculations in size, so before i did that i dump images for all the partitions to be deleted (I did not backup the other partitions, maybe i was lazy).
I don't know how i messed up so now all i have is a QHSUSB_DLOAD device that i'm not able to get the drivers for.
The hardware id is USB\VID_19D2&PID_FFAE&REV_0000&MI_00 but i cannot find it, nor do i know what other driver i can use to put that string inside and get it to work and maybe try to unbrick my device. But on the other side i have a QHSUSB_DLOAD usb device with 5 units from F to J and the Disk Management shows a 30GB disk with around 15 partitions.
My device comes with Snapdragon 600 quad-core a 1.5GHz processor, 2GB of RAM y 32GB of internal storage.
Can anyone help me?
Hi,
My phone is stuck at boot stage where the rom logo animation (CrDroid rom) is animating, so no freeze. The phone never goes further than that.
I can boot into either bootloader, Fastboot (Secure boot: enabled, Lock State: unlocked) and recovery. I also have access to ADB/Fastboot from PC. I've managed to init a shell but /sdcard is empty
When I enter recovery (TWRP 3.3.1-hh), this is the content of recovery log/terminal:
Code:
[COLOR="Red"]Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Failed to mount '/cache' (Invalid argument)[/COLOR]
Updating partition details...
[COLOR="Red"]Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)[/COLOR]
...done
[COLOR="red"]Unable to mount storage
Failed to mount '/data' (Invalid argument)[/COLOR]
Full SELinux support is present.
[COLOR="red"]Unable to mount /data/media/TRWP/.twrps[/COLOR]
MTP Enabled
What solution do I have in order to retrieve my data? I think I encrypted the phone with a SIM PIN code, but I'm not sure because I do it sometimes when I flash a ROM, but this time I may have decided not to do it. I can't remember for sure. The other reason for my doubt is if I understand correctly, some recent versions of Android are forced encrypted, though I thought that was only valid for stock ROM which is not my case.
I found this topic (https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643) that seems to describe a process in order to get encrypted files back by flashing a ROM, but it's for OnePlus6. Do you guys think this can work for me?
Help would be much appreciated.
Best regards,
Specs: Nexus 5 (LG-D821), TWRP 3.3.1-HH, crDroidAndroid-9.0-20191014-hammerhead-v5.8 (https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v5-4-t3931587)
EDIT: I gave it up in the end
Bump,
Anyone that can help?
danoussh said:
Hi,
My phone is stuck at boot stage where the rom logo animation (CrDroid rom) is animating, so no freeze. The phone never goes further than that.
I can boot into either bootloader, Fastboot (Secure boot: enabled, Lock State: unlocked) and recovery. I also have access to ADB/Fastboot from PC. I've managed to init a shell but /sdcard is empty
When I enter recovery (TWRP 3.3.1-hh), this is the content of recovery log/terminal:
What solution do I have in order to retrieve my data? I think I encrypted the phone with a SIM PIN code, but I'm not sure because I do it sometimes when I flash a ROM, but this time I may have decided not to do it. I can't remember for sure. The other reason for my doubt is if I understand correctly, some recent versions of Android are forced encrypted, though I thought that was only valid for stock ROM which is not my case.
I found this topic (https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643) that seems to describe a process in order to get encrypted files back by flashing a ROM, but it's for OnePlus6. Do you guys think this can work for me?
Help would be much appreciated.
Best regards,
Specs: Nexus 5 (LG-D821), TWRP 3.3.1-HH, crDroidAndroid-9.0-20191014-hammerhead-v5.8 (https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v5-4-t3931587)
Click to expand...
Click to collapse
You can't decrypt files on n5.
There are 2 types of encryption:
FBE - File Based Encryption
FDE - Full Disk Encryption
We don't have fbe. When you press the encrypt button in Rom settings. You will get fde. I don't know crdroid but if you encrypted your disk, than sorry afaik no chance to rescue your files here. Go and start with formatting data partition or flash stock 6.0.1 and flash another rom again.
lulli1 said:
You can't decrypt files on n5.
There are 2 types of encryption:
FBE - File Based Encryption
FDE - Full Disk Encryption
We don't have fbe. When you press the encrypt button in Rom settings. You will get fde. I don't know crdroid but if you encrypted your disk, than sorry afaik no chance to rescue your files here. Go and start with formatting data partition or flash stock 6.0.1 and flash another rom again.
Click to expand...
Click to collapse
Thanks for the reply. I really hoped there was a way by installing a new rom above which would allow full disk encryption to be unlocked again.
EDIT: Before I give up, here is some extra info.
I can navigate through the TRWP file manager on system through folders, I see files and folders. Is that a clue that my phone is not full disk encrypted, or is full disk encrypted only for user data and the full system?
Also here is a dump I did via ADB shell.
Code:
~ # [6ncat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1500000 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 265375 mmcblk0p27
179 28 13404138 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ # [6n
------------------------------------------
~ # ls -la /dev/block/platform/msm_sdcc.1/by-name/[J
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 620 Jan 5 21:43 .
drwxr-xr-x 4 root root 700 Jan 5 21:43 ..
lrwxrwxrwx 1 root root 21 Jan 5 21:43 DDR -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 5 21:43 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Jan 5 21:43 abootb -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 5 21:43 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 5 21:43 cache -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 5 21:43 crypto -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 5 21:43 fsc -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 5 21:43 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 5 21:43 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 5 21:43 imgdata -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 5 21:43 laf -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 5 21:43 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 5 21:43 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 Jan 5 21:43 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 5 21:43 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 5 21:43 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 5 21:43 pad -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 5 21:43 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 5 21:43 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 5 21:43 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 5 21:43 rpmb -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 Jan 5 21:43 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 5 21:43 sbl1b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 5 21:43 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Jan 5 21:43 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 5 21:43 system -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 Jan 5 21:43 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 5 21:43 tzb -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 5 21:43 userdata -> /dev/block/mmcblk0p28
~ # [6n
I gave up and decided to reinstall android.
For those who may have trouble flashing because of /data not wanting to format, try to flash new TWRP recovery (latest one for your device.). You should be able to boot back into recovery and then you can format/wipe /data.