[TOOL][NOT TESTED] BOOT partition repartitioner - Samsung Galaxy J6 Guides, News, & Discussion

[TOOL][NOT TESTED] BOOT partition repartitioner - Samsung Galaxy J6 Guides, News, & Discussion

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

Related

[INDEX][SGH-T599x][FIRMWARE]

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

[FIRMWARE] AT&T Galaxy Note 3 N900A UNEXE STOCK + Analysis PIT + EFS BACKUP

Hi guys!
As you know, flashing of the older firmware is not possible because of the boot secure into bootloader.
But there is a way to downgrade the firmware without flashing bootloader that can't be to downgrade. But unfortunately it will increase the value KNOX WARRANTY BIT 0x1.
So I extracted parts of the firmware for your convenience and an opportunity to downgrade or flashing individual parts of stock firmware..
AP = Android Platform
BL = Bootloader
CP = Modem (radio)
CSC = Region & mobile operator
pit = Partition table
Download:
N900AUCUBMI1
{
"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"
}
***
N900AUCUBMI9
N900AUCUBMJ5 - without system
Special tnx designgears for OneClick.exe
How to flash:

----------------------------------------------------------
PIT Magic - Analysis for: HLTE_USA_ATT_32G.pit
----------------------------------------------------------
Code:
<<< Pit File Start >>>
----------------------------------------------------------
<<< Unknown PIT File Properties >>>
----------------------------------------------------------
Entry Count: 29
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 14137
Unknown 6: 52
Unknown 7: 0
Unknown 8: 0
----------------------------------------------------------
<<< PIT File Entries >>>
----------------------------------------------------------
----------------------------------------------------------
Entry Memory Address: 0x1C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 1
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 8*192
Block Count: 30*720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APNHLOS
Flash FileName: NON-HLOS.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xA0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 2
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 38*912
Block Count: 117*632
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash FileName: modem.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x124
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 3
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 156*544
Block Count: 1*024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash FileName: sbl1.mbn
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x1A8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 4
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 157*568
Block Count: 64
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DBI
Flash FileName: sdi.mbn
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x22C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 5
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 157*632
Block Count: 64
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DDR
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x2B0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 6
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 157*696
Block Count: 4*096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ABOOT
Flash FileName: aboot.mbn
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x334
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 7
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 161*792
Block Count: 1*024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RPM
Flash FileName: rpm.mbn
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x3B8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 8
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 162*816
Block Count: 1*024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZ
Flash FileName: tz.mbn
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x43C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 9
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 163*840
Block Count: 20*480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PAD
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x4C0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 10
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 184*320
Block Count: 20*480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash FileName: param.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x544
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 11
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 204*800
Block Count: 28*672
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash FileName: efs.img.ext4
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x5C8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 12
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 233*472
Block Count: 6*144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST1
Flash FileName: nvrebuild1.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x64C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 13
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 239*616
Block Count: 6*144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST2
Flash FileName: nvrebuild2.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x6D0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 14
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 245*760
Block Count: 22*528
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash FileName: boot.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 15
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 268*288
Block Count: 26*624
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash FileName: recovery.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x7D8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 16
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 294*912
Block Count: 26*624
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FOTA
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x85C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 17
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 321*536
Block Count: 14*318
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BACKUP
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x8E0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 18
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 335*854
Block Count: 6*144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSG
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x964
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 19
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 341*998
Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSC
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x9E8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 20
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 342*000
Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SSD
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xA6C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 21
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 342*016
Block Count: 16*384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSIST
Flash FileName: persist.img.ext4
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xAF0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 22
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 358*400
Block Count: 18*432
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash FileName: persdata.img.ext4
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xB74
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 23
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 376*832
Block Count: 5*122*048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash FileName: system.img.ext4
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xBF8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 24
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 5*498*880
Block Count: 1*024*000
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash FileName: cache.img.ext4
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xC7C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 25
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 6*522*880
Block Count:
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash FileName: userdata.img.ext4
FOTA FileName: remained
----------------------------------------------------------
Entry Memory Address: 0xD00
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 70
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size:
Block Count: 34
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PGPT
Flash FileName: pgpt.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xD84
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 71
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 34
Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash FileName: MSM8974.pit
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xE08
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 72
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 50
Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5
Flash FileName: md5.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xE8C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 73
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 61*071*327
Block Count: 33
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SGPT
Flash FileName: sgpt.img
FOTA FileName:
----------------------------------------------------------
<<< Pit File End >>>
----------------------------------------------------------

