Database Users

U8800 partition scheme.

In case this info is of use to someone...
Trying to understand what goes where,
Here is the partition table of a U8800:
#######################################
Disk /dev/sdb: 3959 MB, 3959422976 bytes
1 heads, 62 sectors/track, 124729 cylinders, total 7733248 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
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 491520 245760 b W95 FAT32
/dev/sdb2 * 491521 492520 500 4d QNX4.x
/dev/sdb3 492521 498520 3000 46 Unknown
/dev/sdb4 498521 7733247 3617363+ 5 Extended
/dev/sdb5 524288 548863 12288 59 Unknown
/dev/sdb6 655360 921599 133120 4c Unknown
/dev/sdb7 1048576 1049575 500 5a Unknown
/dev/sdb8 1179648 1185791 3072 58 Unknown
/dev/sdb9 1310720 1324719 7000 50 OnTrack DM
/dev/sdb10 1441792 1447935 3072 4a Unknown
/dev/sdb11 1572864 1579007 3072 4b Unknown
/dev/sdb12 1703936 2154495 225280 83 Linux
/dev/sdb13 2228224 3457023 614400 83 Linux
/dev/sdb14 3538944 7733247 2097152 69 Unknown
#############################################
sdb1: This is the FAT32 partition that gets mounted when we boot into pink screen;
It holds, among other files, EMMCBOOT.MBN, which, if not present and as far as I've experimented, will get the phone straight into a blue screen and initiate a flash procedure if a 'dload' folder with a ROM is found in the sdcard. The contens of this partition are changed when a ROM is flashed.
sdb2: Is flagged as bootable, and holds an (so far) unknown filesystem (if any; could hold a raw binary image, for instance);
sdb3: Holds an unknown filesystem, if any. This partition is changed whenever you flash a ROM. dumping this partition back, from any 2.3BETA, to a 2.3 (B522) running phone, will get the USB pink screen mode working again, allowing acces to sdb1.
sdb5: holds an unknown filesystem if any; dumping this one back gets us the original "IDEOS" logo and, probably, whatever is needed to make previous CWM backups work again.
sdb6: ext3 filesystem with a directory called "recovery".
sdb7: Unknown filessytem, if any.
sdb8: Unknown filesystem, if any.
sdb9: Unknown filesystem, if any.
sdb10: Unknown filesystem, if any.
sdb11: Unknown filesystem, if any.
sdb12: ext3 filesystem; gets mounted at "/system".
sdb13: ext3 filesystem; gets mounted at "/data".
sdb14: vfat filesystem; represents the internal sdcard.
I'm trying to find out what needs to be restored in order to perform a clean, reliable downgrade. sdb5 is a must, but not the only one. I've flashed 2.2 and dumped it back right after. The result is an almost downgraded U8800. I say almost because charging the battery while the phone is off shows a different image (the one that comes with 2.3) and I can't power up the phone unless I take the cable out; this means there are still remnants of 2.3 somewhere...
UPDATE: Not being able to power up the phone was to due to the CWM recovery; restoring original recovery.img solved that one.

[Info] List of Samsung Galaxy S2 GT-I9100 devices and partitions

