yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] Zinken:
First of all, thank you for this guide. If it solves my freezing issues and eliminates the need for flashing a stock rom between upgrades I will be very pleased.

One thing though: when executing the formatting with command "task 28 55aa" I het a different output,

Cmd>task 28 55aa

Format start

Fill RSVD information for block 288 to 321

Storage start sector=0xBB00, total sector=0xED40

Storage start block=781, total block=949

Total Bad Block in CE: 3

Erase physical block from 1074 to 2048

formatstorage Bad block found: 1329

formatstorage Bad block found: 1389

formatstorage Bad block found: 1525

Format end

Do you know what these bad blocks mean?

Thanks in advance!
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
Currently I dont know what the Bad Blocks mean, can you flash you device?

If you can i wouldnt worry as sometimes i get bad blocks and sometimes i dont!!

I have been looking for ages for info on this but i guess it is privy to a select few!!

MG
[Touch Diamond, MDA Compact IV ROM Development] Zinken:
Yeah, no problem to flash and no issues noticed after flashing. In other words nothing to worry about I guess.

Thanks anyway.
[Touch Diamond, MDA Compact IV ROM Development] cashlee:
hello

i am using vista 64

i have a problem with "Driver Installation "

at step 9 when i have click on 'have disk', i have select the "wceusbsh"

when i clicked on OK , it said

" this folder doesnt contain a compatible software driver for your

device. If the folder contains a driver, make sure it;s designed to work with

windows for x64 based system"

i also tried it on safe mode, but it doesn;t work
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
Hi,

I think you need this:

(It is posted at the bottom of the driver installation section, maybe ill move it to the top!!)

MG
[Touch Diamond, MDA Compact IV ROM Development] kwambewright:
32 bit sys

which drivers do i use for a win 7 32 bit system?
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
the ones for a 32 bit system? (What kind of question is that?:confused:)

Do you really need talked through that? and no your question is not valid its stupid!

x64 means 64 bit

x86 means 32 bit

MG
[Touch Diamond, MDA Compact IV ROM Development] edefux:
hey guy´s i have problems with step 7 flashing from internal storage.

"7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and IMMEDIATELY press and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash"

this is the way you describe it. i ran mtty and all the commands worked ... last task immediately disconnected the device. i pushed the red button with the pen then held the volume key down and pressed the circle button at the same time. this brings me into a menu where i have 3 options ... i took the first one "restore to factory settings" the i pressed vol up to boot but i can not iniciate the rom flash !!!

i immediately held vol down and back ... the device restores only the factory settings, but still my aztor rom is on there (???) no flash

what did i do wrong ... can i now savely flash throug active sync, am i through with the mtty process now?
[Touch Diamond, MDA Compact IV ROM Development] neoceltic:
Have you previously copy the new diamimg.nbh (the ROM that you want to flash) in your internal storage? :confused:

If not, the vol down and back button do nothing because there is no image file ROM to flash! ;)
[Touch Diamond, MDA Compact IV ROM Development] edefux:
thanks for your fast reply ... but i did copy the diaming.nbh to the root of the internal storage ... even renamed it in DIAMING.nbh to match the instructions ...

?(
[Touch Diamond, MDA Compact IV ROM Development] neoceltic:
Yes, but you'll have to rename as DIAMIMG.nbh (not DIAMING.nbh). it is for DIAMond IMaGe. :p
[Touch Diamond, MDA Compact IV ROM Development] edefux:
omG .... thanks mate ... how did i get through university with this sort of reading disorder (?) ;)

XP users like me ... no need for the driver installation

thx for this great guide
[Touch Diamond, MDA Compact IV ROM Development] Shizophren:
Hi, i have the same Problem at Step 9. I cannot choose the wceusbsh.inf File.

I started my Vista 64 bit in this "ignore digitally signed drivers" mode, but i still get the messege, that the driver is not supportet on 64Bit OS.

My Device is connected and the bootloader says USB. What can i do???

OK, the W7 X64 Driver seems to working, but after installing i get the messege that my device cannot be started...whats that?
[Touch Diamond, MDA Compact IV ROM Development] Jujulian:
Since I did this the first Sign of Live is the Diamond Logo and afterwards I get the Diamond Logo again with the rom infos etc in the right corner...

Berforhand that act was faster and I had the rom infos direct...

