Develop Bugs

[Q] radio update problem

i cannot update the latest radio 32.56.00.32U_5.17.05.08
i m using insercoin gingersense v2
i tried updating it shows update complete but the radio is still the same
any idea ????

Have the same problem,
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
Radio version: 5.11.05.27.
SPL/hboot version: 0.93.1000.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
Flashing "radio" - PLEASE WAIT.
"radio" flash FAILURE.
Whats the problem?

do you use a custom hboot? If yes, your cache partition is probably to small to hold a radio-flash (depends on which hboot exactly you are using), so you have to use fastboot to flash radios.

Are you flashing from Recovery? If so, are you using a custom Hboot that doesn't have a large enough cache partition?

Im using CM7 hboot, and i was tring to flash with festbootcomander 1.1

Try flashing it in fastboot with "fastboot flash radio radio.img". Making sure the radio.img is in the proper folder before hand.
or try Android Flasher...I think it does the radio...not 100% though. But again, I'm not sure if these utilities use the cache partition or not. If they do, CM7's Hboot is too small.

Step-by-step, if you need it. (Taken from www.oxygenrom.com)
Flash Radio (S-OFF fastboot method):
1.Fully charge your phone
2.Download the radio image from the link below and unzip the radio.img
3.Connect your phone to your computer.
4.Reboot your phone into the bootloader (fastboot mode).
5.At the command prompt on your computer type: fastboot devices
6.A value like HTXXXXXXXXXXX should be displayed with the word fastboot next to it.
7.Your phone screen should have FASTBOOT USB on it.
8.If all of the above is not exactly as described DO NOT PROCEED and resolve your fastboot problem.
9.At the command prompt type: fastboot flash radio "filename".img - you must type it correctly!
10.Now, observe the computer and be patient TOUCH NOTHING!!
11.The process will copy the image to your phone, write the image to the radio partition and perform some magic be patient TOUCH NOTHING!!
12.Watch the little indicator at the top of your phone screen.
13.Once the process appears to finish (it may not say complete) wait a further FULL 60 SECONDS and be patient TOUCH NOTHING!!
14.Then, and only then, reboot your phone.

Tnx but getting in the command prompt:
C>fastboot devices
'FASTBOOT' is not recognized as
operable program or batch file.
S O L V E D:
I unzipped the radio and and flashing only the radio.img with the fastboot commander 1.1

[Q] Bricked phone?

Hi all,
Here's the situation;
Tried to update to the latest official rom after buying a HTC Desire from a friend. When upgrading this error appeared: ERROR [110]
After this, the phone rebooted and is stuck on the HTC logo with 4 exclamation marks in each corner.
I can't boot into recovery, nor hboot, only fastboot seems to work. Below you can find the fastboot output.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 6.93.1002.
Radio version: 5.17.05.23.
Main software version: 3.14.405.1.
cid: htc__e11.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
Tried making a goldcard with another phone, and reflash, but the same error appears with the same result.
There is not that much info about this problem, already tried everything i've found...

Hi did you flash aplharev downgrade hboot? as you saying fastboot working try to flash it and run ruu again. Is 'fastboot oem boot' working?

already downgraded hboot
and 'fastboot oem boot' returns 'FAILED (status read failed (Too many links))'

just find out it fails on flashing the radio.
Maybe he blocks on trying to downgrade the radio? I'm not able to downgrade radio true fastboot commander neither.

Hi try to flash alpharev stock and do it again... it has bigger cache partition... see :http://forum.xda-developers.com/showthread.php?t=1171494
ps did you restart phone after flashing downgrade?

I just did following steps:
1. flashed 'bravo_alphaspl.img' as Hboot/SPL
2. rebooted
3. trying to downgrade radio again, same sh*t, tried the RUU installer again, also same sh*t

just did some searches... you can try it but no sure, as you are able to flash radio any time unless any other problem
flash downgrade
fastboot erase cache
fastboot oem rebootRUU
run ruu

i'm NOT able to downgrade the radio version...
guess this is the cause of all my problems...
any other suggestions?

