Develop Bugs

Upgrade an nb0 file with MTTY: problems

Hello everyone, i hope someone knows what the hell my JasJar bootloader have, since i'm trying to flash my device without success.
I've searched everywhere in the forum but found just a message with no reply.
First of all, i've unlocked my jasjar, it's now a superCID device. Or well, i guess so, since i can exec lnb commands.
Here you are the "log" from mtty:
-------------------------------------------------------
USB>task 32
Level = 0
USB>info 2
HTCS00000000 î¢-HTCE
USB>lnb c:\image.nb0
:F=c:\image.nb0
:A=70100000
:O=00000000
:L=FFFFFFFF
start NB image download
Fail to synchronize with the host (1)
USB>
-------------------------------------------------------
Using the "l" command jasjar hangs and MTTY claims a timeout in \\\wcehUSB1 or something after 5 minutes.
Any idea? I've tried with USB2 and USB1.2, tried differend PC models and differend baud but nothing change.
The "info 2" returns a strange SuperCID message. 2 bad.
Any advice is appreciated!
----------Refresh------------------------
I've also tried to upgrade bootloader to v1.1 but still have same issues...

Broken Radio ROM blocks official O2 rom, MaUpgradeUt_noID.exe fails "error 114"....

Broken Radio ROM blocks official O2 rom, MaUpgradeUt_noID.exe fails "error 114"....
Hello
I hope someone here is able to help me.
I have spent the whole of the last 48 hours (no sleep) trying to fix my O2 XDA Exec. I *believe* that I have tried everything suggested on this forum and on Buzz's site but there is just so much on here now that I may well have missed something.
History:
Over the last few months, my phone has gradually got more inconsistent - dropping calls, refusing to answer calls, losing signal and so on. On Jan 1st, I turned it on and it had lost all my settings - Opera reg code, Wifi encryption, O2 net settings, etc.
I spent the last week with sometimes having network, sometimes not. Finally it just gave up altogether. In Settings>System>Device Info, "Radio Version", "Protocol version" and "IMEI" are all completely blank. When booting, the red text states "No GSM".
Reading around this site it appeared that I should be able to reinstall the radio ROM from the official O2 download however this errored with the Incorrect Country Code error. I have carried out full hard resets and still cannot get any Radio ROM visible. I assume that the lack of IMEI is affecting the official O2 downloads?
Since then, I have tried most variations on this site of ROM installs using MaUpgradeUt_noID.exe suggested in the wiki (with and without entering mtty code: "set 14 0").
Full three-part ROM and radio-only ROM install attempts all fail with the Error 114 "Radio Rom Update Error" (the radio ROM is always attempted first).
The only success I have seen was an update of Bootloader from 1.00 to 1.01 which worked completely perfectly and proved that the PC can indeed connect to the XDA when it feels like it.
After two days of earning no money ( I am self-employed) and no money to spend on support, I wonder if anybody has another suggestion for me?
In case it helps: ROM version: 1.30.107 WWE, ROM date: 04/11/06, ExtROM version: 1.30.162 WWE
All advice welcome
Thanks
Leapy

extract everything from the exe and do an upgrade without the radio.nbf

did you read what he said? its the radio that's bad and needs replacing
i don't know, sorry

poussin69 said:
extract everything from the exe and do an upgrade without the radio.nbf
Click to expand...
Click to collapse
I am now totally confused.
I know there was a smiley at the end of your comment, I just can't work out if you are being funny or astute (or both?). Can you explain how reinstalling the non-radio ROMs will help? Would that restore the IMEI?
TIA
Leapy

Midget_1990 said:
i don't know, sorry
Click to expand...
Click to collapse
Thanks for responding anyway. At least I am not crying alone in the wilderness.
It would be terrific to find a fix, though.

Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
http://www.buzzdev.net/index.php?option=com_content&task=view&id=78&Itemid=1

