Google
  Web www.gpspassion.com


GpsPasSion LIVE!
www.flickr.com
This is a Flickr badge showing public photos from GpsPasSion Live !. Make your own badge here.

www.NaviBlog.com



Versions

Links/Liens




Portal/Portail
Rechercher

- -

Polls/Sondages
Sondage
Pour vous guider sur la Route :
GPS Mobile (SEM)
GPS Intégré
Smartphone
Autre
Voter  -  Résultat des votes
Votes : 2172




Club GpsPasSion
Soutenez le site!

USA: (US$)
EUROPE: (€)
Guide Paypal


GpsPasSion Forums
Home | Profile | Register/Enregist. | Active Topics | Search/Recherche | FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 English Forums - Hardware
 "All in One" Navigation Systems
 Bricked Malata PG-84303 brand PNA
 New Topic  Reply/Répondre
 Printer Friendly
Author Previous Topic Topic Next Topic  

Sambas

1 Posts

Posted - 27 mai 2009 :  08:13:39  Show Profile  Reply with Quote
I have bricked Malata PG-84303 brand PNA. It seems to be very common fault, it just gets stuck on boot screen. Many users have had same problem and for now only solution is to get device changed to new. I decided to investigate if firmware could be reflashed. I got binary dump from working device made by atlas3_nr tool. Found out that it has nboot and eboot bootloaders. With atlas manager I can access them. Now I need to figure out how to make flashable firmware from that full binary dump. I can download firmware by using SD card or Atlas manager. Seems like I would need chain.lst, chain.bin, nk.bin etc files. Anyone with some binary dump and eboot knowledge what I need to do?

V1.10(LOW)
1): Launch EBOOT
2): Launch NK
4): Erase and Reset TOC
5): Toggle NBOOT Menu
6): Set Clock
TOC updated
Jump to: 0xC004C000
Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Jun 24 2008 10:46:59
Centrality Windows CE Atlas Bootloader Version 3.2 Built Oct 17 2008 15:32:04 
dwCacheInfo = 0x1D152152 
EBOOT Version = 0x300B 
TOC {
dwSignature: 0x434F544E
BootCfg { 
  ConfigFlags: 0x7820
  BootDelay: 0xF
  ImageIndex: 1 
  IP: 0.0.0.0
  MAC Address: 00:00:00:00:00:00
  Port: 0.0.0.0
  SubnetMask: 0.0.0.0
}
ID[0] {
  dwVersion: 0x300B
  dwSignature: 0x45424F54
  String: 'eboot.nb0'
  dwImageType: 0x2
  dwTtlSectors: 0x140
  dwLoadAddress: 0x8C04C000
  dwJumpAddress: 0x8C04C000
  dwStartBlock: 0x2
  dwStoreOffset: 0x0
  sgList[0].dwSector: 0x40
  sgList[0].dwLength: 0x140
}
ID[1] {
  dwVersion: 0x1
  dwSignature: 0x43465348
  String: 'PPC2K3.NB0'
  dwImageType: 0xE
  dwTtlSectors: 0x1610
  dwLoadAddress: 0x8C856000
  dwJumpAddress: 0x8C857000
  dwStartBlock: 0xD
  dwStoreOffset: 0x0
  sgList[0].dwSector: 0x1A1
  sgList[0].dwLength: 0x1610
}
chainInfo.dwLoadAddress: 0x8C64C000
chainInfo.dwFlashAddress: 0x0000B1A1
chainInfo.dwLength: 0x00000020
nandxipInfo.dwCodePages: 0
nandxipInfo.dwCopies: 0
nandxipInfo.dwBlockNo: 0x00000000
nandxipInfo.dwCodePages: 0
nandxipInfo.dwCopies: 0
}
Image block starts at physical block 13 virtual block 13
WARNING: OEMPlatformInit failed to initialize Ethernet controller.
SDMMC card is removed!
rSD_CUR_STATE = 0x1F80000
Press [ENTER] to download image now, or [SPACE] to enter boot monitor.

Initiating image download in 9 seconds. 
IsValidMBR: MBR sector = 0x1A0

OpenPartition: Partition Exists=0x0 for part 0x12.

GetReadOnlyPartInfo: READ-ONLY partition have not created.


EBoot V1.09.1 for Centrality Atlas-3

Ethernet Boot Loader Configuration:
---------------------------------------
1) IP address : 0.0.0.0
   Subnet mask: 0.0.0.0
