Database Info

error when flash rom

I try to flash my vodafone PDA 1615 (tytn II vodafone ITA), but the HardSPL dont install correctly.
When I on my PDA boot the boot loader standard 3 colors (whitout unlock CID).
I try to flash the original WWE HTC rom, but the flash program dont work whit my Tytn vodafone.
I try the mtty program but the PDA freeze on splash screen vodafon whit the radio and os version number on low-right of the screen.(the mtty freeze whit this text:
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0x78C0, total sector=0x13A00
Storage start block=504, total block=1256
Total Bad Block in CE: 0
Erase physical block from 792 to 2032
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
I search the vodafone ship rom but I dont find
help me please
and sorry for my english
lucadeejay

I also tried to flash other vodafone rom recostructed (UK, German, Spanish and Italian) whitout luck.
I use the mtty for see my right and I the "FF".
the boot loader write on 3-colors screen:
KAIS130
SPL-1.56.0000
CPLD-8
the command in mtty:
set 14 0
task 8
reset the device but load the bootloader
thx
luca

MDA VARIO 3 stuck at RGB screen! PLEASE HELP

Help!!! MY hardspl flashing is not moving at 18% i dare not unplug or do anything! its been 5 minutes and its supposed to take a minute onli? PLSSSS HELP!
UPDATE: says there was a communication error, i followed the recovery steps, and from there tried to continue. But then it said ready to continue update, but then cant connect! I'm stuck at tricolour with the word USB at the bottom. MDA Vario3 here. PLEASE HELP ME!!

BUMP please help me guys.....please...

bump out of desperation. please guys....i'm sure u guys know what to do, so please help me

Baronic said:
bump out of desperation. please guys....i'm sure u guys know what to do, so please help me
Click to expand...
Click to collapse
flash to your original shipped ROM via MicroSD card.

I've searched everywhere via google and even XDA forum, but i can't find an original T mobile Rom.

try flash it with diffirent bootloader ( spl ) en try it again.

All wrong!
If you stuck in the 3 Color Mode ... then ... you havent Read the First Post carefully!
To fix it ... Download the Programm MTTY -> Deactivate Active Sync -> Connect with MTTY over USB -> Enter "Boot" without ""
Then you must stay in your OS!
Then Read the First Post of the HardSPL Threat.
Copy SSPL to your Phone and not to the SD-Card or something like else. Start it -> You are in the 3 Color Mode with 1.16.Jump -> Flash HardSPL again!
If MTTY Boot not work, you can Try the OEMSBL and use the Command "cego"
If you have device ****ed up ...
You must know, what CID your Device have ... Iif you have buy your Phone in UK ... possible your CID is UK or WWE. Download a Full Rom with CID WWE or UK and Flash it! It restore your SPL, OS, Radio, ....
If any think stand about wrong ID ... you have use the wrong ROM with the wrong CID ... search for a other Rom and try it!
I mean not Cooked or Edit Roms!!!!!!! I mean Full HTC Roms!!!!!!!
If you doesnt find anything ... try www.htc.com -> eclub and hope your IMEI is permited to use it :->

Thanks NetRunner AT for a detailed reply! I did read up and found out about MTTY, but i didnt have any rom to flash since i havent CID unlocked it. I'm now trying from this link
http://forum.xda-developers.com/showpost.php?p=1586817&postcount=2
hopefully something there works. Will update this thread also for future people who face the same problem.
UPDATE: After using "boot" with MTTY i get a pda with a screen that changes from 3 colour > White > Gray > 3 Colour and continue.....so....what do i do now? I also cant flash the original rom, stuck at 0% with communications error

Dude, The people above, while trying to help, & that's nice, are giving you incomplete information.
Please PM me & I'll help you figure it out. The first thing I'd like you to do is run a diagnostic. (Like any good recovery specialist would have you di, FIRST)
Use MTTY, make sure to change the "Flow Control" to RTS/CTS, & when you get to the cmd> prompt enter like this: cmd>info 8
Post the return or even better, PM it to me so we can see what went wrong. You can tell by the location of the bad blocks where the issue is.
I also need to know what your SPl version is, because different spl's can have different valid commands.

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 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 529 (0x211) is bad block
BLOCK 965 (0x3C5) is bad block
BLOCK 967 (0x3C7) is bad block
BLOCK 969 (0x3C9) is bad block
BLOCK 971 (0x3CB) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x700
Partition[2], type=0x25, start=0xD40, total=0x8800
Partition[3], type=0x4, start=0x9540, total=0x11D80
CE Total Length(with sector info) = 0x4AEAA00
CE CheckSum Length(without sector info) = 0x4AA0000
as for the spl i'm not sure if its right since i was halfway Hard-SpLing when i had a communications error.
but this is what i see
KAIS130
SPL-1.56.0000
CPLD-8

Solved
Glad I could help you out!
Another notch on my belt. Close this thread.

Seems that I bricked my vario III as well :(

EDIT: Before you read on... The issue has been solved. If you screwed up flashing this thread might contain some information on what to do..
I really thought I read up quite well before attempting to flash my vario III.
Since this is my first attempt at hardspl-ing / flashing I was quite nervous to do stuff wrong..
so you might guess.. it went kind of wrong.
I started of, following instructions on screen. Untill I got the tri colored screen. There it went wrong since I pulled out the usb cable too soon. (I don't think It was copying files yet)
the screen reads:
KAIS130
SPL-1.93.Jump
CPLD-8
..
USB
Now at the moment my phone is still on tri colored screen.. (with usb noted at the bottom).. but it's no longer recognised by activesync... and also the kaiserunlock tool is saying it couldnt connect anymore.. (I see the three step buttons, step 1 and 3 are blanked.. step 2 is clickable...)
thus.. i ****ed up. I'm uncertain what to do now. I read about the 16% copy error and that MTTY could be used with the boot command.
Should I reset the device before I use MTTY? Since I tried MTTY while the phone is in tricolorscreen and this is it's feedback:
Cmd>boot
Command error !!!
Help me please..

I did exactly the same earlier today but I found this post got me out of trouble.
http://forum.xda-developers.com/showthread.php?t=342032
Good luck

.....It came from this thread - ninth post down
http://forum.xda-developers.com/showthread.php?t=345250

A bit below my post is someone who is in tri color screen as well...
I did the info thingy..
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 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x700
Partition[2], type=0x25, start=0xD40, total=0x8680
Partition[3], type=0x4, start=0x93C0, total=0x11F00
CE Total Length(with sector info) = 0x4A29E00
CE CheckSum Length(without sector info) = 0x49E0000
Cmd>
Cmd>info 2
HTCST-MOB003|Q|cHTCE
Is it safe to (soft or hard)reset the device?

Ahh I guess I didn't read enough
-McMex

@ belchie:
Sry.. I have looked through your links, cant see how those threads would help me? As far as I understand I don't have hard-spl and thus rom flashing is no go..right ?
Is it safe to (soft or hard)reset the device (since it's now running in battery only mode)?

Since the battery didn't charge in tricolor mode I decided to give it a softreset...
black screen.. no reaction to softreset....
my head became red.. I thought I really bricked it..
hard reset... no reaction...
oh oh..
powerbutton...
Tmobile bootlogo...PFJEW!
think it was just (s)spl loaded.. and no file copying had been started.. Gonna give it another go tomorrow
This thread can be closed. Thanks.

Extreme radio issues

So today my radio issues have just pushed me over the edge. I have flashed every known radio to man. I just can not get the device to 1) keep a cell connection for over an hour or 2) reconnect to the outside world after rule 1 fails, no matter what i do short of a flash. What i want to do is COMPLETELY wipe every known trace of the existing radio and reflash it. Is there some way of using mtty or another great tool to totally wipe my radio out of existence?

Here is what info 8 returns via mtty
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 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
Partition[0], type=0x20, start=0x2, total=0x3E
Partition[1], type=0x23, start=0x40, total=0x580
Partition[2], type=0x25, start=0x5C0, total=0xAF00
Partition[3], type=0x4, start=0xB4C0, total=0xFE00
CE Total Length(with sector info) = 0x5ABA600
CE CheckSum Length(without sector info) = 0x5A60000

1.65.24.36
the0ne.john said:
So today my radio issues have just pushed me over the edge. I have flashed every known radio to man. I just can not get the device to 1) keep a cell connection for over an hour or 2) reconnect to the outside world after rule 1 fails, no matter what i do short of a flash. What i want to do is COMPLETELY wipe every known trace of the existing radio and reflash it. Is there some way of using mtty or another great tool to totally wipe my radio out of existence?
Click to expand...
Click to collapse
did u include flashing the 1.65.24.36 radio in ur trials?
as i recall that radio was the only radio u can "flash to" to escape the clutches of the latest niki radios that were unable to flash away from for non CID unlocked devices...any other radio u would try to flash to would give an error so im guessing it completely overwrites existing radios
try it if u havent