RUU flashes the radio also, no need to change radio

Where did you get that update from?

it's isn't the upgrade that failed it was the Hboot image, i had the same error trying RUU the phone with cm2r2 image on hboot, when changed to stock hboot it stoped giving error 110, i had the same screen with exclamation marks, i've managed to get RUU flashed on the phone, i dont remember exact the procedure but fastboot commands worked and i was able to flash the phone with RUU, i used many RUU's until find one that worked with my phone

Did you try htcdev download? that should work

If you were actually paying attention to what are others telling you, you would have your Desire fixed long time ago.

I solved the same problem by doing a backup of a good desire and then flashed via fastboot the boot.img, cache.img, recovery.img and system.img.
I did all of this after I had rolled back the hboot from the Alpherev CM7 version to the stock alpharev hboot so same as on the other phone (this can be done via fastboot of reflashing program.
I then typed 'fastboot boot OEM' in fastboot and hey presto booted up into gingervillan.
Oh and used a gold card when doing it.
Sent from my HTC Runnymede using xda premium

I think I tried like 12-13 RUU updates, finally founded the one I needed!
-RUU_HTC+Desire+Android+2.3+Upgrade+(Gingerbread)-3.14.405.1-
Thanks for all the reply's, none of the solutions above worked for me, except flashing the one and only (latest) RUU for my phone.
I'm going to keep my phone with original rom now, unrooted, because it seems that rooting is impossible with current ROM...

[Q] Desire HD can't boot (red triangle) after AAHK Fail

Hi everyone!
I've managed to screw up my Desire HD after running aahk-11092012, and was wondering if anyone had any bright ideas...
The Phone is a Desire HD bought from SFR here in France in 2011, never rooted or custom rom'ed, although updated with 2or 3 SFR roms since.
I ran aahk from the terminal on a OSX 10.7 (see Output.txt). From this you will see that it wants naturally to downgrade (to Froyo I assume) but downloading the rom fails, and even though I refused the "-n Flash this RUU? (y/n)" question, it continued doing all sorts of things, getting a few error along the way, rebooting the phone into recovery a few times, and finishes with
************* Downgrade failed *************
** Either:
** GoldCtixiard/SDCard failed
** USB connections are not working 100%
************* Downgrade failed *************
I then tried to flash the "Gingerbread HTC WWE 2.50.405.2" rom from the options menu, thinking I'd be clever, but that monumentally fails too..
From this point on the phone boots to the "Red tringle with an exclamation mark" screen (after the white HTC logo) and does nothing else.
Restarting AAHK just fails with a "Error detecting HTC phone on USB connection."
Having discovered the "VOL-UP +Power" recovery screen during this process, the next thing I tried was a "Apply sdcard:update.zip", but this just results in an "Invalid command" message underneath that already present "E: Can't open /cache/recovery/command" in yellow further down the screen.
I then try a "Wipe data/factory reset" and also a "Wipe cache partition". I can't honestly explain this. At least not given that I hadn't really looked up the issue anywhere yet. I also cant remember exactly what the output was, but the result is the same, still the red triangle screen.
OK, so now I finally open my eyes and realize what a moron I've been, so i plunge into actually learning something and realize quickly (aside from I hate myself and I'm not special, bla bla) that there are loads of thing I could have done differently, and directly on the phone, but obviously it's now too late. (See below for the information I CAN get from the Phone)
Oh yes, I did try a "Factory reset" from HBOOT, but still no joy....
The main option I've been looking into has been to recover an original branded SFR firmware and Froyo ROM and go from there, so I did manage to get a PD98IMG.zip file onto the SD card and HBOOT recognizes it, but fails with a "CID Incorrect" error.
I seem, therefore to be stuck whether I want to return to original SFR or continue tryng to flash a custom ROM:
I can't make a goldcard: I cant adb any commands, in HBOOT the device is not found, and in recovery the device is found but is "offline".
I found jo0ls' CID reader, but I dont have a SD card reader directly plugged to the PCI bus!
I did finally try to install a clockwork recovery in FASTBOOT, but get this:
$ fastboot flash recovery recovery-clockwork-5.0.2.0-ace.img
sending 'recovery' (3624 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
I assume this is much the same error as for the PD98IMG...
Sorry about the long winded post, but I hope it has the maximum of info...
Anyone have any ideas?
- I can boot to HBOOT: it shows me this:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Sep 7 2011, 19:06:24
- ...and FASTBOOT, fastboot getvar all gives this:
INFOversion: 0.5
INFOversion-bootloader: 2.00.0027
INFOversion-baseband: 26.03.02.26_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.32.405.6
INFOserialno: SH12GRX00567
INFOimei: 356812048021701
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: VODAP203
INFObattery-status: good
INFObattery-voltage: 4199mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 743ca94a
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
- The recovery is the original "Android system recovery <3e>"

AAHK, and the server hosting the downgrade files, is retired. You can still unlock the bootloader, but your hboot needs updating before it cam be unlocked. I think you could also run your stock RUU.

CID Number shows that your device is a Vodafone device, probably VodaSFR but who knows? Fetch a Voda RUU and install it
Sent from my Desire HD using Tapatalk 2

you need to upgrade your bootloader to 2.00.0029
htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe (sorry, i can´t atach links)
then unlock it(follow htc-dev guide) and you will be able of flashing a custom recovery

pascuals said:
you need to upgrade your bootloader to 2.00.0029
htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe (sorry, i can´t atach links)
then unlock it(follow htc-dev guide) and you will be able of flashing a custom recovery
Click to expand...
Click to collapse
Thanks for all your answers!
@ bananagranola: I did know aahk had been discontinued, I actually mentioned this originally but edited it out to "shorten my post"!
@ humzaahmed155: quite right, I'm with SFR, and I'm trying to simply restore an original branded ROM
@ pascuals: I will look into your suggestion right away! I was vaguely aware I might have to do this but could not get an accurate enough idea of what version might be appropriate for my phone

[SOLVED] [Q] Desire HD can't boot (red triangle) after AAHK Fail
Kawika1611 said:
Thanks for all your answers!
@ bananagranola: I did know aahk had been discontinued, I actually mentioned this originally but edited it out to "shorten my post"!
@ humzaahmed155: quite right, I'm with SFR, and I'm trying to simply restore an original branded ROM
@ pascuals: I will look into your suggestion right away! I was vaguely aware I might have to do this but could not get an accurate enough idea of what version might be appropriate for my phone
Click to expand...
Click to collapse
Woohoo!! I'm so happy, I got the phone working again last night!! I had a ruu kicking around:
RUU_Ace_Sense30_S_Vodafone_FR_3.13.163.3_Radio_12.65.60.29_26.14.04.28_M_release_227340_signed.exe
from the first day I'd bricked it. This hadn't worked the first time I tried it on windows (actually a Parallels VM on Mac), with the phone plugged in, but I can't remember what mode the phone was in; but as you'll see below I must not have been in fastboot...
Whatever, last night I finally tried pascuals's PD9810000 RUU, with the phone connected and in fastboot, the utility detects the phone fine, but fails with a firmware version error, saying the phone is 1.32.405.6, it will install version 3.13.0.0 but I need to "upgrade to 3.12.405.1"..:silly: (see attachments).
Feeling dejected I fired up the rom cited above thinking I have nothing to lose, and...lo an behold...10 minutes or so later the phone reboots to a beautiful welcome screen insulting me for not having inserted a SIM card!!!
Thanks anyway for your answers, at least they got me looking in the right direction!! I will now go a learn properly how this things work before bricking it again

pascuals said:
you need to upgrade your bootloader to 2.00.0029
htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe (sorry, i can´t atach links)
then unlock it(follow htc-dev guide) and you will be able of flashing a custom recovery
Click to expand...
Click to collapse
My HBOOT is 0.85.2425, after S-OFF. Can I update to 2.00.0029? How?
Thanks.

use that link and just run the exe with your phone connected, atleast with debugging on i think, mine was like that, the tool took care of the rest automatically.

mobidor said:
My HBOOT is 0.85.2425, after S-OFF. Can I update to 2.00.0029? How?
Thanks.
Click to expand...
Click to collapse
I see no reason why you need to update the bootloader when you already have s-off. If your bootloader is engineering bootloader then just let it be.
Sent from my Desire HD

[Q] Help Me and my desire hd

Hello everyone,
six months I have the ROM Miui but then the phone is switched off
my htc desire hd will not start
when I start the ext4 recovery touch: the error recovery in safe mode
and I can not install a new ROM or do a wipe
Here is what hboot says:
*******AAHK**********
ACE PVT ENG S-OFF RL
HBOOT-0.85.2425
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011,00:55:45
I also see "HBOOT USB PLUG" when plugged in, and the computer does beep though no connection can be established. HTC Sync doesnt work (on a different computer), adb cannot connect and AAHK doesnt find a device.
The RUU from HTCDEV doesnt find the phone either....
What can I do? I tried to flash many PD98IMG.zip for example that of the stock and PD98IMG_cwmrecovery nothing but the result is always:
sd checking ....
loading .... [PD98DIAG.zip]
No Image
Loading .... [PD98DIAG.nbh]
No Image or Wrong Image
Loading .... [PD98img.zip]
No Image
Loading ...... [PD98img.nbh]
No Image or wrong image.
aspect of your answers and sorry for my english stupid

first method.. you can try flashing recovery from FASTBOOT mode..
download 4EXT recovery.img from here then extracted file and placed it to your adb/ sdk folder on your pc...then flash it through FASTBOOT mode with command "fastboot flash recovery recovery.img"
second method...you can firstly flash RUU that already rooted by phiber2000 download from here.. through bootloader with PD98IMG.zip name of file..to fix your bootloader and at once replaced your hboot to the newest of ENG hboot..after that...you can continued with the first step for flashing recovery.img through FASTBOOT
hope this help..

thanks friend!
I flashed the recovery via fastboot commander but into recovery the ext4 partition is sometimes mounted and sometimes error mounting
the phone works via fastboot commander 1:51 :
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 0.85.2425.
Radio version: 26.10.04.03_m.
Main software version: 2.47.502.7.
cid: 11111111.
cpld: none.
product: ace.
mid: pd9810000.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
I tried to erase the system cache and data but it makes me always the same problem later
What do you advise me to do?

Zueg92 said:
thanks friend!
I flashed the recovery via fastboot commander but into recovery the ext4 partition is sometimes mounted and sometimes error mounting
the phone works via fastboot commander 1:51 :
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 0.85.2425.
Radio version: 26.10.04.03_m.
Main software version: 2.47.502.7.
cid: 11111111.
cpld: none.
product: ace.
mid: pd9810000.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
I tried to erase the system cache and data but it makes me always the same problem later
What do you advise me to do?
Click to expand...
Click to collapse
did you already tried flashing RUU PD98IMG.zip (rooted RUU by phiber2000) that i give it the link to you before..?
just make sure to placed that RUU PD98IMG under the root of your sd card..then flashing it through loading from your phone bootloader..

JJeamy said:
did you already tried flashing RUU PD98IMG.zip (rooted RUU by phiber2000) that i give it the link to you before..?
just make sure to placed that RUU PD98IMG under the root of your sd card..then flashing it through loading from your phone bootloader..
Click to expand...
Click to collapse
thanks friend,
Yesterday I solved and the phone started
but I was wrong to flshare the recovery and did the erase of the system and the phone is dead
when I connect the power supply does not turn on no led
it is fried the motherboard?

Zueg92 said:
thanks friend,
Yesterday I solved and the phone started
but I was wrong to flshare the recovery and did the erase of the system and the phone is dead
when I connect the power supply does not turn on no led
it is fried the motherboard?
Click to expand...
Click to collapse
when I connect it to my pc makes the sound of the new device but not red led power

Zueg92 said:
when I connect it to my pc makes the sound of the new device but not red led power
Click to expand...
Click to collapse
did the phone still can get into bootloader..?

JJeamy said:
did the phone still can get into bootloader..?
Click to expand...
Click to collapse
no i can't....i have deleted bootloader!! :crying:

Zueg92 said:
no i can't....i have deleted bootloader!! :crying:
Click to expand...
Click to collapse
WHAT !!!!...
are you sure that your bootloader is already gone...?
i mean...did you already trid to pressing and hold volume down+power to turn on your phone..then nothing happen..?
if so...then you must take your phone to the services center to flashing emmc from the beginning..
sorry for can't help you more than this..

JJeamy said:
WHAT !!!!...
are you sure that your bootloader is already gone...?
i mean...did you already trid to pressing and hold volume down+power to turn on your phone..then nothing happen..?
if so...then you must take your phone to the services center to flashing emmc from the beginning..
sorry for can't help you more than this..
Click to expand...
Click to collapse
thank you so much you have been very kind ....
Now I try to flash the bootloader via EPROM

Can not fix Splash screen, System Formatted- ERROR 140/Main Version Older

Hello. Can ANYONE please please help?
I started Rooting process- total Newbie but undergoing a BAPTISM OF FIRE!!
UNLOCKed BL, CWM 5.0.2.8. Then, with no back-up made- System Format!
I have been trying to restore my soft-bricked (stuck on Splash screen), but I have hit an issue. I can not find a 100% match for an RUU. Phone will not accept RUU.exe NOR any ROM.zip
I tried custom ROMS from here via SD card initially
Then, I've tried to flash (Bootloader RELOCKED, CWM installed) via:
RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe
99.9% ROM match- it is 401.3, (I recorded mine in written notes as 401.2); BUT 0% radio match- I have 7.57.39.10.
My ROM 2.13.401.2/ my software- 2.26.401.3/ my radio: 7.57.39.10M- a combo of RUU 2.13's ROM & RUU 2.26's software & radio (OTA updated at some point perhaps?)
It looked as though it would work, BUT, I got:
HTC Android ROM Update Utility 1.0.3.2011
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again
As software is 2.26.401.3 I tried: RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe.
0% ROM match but 100% match of software id & 100% radio match
With this:
1) Tried to flash exe direct. Got: "ERROR [140]: BOOTLOADER VERSION ERROR".
2) Retried to flash RUU after ripping recovery.img from ROM.zip & placed in folder with the adb files. Got: Same result.
3) I tried microSD card flash with ROM.zip, (BL UNlocked) taken from RUU_Marvel_S_2.26........route. Got "Error: Main Version is older!"
Tried PG76IMG from [ROM][HTC][WILDFIRE S A510e][EUROPE][2.3.5][PG76IMG.ZIP] To Flash From Hboot, "Installation aborted; bad!"- multiple downloads, multiple tries- file is 152 MB & I keep getting 148 MB (151,553KB).
I also tried to flash PG76IMG_Marvel_HTC_Europe_2.13.401.2_Radio_47.23a.35.3035H_7.53.39.03M_release_225747_signed.zip from shipped-roms
[100% ROM match & 0% radio] via SD card.
Got it wrong!! At least all it did was wipe CWM & did not full-brick! So now my Recovery was back to default: Android system recovery <3e> but I could un-unlock/ re-lock BL & put CWM back, no probs.
So I read multiple threads/ sites over the past week on both "Error 140" & "Main version is older", & can not find an answer. They are mostly either other-Model related or unresolved amongst other things.
,
I decided to quit while I'm ahead [just Slash screen with UN/RE lockable BL & able to CWM] & post this in hope of knowledgeable assistance. Surely, this IS self-fixable? What am I doing/ not doing?
My options, as far as I can tell, from shipped-roms.com are:
RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe OR.......
Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed_ROM.zip
Both are 99.9% ROM match- they are 401.3, I recorded mine as 401.2; BUT 0% radio match- I have 7.57.39.10.
Can not see it being RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe?
Q; (1) Why RUU/ROM.zips are not flashing/ which & version to use??
Q: (2) Do I need to downgrade something? If so what & how?
Q. (3) Any thoughts, anyone anything?
FULL HANDSET STATS:
Wildfire S A510E
***RELOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.13.401.2
Software: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.0099
HTC Sense Version: 2.1
Carrier: Unlocked
fastboot getvar all (with serial/ imei #s edited):
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0099
(bootloader) version-baseband: 7.57.39.10M
(bootloader) version-cpld: None
(bootloader) version-microp: 0451
(bootloader) version-main: 19.26.401.3
(bootloader) serialno: ############
(bootloader) imei: ###############
(bootloader) product: marvel
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PG7610000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4073mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 510e562c
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Thanks.

I was looking for an exact RUU.exe for my ROM: 2.13.401.2 NOT .3 as offered by shipped-roms & others.
After trawling Google I found this: tsar3000.com/Joomla. Clicked downloads tab along the top, chose HTC & scanned down the list. I picked #42 (HTC WildeFire S A510E / A510c / MetroPCS - Marvel / C Stock Roms)
Looking down it I found RUU_Marvel_S_HTC_Europe_2.13.401.2_Radio_47.23a.35.3035H_7.53.39.03M: an EXACT RUU.exe match for my ROM.
<clicked RUU link> took me to a file share website: fileom.com.
Created account, & after verifying by clicking link & email, downloaded RUU.
Then:
1) RELOCKED BootLoader- cmd prompt & typed: fastboot oem lock
The tried a straight RUU.exe flash. This returned the ERROR 140: BOOTLOADER VERSION ERROR etc.
2)Started RUU; went NO FURTHER.
Clicked START on PC. Searched for %temp% folder. Found the two created when RUU is run.
To do this- call up the temp folder. Kill the RUU. Restart the RUU.
Keep doing this and you begin to notice 2 folders will appear when RUU is started & disappear when RUU is stopped.
Checked both to find a .zip called "ROM.zip".
Took it to a new folder so it did not interfere with anything. Unzipped it.
Copied 3 of the revealed files to the \Android folder (my folder containing my ROOTing files- adb/ BootLoader unlock file from HTC/ etc.)
The 3 are recovery.img, boot.img & system.img
Then:
RE-UnLocked BootLoader- opened cmd prompt & typed cd \Android; as my HTCdev Unlock file was still in \Android
Then typed fastboot flash unlocktoken Unlock_code.bin.
Agreed the pop-up on the handset. It booted itself to the Splash screen. I disconnected USB & pulled/ replaced battery.
Booted into HBOOT>Fastboot & connected USB
I proceeded to flash the 3 .img files by typing in cmd prompt:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Just for good measure I relocked the BootLoader, as I knew it would restart the phone in Normal boot without me having to interfear with the handset.
I typed: fastboot oem lock in cmd prompt
WHAT HAPPENED NEXT????
Phone reboots
Black screen with double arrows in circle, stays for 30 secs, then...
White htc screen as before EXCEPT THIS TIME I got "quietly brilliant" written underneath & do-di-do-do-do-do jingle.
Phone paused on "quietly brilliant" screen for one-and-a-half minutes......then......the standard phone set-up screens & ON!!!!!!!
YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Handset is working, has all the apps etc as before. The only change is the "about phone" section of settings. It is a bit more basic with the info it yeilds, as software is older than what I had.
I suppose this will change as OTA updates come in. I can live with that for now!!
PHONE IS RESTORED!!!!!!!!!!!!!!!!!!!!!

