PDA

View Full Version : HELP! Weird diamond / problems with Memory ?


luftdieb
27th July 2009, 11:29 PM
Hi,
in the past few weeks, I tried many different ROMS mostly based on WM6.5.
The Diamond rans really smoothly without any problems of stability and reliability.
But since one week, I'm having problems.
The problems begins, that the device restarts by himself e.g while I'm playing kevtris. But this restarts happends not from the beginning. So I could playing a couple of hours without problems. And suddenly, the device restarts with the initial phase of WM with calibrating touchscreen...
I assumed problems with this ROM (EnergyROM_DIAMOND_20090629_Standard), then I tried several ROMs with WM6.5 (e.g.CleanBlackBasic31). But all of them doesn't allow me suddenly, to install all my desired cab files, I had installed sucessfully in the past.
I went back to WM6.1 ROMs, where I used sucessfully in the past. But also with this ROMs (e.g. AZTOR_V11-GER-ULTIMATE), the installation of my cab files crashing after WM complete the initialization process. This happends not with the first cab file. I'm installing 3-4 files without any problems. And then while the installation of the next cab file, the installation failes. When I'm going to "Windows - Programs", all installed packages of myself having no original Icons. When I'm trying to start one of those "blank" icons, I'm starting a neverending process. I can't abourt such a start. After I'm doing a reset, the device hangs (for >15 minutes) at the initialization screen, where the ROM version will be shown. When I'm resetting again, WM starts with the initial phace of WM with calibrating of touchscreen. But this WM is not in stable condition. I have to reset to factory settings to get a running WM back.

I tried also the reset to factory settings (VolUP+EnterButton) many times, which works, but didn't solve my problems.
The radio ROM I used since ~ 3 month 1.09.25.23.

Have anybody an idea? Could this a hardware problem of the internal memory? Is there any stronger reset posibility which avoid problems of previous installation?

Best regards
luftdieb

TreeUK
28th July 2009, 12:19 AM
I've been getting similar issues, programs refusing to run complaining there's no memory even when no programs are in memory.

mancsoulja
28th July 2009, 02:33 AM
Its just because you have flashed many roms :p when you flash a rom old system settings and such get left over from previous flashes, and after abit and many flashes all this info gets mixed up and corrupt, try using mitty to format your device, this will erase the portion of the memory where these settings are held, then flash a stock rom, this will install the default htc settings, then flash a rom of your choice :D

mosec
28th July 2009, 08:36 AM
I had the same problem which was solved after I flashed shaks 4.30 rom. Somehow I wasn't able to flash any of the stock roms. Anyway try a stock rom or that mtty tool and everything will be fine:)

luftdieb
29th July 2009, 12:08 AM
@ALL: Thanks for your reply. I just used the search function of the forum and found the following page about mtty (http://wiki.xda-developers.com/index.php?pagename=Diamond_Bootloader)
I could also get a connection to my diamond with mtty. But up to now, I didn't have the heart to do one of the following commands:
task 28: Format NAND
task 29: Format BinFS
task 2a: Format ALL

And what means: 28 55aa will also reformat the "partition"

What happends after I'm doing such a formating? Is a operating system still on the device? Or is only the SPL Bootloader active, which I have to use to get a new .nbh file on the device?

I just did a few commands with mtty:

Cmd>checkimage
SPL CRC checksum = 0xCB7389E9
CE CRC checksum = 0x3B4697DA
ExtROM CRC checksum = 0x0

Cmd>info 7

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
Partition[0], type=0x20, start=0x2, total=0x3E
Partition[1], type=0x23, start=0x40, total=0x800
Partition[2], type=0x25, start=0x840, total=0xC3C0
Partition[3], type=0x4, start=0xCC00, total=0xDCC0

CE Total Length(with sector info) = 0x6666000
CE CheckSum Length(without sector info) = 0x6600000

Cmd>info 9
Storage Start Addr=0x56A20000, length:0x6ECE600

Thanks in adavnce for reply...

mancsoulja
29th July 2009, 12:29 AM
when you run task 29: Format BinFS, it will erase everything on you device, even the os & system partition which is most prob causing the problem, no worries tho when you switch the device on it will show the touch diamond splash, so just put it into bootloader, then connect it to your pc, you can flash a new rom using an ruu :)

luftdieb
30th July 2009, 09:06 PM
Thanks for this good advise. Everything looks really good after using "mtty", doing "task 29", using ruu and flashing any firmware.

Best regards
luftdieb