Attempted Unlock of Fire HD 8 (2016/ 6th generat). Is this tablet terminally bricked? - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting
I had assembled a Fire HD 8 (2016) using parts from three different tablets, and I thought I'd have a play and see it if I could unlock it using a modified version of amonet for karnak (Fire HD 8, 2018).
I started with a rooted Fire HD 8 (2016) running Fire OS 5.6.3.4 (build 626536720). Amonet-karnak-v3.01 was downloaded from here: https://forum.xda-developers.com/showpost.php?p=80166353&postcount=1. Image files from Fire OS 5.6.3.4, update-kindle-49.6.2.6_user_626536720.bin: lk.bin, tz.img, preloader.bin, preloader.hdr0 and preloader.hdr1 were copied to amonet/bin, replacing the originals. The script 'fireos-step.sh'' was edited to allow 'max_pl=6' (preloader version 6), to change the model to 'full_giza' and to change the path (PART_PREFIX=) to /dev/block/platform/mtk-msdc.0.
The output from running the modified 'fireos-step.sh' script was as follows:
Code:
[email protected]:~/Downloads/amonet-giza-t/amonet$ sudo ./fireos-step.sh
Testing root access...
uid=0(root) gid=0(root) context=u:r:init:s0
PL version: 6 (6)
LK version: 1 (1)
TZ version: 258 (258)
Flashing PL
1602 KB/s (138924 bytes in 0.084s)
271+1 records in
271+1 records out
138924 bytes transferred in 0.063 secs (2205142 bytes/sec)
271+1 records in
271+1 records out
138924 bytes transferred in 0.016 secs (8682750 bytes/sec)
Flashing LK-payload
62 KB/s (2872 bytes in 0.044s)
5+1 records in
5+1 records out
2872 bytes transferred in 0.005 secs (574400 bytes/sec)
Flashing LK
4234 KB/s (487392 bytes in 0.112s)
951+1 records in
951+1 records out
487392 bytes transferred in 0.045 secs (10830933 bytes/sec)
Flashing TZ
4218 KB/s (3307008 bytes in 0.765s)
6459+0 records in
6459+0 records out
3307008 bytes transferred in 0.287 secs (11522675 bytes/sec)
6459+0 records in
6459+0 records out
3307008 bytes transferred in 0.297 secs (11134707 bytes/sec)
Flashing TWRP
4285 KB/s (13930496 bytes in 3.174s)
27208+0 records in
27208+0 records out
13930496 bytes transferred in 1.046 secs (13317873 bytes/sec)
Patching boot
2+0 records in
2+0 records out
1024 bytes transferred in 0.001 secs (1024000 bytes/sec)
2+0 records in
2+0 records out
1024 bytes transferred in 0.004 secs (256000 bytes/sec)
- Inject microloader
2+0 records in
2+0 records out
1024 bytes transferred in 0.004 secs (256000 bytes/sec)
Flashing PL header
44 KB/s (2048 bytes in 0.044s)
44 KB/s (2048 bytes in 0.044s)
4+0 records in
4+0 records out
2048 bytes transferred in 0.040 secs (51200 bytes/sec)
4+0 records in
4+0 records out
2048 bytes transferred in 0.052 secs (39384 bytes/sec)
Rebooting to TWRP
[email protected]:~/Downloads/amonet-giza-t/amonet$
This seemed OK but after rebooting, the tablet got stuck on the white Amazon logo, with no recovery mode available.
Amonet_giza_v1.3 was downloaded from here: https://forum.xda-developers.com/showpost.php?p=80232977&postcount=1. I ran the script 'bootrom-step.sh' (shorting method) and this was apparently sucessful:
Code:
[email protected]:~/Downloads/amonet-giza-v1.3$ sudo ./bootrom-step.sh
[2020-06-17 14:49:13.017742] Waiting for bootrom
[2020-06-17 14:49:44.205417] Found port = /dev/ttyACM0
[2020-06-17 14:49:44.215424] Handshake
[2020-06-17 14:49:44.263501] Disable watchdog
* * * Remove the short and press Enter * * *
[2020-06-17 14:49:48.644612] Init crypto engine
[2020-06-17 14:49:48.790589] Disable caches
[2020-06-17 14:49:48.798307] Disable bootrom range checks
[2020-06-17 14:49:48.898946] Load payload from ../brom-payload/build/payload.bin = 0x48D8 bytes
[2020-06-17 14:49:48.965959] Send payload
[2020-06-17 14:49:53.690455] Let's rock
[2020-06-17 14:49:53.699383] Wait for the payload to come online...
[2020-06-17 14:49:54.420378] all good
[2020-06-17 14:49:54.429345] Check GPT
[2020-06-17 14:49:54.802163] gpt_parsed = {'nvram': (7168, 10240), 'recovery': (92416, 32768), 'expdb': (154880, 20480), 'para': (137472, 1024), 'lk': (58880, 1000), 'secro': (125184, 12288), 'frp': (175360, 2048), 'protect2': (37888, 20480), 'metadata': (197888, 80640), 'logo': (138496, 16384), 'tee1': (177408, 10240), 'protect1': (17408, 20480), 'tee2': (187648, 10240), 'seccfg': (58368, 512), 'boot': (59880, 32536), 'proinfo': (1024, 6144)}
[2020-06-17 14:49:54.806253] Check boot0
[2020-06-17 14:49:55.053280] Check rpmb
[2020-06-17 14:49:55.269372] Downgrade rpmb
[2020-06-17 14:49:55.277150] Recheck rpmb
[2020-06-17 14:49:56.174262] rpmb downgrade ok
[2020-06-17 14:49:56.180584] Clear preloader header
[8 / 8]
[2020-06-17 14:49:56.897490] Flashing TZ
[6459 / 6459]
[2020-06-17 14:52:29.248010] Flash LK
[952 / 952]
[2020-06-17 14:52:52.133657] Flash PL
[280 / 280]
[2020-06-17 14:53:10.364218] Reboot
[email protected]:~/Downloads/amonet-giza-v1.3
However, it is still getting stuck at the white Amazon logo. Is there any way of resurrecting this tablet?
MontysEvilTwin said:
I had assembled a Fire HD 8 (2016) using parts from three different tablets, and I thought I'd have a play and see it if I could unlock it using a modified version of amonet for karnak (Fire HD 8, 2018).
I started with a rooted Fire HD 8 (2016) running Fire OS 5.6.3.4 (build 626536720). Amonet-karnak-v3.01 was downloaded from here: https://forum.xda-developers.com/showpost.php?p=80166353&postcount=1. Image files from Fire OS 5.6.3.4, update-kindle-49.6.2.6_user_626536720.bin: lk.bin, tz.img, preloader.bin, preloader.hdr0 and preloader.hdr1 were copied to amonet/bin, replacing the originals. The script 'fireos-step.sh'' was edited to allow 'max_pl=6' (preloader version 6), to change the model to 'full_giza' and to change the path (PART_PREFIX=) to /dev/block/platform/mtk-msdc.0.
The output from running the modified 'fireos-step.sh' script was as follows:
Code:
[email protected]:~/Downloads/amonet-giza-t/amonet$ sudo ./fireos-step.sh
Testing root access...
uid=0(root) gid=0(root) context=u:r:init:s0
PL version: 6 (6)
LK version: 1 (1)
TZ version: 258 (258)
Flashing PL
1602 KB/s (138924 bytes in 0.084s)
271+1 records in
271+1 records out
138924 bytes transferred in 0.063 secs (2205142 bytes/sec)
271+1 records in
271+1 records out
138924 bytes transferred in 0.016 secs (8682750 bytes/sec)
Flashing LK-payload
62 KB/s (2872 bytes in 0.044s)
5+1 records in
5+1 records out
2872 bytes transferred in 0.005 secs (574400 bytes/sec)
Flashing LK
4234 KB/s (487392 bytes in 0.112s)
951+1 records in
951+1 records out
487392 bytes transferred in 0.045 secs (10830933 bytes/sec)
Flashing TZ
4218 KB/s (3307008 bytes in 0.765s)
6459+0 records in
6459+0 records out
3307008 bytes transferred in 0.287 secs (11522675 bytes/sec)
6459+0 records in
6459+0 records out
3307008 bytes transferred in 0.297 secs (11134707 bytes/sec)
Flashing TWRP
4285 KB/s (13930496 bytes in 3.174s)
27208+0 records in
27208+0 records out
13930496 bytes transferred in 1.046 secs (13317873 bytes/sec)
Patching boot
2+0 records in
2+0 records out
1024 bytes transferred in 0.001 secs (1024000 bytes/sec)
2+0 records in
2+0 records out
1024 bytes transferred in 0.004 secs (256000 bytes/sec)
- Inject microloader
2+0 records in
2+0 records out
1024 bytes transferred in 0.004 secs (256000 bytes/sec)
Flashing PL header
44 KB/s (2048 bytes in 0.044s)
44 KB/s (2048 bytes in 0.044s)
4+0 records in
4+0 records out
2048 bytes transferred in 0.040 secs (51200 bytes/sec)
4+0 records in
4+0 records out
2048 bytes transferred in 0.052 secs (39384 bytes/sec)
Rebooting to TWRP
[email protected]:~/Downloads/amonet-giza-t/amonet$
This seemed OK but after rebooting, the tablet got stuck on the white Amazon logo, with no recovery mode available.
Amonet_giza_v1.3 was downloaded from here: https://forum.xda-developers.com/showpost.php?p=80232977&postcount=1. I ran the script 'bootrom-step.sh' (shorting method) and this was apparently sucessful:
Code:
[email protected]:~/Downloads/amonet-giza-v1.3$ sudo ./bootrom-step.sh
[2020-06-17 14:49:13.017742] Waiting for bootrom
[2020-06-17 14:49:44.205417] Found port = /dev/ttyACM0
[2020-06-17 14:49:44.215424] Handshake
[2020-06-17 14:49:44.263501] Disable watchdog
* * * Remove the short and press Enter * * *
[2020-06-17 14:49:48.644612] Init crypto engine
[2020-06-17 14:49:48.790589] Disable caches
[2020-06-17 14:49:48.798307] Disable bootrom range checks
[2020-06-17 14:49:48.898946] Load payload from ../brom-payload/build/payload.bin = 0x48D8 bytes
[2020-06-17 14:49:48.965959] Send payload
[2020-06-17 14:49:53.690455] Let's rock
[2020-06-17 14:49:53.699383] Wait for the payload to come online...
[2020-06-17 14:49:54.420378] all good
[2020-06-17 14:49:54.429345] Check GPT
[2020-06-17 14:49:54.802163] gpt_parsed = {'nvram': (7168, 10240), 'recovery': (92416, 32768), 'expdb': (154880, 20480), 'para': (137472, 1024), 'lk': (58880, 1000), 'secro': (125184, 12288), 'frp': (175360, 2048), 'protect2': (37888, 20480), 'metadata': (197888, 80640), 'logo': (138496, 16384), 'tee1': (177408, 10240), 'protect1': (17408, 20480), 'tee2': (187648, 10240), 'seccfg': (58368, 512), 'boot': (59880, 32536), 'proinfo': (1024, 6144)}
[2020-06-17 14:49:54.806253] Check boot0
[2020-06-17 14:49:55.053280] Check rpmb
[2020-06-17 14:49:55.269372] Downgrade rpmb
[2020-06-17 14:49:55.277150] Recheck rpmb
[2020-06-17 14:49:56.174262] rpmb downgrade ok
[2020-06-17 14:49:56.180584] Clear preloader header
[8 / 8]
[2020-06-17 14:49:56.897490] Flashing TZ
[6459 / 6459]
[2020-06-17 14:52:29.248010] Flash LK
[952 / 952]
[2020-06-17 14:52:52.133657] Flash PL
[280 / 280]
[2020-06-17 14:53:10.364218] Reboot
[email protected]:~/Downloads/amonet-giza-v1.3
However, it is still getting stuck at the white Amazon logo. Is there any way of resurrecting this tablet?
Click to expand...
Click to collapse
Have you tried flashing the full image from amazon?
Michajin said:
Have you tried flashing the full image from amazon?
Click to expand...
Click to collapse
I can't get into recovery. I think that the standard recovery was overwritten by TWRP, but it won't boot into TWRP.
MontysEvilTwin said:
I can't get into recovery. I think that the standard recovery was overwritten by TWRP, but it won't boot into TWRP.
Click to expand...
Click to collapse
I never seen Giza get that far to make the full unlock/TWRP install. Can you show me the thread that unlocks it? The thread you listed was a unbrick thread. Did you try anything that might have wiped the recovery partition? Vol (+or-) and power don't try and force recovery? (i dont have a giza, just trying to help).
Michajin said:
I never seen Giza get that far to make the full unlock/TWRP install. Can you show me the thread that unlocks it? The thread you listed was a unbrick thread. Did you try anything that might have wiped the recovery partition? Vol (+or-) and power don't try and force recovery? (i dont have a giza, just trying to help).
Click to expand...
Click to collapse
There is no official unlock, I was playing around with a spare tablet and I used the latest version of amonet for karnak (v 3.0.1) but with giza bootloader files and a modified fireos-step script. According to the output (post #1) TWRP did flash correctly and as this is based on amonet for karnak it will have overwritten the recovery partition. It was a risk, as while the giza, douglas and karnak tablets all have a common processor, the douglas requires the device to be repartitioned and TWRP to be installed on a second recovery partition, karnak does not.
There is an old thread (see here: https://forum.xda-developers.com/hd8-hd10/orig-development/fire-hd8-2017-amonet-debrick-root-t3897841) which enabled the douglas to be rooted before mtk-su was released. This installed karnak bootloader files using amonet and then flashed a rooted software image (hacked fastboot) before flashing the devices own bootloaders. This also works for giza using giza bootloaders. I will probably try this method. I am not sure if it is sufficient to flash a system and boot image or if I need to reflash a separate recovery image too?
MontysEvilTwin said:
There is no official unlock, I was playing around with a spare tablet and I used the latest version of amonet for karnak (v 3.0.1) but with giza bootloader files and a modified fireos-step script. According to the output (post #1) TWRP did flash correctly and as this is based on amonet for karnak it will have overwritten the recovery partition. It was a risk, as while the giza, douglas and karnak tablets all have a common processor, the douglas requires the device to be repartitioned and TWRP to be installed on a second recovery partition, karnak does not.
There is an old thread (see here: https://forum.xda-developers.com/hd8-hd10/orig-development/fire-hd8-2017-amonet-debrick-root-t3897841) which enabled the douglas to be rooted before mtk-su was released. This installed karnak bootloader files using amonet and then flashed a rooted software image (hacked fastboot) before flashing the devices own bootloaders. This also works for giza using giza bootloaders. I will probably try this method. I am not sure if it is sufficient to flash a system and boot image or if I need to reflash a separate recovery image too?
Click to expand...
Click to collapse
I fixed it using the last method described in my previous post; the original HD 8 (2017) debrick thread. This used shorting with the bootrom method to install karnak preloader, TZ and LK files, plus hacked fastboot. I then flashed boot.img (taken from the '.bin' of the OS 5.3.6.4 software - first build), system.img (created from the same software using a python script, as described in the link) and, to be safe, I also flashed recovery.img (copied from another 2016 HD 8 running the same version of software). Then I used bootrom again (amonet-res from the link, with 2016 HD 8 files) to restore 2016 HD 8 preloader plus LK and TZ files. The device then booted normally into Fire OS.
MontysEvilTwin said:
I fixed it using the last method described in my previous post; the original HD 8 (2017) debrick thread. This used shorting with the bootrom method to install karnak preloader, TZ and LK files, plus hacked fastboot. I then flashed boot.img (taken from the '.bin' of the OS 5.3.6.4 software - first build), system.img (created from the same software using a python script, as described in the link) and, to be safe, I also flashed recovery.img (copied from another 2016 HD 8 running the same version of software). Then I used bootrom again (amonet-res from the link, with 2016 HD 8 files) to restore 2016 HD 8 preloader plus LK and TZ files. The device then booted normally into Fire OS.
Click to expand...
Click to collapse
Awesome!
Sounds like you had it unlocked, and you could have installed TWRP (douglas?) over stock recovery from the hacked fastboot.
Michajin said:
Awesome!
Sounds like you had it unlocked, and you could have installed TWRP (douglas?) over stock recovery from the hacked fastboot.
Click to expand...
Click to collapse
I think someone who knows what they are doing could get it working. I know it flashed TWRP for karnak when I first tried to unlock but something I did temporarily bricked the tablet. The method I used to recover installs karnak files on the device. The screen stays black but hacked fastboot still runs.
It may be that the exploit for douglas is worth trying. This is a bit different to karnak in that it repartitions the device and installs TWRP on a secondary partition.
MontysEvilTwin said:
I think someone who knows what they are doing could get it working. I know it flashed TWRP for karnak when I first tried to unlock but something I did temporarily bricked the tablet. The method I used to recover installs karnak files on the device. The screen stays black but hacked fastboot still runs.
It may be that the exploit for douglas is worth trying. This is a bit different to karnak in that it repartitions the device and installs TWRP on a secondary position.
Click to expand...
Click to collapse
Promising move. Thanks! :good:
Wish @k4y0z or @xyz could spare some time to look into your hints described here to unlock this 8hd 6th gen bad boy.
Fingers crossed!
drdtyc said:
Promising move. Thanks! :good:
Wish @k4y0z or @xyz could spare some time to look into your hints described here to unlock this 8hd 6th gen bad boy.
Fingers crossed!
Click to expand...
Click to collapse
I have done nothing original really. I am sure those guys you mentioned could make this work (assuming the LK file has the necessary vulnerability) but they may not have the tablet in question, the time and/ or the inclination.
You did a great job. I expect that you only need some operations. To try, I can help you try because I own 3 from Amazon hd8 6th giza
I was thinking of modifying amonet for douglas (HD 8, 2017) and trying it on the 2016 model. This would involve replacing some of the files in amonet/bin with their equivalents from the latest HD 8, 2016 software 'bin' and minor tweaking of the 'step-1' and 'step-2' scripts. This method re-partitions the device to create new 'boot_x' and 'recovery_x' partitions. The partitioning schemes for these two devices are different: they have the same 'by-name' paths, but the 2016 model has some extra partitions, and has a different partition numbering scheme. I am not sure if the amonet (HD 8, 2017) scripts would partition the 2016 device correctly or if they would create an unrecoverable brick. I may try it anyway at some point out of curiosity.
MontysEvilTwin said:
I was thinking of modifying amonet for douglas (HD 8, 2017) and trying it on the 2016 model. This would involve replacing some of the files in amonet/bin with their equivalents from the latest HD 8, 2016 software 'bin' and minor tweaking of the 'step-1' and 'step-2' scripts. This method re-partitions the device to create new 'boot_x' and 'recovery_x' partitions. The partitioning schemes for these two devices are different: they have the same 'by-name' paths, but the 2016 model has some extra partitions, and has a different partition numbering scheme. I am not sure if the amonet (HD 8, 2017) scripts would partition the 2016 device correctly or if they would create an unrecoverable brick. I may try it anyway at some point out of curiosity.
Click to expand...
Click to collapse
Great, as amonet for giza is taking shape!
Would pm @k4y0z get a useful answer of partition schemes ? It is like straight from the horse's mouth, so to speak, as he is the author of those 'step-1' and 'step-2' scripts.
My apologies in advance if this post breaks any etiquette of the XDA forum.
drdtyc said:
Great, as amonet for giza is taking shape!
Would pm @k4y0z get a useful answer of partition schemes ? It is like straight from the horse's mouth, so to speak, as he is the author of those 'step-1' and 'step-2' scripts.
My apologies in advance if this post breaks any etiquette of the XDA forum.
Click to expand...
Click to collapse
Please don't get your hopes up. I am having a look out of interest and to learn a bit, but what needs changing may be beyond me.
MontysEvilTwin said:
Please don't get your hopes up. I am having a look out of interest and to learn a bit, but what needs changing may be beyond me.
Click to expand...
Click to collapse
Good that you are looking into this!
Keep up the good work.
Not all hope is lost yet to unlock this bad boy.
---------- Post added at 05:42 PM ---------- Previous post was at 05:35 PM ----------
https://forum.xda-developers.com/hd8-hd10/general/custom-recovery-rooted-6th-gen-fire-hd-t3540050
This thread discusses the partition structure of several Fire tablets including the 8hd 6th gen. All these are beyond me.
It may be of use to @MontysEvilTwin.
---------- Post added at 05:43 PM ---------- Previous post was at 05:42 PM ----------
https://forum.xda-developers.com/amazon-fire/development/partitions-list-t3236213
This thread lists the partition structure of Fire Android devices.
It may be of use to @MontysEvilTwin.
anyone need help i am ready i have three rooted device from GIZA
regards
Ever since I got the tablet in 2017, I was looking for a way to get TWRP working on this device. Thanks for giving me hope for a a full unlock experience!
I have a rooted device, so feel free to ask me run some commands (that doesn't brick it hopefully, it's my daily driver for stuff)
(I guess it's almost time to start porting LineageOS?)
Unfortunately my attempt has ended in failure. I downloaded amonet-douglas-v1.2 (see here: https://forum.xda-developers.com/showpost.php?p=80154797&postcount=1) and replaced the LK, TZ, and preloader images in the 'bin' folder with those from the latest version of FIre OS for giza (5.3.6.4). I also edited the 'Step-1' and 'Step-2' scripts to allow them to run on the giza (HD 8, 2016). I ran Step-1. Output here:
Code:
[email protected]:~/Downloads/amonet-giza-t2/amonet$ sudo ./step-1.sh
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Testing root access...
uid=0(root) gid=0(root) context=u:r:init:s0
PL version: 6 (6)
LK version: 1 (2)
TZ version: 258 (259)
Your device will be reset to factory defaults...
Press Enter to Continue...
Dumping GPT
34+0 records in
34+0 records out
17408 bytes transferred in 0.001 secs (17408000 bytes/sec)
97 KB/s (17408 bytes in 0.174s)
Modifying GPT
[2020-06-23 12:47:56.140090] Input GPT:
[2020-06-23 12:47:56.155798]
[2020-06-23 12:47:56.165320] Sector size (logical): 512 bytes
[2020-06-23 12:47:56.181377] Disk identifier (GUID): 0977B6B6-2B39-4075-8CCF-F0F9A3D117CD
[2020-06-23 12:47:56.187570] Partition table holds up to 128 entries
[2020-06-23 12:47:56.192110] This partition table begins at sector 2 and ends at sector 33
[2020-06-23 12:47:56.196498] First usable sector is 34, last usable sector is 30777310
[2020-06-23 12:47:56.201418] Other partition table is at sector 30777343
[2020-06-23 12:47:56.207044]
[2020-06-23 12:47:56.212063] Number Start (sector) End (sector) Size Name
[2020-06-23 12:47:56.270255] 1 1024 7167 3.00 MiB proinfo
[2020-06-23 12:47:56.280114] 2 7168 17407 5.00 MiB nvram
[2020-06-23 12:47:56.294441] 3 17408 37887 10.00 MiB protect1
[2020-06-23 12:47:56.315751] 4 37888 58367 10.00 MiB protect2
[2020-06-23 12:47:56.327317] 5 58368 58879 256.00 KiB seccfg
[2020-06-23 12:47:56.338008] 6 58880 59879 500.00 KiB lk
[2020-06-23 12:47:56.348155] 7 59880 92415 15.89 MiB boot
[2020-06-23 12:47:56.364741] 8 92416 125183 16.00 MiB recovery
[2020-06-23 12:47:56.375237] 9 125184 137471 6.00 MiB secro
[2020-06-23 12:47:56.385676] 10 137472 138495 512.00 KiB para
[2020-06-23 12:47:56.403211] 11 138496 154879 8.00 MiB logo
[2020-06-23 12:47:56.414057] 12 154880 175359 10.00 MiB expdb
[2020-06-23 12:47:56.423967] 13 175360 177407 1024.00 KiB frp
[2020-06-23 12:47:56.446425] 14 177408 187647 5.00 MiB tee1
[2020-06-23 12:47:56.457419] 15 187648 197887 5.00 MiB tee2
[2020-06-23 12:47:56.466734] 16 197888 278527 39.38 MiB metadata
[2020-06-23 12:47:56.486107] 17 278528 280575 1024.00 KiB kb
[2020-06-23 12:47:56.501732] 18 280576 282623 1024.00 KiB dkb
[2020-06-23 12:47:56.511501] 19 282624 3588671 1.58 GiB system
[2020-06-23 12:47:56.534411] 20 3588672 4457023 424.00 MiB cache
[2020-06-23 12:47:56.545231] 21 4457024 4458047 512.00 KiB MISC
[2020-06-23 12:47:56.554629] 22 4458048 4490815 16.00 MiB persisbackup
[2020-06-23 12:47:56.572927] 23 4490816 4499455 4.22 MiB PMT
[2020-06-23 12:47:56.583723] 24 4499456 30777310 12.53 GiB userdata
[2020-06-23 12:47:57.130509]
[2020-06-23 12:47:57.135884] Regenerate primary and backup GPT from input
[2020-06-23 12:47:57.140959] Writing regenerated GPT to gpt-G000KW0463310950/gpt.bin.gpt
[2020-06-23 12:47:57.272546] Writing regenerated backup GPT to gpt-G000KW0463310950/gpt.bin.bak
[2020-06-23 12:47:57.296137] Writing backup GPT offset to gpt-G000KW0463310950/gpt.bin.offset
[2020-06-23 12:47:57.325285]
[2020-06-23 12:47:57.330897] Modified GPT Step 1:
[2020-06-23 12:47:57.351999]
[2020-06-23 12:47:57.358603] Sector size (logical): 512 bytes
[2020-06-23 12:47:57.364570] Disk identifier (GUID): 0977B6B6-2B39-4075-8CCF-F0F9A3D117CD
[2020-06-23 12:47:57.369705] Partition table holds up to 128 entries
[2020-06-23 12:47:57.374261] This partition table begins at sector 2 and ends at sector 33
[2020-06-23 12:47:57.378757] First usable sector is 34, last usable sector is 30777310
[2020-06-23 12:47:57.383981] Other partition table is at sector 30777343
[2020-06-23 12:47:57.389786]
[2020-06-23 12:47:57.396300] Number Start (sector) End (sector) Size Name
[2020-06-23 12:47:57.413002] 1 1024 7167 3.00 MiB proinfo
[2020-06-23 12:47:57.429682] 2 7168 17407 5.00 MiB nvram
[2020-06-23 12:47:57.462799] 3 17408 37887 10.00 MiB protect1
[2020-06-23 12:47:57.479811] 4 37888 58367 10.00 MiB protect2
[2020-06-23 12:47:57.500102] 5 58368 58879 256.00 KiB seccfg
[2020-06-23 12:47:57.513027] 6 58880 59879 500.00 KiB lk
[2020-06-23 12:47:57.521735] 7 59880 92415 15.89 MiB boot
[2020-06-23 12:47:57.530851] 8 92416 125183 16.00 MiB recovery
[2020-06-23 12:47:57.546480] 9 125184 137471 6.00 MiB secro
[2020-06-23 12:47:57.558800] 10 137472 138495 512.00 KiB para
[2020-06-23 12:47:57.567431] 11 138496 154879 8.00 MiB logo
[2020-06-23 12:47:57.583867] 12 154880 175359 10.00 MiB expdb
[2020-06-23 12:47:57.601516] 13 175360 177407 1024.00 KiB frp
[2020-06-23 12:47:57.612980] 14 177408 187647 5.00 MiB tee1
[2020-06-23 12:47:57.622936] 15 187648 197887 5.00 MiB tee2
[2020-06-23 12:47:57.633490] 16 197888 278527 39.38 MiB metadata
[2020-06-23 12:47:57.647775] 17 278528 280575 1024.00 KiB kb
[2020-06-23 12:47:57.659414] 18 280576 282623 1024.00 KiB dkb
[2020-06-23 12:47:57.679812] 19 282624 3588671 1.58 GiB system
[2020-06-23 12:47:57.690797] 20 3588672 4457023 424.00 MiB cache
[2020-06-23 12:47:57.700665] 21 4457024 4458047 512.00 KiB MISC
[2020-06-23 12:47:57.714175] 22 4458048 4490815 16.00 MiB persisbackup
[2020-06-23 12:47:57.730194] 23 4490816 4499455 4.22 MiB PMT
[2020-06-23 12:47:57.739627] 24 4499456 30325759 12.31 GiB userdata
[2020-06-23 12:47:57.749898] 25 30325760 30551039 110.00 MiB boot_tmp
[2020-06-23 12:47:57.759279] 26 30551040 30776319 110.00 MiB recovery_tmp
[2020-06-23 12:47:58.281302]
[2020-06-23 12:47:58.286574] Writing primary GPT (part 1) to gpt-G000KW0463310950/gpt.bin.step1.gpt
[2020-06-23 12:47:58.428890] Writing backup GPT (part 1) to gpt-G000KW0463310950/gpt.bin.step1.bak
[2020-06-23 12:47:58.455505]
[2020-06-23 12:47:58.466746] Modified GPT Step 2:
[2020-06-23 12:47:58.481602]
[2020-06-23 12:47:58.487415] Sector size (logical): 512 bytes
[2020-06-23 12:47:58.492206] Disk identifier (GUID): 0977B6B6-2B39-4075-8CCF-F0F9A3D117CD
[2020-06-23 12:47:58.511517] Partition table holds up to 128 entries
[2020-06-23 12:47:58.518431] This partition table begins at sector 2 and ends at sector 33
[2020-06-23 12:47:58.523640] First usable sector is 34, last usable sector is 30777310
[2020-06-23 12:47:58.529462] Other partition table is at sector 30777343
[2020-06-23 12:47:58.543548]
[2020-06-23 12:47:58.566847] Number Start (sector) End (sector) Size Name
[2020-06-23 12:47:58.578207] 1 1024 7167 3.00 MiB proinfo
[2020-06-23 12:47:58.600018] 2 7168 17407 5.00 MiB nvram
[2020-06-23 12:47:58.621133] 3 17408 37887 10.00 MiB protect1
[2020-06-23 12:47:58.629613] 4 37888 58367 10.00 MiB protect2
[2020-06-23 12:47:58.642478] 5 58368 58879 256.00 KiB seccfg
[2020-06-23 12:47:58.656863] 6 58880 59879 500.00 KiB lk
[2020-06-23 12:47:58.665863] 7 59880 92415 15.89 MiB boot_x
[2020-06-23 12:47:58.674533] 8 92416 125183 16.00 MiB recovery_x
[2020-06-23 12:47:58.686749] 9 125184 137471 6.00 MiB secro
[2020-06-23 12:47:58.713124] 10 137472 138495 512.00 KiB para
[2020-06-23 12:47:58.726349] 11 138496 154879 8.00 MiB logo
[2020-06-23 12:47:58.738046] 12 154880 175359 10.00 MiB expdb
[2020-06-23 12:47:58.764317] 13 175360 177407 1024.00 KiB frp
[2020-06-23 12:47:58.777031] 14 177408 187647 5.00 MiB tee1
[2020-06-23 12:47:58.793473] 15 187648 197887 5.00 MiB tee2
[2020-06-23 12:47:58.805405] 16 197888 278527 39.38 MiB metadata
[2020-06-23 12:47:58.813721] 17 278528 280575 1024.00 KiB kb
[2020-06-23 12:47:58.823369] 18 280576 282623 1024.00 KiB dkb
[2020-06-23 12:47:58.836732] 19 282624 3588671 1.58 GiB system
[2020-06-23 12:47:58.855238] 20 3588672 4457023 424.00 MiB cache
[2020-06-23 12:47:58.868765] 21 4457024 4458047 512.00 KiB MISC
[2020-06-23 12:47:58.895499] 22 4458048 4490815 16.00 MiB persisbackup
[2020-06-23 12:47:58.905577] 23 4490816 4499455 4.22 MiB PMT
[2020-06-23 12:47:58.913732] 24 4499456 30325759 12.31 GiB userdata
[2020-06-23 12:47:58.925229] 25 30325760 30551039 110.00 MiB boot
[2020-06-23 12:47:58.944759] 26 30551040 30776319 110.00 MiB recovery
[2020-06-23 12:47:59.460926]
[2020-06-23 12:47:59.466811] Writing primary GPT (part 2) to gpt-G000KW0463310950/gpt.bin.step2.gpt
[2020-06-23 12:47:59.594491] Writing backup GPT (part 2) to gpt-G000KW0463310950/gpt.bin.step2.bak
Flashing temp GPT
239 KB/s (17408 bytes in 0.070s)
34+0 records in
34+0 records out
17408 bytes transferred in 0.001 secs (17408000 bytes/sec)
Preparing for Factory Reset
Rebooting into Recovery
[email protected]:~/Downloads/amonet-giza-t2/amonet$
This seemed to run OK; the device rebooted and did a factory reset. I then ran Step-2. The output is below:
Code:
[email protected]:~/Downloads/amonet-giza-t2/amonet$ sudo ./step-2.sh
Testing root access...
uid=0(root) gid=0(root) context=u:r:init:s0
Looking for partition-suffix
lrwxrwxrwx root root 2020-06-23 11:48 recovery_tmp -> /dev/block/mmcblk0p26
Flashing exploit
57 KB/s (4096 bytes in 0.069s)
3563 KB/s (492132 bytes in 0.134s)
8+0 records in
8+0 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
961+1 records in
961+1 records out
492132 bytes transferred in 0.035 secs (14060914 bytes/sec)
8+0 records in
8+0 records out
4096 bytes transferred in 0.002 secs (2048000 bytes/sec)
961+1 records in
961+1 records out
492132 bytes transferred in 0.034 secs (14474470 bytes/sec)
Flashing LK
3589 KB/s (487392 bytes in 0.132s)
951+1 records in
951+1 records out
487392 bytes transferred in 0.040 secs (12184800 bytes/sec)
Flashing TZ
3689 KB/s (3307008 bytes in 0.875s)
6459+0 records in
6459+0 records out
3307008 bytes transferred in 0.270 secs (12248177 bytes/sec)
6459+0 records in
6459+0 records out
3307008 bytes transferred in 0.325 secs (10175409 bytes/sec)
Flashing Preloader
44 KB/s (2048 bytes in 0.044s)
44 KB/s (2048 bytes in 0.044s)
1706 KB/s (138924 bytes in 0.079s)
4+0 records in
4+0 records out
2048 bytes transferred in 0.056 secs (36571 bytes/sec)
4+0 records in
4+0 records out
2048 bytes transferred in 0.059 secs (34711 bytes/sec)
271+1 records in
271+1 records out
138924 bytes transferred in 0.067 secs (2073492 bytes/sec)
271+1 records in
271+1 records out
138924 bytes transferred in 0.018 secs (7718000 bytes/sec)
Flashing final GPT
350 KB/s (17408 bytes in 0.048s)
34+0 records in
34+0 records out
17408 bytes transferred in 0.002 secs (8704000 bytes/sec)
Flashing final GPT (backup)
335 KB/s (16896 bytes in 0.049s)
33+0 records in
33+0 records out
16896 bytes transferred in 0.002 secs (8448000 bytes/sec)
Flashing TWRP
3565 KB/s (13512704 bytes in 3.701s)
26392+0 records in
26392+0 records out
13512704 bytes transferred in 1.596 secs (8466606 bytes/sec)
Rebooting into TWRP
[email protected]:~/Downloads/amonet-giza-t2/amonet$
Unfortunately, after rebooting the device got stuck on the white Amazon logo. I attempted to recover using the original debrick method for douglas (a reworking of the original karnak unlock method) modified for giza: see here (https://forum.xda-developers.com/showpost.php?p=78853205&postcount=1) However the bottom write method fell over; the device failed a gpt check:
Code:
[email protected]:/media/x/SD Card/Giza-Restore/amonet$ sudo ./bootrom-step.sh
[2020-06-23 15:30:19.049767] Waiting for bootrom
[2020-06-23 15:30:33.527575] Found port = /dev/ttyACM0
[2020-06-23 15:30:33.542589] Handshake
[2020-06-23 15:30:33.581694] Disable watchdog
* * * Remove the short and press Enter * * *
[2020-06-23 15:30:35.884990] Init crypto engine
[2020-06-23 15:30:36.034842] Disable caches
[2020-06-23 15:30:36.044648] Disable bootrom range checks
[2020-06-23 15:30:36.161904] Load payload from ../brom-payload/build/payload.bin = 0x4690 bytes
[2020-06-23 15:30:36.205440] Send payload
[2020-06-23 15:30:40.773015] Let's rock
[2020-06-23 15:30:40.788256] Wait for the payload to come online...
[2020-06-23 15:30:41.517972] all good
[2020-06-23 15:30:41.527461] Check GPT
[2020-06-23 15:30:41.888837] gpt_parsed = {'tee1': (177408, 10240), 'boot_x': (59880, 32536), 'nvram': (7168, 10240), 'frp': (175360, 2048), 'metadata': (197888, 80640), 'protect1': (17408, 20480), 'protect2': (37888, 20480), 'logo': (138496, 16384), 'tee2': (187648, 10240), 'secro': (125184, 12288), 'expdb': (154880, 20480), 'seccfg': (58368, 512), 'proinfo': (1024, 6144), 'lk': (58880, 1000), 'recovery_x': (92416, 32768), 'para': (137472, 1024)}
Traceback (most recent call last):
File "main.py", line 123, in <module>
main()
File "main.py", line 69, in main
raise RuntimeError("bad gpt")
RuntimeError: bad gpt
[email protected]:/media/x/SD Card/Giza-Restore/amonet$
Is there anything I can do to restore this tablet?
Looks like the device now has 'boot_x' and 'recovery_x' partitions but no boot or recovery. I can get bootrom working (by modifying 'main.py') but can't get into fastboot. Is it possible to rename the '_x' partitions directly through bootrom? Or is there another clever way?
Related
Partition problems, no ERI, Unknown IMEI, no USB
I was attempting to troubleshoot another phone I had and it was suggested somewhere on here that I back up my efs partition and gave directions to use the command "reboot nvbackup". Well the result was not good. I've searched the forums for over a week and have decided to finally post as I'm out of ideas. I followed radionerd's thread here and was able to get the Baseband back but I still do not have anything in "Hardware Version", and show "0" in PRL version, "None" in ERI version, "Unknown" in IMEI. The kicker is that somehow my USB no longer works when connecting to the PC. The cord works fine with other phones and it charges this phone but gives a "USB device is not recognized" error when connecting, under device manager it shows up as "Device Descriptor Request Failed". I have been able to flash back to a stock ROM using TWRP (RUEOF1 is what I've been flashing) but that hasn't helped at all. I've attempted to copy mmcblk1 from the sd but it always fails, both from TWRP file manager and from the ES File Explorer. I'm guessing if I was able to flash a new PIT file I'd be good but I have no idea how to do that without having USB support. I do have working WIFI and SD card access, along with a good operating system. I've tried a lot of stuff over the past week so I apologize if I haven't already mentioned it but I'm looking for help to see if anyone has an idea about what can be done. Thanks!
If you unlocked your bootloader using the "standard method" then the "debrick" image you created on the SD card has a backup of literally every partition EXCEPT the ones that you would normally flash with Odin (or a ROM, e.g. boot, system, userdata, cache etc). The reason that that unlocking method created a debrick image is so that people could save it so they would have it for emergencies. Such as the one you created. Even the PIT data is included in a hidden partition inside the debrick image. But having a PIT file only allows you to re-partition flash memory, which you don't need; it's partitioned already. Re-writing the PIT is not going to magically recreate data inside those partitions that you erased. Here's the bottom line: factory images, just like ROM files have NEVER had 100% of the partitions needed to restore the phone back to working condition. So there's darn good reasons to have backups or avoid wiping all of memory. I think that @hsbadr had posted some debrick images taken during older ROM releases (N* series, I think) on his AFH (androidfilehost.com) site. Whether or not substituting some subset of those partitions (e.g. efs, persist, etc) onto your device will work correctly or not, but it's certainly worth a try at this point. Skills you need to learn: figuring out byte offsets from the GPT partition table at the beginning of the debrick file to get the partition offsets in the "debrick" blob, and "dd" command options for grabbing exactly the byte ranges you want out of a single large blob file containing many partitions. (e.g. "skip=", "bs=", "count="). Note also that the Unix GPT partitioning tools "gdisk" will let you examine the Primary GPT (UEFI?) partition table in the debrick image even though the secondary GPT is not present. That way, you can figure out the exact length and initial offset of partitions that you want to copy out of the debrick image into your device. (The reason for the missing secondary GPT is that the GPT/UEFI partition table indicates the presence of very large partitions such as /system, /cache, and /userdata, and the secondary GPT is always near the very end of the disk. Because the "debrick" image is literally a byte-for-byte copy of only the first 256 MB of the mmcblk0 flash device, there is no secondary GPT some 32GB "later" then the beginning of the debrick image. red indicates partitions in debrick not appearing in Odin factory Images Code: $ gdisk /tmp/mj7-debrick-unlocked.img Command (? for help): p Disk /tmp/mj7-debrick-unlocked.img: 524288 sectors, 256.0 MiB Logical sector size: 512 bytes Disk identifier (GUID): NNNNNNNN-NNNN-NNNN-NNNN-NNNNNNNNNNNN Partition table holds up to 128 entries First usable sector is 34, last usable sector is 61071326 Partitions will be aligned on 2-sector boundaries Total free space is 8158 sectors (4.0 MiB) Number Start (sector) End (sector) Size Code Name 1 8192 38911 15.0 MiB 8300 apnhlos 2 38912 156543 57.4 MiB 0700 modem 3 156544 157567 512.0 KiB FFFF sbl1 4 157568 157631 32.0 KiB FFFF dbi 5 157632 157695 32.0 KiB FFFF ddr 6 157696 161791 2.0 MiB FFFF aboot 7 161792 162815 512.0 KiB FFFF rpm 8 162816 163839 512.0 KiB FFFF tz [color=red] 9 163840 184319 10.0 MiB FFFF pad 10 184320 204799 10.0 MiB 8300 param 11 204800 233471 14.0 MiB 8300 efs 12 233472 239615 3.0 MiB FFFF modemst1 13 239616 245759 3.0 MiB FFFF modemst2[/color] 14 245760 268287 11.0 MiB FFFF boot 15 268288 294911 13.0 MiB FFFF recovery [color=red] 16 294912 321535 13.0 MiB FFFF fota 17 321536 335853 7.0 MiB 8300 backup 18 335854 341997 3.0 MiB FFFF fsg 19 341998 341999 1024 bytes FFFF fsc 20 342000 342015 8.0 KiB FFFF ssd 21 342016 358399 8.0 MiB 8300 persist 22 358400 376831 9.0 MiB 8300 persdata [/color] --------- debrick image ends ~72 MB into the start of the system partition -------- 23 376832 5931007 2.6 GiB 8300 system 24 5931008 8028159 1024.0 MiB 8300 cache 25 8028160 61071326 25.3 GiB 8300 userdata I would start by restoring as few partitions are necessary e.g. "efs" and "persist" before I would bother with the others. Example using data given above. (You should check your own work.) efs partition: blocks 204800 to 233471 in debrick image, blocks are 512 bytes. check length: (233471-204800+1)*512 = 14680064 14680064 / (1024 * 1024) = 14 O.K. so: # dd if=/sdcard/debrick.img bs=512 skip=204800 count=28672 of=/dev/block/platform/msm_sdcc.1/by-name/efs (or get clever and faster) # dd if=/sdcard/debrick.img bs=1048576 skip=100 count=14 of=/dev/block/platform/msm_sdcc.1/by-name/efs You should be pretty sure what you are doing with byte offset calculations with the "dd" command. Fortunately you are relying on the partitioning already present on the output side of things, so the worst that you could do is write misaligned garbage to a partition. So long as you don't do something incredibly stupid like overwrite a bootloader partition you should be OK. cheers
Thanks for the reply, I forgot to subscribe so I just saw the post. I have been able to copy all of the partitions from another phone but it hasn't helped. I'm now wondering if I'm missing a hidden partition.
LG V20 9008 Error
I screwed up my V20. Now the only thing the device manager sees is Qualcomm HS-USB QDLoader 9008. Anybody know a fix?
bump ---------- Post added at 07:58 PM ---------- Previous post was at 07:52 PM ---------- looks like we just need board diag settings for the lg boardiag tool here https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868
For now, only LG can fix that. If your phone is still under warranty with your carrier, or with LG -- send it back. When I was starting off with the V20 before I understood that they used UFS memory now, and had updated protected boot, I bricked one phone twice, and another on purpose (to test something), and LG fixed both phones all three times. -- Brian
Yeah. I ended up shipping it to them. Already had an overheating issue so they didn't even check to see what was going on. They just replaced the mobo. Thank you for the reply though.
Do you mind me asking what you did to get the 9008? -- Brian
No not at all. Let's see...If I remember right I was flashing firmware in LG UP and LG UP froze the device. And without thinking about it I pulled the battery and caused it not to install anything. I have a H910 variant so there was no KDZ for it. So I had flashed the H910PR originally and it worked but I wanted root back so I was trying to flash I think either the H915 or H918. Pretty sure H915 KDZ.
H915 flashes fine on the H910 (only way to root it now). The H918 uses a different RSA key, so if you flash any other model's KDZ onto the H918, or the H918 KDZ onto any other model, it will have the wrong RSA key, and go into 9008 mode. The other possibility, is that depending on which H910PR KDZ you flashed, it may have incremented the ARB (anti-rollback) version. If you then flashed the H915 KDZ, it may have had a lower ARB. If you flash firmware that has a lower ARB than what is on your phone, it also goes into 9008 mode. -- Brian
Huh. Thank for that info. Speaking of that I saw your H910M root and it worked but I ran into issues with LineageOS so I ended up forced to go back to stock and in doing so had to update to the SW:H91010p. Build:NRD90M. I still have the dump from the root process though. ARB is 0 you think I could flash it back to the H910M?
Yep! You can flash any firmware for a given model as long as the ARB is the same version or greater. ARB gets burned into QFPROM the first time XBL loads. So if you flash firmware that has a greater ARB, and your phone boots, you are now stuck on that ARB version. The H910 is ARB 0 for 10p, so you are fine flashing 10m. -- Brian
Awesome. I'm doing a dumb just in case something goes awry. Thank you.
runningnak3d said: Do you mind me asking what you did to get the 9008? -- Brian Click to expand... Click to collapse I was shipping mine to them for a couple other issues, and was rooted with TWRP running the latest firmware on H918. I wanted to flash stock firmware to undo the root and TWRP so they wouldn't know it had been modified, but I also wanted to put it on an earlier firmware so I could root it again when I got it back, I was gonna tell them not to update the FW. Long story short I guess anti roll back was tripped despite the root and TWRP so LGUP wouldnt flash older firmware. I thought I'd be slick and flash the bootloader to an older one from twrp and see if LGUP would flash it then. Nope. Total brick. This is the first time I have ever full on bricked a device in over 10 years of modifying phones starting with windows mobile.
kdz extract for linux sd card write done command link https://mega.nz/#!cJ9WUAiA!TSt9L5G3C...n8vx0pQ9ToxCFw https://forum.xda-developers.com/g4/...-qfil-t3748946 [[email protected] ~]$ sudo dmesg -c >> /dev/null [sudo] password for android: [[email protected] ~]$ dmesg [13324.923241] usb 1-2: new full-speed USB device number 11 using ohci-pci [13325.594494] usb 1-2: config 1 interface 0 altsetting 0 endpoint 0x81 has invalid maxpacket 512, setting to 64 [13325.594499] usb 1-2: config 1 interface 0 altsetting 0 endpoint 0x2 has invalid maxpacket 512, setting to 64 [13325.618041] usb-storage 1-2:1.0: USB Mass Storage device detected [13325.634811] scsi host3: usb-storage 1-2:1.0 [13326.672238] scsi 3:0:0:0: Direct-Access Mass Storage Device 1.00 PQ: 0 ANSI: 0 CCS [13326.695215] sd 3:0:0:0: [sdb] 61857792 512-byte logical blocks: (31.7 GB/29.5 GiB) [13326.707634] sd 3:0:0:0: [sdb] Write Protect is off [13326.707636] sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00 [13326.722615] sd 3:0:0:0: [sdb] No Caching mode page found [13326.722617] sd 3:0:0:0: [sdb] Assuming drive cache: write through [13326.802629] sdb: sdb1 [13326.859174] sd 3:0:0:0: [sdb] Attached SCSI removable disk [[email protected] ~]$ sudo fdisk -l /dev/sdb Disk /dev/sdb: 29.5 GiB, 31671189504 bytes, 61857792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdb1 8192 61857791 61849600 29.5G c W95 FAT32 (LBA) [[email protected] ~]$ cd /home/android/21y/ [[email protected] 21y]$ sudo -s [fwul 21y]# dd if=PrimaryGPT.bin of=/dev/sdb 32768+0 records in 32768+0 records out 16777216 bytes (17 MB, 16 MiB) copied, 43.9727 s, 382 kB/s [fwul 21y]# sync [fwul 21y]# ls -la /dev/disk/by-partlabel/sbl1 lrwxrwxrwx 1 root root 10 May 3 09:17 /dev/disk/by-partlabel/sbl1 -> ../../sdb3 [fwul 21y]# cd /home/android/21y/ [fwul 21y]# sudo -s [fwul 21y]# for i in $(ls *.bin |egrep -v "(GPT|userdata)");do echo dd if=$i of=/dev/disk/by-partlabel/${i/\.bin};done dd if=abootbak.bin of=/dev/disk/by-partlabel/abootbak dd if=aboot.bin of=/dev/disk/by-partlabel/aboot dd if=apdp.bin of=/dev/disk/by-partlabel/apdp dd if=boot.bin of=/dev/disk/by-partlabel/boot dd if=factory.bin of=/dev/disk/by-partlabel/factory dd if=felica.bin of=/dev/disk/by-partlabel/felica dd if=hypbak.bin of=/dev/disk/by-partlabel/hypbak dd if=hyp.bin of=/dev/disk/by-partlabel/hyp dd if=laf.bin of=/dev/disk/by-partlabel/laf dd if=modem.bin of=/dev/disk/by-partlabel/modem dd if=msadp.bin of=/dev/disk/by-partlabel/msadp dd if=persist.bin of=/dev/disk/by-partlabel/persist dd if=pmicbak.bin of=/dev/disk/by-partlabel/pmicbak dd if=pmic.bin of=/dev/disk/by-partlabel/pmic dd if=raw_resourcesbak.bin of=/dev/disk/by-partlabel/raw_resourcesbak dd if=raw_resources.bin of=/dev/disk/by-partlabel/raw_resources dd if=recovery.bin of=/dev/disk/by-partlabel/recovery dd if=rpmbak.bin of=/dev/disk/by-partlabel/rpmbak dd if=rpm.bin of=/dev/disk/by-partlabel/rpm dd if=sbl1bak.bin of=/dev/disk/by-partlabel/sbl1bak dd if=sbl1.bin of=/dev/disk/by-partlabel/sbl1 dd if=sdibak.bin of=/dev/disk/by-partlabel/sdibak dd if=sdi.bin of=/dev/disk/by-partlabel/sdi dd if=sec.bin of=/dev/disk/by-partlabel/sec dd if=system_691200.bin of=/dev/disk/by-partlabel/system_691200 dd if=tzbak.bin of=/dev/disk/by-partlabel/tzbak dd if=tz.bin of=/dev/disk/by-partlabel/tz [fwul 21y]# for i in $(ls *.bin |egrep -v "(GPT|userdata)");do dd if=$i of=/dev/disk/by-partlabel/${i/\.bin};done 4096+0 records in 4096+0 records out 2097152 bytes (2.1 MB, 2.0 MiB) copied, 4.99972 s, 419 kB/s 4096+0 records in 4096+0 records out 2097152 bytes (2.1 MB, 2.0 MiB) copied, 5.16635 s, 406 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.42203 s, 369 kB/s 81920+0 records in 81920+0 records out 41943040 bytes (42 MB, 40 MiB) copied, 136.39 s, 308 kB/s 94208+0 records in 94208+0 records out 48234496 bytes (48 MB, 46 MiB) copied, 118.618 s, 407 kB/s 16384+0 records in 16384+0 records out 8388608 bytes (8.4 MB, 8.0 MiB) copied, 20.8579 s, 402 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.41575 s, 370 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.36919 s, 383 kB/s 98304+0 records in 98304+0 records out 50331648 bytes (50 MB, 48 MiB) copied, 121.167 s, 415 kB/s 176128+0 records in 176128+0 records out 90177536 bytes (90 MB, 86 MiB) copied, 219.763 s, 410 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.57476 s, 333 kB/s 65536+0 records in 65536+0 records out 33554432 bytes (34 MB, 32 MiB) copied, 82.7691 s, 405 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.48758 s, 352 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.36699 s, 384 kB/s 8192+0 records in 8192+0 records out 4194304 bytes (4.2 MB, 4.0 MiB) copied, 10.0502 s, 417 kB/s 8192+0 records in 8192+0 records out 4194304 bytes (4.2 MB, 4.0 MiB) copied, 10.0968 s, 415 kB/s 81920+0 records in 81920+0 records out 41943040 bytes (42 MB, 40 MiB) copied, 103.158 s, 407 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.43053 s, 366 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.37484 s, 381 kB/s 2048+0 records in 2048+0 records out 1048576 bytes (1.0 MB, 1.0 MiB) copied, 2.61353 s, 401 kB/s 2048+0 records in 2048+0 records out 1048576 bytes (1.0 MB, 1.0 MiB) copied, 2.616 s, 401 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.38069 s, 380 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.35592 s, 387 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 1.37754 s, 381 kB/s 884736+0 records in 884736+0 records out 452984832 bytes (453 MB, 432 MiB) copied, 26.0372 s, 17.4 MB/s 2048+0 records in 2048+0 records out 1048576 bytes (1.0 MB, 1.0 MiB) copied, 2.63721 s, 398 kB/s 2048+0 records in 2048+0 records out 1048576 bytes (1.0 MB, 1.0 MiB) copied, 2.6402 s, 397 kB/s [fwul 21y]#
aaya888 said: kdz extract for linux sd card write done command link https://mega.nz/#!cJ9WUAiA!TSt9L5G3C...n8vx0pQ9ToxCFw https://forum.xda-developers.com/g4/...-qfil-t3748946 [[email protected] ~]$ sudo dmesg -c >> /dev/null [sudo] password for android: [[email protected] ~]$ dmesg [13324.923241] usb 1-2: new full-speed USB device number 11 using ohci-pci Why are you posting this in multiple threads?, zip it up and upload it somewhere, no one wants to scroll through that crap Sent from my LG-H910 using XDA Labs Click to expand... Click to collapse
@aaya888 Dude, that is for creating a bootable SD card for the G4. The G4 uses eMMC NAND. It is NOT possible to create a bootable SD card for a phone that uses UFS NAND (like the G5, V20, G6, V30, G7). Let me rephrase that. It is not possible without a firehose. With a firehose, you can change the bootpath to /dev/block/mmcblk0. However, if you have a firehose, then you don't need a bootable SD card to unbrick your phone. -- Brian
runningnak3d said: @aaya888 Dude, that is for creating a bootable SD card for the G4. The G4 uses eMMC NAND. It is NOT possible to create a bootable SD card for a phone that uses UFS NAND (like the G5, V20, G6, V30, G7). Let me rephrase that. It is not possible without a firehose. With a firehose, you can change the bootpath to /dev/block/mmcblk0. However, if you have a firehose, then you don't need a bootable SD card to unbrick your phone. -- Brian Click to expand... Click to collapse https://mega.nz/#!UJk1HYRQ!SMufYIICHn1mC5UuzGJafKPVc4_IiV-Bf8Xp8T6oD-M [email protected]:~/Downloads$ cd kdz [email protected]:~/Downloads/kdz$ ls abootbak.bin eksst.bin mksdcard recovery.bin aboot.bin encrypt.bin modem.bin reserve.bin apdp.bin factory.bin modemst1.bin rpmbak.bin boot.bin fota.bin modemst2.bin rpm.bin cdt.bin fsc.bin mpt.bin sd.img cmnlib64bak.bin fsg.bin msadp.bin sec.bin cmnlib64.bin hypbak.bin -o sns.bin cmnlibbak.bin hyp.bin op.bin spare1.bin cmnlib.bin -i partitions.txt spare2.bin ddr.bin keymasterbak.bin persist.bin system.bin devcfgbak.bin keymaster.bin pmicbak.elf tzbak.bin devcfg.bin keystore.bin pmic.elf tz.bin devinfo.bin lafbak.bin raw_resourcesbak.bin xbl2bak.elf dip.bin laf.bin raw_resources.bin xbl2.elf dpo.bin misc.bin rct.bin xblbak.elf drm.bin mkgpt recoverybak.bin xbl.elf [email protected]:~/Downloads/kdz$ sudo ./mksdcard -g -o f800l.img -p partitions.txt -i lk_sdrescue/build-msm8996 -i bootloaders-sdboot [sudo] password for aaya: === Entry: name: laf, size: 49152, align: , type: 98523EC6-90FE-4C67-B50A-0FC59ED6F56D, format: , file: laf.bin === Entry: name: mpt, size: 49152, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: mpt.bin === Entry: name: drm, size: 12288, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: drm.bin === Entry: name: sns, size: 8192, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: sns.bin === Entry: name: misc, size: 49152, align: , type: 82ACC91F-357C-4A68-9C8F-689E1B1A23A1, format: , file: misc.bin === Entry: name: factory, size: 16384, align: , type: 20117F86-E985-4357-B9EE-374BC1D8487D, format: , file: factory.bin === Entry: name: encrypt, size: 1024, align: , type: 323EF595-AF7A-4AFA-8060-97BE72841BB9, format: , file: encrypt.bin === Entry: name: eksst, size: 1024, align: , type: 45864011-CF89-46E6-A445-85262E065604, format: , file: eksst.bin === Entry: name: rct, size: 64, align: , type: 8ED8AE95-597F-4C8A-A5BD-A7FF8E4DFAA9, format: , file: rct.bin === Entry: name: ssd, size: 1024, align: , type: 2C86E742-745E-4FDD-BFD8-B6A7AC638772, format: , file: ssd.bin === Entry: name: keystore, size: 1024, align: , type: DE7D4029-0F5B-41C8-AE7E-F6C023A02B33, format: , file: keystore.bin === Entry: name: persist, size: 32768, align: , type: 6C95E238-E343-4BA8-B489-8681ED22AD0B, format: , file: persist.bin === Entry: name: lafbak, size: 49152, align: , type: E0B10BE8-8B5F-46D0-BC9A-A629CC3E063D, format: , file: laf.bin === Entry: name: system, size: 1024, align: , type: 97D7B011-54DA-4835-B3C4-917AD6E73D74, format: , file: system.bin === Entry: name: cache, size: 1024, align: , type: 5594C694-C871-4B5F-90B1-690A6F68E0F7, format: , file: cache.bin === Entry: name: cust, size: 1024, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: cust.bin === Entry: name: op, size: 1024, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: op.bin === Entry: name: userdata, size: 1024, align: , type: 1B81E7E6-F50D-419B-A739-2AEEF8DA3335, format: , file: userdata.bin === Entry: name: grow, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow.bin === Entry: name: xbl, size: 2048, align: , type: DEA0BA2C-CBDD-4805-B4F9-F428251C3E98, format: , file: xbl.bin === Entry: name: xblbak, size: 2048, align: , type: DF24E5ED-8C96-4B86-B00B-79667DC6DE11, format: , file: xbl.bin === Entry: name: fota, size: 4096, align: , type: 86A7CB80-84E1-408C-99AB-694F1A410FC7, format: , file: fota.bin === Entry: name: fsg, size: 2048, align: , type: 638FF8E2-22C9-E33B-8F5D-0E81686A68CB, format: , file: fsg.bin === Entry: name: dip, size: 1024, align: , type: 4114B077-005D-4E12-AC8C-B493BDA684FB, format: , file: dip.bin === Entry: name: devinfo, size: 1024, align: , type: 65ADDCF4-0C5C-4D9A-AC2D-D90B5CBFCD03, format: , file: devinfo.bin === Entry: name: grow2, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow2.bin === Entry: name: xbl2, size: 2048, align: , type: DEA0BA2C-CBDD-4805-B4F9-F428251C3E98, format: , file: xbl.bin === Entry: name: xbl2bak, size: 2048, align: , type: DF24E5ED-8C96-4B86-B00B-79667DC6DE11, format: , file: xbl.bin === Entry: name: grow3, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow3.bin === Entry: name: ddr, size: 2048, align: , type: 20A0C19C-286A-42FA-9CE7-F64C3226A794, format: , file: ddr.bin === Entry: name: reserve, size: 64, align: , type: 7A37A18E-48F0-BCA5-935E-5795DBB57FF8, format: , file: reserve.bin === Entry: name: cdt, size: 8, align: , type: A19F205F-CCD8-4B6D-8F1E-2D9BC24CFFB1, format: , file: cdt.bin === Entry: name: spare1, size: 4096, align: , type: 7EFE5010-2A1A-4A1A-B8BC-990257813512, format: , file: spare1.bin === Entry: name: grow4, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow4.bin === Entry: name: boot, size: 32768, align: , type: 20117F86-E985-4357-B9EE-374BC1D8487D, format: , file: boot.bin === Entry: name: recovery, size: 32768, align: , type: 9D72D4E4-9958-42DA-AC26-BEA7A90B0434, format: , file: recovery.bin === Entry: name: recoverybak, size: 32768, align: , type: DF24E5ED-8C96-4B86-B00B-79667DC6DE11, format: , file: recovery.bin === Entry: name: tz, size: 2048, align: , type: A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4, format: , file: tz.bin === Entry: name: tzbak, size: 2048, align: , type: E6C8667F-8044-44A7-B1D9-BEFE88AAD86C, format: , file: tz.bin === Entry: name: aboot, size: 2048, align: , type: 400FFDCD-22E0-47E7-9A23-F16ED9382388, format: , file: aboot.bin === Entry: name: abootbak, size: 2048, align: , type: C993E3DF-FE66-49C9-8D8D-7C681C4DCAE9, format: , file: aboot.bin === Entry: name: raw_resources, size: 4096, align: , type: 4627AE27-CFEF-48A1-88FE-99C3509ADE26, format: , file: raw_resources.bin === Entry: name: raw_resourcesbak, size: 4096, align: , type: C1DAB2CF-697D-4665-B43D-00BA47487528, format: , file: raw_resources.bin === Entry: name: rpm, size: 256, align: , type: 098DF793-D712-413D-9D4E-89D711772228, format: , file: rpm.bin === Entry: name: rpmbak, size: 256, align: , type: 680CA584-238C-4E0F-8438-15F43257A055, format: , file: rpm.bin === Entry: name: hyp, size: 384, align: , type: E1A6A689-0C8D-4CC6-B4E8-55A4320FBD8A, format: , file: hyp.bin === Entry: name: hypbak, size: 384, align: , type: 24C03326-2523-4E03-8C5E-B07ED7A44CD9, format: , file: hyp.bin === Entry: name: pmic, size: 64, align: , type: C00EEF24-7709-43D6-9799-DD2B411E7A3C, format: , file: pmic.bin === Entry: name: pmicbak, size: 64, align: , type: 4E646DCC-29E2-459A-B7C5-618E6F3AD76A, format: , file: pmic.bin === Entry: name: devcfg, size: 64, align: , type: F65D4B16-343D-4E25-AAFC-BE99B6556A6D, format: , file: devcfg.bin === Entry: name: devcfgbak, size: 64, align: , type: 10A0C19C-516A-5444-5CE3-664C3226A794, format: , file: devcfg.bin === Entry: name: modem, size: 98304, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: modem.bin === Entry: name: sec, size: 16, align: , type: 303E6AC3-AF15-4C54-9E9B-D9A8FBECF401, format: , file: sec.bin === Entry: name: keymaster, size: 384, align: , type: 4F772165-0F3C-4BA3-BBCB-A829E9C969F9, format: , file: keymaster.bin === Entry: name: keymasterbak, size: 384, align: , type: 7C29D3AD-78B9-452E-9DEB-D098D542F092, format: , file: keymaster.bin === Entry: name: cmnlib, size: 384, align: , type: 73471795-AB54-43F9-A847-4F72EA5CBEF5, format: , file: cmnlib.bin === Entry: name: cmnlibbak, size: 384, align: , type: 7C29D3AD-78B9-452E-9DEB-D098D542F092, format: , file: cmnlib.bin === Entry: name: cmnlib64, size: 384, align: , type: 8EA64893-1267-4A1B-947C-7C362ACAAD2C, format: , file: cmnlib64.bin === Entry: name: cmnlib64bak, size: 384, align: , type: 379D107E-229E-499D-AD4F-61F5BCF87BD4, format: , file: cmnlib64.bin === Entry: name: apdp, size: 64, align: , type: E6E98DA2-E22A-4D12-AB33-169E7DEAA507, format: , file: apdp.bin === Entry: name: msadp, size: 64, align: , type: ED9E8101-05FA-46B7-82AA-8D58770D200B, format: , file: msadp.bin === Entry: name: dpo, size: 1024, align: , type: 11406F35-1173-4869-807B-27DF71802812, format: , file: dpo.bin === Entry: name: grow5, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow5.bin === Entry: name: modemst1, size: 2048, align: , type: EBBEADAF-22C9-E33B-8F5D-0E81686A68CB, format: , file: modemst1.bin === Entry: name: modemst2, size: 2048, align: , type: 0A288B1F-22C9-E33B-8F5D-0E81686A68CB, format: , file: modemst2.bin === Entry: name: fsc, size: 1024, align: , type: 57B90A16-22C9-E33B-8F5D-0E81686A68CB, format: , file: fsc.bin === Entry: name: spare2, size: 4096, align: , type: 40270447-93EC-4805-9779-83A3AE37CFF0, format: , file: spare2.bin === Entry: name: grow6, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow6.bin === Entry: name: persistent, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: persistent.bin === Entry: name: grow7, size: 4096, align: , type: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, format: , file: grow7.bin === Create file with size (kb): 559145 === Create image file: f800l.img 1+0 records in 1+0 records out 1024 bytes (1,0 kB, 1,0 KiB) copied, 0,0229406 s, 44,6 kB/s === Create part: name:laf, size:49152, type:98523EC6-90FE-4C67-B50A-0FC59ED6F56D, align:, format:, file: Creating new GPT entries. Setting name! partNum is 0 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:mpt, size:49152, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 1 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:drm, size:12288, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 2 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:sns, size:8192, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 3 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:misc, size:49152, type:82ACC91F-357C-4A68-9C8F-689E1B1A23A1, align:, format:, file: Setting name! partNum is 4 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:factory, size:16384, type:20117F86-E985-4357-B9EE-374BC1D8487D, align:, format:, file: Setting name! partNum is 5 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:encrypt, size:1024, type:323EF595-AF7A-4AFA-8060-97BE72841BB9, align:, format:, file: Setting name! partNum is 6 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:eksst, size:1024, type:45864011-CF89-46E6-A445-85262E065604, align:, format:, file: Setting name! partNum is 7 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:rct, size:64, type:8ED8AE95-597F-4C8A-A5BD-A7FF8E4DFAA9, align:, format:, file: Setting name! partNum is 8 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:ssd, size:1024, type:2C86E742-745E-4FDD-BFD8-B6A7AC638772, align:, format:, file: Setting name! partNum is 9 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:keystore, size:1024, typeE7D4029-0F5B-41C8-AE7E-F6C023A02B33, align:, format:, file: Setting name! partNum is 10
REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: nameersist, size:32768, type:6C95E238-E343-4BA8-B489-8681ED22AD0B, align:, format:, file: Setting name! partNum is 11 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:lafbak, size:49152, type:E0B10BE8-8B5F-46D0-BC9A-A629CC3E063D, align:, format:, file: Setting name! partNum is 12 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:system, size:1024, type:97D7B011-54DA-4835-B3C4-917AD6E73D74, align:, format:, file: Setting name! partNum is 13 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:cache, size:1024, type:5594C694-C871-4B5F-90B1-690A6F68E0F7, align:, format:, file: Setting name! partNum is 14 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:cust, size:1024, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 15 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: namep, size:1024, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 16 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:userdata, size:1024, type:1B81E7E6-F50D-419B-A739-2AEEF8DA3335, align:, format:, file: Setting name! partNum is 17 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:grow, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 18 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:xbl, size:2048, typeEA0BA2C-CBDD-4805-B4F9-F428251C3E98, align:, format:, file: Setting name! partNum is 19 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:xblbak, size:2048, typeF24E5ED-8C96-4B86-B00B-79667DC6DE11, align:, format:, file: Setting name! partNum is 20 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:fota, size:4096, type:86A7CB80-84E1-408C-99AB-694F1A410FC7, align:, format:, file: Setting name! partNum is 21 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:fsg, size:2048, type:638FF8E2-22C9-E33B-8F5D-0E81686A68CB, align:, format:, file: Setting name! partNum is 22 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:dip, size:1024, type:4114B077-005D-4E12-AC8C-B493BDA684FB, align:, format:, file: Setting name! partNum is 23 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:devinfo, size:1024, type:65ADDCF4-0C5C-4D9A-AC2D-D90B5CBFCD03, align:, format:, file: Setting name! partNum is 24 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:grow2, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 25 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:xbl2, size:2048, typeEA0BA2C-CBDD-4805-B4F9-F428251C3E98, align:, format:, file: Setting name! partNum is 26 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:xbl2bak, size:2048, typeF24E5ED-8C96-4B86-B00B-79667DC6DE11, align:, format:, file: Setting name! partNum is 27 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:grow3, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 28 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:ddr, size:2048, type:20A0C19C-286A-42FA-9CE7-F64C3226A794, align:, format:, file: Setting name! partNum is 29 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:reserve, size:64, type:7A37A18E-48F0-BCA5-935E-5795DBB57FF8, align:, format:, file: Setting name! partNum is 30 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:cdt, size:8, type:A19F205F-CCD8-4B6D-8F1E-2D9BC24CFFB1, align:, format:, file: Setting name! partNum is 31 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:spare1, size:4096, type:7EFE5010-2A1A-4A1A-B8BC-990257813512, align:, format:, file: Setting name! partNum is 32 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:grow4, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 33 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:boot, size:32768, type:20117F86-E985-4357-B9EE-374BC1D8487D, align:, format:, file: Setting name! partNum is 34 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:recovery, size:32768, type:9D72D4E4-9958-42DA-AC26-BEA7A90B0434, align:, format:, file: Setting name! partNum is 35 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:recoverybak, size:32768, typeF24E5ED-8C96-4B86-B00B-79667DC6DE11, align:, format:, file: Setting name! partNum is 36 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:tz, size:2048, type:A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4, align:, format:, file: Setting name! partNum is 37 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:tzbak, size:2048, type:E6C8667F-8044-44A7-B1D9-BEFE88AAD86C, align:, format:, file: Setting name! partNum is 38 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:aboot, size:2048, type:400FFDCD-22E0-47E7-9A23-F16ED9382388, align:, format:, file: Setting name! partNum is 39 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:abootbak, size:2048, type:C993E3DF-FE66-49C9-8D8D-7C681C4DCAE9, align:, format:, file: Setting name! partNum is 40 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:raw_resources, size:4096, type:4627AE27-CFEF-48A1-88FE-99C3509ADE26, align:, format:, file: Setting name! partNum is 41 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:raw_resourcesbak, size:4096, type:C1DAB2CF-697D-4665-B43D-00BA47487528, align:, format:, file: Setting name! partNum is 42 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:rpm, size:256, type:098DF793-D712-413D-9D4E-89D711772228, align:, format:, file: Setting name! partNum is 43 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:rpmbak, size:256, type:680CA584-238C-4E0F-8438-15F43257A055, align:, format:, file: Setting name! partNum is 44 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:hyp, size:384, type:E1A6A689-0C8D-4CC6-B4E8-55A4320FBD8A, align:, format:, file: Setting name! partNum is 45 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:hypbak, size:384, type:24C03326-2523-4E03-8C5E-B07ED7A44CD9, align:, format:, file: Setting name! partNum is 46 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: namemic, size:64, type:C00EEF24-7709-43D6-9799-DD2B411E7A3C, align:, format:, file: Setting name! partNum is 47 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: namemicbak, size:64, type:4E646DCC-29E2-459A-B7C5-618E6F3AD76A, align:, format:, file: Setting name! partNum is 48 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:devcfg, size:64, type:F65D4B16-343D-4E25-AAFC-BE99B6556A6D, align:, format:, file: Setting name! partNum is 49 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:devcfgbak, size:64, type:10A0C19C-516A-5444-5CE3-664C3226A794, align:, format:, file: Setting name! partNum is 50 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:modem, size:98304, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 51 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:sec, size:16, type:303E6AC3-AF15-4C54-9E9B-D9A8FBECF401, align:, format:, file: Setting name! partNum is 52 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:keymaster, size:384, type:4F772165-0F3C-4BA3-BBCB-A829E9C969F9, align:, format:, file: Setting name! partNum is 53 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:keymasterbak, size:384, type:7C29D3AD-78B9-452E-9DEB-D098D542F092, align:, format:, file: Setting name! partNum is 54 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:cmnlib, size:384, type:73471795-AB54-43F9-A847-4F72EA5CBEF5, align:, format:, file: Setting name! partNum is 55 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:cmnlibbak, size:384, type:7C29D3AD-78B9-452E-9DEB-D098D542F092, align:, format:, file: Setting name! partNum is 56 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:cmnlib64, size:384, type:8EA64893-1267-4A1B-947C-7C362ACAAD2C, align:, format:, file: Setting name! partNum is 57 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:cmnlib64bak, size:384, type:379D107E-229E-499D-AD4F-61F5BCF87BD4, align:, format:, file: Setting name! partNum is 58 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:apdp, size:64, type:E6E98DA2-E22A-4D12-AB33-169E7DEAA507, align:, format:, file: Setting name! partNum is 59 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:msadp, size:64, type:ED9E8101-05FA-46B7-82AA-8D58770D200B, align:, format:, file: Setting name! partNum is 60 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:dpo, size:1024, type:11406F35-1173-4869-807B-27DF71802812, align:, format:, file: Setting name! partNum is 61 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:grow5, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 62 REALLY setting name! ---------- Post added at 06:29 AM ---------- Previous post was at 06:28 AM ---------- Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:modemst1, size:2048, type:EBBEADAF-22C9-E33B-8F5D-0E81686A68CB, align:, format:, file: Setting name! partNum is 63 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:modemst2, size:2048, type:0A288B1F-22C9-E33B-8F5D-0E81686A68CB, align:, format:, file: Setting name! partNum is 64 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:fsc, size:1024, type:57B90A16-22C9-E33B-8F5D-0E81686A68CB, align:, format:, file: Setting name! partNum is 65 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:spare2, size:4096, type:40270447-93EC-4805-9779-83A3AE37CFF0, align:, format:, file: Setting name! partNum is 66 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:grow6, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 67 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: nameersistent, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 68 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. === Create part: name:grow7, size:4096, type:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, align:, format:, file: Setting name! partNum is 69 REALLY setting name! Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. [email protected]:~/Downloads/kdz$ sudo parted f800l.img print Model: (file) Disk /home/aaya/Downloads/kdz/f800l.img: 573MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 17,4kB 50,3MB 50,3MB laf 2 50,3MB 101MB 50,3MB mpt msftdata 3 101MB 113MB 12,6MB drm msftdata 4 113MB 122MB 8389kB sns msftdata 5 122MB 172MB 50,3MB misc 6 172MB 189MB 16,8MB factory 7 189MB 190MB 1049kB encrypt 8 190MB 191MB 1049kB eksst 9 191MB 191MB 65,5kB rct 10 191MB 192MB 1049kB ssd 11 192MB 193MB 1049kB keystore 12 193MB 227MB 33,6MB persist 13 227MB 277MB 50,3MB lafbak 14 277MB 278MB 1049kB system 15 278MB 279MB 1049kB cache 16 279MB 280MB 1049kB cust msftdata 17 280MB 281MB 1049kB op msftdata 18 281MB 282MB 1049kB userdata 19 282MB 286MB 4194kB grow msftdata 20 286MB 288MB 2097kB xbl 21 288MB 291MB 2097kB xblbak 22 291MB 295MB 4194kB fota 23 295MB 297MB 2097kB fsg 24 297MB 298MB 1049kB dip 25 298MB 299MB 1049kB devinfo 26 299MB 303MB 4194kB grow2 msftdata 27 303MB 305MB 2097kB xbl2 28 305MB 307MB 2097kB xbl2bak 29 307MB 312MB 4194kB grow3 msftdata 30 312MB 314MB 2097kB ddr 31 314MB 314MB 65,5kB reserve 32 314MB 314MB 8192B cdt 33 314MB 318MB 4194kB spare1 34 318MB 322MB 4194kB grow4 msftdata 35 322MB 356MB 33,6MB boot 36 356MB 389MB 33,6MB recovery 37 389MB 423MB 33,6MB recoverybak 38 423MB 425MB 2097kB tz 39 425MB 427MB 2097kB tzbak 40 427MB 429MB 2097kB aboot 41 429MB 431MB 2097kB abootbak 42 431MB 435MB 4194kB raw_resources 43 435MB 440MB 4194kB raw_resourcesbak 44 440MB 440MB 262kB rpm 45 440MB 440MB 262kB rpmbak 46 440MB 440MB 393kB hyp 47 440MB 441MB 393kB hypbak 48 441MB 441MB 65,5kB pmic 49 441MB 441MB 65,5kB pmicbak 50 441MB 441MB 65,5kB devcfg 51 441MB 441MB 65,5kB devcfgbak 52 441MB 542MB 101MB modem msftdata 53 542MB 542MB 16,4kB sec 54 542MB 542MB 393kB keymaster 55 542MB 543MB 393kB keymasterbak 56 543MB 543MB 393kB cmnlib 57 543MB 543MB 393kB cmnlibbak 58 543MB 544MB 393kB cmnlib64 59 544MB 544MB 393kB cmnlib64bak 60 544MB 544MB 65,5kB apdp 61 544MB 544MB 65,5kB msadp 62 544MB 545MB 1049kB dpo 63 545MB 549MB 4194kB grow5 msftdata 64 549MB 552MB 2097kB modemst1 65 552MB 554MB 2097kB modemst2 66 554MB 555MB 1049kB fsc 67 555MB 559MB 4194kB spare2 68 559MB 563MB 4194kB grow6 msftdata 69 563MB 567MB 4194kB persistent msftdata 70 567MB 572MB 4194kB grow7 msftdata [email protected]:~/Downloads/kdz$ sudo dmesg -c >> /dev/null [email protected]:~/Downloads/kdz$ dmesg [email protected]:~/Downloads/kdz$ sudo fdisk -l /dev/sdb Disk /dev/sdb: 58,4 GiB, 62730010624 bytes, 122519552 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 122519551 122517504 58,4G c W95 FAT32 (LBA) [email protected]:~/Downloads/kdz$ cd kdz bash: cd: kdz: No such file or directory [email protected]:~/Downloads/kdz$ sudo -s [email protected]:~/Downloads/kdz# dd if=f800l.img of=/dev/sdb 1118290+0 records in 1118290+0 records out 572564480 bytes (573 MB, 546 MiB) copied, 160,036 s, 3,6 MB/s [email protected]:~/Downloads/kdz# sync [email protected]:~/Downloads/kdz# ls -la /dev/disk/by-partlabel total 1935116 drwxr-xr-x 2 root root 1160 Луу 27 13:17 . drwxr-xr-x 8 root root 160 Луу 27 07:19 .. -rw-r--r-- 1 root root 2097152 Луу 27 13:14 aboot -rw-r--r-- 1 root root 2097152 Луу 27 13:14 abootbak -rw-r--r-- 1 root root 524288 Луу 27 13:14 apdp -rw-r--r-- 1 root root 41943040 Луу 27 13:14 boot -rw-r--r-- 1 root root 4096 Луу 27 13:14 cdt -rw-r--r-- 1 root root 524288 Луу 27 13:14 cmnlib -rw-r--r-- 1 root root 524288 Луу 27 13:14 cmnlib64 -rw-r--r-- 1 root root 524288 Луу 27 13:14 cmnlib64bak -rw-r--r-- 1 root root 524288 Луу 27 13:14 cmnlibbak -rw-r--r-- 1 root root 2097152 Луу 27 13:14 ddr -rw-r--r-- 1 root root 131072 Луу 27 13:14 devcfg -rw-r--r-- 1 root root 131072 Луу 27 13:14 devcfgbak -rw-r--r-- 1 root root 1048576 Луу 27 13:14 devinfo -rw-r--r-- 1 root root 1048576 Луу 27 13:14 dip -rw-r--r-- 1 root root 524288 Луу 27 13:14 dpo -rw-r--r-- 1 root root 10485760 Луу 27 13:14 drm -rw-r--r-- 1 root root 524288 Луу 27 13:14 eksst -rw-r--r-- 1 root root 524288 Луу 27 13:14 encrypt -rw-r--r-- 1 root root 69206016 Луу 27 13:14 factory -rw-r--r-- 1 root root 4194304 Луу 27 13:14 fota -rw-r--r-- 1 root root 524288 Луу 27 13:14 fsc -rw-r--r-- 1 root root 2097152 Луу 27 13:14 fsg -rw-r--r-- 1 root root 17920 Луу 27 13:14 gpt -rw-r--r-- 1 root root 34304 Луу 27 13:14 gpt_both0 -rw-r--r-- 1 root root 524288 Луу 27 13:14 hyp -rw-r--r-- 1 root root 524288 Луу 27 13:14 hypbak -rw-r--r-- 1 root root 524288 Луу 27 13:14 keymaster -rw-r--r-- 1 root root 524288 Луу 27 13:14 keymasterbak -rw-r--r-- 1 root root 524288 Луу 27 13:14 keystore -rw-r--r-- 1 root root 50331648 Луу 27 13:14 lafbak -rw-r--r-- 1 root root 21757952 Луу 27 13:14 misc -rw-r--r-- 1 root root 0 Луу 27 13:14 modem -rw-r--r-- 1 root root 2097152 Луу 27 13:14 modemst1 -rw-r--r-- 1 root root 2097152 Луу 27 13:14 modemst2 -rw-r--r-- 1 root root 0 Луу 27 13:14 mpt -rw-r--r-- 1 root root 0 Луу 27 13:14 msadp -rw-r--r-- 1 root root 33554432 Луу 27 13:14 persist -rw-r--r-- 1 root root 0 Луу 27 13:14 raw_resources -rw-r--r-- 1 root root 0 Луу 27 13:14 raw_resourcesbak -rw-r--r-- 1 root root 524288 Луу 27 13:14 rct -rw-r--r-- 1 root root 0 Луу 27 13:14 recovery -rw-r--r-- 1 root root 0 Луу 27 13:14 recoverybak -rw-r--r-- 1 root root 32768 Луу 27 13:14 reserve -rw-r--r-- 1 root root 0 Луу 27 13:14 rpm -rw-r--r-- 1 root root 0 Луу 27 13:14 rpmbak -rw-r--r-- 1 root root 0 Луу 27 13:14 sec -rw-r--r-- 1 root root 0 Луу 27 13:14 sns -rw-r--r-- 1 root root 4194304 Луу 27 13:14 spare1 -rw-r--r-- 1 root root 2097152 Луу 27 13:17 spare2 -rw-r--r-- 1 root root 1720893440 Луу 27 13:15 system lrwxrwxrwx 1 root root 10 Луу 27 10:52 Test\x20Partition -> ../../sda4 -rw-r--r-- 1 root root 0 Луу 27 13:15 tz -rw-r--r-- 1 root root 0 Луу 27 13:15 tzbak -rw-r--r-- 1 root root 0 Луу 27 08:07 xbl2 -rw-r--r-- 1 root root 0 Луу 27 08:07 xbl2bak -rw-r--r-- 1 root root 0 Луу 27 08:07 xblbak
[email protected]:~/Downloads/kdz# [email protected]:~/Downloads/kdz# for i in $(ls *.bin |egrep -v "(GPT|userdata)");do echo dd if=$i of=/dev/disk/by-partlabel/${i/\.bin};done dd if=abootbak.bin of=/dev/disk/by-partlabel/abootbak dd if=aboot.bin of=/dev/disk/by-partlabel/aboot dd if=apdp.bin of=/dev/disk/by-partlabel/apdp dd if=boot.bin of=/dev/disk/by-partlabel/boot dd if=cdt.bin of=/dev/disk/by-partlabel/cdt dd if=cmnlib64bak.bin of=/dev/disk/by-partlabel/cmnlib64bak dd if=cmnlib64.bin of=/dev/disk/by-partlabel/cmnlib64 dd if=cmnlibbak.bin of=/dev/disk/by-partlabel/cmnlibbak dd if=cmnlib.bin of=/dev/disk/by-partlabel/cmnlib dd if=ddr.bin of=/dev/disk/by-partlabel/ddr dd if=devcfgbak.bin of=/dev/disk/by-partlabel/devcfgbak dd if=devcfg.bin of=/dev/disk/by-partlabel/devcfg dd if=devinfo.bin of=/dev/disk/by-partlabel/devinfo dd if=dip.bin of=/dev/disk/by-partlabel/dip dd if=dpo.bin of=/dev/disk/by-partlabel/dpo dd if=drm.bin of=/dev/disk/by-partlabel/drm dd if=eksst.bin of=/dev/disk/by-partlabel/eksst dd if=encrypt.bin of=/dev/disk/by-partlabel/encrypt dd if=factory.bin of=/dev/disk/by-partlabel/factory dd if=fota.bin of=/dev/disk/by-partlabel/fota dd if=fsc.bin of=/dev/disk/by-partlabel/fsc dd if=fsg.bin of=/dev/disk/by-partlabel/fsg dd if=hypbak.bin of=/dev/disk/by-partlabel/hypbak dd if=hyp.bin of=/dev/disk/by-partlabel/hyp dd if=keymasterbak.bin of=/dev/disk/by-partlabel/keymasterbak dd if=keymaster.bin of=/dev/disk/by-partlabel/keymaster dd if=keystore.bin of=/dev/disk/by-partlabel/keystore dd if=lafbak.bin of=/dev/disk/by-partlabel/lafbak dd if=laf.bin of=/dev/disk/by-partlabel/laf dd if=misc.bin of=/dev/disk/by-partlabel/misc dd if=modem.bin of=/dev/disk/by-partlabel/modem dd if=modemst1.bin of=/dev/disk/by-partlabel/modemst1 dd if=modemst2.bin of=/dev/disk/by-partlabel/modemst2 dd if=mpt.bin of=/dev/disk/by-partlabel/mpt dd if=msadp.bin of=/dev/disk/by-partlabel/msadp dd if=op.bin of=/dev/disk/by-partlabel/op dd if=persist.bin of=/dev/disk/by-partlabel/persist dd if=raw_resourcesbak.bin of=/dev/disk/by-partlabel/raw_resourcesbak dd if=raw_resources.bin of=/dev/disk/by-partlabel/raw_resources dd if=rct.bin of=/dev/disk/by-partlabel/rct dd if=recoverybak.bin of=/dev/disk/by-partlabel/recoverybak dd if=recovery.bin of=/dev/disk/by-partlabel/recovery dd if=reserve.bin of=/dev/disk/by-partlabel/reserve dd if=rpmbak.bin of=/dev/disk/by-partlabel/rpmbak dd if=rpm.bin of=/dev/disk/by-partlabel/rpm dd if=sec.bin of=/dev/disk/by-partlabel/sec dd if=sns.bin of=/dev/disk/by-partlabel/sns dd if=spare1.bin of=/dev/disk/by-partlabel/spare1 dd if=spare2.bin of=/dev/disk/by-partlabel/spare2 dd if=system.bin of=/dev/disk/by-partlabel/system dd if=tzbak.bin of=/dev/disk/by-partlabel/tzbak dd if=tz.bin of=/dev/disk/by-partlabel/tz [email protected]:~/Downloads/kdz# for i in $(ls *.bin |egrep -v "(GPT|userdata)");do dd if=$i of=/dev/disk/by-partlabel/${i/\.bin};done 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0643486 s, 32,6 MB/s 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0526737 s, 39,8 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0249284 s, 21,0 MB/s 81920+0 records in 81920+0 records out 41943040 bytes (42 MB, 40 MiB) copied, 0,770998 s, 54,4 MB/s 8+0 records in 8+0 records out 4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000361113 s, 11,3 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,023943 s, 21,9 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0197682 s, 26,5 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0210129 s, 25,0 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0205953 s, 25,5 MB/s 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0528205 s, 39,7 MB/s 256+0 records in 256+0 records out 131072 bytes (131 kB, 128 KiB) copied, 0,0161039 s, 8,1 MB/s 256+0 records in 256+0 records out 131072 bytes (131 kB, 128 KiB) copied, 0,00298831 s, 43,9 MB/s 2048+0 records in 2048+0 records out 1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0283786 s, 36,9 MB/s 2048+0 records in 2048+0 records out 1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0326182 s, 32,1 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0400563 s, 13,1 MB/s 20480+0 records in 20480+0 records out 10485760 bytes (10 MB, 10 MiB) copied, 0,22146 s, 47,3 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,00814724 s, 64,4 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0052311 s, 100 MB/s 135168+0 records in 135168+0 records out 69206016 bytes (69 MB, 66 MiB) copied, 1,38552 s, 49,9 MB/s 8192+0 records in 8192+0 records out 4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,106935 s, 39,2 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,00975353 s, 53,8 MB/s 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0546581 s, 38,4 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0183304 s, 28,6 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0188219 s, 27,9 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,113713 s, 4,6 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,00687672 s, 76,2 MB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,00577225 s, 90,8 MB/s 98304+0 records in 98304+0 records out 50331648 bytes (50 MB, 48 MiB) copied, 1,08353 s, 46,5 MB/s dd: writing to '/dev/disk/by-partlabel/laf': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,00924235 s, 0,0 kB/s dd: writing to '/dev/disk/by-partlabel/misc': No space left on device 42497+0 records in 42496+0 records out 21757952 bytes (22 MB, 21 MiB) copied, 0,403093 s, 54,0 MB/s dd: writing to '/dev/disk/by-partlabel/modem': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0290838 s, 0,0 kB/s 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0590141 s, 35,5 MB/s 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0569646 s, 36,8 MB/s dd: writing to '/dev/disk/by-partlabel/mpt': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0378504 s, 0,0 kB/s dd: writing to '/dev/disk/by-partlabel/msadp': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0192231 s, 0,0 kB/s dd: writing to '/dev/disk/by-partlabel/op': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0228324 s, 0,0 kB/s 65536+0 records in 65536+0 records out 33554432 bytes (34 MB, 32 MiB) copied, 0,617191 s, 54,4 MB/s dd: writing to '/dev/disk/by-partlabel/raw_resourcesbak': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0215163 s, 0,0 kB/s dd: writing to '/dev/disk/by-partlabel/raw_resources': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,00581143 s, 0,0 kB/s 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0158591 s, 33,1 MB/s dd: writing to '/dev/disk/by-partlabel/recoverybak': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0129297 s, 0,0 kB/s dd: writing to '/dev/disk/by-partlabel/recovery': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,00115132 s, 0,0 kB/s 64+0 records in 64+0 records out 32768 bytes (33 kB, 32 KiB) copied, 0,016151 s, 2,0 MB/s dd: writing to '/dev/disk/by-partlabel/rpmbak': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0118379 s, 0,0 kB/s dd: writing to '/dev/disk/by-partlabel/rpm': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,00103714 s, 0,0 kB/s dd: writing to '/dev/disk/by-partlabel/sec': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,00582426 s, 0,0 kB/s dd: writing to '/dev/disk/by-partlabel/sns': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,00913119 s, 0,0 kB/s 8192+0 records in 8192+0 records out 4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,103569 s, 40,5 MB/s 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0530615 s, 39,5 MB/s dd: writing to '/dev/disk/by-partlabel/system': No space left on device 3361121+0 records in 3361120+0 records out 1720893440 bytes (1,7 GB, 1,6 GiB) copied, 31,5384 s, 54,6 MB/s dd: writing to '/dev/disk/by-partlabel/tzbak': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0140009 s, 0,0 kB/s dd: writing to '/dev/disk/by-partlabel/tz': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,127579 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=abootbak.bin of=/dev/disk/by-partlabel/abootbak 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0562202 s, 37,3 MB/s [email protected]:~/Downloads/kdz# dd if=aboot.bin of=/dev/disk/by-partlabel/aboot 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0509847 s, 41,1 MB/s [email protected]:~/Downloads/kdz# dd if=apdp.bin of=/dev/disk/by-partlabel/apdp 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0198957 s, 26,4 MB/s [email protected]:~/Downloads/kdz# dd if=boot.bin of=/dev/disk/by-partlabel/boot 81920+0 records in 81920+0 records out 41943040 bytes (42 MB, 40 MiB) copied, 0,771567 s, 54,4 MB/s [email protected]:~/Downloads/kdz# dd if=cache.bin of=/dev/disk/by-partlabel/cache dd: failed to open 'cache.bin': No such file or directory [email protected]:~/Downloads/kdz# dd if=cdt.bin of=/dev/disk/by-partlabel/cdt 8+0 records in 8+0 records out 4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000216207 s, 18,9 MB/s [email protected]:~/Downloads/kdz# dd if=cmnlib64bak.bin of=/dev/disk/by-partlabel/cmnlib64bak 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0289889 s, 18,1 MB/s [email protected]:~/Downloads/kdz# dd if=cmnlib64.bin of=/dev/disk/by-partlabel/cmnlib64 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0250437 s, 20,9 MB/s [email protected]:~/Downloads/kdz# dd if=cmnlibbak.bin of=/dev/disk/by-partlabel/cmnlibbak 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0177252 s, 29,6 MB/s [email protected]:~/Downloads/kdz# dd if=cmnlib.bin of=/dev/disk/by-partlabel/cmnlib 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0159855 s, 32,8 MB/s [email protected]:~/Downloads/kdz# dd if=ddr.bin of=/dev/disk/by-partlabel/ddr 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0672052 s, 31,2 MB/s [email protected]:~/Downloads/kdz# dd if=devcfgbak.bin of=/dev/disk/by-partlabel/devcfgbak 256+0 records in 256+0 records out 131072 bytes (131 kB, 128 KiB) copied, 0,00671658 s, 19,5 MB/s [email protected]:~/Downloads/kdz# dd if=devcfg.bin of=/dev/disk/by-partlabel/devcfg 256+0 records in 256+0 records out 131072 bytes (131 kB, 128 KiB) copied, 0,0130537 s, 10,0 MB/s [email protected]:~/Downloads/kdz# dd if=devinfo.bin of=/dev/disk/by-partlabel/devinfo 2048+0 records in 2048+0 records out 1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0344104 s, 30,5 MB/s [email protected]:~/Downloads/kdz# dd if=dip.bin of=/dev/disk/by-partlabel/dip 2048+0 records in 2048+0 records out 1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0525063 s, 20,0 MB/s [email protected]:~/Downloads/kdz# dd if=dpo.bin of=/dev/disk/by-partlabel/dpo 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0367111 s, 14,3 MB/s [email protected]:~/Downloads/kdz# dd if=drm.bin of=/dev/disk/by-partlabel/drm 20480+0 records in 20480+0 records out 10485760 bytes (10 MB, 10 MiB) copied, 0,206695 s, 50,7 MB/s [email protected]:~/Downloads/kdz# dd if=eksst.bin of=/dev/disk/by-partlabel/eksst 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,00657176 s, 79,8 MB/s [email protected]:~/Downloads/kdz# dd if=encrypt.bin of=/dev/disk/by-partlabel/encrypt 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,00701394 s, 74,7 MB/s [email protected]:~/Downloads/kdz# dd if=factory.bin of=/dev/disk/by-partlabel/factory 135168+0 records in 135168+0 records out 69206016 bytes (69 MB, 66 MiB) copied, 1,40961 s, 49,1 MB/s [email protected]:~/Downloads/kdz# dd if=fota.bin of=/dev/disk/by-partlabel/fota 8192+0 records in 8192+0 records out 4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,10445 s, 40,2 MB/s [email protected]:~/Downloads/kdz# dd if=fsc.bin of=/dev/disk/by-partlabel/fsc 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,00887572 s, 59,1 MB/s [email protected]:~/Downloads/kdz# dd if=fsg.bin of=/dev/disk/by-partlabel/fsg 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0509349 s, 41,2 MB/s [email protected]:~/Downloads/kdz# dd if=grow2.bin of=/dev/disk/by-partlabel/grow2 dd: failed to open 'grow2.bin': No such file or directory [email protected]:~/Downloads/kdz# dd if=grow3.bin of=/dev/disk/by-partlabel/grow3 dd: failed to open 'grow3.bin': No such file or directory [email protected]:~/Downloads/kdz# dd if=grow4.bin of=/dev/disk/by-partlabel/grow4 dd: failed to open 'grow4.bin': No such file or directory [email protected]:~/Downloads/kdz# dd if=grow5.bin of=/dev/disk/by-partlabel/grow5 dd: failed to open 'grow5.bin': No such file or directory [email protected]:~/Downloads/kdz# dd if=grow6.bin of=/dev/disk/by-partlabel/grow6 dd: failed to open 'grow6.bin': No such file or directory [email protected]:~/Downloads/kdz# dd if=grow.bin of=/dev/disk/by-partlabel/grow dd: failed to open 'grow.bin': No such file or directory [email protected]:~/Downloads/kdz# dd if=hypbak.bin of=/dev/disk/by-partlabel/hypbak 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0266637 s, 19,7 MB/s [email protected]:~/Downloads/kdz# dd if=hyp.bin of=/dev/disk/by-partlabel/hyp 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0173174 s, 30,3 MB/s [email protected]spire-E1-531:~/Downloads/kdz# dd if=keymasterbak.bin of=/dev/disk/by-partlabel/keymasterbak 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,00618144 s, 84,8 MB/s [email protected]:~/Downloads/kdz# dd if=keymaster.bin of=/dev/disk/by-partlabel/keymaster 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,00514745 s, 102 MB/s [email protected]:~/Downloads/kdz# dd if=keystore.bin of=/dev/disk/by-partlabel/keystore 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,00609891 s, 86,0 MB/s [email protected]:~/Downloads/kdz# dd if=lafbak.bin of=/dev/disk/by-partlabel/lafbak 98304+0 records in 98304+0 records out 50331648 bytes (50 MB, 48 MiB) copied, 0,911995 s, 55,2 MB/s [email protected]:~/Downloads/kdz# dd if=laf.bin of=/dev/disk/by-partlabel/laf dd: writing to '/dev/disk/by-partlabel/laf': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,00618895 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=misc.bin of=/dev/disk/by-partlabel/misc dd: writing to '/dev/disk/by-partlabel/misc': No space left on device 42497+0 records in 42496+0 records out 21757952 bytes (22 MB, 21 MiB) copied, 0,410335 s, 53,0 MB/s [email protected]:~/Downloads/kdz# dd if=modem.bin of=/dev/disk/by-partlabel/modem dd: writing to '/dev/disk/by-partlabel/modem': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0249778 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=modemst1.bin of=/dev/disk/by-partlabel/modemst1 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0639324 s, 32,8 MB/s [email protected]:~/Downloads/kdz# dd if=modemst2.bin of=/dev/disk/by-partlabel/modemst2 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0402436 s, 52,1 MB/s [email protected]:~/Downloads/kdz# dd if=mpt.bin of=/dev/disk/by-partlabel/mpt dd: writing to '/dev/disk/by-partlabel/mpt': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0221325 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=msadp.bin of=/dev/disk/by-partlabel/msadp dd: writing to '/dev/disk/by-partlabel/msadp': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0142649 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=persist.bin of=/dev/disk/by-partlabel/persist 65536+0 records in 65536+0 records out 33554432 bytes (34 MB, 32 MiB) copied, 0,621584 s, 54,0 MB/s [email protected]:~/Downloads/kdz# dd if=pmicbak.bin of=/dev/disk/by-partlabel/pmicbak dd: writing to '/dev/disk/by-partlabel/pmicbak': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,000650274 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=pmic.bin of=/dev/disk/by-partlabel/pmic dd: writing to '/dev/disk/by-partlabel/pmic': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,00025464 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=raw_resourcesbak.bin of=/dev/disk/by-partlabel/raw_resourcesbak dd: writing to '/dev/disk/by-partlabel/raw_resourcesbak': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0157091 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=raw_resources.bin of=/dev/disk/by-partlabel/raw_resources dd: writing to '/dev/disk/by-partlabel/raw_resources': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,00922587 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=rct.bin of=/dev/disk/by-partlabel/rct 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,0247106 s, 21,2 MB/s [email protected]:~/Downloads/kdz# dd if=recoverybak.bin of=/dev/disk/by-partlabel/recoverybak dd: writing to '/dev/disk/by-partlabel/recoverybak': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0176765 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=recovery.bin of=/dev/disk/by-partlabel/recovery dd: writing to '/dev/disk/by-partlabel/recovery': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,000869766 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=reserve.bin of=/dev/disk/by-partlabel/reserve 64+0 records in 64+0 records out 32768 bytes (33 kB, 32 KiB) copied, 0,0476047 s, 688 kB/s [email protected]:~/Downloads/kdz# dd if=rpmbak.bin of=/dev/disk/by-partlabel/rpmbak dd: writing to '/dev/disk/by-partlabel/rpmbak': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,00965593 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=rpm.bin of=/dev/disk/by-partlabel/rpm dd: writing to '/dev/disk/by-partlabel/rpm': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,000823096 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=sec.bin of=/dev/disk/by-partlabel/sec dd: writing to '/dev/disk/by-partlabel/sec': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,0037476 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=sns.bin of=/dev/disk/by-partlabel/sns dd: writing to '/dev/disk/by-partlabel/sns': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,00548995 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=spare1.bin of=/dev/disk/by-partlabel/spare1 8192+0 records in 8192+0 records out 4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,102285 s, 41,0 MB/s [email protected]:~/Downloads/kdz# dd if=spare2.bin of=/dev/disk/by-partlabel/spare2 4096+0 records in 4096+0 records out 2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0504355 s, 41,6 MB/s [email protected]:~/Downloads/kdz# dd if=ssd.bin of=/dev/disk/by-partlabel/ssd dd: failed to open 'ssd.bin': No such file or directory [email protected]:~/Downloads/kdz# dd if=system.bin of=/dev/disk/by-partlabel/system dd: writing to '/dev/disk/by-partlabel/system': No space left on device 3361121+0 records in 3361120+0 records out 1720893440 bytes (1,7 GB, 1,6 GiB) copied, 31,5257 s, 54,6 MB/s [email protected]:~/Downloads/kdz# dd if=tzbak.bin of=/dev/disk/by-partlabel/tzbak dd: writing to '/dev/disk/by-partlabel/tzbak': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,000273897 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=tz.bin of=/dev/disk/by-partlabel/tz dd: writing to '/dev/disk/by-partlabel/tz': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,000330047 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=xbl2bak.bin of=/dev/disk/by-partlabel/xbl2bak dd: writing to '/dev/disk/by-partlabel/xbl2bak': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,000430381 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=xbl2.bin of=/dev/disk/by-partlabel/xbl2 dd: writing to '/dev/disk/by-partlabel/xbl2': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,000282129 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=xblbak.bin of=/dev/disk/by-partlabel/xblbak dd: writing to '/dev/disk/by-partlabel/xblbak': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,000217358 s, 0,0 kB/s [email protected]:~/Downloads/kdz# dd if=xbl.bin of=/dev/disk/by-partlabel/xbl dd: writing to '/dev/disk/by-partlabel/xbl': No space left on device 1+0 records in 0+0 records out 0 bytes copied, 0,000417175 s, 0,0 kB/s [email protected]:~/Downloads/kdz#
Mods need to ban this guy for posting this stuff in multiple threads after he was told previously not to. Sent from my LG-H910 using XDA Labs
@cnjax I wish he wouldn't have posted this until we get Oreo, but since it is out there, he has almost figured out how to boot from an SD card. Also, the massive posts weren't needed, a link to pastebin would have sufficed. This is the ultimate hole that LG can't patch (can't modify the PBL). I won't post the proper way until we get Oreo (LG has wasted enough time trying to close holes), but if someone else wants to do a little work, this method will root the LS997, and the H932 V30.
runningnak3d said: @cnjax I wish he wouldn't have posted this until we get Oreo, but since it is out there, he has almost figured out how to boot from an SD card. Also, the massive posts weren't needed, a link to pastebin would have sufficed. This is the ultimate hole that LG can't patch (can't modify the PBL). I won't post the proper way until we get Oreo (LG has wasted enough time trying to close holes), but if someone else wants to do a little work, this method will root the LS997, and the H932 V30. Click to expand... Click to collapse It doesn't matter what he's almost figured out, there's no reason to post dumps on the forum in multiple places, he could simply post what he's done or figured out and if anyone wanted to see it, he could send it to them directly. Sent from my LG-H910 using XDA Labs
Where is the BCT image on the TPT?
Can someone explain me how the TPT does the booting? According to the nvidia manual there should be a BCT image somewhere on the device, either in SPI or in eMMC but I can not find it. According to this post: https://forum.xda-developers.com/showthread.php?t=2318140 there should be 16 partitions, but it looks like I only have 10: Code: [email protected]:/ # cat /proc/partitions major minor #blocks name 179 0 15387648 mmcblk0 179 1 6144 mmcblk0p1 179 2 8192 mmcblk0p2 179 3 786432 mmcblk0p3 179 4 921600 mmcblk0p4 179 5 2048 mmcblk0p5 179 6 524288 mmcblk0p6 179 7 20480 mmcblk0p7 259 0 143360 mmcblk0p8 259 1 20480 mmcblk0p9 259 2 12939264 mmcblk0p10 [email protected]:/ # ls -al /dev/block/platform/sdhci-tegra.3/by-name/ lrwxrwxrwx root root 2018-08-16 09:07 AP -> /dev/block/mmcblk0p3 lrwxrwxrwx root root 2018-08-16 09:07 CC -> /dev/block/mmcblk0p4 lrwxrwxrwx root root 2018-08-16 09:07 LX -> /dev/block/mmcblk0p2 lrwxrwxrwx root root 2018-08-16 09:07 MC -> /dev/block/mmcblk0p5 lrwxrwxrwx root root 2018-08-16 09:07 PA -> /dev/block/mmcblk0p6 lrwxrwxrwx root root 2018-08-16 09:07 SC -> /dev/block/mmcblk0p7 lrwxrwxrwx root root 2018-08-16 09:07 SS -> /dev/block/mmcblk0p1 lrwxrwxrwx root root 2018-08-16 09:07 UA -> /dev/block/mmcblk0p10 lrwxrwxrwx root root 2018-08-16 09:07 UP -> /dev/block/mmcblk0p8 As p1 is the recovery image and p2 is the kernel, I do not see any more partitions where the BCT image could be. nvflash does not work on my device, as the APX mode is locked. What I find a little bit worrying, is that fdisk says I have no partition table: Code: [email protected]:/ # fdisk -l mmcblk0 Disk mmcblk0: 15.7 GB, 15756951552 bytes 4 heads, 16 sectors/track, 480864 cylinders Units = cylinders of 64 * 512 = 32768 bytes Disk mmcblk0 doesn't contain a valid partition table Should this command fail? But there must be the configuration somewhere, right? I have a TPT 1839-22G
I imaged now the whole eMMC using dd and found out that in difference to the posted partition table, the partitions BCT, PT, EBT and GP1 are missing. the Partitions SOS starts 0x100000 bytes earlier as given in the other thread. Between 0x0 and 0x00d00000 I can find some non zero bytes but nothing which caught my attention. Using gdisk I could restore the partition table: Code: GPT fdisk (gdisk) version 1.0.3 Unsupported GPT version in backup header; read 0x00000000, should be 0x00010000 Partition table scan: MBR: not present BSD: not present APM: not present GPT: not present Creating new GPT entries. Command (? for help): p Disk mmcblk0.img: 30775296 sectors, 14.7 GiB Sector size (logical): 512 bytes Disk identifier (GUID): D3A36F54-6FB0-48C2-B599-DFD0D4E294BF Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 30775262 Partitions will be aligned on 2048-sector boundaries Total free space is 30775229 sectors (14.7 GiB) Number Start (sector) End (sector) Size Code Name Command (? for help): r Recovery/transformation command (? for help): b Recovery/transformation command (? for help): p Disk mmcblk0.img: 30775296 sectors, 14.7 GiB Sector size (logical): 512 bytes Disk identifier (GUID): D3A36F54-6FB0-48C2-B599-DFD0D4E294BF Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 30775262 Partitions will be aligned on 2048-sector boundaries Total free space is 30775229 sectors (14.7 GiB) Number Start (sector) End (sector) Size Code Name Recovery/transformation command (? for help): c Warning! This will probably do weird things if you've converted an MBR to GPT form and haven't yet saved the GPT! Proceed? (Y/N): y Caution! After loading partitions, the CRC doesn't check out! Recovery/transformation command (? for help): p Disk mmcblk0.img: 30775296 sectors, 14.7 GiB Sector size (logical): 512 bytes Disk identifier (GUID): D3A36F54-6FB0-48C2-B599-DFD0D4E294BF Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 30775262 Partitions will be aligned on 2048-sector boundaries Total free space is 30653 sectors (15.0 MiB) Number Start (sector) End (sector) Size Code Name 1 26624 38911 6.0 MiB 0700 体S 2 38912 55295 8.0 MiB 0700 乌X 3 55296 1628159 768.0 MiB 0700 偁P 4 1628160 3471359 900.0 MiB 0700 䅃C 5 3471360 3475455 2.0 MiB 0700 卍C 6 3475456 4524031 512.0 MiB 0700 䥐A 7 4524032 4564991 20.0 MiB 0700 䕓C 8 4564992 4851711 140.0 MiB 0700 单P 9 4851712 4892671 20.0 MiB 0700 䑐A 10 4892672 30771199 12.3 GiB 0700 䑕A Which also shows, that there are no partitions before 0xd00000. But where is the BCT stored then?
LG G2 bricked, partition table corrupt
Update: Somehow, the phone came back, sort of (battery low?!), and I was able to see all partitions again. So I tried fixing the problem by copying boot.img and laf.img to the respective partitions ... I guess you shouldn't try these things at 1:30 am after already getting yourself in a horrible mess, but here I am. Now the phone is stuck at the LG logo screen, the LED flashes green and blue, and nothing happens. All I can do is to push the power button, and the process repeats. Naturally, I cannot see any partitions any longer. Now the device seems to be REALLY dead. Anything I can still try?! Original problem description I have tried, after somehow messing things up when following the guide to install LineageOS on the LG G2 (d802, international version with 32 GB), to resurrect my phone using this guide. However, it failed to solve my problem, and when I tried to boot, the phone still showed only the LG logo, the secure booting error, and then the screen went black, just as before. I guess I should have used dd as well to copy the boot, dbi and laf partitions. Instead, I figured maybe I should try the TWRP Recovery v2.6.3.2 instead of either TWRP v2.8.7.3 or the LineageOS Recovery image, and that probably has been my (final) mistake. Because, before, the output from gdisk looked liked this: Code: Found valid GPT with protective MBR; using GPT. Disk /dev/sdb: 61071360 sectors, 29.1 GiB Model: MMC Storage Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20 Partition table holds up to 36 entries Main partition table begins at sector 2 and ends at sector 10 First usable sector is 34, last usable sector is 61071326 Partitions will be aligned on 2-sector boundaries Total free space is 257992 sectors (126.0 MiB) Number Start (sector) End (sector) Size Code Name 1 32768 163839 64.0 MiB 0700 modem 2 163840 165887 1024.0 KiB FFFF sbl1 3 165888 166911 512.0 KiB FFFF dbi 4 196608 197631 512.0 KiB FFFF DDR 5 229376 231423 1024.0 KiB FFFF aboot 6 231424 233471 1024.0 KiB FFFF rpm 7 262144 294911 16.0 MiB FFFF boot 8 294912 296959 1024.0 KiB FFFF tz 9 296960 296961 1024 bytes 0700 pad 10 327680 333823 3.0 MiB FFFF modemst1 11 333824 339967 3.0 MiB FFFF modemst2 12 339968 339969 1024 bytes FFFF pad1 13 360448 393215 16.0 MiB FFFF misc 14 393216 458751 32.0 MiB 0700 persist 15 458752 491519 16.0 MiB FFFF recovery 16 491520 497663 3.0 MiB FFFF fsg 17 524288 525311 512.0 KiB FFFF fsc 18 525312 526335 512.0 KiB FFFF ssd 19 526336 526337 1024 bytes FFFF pad2 20 526338 527361 512.0 KiB FFFF encrypt 21 557056 573439 8.0 MiB 0700 drm 22 573440 589823 8.0 MiB 0700 sns 23 589824 655359 32.0 MiB FFFF laf 24 655360 720895 32.0 MiB FFFF fota 25 720896 786431 32.0 MiB 0700 mpt 26 786432 787455 512.0 KiB FFFF dbibak 27 787456 789503 1024.0 KiB FFFF rpmbak 28 789504 791551 1024.0 KiB FFFF tzbak 29 791552 791567 8.0 KiB FFFF rct 30 819200 6488063 2.7 GiB 0700 system 31 6488064 7733247 608.0 MiB 0700 cache 32 7733248 7897087 80.0 MiB 0700 tombstones 33 7897088 7929855 16.0 MiB 0700 spare 34 7929856 8028159 48.0 MiB 0700 cust 35 8028160 60948479 25.2 GiB 0700 userdata 36 60948480 61071326 60.0 MiB 0700 grow Now, it looks like this, so I am unable to use dd to copy any files to the (now apparently deleted or at least unavailable) partitions of the LG G2: Code: *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. *************************************************************** Warning! Main partition table overlaps the first partition by 32 blocks! You will need to delete this partition or resize it in another utility. Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize it in another utility. Disk /dev/sdb: 2014208 sectors, 983.5 MiB Model: Mighty Drive Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): DEF7EA8F-7D62-49A1-8F27-4F59EF0FDF29 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 2014174 Partitions will be aligned on 2-sector boundaries Total free space is 0 sectors (0 bytes) Number Start (sector) End (sector) Size Code Name 1 2 2014207 983.5 MiB 0700 Microsoft basic data I am afraid I have no backup of the partition table other than the output above, because I only learned of this feature of gdisk when looking for solutions of this (last) issue. Is there any way I can restore the partition table of my device? Any help in unbricking my phone is, of course, GREATLY appreciated. :fingers-crossed:
Resizing /system and /userdata in Note 3 SM-N9005
Hello to all. I am trying to resize the partition /system using the parted and gdisk commands. But none of these commands succeed in changing mmcblk0 partitions after execution. The things I do are as follows: - install adb and fastboot and put them to the system variables. - enable Settings>developer options>USB debugging and Root debugging - install TWRP recovery. - run cmd in adminitsrator permission. - write these command in CMD : adb root adb reboot recovery adb push gdisk /sbin adb push parted /sbin adb shell chmod 777 /sbin/gdisk adb shell chmod 777 /sbin/parted adb shell ~#> cd /dev/block dev/block> gdisk mmcblk0 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for help): p Disk /dev/block/mmcblk0: 61071360 sectors, 29.1 GiB Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 61071326 Partitions will be aligned on 2-sector boundaries Total free space is 8158 sectors (4.0 MiB) Number Start (sector) End (sector) Size Code Name 1 8192 38911 15.0 MiB 8300 apnhlos 2 38912 156543 57.4 MiB 0700 modem 3 156544 157567 512.0 KiB FFFF sbl1 4 157568 157631 32.0 KiB FFFF dbi 5 157632 157695 32.0 KiB FFFF ddr 6 157696 161791 2.0 MiB FFFF aboot 7 161792 162815 512.0 KiB FFFF rpm 8 162816 163839 512.0 KiB FFFF tz 9 163840 184319 10.0 MiB FFFF pad 10 184320 204799 10.0 MiB 8300 param 11 204800 233471 14.0 MiB 8300 efs 12 233472 239615 3.0 MiB FFFF modemst1 13 239616 245759 3.0 MiB FFFF modemst2 14 245760 268287 11.0 MiB FFFF boot 15 268288 294911 13.0 MiB FFFF recovery 16 294912 321535 13.0 MiB FFFF fota 17 321536 335853 7.0 MiB 8300 backup 18 335854 341997 3.0 MiB FFFF fsg 19 341998 341999 1024 bytes FFFF fsc 20 342000 342015 8.0 KiB FFFF ssd 21 342016 358399 8.0 MiB 8300 persist 22 358400 376831 9.0 MiB 8300 persdata 23 376832 5095423 2.3 GiB 8300 system 24 5095424 5709823 300.0 MiB 8300 cache 25 5709824 5730303 10.0 MiB 8300 hidden 26 5730304 61071326 26.4 GiB 8300 userdata Command (? for help): d Partition number (1-26): 26 Command (? for help):w (curser blinking) and device goes to hang!!!!! anyone can help me? I do this in parted command. It is like above. after restarting the device, all of the partition are there, like before...
I also used PIT file with different partition sizes, but nothing change. Odin shown : RQT_CLOSE!!