GERJDOY said:
I was looking for an exact RUU.exe for my ROM: 2.13.401.2 NOT .3 as offered by shipped-roms & others.
After trawling Google I found this: tsar3000.com/Joomla. Clicked downloads tab along the top, chose HTC & scanned down the list. I picked #42 (HTC WildeFire S A510E / A510c / MetroPCS - Marvel / C Stock Roms)
Looking down it I found RUU_Marvel_S_HTC_Europe_2.13.401.2_Radio_47.23a.35.3035H_7.53.39.03M: an EXACT RUU.exe match for my ROM.
<clicked RUU link> took me to a file share website: fileom.com.
Created account, & after verifying by clicking link & email, downloaded RUU.
Then:
1) RELOCKED BootLoader- cmd prompt & typed: fastboot oem lock
The tried a straight RUU.exe flash. This returned the ERROR 140: BOOTLOADER VERSION ERROR etc.
2)Started RUU; went NO FURTHER.
Clicked START on PC. Searched for %temp% folder. Found the two created when RUU is run.
To do this- call up the temp folder. Kill the RUU. Restart the RUU.
Keep doing this and you begin to notice 2 folders will appear when RUU is started & disappear when RUU is stopped.
Checked both to find a .zip called "ROM.zip".
Took it to a new folder so it did not interfere with anything. Unzipped it.
Copied 3 of the revealed files to the \Android folder (my folder containing my ROOTing files- adb/ BootLoader unlock file from HTC/ etc.)
The 3 are recovery.img, boot.img & system.img
Then:
RE-UnLocked BootLoader- opened cmd prompt & typed cd \Android; as my HTCdev Unlock file was still in \Android
Then typed fastboot flash unlocktoken Unlock_code.bin.
Agreed the pop-up on the handset. It booted itself to the Splash screen. I disconnected USB & pulled/ replaced battery.
Booted into HBOOT>Fastboot & connected USB
I proceeded to flash the 3 .img files by typing in cmd prompt:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Just for good measure I relocked the BootLoader, as I knew it would restart the phone in Normal boot without me having to interfear with the handset.
I typed: fastboot oem lock in cmd prompt
WHAT HAPPENED NEXT????
Phone reboots
Black screen with double arrows in circle, stays for 30 secs, then...
White htc screen as before EXCEPT THIS TIME I got "quietly brilliant" written underneath & do-di-do-do-do-do jingle.
Phone paused on "quietly brilliant" screen for one-and-a-half minutes......then......the standard phone set-up screens & ON!!!!!!!
YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Handset is working, has all the apps etc as before. The only change is the "about phone" section of settings. It is a bit more basic with the info it yeilds, as software is older than what I had.
I suppose this will change as OTA updates come in. I can live with that for now!!
PHONE IS RESTORED!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I am glad that your nightmare has ended :victory:

