Develop Bugs

My grey screen says USB v2.07 I think I killed it!

My grey screen says USB v2.07. I tryed to update the radio to 1.13... I copied the EnterBl.exe over to the Siemens SX66 and executed it. It blinked and then turned off. Then it came back on and displays USB when on the cradel and Serial when removed. I cannot get it to do anything now. Does anyone have any advice?
Thanks,
Bobby
Cingular
Siemens SX 66 ( I have no idea how that translates into blue angel)

same here
if some one has a sulotion please send me instruction or a mail [email protected]
thnx

you are stuck in bootloader mode. just run the setup for rom upgrade/restore for your device and it should work. I think a hard reset will also allow it to reboot into normal mode, but not sure.

Defiant XDA
I cannot seem to get it to reset nor be recognized by the computer when it is placed in the cradle. It will chime as it is placed in the cradle, yet the charging light no longer ignites and the hot-sync program on my WinXP pc does not indicate that they are connected any more.
Thank you for your time!
Bobby

restore the original ROM. I had this issue after I run a defrag on my "Storage" folder using Storage Tools. I could not reset it. Also, upgrade with higher ROM did not work.
You have to restore / setup using original ROM version. Good luck!

Follow this link, download the update and follow through the instructions.
http://t-mobile.iris-global.com/download_manager_mda_3.html

original rom
Does any one has the original rom for the ph20b my son messed it up
\if any one can send it via email or a link will be helpfull
thnx

Another Possible Solution...
This has happened to me numerous times when upgrading to various ROM versions and through experimentation I finally realized that it was related to my storage card. I also remember reading another post like this where this problem can occur if the storage card is on the large side (>= 1GB ).
Just take out the card and reconnect to the cradle and you should be able to flash again.
Hope this helps

crashed/frozen. wont boot (FInixNOver) - cant reflash!

Hi guys.
I was using the installed the FInixNOver 3.0.1 ROM onto my SPV M700 and it was great. I've had it for about 2 weeks without any problems.
Last night I looked at my phone, only to realise that it was completley dead. This didnt shock me to much because the battery was running low, and i decided to let it die completley before recharging it again.
I charged my phone overnight and switched it on this morning, but the phone would freeze at the 'FInixNOver' splash screen (the numbers at the bottom of the screen would appear overlaying the splash, but the phone wouldnt go pass this point).
The only way to turn off the phone from this state is to eject the battery. I have tried removing the sim card, turning it back on in as many ways as possible but to no avail. I am able to get to the TriColor test screen (im running IPL-0.50 / SPL-1.30.Olipro) but with all the custom roms available, they all use the ROMUpdateUtility which requires the phone to have established an activesync connection initially (but this would mean my phone would have to be 'on completley' - so this is catch 22.)
For the record, my phone/battery died while my wired handsfree was attached (dunno if thats of any interest to anyone or the rom baker).
But it looks like the only way i'll be able to flash my phone is by finding a way to install the .nbh file without using the RUU method. Because I can put my phone into test mode manually.... any help or guidence would be very much appriciated.
Thanks.

Ok can you get it into bootloader? power/camera buttons and reset?
sorry didnt read fully.
right get your device into bootloader first,
then open active sync (are you using xp)
then open connection settings and disable usb connection,
put your device into bootloader mode, then run any rom upgrade, i prefer the WM6.1 pdaviets from HERE (Username: PDAVIET / Password: pdaviet)

Your pda does not need active sync with ruu's, so no catch 22. if you turn off usb connection in active sync, you can still run ruu and it will be recognised, unless you are using vista, where you need to change your HTC SYNC drivers.

Thanks for your quick response...
Yes I can get into boot loader using the power and camera buttons (or holding the power and camera buttons when resetting the phone)...
When the phone is in boot loader mode, active sync doesnt even detect the phone anyway, but nevertheless, I have followed your instructions and disabled the USB Connection. (BTW, yes i am using XP)
The phone is still in boot loader mode, so now i try and execute the ROMUpdateUtility.exe and go through the steps, at the 1st step i tick the tickbox and click next, and the 2nd step i tick the tickbox and click next. (this step says DO NOT enter the bootloader manually? - but i have havent i?) anyway, when i click next, it says... "Verifying the information on your Trinity... Please Wait..." for about 10 seconds, and then i get a message "ERROR [260] : CONNECTION"
What am i doing wrong?

