Related
<KANE>How to make i9003 straight flash pack (system embedded cf-root, ext4, deodex)
Most of the theme is zip format and flash with CWM,but so many people still don't know how to made the zip.So I make one tutorials for the people who don't know (EX:CF-Root,ext4,deodex and bla bla bla)
1.First,wipe data and cache
2.Flash the rom that you want via odin
3.Flash CF-Root(UC kernel also can)via odin
4.Open CWM,flash the deodex(zip)(how to make?google search )
5.When you want to convert you system to ext4 format,backup your rom via CWM firstAfter backup finnish,back to main menu,flash the ext4 format file(zip),restore the rom,than your system are fully convert to ext4 format!
6.After finnish first 5 step,use ADB tool
7.Go to wireless and network/USB setting,select "mass storage" ,and then Open "USB debugging" at applications/development ，open CMD(computer)
type “adb shell” and then connect to computer via USB,press enter,and than type
"dd if=/dev/block/stl9 of=/sdcard/system.rfs bs=4096" then system.rfs will copy to internal SDcard（The system.rfs copy at here is included cf-root，ext4 and deodex）
8.Package it need to use linux system（Virtual Machine also can），at least linux 6 or Ubuntu 10
only linux 6 or above support ext4 format system file! If the version lower than 6 that the system.rfs cannot be mount
9.If you want further modify system.rfs, use terminal,type
mount：mount -o loop system.rfs /root/system/
unmount：umount /root/system/
note：(the path above is me own use! I create folder at / , switch to my new file directory, execute this command!
mount before modify，then after unmount it can be save
10.Package it ，must be add boot.bin Sbl.bin param.lfs normalboot.img system.rfs modem.bin and cache.rfs of the original rom,only can flash with this
now we need to cover the system.rfs with after modify one
Cover the normalboot.img in CF-ROOT into it.And cover the cache.rfs with after convert to ext4 one,and add userdata.rfs file
（you can get the cache.rfs and userdata.rfs at attachment, all rom also can use it!）Now you can package it
go to terminal with linux，cd Command change to the folder you create before this, put the boot.bin Sbl.bin param.lfs normalboot.img（cf-root one） system.rfs（modify one） modem.bin cache.rfs（cover one） userdata.rfs（add one）to the folder
Execute the command "tar cf PDA.tar boot.bin Sbl.bin param.lfs normalboot.img system.rfs modem.bin cache.rfs userdata.rfs" to package it！
PDA.tar is the file after synthesis ，and you can add other file if you want
11.And then copy the PDA.tar to desktop，flash with odin！dont forget to flash with pit file!Why must use pit file and userdata.rfs? Because pit file and userdata.rfs will re-partition and reset all user data ! So all version also can flash the zip file and no need to rely on other versions(pit can get at attachment)!
If it is not very good please tell me! Thanks for your support!
Hopes：
1.most of the XDA people are very pro，and I hope you can make a tutorials when you make a new thing
2.At china,so many people use I9003,so many people at XDA too!!so we hope when you create a new thing can add chinese!
（only hope,not force you!thank you!）
Wow i was sear hing just this in all the forum!! Thanks!!
Enviado desde mi GT-I9003 usando Tapatalk
thank you!!
This is awesome. Thanks
Sent from my GT-I9003 using XDA App
I am reading everything a lot of times, to be sure of that I understand everything. Could anybody explain me this? I don't understand...
go to terminal with linux，cd Command change to the folder you create before this, put the boot.bin Sbl.bin param.lfs normalboot.img（cf-root one） system.rfs（modify one） modem.bin cache.rfs（cover one） userdata.rfs（add one）to the folder
Click to expand...
Click to collapse
Hello Kane, if i understood you, with this procedure i can make a PDA.tar file to flash with ODIN but i also need a pit file althaugh it's a single file. Am i wright?
I could use this method to get a full pda.tar with the firmware i am looking for (i mean, if i get an i9003 phone with that firmware)?
I will explain myself:
recently i poste this question in here http://forum.xda-developers.com/showthread.php?p=20360464#post20360464:
Uan_ar said:
Hi people, i'm looking for the firmware UBKPD (2.3.6) wich is the one that is the update from UBKB1 (2.2.1) by kies in Argentina. I would like to get the official and unbranded, but in the official roms threads of sammobile or sampro.pl it didn't appear yet (like the XXKPQ in sammobile).
If anyone get it or if is possible to get it from Samsung i would be pleased.
On the other hand, if anyone can tell me if it's possible to extract it from a updated phone and to make a .tar file to flash to others it would be helpful also.
Thank you very much in advance.
Click to expand...
Click to collapse
If i get a phone with the UBKPD firmware, can i make a "UBKPD_PDA.tar" file? What else do i need to put it in my phone (i got now intalled the XXKPQ)? Should i flash it over XXKPE (ginger, 4 files) or mi old official froyo (UBKB1)?
Thank you very much in advance. Greetings from Argentina.
HI，luiseteyo！Steps should be so!
put the “boot.bin” “Sbl.bin” “param.lfs” “normalboot.img”（cf-root one） “system.rfs”（modify one） “modem.bin” “cache.rfs”（cover one） “userdata.rfs”（add one）to a new folder, then go to terminal with linux，use "cd" Command change to this folder and type :
"tar cf PDA.tar boot.bin Sbl.bin param.lfs normalboot.img system.rfs modem.bin cache.rfs userdata.rfs"
hi，Uan_ar
yes,u need a pit file..it can be found everywhere lol
sure,there is no doubt that u can make a "UBKPD_PDA.tar" file use this method..and u can flash it over every rom
i just wan to say about the ugly typesetting...= - =
and it's nice ... good job...haha
CHINA-KANE said:
hi，Uan_ar
yes,u need a pit file..it can be found everywhere lol
sure,there is no doubt that u can make a "UBKPD_PDA.tar" file use this method..and u can flash it over every rom
Click to expand...
Click to collapse
OOkey, now I understood. But one more thing. I put the device in debugging mode and massive also. I conect it, I open cmd, I write the location of the adb with:
Code:
C:\Users\***\Desktop\ADB
Then I type:
Code:
adb shell
and then the code to backup system.rfs, but it does nothing in the phone and nothing in the cmd, do I have to wait? Thank you very much!!
EDIT: I answer myself. You have to wait despite it doesn't say nothing. The system.rfs backup is in the internal card (in my case)
CHINA-KANE said:
hi，Uan_ar
yes,u need a pit file..it can be found everywhere lol
sure,there is no doubt that u can make a "UBKPD_PDA.tar" file use this method..and u can flash it over every rom
Click to expand...
Click to collapse
Thank you very much Kane. I don't have any difficulties to find the pit, as you said is everywhere. However, my question was made in base that i never used pit when flashing just one pda.tar file.
What happens if i don't add the userdata.rfs? this pda.tar will work also on any other phone? which is te data that goes there? I´m asking you this because i don´t need/want the data from other phones (personal data, imei, etc.) i just want try to make a flashable update firmware for all the argentinian android i9003 comunity.
thanks again, and again
Interesting and useful. I thing the next link is useful: http://forum.xda-developers.com/showthread.php?t=1132724
userdata.rfs must be added, when the district needs it! Any ROM like this!
After connecting phone, enter the command directly in the CMD adb shell, do not brush into the ADB!
my bad ,,,,,,,,
sakindia123 said:
my bad ,,,,,,,,
Click to expand...
Click to collapse
for what?
hey,do u need to like 'sign' the system.img after combining it with pda?coz i always get 'PDA Invalid"
for how want to use Odin to flash the ClockWorkMod Recovery img or any image files like "boot.img", this is a tool to create a tar.md5 file from the img file.
unzip the file tool, and put your img files into the same directory of the batch file.
if you have more than one file put each file in a separate folder.
launch the "ImgToTar.MD5.bat" to create files with the extension of tar.md5 for each img file.
Note: the script rename the each file starting by "recovery*.img" to "recovery.img" , and files named "boot*.img" or "kernel*.img" image to "boot.img". if your file has another name , don't forgot to rename a recovery image to recovery.img, and the boot image to boot.img.
hope that help some body how search a batch file to create tar.md5 file for using it in Odin.
******************** new version of the script:
in this new version you can combine multiple files ,img and bin files, all of them into one file tar.md5 bundle.
a "AllFiles" directory is created including this result pack file ready to use in new Odin version v3.10.7.
Thank you this worked fine on my 9505.
It creates a recovery.tar.md5 with 0 bytes on my Windows XP.. :crying:
Any suggestion?
SeaFargo said:
It creates a recovery.tar.md5 with 0 bytes on my Windows XP.. :crying:
Any suggestion?
Click to expand...
Click to collapse
i can't see what the problem on your system, the tool is very simple. send me a zip of your folder with all files, also the recovery image file, and the tar.md5 file 0b.
Solved!
I find out that Odin is perfectly able to flash a TAR file, even without md5 hash check.
So I've used the Official TAR for Windows and that's it. By the way, 7z tar are not compatible.
Yes odin accept tar file. The md5 sum is a check for the integrity of data on the file. It's more safe to use a tar.md5 instead of tar file.
Envoyé depuis mon GT-I9505 en utilisant Tapatalk 4
mkh.mourad said:
Yes odin accept tar file. The md5 sum is a check for the integrity of data on the file. It's more safe to use a tar.md5 instead of tar file.
Envoyé depuis mon GT-I9505 en utilisant Tapatalk 4
Click to expand...
Click to collapse
how to make odin flash tar without md5 hash?
The same ,you chose the tar file instead of the tar.md5. Odin accepte both extentions in the PDA editbox.
mkh.mourad said:
The same ,you chose the tar file instead of the tar.md5. Odin accepte both extentions in the PDA editbox.
Click to expand...
Click to collapse
but without md5 hash odin refuses to flash for safety reasons. its obvious that tar and md5 are just extensions... i meant how to force odin to flash ordinary tar without md5 hash in it.
Kriomag said:
but without md5 hash odin refuses to flash for safety reasons. its obvious that tar and md5 are just extensions... i meant how to force odin to flash ordinary tar without md5 hash in it.
Click to expand...
Click to collapse
odin accept all this extention PDA files:
*.tar, *.md5, *.smd, *.gz and *.tgz
but only *.md5 file has a hash to check data integrity.
a formatted MD5 checksum line is add at the end of the tar file to produce a file tar.md5
for exemple at the end of a tar file named "recovery.tar" we will find a line like this:
"53a1ee899d6f7b4b39c189739eee6294 recovery.tar"
mkh.mourad said:
odin accept all this extention PDA files:
*.tar, *.md5, *.smd, *.gz and *.tgz
but only *.md5 file has a hash to check data integrity.
a formatted MD5 checksum line is add at the end of the tar file to produce a file tar.md5
for exemple at the end of a tar file named "recovery.tar" we will find a line like this:
"53a1ee899d6f7b4b39c189739eee6294 recovery.tar"
Click to expand...
Click to collapse
when md5 checksum is does not match tar odin refuses to flash, but if there is no md5 at all it should work? i havent tried that lol
i will test it shortly... brb
i think it works, odin accepted kernel tar i used: "tar -H ustar -c boot.img > kernel.tar"
This tool doesn't work for you?
in the first post a have put a new version, it can create from any file with the extention *.img a *.tar.md5.
if any problem happend you can send me the log.txt file.
the latest recoveryclockmod image for odin:
Tried the tool .. didn't work the first time, saw a 'PATH NOT FOUND' in the command window. So I tried again using folder path without any space (i.e..: "D:\tar-tools\" instead of "C:\users\my name\desktop\tar tools unzipped\") and the tool works.
My conclusion, tool did not work if folder path contains space(s).
Thanks for the batch files.
TOPeX85 said:
tries the tool .. didn't work the first time, saw a 'PATH NOT FOUND' in the command window. So I tried using folder path without any spaces #i.e..: "D:\tar-tools\" instead of "C:\users\my name\desktop\tar tools unzipped\"# and the tool works.
My conclusion, tool did not work if folder path contains space#s#.
Thanks for the batch files.
Click to expand...
Click to collapse
thanks
I'll fix this problem in the future
update: the script accepts path and filename with spaces
Didnt work
I have downloaded twice the toll but when I try to decompress winrar send me errors, could you check this please?
Or do I have to use another program to decompress it?
Thanks in advance.
If i want to create a .tar.md5 from modem.bin there's some trick to do to create that?
pimentel07 said:
I have downloaded twice the toll but when I try to decompress winrar send me errors, could you check this please?
Or do I have to use another program to decompress it?
Thanks in advance.
Click to expand...
Click to collapse
I used 7zip rather than Winzip or winrar.
I updated the file by compressing it with WinRAR in zip extension.
sorry man.
bluflight said:
If i want to create a .tar.md5 from modem.bin there's some trick to do to create that?
Click to expand...
Click to collapse
I can not confirm, but I think it'll work.
the only thing is that it must have exactly as the filename: "modem.bin".
mkh.mourad said:
the latest recoveryclockmod image for odin:
Click to expand...
Click to collapse
After 2 hours of searching,this tar file gave me back my recovery, thanks a lot man! :good:
now i can go sleep :victory:
all the methods and commandlines described on your forums to convert the recovery.img to an ODIN flashable .tar or .md5 file simply compresses the .img file itself and puts the .img into the .tar file (so if I open the .tar file with winzip ill see the initial recovery.img I started with inside the .tar file) WHICH in fact is NOT flashable by ODIN please help?
XDA Visitor said:
all the methods and commandlines described on your forums to convert the recovery.img to an ODIN flashable .tar or .md5 file simply compresses the .img file itself and puts the .img into the .tar file (so if I open the .tar file with winzip ill see the initial recovery.img I started with inside the .tar file) WHICH in fact is NOT flashable by ODIN please help?
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Unfortunately I cannot find such a guide under the SII forums. If it was a guide for a different device, there is no guarantee it will work for the SII.
There is a cheater method though, if you have a working system with root. Enable ADB debugging, connect the phone to your PC, fire up adb shell, su, and then dd a copy of the recovery.img on the phone to the recovery partition (sorry I cannot give you the exact path since it varies by model, but it would be along the lines of /dev/block/platform/msm_sdcc.1/by-name/recovery).
To further explore this, or option A (the original thought), please go ahead and create an account. From there, add a post to this thread:
> Samsung Galaxy S II I9100 > Galaxy S II Q&A, Help & Troubleshooting > [Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread
Hope this helps, and good luck!
Hello all, I love all the support from the developers who make our ROMs so great and was wondering the following question. Does anyone know how you can extract the CSC files from the .tar.md5 just so if a new one becomes available, I can just apply it immediately to that current ROM? I searched a few threads and found different methods like the s2toext4 method and that didn't work so anything would be most appreciated. I don't want to take anything from the developers and this will just be for my personal use.
Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
{
"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"
}
*Detection* said:
Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
Click to expand...
Click to collapse
I tried that as the file in Odin contains a cache.img and a hidden.img but when I boot the a custom ROM and check Phone Info, the CSC didn't change. I am just wondering how some developers extracted those .img files into the files we see into say the CSC changer.
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Andrw0830 said:
Hello all, I love all the support from the developers who make our ROMs so great and was wondering the following question. Does anyone know how you can extract the CSC files from the .tar.md5 just so if a new one becomes available, I can just apply it immediately to that current ROM? I searched a few threads and found different methods like the s2toext4 method and that didn't work so anything would be most appreciated. I don't want to take anything from the developers and this will just be for my personal use.
Click to expand...
Click to collapse
Not quite sure what you want to do, flash a stock (any) rom with you CSC ( home _ csc ) check this
Or change the CSC of your custom rom, if so check here
kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
Very useful post, thanks! Works like a charm.
kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
Yep thanks so much. That is what I wanted to accomplish!
Andrw0830 said:
Yep thanks so much. That is what I wanted to accomplish!
Click to expand...
Click to collapse
What if you modify inside the zip (change default region) and flash it back from recovery? Does it work? KNOX still 0x0?
viewdetails said:
What if you modify inside the zip (change default region) and flash it back from recovery? Does it work? KNOX still 0x0?
Click to expand...
Click to collapse
What I believe is if you flash stock Samsung packages from ODIN, your Knox stays at 0x0 but once you flash modified software like TWRP Recovery, then you lose Warranty. Your phone should detect default region anyways as was the case when I went back to stock so only if you change the package integrity or flash custom recovery is when you will trip KNOX unless someone corrects me. I'll keep this thread open for the useful post about extracting .tar.md5 files in case someone has the same question I had, but I may not reply to other questions as besides flashing ROMs am not too knowledgeable in customizing ROMs.
viewdetails said:
What if you modify inside the zip (change default region) and flash it back from recovery? Does it work? KNOX still 0x0?
Click to expand...
Click to collapse
@ viewdetails, did you try modifying the zip to change the default region and flash it back? Did it work?
I've recently bought an S7 whose region code I want to change to XFA, except it is still stock and unrooted, and XFA is part of a multi CSC only.
Not wanting to void the warranty by rooting just yet, I also had the idea of modifying the CSC tar.md5 file to make it work. Thing is I have not done something like this before and I don't know if doing so will set KNOX to 0x1 anyway.
When I download the repair firmware (4 pieces of ROM called repair software) for any device from the internet, the pit file is also available, but when I download the 4 pieces of pit file with SamFirm program, the pit file does not come out. When I extract the csc.tar.md5 file in the downloaded rom, I have the pit file in it. Is that the pit file I would choose in the Re-Partition section in the PIT file? In other words, do they retrieve the pit files in the repair firmware that are installed in the internete by extracting the file csc.tar.md5 like me?
---------- Post added at 10:05 PM ---------- Previous post was at 09:54 PM ----------
*Detection* said:
Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
When you extract the file Csc.tar.md5, the pit file comes out. Odin is the pit file I would choose for Re-Partition?
Click to expand...
Click to collapse
Serifbilgin20 said:
When I download the repair firmware (4 pieces of ROM called repair software) for any device from the internet, the pit file is also available, but when I download the 4 pieces of pit file with SamFirm program, the pit file does not come out. When I extract the csc.tar.md5 file in the downloaded rom, I have the pit file in it. Is that the pit file I would choose in the Re-Partition section in the PIT file? In other words, do they retrieve the pit files in the repair firmware that are installed in the internete by extracting the file csc.tar.md5 like me?
---------- Post added at 10:05 PM ---------- Previous post was at 09:54 PM ----------
Click to expand...
Click to collapse
*Detection* said:
Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
When you extract the file Csc.tar.md5, the pit file comes out. Odin is the pit file I would choose for Re-Partition?
Click to expand...
Click to collapse
You don't need to extract the PIT file, just check repartition, the CSC will do the rest as it contains the PIT anyway
I need a pit file for any device. The firmware file I downloaded for that device is csc.tar.md5 and the pit file that comes out of it is the file I am looking for ?
kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
What did you mean by this ? '' Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.''
EmperorGsi said:
What did you mean by this ? '' Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.''
Click to expand...
Click to collapse
A flashable zip file needs /system to be mounted in order to make modifications - including installing and removing files - under it, so most zip files automatically do the mount process first before they do anything. However sec_csc.zip lacks that process, so if you want to flash it, you have to manually mount /system under MOUNT options first.
kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
kykint said:
A flashable zip file needs /system to be mounted in order to make modifications - including installing and removing files - under it, so most zip files automatically do the mount process first before they do anything. However sec_csc.zip lacks that process, so if you want to flash it, you have to manually mount /system under MOUNT options first.
Click to expand...
Click to collapse
Oh got it thank you. i am trying to get sec_csc.zip from S8 Tur firmware but no recovery folder in cache.img. Do you have any ideas ?
EmperorGsi said:
Oh got it thank you. i am trying to get sec_csc.zip from S8 Tur firmware but no recovery folder in cache.img. Do you have any ideas ?
Click to expand...
Click to collapse
If you're trying to unpack an oreo firmware, looks like imgextractor cannot handle the cache.img properly. Instead you can follow the steps below:
1. Extract lz4 image
Code:
lz4 -d cache.img.lz4
2. Convert the extracted image with simg2img (you can compile one from AOSP source or grab from here)
Code:
simg2img cache.img cache.raw.img
3. Open cache.raw.img with a proper program like 7zip explorer, and you'll find recovery/sec_omc.zip.
I used the method from here.
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-extract-pixel-factory-t3563698
I changed cache.img to system.img
The program created a folder called system and copied there all the files
In system/recovery I found the file sec_csc.zip
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