COSTOM BOOT IMAGE FOR XDA 1 - MDA, XDA, 1010 General

can anyone help me put a costom boot image on an at&t 2003 rom??
no i dont have lunix
no i dont know any c++ or - - or that matter...
i hope someone with a kitchen might be willing to substitute my .bmp for theirs, and cook one for me.
thanks

If you send me the image in the right format, i can add it to the kitchen....
Second way is looking at the tools the xda-developers have done. I think, there is a small tool to change the bootimage...
HTH
Stefan

it is easy to change bootimage !

Lumpi... explain 'correct format'!
gate... explain 'easy', how easy??

ntabikha said:
Lumpi... explain 'correct format'!
Click to expand...
Click to collapse
I an other posting one of the developers said more about the formatÖ
it has to a very specific format: Windows, 16 bit, inverted, R5G6B5 from Photoshop
Click to expand...
Click to collapse
For adding a new bootimage take a look at this:
pnewbmp
you must specify a bmp file, as required by splitrom, and the romversion with '-3' or '-4', this determines the location where the bootsplash is written, for (most!!) 3.x roms this is at 81900000, for 4.x roms, and the chinese 3.x rom it is at 81ec0000.
so be careful, you must first verify that the bootsplash is indeed at this location, otherwise you will overwrite essential data in your rom
Click to expand...
Click to collapse
HTH
Stefan

I changed the bootimage succesfully in a Wallaby, with "pnewbmp.exe" from "itsutils".
http://xda-developers.com/~itsme/download/itsutils.zip
I made the bootimage with Adobe - Photoshop CS. Make a new 240x320 image. Convert it to 256 color with dightering than convert back to RGB. It is not neccessary, but the result is better for the 12 Bit display.
Save the picture in 16bit BMP format, with "flip row order" checked, and "R5 G6 B5" format in the advanced options. The final file size must be 153672 bytes !!
There is two options to upload the bitmap to the memory. There is a -3 and -4 options (target memory address) in pnewbmp.exe. It is depend from the ROM version in your wallaby. You can check the target memory by download the actual bitmap first from one of the two avaible adresses.
When you can open the downloaded bitmap with photoshop, this was the correct target memory area. So: upload the new bitmap to the address where you finded the actual bootimage.
(Use the "open as" function in Photoshop, and select RAW format. You cant open the downloaded bitmap as other ordinary BMP files.)
And thank you Itsme, for the tools!

Sallala said:
I changed the bootimage succesfully in a Wallaby, with "pnewbmp.exe" from "itsutils".
http://xda-developers.com/~itsme/download/itsutils.zip
I made the bootimage with Adobe - Photoshop CS. Make a new 240x320 image. Convert it to 256 color with dightering than convert back to RGB. It is not neccessary, but the result is better for the 12 Bit display.
Save the picture in 16bit BMP format, with "flip row order" checked, and "R5 G6 B5" format in the advanced options. The final file size must be 153672 bytes !!
There is two options to upload the bitmap to the memory. There is a -3 and -4 options (target memory address) in pnewbmp.exe. It is depend from the ROM version in your wallaby. You can check the target memory by download the actual bitmap first from one of the two avaible adresses.
When you can open the downloaded bitmap with photoshop, this was the correct target memory area. So: upload the new bitmap to the address where you finded the actual bootimage.
(Use the "open as" function in Photoshop, and select RAW format. You cant open the downloaded bitmap as other ordinary BMP files.)
And thank you Itsme, for the tools!
Click to expand...
Click to collapse
You have described how to make the picture but you didn't mention how the pnewbmp.exe works, I read this :
newbmp.exe
you must specify a bmp file, as required by splitrom, and the romversion with
'-3' or '-4', this determines the location where the bootsplash is written, for
(most!!) 3.x roms this is at 81900000, for 4.x roms, and the chinese 3.x rom it
is at 81ec0000. so be careful, you must first verify that the bootsplash is
indeed at this location, otherwise you will overwrite essential data in your
rom.
So what are the steps to use this executable file I have 4.01.16 rom ver.
tell me how to be able to get the pic file where and from to upload it again..Thanks in advance.

Ok, let I write the steps:
You must to upoad the new bootimage one of this two memory start addresses: 0x8190000 for 3.x ROMs and to 0x89ec0000 for 4.x ROMs. But, as the readme says, it is good to check this.
1. check the destination memory area:
- go to a command line, and run this commands: (from itsutils)
- pmemdump.exe 0x81900000 151672 3.bmp
- pmemdump.exe 0x81ec0000 153672 4.bmp
Now you downloaded 153672bytes from the flash memory to files 3.bmp and 4.bmp One of these is a bitmap image, the other maybe an empty "black" image. Try to open with Adobe - Photoshop CS.
- select File->Open As->Photoshop RAW format->when the box displays select 240x320 for image size, and 16bit color depth and IBM PC format.
Try this with 3.bmp and 4.bmp. With one of these you can see your actual bootimage. Maybe in grayscale.
2. make your new bootimage, I wrote how.
- check it, it must be 153672 bytes. Not to upload biger image, because you will overwrite other programs in your flashrom.
3. upload the new image.
- pnewbmp -3 yournewimage.bmp if you can open and see your actual bootimage from 3.bmp file or
- pnewbmp -4 yournewimage.bmp if you can open and see your actual bootimage from 4.bmp
Thats it!
Sallala

Sallala said:
Ok, let I write the steps:
You must to upoad the new bootimage one of this two memory start addresses: 0x8190000 for 3.x ROMs and to 0x89ec0000 for 4.x ROMs. But, as the readme says, it is good to check this.
1. check the destination memory area:
- go to a command line, and run this commands: (from itsutils)
- pmemdump.exe 0x81900000 151672 3.bmp
- pmemdump.exe 0x81ec0000 153672 4.bmp
Now you downloaded 153672bytes from the flash memory to files 3.bmp and 4.bmp One of these is a bitmap image, the other maybe an empty "black" image. Try to open with Adobe - Photoshop CS.
- select File->Open As->Photoshop RAW format->when the box displays select 240x320 for image size, and 16bit color depth and IBM PC format.
Try this with 3.bmp and 4.bmp. With one of these you can see your actual bootimage. Maybe in grayscale.
2. make your new bootimage, I wrote how.
- check it, it must be 153672 bytes. Not to upload biger image, because you will overwrite other programs in your flashrom.
3. upload the new image.
- pnewbmp -3 yournewimage.bmp if you can open and see your actual bootimage from 3.bmp file or
- pnewbmp -4 yournewimage.bmp if you can open and see your actual bootimage from 4.bmp
Thats it!
Sallala
Click to expand...
Click to collapse
Sallala,
Thanks a lot mate I'll try it right now I was waiting ur post actually

