Hello,
I tried to extract nk.bin and it was extracted well.
But, dumprom have any bug.
After dumprom util extract files from nk.nb0, it change arm files to mips files.
I extracted files as the following steps;
First, download nk.bin from attached files.
One is arm nk.bin file for wince 5.0 and the other is arm nk.bin file for wince 6.0.
And, download nkbintools files to extract bin image files.
nkbintools also have dumprom util.
1. to dump the content of a nk.bin:
viewbin.exe nk.bin
(write down start and length)
2. cvrtbin -r -a START -w 32 -l LENGTH nk.bin
this command converts the nk.bin to a nk.nb0 (START and LENGTH from the command bevor)
3. dumprom.exe -d dump -v -5 nk.nb0
the content of the nk.bin will be written in the directory "dump". It must exists, otherwise an error occurs.
4. now, see files that is extracted and you will know that they are changed to MIPS files.
Anybody who know why they are changed MIPS files?
Hi all folks,
I have some question about the stock android system in this specific box and the format of the dumped partition.
Try to explain, I'm using rkflashtool to interact with the memory of the RK3188
This is the output of the command
rkflashtool r 0 1 | head -n 11
-------------------------------------------------------------------------------------------------
CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0
init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:
[email protected](misc),
[email protected](kernel),
[email protected](boot),
[email protected](recovery),
[email protected](backup),
[email protected](cache),
[email protected](userdata),
[email protected](kpanic),
[email protected](system),
[email protected](user)
-------------------------------------------------------------------------------------------------
I guess the boot partition is something linke that:
+-------+ <--- 0x00019fe0
| boot |
+-------+ <----0x00012000
With this command i'm able to dump the entrie boot partition on my linux box in a file named b00t.img :
rkflashtool r 0x12000 0x8000 > b00t.img
Now, i have find out that with the tool rkunpack (or simply with dd) i'm able to unpack this b00t.img. The output are two file:
b00t.img-raw
b00t.img-symbol
The first file is no more than a gzip compressed data file, I'm able to extract the data in a directory with this command:
gunzip < ../b00t.img-raw | sudo cpio -i --make-directories
Now in this dir I have all the files of the / partition. I can modify for example the /init.rc.
I want to repack the entrie b00t.img in order to flash it again on the device.
NB:
In this thread this guys work at something like my problem...
http://www.freaktab.com/showthread.p...ull=1#post4055
The difference is that they work on a different partition layout, and the rkunpack of dumped boot.img return they only boot.img-raw.
Obviously I've already tried to repack the modified directory in this two ways:
mkcramfs myboot myboot-temp.img
kcrc myboot-temp.img customboot.img
or
find . ! -name "."| sort | cpio -oa -H newc | gzip -n > ../newboot.gz
kcrc newboot.gz customboot.img
Neither of these leads to obtain a file large enough to fit the boot partition on the deivice, that I want fill with:
rkflashtool w 0x12000 0x8000 < modifiedb00t.img
Has anyone ever worked with rk3188? Any idea?
Thanks in advance.
SOLVED!
Look at http://www.freaktab.com/showthread.php?12200-ANDROID!-boot-img-want-to-modify-only-the-ramdisk.
Hi all folks,
I have some question about the stock android system in this specific box and the format of the dumped partition.
Try to explain, I'm using rkflashtool to interact with the memory of the RK3188
This is the output of the command
rkflashtool r 0 1 | head -n 11
-------------------------------------------------------------------------------------------------
CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0
init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:
[email protected](misc),
[email protected](kernel),
[email protected](boot),
[email protected](recovery),
[email protected](backup),
[email protected](cache),
[email protected](userdata),
[email protected](kpanic),
[email protected](system),
[email protected](user)
-------------------------------------------------------------------------------------------------
I guess the boot partition is something linke that:
+-------+ <--- 0x00019fe0
| boot |
+-------+ <----0x00012000
With this command i'm able to dump the entrie boot partition on my linux box in a file named b00t.img :
rkflashtool r 0x12000 0x8000 > b00t.img
Now, i have find out that with the tool rkunpack (or simply with dd) i'm able to unpack this b00t.img. The output are two file:
b00t.img-raw
b00t.img-symbol
The first file is no more than a gzip compressed data file, I'm able to extract the data in a directory with this command:
gunzip < ../b00t.img-raw | sudo cpio -i --make-directories
Now in this dir I have all the files of the / partition. I can modify for example the /init.rc.
I want to repack the entrie b00t.img in order to flash it again on the device.
NB:
In this thread these guys work at something like my problem...
http://www.freaktab.com/showthread.p...ull=1#post4055
The difference is that they work on a different partition layout, and the rkunpack of dumped boot.img return they only boot.img-raw.
Obviously I've already tried to repack the modified directory in this two ways:
mkcramfs myboot myboot-temp.img
kcrc myboot-temp.img customboot.img
or
find . ! -name "."| sort | cpio -oa -H newc | gzip -n > ../newboot.gz
kcrc newboot.gz customboot.img
None of these leads to obtain a file large enough to fit the boot partition on the deivice, that I want fill with:
rkflashtool w 0x12000 0x8000 < modifiedb00t.img
Has anyone ever worked with rk3188? Any idea?
Thanks in advance.
Anyone?
Tutorial port rom different MTK chipset
MT6589 to MT6572
1. Material Stock
2. Materials Port
From Stock grab:
file-folder:
* / System / lib -> / modules
* / System / lib -> / egl
* / System / lib -> / hw
* / System / lib -> / SoundFX
regular file:
* / System / lib -> from libaudio-resampler.so to / lib -> libaudioutils.so
* / System / lib -> from libcam.camadapter.so to / lib -> libcameraservice.so
* / System / lib -> libMali.so and all related to the GPU. especially libMali.so
================================================
From stock take:
file-folder:
* / System / etc -> / bluetooth
* / System / etc -> / firmware
* / System / etc -> / wifi
regular file:
* / System / etc -> vold.fstab
* / System / etc -> vold.fstab.nand
================================================
From stock take:
* System / usr / keylayout / Generic.kl
or all files in / usr this will fix the bug.
================================================
From stock take:
* / System / vendor
This merge into port.
================================================
From stock take:
* / System / xbin
This merge into port.
================================================
all of the above files kcuali vendor and xbin
replace it to the port.
or first delete the files and replace port exactly above.
if the file is not a MALI GPU port then in / lib there is a file libMali.so
so add libMali.so of stock and all related to the GPU. libEGL.so example.
================================================
Which fairly complicated stage which must edit boot.img.
Take boot.img from the port.
boot.img unloading port and boot.img stock
(Tutor kmrin I dah share)
tutor via apktool android
if use PC / lepi ane kaga ngarti: p
edit boot.img port
click / ramdisk find "init.rc" edit "init.rc"
search! code "mt6589" without quotes
change to "mt6572" without quotes
all code "mt6589" change it to "mt6572"
if it finds one of the codes "mt6582" This let it remain "mt6582" should not be changed.
then save.
take stock of boot.img file named "kernel" without the quotes, its size 3.85Mb
and override all port boot.img.
then unpack be named new.img size 4.46Mb
rename to boot.img
================================================
At Port edit his build.prop
* /system/build.prop
find code: ro.mediatek.platform = MT65xx
example: ro.mediatek.platform = MT6589
MT6589 change so MT6572
example: ro.mediatek.platform = MT6572
search code:
mediatek.wlan.chip = MT6628
mediatek.wlan.module.postfix = _mt6628
change it to:
mediatek.wlan.chip = mediatek.wlan.module.postfix = _
================================================
In the port edit "updater-script" at META-INF
search code:
eg "its format"
format ("ext4", "EMMC", "/ dev / block / mmcblk0p3", "0", "/ system");
change "mmcblk0p3" so "mmcblk0p4"
"Mmcblk0p4" This is a mount point system A7T +
And change also "mount her"
mount ("ext4", "EMMC", "/ dev / block / mmcblk0p3", "/ system");
change "mmcblk0p3" so "mmcblk0p4"
Or change it to as below, this code is universal and suitable for all android MTK
format ("ext4", "EMMC", "EMMC @ android", "0", "/ system");
mount ("ext4", "EMMC", "EMMC @ android", "/ system");
add the code:
symlink ("wlan_mt6582.ko", "/system/lib/modules/wlan.ko");
symlink ("/ system / xbin / libmnlp_mt6572", "/ system / xbin / libmnlp");
before the code "set_perm" or at the beginning of the code "sysmlink"
then save.
================================================
FOR ADVANCED USER !!
Fixing BUG APP THAT WILL MOST FC
Decompile "framework.jar" stock and port
in stock Copas smua contents of:
/ Smali / com / MediaTek
framework.jar to put in place the same port
And this also
smali / com / android / server
Copas also to put in place the same port
recompile framework.jar port
done ...
================================================
Wrap into a flashable zip and install via
CWM or TWRP
LINK SOURCE / ORIGINAL
http://forum.xda-developers.com/showthread.php?t=2701283
A youtube video on this guide
Watch video
Hello guys,
I rarely write guide and tutorials .so neglect my typos and gramatical mistakes
Today im gonna show you how to unpack sparsed system.img files (system_1.img+system_2.img+............+system_*.img)
supports system / cache / userdata / persist / vendor / cust / odm /oem partitions from QFIL firmwares
Lets get started
LINUX
Things Needed:
1) Packsparseimg
2) Imgextractor.exe -Need wine for this
Procedure:
1) First of all extract you device firmware in which you have sparse system.img files in a folder.
(folder path ex:~/Desktop/firmware)
2) Copy the downloaded packsparseimg_v1.1 and Imgextractor.exe in the same folder where you extracted your firmware
(ex:~/Desktop/firmware)
3) Open terminal and enter below commands.
4)
Code:
chmod 0755 packsparseimg_v1.1
5)This command will pack sparse system_1.img....files to system.raw
Code:
./packsparseimg_v1.1
you can use these commands to pack sparse cache and userdata persist,vendor,cust,odm partitions
Code:
Usage of ./packsparseimg_v1.1:
-o string
output dir path (default "./")
-t string
image to unsparse: system / cache / userdata / persist / vendor / cust / odm / oem (default "system")
-x string
xml file to load (default "./rawprogram_unsparse.xml")
6) After joining of sparse system.img's finishes you will get system.raw file
7) Use below commands to unpack system.raw to system folder
Note: You need wine on your linux to run imgextractor.exe
Code:
wine imgextractor.exe system.raw
8) Hell Yeah! you have successfully unpack those system_1,2,3,4....imgs
now you can make your own stock deodexed rom
Downloads For linux:-
[MOD EDIT: URL REMOVED]
Password:innfinite4evr
Imgextractor.exe
WINDOWS
Things Needed:
1) packsparseimg_v1.1
2) Imgextractor.exe
Procedure:
1) First of all extract you device firmware in which you have sparse system.img files in a folder.
(folder path exesktop/Myfirmware)
2) Copy the downloaded packsparseimg_v1.1 and Imgextractor.exe in the same folder where you extracted your firmware
(exesktop/Myfirmware)
3) Open Command Prompt (cmd.exe) and enter below commands.
PS: you can open command propmt by any of these methods. Here method 1 is preferred
Method 1: Most suitable method for this guide
hold down shift key while pressing the right mouse onto the folder you want to open "command prompt" then a new menu item will appear in your context menu offering you exactly that: "open command prompt here" select it and command prompt will open.
Method 2:Search is very helpful. In Windows 7, open the Start Menu and type command or cmd. Then, click or tap the Command Prompt
Method 3ne of the quickest ways to launch the Command Prompt is to use the Run window (press Win+R on your keyboard and type cmd and press enter to open it).
i guess three methods are enough for windows users
4) AFter command prompt opens enter below comamnds to proceed further
5)This command will pack sparse system_1.img....files to system.raw
Note default is "system"
Code:
packsparseimg
you can use these commands to pack sparse cache and userdata persist,vendor,cust,odm partitions
Code:
Usage of packsparseimg:
-o string
output dir path (default "./")
-t string
image to unsparse: system / cache / userdata / persist / vendor / cust / odm (default "system")
-x string
xml file to load (default "./rawprogram_unsparse.xml")
6) After joining of sparse system.img's finishes you will get system.raw file
7) Use below commands to unpack system.raw to system folder
Code:
imgextractor.exe system.raw
8) Now you will get unpacked system folder
Hell Yeah! you have successfully unpack those system_1,2,3,4....imgs
now you can make your own stock deodexed rom
Downloads for windows:-
Imgextractor.exe
Password:innfinite4evr
[MOD EDIT: URL REMOVED]
Changelog:-
in update v1.1
now supports system / cache / userdata / persist / vendor / cust / odm /oem partitions from QFIL firmwares
Credits:
kidd for initially making packsparseimg binary
@and_pDA for imgextractor,exe(Based on sources ext4_unpacker)
@Innfinite4evr for testing this method and write this guide
Great work bro :good: Nice job and thanks for this
great work man. thanks
can you share code?
There is another way to unpacj that instead of using wine.
Code:
mount -o loop -t ext4 system.img [path]
Replace:
[Path] with path to the output directory you want (ex: ~/sys-img)
ext4: This might be different, check it by yourself, but most device now using ext4
Thanks for the info, btw
Please can somebody tell me how to revert the process? To create again sparse images and flash via qfil? Thanks in advance!
cofface said:
can you share code?
Click to expand...
Click to collapse
only prebuilts
cofface said:
can you share code?
Click to expand...
Click to collapse
only prebuilts
I get this error on Ubuntu:
bash: ./packsparseimg: cannot execute binary file: Formato eseguibile non valido
What is the procedure to do the reverse?
How to repack as parts
sir i was trying to repack system folder to system_1.img system_2.img etc.
is there any way for that?
i need to repack and flash to my phone
Doesn't seem to work for Oreo a/b system
@Innfinite4evr Hi there, can you add vendor, cust and odm support ?
AL_IRAQI said:
@Innfinite4evrHi there, can you add vendor, cust and odm support ?
Click to expand...
Click to collapse
Yes there is.
Im thinking to update this stuff
AL_IRAQI said:
@Innfinite4evrHi there, can you add vendor, cust and odm support ?
Click to expand...
Click to collapse
Ive updated the tool, maybe you can try for odm partition.
Innfinite4evr said:
Ive updated the tool, maybe you can try for odm partition.
Click to expand...
Click to collapse
I've try to buy, with all my2 credit card (master card and american express)
I was addebited 1€ in my mastercard, but it always give me error and I can't download the program.
I do not want the refund, I'd like to have the tool!
Samuele Bonzio
I give you my phone number by PM if that need!
Thank you!
Thread closed. PM me when you have download links that don't require payment to be added to the OP.