A clue what I can do to fix this?
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
I dont really understand what you are asking, but i dont believe you did have it faster, i have never once turned my device on and had the rom info immediately, it ALWAYS appears after a few seconds.

I think you have just noticed the small get between the logo showing and the text appearing!

Nothing can fix it, it is how the phone boots!! pretty much the same as your PC, you turn it on, see a black screen, then the white text appears!

I hope i answered your question?

:) MG
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
which drivers are you using? did you use these:

x64 Active Sync Drivers.zip

or the ones saying "Win 7 Tested"

Either set of drivers SHOULD work on vista, but i cannot guarantee this, however i can tell you that all drivers do work and they have been tested and verified by numerous people on the thread.

the only thing i can suggest is that you may have missed something? or try the other x64 drivers and get back to me with the results.

If the worst comes to the worst ill install x64 vista on a virtual box and run through the install myself.

MG
[Touch Diamond, MDA Compact IV ROM Development] kwambewright:
Sorry for my ignorance! I saw the x64 equaling 64 bit and figured it would be the same for 32 bit. My computer knowledge is not that great. Its fine now, I did it on my XP partition and it worked fine. I was hesitant to try on XP because the last time I tried it did not work on either but that was because the instructions were no where near as clear as these and they had me using cmd>task 29. I apologize for looking like an idiot and inconveniencing you with such a heartfelt reply.;)
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
Its ok, I was just a bit stumped by the question!!

task 28 is a command of a different bootloader to format, i think it is from the Himalaya device!

as long as your sorted now!!

MG :)
[Touch Diamond, MDA Compact IV ROM Development] Krzysiec:
I`m running WIN 7 and ... After trying to update driver with working and tested WIN 7 driver System is warning me about not digitaly signed driver and after all (reset PC and enter to bootloader) Serial doesn`t change to USB ... Any idea ?
[Touch Diamond, MDA Compact IV ROM Development] gorbett:
how long does it typically take for a ROM to load? my diamond has been sitting at "Loading..." for about 20 minutes after following the internal storage steps.

