Is my X51V permanently bricked?

rspall · 08-13-09, 12:44 AM

Folk,

Just decided to take my trusty X51V out of mothballs...

Charged battery to full (green light) and decided to apply 'WM50_K_A17_AximX51v_WM5_M17EN.nb0' Custom A17 ROM.

Anyway, I put the DiAd_B_A01_X50v_WM5_ENG.nb0 and _K_A17_AximX51v_WM5_M17EN.nb0' on a freshly formatted SD card, and used WIFI+POWER+RESET to load. I first ran the Bootloader upgrade (selected from list) which finished quickly.

HOWEVER upon reboot WIFI+POWER+RESET to load the new A17 ROM the unit died!

Now it will not turn on (POWERalone), or hard reset (WIFI+POWER+RESET), or even run diagnostics (RECORD+POWER+RESET).

Is my unit permanently bricked? The power light is off regardless of whether there is a battery installed (and latch closed), and only lights up amber when on charge.

Is there anyway (e.g. pay someone in Toronto, Canada) to unbrick the device or is that the end of its life :-o ?

Should diagnostics (RECORD+POWER+RESET) always work even if the boot loader / ROM is screwed?

My cradle is lost but I do have a USB dongle, although I don't know if that helps?

I read stuff about the interal battery / capacity failing - could that be causing my problem?

Thanks in advance.

Roger

emeraldgirl08 · 08-13-09, 02:30 AM

Is that an X50v I see in the nB0 files???

I've never flashed before but shouldn't that be X51v???

johnhu_2005 · 08-13-09, 10:41 AM

Ouch, Emeraldgirl is correct, flashing the wrong ROM for the wrong device will generally brick your device.

What ROM did the x51v have previously before flashing (WM5 A04, WM5 A06, WM5 A12)?

The only error you did was flashing DiAd_B_A01_X50v_WM5_ENG.nb0. The _B_ indicates it is a bootloader file. Therefore, it is an x50v bootloader. That explains why you cannot access the bootloader via Power+WiFi+Reset.

The diagnostic is contained within the bootloader file, I believe. So the wrong bootloader file would cause both the bootloader and the diagnostic to stop working.
~~~~~~~~~~~~~~~~

I really don't have a solution for you because you flash the wrong bootloader. If you cannot access the bootloader, you have a paperweight.

Next time, please ask us for advice before flashing.

Ivan Awfulitch · 08-13-09, 10:53 AM

Contact PPCtechs. They can fix a bricked unit in many cases.

johnhu_2005 · 08-13-09, 10:54 AM

By switching motherboard that cost the same price as the device.

Zaniax · 08-13-09, 06:23 PM

What will happen if one tries again with the correct x51v bootloader.
Is that possible at all ?

Yeah, I'm a really n00b on this :o

rspall · 08-13-09, 07:36 PM

OK, fiest thanks for the help / suggestions...

Yes I accidentily replaced the boot loader with the wrong version! I have an X51V and I stupidly replaced the boot loader with the X50V boot loader - I didn't read the file name correctly and was in too much of a hurry!

I took the unit to PPCtechs in Fountain Valley (I am currently visiting in Cypress, CA) and after 30 minutes in their back room, they said it couldn't be recovered / reset! I don't know what techniques they tried, but they didn't open the unit?

It does seem stupid that only the boot loader can change / replace the boot loader, i.e. wouldn't it have been better to have a built in boot loader loader which can NEVER be replaced and is permanently burned into the unit? So I guess, once you screw the bootloader you are totally screwed.

I am not going to waste money on a replacement motherboard or replacement unit, it is just a shame to once again fill in some land fill which was once my pride an joy.

Are folk absolutely certain that their is no other way to burn the bootloader without the bootloader itself working?

I think I will be buying an Apple iPhone next week!

johnhu_2005 · 08-13-09, 07:44 PM

What is paradoxical is that you need a working bootloader to flash a new bootloader.

Interesting this reminds me of a PC I saw with a broken BIOS. A floppy/CD/USB drive could not be used to flash/repair the BIOS because they were not recognized.
~~~~~~~~~~~~~~~~

I looked over the posts on this thread again.
So I assume you loaded 4 files onto your SD card:

DiAd_B_A01_X50v_WM5_ENG.nb0
DiAd_B_A01_X50v_WM5_ENG_nb0.crc
WM50_K_A17_AximX51v_WM5_M17EN.nb0
WM50_K_A17_AximX51v_WM5_M17EN_nb0.crc

Then you selected "DiAd_B_A01_X50v_WM5_ENG.nb0" in the bootloader. Am I correct?

