I have read that the KF has 8GB of storage. I see two partitions.... one of them is 1GB in size and the other is 5GB
Can someone explain to me how the 8GB is divided up on the KF?
Thanks
If I understand it correctly, it has two partitions. The 1GB and a 7GB that hosts the system software and where the SD-Card section is. The 5GB you see is what's free after the system software and your stored files.
Sent from my Kindle Fire using Tapatalk
If you look at Setup -> Device you will see what the memory allocation is and what is is basically for...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The top section is Application storage and is aprox 1GB. This is where your applications are loaded along with some other data.
The top section is Internal Storage and is what you see when you plug in the device as a USB drive as the SDcard. It is less than 6GB.
It is possible to move applications in a round about way from the Application Memory to the Internal Storage segment.
Dekan54 said:
I have read that the KF has 8GB of storage. I see two partitions.... one of them is 1GB in size and the other is 5GB
Can someone explain to me how the 8GB is divided up on the KF?
Thanks
Click to expand...
Click to collapse
The 1 gb partition is for your apps, etc....the rest is for reading material. It's my understanding there are utilities to repartition. Not sure if you have to root to do that however. This is where the nook tablet and KF differ the most IMO.
Also remember, there is a difference between actual memory and usable memory. Yes, it's 8 gig but that is not a full 8 gig of usable memory (which is why you only see about 6 gig.
For example, my 8 gig flash drive only has a little over 7 gig of usable memory.
Xandralia said:
Also remember, there is a difference between actual memory and usable memory. Yes, it's 8 gig but that is not a full 8 gig of usable memory (which is why you only see about 6 gig.
For example, my 8 gig flash drive only has a little over 7 gig of usable memory.
Click to expand...
Click to collapse
It's not because of "actual memory" and "usable memory" It's because manufactures represent hard drive space using a different reference.
Here's an example for a 1 TB hard drive:
Manufacturers describe the size of their drive in multiples of 1000
1,000 GB = 1,000 * 1,000,000,000 bytes = 1,000,000,000,000 bytes.
Now let's see how many KiB that is. 1 KiB = 1,024 bytes,
so 1,0000,000,000,000 bytes = 976,562 KiB.
So how many MiB is that? 1 MiB = 1,024 KiB.
So 976,562 KiB = 953 GiB.
Operating systems measure hard drive space in GiB, even though they call it "GB".
Thank you to all that answered....
Are some Fires different?
My fire shows 2.13 GB of 5.37 GB available. No matter how I calcluate that, it is still well under 7GB for content storage. Can someone explain? Thanks.
crackedshel said:
My fire shows 2.13 GB of 5.37 GB available. No matter how I calcluate that, it is still well under 7GB for content storage. Can someone explain? Thanks.
Click to expand...
Click to collapse
C:\Programme\Android\Kindle Fire Utility\tools>adb shell
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB fat32 media
Code:
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734296576B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Calculating size using GB still falls short of 8GB. It actually has 7376MiB of storage. And of those 7376MiB, 1134MiB is for apps/data in the data partition, and 5131MiB is for other media in the sdcard partition. Android sits on a 512MiB partition leaving 599MiB for recovery, diagnostics, bootloader, etc.
Would be nice if there was a small drive we could plug into the port to add a little more.
lmntone said:
Code:
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734296576B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Calculating size using GB still falls short of 8GB. It actually has 7376MiB of storage. And of those 7376MiB, 1134MiB is for apps/data in the data partition, and 5131MiB is for other media in the sdcard partition. Android sits on a 512MiB partition leaving 599MiB for recovery, diagnostics, bootloader, etc.
Click to expand...
Click to collapse
+ any drive and any operating system uses some of the storage space for the filesystem format info, the partition tables, the file tables and so on. So it doesn't matter if the it's 8GB or 8GiB you will never have the full 8 of it unless you leave it an unformated unusable drive. The bigger the drive the bigger the amount of it that has to reserved for the format info by the system.
I've always been confused by the partitioning since I got it as well
Granite Gargoyle said:
Would be nice if there was a small drive we could plug into the port to add a little more.
Click to expand...
Click to collapse
It's been said that the Kingston Wi-Drive will have android support soon, so that would give ya a portable hard drive you could hook up to with wifi to carry around with ya.
Starfire70 said:
It's been said that the Kingston Wi-Drive will have android support soon, so that would give ya a portable hard drive you could hook up to with wifi to carry around with ya.
Click to expand...
Click to collapse
From what I've read on other Fire forums, it already does. It sends out its own wifi signal. Cost $49 for 16gb; around $90 for 32gb.
Partition sizes given in decimal kB and MB are inaccurate.
Sizes and offsets given by parted are not exact because they are given in decimal kB and MB, rather than in binary KiB and MiB, while partitioning is done in the binary units. You can see the exact numbers from the following:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
I have no idea what '179' means, but the sizes are all in 1-KiB (i.e., 1024-byte) blocks, and all the numbers are integral multiples or integral fractions of 1024, so that the partition sizes are, except for those too small, all in integral numbers of MiB.
Hi all! I have Kindle Fire HD 8.9 (root, stock 8.4.9), locked with password. My niece tried log in, she enters the password several times, but could not enter, then she just turned off(press power off button). When I tried to enter, the system is don’t requested a password, language was French, and all of the data disappeared since the beginning of 2015. Yes, I know, I need to backup, but I keep going use it.
Later I known in this model, if lead many times an incorrect password, it launch a factory reset, or proposes to do so, my niece does not know English, so ...............
I have read a few instructions, and was able to rooted again and download to my computer directly from the tablet dump memory:mmcblk0 from /dev/block/*. This is the largest unit, so that it should contain all the data, also i download mmcblkp13 /dev/block/platform/omap/omap_hsmmc.1/ *. It is the user's data. All in *.raw format. Scan R-studio and other programs, but all I found was data information from the default firmware.
I read that when you reset, the data do not disappear completely. Then I found one file, I think it only indicates what happened:
last log file:
Starting recovery on Fri Jul 15 18:33:45 2016
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/sda1 (null) 0
2 /system ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/system (null) 0
3 /cache ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache (null) 0
4 /data ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata (null) 0
5 /misc emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (null) 0
6 /boot emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/boot (null) 0
7 /recovery emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery (null) 0
8 /bootloader emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader (null) 0
9 /xloader emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/xloader (null) 0
I:Boot command: boot-recovery
I:Got arguments from /cache/recovery/command
Battery capacity = 99%
Battery temp = 235 (in dCdegree)
Battery status = discharging
stat() of /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata succeeded on try 1
Command: "/sbin/recovery" "--wipe_data" "--batt_level=40"
Recovery counter: 0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=8.4.7_user_4730020
ro.build.version.number=04730020
ro.build.version.name=8.4.7
ro.build.lab126.buildtype=Nightly
ro.build.lab126.build=300
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Fri Aug 2 17:18:29 PDT 2013
ro.build.date.utc=1375489109
ro.build.type=user
ro.build.user=ubuntu
ro.build.host=ip-10-222-195-0
ro.build.tags=test-keys
ro.build.platform.version=UNKNOWN
ro.product.model=KFJWI
ro.product.brand=Amazon
ro.product.name=Kindle Fire
ro.product.device=Kindle
ro.product.board=blaze_tablet
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Amazon
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
ro.build.product=jem
ro.build.description=jem-user 4.0.4 IMM76D 8.4.7_user_4730020 test-keys
ro.build.fingerprint=Android/jem/jem:4.0.4/IMM76D/8.4.7_user_4730020:user/test-keys
ro.build.characteristics=tablet
rild.libpath=/system/lib/libril-lab126qmi.so
com.ti.omap_enhancement=true
opencore.asmd=1
keyguard.no_require_sim=1
wifi.interface=wlan0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.sf.lcd_density=240
ro.opengles.version=131072
omap.audio.mic.main=AMic0
omap.audio.mic.sub=AMic1
omap.audio.power=PingPong
sys.usb.vid=1949
sys.usb.pid=0008
ro.camera.sound.forced=0
dolby.audio.sink.info=speaker
ro.lab126.skipscreenshots=1
persist.lab126.sys.usb.mtp=1
com.lab126.reap=1
com.lab126.trim=1
pcb.temp.sensor.sysfs.node=/sys/devices/platform/omap/omap_i2c.3/i2c-3/3-0070/temp1_input
batt.temp.sensor.sysfs.node=/sys/class/power_supply/bq27541/temp
cpu.temp.sensor.sysfs.node=/sys/devices/platform/omap/omap_temp_sensor.0/temp1_input
hotspot.temp.sensor.sysfs.node=/sys/class/thermal_sensor/thermal_sensor0/device/hotspot_temp
charge.current.sysfs.node=/sys/class/power_supply/smb347_usb/device/charge_current
ro.sf.hwrotation=90
telephony.sms.send=false
persist.whirlwind.enabled=0
persist.whirlwind.unplugged=0
persist.whirlwind.bandscan=0
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
hwui.render_dirty_regions=false
persist.hwc.mirroring.region=0:0:1920:1200
persist.hwc.mirroring.transform=1
persist.lab126.chargeprotect=1
persist.lab126.touchnoisereject=1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=B0CC0603302501R0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=bowser
ro.revision=0
ro.product.processor=omap4470
init.svc.watchdog=running
init.svc.recovery=running
Formatting /data...
Creating filesystem with parameters:
Size: 60814262272
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14847232
Block groups: 454
Reserved block group size: 1024
Created filesystem with 11/3711904 inodes and 279050/14847232 blocks
Formatting /cache...
Creating filesystem with parameters:
Size: 681574400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6944
Inode size: 256
Journal blocks: 2600
Label:
Blocks: 166400
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/41664 inodes and 5415/166400 blocks
Time spent in the recovery: 124.00 seconds
I'm worried about Null 0 operation - whats it is mean?
Its list of partitition:
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0boot0: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0boot0 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0boot1: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0boot1 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p13: 60.8 GB, 60814262272 bytes
4 heads, 16 sectors/track, 1855904 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p13 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p12: 681 MB, 681574400 bytes
4 heads, 16 sectors/track, 20800 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p12 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p11: 929 MB, 929038336 bytes
4 heads, 16 sectors/track, 28352 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p11 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p10: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p10 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p9: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p9 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p8: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p8 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p7: 67 MB, 67108864 bytes
4 heads, 16 sectors/track, 2048 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p7 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p6: 10 MB, 10485760 bytes
4 heads, 16 sectors/track, 320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p6 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p5: 0 MB, 2048 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p5 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p4: 0 MB, 16384 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p4 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p3: 0 MB, 65536 bytes
4 heads, 16 sectors/track, 2 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p3 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p2: 0 MB, 262144 bytes
4 heads, 16 sectors/track, 8 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p2 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p1: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0p1 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.1/mmcblk0: 62.5 GB, 62537072640 bytes
256 heads, 63 sectors/track, 7573 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/omap/omap_hsmmc.1/mmcblk0p1 1 7574 61071359+ ee EFI GPT
Maybe someone knows, there can be a way to raise the data may have some manipulation of data blocks or there are nothing here, all the data were erase and it makes no sense to do something(special firm ), so the question for those who understand?
I'm curious as to what command you used to dump the kindle data. If you used ADB's backup mechanisms, I don't see why you couldn't restore via ADB as well. If you directly ran dd (either on the device or through a shell on a computer connected to it), that's a little more complex. Also, how big are your backup files, and what partition(s) did you dump?
Hi! I used instructions in this thread http://forum.xda-developers.com/showthread.php?t=1818321
I found blocks of partition on my device in these paths: /dev/block/platform/omap/omap_hsmmc.1/* and /dev/block/* .They have mmcblk0* names, mmcblk0 and 13 parts, they have names mmcblk0p1-mmcblk0p13. Block mmcblk0 - largest, he contain all blocks, mmcblk0p13-user data, he also big. So I copy mmcblk0 (62,5gb) and mmcblk0p13(60,8gb) block in *.raw format directly to my PC( I have kindle with 64gb version). I scanned with the R-studio/R-Linux these blocks and i found nothing, only files and folders from usual default stock firmware. It looks like I have a new tablet from shop, all information that i have before it is gone(before it happened, my tablet was rooted, so in system folder left root checker app, and from previous google account, apps and also all that i did with system before-for example removed stock app-office ). So can you look in information that i found in last_log.txt file above. There the same date and time, when i think tablet launch factory reset itself, it contain "(null) 0" operation in each block of partitions and i think it erase permanently all my data. I think it didn’t was a usual factory reset, i think it feature was added by Amazon to reset all tablets they receive from buyers, but I didn’t know about that.
G710V
My Phone got bricked. Showing as Qualcom 9008.
I use LGUP of V30. Then I select G710T kdz and click start it gave me error at begining even not a Single Partition is flashed. 0x200 then i restart via buttons and then dead.
Talharshad said:
G710V
My Phone got bricked. Showing as Qualcom 9008.
I use LGUP of V30. Then I select G710T kdz and click start it gave me error at begining even not a Single Partition is flashed. 0x200 then i restart via buttons and then dead.
Click to expand...
Click to collapse
There's no way to fix the 9008 mode on these phones yet regardless of how it happened
Hey what variant is the g710v?
Was it factory unlocked?
Sent from my OnePlus 5 using the XDA Premium App
aaya888 said:
i can help you with your problem it's posible to repair LG G4 V10 G5 V20 V30 G6 online "online usbredirector customer module"
you can contact me on skype = Aaya888
https://www.facebook.com/18367302566...991780680/?t=5
Model Settings:
Interface : USB
Core : Qualcomm MSM8996 UFS
Loader : QLoader_v2_LG
Connecting...
Sending loader...OK.
Loader successfully initialized.
INFO: Device Total Logical Blocks: 0x75ec00
INFO: Device Block Size in Bytes: 0x1000
INFO: Device Total Physical Partitions: 0x0
INFO: Device Manufacturer ID: 0x1ad
INFO: Device Serial Number: 0x796e6978
INFO: {"storage_info": {"total_blocks":7728128, "block_size":4096, "page_size":4096, "num_physical":7, "manufacturer_id":429, "serial_num":2037279096, "fw_version":"003","mem_type":"UFS","prod_name":"H28U62301AMR"}}
UFS fInitialized: 0x1
UFS Current LUN Number: = 0xd0
UFS Total Active LU: 0x7
UFS wManufacturerID: 0x1ad
UFS Boot Partition Enabled: 0x1
UFS Raw Device Capacity: = 0x3b9e000
UFS Min Block Size: 0x8
UFS Erase Block Size: 0x2000
UFS Allocation Unit Size: 0x1
UFS RPMB ReadWrite Size: = 0x20
UFS Number of Allocation Uint for This LU: 0x0
UFS Logical Block Size: 0x0
UFS Provisioning Type: 0x0
UFS LU Write Protect: 0x0
UFS Boot LUN ID: = 0x0
UFS Memory Type: 0x0
UFS LU Total Blocks: 0x0
UFS Supported Memory Types: 0x8079
UFS dEnhanced1MaxNAllocU: 0x1dcf
UFS wEnhanced1CapAdjFac: 0x200
UFS dEnhanced2MaxNAllocU: = 0x1dcf
UFS wEnhanced2CapAdjFac: 0x200
UFS dEnhanced3MaxNAllocU: 0x1dcf
UFS wEnhanced3CapAdjFac: 0x200
UFS dEnhanced4MaxNAllocU: 0x0
UFS wEnhanced4CapAdjFac: 0x0
UFS LUN Enable Bitmask: 0x7f
UFS Logical Block Count: 0x0
UFS bConfigDescrLock: 0x0
UFS iManufacturerName String Index: 0x1
UFS iProductName String Index: 0x2
UFS iSerialNumber String Index: 0x3
UFS iOemID String Index: 0x4
UFS Inquiry Command Output: SKhynix H28U62301AMR D003
ACK
Device : SKhynix H28U62301AMR D003
Core : Qualcomm MSM8996 UFS
Page size : 4096 B
Block size : 4096 B
Block count : 7803904
Size : 29.77 GB (30484.00 MB)
Connect successful.
---------------------------------------------------------------
SW: 1.6.0; FW: 1.23.
Physical partition number: 0
Block count : 7728128 (0x75EC00)
Size : 29.48 GB (30188.00 MB)
P00: GPT (00000000, 00000006) 24 KB
P01: laf (00000006, 00003000) 48 MB
P02: lafbak (00003006, 00003000) 48 MB
P03: mpt (00006006, 00002000) 32 MB
P04: drm (00008006, 00000A00) 10 MB
P05: sns (00008A06, 00000600) 6 MB
P06: misc (00009006, 00002000) 32 MB
P07: factory (0000B006, 00004200) 66 MB
P08: encrypt (0000F206, 00000080) 512 KB
P09: eksst (0000F286, 00000080) 512 KB
P10: rct (0000F306, 00000080) 512 KB
P11: ssd (0000F386, 00000080) 512 KB
P12: keystore (0000F406, 00000080) 512 KB
P13: carrier (0000F486, 00002800) 40 MB
P14: persist (00011C86, 00002000) 32 MB
P15: system (00013C86, 00169800) 5.648 GB
P16: cache (0017D486, 00081800) 2072 MB
P17: userdata (001FEC86, 0055F800) 21.49 GB
P18: grow (0075E486, 00000775) 7.457 MB
Physical partition number: 1
Block count : 8192 (0x2000)
Size : 32.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl (00000006, 00000300) 3072 KB
P02: xblbak (00000306, 00000300) 3072 KB
P03: fota (00000606, 00000400) 4 MB
P04: fsg (00000A06, 00000200) 2048 KB
P05: dip (00000C06, 00000100) 1024 KB
P06: devinfo (00000D06, 00000100) 1024 KB
P07: grow2 (00000E06, 00000001) 4 KB
Physical partition number: 2
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl2 (00000006, 00000300) 3072 KB
P02: xbl2bak (00000306, 00000300) 3072 KB
P03: grow3 (00000606, 00000001) 4 KB
Physical partition number: 3
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: ddr (00000006, 00000200) 2048 KB
P02: reserve (00000206, 00000008) 32 KB
P03: cdt (0000020E, 00000001) 4 KB
P04: grow4 (0000020F, 00000001) 4 KB
Physical partition number: 4
Block count : 59392 (0xE800)
Size : 232.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: boot (00000006, 00002800) 40 MB
P02: recovery (00002806, 00002880) 40.5 MB
P03: recoverybak (00005086, 00002880) 40.5 MB
P04: tz (00007906, 00000200) 2048 KB
P05: tzbak (00007B06, 00000200) 2048 KB
P06: aboot (00007D06, 00000200) 2048 KB
P07: abootbak (00007F06, 00000200) 2048 KB
P08: raw_resources (00008106, 00000400) 4 MB
P09: raw_resourcesbak (00008506, 00000400) 4 MB
P10: rpm (00008906, 00000080) 512 KB
P11: rpmbak (00008986, 00000080) 512 KB
P12: hyp (00008A06, 00000080) 512 KB
P13: hypbak (00008A86, 00000080) 512 KB
P14: pmic (00008B06, 00000080) 512 KB
P15: pmicbak (00008B86, 00000080) 512 KB
P16: devcfg (00008C06, 00000020) 128 KB
P17: devcfgbak (00008C26, 00000020) 128 KB
P18: modem (00008C46, 00005600) 86 MB
P19: sec (0000E246, 00000080) 512 KB
P20: keymaster (0000E2C6, 00000080) 512 KB
P21: keymasterbak (0000E346, 00000080) 512 KB
P22: cmnlib (0000E3C6, 00000080) 512 KB
P23: cmnlibbak (0000E446, 00000080) 512 KB
P24: cmnlib64 (0000E4C6, 00000080) 512 KB
P25: cmnlib64bak (0000E546, 00000080) 512 KB
P26: apdp (0000E5C6, 00000080) 512 KB
P27: msadp (0000E646, 00000080) 512 KB
P28: dpo (0000E6C6, 00000080) 512 KB
P29: grow5 (0000E746, 00000001) 4 KB
Physical partition number: 5
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: modemst1 (00000006, 00000200) 2048 KB
P02: modemst2 (00000206, 00000200) 2048 KB
P03: fsc (00000406, 00000080) 512 KB
P04: grow6 (00000486, 00000001) 4 KB
Physical partition number: 6
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: persistent (00000006, 00000200) 2048 KB
P02: grow7 (00000206, 00000001) 4 KB
Click to expand...
Click to collapse
That's for the Snapdragon 820.
Josh McGrath said:
That's for the Snapdragon 820.
Click to expand...
Click to collapse
INFO: Device Total Logical Blocks: 0xece800
INFO: Device Block Size in Bytes: 0x1000
INFO: Device Total Physical Partitions: 0x0
INFO: Device Manufacturer ID: 0x198
INFO: Device Serial Number: 0x48494241
INFO: {"storage_info": {"total_blocks":15525888, "block_size":4096, "page_size":4096, "num_physical":7, "manufacturer_id":408, "serial_num":1212760641, "fw_version":"100","mem_type":"UFS","prod_name":"THGAF4G9N4LBAIRB0100"}}
UFS fInitialized: 0x1
UFS Current LUN Number: = 0xd0
UFS Total Active LU: 0x7
UFS wManufacturerID: 0x198
UFS Boot Partition Enabled: 0x1
UFS Raw Device Capacity: = 0x7734000
UFS Min Block Size: 0x8
UFS Erase Block Size: 0x2000
UFS Allocation Unit Size: 0x1
UFS RPMB ReadWrite Size: = 0x40
UFS Number of Allocation Uint for This LU: 0x0
UFS Logical Block Size: 0x0
UFS Provisioning Type: 0x0
UFS LU Write Protect: 0x0
UFS Boot LUN ID: = 0x0
UFS Memory Type: 0x0
UFS LU Total Blocks: 0x0
UFS Supported Memory Types: 0x801f
UFS dEnhanced1MaxNAllocU: 0x3b9a
UFS wEnhanced1CapAdjFac: 0x200
UFS dEnhanced2MaxNAllocU: = 0x20
UFS wEnhanced2CapAdjFac: 0x200
UFS dEnhanced3MaxNAllocU: 0x0
UFS wEnhanced3CapAdjFac: 0x0
UFS dEnhanced4MaxNAllocU: 0x0
UFS wEnhanced4CapAdjFac: 0x0
UFS LUN Enable Bitmask: 0x7f
UFS Logical Block Count: 0x0
UFS bConfigDescrLock: 0x0
UFS iManufacturerName String Index: 0x1
UFS iProductName String Index: 0x2
UFS iSerialNumber String Index: 0x3
UFS iOemID String Index: 0x4
UFS Inquiry Command Output: TOSHIBA THGAF4G9N4LBAIRB0100
ACK
Device : TOSHIBA THGAF4G9N4LBAIRB0100
Core : Qualcomm MSM8998 UFS
Page size : 4096 B
Block size : 4096 B
Block count : 15613952
Size : 59.56 GB (60992.00 MB)
Connect successful.
---------------------------------------------------------------
SW: 1.5.9; FW: 1.23.
Physical partition number: 0
Block count : 15525888 (0xECE800)
Size : 59.23 GB (60648.00 MB)
P00: GPT (00000000, 00000006) 24 KB
P01: laf (00000006, 00003000) 48 MB
P02: lafbak (00003006, 00003000) 48 MB
P03: mpt (00006006, 00002000) 32 MB
P04: drm (00008006, 00000A00) 10 MB
P05: sns (00008A06, 00000600) 6 MB
P06: misc (00009006, 00000100) 1024 KB
P07: ftm (00009106, 00002000) 32 MB
P08: factory (0000B106, 00004200) 66 MB
P09: encrypt (0000F306, 00000080) 512 KB
P10: eksst (0000F386, 00000080) 512 KB
P11: rct (0000F406, 00000080) 512 KB
P12: ssd (0000F486, 00000080) 512 KB
P13: keystore (0000F506, 00000080) 512 KB
P14: persist (0000F586, 00002000) 32 MB
P15: srtc (00011586, 00000800) 8 MB
P16: qni (00011D86, 00001800) 24 MB
P17: pstore (00013586, 00000200) 2048 KB
P18: system (00013786, 0019A200) 6.408 GB
P19: cache (001AD986, 00020000) 512 MB
P20: userdata (001CD986, 00D00E74) 52.01 GB
P21: grow (00ECE7FA, 00000001) 4 KB
Physical partition number: 1
Block count : 8192 (0x2000)
Size : 32.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl (00000006, 00000380) 3584 KB
P02: fota (00000386, 00000400) 4 MB
P03: fsg (00000786, 00000200) 2048 KB
P04: dip (00000986, 00000100) 1024 KB
P05: devinfo (00000A86, 00000100) 1024 KB
P06: grow2 (00000B86, 00000002) 8 KB
Physical partition number: 2
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl2 (00000006, 00000380) 3584 KB
P02: grow3 (00000386, 00000002) 8 KB
Physical partition number: 3
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: ddr (00000006, 00000200) 2048 KB
P02: cdt (00000206, 00000001) 4 KB
P03: grow4 (00000207, 00000002) 8 KB
Physical partition number: 4
Block count : 71680 (0x11800)
Size : 280.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: boot (00000006, 00002800) 40 MB
P02: recovery (00002806, 00002880) 40.5 MB
P03: recoverybak (00005086, 00002880) 40.5 MB
P04: tz (00007906, 00000200) 2048 KB
P05: tzbak (00007B06, 00000200) 2048 KB
P06: raw_resources (00007D06, 00000400) 4 MB
P07: raw_resourcesbak (00008106, 00000400) 4 MB
P08: rpm (00008506, 00000080) 512 KB
P09: rpmbak (00008586, 00000080) 512 KB
P10: hyp (00008606, 00000080) 512 KB
P11: hypbak (00008686, 00000080) 512 KB
P12: pmic (00008706, 00000080) 512 KB
P13: pmicbak (00008786, 00000080) 512 KB
P14: devcfg (00008806, 00000020) 128 KB
P15: devcfgbak (00008826, 00000020) 128 KB
P16: modem (00008846, 00006E00) 110 MB
P17: sec (0000F646, 00000080) 512 KB
P18: keymaster (0000F6C6, 00000080) 512 KB
P19: keymasterbak (0000F746, 00000080) 512 KB
P20: cmnlib (0000F7C6, 00000080) 512 KB
P21: cmnlibbak (0000F846, 00000080) 512 KB
P22: cmnlib64 (0000F8C6, 00000080) 512 KB
P23: cmnlib64bak (0000F946, 00000080) 512 KB
P24: apdp (0000F9C6, 00000080) 512 KB
P25: msadp (0000FA46, 00000080) 512 KB
P26: dpo (0000FAC6, 00000080) 512 KB
P27: abl (0000FB46, 00000100) 1024 KB
P28: ablbak (0000FC46, 00000100) 1024 KB
P29: limits (0000FD46, 00000001) 4 KB
P30: toolsfv (0000FD47, 00000100) 1024 KB
P31: logfs (0000FE47, 00000800) 8 MB
P32: storsec (00010647, 00000020) 128 KB
P33: storsecbak (00010667, 00000020) 128 KB
P34: grow5 (00010687, 00000002) 8 KB
Physical partition number: 5
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: modemst1 (00000006, 00000200) 2048 KB
P02: modemst2 (00000206, 00000200) 2048 KB
P03: fsc (00000406, 00000080) 512 KB
P04: grow6 (00000486, 00000002) 8 KB
Physical partition number: 6
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: frp (00000006, 00000200) 2048 KB
P02: grow7 (00000206, 00000002) 8 KB
Yet again, that is the wrong model. That is not the G7. (!!!).
It's good you can do that particular chipset, but You're really taking a huge hit to your credibility here.
Hi,
Anyone had any luck? I also bricked my G710PM. I tried creating a Partition0.xml for QFIL from the PrimaryGPT_x.bin files extracted from G710EM10b_00_0521.dz but I can't test it because I can't find the correct Firehose file. I've attached the files, maybe it helps someone
DonDie said:
Hi,
Anyone had any luck? I also bricked my G710PM. I tried creating a Partition0.xml for QFIL from the PrimaryGPT_x.bin files extracted from G710EM10b_00_0521.dz but I can't test it because I can't find the correct Firehose file. I've attached the files, maybe it helps someone
Click to expand...
Click to collapse
You'd be very lucky to find d the Firehouse file. Last file that was leaked was for the G4!
There are companies like spammy above that do this but it'd be quicker to just get a warranty replacement from T-Mobile or LG.
F- LG I hope they get a million damaged units cause they won't release the files we need to fix them ourselves
I had the wrong person mentioned. Please ignore
Josh McGrath said:
Wtf is wrong with you? That's for the g6. Yet again you have proved you're ignorance and taken yet another serious blow to your credibility.
Maybe you missed it. The g7 has a different chipset than the 8996, 8998 chipset.
Mods can you please delete this thread? Its this guy and his spam, and incorrect spam at that.
Click to expand...
Click to collapse
Have you watched the movie? Unless it's fake around 13:05 there was a G7 folder with the SDM845 Firehose file.
@ aaya888
Would you mind sharing the file?
DonDie said:
Have you watched the movie? Unless it's fake around 13:05 there was a G7 folder with the SDM845 Firehose file.
@ aaya888
Would you mind sharing the file?
Click to expand...
Click to collapse
I did, and saw it was a g6 with v20 partition tables. And actually, I thought it was the same guy I was correcting over and over and it is not so I have corrected my earlier post. I think they other guy got banned ?
@aaya888
How is the state of H918 (TMO V20) firehose fixin now a days, still no go?
Josh McGrath said:
There's no way to fix the 9008 mode on these phones yet regardless of how it happened
Click to expand...
Click to collapse
contact me i can help you out
Tennolee said:
contact me i can help you out
Click to expand...
Click to collapse
It's not me that needs the help but I know a lot of people could use your help after a hard brick.
Tennolee said:
contact me i can help you out
Click to expand...
Click to collapse
Can you do it remotely and how much will it cost?
DonDie said:
Can you do it remotely and how much will it cost?
Click to expand...
Click to collapse
Hi all, I bricked my Tmobile variant and I have an Octoplus Pro box, however not the right loader. Octoplus only supports EWM version
KennynGGG said:
Hi all, I bricked my Tmobile variant and I have an Octoplus Pro box, however not the right loader. Octoplus only supports EWM version
Click to expand...
Click to collapse
The latest version of Octoplus LG has PM/AWM/EM support (v.2.8.9 but 2.9.2 is out as well):
G710AWMH - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EM - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EMW - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
Try selecting the version you wish to flash to, for example, G710AWM and write the .KDZ for that model. Hopefully that un-bricks it for you.
Dont hold me to this as my experience is more HTC/Samsung than LG, I am newer to LG so I dont necessarily know if it will re-write the partitions correctly to fix 9008 but thats where I would start. Trying to flash .KDZ through otcoplus to hopefully recover the device if I were in a bricked situation.
GROOVYJOSHCLARK said:
The latest version of Octoplus LG has PM/AWM/EM support (v.2.8.9 but 2.9.2 is out as well):
G710AWMH - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EM - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EMW - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
Try selecting the version you wish to flash to, for example, G710AWM and write the .KDZ for that model. Hopefully that un-bricks it for you.
Dont hold me to this as my experience is more HTC/Samsung than LG, I am newer to LG so I dont necessarily know if it will re-write the partitions correctly to fix 9008 but thats where I would start. Trying to flash .KDZ through otcoplus to hopefully recover the device if I were in a bricked situation.
Click to expand...
Click to collapse
THanks, that's the reason I think JTAG pro can't send the loader to mine because it's G710TM which is not listed. I swear somehow that I had that same issue before but was able to fix just not now. Only if I can find the real Test Point to connect to ground. Their picture is very hard to see because it's not the whole motherboard picture just the section where the Test Points are.
Hi, I just changed the firmware on my G710 and LGUP informed Completed, but the phone never turned back on.
I just found out I am also on the Qualcomm 9008. Did you manage to fix your issue?
tks!
i need stock FirmWare for g570v stock rom, if anyone have?