C:\Documents and Settings\Neo\Desktop\wallaby boot screen changer\build>pnewbmp
0x89ec0000 151672 3.bmp
Usage: { -3 | -4 } pnewbmp filename
Where should I look for the .bmp file in the xda or in my pc , I searched for it in the ppc I didn't find it thus I searched in my pc I didn't find it as well !!?? :?

C:\Documents and Settings\Neo\Desktop\wallaby boot screen changer\build>pnewbmp
0x89ec0000 151672 3.bmp
Click to expand...
Click to collapse
What you write is wrong!
pnewbmp does not need the start memory address nor the size.
???
pnewbmp -4 mycustomspash.bmp --> write bitmap
pmemdump 0x89ec0000 4.bmp --> download bitmap from flasrom
pmemdump place the image where pmemdump is in.
I uncompress itsutils here:
Y:\Y_down\PPC_MOJO_SZUFF\Rom_update\HTC_Wallaby\itsutils\
(exe files in the "build" directory)
so I started a command line and type:
y:
cd \
cd Y_down\PPC_MOJO_SZUFF\Rom_update\HTC_Wallaby\itsutils\build
pmemdump 0x89ec0000 4.bmp
And my downloaded image (4.bmp) is created in here:
Y_down\PPC_MOJO_SZUFF\Rom_update\HTC_Wallaby\itsutils\build
It is neccesarry to copy the itsutils.dll from the build folder to the devices \windows\ directory if it is not there already.
Sallalalalalala

Excuse me I haven't notice that I replaced pmemdump.exe with pnewbmp.exe lol :lol: thanks again....

Thanks Guys
I didn't actually know that was possible. I have created a few roms and was always disapinted that I couldn't make my own boot up immage I love the Idea so I created a new one You guys may like it
{
"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"
}

Re: Thanks Guys
TBCompDesign said:
I didn't actually know that was possible. I have created a few roms and was always disapinted that I couldn't make my own boot up immage I love the Idea so I created a new one You guys may like it
Click to expand...
Click to collapse
Nice bootimage. I placed my photo, name address and contact information. (but I know, the reason to help this when I leave the PDA is equal to 0,1%)
But there is a topic, to post your boot image. It name is "Post your boot images here" or something like this.

Wrong ROM Address cause PC Communication Error
I just run pnewbmp -3 yournewimage.bmp
When I soft reset, it can't communicate with PC (Error 87).
So I can't re-format my ROM with USB or infrared, because I've just erased PC communication with the command (" pnewbmp -3 yournewimage.bmp" )
The only solution is re-format my ROM from SD Card.
Please help me how to re-format from SD Card?
Thanks a lot
-------------
XDA I
Sallala said:
Ok, let I write the steps:
You must to upoad the new bootimage one of this two memory start addresses: 0x8190000 for 3.x ROMs and to 0x89ec0000 for 4.x ROMs. But, as the readme says, it is good to check this.
1. check the destination memory area:
- go to a command line, and run this commands: (from itsutils)
- pmemdump.exe 0x81900000 151672 3.bmp
- pmemdump.exe 0x81ec0000 153672 4.bmp
Now you downloaded 153672bytes from the flash memory to files 3.bmp and 4.bmp One of these is a bitmap image, the other maybe an empty "black" image. Try to open with Adobe - Photoshop CS.
- select File->Open As->Photoshop RAW format->when the box displays select 240x320 for image size, and 16bit color depth and IBM PC format.
Try this with 3.bmp and 4.bmp. With one of these you can see your actual bootimage. Maybe in grayscale.
2. make your new bootimage, I wrote how.
- check it, it must be 153672 bytes. Not to upload biger image, because you will overwrite other programs in your flashrom.
3. upload the new image.
- pnewbmp -3 yournewimage.bmp if you can open and see your actual bootimage from 3.bmp file or
- pnewbmp -4 yournewimage.bmp if you can open and see your actual bootimage from 4.bmp
Thats it!
Sallala
Click to expand...
Click to collapse

Related

aChef ROM Utils ver 0.2.1 (beta)

