how to create a os sdimg to update? - 8125, K-JAM, P4300, MDA Vario Software Upgrading

when i try to create a os sdimage from os.nb by using typhoonnbfdecode.pl,something is wrong. the program displays as:
read 03900000 for os from 04e3d4c0-OS.nb
no ECEC at 0x40 in OS image
how can i make the os sdimage?
The mini USB of my O2 miniS is damaged by the recharger,so the only way to update is from the miniSD.
I find that the typhoonnbfdecode.pl can make the sdimage for wiszard,so i install perl,and nbfutils.
when i try to create a spl sd image,i succeed.
the cmd is : perl typhoonnbfdecode.pl -r spl.nb -d sdimage
but when i try to create a os sd image from the os of O2 wm5 2.21.4.101 ,it displayed as :
read 03900000 for os from 04e3d4c0-OS.nb
no ECEC at 0x40 in OS image
what's wrong?
How can i create a Os sd image?

i have a damaged usb and i want to change the rom using the sd too
i hope someone helps us
i will try to find stuff too.

Related

Crash flashing BREEZE. Boot is working. Help me pls.

Hi, I flashing my friends Mteor from ROM 5.2.19593 (Build 19593.1.1.7) 1.038 to 1.044 and flashing crashed. Now working only switch to boot loader. I checked flash more rom from SD card, but finished on NOT ALLOW. It's problem nocompatibile SPL.
Now is boot with version
BREE100 IPL-1.0
BREE100 SPL-1.10.0000
I have second Breeze with working ROM 5.2.19593 (Build 19593.1.1.7) 1.044
Can you help me:
I need find new ROM compatibilite with SSPL-1.10.0000
or some program or some way for switch to SSPL-7.77 from SD_card or PC
or some way from full backup form my Mteor anf restore to second Mteor.
Can i use program and adress from HTC Wing? I don't know prosses for restore it.
REM This creates a backup of your current SPL
mkdir 1
REM cecopy SurrealNetworksAppUnlock.cab dev:\
REM prun SurrealNetworksAppUnlock.cab
pmemdump -a 0x8C000000 0x40000 1\spl-backup.nb
echo "spl-backup.nb written to subdirectory 1"
pause "press return to exit"
REPAIRED
It's possiblle flashing SSPL 1.10.000 by Russia original flash QTEK_A07 from http://wiki.xda-developers.com/index.php?pagename=Breeze_Upgrades
next time i flashed hardSPL 7.77
next time i flashed new ROM from.

why can I install radio please, but Roms yes ?

