WARNING!
I'm not responsible for anything that happens to your device after using this guide
Use at your own risk!​
CREDITS to @lch920619x for the original guide, @aboodyaiman for teaching me how to convert the ROM in the first place. This small guide is simply a newer one with updated links and steps on converting ROMs to work with 11GB pit. I'll add images when I have time yay
You will need THIS PACKAGE for converting between 8GB and 11GB pits, THIS PACKAGE for converting the ROMs you want to work with 11GB pit.
If you haven't download Odin yet then here is ODIN 3.12.3 ( you will need it to convert PIT between 8GB & 11GB
Installing the PIT files
1. Download the PIT Package
2. Flash pit your desired pit (PIT)
<8GB.pit to convert to the standard 8GB data partion - RECOMMENDED>
<11GB.pit to convert to the 11GB data partition>
3. Flash CF-Auto-Root (AP)
4. Wipe Cache & Data in stock recovery.
5. Flash modem (AP)
6. Flash param.bin (CP)
7. Flash custom recovery (AP)
8. Format all partitions using TWRP
9. Optional: Update to latest TWRP if you wish
Converting ROMs to work with 11GB pit
<Haven't test on Alberto's Lineage since I don't have the device anymore, REMEMBER that Alberto said he is NOT supporting 11GB pit for now>
1. Head to Python website, download and install Python
2. Download ROM CONVERT PACKAGE and extract it anywhere
3. Extract File context, system.new.dat and system.transfer.list from the ROM zip you want to convert in to where you extract the ROM CONVERT PACKAGE
4. Execute extractor and press 1, then press Enter three times
5. It will provide system folder when it's done
6. Extract boot.img, meta folder and file context from the original ROM zip again.
7. Replace updater-script with the one in the ROM COVERT PACKAGE
8. Add all to zip archive and flash your new 11GB pit compatible ROM
sry i am a newbee for packing and unpacking rom. I want to flash ALE95 n5 7.1. but since it doesnt supports 11gb pit. i am giving a try.
1. i downloaded and install python 2.x.x
2. now i am stuck at how to extract file context, system.new.dat, system.transfer.list from ALE95.
i googled much, i downloaded filecontext tools, system.extractor.win, rom convert package all. but how to use python and extract those files and repacking i duuno. i did bit of research in google also.. but need some guidance please
can you make video review about how to convert roms from 8 gb to 11gb
Related
finally! succesfully patch my mk4 rom using heimdall on osx, now my wifi is working thanks so much doc... in case somebody wants to know how
dr ketans wifi patch http://forum.xda-developers.com/showthread.php?t=2531965
1: download GUI Tar https://www.macupdate.com/app/mac/14503/gui-tar
2. download dr ketan wifi patch, extract contents
3. edit file patch.tar.md5 to patch.tar
4. extract the contents of patch.tar using GUI Tar, files are param.bin, tz.img
5. from heimdalls utilities tab download your PIT file
6. go to flash tab, browse through your downloaded pit file.
7. under partitions press add, in partition details > partition name choose tzsw, in file choose tz.img (the file you extracted using GUI Tar)
8. again, under partitions press add, in partition details > partition name choose param, in file choose param.bin (the file you extracted using GUITar)
9. click restart, your device will reboot after flashing
hit thanks if u think i helped you
thanks again dr ketan for your awesome patch....
Reference Thread
Samsung Galaxy S4 I9500 Lollipop Modems and Bootloaders​
Technical background
Actually, we have a dedicated thread that should host updated modems and bootloaders (for both I9500 and I9505). However, the thread was no longer updated since 2014, even the OP is never online since 2014. So, I created this thread to host all Lollipop bootloaders and modems for I9500.
Why do need we update our modem and bootloader?
As you may know, firmwares are updated often, as long as our device still get support from Samsung. Custom ROMs does the same. And often new updates are giving problems with incorrect version of your modem or bootloader (like you installed Lollipop firmware on KitKat bootloader). We need to update our modem and bootloader to ensure the maximum compatibility available and will keep us secure, everywhere (althrough we need an additional protection too).
Installation procedure
Installation via recovery (modem only):
Make sure you've installed the latest version of CWM/PhilZ/TWRP. I'd recommend TWRP.
Make sure you've done an EFS backup (just to be safe).
Reboot to Recovery mode by combination of Power+Home+Vol(+) buttons.
a. For CWM, select Install zip from sdcard.
b. For PhilZ, select Install zip then select Install zip from sdcard0 or sdcard1.
c. For TWRP, select Install.
Navigate to modem zip.
a. For CWM/PhilZ, select "Yes, instal ..."
b. For TWRP, swipe Install button.
Reboot to system.
If after installation of modem your baseband version is Unknown, restore your EFS backup.
Installation via Odin (modem and/or bootloader):
Make sure you've installed the latest version of Samsung USB Drivers on your computer.
Make sure you've done an EFS backup (just to be safe).
Reboot to Download mode by combination of Power+Home+Vol(-) buttons and proceed by pressing Vol(+).
Plug your phone to your computer.
Extract the archive (if compressed).
Open Odin and select modem and/or bootloader .tar or .tar.md5 file(s) into the corresponding location.
Select Start to proceed.
In case if your modem and/or bootloader isn't updated, repeat step 3-6, untick Auto Reboot, and select Start to proceed. Then, do a hard reboot by holding power button for 10 seconds.
If after installation of modem your baseband version is Unknown, restore your EFS backup.
How to contribute
You're welcome to send your contribution. Make sure that version you want to contribute isn't listed on this thread. You need two files: modem.bin and sboot.bin. You could obtain by extracting both files from stock firmware .tar.md5 using 7-Zip on Windows or Archive Manager on Ubuntu (remove .md5 extension first).
Packing into .tar file(s) (modem and/or bootloader):
You need an Ubuntu-installed machine or any distribution based on Ubuntu installed on your machine.
Move both files into your working directory.
Open Terminal and move it into your working directory. Example, if you're working on Desktop folder, enter this command:
Code:
$ cd Desktop
Pack one by one files using these commands:
Code:
$ tar -h ustar -c modem.bin > MODEMVER.tar [COLOR=Green]# Modem[/COLOR]
$ tar -h ustar -c sboot.bin > BOOTLOADERVER.tar [COLOR=Green]# Bootloader[/COLOR]
Replace MODEMVER.tar and/or BOOTLOADERVER.tar with version you're packing. Example, if you're packing I9500UBUHOK1 modem, change MODEMVER.tar to I9500UBUHOK1-MODEM.tar.
Add md5 checksum into .tar file(s) using this command:
Code:
$ md5sum -t PACKAGE.tar >> PACKAGE.tar
Replace PACKAGE.tar with .tar file(s) you've created. If you've more than one .tar file, insert one first and repeat this for another one.
Finally, rename file(s) using this command:
Code:
$ mv PACKAGE.tar PACKAGE.tar.md5
Replace PACKAGE with .tar file(s) you've created (without .tar extension).
Compress it into zip file(s) then attach it here or upload to somewhere else.
If you're a bit lazy to do all these steps above, grab any Odin flashable .tar files, delete everything and replace it with modem.bin or sboot.bin then rename it.
Packing into .zip file (modem only):
Download the attached template below.
Open it with any archiver app.
Put modem.bin inside modem folder.
Rename the .zip file to the version you've included.
Attach it here or upload it somewhere else.
This list is incomplete. Help me to complete this list by contributing.
Note: Sorted by the changelist number.
Latest:
UBUHPB2 (Latin America)
Changelist number: 7068753
Download: Modem Zip - Odin | Bootloader
UBUHOK2 (Latin America)
Modem version: UBUHOK1
Changelist number: 6332925
Download: Modem Zip
XXUHPB3 (Middle East and Africa)
Modem version: XXUHPB1
Changelist number: 6164126
Download: Modem Zip - Odin | Bootloader
XXUHOC6 (South East Asia)
Modem version: DXUHOA1
Changelist number: 3943544
Download: Modem Zip
Thread closed at OP's request.
I have the stock boot image file of SM-G955FD Oreo (8.0.0) Indian firmware
in .tar.md5 format I need it to be converted to .img as .tar.md5 format is not supported by MagiskManager for patching.
Here is the stock boot image of SM-G955FD Oreo (8.0.0) Indian firmware :
http://www9.zippyshare.com/v/HVR3TIEb/file.html
Please any body provide me this boot image file in .img format or tell me an easy way to do so.
Thanks a lot in anticipation!
You don't convert .tar.md5 files into .img. .tar.md5 is just a regular tar archive (ustar format) with md5 checksum appended to it. You can unpack it as any other tar archive, it contains the device images you are probably asking for.
Oreo images are lz4-compressed, so you also need to decompress them, after that you will be left with usable .img files for different partitions.
Edit: Here's G955FXXU1CRB7 boot.img
Can you give me link to Galaxy S3 SGH T999N boot.img please
I have a problem. I am new in the domain of android customization and that is why I am testing.
I have a PDA file for my old GT-S6102 Galaxy Y, which contains the following files:
boot.img
param.lfs
Sbl.bin
system.img
userdata.img
I also downloaded a custom ROM from the internet called evo_x2.1 (evo_x2.1.zip) which contains the following files:
META-INF (folder)
system (folder)
installbusybox (file)
Normaly this file is supposed to be put on /sdcard and update the system partition only from recovery mode.
But I have a question: Can I edit my PDA file mentioned above by inserting this ROM in it? (so that when I flash this firmware with odin into my phone I will no longer have to update it with this ROM separately afterwards, manually)
I tried to create a system.img which contained the files included in the ROM file and replaced the system.img in the PDA file with the system.img I just created from the ROM file.But when I try to flash the PDA with Odin, it crashes while analyzing the file.
NOTE: there is no md5 hashsum at the end of the PDA so there is no problem concerning the integrity of the file.
Thank you, and any observations are welcomed.
ReznicencuBogdan said:
I have a problem. I am new in the domain of android customization and that is why I am testing. I have a PDA file for my old GT-S6102 Galaxy Y,........
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is also specific to your device as well.
https://forum.xda-developers.com/galaxy-y
With that guidance...
Your best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=2063534
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
ReznicencuBogdan said:
I have a problem. I am new in the domain of android customization and that is why I am testing.
I have a PDA file for my old GT-S6102 Galaxy Y, which contains the following files:
boot.img
param.lfs
Sbl.bin
system.img
userdata.img
I also downloaded a custom ROM from the internet called evo_x2.1 (evo_x2.1.zip) which contains the following files:
META-INF (folder)
system (folder)
installbusybox (file)
Normaly this file is supposed to be put on /sdcard and update the system partition only from recovery mode.
But I have a question: Can I edit my PDA file mentioned above by inserting this ROM in it? (so that when I flash this firmware with odin into my phone I will no longer have to update it with this ROM separately afterwards, manually)
I tried to create a system.img which contained the files included in the ROM file and replaced the system.img in the PDA file with the system.img I just created from the ROM file.But when I try to flash the PDA with Odin, it crashes while analyzing the file.
NOTE: there is no md5 hashsum at the end of the PDA so there is no problem concerning the integrity of the file.
Thank you, and any observations are welcomed.
Click to expand...
Click to collapse
It doesn't quite work like that, you can create your own Odin flashable file(.tar.md5) containing the custom ROM, but it isn't as simple as just pasting the system.img into the .tar.md5.
Here are some threads for extracting Odin files and for creating your own .tar.md5 using the custom ROM file.
This thread is for correctly extracting the existing .tar.md5:
https://www.rwilco12.com/forum/showthread.php?tid=74
This thread is for creating your own Odin flashable .tar or .tar.md5:
https://www.rwilco12.com/forum/showthread.php?tid=92
Sent from my LGL84VL using Tapatalk
Acquire a similar scatter file for another device.
Use ADB to extract Partition information.
Edit similar Scatter using ADB and Device for Reference's.
Add the Partition information into the similar scatter.
Test scatter file for proper PMT & HW Chip ID.
Error & Repairs for HW ID Mismatch & PMT Changed.
Test Error repaired scatter to extract Preloader.
Extract preloader from BOOT_0.
Test Preloader with boot.img extraction & download.
Save Scatter file & Preloader into a safe place.
Use Scatter & Preloader for Memory Test.
Use Memory Test information for Read back of entire Memory.
Save Full Read back to a safe place.
Extract System.img, Boot.img, Recovery.img, NVram.img, NVDATA.img, frp.img, Etc.
Compile Firmware for SP Flash Tool.
Edit & Remove proprietary information from firmware for custom release.
Leave stock for stock Firmware extraction.
For Pure time consumption reasons, this guide may take me a while to complete, however the steps above should give you a rough idea of how everything is going to be written...
To start with, the information is so much at once, that I've made a video to help people go along with it...
The video is in 2 parts & in English... Please watch these first, that'll cover about everything in the steps except a few things like compilation of extracted IMG files.
The second video should be watched after the first video, so I've put that link in the description of video 1.
https://youtu.be/e2_U68EGSlY
OK... Now you've seen the instructions, you can work through extracting every partition you'll need for a firmware backup.... You don't need all of them !
After that, Copy the following files (you should now have them all ) to a new folder called Stock Firmware for SP Flash Tool ..
boot.img
cache.img
lk.img
logo.img
preloader.bin
recovery.img
secro.img
system.img
trustzone.bin or .img
userdata.img
MT*****_Android_scatter.txt
Now you need to edit the Scatter file using NotePad++ or another program that won't wreck line endings... Word pad & Notepad will wreck line endings and destroy the scatter file.
Edit the scatter file to now have the correct file names, eg.....
preloader_******_njh_gjb_.bin TO preloader.bin - The same as your copied file name.
boot_example_mt.img TO boot.img - The name of the file for boot.
Now the scatter file, Image's & Preloader should be all together...
ZIP the folder to remove empty space in .img files, Shrink the Firmware to a Zip file.....
You just need to extract the zip file and open the scatter file in SP Flash Tool v5.16+ .. Then select Download to do a firmware installation.
I will edit this guide in time, however I just wanted to get out how I do this on my MTK Device's... People keep asking me how to do it, so I released the video and this extra information for them... I don't make money on YouTube so everything here is provided free & I don't make any money from helping !!! Sorry about the terrible audio !