Database Develop

Did I just brick?

Ugh... I was flashing a new radio file to try to fix my speaker issue, and it locked up at 95%... apon reboot I have the tri colored screen... and I had to use the Whitescreen fix to get it to flash to 95%.... Now that I am stuck at the tri color screen I can't seem to get it to work again (since I can't get in to run the white screen fix program on my Tilt).
Any suggestions?

First things. What does it sayt on your screen. Post evry word & number you can see on the tri-color (BL) screen.
After you tell me that, I'll tell you what to do next.

In the Upper right hand corner it says RUUNBH
On the left side a little lower it says
KAIS1*0
SPL-1.56.0000
CPLD-8
At the bottom of the screen if I have USB plugged in it says USB, if nothing is plugged in it says Serial.

OK, now I'm gonna have to chew you a new A$$HOLE for a minute, so be patient!
WHY IN THE HELL WOULD YOU FLASH WITHOUT HAVING HARDSPL INSTALLED????
Okay, now that's out of the way, you have a RUU flag set in the device because you force flashed over MFG SPL.
You need to first download MTTY v1.1.6 & then do the following. *I assume you are using an XP pc. If not tell me BEFORE doing anything.
On your PC hit Ctrl, ALT, Delete. Select Task Manager & end the following processes:
1. WCESCOMM.exe
2. WCESMgr.exe
3. rapimgr.exe
Also kill any firewall that may be running & in particular any McCaffee security products.
Remove SIM & SD card, then Plug your device in, & launch MTTY.
Select flow control RTS/CTS & then select the USBCE0001 (or similar) or USB port.
Hit your enter key until you see the prompt "cmd>"
At this prompt enter only the following & exactly as it's written: info 8
It should look like this "cmd>info 8"
Please not there is a space between the word info & the number eight (8).
Post the return from the MTTY screen or PM me with it & I'll tell you the next step.
DO NOT PLAY WITH MTTY!!! It is not a toy. Do not try entering random commands, etc. MTTY can brick your device if you are not careful. I unbrick about 5 of these a day, so I have a ton of experience with MTTY & CE.

Thank you SO much for the detailed help. My only problem now is tracking down MTTY.
I apreciate the help!

You might try this thread that talks about mtty...
http://forum.xda-developers.com/showthread.php?t=371154

Got same problem with error 262
Thought i had installed hardspl but not sure now,
my tricolour screen shows the following
KAIS130 MFG
SPL-1.0.0liPof
CPLD-8
with RUUNBH in the top right corner
and info 8 shows
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 781 (0x30D) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x740
Partition[2], type=0x25, start=0xD80, total=0x8180
Partition[3], type=0x4, start=0x8F00, total=0x123C0
CE Total Length(with sector info) = 0x47C7800
CE CheckSum Length(without sector info) = 0x4780000
Cmd>
Any help would be greatly appreciated

torrac said:
Thought i had installed hardspl but not sure now,
my tricolour screen shows the following
KAIS130 MFG
SPL-1.0.0liPof
CPLD-8
with RUUNBH in the top right corner
and info 8 shows
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 781 (0x30D) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x740
Partition[2], type=0x25, start=0xD80, total=0x8180
Partition[3], type=0x4, start=0x8F00, total=0x123C0
CE Total Length(with sector info) = 0x47C7800
CE CheckSum Length(without sector info) = 0x4780000
Cmd>
Any help would be greatly appreciated
Click to expand...
Click to collapse
You are missing a ton of info. Looks like a lot of corrupt data on your device.
I would reset the device to restart in CE by clearing out the RUU Flag, (cmd>set 16 0) then give it the boot command. (cmd>boot).
After that you need to plug back in, restart Activesync & flash an OEM rom to overwrite the bad data.
You DO have HardSPL though, that is good.
If you are a Tilt user, go to http://htc.com/us & DL the ROM from Support/ Software Downloads.
Aftyer flashing the OEM ROM, redo the info 8 (cmd>info 8) & see if Bad Blocks are still reported. Let me know.

I also have the untouched roms on my 4shared site if you need to link any GS.

<3 threads like these, someones in danger and allways someone to help this is why i love xda-developers