2) Boot delay: 15 seconds
3) DHCP: ENABLED
4) Max Bad blocks reserved: 10
5) Startup image: DOWNLOAD NEW
6) Program RAM image into Boot Media: ENABLED
7) MAC address: 00:00:00:00:00:00
8) Bluetooth address: 00:00:00:00:00:00
9) Format Boot Media for BinFS
0) Format Boot Media for Monolithic NK Image

A) UPDATE image from SD/MMC card
D) DOWNLOAD image now
F) Low-level FORMAT Boot Media
N) New NANDFLASH Driver: DISABLED
L) LAUNCH existing Boot Media image
S) Save Configuration and Exit
U) Using AtlasMgr to download NK image
I) DOWNLOAD image via USB RNDIS Ethernet
R) LAUNCH existing Boot Media image via USB RNDIS KITL
C) Read-Only User FAT partition (type 0x12) block num: 0
P) Read-Only User FAT partition (type 0x12): Not exist
V) Image check sum
X) Clean Hive Partition
G) Dump Flash
T) Debug NandFlash
---------------------------------------

Enter your selection: g

Ads


cri92

1 Posts

Posted - 19 juil. 2009 :  23:21:20  Show Profile  Reply with Quote
quote:
Originally posted by Sambas

I have bricked Malata PG-84303 brand PNA. It seems to be very common fault, it just gets stuck on boot screen. Many users have had same problem and for now only solution is to get device changed to new. I decided to investigate if firmware could be reflashed. I got binary dump from working device made by atlas3_nr tool. Found out that it has nboot and eboot bootloaders. With atlas manager I can access them. Now I need to figure out how to make flashable firmware from that full binary dump. I can download firmware by using SD card or Atlas manager. Seems like I would need chain.lst, chain.bin, nk.bin etc files. Anyone with some binary dump and eboot knowledge what I need to do?

V1.10(LOW)
1): Launch EBOOT
2): Launch NK
4): Erase and Reset TOC
5): Toggle NBOOT Menu
6): Set Clock
TOC updated
Jump to: 0xC004C000
Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Jun 24 2008 10:46:59
Centrality Windows CE Atlas Bootloader Version 3.2 Built Oct 17 2008 15:32:04 
dwCacheInfo = 0x1D152152 
EBOOT Version = 0x300B 
TOC {
dwSignature: 0x434F544E
BootCfg { 
  ConfigFlags: 0x7820
  BootDelay: 0xF
  ImageIndex: 1 
  IP: 0.0.0.0
  MAC Address: 00:00:00:00:00:00
  Port: 0.0.0.0
  SubnetMask: 0.0.0.0
}
ID[0] {
  dwVersion: 0x300B
  dwSignature: 0x45424F54
  String: 'eboot.nb0'
  dwImageType: 0x2
  dwTtlSectors: 0x140
  dwLoadAddress: 0x8C04C000
  dwJumpAddress: 0x8C04C000
  dwStartBlock: 0x2
  dwStoreOffset: 0x0
  sgList[0].dwSector: 0x40
  sgList[0].dwLength: 0x140
}
ID[1] {
  dwVersion: 0x1
  dwSignature: 0x43465348
  String: 'PPC2K3.NB0'
  dwImageType: 0xE
  dwTtlSectors: 0x1610
  dwLoadAddress: 0x8C856000
  dwJumpAddress: 0x8C857000
  dwStartBlock: 0xD
  dwStoreOffset: 0x0
  sgList[0].dwSector: 0x1A1
  sgList[0].dwLength: 0x1610
}
chainInfo.dwLoadAddress: 0x8C64C000
chainInfo.dwFlashAddress: 0x0000B1A1
chainInfo.dwLength: 0x00000020
nandxipInfo.dwCodePages: 0
nandxipInfo.dwCopies: 0
nandxipInfo.dwBlockNo: 0x00000000
nandxipInfo.dwCodePages: 0
nandxipInfo.dwCopies: 0
}
Image block starts at physical block 13 virtual block 13
WARNING: OEMPlatformInit failed to initialize Ethernet controller.
SDMMC card is removed!
rSD_CUR_STATE = 0x1F80000
Press [ENTER] to download image now, or [SPACE] to enter boot monitor.

Initiating image download in 9 seconds. 
IsValidMBR: MBR sector = 0x1A0

OpenPartition: Partition Exists=0x0 for part 0x12.

GetReadOnlyPartInfo: READ-ONLY partition have not created.


EBoot V1.09.1 for Centrality Atlas-3

Ethernet Boot Loader Configuration:
---------------------------------------
1) IP address : 0.0.0.0
   Subnet mask: 0.0.0.0