What radio did you flash? What device do you have? Where do you live?

Currently i am running 1.70.olinex, but i have flashed every stock rom, and every radio known for the kaiser, including various niki and polaris radios. I have also done 3 different spl's, 1.0.olipof, 1.1olipof, 3.56 hard2.

that's a patched radio, used for unlocking
flash a different radio
http://forum.xda-developers.com/showthread.php?t=393182

[Q Expert] Semi-Bricked TP2 - Tried: Flash ROM, StockROM, HSLP, Radio, Task8,28,29...

EDITED: Phone started working after coming back to the US and getting a CDMA signal.
Original Reference Thread: PPCGeeks.com Windows Mobile > WM HTC Devices > HTC Touch Pro 2 - Bricked Phone from Advanced Settings = Glyph Cache 32KB + File Cache Auto (Energy ROM)
I bricked my phone after using the Advanced Settings to change the Glyph Cache to 32KB and enabling File System Cache to Auto. Got prompted to Soft-Reset and phone went into boot screen loop.
Here's what I tried with no help:
Reset to Factory Settings (Power + Up)
Reflash newer Energy ROM 21916 RHODCDMA Cookie 2.0 Apr 26 2011 from April 19 2011 version that I used before
Reset to Factory Settings Again
Radio Reflash 2.32.00WU
Task29
HardSPL 1.01 (1.00 Olinex)
Phone always goes to Touch Pro 2 black boot screen, stays there for a little while and reboots.
I'm baffled on how a setting inside the WM OS can break the phone and make it unfixable after ROM reflashing... twice and factory resets.
Only thing unusual is that I'm on vacation and I now use a SIM card in this phone since there is no CDMA service here. Before this screw-up everything was working great.
Since nothing worked I have to go back to flashing a stock Sprint ROM and start from scratch. Seriously, WTF went wrong with Advanced Settings?
Bad news, something serious got screwed up on this phone.
Task29 done
Stock ROM Flashed - RUU_Rhodium_W_WM65_Sprint_WWE_2.04.651.4_RS_2.32WF_NV_SPCS_2.20_0224_PRL60660_Ship.exe
Interrupted at 4% and went into ROM Error Recovery successfully, Stock ROM flashed successfully
Hard Reset (Power + Send + End) + VolUp + VolUp
Nothing worked! Phone is now stuck at white and green HTC boot screen, same as before black Touch Pro 2 screen.
WTF did Advanced Settings do to brick this phone so badly with Energy ROM?
I've been flashing ROMs and radios and SPLs without issues for years, but one usage of Advanced Settings screwed this phone like a pooch. I'm a bit pissed since this is my Wife's phone and we're away on vacation where we need the phone for SIM card access internationally.
I've tried flashing some more things to the phone thinking that the Radio is corrupt or something, but nothing works.
Sprint Radio 1.96WV
Sprint Stock ROM again
I wonder if the phone requires CDMA signal somehow when it is reflashed with radio or something to initialize some parameters however here there is no CDMA, only GSM. I've rebooted the phone here and it came back up normally, but after the soft-reset from Advanced Settings app it got screwed completely.
I tried some more things.
Task29 - Works because boot screen changes to black Touch Pro 2 and it gets stuck there permanently.
Radio - 2.32.00WU (Sprint) World Unlocked for SIM card
Stock Sprint ROM again...
After this, I might have to resolve to finding some mtty commands to see if there is anything that I can do with those.
Phone is still bricked. I'm trying some MTTY commands to see if clearing it all and starting fresh might worked. I did task 28 and task 29 twice and below is the output from the second run. I'll reflash the stock Sprint ROM to see if it goes anywhere.
mtty 1.42 to USB
Code:
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSRHOD4000HTCE
Cmd>task 28
Format start
Fill RSVD information for block 351 to 384
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
Cmd>task 29
Format BINFS start
CE start start block=384, total block=3712
ERASE block 768 FAIL !!!
Write 0xFF start page=0x6000, total page=0x3A000
Format BINFS end
Cmd>ResetDevice
Phone is still screwed. I couldn't find a list of HardSPL 1.00 Olinex commands and registers either to fix this problem. This has now taken half of my vacation day.
Code:
Cmd>set 16 0
Cmd>task 8
I'm hoping to find something from within mtty commands to help me. Here's some info about my phone in case anyone sees something not right or some kind of an explanation as to why the phone bricked itself.
Code:
md>info 0
Platform Model ID:RHOD40000
Platform HW Board ID:4, UNKNOWN
Cmd>info 1
Cmd>info 2
HTCSSPCS_001ćž7HTCE
Cmd>info 3
HTCSRHOD40000
Cmd>info 4
HTCSSPCS_001ćž7HTCE
Cmd>info 5
Cmd>info 6
HTCST ÚČŇHTCE
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: Rhodium_W, Bootloader Version : 1.00.OliNex
Built at: Jul 16 2009 21:25:07
Copyright (c) 1998-2006 High Tech Computer Corporation
Board ID=0x4
CPU ID=0x4117B362
TURBO HW =1
TURBO SW =1
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_kby00n00hm
DEVICE ID=0xBC
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 4 (0x4) is reversed block
BLOCK 5 (0x5) is reversed block
BLOCK 7 (0x7) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 20 (0x14) is reversed block
BLOCK 21 (0x15) is reversed block
BLOCK 22 (0x16) is reversed block
BLOCK 23 (0x17) is reversed block
BLOCK 24 (0x18) is reversed block
BLOCK 25 (0x19) is reversed block
BLOCK 26 (0x1A) is reversed block
BLOCK 27 (0x1B) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
BLOCK 32 (0x20) is reversed block
BLOCK 768 (0x300) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x980
Partition[2], type=0x25, start=0xFC0, total=0x1AD40
Partition[3], type=0x4, start=0x1BD00, total=0x1E300
CE Total Length(with sector info) = 0xDF5E800
CE CheckSum Length(without sector info) = 0xDE80000
Cmd>info 9
Fixed new dwPSImageSize = 0xDE80000
Storage Start Addr=0x5E2C0000, length:0xDF3E600
Trying some more things.
Stock Sprint ROM - Flashing from SD card with RHODIMG.nbh.
Stock ROM flash from SD completed successfully but still same issue. New white green HTC boot screen with same looping reboots.
Never get to the red radio version codes, just like after first reboot.
Click to expand...
Click to collapse

