I got a XDA new ROM which is 4.00.01. It's a BIN file. 32 MB. I don't know how to flash it. Anyone has ideas?
What's the exact size in bytes?
I have seen .bin files which start with the string 'B000FF'
you can use
Code:
perl splitrom.pl yourfile.bin -wo outfile.nb1 -t nb1
to convert it to nb1.
you can find splitrom.pl in the mkrom distribution archive.
splitrom understands several types of romimages.
Can I convert to NBF file? So that I can use PROGRAM A to install. Size is 33,555,995 bytes. It start with B000FF.
you must make sure there is either a bootloader in your .bin file,
or you get a bootloader from another source.
you can extract a bootloader from another nbf file using
Code:
perl splitrom.pl yournbf.nbf -wl bootloader.nb0
you must make very sure that your nbf really contains a bootloader, if it doesn't and programme a overwrites it with junk, you will have your self a brand new hightech paperweight.
a safer way to burn unknown images, is via an sd card + xdarit + bootloader mode.
What is the command to convert to NBF once I got the bootloader? When I try to extract the bootloader, I got the following message: "80000000 - 80040000 -- bootloader 0 files 1 modules". Does that mean no bootload information inside the NBF file?
that means you are looking at a file containing just a bootloader, no OS.
Code:
perl splitrom.pl yourfile.bin -rl bootloader.nb0 -wo outfile.nbf -t nbf -n PW10A1-ENG-3.17-001
to convert .bin + bootloader to .nbf
you can check the result again using
Code:
perl splitrom.pl outfile.nbf
Sorry about having so many questions. How can I make sure that the nbf really contains a bootloader? I use the NBF file from O2 UK RUU 3.17.03 to extract bootloader which under PROGRAM A folder. Can I use "perl splitrom.pl yourbin.bin -wl bootloader.nb0" to
extract the bootloader from my BIN file? I use UltraEdit to view the BIN file, I notice some information about bootloader 5.22 (not 5.17). The person give me this ROM said it's the PPC 2003 final. Actually I was given a HTC tool to flash the BIN file. But when I load the bin file, it checks my SD card and tells me invalid card. So I cannot flash directly.
well, that is a difficult question. in an ideal world we would have ready a list of bootloaders, and md5sums of these. for easy idendification. but not done that yet. su currently I look at the binary. and see if I see this line in the hexdump:
0000060: 4543 4543 0010 0a8c 0000 0000 0000 0000 ECEC............
and at about 0001580 there should be some lines with '*' and 'init debugserial...'
then it at least resembles something that looks like a bootloader, and not accidentally an os image. ( yes, that is a mistake we made fore you, leading us to abother intersting development : jtag flashing
5.22 is the latest I saw too.
so does your .bin file start with 'b000ff' ? can you maybe upload this file to
ftp://xda-developers.com ?
actually we noticed that somehow for recent roms the bootloader was not flashed by programme A. even though we managed to overwrite it with crap with one of our own experiments. possibly a different version of programme A. we have not researched this yet.
I would be interested in that htc program too.
you can only extract a bootloader from your .bin file if it contains one. .bin files may contain any memory region. so I don't know if yours does.
I saw the following information. So I believe it has bootloader.
0000060: 4543 4543 0010 0a8c 0000 0000 0000 0000 ECEC............
about 0001580 there should be some lines with '*' and 'init debugserial...'
I've done the following. I don't know if I'm right.
1. I run "perl splitrom.pl yourfile.bin -wl bootloader.nb0 -t nb0" to extracted the bootloader.
2. Run "perl splitrom.pl yourfile.bin -wo outfile.nb1 -t nb1" to extract OS.
3. Run "perl splitrom.pl yourfile.bin -rl bootloader.nb0 -wo outfile.nbf -t nbf -n PW10A1-ENG-4.00-001" to get NBF file. I got error message said romimage already has bootloader. So I run "perl splitrom.pl yourfile.bin -wo outfile.nbf -t nbf -n PW10A1-ENG-4.00-001" to convert to NBF file directly. I dont' know if this the right command to convert BIN to BNF file, but I didn't see any error.
4. I run "perl splitrom.pl outfile.nbf" to check and below is the result.
rommap: 80000000-81f00000
no xipchian found
no operator rim found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8015c5c8 -- kernel 5 files 5 modules
80180000 - 80376bd0 -- kernel 10 files 14 modules
80380000 - 8064306c -- kernel 20 files 36 modules
80670000 - 80be66a8 -- kernel 107 files 88 modules
80c80000 - 8102ce98 -- kernel 11 files 36 modules
81050000 - 813ef114 -- kernel 95 files 44 modules
81400000 - 815d2238 -- kernel 34 files 7 modules
815f0000 - 8171bc7c -- kernel 56 files 19 modules
817c0000 - 81adf390 -- kernel 109 files 40 modules
81980000 - 81925800 -- bitmap :30000be5 .. 010000ea
I tried to upload the file to your FTP. But no permission. Please PM your MSN Messenger ID, so that we can discuss more baout this ROM.
Thanks
I don't have msn, but you can find me on irc in #xda-developers on ircnet
( if you don't know a server: irc.nl.uu.net )
3: yes, that should work.
if you want to replace the exsisting bootloader, you can type "perl splitrom.pl outfile.nb1 -rl bootloader.nb0 -wo outfile.nbf -t nbf -n PW10A1-ENG-4.00-001"
4: ah, ppc2003 roms have a different structure splitrom cannot yet find
the xipchain in its new location. that is why it says 'kernel' on all lines.
also the bitmap it mentions is not the bitmap.
another issue may be that the nbf it creates has the wrong size, since
the xipchain in ppc2003 roms is in a location which was not originally
present in nbf files, I am not sure if programme a can write it correctly.
forgot to tell you the password: user=xdaftp pass=xdaftp
Replacing a corrupted bootloader via ActiveSync
I have a T-Mobile PPC Phone on which I have installed the AT&T radio stack and the XDA-Developers 1.1 ROM. All works well except for the fact that I appear to have corrupted the bootloader. The device now jumps directly into Windows CE and ignores any keys which I press when performing a soft reset.
From reading the rest of this thread it seems that I may be able to replace my corrupted bootloader via ActiveSync if I prepare an image file correctly. Is this true, or am I misunderstanding the ActiveSync upgrade process? As I can't reload from SD card, I'd be grateful for some expert advice before I go ahead - I can't afford to get it wrong!
Thanks,
Malcolm
Hi,
I've already upload the PPC2003 for XDA to your FTP. Please check your private message for the password for the ZIP file.
Thanks
After one week with a T-Mobile US version (32Mb) i want to thank you all for your job.
I mean that first thing when I got it I've installed SE 1.2 and unlocked it. Afterwards I was toying with TMO 4.00.16 ENG and also upgraded radio to 6.24.
Everythnig is smooth but ... I want to build my own ROM. I've set up the makerom on a linux box and i think i will follow this steps:
1. perl setup.sh nk.nbf (this one taken from the origina TMO distribution in the RUU directory) - on the linux box
2. dumprom -4 -d files -q nk.nbf - on the linux machine to get all files
3. perl fdf2reg.pl files/default.fdf cfg/default.reg - linux
4. tr -d "\0" <files/initobj.dat >cfg/initobj.txt - linux box
5. cp files/initdb.ini cfg/initdb.ini - linux box
6. delete all files & add all the files I want to add (all kind of software)
7. bash mkrom.sh out/out.nbf - to generate the file for the SD
Questions:
a) is it possible to remove some files from the original ROM and how (any additional steps required)
b) using ssnap for the addtitional software installed ... where shall i make the additions (in files and for registry) ?
Thanks for all your support.
Decebal
PS. Any XDA owner from Romania ?
Hello,
I'm developing my own ROM using the "XDA ROM Kitchen". However once Clicking "Build Rom" I obtain the error "All workspaces are busy now. Try again in 20 seconds or so..." I will list my setup.
------------------------------------------------
OS: SuSE Linux 10.0.0.42
kernel-default-2.6.16_rc1_git3-4
kernel-source-2.6.16_rc1_git3-4
kernel-syms-2.6.16_rc1_git3-4
------------------------------------------------
Webserver
XAMPP for Linux 1.5.1
Includes:
Apache 2.2.0
MySQL 5.0.18
PHP 4.4.1
PHP 5.1.1
Perl 5.8.7
Install directory = #/opt/lampp/
------------------------------------------------
RomKitchen date = 04/01/2005
Install directory = #/opt/lampp/htdocs/kitchen_template/
Rom used = 3.17.03ENG
MKROM date = 04/01/2005
Run locally via
"localhost/kitchen_template/"
I select any adequate options, and select build rom (tested on all three options) and error "All workspaces are busy now. Try again in 20 seconds or so..." Is displayed.
The Rom directory structure is as follows:
'/opt/lampp/htdocs/kitchen_template/'
'/opt/lampp/htdocs/kitchen_template/data'
'/opt/lampp/htdocs/kitchen_template/download'
'/opt/lampp/htdocs/kitchen_template/kitchen.local'
'/opt/lampp/htdocs/kitchen_template/workspace'
'/opt/lampp/htdocs/kitchen_template/workspaces'
The ROM location is as follows:
'/opt/lampp/htdocs/kitchen_template/data/00_Select your Base ROM/3.17.03 ENG O2-Euro/_/cfg/rom.nb1'
------------------------------------------------
Could anyone please help me evaluate the problem and perhaps correct this? such as after install configurations. I would greatly appreciate it also share my kitchen once complete.
Thanking in advance
John
*bump*
Hello,
Still no avail with this problem, I descovered php5 is not compatible and php4 fixes many issues, yet still no fix for the 20 second error.. please anyone?
John
Shadow_relm said:
However once Clicking "Build Rom" I obtain the error "All workspaces are busy now. Try again in 20 seconds or so..."
Click to expand...
Click to collapse
check the workspace directory. There have to be write access by you apache user, and it has to be empty. This error normally cames when it isn´t possible to create a workspace, or all workspaces are in use....
Stefan
LumpiStefan said:
Shadow_relm said:
However once Clicking "Build Rom" I obtain the error "All workspaces are busy now. Try again in 20 seconds or so..."
Click to expand...
Click to collapse
check the workspace directory. There have to be write access by you apache user, and it has to be empty. This error normally cames when it isn´t possible to create a workspace, or all workspaces are in use....
Stefan
Click to expand...
Click to collapse
Thankyou Works fine now , all i got to do is alter a few things, is it posible to obtain the WMP10 files and include into this rom? If not that is cool.
John
Hello,
Sorry, The error still appears now its constatly again. and i am incapable of compiling roms. any suggestions?
thankyou
Re: Hello,
Shadow_relm said:
Sorry, The error still appears now its constatly again. and i am incapable of compiling roms. any suggestions?
thankyou
Click to expand...
Click to collapse
Update, I can now creat NK.nb1 and NK.nbf files with the kitchen, the files flash perfectly and flawlessly. Yet when running installer EXE it displays the usual..
Creating ROM... Please be patient.
Copying ROM files
Why not using the time for donating? ;-)
Running mkrom
Your ROM is done. (click here to view the log)
But uppon downloading the rom its only 200-500kb the logg says as follows
no files for configid 26220739 2620749 27202 20404 20408 20412 23410write xip block starting at 81800000, with 27 fileswrite xip block starting at 81980000, with 0 filesthis rom seems to be 3.17.03 ENG 2003-05-15 o2eurothis bootloader seems to be V5.22 2003-05-15 17:46:5580000000 - 80040000 -- bootloader 0 files 1 modules80040000 - 8026a804 -- kernel 13 files 11 modules802c2000 - 8057d330 9 OS 15 files 32 modules80580000 - 8075a69c 8 SHELL 79 files 27 modules80780000 - 80a13b04 7 BROWSING 9 files 14 modules80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules80dc0000 - 80ebd150 5 SYNC 12 files 22 modules80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules81080000 - 81348248 3 24MCONSUMER 69 files 1 modules81400000 - 814019a4 -- xip chain 10 xip entries81440000 - 817f6f14 1 MISC 209 files 40 modules81800000 - 8189ec94 10 XDA_DEVELOPERS1 27 files 0 modules81900000 - 81925800 -- bitmap : 101a301a .. beb6fc8d81940000 - 81944000 -- operator rom 0 files81980000 - 81981054 11 XDA_DEVELOPERS2 0 files 0 modules../rom.exe: found a preamble of 31232 bytes adding: English/NK.nbfzip I/O error: No space left on devicezip error: Output file write failure (write error on zip file)
since I have no chance to get sources for all kitchen tools, so i'v decided to write new svn repository with all tools
command:
svn co http://lrk-python.googlecode.com/svn htc-python
todo:
fdi - decompession of cabbed files - with help of cabsdk.exe ported to linux
xip - full port
tools witch are found working:
nbh2dbh
dbh2nb
osextract - on windows 32
part-os
target: linux-x64
usage - and what be discovered
steps:
ln -s uour file.nbh rom.nbh
xe1-nbh2dbh.py - converts rom.nbh to tempfile.dbh
xe2-bdh2nb.py - converts tempfile.dbh (from previus step) to : ) other formats, where one of them is *OS*
softlink this file to windows.nb
xe3-osextract -will decmpose windows.nb to partitions
- and here im flying
25 - sys partition
others - are xips - in simple case
am - seeking for volunters to do the other steps to fully decompile/recompile xip and friends
Hi all, I have problems using osnbtool: when I open it it closes immediatly...
Can somebody tell me how to use it? I'm using Windows 7
Never used it but try right click and run as administrator.
It is a console tool. You need to run it from the Command Prompt in admin priviledge.
Ok I managed to run It, the problem now is that the program crashes after some time... what should I do now?
Please somebody answer
Didn't you get this if you just type "osnbtool" on the command prompt? The built-in help is good enough. What exactly do you want to use it for?
$ ./tools/osnbtool.exe
OS ROM Partition Tool V1.59 By Weisun :> PDAclan.com
A powerful tool for de-pack partitions from OS.NB!(RAW-OS-IMAGE)
*** Decompress & compress SRPX partitions,unpack & pack partitions.
*** Support to re-structure OS.NB when insert a resized partition.
====Command for decompress,compress,unpack & pack partitions:
-d <OS.NB> <Num> <OUT.BIN> Decompress Num of part from OS image to OUT.BIN
-c <OS.NB> <Num> <IN .BIN> Compress or insert IN.BIN to OS image
====Command for split to a RAW-OS-IMAGE form srcFile & repack:
-sp <fName.ext> Split source file to fName.ext.PRE & fName.ext.OS.NB
----'fName.ext.OS.NB' means that RAW-OS-IMAGE.
----it can remove extra-data(SECTOR_ENTRYs) or B000FF struc.
-extra <fName.ext> [0x"intBlocksToFill" | 0x"dwBlockSize"] Insert extra fields (SECTOR_ENTRYs) & get fName.ext.EXA
-2bin <fName.ext> [0x"StartADDR"|-CutHeader] Pack fName.ext to BIN(B000FF)
-FixBinHeader <fName.ext> [0x'intRecordsToAdd'] Fix 'B000FF' header-entry.
====Command for unmask src file :
-x <fName.ext> <0x"dwKeyWord"> [outFile] Unmask source file to outFile
====Command for PagePool value changing in XIP.BIN:
-pp <XIP.BIN> <0x"dwOFFSET"> <decVal"MB"> [-y] Change PagePool Value at OFFSET in source XIP file
-ap <XIP.BIN> <decVal"MB"> [-y] Auto search & change PagePool Value in source XIP file.