Develop Bugs

[SOLVED] No Boot, no ADB, no Recovery, only fastboot :( How to create a Goldcard now?

I'm stuck at a nearly 99% brick I think...
I've got an AMOLED Desire from T-Mobile Germany (still branded), with HBOOT 0.80.0000, rooted via Unrevoked and still S-ON.
The phone gets stuck during the boot process when the provider-splashscreen (or HTC-Logo) is shown at the beginning. Only pulling out the battery will shut the phone down.
The same happens when I try to get into Recovery via HBOOT. The only option is to pull the battery.
If I connect the phone via USB and enter Fastboot it is recognized by the computer with the command "fastboot devices".
I can't use ADB, because I can't access the recovery.
I downloaded the right RUU for my provider/amoled/hboot 0.80.0000 Desire (RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed) and extracted the ROM.zip from the installer. I renamed the file to PB99IMG.zip and manually moved it to the SDcard using my computer.
But, when I enter HBOOT the file is recognized and extracted, but then it fails ...due to an "incorrect CID".
The same happens if I manually execute the RUU....exe under Windows with my phone plugged in via USB. (It's error code 131 in the flash program of the RUU....exe).
A very helpful user (cargo) of a german Android forum (www.android-hilfe.de - link to his posting) assumed that my HBOOT is not correctly displayed and I might have a "newer" one than 0.80.0000
This leaves me quite without any option than to flash HTC RUU 2.29.405.5, which brings HBOOT 0.93.0001...(but I may be able to downgrade again.)
But this flash process is only possible if I have a Goldcard, which I actually don't have at the moment
Is there any way to create a Goldcard for my device in my actual position (only fastboot working, no boot to run the system, no adb working, no recovery access)?
Every howto explaining the goldcard crating process requires either working adb or even a running system for apps like "goldcard helper" or being able to use "terminal emulator"
I would be very very thankful for every bit of help
Maybe there is some way
Thanks in advance guys!

I believe that goldcards are specific to the card and not the phone(read it somewere on here) so it should be possible to make one without using your phone.
Sent from my HTC Desire using XDA App

TheGhost1233 said:
I believe that goldcards are specific to the card and not the phone(read it somewere on here) so it should be possible to make one without using your phone.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
As far as I know you need the phone for your goldcard. At least it was said in the tutorial I was following a few months back. You need to connect the phone to get the serial number (through ADB shell) which you will need to hex-reverse and put it on your SD card image.
To be honest, they are more sophisticated methods now (as I read) creating a goldcard, but since unrEVOked, i do not follow that part.
And by the way, why don't you flash the HTC RUU 2.29.405.5? 0.93 HBOOT can be downgraded. But with the latest tools you can S-Off, root & whatever with that HBOOT, too.

I just tried flashing the HTC RUU 2.29.405.5 with the PB99IMG-method.
But I get an error "CID incorrect"
I treid to execute the HTC RUU.exe and I get again error code 131...which means something like "user-ID error"
But I could grab a screenshot of the actual "version" of the RUU...or what is this?
Thanks guys

CID incorrect? Your phone is unbranded or branded? Because I found this:
ERROR [294] : INVALID VENDOR ID
Every device contains a short string that identifies the operator who sold it. Because the same device is sold by different operators, this prevents users from flashing a T-Mobile ROM to a device that was sold by Orange, for example. You probably need to Install a HardSPL or CID Unlock your device.
Click to expand...
Click to collapse
I recommend to find a RUU for your device (e.g Vodafone, T-mobile etc.)
Also:
ERROR [131]: CUSTOMER ID ERROR
One of these error messages will appear when you use the wrong RUU to do the update. The RUU will check if the Model ID and Language ID are compatible with the Android phone. Make sure you use the correct RUU to update.
Click to expand...
Click to collapse

If it's saying wrong CID then it's branded, simple as that

1. Boot your phone in fastboot
2. Run the ruu that matches your phone.
You need a T-mobile branded ruu.
You can look here for one that matches. http://shipped-roms.com/index.php?category=android&model=Bravo
I think you can try an UK one, because it is multilingual.
If it is giving you the same errors, then you picked a wrong version.

EddyOS said:
If it's saying wrong CID then it's branded, simple as that
Click to expand...
Click to collapse
well it said "incorrect cid" even with a t-mobile branded ruu :/

If you are rooted, then boot into the bootloader and flash a custom rom. Then create a gold card.

Lennyz1988 said:
If you are rooted, then boot into the bootloader and flash a custom rom. Then create a gold card.
Click to expand...
Click to collapse
Yes, try that too, if you can.
Also use a NOA2SD Rom if you dont have ext partition. Or create one on your PC (if you want to use an A2SD ROM).

How can I flash a Rom using the bootloader?
Simply rename the zipped Image of a custom Rom into "PB99IMG.zip", put in on the SDcard and boot into HBOOT?
Thank you

spaboleo said:
How can I flash a Rom using the bootloader?
Simply rename the zipped Image of a custom Rom into "PB99IMG.zip", put in on the SDcard and boot into HBOOT?
Thank you
Click to expand...
Click to collapse
Yes, if you rooted with unrEVOked. Boot in to recovery (clockworkMOD/AmonRa) wipe all data and flash a CUSTOM rom.
You don't have to rename it, it can be anything as soon as it is .zip

nagypapi said:
Yes, if you rooted with unrEVOked. Boot in to recovery (clockworkMOD/AmonRa) wipe all data and flash a CUSTOM rom.
You don't have to rename it, it can be anything as soon as it is .zip
Click to expand...
Click to collapse
Uhm...flashing a custom rom in general is no problem...but i can't access Recvoery
as described in the initial post of the thread only the bootloader (HBOOT) and fastboot are working.

spaboleo said:
Uhm...flashing a custom rom in general is no problem...but i can't access Recvoery
as described in the initial post of the thread only the bootloader (HBOOT) and fastboot are working.
Click to expand...
Click to collapse
Yeah, sorry, my bad.
Well you can try to falsh it via PB99IMG.zip, but i won't think it work.
your only hope is finding a working RUU. (at least seems to me, if you can access only fastboot).

Hi all, have same trouble with flashing via PB99IMG, but in my case, the device normally loads the firmware and returned to fastbut. When you try to go to recovery device hangs on the logo. Фfter removing the battery and re-attempt to restart the device, it begins to vibrate 7 times and then freezes on the logo. What do these vibration?

PB99IMG.zip will work as you don't need recovery. Just put it on the root of your SD card and boot into HBOOT. It'll find the file and flash it

did renaming rom to pb99img nd flash via hboot work for you?
i have a similar problem, rather same prob, only fastboot available

To let this thread maintain usefullness for future readers:
The solution was to take a goldcard from a friend and flash the right (matching hboot, provider and version) RUU, by using the PB99IMG method.
By this the phone will be set back to it's delivery state! This will include the Rom, all data in the NAND storage the recovery and everything else, which got modified like getting root access or S-OFF etc.
Troubles were caused by USB-Brick or an error on my old ext3 partition or maybe even corrupt data in my Titanium file-backup I restored a few days before the crash :/
I can't clearly say what is the main cause...maybe it was a combination of all.
If you don't have got any chance of getting another goldcard (yes the goldcard creation does NOT depend on the devices! It can be created with ANY android phone ) you are really screwed.
My advice: Always keep a spare microSD card, equipped with it's goldcard image around!
Because I was not able to find any method to echo the CID (Id of the SDcard) in fastboot.
Greetings
And good luck to all of you having comparable issues

flash stock rom after s-off & hoot without usb

Hi,
on my desire I'm running Cyanogen Mod 7.10 with it's dedicated hboot partition table and hboot 0.93.1000.
So far everything went fine but yesterday the usb port screwed up. So I'm not able to charge the phone anymore nor establish a usb connection.
To send it back to htc I'd like to flash a stock t-mobile rom and remove the s-off and all the other thinks which might be suspicious.
As far as I read and understood, I need to
1. flash the Bravo Downgrader from Alpharev to recovery the original partition table. To do so I put this file on the sd card, named it PB99IMG.zip and pressed vol down and power. Then it tells me that the cid is incorrect?
- does anyone know why?
2. if this was successful I should install a stock rom. I downloaded RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.0 6.00.02_2_release_127570_signed.exe
which should be for entire Europe hopefully. But this is an exe file and if I extract it there's only a cab file which shows up and I don't know which one I am supposed to transform to a zip file. Or isn't this possible at all?
hope someone can bring light into my darkness of not getting it right.
greetz
macx

I don't know too much about this, as I am trying to stumble my way though it myself without bricking my HTC Desire. However, i do know that inside the CAB file you mention, there is a file called rom.zip. This file contains all the images you require to flash your device.
So after opening up the exe file (I refer to RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865.exe which is what I am using) you get a folder (RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865). Inside this there is yet again another folder (Disk1). Inside this folder exists Data1.cab (archive) and inside Data1.cab (I used ScanZip to open it) there is rom.zip.
Check these links for more detailed instructions:
http://forum.xda-developers.com/showthread.php?t=575448 (looks slick)
http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
Like I said, I've very little idea about this and I'm still reading up, but I figured this information may help you. Best of luck, HTH.

The instructions from here worked flawlessly.
androidforums (DOT) com (FS) htc-desire (FS) 177907-froyo-2-09-405-8-update-windows-not-required (DOT) html
change (DOT) and (FS) to . and / respectively. I'm not allowed to post this many URLS incase I'm spamming. I followed this, and in 5 minutes I had my phone as it was when HTC sold me it.
Make sure you have a good amount of battery. Best of luck.

Here is "How to Extract the ROM from an RUU".

thanks for your replies. At the moment the battery is to weak to give it a try again.
But I'll follow these steps as soon as I found someone who can charge my battery in his phone. ^^
Greetz
macx

Hi again,
I got my battery charged now and was able to extract the rom.zip from the original ruu.
For those who are interested in how I did it. I simply started the ruu***.exe and search my profile folder for a rom.zip.
So far so good.
Then I rename it to PB99IMG.zip and start the bootloader by pressing vol down and power. It finds the zip file and starts loading it.
Then I get the message "Main version is older! Update fail!"
I'm stuck here, because I don't know what exactly this means. What is the main version? and what else can I try to get back to the factory defaults?
edit:
the first time I tried flashing RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed
it loaded the zip file, then rebooted did the same loading procedure again and then the ""Main version is older! Update fail!" message came up.
If I try it again with now with the same file there is no reboot but the error messages pops up directly. And I realised
that I've got a new bootloader.
now it says:
Bravo PVT1 SHIP S-ON
HBOOT-0.80.0000
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Mar 29 2010, 21:34:33
For me it looks like it flashed the other HBOOT but didn't flash the rom.
Do you guys have an idea?
Greetz
Macx

ok,
i keep on trying.
I also tried to flash RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
first it didn't work because of CID incorrect error message.
After creating a goldcard and trying it again it worked and flashed the rom.
Now my phone runs this version just fine and I gave it a try again to flash the original T-Mobile. This is the lastest version available in the xda Wiki.
Same error again.
Main version is older! Update fail!
What I still do not understand, is what exactly is meant by main version. I got this
error even when there was no rom installed at all. So could it be possible that the rom version is meant by this message?
Even if so, do you know where I can get a T-Mobile version which is newer then the one I tried a million times?
Help is really really appreciated
Greetz
macx

Bootloop After Trying to Unroot

Hello All,
I am completely stuck after trying to fix my girlfriend's phone.
S-Off
HBOOT 6.13.1002
Radio 0.99.01.0225_2
eMMC-boot
___________________________
The phone was rooted over a year ago (not by me). I flashed the HTC12-MROM found here:http://forum.xda-developers.com/showthread.php?t=1892450
The ROM was recently updated, so I did a nandroid backup and tried installing the new rom zip. When I tried to format and wipe the system, everything went to hell.
Whenever I tried to format system, wipe data/cache, I got these messages:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also got messages saying:
error formatting /cache!
error formatting /data
I tried just rebooting the phone, but got stuck in bootloops.
I pulled the battery, tried to do a factory reset, but still got stuck in bootloops.
My genius idea was to try to unroot and take it to a verizon store. No such luck.
I used this guide to try to unroot. http://theunlockr.com/2011/10/14/how-to-unroot-and-return-the-droid-incredible-2-back-to-stock/ I got through Step 1 and flashed the stock ROM file, but the phone was still bootlooping.
I pulled the battery and tried to get into CWM, but the screen goes to a generic phone with a red triangle and exclamation point. If I try to simply reboot the phone, it says "updating software..." but does not move. It's been in this position for at least a half hour.
Can anyone suggest a fix? I can still get into HBOOT. I want to fix this or get it back to stock so I can bring it to Verizon.
Thanks in advance for your help.

That's one of the oldest RUU (Froyo) file from VZW - you might want to try flashing a newer GingerBread RUU from your computer to the DI2 via micro-usb cable. Boot into Bootloader (HBoot) first - make sure that the PC recognize it in USB (nothing like "unknown" or errors reading device, etc.)
http://www.androidfiles.org/ruu/sec....01.1111_NV_VZW1.92_release_225831_signed.exe
Download & flash it, follow the prompts and it should restore your device to stock unrooted condition, then it's a matter of unrooting it again & pushing CWM (with 'adb")
Let it bootup initially and go thru the setup - most likely, you will need to (Re)Activate it OTA again, download/update PRL's - if you can make outgoing call and receiving incoming call, got working 3G/Evdo data and WiFi - it's good to go. If NOT, you will need to call VZW tech support at #8899 [Send/Call] as they will need to take steps to restore your device's security settings (i.e.. "A" keys, etc.) on their end and have you power cycle the device 2 or3 times, get you to make a successful test call, etc.
As for that continuous bootlooping while it's in bootloading mode, it might be a PG32IMG.zip file on the mSD card, pull the Sim card & use a PC to rename and/or delete it, that should help stop the endless loop and help launch it into bootloader and/or recovery.

Thanks for getting back to me. How exactly do I flash this? I can only get into HBOOT. Should I rename this file PG32IMG.zip and put it on the base of the SD?
EDIT
That was a completely retarded question. I figure I can use a cmd prompt to flash this, however, I don't think I've ever had to do that. Can you walk me through it?
Thanks again!

So I figured out how to flash the .exe (literally just plug into the USB and run as administrator). It installed completely fine, but still bootloops. Gets to the red droid eye then boots back to the white HTC screen. It's still not loading.
Any other ideas?

double zero said:
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator) ... It's still not loading. Any other ideas?
Click to expand...
Click to collapse
Okay, let's try to get it stop the bootlooping first. Pull out the mSD card & VZW's Sim card too, if installed after taking out the battery. Let it sit for a minute + and re-insert battery only. Power on while holding the Volume Down key only to get it into Bootloader mode - press the Power key to confirm and you should be in HBoot, move down to Factory Reset and press it.
Next, try to go into Recovery screen from HBoot menu and see if you can see the HTC/factory recovery menu (if the RUU was installed, your previous CWM or TWRP should be gone)
Reconnect via mUSB cable to the PC, and clean flash the RUU again - do NOT put the mSD card back in the side slot yet. Let's see (and hope) if it will continue to setup all the way to finish (HTC activation screen) without bootloop or freezing at the white HTC screen.
The other option is to manually flash things using ADB tools (factory Images - system.img and recovery.img, etc.) that's probably beyond your skills ?? as the file systems, bootloader, etc. were likely corrupted & damaged. There are details / guides & steps-by-steps on how to do it in the Development sub-section ...
Let's see if these ideas will work for your devices and if not ... unless someone else "cruising" here has further tips, your device is almost fully restored back to stock to bring back to Big Red for help, IF and if ...

I pulled the SD and Sim Card as you suggested and got it into HBOOT. I hit "Factory Reset" and the phone eventually went into the white HTC screen (and did not move).
I pulled the battery, went back into HBOOT and scrolled down to Recovery. However the phone is stuck at the generic phone with red triangle/exclamation point.
Should I try to get into HBOOT and try to flash the RUU again?

double zero said:
... Should I try to get into HBOOT and try to flash the RUU again?
Click to expand...
Click to collapse
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.

Letitride said:
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Click to expand...
Click to collapse
Letitride,
I did exactly as you said, installed the RUU again (it said it was successful). I powered down and put into another microSD card I had (FAT formatted and completely blank). No luck. The phone only boots up to the Red Droid Eye, then reboots to White HTC screen, etc.
I also tried using the factory rom in PG32IMG.ZIP format, same thing. The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Thanks.

double zero said:
... The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Click to expand...
Click to collapse
DD - Here's XDA's Guide to ADB for your reference - http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
Link to VZW's RUU files (only used the ones on the bottom of the listed directory for VivoW - it's for DI2 http://www.androidfiles.org/ruu/?dir=Vivo_VivoW
The .1111 Radio flashed is different as shown on the Bootloader is different because it is from a different RUU/Rom build, it is one of the correct ones designed for the device - it is fine. Mine is using a .0312 radio and there is a newer radio with .0320 - they all worked in conjunction with the device, results varied depending on the hardware or build date - results varied.
Both of our DI2 are running fine on HBOOT 6.13.1002
Here is a link to one of the thread with a working HBOOT .96.2000 in ZIP format that you can download & flash from Bootloader - it might help reverse/downgrade to this older version from your existing/newer one - it might NOT work, however as yours is newer (post #37) - http://forum.xda-developers.com/showthread.php?t=1064366&page=4
Is it possible that the device was flashed with the leakded/unofficial RUU or IMG zip file released for China / CDMA-GSM and not meant for VZW's CDMA market ?? If so, it likely corrupted the file/root/boot structure ??
Were you able to do a Factory Reset inside the HBOOT menu ??
Also, do you see the HTC Recovery Menu as it should've been flashed onto the device ?
In any event, let's try doing a wipe of the device once you get into "ADB" with the following command prompt, once it's connected via USB
fastboot -w
Then, try running the RUU again (select this one from the list in the link) - without the new blank mSD card, and with the mSD card
Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe

Add'l thoughts for DZ
Playing w N7 but thinking about your issues, with device still S-OFF (unlocked) - if nothing is working but you can still get into Bootloader, why not try (manually, via ADB if necessary) flash Custom Recovery (CWM or TWRP, whichever works) - boot into that - and, load the SuperDuperWipe script written by ChillyBean in a Zip file. That should do the deep cleansing and wiping to hopefully removed all the hidden files & bits/pieces left on the / or /SD directories that possibly contributed to all the issues you are experiencing - I don't believe it can reverse or rollback your HBOOT version to .97 or earlier (never tried it, maybe it will or it won't) At this point, it doesn't hurt to try or you have everything to gain ...
If the custom recovery & superwipe worked, then, try flashing the RUU again and see if it will boot up fully without looping? From there, you will have a good base, backup first and decide to load/restore custom rom, kernel or minor mods/tweaks ...
Meanwhile, hope you are reading up on ADB - it's a bit "scarely" doing it the first time, after a few command prompts & success - you will feel good about it.

Flash new ROM to a soft-bricked Spalsh screen using PC only.

I was doing a first-time root. CWM installed OK. Then I did something TOTALLY STUPID...and the end result is perm. Splash screen.
On normal power-up, it's stuck on Splash screen white backgound with green "HTC".
It won't go any further.
Tried Recovery but didn't do BACK-UP!! I don't have access to another phone that supports micro-SD, to transfer the file to SD, insert in HTC and use it with Recovery CWM that way?? (Guessing)
I don't know any fastboot/ recovery commands for cmd prompt to send new ROM to the phone.
My phone stats:
***UNLOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.
HTC Sense Version: 2.1
Carrier: Network Unlocked
I can still HBOOT.
CWM is still working Recovery
I've managed to get the shipped rom that closest matches mine via shipped-roms.com- RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe
Or I also got PG76img.zip from xda thread [Marvelc] PG76IMG ZIPs (Taking requests) by member Kalaker (Thank you)
So I have to find a way to flash via PC only.
should add:
When I tried to run the Marvel exe direct, the wizard stalls at the Verifyinf stage as"Error [170]: USB CONNECTION ERROR". The ROM Update Utility cannot connect to your Android phone. Please check that the USB cable is connected properly between the PC and your Android phone.
It is!
I'm using Windows XP
Please help.
Thanks

GERJDOY said:
I was doing a first-time root. CWM installed OK. Then I did something TOTALLY STUPID...and the end result is perm. Splash screen.
On normal power-up, it's stuck on Splash screen white backgound with green "HTC".
It won't go any further.
Tried Recovery but didn't do BACK-UP!! I don't have access to another phone that supports micro-SD, to transfer the file to SD, insert in HTC and use it with Recovery CWM that way?? (Guessing)
I don't know any fastboot/ recovery commands for cmd prompt to send new ROM to the phone.
My phone stats:
***UNLOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.
HTC Sense Version: 2.1
Carrier: Network Unlocked
I can still HBOOT.
CWM is still working Recovery
I've managed to get the shipped rom that closest matches mine via shipped-roms.com- RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe
Or I also got PG76img.zip from xda thread [Marvelc] PG76IMG ZIPs (Taking requests) by member Kalaker (Thank you)
So I have to find a way to flash via PC only.
should add:
When I tried to run the Marvel exe direct, the wizard stalls at the Verifyinf stage as"Error [170]: USB CONNECTION ERROR". The ROM Update Utility cannot connect to your Android phone. Please check that the USB cable is connected properly between the PC and your Android phone.
It is!
I'm using Windows XP
Please help.
Thanks
Click to expand...
Click to collapse
You can mount the MicroSD card from the recovery, you will find the option in "Mounts and storage" or something with a similar name

csoulr666 said:
You can mount the MicroSD card from the recovery, you will find the option in "Mounts and storage" or something with a similar name
Click to expand...
Click to collapse
Thanks.
Yes, in Recovery>Mounts & Storage, there is an option to mountSD.
I didn't see what this would do. BUT I did mounted the SD, re-ran Marvel.exe- in both Recovery AND normal power on Splash screen.
But I still got the same error message as before: "USB CONNECTION FAILED".
I think I need a command that works in cmd like the one on the Unlock BootLoader stage: e.g. the two-fold cd \Android & \Android>fastboot oem get_ etc.
Thanks

GERJDOY said:
Thanks.
Yes, in Recovery>Mounts & Storage, there is an option to mountSD.
I didn't see what this would do. BUT I did mounted the SD, re-ran Marvel.exe- in both Recovery AND normal power on Splash screen.
But I still got the same error message as before: "USB CONNECTION FAILED".
I think I need a command that works in cmd like the one on the Unlock BootLoader stage. The two-fold cd \Android & \Android>fastboot oem get_ etc.
Thanks
Click to expand...
Click to collapse
You won't be able to run any thing from there, what you can do is transfer a ROM and flash it. Try using the stock roms from here

csoulr666 said:
You won't be able to run any thing from there, what you can do is transfer a ROM and flash it. Try using the stock roms from here
Click to expand...
Click to collapse
Thank you for the advice and link
Used a Galaxy S4 to download the ROM from the thread that links in the post above. THANK YOU.
Now I shall:
Insert into HTC
HBOOT>Recovery>Mounts & Storage>Mount SD>+++++Go Back+++++>Install zip from sdcard
And this should install:
from thread: [ROM]stock rom with cool features & perfectly stock roms[UPDATED:15/03/2013] by member crossfire77
PERFECTLY STOCK ROMS IN VARIOUS VERSIONS
FOR MARVEL
its based on latest EU 2.26.401.3 release,android version :2.3.5 [MULTILANGUAGE SUPPORT]
3) it is perfectly stock rom,not even rooted.of course odexed.
http://www.mediafire.com/?zwzyawscawlgwvs
Thanks (& fingers crossed)

