Hi!
I have some problems And sorry for my english.
I bought a H96 Max X4 Android TV box from Geekbuying. I have factory firmwares for it, so i start to modify the device. It has Android TV 11 version.
The device has root shell on adb, but the device not rooted itself.
The problems are:
I can unpack superimage from stock firmware, and able to do dd backup super from device. But i can not use fastboot flashing because of "FAILED (remote: 0ffff13c)" error.
The number changes depending on which superimage I am trying to write.
This is not real problem, beacuse of i can use dd for flash back the images.
But...
If i try to write back the backuped superimage or what extracted from stock FW, everything is okay. But the unpacked and repacked image causes bootloop.
The lpdump says the device's metadata and the repacked superimage's metadata are the same:
ohm:/ # lpdump
Slot 0:
Metadata version: 10.2
Metadata size: 1104 bytes
Metadata max size: 65536 bytes
Metadata slot count: 3
Header flags: virtual_ab_device
Partition table:
------------------------
Name: system_a
Group: amlogic_dynamic_partitions_a
Attributes: readonly
Extents:
0 .. 1839895 linear super 2048
------------------------
Name: system_b
Group: amlogic_dynamic_partitions_b
Attributes: readonly
Extents:
------------------------
Name: vendor_a
Group: amlogic_dynamic_partitions_a
Attributes: readonly
Extents:
0 .. 357943 linear super 1843200
------------------------
Name: vendor_b
Group: amlogic_dynamic_partitions_b
Attributes: readonly
Extents:
------------------------
Name: product_a
Group: amlogic_dynamic_partitions_a
Attributes: readonly
Extents:
0 .. 854999 linear super 2201600
------------------------
Name: product_b
Group: amlogic_dynamic_partitions_b
Attributes: readonly
Extents:
------------------------
Name: odm_a
Group: amlogic_dynamic_partitions_a
Attributes: readonly
Extents:
0 .. 1559 linear super 3057664
------------------------
Name: odm_b
Group: amlogic_dynamic_partitions_b
Attributes: readonly
Extents:
------------------------
Name: system_ext_a
Group: amlogic_dynamic_partitions_a
Attributes: readonly
Extents:
0 .. 133159 linear super 3059712
------------------------
Name: system_ext_b
Group: amlogic_dynamic_partitions_b
Attributes: readonly
Extents:
------------------------
Super partition layout:
------------------------
super: 2048 .. 1841944: system_a (1839896 sectors)
super: 1843200 .. 2201144: vendor_a (357944 sectors)
super: 2201600 .. 3056600: product_a (855000 sectors)
super: 3057664 .. 3059224: odm_a (1560 sectors)
super: 3059712 .. 3192872: system_ext_a (133160 sectors)
------------------------
Block device table:
------------------------
Partition name: super
First sector: 2048
Size: 2415919104 bytes
Flags: none
------------------------
Group table:
------------------------
Name: default
Maximum size: 0 bytes
Flags: none
------------------------
Name: amlogic_dynamic_partitions_a
Maximum size: 1876951040 bytes
Flags: none
------------------------
Name: amlogic_dynamic_partitions_b
Maximum size: 1876951040 bytes
Flags: none
------------------------
I use this command to repack the superimage:
./lpmake --metadata-size 65536\
--device-size=2415919104\
--metadata-slots=3\
--super-name=super\
--group=amlogic_dynamic_partitions_a:1876951040\
--group=amlogic_dynamic_partitions_b:1876951040\
--partition=system_a:readonly:942026752:amlogic_dynamic_partitions_a\
--partition=system_b:readonly:0:amlogic_dynamic_partitions_b\
--partition=vendor_a:readonly:183267328:amlogic_dynamic_partitions_a\
--partition=vendor_b:readonly:0:amlogic_dynamic_partitions_b\
--partition=product_a:readonly:437760000:amlogic_dynamic_partitions_a\
--partition=product_b:readonly:0:amlogic_dynamic_partitions_b\
--partition=odm_a:readonly:798720:amlogic_dynamic_partitions_a\
--partition=odm_b:readonly:0:amlogic_dynamic_partitions_b\
--partition=system_ext_a:readonly:68177920:amlogic_dynamic_partitions_a\
--partition=system_ext_b:readonly:0:amlogic_dynamic_partitions_b\
--image=system_a=/super/system_a.img\
--image=system_b=/super/system_b.img\
--image=vendor_a=/super/vendor_a.img\
--image=vendor_b=/super/vendor_b.img\
--image=product_a=/super/product_a.img\
--image=product_b=/super/product_b.img\
--image=odm_a=/super/odm_a.img\
--image=odm_b=/super/odm_b.img\
--image=system_ext_a=/super/system_ext_a.img\
--image=system_ext_b=/super/system_ext_b.img\
--virtual-ab\
--output /super/supernew.img
The unpacked modified superimage and the unpacked stock superimage gives the same files.
Any idea for what is the problem?
Thanks!
For more information here are the imjtool results:
Original, factory superimage:
./imjtool /mnt/rawsuper.img
MMapped: 0x7f9606303000, imgMeta 0x7f9606304000
liblp dynamic partition (super.img) - Blocksize 0x1000, 3 slots
LP MD Header @0x3000, version 10.2, with 10 logical partitions @0x0 on block device of 2304 GB, at partition super, first sector: 0x800
Partitions @0x3100 in 3 groups:
Group 0: default
Group 1: amlogic_dynamic_partitions_a
Name: system_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x100000 spanning 1 extents of 898 MB)
Name: vendor_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x38400000 spanning 1 extents of 174 MB)
Name: product_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x43300000 spanning 1 extents of 417 MB)
Name: odm_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x5d500000 spanning 1 extents of 780 KB)
Name: system_ext_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x5d600000 spanning 1 extents of 65 MB)
Group 2: amlogic_dynamic_partitions_b
Name: system_b (read-only, empty)
Name: vendor_b (read-only, empty)
Name: product_b (read-only, empty)
Name: odm_b (read-only, empty)
Name: system_ext_b (read-only, empty)
And the repacked superimage:
./imjtool /mnt/supernew.img
MMapped: 0x7f3a9dc5b000, imgMeta 0x7f3a9dc5c000
liblp dynamic partition (super.img) - Blocksize 0x1000, 3 slots
LP MD Header @0x3000, version 10.2, with 10 logical partitions @0x0 on block device of 2304 GB, at partition super, first sector: 0x800
Partitions @0x3100 in 3 groups:
Group 0: default
Group 1: amlogic_dynamic_partitions_a
Name: system_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x100000 spanning 1 extents of 898 MB)
Name: vendor_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x38400000 spanning 1 extents of 174 MB)
Name: product_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x43300000 spanning 1 extents of 417 MB)
Name: odm_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x5d500000 spanning 1 extents of 780 KB)
Name: system_ext_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x5d600000 spanning 1 extents of 65 MB)
Group 2: amlogic_dynamic_partitions_b
Name: system_b (read-only, empty)
Name: vendor_b (read-only, empty)
Name: product_b (read-only, empty)
Name: odm_b (read-only, empty)
Name: system_ext_b (read-only, empty)
There Is no any idea?
Related
UPDATED WITH SAMSUNG ORIGINAL FIRMWARE
Hi SGH-T599 users!
I don't have this device myself, but a S3mini which is pretty much the same device.
Since no official firmwares is to be found yet, and @Unjustified Dev made CM10.1 and CWM I thought it would be good to make something for odin as an option to get back to stock.
These are reworked images taken from devices with dd-method.
Each tar contains boot.img, cache.img, system.img and recovery.img.
Boot and recovery repacked to be accual size. System and cache totaly repacked to sparse ext4-img files.
I also added supersu, su binary and busybox so these are pre-rooted
If you for some reason want to unroot, go to supersu settings and tick full unroot.
T599-Pre-rooted.zip - 600.17 MB
T599N-Pre-rooted.zip - 572.45 MB
T599V-Pre-rooted.zip - 579.90 MB
Included is also a zipped "modem.bin" If you messed up your modem you can get it flashed to device with Terminal Emulator.
Put "modem.bin" on your sdcard. In TM, type:
Code:
su
dd if=/sdcard/modem.bin of= dev/block/mmcblk0p16
OFFICIAL FIRMWARESGH-T599 HOME_T599UVAOH1_T599TMBAOH1_969628_REV00_user_low_ship<- Strange name. Home usually means no reset and REV00_user_low_ship is usually seen on full flash files with factory reset on flash. This one have both. Don't know if it resets or not.
SGH-T599V T599V_T599VYVLAME4_T599VVLAME4
SGH-T599N T599NUVAOH1_T599NTMBAOH1_T599NUVAOH1_HOME
"one-click-root" (works on s3mini so I think it works here as well)
Enable USB debug. View attachment VRoot_1.6.0.3689_english.zip
Otherwise cydiaimpactor is known to work.
Links to related threads which together made everything possible:
[ROM] [4.3.1] [OFFICIAL][Nightlies][Codinaxx Galaxy Exhibit T599X Variants]PAC-Man
[ROM][4.2.2.][UNOFFICIAL] CyanogenMod 10.1 for Galaxy Exhibits
[Recovery][CWM] SGH-T599- Working
[System, Boot & Recovery Dump][8-27-13] SGH-T599 (4.1.2) JZO54K.T599UVAMB5
If coming from CM or other custom rom, FIRST GO TO RECOVERY AND MAKE A FACTORY RESET
HOW TO FLASH:
Download Odin 3.04 and install samsung drivers.
Unzip downloaded firmware.
Open Odin, put phone in download mode (vol-/home/power).
Connect phone to computer, and place the *tar.md5 in PDA-box.
Make sure F-reset time and auto reboot is ticked. Press START.
Attached to this post you'll find a zipped wipe.tar for odin. Unzip and load as pda.
It's just empty cache and should work to break bootloops if you can't get to recovery.
Thanks to @Unjustified Dev @goldfingerfif @exothermic @DJVargas (sorry if I forgot someone) Just let me know and I'll add it.:good:
Reserved for flashable zips
SGH-T599V-deodex.zip - 337.80 MB Replace T599V system-apps and framework to de-odexed. Link to updater script
SGH-T599V GoogleBoot logo mod & back to stock zip's Thx to @Exothermic for testing!
Test for bootlogo mod - all SGH-T599 models.
Partitions & pit-files
Additional info.
Partition-table and file names.
Code:
SGH-T599:
/proc/partitions
major minor #blocks name
7 0 5229 loop0
179 0 3866624 mmcblk0
179 1 128 mmcblk0p1 - MBR,GPT
179 2 384 mmcblk0p2 - MasterTOC - STE_boot.bin
179 3 1024 mmcblk0p3 - codinavid.pit / codinatmo.pit
179 4 1024 mmcblk0p4 - md5.img
179 5 512 mmcblk0p5 - STE_boot1.img
179 6 512 mmcblk0p6 - STE_boot2.img
179 7 512 mmcblk0p7 - dnt.ssw
179 8 512 mmcblk0p8 - reserved
179 9 1024 mmcblk0p9 - cspsa.img
179 10 1024 mmcblk0p10 - cspsa2.img
179 11 16384 mmcblk0p11 - EFS.img
179 12 16384 mmcblk0p12 - modemfs.img
179 13 16384 mmcblk0p13 - modemfs2.img
179 14 51200 mmcblk0p14 - ssgtest.img
179 15 64 mmcblk0p15 - ipl.bin
179 16 14336 mmcblk0p16 - modem.bin
179 17 2048 mmcblk0p17 - normal.bin
179 18 2048 mmcblk0p18 - normal2.bin
179 19 16384 mmcblk0p19 - param.lfs
179 20 16384 mmcblk0p20 - boot.img
179 21 16384 mmcblk0p21 - recovery.img
179 22 1228800 mmcblk0p22 - system.img
179 23 737280 mmcblk0p23 - cache.img
179 24 102400 mmcblk0p24 - hidden.img
179 25 1535983 mmcblk0p25 - userdata.img
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15637504 mmcblk1
179 97 15633408 mmcblk1p1
254 0 5229 dm-0
Analysis of codinavid.pit:
Code:
----------------------------------------------------------
PIT Magic v1.3.10 Copyright © Gaz 2012.
----------------------------------------------------------
Analysis for: codinavid.pit
----------------------------------------------------------
----------------------------------------------------------
<<< Pit File Start >>>
----------------------------------------------------------
----------------------------------------------------------
<<< PIT File Header Information >>>
----------------------------------------------------------
Header Magic: 0x12349876 (4 Bytes)
Entry Count: 25 (4 Bytes)
----------------------------------------------------------
Dummy Data #1 (In String and Hexadecimal Format):
----------------------------------------------------------
String: COM_
Hexadecimal: 434F4D5F
----------------------------------------------------------
Dummy Data #2 (In String and Hexadecimal Format):
----------------------------------------------------------
String: TAR2
Hexadecimal: 54415232
----------------------------------------------------------
Dummy Data #3 (In String and Hexadecimal Format):
----------------------------------------------------------
String: codi
Hexadecimal: 636F6469
----------------------------------------------------------
Dummy Data #4 (In String and Hexadecimal Format):
----------------------------------------------------------
String: na
Hexadecimal: 6E610000
----------------------------------------------------------
Dummy Data #5 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data Length: (4 Bytes Per Block, 20 Bytes In Total.)
----------------------------------------------------------
Header Size: (28 Bytes)
----------------------------------------------------------
<<< PIT File Entries >>>
----------------------------------------------------------
----------------------------------------------------------
Entry Memory Address: 0x1C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 1
Attribute: 2 (STL)
Update Attribute: 1 (FOTA)
Block Size:
Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MBR,GPT
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xA0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 2
Attribute: 2 (STL)
Update Attribute: 1 (FOTA)
Block Size: 256
Block Count: 768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MasterTOC
Flash FileName: STE_boot.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x124
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 70
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 1*024
Block Count: 2*048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash FileName: codinavid.pit
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x1A8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 71
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 6*144
Block Count: 2*048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash FileName: md5.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x22C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 3
Attribute: 2 (STL)
Update Attribute: 1 (FOTA)
Block Size: 8*192
Block Count: 1*024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEboot1
Flash FileName: STE_boot1.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x2B0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 4
Attribute: 2 (STL)
Update Attribute: 1 (FOTA)
Block Size: 9*216
Block Count: 1*024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEboot2
Flash FileName: STE_boot2.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x334
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 5
Attribute: 2 (STL)
Update Attribute: 1 (FOTA)
Block Size: 10*240
Block Count: 1*024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Dnt
Flash FileName: dnt.ssw
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x3B8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 6
Attribute: 2 (STL)
Update Attribute: 1 (FOTA)
Block Size: 11*264
Block Count: 1*024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: reserved
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x43C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 7
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 16*384
Block Count: 2*048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CSPSAFS
Flash FileName: cspsa.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x4C0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 8
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 18*432
Block Count: 2*048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CSPSAFS2
Flash FileName: cspsa2.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x544
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 9
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 20*480
Block Count: 32*768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash FileName: EFS.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x5C8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 10
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 53*248
Block Count: 32*768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ModemFS
Flash FileName: modemfs.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x64C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 11
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 86*016
Block Count: 32*768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ModemFS2
Flash FileName: modemfs2.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x6D0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 12
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 118*784
Block Count: 102*400
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Fota
Flash FileName: ssgtest.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 13
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 380*928
Block Count: 128
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: IPL Modem
Flash FileName: ipl.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x7D8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 14
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 385*024
Block Count: 28*672
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Modem
Flash FileName: modem.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x85C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 15
Attribute: 2 (STL)
Update Attribute: 1 (FOTA)
Block Size: 417*792
Block Count: 4*096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Loke4
Flash FileName: normal.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x8E0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 16
Attribute: 2 (STL)
Update Attribute: 1 (FOTA)
Block Size: 421*888
Block Count: 4*096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: 2ndLoke4
Flash FileName: normal2.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x964
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 17
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 425*984
Block Count: 32*768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash FileName: param.lfs
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x9E8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 18
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 458*752
Block Count: 32*768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Kernel
Flash FileName: boot.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xA6C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 19
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 491*520
Block Count: 32*768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Kernel2
Flash FileName: recovery.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xAF0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 20
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 524*288
Block Count: 2*457*600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash FileName: system.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xB74
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 21
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 2*981*888
Block Count: 1*474*560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHEFS
Flash FileName: cache.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xBF8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 22
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 4*456*448
Block Count: 204*800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash FileName: hidden.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xC7C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 23
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 4*661*248
Block Count:
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash FileName: userdata.img
FOTA FileName: remained
----------------------------------------------------------
<<< Pit File End >>>
----------------------------------------------------------
Unzip and load in Odin [Pit]
Awesome Job! Thank you as well to @tys0n @Unjustified Dev @goldfingerfif @Exothermic and anyone else who made this possible. Glad you got your thread up.
Sent from my SGH-T599N using Tapatalk
I can also use the recovery to the original rom from s3mini?
Gesendet von meinem GT-I8190 mit Tapatalk
jony1512 said:
I can also use the recovery to the original rom from s3mini?
Gesendet von meinem GT-I8190 mit Tapatalk
Click to expand...
Click to collapse
No you can't. They are very much alike and share same partition layout but s3mini recovery will give you nothing but bootloop. Thats also one of the reason I started this "odin-project" for T599 in the first place.
What's wrong with T599 recovery?
tys0n said:
No you can't. They are very much alike and share same partition layout but s3mini recovery will give you nothing but bootloop. Thats also one of the reason I started this "odin-project" for T599 in the first place.
What's wrong with T599 recovery?
Click to expand...
Click to collapse
ok thanks in advance for the answer. I wanted to have the recovery system as I have read that the recovery system and the menu has rwecovery of the Phil3759. or because I've now read something wrong? sorry my english is not so good. I had to make in order to use the recovery system?
thanks
Sent from my SGH-T599N using xda app-developers app
Can we flash it too? (GT-I8190)
Sent from my GT-I8190 using xda app-developers app
jony1512 said:
ok thanks in advance for the answer. I wanted to have the recovery system as I have read that the recovery system and the menu has rwecovery of the Phil3759. or because I've now read something wrong? sorry my english is not so good. I had to make in order to use the recovery system?
Click to expand...
Click to collapse
klopp-o-mat said:
Can we flash it too? (GT-I8190)
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
I wish we had phils recovery too, but these files are for T-599 only.
tys0n said:
I wish we had phils recovery too, but these files are for T-599 only.
Click to expand...
Click to collapse
if that is not for the mini s3, I do not understand why this will be posted in s3 mini forum. I'm now even after everything had asked because I like the recovery system of Phils.
Gesendet von meinem GT-I8190 mit Tapatalk
jony1512 said:
if that is not for the mini s3, I do not understand why this will be posted in s3 mini forum. I'm now even after everything had asked because I like the recovery system of Phils.
Gesendet von meinem GT-I8190 mit Tapatalk
Click to expand...
Click to collapse
It's in s3 mini forum because it's built on the same board and got same partition layout. It doesn't have it's own forum..at least not yet, and because it's the US version of s3mini with only a few differences.
tys0n said:
It's in s3 mini forum because it's built on the same board and got same partition layout. It doesn't have it's own forum..at least not yet, and because it's the US version of s3mini with only a few differences.
Click to expand...
Click to collapse
okay now I understand all that thank you for your help. wiessen they might ask if you could do the mini for the s3 can build the recovery system of Phils. I would try it myself but I have no stable internet connection and I am not familiar with Ubuntu.
Gesendet von meinem GT-I8190 mit Tapatalk
jony1512 said:
okay now I understand all that thank you for your help. wiessen they might ask if you could do the mini for the s3 can build the recovery system of Phils. I would try it myself but I have no stable internet connection and I am not familiar with Ubuntu.
Gesendet von meinem GT-I8190 mit Tapatalk
Click to expand...
Click to collapse
I'm not the one to do it, but instructions on how to get it done is in Phil's main thread for his recovery. Scroll down to post#2. [18.10.2013]CWM 6.0.4.4 Advanced Edition / PhilZ Touch 5.18.5 + exFAT + NTFS
Thank you so much! This is exactly what I needed.
iAmWillJ91 said:
Thank you so much! This is exactly what I needed.
Click to expand...
Click to collapse
You're welcome Glad you found it.
tys0n said:
I'm not the one to do it, but instructions on how to get it done is in Phil's main thread for his recovery. Scroll down to post#2. [18.10.2013]CWM 6.0.4.4 Advanced Edition / PhilZ Touch 5.18.5 + exFAT + NTFS
Click to expand...
Click to collapse
I try my luck've just seen this applies also for Windows. I've just looked at the time of Phil's git I've got to ask a times I think of the mini s3 DEVICE_CONFIG out or where to get something to read?
Gesendet von meinem GT-I8190 mit Tapatalk
jony1512 said:
okay now I understand all that thank you for your help. wiessen they might ask if you could do the mini for the s3 can build the recovery system of Phils. I would try it myself but I have no stable internet connection and I am not familiar with Ubuntu.
Gesendet von meinem GT-I8190 mit Tapatalk
Click to expand...
Click to collapse
I'll try to port it
Sent from my SCH-I535 using Tapatalk
@tys0n I need a stock recovery image. Good thing is our ramdisk is exactly the same. All I need to do is change kernel.
Sent from my SCH-I535 using Tapatalk
Unjustified Dev said:
@tys0n I need a stock recovery image. Good thing is our ramdisk is exactly the same. All I need to do is change kernel.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Here's i8190_Stock_recovery.img
I'll be happy to test it, and thanks in advance
I have a Nexus S 9023 fresh of bootloader unlocking becasue I want to solve a limitation due to the storage available for the installable apps (i.e. the /data partion). I know there are apps like App2SD or Link2SD but I want to follow another cleaner solution.
So I unlocked the bootloader and ran the cyanogenrecovery.20140922.crespo.img recovery to try repartitioning the SD card. On the host system connected to the Nexus S with an USB cable:
Code:
adb reboot bootloader
fastboot boot cyanogenrecovery.20140922.crespo.img
As you probably know the internal SD card (i.e. MMC flash) has three partitions with the following layout:
Code:
~ # 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) p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB ext4 system
2 538MB 1612MB 1074MB ext4 userdata
3 1612MB 15.9GB 14.3GB fat32 media
After a few commands using the parted utility
Code:
~ # 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)
(parted) rm 2
rm 2
(parted) rm 3
rm 3
(parted) mkpart primary ext4 538MB 3098MB
mkpart primary ext4 538MB 3098MB
(parted) name 2 userdata
name 2 userdata
(parted) mkpart primary fat32 3098MB 100%
mkpart primary fat32 3098MB 100%
(parted) name 3 media
name 3 media
(parted) p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB ext4 system
2 538MB 3098MB 2560MB ext4 userdata
3 3098MB 15.9GB 12.8GB fat32 media msftres
I successfully managed to change the layout of the disk:
Code:
~ # cd /dev/block/platform/s3c-sdhci.0/
/dev/block/platform/s3c-sdhci.0/by-name # ln -s /dev/block/mmcblk0p1 system
/dev/block/platform/s3c-sdhci.0/by-name # ln -s /dev/block/mmcblk0p2 userdata
/dev/block/platform/s3c-sdhci.0/by-name # ln -s /dev/block/mmcblk0p3 media
/dev/block/platform/s3c-sdhci.0/by-name # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 193.1M 136.0K 193.0M 0% /dev
tmpfs 193.1M 12.0K 193.1M 0% /tmp
tmpfs 193.1M 0 193.1M 0% /storage
tmpfs 193.1M 0 193.1M 0% /mnt/secure
tmpfs 193.1M 0 193.1M 0% /mnt/fuse
/dev/block/mtdblock4 469.5M 2.3M 467.2M 0% /cache
/dev/block/vold/179:3
11.9G 1.0G 10.9G 8% /storage/sdcard0
/dev/block/platform/s3c-sdhci.0/by-name/userdata
2.3G 132.0M 2.1G 6% /data
Up to here everthing looks fine.... So where it he problem? As soon as I reboot the partition layout is lost :crying: (this already happens in the recovery boot without booting the system regularly).
What am I doing wrong? Is the bootloader a supervisor of the partition layout correcting any difference comparing to a predefined value? If I try to boot the system I am asked about a password to decrypt the data partition, I guess Android doesn't find any useful file in the data partition so it thinks the partition is crypted
shouldnt you flash the custom recovery for that type of partitioning?
Sent from my Nexus S using XDA Premium 4 mobile app
g33k0 b3lk0w said:
shouldnt you flash the custom recovery for that type of partitioning?
Click to expand...
Click to collapse
First of all the procedure with Clockworkmod recovery doesn't work. Nevertheless that procedure is not what I want to obtain. because the partitioning done with CWM would divide the original FAT32 partition in two parts, the first will be dedicated to Link2SD or similar apps (so it will be an ext4) and the second to the FAT32 partition. In this way the partition layout would be:
Code:
/dev/block/mmcblk0 -> system partiotion
/dev/block/mmcblk1 -> userdata partition
/dev/block/mmcblk2 -> additional userdata partition for Link2SD or similar apps
/dev/block/mmcblk3 -> FAT32 partition
I don't see the reason in using 2 userdata partions + LinkSD when it's clearly easier to just enlarge the /dev/block/mmcblk1 partition. Moreover this solution preserves the size of the system partition but eventually I want to increase also that (for instance CM11 + gapps need more space).
I even tried chaning only the original FAT32 partition mimicking the 4 partition layout described above but as soon as I reboot I loose the changes. I suspect the problem is due to the bootloader which checks the partion layout during boot and restores the PIT
@efferre
Have you seen this? I have managed to manipulate succesfully around the nexus s storage. I am going to upload the latest cm11 m12 rom in the next couple of days.
KreAch3R said:
Have you seen this? I have managed to manipulate succesfully around the nexus s storage. I am going to upload the latest cm11 m12 rom in the next couple of days.
Click to expand...
Click to collapse
Yes, I have seen your post but I haven't tried yet that solution up to now. I prefer keeping the things simple
As the partition layout on the eMMC is using the new GPT standard (besides the MBR), I have also tried with gdisk (after having crosscompiled for ARM), a tool which is GPT-aware. Same result
Last step, I want to play with the PIT data. I have found heimdall which is capable to dump PIT data and later write back a modified version as done here using PITMagic.
Here is the PIT dump I get after putting the phone in download mode:
Code:
heimdall print-pit --file i9023.pit.orig
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Entry Count: 16
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 0
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: IPBL
Flash Filename: bootloader.img
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 1
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 7
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL
Flash Filename:
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 2
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 7
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename:
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 3
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename:
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 4
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 5
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MISC
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 5
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 6
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 7
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1878
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #8 ---
Binary Type: 1 (CP)
Device Type: 0 (OneNAND)
Identifier: 8
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 54
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: radio.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 9
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 27
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename:
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 10
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DGS
Flash Filename: dgs.img
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 0
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PGPT
Flash Filename: emmc.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 1048576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 2097152
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 33554432
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MEDIA
Flash Filename: media.img
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 33
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SGPT
Flash Filename:
FOTA Filename:
but I have a few doubts:
can I write back the modified PIT (on the eMMC part) without having to flash back the OneNand parts (i.e. the repartitioning is touching only the modified parts of the PIT, in my case only the eMMC)?
after looking at the PIT sections, in particular at #14, I see a discrepancy because it says that the size of the MEDIA partition is more than 17GB which is of course not possible because the whole eMMC is only 16GB (I have opened a ticket for @benjamin)
This is exactly what I wanted to do on my phone, but I don't have too much spare time at the moment to experiment with it.
It's a bad news that it doesn't seem to work (my original idea was to follow this approach: http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058 ). That tutorial says that "you have to re-flash your rom", did you re-flash it after re-partitioning the drive?
@efferre
Unfortunately, this is too low level for me. I have never messed around with partitions besides the normal PC formatting stuff. I just wanted to let you know that you can re-partition your Nexus S however you want using lvm. I have a very functional Nexus S with a combined 16GB storage (just like the newer smartphones) without any loss of performance (at least with my usage).
Good luck with your endeavors!
ekerazha said:
That tutorial says that "you have to re-flash your rom", did you re-flash it after re-partitioning the drive?
Click to expand...
Click to collapse
I don't think the flashing of the ROM changes the PIT and that procedure you pointed is for a Sony Xperia S device (i.e. not Samsung so I don't know if it has even a PIT), I think the reflashing is mandatory only when you change the /system partition.
Out of curiosity I have retested again the procedure changing the partition table with gdisk in recovery mode and, during the same session, uploading cm-10.2.1-crespo.zip with adb sideload. After the reboot the old partition table is recovered to the original values. The data in the media partition have not been touched, only the partition layout is changed by the bootloader.
Looking at the R880 source, the SBL is playing with the partition table so I'm pretty convinced that I need to upgrade the PIT, probably it's only necessary to change the PIT itself and the bootloader will change the partition layout for me
The next step would be to use heimdall to change the PIT but, as written above, I have a doubt of the data it reports dumping the current PIT so I want to wait for Benjamin's comment about the correctness of the dumped PIT data (do you know if it's possible to get the PIT with Odin for a comparison?) and some details the procedure heimdall follows.
For completeness, from the PIT acquired with heimdall, here is the calculated layout of the eMMC memory:
Code:
entry start stop size
11 0 1048575 1048576 (1 MiB)
12 1048576 537919487 536870912 (512 MiB)
13 537919488 1611661311 1073741824 (1 GiB)
14 1611661312 18791530495 17179869184 (16 GiB) ?????
15 18791530496 18791547391 16896 (16.5 kiB)
while this is the layout returned by gdisk:
Code:
~ # sgdisk -p /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31105024 sectors, 14.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 31104990
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 1050623 512.0 MiB 0700 system
2 1050624 3147775 1024.0 MiB 0700 userdata
3 3147776 31104990 13.3 GiB 0700 media
As you can see there is a discrepancy in the media partition size (14th entry of the PIT).
I thought the same approach used for the Xperia S would also work on the Nexus S. Unfortunately, I don't have any experience with this "PIT" and I never really used Odin as I always flashed everything through fastboot (the Nexus way).
ekerazha said:
I thought the same approach used for the Xperia S would also work on the Nexus S. Unfortunately, I don't have any experience with this "PIT" and I never really used Odin as I always flashed everything through fastboot (the Nexus way).
Click to expand...
Click to collapse
Yes, me too, up to now I have always used fastboot to flash images. I'm afraid of screwing up the device following other procedure so I want to be 100% before trying anything with heimdall.
PIT is the acronym of Partition Information Table, it's something typical of Samsung devices and it is somewhere hidden in the flash (more information in this thread). For instance for the Galaxy Nexus I have found some code here which references to its structure and location but nothing specific for the Nexus S.
Let me know if you can manage to change the partition layout without using LVM
I have problem with unbricking Lumia 520. I've bricked it while flashing engineering SBL3 on Windows 10 with Windows 8.1 FFU. Phone was stuck on 05C6:F006 mode. I switched mode by shorting fourth JTAG pin, now it boots in QHSUSB_DLOAD (05C6:9008). But i can't flash firmware. Tried many .hex files, same effect...
Log:
Code:
c:\Lumia>thor2 -mode emergency -hexfile hex.hex -mbnfile GPT0.bin -orig_gpt
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode emergency -hexfile hex.hex -mbnfile GPT0.bin -orig_gpt
Process started Sat Aug 13 20:03:36 2016
Logging to file C:\Users\gabixdev\AppData\Local\Temp\thor2_win_20160813200336_ThreadId-2248.log
Debugging enabled for emergency
Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Connection to DLOAD mode succeeded
Get Dload parameters
Sending HEX flasher to the device
Sending GO command if HEX flasher successfully uploaded.
Emergency Programmer V1 version 2014.10.31.001
Mbn download selected
Waiting for connection to flash programmer
Connecting to flash programmer
Received valid HELLO_RSP
Safe version=true, transfer size=15360
Received valid SECURITY_RSP
Successfully connected to flash programmer
Connection to flash programmer succeeded
Uploading bootloader(s), UEFI, etc from MBN image to the eMMC. This will take up to 20 seconds
Reading GPT from binary
-- GPT STARTs--
name: DPP
startLBA: 4096
endLBA: 20479
size: 0x0000000000800000 bytes
attributes: 0x0
name: MODEM_FSG
startLBA: 20480
endLBA: 26623
size: 0x0000000000300000 bytes
attributes: 0x0
name: SSD
startLBA: 28672
endLBA: 28703
size: 0x0000000000004000 bytes
attributes: 0x0
name: SBL1
startLBA: 32768
endLBA: 35767
size: 0x0000000000177000 bytes
attributes: 0x0
name: SBL2
startLBA: 36864
endLBA: 39863
size: 0x0000000000177000 bytes
attributes: 0x0
name: SBL3
startLBA: 40960
endLBA: 45055
size: 0x0000000000200000 bytes
attributes: 0x0
name: UEFI
startLBA: 45056
endLBA: 50055
size: 0x0000000000271000 bytes
attributes: 0x0
name: RPM
startLBA: 53248
endLBA: 54247
size: 0x000000000007d000 bytes
attributes: 0x0
name: TZ
startLBA: 57344
endLBA: 58343
size: 0x000000000007d000 bytes
attributes: 0x0
name: WINSECAPP
startLBA: 61440
endLBA: 62463
size: 0x0000000000080000 bytes
attributes: 0x0
name: BACKUP_SBL1
startLBA: 65536
endLBA: 68535
size: 0x0000000000177000 bytes
attributes: 0x0
name: BACKUP_SBL2
startLBA: 69632
endLBA: 72631
size: 0x0000000000177000 bytes
attributes: 0x0
name: BACKUP_SBL3
startLBA: 73728
endLBA: 77823
size: 0x0000000000200000 bytes
attributes: 0x0
name: BACKUP_UEFI
startLBA: 77824
endLBA: 82823
size: 0x0000000000271000 bytes
attributes: 0x0
name: BACKUP_RPM
startLBA: 86016
endLBA: 87015
size: 0x000000000007d000 bytes
attributes: 0x0
name: BACKUP_TZ
startLBA: 90112
endLBA: 91111
size: 0x000000000007d000 bytes
attributes: 0x0
name: BACKUP_WINSECAPP
startLBA: 94208
endLBA: 95231
size: 0x0000000000080000 bytes
attributes: 0x0
name: UEFI_BS_NV
startLBA: 98304
endLBA: 98815
size: 0x0000000000040000 bytes
attributes: 0x0
name: UEFI_NV
startLBA: 102400
endLBA: 102911
size: 0x0000000000040000 bytes
attributes: 0x0
name: PLAT
startLBA: 106496
endLBA: 122879
size: 0x0000000000800000 bytes
attributes: 0x0
name: EFIESP
startLBA: 131072
endLBA: 262143
size: 0x0000000004000000 bytes
attributes: 0x0
name: MODEM_FS1
startLBA: 262144
endLBA: 268287
size: 0x0000000000300000 bytes
attributes: 0x0
name: MODEM_FS2
startLBA: 270336
endLBA: 276479
size: 0x0000000000300000 bytes
attributes: 0x0
name: UEFI_RT_NV
startLBA: 278528
endLBA: 279039
size: 0x0000000000040000 bytes
attributes: 0x0
name: UEFI_RT_NV_RPMB
startLBA: 282624
endLBA: 282879
size: 0x0000000000020000 bytes
attributes: 0x0
-- GPT ENDs --
Sending OPEN_MULTI_REQ
Message send failed with error code -1
Failed to get response to OPEN_MULTI_REQ
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 18.00 seconds.
THOR2_EMERGENCYFLASHV1_ERROR_MSG_SEND_RECEIVE_FAILED
THOR2 1.8.2.18 exited with error code 85021 (0x14C1D)
SHA-1 of HEX.hex: 868570B59B84852AFE74DEF65C166AF2EC054742
you can teamview me?
Is there a result by now?
Hello Guy, Can you use teamviewer?
download it and tell me to my mail - [email protected]
i will fix it. or just go to http://forum.xda-developers.com/win...nt/fix-dead-phone-bricked-bootloader-t3496232 maybe it can help you
Following lineage os' official guide for the verizon gs5 ...
I'm afraid that my problem may be coming from me not doing something before even attempting to install lineage os on my phone. Something verizon specific... I read somewhere about an activation lock... but I'm unsure of if I need to do this, as the lineage os guide doesn't call for it explicitly.
In reference to the guide's basic requirements, I have:
"
1. Make sure your computer has adb. Setup instructions can be found here.
2. Enable USB debugging on your device.
"
Continuing, with the guide, I ran:
```heimdall print-pit: ```
(and got) ...
```
Entry Count: 30
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 14137
Unknown 6: 52
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 30720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APNHLOS
Flash Filename: NON-HLOS.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 38912
Partition Block Count: 117632
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 156544
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash Filename: sbl1.mbn
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 157568
Partition Block Count: 128
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DBI
Flash Filename: sdi.mbn
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 157696
Partition Block Count: 64
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DDR
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 157760
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ABOOT
Flash Filename: aboot.mbn
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 161856
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RPM
Flash Filename: rpm.mbn
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 162880
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZ
Flash Filename: tz.mbn
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 163904
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSG
Flash Filename:
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 170048
Partition Block Count: 14272
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PAD
Flash Filename:
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 184320
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 204800
Partition Block Count: 28672
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img.ext4
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 233472
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST1
Flash Filename: nvrebuild1.bin
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 239616
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST2
Flash Filename: nvrebuild2.bin
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 245760
Partition Block Count: 26624
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 272384
Partition Block Count: 30720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 303104
Partition Block Count: 26624
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FOTA
Flash Filename:
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 329728
Partition Block Count: 14318
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BACKUP
Flash Filename:
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 344046
Partition Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSC
Flash Filename:
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 344048
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SSD
Flash Filename:
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 344064
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSIST
Flash Filename: persist.img.ext4
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 360448
Partition Block Count: 18432
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img.ext4
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 378880
Partition Block Count: 6144000
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img.ext4
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 24
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 6522880
Partition Block Count: 2097152
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img.ext4
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 25
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 8620032
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CARRIER
Flash Filename: carrier.img.ext4
FOTA Filename:
--- Entry #25 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 26
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 8640512
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img.ext4
FOTA Filename: remained
--- Entry #26 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 34
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PGPT
Flash Filename: pgpt.img
FOTA Filename:
--- Entry #27 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: MSM8974.pit
FOTA Filename:
--- Entry #28 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 72
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5
Flash Filename: md5.img
FOTA Filename:
--- Entry #29 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 73
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30777311
Partition Block Count: 33
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SGPT
Flash Filename: sgpt.img
FOTA Filename:
Ending session...
Rebooting device...
Releasing device interface...
```
This seemed like a success. So then I continued with the guide and ran:
```
heimdall flash --RECOVERY <recovery_filename>.img --no-reboot:
```
(and got) ...
```
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Releasing device interface...
```
I've tried using a different usb port, resetting the device, restarting my pc, trying two different versions of Heimdall....
I'm hoping this problem is just due to something I foolishly overlooked.
Thank you for the help.
I am running Manjaro linux, as well.
I have a verizon gs5 cid 11...
Doesn't seem to be possible to unlock the bootloader.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
FLASHING THIS WILL DELETE /BOOT AND /RECOVERY PARTITION!!
VERY IMPORTANT: YOU WON'T BE ABLE TO FLASH TWRP OR ANY OTHER RECOVERY, AS /RECOVERY WILL BE SHRINKED TO 23 MiB AND TWRP SIZE IS AT LEAST 28 MiB.
this is a repartitioner for /boot partition (to 47 MiB instead of 32 MiB), to make it to work i had to shrink /recovery partition (as it's the nearest partition; /boot is /dev/block/mmcblk0p10 and /recovery is /dev/block/mmcblk0p11), it works in this way:
/tmp/sgdisk $DK --delete 10 -> deletes /boot
/tmp/sgdisk $DK --delete 11 -> deletes /recovery
/tmp/sgdisk $DK --new=10:124928:221184 -> creates /boot again, with Block Size: 124.928 and with Block Count: 96.256
/tmp/sgdisk $DK --new=11:221184:268288 -> creates /recovery again with Block Size: 268.288 and with Block Count: 47.104
to get some infos from stock j6 PIT file i used Pit Magic (https://forum.xda-developers.com/t/...-samsung-pit-creator-editor-analyzer.1916936/)
Stock BOOT Partition:
Code:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 10
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 124.928
Block Count: 65.536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash FileName: boot.img
FOTA FileName:
Stock RECOVERY Partition:
Code:
----------------------------------------------------------
Entry Memory Address: 0x7D8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 11
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 190.464
Block Count: 77.824
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash FileName: recovery.img
FOTA FileName:
To get these numbers i just did some mathematical proportions:
using a unix blocks to megabytes converter (http://www.unitconversion.org/data-storage/blocks-to-megabytes-conversion.html) i found that 65.536 blocks correspond to 32 MiB.
so i did:
Code:
65.536 : 32 = x : 47
where 65.536 is the block count, 32 are the corrisponding MiB, x is the block count to find to get 47 MiB and 47 are the MiB i wanted to have.
so i just did: (65.536 * 47) / 32 = 96.265 -> corresponding to 47 MiB.
CREDITS: @ProtoDeVNan0 for his EPR