Huumm.. why dont you flash your phone throw the sd card??
Read this link:
http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing

try to flash your phone with some official rom and after that flash it with any other you want!

manos_23 said:
try to flash your phone with some official rom and after that flash it with any other you want!
Click to expand...
Click to collapse
I would recommend this option above, to be safe, i usually get them error messages when the battery is below 50% or sometimes i try it again and it works. it does state do not manually enter bootloader but i always do it this way.

also make sure active sync is not still running in taskmanager under the alais: wcescomm.exe and WCESMGR.exe, end them both.

I've just tried using an official ROM, but the problem still occurs with the 'connecting'. It doesnt seem that the computer picks up a connection to the phone whatsoever.
Should i be concerned that at the bottom of the bootloader screen it says "serial", is this correct?
Im starting to get annoyed now.

Bye,
the bottom of the sreen mast say "usb" not serial.

it seems there is a problem, if it states serial. as it should say usb. try THIS

Seems like the problem was that my USB lead was loose and made a bad connection, hence why the bootloader showed 'serial' and not 'usb'... as soon as i wiggled it and heard the 'connection noise' in windows, i knew i was good to go, and so using the RUU worked fine to reupdate my phones ROM.
Thanks for your help.
My only question is that why did it happen in the first plave?

WIZZKID - I just saw your post here now. I have to tell you that I also saw "SERIAL" at the bottom of the bootloader screen and not "USB". As I said I returned it to get another phone but maybe I will try something else for now instead of a P3600i. I will monitor your thread to see how it turns out for your phone, because it seems that we have the same problem.

if you see "serial" instead "usb" your problem is in the usb cable, usb port from your computer or in the usb connector from your trinity!!!!!
I was having the same problem that you have!! my problem was from my usb from mine trinity!! see if the conector is at good conditions !!!

Well as some of you may know, I got my Trinity replaced for sticking at the WM splash screen after a few days. This second one - I have had it ONE night - and the same thing has happened with incomplete booting. This time I have been trying all night to flash the phone to an official ROM, but I cannot do it (apparently) because I can't establish a connection via ActiveSync. When I stick the data cable in while in bootloader I see SERIAL replaced by USB and when I try the flash I get a "270" error (cannot connect to phone) and the phone re-boots to the sticking plash screen. What should I do now?

ladies and gentlemen...
we've got a lot of mixed messages in this thread.. please make sure you're posting the right thing. no need to disable USB when manually going in to bootloader to flash (at least in xp).. Also, you can ignore the part of the RUU that says 'do not manually enter bootloader' (you should really read the guide on my site)
foxuniform- can you please give some details..
1) are you running xp or vista
2) have you flashed hard-spl? if so what version?
in the mean time, try a couple of things.. first, flash hard-spl (even if you already have it, but from the sound of it i think you don't have it on your device).. if that works, try to flash an official ROM. Can also try to use splxploit, then flash hard-spl, and then flash official ROM (there's a guide on my site if you're unsure)
please post your results
*edit*
here are the steps for SD card upgrade, but i HIGHLY recommend flashing Hard-spl first..
try to do it from SD card. how?
Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract (http://www.cabextract.org.uk/) .
Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
With miniSD card inserted on the phone, start the bootloader (hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom).
You should see the screen pictured on the left, confirm flashing on screen by pressing the power button.
Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
When flashing completes soft-reset your device.
Make sure your SD has FAT32 and has no label. There have been reports that if SD has a label the bootloader can not access the TRINIMG.nbh

racerx_ I have carefully read your response and suggestions, and thanks for your expertise input on the matter. I am fairly new to this stuff so read below carefully as you may find errors in the way I tried to go about doing what I was hoping to accomplish.
First let me answer your questions. I am running Windows XP. The phone is in it's completely natural state in that I have not flashed it in any way. The ROM I was TRYING to flash to the phone while it was not starting properly (this is where I manually entered bootloader) is an official ROM from the HTC website (please note everyone that when I registered my P3600i on the HTC website it came up as the Dopod 810). Anyway, that never worked. ActiveSync never detected the phone (and I guess that's the reason I could not do anything as far as flashing goes). I HARD-RESET my P3600i and it booted normally. I re-installed all the stuff I had on it, from memory card to various .cab files, and the phone is working beautifully thus far. I will report if anything funny happens again.
I have to ask you racerx_, if I CAN flash hard-SPL on the P3600i according to the lovely guide on www.trinityguides.info. I have been of the opinion that things don't work for the P3600i as they did for the P3600, and that has been echoed by many P3600i users on this forum who are ready and waiting to try out some cooked ROMs (myself included).
For the sake of record, my phone is running rom version 3.00.707.17 and radio version 1.46.00.11. I patiently await your response.

woaaahhh..
i didn't notice the 'i' in your previous post... yeah, as far as i know, these ROMs are not flashable on your p3600i.. sorry..
**correct me if i'm wrong somebody**

Yeah I kinda thought that would be your response. By the way - do you think that this phenomenon of sticking at the Windows Mobile splash screen (both the P3600 and P3600i models apparently) has anything to do with something users do with the devices, or you figure it's an inherent software glitch of some sort? I am wondering if I should try a different model or hold on to my P3600i? Hope it's not something that'll happen again - I fly for a living and it's not gonna be good to have the thing screw up on me away from base - I really count on it for everything from casual keeping in touch on Messenger to viewing my work schedule. I love the Trinity though - it's one of my all-time favourite HTC phones.

hmm... i don't think its inherent in the Trinity.. (not a hardware issue.. in my opinion)
its been a while since i followed the posts on it, but always seems to be software related.. sometimes ROM-specific problem. Personally, i've probably flashed as many ROMs as anyone and the only time i ever encountered problems was with the official HTC WM6 ha.. go figure.. I think ppl did find that hard resets before and after flashing are helpful as well..
i love my trinity, and there's not much else on the market to make me want to trade it in (is it just me, or have pda's kind of stopped getting cooler).. i'd stick with it..