Tried to install ROM from zip:
I got:
E:Error in /sdcard/marvel_signed_021213_001159.zip
(status 0)
Any ideas what happened?

Spent the evening/night trying a few different things.
Tried a different ROM, on a different SD Card- so as not to jeopardize the copy I have.
So I download, via the Galaxy S4,:
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe from
www.androidruu.com/?developer=Marvel_MarvelC[/url]
Put the card in the HTC & the download was not listed on the SDCard!
It's definitely there- rechecked it in the S4!
I thought maybe the Wildfire could not see it for some reason so made a folder with the S4, called it Xda & copied the file into it.
So there are now two copies- #1 directly on the card & #2 in the new Xda folder.
I put the card back in the HTC Wildfire & yet again neither were showing. #1 still did not show & although the Xda folder WAS there, the phone read it as having no files!!
So, I thought there might be a problem with either the card OR the downloaded file.
SO....
I got the original SD Card that has the marvel_signed_021213_001159.zip on it, that failed to load earlier, & I downloaded:
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe from shipped-roms.com/index.php?category=android&model=Marvel
Once again, when I put the SD Card into the Wildfire- NOTHING. No file, yet, according to the S4 it's there- right above the marvel from earlier.
Strange? I can not work it out. There is no dot/ full stop before the name on either download on either SD card- a method to hide files apparently on the S4.
At least I've got one working? copy from earlier but THAT still returns the message:
E:Error in /sdcard/marvel_signed_021213_001159.zip (status 0)
Have not found a direct PC to phone method yet either.
Thanks