A.S._id said:
Added N900AUCUBMI9
Click to expand...
Click to collapse
I can used this in odin ????

SAMSUNG AT&T Galaxy Note 3 N900A EFS BACKUP/RESTORE
Instructions:
! Need for backup Root access and debugging USB
1. Extract from the zip and run .bat file
2. Is okay to your PC and follow the menu
Automatically create a text file of all the parameters of the device at the time of the copy
Automatic backup of efs:
* Odin flash file -. tar.md5,
* dd copy - raw.img
* tar.gz archive (need busybox)
Automatic naming of files and backup archive version of the firmware
Restore to choose from archives and backup images
Automatic start of Odin and the transition to the flashing mode when selecting Odin Restore

A.S._id said:
Of course
Click to expand...
Click to collapse
Bootloader is not been unlocked yet?

fern1221 said:
Bootloader is not been unlocked yet?
Click to expand...
Click to collapse
it's impossible - downgrade bootloader, only flash without it..

So does this mean we can now get a recovery and thus flash away. Maybe I'm not understanding what's happening here. Please go easy on me fellas.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

androidmechanic said:
So does this mean we can now get a recovery and thus flash away. Maybe I'm not understanding what's happening here. Please go easy on me fellas.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Now you can all...
You can extract any part to package into tar and flash it... but not bootloader
You can extract recovery.img, change stock recovery on cwm
You can extract system.img via dsixda kitchen and build custom zip...
You can analysis pit file and will know partition table for backup efs...
And more different things...
May be this thread better to move into development part
there she probably would have been more useful

A.S._id said:
Now you can all...
You can extract any part to package into tar and flash it... but not bootloader
You can extract recovery.img, change stock recovery on cwm
You can extract system.img via dsixda kitchen and build custom zip...
You can analysis pit file and will know partition table for backup efs...
And more different things...
May be this thread better to move into development part
there she probably would have been more useful
Click to expand...
Click to collapse
A.S., it sounds to me as you started an era of possible custom ROMs development for our N900A. Am I right?
The question I have since the first day with my phone is if it would be possible to flash the stock ROM of the N9005 (international version of the Note3) in this N900A variant. I do not use the phone in the AT&T network and would love to get rid of all AT&T stuff.
Even having the booloader locket, would this method let us able to do that?
Thanks!

cabtouch said:
A.S., it sounds to me as you started an era of possible custom ROMs development for our N900A. Am I right?
The question I have since the first day with my phone is if it would be possible to flash the stock ROM of the N9005 (international version of the Note3) in this N900A variant. I do not use the phone in the AT&T network and would love to get rid of all AT&T stuff.
Even having the booloader locket, would this method let us able to do that?
Thanks!
Click to expand...
Click to collapse
No, I'm hasn't n900a, but has n900 (exinos octa) and don't wanna to experiment with n900a...
To me was interesting to see firmware n900a, but don't find it.
So I extracted this from oneclickbin.exe and uploaded for users...

Would totally like to see what Designgears thinks of all this!

Can someone please extract the following files for me please
System/lib:
libaudio-ril.so
libreference-ril.so
libril.so
libril-qcril-hook-oem.so
librilutils.so
libsec-ril.so
libsecril-client.so
Need these files to make a flashable ril for tmob note 3 device for use in att.
More info http://forum.xda-developers.com/showthread.php?p=46995808#post46995808
Thanks