Aarrgghhh Help Error 260 When Flashing

Help please
i have a t-mobile uk mda compact 3 phone nd im on t-mobile uk tariff, i have downloaded the official t-mobile uk windows mobile 6 rom.
when i atcive sync and go to flash the new rom i get the utility program up, the phone turns different colours ie red, green blue with black strips, the bar then shows on the pda on the pc screen it gets to 3% and bang invaild error 260 and the phone then resets
ive tried it on xp as im on vista same thinf happens, ive tried uspl, no joy can someone tell me how to get thos rom flashed to the phone in vista a easy step by step procedure to follow cause so far ive lost 8 hours since sunday to tonight
please help.............

SD card removed?
remove your SD card

USB board
you may have been not so carefully with the USB connection contact of the phone, or you ahve charged the phone at car while you were starting the car engine..some guys repaired this in service, or it passes by itself.
at me i tried different days and different softs ... and i did i, i got the same error.

fun0815 said:
remove your SD card
Click to expand...
Click to collapse
Hi i have removed SD Card, tried it without, with also with and without sim card still no joy i need step by step help on this

pskint said:
you may have been not so carefully with the USB connection contact of the phone, or you ahve charged the phone at car while you were starting the car engine..some guys repaired this in service, or it passes by itself.
at me i tried different days and different softs ... and i did i, i got the same error.
Click to expand...
Click to collapse
The phone usb connector is fine, i dont charged the phone in a car as i dont own a car
so what is ther soultion there is nothing wrong with the phone or the connector as it connects up via usb and uses active sync also installing other software and transferring pictures, music to and from it also work fine!
i can see both the phones memory and sc card in my computer.
its just this bloody rom file and error 206 that i am still needing someones expert advise and step by step help on

Please Please Please Please Heeellpp Aargggh Part 2
CAN someone please help me out and to whoever has managed to upgrade using vista!!!!!!
please help

After searching this forum, this came up:
http://forum.xda-developers.com/showthread.php?t=312052
Title: USPL - 100% Working in vista
step 7 says:
7. After switching the drivers plug your artemis again and install USPL, there should be no more problems with connection lost (errors 260, 270)​
Suggest you read that thread, hopefully it solves your problem.

[TUT] Unbricking your Excalibur