GERJDOY said:
Spent the evening/night trying a few different things.
Tried a different ROM, on a different SD Card- so as not to jeopardize the copy I have.
So I download, via the Galaxy S4,:
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe from
www.androidruu.com/?developer=Marvel_MarvelC[/url]
Put the card in the HTC & the download was not listed on the SDCard!
It's definitely there- rechecked it in the S4!
I thought maybe the Wildfire could not see it for some reason so made a folder with the S4, called it Xda & copied the file into it.
So there are now two copies- #1 directly on the card & #2 in the new Xda folder.
I put the card back in the HTC Wildfire & yet again neither were showing. #1 still did not show & although the Xda folder WAS there, the phone read it as having no files!!
So, I thought there might be a problem with either the card OR the downloaded file.
SO....
I got the original SD Card that has the marvel_signed_021213_001159.zip on it, that failed to load earlier, & I downloaded:
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe from shipped-roms.com/index.php?category=android&model=Marvel
Once again, when I put the SD Card into the Wildfire- NOTHING. No file, yet, according to the S4 it's there- right above the marvel from earlier.
Strange? I can not work it out. There is no dot/ full stop before the name on either download on either SD card- a method to hide files apparently on the S4.
At least I've got one working? copy from earlier but THAT still returns the message:
E:Error in /sdcard/marvel_signed_021213_001159.zip (status 0)
Have not found a direct PC to phone method yet either.
Thanks
Click to expand...
Click to collapse
Hi,
AFAIK, you will not be able to flash an .exe file from the SD card, there were meant to be used on a PC for flashing through the USB cable, so you will only be able to flash .zip files from the SD card.
The E:Error in /sdcard/marvel_signed_021213_001159.zip (status 0) error is usually associated with a bad META-INF folder inside the zip file, meaning that either the signature file is corrupted, there is something wrong in the any of the files inside this folder, or just the whole zip file is corrupted. CWM is preventing you from doing something wrong.
Try to download and flash the file again, wait for more answers and, as a last resort, try with a different zip file (search for exactly the same rom) or another version in the thread that @csoulr666 posted (options 1 or 2).
Regards.