Pikezer1337 said:
Would totally like to see what Designgears thinks of all this!
Click to expand...
Click to collapse
But what hi can to say?
I'm extract this OneClick.exe without any scripts or bats on my UBUNTU 13.04 via Okteta hex editor...
p.s. I asked his, how to extract firmware from .exe before relise his .bat, but he don't answer me, so I myself had to think how to do it...

aalupatti said:
Can someone please extract the following files for me please
System/lib:
libaudio-ril.so
libreference-ril.so
libril.so
libril-qcril-hook-oem.so
librilutils.so
libsec-ril.so
libsecril-client.so
Need these files to make a flashable ril for tmob note 3 device for use in att.
More info http://forum.xda-developers.com/showthread.php?p=46995808#post46995808
Thanks
Click to expand...
Click to collapse
HERE

A.S._id said:
But what hi can to say?
I'm extract this OneClick.exe without any scripts or bats on my UBUNTU 13.04 via Okteta hex editor...
p.s. I asked his, how to extract firmware from .exe before relise his .bat, but he don't answer me, so I myself had to think how to do it...
Click to expand...
Click to collapse
No sorry I phrased that wrong. I didnt mean that you stole his work I meant I wanted to see if maybe he could get something with the bootloader going from this. You have done great work and hopefully some roms can come from this.

A.S._id said:
HERE
Click to expand...
Click to collapse
Thank yo so much for the files.

A.S._id said:
HERE
Click to expand...
Click to collapse
Is it safe to flash the modem files onto a tmobile device or am i goingn to end up with a brick ?

so can I use this to completely return to factory without triggering anything?

can anyone confirm the backup in post 3 works ok?
Thanks.

Hardcore!
Hehe, I use a hex editor on windows to do the same. However, there is a tool I use to do it now, its called exodin.
I have also downgraded with the older firmware exe and never tripped knox. As did many others with the original root method.

Problem in changing the partition layout of the internal MMC SD card

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

Bricked A500FU after reboot nvbackup

Hi.
So stupidly I used an adb command that wasn't supposed to be used on my device.
While trying to make a backup of the IMEI I used adb reboot nvbackup.
After that the phone is in endless bootloops.
Already tried to restores software with kies and nothing.
If someone could help me about fixing it with Odin I would be grateful.

rmrbpt said:
Hi.
So stupidly I used an adb command that wasn't supposed to be used on my device.
While trying to make a backup of the IMEI I used adb reboot nvbackup.
After that the phone is in endless bootloops.
Already tried to restores software with kies and nothing.
If someone could help me about fixing it with Odin I would be grateful.
Click to expand...
Click to collapse
Just download latest firmware and flash with odin. If it won't work, then try with 4-file firmware.

I'm going to try flashing stock with ODIN. I already found the correct version for my phone.
About the emergency firmware.
The 4 file recovery software that I finf is only 4.4.4 and my phone already had 6.0.1.
Can flashing this older software brick it?

rmrbpt said:
I'm going to try flashing stock with ODIN. I already found the correct version for my phone.
About the emergency firmware.
The 4 file recovery software that I finf is only 4.4.4 and my phone already had 6.0.1.
Can flashing this older software brick it?
Click to expand...
Click to collapse
Have you tried odin yet?
For the 4-file you'll have to get a 6..0.1. Any specific country/carrier you need? I can try to find it.

Unfortunately I can only try it tomorrow.
I tried to find the 4 file firmware for 6.0.1 but still nothing...
My phone is an SM-500FU with no carrier from Portugal so TPH is the firmware I need.
Thanks for your help.

rmrbpt said:
Unfortunately I can only try it tomorrow.
I tried to find the 4 file firmware for 6.0.1 but still nothing...
My phone is an SM-500FU with no carrier from Portugal so TPH is the firmware I need.
Thanks for your help.
Click to expand...
Click to collapse
I got the 4-file for 6.0.1 TPH in case you'll need it.
A500FUXXS1CQC4_FUXXU1CPH3A_FUOXX1CPH1-6.0.1- [4-File].zip

