Develop Bugs

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 ((

Bricked diamond...

Alright i have a telus HTC diamond (CDMA) and iv unlocked it with cmonex bootloader (The CDMA version on PPCGeeks). I dont know wut i touched but now my phone doesnt boot into windows, it just keeps resetting... When i type rtask c into MTTY (I can still get into the bootloader) it says
Calibration
No Card inserted
HTC_SMEM_CE_RADIO_DBG_FLAG: 300
Enter Radio Image
Iv tried flashing the sprint shipped rom with radio but that did not work...
does any1 have any idea of how to fix this?

CashMoney18 said:
Alright i have a telus HTC diamond (CDMA) and iv unlocked it with cmonex bootloader (The CDMA version on PPCGeeks). I dont know wut i touched but now my phone doesnt boot into windows, it just keeps resetting... When i type rtask c into MTTY (I can still get into the bootloader) it says
Calibration
No Card inserted
HTC_SMEM_CE_RADIO_DBG_FLAG: 300
Enter Radio Image
Iv tried flashing the sprint shipped rom with radio but that did not work...
does any1 have any idea of how to fix this?
Click to expand...
Click to collapse
You MUST install HardSPL before doing anything else........also, try a hard reset......

i do have a hardSPL... i have 0.43.CMONEX on the phone right now and i already tried hard reset many times but it does not work...

CashMoney18 said:
i do have a hardSPL... i have 0.43.CMONEX on the phone right now and i already tried hard reset many times but it does not work...
Click to expand...
Click to collapse
try this one....
http://forum.xda-developers.com/attachment.php?attachmentid=37669&d=1177280888
good luck

that will brick my phone 4ever... i have a CDMA Diamond... thats a GSM hardSPL not a CDMA hardSPL... i have the right hardSPL that is not the problem...

CashMoney18 said:
that will brick my phone 4ever... i have a CDMA Diamond... thats a GSM hardSPL not a CDMA hardSPL... i have the right hardSPL that is not the problem...
Click to expand...
Click to collapse
Sorry about that. my mistake.........

When did that first occur ?
After flashing Hard SPL ?
Anything we need to know about that ?
Could be that NAND is broken. Do a check on bad blocks.
Cya,
Viper BJK

No it was not flashing of the hardSPL... it must have happened when i was trying to figure out how to change the esn... only thing i cud think of that i did wrong was I did the QMAT security unlock with HTC on command which was in the QMAT manual... but i dont think that would brick it like this... would it? also how would i do a bad block check on a diamond... could u list the commands in order? i dont want to mess it up even more...
EDIT: Well apparently i do have bad blocks... what to do now? is that the reason why i cant boot into windows?
It also says my device name is a samsung... which i dont think is right...
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 523 (0x20B) is bad block
BLOCK 869 (0x365) is bad block
BLOCK 1696 (0x6A0) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x800
Partition[2], type=0x25, start=0xE40, total=0xE900
Partition[3], type=0x4, start=0xF740, total=0xC340
CE Total Length(with sector info) = 0x7C1BA00
CE CheckSum Length(without sector info) = 0x7BA0000
Click to expand...
Click to collapse

bump... for viper 2 c

1. Ok ... what command did you use using QMAT ?
2. Did you change any bootmethod or anything else with for example debugtool ?
The bad blocks seem to be not the problem.

the commands i used in QMAT were "rseed" and "rpass" "set 16 0"
i also followed these steps after the brick
1. Get mtty
2. Connect to USB, press enter
3. Type task 32, enter <--Donno what is it for
4. Type 28, enter <--format DOC
5. Flash CE Rom only
6. Hard Reset
but that did not work either...
Also could you give me some examples of commands on changing bootmethod as im not sure if i used any... and i did not touch any debug tools...

CashMoney18 said:
the commands i used in QMAT were "rseed" and "rpass" "set 16 0"
i also followed these steps after the brick
1. Get mtty
2. Connect to USB, press enter
3. Type task 32, enter <--Donno what is it for
4. Type 28, enter <--format DOC
5. Flash CE Rom only
6. Hard Reset
but that did not work either...
Also could you give me some examples of commands on changing bootmethod as im not sure if i used any... and i did not touch any debug tools...
Click to expand...
Click to collapse
ok here's some tips/ideas:
try typing "boot" in mtty or qmat
if this doesn't get the OS booting then you can try "set 14 0"
if that's no good, then to read config flags you can use "readconfig" (as you have MFG spl), all values should come back as 0x0, if not, let us know.
for bootmodes you can check your current bootmode in oemsbl after rtask a. you can try setting it to 0 ("setboot 0" command after typing "rtask a") but i dont think that's the issue.
(note, all the other commands i listed are not for rtask, only setboot is.)

alright i tried all the commands and heres the results
When i type just "boot" the device just keeps reseting
When i type "set 14 0" it comes back with a string of
HTCST ÚÈÒHTCE
and doesnt do anything
"readconfig" all the values are 0x0 like they should be i suppose
and when trying "setboot 0" it gives me an invalid cmd error while in rtask...

HTC_SMEM_CE_RADIO_DBG_FLAG: 300
doesn't seem to be 0x0. You are sure that all items in readconfig are 0x0 ?
Ok ... it seems that the bootmode is incorrectly set.
Try to "setboot 0" after "rtask a".
That will only work if your device is security unlocked

Yes im sure that there all 0x0... unless im looking at the wrong thing but HTC_SMEM_CE_RADIO_DBG_FLAG is not in the readconfig...
Also it tells me that setboot 0 is an invalid command... and im pretty sure im security unlocked (SuperCID and the bootloader says security unlocked at the top)... only thing i can think of is maybe the 0.43.CMONEX bootloader does not have the setboot command...
Cmd>rtask a
Enter Radio Bootloader
POWER ON PMIC VREG_USB : SUCCESS!
ECHO ON MODE
setboot 0
Invalid cmd!...
readCID
@CID: 00000000
Click to expand...
Click to collapse
EDIT: Alright so i just found this new command "checkimage" and it came up with
Cmd>checkimage
SPL CRC checksum = 0x40142266 CE CRC checksum = bad=0x300
bad=0x45A
0xA069868D ExtROM CRC checksum = 0x0
Click to expand...
Click to collapse
which is where i believe the HTC_SMEM_CE_RADIO_DBG_FLAG: 300 is coming from... any ideas?

Ahh ok .... way better.
Yes, setboot is only available on MFG Bootloader.
As you can see, the CE OS CRC failed. So you need to flash CE OS again.
Be sure that you flash a valid ROM. Try an original one from HTC.
Maybe you've got a connection problem whilst uploading. Try to flash again using another PC
If that doesn't work out, it seems your nand flash is broken.
Cya,
Viper BJK

alright so i flashed the original sprint shipped rom again buh that did not fix the checkimage error... so any more ideas on how i may fix this
NAND broken as in theres no way of fixing it ?
Also i got a tip from someone aty ppcgeeks to flash the radio via rtask... would that make a diffrence as opposed to flashing normally through the bootloader and RUU?

Err flashing via rtask is possible ... but it's really user-un-friendly and more risky
I guess they thought about rwfactory command ...
I'll rethink the options in the next days and will come back to you.
Cya,
Viper BJK

Alright so heres another update on my progress or not so progress... lol
I flashed the verizon CDMA radio that was just released (For the HTC TOUCHPRO but works on the diamond as well) and now instead of the phone resetting it just keeps vibrating right after the touch diamond text/Red info screen...

I really guess your NAND is broken ....

Huge Diamond Problems...

Hi ppl, i have this horrible problem all of the sudden.
I cant seem to get my phone to work sience 3 days ago, i think it has to do with a "Over Flashing Syndrome". I think ive flashed it too many times sience i got it last year. Ive had some really random problems, like some programs not wanting to install at all and programs looking distorted, now lastly hard-reseting it self everytime i Soft Reset and finally now it doesnt even boot even if i hard-reset, it stucks on the "Touch Diamond" start screen, where the radio and ROM version shows... ...
Ive heard something about flashing it to stock to get rid of these kind of problems, can somebody point me to any specific direction that can show me how to fix this? Would be great.
Thanks in advance.

mtty in usb mode, task 29.
Search thread about "strange problem [solved]".

OMG... i cant get this mtty thing to work for me... maybe its Win 7 fault or something...
Gonna try it on the virtual XP ... this is frustrating as hell...

yeah i also had problems with mitty, try with xp it should work

OMFG finally i made it work, i had to install another HTC Sync USB Driver from a thread, then i had to run the original mtty xp in Administrator Mode in Win 7 and select USB.
Now i got this msg after doing what they told me.
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 1506 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Ive read that some Fails happen but are often just ignored.
Im gonna try flashing a ROM now, fingers crossed for me plz.
[Im going to write how i did for further notice, To just clarify some stuff im using Windows 7 build7201:
First of i downloaded and installed the driver in this thread:
http://forum.xda-developers.com/showpost.php?p=3424459&postcount=11
Then i Used mtty in this link: http://forum.xda-developers.com/attachment.php?attachmentid=165433&d=1236782363
and followed these steps:
Procedure:
1. bring the device to bootloader.
2. Launch ActiveSync on PC
3. Go to connection settings
4. Uncheck the Allow USB Connection
Connect the USB to the Phone
5. Now, run mtty1_1_.42_538 on PC.
6. CMD>task 29
7. Flash the ROM of your choice.]
BTW... dont be as dumb as me and still have mtty running while trying to flash ur phone... shut down mtty THEN start to flash ur phone xD stupid me
Love u all here. thanks for pointing me in the right direction!!
EDIT: Its working like i just bought it!! Thanks a lot again, my problem:
SOLVED!!

Glad you got it sorted out buddy.

just like the thread i posted a week ago, and i'm sure more and more like this going to appear,
so please one of the moderators put this one as sticky

well... it happend again for me after 4 flashes... Hard Resets itself--- but MTTY works everytime anyways... so im not worried about having to redoo that step several times....
But something tells me theres more to this problem anywayz... The Hardspl i use is 1.93 --- these new roms go on what 2.09 ? shouldnt there be a hardspl 2.09?`or am i completly wrong?

[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.

Problems when flashing my diamond

I tried to put my diamond on factory default OS.
But when i tried to flash in the tricolor screen with this config
DIAM110 64M
SPL-1.93.0000
MIcroP-DIam (led) v11
PSOC Diam Stage_PVT v0x32
So, when i try to flashing a cooked rom, the progress bar freeze to 0%, and when i try to put some official rom the progress bar is stuck in 1%.
The Mtty shows the next :
CMD
Command error !!!
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 242 FAIL !!!
ERASE block 1026 FAIL !!!
ERASE block 1670 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
The serial number of my phone is HT836KK00873, i try to put some official roms, but i cannot find the way to work on the phone (always the progress bar stop at 1%)
Can anyone help me please ? thanks

jaguar76 said:
I tried to put my diamond on factory default OS.
But when i tried to flash in the tricolor screen with this config
DIAM110 64M
SPL-1.93.0000
MIcroP-DIam (led) v11
PSOC Diam Stage_PVT v0x32
So, when i try to flashing a cooked rom, the progress bar freeze to 0%, and when i try to put some official rom the progress bar is stuck in 1%.
The Mtty shows the next :
CMD
Command error !!!
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 242 FAIL !!!
ERASE block 1026 FAIL !!!
ERASE block 1670 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
The serial number of my phone is HT836KK00873, i try to put some official roms, but i cannot find the way to work on the phone (always the progress bar stop at 1%)
Can anyone help me please ? thanks
Click to expand...
Click to collapse
Hi,
If you want to flash a cooked rom,you must update your SPL to 1.93OliNex.
So,pls update your SPL to 1.93.
About MTTY,you can first run info 8 and task 28.
good luck

Using Mtty without having hspl 1.93 olinex or 1.40 olinex is not a good thing,you may brick your phone

HELICOPTER88 said:
Using Mtty without having hspl 1.93 olinex or 1.40 olinex is not a good thing,you may brick your phone
Click to expand...
Click to collapse
What do you think about that ? My phone is bricked ??
I try to flash with mtty but if you see the version of hspl is 1.93.0000, so i guess thas is a spl signed, cause when i try to put a coocked rom, the progress bar dont move, still in 0% but when i put an official rom the progress bar shows me 1% and stops.
Is there any solution for my problem or i just simply broke the phone ???
Thanks

jaguar76 said:
What do you think about that ? My phone is bricked ??
I try to flash with mtty but if you see the version of hspl is 1.93.0000, so i guess thas is a spl signed, cause when i try to put a coocked rom, the progress bar dont move, still in 0% but when i put an official rom the progress bar shows me 1% and stops.
Is there any solution for my problem or i just simply broke the phone ???
Thanks
Click to expand...
Click to collapse
You may try using http://forum.xda-developers.com/attachment.php?attachmentid=93362&d=1213719705
the you should be able to flash custom roms

HELICOPTER88 said:
You may try using
the you should be able to flash custom roms
Click to expand...
Click to collapse
I try to do what you said (Unsigned-Hard-SPL-Diamond-OliNe) but the progress bar stay in 0% and get an 262 connection error
I starting to think that my cel pass away to a better life

jaguar76 said:
I try to do what you said (Unsigned-Hard-SPL-Diamond-OliNe) but the progress bar stay in 0% and get an 262 connection error
I starting to think that my cel pass away to a better life
Click to expand...
Click to collapse
Did you tried to flash in bootloader mode?
to go into bootloader press soft reset then volume down
What os do you have on your computer?

HELICOPTER88 said:
Did you tried to flash in bootloader mode?
to go into bootloader press soft reset then volume down
What os do you have on your computer?
Click to expand...
Click to collapse
I try the bootloader (see the attachment in the first post), anyway, its the only way to comunicate with my phone
Mi problem is that i cannot upload any rom signed or unsigned to the phone

can't work yet
any ideas please ?
thanks