Still looking for an answer to my USB issue. In the meantime I tried 1 of uk_yo tachibana's suggestions
Downloaded a fresh copy of marvel_signed_021213_001159.zip & clicked install zip from SD card.
This time I got:
--Installing: /sdcard/marvel_signed_021213_001159.zip
Finding update package...
Opening update package...
The handset has been like this since around 10.05 am. I was expecting something else to happen by now (3 hours + later)
I will leave it a while longer, before I try another file.
I assume it has crashed again?
Thanks.

UPDATE:
I've been trying various downloads & ways, yesterday and today. Read umpteen threads & websites.
I've tried multiple downloads of the files. I've used two SD Cards (to verify that SD was not an issue). Also, used both with all files via 2 browsers- Chrome & FireFox, as 1 thread I read recommended that the questionair tries downloading the files with another browser; as either the files are corrupt or the download was- as they too kept getting the "Installation aborted (Status 0)" error.
example of what I keep getting:
Insert SDcard to WildfireS. HBOOT>Recovery
(every time) I do the four wipes...
Wipe data/factory reset
Wipe cache partition completed
(Advanced)
Wipe Dalvik Cache
Wipe Battery Stats
+++++Go Back+++++
Then I click:
- Install zip from sdcard
My options
- choose zip from sdcard
- apply /sdcard/update.zip
- toggle signiture verification
- toggle script asserts
-+++++Go Back+++++
I click:
- choose zip from sdcard
I get my list of files/folders on sdcard
I choose:
(example) marvel_signed_021213_015156.zip
the handset then starts:
--Installing: /sdcard/marvel_signed_021213_015156.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/marvel_signed_021213_015156.zip
(status 0)
Installation aborted
Files I've used (multiple downloads of):
#1
021213_024029.zip
021213_015156.zip
021213_001159.zip
from: [ROM]stock rom with cool features & perfectly stock roms[UPDATED:15/03/2013] by member crossfire77
#2
G76IMG.zip
from: [ROM][HTC][WILDFIRE S A510e][EUROPE][2.3.5][PG76IMG.ZIP] To Flash From Hboot by member d33ps1x
This one returns the error message:
Installing update...
E:Error in /sdcard/PG76IMG.zip
(bad)
Installation aborted
#3
and also:
marvel_perfect_stock.zip
from: [ROM][STOCK 2.3.5]marvel perfectly stock rom... not even rooted!!! by member rjshrjndrn
Even though, later in the thread, the OP says it's not flashable from SD Card as it isn't .img & says renaming is not an option. Just thought I would give it a shot!
I'm looking into "how to rip a PG76IMG off from %temp%"?.
(a) Not sure how to do this yet
(b) If it will even work
HOWEVER, marvel_perfect_stock.zip SHOULD work as is; as a zip- so I put a copy in my PC folder (with the rest of my files-fastboot, adb, cwm etc.).
I just don't know how to use it- there must be some kind of cmd prompt instruction, but it is not listed.
Still can not get past the Marvel_RUU wizard's error from earlier yet, either!
Thanks.

