I have installed jeff summers version of xda tools. And though I think I understand what I am doing I am not totally convinced. Before I embark on cooking roms and upgrading etc I would like to be able to do the following:
1: Dump my current rom from my device to my PC I can do this using XDAtools OSImage but can only Can this only be NB1(windows CE(*.nb1) type files if I try to call this NBF I get the following error:
error opening C:\program files\xdatools\bootloader_v5_15.nb0ea for reading. the system cannot find the file specified.
error opening source bootloader from C:\program files\xdatools\bootloader_v5_15.nb0ea. error opening target device.
Can I dump my device memory into a file called ‘xxxx.NBF’?
2: When I try to upgrade my ROM by:
Start OSImage tool and select source as:
‘C:\PROGRAM FILES\XDATOOLS\BINARIES\ATT160204.NB1’
Select destination as ‘device memory (via programmeA) ‘
When attempting to load an ‘NB1’ ROM from my PC to my device memory (via programmeA) I always get the following message:
ProgrammeA not found - run with --register error opening target device.
I originally ran the programmeA with --register when first installed.
I have tried searching for a solution but to no avail. Any help appreciated.
Thanks John.
If you're trying to burn your original ROM back to the device that shouldn't be a problem. Use the [...] button to locate your .nb1 ROM for the source, and select Device Memory (via Programme A) as your destination.
Have you installed ProgrammeA.exe into the binaries folder of XDATools? That's the only thing I can think of.
Thanks I have tried this but believe the problem is the ProgrammeA file but it is definetly in the binaries folder. I am running win98SE but don't think this should be a problem. When you run jeffs tools it extracts itself out under program files and places all the required files in the right directories. Would appreciate it if any one out there can supply some help ?
Thanks John
I think I know what the problem is...
I have the same problem. If you look at the dos box that pops up you see that programmeA.exe looks in to the \\Binaries\English\ folder for a *.nbf file. It looks like you will have to provide it a *.nbf file in stead of a *.nb1
Related
After downloading Jeff Summer's rom (.exe file), I tried clicking on it to extract the files...no good.
Then I used Winzip and extracted to C:\windows\temp.
Next I click on start.bat and the dos window comes up stating NBF directory not in the C:\windows\temp directory?
I move the nbf file to this directory and the uprgrade process starts.
Next I get Error 012
"Rom image that you are trying to upgrade is not compatible to your Pocket PC.
Your device
ModelW10B1
Rom version 3.14
Lang: english
Your upgraded image information:
ModelW10A1
Rom version 3.17
Lang: english
Please download comaptible utility."
What the hell went wrong??
:? :?
Sound like you extracted everything in one directory instead of in the directories mentioned in the self-extracting exe. Or something similar.
Not exactly. Here's what I did as best as I can remember.
When I clicked on the .exe file, a dos box opened, gave me an error message that it could not find the nbf directory.
Then I used winzip to extract the files into the same directoy as the .exe file.
From there I tried running the start.bat file. Still no good.
What finally worked was a strange combination of clicking on the .exe file and then immediately clicking on start.bat. This was after I moved the nbf file from the \english subdirectory to the subdirectory that had the .exe file.
It was a strange work around, but it work and the rom loaded and seems to work well.
I am getting the same problem here but I havent been able to work around it. I tried what worked for you without success.
File was downloaded from Jeff Summer site. I click on the downloaded file and it would start unzipping and the adaptROM program would run itself. The Programme A shows up and and displays STEP 1, Welcome to ROM upgrade utility.
Go next. Release note is empty. Next again I will get the Error 007 message saying that NO ROM IMAGE FILE.
I am using AT&T SX56 and running Window 98, and had no problem upgrading before from Siemens site.What can I possibly do wrong?
Thanks.
try this.
unzip the 'jeff summers' file to a new folder on your desk-top for convenience.
check that you have
adaptrom.exe
programme A.exe
readme.rtf
start.bat
English (folder)
CLoader_serial.nb
CLoader_usb.nb
GetConnectionType.dll
Nk.nbf
remote_flash.exe
SetSystemTime.dll
if all files are present, connect your XDA and run start.bat.
if any files are missing, although they shouldn't be, download the .zip file again.
ian
Spent a lot of time on it, trying to figure out what went wrong with mkrom when cooking 4.00.xx roms. finally figured it, well, almostly. here is a short step by step tutorial for people who do not want to set up the complicated kitchen but wish to use mkrom as in the good old 3.17 time.
I assume you already know the rom flush process already, if given a NBF file. also you need a linux box with perl.
I know quite a few people struggled and have not had a clue. and I believe there is some bugs in the mkrom package that gives the trouble.
1. download the newest mkrom from http://xda-developers.com/~itsme/download/mkrom_136.zip. this is the only piece of software you would need.
2. unpack it to, say mkrom, directory. then make directories cfg
3. get hold of a copy of rom file and its corresponding paramter files. the parameter files can be obtained from the demo kitch download ftp://kitchen:[email protected]/data look inside the "00_base ROM" and the parameter files should be under cfg directory of each rom directory. bascially the parameter files tells mkrom, where to start to put added files and how large space there is. there are two blocks of space that can be used. so the file has format
wincever=4
start1=81740000
size1=00040000
start2=81b00000
size2=003c0000
startbmp=81ec0000
startop=81b00000
the first three lines are same for all 4.00.xx roms, start2 varies for different roms, startbmp is also the same for all roms. startop should be the same as start2. size2 will be startbmp-start2, remember they are all in hex. you can calculate how large space there is once you get hold of the start2 parameter.
anyway, put the parameter files under the mkrom/cfg directory, with name "params"
4. copy a rom file (.nbf), say rom.nbf, into mkrom directory and run "./setup rom.nbf". this will creates several files under cfg.
5. mkdir a directory mkrom/romfile, enter it and make another directory file , then type "../dumprom ../cfg/rom.nb1 -4 -d file"
here comes the first bug. the setup.sh tells you that dumprom can only be used in windows box. but in fact, there is a compiled dumprom for linux in the directory (you might need to set it to be executable though). however, this linux version does not put extracted files into the "file" directory as it is supposed to, instead it just write file as "file\xxx" where xxx is the actual file name extracted from rom. it is a bug but as long as we know it, not a big deal. the is someone posted a correct version of dumprom in this forum though.
6. you should be able to find three files (or with the "file\" prefix added) with name default.fdf initobj.dat initdb.ini. these are the three files that needs to be process as indicated by setup.sh. follow the instruction to create the default.reg initobj.txt initdb.ini and copy them to cfg directory.
7. make a directory mkdir/files. you are ready to create a clean rom now by running "./mkrom output.nbf", the created output.nbf should be fine.
So far so good, followed the instruction of mkrom. next would need to add our files. then comes the problem. if you add files into the mkrom/files directory, and run "./mkrom output.nbf" again, it is almost definitely that the created rom is bad. I am not 100% sure why, but here is what I believe:
the mkrom script scan files in the "files" directory and put files in there into the "files1", "files2" directory, each of them is supposed to fill the two space in rom starting from "start1" and "start2" in parameter file. the size of files under "file1" should be less than "size1", similar "files2" and 'size2". when mkrom does this, it is highly possible that the three critial files "default.fdf, initobj.dat, initdb.ini" are placed into "files2" directory instead of "files1" directory and renders the rom bad.
here is what I did
edit the mkrom.sh, delete the line that splits files in "files" into "files1, files2" directory. change the three lines that convert the three critial files so that these three files are created in "files1" directory instead of "files" directory. then put your files into "files1" and "files2". just be careful, keep the size less than specified by "size1" and "size2".
then you can run "./mkrom.sh output.nbf" as before, and the resulted rom will be good.
hope this helps. however still a couple of problems
1. the fdf2reg.pl won't recoganize the default.fdf extracted from 4.00.21 rom or 4.01.00 rom
2. if i change the content of initobj.txt, the created rom won't boot. I might have done something wrong in initobj.txt though. but I used to be able to do this for 3.17 rom
3. I did not try to modify registry, as my only purpose is to put my files into ROM to save space. all registry can be done later by installing the software and choose not to overwrite existing files in ROM. must simpler.
the unix version of dumprom does not decompress files, that is why your default.fdf etc seem corrupted.
this is because I only have the decompression code in the form of a binary library, which I have not figured out how to link to under linux.
the only use of dumprom under unix is to find the offsets in rom where filepointers to default.fdf etc should be patched.
I should maybe disable the '-f' option in dumprom for the unix version, to make things less confusing.
but it looks to me that the dumprom under linux worked for pre- 4.00.16 rom. only not for after 4.00.21 roms. so are they different?
maybe the default.fdf was not compressed in the 3.x roms?
I am quite sure it does not work for compressed files under linux - I just did not implement the compression routines.
dumprom worked with 4.00.05 4.00.11 4.00.16 roms. I cooked 4.00.11 and 4.00.16 roms, and the rom was fine. I never used windows box during the process. only when i tried 4.00.21 and 4.01.00, there was error. anyway, i don't care, since I need as much rom as possible and 4.00.11 seems to be the best choice for me.
thanks for writting mkrom, a terrific tool. I don't like the way xda-developers.com promoting kitchen but not mkrom. mkrom is much simpler to setup and run, as long as you know about linux. the kitchen is much more complicated to get it to work and most people don't actually need such flexibility I believe.
ok i installed cygiwin and was with u till step 5, then i am lost.. when i run step 6 dumprom (in DOS) gives me an ewrror here atr the first few lines from dumprom( wiht latest ATT official release)
img 00000000 : hdr=8c0a1000 base=8c078000 commandlineoffset=8c077fe0
img 00040000 : hdr=800cdde0 base=80000000 commandlineoffset=7fffffe0
img 00180000 : hdr=8024db88 base=80000000 commandlineoffset=7fffffe0
img 00380000 : hdr=8039b334 base=80000000 commandlineoffset=7fffffe0
img 00670000 : hdr=80be2c40 base=80000000 commandlineoffset=7fffffe0
img 00c00000 : hdr=80e99400 base=80000000 commandlineoffset=7fffffe0
img 01050000 : hdr=813efc74 base=80000000 commandlineoffset=7fffffe0
img 01400000 : hdr=815d2ba4 base=80000000 commandlineoffset=7fffffe0
img 015f0000 : hdr=815f0650 base=80000000 commandlineoffset=7fffffe0
img 017c0000 : hdr=81bba0a4 base=80000000 commandlineoffset=7fffffe0
ERROR: could not find pointer for ofs 8c0a1000
invalid romhdr ofs 8c0a1000
ERROR: could not find pointer for ofs 00000000
7fffffe0 - 80000000 L00000020 unknown 30315750 452d3142 412d474e 2d30332e 2d353030 62373239 2d2d2d2d 2d2d2d2d
80000000 - 80000004 L00000004 romsection id=ea0003fe
80000004 - 80000040 L0000003c NUL
80000040 - 80000048 L00000008 'ECEC' -> 8c0a1000
errorsgalore...
so help me here how do i make sure the files extracted are all good also the size (as per ) windows explorer is 33+ not sure how all has been installed in the 32mb rom
did you get default.fdf initobj.dat initdb.ini out of dumprom. dumprom also reported tons of errors but as long as you get the three files out, it is ok.
Dumprom tries to figure out for each byte in the rom what it does. If it doesn't know it says 'unknown' this is not an error, just that dumprom could not determine the use of this byte. The 'could not find 00000000' message means that it encountered a NULL pointer somewhere in rom where it did not expect it, the other one is a pointer to RAM, which dumprom does not know exists. You can safely ignore these errors.
Dumprom was initially written to assist in figuring out what I did not know about the rom, so it tries to figure out stuff that is unknown. Later I added the code to extract files to it. Maybe I should split dumprom in one research tool, to do a detail examination of the rom, and one tool to only extract files.
Most files in rom are compressed, that is why they are more than 33M when uncompressed.
ok i understande the messages...
now here is what i did
ran ssnap and got a picture of the OS and did a compare and have a list of entries i want to add to registru and a folder with bunch of subfolders that need to be added on install
not sure how step 6 goes.. to convert the files to .reg and .txt and how/where do i add my files and registry entries....
any tips...
update...
i did fdf2reg and made a .reg file added my entries in there and then ran reg2fdf to recreatre the fdf...
i hope this is right now i need to fig out how to specify where the files i want added are to be copied i mean some go into windows some in new filders that need to be created...
plz tell me how to go forward.
you don't need to re-create the fdf file again, mkrom does it for you, you only need to take care of the default.reg file under cfg
I am not sure whether you can put files under directories other than \windows only. I did not try that. I suppose all files under /files1 and /files2 go to \windows directory just they happen to locate in different memory location in ROM
Hello all,
I'm having a problem with my qtek 9000 with latest rom from myqtek.com, some programs can't be opened because they say: "The file "patched-game-file-here" cannot be opened. Either it is not signed with a trusted certificate or one of its components cannot be found. You might need to reinstall or restore this file"
I've tried some files to disable certificate security but no luck, the problem is still there :|
Anyone can help getting over this problem?
Try this.
http://buzzdev.net/index.php?option=com_remository&Itemid=109&func=fileinfo&id=194
This is from the wiki:
Code:
Allow the unsigned app from installing for everything.
HKEY_LOCAL_MACHINE\Security\Policies\Policies] Change value 0000101a from 0 to 1
Do a soft reset.
V
Hello all, tks for your help
vijay555 - i tested your code but no luck, problem still there.
victoradjei - i've tested that app, pretty simple to use an finally it works ! (YES TK U) , for now it's a solution let's hope someone can make a .cab in order to disable this security check for good.
Hi,
I have an htc P3600.
I've downloaded the application for buzddev.
I've also changed the registery but I do not know what to do with that application. There is the signcode.exe, what should I do with that file downloaded?
Could someone shed some light on how to use the app from Buzzdev? Is it supposed to be run on the device?
I ran the EXE file on my PC and a DOS window popped up and closed itself and nothing happened.
Thank you in advance!
Extract the SignCode files into a folder. Then you have to run it from the command line or the "Run" option from the "Start" button and tell it what EXE file to fix. Since this program actually changes the executable file by changing the embedded security certificate, you might want to make a backup copy of the EXE file first.
Here's the syntax:
<path to SignCode files>sign.bat <path to program and filename>
If you extracted the signcode files to your "C:\Program Files\SignCode" folder and are trying to fix your "C:\Program Files\SomeGame\SomeGame.exe" file, here's EXACTLY (quotes and all) what you would type in the "Start" "Run" box or a command prompt:
Code:
"C:\Program Files\SignCode\Sign.bat" "C:\Program Files\SomeGame\SomeGame.exe"
You should notice the timestamp of the file change indicating that the embedded security certificate was changed. Copy the updated file and overwrite the original EXE file on your mobile device and then try running it. This will still pop up an "Untrusted Source" type of security message on your mobile device but you will have the option to install it anyway and it will work fine after that.
This should work too, M$ made a tool for provisioning devices.
http://www.microsoft.com/downloads/...8c-d587-47e0-908b-09fee6ea517a&displaylang=en
victoradjei methode worked perfectly for me on WM6
Does anyone have the info that was in this link?
The forum is their but looks like the link is dead.
http://buzzdev.net/index.php?option=com_remository&Itemid=109&func=fileinfo&id=194
Thanks,
Kenny
I dont know, but could try attached may help. I don't know anything else to help... hopefully someone else will.
Hello,
I am trying to copy a file (from my smartphone to SD card), which have a 'ROM' attribute set and... it is impossible - acces denied is showed (even in Resco Explorer, Total Commander). I can't even change that attribute.
Please help me to find any solution
Best greetings,
RA
You should be able to extract files from the ROM file on your PC thanks to the tools provided in one of the sticky about ROMs modifications.
Unfortunatelly...
Cricri said:
You should be able to extract files from the ROM file on your PC thanks to the tools provided in one of the sticky about ROMs modifications.
Click to expand...
Click to collapse
I have extracted an 'nb' file from my ROM file, but WinImage can't open it ("not FAT16, FAT32 file"). It is WM6 image file, what tools to open this 'nb' file?
Best greetings,
RA
I, too, am trying to find a way to copy some ROM attributed files.
Ultimately, I am trying to move/copy some apps from one smartphone (WM5) to another (WM6). Is there a way to copy them to a zip file and move the files that way or maybe even using a backup copy (i.e. using Sprite Backup?) and restoring to a different phone?
Any help or direction would be appreciated. If there is another thread out there, please be sure to point me to it since searching brings up a lot of different threads.
u need to extract the rom.
Funny, but you make it sound so easy... ;-) I've been searching to figure out how to do that and found some instructions I'm hoping I can follow for the one phone, but not sure it it will apply to the old phone (WM5). If I do manage to dump the ROM, where does it go and does it extract the files in cab format for easy upload?
Update: I found a file extractor at http://pdaphonehome.com/forums/ppc-6700-xv6700/56057-6700-rom-dump.html which may have originally come from Buzz... (thanks Buzz!)? so now I have all the files and modules off the old phone, but am running into some issues installing. I can transfer the files indirectly, and can find the specific application file, but when trying to run the app, it tells me that it's still missing files to enable the program. Any ideas on how to determine which files they might be or how to install the files via Activesync?