rspall · 08-13-09, 08:55 PM

Originally Posted by johnhu_2005

What is paradoxical is that you need a working bootloader to flash a new bootloader.

Interesting this reminds me of a PC I saw with a broken BIOS. A floppy/CD/USB drive could not be used to flash/repair the BIOS because they were not recognized.
~~~~~~~~~~~~~~~~

I looked over the posts on this thread again.
So I assume you loaded 4 files onto your SD card:

DiAd_B_A01_X50v_WM5_ENG.nb0
DiAd_B_A01_X50v_WM5_ENG_nb0.crc
WM50_K_A17_AximX51v_WM5_M17EN.nb0
WM50_K_A17_AximX51v_WM5_M17EN_nb0.crc

Then you selected "DiAd_B_A01_X50v_WM5_ENG.nb0" in the bootloader. Am I correct?

ALMOST...

My SD Card had:

DiAd_B_A01_X50v_WM5_ENG.nb0 - not there at fiest
DiAd_B_A01_X50v_WM5_ENG_nb0.crc - not there at fiest
WM50_K_A17_AximX51v_WM5_M17EN.nb0
WM50_K_A17_AximX51v_WM5_M17EN_nb0.crc
DiAd_K_A17_AximX51v_WM5_M17EN.nb0
DiAd_K_A17_AximX51v_WM5_M17EN_nb0.crc

I first SUCCESSFULLY installed 'DiAd_K_A17_AximX51v_WM5_M17EN.nb0' using the existing WM2003 boot loader. I rebooted, tried everything out and was happy, except the performance wasn't so good. SO...

I reasoned that I using WM5 / WM6 so I should really have the WM5 boot loader, which may make it run faster - weird logic I know.

Then I grabbed 'DiAd_B_A01_X50v_WM5_ENG.nb0' (not noticing the X50v!) and thought I would use it to update the boot loader.

I updated the bootloader successfully, and then it never restarted / rebooted ever again :-)

mkss55442 · 08-13-09, 08:57 PM

rspall,

Are you interested in selling it for parts? If so, what condition is the screen in?

Thanks,
Mark

rspall · 08-13-09, 09:09 PM

Originally Posted by mkss55442

rspall,

Are you interested in selling it for parts? If so, what condition is the screen in?

Thanks,
Mark

Everything is in pristine condition - always had screen protector and case.

Also has 2 extended batteries... I really miss my Axim :-)

I want to be absolutely certain there is no way of unbricking it first, and then it is over to ebay / craigslist!

JakeRich · 08-13-09, 10:38 PM

Did you look at this thread?

Recovering a bricked Axim.

May or may not help, but it's pretty complete.

johnhu_2005 · 08-13-09, 11:12 PM

Interesting.

WM50_K_A17_AximX51v_WM5_M17EN.nb0
WM50_K_A17_AximX51v_WM5_M17EN_nb0.crc
DiAd_K_A17_AximX51v_WM5_M17EN.nb0
DiAd_K_A17_AximX51v_WM5_M17EN_nb0.crc

DiAd is for WM2003SE bootloaders. WM50 is for WM5 bootloaders. So I guess when you have those four files on a SD card, you only saw DiAd_K_A17_AximX51v_WM5_M17EN.nb0 before flashing? (The WM50 files would not show under a WM2003 bootloader)

You are suppose to flash the bootloader before the OS. As the bootloader boots (

) the OS.

I am pretty darn certain you have a truly bricked Axim on your hands.

You can private message Steven for some assistance. But I am afraid he will probably give you the same answer as we have. I have him on IM so I will ask him the first chance he is on.

@JakeRich, the solutions found in Steven's post all require a working bootloader.

~~~~~~~~~~~~~~~
I apologize for the fragmented thoughts, I am thinking out loud.

rspall · 08-15-09, 10:46 AM

For the 'smarter' Axim owners (the ones that can read :-))...

1) What is the better CUSTOM (Unsupported by Dell) O/S?
- Windows Mobile 5 A17
- Windows Mobile 6

2) If answer to (1) is WM 6, then which version should X51V users use?

3) I proved that the WM2003 bootloader works with WM A15 (and I assume WM6 too), so what is the point of X51V boot loader for WM5?

4) Should the X51V boot loader ever be updated / changed from original, and if so in what situations?

Regards,

Roger

rspall · 08-15-09, 10:48 AM

Originally Posted by mkss55442

rspall,

Are you interested in selling it for parts? If so, what condition is the screen in?

Thanks,
Mark

The unit is in EXCELLENT condition... how much for parts :-)