Warning to those who don't know what you're doing. Don't to be tempted to attempt this program.
[Introduction]
aChef is a ROM Utility for Hermes and Trinity to convert from OS.nb to imgfs_raw_data.bin and vice versa. (Just like prepare_imgfs.exe and make_imgfs.exe) Then you can use AddFile.exe and DelFile.exe to cook your own ROM.
[Attention]
Currently, this program ONLY designed and tested for supported ROMs (The program will detect automatically). IMGFS generated by the -force option is not tested for the flashing process.
[Usage]
You have to install Java (http://jave.sun.com) to use this program.
To extract to imgfs
==============
java -jar aChef.jar -1 06_OS.nb
To force extract of untested OS to imgfs
==========================================
java -jar aChef.jar -1 06_OS.nb -force
To convert imgfs to 06_OS.nb
=======================
java -jar aChef.jar -2 06_OS.nb
[Change Log]
<0.2.1> (latest)
- fix a bug occurs after delete large files
<0.2.0>
- improve conversion speed
- add support to Trinity OS.nb
- add checking for supported OS.nb
- bug fixes
<0.1.0>
- initial release
[Example]
- Get RUU_signed.nbh from the ROM
C:\test>NBHextract.exe RUU_signed.nbh
C:\test>java -jar aChef.jar -1 06_OS.nb
C:\test>echo 111 > test.txt
C:\test>AddFile.exe test.txt
C:\test>java -jar aChef.jar -2 06_OS.nb
- Flash using Bootloader 1.01 MFG (http://forum.xda-developers.com/showthread.php?t=290206)
Please make sure you know what u are doing before your flash the modified ROM to your device. Do it at ur own risk!!!
woowoo! great work, i'll try it later.
thank y man!
Hi
The tool works.But it needs an actual Java runtime to work.
Just tried it and it seems to work.
Don't know nothing about cooking yet, but it seems okay
Tried it without adding something and the new file is exactly the same as the original
When adding a file it is a little different, from the look of it it seems to work, but who is willing to try a flash?
trion said:
When adding a file it is a little different, from the look of it it seems to work, but who is willing to try a flash?
Click to expand...
Click to collapse
I have tried the flashing part for several times already. After add files of 3xxkb and delete a few files, all the changes were exactly what I expected after the flash.
Whith Hermes RUU_Hermes_HTC_WWE_2.05.xxxx Rom - OK!!!!
But... with Trinity ROMs and old Hermes Roms - Problems!!!
I used your tools for nb-file:
C:\java -jar aChef.jar -1 06_OS.nb
C:\java -jar aChef.jar -2 06_OS.nb
.....after that i got nb file, then I compared this file and original 06_OS.nb. So got many diffrerences between its. Just see my screenshot
{
"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"
}
lvsw said:
Whith Hermes RUU_Hermes_HTC_WWE_2.05.xxxx Rom - OK!!!!
But... with Trinity ROMs and old Hermes Roms - Problems!!!
Click to expand...
Click to collapse
He also said to only use it on the 2.05 rom.
But I don't see this as a problem, it's just his first alpha release, so we can start experimenting with cooking. It's just that I never done it before and I don't want to brick my device by flashing a failed cooked rom
Maybe someone more experienced in cooking can make a nice AKA 3.x rom that works better than this test version or even a crossbow version would be possible now
can i convert the raw file part of extracted rom in nb flash file?
5n0rk said:
can i convert the raw file part of extracted rom in nb flash file?
Click to expand...
Click to collapse
This will be possible in future release.
lvsw said:
Whith Hermes RUU_Hermes_HTC_WWE_2.05.xxxx Rom - OK!!!!
But... with Trinity ROMs and old Hermes Roms - Problems!!!
.....after that i got nb file, then I compared this file and original 06_OS.nb. So got many diffrerences between its. Just see my screenshot
Click to expand...
Click to collapse
It should work with the newly released version 0.2.0
aChef version 0.2.1 is released to fix a bug...
ahlok_hk said:
aChef version 0.2.1 is released to fix a bug...
Click to expand...
Click to collapse
Thanks! I create firth custom ROM for Trinity! - http://forum.xda-developers.com/showthread.php?p=1141089#post1141089
Does this mean that we can start building ROM's for the TyTN from scratch? Or can we only modify existing ones?
If it is the first case then where can I find all files needed to build my own custom ROM and if anyone knows where to find a nice tutorial I would even be more happy. ;-)
Hi,
I am new to this stuff. How can we try this to convert extended rom file like 04_ExtROM.nb. Once its converted to bin how can we open it.
Thanks.
JohanDC said:
Does this mean that we can start building ROM's for the TyTN from scratch? Or can we only modify existing ones?
If it is the first case then where can I find all files needed to build my own custom ROM and if anyone knows where to find a nice tutorial I would even be more happy. ;-)
Click to expand...
Click to collapse
A tutorial would be perfect. I have lots of things in mind but just to afraid to brick my device.
With his tool it should be possible to update the 2.05 rom with 2.06 stuff from cingular, withouth the cingular crap. And maybe some new stuf from a crossbow rom i guess? and the widcomm stack into the rom
Maybe someone who know how to do this can write a simple tutorial, or point us to one. Or maybe Lvsw is willing to make one for us?
Some things I like to know is, how do you select the folder a file is placed in with addfile and how do you add the registry settings. I guess when you know this it's just adding the stuff you like and that's it..?
trion said:
...
Some things I like to know is, how do you select the folder a file is placed in with addfile and how do you add the registry settings. I guess when you know this it's just adding the stuff you like and that's it..?
Click to expand...
Click to collapse
You can follow the example in post #1 to add and delete file in existing rom. All file will be placed in /windows folder.
Maybe also modify (delete then add) the following files
- modify initflashfiles.dat (cut first 2 bytes after edit with notepad)
- modify default.hv and user.hv
See also this thread for more information: http://forum.xda-developers.com/showthread.php?t=249836
ahlok_hk said:
You can follow the example in post #1 to add and delete file in existing rom. All file will be placed in /windows folder.
Maybe also modify (delete then add) the following files
- modify initflashfiles.dat (remove first 2 bytes edit with notepad)
- modify default.hv and user.hv
See also this thread for more information: http://forum.xda-developers.com/showthread.php?t=249836
Click to expand...
Click to collapse
Thanx, when I have more time I should be able to use this to create a rom with the Widcomm stack in it
And some crossbow stuff. (I'm guessing I can delete the programs and replace them with the programs from any crossbow rom? But when I replace the core windows files I guess I get into trouble?)
Is there a way to test the rom is okay? Or is there always the risk of creating trashed NAND?
why there is no one cook a hermes rom?
i just want to know how many files we can add to the os.nb and the size?(Max ?Mb for all files and Max ?Mb for a single file)
i am chinese and i need to add a font about 4Mb and wince.nls 1M, is it possible?
trion said:
Is there a way to test the rom is okay? Or is there always the risk of creating trashed NAND?
Click to expand...
Click to collapse
I would say that as long as you just modify the imgfs, the generated OS.nb would be safe to flash to NAND. There was an incidence that the aChef had a bug which created an almost empty IMGFS and I flashed it to my Hermes. But it was easily recovered by just flashing another valid OS.nb back to the device.
Of coz I cannot guarantee that it is 100% safe. But the main point of flashing a ROM is:
- type carefully
- use reliable USB cable(don't use retartable one!)
- reboot the PC before flashing.
- reboot the Hermes before flashing.
- make sure battery is 50% or above
- don't touch anything when flashing.
ahlok_hk said:
I would say that as long as you just modify the imgfs, the generated OS.nb would be safe to flash to NAND. There was an incidence that the aChef had a bug which created an almost empty IMGFS and I flashed it to my Hermes. But it was easily recovered by just flashing another valid OS.nb back to the device.
Of coz I cannot guarantee that it is 100% safe. But the main point of flashing a ROM is:
- type carefully
- use reliable USB cable(don't use retartable one!)
- reboot the PC before flashing.
- reboot the Hermes before flashing.
- make sure battery is 50% or above
- don't touch anything when flashing.
Click to expand...
Click to collapse
Thanx!
When I have the time I will start some experiments, unless someone else already created the perfect rom by then
Thanx a lot for your program and the info!

New WM6 Upgrade Guide

**French Translation Click here : French Translation (Thanks to xvx45)
**German Translation Click here: German Translation (Thanks to animelover)
**Indonesian Translation Click here: Indonesian Translation (Thanks to varanusvincent)
**Italian Translation Click here: Italian Translation (Thanks to slim_s200)
The old way of upgrading to wm6 is dead and gone. This is a guide to upgrade your phone from WM5 to WM6.
You should follow these steps carefully. Step 3 and 4 are necessary only if the WM6 rom you have downloaded instead of nk.nbf has os.nb file and the ExtROM folder:
Download update_package.zip and unzip it on your PC.
Update_Package (rapidshare)
Update_Package (4shared)
HardSPL
If you haven't HardSPL your phone you should. but the good news is you have to do it once and for all.
Connect your device to the usb port then go to HardSPL folder and run HardSPL.bat from your PC. (Thanks to Prislav)
The HardSPL.bat will perform the SoftSPL first and then will do the HardSPL. so you don't have to do the SoftSPL manually.
Before doing the HardSPL you should know:
SPL - Second Program Loader is a boot loader. SPL is similar to a BIOS in a computer and can be flashed and updated.
G3 or G4: If you soft reset your phone you will see four numbers on top left of the screen. The first one is IPL version. which has this format : #.##.000# the last digit of IPL version indicates if the device is G3 or G4. the G4 device IPL version will end with 0001 and the G3 device IPL version will end with 0000. for example if your device is G4 you might see something like: 2.20.0001
the reason we HardSPL the phone is that the original SPL that comes with the phone check the CID
Making the Extension Rom.nb (using that 10Mb that we never used)
go to Update_Package\Create Extended Rom\Winimage Trial and run the winimage.exe
open the Create Extended Rom\extrom-base\extende_rom.nb with winimage.exe
you will see a file inside it says : "You should put your files here". Delete that file!
go to the ExtRom folder. (Look at the picture) you will find ExtRom folder in most of the wm6 roms. when you download a wm6 rom, this folder is usually beside the Upgrade_ROM.bat .
make all the files read only (Select them, right click , then properties and then read Only) <-------Important!! (Updated)
inject the ExtRom folder
save the 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"
}
Convert os.nb and extended_rom.nb to nk.nbf
go to Update_Package\Create Nk.nbf and run nb2nbf.exe
Change the Model ID from Wizard to : Prophet
the CID filed must be empty!! But you can put any number for the OEM version.
select "File #1" then browse and select the extended_rom.nb that you have created from step 3.
Set the start address to 9B000000
Type Extension Rom for image name (Extension Rom not Extended Rom)!!! Edit: you can also write Extension instead of Extension Rom.
select "File #2" then browse and select the os.nb you have downloaded.
Select OS from Image Name drop down box
Select the location you want to save the output file (nk.nbf)
Click on Translate button on the top right of the screen.
Flash the nk.nbf
Using ROMUpdateUtility_NV_G3.exe or ROMUpdateUtility_NV_G4.exe you can flash the nk.nbf file you have created (or downloaded).
copy the nk.nbf that you have created to Update_Package\Update Utilities.
click on ROMUpdateUtility_NV_G3.exe or ROMUpdateUtility_NV_G4.exe and follow the instructions. Your main battery has to be more than 50% charge in order to be able to upgrade your rom( just a safety measure).
The benefits of using this new method:
More STORAGE area ! the smaller the os.nb the larger your storage!
I encourage all of you who haven't tried this method yet, to try this method. Specially if your favorite rom is relatively a clean rom and consequently has small os.nb. If you want to know how much extra storage you will get by using this method subtract the size of the os.nb (in kb) from 58,368. the difference will be the amount of storage you will gain when you try this new method.
Faster and safer Rom Upgrade.
Update: I have Attached the ScreenShots for those who can't see them from where I uploaded them.
Update2: You have to make the files in ExtRom read only before injecting the ExtRom folder.
Thanks to:
Prislav for the HardSPL http://forum.xda-developers.com/showthread.php?t=349900
Faria for his excellent tutorial about making the extended rom.
K0ster for reviewing this guide and giving constructive feedback
Updates:
I edit the first post. change the model number from PM300 to Prophet.
thanks a bunch hma4 this makes life... good and easy...
why now so sudden all this really perfect sollutions... now that the prophet is getting OLD...
well i'm gunna stick to my prophet just a while longer...
hma4 said:
[*] Convert os.nb and extended_rom.nb to nk.nbf
go to Update_Package\Create Nk.nbf and run nb2nbf.exe
Change the Model ID from Wizard to : PM300
do not type anything in other fields.
select "File #1" (Important!!) then browse and select the extended_rom.nb that you have created from step 3.
Set the start address to 9B000000
Type Extension Rom for image name (Extension Rom not Extended Rom)!!!
select "File #2" then browse and select the os.nb you have downloaded.
Select OS from Image Name drop down box
Select the location you want to save the output file (nk.nbf)
Click on Translate button on the top right of the screen.
Click to expand...
Click to collapse
I want to post some correctives:
Model ID: Prophet
Language: ENG or RUS (like i do )
OEM version: any digits
Operator version: any digits
CID: MUST be empty
Output file: path to yours nk.nbf
File 1: any nb-file (in my nk.nbf - this is 80040000-OS.nb, image name is OS)
File 2: any nb file (in my nk.nbf - this is 9b000000-Extension.nb, image name is - Extension)
If you want, you could add GSM and Splash.
But if i insert GSM and Splash, i insert GSM in File 1, Splash in File 2, OS in File 3, ExtROM in File 4. (Like in official ROM )
Enjoy.
k0ster said:
I want to post some correctives:
Model ID: Prophet
Language: ENG or RUS (like i do )
OEM version: any digits
Operator version: any digits
CID: MUST be empty
Output file: path to yours nk.nbf
File 1: any nb-file (in my nk.nbf - this is 80040000-OS.nb, image name is OS)
File 2: any nb file (in my nk.nbf - this is 9b000000-Extension.nb, image name is - Extension)
If you want, you could add GSM and Splash.
But if i insert GSM and Splash, i insert GSM in File 1, Splash in File 2, OS in File 3, ExtROM in File 4. (Like in official ROM )
Enjoy.
Click to expand...
Click to collapse
Thanks K0ster, but the Model ID or the order of files I think doesn't matter. I followed the Faria instructions in his tutorial. the first field "File #1" is the only field that can have a longer name such as "Extension Rom". I haven't test "Extension" instead of "Extension Rom", but I think both is possible and correct. I will update the first post accordingly
once again thank you for your review
IF CID Unlocked by paid service do i need HardSPL ?
I have an Orange SPV M600 and i CID unlocked it using the paid service.
So do i have to HardSPL my phone ???
yes yes yes... thanks... is that what i'm talking about
I followed the described steps very exactly but my Neo stucks in bootloader everytime I flashed it with my created nk.nbf!
There are two reasons why it's not working for me, I think:
- I did a mistake in creating the OS.nb
- I did a mistake in creating the nk.nbf
I make a new try with the Mysterious 1.0 GER, hopefully it will work for me ...!
thank u mr hma4
please upload the images on first post in www.tinypic.com
i cant see them.
thanks
animelover said:
I followed the described steps very exactly but my Neo stucks in bootloader everytime I flashed it with my created nk.nbf!
There are two reasons why it's not working for me, I think:
- I did a mistake in creating the OS.nb
- I did a mistake in creating the nk.nbf
I make a new try with the Mysterious 1.0 GER, hopefully it will work for me ...!
Click to expand...
Click to collapse
You MUST use JumpSPL or HardSPL for Prophet.
But for install HardSPL you need JumpSPL
k0ster said:
You MUST use JumpSPL or HardSPL for Prophet.
But for install HardSPL you need JumpSPL
Click to expand...
Click to collapse
@animelover, k0ster is right !
The HardSPL.bat that I've provided here will do the softSPL and then HardSPL. just follow the procedure one by one.
farzin_silver said:
thank u mr hma4
please upload the images on first post in www.tinypic.com
i cant see them.
thanks
Click to expand...
Click to collapse
I have attached the Screen Shots to the first post
hma4 said:
The benefits of using this new method:
More STORAGE area ! the smaller the os.nb the larger your storage!
I encourage all of you who haven't tried this method yet, to try this method. Specially if your favorite rom is relatively a clean rom and consequently has small os.nb. If you want to know how much extra storage you will get by using this method subtract the size of the os.nb (in kb) from 58,368. the difference will be the amount of storage you will gain when you try this new method.
Click to expand...
Click to collapse
I havnt tried whole method but step 3-5 are normal and 2 is new, so is 'more storage' result of step 2 ? (yes one has to use tadzio to reduce OS.nb)
what might be actual cause of 'more storage'?
nandlal_mk said:
I havnt tried whole method but step 3-5 are normal and 2 is new, so is 'more storage' result of step 2 ? (yes one has to use tadzio to reduce OS.nb)
what might be actual cause of 'more storage'?
Click to expand...
Click to collapse
flashing with UpdateUtility. when you flash your roms with Pdocwrite even though the os.nb is small, the storage area wont get merged with that free space. Making the nk.nbf and then flashing it with UpdateUtility will merge that free space with storage. also as you know you can't flash your rom with UpdateUtility if you haven't Hard(or soft) SPL.
I've followed the steps exactly again, with the same result: my Neo stucks at the second boot screen!
I used the HyperCore Kitchen to cook the OS.nb with a size of 49,9 MB instead of 57 MB! After that I used your nb2nbf, merged the Extension ROM image (only with 3 CAB files, the AutoRun.exe, Config.txt and Extension ROM image) and OS.nb to a nk.nbf! I've started the HardSPL installation, finished it well and then started the ROMUpdateUtility_NV_G4.exe (I have a G4 XDA Neo)!
I don't know where's my mistake, it's a ****ing ****! (Not your method )
And the screen of my Neo is flickering a little bit now!
hma4 said:
flashing with UpdateUtility. when you flash your roms with Pdocwrite even though the os.nb is small, the storage area wont get merged with that free space. Making the nk.nbf and then flashing it with UpdateUtility will merge that free space with storage. also as you know you can't flash your rom with UpdateUtility if you haven't Hard(or soft) SPL.
Click to expand...
Click to collapse
that means 'more storage ' can be achieved even only with SSPL ?
nandlal_mk said:
that means 'more storage ' can be achieved even only with SSPL ?
Click to expand...
Click to collapse
yes ,SPL has nothing to do with the storage ! as I said before it's the UpdateUtility.
animelover said:
I've followed the steps exactly again, with the same result: my Neo stucks at the second boot screen!
I used the HyperCore Kitchen to cook the OS.nb with a size of 49,9 MB instead of 57 MB! After that I used your nb2nbf, merged the Extension ROM image (only with 3 CAB files, the AutoRun.exe, Config.txt and Extension ROM image) and OS.nb to a nk.nbf! I've started the HardSPL installation, finished it well and then started the ROMUpdateUtility_NV_G4.exe (I have a G4 XDA Neo)!
I don't know where's my mistake, it's a ****ing ****! (Not your method )
And the screen of my Neo is flickering a little bit now!
Click to expand...
Click to collapse
Take it easy man Make sure your os.nb is okay to begin with then make sure you are typing those start address and image name correctly.
hma4 said:
yes ,SPL has nothing to do with the storage ! as I said before it's the UpdateUtility.
Click to expand...
Click to collapse
OK it works in my style!
As i dont want to alter SPL permanatly, i just ran SSPL and flashed reduce size OS.nb with old NVID_RUU (its same as in package provided here ).
And sure-- Spaces are MORE..!!!!!
thanx hma4 for right direction and time saving.
Hi hma4 , this is working for me in all the Rom's but in Korand ROM the extended don't work after flash .
Do you know if we must change the extended adress with this specific ROM.
Regards.

[TUT] How To Make Your Own Boot Screen and Hard Reset Screen

You are boring with default Boot Screen on Your Atom/ Atom Exec, and want to changes it with your favourite images. Read this instructions:
1. Download tools from HERE
2. Extract rar files in one folder with rom file diskimage_Ver.nb0
3. Install Hex Workshop 4.2 (hw32v423.exe) on your PC, or u can using another hex editor. But i'm personaly like this software.
4. Typed command RomMaster.exe diskimage_ver.nb0 -w 5 -b 0x0018000c -x -o xip.bin. It's will generated xip.bin for you
3. Run xipport, choose dump xip.bin and write maps. Close xipport
4. Prepare your own image with size 240x320, flip and rotate it 180 degrees. It's will look like screenshot. Save as bmp, file size must be 230.454 bytes. If u have Corel Paint Shop Pro Photo X2, it will save with this size automatically.
{
"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"
}
5. Run Hex Workshop 4.2 and open your own image, block all or select all than copy. Don't close Hex program
6. Open S000 from nk.exe region on your dumped xip folder with Hex Workshop. ctrl+F On your keyboard and on pop up windows choose text string, on value typed bm6, and ok. Select Edit on top left and choose Select Block. On pop up windows set block to 230454, Dec for decimal, and on method choose size of block. Paste in black area, than save. Select yes if program ask to make backup of S000 and move backup file to another location (for sometimes u want restore your boot screen). See at screenshot
7. Run xipport, realloc P, write maps than build xip_out.bin, specify address 0018000c for diskimage_ver.nb0 than click write xip_out.bin
8. Flash your new rom to device
ps: Follow this step to changes Hard Reset Screen on S003 from nk.exe region
Weel done, i hope this thread will help u
Regards,
Add download links for tools
This is possible to changes splash screen without flashing?
great job!!! this should be pinned!!!!
sticky it!!
brian_2cool4u said:
great job!!! this should be pinned!!!!
sticky it!!
Click to expand...
Click to collapse
Yeah, i second that!
Sticky it..!!!
aank said:
This is possible to changes splash screen without flashing?
Click to expand...
Click to collapse
I think that's impossible for now! maybe later if anyone make a program to changes "ROM FILES" on active device
abusalza said:
I think that's impossible for now! maybe later if anyone make a program to changes "ROM FILES" on active device
Click to expand...
Click to collapse
Nevermind,
i'll try to make one...
Thank You.
Thank You for your rom.
I will create from your sample and I found nice image.
Happy every time for you.
http://www.zune-wallpapers.com/a/all_recommended,2.html
Loedsiriya said:
Thank You for your rom.
I will create from your sample and I found nice image.
Happy every time for you.
http://www.zune-wallpapers.com/a/all_recommended,2.html
Click to expand...
Click to collapse
woaa... it's all so expresive. thnx, bro
anyway this threads sould be sticky, please mods
Other way, Direct modify.
I search by "first boot screen" and found someting from old post by someone.
this details.
I select modify at diskimage_Ver.nb0 file. It's easy modifying.
1.1st boot screen is black dragon on gold ray.
2. 2nd boot screen is BootScr.bmp. ====[black dragon on gold ray]
It's can use resco exploror replace after boot complete.
3.3th screen is show long time as 1st screen.
I use HitMan in Black color wallpaper. 3th file is welcomehead.96.png.
It's can use resco exploror replace after boot complete.
for 2nd and 3th image in \Windows and not flip
1st must flip vertical.
Please backup diskimage_Ver.nb0 before modify you boot screen.
When you find it by name. Your must found in the world. If have name.
=========================================
okay fellas, time to learn how to change the 1st bootscreen on your atom.
1. prepare your 1st boot screen 240 X 320 in bmp format
2. flip vertical (Must!!) and save it. file size is 230,454 bytes
3. Open your bmp file with Hex Editor (e.g. XVI32)
now you can change your 1st bootscreen either in nk.exe (inside xip during cooking) or on the diskimage_Ver.nb0
================================================== ===
on ATOM/ATOM Pure
xip mode.
1. goto nk.exe, open S000 file with hex editor.
2. the existing 1st bootscreen bmp file from address 3CD0 to 3C103
3. you may replace it with your bmp (cut & paste to that range address)
diskimage_Ver.nb0
1. open diskimage_Ver.nb0 file with hex editor.
2. the existing 1st bootscreen bmp file from address 184CDC to 1BD111
3. you may replace it with your bmp (cut & paste to that range address)
================================================== ===
on ATOM EXEC
xip mode.
1. goto nk.exe, open S000 file with hex editor.
2. the existing 1st bootscreen bmp file from address 3D50 to 3C185
3. you may replace it with your bmp (cut & paste to that range address)
diskimage_Ver.nb0
1. open diskimage_Ver.nb0 file with hex editor.
2. the existing 1st bootscreen bmp file from address 184D5C to 1BD191
3. you may replace it with your bmp (cut & paste to that range address)
================================================== ===
done!, enjoy your own 1st bootscreen on your device
** I'll assume you already know how to replace the block data (range address) in Hex Editor **
cheers!!
=========================================
thx all for sharing your knowledge
Yup, thanks for this tutorial, tried it and it works like a charm, very easy once you get the hang of using the Hex editor.
PaSSoA said:
Yup, thanks for this tutorial, tried it and it works like a charm, very easy once you get the hang of using the Hex editor.
Click to expand...
Click to collapse
Guys is suitable for ATOM LIFE?
Thankyou for you tutorial Abusalza, great work!
If we dont have corel Paint Shop but have Adobe Photoshop how can we adjust the image to that document size?
Any suggestions appreciated, thanks again.
well i think its pretty much the same.
but last time i used photoshop it saved size was 230.456 bytes.
so cut it the two byte using hex editor and its still showing fine
homer285 said:
Thankyou for you tutorial Abusalza, great work!
If we dont have corel Paint Shop but have Adobe Photoshop how can we adjust the image to that document size?
Any suggestions appreciated, thanks again.
Click to expand...
Click to collapse
Thanks worked it out
pdafre4k said:
well i think its pretty much the same.
but last time i used photoshop it saved size was 230.456 bytes.
so cut it the two byte using hex editor and its still showing fine
Click to expand...
Click to collapse
Yup. deleted 2 bytes on last line. sorry forget to explain before
pdafre4k said:
well i think its pretty much the same.
but last time i used photoshop it saved size was 230.456 bytes.
so cut it the two byte using hex editor and its still showing fine
Click to expand...
Click to collapse
becarefull, your xip module could be ruined, because the bootscreen want a place to be located either, if you port the 23x.456, it wont be bm6, but bm9 or 8,.
So, it will take place more than you think,.
you have to use some program like corel (adobe photoshop doesnt works easily for me)
then it will create 230.454,.
regards,.
Microsoft Paint works perfectly too save-as 24-bit bitmap.
Garmin said:
becarefull, your xip module could be ruined, because the bootscreen want a place to be located either, if you port the 23x.456, it wont be bm6, but bm9 or 8,.
So, it will take place more than you think,.
you have to use some program like corel (adobe photoshop doesnt works easily for me)
then it will create 230.454,.
regards,.
Click to expand...
Click to collapse
don't worry, mate. if u get files as bm8, bm9 or others, edit with hex and changes to bm6 and deleted 2 bytes last lines to get correct sizes...

[TUTORIAL] How to unpack Android ROMs on Windows

{
"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"
}
As all of you well know, Android is an open source operating system and as such the development and modding are the bread and butter for devices with this OS.
In this thread I'll explain how to extract the firmware partition containing the operating system and programs with a Windows PC.
The purpose of this thread is to share knowledge, so feel free to help me to dump device such as Acer, Samsung and Sony Ericsson, expecially I need someone that help me with Acer's .bin
1. Unpack the system partition from an HTC ROM
What you need:
UniExtract: http://legroom.net/software/uniextract (freeware)
ZipScan: http://www.zipscan.co.uk/ (shareware)
Cygwin: http://cygwin.org/setup.exe (freeware)
Unyaffs for Windows: http://goo.gl/z6yI
Download and install all the tools (Unyaffs it's a prompt executable, so it isn't installable)
Now you need an HTC ROM, download one at your pleasure from Conflipper's site: http://www.shipped-roms.com/shipped/
Once you have downloaded it, right click on the ROM executable and select Extract with UniExtract in the subfolder (v.fig1), select Isxunpack extraction and then clik on the OK button (v. fig2)
Now in the subfolder you have the various files which make up the executable, including data1.cab which is the file that we are more interested in (do not delete other files).
Open ZipScan, go to File -> Open Archive File... and browse until select the data1.cab. You should see something like this:
Extract from the cab only the ROM.zip and open this file with any archives extraction software (eg WinRAR or the same ZipScan). Inside you have various .img files which make up the ROM, but for the purposes of this guide, we need only the system.img.
Copy in a blank folder this file, unyaffs.exe and cygwin1.dll (you'll find it in C:\Cygwin\Bin).
Now open Cygwin from Start -> All Programs to ensure that its functions are integrated to the Windows Prompt and close it.
Open the Windows Prompt (Start -> All Programs -> Accessories) and position yourself in the folder containing the files using the cd command or alternatively install this .reg which allow you to open the Windows Prompt in the chosen folder by command in the context menu (Right click on the folder -> Command Prompt Here).
Now the last thing that you have to do is to give the extraction command: unyaffs system.img
Et voilà, now you have the folders containing the extracted system.
Enjoy
2. Unpack the system partition from a Motorola ROM
°°°Coming Soon°°°
°°°reserved°°°
°°°2nd reserved°°°
°°°3rd reserved°°°
Thank you! I had found a different way but this will save some steps.
mark
i will see
!!!!!!!!!!!!!!!!111
Someone once told me you can just run the .exe file, let it open, use windows to search for the rom.zip that would have been extracted into a temp folder, drag&drop to another location, then cancel the .exe again.
Haven't tried this myself though.
What else can you show us in windows?... Is it at all possible to extract ramdisc thingies from kernels so we can apply one custom kernel to other roms ourself?
... or should I bite the bullet and install/learn how to use ubuntu?
Nice initiative. Finish the guides and I'll see to it that it's stickied.
ddotpatel said:
Is it at all possible to extract ramdisc thingies from kernels so we can apply one custom kernel to other roms ourself?
... or should I bite the bullet and install/learn how to use ubuntu?
Click to expand...
Click to collapse
There are simple perl scripts kicking about to unpack/pack boot.img, so you can use them on Windows as long as you install perl first - say either via Cygwin or Active State.
I just used WinRAR to do everything that UniExtract and ZipScan can do.
...so basically you showed me that system.img can be unpacked using the linux command-line utility UnYaffs.exe, which can be run through CygWin. Thanks.
Why doesn't someone make a UnYaffs.exe for windows command line?
After I change things, how to I ReYaffs it to system.img? ...and when I re-zip it don't I have to sign it or something? If I modify an apk do I have to deODEX it first? Do I reODEX after?
I would love a quick tutorial on, say, how to change an icon for an app. Something that shows people who already know how to do this type of stuff a brief step-by-step guide to taking a [ROM], adding and deleting a few apks inside it, making a graphical change to an apk inside it (skinning), and then recooking those changes in to a new [ROM] to be shared with all.
rpmccormick said:
I just used WinRAR to do everything that UniExtract and ZipScan can do.
...so basically you showed me that system.img can be unpacked using the linux command-line utility UnYaffs.exe, which can be run through CygWin. Thanks.
Why doesn't someone make a UnYaffs.exe for windows command line?
After I change things, how to I ReYaffs it to system.img? ...and when I re-zip it don't I have to sign it or something? If I modify an apk do I have to deODEX it first? Do I reODEX after?
I would love a quick tutorial on, say, how to change an icon for an app. Something that shows people who already know how to do this type of stuff a brief step-by-step guide to taking a [ROM], adding and deleting a few apks inside it, making a graphical change to an apk inside it (skinning), and then recooking those changes in to a new [ROM] to be shared with all.
Click to expand...
Click to collapse
No ****... I was wondering why he's making it all so complicated with all these extra tools when I can click the file in Winrar (extract to...) and be done. All in ONE step for me.. LOL
For me it was more than one step because using WinRAR on system.img didn't get all the files out. Using unyaffs did. But now I have a system.img from a new Android tablet and I can't get anything out of it other then the META-INF directory using WinRAR, Unyaffs, or UniExtract. Anyone have any clue how to get in to those?
...and I still want an easy tutorial on how to re-assemble a flashable system.img / update.zip once I change some stuff in there.
I really hope one of those reserved spots is for the newer Samsung phones. What really cheeses me, though, is that I had that explained to me once, and I can't find it, and didn't write it down
I've compiled both unyaffs.exe, mkyaffsimage and mkyaffs2image for cygwin, with the DLL you can use them on Windows too. Sadly, I don't know too much about C and C++, so I can't make it work, but maybe I will try to compile them for Windows, and with some bugfixing, MAYBE it will run.
Samsung did not use the usual yaffs image (for Galaxy S at least), but their own format, what can be easily extracted. I will post some more about it as soon as I get back to windows, recompile the executables and upload them.
i wana extract boot.img , but i have some error
$ gunzip -c boot.img | cpio -i
bash: cpio: command not found
gzip: boot.img: not in gzip format
Click to expand...
Click to collapse
I had some problems with unyaffs. This version posted on 1st page is bugy, if you have same problem try...
hmmm i have i more problem: To prevent spam to the forums, new users are not permitted to post outside links in their messages.
so sry guys i can't help you right now
rpmccormick said:
i just used winrar to do everything that uniextract and zipscan can do.
...so basically you showed me that system.img can be unpacked using the linux command-line utility unyaffs.exe, which can be run through cygwin. Thanks.
Why doesn't someone make a unyaffs.exe for windows command line?
After i change things, how to i reyaffs it to system.img? ...and when i re-zip it don't i have to sign it or something? If i modify an apk do i have to deodex it first? Do i reodex after?
I would love a quick tutorial on, say, how to change an icon for an app. Something that shows people who already know how to do this type of stuff a brief step-by-step guide to taking a [rom], adding and deleting a few apks inside it, making a graphical change to an apk inside it (skinning), and then recooking those changes in to a new [rom] to be shared with all.
Click to expand...
Click to collapse
+1000
.
WinImage can extract the .img.
Unfortunately, I don't think it can repack them properly.

Extract system.new.dat of Nougat and Marshmallow (easily)

IMP NOTE : Use " python-2.7.xx" ,latest version otherwise extractor will led to undesired output like this one https://forum.xda-developers.com/showpost.php?p=72165633&postcount=295 and extractor supports android 7.1.2(updated on 18-May-2017)
Extractor of system.new.dat of Marshmallow and Lollipop ROM's
​
{
"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"
}
DOWNLOAD
OLD
Extractor 1.0
or
Mirror
Extractor 2.0
Extractor 3.0
UPDATED
Extractor 4.8 (Updated on 18-May)
SOURCE
$GIT-HUB Contribute!
Changelog -> https://github.com/matriex/System_Extractor-WIN/commit/4b94cde74f63f6f1ff21b8c745b306326b15cb5a
Alternative of repack, if the repack script doesn't works with your system folder then try this script SCRIPT / GUIDE
How to
Extract ext4-Image files
Download Imgextractor.exe binary from the link
https://github.com/matriex/System_Extractor-WIN/blob/master/bin/Imgextractor.exe
1. Create a folder named ext and copy the binary to ext folder
2. Copy your image file ,say "system_1.img" to ext folder
3. Select the ext folder , hold the shift (right) click RMB
4. Select "Open command window here"
5. Then type this command on CMD
Code:
Imgextractor.exe system_1.img -i
6. The files will be in "system_" named folder.
NOTE:You should rename IMG file to system_1.img before doing anything
Extract *.DAT files
Users, The extractor works with nought 7.0.0 and 7.1.1 perfectly (tested with CM14.1-2016-12-12 & aosp_7.0_2016-09-19), If you encounter errors then please install python and then try extracting again
Method I
Download and run the extractor .
METHOD II (command line)
Use python 2.7.xx
1. Download zip and extract sdat2img.py binary from the link
https://github.com/xpirt/sdat2img/archive/master.zip
2. Create a folder "ext"
3. copy "sdat2img.py", "system.transfer.list" and "system.new.dat" to ext folder
4. Open cmd on "ext", (by selecting and holding shift , you will find "Open command window here")
5.Type this on command window
Code:
python sdat2img.py system.transfer.list system.new.dat system.img
6. After that you'll find system.img on that folder, that image file is ext4 image file and can be extracted by this guide
http://forum.xda-developers.com/showthread.php?t=2285831
END OF SUPPORT I DON'T HAVE ANY METHODS LEFT AND PLESE ASK PROBLEMS RELEATED TO ANDROID 6.0 ONLY
Repack *.DAT
/*Repack will or will not work, Don't panic if it not worked, You can still use folder =) */
For flashing xyz_ROM.zip with dat files , you need to modify updater-script
Script, "of some roms" , b'coz some roms contains a link b/w updateR-script
and system.transfer.list. The link includes following : There is a line in
updateR-script script called
Code:
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "36,0,32770,......,307199") == "0b20303394271424267e36a0ce7573f1b62ddc0d" then
if you found this in
updateR-script then from here follow the guide Repack_INFO.txt otherwise
directly copy system.new.dat and system.transfer.list to ROM folder and
repack/zip it and flash it.
Repack ,select from script, then choose manually (option 1)
Copy all your ROM files/subfolders(bin ,app ,build.prop etc) to system folder
Everything is expalined in extractor, read it carefully
If you found "range_sah1()" on your updateR-script then continue below, else only you have to replace system.new.dat and system.transfer.list of "xyz_ROM"
CONTINUE ONLY IF YOU FOUND RANGE RANGE_SHA1
After repack a SHA1_VALUE of system.new.dat is generated and file is created as "SHA1_VALUE.txt" with "system.new.dat" & "system.transfer.list"
And follow this guide Repack_INFO.txt (attached end of this POST)
OR GIT ATTACHEDhttps://github.com/matriex/System_Extractor/blob/master/Repack_INFO.md
That's all if you need help feel free to comment
Thanks for using this method I can't say it will work , but what's wrong in trying , I tried 10 to 20 times to make it work
A LITTLE ADVICE
1. If the script failed to work ,please take a look at this post again I'm sure I've posted enough resource which will help you out in extracting and repacking .DAT files .
2. Please keep this thread clean.
3. Please don't quote whole thread(use tags).
4. I take no responsibility of repacking system.img!
5. For Linux users :https://github.com/matriex/System_Extractor-Linux/blob/master/README.md
6. Use Python 2.7.x or otherwise extractor will not work Do not use python 3.0 or update sdat2img.py binary!
Thanks to @xpirt for sdt2img
Repack_INFO.txt (GIT-HUB, clear view)
Any possible way to put it back?
? if possible Or why don't you flash it directly by folder
matrixex said:
Wait comming soon if possible
Or why don't you flash it directly by making some changes in updater-script
Click to expand...
Click to collapse
I am in no dire need of it right away, I am just asking for any future need.
nicesoni_ash said:
I am in no dire need of it right away, I am just asking for any future need.
Click to expand...
Click to collapse
Hi
I have successfully created repack script for system to dat , download it and reply worked or not
Deleted
Deleted
Works well on new Nutella OTA images. Thx
tweakradje said:
Works well on new Nutella OTA images. Thx
Click to expand...
Click to collapse
Cool please give me the link to android N OTA
Sure. Here you go http://developer.android.com/preview/download-ota.html
Cheers
tools not working broo
Source
Tools not working bro
Thanks. Tested and it worked.
v3ndul said:
Tools not working bro
Click to expand...
Click to collapse
Impossible i have tried it with marshmallow and Lollipop system.new.dat files several times(truly 4-5 ROMS more than 10times) it worked without any issues please be sure that you have copied your files as stated and also match the names as stated in extractor.
Don't copy whole post just use HIDE
v3 doesnt work. when I open it (with admin rights) I see the copyright and warnings then it closes and opens a new windows. it does that again and again sort of like a loop
Abaddon said:
v3 doesnt work. when I open it (with admin rights) I see the copyright and warnings then it closes and opens a new windows. it does that again and again sort of like a loop
Click to expand...
Click to collapse
same here
edit: solved using this version
View attachment 3692066
kenzolo said:
same here
edit: solved using this version
View attachment 3692066
Click to expand...
Click to collapse
Abaddon said:
v3 doesnt work. when I open it (with admin rights) I see the copyright and warnings then it closes and opens a new windows. it does that again and again sort of like a loop
Click to expand...
Click to collapse
I am really sorry this is because i converted bat file to exe file
Just uploaded a new version of v3.0 just download it
And you will get two things
1 bin
2 system_extractor.bat
Just run system_Extractor and enjoy
v3ndul said:
Tools not working bro
Click to expand...
Click to collapse
Don't quote the op.
Hi,
I've managed to extract, but repacking is giving the following error:
Found System FOLDER
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
error: ext4_allocate_best_fit_partial: failed to allocate 584 blocks, out of space?
Click to expand...
Click to collapse
I double checked, and I haven't ran out of disk nor RAM.
Can you help me?
Thanks
pacacc said:
Hi,
I've managed to extract, but repacking is giving the following error:
I double checked, and I haven't ran out of disk nor RAM.
Can you help me?
Thanks
Click to expand...
Click to collapse
No bro you haven't ran out of disk or RAM :silly:
This problem persist due to size of your system folder i.e it must be greater than 2GB
Right?
Don't worry jusy edit my batch file code using notepad ++
Here which line you have to edit
Search this line
bin\make_ext4fs.exe -s -l 2048M system.img system
Now replace 2048M with 4096M
After that the line will look like
bin\make_ext4fs.exe -s -l 4096M system.img system
And after that save it.
Done
Reply it worked or not
EDIT ON 30/5/2016
Use new version 4.0 IT CAN CALCULATE SIZE AUTOMATICALLY NO NEED TO EDIT SCRIPT
thanks for sharing this
i'm done the following
1. unpack
2. editing system file content(replace & delete)
3. repack (without error)
4. copy 2 file (system.new.dat & sistem.transfer.list) through 7zip
is that the correct steps? i mean, after that i can flash it like other rom zip

Categories

Resources