hello and sorry for my bad English because I'm French.
Excuse me if my application you bored but I would simply like to improve radio reception with Radio 1.10.25.18 that seems better than what you offer and where I work, I barely get the signal.
I bought it released all operators.
I realized that my seller had purchased from the operator SFR and he has certainly made available for all operators to sell because his bill comes from SFR.
I can not install the Radio 1.10.25.18 with X1_RUU_Radio_UpdateUtility.
my X1 is released to all operators.
I use it with the operator Orange.
when I started the flash to install the new radio after synchronization total NETFramework 3.5 installed,
I have the following information in the PC:
IMAGE VERSION: 1.02.933.3
UPDATE TO: 1.00.000.0
I click to start operation
on GSM, the screen goes black, and 3 colors with which all this appears:
KOVS110
KPL-0.72 Olinex
MicroP1-707
MicroP2-707
then the screen goes gray with these instructions:
loading ...
NO IMAGE FILE!
then again with 3 colors:
KOVS110
KPL-0.72 Olinex
MicroP1-707
MicroP2-707
and then the gray panel with the update that begins and always fails to 5% growth and re gsm starts as if nothing had been attempted.
on my PC, I have the following information:
ERROR 244: INVALID MODEL ID
This utility can not be used for you PDA Phone.
Please check you Update utility
N-KPXV5667-S-RBRK./01 *
I have operate hard spl utility before, 100% ok
can you confirm that my problem is that it is not supercid and if so, could you help me?
thank you in advance
1- Be sure your phone ir > 50% battery charge (100% recommended)
2- Remove the SD card from the phone
3- Rename the radio file to KOVSimg.nbh and be sure to copy the radio file into THE SAME FOLDER where the RUU radio update utility exe is located
4- Be sure you put ONLY ONE *.nbh file into the RUU folder
PLAN B: Temporarily set your Windows PC to ENGLISH in
-> "control panel" -> "Region and Language configuration"
PLAN C: Use the micro SD card flashing method instead of the "RUU from PC" method
thank you gtrab, I try it !!
yes the "no image file" is because the x1 in bootloader (tricolour screen) is searching the SDcard for the KOVSimg.nbh file.
- Be sure your phone ir > 50% battery charge (100% recommended)
I have wait to get 80% into battery before trying
2- Remove the SD card from the phone
ok
3- Rename the radio file to KOVSimg.nbh and be sure to copy the radio file into THE SAME FOLDER where the RUU radio update utility exe is located
I have rename : this radio name "DIAMING.nbh" in "KOVSimg.nbh"
I have use : Radio v1.10.25.18 (Xperia)(52.56.25.29H) (SU) (Quad Band)
ligne n°3 : http://forum.xda-developers.com/showthread.php?t=470306
4- Be sure you put ONLY ONE *.nbh file into the RUU folder
only KOVSimg.nbh inside
I obtain only this result :
when I started the flash to install the new radio after synchronization total NETFramework 3.5 installed,
I have the following information in the PC:
IMAGE VERSION: 1.02.933.3
UPDATE TO: 1.00.000.0
I click to start operation
on GSM, the screen goes black, and 3 colors with which all this appears:
KOVS110
KPL-0.72 Olinex
MicroP1-787
MicroP2-707
finish to get this message :
loading ...
NO IMAGE FILE!
and then the gray panel with the update that begins and always fails to 4% growth and re gsm starts as if nothing had been attempted.
on my PC, I have the following information:
ERROR 244: INVALID MODEL ID
This utility can not be used for you PDA Phone.
Please check you Update utility
N-KPXV5667-S-RBRK./01 *
after :
PLAN B: Temporarily set your Windows PC to ENGLISH in
-> "control panel" -> "Region and Language configuration"
I try it, the same result
PLAN C: Use the micro SD card flashing method instead of the "RUU from PC" method
can you inform me please better about this method ?
thank a lot !
__________________
Couguy said:
..."DIAMING.nbh" in "KOVSimg.nbh"
I have use : Radio v1.10.25.18 (Xperia)(52.56.25.29H) (SU) (Quad Band)
ligne n°3 : http://forum.xda-developers.com/showthread.php?t=470306
Click to expand...
Click to collapse
LOL
That's a DIAMOND RADIO !!
Not suitable for Xperia X1 !!
You need to hex-edit the radio to make it compatible with Xperia X1
You can download some radios already hex-edited for Xperia X1 FROM THIS THREAD or you can learn how to hex-edit any radio by yourself CHECKING THE RADIOS THREAD HERE
I wrote a mini-tutorial on how to hex-edit radios HERE, page 9, post 87 from the Radio's thread
ecrivez moi un message privé si vous avez besoin de plus aide
thanks, I send you a MP
I close this post and a big tanks to gtrab for the superb help !!!!
all is good now with this :
I downloaded the file ONLY into this post :
http://forum.xda-developers.com/showthread.php?t=466404
there are others post where there are possibility to download radio special Xpéria but at the end, there are not the same and my problem com from all these others links !
I renamed as indicated
I removed the memory card.
I launched the operation and OK.
if you get this like me at firt:
transfert 99% and error 262, wait 100% about battery and retry !
thank you
Removed the SD card and OK.
gtrab said:
1- Be sure your phone ir > 50% battery charge (100% recommended)
2- Remove the SD card from the phone
3- Rename the radio file to KOVSimg.nbh and be sure to copy the radio file into THE SAME FOLDER where the RUU radio update utility exe is located
4- Be sure you put ONLY ONE *.nbh file into the RUU folder
PLAN B: Temporarily set your Windows PC to ENGLISH in
-> "control panel" -> "Region and Language configuration"
PLAN C: Use the micro SD card flashing method instead of the "RUU from PC" method
Click to expand...
Click to collapse
Same problem. Removed the SD card and OK.
Thanks...

750 Dead after flashing with wrong OS

