Bricking...

[hifiasylum]

Hi.
I am a bit embarrassed about writing this, I never thought I would make a brick of my Prophet during “upgrades”...
But here I am, with a phone that don't want to sync with any computer after I accidentally pressed cancel on an active sync dialog box asking for setup with a new device, during upgrade to the latest Touch VIII. Have upgraded several times with several different ROM’s before, but this time things went wrong.
If I choose to start my device normally, it goes trough the HTC screen and stops after the Qtek (HTC in Norway) screen listing the different versions of the hardware…
When I restart to boot loader (Cam button + reset) the 3 colours turn up ok, but when I put an USB cable in the device and the lower, left part of the screen shows USB, active sync will not recognise any new device no matter what I do.
I can still find the Prophet when I go to properties on the computer, but somehow active sync does not care about that.

Are there any way to use a program at the host computer to sync properly with the Prophet?

I would really appreciate any help that could rectify this problem.

Regards, Lars Norway

[panda88]

I believe the " WM6 Upgrade Guide" thread has the info you needed.

[hifiasylum]

I believe the " WM6 Upgrade Guide" thread has the info you needed.

Tried the info there without success... :(
The guide assumes that you have connection with ActiveSync, but I can not seem to get connection.

So, I really need some advice about how to make a connection to the computer I will make the programming from, when ActiveSync is not working properly.

Have tried to restart both the device and the host computer, have reinstalled ActiveSync, have tried to start the different roms without having a connection to A.S., but no luck...

Have realized my mistake and bought a new Prophet, but would still like to get the old one working again. :)

[panda88]

it has nothing to do with activesync.

Not sure u really understand the below statement from the thread I mentioned.
RECOVERING FROM ERROR IN STEP 8 WM5->WM6
1. Don't panic
2. Don't panic
3. Unplug the phone
4. Reset with stylus,and keep the Camera Button pressed.
5. A 3 color screen will appear(Bootloader Screen)
6. Connect your device with your PC,and run the NVID(no vendor) WM5 rom.
7. The device will be resetted after RUU(rom update utility)finishes
8. Repeat the WM6 upgrade,from STEP 5..

in case you can't NVID roms, you can still use those step1 roms mentioned by ROM gurus here.

[hifiasylum]

6. Connect your device with your PC,and run the NVID(no vendor) WM5 rom.


Well, the problem is that I am not able to connect...
As far as I understand, the only way to connect is by using ActiveSync?
Regards

[panda88]

connect = the cable between prophet and your pc. after that just run the rom update utility. just dun bother the activesync (does it sound logical to u to establish activesync in bootloader mode?)

[hifiasylum]

OK, I have tried it, but will try on some different computers also.
Posting in a couple of hours. :)

Thanks for your help so far!

[panda88]

then wish u good luck. happy un-bricking. ;)

[hifiasylum]

OK, same as before.
Depending on which ROM I try, the following messages are the result:
Error [300]: Invalid update tool.
Error [274]: Connection (The update utillity cannot connect to your PDA phone.)

If I try the Touch VIII direct, it stops in Initializing for a while, and then a message appears with the text: Cannot connect to device, Would I like to try again?

Besides, in the welcome screen during the "ROMUpdateUtility_NV_G4.exe" in the Prophet_PV_Temp program, step nr. 2. asks me to ""Establish an ActiceSync connection with your PDA phone."

So, no change from yesterday yet... :(

[zeroed]

are you using windows vistA???

[hifiasylum]

Have only been using computer with XP Pro installed.
Anybody of the opinion that the connection tools built into Vista might do a better job?

[rondol1]

Have only been using computer with XP Pro installed.
Anybody of the opinion that the connection tools built into Vista might do a better job?

No, on the contrary. The best change you have is XP. Zeroed asked about Vista because it could be the reason of your troubles.

What I should do is just one detail different of what you have already tried:
Put the prophet in bootloader.
DISable "allow USB conection" in the conection-setting panel of ActiveSync
Connect your prophet with the USB cable
Run the NVID RUU again

If that is succesfull, you can upgrade to the WM6 ROM you like.

[hifiasylum]

OK, will do.
Tried Vista just now, same errors and no luck.
Be posting in a minute... :)

[hifiasylum]

OK, now I'm back.
Made a restart of the host computer, changed settings in ActiveSync, startet my device in Bootloader...
But unfortunately, no more success this time either.