2) Boot delay: 15 seconds
3) DHCP: ENABLED
4) Max Bad blocks reserved: 10
5) Startup image: DOWNLOAD NEW
6) Program RAM image into Boot Media: ENABLED
7) MAC address: 00:00:00:00:00:00
8) Bluetooth address: 00:00:00:00:00:00
9) Format Boot Media for BinFS
0) Format Boot Media for Monolithic NK Image

A) UPDATE image from SD/MMC card
D) DOWNLOAD image now
F) Low-level FORMAT Boot Media
N) New NANDFLASH Driver: DISABLED
L) LAUNCH existing Boot Media image
S) Save Configuration and Exit
U) Using AtlasMgr to download NK image
I) DOWNLOAD image via USB RNDIS Ethernet
R) LAUNCH existing Boot Media image via USB RNDIS KITL
C) Read-Only User FAT partition (type 0x12) block num: 0
P) Read-Only User FAT partition (type 0x12): Not exist
V) Image check sum
X) Clean Hive Partition
G) Dump Flash
T) Debug NandFlash
---------------------------------------

Enter your selection: g


Go to Top of Page

ablbd

358 Posts

Posted - 23 nov. 2009 :  20:29:12  Show Profile  Reply with Quote
In case you are still interested, I am working on a complex tool. Recently it got a new option: it creates from a raw dump the MSBIN files. Image (and file) names are taken from the xip chain, so they will work. To be successful, 1 condition have to be fulfilled: the dump must come from exactly the same device as the bricked one. The packing routine is not yet optimised, so flashing takes a little bit more than it should. Use external source during flashing and you'll be in the safe side.
Upload somere your dump and you'll get the "bin"'s. No need for AtlasMgr, OS can be flashed from SD too.

Edited by - ablbd on 23 nov. 2009 20:42:45
Go to Top of Page

cnoux35

France
5 Posts

Posted - 25 nov. 2011 :  10:25:42  Show Profile  Reply with Quote
quote:
Originally posted by Ablbd
In case you are still interested, I am working on a complex tool. Recently it got a new option: it creates from a raw dump the MSBIN files. Image (and file) names are taken from the xip chain, so they will work. To be successful, 1 condition have to be fulfilled: the dump must come from exactly the same device as the bricked one. The packing routine is not yet optimised, so flashing takes a little bit more than it should. Use external source during flashing and you'll be in the safe side.
Upload somere your dump and you'll get the "bin"'s. No need for AtlasMgr, OS can be flashed from SD too.


Hi Ablbd,
Are you still here ? You posted this, 2 years ago!
Is it still possible to get hour help for a bricked gps "Evadeo"? It has got a Sirf-Atlas III CPU, and I have got a dump from DiskRW (.img file) and another one from Atlas3_nr (bin files) - 64 Mb each. They both come from an identical working unit. It must be necessary to download NK.bin (or PPC2K3.nb0) to the flash unit to get the bricked unit alive again, as it showns only a bleue screen!
I've now uploaded the dumps.
Thanks for answer

Evadeo for ever

Edited by - cnoux35 on 30 nov. 2011 09:37:09
Go to Top of Page

ablbd

358 Posts

Posted - 27 nov. 2011 :  21:31:51  Show Profile  Reply with Quote
Hi knoux35
I left a new post notification on this page so no problem. I should know what type of Evadeo you have, maybe I have the original rom for it and if not, at least to put your files in the proper folder for this particular Evadeo. I'll be back soon with the upgrade file.

Regarding file name, don't be so sure! IE, Evadeo x50/x60 requires G407n_OS.bin...
Go to Top of Page

cnoux35

France
5 Posts

Posted - 27 nov. 2011 :  22:04:15  Show Profile  Reply with Quote
Hi Ablbd,
No, the type is Evadeo "M" series (M20,M30,M35). G407n_OS.bin is for X series, not the same!
Thanks anyway for answer. For M series, the "maker" (IGN) doesn't provide the OS upgrade.
So only one solution, extract files from dumps, as you know to do so!
OS is windows CE 5.0. It looks like NBOOT and EBOOT are OK, since we can run them with Atlas Mgr. Unfortunately, we don't have got the special USB cable required to dump from a working device, and it looks like it's not possible to dump to the SD card neither (not working).
I began extracting NK.nb0 from image file, as you explained to do in forum buzzdev.com, but I've a lot to learn for succeeding in final result (chain.bin, TINYNK ...)
So thanks for an (or several) upgrade file.

Evadeo for ever

Edited by - cnoux35 on 28 nov. 2011 10:31:20
Go to Top of Page

ablbd

358 Posts