Hi everyone,
I have a big problem and I need urgent help please. I have ATT 750 unlocked and I'm outside the States now. My Treo was 6.0 then I upgrade it to 6.1 so far so good.
Then I saw a custom rom that I thought it was interesting. the custom rom was for HTC Dimond I think. without paying too much attention. I started the upgrade. It went 70% before the upgrade crashed.
Now my Treo is not responding to anything. I have the original ATT 6.0 SD upgrade and I have the 6.1 lite upgrade. I'm using CheetahUnlocker to flash the SPL (that is working) but when I try to install the 6.0 or 6.1 using Kaiser Custom RUU v1 it crash.
I saw an earlier post that suggest to place the original 6.0 on a freshly formatted SD and install from there. that is not working either. when I try to install the software it goes into these steps before it crashes: btw, I have the tri-color bar and it has the following info:
CHEE100
IPL-0.20
SPL-1.40.01iNex
while update in progress i see the following:
CHEEIMG.nbh
SPLASH1 - OK
BOOTLOADER - OK
GSM - OK
MicroP - OK
EXTROM - Fail
OS -
After the crash I get this msg: "Update Terminate Update Failed"
Any suggestion please? need more info? then let me know
Thanks in advance
Sam
Someone please help.... I'm sure someone has some suggestions.
By the way, I've tried RUUwrapper and that didn't help either.
Thanks in advance
I've got the same problem and finally I can solve my problem.
The procedure :
1. Open mtty and by connection via usb, just do :
Command mtty:
- task 2a
- flash:
[1- press enter
2 - type "set 14 0"
3 - type "task 28 55aa"]
you shoul see now the program runing a lot of things that I don`t remember what...
then when it ends try the SD instal...
If It still doesn`t work then:
[1- press enter
2- "erase"
3- "checksum"
4- "checkimage"
5- "task 0"]
then reflash your radio & OS by SDCARD...
- set 16 0 0
- info 7
- info 8
2. It means your PDA has no ROM OS and Radio.
3. Copy CHEEIMG.nbh (ROM OS) to formatted SD Card.
4. Insert the SD Card to PDA and just install by push the 3rd side button together with soft reset (by stylus).
5. Replace file CHEEIMG.nbh (ROM OS) with CHEEIMG.nbh of Radio.
6. Do same procedure as number 4.

Tattoo Custom Recovery Image