Update in other thread since yesterday, still won't work.
F.A.T.M.T.I.D.Q:
(Frequently Asked TOO Many Times Infuriating Damn Questions):
-------------------------------------------------------------------------
1: "After task 28, I get this output in MTTY: Total Bad Block in CE: x"
2: "After task 29, I get this output in MTTY:
ERASE block xxx FAIL !!!
ERASE block xxx FAIL !!!"
(where x is a random number)
This has been asked 100+ times in the Diamond thread so this is the final time I will answer:
IT MEANS NOTHING..NADA..ZIP! I have not experienced ANY problem with this output...Please stop asking!
------------------------------------------
Click to expand...
Click to collapse
According to the THE DEFINITIVE MTTY thread on XDA the bad blocks mean nothing, guessing that they get marked as bad in the BINFS file table and won't be used, that's all, same as FAT bad blocks.
Still hoping to find a solution, just wish to engage more experienced folks to inform me about more direct diagnostic and possible repair procedures since I've exhausted the limits of my very limited ROM flashing knowledge.
However, I'm on vacation in a foreign country and my wife's eBay purchased phone goes Tits Up on the second day so replacing it is not an option in so many words. Best I can do is tomorrow give her my identical TP2 and import her contacts.
horndoctor said:
Have you tried removing your sim card then hard reset and/or put it in bootloader then flash shipped 6.1 rom? :dontknow:
Click to expand...
Click to collapse
I tried the Sprint 6.5 ROM but I'll give the older 6.1 ROM a try after the download finishes. I don't know why the 6.1 ROM would be any different than the 6.5 one but I'll try anything at this point.
PPCGeeks > Windows Mobile > WM HTC Devices > HTC Touch Pro 2 > CDMA TP2 Development - [STOCK ROM COLLECTION] RhodiumW Stock ROMs [Telus VZW SPCS USC] UPDATE 3/19/10
RUU_Rhodium_W_Sprint_WWE_1.21.651.3_RS_1.96WF_NV_S PCS_1.42_0430_PRL60652_Ship.exe
I have an identical HTC TP2 that works and I'm wondering if doing a memory dump from one phone and loading it to the other might somehow revive the broken phone. I have mtty working but don't know enough on how to use it or if it will even work.
JakFrost said:
I tried the Sprint 6.5 ROM but I'll give the older 6.1 ROM a try after the download finishes. I don't know why the 6.1 ROM would be any different than the 6.5 one but I'll try anything at this point.
RUU_Rhodium_W_Sprint_WWE_1.21.651.3_RS_1.96WF_NV_S PCS_1.42_0430_PRL60652_Ship.exe
Click to expand...
Click to collapse
S.S.D.D. - Same **** Different Day
Didn't work either.
Trying some more things.
Relocked SPL to SPL-0.63.0000
Cannot go back to HardSPL with manual method, flash stays at 0%.
Stock ROM - Sprint WM 6.1
Slamming head against wall now. Getting to the complete end of all possible things to flash to this device.
Back to magic of mtty.
Code:
Cmd>task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=351, total block of CE=3745
ERASE block 768 FAIL !!!
Write 0xFF start page=0x57C0, total page=0x3A840
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
Task 2a - complete format of all memory, except for the SPL didn't work. I flashed the Sprint stock ROM and same result, tried going to HardSPL with RHODIMG.nbh but can't do it anymore, that like it matters since if I could get into WM OS I could do it from there.
I checked the info 8 output on my good TP2 and it is very similar, only big differences are that it lists itself as "HTCSSuperCID" and doesn't show Bad Block 768.
I searched for "reboot loop" on PPCGeeks and XDA forums and couldn't find anything useful for my situation since my phone won't even show the red radio version codes during boot-up, while other people just had reboot loops when starting the OS or after flashing a bad GSM ROM. I can't even get that far.
I was hoping to make this TP2 last at least another few months until the dual-core phones came out in force so that my wife and I can switch away from these slow and old phones to something newer and better running Android but it seems like she's going to be doing an upgrade after we're back from vacation.
Click to expand...
Click to collapse

I bricked my phone after using the Advanced Settings to change the Glyph Cache to 32KB and enabling File System Cache to Auto. Got prompted to Soft-Reset and phone went into boot screen loop.
Click to expand...
Click to collapse
too bad! how the hell is this possible?
scary...

ericjm said:
too bad! how the hell is this possible?
scary...
Click to expand...
Click to collapse
The soft-reset might have been the trigger that showed the reboot loop and not Advanced Settings which was just like any application that could have requested a soft-reset from the user.

FRAK THE PHONE - IT WORKS!
After getting back to the US today my wife turned on her "bricked" phone and the thing booted up like nothing happened, straight to the Sprint OEM ROM that I flashed to it as the last thing.
It seems that it needed a CDMA signal to initialize the Radio ROM on boot-up so that it could continue the test of the way, without CDMA the phone got stuck in a reboot-loop.
I still have no idea how this happened to one phone when the other was just fine.