YG-902M-ABFSJ-2G-AS-5LS MTK MT3351 WinCE GPS Firmware

User question

Szukam firmware do chińskiej nawigacji GPS opartej na płycie YG-902M-ABFSJ-2G-AS-5LS.
Wersja OS: V1.1.0.10.04.10 2G
Wersja AP: V1.3.01.10.05.05
Chipset MTK MT3351, WinCE, ekran 4,3 cala, Bluetooth.
Urządzenie zawiesza się na ekranie startowym, potrzebuję plików firmware/boot do przywrócenia przez kartę SD.
Znane też jako YG-902M v2.3 lub YG-902M-FSJ-2G-4LS-5LS.

Artificial Intelligence Response

Direct answer to the question

For your YG-902M-ABFSJ-2G-AS-5LS / YG-902M-FSJ-2G-4LS-5LS, MTK MT3351, WinCE, 2 GB NAND, 4.3", Bluetooth navigation unit, the most relevant firmware family to look for is:

• FW_MTK_YG2GB.rar
• sometimes referenced for YG-902M V2.1/V2.3, Pioneer PI-5020 / PI-5010, and some GoClever 4366 / 5066 FMBT units
• commonly mentioned archive password: igolas2010
• search also for:
  • YG-902M-FSJ-2G-4LS-5LS
  • YG-902M-ABFSJ-2G-AS-4LS-5LS
  • GoClever 5066 FMBT YG902M
  • Pioneer YG-902M MT3351 xip.nb0 gpsapp.msk

Old forum references indicate that for this board family the SD recovery normally uses files such as xip.nb0 and gpsapp.msk, sometimes together with files from a GPS+BT folder, and in some cases a final GPSTEST / gpstest.exe step is needed to reinstall or initialize the shell/menu. A GSMForum thread describes a very similar unit marked YG-902M-FSJ-2G-4LS-5LS, OS V1.1.0.10.01.15.2G and says the recovery was done with contents of GPS+BT plus gpsapp.msk and xip.nb0 from FW_MTK_YG2GB. (gsmforum.ru)

Most important warning: do not flash bootloader files unless the device is already a hard brick. Avoid writing files named like eboot.nb0, xldr_3351.nb0, metazone.bin, datazone.bin, etc. Forum repair notes for MTK navigation units repeatedly warn to flash without bootloaders/metazone/datazone when recovering a device that still shows a logo. (4pna.com)

---

Detailed problem analysis

Your symptom — device freezes on the startup screen — usually means:

• the primary bootloader/EBOOT is still alive;
• LCD initialization works;
• NAND is at least partly readable;
• the failure is likely in:
  • Windows CE OS image,
  • XIP/NK image,
  • ResidentFlash / ResidentFlash2 menu partition,
  • gpsapp.msk shell package,
  • corrupted registry or startup path.

So this is not necessarily a “dead bootloader” case. It is safer to start with SD-card OS/menu recovery, not with PC flash tools or test-point flashing.

The board marking is important:

Marking	Meaning / relevance
YG-902M	Mainboard family
MTK MT3351	MediaTek PND/GPS SoC
2G	Internal NAND/flash around 2 GB class; firmware must match this
ABFSJ / FSJ	Usually feature set: Bluetooth/FM/AV/shell variants, depending on vendor
4LS / 5LS / AS-5LS	LCD/panel/backlight/touch variant; wrong firmware may cause white screen, black screen, wrong touch, or inverted display
WinCE	Usually Windows CE 5.0/6.0 generation depending on build

The closest publicly indexed references I found are not for your exact OS build V1.1.0.10.04.10 2G / AP V1.3.01.10.05.05, but they are for the same board family and very similar hardware strings. One GSMForum case lists YG-902M-FSJ-2G-4LS-5LS with OS V1.1.0.10.01.15.2G, and a 4PNA archive references YG-902M-ABFSJ-2G-AS-4LS-5LS with similar “hang on splash/Launching image” symptoms. (gsmforum.ru)

Firmware package you should try to locate

The historically referenced package is:

FW_MTK_YG2GB.rar

A DonanımHaber archive specifically mentions this file for YG-902M/YG 2 GB MTK devices and states that a commonly used password for that archive was:

igolas2010