It's completely selfish...
The ONLY reason I help is so people leave Oli, Pof, Tadzio, & many more I'm forgeting alone.
I want the really smart guys here working on new tools & ways to better utilize the technology. In past forums, if you had issues you bugged the crap out of Oli, or Pof to the point of Mania (I Know, I'm nearly there) & I don't want any of the guys to stop sharing their knowledge or their tools just because too many people can't follow direction directions.
I want brighter minds working on bigger projects, so I try & take some of the issues I can help with.
But make no mistake, I ultimately do it for ME & what I want.

GSLEON3 said:
OK, now I'm gonna have to chew you a new A$$HOLE for a minute, so be patient!
WHY IN THE HELL WOULD YOU FLASH WITHOUT HAVING HARDSPL INSTALLED????
Okay, now that's out of the way, you have a RUU flag set in the device because you force flashed over MFG SPL.
You need to first download MTTY v1.1.6 & then do the following. *I assume you are using an XP pc. If not tell me BEFORE doing anything.
On your PC hit Ctrl, ALT, Delete. Select Task Manager & end the following processes:
1. WCESCOMM.exe
2. WCESMgr.exe
3. rapimgr.exe
Also kill any firewall that may be running & in particular any McCaffee security products.
Remove SIM & SD card, then Plug your device in, & launch MTTY.
Select flow control RTS/CTS & then select the USBCE0001 (or similar) or USB port.
Hit your enter key until you see the prompt "cmd>"
At this prompt enter only the following & exactly as it's written: info 8
It should look like this "cmd>info 8"
Please not there is a space between the word info & the number eight (8).
Post the return from the MTTY screen or PM me with it & I'll tell you the next step.
DO NOT PLAY WITH MTTY!!! It is not a toy. Do not try entering random commands, etc. MTTY can brick your device if you are not careful. I unbrick about 5 of these a day, so I have a ton of experience with MTTY & CE.
Click to expand...
Click to collapse
Hi my kaiser looks like briked ! black screen ,green light, can not acces bootloader, active sync do not recognize it .. when i connect it with mtty and write any command like (info 8, set 16 0) there is a reply Invalid command ! What shoul I do to make my kaiser working ? This problem appears after unsuccesuful nuespl instaling (and dont read for what is nuespl so I have just installed it and my phone stuck, after reset my screen goes black....)

It has been a week now ? And you have posted everywhere. At some point you are going to have to admit that you killed your phone. Sorry

denco7 said:
It has been a week now ? And you have posted everywhere. At some point you are going to have to admit that you killed your phone. Sorry
Click to expand...
Click to collapse
On investigation I see what you mean - all those posts about the same issue I hope people starting out see this and take it as a warning that doing the wrong thing if you don't know what you're doing does have the capacity to ruin your phone so it's best to read up all the wiki contents and threads about flashing the Kaiser, berfore attempting to do so. On a +ve point, I think IP13 may find people here interested in buying the phone for parts.

Another dead Kaiser?

Here is the situation:
I've used mtty because i was looking for bad blocks.
I've DELETED ALL on my kaiser, bootloader included
After an S100, an Hermes, now has come my time... Bricked PDA
When i connect the pda to the PC, it recognize it as an unknown "Data Interface"
When i power on it, the green light come on, but nothing else.
No bootloader, No Hreset.
Here is a log made by the stupid guy who is typing
Code:
Cmd>task 28
Format start
Fill RSVD information for block 288 to 309
Storage start sector=0x7CC0, total sector=0x13600
Storage start block=520, total block=1240
Total Bad Block in CE: 0
Erase physical block from 808 to 2032
si backup: Erase physical block from 2032 to 2048
Format end
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
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x740
Partition[2], type=0x25, start=0xD80, total=0x6F40
Partition[3], type=0x4, start=0x7CC0, total=0x13600
CE Total Length(with sector info) = 0x3E9E600
CE CheckSum Length(without sector info) = 0x3E60000
Cmd>task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=288, total block of CE=1760
Write 0xFF start page=0x4800, total page=0x1B800
SPL version and MFG TAG are same, skip it.
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
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
OS NOT FOUND !!!
Cmd>
...my error was the reboot of the phone :x :x :x
...but task 2a with the hermes repairs bad blocks.... here has FORMATTED ALL!

Holy $hit. You screwed the pooch man. Damn.
Contact GSLEON3, if anyone can help, he can. Good luck. I know I cant help you but I wanted to post to give you the name of someone who can, maybe.

You sir are an IDIOT! (sorry couldn't resist)
I reported the change in task 2a months ago, the info is readily available in the forum & also in the wiki.
If you reset before flashing a new SPL bootloader after a task 2a command, you end up with a shinny new brick!
As of this point, both myself & Jocky are working on trying to find a remedy for this.
If your device is security unlocked I can help you NOW!
However, If you never ran the security unlocker, you'll just have to wait until I or Jocky, or anbody for that mater figures out a way to flash thru OEMSBL using radata commands.
You are now stuck in OEMSBL. & again unless security unlocked there is no solution yet.
I can't even count the number of times I have posted the fact the every SPL, Including HardSPL, for every different model can & do have different commands & subsequently different outcomes.
I believe Jocky is the closest to being able to recover this type of brick, he's also a hell of a lot smarter than I, but I also know he's not there yet.
If you are security unlocked, contact me & I'll help you out, otherwise, wait patiently.

You're ABSOLUTELY RIGHT!!!!
...the fact is that i have very little time to spent into forums reading, and i cannot follow all topics (the conseguences are here
if for security unlocked you mean the HardSPL installed, i have it but... something say me that isn't enough

SkizZO said:
You're ABSOLUTELY RIGHT!!!!
...the fact is that i have very little time to spent into forums reading, and i cannot follow all topics (the conseguences are here
if for security unlocked you mean the HardSPL installed, i have it but... something say me that isn't enough
Click to expand...
Click to collapse
NO EXCUSES! I have a full time career, a part time business witrh a partner, an eight year old daughter, & nine & ten year old step sons. Take your phone into the library, AKA: restroom, & read.
At least the wiki, where all of the most important stuff is. There isn't that much there, only really important things, especially in the upgrading section.
As for Security Unlocker, NO that is not HardSPL. Coming from another forum you should know that.
HardSPL is CID unlock. See here for security unlocker: http://forum.xda-developers.com/showthread.php?t=361236
Although, I'd have to say from what I've heard, this is unlikely to have been done.
I do believe it will be possible to fix, & in the near future, just not quite yet. Sorry, don't have better news for you.

what a BAD NEWS !!!!
i hope there is a way to use a driver to make windows recognize the phone in bootloader....

"SPL start start block=288, total block of CE=1760
Write 0xFF start page=0x4800, total page=0x1B800
SPL version and MFG TAG are same, skip it.
restore SPL OK"
wow what a bug ... I guess SPL didn't get restored because it skipped the reflash - they must be using the common code to flash it (same code used when it is an NBH), so the version check fails, as the SPL i assume is a hardspl and so won't let overwrite itself.
so this must be a bug that only hardspl has.
anyway this is an MFG hardspl yes? then before task 2a'ing you'd be better off unpatching the overwrite protection then maybe 2a won't kill your kaiser after all.
here's how :
you need to issue several commands.
1. task 32
2. to verify we are at the right place (this command list will only work if the hardspl base is the same MFG version I'm thinking of) :
three commands:
mw 8C019AE4 1
mw 8C019B00 1
mw 8C019B1C 1
all of them should return E1A00000.
3. if the previous step went well, to actually unpatch write protection two more commands:
mw 8C019AD4 1 0A000023
mw 8C019AE4 1 EA00001C
ok now that should have unpatched the overwrite protection, so final conclusions:
1) either I'm right and this fixes task 2a and it won't be lethal now
2) or I'm wrong and it has another cause for being so fatal, but in that case, after doing the task 2a, you should be able to flash an SPL into nand even if it is empty - as long as you don't reset the phone the SPL is still in RAM to download another SPL.
P.S: please let me know if task 2a did kill non hardspl 'ed kaisers too
P.S.2: if second step doesn't return E1A00000 and the spl *is* MFG let me know

I feel for you
Thought I had killed my device after using old SPL software from my Trinity on my Kaiser thinking it would work. Yes, I didn't read enough info.
The reflash got to 18% and hung then stopped...Luckily the device resumed to bootloader but it wouldn't accept any OEM ROM I threw at it.
Read for about 4 hours and found out about mtty and a recovery task that finally returned the device to a hard reset state. I almost wept when it worked

Ultimate Idiot
Ok I know I'm the ultimate idiot, however while trying to get rid of the Radio from Hell, I accidentally task 2a-ed my phone.
now I see many tips on how to solve this, I have Vista and XP, however the Xp computers don't seem to like the driver for the phone neither does Vista.
continuing on
I got the drivers installed and changed the ports
(i get no usb connection though, just through the com ports)
now when I try to type commands, I get errors (I'm typing them in right)
or it becomes unresponsive.
any help in this would be appreciated.

Kaiser stuck on Bootloader Screen saying: "No Image File"

Hey everybody,
first of all i want to say BIG THANKS for all the informative posts that helped me in the past.
Now, i'm facing a problem which seems unsolvable at the moment
It started with my USB Port Issue. The MINI USB connector did not work anymore (no power and no data connection)m because of some twisted connector pins. So i ordered a broken HTC Tytn 1 and gave it to an electrician who replaced the broken usb port of the kaiser.
The Kaiser is now repaired, usb connectors works well, but since the electrician replaced the connector, the Device does not boot anymore.
Only thing i see is the Bootload Screen which is in a flash interrupted by a screen which says: "loading.....no image file". Then it turns back to bootload modus.
I Flashed the Original HTC ROM 6.1 but it stays the same. I Flash the 1.4 M-Diamond Full it stays the same.
I tried this:
http://forum.xda-developers.com/showpost.php?p=1765045&postcount=2
The Device finally booted but once the device started to configure the OS, it switched back to the Bootloader Mode.
There is obviously no chance to get the device running!
Does anybody of you know the solution for this Problem? I don't like a 500bucks phone stuck on the boatloader screen. I mean..those colours really look nice hahahaha.. please help me
Thanks

My Log on mtty.exe
This is my Log Msg on Mtty.exe after i send the command "boot"
boot
"Fill RSVD information for block 288 to 309
Storage start sector=0x9400, total sector=0x11EC0
Storage start block=613, total block=1147
Total Bad Block in CE: 2
Erase physical block from 903 to 2032
formatstorage Bad block found: 1134
formatstorage Bad block found: 1939
si backup: Erase physical block from 2032 to 2048
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 LC card
SD Init OK
SDFATChkConf: RhOpenFile() failed KAISCONF.txt
OEMIPLInit clear 10MB ext RAM
OEMGetUpdateMode
OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage crc of Mini-Kernel:0x637924DC
OEMLaunchImage 80000000
Jump to Physical Address 10300000"

Give some of the ideas in this thread a go (especially the cmonex Hard SPL bit): http://forum.xda-developers.com/showthread.php?t=423486
If nothing work's I'll have a look tonight (if I get on my PC ... ).
Ta
Dave

ain't workin' yet!
Hey dave, thank you for your link!
I really do try to get this device running and i'm very patient, reading every single thread carefully in order to avoid messing up!
After your post, i tried this one:
"If you are using one of the pof (OliPof) or jockyw2001 Hard SPLs and still cannot boot. ref
This method is not needed if just the RUUNBH is showing on screen, for that the other solutions suffice.
Download KaisDiagTest1.zip from here. (Try here if the link doesn't work).
Format your MicroSD to Fat32 (if you havn't already done so).
Copy the KAISDIAG.NBH image file from the zip on to the root. (This is basically an SSPL patched to load from SD without booting OS.)
Insert the SD Card into the phone and turn it on.
It should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
You should then be able to flash a ROM using KaiserCustomRUU over USB as normal (see above for instructions).
Before you flash, test the connection by opening MTTY and seeing if you can select the USB option to connect to. (See above).
If your PC doesn't see the device, try a replug. Also, the USB should be plugged in all the time (except for when you replug).
If this doesn't work, please read and then post here - there may be another method waiting for testing."
It didn't work, even after Flashing the M-Diamon 1.3 (3.0) the device does not boot. Entering "boot" in mtty.exe does not help either, because the device screen slowly turns WHITE ! WHAT THE HELL?
I tried this also:
http://forum.xda-developers.com/showthread.php?t=420683
i tried 356, 329 ( this i tried first ). and after patching it i flashed m-diamond 1.4 -> no success, and original htc 6.1 -> no success.
just take a look at how my kaiser reacts :
http://rapidshare.com/files/165190998/kaiserissue.wmv
so, i've tried every hardspl from cmonex and it all remains the same, the device turns on, the bootloader screen appears it shows ( as illustrated in the video ) the spl version and so on...
here is my log from mtty.exe:
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
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 537 (0x219) is bad block
BLOCK 608 (0x260) is bad block
BLOCK 846 (0x34E) is bad block
BLOCK 1651 (0x673) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x740
Partition[2], type=0x25, start=0xD80, total=0x86C0
Partition[3], type=0x4, start=0x9440, total=0x11E80
CE Total Length(with sector info) = 0x4A6A200
CE CheckSum Length(without sector info) = 0x4A20000
what's the deal with the "bad blocks" ? Damnit, i really do despair of the whole process, i tried 7-8 hours now and it doesn't seem to work!
Please, if anybody of you knows exactly! what the problem is/could be, let me know and in order to save time, feel free to contact me on msn: [email protected]

Well,
if you have a SD card, give it a shot and try to flash your original (current installed) ROM from SD by following this HOW-TO - just make sure that you use the exact same ROM as you have on the device in case it is not HARD_SPL'ed

hey, thanks for your post.
there's no way actually..i flash the original / actual rom via sd card, 100% installed but still same issue, stuck on the bootloader !
I'm not quite sure but what exactly is the second line in the bootloader which says: "SPL-1.0.OliPof". How do i get this changed?
what about the "bad blocks" in my mtty.exe log?
it is So weird that non of the (very good) sticked posts do help i guess my tilt is dead...

the BAD BLOCKS:
It seems to be normal under MTTY - I had about 4 different KAISER connected with mtty and on all of them it found some bad blocks - maybe just something it can't read due security restrictions or special formattings - OLLI P might be the right guy to ask ... he seems to be the expert on that part.
The "SPL-1.0.OliPof" tells me that your device is already HARD SPL, so, you should be able to flash any ROM.
Please, connect your device via USB to MTTY, once you are connected and pressed ENTER to get the input "C:>" type simply BOOT and hit ENTER.

BTW:
If the BOOT command does not work, try the solution in the first post of the following thread:
http://forum.xda-developers.com/showthread.php?t=371154&highlight=boot+loader+fix
That worked for me on a Tilt version of the Kaiser.
The mentioned "WCEUSBSH001" in that thread should be "USB" (depending on your MTTY version).

thanks again!
Hey Junner,
thanks for your post!
What about if the HardSPL is broken? is there any possibility to fix/renew it?
I've used mtty.exe a lot the last 10 hours . The "boot" command did fail most of the time. Some times the device bootet with the previously flashed rom (for instance the m-diamond)...but once Windows Mobile starts the "auto configure routine", the device restarts and the bootloaderscreen appears.
"Set 16 0" / "Set 14 0" ( i know if can be different depending on the device ) does not work. "Task 0" and "Task 8" ain't work either.
So, what now? As you can see: No matter! what i do...in the end i only have a bootloader screen...honestly i'm traumatized! i will NEVER be able to flash any device again HAHAHAH
btw: 4sure i tried both mtty versions. I even tried the procedure on different computers.

Please, connect your device via USB to MTTY, once you are connected and pressed ENTER to get the input "C:>" type simply BOOT and hit ENTER.
Click to expand...
Click to collapse
Hey again.
Check out the Video i uploaded. There you can see that the device will not boot

While 'glimpsing' at your video, I saw that you did not even have a DOS PROMPT in MTTY when you typed BOOT!
When connecting via MTTY, hit ENTER first once or twice and wait for the C:> afterwards type BOOT and hit ENTER again! If that does not work, try to do the exact same with the stuff mentioned above in the thread (SET 16 0) ...
IN ANY CASE: make sure you get the DOS PROMPT first in MTTY !!!
Since your phone is HARD_SPL'ed and you say you can't flash any ROM, the only one thing I can think of, is, that your electrical repair man damaged the physical ROM while working on your USB port.
It looks strange to me because if there would be a physical damage to the chip, you wouldn't be able to complete the flashing process.
What happens exactly when you try to reflash your device with a standard ROM??? What errors do you get? What does your device exactly do during flashing?

FINALLY!
Hey again.
Of course you are right, sorry for that. I had to handle recording and entering the command at the same time
I finally fixed the problem! Unfortunately i'm in a hurry right now, i will report later! Many thanks for your help so far!!!
Talk to you later!

Having the same problem!
I see you have solved your problem, and as I have the same one, please explain me how you managed to get the device working, as I am out of my wits trying to repair my Kaiser!!!

Also have the same problem with my Kaiser. Could anybody explain how to fix the no image file problem, please?

Is there any chance to solve that problem? Or do I have to throw my Kaiser away? PLEASE help me to fix it!!

No WLAN due to Erased EEPROM****SOLVED****

I'm facing the same problem with my wlan as described in http://forum.xda-developers.com/showthread.php?t=322225 thread for Hermes. Due to the fact that Hermes uses different wlan chip(so the eeprom data are not the same) the procedure didn’t work for my Trinity. Can somebody provide the output of a good eeprom? or provide any help.
Thank you to gruptnt for his WLAN Fix!
gruptnt FIX:
http://forum.xda-developers.com/showpost.php?p=5313622&postcount=340
SuperSport Tutorials:
http://forum.xda-developers.com/showpost.php?p=5314726&postcount=345

I have the same problem too. Any help would be appreciated...

same here...

Wlan eeprom needed !!! Help !!!
Where i can download the EEPROM?
HTC support sucks, they not give it me.
Alternative:
How I can dump the EEPROM from a other Trinity with functional WLAN? The Hermes guide not work for me! Is there anywhere a german / english guide at the net??? or can a advanced trinity user from forum explain me in german / english what i had to do. Please.
Sorry for my bad english...

also I have this problem
but i think procedure hermes not work because
it requires a specially patched SPL... (hermes)
chip wlan is equal to hermes ? and eeprom code?
with putty :
Cmd>task 32
Level = 0
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is BAD block !!! <<<<<<< is bad
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Partition[0], type=0x20, start=0x2, total=0xFE
Partition[1], type=0x23, start=0x100, total=0x1400
Partition[2], type=0x25, start=0x1500, total=0x26A00
Partition[3], type=0x4, start=0x27F00, total=0x55500
CE Total Length(with sector info) = 0x511F800
CE CheckSum Length(without sector info) = 0x4FE0000
Cmd>task 37
.....
09/12/2009 16:19:31 [K :: KERNEL] HTC Nand Read!
09/12/2009 16:19:31 [K :: KERNEL] Kernel: EEPROM signature=FF FF FF FF FF <<<<<< bad
09/12/2009 16:19:31 [K :: KERNEL] HTC Nand Read!
09/12/2009 16:19:31 [K :: KERNEL] Kernel: EEPROM signature Old=FF FF FF FF FF <<<<< bad
09/12/2009 16:19:31 [K :: KERNEL]
Cmd>password 0000000000000000
Invalid password.
HTCSF kEØ(HTCEPassWord: 0000000000000000
Cmd>password BsaD5SeoA
Pass.
HTCST ÚÈÒHTCEPassWord: BsaD5SeoA
Cmd>set 1e 1
Cmd>rbmc 500a0000 40000
GetExtRomData+(): *pszPathName=500a0000, dwStartAddress=40000, dwLength=8C08DAA4
:F=500a0000
:A=00040000
:L=8C08DAA4
:rbmc=8DAA4

but file nb is blank
On
trinity100
ipl-0.50
spl-1.30.olipro
Tnks 4 all help

I have managed to get the eeprom data by installing the SPL (oli 2.30) for hermes as described is the procedure. I did not have any issue with my device and it did the work, but you have to try it on your own risk.
The password 0000000000000000 will then work.
Move back to trinity SPL (oli 1.30) immediately after completing the procedure.

konst_kk said:
I have managed to get the eeprom data by installing the SPL (oli 2.30) for hermes as described is the procedure. I did not have any issue with my device and it did the work, but you have to try it on your own risk.
The password 0000000000000000 will then work.
Move back to trinity SPL (oli 1.30) immediately after completing the procedure.
Click to expand...
Click to collapse
Did you boot to OS with the hermes spl or or you just do the work whithout quitting the bootloader?
Olipro 2.30 is protected against flashing SPL as is 1.30?
Have you done a full backup of your eeprom? If so, which are the addresses?
Thanks

how u manage to install SPL 2.30 HERMES on TRINITY ????????

I haven't done it but:
Take the .nb and transform it into nbh file and flash it
Or use the splexploit

mac_es said:
I haven't done it but:
Take the .nb and transform it into nbh file and flash it
Or use the splexploit
Click to expand...
Click to collapse
are u sure because i think the address on memory is different of hermes

Who can Fix Trinity?
I want tools+batch file to fix it my Trinity.
Please help me.

No, I did not boot to OS; just reverse to trinity spl immediately after getting the eeprom data. As far as the installation of hermes spl concerns, I was newbie at that time and I just follow the hermes instructions without knowing the risk; but it worked. Memory addresses are the same with hermes, I've performed about 1000 lnb commands using the hermes memory addresses without causing any problem to my trinity.
Always make sure you have a valid backup.

konst_kk said:
As far as the installation of hermes spl concerns, I was newbie at that time and I just follow the hermes instructions without knowing the risk; but it worked. Memory addresses are the same with hermes, I've performed about 1000 lnb commands using the hermes memory addresses without causing any problem to my trinity..
Click to expand...
Click to collapse
ok .. can u explain here you procedure and file use ?
u can attach file use ?

konst_kk said:
No, I did not boot to OS; just reverse to trinity spl immediately after getting the eeprom data. As far as the installation of hermes spl concerns, I was newbie at that time and I just follow the hermes instructions without knowing the risk; but it worked. Memory addresses are the same with hermes, I've performed about 1000 lnb commands using the hermes memory addresses without causing any problem to my trinity.
Always make sure you have a valid backup.
Click to expand...
Click to collapse
do you sloved it??, can you upload your nbh to 4shared or mediafile for me please!!! Thanks

any news?
hi guys... why somenone has solved the problem and there is no written procedure to help all others in the same situation?
Is there a mysteriuos answer?
Bye.
Talpottolo

Same prob too...
can i use mtty to fix?

Hi guys,
i' ve joined the NO WLAN club few days ago,i tried everything with no success,downgrading,upgrading , i even followed the Hermes instructions with no luck-getting continuous errors.Is out there a trin guru who can post the procedure step by step ,and the files also .From what i understand we need a EEPROM dump to put our mac adress in (i fortunately have it).
PLEASE PLEASE somebody make a guide for dummies , are manu users out there having a NAND 0X06 BAD BLOCK (wlan).

sterh said:
Hi guys,
i' ve joined the NO WLAN club few days ago,i tried everything with no success,downgrading,upgrading , i even followed the Hermes instructions with no luck-getting continuous errors.Is out there a trin guru who can post the procedure step by step ,and the files also .From what i understand we need a EEPROM dump to put our mac adress in (i fortunately have it).
PLEASE PLEASE somebody make a guide for dummies , are manu users out there having a NAND 0X06 BAD BLOCK (wlan).
Click to expand...
Click to collapse
ok first we can't resolved with hermes guide ...
second in this week i write what i find
bye

Same problem
I have the same problem
WLAN ERROR
and
NO GSM
can some one help us

I too have the same problem! but someone has ever managed to solve it?

Software or hardware problem?

HTC TyTN II
1. Wirlles DOES NOT WORK
2. Sometimes the signal does not work
3. The camera DOES NOT WORK
4. disc does not work
5. World to the keyboard does not work
Is this a software problem?
Sorry on my bad english.

konzul said:
HTC TyTN II
1. Wirlles DOES NOT WORK
2. Sometimes the signal does not work
3. The camera DOES NOT WORK
4. disc does not work
5. World to the keyboard does not work
Is this a software problem?
Sorry on my bad english.
Click to expand...
Click to collapse
Back up you data and do a hard reset. If the problems persist, you can pretty mouch assume it is a hardware problem.

Hello
I have some problems with the storge.. i have it find with MTTY
when I start my phone it won't show the radio version ect. only the boot display will work for few seconds
and it's crashs! What can i do!? I have flash some roms.
it flashes and it go but it didn't start it.
HardSPL 1.0 from oli
Rom before crash: NoThrills_WM61_GER_V3

meylan said:
Hello
I have some problems with the storge.. i have it find with MTTY
when I start my phone it won't show the radio version ect. only the boot display will work for few seconds
and it's crashs! What can i do!? I have flash some roms.
it flashes and it go but it didn't start it.
HardSPL 1.0 from oli
Rom before crash: NoThrills_WM61_GER_V3
Click to expand...
Click to collapse
Try upgrading your hardspl to 33.4 or 3.29 ,1.0 is a WM 6.0 hardspl.

I have try to upgrade Hardspl many times. And it doesn't do it
so I have try to fix my storege yesterday and then it's broke
then i want start only the lcd goes green.
no screen anymore
task 28 55aa
Format start
Fill RSVD information for block 288 to 309
Storage start sector=0x8DC0, total sector=0x12500
Storage start block=588, total block=1172
Total Bad Block in CE: 0
Erase physical block from 876 to 2048
formatstorage Bad block found: 1603
Format end
Cmd>task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=288, total block of CE=1760
ERASE block 1315 FAIL !!!
Write 0xFF start page=0x4800, total page=0x1B800
SPL version and MFG TAG are same, skip it.
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
Cmd>task 32
Cmd>task 37
Invalid debug log data. Please check debug log raw data in addr 0xAE100000
Cmd>task 28
Format start
Fill RSVD information for block 288 to 309
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
Cmd>erase
HTCST ÚÈÒHTCE
Cmd>erase a0040000
HTCST ÚÈÒHTCE
Cmd>checksum
Cmd>checkimage
SPL CRC checksum = 0x5507A35A
CE is None.
ExtROM is None.
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 8 (0x8) is reversed block
BLOCK 1315 (0x523) is bad block
OS NOT FOUND !!!
Cmd>info 7
CPLD ID=0x8
Cmd>wdatah
Command error !!!
Cmd>rtask 0
Cmd>rtask 4
Cmd>checkimage
SPL CRC checksum = 0x5507A35A
CE is None.
ExtROM is None.
Cmd>password BsaD5SeoA
Pass.
HTCST ÚÈÒHTCE
Cmd>ruurun 0
Command error !!!
Cmd>ResetDevice
what i can do ? since last command it didn't start it

try a new radio and maybe it'l work

meylan said:
what i can do ? since last command it didn't start it
Click to expand...
Click to collapse
The reason it won't start anymore is because you ran Task 2a, which, unlike previous devices, formats EVERYTHING away, including the SPL and Windows Mobile. It essentially bricks the device, as it will not boot past OEMSBL (The radio bootloader, it comes first in boot order and loads the SPL, AFAIK). As soon as the device is reset after running the Task 2a command, the device will not boot as there is no OS bootloader, nor is there anything to boot. However, Jockyw2001 has created tools which may help to recover from a task 2a. A thread concerning Task 2a bricks can be found here. Best of luck with recovering your device.

DaveTheTytnIIGuy said:
The reason it won't start anymore is because you ran Task 2a, which, unlike previous devices, formats EVERYTHING away, including the SPL and Windows Mobile. It essentially bricks the device, as it will not boot past OEMSBL (The radio bootloader, it comes first in boot order and loads the SPL, AFAIK). As soon as the device is reset after running the Task 2a command, the device will not boot as there is no OS bootloader, nor is there anything to boot. However, Jockyw2001 has created tools which may help to recover from a task 2a. A thread concerning Task 2a bricks can be found here. Best of luck with recovering your device.
Click to expand...
Click to collapse
agh f*** thanks i didn't know that...
It's normal that the device isn't detected as qualm anymore?
it display me by connecting with Pc: "DATA LINK" or so

meylan said:
agh f*** thanks i didn't know that...
It's normal that the device isn't detected as qualm anymore?
it display me by connecting with Pc: "DATA LINK" or so
Click to expand...
Click to collapse
When I manually put my phone in OEMSBL, which is what yours should be in when you turn it on right now (the light is green but the screen stays black), windows detects it in Device Manager as: ZTE NMEA Device CDMA 1X, ZTE Diagnostics Interface 6000 CDMA 1X, ZTE USB Modem 6000 CDMA 1X. It should also detect the GPS and some other stuff, but I can't find those in Device manager.

mhh i used MTTY but i can't get in download mode
what commands should I write?

meylan said:
mhh i used MTTY but i can't get in download mode
what commands should I write?
Click to expand...
Click to collapse
This kind of stuff is too complicated for me, so I can't answer that myself. However, there are many threads that talk about task 2a resets and how to recover from them. Here, here, and here are all good places to start. But keep in mind that you should NOT try anything in these threads unless you have read everything, and are absolutely sure that the tool is for your specific situation. For example, DO NOT use the FrankenKaiser version in the third link if you don't have the Radio from Hell installed.
Alternatively, you could try the XDA IRC channel, or PM jockeyw2001.
Once again, best of luck repairing your brick.