Feel that the device must be more seriously defective/broken than others, this mishap happend at the end of the programming, when the 3 partitions were being written in the device. I was loading Touch VIII... :(

Anybody know if there is any more combination of buttons or reset methodes I could try?
Next step is to start opening the Prophet...:eek:

[rondol1]

OK, now I'm back.
Made a restart of the host computer, changed settings in ActiveSync, startet my device in Bootloader...
But unfortunately, no more success this time either.

Feel that the device must be more seriously defective/broken than others, this mishap happend at the end of the programming, when the 3 partitions were being written in the device. I was loading Touch VIII... :(

Anybody know if there is any more combination of buttons or reset methodes I could try?
Next step is to start opening the Prophet...:eek:

Sorry, I'm out of options...

[hifiasylum]

OK.
Thanks again for all help and support.
Really appreciated!
Regards, Lars

[kenxu]

OK.
Thanks again for all help and support.
Really appreciated!
Regards, Lars

Just wondering if your computer detects prophet as a device at all? Does the normal plug device sound comes on when you plug in? Just a long shot, stick in a SD card and try with windows media player to see if it can sync or put files onto SD card. if so, get rom refreshed via SD card...

try few hard resets before you try this.

[hifiasylum]

Not quite sure I understood what you suggested. I can get the device up in the host computers machine properties, but there is no way to get it up in any other program - like the Windows explorer.

Or are you saying that there is a way to boot the Prophet directly from a SD card? That would impress me!!! :)

[Stuclint]

Not quite sure I understood what you suggested. I can get the device up in the host computers machine properties, but there is no way to get it up in any other program - like the Windows explorer.

Or are you saying that there is a way to boot the Prophet directly from a SD card? That would impress me!!! :)

This sounds dumb, but try restarting your PC, closing all apps running in background (including firewalls), restarting Prophet (with stylus in reset hole). DO NOT TRY TO USE ACTIVE SYNC. Boot into bootloader (Three colours screen), connect USB cable and flash QTEK lastest official, or Jesterz AKU 3.3 (I have found this ROM to have magical powers of unbricking.)

Good luck!

[panda88]

OK.
Thanks again for all help and support.
Really appreciated!
Regards, Lars

Hmm this is wierd.I ran into problem earlier this month trying to flash a ROM but got stuck somewhere. So I followed the steps given in the sticky thread. Everything work smoothly. I am using XP SP2 and mine is a G3.

Let's make the assumption that your PDA is not faulty. Maybe you can try the steps again but this time :-
1. Change to another USB cable (or you may test the existing cable by connecting to a working pda)
2. Change to another USB port
3. Make sure you are not running any program that hogs the USB resource
4. If you are using USB hub, please don't connect using it. Make a direct connection to your computer.

that's all I can offer now...hope it helps.

[hifiasylum]

Hi guys. Thanks for the effort.
Great forum this!
I've tried what you have suggested, but no luck.
Now the Prophet is out of juice and I guess my tryin' is over until I get the new Prophet and have a chance to recharge the batteries in that. It seems that the charging function is lost with the devices OS?
Anyways, thanks a bundle for your help, and I will keep trying in about a week. (I'm currently out in the north sea, at work)
Regards, Lars ;)

[2241Alexanders]

Presumably you know it, but...
There are 2 hardware versions of Prophet, named G3 and G4.
For the wm5 upgrade tools it is important to choose the right one, wm6 flashing tools are 'universal'.
I see you used G4 upgrade tool, but maybe you have a G3 phone?
It may be worth it to try.

[hifiasylum]