I'm trying this this afternoon.
Big thanks for the file! Searched the whole web and couldn't find it.

So I tried it with only 1 file and after that with the 4 files and still nothing.
To try the "repartition" option on ODIN I need a PIT file right?

rmrbpt said:
So I tried it with only 1 file and after that with the 4 files and still nothing.
To try the "repartition" option on ODIN I need a PIT file right?
Click to expand...
Click to collapse
Oh that's a bummer! 4-files usually fixes all types of bootloops.
I'm not familiar with that "adb reboot nvbackup" command and what it is supposed to do. Makes me wonder why it still bootloops.
Hers the pit-file in case you dont have it. Just unzip.
View attachment A5ULTE_EUR_OPEN.zip

From what I could read this is a specific command to SIII. In other phones it corrupts FSG and backup partitions.
"I started looking at "FSG" and "backup" partitions since "reboot nvbackup" writes partitions modemst1 and modemst2 to Backup and FSG. In other phones this makes a backup copy. "reboot nvrestore" would restore bad modemst's mounts. In Note 3's FSG partition is a system partition. Reboot nvbackup overwrote FSG. My blocks were obviously corrupted."
https://forum.xda-developers.com/showthread.php?t=2657519
I should leave
Auto Reboot, Repartition and F. Reset Time with the tick
and
Nand Erase All, Flash Lock and T Flash deselected right?
After I try this I'm gonna send to Samsung tomorrow.
Thanks for your help.