The same forum post warns that such firmware should be used for recovery, not as a casual update. (forum.donanimhaber.com)

A typical useful package may contain some of these files:

xip.nb0
gpsapp.msk
gpstest.exe
Update.exe
gpsupdate.pack
logo.nb0
logo.bmp

Some full flash-tool packages may also contain dangerous low-level files:

eboot.nb0
xldr_3351.nb0
xldr_3351.nb0.ind
metazone.bin
mt3351_datazone_bank0.bin
multi-scatter.txt

For your current symptom, do not copy or flash the low-level bootloader/metazone/datazone files unless you have a verified dump from the same board revision and LCD variant.

---

Current information and trends

The practical problem is that this device family is from roughly the 2010–2013 Chinese PND/GPS era, so many original links on Rapidshare, 4shared, Hotfile, DepositFiles, etc. are dead, gated, or mirrored inconsistently. The surviving information is mostly in old forum archives such as 4PNA, GSMForum, and DonanımHaber. Search results still show relevant indexed threads, but some attachments are hidden behind forum access or no longer downloadable. (gsmforum.ru)

The best current approach is therefore:

1. search by board string, not by front brand;
2. search by firmware archive name;
3. ask on legacy GPS repair forums for re-upload;
4. if you find a working identical unit, make a dump before experimenting;
5. avoid bootloader flashing unless absolutely required.

This is a common pattern with old MTK WinCE navigation units: the hardware was sold under many brands, while the actual firmware compatibility depends more on mainboard revision + NAND size + LCD panel + optional BT/FM/AV hardware than on the logo printed on the casing.

---

Practical guidelines

1. Prepare the SD card

Use the most conservative card possible:

• 512 MB, 1 GB, or 2 GB SD/microSD preferred;
• avoid high-capacity SDHC/SDXC cards if possible;
• format as:
  • FAT16 if the card is 2 GB or smaller, or
  • FAT32 if FAT16 is not accepted;
• allocation unit: try 16 KB or 32 KB;
• card label: preferably empty/no label;
• copy recovery files to the root directory, not into a folder, unless the package instructions explicitly say otherwise.

Old MTK bootloaders can be surprisingly sensitive to SD card type. A firmware may be correct but not start simply because the bootloader cannot read the card.

2. Minimal SD recovery set

For the YG-902M 2 GB family, start with a minimal recovery set such as:

/xip.nb0
/gpsapp.msk

If the archive includes a GPS+BT folder, follow the package convention. In the similar GSMForum case, the user copied the contents of the GPS+BT folder to the SD root and also added gpsapp.msk and xip.nb0 from FW_MTK_YG2GB. (gsmforum.ru)

Depending on the archive, you may also need:

/gpstest.exe

or a second-stage procedure where after the OS flash you erase the SD card and place only the GPSTEST file to initialize the shell/menu. This was also described in the similar GSMForum recovery sequence. (gsmforum.ru)

3. Files to avoid at first

Do not place these files on the SD card during first recovery attempts:

eboot.nb0
xldr_3351.nb0
xldr_3351.nb0.ind
metazone.bin
mt3351_datazone_bank0.bin
datazone.bin
multi-scatter.txt

Those are for low-level flashing. If the wrong EBOOT/XLDR/metazone is written, the unit can go from “stuck on logo” to:

• black screen,
• white screen,
• no logo,
• no SD recovery,
• only detectable as MT3351 USB VCOM,
• requiring test-point recovery or external NAND programming.

The 4PNA archive guidance for MTK firmware requests explicitly says to flash without EBOOT, METAZONE, DATAZONE to avoid unnecessary damage. (4pna.com)

4. Recovery procedure

1. Fully charge the device or connect it to a stable charger.
2. Insert the prepared SD card.
3. Press RESET.
4. Power on the device.
5. Watch for a blue/installer/update screen, or messages like:
   • Read image from SD card
   • Write image to NAND
   • Launching image
6. Do not disconnect power during NAND write.
7. After completion or reboot, remove the SD card to avoid an update loop.
8. If required, perform the second-stage GPSTEST step.

If the unit still freezes at “Launching image”, the OS may have loaded but the shell/menu package is wrong or missing. In that case, concentrate on gpsapp.msk, ResidentFlash2 contents, and the correct AP/menu version rather than repeatedly reflashing the OS.