I'm starting this thread to document the work on creating a custom recovery image for the Tattoo.
The main goal is to provide a recovery image that will serve as the launchpad for flashing custom roms.
The Tattoo Custom Recovery Image will provide:
1) A way to use an update.zip signed with test-keys (already accomplished);
2) A way to perform a full backup of mtd2,mtd3,mtd4 and mtd5 (boot,system,cache and data).
3) A way to perform a full restore of the backup achieved by 2);
4) Adb support (already accomplished);
4.1) Adb shell support.
I'm open to input about using nandroid. Right now, without a S-OFF/ENG SPL this looks useless.
Also, if you have any other special need for recovery, please feel free to express it
Alpha release
Tattoo's Custom Recovery Image, Alpha Release
This first release includes:
- ADB enabled recovery
- ADB enabled root shell
- Accept update.zip signed with test keys
- All partitions mounted
- Custom recovery program (the last two options are stubs, not really working yet)
- Included in /sbin: busybox, flash_image and BART
- I've not used BART and, at the moment, cannot attest if it works or not.
- Backup script in /sbin/backup.sh
- Restore script in /sbin/restore.sh
With this custom recovery you can now do a full backup of your unit, by dumping the mtd block devices to your sdcard. Afterwards, you can use flash_image to recover your Tattoo to it's previous state.
I'm releasing this image as is. This is not a point-and-click recovery tool. If you don't know what you're doing, you can seriously damage your unit. The only reason I'm releasing this is in an effort to provide other devs with a way to easily recover their units, back to day-to-day configuration, while experimenting with them.
To flash:
Copy TCRI.alpha.img to /sdcard.
Run "flash_image recovery /sdcard/TCRI.alpha.img"
To reboot into recovery (quickest way)
adb reboot recovery
Please comment
thanks for you work
i try to flahs and get permission denied, do you know why?
flash_image: permission denied
chusen said:
i try to flahs and get permission denied, do you know why?
Click to expand...
Click to collapse
Partition remounted writeable from a fresh rebooted system with the tattoo-hack.ko module inserted??
But I'm sure you did that before because of:
I'm releasing this image as is. This is not a point-and-click recovery tool. If you don't know what you're doing...
Click to expand...
Click to collapse
;-)
-bm-
Thank you very much for your excellent job
Someone could install custom alpha recovery?
thx
@-bm-:yes I will try that way since the beginning. i mount with rw permissions /system and /data. i know is not a point-and-click recovery tool but i think i need more permissions but where?
Where did you guys get your flash_image binary from ?
The error you're getting is from flash_image, not from my recovery image.
I'll attach the flash_image I've been using to this post.
Please tell me if this solves your problem. You need tattoo-hack.ko module inserted, if you're using a release kernel.
Edit: You have the correct permissions in your flash_image binary, right ? After pushing it to the device, don't forget to chmod 755
It works I like drawing, jejeje.
Backup and Restore functionality appears to have no further
The adb root shell is perfect
Very good Work
for when the beta version? and the final version? lol
I try to dump the system userdata and boot.img and when i try to extract with unyasffs and i get this when i try to extract system.img
Code:
4 [main] unyaffs 3940 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
644 [main] unyaffs 3940 open_stackdumpfile: Dumping stack trace to unyaffs.exe.stackdump
and this with others
Code:
broken image file
Code:
[email protected]:~/Tattoo/images/boot/1$ ../../unpack.pl ./boot.1.img
Page size: 2048 (0x00000800)
Kernel size: 1899580 (0x001cfc3c)
Ramdisk size: 160952 (0x000274b8)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1 console=null
Writing boot.1.img-kernel ... complete.
Writing boot.1.img-ramdisk.gz ... complete.
528 blocks
[ boot.1.img-ramdisk.gz decompressed to boot.img-ramdisk ]
My image dumping script is OK
Take a look here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
The boot.img is not a yaffs2 image. It's a special format, comprised by a 2k header, a kernel image and a ramdisk.
The system.img is a yaffs2 image. From unyaffs's homepage: "Unyaffs is a program to extract files from a yaffs file system image. Now it can only extract images created by mkyaffs2image."
Chusen, I think it would be better to create a new thread for this, since it doesn't concern the custom recovery image directly.
Thank god for custom recovery!
Now we can really start cooking ROMs... gonna break out the tools tonight and get Android 1.6/2.1 sources ready to compile.
leon1984 said:
for when the beta version? and the final version? lol
Click to expand...
Click to collapse
You tell me
Next in line is to tie the backup/restore scripts to the UI, which won't be too hard.
Later, I may mess around with nandroid and bart, to see if they provide something more than my scripts.
Afterwards, when we have some custom roms available, I may create a downloader/updater option, to make it easier to install those.
Also, I'm taking requests for new features
suggestions about scripts
Excellent work, mainfram3. Thank you.
I have extracted the img file, and check backup.sh and restore.sh scripts. The code for checking sdcard remaining space is done. Here it is:
Code:
## TEST: Check free space in sdcard
NEED_KB="200000"
REM_KB=`du /sdcard | awk '{print $6}'`
if [ ${REM_KB%K} -lt $NEED_KB ]; then echo "Not enough space in /sdcard, exiting"; exit; fi
backup space min set to 200MB.
There is another suggestion about restore.sh. Because of backing up img to /sdcard/Backup, $1 might not be needed, right?
mainfram3 said:
Code:
[email protected]:~/Tattoo/images/boot/1$ ../../unpack.pl ./boot.1.img
Page size: 2048 (0x00000800)
Kernel size: 1899580 (0x001cfc3c)
Ramdisk size: 160952 (0x000274b8)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1 console=null
Writing boot.1.img-kernel ... complete.
Writing boot.1.img-ramdisk.gz ... complete.
528 blocks
[ boot.1.img-ramdisk.gz decompressed to boot.img-ramdisk ]
My image dumping script is OK
Take a look here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
The boot.img is not a yaffs2 image. It's a special format, comprised by a 2k header, a kernel image and a ramdisk.
The system.img is a yaffs2 image. From unyaffs's homepage: "Unyaffs is a program to extract files from a yaffs file system image. Now it can only extract images created by mkyaffs2image."
Chusen, I think it would be better to create a new thread for this, since it doesn't concern the custom recovery image directly.
Click to expand...
Click to collapse
and if you want to extract the boot.img here are the two scripts you need to fully extract the kernel(zImage) and ramdisk
split_bootimg.pl
and
extract-ramdisk.sh
they are attached below
jamezelle:
extract-ramdisk.sh missed #!, and the ramdisk zip file should be passed to $1 of this script.
mainfram3 said:
1) A way to use an update.zip signed with test-keys (already accomplished);
Click to expand...
Click to collapse
Hi mainfram3,
I don't want to jack your thread - could you add a little elaboration on this point, or provide a URL so I can learn a little more? The SPL on the phone (oem-78 or fastboot mode) accepts updates signed with the test key from the SDK? (Or some other key?) (On the Eris, the "rom.zip" files unpacked by the RUU are prepended with a mystery blob of 256 bytes - s'pose it could be a mic/sig, but if that's what it is, it don't appear to be in a standard DSA/RSA format, and those .zip files are not signed using the .apk/.jar manifest-signing method)
FYI here's an entertaining story of an epic fail in a related area. After reviewing the fastboot sources from the android tree, I decided that I wanted to spy on the (Windows) RUU update program by sniffing the USB bus - in particular to see if it was explicitly passing signatures in .sig files. (That's an undocumented command-line behavior in fastboot.)
Turns out that recent versions of libpcap and Wireshark allow for USB bus capture on Linux - and using the "usbmon" kernel module in Ubuntu 8.04 LTS, sniffing the USB (5k packet size) seems to work without hitch, even at USB 2.0 speeds. So I took it one step further, and installed WIn Xp SP3 in a QEMU VM on the Ubuntu machine, with the intention of running the RUU updater inside the Xp VM and sniffing the USB bus in the host OS (Linux) machine.
The result? QEMU/Win Xp VM can talk to the phone in either fastboot or adb mode, but bluescreens as soon as you start to move data at any appreciable rate. Doesn't seem to be dependent on whether monitoring is taking place. I might try putting the phone behind a cheapo USB 1.1 hub, and see if that helps, but for the moment I am stopped out on this hack.
bftb0
cn.fyodor said:
jamezelle:
extract-ramdisk.sh missed #!, and the ramdisk zip file should be passed to $1 of this script.
Click to expand...
Click to collapse
it works yea sorry about the
#/bin/sh
i didnt write the scripts btw