thanks!
[Touch Diamond, MDA Compact IV ROM Development] Krzysiec:
Ok my previous post is out of date ;) Stupid me i didn`t noticed there was write to run WIN 7 with f8 and turn off signed drivers checking ;) After that everything went right :) THANKS a lot for GREAT HOW TO ! ;) Cheers !
[Touch Diamond, MDA Compact IV ROM Development] Reb0rn:
still cant belive they havent stickyd this thread... its not something you just let pass by...
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
Takes about 5-6 mins!

MG
[Touch Diamond, MDA Compact IV ROM Development] mderksen:
I have got some problems.

I installed the correct USB (2003) drivers.

Rebooted my device and copied DIAMIMG.nbh to the internal storage root.

Started MTTY and used the MTTY codes, no problems so far.

Disconnect the USB cable after last MTTY code and did Hard-reset.

But it doens't show "Press VolUp to boot". It displays

1. Press VolUp to restore manufacturer default

2. Press VolDown to restore manufacturer default and format moviNAND.

3. Press other keys to cancel

What happend? :(
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
follow this instructions, you havent done the hard reset, you only get vol up to boot after hard reset, all you have done is initiated the hard reset, not actually started it!!

MG
[Touch Diamond, MDA Compact IV ROM Development] mderksen:
This is my MTTY output:

After this i get to point 7. I removed the USB cable from my device and did hard reset (Pen Reset, then Press and Hold Vol Down and Circle). But I still get this menu:

1. Press VolUp to restore manufacturer default

2. Press VolDown to restore manufacturer default and format moviNAND.

3. Press other keys to cancel

*edit*

I'm using the BsB6.5Q ROM btw (http://xdaforums.com/showthread.php?t=506533)

Thanks
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
so press volume up to hard-reset, then press volume up to boot.

this thread is about MTTY, and hard-resetting is common knowledge so im not covering things like hard-resetting.

i dont see the problem, i assume you know how to hard-reset?

MG
[Touch Diamond, MDA Compact IV ROM Development] mderksen:
Thank you very much!

I thought the hard reset was already been done by pressing the reset button + vol down + circle. It worked now. Sorry for not understanding. But I thought you had another menu when pressing reset + vol down + circle.
[Touch Diamond, MDA Compact IV ROM Development] MattJ1989:
Just wanted to say thank you so much! Made my Diamond work perfectly again!
[Touch Diamond, MDA Compact IV ROM Development] Riel:
I want a new rom. I want to format the device first to make it best.

I do a format (it's clean then)

I do a hard reset (the old rom is installed back)

I flash new rom (over the old rom)

What's the advantage ?

Another question is this:

ON first format I got:

Erase physical block from 1168 to 2048

Then I flashed new ROM, and did MTTY again (for my feeling eliminate the above problem) and with the format after the new rom flash I get:

Erase physical block from 793 to 2048

Looks like a good 400 blocks more?

And last:

7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and IMMEDIATELY press and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash

Why can't I do:

7: Immediately DISCONNECT your device and Hard-reset (Pen Reset, then Press and Hold Vol Down and Back) (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
No Problem, im glad to help :):)

MG
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
what are you talking about?

how can the old rom be installed when you have just formatted with MTTY?

Why are you doing this without knowing what your doing? also if your using this thread you should know why your performing these actions!!

THe reason for this is VERY well documented on this site, and can be easily found if you read the first post of most ROMs, here is an example from the BSB thread:

Firstly, why MTTY, flash a rom then MTTY again? why are you doing this? it does not say anywhere to do this.

It is quite obvious why this has happened, the first ROM was Smaller then the second one you flashed.

why would you do this?

I dont know, just press the buttons, they are in the same place on every Diamond.

Im really sorry to say this but you havent asked one question here, and all of your errors and questions have been addressed in the thread and the instructions.

I can only suggest you read the instructions and follow what they ACTUALLY say, not what you have done.

MG
[Touch Diamond, MDA Compact IV ROM Development] gozeff:
quote:

6b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:

---------------------

MTTY OUTPUT:

---------------------

CMD>set 14 0

HTCST UEHTCEUSB>

---------------------

my device behaves differently. it says:

----------------

Cmd>set 14 0

HTCST ÚÈÒHTCE

Cmd>

----------------

should i go on with the process? i just wanna be sure it won't damage the device. thanx in advance.
[Touch Diamond, MDA Compact IV ROM Development] Riel:
It's not that I didn't know what i was doing, in fact, used MTTY a lot. This morning I was thinking what info the hard-reset was trying to write, but it doesn't :)

I was wondering why to hard reset first, and then engage the flash procedure from NAND, and not immediatedly start the flash procedure?

So all my questions were stupid, and the different sizes are obvious to me now :)

Sorry bothering :p
[Touch Diamond, MDA Compact IV ROM Development] Riel:
But still:

This is whats actually happening throughout the process:

-------------------------------------------------------

1: Enter bootloader

2: MTTY

3: Hard-Reset

4: Flash ROM

5: Hard Reset

the effect of this process is:

1: Bootloader gives access to the NAND

2: MTTY formats the NAND (removes the existing rom)

3: Hard-Reset clears the device and partition

4: Flash sends ROM to NAND

5: Hard Reset cleans out the files left over from the flash.

does that make it clearer?

MG

-------------------------------------------------------

But what I meant to point out:

1: OK

2: OBVIOUS

3: IT REINSTALLS THE LAST ROM? (Back to factory settings, progress bar)

4: FLASHES NEW ROM FROM DIAMIMG.nbh

5: IT INSTALLS FLASHED ROM

Or do I see that wrong?
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
Hi,

if you read the thread, the outputs displayed by mtty sometimes vary dont worry bout it.

MG
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
No problems!!

No, this resets factory settings of a ROM is present on the NAND, if there is no ROM present, all settings are ZERO, resulting in the device clearing any files left by MTTY.

then you flash to a completely empty NAND with your new ROM, and this is what stops the bloated ROM effect, which is caused by fragments of previous roms being left on the NAND and interfering with the new rom!

MG :)
[Touch Diamond, MDA Compact IV ROM Development] Riel:
I am sorry if I don't get this :) But:

when formatting the NAND, the 'previous' rom is not gone, it is still sitting somewhere (since I can recover it by hard reset?).

No, this resets factory settings of a ROM is present on the NAND, if there is no ROM present, all settings are ZERO, resulting in the device clearing any files left by MTTY.

Than resetting should not make my phone boot at all before flashing a new rom?

It still does here ...

so:

when I task 28 55aa?

reboot with task 8

perform a hard reset (writing zero)

it will boot the previous rom! (preparing device for first use blabla)

Are there different places where rom-info is stored?

When I flash a nbh file, is it going somewhere else first?
[Touch Diamond, MDA Compact IV ROM Development] moeper:
Hi mystic,

how do I know, if the ROM flash happend? I do all you descrip, but at the point "press vol down + back arrow" everything is going very fast and I can´t believe, that the flash worked, how do I know if flash worked or I only start my old flash with some hard reset problems...???

THX
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
the flash from internal storage should only take 2-3 minutes!!!

it takes 10-12 from USB!

if you followed the instructions ytou will have sucessfully flashed your phone!

Congrats

MG ;):)
[Touch Diamond, MDA Compact IV ROM Development] moeper:
is there a visual recognition? Cause I think after pressing Vol Up the phone directly reboots and start the old flash and nothing real happens withal pressing minus + right...mhhh....cause I have the problem with my flash that it says two theys one after another, "phone could not boot correctly, press send du reset or some other key to continue [...]" and after pressing some key it has done half a hard reset and 75% of data were lost...very strange...hope this is done by now, or I did it not correctly and don´t have a real mtty flashed mobilphone...
[Touch Diamond, MDA Compact IV ROM Development] eruvaer:
Hi MysticGenius,

first thanks a lot for this thread, helped me to fix some strange problems with my diamond :).

As a suggestion, could you add to your first post that this also works out of box with windows xp? Because I first tried several times with windows 7 and didn't get the drivers to work, till I read somewhere else that it should work with xp w/o installing drivers. Tried it and had no problems. Voted for sticky :).

Greets Eruvaer
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
Sure thing!!

MG
[Touch Diamond, MDA Compact IV ROM Development] ascorpion:
I've got some problems with my MDA.

In mtty output i get 'Total Bad Block in CE: 1'. Tried many times. It happens all the time. Then i tried 'task 29' (thx to cmonex for tip but still no results)

Maybe i paste whole mtty output and somene could help me and other people who gets those message.

Cmd>set 14 0
HTCST ÚČŇHTCE
Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 321
Storage start sector=0x7700, total sector=0x13000
Storage start block=509, total block=1216
Total Bad Block in CE: 1

Erase physical block from 800 to 2048

Format end

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 339 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end

Cmd>task 8

Hope someone can help, Regards.

PS,

I use Hard SPL 1.93, phone is SIM UNLOCKED. I use cooked ROMs like Nataly and Cloudy 1.3.

Tried upgrading to STOCK rom but after a week i got random hard reset with Error which is show in the picture.
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
Help with what? just flash a different rom!

the error you show in the pic is caused from a Manila 3D error, flash to a different rom!!

No-one can do anything about bad CE block, also if you read the thread this has been covered a few times

Dont know why you would do this, this formats the BinFS not the NAND!!

I still dont know what exactly you want help with?

MG
[Touch Diamond, MDA Compact IV ROM Development] ascorpion:
Just wanted to know how to format and clean phone with mtty when i get bad CE block...

but if you say no-one can do anything with this.

Thanks for answer
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
As i said if you read the thread, there has been 2-3 people mentioning that they have some bad blocks, even some CE block errors.

but as long as you can flash your device!!

MG
[Touch Diamond, MDA Compact IV ROM Development] pietvu:
type

In the tutorial it said type but i used copy paste. That’s why it did not work. I hope my comment saves other people some time.

Thank you for the description.
[Touch Diamond, MDA Compact IV ROM Development] 4D3:
It says all the way through the instructions "type" did you read them?

MG
[G1 Q&A, Help & Troubleshooting] AdrianK:
Hi, I'd like to have a go at making my own rom for personal use and I'd like to base it on Rogers. Does anyone know where I can find a plain Rogers rom, or a build with hardly any modifications?
[G1 Q&A, Help & Troubleshooting] pinetreehater:
I think one of the first places I would start is here

There are some more ROM databases out there, but this one is fairly comprehensive.

Good Luck,

Pine
[Touch 3G General] ecotack:
My Jade use to get a reasonable WiFi signal at home, even outside at the garage. Inside would always give 54Mbps. However yesterday we got WiFi at work and my Jade struggled to get a signal in the next room. Checked my WiFi at home and now its struggling to get a signal in the next room there also, even near to the router it won't get a full signal or 54Mbps.

Other WiFi device are getting full signals at both home and work.

I have not changed any settings or installed anything in the time between knowing I can get a good signal and now.

Any ideas?
[Touch 3G General] MvBoe:
It sounds like a hardware-defect. :(
[Touch 3G General] azahidi:
Try softreset and try activate wi-fi again. See if it works ok. If not it could be hardware defect (the wi-fi chip maybe)
[Touch 3G General] MvBoe:
One additional idea: See under "Start/Settings/Connections/WLAN/EnergyMode" (translated from German, perhaps similar) and adjust the energy-mode to performance-optimized.
[Touch 3G General] ecotack:
First thing I tried was a soft reset, didn't make a difference. Performance is selected over power saving.
[Touch 3G General] MvBoe:
Any difference, if you change it to "performance"?
[myTouch 3G, Magic General] willko:
Hi all,

I was hoping someone could explain some of the data from the FASTBOOT screen...

I have an HTC Vodafone Magic and this is what appears on the FASTBOOT screen:

SAPPHIRE PVT 32B SHIP S-ON G

HBOOT-1.33.004 (SAPP100000)

CPLD-10

RADIO -2.22.19.26I

Apr 9 2009, 23:30:40

In particular, what does the "S-ON" vs "S-OFF" signify?

I take it the "G" indicates Google branded HTC?

how about "HBOOT-...."?

and the "CPLD-10"?

A friend came round a few days ago, flashed my ROM to the Smartphone France 2.5.0 ROM so I could sync with exchange server ( mixed reations ATM, contacts sync keeps giving errors... heard it was not fixable?). That's what lead me here... ;)

I'd like to try the recovery-RAv1.1.2G.img and the latest 32B Hero (pure black) - VODAFONE MAGIC - KITCHEN and see if they're any better, specifically for the exchange syncing.

Better know my basics first though,... I hope I haven't missed an obvious post that discusses this by my search efforts using "ENG S-ON" and "CPLD-10" returned nothing (too short? bad syntax?)

Any help/explanation much appreciated - Also any comments re: the proposed ROM flashing above...? i.e. is this a "good" choice ATM?

Many thanks, and what a great community! :D
[myTouch 3G, Magic General] SamuriFish:
read this place first

Hi

Im new to this as well I found some great resources here.

check this out, i didnt and had to lean the hard way:

http://xdaforums.com/showthread.php?t=519523

hope it goes well
[8525, TyTN, MDA Vario II, JasJam ROM Development] Scotty93:
ive made a theme and cooked it into the rom but i dont know how to make it start with that theme as the standard theme.

any help would be useful, thanks in advance
[8525, TyTN, MDA Vario II, JasJam ROM Development] + Que PPC:
i had this question too... so i think in the folder that contains the start icons must be a rgu with that reg entrie... then I think we must to add some entries in dsm files from base dpi96 themes dpi 96 resh resv and other where themes resides.

Will search around that folders for that RGU
[8525, TyTN, MDA Vario II, JasJam ROM Development] Scotty93:
ok, i thought it would be a registry entry somewhere but i dont know much about them so didnt really know where to start
[8525, TyTN, MDA Vario II, JasJam ROM Development] joshkoss:
if 6.1 you will use:

EXEC: \windows\cusTSK.exe \windows\HTC_BrandGREY.tsk

if 6.5 u would use TSK: \windows\HTC_BrandGREY.tsk

Closing thread. This question should be posted in a kitchen thread not a new thread.
[Touch Pro2, Tilt 2 Windows Mobile General] PqRambo:
Does anyone have the reports of messages sent to work as it should be?

If I send an SMS message by the default editor, I receive the report sent messages, but if i use the editor of TouchF, then i dont receive. The only way to overcome the problem, is to enable the sms sent report to all contacts for each new message that i sent.
[Windows Mobile Development and Hacking General] Ar5enal:
Hi,

Did anyone have a try on the accelerometer on the new Tosh TG01. Seems jsr256 is not on the device. :confused: If anyone is able to crack the accelerometer implementation pls let me know.:o Thanks
[XPERIA X1 Q&A, Help & Troubleshooting] melaskalany:
Is it out yet? :confused: