First of all I apologies because my thread isn't really phone related. But I saw that some members have experience with magellan gps devices, like Roadmate.
Triton are new GPS handled devices from Magellan. They run WINCE 5.0 Core and have custom shell(similar structure like Roadmate devices).
Issue that I have is that during upgrade of firmware power went down on my Desktop PC and flashing process gone bad. Now I can power up device but there is no connectivity to PC(shell uses special drivers to connect to PC, which now are probably corrupted or what so ever).
So what I would like to now is somebody can explain to me is it possible to change somehow startup process, or something similar. I think that word "cooking" is used to describe process of editing OS image to add, replace, modify OS. I tried some of tools for editing but I'm not sure where I'm making mistakes because I can't even get dump of files from OS image. I again say it is WinCE 5.0 CORE. I tried looking with hex editor but I can't find any reference to mgmShell.exe(that is name of shell exe). I would be very thankful if somebody could explain me these things to me because then I would probably be able to copy files back(I would add FileManCE or MortScript and I figured out way of applying OS image from SD Card) from SD card to internal storage and restore my unit.
If there is anybody interested I will put somewhere whole update package from Magellan. It contains OS image in bin format.
Again I apologies but I'm very desperate to restore my unit , and as I can see this only place with enough knowledge to help me. Sorry.
Related
I have probably a stupid question, but I ask it.
I would like to know if it is possible to upgrade a pda without flashing ? why it is not enough to install a big cab and load registry ?
I know most of the pda have just 64 Mb memory. and often the rom is 64 Mb, so if we do like that at the end we will have no memory.
But O2 XDA Flame has 2 Gb of memory. so 64 Mb is nothing and I can spend it, if that allows me to upgrade it without the need to cook a rom with complex tools, to find how to be in bootloader, and without the ask to brick it.
Stupid question ?
I can't imagine that no one knows concerning my question in xda- devs.
Not so stupid question. But the answer is simple - because the bootloader was designed in such a way it can only load the OS from its special partition in a special manner.
There are some ways to boot from specially formatted SD, but thats all.
and a cab file is a pocketpc install file
a pocketpc install file cant change the os
because it would mean that the installed things
had to update the system which was running it
think sawing over the branch you are sitting on in the tree
Theoretically, you could overwrite all the non-system files (or at least the ones not needed for initiating the boot) with all the new files and overwrite the hv registry files... but I wonder how well this would work... And how fast it would be if you're not using modules but instead just files... and you couldn't really update it to WM6...
Thanks to all of you.
When I have asked the question, we where not able to flash the Flame. Now we are.
So know I am in the process to port wm6 on the Flame.
I have extracted the xip of the Flame using xipport.
And I have also extracted the xip of the WM6 port to Universal of ranju.
Now I am in the process of merging the 2 xip.
If somebody can give me some advices, I will be glad.
Ranju has started. But I need more info in the process of mixing.
Hello,
Because my internal nand memory was corrupted, my device (eten x600) can't load the booter section of the rom. Because of the way the phone acts, i guess only the first sectors of the memory were corrupted (booter,ipl,knight, usbdl etc) If I reflash only the booter through usbdl the device will boot corectly one time (then the booter gets corrupted next time when powering on the device).
So untill i sort this out i have 2 possible solutions, as far is i see:
1.make this booter.bin file flash'able from sd card in bootloader mode (at least i wount depend on a computer to run usbdl.exe). As it is, the bootloader doesn't recognise it as a valid rom, because of the missing headers I supose...
2. modify the booter.bin in order to rearm itself, reactivate, relocate or something similar in order not to get corruped on restart, or rewrite itself on every restart. I have no ideea on how to do this or if it's possible in some way.
So, if any cooker or advanced user can help me, please try, i'll make this on myself if i'm pointed in the right direction, tools needed etc. What is possible and what not?
Also I would like to make this some sort of sticky on eten-users, when I have a plausible final solution, because it seems no one there knoks what to do with this corrupted memory problems.
Hi all,
I have an ASUS R600 GPS running WinCE 5.0 core. I unlocked it using AsusPocket (ASUS customized version of MioPocket to keep things such as bluetooth) and everything seemed fine.
However I'm running against a "low memory" errors when running certain navi software such as Navigon and iGo. The device has 64 Mb of RAM which should be plenty for these, as my cheap Omnitech has the same amount and has no problems.
With help of MioPocket guys, I traced it down to a massive \Windows in this device's ROM. It is like 25 Mb as they dumped not only every dll they could find there, but also eg a lot of big wav and bmp files. Couple wav files are close to 1Mg each! Since according to these folks \Windows just gets copied from ROM to RAM on startup, I end up with far less free memory to play with than I'd like.
I'm new to ROM cooking but with some help I'm sure I could do it. To keep things very simple I was thinking of just replacing these big wav files with a small one. This way the file count and names wouldn't change and I wouldn't run a risk of ever running into a "file not found" condition. I really don't care if on startup the device plays a simple "ding" as opposed to 20 sec sound. Since soft that I want actually runs and only gets into low memory condition on more complex route recalculation or reality view screens, I think this would be enough to get me over the hurdle. Of course, any checksums will need to be regenerated as needed.
So, at this point I have downloaded upgrade ROM images for this device. Is that something that can be disassembled, modified as described above, and put back together? I tired naively unleashing dumprom on one of these .bin files, but got back "unable to determine loading offsets" error. I guess I shouldn't be surprised as at this point I don't know what I'm doing...
Can anybody offer any help to me? With all the amazing things I read on this site people doing with ROM modifications, it looks like what I'm trying to do should be a walk in the park. Am I right trying to go from upgrade .bin file? Or should I get some tools to read off the device? Please help.
Btw. if anybody'd like to peek at this upgrade bin, it can be downloaded here: hxxp://support.asus.com/download/download.aspx?modelname=R600&SLanguage=en-us, in the firmware section, version 4.3.0 and version 4.8.0 for NA users. Unfortunately no direct link.
Thanks in advance
mamon
I'm currently developing a program that basically receives updates and performs them on mobile devices. These are running Windows Mobile 2003.
The update simply consists in a number of files/directories deletes, creates, attributes changes and overwrites (when modified). It's not clever or optimised in any way. But there is a problem.
If the program finds some files need to be modified, the program performs the modification and then immediately makes a kernel call to hard reset the device, so as to reload the OS which is set to read the persistent directories for further booting instructions (which was just changed).
It appears a small number of devices went through such an update but the old data is still being loaded into the registry for instance. There is no trace of where this could come from and I can guarantee it is not burnt into the OS's ROM. I suspect FAT12 or FAT16 corruption of its tables or perhaps its "Root Level Directory" section... reason is probably that the program makes the hardreset too quickly for all buffers to flush in time. Being a hardreset and not a soft one, I assume the buffers are destroyed and never written on disk, thus some changes are lost and some may have been done partially. This problem leaves what I call ghost files around. These files cannot be found anywhere, but somehow are read by the program in OS ROM that is set to find them in the root level dirs of the persistent partitions.
I've been researching like crazy to find a way to make a good call to FlushFileBuffers() to flush everything (data and metadata) before doing the hardreset. But I haven't found any good documentation that works for win32 ce 3.0. I've had to implement all kinds of silly workaround that are making the whole process take much longer than needed...
I'd like your input on how I could make sure everything is flushed properly on these WM2003 devices before I issue the call to hard reset.
Thanks,
Simon
So I have a broken sd card port, which does not read my sd cards anymore. And I was already on scoot's latest android build, but what do you do when something is broken? Well, you go back to factory settings and for our blessed HTC Kaiser or in my case MDA Vario III, this means going back to the abomination called WM (and to make matters even worse it is tmobile themed). But it seems that this also doesn't fix the problem and the sd card is still not read. It does say it needs to format the sd card for it to work, which I then give the permission to do, but it is never able to finish the format.
So my question is fairly simple: how to flash android on your WM device with usb?
thanks in advance!
( I am really stupid, going back to WM )
**I have looked for other guides, but they all assume you to already have android installed on your phone**
It sounds like the ribbon cable is broken for the SD card. The only fix is to replace it, unless there is some other problem with the main board.
So how am I suppose to replace this "riboon cable" do I need to buy some extinct hardware specifically for the kaiser (which probably is impossible to get?) or can I do it some other way. And is there really no way to flash Android on the kaiser via usb, since I think I can manage with only a couple of apps on the internal storage...
Also I have already tried to flash android on my htc kaiser:
- I dragged and dropped the KAISIMG.NBG over the installer of my original t-mobile rom, but somehow it just installs the original rom again and not the KAISIMG.NBG
AFAIK, the only 2 ways to flash anything to a Kaiser is through the SD card or USB port. Noone (to my knowledge) has ever created a RUU-flashable Android package for the Kaiser or any other device, which would be your only option.
Given the constraints on the RAM built into the Kaiser, you would have to build a pretty small package for the install, maybe 55-60MB, use Oli's NBH creator and (hopefully) build an installable package that can be sent via USB with an unsigned RUU updater.
If someone wants to take on the task of stripping an androidinstall package, extracting it and repacking it into a RUU installable NBH, feel free. I know it can be done with a kernel package, but that is only 3MB and goes to the first partition. All the other files would have to go to the correct partitions as well (/system, /data, /cache, etc.).
So how am I suppose to make an installable package? I have the file to get WM to Android, the kernel, and scoots android install package, which I have stripped down to 67 mb.
What should I do with these files? Do you have some kind of instructions?
You would have to figure out how to not only partition the NAND, but direct the kernel and all files to their appropriate partitions.
Someone must have some info on how to do this...
Sent from this addictive thumb magnet...