pof said:
Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
Click to expand...
Click to collapse
Thank you for the suggestion, I just tried as you proposed. "Error 114 - Radio ROM Update Error" *sob*!
It's a real shame. It's actually the ideal phone for my needs.
Leapy

1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!

http://forum.xda-developers.com/showthread.php?p=994444#post994444
first as recomended i disabled usb from activesync
then downloaded mtty 1.42
connected the usb and started mtty
chose usb
white screen.....
typed set 14 0...
some gibrish on the screen....
ran the rom update....but it informed me that the rom is not for my device...
typed task 0 in mtty (not sure bout the command but its on page 2 of the forum)
ran the update....nothing same error....
now i saw that my universals screen was blank....
removed the battery....and then restarted my universal....
this might help you...
rtask 0/1/3/4

pof said:
1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!
Click to expand...
Click to collapse
Thank you. I think I did everything exactly as you instructed.
Please find attached the zipped log file.
I would welcome your advice.
Leapy

Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not

Error 114: Radio Rom Update Error
WOW I have the same problem.....
but this commands for mtty...did nothing to my problem.
ERROR 114: RADIO ROM UPDATE ERROR
I don't know if that helps you....on my PDA it says Upgrade Radio Stack Please Wait...
I have the perfect phone....but it is not a phone anymore...and I go crazy.
Is there any way to update the radio rom from SD card??
Please Help

posted reply to incorrect post - cannot delete post - ignore. Please see next post.

pof said:
Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not
Click to expand...
Click to collapse
Well, I too am a little "crazy" so I did as you suggest.
I tried to put Buzz's "unlock" radio v 0.0.0.0 ROM on using MaUpgradeUt_noID.exe. And guess what, it fails again but with a different error!
Error 150: ROM UPGRADE UTILITY ERROR. "This rom upgrade utility is not designed for your device. Please get proper ROM Upgrade Utility and try again!"
I attach the USB Monitor log if it proves any use?
I will try and use the official O2 ROMs and see how that goes.
Thanks again for your assistance, I truly appreciate it.
Leapy

To Leapy...
How did this problem started to you??
I have been using this phone for 1 week, after that I changed my SIM card with another one called MAGIC-SIM card, (programmable) with 8 SIM numbers.
After that day ALL the **** started!!!!!
I had problems during my dialing the number on phonepad...
when I was trying to make a call... it hang up.
After some soft reset...it didn't ask me for PIN.
After a hard reset.... on boot screen it said NO GSM
and then on antenna icon on the top of the screen the antenna had a little x on the right side.
Then the known problem ERROR 114: RADIO ROM UPDATE ERROR
I can update any rom I want but not the Radio ROM

leapy said:
I will try and use the official O2 ROMs and see how that goes.
Click to expand...
Click to collapse
well, I tried the O2 update and just got the generic "CID" error - twice. So I guess I am no nearer fixing this issue...
All advice welcome.
Leapy

leapy said:
Well, I too am a little "crazy" so I did as you suggest.
[...]
I attach the USB Monitor log if it proves any use?
Click to expand...
Click to collapse
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.

my friend got the exact same problem with his EXEC, and send it back to O2, they charge him apprx USD500 for mainboard replacement.....(fiuhh.....)

pof said:
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.
Click to expand...
Click to collapse
Thanks for your continued assistance.
I tried twice with the 0.0.0.0 radio ROM and this time the error has reverted to Error 114 again. With both these attempts, I noticed that the displayed "currently installed" ROM versions were blank - previously I saw the actual on-board version numbers. Not sure if that indicates anything?
Capture logs attached:

leapy said:
Not sure if that indicates anything?
Click to expand...
Click to collapse
That indicates you previously had activesync enabled and now don't.
Exactly same error as before, radio bootloader is not responding when the RUU sends 'rinfo' and 'rerase' commands to it, then the RUU gives up trying.
You can backup the radio ROM from another device with "d2s 60000000 00800000", and theoretically you should be able to load it into yours by using "L" command... but I'm not experienced with universal bootloader and can't say for sure if this will work and the right commands to do it... so please wait until someone reads this and can help you more than me, or research by yourself if you have the time to do it

