Database Develop

Flash ROM problems - it refuses to flash

Ok, I am having a difficulty in flashing ROM using MaUpgradeUt_noID.exe and/or BaUpgradeUt.exe
Using MaUpgradeUt_noID.exe
I have the system rom (Aku's version) and a radio rom (1.5). Next, I run MaUpgrade tool; it detects the device flash as follows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Okay, you might have questioned why is the device v5; that's because it worked before with baupgradeut tool, but right now, it doesn't work anymore and I wasn't sure how I managed to get it to work in the first place. The main reason I wanted to upgrade again was the radio rom (the connection is really bad) and the transcriber failed to function properly as an extended rom but that was like months after I did this. I often had to reset the device to fix those issues.)
Then after pressing Next, ActiveSync (I tried final version 4.5 as well as an older version 4.2 - both failed) would then get disconnected and ma utility will give me a Connection problem error as follows. I have to reset the PDA device to get activesync reconnected.
Using BaUpgradeUt.exe
Now this is the annoying part. I loaded the GetDeviceData.exe on the PDA and obtained the following:
Code:
P H 2 0 B 1 W W E AT%CID? 5 . 0 4 . 1 0 . 1.02.10 % 4
Removing all of the spaces, I get something like this:
Code:
PH20B1 WWE AT%CID? 5.04.10. 1.02.10 % 4
I wasn't able to find the device operator. So I just edited EditFix.bat like this (and of course, I run this batch - both files are modified (nk and radio_ ones)):
Code:
xda3nbftool -sd PH20B1 -sl WWE -so "" ms_.nba
xda3nbftool -sd PH20B1 -sl WWE -so "" nk.nba
xda3nbftool -sd PH20B1 -sl WWE -so "" radio_.nba
where I also tried to replace "" with T-MOB101, XGULB001, and XGULA001. (since the device is a Siemens SX66 purchased on ebay) All failed and returned a model error.
Is there anything I should do?