Posted - 28 nov. 2011 :  17:31:27  Show Profile  Reply with Quote
This is a multi-xip image: http://www.megaupload.com/?d=4KO47P5V
Try to copy the files into the root of a <2G SD formatted FAT(16) under WinXP and play with some button combinations in order to enter upgrade; if doesn't work, enter boot monitor menu with atlasmgs: nboot 1:Eboot, after launching eboot press space->enter, select "U) Using AtlasMgr to download NK image"; it will activate "upgrade NK" button, press it and select chain.lst from above package.
Go to Top of Page

cnoux35

France
5 Posts

Posted - 28 nov. 2011 :  19:07:21  Show Profile  Reply with Quote
OK, many thanks.
For the combinations, I think they're RESET while pressing upper button for 1-2 seconds(as for Atlas Mgr).
OK too with Atlas Mgr, I've already seen that procedure, I just missed the precious files.
Thanks again.
I'll report result ...
If success, several victims of the "blue screen" among "evadeistes" will be very glad!

Evadeo for ever

Edited by - cnoux35 on 28 nov. 2011 20:12:13
Go to Top of Page

cnoux35

France
5 Posts

Posted - 28 nov. 2011 :  23:18:26  Show Profile  Reply with Quote
Incredible, fantastic, unhoped! You're a true magician !

Thanks a thousand more! It is alive again, after putting the 4 files on a SD card, and starting with Reset and 10 seconds pressing the upper button, and a few minutes ...

Without a hiccup, it has come back to life!

I'll just have a last question about my device : in testing Atlas Mgr, I most probably modified the clock of mine, and now, it's very slow! It's not very annoying, because I don't use it as a GPS, only for tests, but tests are longer.
I tried to restore normal settings (4 choices under option 6 of NBOOT), but it is always slow. Could the OS updtate correct this problem ? This is just the supplementary question !

Evadeo for ever
Go to Top of Page

ablbd

358 Posts

Posted - 29 nov. 2011 :  06:00:51  Show Profile  Reply with Quote
No, clock settings are stored inside nboot and OS has nothing to do with this. A reasonable value could be 368 (or 396, with the risk of over-heating the CPU in hot days) MHz but you have to find the proper division ratio(2'nd choice), which usually is 4:2:2:1. In case that the division ratio is not correctly set, some hardware like display or RAM may not function properly.
Go to Top of Page

cnoux35

France
5 Posts

Posted - 29 nov. 2011 :  16:29:54  Show Profile  Reply with Quote
Thanks one more time, Ablbd, I'm going to apply these recommendations !

Thanks again from Evadeo_M users !
Bye

Evadeo for ever
Go to Top of Page

exe

Spain
3 Posts

Posted - 16 déc. 2011 :  22:30:20  Show Profile  Reply with Quote
hello all! i´m new to this forum and really have searched before posting here, but didnt find anythink that could help me :( . i have a supratech triton xl gps, and without intention i have flashed a wrong file. at this momment my computer doesn´t recognize him anymore... i have try´d atlasmgr (diferent version, and 2 computers) but nothing. @ ablbd from what i see, you really know much about this thing´s. i want to know is there a way to fix my device? thank you all in advance and wait for any ideas.

PS: allmost forgot, when i push the power button only a red led light it show´s. no light on the screen nothing.

Edited by - exe on 16 déc. 2011 22:34:58
Go to Top of Page

ablbd

358 Posts

Posted - 17 déc. 2011 :  16:38:18  Show Profile  Reply with Quote
exe, try to reflash from sd with this: http://www.megaupload.com/?d=4E3K2RJH
You must find a button combination which starts the upgrade; be carefull with SD, read my previous post.
Go to Top of Page

exe

Spain
3 Posts

Posted - 18 déc. 2011 :  11:57:01  Show Profile  Reply with Quote
thank you for your help but i try that in every possible combination and it doesn't want to start the update. i'm also romanian and we can speak on other's forum in romanian for better comunication or we can speak here. if you have any other idea i will be very happy to try it. thank's one more time and wait for any sugestion.
Go to Top of Page

exe

Spain
3 Posts

Posted - 10 févr. 2012 :  16:35:05  Show Profile  Reply with Quote
hello all, hello ablbd !! nobody can´t help me please? my gps is steel dead :( can anyone explain step by step how can i use atlasmgr?? how i make the connexion? please someone help me..
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply/Répondre
 Printer Friendly
Jump To:
GpsPasSion Forums © 2002-2014_GpsPasSion/Manzanite Go To Top Of Page
This page was generated in 0,59 seconds. Powered By: Snitz Forums 2000 Version 3.4.05