Related
I managed to get SN40001wwe_AWS.bin wich is a bin format ppc2003 for xda (version 4.0.0.1 !!!)
If u have any ftp I'll upload it
upload to here please
Address : ftp://kellylau.uhome.net
User : kellylau
password : xda
By the way, do you have the writing utility for bin files?
If not we may have difficulty to write the rom.
Thanks.
you can convert it to .nb1 using
Code:
perl splitrom.pl SN40001wwe_AWS.bin -wo nk.nb1 -t nb1
or to nbf ( if it contains a bootloader, which I think it does ) with
Code:
perl splitrom.pl SN40001wwe_AWS.bin -wo nk.nbf -t nbf -n PW10A1-ENG-4.00-007
and then use adaptrom to fix the nbf file such that it can be flashed with programme A.
Have bootloader too. Uploading in progress. I got the ipaq 3970 ppc 2003 too. If u need it i can upload it too
I flashed my XDA with it ok Nice new screen on startup "Test Only Not for sell" ehehe
Don't need any pached It's working OK on XDA O2 !!
Use the splitrom.pl to make it NBF. The ftp don't work cause i wanted to upload the nbf file.
Helloo,,
florin_m ,
i waited for it too long time
please upload it to a public web or ftp serve for public sharing.
thanx in advance
Link for edonkey p2p
ed2k://|file|ppc2003_4001.zip|16025280|8E4C8F1EA55F520E909E8CCDF36B6667|/
I made it nbf. use xartit to write it to a sd card and flash it. That i did for better security!
edonkey dont downloading the file !
gime a ftp and i'll upload
well
FTP server is: ftp.members.lycos.co.uk
FTP login: xdarom
FTP password: xda2003
& thanx very much
by the way
FTP server is: ftp.members.lycos.co.uk
FTP login: xdarom
FTP password: xda2003
Passive MODE
Upload in progress!
1. Will this work with Programme A if done through AdaptROM ?
2. How big is the zip (im on the ftp server watching the bytes go up...)
upload done
Should work with program a, but i don't take any responsabilitys!!!
Can you post a screen shots of the Start, Settings, System, About page and one of the Device Information page?
You guys can download the NK.nbf file from my FTP server if you want:
Server: ftp.zensay.com
user: qtek
passwd: qtek
Version 4.20.1081 (Build 13100)
Want me to take a picture of that ?
In Device info:
ROM version: 4.00.01 ENG
ROM date: 05/16/03
sheran_g said:
You guys can download the NK.nbf file from my FTP server if you want:
[...]
Click to expand...
Click to collapse
You may want to zip it: turns 32 MB into 15 or so...
@sheran_g
I keep get Timeout
I uploaded the nbf on all 2 ftp server from this topic
@XDA developer Peter Poelman check PM
OK, I'll start by saying sorry for my stupidness and thankyou for listening to my plea.
I downloaded Jeff's XDA special edition .exe file and unzipped it to a Dir seeing all the files needed to upload a new ROM to my XDA.
I (in all my wisdom) decided to run the osimagetool with the --register and proceeded to right click on the nbf 30mb rom image and selected burn...thinking this was the way to do it (not even trying to run the original exe)
The "programme a" program started and started updating my xda. It started off updating and after a few seconds i heard the "BLIMP" of the activesync telling me it has disconnected, then another blimp telling me it had restarted and re-connected to active sync, but the loader on the screen quickly zipped to 100% done and told me to remove and reboot the xda. The xda however was telling me "upgrading... It will take about 5 minutes". Urk
Now im left with an XDA that sit's on this upgrading screen even after reboot of it.
OK... ive done wrong.. im silly... would any one step up and help me out here (BIG PLEASE AND TY also). Ive got an XDA serial cable sitting here next to me as well as the usb cradle (which im sure wont help now the xda cant run active sync)....
Ideas? Can i run the original rom uploader (xredit?) rather than osimagetool with the serial cable to upload either the new rom i have or the rom i backed up of my old device before doing all this (yes i did back it up to my harddrive first - phew?).
Thanks for reading, and i hope someone can point me to a place in the forum where all people like me end up, or even better send me an email pointing me in the right direction.
Thank you! (email Tony at [email protected])
Note: my original version was 3.17.03 and the "programme a" upgrade program said it was upgrading to 3.16.
can you tell me what splitrom says about the nk.nbf that is now in the 'english' subdirectory of the path
pointed to by the registry key "Software\\XDA Developers\\OsImageWriter", "Programme A Path" ( in current-user )
thanks for coming back to me.
unfortionately, i dont have perl installed on my windows xp machine so the batch file you linked to do doesnt work. If you have a link for a perl install anywhere I'll be happy to install and run it.
In the key you mentioned, here is the value: D:\XDAtools-Jeff\binaries
The directory i unzipped Jeff's version of your tools to.
Im not sure if you perl script does other things, so in the meantime, i'll go and try and find perl (im sure ive installed it on a work machine i had years ago - seem to remember adding local path variables for it)... i'll check my cd archive for it.
Thanks for the help, much appriciated
Tony.
perl can be obtained from either http://www.cygwin.com/setup.exe or http://www.activestate.com/Products/Download/Download.plex?id=ActivePerl
cheers, i'll dl then run the script....
n1 guv
C:\Documents and Settings\tkett.ADPLATES>D:\splitrom.bat
Can't locate List/Util.pm in @INC (@INC contains: C:/Perl/lib C:/Perl/site/lib .
) at D:\splitrom.bat line 86.
BEGIN failed--compilation aborted at D:\splitrom.bat line 86.
^^
Thats the error message i get when running that perl script.
Ive searched the hdd for Util.pm and its sitting in my c:\perl\lib\sgi dir
Things just arent going right for me at the mo.
this module is standard with perl 5.8, with perl 5.6 you have to install
it manually.
as a quick fix, you may also just add a 'min' function manually
Code:
sub min {
my $min;
for (@_) {
$min= $_ if (!defined $min || $_ < $min);
}
return $min;
}
and uncomment the line
Code:
#use List::Util qw(min);
C:\Documents and Settings\tkett.ADPLATES>D:\splitrom.bat
Usage: splitrom <romimage(s)> [options]
-wx xipchain where to write xipchain
-wo osrom where to write output image
-wb bitmap where to write bitmap
-wl bootloader where to write bootloader
-rl bootloader which bootloader to use for NBF
-n nbfinfotext what NBF header to use [ex: PW10A1-EN
-ri nbfinfofile or where to read NBF header info from
-wi nbfinfofile where to save NBF header info
-rx xipchain where to get xipchain from
-rb bitmap where to get bitmap from
-rm [email protected] insert new romsection.
-ob offset where to find the bootup image
-oe offset the end of the desired os image ( def
0000 )
-t NBF | B000FF | NB? | IMG type of result image (default is NB1)
^^^^ Ive put your routine in replacement of that line and am given the options above when running splitrom now. What parameter would you like me to run ?
As always.... a big thanks for the help.
Tony
Itsme, thanks for your interest in my problem. And im very glad people like you are around to help
I have however and thankfully repaired the fault.
Here, (for other newb's like me that get stuck) is how i done it:
I had already backed up my ROM using the osimagetool program to a nb1 file on my pc called "oldrom.nb1". Now because my XDA wasnt booting into Pocket PC windows, i couldnt use active sync to sent the rom image I backed up, back to the XDA...so I had to go and buy a cheap SD reader from my local Dixons store and run osimagetool again. This time writing the rom i had backed up to the SD card in the new SD reader.
Then I rebooted the XDA into the bootloader (hold down the top power button and do a soft reset) and selected to reflash the XDA using the SD card.
If you havent already backed up your rom from your xda to file, then I presume, you have to find another person with an XDA so you can download thers to your SD card (once your in the bootloader menu, press the contacts button to get the options to dump their rom to your card). OR find an NB1 file on the internet that matches your phone version.
These may be simple instructions for most of you, but i've seen a few posts that directly relate to the problem i had, and saw people crying for help, just like i did...hopefully this will help those few.
I did also have a serial cable, and im sure there is a way to upload roms you have on your pc to the XDA via that (using the xda developers old rom tool), but im afriad i didnt read into that after finding out this method. (this way may be better for the skint people who dont want to buy an SD reader, but can get hold of a serial cable for cheap)
REMEMBER FOLKS
It was silly of me to try and flash the device in the first place without reading loads and loads of entries on these forums and really finding out what is going on instead of just flashing blindly in the hope that it would work first time.... please dont follow my lead. :shock:
Thanks again for your help Itsme...and one last question... do you think that with that registry entry as it was above, that i can try again with the .exe jeff made (possibly downloading it again in case of corruption)
(yes i am a glutten for punishment)
Tony
still I'd like to know what went wrong in your case.
can you type 'splitrom nk.nbf' ( in the 'english' subdirectory )
sure:
D:\XDAtools-Jeff\binaries\English>splitrom.bat nk.nbf
this rom seems to be 3.17.03 ENG 2003-05-15 o2euro
this bootloader seems to be V5.15 2002-06-06 20:29:17
no bitmap found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8026a804 -- kernel 13 files 11 modules
802c2000 - 8057d330 9 OS 15 files 32 modules
80580000 - 8075a69c 8 SHELL 79 files 27 modules
80780000 - 80a13b04 7 BROWSING 9 files 14 modules
80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules
80dc0000 - 80ebd150 5 SYNC 12 files 22 modules
80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules
81080000 - 81348248 3 24MCONSUMER 69 files 1 modules
81400000 - 81401484 -- xip chain 8 xip entries
81440000 - 817f6f14 1 MISC 209 files 40 modules
81940000 - 81d2d2b5 -- operator rom 81 files
Tony.
ahhh... haNG ON.... the one i used was in the .exe's folder.. not jeffs tools folder:
D:\XDA-developers-SER-v12\English>splitrom.bat nk.nbf
this rom seems to be 3.16.52 ENG 2003-03-10 XDASER-12
this bootloader seems to be V5.22 2003-05-15 17:46:55
no bitmap found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8026a804 -- kernel 13 files 11 modules
802c2000 - 8057d330 9 OS 15 files 32 modules
80580000 - 8075a69c 8 SHELL 79 files 27 modules
80780000 - 80a13b04 7 BROWSING 9 files 14 modules
80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules
80dc0000 - 80ebd150 5 SYNC 12 files 22 modules
80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules
81080000 - 81348248 3 24MCONSUMER 69 files 1 modules
81400000 - 814019a4 -- xip chain 10 xip entries
81440000 - 817f6f14 1 MISC 209 files 40 modules
81800000 - 818e0c14 10 XDA_DEVELOPERS1 13 files 0 modules
81940000 - 8198b6e5 -- operator rom 20 files
819c0000 - 81ee9a58 11 XDA_DEVELOPERS2 202 files 0 modules
hence the 3.16 now.
Hi Ajkett,
Thanks for sharing your knowledge of how to resolve your problem with us. I have however used a new 64 mb sd card to flash my old rom (3.16) to it before trying out the Jeff rom kitchen exe and thank god things are fine for me. Now I have bought a cheap 6 in 1 card reader/writer and would like to keep the old rom in a safe place in my hard disk hence freeing my sd card so that I could use it. I have read those threads in the rom tool section many times and still can't work out how to use the osimagetool. When I clicked on it, it gives me the interactive screen but always do not read my sd card. Even with the card reader, it seems to "think" that the sd card is unformatted and ask to format the card for me. Now the question is whether the rom is inside or not? How can I use the rom tools to read the sd card and copy the rom to the hard disk? What does a rom file appear as? Is it like the nk.nb1 file created in Jeff's rom kitchen?
Cheers
Vic
ahhh your trying to read the rom from the sd card after dumping it to the sd card from the xda?
the way i got it onto my harddrive was without an sd card. Just run the osimage tool and select the xda current memory as the source and then type c:\oldrom.nb1 as the destination.... it will use activesync to read the rom straight from the device.... you dont need the sd card to back it up.
Then when i ****ed my xda up, i run the osimage tool again and wrote from source - oldrom.nb1 to the sd card reader to a formatted sd card.
When it writes it, it gets rid of all the formatting so you wont be able to see whats on it on your pc....the only thing its good for then is to use on the xda to overwrite the rom, until you format it again that is.
Its not like a file on the sd card... its like a bootdisk with the rom written in a way that the xda will understand that its a bootdisk and will boot from it to overwrite itself... like the file is in raw format... not a nb1 file or anything (looks like lots of gobbledigoop) and the pc will not read it.
Thanks Ajkett,
Thanks for your kind reply anyway.
Got it done. The osimagetool could read but I did not write the path correctly; it has to be rom.nb1 apparently for it to work. I even used the card reader and managed to write the rom again the same way to my hard disk. I hope this is the correct way of doing it and it seems that the rom.nb1 file on my harddisk is about 30.5 mb which is probably about right for the old 3.16 rom I had dumped onto it by the XDA.
What puzzles me is that if it can read as source rom.nb1 file when you say you rewrite it to the sdcard, it becomes mumbo jumbo again but it should flash ok within bootloader mode via the XDA. Is this correct?
Cheers
Vic
yep your correct... even thogh it doesnt write a nice 30mb rom.nb1 file to your sdcard, the xda still reads it to boot from.... it must need it a raw info.
The ultimate ( Asus MYPAL A620BT ) Pocket PC thread
World Wide English Windows Mobile 2003 / PocketPC 2003
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
German Windows Mobile 2003 / PocketPC 2003
(Screenshoots, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
1. Introduction
2. Attemps getting a A620BT ROM image
3. Hacking/modifying the ROM image
4. A620BT Combo Buttons
5. Screenshots - how did I built them?
6. Problems/questions
1.) Introduction
Hi.
Short time ago I bought the Asus MYPAL A620BT Pocket PC / PDA.
It is a great PDA bundled with the superb "Destinator" navigation software.
Well, I like it to modify embedded software & firmware (especially BIOS files),
as you can see here:
The BNOBTC homepage
So I started to do some reverse-enginering with the A620BT.
2.) Attemps getting a A620BT ROM image
So, logically, I looked for a method how to dump / get the ROM file,
before I could start modifying the Asus MYPAL A620BT ROM itself.
I could not find anything, even the Asus support homepage did not help any further.
But with the help of google.com I could find other interesting stuff:
3.) Hacking/modifying the ROM image
Asus' FTP Server for "special" PDA related files:
"ftp4.asus.com.tw"
UN: PDAUser
PW: pda9983!
( Tip: When I was writing this article the UN:ftp01tk* and PW:vtf2g6z* seemed to be outdated and did/do not work anymore.)
*= can also be found by google.com
Here:
ftp4.asus.com.tw/PDA/AD620BT/ROMImage/PPC2003
I was able to find English, German, etc..., ROM update files.
Inside the zip archives (e.g.: "SW-A4H01WA-007_09931WWE.ZIP") you can find following files:
+ AD620N.nb0
+ BOOT620N.nb0
+ IPL620N.nb0
+ .doc / .txt / readme file
3.1.) AD620N.nb0
It contains the Pocket PC operating system (Windows Mobile 2003 [a.k.a PocketPC 2003])
and the PocketPC Diagnostic Program
(Screenshoots, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
The eight symbolic characters, which are shown on the upper-left and upper-right corner inside the
PocketPC Diagnostic Program can also be found in the "AD620N.nb0" file.
Here is the list with offsets, data and images of/from the symbolic chars:
symbolic character 1 @ 0x0000A400:
00001010FFFE101000007FFC01001110FFFE111001007FFC01003FF801000100
symbolic character 2 @ 0x0000A420:
00007DFE1010102021FE21024102FDFE4502450245FE4502450245FE7C480084
symbolic character 3 @ 0x0000A440:
00003FF80100FFFE8102BD7A8102BD7A00003FF821083FF821083FF8010201FE
symbolic character 4 @ 0x0000A460:
00007C924492452446487D244492449244407DFE4586454A4532454A45868DFE
symbolic character 5 @ 0x0000A480:
000020202020202023FCF82020202BFC310420886050A02020502088A1046202
symbolic character 6 @ 0x0000A4A0:
000003FE00480048FC48084811FE20484048BC482448244824483C8801080208
symbolic character 7 @ 0x0000A4C0:
000001000100010001007FFC41044104410441047FFC01000100010001000100
symbolic character 8 @ 0x0000A4E0:
00000000020001801100510851045006D00290021008100810080FF000000000
There is also another method to get the symbolic characters:
The ROM update file contains a kind of a file system which can be viewed with the really great utility:
=+ DUMPROM += by Willem Jan Hengeveld ( The XDA Developers homepage ).
With DUMPROM I could extract all files and "nk.exe" is the actual/proper/real file
which contains the PocketPC Diagnostic Program / AD620 Test Program.
Because of the "nk.exe" does not begin at offset 0x00 inside the "AD620N.nb0" file,
the real adresses are following:
symbolic character 1 @ 0x00009800.
symbolic character 2 @ 0x00009820.
symbolic character 3 @ 0x00009840.
symbolic character 4 @ 0x00009860.
symbolic character 5 @ 0x00009880.
symbolic character 6 @ 0x000098A0.
symbolic character 7 @ 0x000098C0.
symbolic character 8 @ 0x000098E0.
To view / see the symbolic characters, you just need to convert the hex data into binary (0,1) strings.
For example let us convert the data of the first symbolic character into a viewable symbolic character:
0000 1010 FFFE 1010 0000 7FFC 0100 1110 FFFE 1110 0100 7FFC 0100 3FF8 0100 0100
==>
Code:
HEX |Binary
------+--------
00 00 |00000000 00000000
10 10 |00010000 00010000
FF FE |11111111 11111110
10 10 |00010000 00010000
00 00 |00000000 00000000
7F FC |01111111 11111100
01 00 |00000001 00000000
11 00 |00010001 00010000
FF FE |11111111 11111110
11 10 |00010001 00010000
01 00 |00000001 00000000
7F FC |01111111 11111100
01 00 |00000001 00000000
3F F8 |00111111 11111000
01 00 |00000001 00000000
01 00 |00000001 00000000
Now, let us convert all "0" to "." and "1" to "X" to get a better view:
Code:
................
...X.......X....
XXXXXXXXXXXXXXX.
...X.......X....
................
.XXXXXXXXXXXXX..
.......X........
...X...X...X....
XXXXXXXXXXXXXXX.
...X...X...X....
.......X........
.XXXXXXXXXXXXX..
.......X........
..XXXXXXXXXXX...
.......X........
.......X........
Then, with a drawing program / utility,
each "X" will be drawn as a colored pixel and each "." will not be painted.
Finally, you reached to convert a binary character into a bitmap and you can see the first symbolic character:
(Screenshoot, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
(Now you are able to modify the upper-left and upper-right corner of the diagnostic screen inside the "nk.exe" )
(The background color green was just used for easier image processing.)
The PocketPC Diagnostic Program ( AD620N Test Program ) also contains a nice
Key/Button Test
title scren --> testing the buttons
-->
(Screenshots / animations, PNG / gif conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
3.2.) BOOT620N.nb0
This file contains the bootloader and a built-in flash utiliy which can be accessed by/with special Combo Buttons in section "4"
Furthermore it contains the splash logo which is shown after a reset / after "booting" the Asus MYPAL A620BT PDA.
Here is a photo, which I made:
(Photo by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net)
However, I am not able to rip and display the logo in a decent way.
If you open the BOOT620N.nb0 file in a HEX editor and if you jump to offset:
0x00001E45 (or: 0x00001E47, if the 0D0A string does not belong to the image data),
then you can see the beginning of the image data.
It seems to be any kind of a palette area.
The real / plain image data seems to begin @ offset: 0x00001F98 and seems to end @ offset: 0x00027798.
That means 25800 Bytes [Hex] = 153600 Bytes.
After extracting the area ( after extracting the mentioned 153600 Bytes ) and pasting the data to a new (.RAW) file,
you can open the file in programs which are able to import/open raw files, such as:
"Irfanview".
( http://www.irfanview.com )
In Irfanview choose "RAW - RAW Image Data" as file type when you open the new built .RAW file.
After selecting and opening the file, a new window appears, where you can enter the dimensions and select the bits per pixel.
Take: 240 * 320 * 16bit.
This was my first attempt.
(The RAW image file began with one byte too much. )
(I did not copy and paste the area: 0x00001F98 - 0x00027798. I copied 0x00001F97 - 0x00027798. )
(Screenshoot, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
This was my final attempt:
(This time, the area: 0x00001F98 - 0x00027798 inside the BOOT620N.nb0 was copied and pasted to a new raw file exactly.)
(Screenshoot, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
The logo seems to be have a color depth of 16 bit (2bytes per pixel) + a kind of a palette??????!????
Well, as you can see, I am currently not able to display the image correctly.
So, there are questions.
Please goto section 6.
3.3.) IPL620N.nb0
? ? ?
So, logically, there are questions.
Please goto section 6.
3.4.) .doc / .txt / readme file
The file contains helpfull information and detailed instruction for a ROM Image Update.
It also describes the special Combo Buttons.
4.) Special Combo Buttons
1. Power button + Reset Button --> Cold Boot
2. Record button + Reset Button --> ROM Image Update (Immediately Update AD620N.nb0)
3. AP1 button + Reset button --> Eboot Mode
4. AP2 button + Reset button --> ROM Image Update (Need User Input File Name)
5. AP3 button + Reset button --> Diagnostic Program
6. Power button + AP4 button --> Calibration for Touch Screen
There are further questions.
Please goto section 6.
5.) Screenshots - how did I built them?
Here are some programs which are able to control Pocket PC systems via PC (Netmeeting-like)
and which can be used to build screenshots as long as the Pocket PC is not in FlashROM mode or inside the Diagnostic Program.
+ ActiveSync Remote Display ( part of Windows Mobile Developer Power Toys)
( free download: http://www.microsoft.com/downloads/...d6-1dcc-47aa-ab28-6a2b006edfe9&displaylang=en )
( http://download.microsoft.com/downl...-83a0-81d7d9ac9ce1/WindowsMobilePowerToys.msi )
+ dotPocket (commercial software)
( http://www.dotpocket.com/pocket-pc-software.html )
+ Pocket Controller (commercial software)
( http://www.soti.net/ )
Because there are no(**) lossless methods to grab the screen while the PDA is in Diagnostic - or in FlashROM mode,
and because there are no screen dumping utilities which would work in the mentioned states/modes,
I looked for alternatives and I found some.
With the help of my Plustek USB scanner I could take some really huge and detailed scans from my Asus MYPAL A620BT.
The images were scanned with 1200 DPI, so I was able to:
+ see each dot/pixel/transistor on the touchscreen/TFT
+ re-draw each character and symbol and store each of them in a single graphics file.
With the help of HTML I could rebuild the different screens in a pixel accurate way.
So, I did a huge amount of reverse engineering to get decent screenshots instead stupid and bad photos.
( **= Theoretical, I could open the PDA and grab the digital video / display data from the
TFT / touchscreen pins. )
There are further questions.
Please goto section 6.
6.) Problems, troubles & questions.
Reffering to: 3.) Hacking/modifying the ROM image & 3.3.) IPL620N.nb0:
What are the files: "BOOT620N.nb0" "IPL620N.nb0" detailed for?
How to dump the bootloader area from a Pocket PC to a file?
Reffering to: 3.2) BOOT620N.nb0,
I would like to know:
"How to rip and modify the splash logo in a accurate way?"
"Did I forget something to do?"
Reffering to: 3.4.) .doc / .txt / readme file,
are there further Combo Buttons?
Reffering to: 5.) Screenshots - how did I built them?:
I already tried find the binary data for the displayed font /characters,
when the Asus MYPAL A620BT is in Diagnostic - or in FlashROM mode.
So, I tried to find the binary data for many re-painted chars in the three .nb0 files and extracted files.
For example, I also looked for the binary data of the character: A [ 3078CCCCFCCCCC ]
Code:
HEX|Binary
---+--------
30 |00110000 ..XX....
78 |01111000 .XXXX...
CC |11001100 XX..XX..
CC |11001100 ==> XX..XX..
FC |11111100 ==> XXXXXX..
CC |11001100 XX..XX..
CC |11001100 XX..XX..
However, no files seems to contain the "console font".
In the PC area, the VGABIOS contains the (8*8, 8*16,...) charsets/fonts,
which are "encoded" in the same binary way.
Is there any kind of "VGABIOS" inside the Pocket PC?
(WinRAR and TotalCommander are able to search HEX strings inside files.)
Where is the standard/console font stored (in)?
Is it also stored in one of the .nb0 files?
Reffering to 2.) Attemps getting a A620BT ROM image:
After a second search with http://www.google.com,
I could find two methods to dumping the rom, but both methods do not really work.
a)
The OSImage Tool ( http://www.xs4all.nl/~itsme/projects/xda/OsImageTool.html ) seems to work,
but after ~ 1.5 - 1.7MB nothing happens anymore.
No crash, ...etc., the dumping process just stops and nothing happens anymore.
I tried the OSImage Tool many time and I also removed/closed all applications from the memory.
(Pocket PC->settings->memory)
But everytime I try to dump,
the OSImage Tool stops after ~ 1.5 - 1.7MB.
The dumped part seems to be ok. (There are no weird chars inside the 1.5MB dumped part.)
However, it is just a part - not the whole dump.
In this forum I could find another person, who described the same problem in another thread:
http://forum.xda-developers.com/viewtopic.php?p=34550#34550
I did not try the "bootblaster" yet.
But, I think it is important that the current OSImage Tool will also be improoved.
b)
grab_it ( http://forum.xda-developers.com/viewtopic.php?t=22861 ) brings a stupid error message:
(Screenshoots, PNG conversion and highest possible lossless PNG optimization & file size reduction by:
Borg Number One - borg_no [dot] one -at- gmx [dot] net
Thanks go to GIMP, PNGCRUSH and PNGOUT)
The autostart feature worked and I also tried to start the grab_it manually, but everytime I get the error message:
Cannot create file
I think this will work
grab_it by default trys to write dump.bin file to "/Storage Card" folder since you have "/Speicherkarte" instead it ends with error message try attached file with modiffyed grab_it to work with your asus.
How to restore ROM
Is it possible to restore the original ROM as my PDA doesn't boot (I believe it lost the ROM image).
latest rom for A620BT GER
hi everybody,
i know it's an old post and i'm very unhappy to get it outside the recycle bin but i really need ur help.
IS THERE SOMEBODY WHO HAD THE LATEST ROM v0.99.31 or so in german language for Asus MyPal A620BT? I really need it.
Thanks to the one who can share it with me.
gReeTs
cYBERdEL
rom asus a620bt
hello guys.I desperately need a ROM in English for a620bt.ma someone can help please. [email protected]
Finally i found ROM for A620bt v0.99.31 WWE,and German language,and for A620 the last ROM.I am verry hapy.yeah
A620BT ROM image?
Finally i found ROM for A620bt v0.99.31 WWE,and German language,and for A620 the last ROM.I am verry hapy.yeah
I'd also be a happy guy like you - could you please send the ROM for A620bt v0.99.31 WWE?
thanks in advance
Luke
[email protected]
Dear all
i keep reading most of the topics about upx files and download the latest ver from http://upx.sourceforge.net/
I did not found any clear steps of
How to UPX .exe & .dll files?
Can some help, please?
Best is:
upx --best --crp-ms=999999 --nrv2b -o FILE_OUT.exe FILE_IN.exe
Whiterat said:
Best is:
upx --best --crp-ms=999999 --nrv2b -o FILE_OUT.exe FILE_IN.exe
Click to expand...
Click to collapse
How does that differ from upx --brute file ?
Also upx 3.01 was released on July 31, 2007 so make sure you have the latest version for best results.
Yes I have 3.01 but I read the help file and I'm not sure that I know the steps
Can someone elaborate,
Regards
The_hesham said:
Yes I have 3.01 but I read the help file and I'm not sure that I know the steps
Can someone elaborate,
Regards
Click to expand...
Click to collapse
Ok sparky..how much more elaboration do you need then for two different people to give you sample command lines?
If you can't figure out "upx --brute *" after reading my post you really don't need to run the app. It's a command line app.
famewolf said:
Ok sparky..how much more elaboration do you need then for two different people to give you sample command lines?
If you can't figure out "upx --brute *" after reading my post you really don't need to run the app. It's a command line app.
Click to expand...
Click to collapse
Ok sparky
I do not understand
upx --brute is this explanation well help me to compress & decompress
If u dont want to explain, sure somone else will
I guess "upx --help" was to much effort for you. If this and the previous posts are not clear enough for you I look forward to seeing someone else explain it so you can understand.
upx --help
Ultimate Packer for eXecutables
Copyright (C) 1996,1997,1998,1999,2000,2001,2002,2003,2004,2005,2006,2007
UPX 3.01 Markus Oberhumer, Laszlo Molnar & John Reiser Jul 31st 2007
Usage: upx [-123456789dlthVL] [-qvfk] [-o file] file..
Commands:
-1 compress faster -9 compress better
--best compress best (can be slow for big files)
-d decompress -l list compressed file
-t test compressed file -V display version number
-h give this help -L display software license
Options:
-q be quiet -v be verbose
-oFILE write output to 'FILE'
-f force compression of suspicious files
--no-color, --mono, --color, --no-progress change look
Compression tuning options:
--brute try all available compression methods & filters [slow]
--ultra-brute try even more compression variants [very slow]
Backup options:
-k, --backup keep backup files
--no-backup no backup files [default]
Overlay options:
--overlay=copy copy any extra data attached to the file [default]
--overlay=strip strip any extra data attached to the file [DANGEROUS]
--overlay=skip don't compress a file with an overlay
Options for atari/tos:
--all-methods try all available compression methods
Options for djgpp2/coff:
--coff produce COFF output [default: EXE]
--all-methods try all available compression methods
--all-filters try all available preprocessing filters
Options for dos/com:
--8086 make compressed com work on any 8086
--all-methods try all available compression methods
--all-filters try all available preprocessing filters
Options for dos/exe:
--8086 make compressed exe work on any 8086
--no-reloc put no relocations in to the exe header
--all-methods try all available compression methods
Options for dos/sys:
--8086 make compressed sys work on any 8086
--all-methods try all available compression methods
--all-filters try all available preprocessing filters
Options for ps1/exe:
--all-methods try all available compression methods
--8-bit uses 8 bit size compression [default: 32 bit]
--8mb-ram 8 megabyte memory limit [default: 2 mb]
--boot-only disables client/host transfer compatibility
--no-align don't align to 2048 bytes [enables: --console-run]
Options for tmt/adam:
--all-methods try all available compression methods
--all-filters try all available preprocessing filters
Options for vmlinuz/386
--all-methods try all available compression methods
--all-filters try all available preprocessing filters
Options for watcom/le:
--le produce LE output [default: EXE]
Options for win32/pe, rtm32/pe & arm/pe:
--compress-exports=0 do not compress the export section
--compress-exports=1 compress the export section [default]
--compress-icons=0 do not compress any icons
--compress-icons=1 compress all but the first icon
--compress-icons=2 compress all but the first icon directory [default]
--compress-icons=3 compress all icons
--compress-resources=0 do not compress any resources at all
--keep-resource=list do not compress resources specified by list
--strip-relocs=0 do not strip relocations
--strip-relocs=1 strip relocations [default]
--all-methods try all available compression methods
--all-filters try all available preprocessing filters
file.. executables to (de)compress
This version supports:
amd64-linux.elf linux/ElfAMD
amd64-linux.kernel.vmlinux vmlinux/AMD64
arm-linux.elf linux/armel
arm-linux.kernel.vmlinux vmlinux/armel
arm-wince.pe arm/pe
armeb-linux.elf linux/armeb
armeb-linux.kernel.vmlinux vmlinux/armeb
fat-darwin.macho Mach/fat
i086-dos16.com dos/com
i086-dos16.exe dos/exe
i086-dos16.sys dos/sys
i386-bsd.elf.execve BSD/386
i386-darwin.macho Mach/i386
i386-dos32.djgpp2.coff djgpp2/coff
i386-dos32.tmt.adam tmt/adam
i386-dos32.watcom.le watcom/le
i386-freebsd.elf BSD/elf386
i386-linux.elf linux/elf386
i386-linux.elf.execve linux/386
i386-linux.elf.shell linux/sh386
i386-linux.kernel.bvmlinuz bvmlinuz/386
i386-linux.kernel.vmlinux vmlinux/386
i386-linux.kernel.vmlinuz vmlinuz/386
i386-netbsd.elf BSD/elf386
i386-openbsd.elf BSD/elf386
i386-win32.pe win32/pe
m68k-atari.tos atari/tos
mipsel-linux.elf linux/mipsel
mipsel.r3000-ps1 ps1/exe
powerpc-darwin.macho Mach/ppc32
powerpc-linux.elf linux/ElfPPC
powerpc-linux.kernel.vmlinux vmlinux/ppc32
Whiterate said
upx --best --crp-ms=999999 --nrv2b -o FILE_OUT.exe FILE_IN.exe
You explain very much
How does that differ from upx --brute file ?
I can list 4 u how many commands in buzz
most of them made problems with the icons
I was looking for a clear command someone try it and it works withy min. prob.
The help u mention I raed it before asking & u still think it is clear!!
I'm looking 4 this correct command 4 more than 3 days.
each time the replyers have prob.
If reach 2 the right command just post it.
Finaly I found it for PC & PPC - latest
Software Name: UPX4PC
Software Version: 1.2.1, Packaged with UPX version 3.00.
Release Date: 10th May 2007
Supports: Windows PC
The link
http://mobile-sg.com/software/?p=UPX4PC&platform=pc
UPX4PPC
Software Version: 0.4.2
Release Date: 9th September 2007
The link
http://mobile-sg.com/software/?p=UPX4PPC&platform=ppc
The_hesham said:
Software Name: UPX4PC
Software Version: 1.2.1, Packaged with UPX version 3.00.
Release Date: 10th May 2007
Supports: Windows PC
The link
http://mobile-sg.com/software/?p=UPX4PC&platform=pc
UPX4PPC
Software Version: 0.4.2
Release Date: 9th September 2007
The link
http://mobile-sg.com/software/?p=UPX4PPC&platform=ppc
Click to expand...
Click to collapse
thanks the_hesham .. downloading and trying
I am Using Original ROM RUU_Elfin_hTC_Asia_India_3.07.720.03_4.1.13.71_03.34.90_BLUE_Ship.
The problem faced by me is that i am not able to edit my date format on the home screen. I have tried all the combinations.
Initialy i went to regional setting and changed the short date setting and later went to HKLM/nls/override and then edited SSDte to ddd, dd MMM, yy. and then rebooted the ELFIN. but that **** stuff won't change. I have been doing this registry edit in all my other handsets but they turnout to be right.
Even after many combinations my date remains to be Dec 06, 2008(format only). Actually i want it to be Sat, 6 Dec, 2008.
I seriously look upon you senior members to help me out.
My details are as such:
Touch version : Elfin
Device ID : ELF010050
CID : DOPOD001
IPL : 3.07.0002
SPL : 3.07.0000
ROM Version : 3.07.720.03
ExtROM Version : None
Operator Version: None
AKU Version : 1.2.7
Page Pool : 12 MB
RAM Size : 128 MB
ROM Size : 256 MB
Model No. : ELF0100
ROM VERSION: 3.07.720.03
ROM DATE: 10/25/08
RADIO VERSION: 03.34.90
PROTOCOL VERSION : 4.1.13.71
WINDOWS MOBILE 6.1 Professional
CE OS 5.2.19972 (bUILD 19972.1.2.7)
Partial Solution found
Copy the file attached here below and Paste it into My Documents of your ELFin
Disable the Touchflo from Start<Setting tabs<Today<Items.
Now Go to My Documents Folder(using File Explorer) and press Manila2D file (the one pasted), wait for a second and the Home page with proper date format is seen.
Step Further
I tried pasting this file into Windows folder instead of My Documents folder, it says
" A system file named 'Manila2D' already exist.
Replace the existing file 1.07M, Thu,9Oct08, with this one?
1.07M, Tue,9Dec,08
Yes No,
If I press yes then it further displays a message saying:
X Cannot copy 'Manila2D':
Access is denied.
Be certain that there is enough free storage memory, that the destination is not write-protected and that the file is not currently in use.
CAN SOME BODY HELP HOW TO INSERT THIS FILE INTO WINDOWS FOLDER.