Your operator code seems to be deleted (should be sth like T-MOB101 - read here: http://wiki.xda-developers.com/index.php?pagename=GetDeviceData ). Now you can only use MaUpgradeUt_noID.exe untill you repair it (anyway operator code is not needed after all) by installing ROM with correct Operator code for your device (if you know/remeber it) set by operator or you using xda3nbftool.
Apart from this, you seem not to follow the procedure: you should put BA in Bootloader mode, not leave ActiveSync mode when you initiate upgrade.
Please post your results here, when you finish.

pichus said:
Ok, I am having a difficulty in flashing ROM using MaUpgradeUt_noID.exe and/or BaUpgradeUt.exe
Using MaUpgradeUt_noID.exe
I have the system rom (Aku's version) and a radio rom (1.5). Next, I run MaUpgrade tool; it detects the device flash as follows:
(Okay, you might have questioned why is the device v5; that's because it worked before with baupgradeut tool, but right now, it doesn't work anymore and I wasn't sure how I managed to get it to work in the first place. The main reason I wanted to upgrade again was the radio rom (the connection is really bad) and the transcriber failed to function properly as an extended rom but that was like months after I did this. I often had to reset the device to fix those issues.)
Then after pressing Next, ActiveSync (I tried final version 4.5 as well as an older version 4.2 - both failed) would then get disconnected and ma utility will give me a Connection problem error as follows. I have to reset the PDA device to get activesync reconnected.
Click to expand...
Click to collapse
Hello,
I've the same 101 error...
I don't really understand how to find a solution to upgrade without that problem...could you help me ?

Once I had a problem like this one and I figured out that I could not flash my device + radio at the same time.
Try removing the radio.nbf from the folder where MaUpgradeUt_noID.exe and then try to flash your device.
If it works, then remove the nk.nbf from the folder, put back the radio.nbf and try to flash it.

Tks.
I've put a topic for that.
It seems to be a Vista OS problem...

eleger91 said:
Tks.
I've put a topic for that.
It seems to be a Vista OS problem...
Click to expand...
Click to collapse
I confirm everything. Same problem for me with Vista. Upgrade is possible only under Xp. Maupgrade is not compatible with Vista. Someone should make a Vista version of it.

Nope not only vista. my xp home is having excatly the same problem. Completely stuck now and getting PreSetUSB along with other error msgs now on the device.

hi all of you
how can I fix sam problem

I'm having the exact same problem as you guys. anyone managed to find a work around to it ?

try this workaround...
1. avoid Vista... use XP
2. flash in BOOTLOADER mode. (press and hold Record+Powerbutton then softreset) then just ignore if the Device info FROM is missing... just click upgrade.

Hi Silver Samurai,
I am flashing in Winxp using bootloader mode and Maupgrade. Doesn't seem to work. I have followed everything in the wiki step by step. Such as disabling activesync.
Really don't know where i have gone wrong.

mtnbikefreak said:
Hi Silver Samurai,
I am flashing in Winxp using bootloader mode and Maupgrade. Doesn't seem to work. I have followed everything in the wiki step by step. Such as disabling activesync.
Really don't know where i have gone wrong.
Click to expand...
Click to collapse
what error numbers are you getting?
when does it fail?

Well i make a hard reset (No for the first option and yes to the 2nd and 3rd options.) After that leaving it in bootloader mode - showing serial and bootloader version number v2.08.
I make sure that activesync (usb connection is disabled). Close wcecomm.exe and other files related to activesync in taskmanager. Connected the usb cable and it changes from serial to usb. Invoked the Maupgrade noid.exe. It hangs there indefinately for more than 30 mins showing the screen that it is checking the xda. If i pull the cable out, it immediately shows device error.
I know that there is nothing wrong with the cradle as i can connect to activesync in normal mode and install programs / files.
I can still boot up after that with wm2005 helmi. Cannot seem to erase the rom. Funny thing is that with wm2005 my sd card cannot be detected. Previously with wm2003 it can be detected. However when the screen is off, and when i insert the sdcard, it does turn on. Likewise when i remove the card and the screen is off, it would also come on. But that is a total different aspect altogether. Anyway i figured that if i can reflash to the official wm2003 rom, it would solve that problem.
Sorry for the wall of text, but i just wanted to fully describe the problem i am facing. Could it be that the DiskOnChip is already corrupted ? Don't think that it's the Intel SRAM/Nand Flash chip as it's only 128Mbits. which only stores the bootloader.

is there an SD Card inserted when you are trying these procedures?
can you try both with or without it?
try without an SD first
please post your result.

Yes i have tried both with sd card and no sd card. If the SD card is inserted, in bootloader mode, the serial won't change to usb until i eject the sdcard. The screen would just get stuck showing the msg, checking the xda.

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

Help out OliNex / HARDSPL development by looking up your internal storage brandname

Hi There!
As requested in this topic, I promised to write an tutorial regarding on how to find your internal memory brand (to be clear, NOT your SD Storage Card brand).
This is important because there are ALOT of Rhodium Devices out there which use "Samsung" internal memory and OliNex needs to find a device which uses Hynix (or any different then samsung_kby00xxx) so they can test HardSPL for the Rhodium with it.
So...In short, read the tutorial below if you wan't to help out hardspl development AND if you're willing to, if you have internal memory that's from Hynix (or any different then samsung_kby00xxx), act as a tester for their HardSPL.
Cmonex also wrote a very short tutorial using a different program, you can scroll down a bit and read it or click here.
Originally Posted by cmonex
[SIZE=+3]PLEASE STOP POSTING YOUR FLASH INFO IF YOU ONLY HAVE THE samsung_kby00n00hm[/SIZE]
...because it gives no new information to anyone, or anything useful.
The Tutorial:
Requirements:
QMAT
Windows Mobile Device Center 6.1 for vista or ActiveSync 4.5 for Windows XP
USB Cable for connecting your phone with your pc
Warning:
I'm in no way reliable if you screw your phone up...altrough I seriously doubt that you can actually screw anything up using QMAT and just these instructions.
Step 1
Note:
As I'm personally using Vista x64 I can't explain in full length on how to disable USB Connections in ActiveSync for Windows XP.
Note2: Begin with your device NOT connected to your pc.
First we are going to disable USB connections so QMAT can succesfully communicate with your device.
To do this, open the Windows Mobile Device Center.
Click on "Mobile Device Settings" and then click on "Connection Settings".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Untick "Allow USB Connections" in the new window that just popped up.
Click on "Ok" and then close Windows Mobile Device Center.
Step 2
Enter bootloader mode with your device, DO NOT CONNECT YOUR DEVICE JUST YET!. To do this:
* Remove the stylus from your phone then remove the back cover from the phone.
* Hold the Volume Down button.
* Use the stylus to press the reset hole.
* Or if the device was powered off, hold the volume down button and then press the power button to turn the device on.
You should see "Serial" at the bottom of the screen.
Step 3
Connect your phone to your pc using a USB cable, any USB to Mini-USB cable should be fine, just to be on the safe side you could use the USB cable from the original packaging.
The word "Serial" at the bottom of the screen should turn into "USB", also if this is your first time entering bootmode and connecting your device to the pc it should install some drivers and stuff...this is normal
Step 4
Now the real stuff begins....
Open up QMAT
Click "Hardware Forensics" at the top of the program.
Click on "Use Mobile Ports" at the sub-menu which just appeared.
Click on the tab "Modem Port (Async)"
Click on either Start USB (Vista) if you have vista, or Start Serial (XP) if you have XP.
If everything wen't ok the button you just clicked turned into "Stop USB". Just don't click it just yet
In the Textfield at the left of the buttons you type in:
"info 8" (without the quotes afcourse...) and then press return (enter).
All kinds of information should start popping up in the big textfield below.
Scroll up....and you should see something like this:
Code:
info 8
--- 2K bytes sector version ---
DEVICE NAME=*YOUR INFO HERE*
DEVICE ID=*YOUR INFO HERE*
DEVICE MAKER ID=*YOUR INFO HERE*
PAGE SIZE=*YOUR INFO HERE*
TOTAL PAGE SIZE=*YOUR INFO HERE*
BLOCK COUNT=*YOUR INFO HERE*
BLOCK PAGE=*YOUR INFO HERE*
This is what it displayed with me:
Your brand is stated after "Device Name". Now...please reply with this information if the one you're seeing is displaying ANYTHING else then samsung_kby00xxx (specially if it's stating Hynix)
You can select the text needed and copy it to a notepad file or any other text-file...or this forum afcourse
After you're finisht, hit "Stop USB" and close down QMAT.
Safely remove your device from your pc, reset it and it should start up again as normal.
Re-enable usb connection in the Windows Mobile Device Center.
Thanks to Olipro for personally giving instructions to me on how to do all of this in the first place.
Todo:
Make Video tutorial.

Works in windows 7 as well!
For those cutting edge folkies who use windows 7, it works as well.. just follow the Vista instructions. I can also confirm that it did NOTHING to any any information on my device..
BTW.. sorry guys.. mines samsung!

many thanks for the tut & here is a perhaps simpler way for some people.
1. simply download itsutils from http://nah6.com/~itsme/itsutilsbin-20090515.zip
2. extract to empty folder and make sure your device is synced.
2b. you may have to install http://hpcmonex.net/roms/enablerapinew.cab on the device.
3. goto to the above folder with cmd - if you dont know how to use cmd then i dont need you as a tester anyway (sorry no offense meant!)
4. command: pmemdump -p 0x01ffc0ac 0x4
5. if it shows ad bc 10 55 (flash deviceid) then it's hynix flash
edit: actually the first tutorial is still very useful, if "info 8" shows something other than samsung_kby00n00hm it may still be very interesting!
if you do my steps then if it shows anything other than ec bc 42 15 (which is samsung_kby00n00hm) then please let me know.

Cmonex thank you for your short tutorial.
I edited my tutorial stating explicitly that if someone finds anything other then samsung they should reply with the info

Hi,
I'm under Seven x64, and the first how to didn't word, Qmat can't find usb port.
Cmonex's solution works well, unfortunately, I have Samsung's memory

mtech said:
Same here, Samsung.
Out of curiousity, anyone get this:
BLOCK 32 (0x20) is reversed block
BLOCK 2585 (0xA19) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0xA80
Partition[2], type=0x25, start=0x10C0, total=0x15980
Partition[3], type=0x4, start=0x16A40, total=0x24580
about BLOCK 2585 being bad?
Click to expand...
Click to collapse
Also had that. Think it's normal.

I have a TP2 WWE and the result is:
C:\0>pmemdump -p 0x01ffc0ac 0x4
Copying C:\0\itsutils.dll to WCE:\windows\itsutils.dll
01ffc0ac: ec bc 42 15 ..B.
Click to expand...
Click to collapse

Thread stuck.
Dave

monx® said:
it seems until now everybody hv samsung chipset (including me).
what about only post here if u hv other than samsung chip? so we wont get over excited when see new post here (except this post please )
Click to expand...
Click to collapse
Agreed.
I edited my start-post/tutorial and clearly stated that people only should reply if they have anything else then samsung_kby00xxx.

Can somebody explane me why need Hynix chip ? Samsung are more secured or what ?
ps: 3 pieces of TP2, all samsung chips. I remember that week or two ago, I disassembled one tp2 with damaged screen and i think it was Hynix chip on board, if it mean anything.

borce_razor said:
Can somebody explane me why need Hynix chip ? Samsung are more secured or what ?
ps: 3 pieces of TP2, all samsung chips. I remember that week or two ago, I disassembled one tp2 with damaged screen and i think it was Hynix chip on board, if it mean anything.
Click to expand...
Click to collapse
It's probably an inventory/stock issue. Vendors may not have the same flash chips in stock to use on all manufactured devices. Or there could be different factories with different components available, so one factory could be putting in Hynix flash. This is a very common practice...
Hynix/Hyundai also produces RAM and other ICs, so this may have been what you've seen on your broken TP2.
cmonex,
is it geometry/block size or mfg partition location that is different on Hynix chips?

pen-pen said:
Hi,
I'm under Seven x64, and the first how to didn't word, Qmat can't find usb port.
Cmonex's solution works well, unfortunately, I have Samsung's memory
Click to expand...
Click to collapse
if you need help with that USB thing, feel free to PM me

mtech said:
Same here, Samsung.
Out of curiousity, anyone get this:
BLOCK 32 (0x20) is reversed block
BLOCK 2585 (0xA19) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0xA80
Partition[2], type=0x25, start=0x10C0, total=0x15980
Partition[3], type=0x4, start=0x16A40, total=0x24580
about BLOCK 2585 being bad?
Click to expand...
Click to collapse
it's normal, most nand devices ship with at least one bad block though I have some that have no bad blocks just luck really, and it's not a problem if it has a couple of them, there is enough other blocks to replace them.

shure2 said:
samsung here too, are you sure that they have used hynix memory?
Click to expand...
Click to collapse
well, looks like for topaz there was no non-samsung chips, while hspl was in testing... I know that because no tester had any issues regarding flashing itself; but as soon as I released it they started getting hynix ones. that was nice timing.

CHfish said:
Sorry for spaming the thread (I've got samsung too) but
I've got a test device from HTC - and it says "Security Unlocked" on the top line of the bootloader - is this of any interest to you?
Does this mean I might flash any (unsigned) ROM?
Further information:
Code:
RHD100 32M SS-BC
SPL-0.78.0000
MicroP-Rhodium (LED) v9
MicroP-Rhodium (KEY) v4
TURBO HW/TURBO SW
TP MFG DATA
512,524 794,844
793,200 225,198
227,846 Calibrated
CHfish
Click to expand...
Click to collapse
neat that you have a prerelease. security unlock got nothing to do with OS flashing, sorry. but it is probably also supercid, so you can flash any HTC rom (but not cooked roms).

stepw said:
It's probably an inventory/stock issue. Vendors may not have the same flash chips in stock to use on all manufactured devices. Or there could be different factories with different components available, so one factory could be putting in Hynix flash. This is a very common practice...
Hynix/Hyundai also produces RAM and other ICs, so this may have been what you've seen on your broken TP2.
cmonex,
is it geometry/block size or mfg partition location that is different on Hynix chips?
Click to expand...
Click to collapse
a nand ctl config register is different. this configs for example where to find bad block bytes in the raw read of a nand page (btw, some of the config values are different on hynix than on samsung, but the bad block one happens to be the same on both). on topaz its contents can get "corrupt" (as I dont have such a problematic device I still don't know why), and it happens that the "corrupt" contents didn't affect much except that the SSPL could not read/write nand (it thought all blocks were bad but did not attempt to write the bad block data back); I put "corrupt" in quotes as it is always the same value, not random. anyway, I fixed that on topaz in the end but I would like to see one such device on rhodium, let's see if someone comes up with one soon. I'm pretty sure rhodium has devices with hynix too (even raphael has them, but it wasn't a problem on raphael).
PS: I think the problem with it getting "corrupt" is that topaz (and rhodium probably) handles this config register differently anyway (different from raphael etc). I mean the part is different when you send a request to nand via dm with some buffers with commands and configs in them. what I don't know is exactly how this affects the hynix devices.

cmonex said:
well, looks like for topaz there was no non-samsung chips, while hspl was in testing... I know that because no tester had any issues regarding flashing itself; but as soon as I released it they started getting hynix ones. that was nice timing.
Click to expand...
Click to collapse
Uhhh...that's bad.
Don't you think people would be clever enough to understand a warning message like "check your internal memory before flashing HardSPL!"
...uhm...no...
...forget my words...just a moronic touch of confidence in mankind

cmonex said:
a nand ctl config register is different. this configs for example where to find bad block bytes in the raw read of a nand page (btw, some of the config values are different on hynix than on samsung, but the bad block one happens to be the same on both). on topaz its contents can get "corrupt" (as I dont have such a problematic device I still don't know why), and it happens that the "corrupt" contents didn't affect much except that the SSPL could not read/write nand (it thought all blocks were bad but did not attempt to write the bad block data back); I put "corrupt" in quotes as it is always the same value, not random. anyway, I fixed that on topaz in the end but I would like to see one such device on rhodium, let's see if someone comes up with one soon. I'm pretty sure rhodium has devices with hynix too (even raphael has them, but it wasn't a problem on raphael).
PS: I think the problem with it getting "corrupt" is that topaz (and rhodium probably) handles this config register differently anyway (different from raphael etc). I mean the part is different when you send a request to nand via dm with some buffers with commands and configs in them. what I don't know is exactly how this affects the hynix devices.
Click to expand...
Click to collapse
This is odd, there's a flash driver - a geometry descriptor and a set of flash related procs in SPL for each supported NAND flash type. I don't see how SPL would work at all (e.g. flash OS and such) if Hynix driver is broken/missing. There should be no need to program NAND directly in SSPL AFAIK, the driver should be taking care of setting proper flags (block status, bad block, etc...) in out-of-band portion of NAND page.
Is there a chance SPL on devices with Hynix NAND includes a Hynix driver and SPL on devices with Samsung NAND does not? They might even be the same version, but the driver could be missing in one...

stepw said:
This is odd, there's a flash driver - a geometry descriptor and a set of flash related procs in SPL for each supported NAND flash type. I don't see how SPL would work at all (e.g. flash OS and such) if Hynix driver is broken/missing. There should be no need to program NAND directly in SSPL AFAIK, the driver should be taking care of setting proper flags (block status, bad block, etc...) in out-of-band portion of NAND page.
Is there a chance SPL on devices with Hynix NAND includes a Hynix driver and SPL on devices with Samsung NAND does not? They might even be the same version, but the driver could be missing in one...
Click to expand...
Click to collapse
OK I'll try to explain a bit better... when the topaz (and rhodium) SPL boots, its nand driver code can of course handle either chip, but it relies on this nand config register having the right value on booting SPL (normally radio bootloader sets it up for SPL). this value is what changes on hynix units when or before loading SSPL, and I don't know why. - but I intend to find out
PS: the SPL binary itself is same for both types.

Is there any chance you guys will release a Samsung-only HardSPL with a big fat warning label?

HELP! Regular SPL and no OS!

**This is a unique issue so please help**
See below for what I've done so far... a lot of things have changed
Yeah so originally I had a problem with the earpiece not working so I decided to put on original ROM.
The problem is, I have a DIAM110 which doesn't have any official ROMs (not that I know of, that is).
So I had Hard-SPL and downloaded a ROM for DIAM110, and installed it, but no luck with earpiece problem. I then put SPL 1.93 (original) on it.
Then I found someone's dump of my original version, and I added the original radio and my original SPL that I dumped before. But I guess because I had original SPL or ROM wasn't built correctly, at 100% it said corrupted ROM.
Now when I turn it on I just see the black "TOUChDIAMOND" boot screen, and the numbers don't show up. Mtty works, but I can't seem to put any other OS nor can I restore Hard-SPL. And I can't find original ROM for DIAM110 that's signed by HTC.
What do I do?! Thanks.

So in other words I'm stuck in the bootloader. According to MTTY there is no OS left on my device. So basically:
-Stock SPL
-No OS
What to do?
This is output from MTTY:
Code:
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 3 (0x3) is reversed block
BLOCK 8 (0x8) 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 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
BLOCK 1477 (0x5C5) is bad block
OS NOT FOUND !!!
Cmd>info 9
NO user storage

*bump*
I've tried installing Hard-SPL 1.30, 1.93, and others (Olinex) but it freezes at 0% and eventually I get error 262.
~codeslicer

Hmm I wonder if anyone is reading this... but I might as well post progress in case anyone has this issue.
Anyways, I think this will take a long while to fix. Using mtty I connected my device, and ran these commands:
Code:
Cmd>info 0
Platform Model ID:DIAM11000
Platform HW Board ID:1, PROT
Cmd>info 2
HTCSHTC__017ýlˆ×HTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSDIAM1100HTCE
Cmd>
So, I found out that devid was DIAM11000, and CID HTC__017. So, I found my DIAM10000 ROM, opened up hexedit, modified the values!... and...
Still gets stuck at 0% with error 262.
=============
Still several things to try. I bet I can install Hard-SPL if I somehow get that DIAMIMG onto the internal storage. But HOW?
Or maybe I can connect my diamond to a Flash drive, fabricate a USB Y cable like the one in the service manual (the diamond apparently does not provide power to operate connected storage), format to FAT32, and install from there. If I get to that point (hopefully another solution will present itself), I really hope it won't get stuck at 0%.
I'm not giving up yet. Although a nudge in the right direction would be helpful.
~codeslicer

Let's see, just tried the boot command:
Code:
Cmd>boot
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fill RSVD information for block 288 to 321
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
If I quickly remove it after issuing command, I get stuck in the TOUChDIAMOND forever.
If I don't, then I can't turn it on (or it doesn't seem to), and I see the navi board's cool charging animation that doesn't end even if I remove the usb connection. A quick removal and replacement of the battery allows me to see either the tri-color screen or the bootloader for my enjoyment.
~codeslicer

the adventure continues
Probably the last thing I'm doing today. 6 hours of "fixing" is long enough!
BY THE WAY: If anyone knows all commands for diamond spl in mtty, please post!
====
So, I tried running task 2A. Erases everything. It even erased the last of HTC's customization - the beautiful TOUChDIAMOND splash. Oh well. But it didn't erase one thing and that's block 1477.
Anyways, something is strange here. After running task 2A, info 8 shows only bad block:
Code:
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 1477 FAIL !!!
Write 0xFF start page=0x4800, total page=0x1B800
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
BLOCK 1477 (0x5C5) is bad block
OS NOT FOUND !!!
Then, when I run task 28 55aa, the reversed blocks come back!
Code:
Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
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 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 1477 (0x5C5) is bad block
OS NOT FOUND !!!
Same thing with task 29:
Code:
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 1477 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS 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 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 1477 (0x5C5) is bad block
OS NOT FOUND !!!
Strange! I'm actually curious to running tasks 0-100, but that's probably not a good idea - HTC probably but task X in which bricks the device!
Time to get some coffee!
~codeslicer

Hi,
what does it say when your device is in bootloader?
can you take a pic?
EDIT: CHECK THIS THREAD
MG

Sure, pic is attached.
EDIT: I've tried doing what the link says, but I can't copy the file over because I'm only in bootloader mode.

*bump*
Apparently there are is some special key combination that can reset device? Which causes some heavy vibration and restores some things? If anyone knows, please respond.

No key combination will help you!
the problem you have is the fact that you have not read a single thing on any thread.
I cannot get my head round why, WITHOUT HSPL you would be using MTTY? that i have to say is quite possibly the most stupid thing i have heard this year!
Because you have NO HSPL, you can ONLY flash vis USB a stock rom which originated in your country. because you have SPL, you cannot bypass the security which allows you to flash cooked roms.
there are 2 things you can do, download EVERY stock rom you can find and attempt to flash it via USB until you find one that works.
Or 2, because your device has normal SPL, you could probably call HTC tech support, and just say that your phone was fine last night, you turned it off and the only thing you can now see it the logo screen and bootloader.
as i said, this is the most stupid thing i have heard of, its just insain! what kind of "special" person uses MTTY with NO HSPL?
I mean even if you read the threads on MTTY (which I wrote!!) they clearly say:
MysticGenius said:
AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!
Click to expand...
Click to collapse
MG

You flame too much man. I've read everything. But in my situation I have to TRY new things. Do you think I would really go through all this problem when I could just flash a stock ROM? I guess you didn't read my thread. Because I just have a white screen now, no logo.
Mtty can still be used without Hard-SPL it's just more dangerous. But at the time I thought I had no choice because all stock ROMs I've seen are for DIAM100, not DIAM110. I even emailed HTC asking for stock ROM for DIAM110. They said such does not exist. So trying all is pointless.
I guess I'll soon have no choice but to call HTC. Problem is I don't have a warranty. Anyone have experience with HTC's phone support? Is it free?
Also, I don't want to tell them that my phone just all of a sudden stopped working. That would mean defective hardware.
~codeslicer

Alright, well I've called and emailed HTC numerous times, and with no ROM download available, they only option they say is to send it to repair. But... paying $135 to have a ROM reflashed does sound a bit ridiculous.
These are the options left:
Modify a ROM to make it work with the stock SPL
Install Hard-SPL or another SPL alternative from bootloader mode
Copy a ROM or Hard-SPL to Internal Storage somehow, or
Try experimenting with the USB trigger mode and somehow get it to read Hard-SPL/a ROM from a flash drive. Anyone know if the SPL can be updated from USB trigger mode?
So if anyone has any suggestions or links, please share. You'd help not only me but others with this issue.
~codeslicer

Alright, after looking more closely at the HTC service guide, it seems that it will indeed be possible to override the bootloader from USB Trigger mode! Look at the attached image. The "OK" next to Bootloader leads me to believe that the bootloader can be overridden in this mode, so Hard-SPL can be installed.
The reason I think Hard-SPL can't be installed from bootloader is because the memory is in use? Or am I wrong and Hard-SPL can ONLY be installed from activesync?
~codeslicer

codeslicer said:
Alright, after looking more closely at the HTC service guide, it seems that it will indeed be possible to override the bootloader from USB Trigger mode! Look at the attached image. The "OK" next to Bootloader leads me to believe that the bootloader can be overridden in this mode, so Hard-SPL can be installed.
The reason I think Hard-SPL can't be installed from bootloader is because the memory is in use? Or am I wrong and Hard-SPL can ONLY be installed from activesync?
~codeslicer
Click to expand...
Click to collapse
I flash HSPL on diamond same way as a rom! (from internal storage!) so yes HSPL can be flashed directly from bootloader.
MG

MysticGenius said:
I flash HSPL on diamond same way as a rom! (from internal storage!) so yes HSPL can be flashed directly from bootloader.
MG
Click to expand...
Click to collapse
Hey, thanks for the response. I haven't yet seen a way to transfer the NBH to my internal storage as there is no OS so I can't transfer files. When I try to install Hard-SPL using bootloader/USB connection I get stuck at 0%.
So anyways do you know of a way to copy file to Internal Storage when it's in bootloader? If not, I'm going to make the USB connector for the Trigger Mode, there are many posts on how people succeeded like here: http://forum.xda-developers.com/showthread.php?t=413510
~codeslicer

First of all to solve your problem you have to find the country your diamond is from...For that you have to enter
http://service.htceurope.com/htcdistributor/Default.aspx
and to print all necessary information about your diamond... Then you will recieve the country (in my case it was made for ITALY).. Then the most part of Diamonds have a chip on their keyboard, which wouldn't permit you to upgrade your firmware or SPL so simple..Then you have to find the Operator Firmware (most of operators as 3G, AT&T etc. have it's own firmware)...You have to download all existing operator firmware of the country it was made for and to upgrade your firmware( in my case it was 3G ITALY)... Then following standart instruction you have to put HardSPL and firmware you like...
Sorry my BAD english... P.S. it works 100%!!!

Hey,
Thanks for your reply. Your english is fine. This is what I got:
Code:
SN : #omitted#
IMEI :#omitted#
Part Number :99HEJ116-00
Part Description :SKU,HTC,English-US,USA,UMTS 850/1900,Cut,Brightpoint US,Black,w/o SIM Lock,DIAMOND-C9
Customer Name :
Customer Model :
HTC Model :DIAMOND-C9
Error Message :
I already called HTC asking for firmware. They say their website does not have it. Do you know who would have it?
~codeslicer

Ok, well I now have a home made Y USB cable with flash drive. When I put stock ROM with wrong version I got "not allowed" error so I know it can read file off flash drive. When I put Hard SPL image though I get stuck on "Loading...". Is there a working Hard SPL to flash from internal storage/external usb or something else?
~codeslicer

Also tried Trinity SPLxploit using wdata and the third option... no luck.
HTCFlasher didn't work on Linux (/dev/ttyUSB0 not found/mounted; problem with ipaq module), so going to compile it on Win32 with cygwin and see how it goes.
~codeslicer

Ok, made a request to where I got it from (Amazon) to ask HTC to make ROMs. It'd be helpful if anyone with this issue could do the same - you'd help others as well.
~codeslicer

MTTY and Error 262 when trying to instal HSPL till the Doc shows up...

Well, what happened:
i flashed hspl
i flashed Dynamics_GTX_2.4.5_WWE_Kovsky.nbh
i was happy
i realized that i cant sim-unlock here, so:
i flashed orig. spl aka RUU_Signed.nbh
and then i flashed original APP_SW_X1i_MOBCOM_AT_CDF1215-0312_KOV_R1AA019.nbh
then i sim unlocked the phone by code
then i went directly for a 28
it hang itself when i tried to do flash hspl at 17%
since then, i get everytime stuck at 0% and get the msg 262
even messing around with mtty and all different roms and programs and settings didnt lead any further.
task 28 looks like:
Cmd>task 28
Format start
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
Cmd>
task 29 looks like:
Cmd>task 29
Format BINFS start
CE start start block=321, total block=3775
Write 0xFF start page=0x5040, total page=0x3AFC0
Format BINFS end
Cmd>
task 8 seem to take forever, the screen shines in bright white.
with power and vol down i see:
3 colors
kovs110
spl-0.72.0000
microP1-707
microP2-707
serial (which, ofc. turns into usb when i am connecting it)
from there on everything went fine, but the flashing.
ofc i try to flash hspl, but every method hangs at 0% with error 262
mtty up and running (as far as i can see ) i definitely need help.
crawled the forums für 18 hours now, i cant find a solution to this on my own.
btw. cant load something on the card, otherwise i would have tried to load from the map...
again, i call for HEEEEEEEEEEEEEEELPPPPPPPPPPPP!!!!!!!!

no one? :O
do i have produced a brick?
playing around to find out whats going on:
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: Kovsky, Bootloader Version : 0.72.0000
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=micron_mt29f4g16abc
DEVICE ID=0xBC
DEVICE MAKER ID=0x2C
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
.
.
.
BLOCK 32 (0x20) is reversed block /////// that seems to be quite long, in the documentation it goes just till 12 and then it shows partitions, which are not showed at my device :/
OS NOT FOUND !!!
Cmd>checkimage
SPL CRC checksum = 0xEC2F928F
CE is None.
ExtROM is None.
Cmd>task 32
gives no output.
is it possible to flash per mtty? (LRS?)
btw it boots into white screen, not three color bootloader screen
with power vol down into bootloader without any problems
but from there on it always stucks at 0%
//edit
set up an old laptop with winXP and tried it there - you never know? - didn't work...
//edit #5
got a micro sd card
formated it with fat32, put the RUU_Signed.nbh on it,
renamed it to KOVSIMG.nbh, put it in the phone and started it with vol down and powerbutton to the bootloader.
hangs at loading...

come on guys, some one have to have something to say!

To be honest it does not sound promising
try this with mtty
Cmd>set 16 0
Cmd>task 14 0
Cmd>reboot
then try and flash a stock rom

when copied on the sd card, it hangs at loading
when flashed over usb, it hangs at 0% at the progressbar

if you try another hspl does it just sit at 0% ?

i just tried this one out: http://forum.xda-developers.com/showthread.php?t=431218
are there other versions of hardspl?

sorry i meant doing another hardspl with the version your using

yep... just sitting at loading or 0% depends on the way i try to flash
i think, somehow the partitions are ****ed up,
is there some one who knows the mtty and bootloader stuff very well?

have you thought of trying one of the Android NAND roms? If you can just get it to install, you could then go back to windows mobile

do i not need hard spl for android?
does android not get flashed like a windows rom?
i ll read into that, thx for the tipp

It's similar to windows roms yes, but there is a version (ICS 4.0.4alpha), that changes the internal partitions so as a long shot you could try this and then try flashing back to a windows rom.
The thread in question is
http://forum.xda-developers.com/showthread.php?t=1614236