Everything you ever needed to know about "unbricking" your Excalibur but were afraid to ask is in this guide. I've put together this guide for those of you who either intentionally or unintentionally "bricked" or think you've "bricked" your Excalibur.
It is not easy to brick an Excalibur if you actually read and follow all of the steps and guidelines before a flash. In fact, not many things can go wrong unless a USB cables disconnects during a flash, your PC crashes in the middle of a flash, or you flash a corrupt image file to your device. Statistically, most of the time people only think their Excalibur is "bricked" when actually it's not.
There are three methods you can use depending of the severity of the "bricking". The first method will unbrick 50% of all Excalibur's that have simply "locked up" and won't reboot properly. The second method will unbrick 95% of all Excalibur's that encountered flashing problems or flash failures. The third and final method, and the most involved, is a "last resort" for those who have tried method's one and two numerous times unsuccessfully.
** Please perform these steps and methods at your own risk. I am not responsible for any damage you cause your device using this guide.
If you're new to the Excalibur or SmartPhones in general, please take the time to read the WiKi and this post by Stylez for valuable info before you post or try any of these steps.
http://forum.xda-developers.com/showthread.php?t=397583
http://forum.xda-developers.com/showthread.php?t=537151
But, before I even get into unbricking, if your phone is in fact working right now, I highly recommend you flash HardSPL to avoid even having to follow these steps anytime in the future. The steps and info for HardSPL and JumpSPL can be found in this thread by jockyw2001:
http://forum.xda-developers.com/showthread.php?t=329605
HardSPL basically flashes your phone with an "unlocked" security partition so all security checks are bypassed when you try to flash a cooked ROM or a ROM designed for another variation of the Excalibur such as Dopod, HTC, TMO Dash, etc. Makes life much easier when trying different ROMS or cooking and testing your own! Thanks jockyw2001!!
Ok, so onto the fun stuff... Your phone won't boot... Either it's locked up and simply stopped booting or you flashed your phone and it won't boot. What do you do??
Method 1: Assuming you didn't get "bricked" from a flash problem, the first and easiest method for "unbricking" your Excalibur is (this will erase ALL data in your Excalibur):
(This method works for 50% of supposedly "bricked" Excaliburs)
Remove your SIM and SD card
Remove and reinsert your battery
While holding the two softkeys with your thumbs, press the power button
Continue holding the softkeys until a black screen appears saying "This operation will delete all your..."
Press "'send"' to restore to hard reset your phone
Let the phone cold boot and restore
That didn't work!! . This next method will reflash your phone to the factory ROM.
Method 2: Second way to the path of unbricking is:
(This method will unbrick 95% of all Excaliburs)
Get a hold of your Shipped ROM. You can find these ROMS either in Dopod's site, HTC's site (with a valid serial #), TMO's site (http://www.t-mobile.com/wmupgrade/ with a valid IMEI), or right here at XDA at this post (http://forum.xda-developers.com/showthread.php?t=381726)
Download one of these factory ROMS and unpack it. **Remember, if your phone is a TMO Dash, you MUST use a TMO Dash ROM. If your phone is HTC Branded, you MUST use an HTC ROM, etc., etc., etc...
Remove the SD card if one is inserted in the phone
Remove the battery from your phone for a few seconds. I found this step to be essential to reset the device. Put the battery back in.
While holding the camera button on the right side, press the power button. The phone will enter "bootloader" mode and you will see a tricolor bootscreen.
While in this mode, plug in your USB cable and you will hear the "ba-bing" USB sounds as the device connects
Unpack the ROM package you just downloaded and run RomUpdateUtility.exe. Follow the steps, check the appropriate boxes, and start the flash
Assuming all goes well, your phone will flash to the factory ROM and you can then troubleshoot what went wrong the first time that bricked your phone.
Oh no!! That still didn't work!? Or it worked but the flash failed with Error 270 or another error......... Never fear!! XDA-Developers is here! This next method is a bit more intense. It creates a "goldcard" which is used to SuperCID the Excalibur so that it doesn't care about what factory ROM you flash. Please have the factory (not a cooked) ROM ready to go.
** (This method is not intended for Newbie's and some enhanced knowledge of HTC devices and Windows is required to successfully work.)
** (Retry the second method several times with a few different factory ROMS before attemting the below)
Method 3: The third "goldcard" method is a bit more intensive and should be used as a "last resort" so follow closely:
(should unbrick ANY bricked Excalibur if performed correctly)
Get a cup of coffee or tea
You will need a working Donor HTC device with a microSD slot and a microSD card that is smaller than 1GB (will be formatted) to create "goldcard" image using QMAT tools as described below
You will need QMAT. Get it from http://revskills.de/index.html.
Go to the Download link and download the latest version and unpack QMAT
Have some coffee
Use a SD card reader (either USB for microSD adapter) in your PC to access the SD card through Windows. Format the SD card with FAT32.
* Insert the SD card into the donor HTC device and boot up the device. Connect the USB cable and establish an Activesync connection.
Open QMAT and go to the "Hardware Forensics" menu and select "Generate HTC Goldcard"
In "Select device key:" select the Excalibur
You will need the serial number fro the inserted SD card so click the "Get SD Card Serial from WINCE Device" button
Once the Serial number appears in the box, click the "Save Goldcard Image to WINCE SD" button below
If no errors pop up and all goes well, skip the next step
If you get an error or a popup saying "Goldcard for newer devices isn't implemented in newer devices", you must buy and register the software. Believe me, it's worth the small amount of $ you will spend to bring your expensive device back to life!
Now remove the SD card with the newly written Goldcard image from the Donor HTC device
Insert the SD card back into your PC using the microSD card reader adapter. Browse to the drive letter assigned to it. You will see no files on the SD card, this is normal.
(If, for some reason your PC sees the SD card as unformatted, something went wrong. Remove it and reinsert it into the Donor HTC device. The device should see the card as unformatted and ask you to format it, say yes. Now go back to the "* Insert the SD card into the donor HTC device" step above and repeat the steps)
Unpack your Dopod or other factory ROM and copy RUU_Signed.nbh to the SD card. Once it had finished copying, rename the file to EXCAIMG.nbh. Remove the SD card from the PC.
Make sure the Excalibur is off and insert the SD card
Enter bootloader mode as mentioned earlier (hold the camera button while pressing the power button). No need to connect the USB cable.
You will see a gray screen that says "loading". It will then find the EXCAIMG.nbh file and ask if you would like to start the update process. Follow the instructions and let the phone flash.
It will take 10-15 mins but your phone should boot fine and be back in action!
QMAT is a VERY powerful tool written by viperbjk that allows for full low level manipulation of HTC and WINCE tasks. Read all about it here http://revskills.de/index.html.
Many thanks to jockyw2001 for his amazing HTC device knowledge! Also thanks to all who contributed to this post.
Hope this tutorial helps!

Updates and more info will be here.

What if the phone will not enter bootloader mode?
ookba said:
Updates and more info will be here.
Click to expand...
Click to collapse
Hi OOkba,
This happened to a friend in the office's Dash. It simply froze up while operating. I actually got on the phone with HTC support. We couldn't get it to do anything. It does power up but then freezes.
The HTC guy was of the opinion that it is hardware related.
You ever solved that one?
BTW - I am running the 7.18 6.5 - love it - thank you so much

all steamed out said:
Hi OOkba,
This happened to a friend in the office's Dash. It simply froze up while operating. I actually got on the phone with HTC support. We couldn't get it to do anything. It does power up but then freezes.
The HTC guy was of the opinion that it is hardware related.
You ever solved that one?
BTW - I am running the 7.18 6.5 - love it - thank you so much
Click to expand...
Click to collapse
Thanks, glad you like it. Try this guide for your friend. Sounds like an easy fix unless it is indeed hardware related.

HI OOKBA. I can't find my shipped rom. I have a HTC Excalibur from Digitel, Venezuela. The serial number is SZ702FJ05879. I try all roms and not working. Please, help me. (sorry my bad english)

thank. I formated SD card and insert SD card in to my phone.But Do I need turn on my phone when connect with computer? because when I run QMAT software is error. " could not open connection? Device connected?". Help me. I need help from you

mydreamisrich said:
thank. I formated SD card and insert SD card in to my phone.But Do I need turn on my phone when connect with computer? because when I run QMAT software is error. " could not open connection? Device connected?". Help me. I need help from you
Click to expand...
Click to collapse
Yes, you have to have a spare working phone to create a "goldcard". The phone must be powered on and sync'd via USB so QMAT can access the storage card.

alfatech said:
HI OOKBA. I can't find my shipped rom. I have a HTC Excalibur from Digitel, Venezuela. The serial number is SZ702FJ05879. I try all roms and not working. Please, help me. (sorry my bad english)
Click to expand...
Click to collapse
English is good!! Who is your Carrier? Maybe your carrier has a ROM UPdate on their website? You should be able to use the TMO or Brightpoint ROM. You tried all the factory ROMS and they fail to flash?

ookba said:
Yes, you have to have a spare working phone to create a "goldcard". The phone must be powered on and sync'd via USB so QMAT can access the storage card.
Click to expand...
Click to collapse
I tried turn on my phone. And connect computer by USB but the same error. QMAT can't access the storage card. What does I do?

Sup ookba!
I really want to flash my TMobile Dash using your rom, looks pretty cool but I'm deadly afraid of bricking my phone so first, I took a look on my System Info and it says
ROM Version: 1.33.422.1 (tho its a TMobile Dash, I think the seller flashed it with this international rom).
Model Name: HTC S621
So I got 3 questions
1) Can i flash 3VO rom on this phone?
2) If the flashing fails, can i just use another 1.33.422.1 ROM and reflash it?
3) Will the flashing process (both ways) will bring the SIM Lock back?
Greetings from Brazil and sorry about my glass-cracking, horrible and ultra-bad english.