Hello.
On the SD Card side of things, I have read threads that suggest, after multiple downloads [even through different browsers] of a file still return the (Status 0)/ (bad)- that maybe my cwm version needs updating, in order to push the chosen file through.
After doing a "Google search" for cwm for wildfire s download, I got two main options:
1) clockworkmod.com/rommanager‎ BUT, this only offers ver: 5.0.2.8 which is already the one I have.
2) code.google.com/p/cm9-wildfire-s/downloads/detail?name...cwm...THIS gives me a download: Unoffical ClockworkMod v6.0.0.7 Recovery for Marvel.
The file is PG76IMG-cwm-6.0.0.7-UNOFFICIAL-marvel.zip 4.5 MB. [You need to rename it to PG76IMG.zip and copy it to your SD card.]
Now I have already downloaded it [via Firefox on Galaxy S4, renamed as instructed & put on SD]
I JUST HAVE NOT installed/ ran it yet on the Wildfire S as I'm unsure if it's safe to do so OR even if I SHOULD mess around further with the handset/ WORKING Recovery [esp. as the file states UNOFFICIAL CwM]!
Any thoughts on this, as I'm running out of options for solutions?
Thanks.

Aaaah NEARLY!!!!!!!
Found this thread:
Htc wildfire s Stock rom by member gabontz_vl
It advised to go to follow this link:
androidforums.com/wildfire-s-...ed-device.html
So I did this and I followed it's advice and got the Wizard working:
HAD TO ***Relocked*** my Bootloader gurrrr! Will have to unlock again when I have my ROM back!
HTC Android Phone ROM Update Utility 1.0.5.2011
Current information about your Android phone:
Image version:
19.26.401.3
<Click update>
From 19.26.401.3
to
2.26.401.3
Phone restarts; "HTC" appears on black screen
Wizard says the process will take 10 mins to update
BUT after NEARLY working, it failed saying:
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update cannot update your Android phone.
Please get correct ROM Update Utility and try again.
Note the wizard matched my ROM & Radio perfectly.
Have not messed with HBOOT. It's still the original 1.09.0099.
Where do I go from here?
Thanks