5. If SD recovery is not detected

Try, in order:

• another smaller SD card;
• FAT16 instead of FAT32;
• different cluster size;
• rename the OS file if the bootloader expects another name.

One 4PNA archive entry mentions that for some YG-902M variants the bootloader expected an OS file name such as:

902M_SD_M4K.nb0

rather than simply xip.nb0. (4pna.com)

Other MTK/GoClever firmware discussions list many possible .nb0 names used by different bootloaders, so a name mismatch is a real possibility. (4pna.com)

However, do not randomly rename and flash bootloader files. Only rename the OS/XIP image when you are reasonably sure it is the image expected by the bootloader.

---

Supporting explanations and details

Why firmware compatibility is difficult here

Two devices can both say YG-902M and still require different firmware because of:

• LCD timing differences;
• backlight polarity;
• touch controller calibration;
• NAND geometry;
• SDRAM size;
• Bluetooth module type;
• FM transmitter/radio chip;
• AV input hardware;
• shell path stored in registry;
• different gpsapp.msk menu layout.

A wrong but “close” firmware may partially work: it may show the logo, write NAND, and then fail at Launching image, show a white screen, lose Bluetooth, or boot into a menu with non-working touch.

Recommended search strings

Use exact quoted searches:

"FW_MTK_YG2GB.rar"
"YG-902M-FSJ-2G-4LS-5LS"
"YG-902M-ABFSJ-2G-AS-5LS"
"YG-902M-ABFSJ-2G-AS-4LS-5LS"
"YG-902M V2.3 MT3351 2G"
"Pioneer PI5020 YG-902M"
"GoClever 5066 FMBT YG902M"
"xip.nb0 gpsapp.msk YG-902M"
"902M_SD_M4K.nb0"

If you register on repair forums, include in your request:

Mainboard: YG-902M-ABFSJ-2G-AS-5LS
Alternative marking: YG-902M-FSJ-2G-4LS-5LS
OS: V1.1.0.10.04.10 2G
AP: V1.3.01.10.05.05
CPU: MTK MT3351
Display: 4.3", likely 480x272
Features: Bluetooth, possibly FM/AV depending on board
Symptom: freezes on boot logo, SD recovery needed
Needed files: xip.nb0, gpsapp.msk, GPSTEST / SD recovery package

This exact information greatly improves the chance that someone with an old archive or dump can identify the right package.

---

Ethical and legal aspects

Firmware images for these devices may contain:

• copyrighted Windows CE components;
• proprietary OEM shell/menu files;
• licensed Bluetooth/FM stack components;
• navigation software launchers.

For that reason, I cannot provide pirated firmware files directly. The safest legal route is:

• use a firmware dump from your own device if available;
• obtain files from the device seller/manufacturer if possible;
• use forum re-uploads only for legitimate repair of your own hardware;
• avoid bundled commercial navigation software unless you own a license.

Technically, for repair you mainly need the bootable OS image and OEM shell, not necessarily any map/navigation application.

---

Possible disclaimers or additional notes

• Your OS/AP version is not exactly the same as the most visible archived cases. It is close enough to guide the search, but not enough to guarantee binary compatibility.
• If your unit shows a logo, do not start with test-point flashing.
• If after experimenting you get only a white screen or no logo, you may have flashed an incompatible boot/display configuration.
• If the device is detected by PC only as MT3351 USB VCOM, then it may require PndFlashTool/FlashTool + correct boot files + test point, but this is a higher-risk recovery path.
• Before writing anything low-level, make a NAND dump if the tool still allows reading.

---

Brief summary

Look for FW_MTK_YG2GB.rar, especially in old 4PNA, GSMForum, and DonanımHaber references. The commonly cited password is igolas2010. For your “stuck on startup logo” case, start with SD-card recovery using xip.nb0 and gpsapp.msk, possibly with the GPS+BT package contents and a later GPSTEST step. Use a small FAT/FAT16 SD card. Most importantly: do not flash eboot, xldr, metazone, or datazone files unless you are recovering a true hard brick with verified files for the same board/LCD variant.

Disclaimer: The responses provided by artificial intelligence (language model) may be inaccurate and misleading. Elektroda is not responsible for the accuracy, reliability, or completeness of the presented information. All responses should be verified by the user.