aletkd said:
Sup ookba!
I really want to flash my TMobile Dash using your rom, looks pretty cool but I'm deadly afraid of bricking my phone so first, I took a look on my System Info and it says
ROM Version: 1.33.422.1 (tho its a TMobile Dash, I think the seller flashed it with this international rom).
Model Name: HTC S621
So I got 3 questions
1) Can i flash 3VO rom on this phone?
2) If the flashing fails, can i just use another 1.33.422.1 ROM and reflash it?
3) Will the flashing process (both ways) will bring the SIM Lock back?
Greetings from Brazil and sorry about my glass-cracking, horrible and ultra-bad english.
Click to expand...
Click to collapse
Yes, your phone is fine. Make sure you follow all of the flashing instructions. Make sure you remove your SD card, connect your phone, run SDA Application Unlock, and run auto.bat from the update package.

mydreamisrich said:
I tried turn on my phone. And connect computer by USB but the same error. QMAT can't access the storage card. What does I do?
Click to expand...
Click to collapse
I dont know what you're doing wrong. Sounds like you're not establishing an Activesync connection properly.

Ok, Ookba. My carrier is DIGITEL and don't have support in the website. The phone comes originally with WM5 in spanish. I try all the factory roms and not working. Please, tell me if there is any solution or I forget the phone.
Thank you any help.