GERJDOY said:
Aaaah NEARLY!!!!!!!
Found this thread:
Htc wildfire s Stock rom by member gabontz_vl
It advised to go to follow this link:
androidforums.com/wildfire-s-...ed-device.html
So I did this and I followed it's advice and got the Wizard working:
HAD TO ***Relocked*** my Bootloader gurrrr! Will have to unlock again when I have my ROM back!
HTC Android Phone ROM Update Utility 1.0.5.2011
Current information about your Android phone:
Image version:
19.26.401.3
<Click update>
From 19.26.401.3
to
2.26.401.3
Phone restarts; "HTC" appears on black screen
Wizard says the process will take 10 mins to update
BUT after NEARLY working, it failed saying:
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update cannot update your Android phone.
Please get correct ROM Update Utility and try again.
Note the wizard matched my ROM & Radio perfectly.
Have not messed with HBOOT. It's still the original 1.09.0099.
Where do I go from here?
Thanks
Click to expand...
Click to collapse
Try using a zip extracted from an RUU
1. First download and run an RUU on your computer(the latest one you can find)
2. After the first window pops up, close it
3. Then in "Run" type "%temp%"
4. In there find a file named "ROM.zip"
5. Rename it to "PG76IMG.zip"
6. Put it on the root of the SDcard(no folders)
7. Now boot into the bootloader
8. It will check and ask you to flash the file, press the Vol up button
9. And you'll get a completely stock rom
Do make sure that your bootloader is Relocked when you do this, you can unlock it using the same unlock code

csoulr666 said:
Try using a zip extracted from an RUU
1. First download and run an RUU on your computer(the latest one you can find)
2. After the first window pops up, close it
3. Then in "Run" type "%temp%"
4. In there find a file named "ROM.zip"
5. Rename it to "PG76IMG.zip"
6. Put it on the root of the SDcard(no folders)
7. Now boot into the bootloader
8. It will check and ask you to flash the file, press the Vol up button
9. And you'll get a completely stock rom
Do make sure that your bootloader is Relocked when you do this, you can unlock it using the same unlock code
Click to expand...
Click to collapse
I've just spotted the reply, thank you for the advice csoulr666.
Yes I will do this now & let you know how I get on.
Again, thanks.