Auto-Modify Boot Image [New! Ported to Windows, 23 Aug 2012]

I ported my automatic boot image modifier from Linux/Ubuntu to Windows. As with the Ubuntu version, my auto-modifier redirects ROM filesystem mounts from emmc (internal memory) to SD card (external memory) in the boot image to more quickly boot a ROM hosted on SD.
Features
Simple, lightweight install. No need to separately install Cygwin and required packages.
As with the Ubuntu version, the boot image ramdisk directory is automatically modified to redirect filesystem mounts for /system, /cache and /data from emmc to SD card so you can quickly boot a ROM hosted on SD. No other changes are made, though the Perl code can be altered as necessary to further modify ramdisk.
Tested working on XP using NottachTrix 1.3.1 AT&T boot image file. For Win 7, you may need to tweak User Access Control (UAC) to launch Cygwin.
Note: The unpacker script is just a copy of “split_bootimg.pl“ found here: http://www.enck.org/tools.html (Thanks Bill.)
Instructions
1. Download cygwin-auto-modify-boot.zip (50MB) here: http://www.mediafire.com/?kz9fqzwznzizb1z
2. Unzip files to Windows c:\ . OR, if you already have a fully functioning c:\cygwin build that contains the Perl v5.14.2, cpio and gunzip binaries, you should only need to extract the directory: cygwin\home\modify-boot to c:\. In any event, you should backup your existing c:\cygwin directory prior to unzipping.
3. Copy the original boot image file (boot.img in this example) to c:\cygwin\home\modify-boot
4. Navigate to c:\cygwin and launch c:\cygwin\cygwin.bat . This opens a cygwin command window, and also generates a set of user configuration files if opened for the first time.
5. In the Cygwin command window, enter: cd ../modify-boot . Here is my directory listing after Cygwin configured my system:
6. In the Cygwin command window, enter the command: ./modify-boot.sh boot.img and press Enter at the prompts. For me, the entire process took ~30 seconds to modify a NottachTrix boot image.
If everything goes right, the system creates a “boot-repack.img” file based on the modified ramdisk and stores it in the modify-boot directory. Various log/debug data are presented on screen and stored in the modify-boot directory.
That’s all! From here you can “fastboot flash boot boot-repack.img” to boot your SD-based ROM, or store the modified image in a boot configuration directory. See http://forum.xda-developers.com/showthread.php?t=1645344
Please note: The size of my dev team has never exceeded one (me); yet I will try to field requests for help as I am able.
References and Credits
http://cygwin.com/install.html
http://www.enck.org/tools.html
http://forum.xda-developers.com/showthread.php?t=1630130
+++++
Linux/Ubuntu Version
Many have studied this excellent tutorial on how to unpack, modify and repack Android ROM boot images: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images. Its contents form a solid baseline for customizing ROM boot images and ROMs in general. Here I attempt to automate the process of modifying boot images.
Results thus far provide an efficient means of booting ROMs that are cloned to SD card (see my clone thread: http://forum.xda-developers.com/showthread.php?t=1764680 ), as shown in the example below.
modify-boot zip: http://www.mediafire.com/?luobv279pcv827k contains five files: three Perl scripts to unpack, modify and repack a boot image, the “mkbootimg” executable, and an executive batch file to run the three Perl scripts in sequence.
Boot image modifier script: modify-bootimg-atrix.pl features a useful example of how customizations can be pre-programmed by including code to redirect ROM filesystem mounts to SD card, thus enabling us to boot SD card-based ROMs --- almost on the fly.
Of course there are many references to customizing boot images, but to my knowledge this is the first published attempt to automate the process. And since there are some interesting projects related to hosting Perl on Android (see References below), I think it would be fun to develop a CWM-flashable zip (or similar tool) that loads a Perl script interpreter and then runs a pre-programmed boot image modifier --- all on phone, without computer aiding.
Preliminaries
Linux-based OS (Ubuntu 12.04 preferred --- it's still free)
Android SDK Platform Tools (includes adb and fastboot)
Perl (Ubuntu 12.04 includes Perl 5.14.2)
Example: Boot Neutrino V2.8 GT cloned to SD card
Suppose we have already cloned Neutrino V2.8 GT ROM (/system, /cache and /data) to SD card. To boot it:
1. Download modify-boot.zip: http://www.mediafire.com/?luobv279pcv827k to Desktop and extract directory: /modify-boot to ~/Desktop
2. Extract boot.img from Neutrino V2.8 GT ROM.zip and drop it in ./modify-boot
3. Open a terminal, get root and cd ~/Desktop/modify-boot
4. Enter: “sh ./modify-boot.sh boot.img” and follow prompts (Output file: boot-repack.img)
5. Boot to fastboot and connect phone to computer
6. fastboot flash boot boot-repack.img
7. fastboot reboot
Once phone is booted, we can run a sanity check by entering:
adb shell (access Android filesystems)
# mount
Results should include the highlighted device names for filesystem mounts:
Code:
[COLOR="Blue"]/dev/block/mmcblk1p2 on /system[/COLOR] type ext4 (rw,noatime,nodiratime,errors=continue,barrier=0,nobh,data=writeback,noauto_da_alloc,discard)
[COLOR="Blue"]/dev/block/mmcblk1p4 on /data[/COLOR] type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback,noauto_da_alloc,discard)
[COLOR="Blue"]/dev/block/mmcblk1p3 on /cache[/COLOR] type ext4 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=0,nobh,data=writeback,noauto_da_alloc,discard)
We can now boot a cloned Neutrino V2.8 GT ROM from SD card, and/or save the modified boot image in a safe, visible location on SD card to configure dual boot (please see: http://forum.xda-developers.com/showthread.php?t=1645344 ). Or, we can roll the modified image into a flashable zip for a standalone boot push.
Standard disclaimers apply. In short, I am not responsible for any harm you or your phone may incur by using any or all of this material.
References
http://code.google.com/p/perldroid/
http://code.google.com/p/android-scripting/
http://forum.xda-developers.com/showthread.php?t=1585009
Credits
Many thanks to the Android Community Effort ( http://android-dls.com/wiki/index.php?title=Main_Page ), and to my friend and xda member ghost_og for his “mkbootimg” command-line fix that made boot image repacking work for Atrix.
Boot modifier script: modify-bootimg-atrix.pl includes logic to search both init.rc (Blur) and init.olympus.rc (CM) in ramdisk for ROM filesystem mounts.
Hi,
If you look at my Gobstopper for 2.3.6 I do exactly this kind of thing. I unpack the boot image into kernel and initramfs, modify init.rc, package it up again and flash back to boot. The binaries and source are included if you want to take a look.
Cheers!
Is it possible to modify partitions numbers? because i use different partitions because of webtop2sd and swap partition?
Adam
NFHimself said:
Hi,
If you look at my Gobstopper for 2.3.6 I do exactly this kind of thing. I unpack the boot image into kernel and initramfs, modify init.rc, package it up again and flash back to boot. The binaries and source are included if you want to take a look.
Cheers!
Click to expand...
Click to collapse
Elegant! Does it support multiple command lines? Also, does it support AT&T yet?
sendust7 said:
Elegant! Does it support multiple command lines? Also, does it support AT&T yet?
Click to expand...
Click to collapse
There is nothing Bell specific to it, static linked binaries so no rom dependence. It doesn't do anything about multiple command lines, no, the normal boot/recovery images have any at all, let alone multiple ones.
Cheers!
Is that right?
"5. Boot to fastboot and connect phone to computer
6. fastboot flash boot-repack.img
7. fastboot reboot"
Because my output is like this:
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools# ./fastboot flash boot-repack.img
unknown partition 'boot-repack.img'
error: cannot determine image filename for 'boot-repack.img'
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools#
and, of course, the boot-repack.img is in the same folder of fastboot
---
I've tried fastboot flash boot boot-repack.img. It softbricked
Reflashing the original boot.img de-bricked it without a hassle. Guess your solution is not compatible with Morrisoft CM7 ROM
GTMoraes said:
Is that right?
"5. Boot to fastboot and connect phone to computer
6. fastboot flash boot-repack.img
7. fastboot reboot"
Because my output is like this:
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools# ./fastboot flash boot-repack.img
unknown partition 'boot-repack.img'
error: cannot determine image filename for 'boot-repack.img'
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools#
and, of course, the boot-repack.img is in the same folder of fastboot
---
I've tried fastboot flash boot boot-repack.img. It softbricked
Reflashing the original boot.img de-bricked it without a hassle. Guess your solution is not compatible with Morrisoft CM7 ROM
Click to expand...
Click to collapse
Soft-brick is usually caused by one or more of the following:
1. The three ext partitions required to host ROM on SD card either do not exist, are not big enough or are corrupt.
2. The three ext partitions exist but no ROM is installed
3. ROM is not compatible with phone
4. User does not wait long enough for phone to boot after installing ROM. First boot usually takes 3 to 5 minutes as the phone is building cache. Subsequent boots should not take longer than a minute with a Class 4 or higher SD card.
And yes, the boot command should be: fastboot flash boot {boot-image}
Cheers
I ported my automatic boot image modifier from Linux/Ubuntu to Windows. As with the Ubuntu version, my auto-modifier redirects ROM filesystem mounts from emmc (internal memory) to SD card (external memory) in the boot image to more quickly boot a ROM hosted on SD.
Features
Simple, lightweight install. No need to separately install Cygwin and required packages.
As with the Ubuntu version, the boot image ramdisk directory is automatically modified to redirect filesystem mounts for /system, /cache and /data from emmc to SD card so you can quickly boot a ROM hosted on SD. No other changes are made, though the Perl code can be altered as necessary to further modify ramdisk.
Tested working on XP using NottachTrix 1.3.1 AT&T boot image file. For Win 7, you may need to tweak User Access Control (UAC) to launch Cygwin.
hi, the size from my original boot is 8 megas, after unpack and repack the size is 4.8 megas, and does not work, my boot is from motorola xt928, did you know why change the size,,thanks
Using CM10 from SD Card (Nottachtrix on internal)
For anyone looking to run Nottachtrix (or other rom) from internal memory and CM10 from external. You'll run into the same problem I did. The init.rc and init.olympus.rc files don't contain the partition information. You need to update the fstab.olympus file in the boot.img. I've attached mine for comparison. (note, after repartitioning my SD Card several times I ended up with a phantom partition (mmcblk1p4) therefore my data is actually on mmcblk1p5.
SD card partition sizes:
System: 340mb
Cache: 700mb
Data: 1.25gb
Additional notes about my partitioning experience:
The DD command in linux (and ADB) copies the entire partition exactly to the SD card's partition, therefore you lose space if you leave it this way. I used DD, but then used fsarchiver to backup all of the sd card's partitions, repartitioned the card again, and restored the partition info with fsarchiver. This made my SD card a lot cleaner and avoided wasting any space.
Everything's running great now. Thank you everyone who made dual booting possible!
Would this tool work on Desire HD?
Need some help. I pulled the boot.img created from ROM1 using copy-boot.img (until step 5 here) and when I ran modify-boot.sh on it, I got the below message:
Unpacking boot image...
Found a secondary file after the ramdisk image. According to the spec (mkbootimg.h) this file can exist, but this script is not designed to deal with this scenario.​
So, I got the boot-NottachTrix-1.3.1-att-sd-ext.img file from this thread and fastboot flashed it, thinking it is already modified, but my phone didn't boot. Then I tried running modify-boot.sh on it and then realized that it has a binary that won't run on mac.
Could someone tell me if I am on the right track with the 2nd steps above so that I can get hold of a ubuntu machine? I tried running it on a puppy linux livecd and it didn't work.
Why didn't the first step work? Is the boot.img created by the copy-boot.sh not in the right format?
Update: I forgot to mention this, but I have NottachTrix 1.3.1 installed on emmc but the size of the boot.img extracted by copy-boot.sh doesn't match that of the one attached to the above link. The one linked is size 3440640 while the one copy-boot.sh created is of size 8388608. For now, I fastboot flashed the later and got back into ROM1. I meanwhile got a livecd boot of ubuntu and ran modify-boot.sh on the one I downloaded and it created boot-repack.img successfully, but I had no success booting with it either.
irha said:
Need some help. I pulled the boot.img created from ROM1 using copy-boot.img (until step 5 here) and when I ran modify-boot.sh on it, I got the below message:
Unpacking boot image...
Found a secondary file after the ramdisk image. According to the spec (mkbootimg.h) this file can exist, but this script is not designed to deal with this scenario.​
So, I got the boot-NottachTrix-1.3.1-att-sd-ext.img file from this thread and fastboot flashed it, thinking it is already modified, but my phone didn't boot. Then I tried running modify-boot.sh on it and then realized that it has a binary that won't run on mac.
Could someone tell me if I am on the right track with the 2nd steps above so that I can get hold of a ubuntu machine? I tried running it on a puppy linux livecd and it didn't work.
Why didn't the first step work? Is the boot.img created by the copy-boot.sh not in the right format?
Update: I forgot to mention this, but I have NottachTrix 1.3.1 installed on emmc but the size of the boot.img extracted by copy-boot.sh doesn't match that of the one attached to the above link. The one linked is size 3440640 while the one copy-boot.sh created is of size 8388608. For now, I fastboot flashed the later and got back into ROM1. I meanwhile got a livecd boot of ubuntu and ran modify-boot.sh on the one I downloaded and it created boot-repack.img successfully, but I had no success booting with it either.
Click to expand...
Click to collapse
I have a newer thread: Dual Boot Atrix: Simplified and Standalone: http://forum.xda-developers.com/showthread.php?t=2124668
which presents my own custom standalone tools to do the following:
Partition SD card
Copy ROM from EMMC to SD
Flash boot image via Atrix Boot Emporium
Flash another ROM of choice to EMMC
No computer required.
On first boot, elapsed time from power-up to welcome screen can be several minutes --- especially for larger ROMs --- as the system is building cache.
Hope this helps
sendust7 said:
I have a newer thread: Dual Boot Atrix: Simplified and Standalone: http://forum.xda-developers.com/showthread.php?t=2124668
which presents my own custom standalone tools to do the following:
Partition SD card
Copy ROM from EMMC to SD
Flash boot image via Atrix Boot Emporium
Flash another ROM of choice to EMMC
No computer required.
On first boot, elapsed time from power-up to welcome screen can be several minutes --- especially for larger ROMs --- as the system is building cache.
Hope this helps
Click to expand...
Click to collapse
Thank you very much! I was able to directly go to the step 4, since I manually copied the partitions already and after verifying that I could boot into the sdcard, used the steps in the "Configuring Dual Boot" thread to get it switch between the two.
It looks like my sdcard is too slow to run android from it, so I will have to find another faster card

Categories

Resources