Yes, I know.
My Prophet is a G4 version.
Have been using this WM 5 basic ROM 4 or 5 times, no problems.
What happened was that I accidentily pressed cancel in an ActiveSync dialoge box asking me if I wanted to create a new partnership with the new device at the end of the rom upgrade (Touch VIII)...
My hand was faster than my brain... :(

I guess my brain was stuck in some kind of screensaver-modus?

Anyways, I have another Prophet on its way home in a small week. Hopefully I can use time later to find a solution for unbricking the damaged Prophet.

Best regard, Lars

[systemrun]

Have you tried using another usb cable? Just a thought...
:confused:

[hifiasylum]

Hi Systemrun.
Thanks for yuor advice! Unfortunately I have tried 3 different cables that I know are working with other devices... :(

I am leaving for home tomorrow, will then try more things once I get my battery charged up again. Have the other Prophet waiting for me in the post. :D

Regards, Lars

[dholey]

before loosing ur heart .. do one more thing .... un-install active sync and re install it ... i hope u will thank me.....

[panda88]

Hi Lars, I have been thinking about your problems. The below is based on my imagination...so experts are free to comment or condemn...

It seems there is problem with the USB connection. Is there a way to run mtty utility and confirms the USB port is working? I supposed we need to enter some command to test the connectivity thru hyperterminal or something similar.

[hifiasylum]

before loosing ur heart .. do one more thing .... un-install active sync and re install it ... i hope u will thank me.....

Tried and not working I am afraid.

[hifiasylum]

Hi Lars, I have been thinking about your problems. The below is based on my imagination...so experts are free to comment or condemn...

It seems there is problem with the USB connection. Is there a way to run mtty utility and confirms the USB port is working? I supposed we need to enter some command to test the connectivity thru hyperterminal or something similar.

Actually, I think you have a point there. If by some way, I was able to connect the Prophet to the host computer without ActiceSync or if There was some way to make AS talk to the device, I think the problem might be solved. :)
I can find the device in the hardware properties, but AS doesn't care... :eek:

I am currently sending the Prophet to a friend with some background in electric and computers in quite a high level, maybe he'll be able to scare the Prophet shitless - and make it work?!?

We'll see. Will keep you posted.

Regards, Lars

[hifiasylum]

AT LAST, I finally got my Prophet working again !!!

But the way to do it was risky to say the least !
Here is what I did:
1. I connected the Prophet to the computer, and it was found in hardware properties in the host computer, but ActiveSync would still not recognise the device…
2. After trying allsorts of things to make the Prophet wake up again for almost a month, me and a friend thought; to hell with it, lets just try all things possible to make the damn thing alive again - or else it deserves to be a brick !!! :eek:
(We had still not tried the G3 version of the Step 1 ROM – this device is G4)
3. So while starting this Step 1 ROM (NVID(no vendor) AKU2.2 rom), we did reset the device (Bootloader while connected to the host computer with the USB cable) only seconds into the reprogramming process with the G3 version of this ROM. (That was the only thing we had not tried.)
And, yes, I know that this will surely brick the phone, but we were kind of frustrated… :mad:
AND it did not brick !!! :)
We have verified this trick one more time, and it really works.
4. When the AKU 2.2 ROM progress reaches 100%, things are back to normal and other ROM’s are possible upgrade paths again.

Anyway, thanks for all the helping replies I have gotten during this depressing times with my “Bricked” Prophet !!!

Regards, Lars :D

[2241Alexanders]

Glad to see you got rid of one brick.

Just for me to make sure:
You started to flash your G4 prophet with a G3 NVID WM5 rom, hard resetted during first flash, restarted flashing and that did the trick?

How could that be?

Tempting to add this knowledge in wiki, but I'm afraid that would result in more bricks than less ....

[hifiasylum]

Glad to see you got rid of one brick.

Just for me to make sure:
You started to flash your G4 prophet with a G3 NVID WM5 rom, hard resetted during first flash, restarted flashing and that did the trick?

How could that be?

Tempting to add this knowledge in wiki, but I'm afraid that would result in more bricks than less ....

This IS risky, would not recommend that the information is added to Wiki.
Maybe other Prophets cannot take being feeded the G3 version of the basic RUU?

Over to the method of flashing:
The whole problem with my bricked device was that ActiveSync would not recognice the device/would not
connect to it.
Therefor, while in bootloader, i started the G3 ROM and 1 second after the initialisation of the program, I SOFT-RESETTED the device.
The reason for this is that windows for a very short period of time starts to recognice the device.
That enables the ROM to "find" the device, even without ActiveSync.
(The G3 version of the basic ROM would start, the G4 version would not start... This was found out by chance.)

But again, I must point out that this G3 ROM programming was done with a high risk of peramently damaging my device. I, however, felt that I had nothing to loose...

After the softresetting, the ROM programming went on as normal and I could follow the "standard" procedures for upgrading.

OK?

Regards, Lars

[hifiasylum]

Oops, something happend here...
(No post intended.)