Thanks again to csoulr666.
Followed the instructions to the letter.
After powering on in HBOOT, the handset automatically began "checking...PG76IMG.zip". A load-bar appeared at the top-righthand corner of the screen. When checking completed, I got:
Main Version is older!
Update fail!
Press <power> to reboot.
Now, I extracted from RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe-
as the stats for my software were ROM: 2.26.401.3 & Radio 7.57.39.10M.
A perfect match. So what is this "Main Version is older" referring to?
I am a little confused.
Thanks.

GERJDOY said:
Thanks again to csoulr666.
Followed the instructions to the letter.
After powering on in HBOOT, the handset automatically began "checking...PG76IMG.zip". A load-bar appeared at the top-righthand corner of the screen. When checking completed, I got:
Main Version is older!
Update fail!
Press <power> to reboot.
Now, I extracted from RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe-
as the stats for my software were ROM: 2.26.401.3 & Radio 7.57.39.10M.
A perfect match. So what is this "Main Version is older" referring to?
I am a little confused.
Thanks.
Click to expand...
Click to collapse
Try using one that is newer than your current version

Thank you to csoulr666 for the advice. I apologise for the delay in responding (as I saw this at 9am). I have spent the day (& most of last night ) on Google, reading umpteen threads-
"googling": ERROR [140]: BOOTLOADER VERSION ERROR/ The ROM Update cannot update your Android phone/ Main Version is older/ ruu could not update my rom version/ latest stock rom for wildfire s/ htc wildfire s newest update/ original stock rom for htc wildfire s/ stock roms for wildfire s/ HTC Wildfire S Software newer than 2.26.401.3/ update from 2.26.401.3/ update android 2.3 6/ download android 2.3 6 for htc wildfire s.
The latest RUU IS 2.26.401.3. That is the one I am using, both as RUU, & to extract the ROM to .zip. I can not find ANY NEWER RUU.
I am unclear as to what "Try using one that is newer than your current version" referrs to, sorry; so I could only reason that it must be the Android version.
As the RUU is the latest- 2.26, it should surely contain ver:2.3.5. If it's not, which the error messge implies it's not?, I'm not sure how to check the Android version contained within nor how to replace it as I can not find a seperate 2.3.5 file. I can not find an Android 2.3.5 file download, nor how to update an RUU in .exe form or an independant ROM .zip ripped from it, .
I am now really stuck & fresh out of ideas.
Thanks

GERJDOY said:
Thank you to csoulr666 for the advice. I apologise for the delay in responding (as I saw this at 9am). I have spent the day (& most of last night ) on Google, reading umpteen threads-
"googling": ERROR [140]: BOOTLOADER VERSION ERROR/ The ROM Update cannot update your Android phone/ Main Version is older/ ruu could not update my rom version/ latest stock rom for wildfire s/ htc wildfire s newest update/ original stock rom for htc wildfire s/ stock roms for wildfire s/ HTC Wildfire S Software newer than 2.26.401.3/ update from 2.26.401.3/ update android 2.3 6/ download android 2.3 6 for htc wildfire s.
The latest RUU IS 2.26.401.3. That is the one I am using, both as RUU, & to extract the ROM to .zip. I can not find ANY NEWER RUU.
I am unclear as to what "Try using one that is newer than your current version" referrs to, sorry; so I could only reason that it must be the Android version.
As the RUU is the latest- 2.26, it should surely contain ver:2.3.5. If it's not, which the error messge implies it's not?, I'm not sure how to check the Android version contained within nor how to replace it as I can not find a seperate 2.3.5 file. I can not find an Android 2.3.5 file download, nor how to update an RUU in .exe form or an independant ROM .zip ripped from it, .
I am now really stuck & fresh out of ideas.
Thanks
Click to expand...
Click to collapse
Did you get this sorted?
I too had the same problems as you. I am on the same HBOOT and radio and my Cid is O2__001 (UK) and all the errors you encountered were the same for me.
I got it working tonight by creating a GOLDCARD SD card (search XDA/Google for it and use Youtube to find out how to create one) and using the Rom extracted from the latest RUU 2.26.401.3.
Now im totally stock.
If you need anymore help PM me.

fgw3987 said:
Did you get this sorted?
I too had the same problems as you. I am on the same HBOOT and radio and my Cid is O2__001 (UK) and all the errors you encountered were the same for me.
I got it working tonight by creating a GOLDCARD SD card (search XDA/Google for it and use Youtube to find out how to create one) and using the Rom extracted from the latest RUU 2.26.401.3.
Now im totally stock.
If you need anymore help PM me.
Click to expand...
Click to collapse
Am having the same issue. Error 140. Can you help me pls.

ketchi_ks said:
Am having the same issue. Error 140. Can you help me pls.
Click to expand...
Click to collapse
Sorry mate, I no longer have this phone. Did u try the steps I took?
Sent from my HTC One using XDA Free mobile app

[Q] HTC Desire Bravo PVT1 badly bricked. Unrooted and S-ON