To run this commands you need a rooted device with BusyBox and parted. Using stock partition layout. You can change the partition layout to get more or less than 2GB of size for the data partition:
[MOD][GUIDE]Partition your internal memory for better App management (Pit Files)
List of devices by name:
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
Click to expand...
Click to collapse
List of fdisk for all given partitions:
Command (needs Superuser or equivalent and Busybox):
su
find /dev/block/platform/dw_mmc/ -name 'mmc*' -exec fdisk -l {} \; > /sdcard/list_of_sgs2_partitions.txt
Click to expand...
Click to collapse
Code:
Disk ./mmcblk0boot0: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0boot0 doesn't contain a valid partition table
Disk ./mmcblk0boot1: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0boot1 doesn't contain a valid partition table
Disk ./mmcblk0p12: 536 MB, 536870912 bytes
4 heads, 16 sectors/track, 16384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p12 doesn't contain a valid partition table
Disk ./mmcblk0p11: 12.3 GB, 12356419584 bytes
4 heads, 16 sectors/track, 377088 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
./mmcblk0p11p4 1 1 0 0 Empty
Partition 4 does not end on cylinder boundary
Disk ./mmcblk0p10: 2147 MB, 2147483648 bytes
4 heads, 16 sectors/track, 65536 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p10 doesn't contain a valid partition table
Disk ./mmcblk0p9: 536 MB, 536870912 bytes
4 heads, 16 sectors/track, 16384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p9 doesn't contain a valid partition table
Disk ./mmcblk0p8: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p8 doesn't contain a valid partition table
Disk ./mmcblk0p7: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p7 doesn't contain a valid partition table
Disk ./mmcblk0p6: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p6 doesn't contain a valid partition table
Disk ./mmcblk0p5: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p5 doesn't contain a valid partition table
Disk ./mmcblk0p4: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p4 doesn't contain a valid partition table
Disk ./mmcblk0p3: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p3 doesn't contain a valid partition table
Disk ./mmcblk0p2: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p2 doesn't contain a valid partition table
Disk ./mmcblk0p1: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p1 doesn't contain a valid partition table
Disk ./mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
./mmcblk0p1 1 1923456 15387647+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Mounted filesystems:
Code:
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 415M 32K 415M 4096
/mnt/asec 415M 0K 415M 4096
/mnt/obb 415M 0K 415M 4096
/system 503M 429M 74M 4096
/cache 98M 4M 94M 4096
/efs 19M 8M 11M 4096
/data 1G 666M 1G 4096
/mnt/.lfs: Function not implemented
/mnt/sdcard 11G 2G 9G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
temporal fstab:
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (ro,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/259:3 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd type tmpfs (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000)
tmpfs on /mnt/sdcard/usbStorage type tmpfs (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000)
/dev/block/vold/179:25 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:25 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/org.ais.archidroid-1 type vfat (ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
AdamOutler said:
Hey guys. I'm doing some work to figure out how to recover Galaxy Nexus devices which are hard-bricked.. ie.. they have a bad or no bootloader installed.
the boot sequence
1. IROM - the Internal ROM which cannot be rewritten on the device. This loads the XLoader.
2. XLoader/MLO - This completes the initialization of the processor and memory, and loads up the relatively huge U-Boot ( Samsung modified this and calls it SBL)
3. UBoot/SBL - This "Bootloader" is almost a complete operating system. The U-Boot initializes the screen, provides Odin mode, Fastboot Mode as well as loading the kernel/recovery and provides a UART debugging mode (Yet to be unlocked).
4. Kernel - Once we reach this point, it's all clear.. the kernel is linux which loads android and all sorts of other things.
The Problem
People are bricking their devices at stage 2 and 3 of this boot sequence... This leaves them unable to boot Fastboot or Odin. The device is 100% interchangable with a brick. These devices are ending up hard bricked.
The solution
We must come up with a way to undo the hard brick. Here are some things i'm looking at to use the native hardware to recover itself.
When you plug in the device (when off), you will immediately notice a Texas Instruments D010 device gets enumerated. This is a debug mode for the processor.
Code:
Bus 001 Device 023: ID 0451:d010 Texas Instruments, Inc.
We've started looking at some bootloader output here: http://forum.xda-developers.com/showthread.php?t=1461986
You can find information about the OMAP4 bootloaders here: http://omapedia.org/wiki/Bootloader_Project
Help
I need help locating drivers to initialize the 0451:d010 device and make it readable from within Linux or Windows.. Generally Linux is easier to find appropriate drivers.
I could use some help collecting more reading materials and resources.
I think together as a community we can take care of this problem.
Click to expand...
Click to collapse
AdamOutler said:
There's more to the boot then the OP mentioned... there's 6 partitions involved, not 4.
irom = hard coded
IBL/PBL = initial bootloader and primitive bootloader
SBL = Secondadary Bootloader finds linux
param = contains paramaters to run the phone and required for boot.
SBL2 = download mode (included in SBL)
PIT = Partiton Information Table
Don't touch any of these files.
If you touch the param.ifs, the phone can still boot, however you will see a black screen if something goes wrong.
Code:
BOOT 00000000 0000 0003FFFF 0001
PIT 00040000 0001 0003FFFF 0001
EFS 00080000 0002 009FFFFF 0028
SBL 00A80000 002A 0013FFFF 0005
SBL2 00BC0000 002F 0013FFFF 0005
PARAM 00D00000 0034 004FFFFF 0014
KERNEL 01200000 0048 0077FFFF 001E
RECOVERY 01980000 0066 0077FFFF 001E
FACTORYFS 02100000 0084 11E7FFFF 047A
DBDATAFS 13F80000 04FE 085FFFFF 0218
CACHE 1C580000 0716 022FFFFF 008C
MODEM 1E880000 07A2 00C7FFFF 0032
07D4 1F500000
Click to expand...
Click to collapse
Aditional links:
* Definitive guide to Bricking *
[Guide] Types of Android backups
[REF] GT-I9100 PIT v Flash Analysis
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel
[GUIDE] Making Dump Files Out of Android Device Partitions

/sdcard
This is nice, thank.
But where is from block device the sdcard. How working the "vold"?
How can I partition sdcard with fdisk or with parted?

gyurman said:
This is nice, thank.
But where is from block device the sdcard. How working the "vold"?
How can I partition sdcard with fdisk or with parted?
Click to expand...
Click to collapse
Partition the sdcard from clockworkmod recovery

Thanks, but I want use parted, or fdisk. But what mmcblk0? use sdcard? mmcblk0p11?

[Q] CWM can't mount /cache

I have a problem, I've flashed CWM Recovery v6.0.3.2 on my i9505, but when it starts I get the following errors:
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
I've tried everything (fix permissions, format cache)
Why? How can I solve this?
Here's the log file:
Code:
Starting recovery on Sun Feb 22 07:06:52 1970
framebuffer: fd 4 (1080 x 1920)
ClockworkMod Recovery v6.0.3.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p20 (null) 0
2 /system ext4 /dev/block/mmcblk0p16 (null) 0
3 /data ext4 /dev/block/mmcblk0p29 (null) -16384
4 /cache ext4 /dev/block/mmcblk0p18 (null) 0
5 /recovery emmc /dev/block/mmcblk0p21 (null) 0
6 /sdcard datamedia /dev/null (null) 0
7 /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
W:failed to mount /dev/block/mmcblk0p18 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.hardware=qcom
ro.boot.debug_level=0x4f4c
ro.boot.cp_debug_level=0x55FF
ro.boot.emmc_checksum=3
ro.boot.bootloader=I9505XXUAMDM
ro.boot.nvdata_backup=0
ro.boot.boot_recovery=1
ro.boot.emmc=true
ro.boot.serialno=b3126c9c
ro.boot.baseband=mdm
ro.serialno=b3126c9c
ro.bootmode=unknown
ro.baseband=mdm
ro.bootloader=I9505XXUAMDM
ro.hardware=qcom
ro.revision=11
ro.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=JDQ39E
ro.build.display.id=cm_jfltexx-userdebug 4.2.2 JDQ39E eng.hudson.20130608.221635 test-keys
ro.build.version.incremental=eng.hudson.20130608.221635
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sat Jun 8 22:17:19 PDT 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=hudson
ro.build.host=koushik-lion
ro.build.tags=test-keys
ro.product.model=GT-I9505
ro.product.brand=samsung
ro.product.name=jfltexx
ro.product.device=jflte
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
ro.build.product=jflte
ro.build.description=jfltexx-user 4.2.2 JDQ39 I9505XXUAMDE release-keys
ro.build.fingerprint=samsung/jfltexx/jflte:4.2.2/JDQ39/I9505XXUAMDE:user/release-keys
ro.build.characteristics=default
ro.cm.device=jfltexx
rild.libargs=-d /dev/smd0
telephony.lteOnGsmDevice=1
ro.telephony.default_network=9
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.hwui.text_cache_width=2048
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.chipname=apq8064
ro.ril.hsxpa=1
ro.ril.gprsclass=10
persist.radio.add_power_save=1
persist.radio.snapshot_disabled=1
persist.radio.use_se_table_only=1
persist.radio.fill_eons=1
com.qc.hardware=true
persist.radio.apm_sim_not_pwdn=1
ro.telephony.call_ring.multiple=0
ro.sf.lcd_density=480
ro.ril.transmitpower=true
ro.opengles.version=131072
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
persist.audio.speaker.location=high
ro.qc.sdk.audio.fluencetype=fluence
persist.timed.enable=true
ro.emmc.sdcard.partition=17
ro.use_data_netmgrd=true
persist.data.ds_fmc_app.mode=0
persist.ims.regmanager.mode=0
ro.config.ehrpd=true
persist.omh.enabled=1
persist.data_netmgrd_nint=16
lpa.decode=true
rild.libpath=/system/lib/libril-qc-qmi-1.so
ril.subscription.types=NV,RUIM
ro.cdma.subscribe_on_ruim_ready=true
persist.radio.no_wait_for_card=0
media.aac_51_output_enabled=true
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ro.telephony.ril.v3=newDriverCall
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.logs=0
ro.telephony.ril_class=SamsungQualcommRIL
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.hwui.texture_cache_size=48
ro.hwui.layer_cache_size=32
ro.hwui.path_cache_size=8
ro.hwui.shape_cache_size=2
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=4
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=512
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=10.1-20130609-UNOFFICIAL-jfltexx
ro.modversion=10.1-20130609-UNOFFICIAL-jfltexx
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Deneb.ogg
ro.config.alarm_alert=Hassium.ogg
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p18 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p18 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p18 (Invalid argument)
W:Can't unlink /cache/recovery/command
I:Can't partition non-vfat: datamedia
I:Can't format unknown volume: /emmc
And the output of fdisk -l /dev/block/mmcblk*:
Code:
[email protected]:/ # fdisk -l /dev/block/mmcblk*
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Disk /dev/block/mmcblk0p1: 13 MB, 13078528 bytes
4 heads, 16 sectors/track, 399 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1p1 ? 12158374 29994462 570754815+ 72 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(357, 116, 40) logical=(12158373, 2, 5)
Partition 1 has different physical/logical endings:
phys=(357, 32, 45) logical=(29994461, 2, 3)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p1p2 ? 2635774 32886216 968014120 65 Unknown
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(288, 115, 43) logical=(2635773, 3, 3)
Partition 2 has different physical/logical endings:
phys=(367, 114, 50) logical=(32886215, 0, 2)
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p1p3 ? 29216898 59467339 968014096 79 Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(366, 32, 33) logical=(29216897, 3, 10)
Partition 3 has different physical/logical endings:
phys=(357, 32, 43) logical=(59467338, 1, 9)
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p1p4 ? 1 56831664 1818613248 d Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(372, 97, 50) logical=(0, 0, 1)
Partition 4 has different physical/logical endings:
phys=(0, 10, 0) logical=(56831663, 3, 16)
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
Disk /dev/block/mmcblk0p10: 14 MB, 14286848 bytes
4 heads, 16 sectors/track, 436 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p10 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p11: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p11 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p12: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p12 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p13: 0 MB, 798720 bytes
4 heads, 16 sectors/track, 24 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p13 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p14: 0 MB, 798720 bytes
4 heads, 16 sectors/track, 24 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p14 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p15: 0 MB, 798720 bytes
4 heads, 16 sectors/track, 24 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p15 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p16: 2894 MB, 2894069760 bytes
4 heads, 16 sectors/track, 88320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p17: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p17 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p18: 2170 MB, 2170552320 bytes
4 heads, 16 sectors/track, 66240 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p18 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p19: 6 MB, 6291456 bytes
4 heads, 16 sectors/track, 192 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p19 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p2: 54 MB, 54030336 bytes
4 heads, 16 sectors/track, 1648 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p2p1 ? 12158374 29994462 570754815+ 72 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2p2 ? 2635774 32886216 968014120 65 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p2p3 ? 29216898 59467339 968014096 79 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p2p4 ? 1 56831664 1818613248 d Unknown
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
Disk /dev/block/mmcblk0p20: 10 MB, 10485760 bytes
4 heads, 16 sectors/track, 320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p20 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p21: 10 MB, 10485760 bytes
4 heads, 16 sectors/track, 320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p21 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p22: 10 MB, 10485760 bytes
4 heads, 16 sectors/track, 320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p22 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p23: 6 MB, 6291456 bytes
4 heads, 16 sectors/track, 192 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p23 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p24: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p24 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p25: 0 MB, 8192 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p25 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p26: 9 MB, 9437184 bytes
4 heads, 16 sectors/track, 288 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p26 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p27: 524 MB, 524288000 bytes
4 heads, 16 sectors/track, 16000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p27 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p28: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p28 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p29: 9961 MB, 9961472000 bytes
4 heads, 16 sectors/track, 304000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p29 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p3: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p3 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p4: 0 MB, 262144 bytes
4 heads, 16 sectors/track, 8 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p4 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p5: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p5 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p6: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p6 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p7: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p7 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p8: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p9: 17 MB, 17301504 bytes
4 heads, 16 sectors/track, 528 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p9 doesn't contain a valid partition table
Disk /dev/block/mmcblk1: 1977 MB, 1977614336 bytes
64 heads, 63 sectors/track, 957 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 957 1929244+ 6 FAT16
Disk /dev/block/mmcblk1p1: 1975 MB, 1975546368 bytes
4 heads, 16 sectors/track, 60288 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System

UP
UP?

incompatible recovery.img?
This can be caused by an incompatible recovery.img. I had this issue by downloading a recovery.img for my phone, but turned out to have an incorrect recovery.fstab file in it. This caused wrong mount points being assigned. Digging into this problem, the contents of /proc/emmc should match the recovery.fstab in the recovery.img you're using. Where did you get the CWM recovery from?

LG G6 H872 tmobile shows qualcomm 9008 mode i need partition file to unbrick

hi I am looking LG-VS988 dump file or h872 dump file to unbrick my L6 H872 my phone in QUALCOMM 9008 mode please help
I need MSM8996 .mbn file and rawprogram0.xml
to restore back my device now stucked on Qualcomm HS-USB QDLoader 9008 mode
I have same phone working condition can anyone guide me how to read files from working phone ?
thanks in advance
please help

I have same brand and same problem nobody here have a solution...did You fix It? If Yes how? It is strange is pass more then One years and nobody found a solution

deepmobileworld said:
hi I am looking LG-VS988 dump file or h872 dump file to unbrick my L6 H872 my phone in QUALCOMM 9008 mode please help
I need MSM8996 .mbn file and rawprogram0.xml
to restore back my device now stucked on Qualcomm HS-USB QDLoader 9008 mode
I have same phone working condition can anyone guide me how to read files from working phone ?
thanks in advance
please help
Click to expand...
Click to collapse
I think you should flash some stock stuff to have it working again.
In order, you have to restore your stock KDZ: you can use this guide, or try this.
In addition, you could need to follow these steps to restore your Qualcomm micro-firmware (according to your chipset, you’ll have to use some different files).
If you tell me how to recreate this situation, I’ll try something.
Good luck! :fingers-crossed:

kdz extract linux sd card write done
command link https://mega.nz/#!cJ9WUAiA!TSt9L5G3C...n8vx0pQ9ToxCFw
https://forum.xda-developers.com/g4/...-qfil-t3748946
sorry bad english
[email protected]:~/Downloads$ sudo dmesg -c >> /dev/null
[sudo] password for aaya:
[email protected]:~/Downloads$ dmesg
[email protected]:~/Downloads$ 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$ cd kdz
[email protected]:~/Downloads/kdz$ sudo -s
[email protected]:~/Downloads/kdz# dd if=PrimaryGPT.bin of=/dev/sdb
48+0 records in
48+0 records out
24576 bytes (25 kB, 24 KiB) copied, 0,0441583 s, 557 kB/s
[email protected]:~/Downloads/kdz# sync
[email protected]:~/Downloads/kdz# ls -la /dev/disk/by-partlabel
total 0
drwxr-xr-x 2 root root 60 Луу 18 19:32 .
drwxr-xr-x 7 root root 140 Луу 18 19:32 ..
lrwxrwxrwx 1 root root 10 Луу 18 18:35 EFI\x20System\x20Partition -> ../../sda1
[email protected]:~/Downloads/kdz# cd kdz
bash: cd: kdz: No such file or directory
[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=cache.bin of=/dev/disk/by-partlabel/cache
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=grow2.bin of=/dev/disk/by-partlabel/grow2
dd if=grow3.bin of=/dev/disk/by-partlabel/grow3
dd if=grow4.bin of=/dev/disk/by-partlabel/grow4
dd if=grow5.bin of=/dev/disk/by-partlabel/grow5
dd if=grow6.bin of=/dev/disk/by-partlabel/grow6
dd if=grow.bin of=/dev/disk/by-partlabel/grow
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=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=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=ssd.bin of=/dev/disk/by-partlabel/ssd
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
dd if=xbl2bak.bin of=/dev/disk/by-partlabel/xbl2bak
dd if=xbl2.bin of=/dev/disk/by-partlabel/xbl2
dd if=xblbak.bin of=/dev/disk/by-partlabel/xblbak
dd if=xbl.bin of=/dev/disk/by-partlabel/xbl
[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,0645802 s, 32,5 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,033826 s, 62,0 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0139195 s, 37,7 MB/s
81920+0 records in
81920+0 records out
41943040 bytes (42 MB, 40 MiB) copied, 0,538989 s, 77,8 MB/s
1048576+0 records in
1048576+0 records out
536870912 bytes (537 MB, 512 MiB) copied, 6,8639 s, 78,2 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000314755 s, 13,0 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00478674 s, 110 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00568034 s, 92,3 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00660332 s, 79,4 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00483936 s, 108 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0297275 s, 70,5 MB/s
256+0 records in
256+0 records out
131072 bytes (131 kB, 128 KiB) copied, 0,00236585 s, 55,4 MB/s
256+0 records in
256+0 records out
131072 bytes (131 kB, 128 KiB) copied, 0,00274482 s, 47,8 MB/s
2048+0 records in
2048+0 records out
1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0135021 s, 77,7 MB/s
2048+0 records in
2048+0 records out
1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0120692 s, 86,9 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0153506 s, 34,2 MB/s
20480+0 records in
20480+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0,13946 s, 75,2 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00688644 s, 76,1 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0049967 s, 105 MB/s
135168+0 records in
135168+0 records out
69206016 bytes (69 MB, 66 MiB) copied, 1,01334 s, 68,3 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0511182 s, 82,1 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00611613 s, 85,7 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0170799 s, 123 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000273026 s, 15,0 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000179081 s, 22,9 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000323429 s, 12,7 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,00018018 s, 22,7 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000267083 s, 15,3 MB/s
7080+0 records in
7080+0 records out
3624960 bytes (3,6 MB, 3,5 MiB) copied, 0,0571791 s, 63,4 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00556187 s, 94,3 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00537099 s, 97,6 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00457723 s, 115 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0146511 s, 35,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00600904 s, 87,2 MB/s
98304+0 records in
98304+0 records out
50331648 bytes (50 MB, 48 MiB) copied, 0,67333 s, 74,8 MB/s
98304+0 records in
98304+0 records out
50331648 bytes (50 MB, 48 MiB) copied, 0,616455 s, 81,6 MB/s
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0,404057 s, 83,0 MB/s
176128+0 records in
176128+0 records out
90177536 bytes (90 MB, 86 MiB) copied, 1,1437 s, 78,8 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0244209 s, 85,9 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0240775 s, 87,1 MB/s
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0,426183 s, 78,7 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00713832 s, 73,4 MB/s
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0,405352 s, 82,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0956617 s, 5,5 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00720851 s, 72,7 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0700125 s, 59,9 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0754277 s, 55,6 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0422099 s, 12,4 MB/s
82944+0 records in
82944+0 records out
42467328 bytes (42 MB, 40 MiB) copied, 0,51604 s, 82,3 MB/s
82944+0 records in
82944+0 records out
42467328 bytes (42 MB, 40 MiB) copied, 0,542084 s, 78,3 MB/s
64+0 records in
64+0 records out
32768 bytes (33 kB, 32 KiB) copied, 0,00882342 s, 3,7 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0230715 s, 22,7 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0240835 s, 21,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00557492 s, 94,0 MB/s
12288+0 records in
12288+0 records out
6291456 bytes (6,3 MB, 6,0 MiB) copied, 0,100289 s, 62,7 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0708991 s, 59,2 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,042133 s, 49,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0214201 s, 24,5 MB/s
dd: writing to '/dev/disk/by-partlabel/system': No space left on device
1740777+0 records in
1740776+0 records out
891277312 bytes (891 MB, 850 MiB) copied, 11,3213 s, 78,7 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,0257604 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,0130488 s, 0,0 kB/s
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,0112316 s, 0,0 kB/s
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,00448855 s, 0,0 kB/s
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,00429619 s, 0,0 kB/s
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,00457151 s, 0,0 kB/s
[email protected]:~/Downloads/kdz#

Hey Bro,
link Mega is encrypted, help
Regards

Attempted Unlock of Fire HD 8 (2016/ 6th generat). Is this tablet terminally bricked?

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?