Hi,
I have a big problem, i cannot run the P535RomTool.exe
when i try to run it, the black window pop up for a mili second and then nothing happened..
I have installed the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86): http://www.microsoft.com/downloads/d...displaylang=en. I have Windows XP SP2. what I have still to make it to run this tool? Plaese help me!!!
Thanks
P535RomTool is the console application.
You must run it in cmd console (Start->Run cmd) or by cmd(bat) files with parameters.
Possible Parameters:
-s <ROMFile.nb0> Re-compute CRC on .NB0 file
-d<x> <package.cap> [ROMFile.nb0] Extract .NB0 OS image from WMx (x=5 or 6) .CAP update package
-up <ROMFile.nb0> <N> <destimg> Unpack compressed partition image number N (0-3)
For example:
P535RomTool.exe -d6 AsusP535.cap GalaxyII.NB0
This tool can be used to either decompile or compile ROMs for various Asus devices that used the ABI firmware format (Can also be used in O2 XDA Zest ). The current version can support P835 unencrypted ABI, and even encrypted ABI from updater EXE! Current finding is this tool also supports unreleased Garmin-Asus ROMs!
Thanks (Especially )Harshal and Leon in AsusPda for testing.
Usage:
- Decompiling ROM
1. p835abisplit2 <abi/exe file>
2. os.nb0 and extrom.img released (Only for Pre-P835 devices), os.nb0 cab be processed by imgfsfromnb or osnbtool, extrom.img can be processed by WinImage.
- Compiling ROM
1. First rename the new os.nb0 to os-new.nb0, and rename extrom.img to extrom-new.img (If the new files do not exist, then the compiler will use the parts from original ROM)
2. p835abisplit2 /b <abi/exe file>
3. out.abi releases, which can be used to flash directly (Only for Pre-P835 devices or Post-P835 devices with unencrypted ROM).
4. If you input the updater EXE to p835abisplit2, it will also produce out.exe with region locked patched which can be used to flash your new ROM directly on devices with any region!
- Note when building ROM
1. If you need to modify XIP, make sure the modded XIP is the same size as the original one before merging back to nb0, otherwise booting will fail
2. For Pre-P835 devices, current version can create big-storage ROMs with variable size of imgfs. If the new OS is smaller than the original one, the freed space will be allocated to user space (The left part as shown in Memory setting) after flashing. However the user space display will only reflect the change on second flash.
3. For Post-P835 devices, all partitions must be exactly same size with the original one (i.e. you need to pad the partition before putting it back), otherwise the device won't boot.
4. For Pre-P835 devices, you can modify ExtROM as you like, but not remove or rebuild the image file, otherwise you may get a brick! (Not able to enter bootloader)
Final Warning: Customizing a ROM always has risks, I won't be responsible for any damages lead to your custom ROM!
Release Notes:
v2.40:
- Added support for M930
v2.32:
- Support extraction of encrypted ABI file resource from P835 updater exe
- Support reconstruction of P835 updater exe
- When rebuild to exe, the produced out.exe is patched to install in devices of any region.
V2.20:
- Support extration and rebuilding of P835 ABI file (Note that not for ABI inside EXE)
- When rebuild with exe, OUT.EXE will be produced for direct flashing
starkwong said:
This tool can be used to either decompile or compile ROMs for various Asus devices that used the ABI firmware format (Can also be used in O2 XDA Zest ).
Thanks Harshal and Leon in AsusPda for testing.
Usage:
- Decompiling ROM
1. p565abisplit2 <abi/exe file>
2. os.nb0 and extrom.img released, os.nb0 cab be processed by imgfsfromnb or osnbtool, extrom.img can be processed by WinImage.
- Compiling ROM
1. First rename the new os.nb0 to os-new.nb0, and rename extrom.img to extrom-new.img (If the new files do not exist, then the compiler will use the parts from original ROM)
2. p565abisplit2 /b <abi/exe file>
3. out.abi releases, which can be used to flash directly.
- Note when building ROM
1. If you need to modify XIP, make sure the modded XIP is the same size as the original one before merging back to nb0, otherwise booting will fail
2. OS part doesn't need to be the same size as the original. If the new OS is smaller than the original one, the freed space will be allocated to user space (The left part as shown in Memory setting) after flashing. However the user space display will only reflect the change on second flash.
3. You can modify ExtROM as you like, but not remove or rebuild the image file, otherwise you may get a brick! (Not able to enter bootloader)
Final Warning: Customizing a ROM always has risks, I won't be responsible for any damages lead to your custom ROM!. Moreover, don't use it in P835 abi, it won't work
Click to expand...
Click to collapse
Nice we all waiting for it
Many Congrats for successfully ripping through the ROM !!
Partition offsets and checksums reported by the tool are :
Part #0002 sz:0003e000=>0003e000 cs:625f94b2=>625f94b2 of:000003a0=>000003a0
Part #0004 sz:00100000=>00100000 cs:ffe5f731=>ffe5f731 of:0003e3a0=>0003e3a0
Part #0103 sz:00452a8c=>00452a8c cs:99f65978=>99f65978 of:0013e3a0=>0013e3a0
Part #0104 sz:000fffc0=>000fffc0 cs:5e03943f=>5e03943f of:00590e2c=>00590e2c
Part #0005 sz:07e00000=>07e00000 cs:674f4072=>674f4072 of:00690dec=>00690dec
Part #0013 sz:00a00000=>00a00000 cs:56994bf9=>56994bf9 of:08490dec=>08490dec
I am a little scared to use this tool for following reasons :
1. Actually, the IMGFS & ExtROM offsets are '00690dfc' & '08490dfc' respectively.
2. Checksums( 674f4072, 56994bf9....) can not be located in the Header.
3. The Adler32 checksum for the ExtROM is '5ff94bfa', while your tool reports '56994bf9'.
Any clues ?
rishi2504 said:
Many Congrats for successfully ripping through the ROM !!
Partition offsets and checksums reported by the tool are :
Part #0002 sz:0003e000=>0003e000 cs:625f94b2=>625f94b2 of:000003a0=>000003a0
Part #0004 sz:00100000=>00100000 cs:ffe5f731=>ffe5f731 of:0003e3a0=>0003e3a0
Part #0103 sz:00452a8c=>00452a8c cs:99f65978=>99f65978 of:0013e3a0=>0013e3a0
Part #0104 sz:000fffc0=>000fffc0 cs:5e03943f=>5e03943f of:00590e2c=>00590e2c
Part #0005 sz:07e00000=>07e00000 cs:674f4072=>674f4072 of:00690dec=>00690dec
Part #0013 sz:00a00000=>00a00000 cs:56994bf9=>56994bf9 of:08490dec=>08490dec
I am a little scared to use this tool for following reasons :
1. Actually, the IMGFS & ExtROM offsets are '00690dfc' & '08490dfc' respectively.
2. Checksums( 674f4072, 56994bf9....) can not be located in the Header.
3. The Adler32 checksum for the ExtROM is '5ff94bfa', while your tool reports '56994bf9'.
Any clues ?
Click to expand...
Click to collapse
Tool works properrly.No harm is trying
starkwong, is there any tool to decompile P835's ROM in the same way?
New version posted.
rishi2504:
The image checksum is not calculated by plain Adler32, actually is uses the same formula as older Asus ROMs, however it is not a one-time calculation.
Checksums are inside header, given you decoded it correctly.
starkwong, here's what I get when trying to decompile a ROM:
Code:
v2.40 (Jun 16 2009 19:56:06)
ExtractABI(): Trying to load G5_ALL_V4.11.0_V3.6.12.P2_Ship_WWE_app_MYS00_V2.3.6.exe...
Module loaded, searching for BIN resource...
Found matching resource at BIN #211!
GetPartitions(): Getting Partition Information...
*** Encrypted ABI detected
ABI Version 0x00030012
Project Name: G5
Partition Type: 000f [email protected]
Partition Type: 000e [email protected]
Partition Type: 000e [email protected]
Partition Type: 0004 [email protected]
Partition Type: 0004 [email protected]
Partition Type: 000f [email protected]
Partition Type: 000f [email protected]
Partition Type: 0102 damage [email protected]
Partition Type: 0005 UnKnown [email protected]
Partition Type: 0002 [email protected]
Partition Type: 0003 [email protected]
ProcessABI(): Writing OS data...
* BIN(P835) Image Detected
Warning: OS.nb0/flash.bin is not a NB image, not modifying MSFLSH50 headers
ProcessABI(): No ExtROM partition found.
OK!
So it seems that partitions are not detected correctly, there's no os.nb0 at the output, and the flash.bin apperars to be of no use. Even when I found imgfs partition inside of it, there's still something wrong with it, e.g. bad start block offset, and everything else is also broken.
Can you help me with this?
In fact it is correct, as Asus uses B000FF image on P835, not a plain NB0 image.
You need to use osnbtool to get a nb0 with extra bytes, then use nbsplit -data 2048 -extra 8 to get a nb0 with sector size 0x800.
ginkage said:
starkwong, here's what I get when trying to decompile a ROM:
Code:
v2.40 (Jun 16 2009 19:56:06)
ExtractABI(): Trying to load G5_ALL_V4.11.0_V3.6.12.P2_Ship_WWE_app_MYS00_V2.3.6.exe...
Module loaded, searching for BIN resource...
Found matching resource at BIN #211!
GetPartitions(): Getting Partition Information...
*** Encrypted ABI detected
ABI Version 0x00030012
Project Name: G5
Partition Type: 000f [email protected]
Partition Type: 000e [email protected]
Partition Type: 000e [email protected]
Partition Type: 0004 [email protected]
Partition Type: 0004 [email protected]
Partition Type: 000f [email protected]
Partition Type: 000f [email protected]
Partition Type: 0102 damage [email protected]
Partition Type: 0005 UnKnown [email protected]
Partition Type: 0002 [email protected]
Partition Type: 0003 [email protected]
ProcessABI(): Writing OS data...
* BIN(P835) Image Detected
Warning: OS.nb0/flash.bin is not a NB image, not modifying MSFLSH50 headers
ProcessABI(): No ExtROM partition found.
OK!
So it seems that partitions are not detected correctly, there's no os.nb0 at the output, and the flash.bin apperars to be of no use. Even when I found imgfs partition inside of it, there's still something wrong with it, e.g. bad start block offset, and everything else is also broken.
Can you help me with this?
Click to expand...
Click to collapse
B000FF image cannot be modified without osnbtool or viewbin or cvrtbin tool..For Ext ROM there is no partition in the abi file which can b read as .nb0 Ext ROM is inside the OS and is not as a partition.So what the output u get from the tool is correct.Whatever ROMs u saw mine are from using the same tool
I hope this clarifies.
starkwong, Thank you so much, it worked perfectly!
Can't use this tool on my Asus M530w. Getting this message:
Copyright(C) 2009 Studio KUMA(starkwong). All rights reserved
v2.40 (Jun 16 2009 19:56:06)
ExtractABI(): Trying to load nk.abi...
Failed loading as module (193). Perhaps ABI?
Trying as ABI directly...
Creating file mapping...
GetPartitions(): Getting Partition Information...
Error: AES Key not suitable for this ROM
unencrypted vers encrypted
There is little bit mess in description.
If you will use unecrypted rom + p835abisplit2 you will get os.nb0.
With encrypted rom + p835abisplit2 you will get flash.bin.
starkwong said:
4. For Pre-P835 devices, you can modify ExtROM as you like, but not remove or rebuild the image file, otherwise you may get a brick! (Not able to enter bootloader)
Click to expand...
Click to collapse
Hi,
Can i add my own cab/xml files to this Ext_ROM, after removing the files not needed ?
rishi2504 said:
Hi,
Can i add my own cab/xml files to this Ext_ROM, after removing the files not needed ?
Click to expand...
Click to collapse
Don't bother dude , figured it out ...
Is there anyway I can extract the flash.bin file from a .abi file using this tool?
My P835 is unable to upgrade from the SD card with the .abi file on it.. so I wanted to extract the flash.bin and see if I can use the QPST tool to update the image with flash.bin file..
Sorry if I'm being stupid here (not unusual!). I'm trying to use this tool to get a .abi file out of O2's "Xda_Zest Firmware Update_V7.7.0S.WWE20.00_M4.6.5.P7_V2.1.4 GBR20.exe" so I can stick it on the SD card and flash the ROM, but of course I'm only ending up with the two files you mention, os.nb0 and extrom.img, no .ABI file. I can look in the extrom.img file with winrar, but the file only contains FINDMA~1.000 (300 bytes), 000dummy.001 (0 bytes) and _setup.xml (1205 bytes).
Plainly I'm thick - where am I going wrong, and how do I get the .ABI file?
Hello guys,
I am trying to extract system.img.
I got system.img from this file
RUU_Vision_HTC_ARA_1.83.415.2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_168396_signed.exe
I tried unyaffs with no luck. I actually tried to use unyaffs on some other system.img and it worked.
I get this
0 [main] unyaffs 4172 exception::handle: Exception: STATUS_ACCESS_VIOLATIO N
1094 [main] unyaffs 4172 open_stackdumpfile: Dumping stack trace to unyaffs.exe.stackdump
Please help
hey,
maybe you should try this in the android developement forum. here are only g2 users and i guess in the developement forum there might be more ppl who could help you with that!
Unyaffs is used on img files created during a nandroid backup.
For most img files contained in an RUU, it's simply the filesystem it would normally be on the phone, in this case ext3. You need to mount or open the file with the ext3 filesystem.
I found ext2explore tool much easier on Windows.
Download
Edit: Didn't realize it's old thread-
Hi i'd like to unyaffs a cg39 file from a sbf
ajust it a little, and pack it back to do a nandroid restore (system.img)
how do i repack my /system dump to system.img
i've read that i need to use mkyaffs2image to back it into a system.img
(and do the md5sum)
where can i get mkyaffs2image.exe for windows ?
or is there an other way to make system.img files on a windows machine ?
(or do i have to use linux for (de)packing ??)
kind regards, Collen
Hi there.
Few months ago, before updating my z1 compact to 5.1.1, i've done a backup with sony pc companion, but i decided to not restore it.
Now i need some notes and files in that backup, so is there a way to get them without restoring everything? I tried to open the .dbk file with 7zip, but the notes backup file has no extension so i don't know how to open.
Thank you.
dario2510 said:
Hi there.
Few months ago, before updating my z1 compact to 5.1.1, i've done a backup with sony pc companion, but i decided to not restore it.
Now i need some notes and files in that backup, so is there a way to get them without restoring everything? I tried to open the .dbk file with 7zip, but the notes backup file has no extension so i don't know how to open.
Thank you.
Click to expand...
Click to collapse
I think backups are usually ext4. Try Ext4 unpacker or Ext2 explore.
dario2510 said:
Hi there.
Few months ago, before updating my z1 compact to 5.1.1, i've done a backup with sony pc companion, but i decided to not restore it.
Now i need some notes and files in that backup, so is there a way to get them without restoring everything? I tried to open the .dbk file with 7zip, but the notes backup file has no extension so i don't know how to open.
Thank you.
Click to expand...
Click to collapse
Tested with 7zip on the phone and seems to be working. My backups are TWRP, and info is packed in ext4.win files. 7z e command unpacked it.
Here's the output, (terminal wouldn't let me take a screenshot)...
7z e system.ext4.win000
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
p7zip Version 9.20 (locale=C,Utf16=off,HugeFiles=on,4 CPUs)
Processing archive: system.ext4.win000
Extracting AndroidManifest.xml
Extracting res/layout-v17/settings_checkbox.xml
Extracting res/layout/disclaimer_dialog1.xml
Extracting res/layout/disclaimer_dialog2.xml
Extracting res/layout/disclaimer_dialog3.xml
Extracting res/layout/disclaimer_prototype.xml
file settings_checkbox.xml
already exists. Overwrite with
res/layout/settings_checkbox.xml?
(Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit? Y
Extracting res/layout/settings_checkbox.xml
Extracting res/mipmap-hdpi-v4/ic_settings.png
file ic_settings.png
already exists. Overwrite with
res/mipmap-mdpi-v4/ic_settings.png?
(Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit? A
Extracting res/mipmap-mdpi-v4/ic_settings.png
Extracting res/mipmap-xhdpi-v4/ic_settings.png
Extracting res/mipmap-xxhdpi-v4/ic_settings.png
Extracting res/xml/settings.xml
Extracting resources.arsc
Extracting META-INF/MANIFEST.MF
Extracting META-INF/SONY-ERICSSON-E-PLATFORM-SIGNING-LIVE-864F-3.SF
Extracting META-INF/SONY-ERICSSON-E-PLATFORM-SIGNING-LIVE-864F-3.RSA
Extracting classes.dex
Everything is Ok
Files: 17
Size: 433866
Compressed: 1618233344
[email protected]:/sdcard1/twrp/BACKUPS/CB5A20B0Q8/2015-12-25--.236 #
levone1 said:
Tested with 7zip on the phone and seems to be working. My backups are TWRP, and info is packed in ext4.win files. 7z e command unpacked it.
Here's the output, (terminal wouldn't let me take a screenshot)...
7z e system.ext4.win000
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
p7zip Version 9.20 (locale=C,Utf16=off,HugeFiles=on,4 CPUs)
Processing archive: system.ext4.win000
Extracting AndroidManifest.xml
Extracting res/layout-v17/settings_checkbox.xml
Extracting res/layout/disclaimer_dialog1.xml
Extracting res/layout/disclaimer_dialog2.xml
Extracting res/layout/disclaimer_dialog3.xml
Extracting res/layout/disclaimer_prototype.xml
file settings_checkbox.xml
already exists. Overwrite with
res/layout/settings_checkbox.xml?
(Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit? Y
Extracting res/layout/settings_checkbox.xml
Extracting res/mipmap-hdpi-v4/ic_settings.png
file ic_settings.png
already exists. Overwrite with
res/mipmap-mdpi-v4/ic_settings.png?
(Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit? A
Extracting res/mipmap-mdpi-v4/ic_settings.png
Extracting res/mipmap-xhdpi-v4/ic_settings.png
Extracting res/mipmap-xxhdpi-v4/ic_settings.png
Extracting res/xml/settings.xml
Extracting resources.arsc
Extracting META-INF/MANIFEST.MF
Extracting META-INF/SONY-ERICSSON-E-PLATFORM-SIGNING-LIVE-864F-3.SF
Extracting META-INF/SONY-ERICSSON-E-PLATFORM-SIGNING-LIVE-864F-3.RSA
Extracting classes.dex
Everything is Ok
Files: 17
Size: 433866
Compressed: 1618233344
[email protected]:/sdcard1/twrp/BACKUPS/CB5A20B0Q8/2015-12-25--.236 #
Click to expand...
Click to collapse
I haven't understood how this could have helped me, but i solved in another way:
I found notes folder in backup directory, then I used this program to extract files from fullbackupdata and finally i found my notes written in some databes files.
Hope this could help someone.