alfatech said:
Ok, Ookba. My carrier is DIGITEL and don't have support in the website. The phone comes originally with WM5 in spanish. I try all the factory roms and not working. Please, tell me if there is any solution or I forget the phone.
Thank you any help.
Click to expand...
Click to collapse
Try the "Goldcard"' method. This should SuperCID your phone and allow you to flash ANY shipped factory ROM. Please follow the tutorial closely. You will need a spare phone with a microSD slot.

Ok, Ookba. But the spare phone must be a same model than mine? (HTC S620)

alfatech said:
Ok, Ookba. But the spare phone must be a same model than mine? (HTC S620)
Click to expand...
Click to collapse
No, just has to Windows Mobile based and have a SDHC slot.

OK. I try with 3rd method and when run Qmat and select "Get SD Card serial from WINCE Device" appears the message "You need to set rigth registry permissions. See QMAT manual for more info." and not recognizes the sd card.
What is the problem?

Thanks, Ookba. You're great, man. Finally someone offers solutions to my problem. Thank you very much. My Phone came back to life again. I make a donation soon.

alfatech said:
Thanks, Ookba. You're great, man. Finally someone offers solutions to my problem. Thank you very much. My Phone came back to life again. I make a donation soon.
Click to expand...
Click to collapse
GREAT!!!!! Congratulations!

I tried but when I click Get SD Card Serial from WINCE Device in the box none found and click Save Goldcard Image to WINCE SD is card ID isn't 16 bit (32 charter) long. I isn't succesful. help me???????

What do you do if the unlocker errors half-way through?

I actually have a new phone coming today because I had no idea what to do and when I called neither did Verizon.
I seen the GPS fix thread, downloaded all the necessary files, ran the first unlocker (.40) and it errored half-way through the process, I figured big deal I'll just run it again..
Well, my USB would show on the phone screen but in the bootload mode the unlocker programs couldnt detect my phone at all and I couldn't get out of bootload mode whether I hit soft reset or took out the battery. So I decided to try going ahead an upgrading, I tried the next step on the list (sprint rom) but the upgrade would error as well, then I tried the verizon one, error, and the just tried jumping back to the NFSFan ROM and it didn't even begin to error it said it wasn't allowed or something.
Anyways, I had no idea what to do... took it in to the store, they looked at it for awhile then told me to call a number, I tried the number and they attempted to wipe it from their side and couldnt do anything so they told me they'd send another one being I was still in my 1-year warranty.
Is this how you brick a phone? Having an error during an unlocker/upgrade? Or could I have fixed this if I asked here before I sent for a new 1? I don't mind because I'm hype for a brand new phone, I just wonder if it can be fixed incase this ever happens again.

