RomMaster.exe -w 5 OS.nb.payload -x -o xip.bin
?
there you go
Code:
RomMaster.exe -x -w 5 -b 0x320000 OS.nb.payload -o xip.bin
Related
I get the below when trying to extract some files from a rom.
I am trying to upgrade my G4 Cingular with WM5 to a rom with WM6. I just got the phone yesterday used from a friend. So far I have unlocked phone so that it works with my T-Mobile sim. Been reading and trying to update rom since last night.
A set of instructions I found wanted me to run typho5 from the dos prompt. but it appears to be looking for typhoonbfdecode.pl
Any help would be appreciated...
C:\newrom>typho5.exe -x nk.nbf
Usage: typhoonnbfdecode.pl filename
lists contents of filename
or typhoonnbfdecode.pl [-i] [-v] -x infile
extract modules
-i decode as sd header image
-t file is tornado nbf, with large header
-v also list headers
-s convert SPL to memory image
or typhoonnbfdecode.pl [-r module=file] [-p param=value] -c outfile
create new nbf
-s convert SPL memory image to nbf image
-t file is tornado nbf, with large header
-r specify the modules to read, module can be one of:
os, ipl, spl, splash or gsm
-p specify the header values, param can be one of:
device, language, magic, operator, flags, version or blversion
or typhoonnbfdecode.pl [-r module=file] [-p param=value] -d outfile
create sdcard image
-r specify the modules to read, module can be one of:
os, ipl, spl, splash or gsm
-p specify the header values, param can be one of:
docuniqueid, blversion, cid, seclevel, timestart, timeend
keys, cardid
Use WST (check my signature) and you'll have a nice GUI to do it for you
cheers
mestrini said:
Use WST (check my signature) and you'll have a nice GUI to do it for you
cheers
Click to expand...
Click to collapse
thanks...hope it's help me to learn how to cook my own rooms...
After installing stock versions of 4.0.4, 4.1.1, or 4.1.2, the kernel will mount the recovery partition as read only so that ClockWorkMod (or any other recovery) will not install properly. Here are the commands to fix the kernel so that it mounts the recovery partition as writable and turns off secure mode:
The following commands below assume that you have already downloaded your desired firmware from sammobile.com and have extracted the boot.img (kernel) file from it using the tar utility. This tutorial is for Linux only and tested on Ubuntu 12.04.
Code:
unmkbootimg boot.img
mkdir ramdisk
cd ramdisk
gunzip -c ../initramfs.cpio.gz | cpio -i
patch -p1 < ../ro.secure.diff
find . | cpio -o -H newc | gzip > ../initramfs-new.cpio.gz
cd ..
mkbootimg --kernel kernel.gz --ramdisk initramfs-new.cpio.gz --base 0x80000000 --cmdline 'console=ttyO2,115200n8 mem=1024M androidboot.console=ttyO2 vram=20M omapfb.vram=0:16M androidboot.carrier=wifi' -o new_boot.img
Contents of patch (ro.secure.diff):
Code:
--- ramdisk/default.prop.org 2013-02-18 03:40:22.442572189 +0100
+++ ramdisk/default.prop 2013-02-18 03:40:56.158572156 +0100
@@ -1,7 +1,7 @@
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
-ro.secure=1
+ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
I have attached also below an example of the flash-able zip file used for installing the new boot.img through ClockworkMod. Just replace the boot.img inside the kernel.zip file with the new boot.img that you just created from the directions above and sign the zip (signing is optional).
Hello everybody,
I am using The Titan Prime ROM (Version 1.0.2) on my XT1068. It is very stable and fast. (Thanks to @Shawn5162 and his helpers!)
Nevertheless I would like to make some modifications to the boot.img. I am able to modify the system folder and resign the package.
But if I try to unpack and repack the boot.img the phone jumps immediately into the bootloader after the start and says 'Fastboot Reason: Fall-through from normal boot mode'.
I hoped you could have a look at my workflow and tell me what I am doing wrong:
First I take your Rom and unzip it:
Code:
$ unzip TitanPrimeROMv1.0.2-XT1068-69.zip -d Titan
$ cd Titan
Here is what the boot_info tells me:
Code:
$ boot_info boot.img
PAGE SIZE: 2048
BASE ADDRESS: 0x00000000
RAMDISK ADDRESS: 0x01000000
CMDLINE: 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags'
Then I unpack the boot image:
Code:
$ unpack boot.img
Boot = boot.img
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
Kernel size 6449544
Kernel address 0x8000
Ramdisk size 807152
Ramdisk address 0x1000000
Secondary size 0
Secondary address 0xf00000
Kernel tags address 0x100
Flash page size 2048
Board name is ""
Command line "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags"
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
$ mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x0 --cmdline 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags' -o new_boot.img
---------------
2974 blocks
Now I make some minor modification to the boot image like adding a file:
Code:
$ touch boot/ramdisk/hello_ramdisk
Then I try to rebuild the ramdisk:
Code:
$ mkbootimg --kernel boot/zImage --ramdisk boot/new-ramdisk.cpio.gz --base 0x0 --cmdline 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags' -o boot.img
I remove the boot folder, zip it and sign it:
Code:
$ mv boot ../
$ zip -r myrom.zip *
$ java -classpath /opt/android-sdk/tools/sign/testsign.jar testsign myrom.zip myrom-signed.zip
Then I place the file on the sdcard and try to install it via TWRP ‘Install’.
I am not sure what I am doing wrong any help would be appreciated :fingers-crossed:
Edit
I have tried the same procedure with CM-12-unofficial and stock ROMs and the result is the same, if I touch anything.
Did you ever solve this problem?
Edit: https://github.com/xiaolu/mkbootimg_tools worked for me.
I was using this tool (http://forum.xda-developers.com/showthread.php?t=633246) to repack boot and recovery images but it's not working with my watch's images. I tried to repack it manually but result is same, it sticks at LG logo. Any suggestion on repacking would be great. Thanks.
Use linux machine and abootimg
Code:
sudo apt-get install abootimg // install abootimg
abootimg -x boot.img or recovery.img //unpack u .img
mkdir unpck // great folder unpck
cd unpck //go to unpck folder
zcat ../initrd.img | cpio -i //unpack initrd.img
after edit repack
find . | cpio -o -H newc | gzip > ../initrd.img //repack intird.img
cd .. //go back folder
abootimg --create name-boot-or-recovery.img -k zImage -r initrd.img //make recovery or boot img
abootimg --create name-boot-or-recovery.img.img -f bootimg.cfg -k zImage -r initrd.img
If error "boot.img: updated is too big for the Boot Image"
abootimg --create boot.img -k zImage -r initrd.img
abootimg --create boot.img -f bootimg.cfg -k zImage -r initrd.img -c "bootsize=size-in-error-bootsize"
So, this one does repacking - http://forum.xda-developers.com/showthread.php?t=2073775
hello,
anybody has an working mi 5x with (oxygen) unlocked bootloader ??
if yes please i need backup of aboot from edl mode by emmcdl.exe
like this
emmcdl.exe -p com5 -f prog_emmc_firehose_8953_ddr.mbn -d aboot -o aboot.mbn
emmcdl.exe -p com5 -f prog_emmc_firehose_8953_ddr.mbn -d abootbak -o abootbak.mbn
emmcdl.exe -p com5 -f prog_emmc_firehose_8953_ddr.mbn -d devinfo -o devinfo.bin
please if u dont know what m talking about dont replay.