Radio ROM upgrade FAILED (NO GSM)

i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.

farehmani said:
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
Click to expand...
Click to collapse
Radio rom upgrades are definately more reliable with the original cable. I have read somewhere in these forum that the mode of radio ROM upgrade is different from other ROMs (CE and Ext rom) this is the reason why it takes more time than the CE rom although the later is much larger in size. I suggest you try again if possible on a different PC. For some strange reason I can upgrade my Radio ROM only in my office PC.

d_ranade said:
Radio rom upgrades are definately more reliable with the original cable. I have read somewhere in these forum that the mode of radio ROM upgrade is different from other ROMs (CE and Ext rom) this is the reason why it takes more time than the CE rom although the later is much larger in size. I suggest you try again if possible on a different PC. For some strange reason I can upgrade my Radio ROM only in my office PC.
Click to expand...
Click to collapse
i have tried on 3 different computers but it doesn't work. also with original cable too. it is definately a software problem as no physical damage was made to my device. there must be something that fixes it.
still while upgrading Error 114. (UNABLE TO UPDATE RADIO ROM)
i wish i could find any help with this...
Farehmani

farehmani said:
i have tried on 3 different computers but it doesn't work. also with original cable too. it is definately a software problem as no physical damage was made to my device. there must be something that fixes it.
still while upgrading Error 114. (UNABLE TO UPDATE RADIO ROM)
i wish i could find any help with this...
Farehmani
Click to expand...
Click to collapse
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?

apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
I too find that upgrade in Bootloader is more reliable.

To let you into a little secret.. I ALWAYS flash now in Bootloader mode.. I have only had a couple of "bad flashes" but all of them were direct from a running OS...

I have sent you a pm, that should solve your issue. Please check your pm's...
Take care,
-Jwrightmcps
farehmani said:
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
Click to expand...
Click to collapse

apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
yes... i have never tried to flash anything while being in the os. always switch my device to the bootloader first. I have BootLoader 1.01
Please help!!

apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
How to put the PPC in Bootloader (Qtek900)?

myname70 said:
How to put the PPC in Bootloader (Qtek900)?
Click to expand...
Click to collapse
Read the wiki - the answers are in there.

apd said:
Read the wiki - the answers are in there.
Click to expand...
Click to collapse
the problem is still there....
i have tried circumvent bootloader password too... and getting error like Win32 Error, Cannot read from the specified device when HEX of password is placed on the memory field of WinDbg.

Tried Another solution for NO GSM but no luck !!
okay here goes; your quoted link had point#5 for no GSM when booting so i followed it as given below.
Pls. see the comments in (( )) for how i conduct these steps and what value is returned.
[[[[--->
Problem 5: Device shows NO GSM when booting (( I'm having this problem ))
1) The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
2) Device won't start after trying to unlock it with HTC Universal Unlocker (HTC_Uni_SIM_Unlock_v1)
Here is how to fix it:
1)Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections". (( Done! ))
2)Put your Hermes (( Universal )) in bootloader mode
3) Connect device to computer using USB cable. (( Done with Original Cable ))
4) Open mtty.exe and select USB port, then connect.
Hit enter twice, you will see the "USB>" prompt. (( Okay but i usually get the USB> prompt with single hit of Enter ))
Type the following commands (do not copy paste!!!) (( I type them ))
USB> password 0000000000000000 (( Returns: HTCSPass1.CMˆËHTCEUSB> ))
USB> set 1e 1 (( Returns: USB> ))
USB> erase a0040000 c80000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a0cc0000 c80000 ((Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a1940000 640000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> set 1e 0 ((Returns: USB> ))
(( Then i close the window of MTTY and proceed to step 5 ))
5) Reset your phone and put it back in bootloader mode (( Here i take my Universal off the usb cable, soft reset it with the stylus and without letting it to boot i switch it into the bootloader mode again and get "Serial & v1.01" on the screen's header and footer ))
6) If your bootloader version is different than 1.04 then Flash Bootloader version 1.04 (( I simply ignore this step as this could be for Hermes users only not for UNIVERSAL Users - Pls. correct me if i'm wrong ))
7) Flash the patched radio used to simunlock the Hermes (( I do it with HTC_Uni_Unlock_v1 it has radio version 0.00.00 BUT still it gets stuck at 0% and after sometime gives the same error 114. Cannot Update Radio ROM ))
Your phone should be alive again (( Its Not ))
<---]]]]
i don't think i'm doing anything wrong here... just the step 5 of bootLoader Update to 1.04...
what comes in your mind ???
i'm desperately missing my pda. its begun to hurt now... please help me rescue my baybee....
farehmani

