Please Help - 614c/612c is now Bricked and Stuck at SDLoader - Possible Solutions Pls

[David@]

Hello,

I did something stupid. I am hoping I can find a way to fix it without sending it back to HP.

I simply flashed the PDA using an incorrect file by copying it to my SD as a flash.dio and booting from it using the SDLoader. I thought if this happened I could still use the HP rom update utility while SDLoader is running, but it doesn't help!.

Now if I do a clean boot or even try to get into the SDLoader it just hangs and shows up but doesn't do anything.

when I have the PDA connected to my PC, my PC doesn't detect that there is a device there!

What could HP possibly do what I can't, do they have special software to bring it back to life or do they use hardware tools to flash it?

I have a strong feeling if I just knew what I am doing I could fix it. Could you please share some knowledge and possible solutions to resolve the problem

I really would like to avoid the cost of fixing it, I don't know how much it might cost as well

Thanks.

[lvfranz]

I have your's same issue.
I don't know what I can do.

[Zoltair Wright]

I have exactly the same problem and I think your 614c is good and bricked. I called HP for hours, talked to people on their support forums, you name it. Nothing worked. The best suggestion I got was "take out the battery for half an hour, then hard reset several times in a row." Didn't work for me, maybe it'll work for you, I hope it does.

If not, I have a pretty exact estimate (http://www.ipaqrepair.co.uk/view_product.php?product=1607) of how much it'll cost to fix. I'll let you know how it goes, I just shipped it to them this evening.

[David@]

Mine is under warranty and I am kind of playing dumb at the moment so I'll see if I'll end up paying or not :cool:.

I sent it today, I hope they get it fixed quickly, we'll see.

I'll explain what I did wrong so people can avoid dangers / stupid things, I only wanted to do it cuz I wanted to learn really thats it.

I extracted diskimage_Ver.nb0 from the PDA using the following:-

pdocread 0x0 0x5000000 diskimage_Ver.nb0

then I renamed diskimage_Ver.nb0 to flash.dio and copied it to SD, this flashed fine and nothing went wrong, so this is going to be my method to backup my rom and hopefully nothing goes wrong with this method in the futrue.

I also flashed successfully the rom Zoltair has posted eariler. and I plan to test the russian rom as soon as I get the PDA back.

However, this is what I did wrong, I also grabbed the follwoing file : Part02.raw using:-

pdocread -w -d TrueFFS -p Part02 0 0x4cbc000 Part02.raw

then I wanted to flash it by renaming Part02.raw to flash.dio (which now I know its not the same thing duh), I copied it to the SD, flashed it and that's when the end of the world happened to my PDA.

I just wanted to learn how I can flash back Part02.raw which remains an unanswered question, I mean what's the point of dumbing it if I cannot restore it.

I understand now that the bootloader is messed up and the only way to fix it is by HP re-programming the chip on the PDA. or using JTag thing which I have no clue how to do it myself.

The problem is the only way for me to learn is to brick my device couple of times but I wish I was able to fix this issue myself so I can keep on learning.

I'd like to ask kindly people who brick their devices to explain what they did exactly so others can avoid these situations in the future and also if anyone has found a method to fix a dead bootloader it would be nice to share his solutions.

Thanks

[NUTPDA]

Hi,

I faced the same problem two weeks back. Copied one of the file from the original HP upgrade package, rename it to flash.dio and tried to flash it via the SDloader (don't ask me why I did that). Bricked my 612 as a resulted :o.

Tried all means to recover but was unsuccessful. Brought it back to HP as my unit was under warranty. Upon collection, was told by the service staff that the ROM chip was corrupted and they gave me a new unit instead :) :D

[David@]

That's great, I don't have mine yet, I hope I get a new one as well. but that's weird, how come they didn't fix it? don't they have the tools to do so.

How long before you recieved your new unit?

Thanks

[NUTPDA]

That's great, I don't have mine yet, I hope I get a new one as well. but that's weird, how come they didn't fix it? don't they have the tools to do so.

How long before you recieved your new unit?

Thanks

Well, I was told that it was more cost effective to replace than to repair. I've waited for about 3-5 days for my replacement unit. I must say that HP's service is pretty good !

[alvatron2003]

hi, i was problem, but now is okay. please chek this, is the solution for mi. ihope help you.http://forum.xda-developers.com/showthread.php?t=459123
6xx, 9xx Stuck@Bootloader. Solition here
"Hi all.
I have 3 semi-brick iPaq device (612c, 614 and 912c). After do a ROM updrage from a bad miniSD card, these device onli show me HP logo when turn on. I'v search too many time and find a way to bring them back. @XDA-dev, I've saw someone have brick iPaq like me.

You need:
DNW (Include Driver file) http://www.mediafire.com/?zmnmzmwnjtk
Your device's Flash.DIO file. How to make a Flash.dio I'll post later. But you can found .DIO file via searching the web.

How to:

- Open DNW.exe, [Configuration] => [Option], change [Download Address] from 0xc000000 to 0x3000000
- Rename FLASH.DIO to FLASH.nb0
- Bring your Device too download mode: RECORD + OK + POWER or RECORD + OK + Reset to enter Download mode. Note: It's not Quanlcomm download.
- Plug your device to PC, and manually select driver to install (files are in SEC folder)
- Back to DNW.exe and [USB Port] => [UBOOT] => [UBOOT] and select Flash.nb0 just renamed and waitting for programed

I've done with these ipaq last week and return them to my customers. These Combine-key to enter download-mode can be wrong with 9xx device. I'll find another device to test later
This solution can change language of your device to language of .DIO fil "

[TheLastOne]

Not exactly sure why you ressurected an old topic when there's the solution just a few topics down.

[ral6387]

read this:
http://forum.xda-developers.com/showthread.php?t=459123