rmrbpt said:
From what I could read this is a specific command to SIII. In other phones it corrupts FSG and backup partitions.
"I started looking at "FSG" and "backup" partitions since "reboot nvbackup" writes partitions modemst1 and modemst2 to Backup and FSG. In other phones this makes a backup copy. "reboot nvrestore" would restore bad modemst's mounts. In Note 3's FSG partition is a system partition. Reboot nvbackup overwrote FSG. My blocks were obviously corrupted."
https://forum.xda-developers.com/showthread.php?t=2657519
I should leave
Auto Reboot, Repartition and F. Reset Time with the tick
and
Nand Erase All, Flash Lock and T Flash deselected right?
After I try this I'm gonna send to Samsung tomorrow.
Thanks for your help.
Click to expand...
Click to collapse
Yes, that's correct.
I just read that link and, yeah..probably same for you. You need backup of "FSG" & "BACKUP" partitions and copy to phone.
---------- Post added at 08:26 PM ---------- Previous post was at 08:18 PM ----------
Could someone make this command in Terminal emu or adb shell to get all partitions, then post it here?
.
ls -al /dev/block/platform/soc.0/7824900.sdhci/by-name
---------- Post added at 08:41 PM ---------- Previous post was at 08:26 PM ----------
tys0n said:
Yes, that's correct.
I just read that link and, yeah..probably same for you. You need backup of "FSG" & "BACKUP" partitions and copy to phone.
---------- Post added at 08:26 PM ---------- Previous post was at 08:18 PM ----------
Could someone make this command in Terminal emu or adb shell to get all partitions, then post it here?
.
ls -al /dev/block/platform/soc.0/7824900.sdhci/by-name
Click to expand...
Click to collapse
Nvm. I got it from the pit file.
FSG is mmcblk0p9 & BACKUP is mmcblk0p19
----------------------------------------------------------
PIT Magic v1.3.10 Copyright © Gaz 2012.
----------------------------------------------------------
Analysis for: A5ULTE_EUR_OPEN.pit
----------------------------------------------------------
----------------------------------------------------------
<<< Pit File Start >>>
----------------------------------------------------------
----------------------------------------------------------
<<< PIT File Header Information >>>
----------------------------------------------------------
Header Magic: 0x12349876 (4 Bytes)
Entry Count: 31 (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: MSM8
Hexadecimal: 4D534D38
----------------------------------------------------------
Dummy Data #4 (In String and Hexadecimal Format):
----------------------------------------------------------
String: 916
Hexadecimal: 39313600
----------------------------------------------------------
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: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 8*192
Block Count: 30*720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APNHLOS
Flash FileName: NON-HLOS.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xA0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 2
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 38*912
Block Count: 117*632
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash FileName: modem.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x124
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 3
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 156*544
Block Count: 1*024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash FileName: sbl1.mbn
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x1A8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 4
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 157*568
Block Count: 64
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DDR
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x22C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 5
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 157*632
Block Count: 4*096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ABOOT
Flash FileName: aboot.mbn
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x2B0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 6
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 161*728
Block Count: 1*024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RPM
Flash FileName: rpm.mbn
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x334
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 7
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 162*752
Block Count: 1*024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: QSEE
Flash FileName: tz.mbn
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x3B8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 8
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 163*776
Block Count: 1*024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: QHEE
Flash FileName: hyp.mbn
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x43C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 9
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 164*800
Block Count: 6*144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSG
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x4C0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 10
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 170*944
Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: sec
Flash FileName: sec.dat
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x544
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 11
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 170*976
Block Count: 21*536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PAD
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x5C8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 12
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 192*512
Block Count: 20*480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash FileName: param.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x64C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 13
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 212*992
Block Count: 28*672
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash FileName: efs.img.ext4
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x6D0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 14
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 241*664
Block Count: 6*144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST1
Flash FileName: nvrebuild1.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 15
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 247*808
Block Count: 6*144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST2
Flash FileName: nvrebuild2.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x7D8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 16
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 253*952
Block Count: 26*624
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash FileName: boot.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x85C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 17
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 280*576
Block Count: 30*720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash FileName: recovery.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x8E0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 18
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 311*296
Block Count: 10*242
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FOTA
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x964
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 19
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 321*538
Block Count: 14*318
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BACKUP
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x9E8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 20
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 335*856
Block Count: 6*144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSC
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xA6C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 21
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 342*000
Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SSD
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xAF0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 22
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 342*016
Block Count: 16*384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSIST
Flash FileName: persist.img.ext4
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xB74
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 23
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 358*400
Block Count: 18*432
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash FileName: persdata.img.ext4
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xBF8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 24
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 376*832
Block Count: 4*915*200
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash FileName: system.img.ext4
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xC7C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 25
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 5*292*032
Block Count: 409*600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash FileName: cache.img.ext4
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xD00
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 26
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 5*701*632
Block Count: 122*880
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash FileName: hidden.img.ext4
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xD84
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 27
Attribute: 5 (READ / WRITE)
Update Attribute: 5 (FOTA)
Block Size: 5*824*512
Block Count:
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash FileName: userdata.img.ext4
FOTA FileName: remained
----------------------------------------------------------
Entry Memory Address: 0xE08
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 70
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size:
Block Count: 34
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PGPT
Flash FileName: pgpt.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xE8C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 71
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 34
Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash FileName: MSM8974.pit
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xF10
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 72
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 50
Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5
Flash FileName: md5.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xF94
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 73
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 15*269*855
Block Count: 33
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SGPT
Flash FileName: sgpt.img
FOTA FileName:
----------------------------------------------------------
<<< Pit File End >>>
----------------------------------------------------------

Tried it with the PIT file also.
Still nothing.
As I still have knox 0x0 I'm leaving it in Samsung tomorrow.
If they fix it fine. If they don't then I'm gonna really mess with it. Custom recovery, dump the partitions Hex edit them and try to reupload them to the phone.
Thanks for your help anyway.

Ok good Hope they fix it.
Otherwise you'll have to count on someone making backups of those partitions for you.
I'd do it for you if I had the device.
Good luck at samsung!
Skickat från min SM-A310F via Tapatalk

Samsung support fixed it
Thank you @tys0n
Thread can be closed.

Basic requirements for installing Lineage OS/Heimdall help

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.

Database Users

welcome