Hi everybody, first of all many thanks for a great forum. I have found it very useful in the past and never needed to seek help, but this time I am stumped and although I read pretty well all the threads on the subject I have not been able to solve my problem and I fear I have a paper weight on my hands.
My Desire does not boot up and stays on the HTC logo on a white screen for ever. This happened after a stupid and unresearched attempt to downgrade my Hboot from 1.03 to earlier ones with RUU_Bravo_H3G_UK_1.20.771.3_Radio_32.36.00.28U_4.06.00.02_2_release_124822.exe.
The process worked fine but my Desire never managed to reboot and got stuck on the opening logo.
I can go into HBOOT USB PLUG and I can charge the battery (the led comes on and eventually goes green). The HBoot screen reads:
LOCKED (00W)
BRAVO PVT1 SHIP S-ON
HBOOT - 1.03.0003
TOUCH PANEL - SYNT0101
RADIO - 4.05.00.11
Date 21 2011 - 20:44:09
I can do FASTBOOT DEVICES and get
HT06XPL00452 fastboot
but any other operation with fastboot always gives me:
FAILED (status malformed (1 bytes)
Does anybody know what this means?
I also tried:
** to rerun the official RUU but I get a clearly wrong message saying that the battery is below 30% charge and the program stops.
** several other RUUs with same result except RUU_Bravo_Froyo_HTC_WWE_2_29_405_5_Radio_32_49_00_32U_5_11_05_27_release_159811_signed.exe which leads to ERROR [170]: USB CONNECTION ERROR. I know the USB Hboot drivers are ok and are those I downloaded from XDA. Device manager shows "Android composire interface"
** select RECOVERY but it goes immediately into the white screen aith HTC logo and gets stuck
** select CLEAN STORAGE . When I answer "Yes to Delete all user data?" it confirms "clear..." and then gets stuck on the log screen
** select SIMLOCK and get
FAT32 init OK
Open MCCMNC file fail
Open CID file fail
Has anybody got any other ideas? Should I just give up and use it as paperweight?

Tried the 2.3.3 WWW RUU? Download it from shippedroms
research and use the PB88IMG.zip method, bortak's troubleshooting guide.

eddiehk6 said:
Tried the 2.3.3 WWW RUU? Download it from shippedroms
research and use the PB88IMG.zip method, bortak's troubleshooting guide.
Click to expand...
Click to collapse
Many thanks eddiehk. The RUUs I had tried before came from shippedroms.com too but I cannot find any for the Desire (nor for the Bravo) with 2.3.3 nor WWW in their name. Do you have a specific link? I have just tried yet another one for luck but got the same result as before "battery less then 30%" which is not!:crying:
The PB88IMG.zip method cannot work for me as I cannot get to write to the system nor the sdcard as the phone does not boot up. I have read a bortak's guide, but it seem to be only for S-OFF setups and it also seems to be only for rooted phones. Mine is not rooted and it has S-ON.
Any other ides anybody?

marco_bruzzone said:
Many thanks eddiehk. The RUUs I had tried before came from shippedroms.com too but I cannot find any for the Desire (nor for the Bravo) with 2.3.3 nor WWW in their name. Do you have a specific link? I have just tried yet another one for luck but got the same result as before "battery less then 30%" which is not!:crying:
The PB88IMG.zip method cannot work for me as I cannot get to write to the system nor the sdcard as the phone does not boot up. I have read a bortak's guide, but it seem to be only for S-OFF setups and it also seems to be only for rooted phones. Mine is not rooted and it has S-ON.
Any other ides anybody?
Click to expand...
Click to collapse
http://shipped-roms.com/index.php?category=android&model=Bravo
"HTC_Desire_Android_2.3_Upgrade.zip" at the bottom
I meant "PB99IMG.zip" method sorry. It should and will work. It does not require the phone to be booted up. It only requires you to copy it to the root of the sdcard (use a card reader). Then boot into bootloader (volume down + power), wait a few seconds, then accept. All in the guide
Or search how to downgrade hboot 1.03 in these forums, I've seen it successfully done on a few occasions.

eddiehk6 said:
"HTC_Desire_Android_2.3_Upgrade.zip" at the bottom
I meant "PB99IMG.zip" method sorry. It should and will work. It does not require the phone to be booted up. It only requires you to copy it to the root of the sdcard (use a card reader). Then boot into bootloader (volume down + power), wait a few seconds, then accept. All in the guide
Or search how to downgrade hboot 1.03 in these forums, I've seen it successfully done on a few occasions.
Click to expand...
Click to collapse
Many thanks again. Unfortunately I got no further. I downloaded the PB99IMG_Bravo_Froyo_HTCCN_CHS_CU_2.35.1402.5_Radio_32.54.00.32U_5.14.05.17_release_163341_signed.zip file from the url you indicated. There were several PB99IMG... and picked one at random. None had the same radio as what was indicated on my Hboot screen by the way. Anyway given the lack of success I suspect it wouldn't have made any difference which one I picked. I then copied it to the root of the sd card using my PC and kept my fingers firmly crossed when I went into bootloader. After a brief moment I saw a subliminal message about checking something but could not read the rest. It then went back to the now very boring Hboot screen with the normal commands "fastboot;recovery;clear storage and simlock".:crying:
Then I tried to use the Universal Android AIO flasher and could see some messages. Trying to flash something in fastboot mode always gave this message:
"(bootloader) signature checking...
FAILED (remote: signature verify fail)"
It does look like something is very screwed up on the internal card and might need a total reformatting. Is it possible or am I barking at the wrong tree?
LATEST UPDATE
OK, I am officially an idiot.
The reason why the .zip file did not work was that I had not changed its name to PB99IMG.ZIP. I did that and hey presto got it to reload the firmware,
As I ended up with a Chinese carrier version I would now like to change it again to a European version preferably a no carrier version. How can I find out which version to pick and which one is the latest version on the ShippedRom site?
In the meantime many many many thanks for all the help. It is so great to have this forum to help all the newbies like me.

@marco_bruzzone
You got a Chinese ROM version because you ignored my advice......
You get the "European version preferably no carrier version" by actually reading my previous post..................
I even quoted the name and location of the correct RUU to use..............

eddiehk6 said:
@marco_bruzzone
You got a Chinese ROM version because you ignored my advice......
You get the "European version preferably no carrier version" by actually reading my previous post..................
I even quoted the name and location of the correct RUU to use..............
Click to expand...
Click to collapse
I am sorry for being dim, I reread your earlier posting and finally understood it. I will now try the correct .zip file. Thanks again