ukyo_tachibana said:
I am glad that your nightmare has ended :victory:
Click to expand...
Click to collapse
THANK YOU!
Yes, so am I. Just really really pleased that I could fix this & not have to rely on professional repair. Also, I am learning SO MUCH about software repair & rooting in the process that it's brillant!
Just waiting for the O.T.A. Updates to come through. I have already had 1 that has upgraded my software from 401.2 to .3. I do a "Check for Update" every 20 minutes or so,
Once this is done, I can reinstall CWM (as I have read that CWM can affect the installation of O.T.A.U.s ). Once I am back to, say 2.26.401.3 software, I will re-install CWM, do A BACK-UP (Hahaha!) & proceed to install SU app./ Custom ROM etc.
Thanks.

can you send me the file ruu......? please
GERJDOY said:
THANK YOU!
Yes, so am I. Just really really pleased that I could fix this & not have to rely on professional repair. Also, I am learning SO MUCH about software repair & rooting in the process that it's brillant!
Just waiting for the O.T.A. Updates to come through. I have already had 1 that has upgraded my software from 401.2 to .3. I do a "Check for Update" every 20 minutes or so,
Once this is done, I can reinstall CWM (as I have read that CWM can affect the installation of O.T.A.U.s ). Once I am back to, say 2.26.401.3 software, I will re-install CWM, do A BACK-UP (Hahaha!) & proceed to install SU app./ Custom ROM etc.
Thanks.
Click to expand...
Click to collapse
can you send me the file ruu......? please