farehmani said:
i don't think i'm doing anything wrong here... just the step 5 of bootLoader Update to 1.04...
what comes in your mind ???
i'm desperately missing my pda. its begun to hurt now... please help me rescue my baybee....
farehmani
Click to expand...
Click to collapse
Don't worry, mate, you're almost there...
Don't worry about the bootloader version, that is just for the Hermes (Universal will be 1.01 or under for G3, 2.1 for G4). If it's under 1.01 it would be worth upgrading to 1.01 which you can find on the ftp.

SpyderTracks said:
Don't worry, mate, you're almost there...
Don't worry about the bootloader version, that is just for the Hermes (Universal will be 1.01 or under for G3, 2.1 for G4). If it's under 1.01 it would be worth upgrading to 1.01 which you can find on the ftp.
Click to expand...
Click to collapse
glad to know about my being almost there... still i wonder whats keeping me away from retaining my device...
i have already got BootLoader 1.01...
what other method should i apply to get it working again?????

I have the same problem, but not in Universal, but apache, jwright help me.

i have the same problem can smeone help

Try this
"Type "task 28 55aa" and hit enter.
This will restore the DOC partition to its original layout and delete all data
including the ROM!
Once finished you must use the "Original OEM ROM" (i.e. JASJAR WWE
1.30.76) that is made for your device and update with it (CE,Extended
and Radio).
Also if your device bootloader version is lower than "v 1.01" you should
update that first (before installing the OEM ROM, but NOT before "Task
28 55aa").
After this is complete you may then use your device again.
Please let me know how things work out for you...
Take care,
-Jwrightmcps"
It solve me...

i am having the same problem with exec it shows me no gsm and when i go to the device information it does not shows the radio ver and my phone imei is 0 can someoe please tell me how do i solve the problem i had read this tread but not understand it can someone please explane me how do i solve the problem

shedragon said:
"Type "task 28 55aa" and hit enter.
This will restore the DOC partition to its original layout and delete all data
including the ROM!
Once finished you must use the "Original OEM ROM" (i.e. JASJAR WWE
1.30.76) that is made for your device and update with it (CE,Extended
and Radio).
Also if your device bootloader version is lower than "v 1.01" you should
update that first (before installing the OEM ROM, but NOT before "Task
28 55aa").
After this is complete you may then use your device again.
Please let me know how things work out for you...
Take care,
-Jwrightmcps"
It solve me...
Click to expand...
Click to collapse
thanx for your suggestion!
i had tried this already... but the problem is beyon this...
i discussed with pof and he said that somehow i screwed up with the qualcomm chip where the radio bootload resides. so it needs replacement.
anyways... thanx budd... i appreciate your support too...
regards...

my hermes having this problem also ((

MTTY with bootloader 2.01.

I try to reset call duration on my Universal bootloader 2.01. I've done this for bootloader 1.00. But when I try "rtask b", it show:
Radio AT command debug with security check.
Read singal error D3
SD read fail!
Wait interpeter timeout
AUX_Process- FAIL, reason 13, dwRead=32, dwWritten=41
And stuck, cant type anything, the device stucks also. I try "task 32", and then "rtask b" => nothing changes. Anyone who can try this on 2.01, please tell me how can we pass this??
Thanks.

Topic closed.

[HELP] Days with a bricked Diamond

Day2 with a bricked Diamond....
=================================
Background
==========
Happened while trying to flash EnergyROM released 7/22
WinXP, not on any USB Hub, and on Unsigned-Hard-SPL-Diamond-Olinex.
The vol down + back + reset method doesn't go to completion (I have had no issues with BsB roms so far using this method), on the Diamond it shows :
--------------------------
00018003
DIAMING.nbh - FAIL
OS - FAIL
Update Terminate
UPDATE FAIL
--------------------------
If I try to soft reset the screen shows the classic bootloader screen, and the RUUNBH at the top-right:-
-----------------------
Diam100 64M
SPL-1.40.OliNex
MicroP-Diam (LED) v.11
-----------------------
PSOC-Diam STAGE_PVT v0x30
Upgrade ROM code error
Please try again
--------------------------------------------
I am able to re-flash this HardSPL (and in doing so removes the ROM Upgrade Error and enter into Bootloader mode (vol down + reset) successfully.
I am also able to re-flash my Radio (Diamond_Radio_1.00.25.05.nbh).
Any rom however that I then try to flash using CustomRUU/ROMUpdateUtility does not work, it always gets stuck at around 20% with the below error:
---------------------------------------------------------
ERROR 226 : FLASH WRITE
Flash write error happened. Pls check your PDA phone.
---------------------------------------------------------
I read that I am supposed to be trying signed ROMs that work with my HardSPL, and went to this thread to get one, but same thing it is also stuck at 20%.
http://forum.xda-developers.com/showthread.php?t=400411
Have also tried the below MTTY method describe in some of the Kaiser (Yes, pretty desperate, getting stupid) threads:
======================================================================================
1. Download mtty.exe from here: http://taeguk.co.uk/xda
2. Disable activesync (connection settings -> uncheck "allow usb connections")
3. Kill the following two processesto stop active sync; rapimgr.exe and wcescomm.exe (Ctrl+Shift+Esc, select from the list of processes).
4. Connect your Kaiser to PC using USB cable.
5. Open mtty, select USB port and click OK.
6. Hit ENTER twice, you should see the "Cmd>" prompt.
7. Type the command "boot", you should see something like this:
Cmd> boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
======================================================================================
...except that I don't get the above lines after executing the boot command, instead I see:
--------------------------------------------------
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fill RSVD information for block 288 to 321
Storage start sector=0xFF40, total sector=0xB080
Storage start block=1054, total block=706
Total Bad Block in CE: 1
Erase physical block from 1345 to 2032
si backup: Erase physical block from 2032 to 2048
Fixed new dwPSImageSize = 0x5640000
--------------------------------------------------
...and my Diamond boots to the "Touch Diamond" screen with the black backdrop. Can someone help?

try to connect the phone with mtty and type task 29.
this should format your phone.
then connect it with activesync and flash a stockrom onto it.
it that works, try flashing a design rom.

Dude, thanks for your reply... I got the following, this means it failed right?
------------------------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 226 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>

epiphone said:
Dude, thanks for your reply... I got the following, this means it failed right?
------------------------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 226 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>
Click to expand...
Click to collapse
try flashing a stock rom. you can download it from the htc website and see what happens.

Dude....Tried this stock rom (actually I tried before trying what you suggested), it still didn't work; the flashing process still stuck at the same place 26%.
RUU_Diamond_hTC_Asia_HK_WWE_1.34.831.1_52.24.25.08_0.93.25_Ship

found this in another thread :
type (dont copy&paste):
task 28
and press enter
If the result is the following then you are out of luck:
flFormatPhysicalDrive:status=23
DOC_format failed!

Got this:
Cmd>task 28
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0xFF40, total sector=0xB080
Storage start block=1054, total block=706
Total Bad Block in CE: 1
Erase physical block from 1345 to 2032
si backup: Erase physical block from 2032 to 2048
Format end
Cmd>
Trying stock rom again.....

on my old phone i had to type
format BINFS
to format the flash. you could try that.
if the rom flash still does not work.
you seem to have a bad block on your internal memory. i am not sure how to get around that.
a stock rom fills the entire rom space with new information. that might introduce problems as well.
maybe you should also try a design rom (not the energy one, because that is a large rom)
try the bsb or deepshining. they have less information and might not use the memory at block 26.
if that does not help, you will have to find people with more knowledge than me.

Still can't flash the stockrom still stuck at 26% after trying task 28...
I can't get the format BINFS command through:
Cmd>format BINFS
Command error !!!
Thanks for your time anyway dude... appreciate it.

try searching , i also found this
http://forum.xda-developers.com/showthread.php?t=296722

*deleted repeated post

*deleted repeated post

Dude.. no offence but that I thought is for Hermes, not HTC Diamond? Also that thread seems pretty old...?

Bump... anyone can give other suggestions?

disconnecting any USB device
epiphone said:
Still can't flash the stockrom still stuck at 26% after trying task 28...
I can't get the format BINFS command through:
Cmd>format BINFS
Command error !!!
Thanks for your time anyway dude... appreciate it.
Click to expand...
Click to collapse
try disconnecting any USB device the PC, including Pendrive (leave only the diamond connected), then flash the stock rom

epiphone said:
Dude.. no offence but that I thought is for Hermes, not HTC Diamond? Also that thread seems pretty old...?
Click to expand...
Click to collapse
i am sorry that there is not a solution on a silver platter.
so after reading my link things you could try:
the hardspl is made by the same person. maybe he included the task 2a in your spl as well?
apparently fixing a bad block can be done with a hardspl. maybe you can send the guy creating the hardspl a personal message with your problem.
get your magic wand, wave and say "reparo"
throw your phone out the window or send it for repairs.

Dude, thanks for your answer, nothing helped me still...
I have tried to PM the SPL makers, but quite sure they wouldn't have time to respond Eventually i have had to book my Diamond in for repairs, not sure what is the cost/repair.
My problem now is what should I do in future, since I figure I will flash again... don't see what I done wrong that can suddenly cause this to happen in the first place... I have been flashing for about a year now.

epiphone said:
Dude, thanks for your answer, nothing helped me still...
I have tried to PM the SPL makers, but quite sure they wouldn't have time to respond Eventually i have had to book my Diamond in for repairs, not sure what is the cost/repair.
My problem now is what should I do in future, since I figure I will flash again... don't see what I done wrong that can suddenly cause this to happen in the first place... I have been flashing for about a year now.
Click to expand...
Click to collapse
there is never any garantee for flashing.
things you can try are the same as the things you tried to restore your phone.
so format or flash a stock rom, before a custumized rom.
do not try every rom, but just the ones that seem professional.

i know this is old topic but i want to contribute.
just today had sort of same issue, except my device flashed full until the end where RUU replied error and the device got stuck spl with RUUNBH. i did task 29 and the flashed a stock htc rom and that fixed issue. just like that.

Hello Everyone!
I'm having the same issue as OP, but I tried task 29, task 28 55aa, task 28, and neither worked for me. The flash of a single OS stucks at 76% with flash write error (226), I've searched the forum for hours, but none of the same flash error code issues was mine. I can reflash radio, but not the os, my hardspl is olinex 1.93, when I reflash the radio it start and stucks at the Touch Diamond screen with the radio and stuff number on the right side. If I then try to flash a rom (even stock rom from HTC site!) It freezes around 65% with the same error. If I command in mtty task 16 0, then again it freezes on the Touch Diamond screen. Please anyone can help?
UP: Got it resolved!! My internal flash is damaged, coz if I flash a 60Mb rom, it succeedes, if I flash a rom with over 80mb in size, it fails.