next time use coke 2.31

vin255764 said:
next time use coke 2.31
Click to expand...
Click to collapse
to do the gpsfix you have to use coke .40, its not like its some old outdated thing the thread is from august everybodys been using it, all i want to know is if theres no return once an error occurs in the middle of an unlocker?

j18yo said:
to do the gpsfix you have to use coke .40, its not like its some old outdated thing the thread is from august everybodys been using it, all i want to know is if theres no return once an error occurs in the middle of an unlocker?
Click to expand...
Click to collapse
There is a fix
what is showing on the bootloader screen for the unlocker?
Also you may want to reflash a shipped ROM. I have had this happen on both Titans and Vogues and reflashing from the bootloader screen always solves the problem.

I'm assuming you have to flash via the SD card right? Because I tried doing it through the USB and all the ROMs would error because the unlocker never fully finished, I mean before all this my phone was unlocked by the 2.31 and I had the newest NFSFan running I just decided to go back for the GPSFix..
The bootloader screen wasn't froze, it showed the usual..
Upper right corner says "RUUNBH"
Then to the left top it says..
VOGU100
SPL-0.36.0000
CPLD-3
and Serial at the bottom until I put the USB in and it turns to USB.. but it doesn't get picked up by the unlocker if I try to re-run it

I guess I answered my own question.. to fix it I'd have to run the unlocker again from the SD Card so it finish's without error since the USB won't pick up right?
My problem is I've never ran anything from the SD card.. if anyone can tell me how you go about loading up an unlocker or ROM from bootload on the SD I'd appreciate it, this way when I get my new phone if I run into a similar problem I can fix it

j18yo said:
I'm assuming you have to flash via the SD card right? Because I tried doing it through the USB and all the ROMs would error because the unlocker never fully finished, I mean before all this my phone was unlocked by the 2.31 and I had the newest NFSFan running I just decided to go back for the GPSFix..
The bootloader screen wasn't froze, it showed the usual..
Upper right corner says "RUUNBH"
Then to the left top it says..
VOGU100
SPL-0.36.0000
CPLD-3
and Serial at the bottom until I put the USB in and it turns to USB.. but it doesn't get picked up by the unlocker if I try to re-run it
Click to expand...
Click to collapse
Try installing this driver on your XP computer http://www.4shared.com/file/101893703/a59b72a/WindowsHTCdrivers.html if you have Vista let me know and I'll give you a link fvor that one. It should then allow you to communicate via USB. Also to answer your next question on flashing from the SD. It is simple you copy the NBH file from a ROM to Root directory of a FAT32 card 2 gb or less. Rename the file to VOGUIMG.nbh place the card into PPC and place into bootloader mode. Then follow the instructions.

j18yo said:
I guess I answered my own question.. to fix it I'd have to run the unlocker again from the SD Card so it finish's without error since the USB won't pick up right?
My problem is I've never ran anything from the SD card.. if anyone can tell me how you go about loading up an unlocker or ROM from bootload on the SD I'd appreciate it, this way when I get my new phone if I run into a similar problem I can fix it
Click to expand...
Click to collapse
All you do is put the .nbh file on the root directory of the memory card(use a newly formatted/clean card). It may delete anything else on the card while flashing.
I would take out the battery. Put in the SD card then turn the phone on. If, like you say, you are stuck in bootloader mode then it should start flashing as soon as it powers up.

Thanks everyone, I received my new phone this was mainly incase it happened again, but I also figured out why I ran into my problem..
During the unlocker I thought I knew the process being I'd done it multiple times, I skipped the part where I unplug the phone from USB and plug it back in so it's no longer connected with ActiveSync... thats why my unlocker error'd, so make sure you don't do that lol
What was messed up is my computers been acting like a piece of ****, it wouldnt even read my SD card so that I could put a file on it, but I don't think I'd wanna do it that way I have all my stuff on my SD card if it erased it I'd have been pissed..
ActiveSync does work, for awhile I thought the USB was only charging my phone because my new one wouldnt pick-up ActiveSync.. no idea why.. but if I plug it in and wait around 10 minutes it finally connects.