Hi There
Diam140 - Olinex:1.93
Used to change ROMs almost everyday - flashoholic. And one bad day a flash failed and after that
Diamond is behaving strangely. Tried 'MTTY'- {task 29} and {task 28} as well. And here is the output
from both:
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
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
task 28
Format start
Fill RSVD information for block 288 to 321
CorrectNandAddr detect error addr =0x3800F164
CorrectNandAddr detect error addr =0x3800F164
CorrectNandAddr detect error addr =0x38000000
CorrectNandAddr detect error addr =0x38000000
CorrectNandAddr detect error addr =0x38000000
bad=0x1D20
R:NO bad block reversed for block ID 0x1D20
CorrectNandAddr detect error addr =0x38000000
ERASE FAIL: 0x1D20
W:NO bad block reversed for block ID 0x1D20
Write NAND Faild
Now if the power button is pushed, after 10 minutes device vibrates and comes up with a greyish screen
and after half an hour or so it can be put bootloader. And some times the battery charges with ring
light animation. But flashing any ROM stops at '0%' without any progress and also Hard Reset not
happening - same no progress bar. Checked 'mtty - info 8' and this is what it gave:
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
OS NOT FOUND !!!
So wanted to change the NAND as above 'samsung_k9k2g08', however Diamond does not use any such chip and
it uses a different combo Nand ROM Memory by the name 'Samsung NAND - KMXEE0A0CM-S600' which is not
possible to change since it is a BGA, atleast with what tools one normally have at home.
Now can someone help reviving the almost bricked Diamond (well some PMs did not do the trick). Any help
is highly appreciated and Thanks in advance
Hi there,
Still stuck with the Device in the same condition. However now this is the output of 'TASK 29 or 28' of late....(given is the end part since it scrolls from the first address)
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FB
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FC
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FD
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FE
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FF
R:NO bad block reversed for block ID 0x7FF
Read sector fail!!!
And also attached the screens for grey screen and HardReset without the progress bar .. can someone help ?
Well, I guess your NAND is broken. Did you try to flash in bootloader mode ?
WBR
viperbjk said:
Well, I guess your NAND is broken. Did you try to flash in bootloader mode ?
Click to expand...
Click to collapse
Hi,
Thanks for the response
Yes, tried flashing from bootloader, with no success. Progress bar stops at 0%. And now 'mtty - info 8 and 9' also gives same scrolling output with read error. Any way out ?
viperbjk said:
Well, I guess your NAND is broken. Did you try to flash in bootloader mode ?
Click to expand...
Click to collapse
Was toying with QMAT and bootloader and since the NAND was broken tried 'Write partition to NAND' with 7200A hotfix and after that though the 'task 28 and 29' of mtty were giving the same out of memory errors, the bootloader screen is showing 'DIAM100' instead of 'DIAM140'. Does it give any hope of reviving NAND with some commands either in QMAT or mtty. Well not being a technical person, expecting some engineering inputs/tips.
Thanks in advance.
.... Was just revisiting this thread to see any progress on the query or any solution posted by other members stuck in similar situation, well No Luck... still holding the dead diamond. But then have moved on to a fully customised iPhone 3G 16GB (JB and Unlocked) and may never ever come back to a WinMo and specially an HTC device. Thanks to all those helped directly or indirectly, it was pleasant visiting these pages at 'xda-developers'. Will be visiting these pages to update on the developments in future as well.....
I read your problems. was not to fix this by using J-Tag? me also interested in that topic, I read somewhere that it would be just mentioned J-Tag fix these problems. Sorry but my English is poor.
Hi isaac12,
Glad you are interested in these things, well did not get any tips from the experts of J-Tag. And tried on my own and reported all the results here. Still want to revive the dead diamond, in fact went to the extent of replacing NAND chip but realised it will be a very costly affair and getting the equipment/expertise was also out of question. So it remains dead......
I am in the same situation. I also use flashaolic.
Have a beer, its time to get a new experimental subject.
Related
I upgraded to WM6 to Schaps_WM6Pro_WWE_4.01_Full.exe after then i tried to go back to
838Pro_HK_ENG_WM6_Upgrade_20070712.zip , the operation stopped on the 20% and
crash Now I just have a 4 color screen showing HERM100 ,IPL-1.04 then HERM100 , SPL-2.03
i have tried to flash more than 12 Rom from wm6 and wm5 with no luck, i have tried to flash
the Radio only ver 1.54 and 1.51 and 1.50 and last 1.47 with no luck all stop and 1%
tried mtty.exe set commend 14 0, 1nb command not available, i think i have Type 2 bricks: Stuck in boot process
mtty output here:
-------------------
Cmd>
Cmd>task 32
CID: Wait interpreter timeout
Level = FF
Cmd>info 2
HTCSF kEØ(HTCE
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 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=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1900
Partition[2], type=0x25, start=0x3200, total=0x1A900
Partition[3], type=0x4, start=0x1DB00, total=0x1CD00
CE Total Length(with sector info) = 0x3C4D800
CE CheckSum Length(without sector info) = 0x3B60000
Cmd>
-----------------------------------------------------
other info:
Model: jasjam - imate
ROM Before Flash: Schaps_WM6Pro_WWE_4.01
Radio Before Flash: ?
Bootloader Before Flash: 1.04
Flash failed at: 1%
Flashing Radio: 1.54. - 1.51.- 1.47
Bootloader After Failure: 1.04
CID Before Failure Super CID: Yes
CID Corrupt: ??
Radio Corrupt: ??
No GSM Error: Yes
Stuck In Bootloader: ??
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Current Device Status: unusable -cannot boot , can see wm6 green screen before today screen
how can i fix it
many thanks
ehab
Help needed "NO GSM"
Thank you Ehab for bringing this issue, I have the same problem exactly, which happened when I installed Radio 1.54.07.0, which was installed completely, but the JasJam never been able to boot beyond the second splash screen with "No GSM" singe.
I tried the same thing you did and I have the same bad luck!
Heeeeeeeeeeeeeeeelp
Please,
Thank you
Help needed "NO GSM"
I'm wondering why when I do
task 32
I get Level = FF
not Level = 0
as mentioned in the Hermes Upgrade Proplems post
Heeeeeeeeeeeeeeeelp
Please,
Thank you
here is the Solution
My solution for the problem by usnig the SD card method,
get an SD card reader and do the followings:
1- Use your Clean formated SD card (formated as FAT32)
2- find original operating system, extract it with WINRAR, if its not already extracted.
3- When OS extracted, you will have 2 files or more.
4- Look for the file called "RUU_signed.nbh" or similar that ends with ".NBH" (lik "herming.nbh")
5- Copy the "RUU_signed.nbh" file or what ever similar that end with .nbh to the SD card
6- Rename the file to "HERMIMG.nbh"
7- do not use the " " meaning rename it as HERMIMG.nbh
8- Reboot your device to bootloader, (hold Ok button on left side and POWER button at same time and stick with stylus in RESET on bottom).
9- that will start bootloader and in few seconds the falshing will start, it will ask you to confirm flashing on screen by pressing the power button. (screen shot)
10- Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
11- a message will say flashing completed.
12- Do soft reset, volah- device workes.
that worked for me, I hop it will work for you
enjoy
Hi Guys,
some times ago i used mtty to clean the device to flash a new rom. After this i can't flash any file. No solution in the posts can help.
The device can start into bootloader (rgb-screen) with following message:
---------------------------------
DIAM100 64MB
SPL-1.93.OliNex
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x30
---------------------------------
all looks normal but when trying to flash a file it shows the gray flash-screen and stops at 0%. After a while it terminates with a communication error (error 262). Has someone an idea what i can do ? any tries with original shipped rom for example fails with the same problem. If some german guy can help my please contact me in icq (70582431) or msn ([email protected]) please !
Thanks guys !
try to reflash hardspl..
nothing is flashable ! i tried first to flash hard-spl again but nothing works... :-(
do you had h-spl before using mtty?if yes tell me what tasks did you used..
if no i think you have bricked your phone
hard-spl was on the device. the time before i flashed my own roms without problems till now.
i used the commands in the mtty-thread:
---------------------
MTTY OUTPUT:
---------------------
CMD>
---------------------
6b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:
---------------------
MTTY OUTPUT:
---------------------
CMD>set 14 0
HTCST ÚÈHTCEUSB>
---------------------
6c: type "task 29" to get your device formatted:
---------------------
MTTY OUTPUT:
---------------------
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 1337 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>
---------------------
6d: type "task 8" to ask your device reboot
uhmm strange i did mtty a lot of times using the same method and no problems...
Are you able to access your internal storage? i you can, try to get the ROM you want, then rename it to DIAMIMG.nbh and flash from internal storage, if you are flashing the 2.03 ROM from HTC, you might have problems too. Are you flashing that HTC Rom or is it a custom one?
Hi,
access to internel storage after clean with mtty ?? after clean there is no rom that can boot in the device to access it ! its fully naked
both is testet orginial shipped rom´s and custom rom's.
do you was having diamimg.nbh in your internal memory?
no, internal storage was cleared by hardreset - "restore manufacturer defaults and format movienand"
here are the outputs from mtty:
------------------------------------------
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 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 306 (0x132) is bad block
BLOCK 414 (0x19E) is bad block
BLOCK 873 (0x369) is bad block
BLOCK 1605 (0x645) is bad block
OS NOT FOUND !!!
------------------------------------------
Cmd>set 14 0
HTCST ÚÈÒHTCE
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 306 FAIL !!!
ERASE block 414 FAIL !!!
ERASE block 873 FAIL !!!
ERASE block 1605 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>task 8
hawkeyexp said:
no, internal storage was cleared by hardreset - "restore manufacturer defaults and format movienand"
here are the outputs from mtty:
------------------------------------------
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 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 306 (0x132) is bad block
BLOCK 414 (0x19E) is bad block
BLOCK 873 (0x369) is bad block
BLOCK 1605 (0x645) is bad block
OS NOT FOUND !!!
------------------------------------------
Cmd>set 14 0
HTCST ÚÈÒHTCE
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 306 FAIL !!!
ERASE block 414 FAIL !!!
ERASE block 873 FAIL !!!
ERASE block 1605 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>task 8
Click to expand...
Click to collapse
Did you try flashing a stock ROM? Try one that isnt newer than 2.03 (note: im not sure about vodafone Diamond ROMs, I have the unlocked version) use the .exe file, try to get the official one from their website.
I think that this is the reason why your flashes fail: http://forum.xda-developers.com/showthread.php?t=409425
hello,
I solve my error 226 by format MTTY with command task 28 55aa.
Perhaps that help you !
hi, also tested but didn´t help !
Is there a way to check the NAND storage for errors? I get errors like this from a "dmesg | grep block"
Code:
yaffs: Attempting MTD mount on 31.3, "mtdblock3"
block 944 is bad
block 998 is bad
block 1083 is bad
block 1459 is bad
block 1460 is bad
Partially written block 21 detected
Partially written block 21 detected
Partially written block 21 detected
Partially written block 21 detected
Partially written block 21 detected
Partially written block 21 detected
Partially written block 21 detected
Partially written block 21 detected
Partially written block 21 detected
So far everything works but i'm a little bit concerned.
EDIT:
The Partially written blocks reappear after restart, however i managed to get rid of them by making a sdcard-filesystemcheck via gparted using a notebook (although there weren't any errors) ! Strange, I thought my phone is broken...
Hi. i have problem with my s3 i want to try to repair nand file sys. is ther any solution?
It seems if you have damaged Blocks in NAND, its harder to play with full flash... full erase...
I have 1 in my S8500...
You know the address first, if you play with erase or full flashes in JTAG...
BUT if you ever seen Blue Screen on your handset. If Debug Level was Mid or High.
Then handset report damaged blocks...
I'll search some Pics... for better understanding.
I have no idea, how many damaged blocks are "normal"...
Best Regards
Edit 1.
Message looks like this on handset, if Blue Screen appears... scroll to page...
Then you can read:
Code:
Bad Block information:
nNumBMP : 0
nAge : 0
Run Time Bad Block Occured :
Init BMPs = 1, Current BMPs = 0
This is taken from my S8530... this is alive and seems no damaged Blocks...
On my S8500 I can remember nNumBMP : 1
With RIFF Box (JTAG) you see for instance address...
http://forum.gsmhosting.com/vbb/f634/solved-s8500-error-pls-help-1089879/
My Block is damaged at 0x07100000
Edit 2.
size of 1 Block is 256 KB (Length 0x40000)
http://forum.xda-developers.com/showpost.php?p=13935305&postcount=23
So 256 KB is loosing/missing/unusable/unrestoreable
I'll check what 0x0710 0000 could contain...
Code:
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = [B][COLOR="Red"]7[/COLOR][/B], Current BMPs =
0
Uuupsi, one of my "new" damaged test Wave 2 devices has 7 damaged Block from 512 MB OneNAND...
7 x 256 KB = 1792 KB
Nearly 2 MB seems damaged...
Device not long enough tested...
Will check again my other devices...
Best Regards
My JTAG S8500 shows me today this:
Code:
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = [COLOR="Red"]4[/COLOR], Current BMPs =
0
Maybe not OneNAND but maybe moviNAND ?
Will check later again...
Best Regards
Now I am 95,7 % sure, this means 512 MB OneNAND.
Code:
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = [B]2[/B], Current BMPs =
0
My S8530 shows me 2 damaged Blocks with RIFF JTAG, if I erase NAND...
My S8500 shows me 1 Block, if I play with RIFF and 1 Block, via Bluescreen:
Code:
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = [B]1[/B], Current BMPs =
0
My prior post with 4... seems during my tests... this was temporary.
I have tested something stupid...
Hmmm. I have 3 devices used with RIFF JTAG...
First S8500 with broken Display
Second S8500 without visible damages... and without damaged blocks.
Third S8530 with broken Display + 50 % unusable Touchscreen + many visible scratches...
Strange, both devices with broken Display have damaged Blocks...
Maybe hard landings can damage OneNAND also...
Best Regards
Bad block management (BBM) is a critical component of NAND flash drivers to improve the reliability and endurance of the flash. NAND is shipped from the factory with “mostly good” cells, meaning there are some cells that are non-functional even when the flash is new. Blocks can also go bad over time, causing loss of data stored in the flash memory or even a bricked device. To prevent flash memory corruption, the Datalight line of FlashFX products employs patented bad block management technology to map bad sectors and avoid storing data in those areas. Using Datalight FlashFX flash memory drivers makes bad block management worry-free, making NAND flash reliable and reducing warranty returns.
Click to expand...
Click to collapse
http://www.datalight.com/solutions/technologies/bad-block-management
Interesting, found it here:
http://forum.xda-developers.com/showpost.php?p=33359041&postcount=6
Also interesting...
eMMC seems also moviNAND...
Best Regards
So my 2013 Nexus 7 usually runs smoothly and stable for long times, but in every few weeks there comes a short period of time when it becomes crazy-unstable, i get random not-waking (sleep of death) and random shutting down problems. After a while (when just putting it to idle for like an hour or so) it gets back to normal and continues to operate normally.
I got several last_kmsgs and posted it to google products forum: here
I thought it's some driver error hoping a fix would come but I just installed today's KRT16S from factory image and experienced the same problem today, 2 times in a row.
What's interesting is that in pretty much each last_kmsgs there's a kernel error pointing to mmcblk0p30.
Some parts of the last errors from a bugreport:
[ 688.135009] end_request: I/O error, dev mmcblk0, sector 4718592
[ 688.135406] Buffer I/O error on device mmcblk0p30, logical block 0
[ 688.135620] lost page write due to I/O error on mmcblk0p30
[ 688.136108] Kernel panic - not syncing: EXT4-fs panic from previous error
And from another:
[ 20.124267] end_request: I/O error, dev mmcblk0, sector 4729088
[ 20.124359] Buffer I/O error on device mmcblk0p30, logical block 1312
[ 20.124450] lost page write due to I/O error on mmcblk0p30
[ 20.124542] JBD2: Error -5 detected when updating journal superblock for mmcblk0p30-8.
[ 20.124694] Kernel panic - not syncing: EXT4-fs (device mmcblk0p30): panic forced after error
I think it's probably a hardware error, and I should RMA it, but since it's an occasionally problem it's really hard to reproduce it would be good if at least I could tell what hardware it this pointing to. Based on it's name is it safe to assume that it's a part of the mmc (16 gb internal storage)?
Any help appreciated.
Well, did some digging around and based on symbolic links on /dev/block/platform/msm_sdcc.1/by-name it looks like mmcblk0p30 is pointing to userdata.
That's definitely on the internal sdcard (emmc), right?
I did several factory image restores which is supposed to rewrite userdata partition right? So that it's still causing errors it indicates it is a hardware issue right? Or is there something else I could try?
Any help appreciated.
Have you eventually sorted this out?
scorpeeon said:
Well, did some digging around and based on symbolic links on /dev/block/platform/msm_sdcc.1/by-name it looks like mmcblk0p30 is pointing to userdata.
That's definitely on the internal sdcard (emmc), right?
I did several factory image restores which is supposed to rewrite userdata partition right? So that it's still causing errors it indicates it is a hardware issue right? Or is there something else I could try?
Any help appreciated.
Click to expand...
Click to collapse