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 !
Related
Wondering if someone could help. I have a Timmy E82 Android 4.3 MTK MT6582 device and been unable to fully root it with any tools, due to /system refusing to mount. My device is true 4.3 it seems.
I'm using:
SP_Flash_Tool_v3.1332.0.187
MTK Droid tools v2.5.1
I made completed all the steps to get a scatter, it created a patched recovery, which I renamed to recovery.img and put both the scatter and the recovery in the same folder.
But then I'm getting error 8038.
Reading here: http://www.phcorner.net/threads/fix-...sh-tool.64302/
And a few other places it suggests the issue is a mis match in the scatter file. What is it I need to modify in the scatter to get it working so I can flash a custom recovery? I honestly don't know what value the SP log is e
Also I read the pre-loader needs to be able to in the same folder, as the scatter and recovery, does also also need to be ticked during the custom recovery flashing process?
Please see my attached scatter file and log with SP tools.
***********************Unpack Repack nb0 Rom******************
Here Is a nb0 tool that unpacks and packs SUT nb0 factory images Used By Some manufactures like Infocus,
Requirements-
Window pc with java Installed
How to unpack
1. Paste your stock Rom File, something.nb0 in Tools Folder
2. Rename it to firmware.nb0
3. Run unpack.exe file hit enter , Done, check unpack Folder Your extracted Rom IS Present,
How To Repack-
1. cut whole Rom From unpack folder and paste in Repack Folder[ you can edit your images],
Like System app etc, don't change name]
2. Run Pack.exe hit enter Done,
3. Your New Rom Is readdy with the name System.nb0 in tools folder
Downloads-
MOD Edit :- Links Removed
bro after i unpack firmware.nb0 file theres no file that related to system.img.???
Incomplete unpacking
Sir please help to completely unpack nb0 file as sut is not working nor my phone's flashier with scatter file is available online. My phone is Infocus m330 with mediatek mt6592 chipset. It's bootloader locked with hard brick that not showing any sign of active other than when connected to pc can be flashed with v com drivers
Please help
Going to test it now ?
Thank you mate
link is dead
Thread Closed.
Thanks
SacredDeviL666.
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
Hey, today in this post I've discussed on the topic
"How to unpack/repack img without PC or android tools (android tool is a little complicated and sometimes doesn't works)."
So let's get started
First of all download & install 'android image studio'
1: open it and click on repack/unpack
2: select the port ROMs boot or recovery img.
3: we get two folders
a.) Split_img --->> contains kernal zimage.
b.) Ramdisk----> contains init.rc recovery. Fstab etc..
4: to delete any file long press on it and click delete
5: to import any file click on import button in right panel & select the file
6: after making desired changes. Repack the img using repack button
7: a file will be created with the name image-new.img
8: export this file using export button and select the desired location.
Congratulations you have just ported an img without PC easily.
Link for the tool: https://play.google.com/store/apps/details?id=com.redlee90.imagekitchenforandroid
Link to my video toitorial for better understanding on this:
If you liked it just PRESS the THANKS button
I need more help, trying to open a .IMG boot file for Samsung s5, it gives the "No Image Supplied" error
Screenshot
Using AIS. Trying to port custom recovery but first thing I've tried is to just unpack and repack stock recovery. When repacking output of AIS is new IMG and new ramdisk. New IMG is smaller than original but from what I've read this should be okay. Flashed new IMG and attempted reboot recovery and all I got was black screen. Flashed stock recovery and it booted recovery fine. Not sure what I'm doing wrong. I used AIS to open the new image it created and then kept doing file/folder comparisons on the output. I narrowed down the difference being recovery.img-ramdisk.cpio. But when I unpack with cpio the contents of the archive are the same. Additionally, I repacked the contents with cpio but it still comes up as not matching the original recovery.img-ramdisk.cpio. My device can and does make replacement recovery images using applypatch with bonus files and boot img. Any help greatly appreciated!
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