i have been experiencing too much instability with nearly all the roms i flash even though i do exactly as the instructions say in each and every rom ... i searched about everything talking about instability ... Task 29 flash maglrd flash cwm with the sizes said in the rom's thread but always getting instability in the rom even though most of people reporting that the rom is stable and working great .... i thought it might be bad blocks and searched for how to check for bad blocks but couldn't find easy way to find out if i got bad blocks or not .... i did try several ways of checking but not getting the same results the thread is talking about .... so can someone plz help me find out whats wrong with my phone??!!
i know that there is too many threads talking about bad blocks and so on and i did nearly read all of them but still cant find a solution
Search for the" definitive mtty thread", there you will find out how to find out if you have bad blocks.
Haven't got link because I am not near my PC.
Edit: you might try and increase the system partition by 5 or 10mb when installing any ROM to compensate for bad blocks (if that is the problem).
Sent from my NexusHD2 using xda premium
well i read all mtty posts he is talking about clean up and so on but none of the commands in his post talking about check for bad blocks .... thanx for help anyways ... i'll give mtty method but is there any method or could give me a report of total internal memory used not used bad blocks system and so on.... as the scan disc in computers do when u scan ur hdd
Once you have mtty set up, the command is - info 8
This will tell you whether there are bad blocks or not!
Edit: This is what mine shows,
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
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 15 (0xF) 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 1680 (0x690) is reversed block
BLOCK 1681 (0x691) is reversed block
BLOCK 1979 (0x7BB) is reversed block
Partition[0], type=0x23, start=0x2, total=0xBE
Partition[1], type=0x0, start=0x0, total=0x0
Partition[2], type=0x0, start=0x0, total=0x0
Partition[3], type=0x0, start=0x0, total=0x0
CE Total Length(with sector info) = 0x60600
CE CheckSum Length(without sector info) = 0x60000
Fortunately I have the Hynix chipset which according to my research is less prone to bad blocks than the Samsung chipset. To check which one you have go into bootloader and on the first line HX-BC is Hynix and SS-BC is the Samsung chipset.
Sent from my NexusHD2 using xda premium
results i dont understand
hey how ru? ... thanx for help well ... i did all what was said in mtty thread and i got these results
i tried task 8 i got my phone restarted then task 28 then task 29 and thats the results i got
Cmd>task 28
Format start
Fill RSVD information for block 497 to 530
Storage start sector=0x0, total sector=0x0
Storage start block=33, total block=0
Bypass ExtROM Block (160+10)
Total Bad Block in CE: 0
Erase physical block from 532 to 344
ExtROM: Erase physical block from 3910 to 4080
si backup: Erase physical block from 4080 to 4096
Format end
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=3566
erase_page - error bad status: 0xB791E960
ERASE block 1726 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1911 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1913 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3338 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
it said total bad block is zero in task 28 why did it say erase block fail in task 29?!
and if its really clean without any bad blocks .... why am i always getting instability with all the roms im trying to flash even though i do exactly as the instructions say
Did you try "Info 8"?
Put the results up here
Sent from my NexusHD2 using xda premium
yep it restarted my phone ... didnt give me any results just restarted the phone ...
Not "task 8", "info 8" !!
Also the fact that task 29 fails is not a good omen!
Sent from my NexusHD2 using xda premium
Actually if you read the mtty thread you'll see that you should expect some errors during task29.ifyou get different errors than the ones mentioned in that thread, then there's a problem.
Also, when you talk about the process (task29,magldr,blahblah) at no point did you mention cleaning up the sd card,, there are things on both the fat32 and the ext that can potentially cause problems If left over from previous roms.
Also also,, sim cards can cause instability across allroms. Got another one to test with for a few hours?
wiammaren said:
i'll give mtty method but is there any method or could give me a report of total internal memory used not used bad blocks system and soon
{
"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"
}
Click to expand...
Click to collapse
Open a terminal emulator and type: df and hit return.
This will give you a list of each partition size and used space.
you can use native sd!
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
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 15 (0xF) 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 972 (0x3CC) is reversed block
BLOCK 973 (0x3CD) is reversed block
BLOCK 974 (0x3CE) is reversed block
BLOCK 975 (0x3CF) is reversed block
BLOCK 976 (0x3D0) is reversed block
BLOCK 977 (0x3D1) is reversed block
BLOCK 978 (0x3D2) is reversed block
BLOCK 979 (0x3D3) is reversed block
BLOCK 980 (0x3D4) is reversed block
BLOCK 1726 (0x6BE) is bad block
BLOCK 1911 (0x777) is bad block
BLOCK 1913 (0x779) is bad block
Partition[0], type=0x23, start=0x2, total=0xFE
Partition[1], type=0x0, start=0x0, total=0x0
Partition[2], type=0x0, start=0x0, total=0x0
Partition[3], type=0x0, start=0x0, total=0x0
CE Total Length(with sector info) = 0x80800
CE CheckSum Length(without sector info) = 0x80000
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=3566
erase_page - error bad status: 0xB791E960
ERASE block 1726 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1911 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1913 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3338 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>task 28
Format start
Fill RSVD information for block 497 to 530
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
this is all the info im getting ... info 8 , task 29 task 28
samsamuel said:
Actually if you read the mtty thread you'll see that you should expect some errors during task29.ifyou get different errors than the ones mentioned in that thread, then there's a problem.
Also, when you talk about the process (task29,magldr,blahblah) at no point did you mention cleaning up the sd card,, there are things on both the fat32 and the ext that can potentially cause problems If left over from previous roms.
Also also,, sim cards can cause instability across allroms. Got another one to test with for a few hours?
Click to expand...
Click to collapse
before each flash i format my sd card and repartition it
Related
Hi to all
I have this problem:
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
Block 0x3A8(936) is BAD block !!!
Block 0x3A9(937) is BAD block !!!
Block 0x3AA(938) is BAD block !!!
Block 0x3FB(1019) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x19D00
Partition[3], type=0x4, start=0x1CD00, total=0x1DB00
CE Total Length(with sector info) = 0x3A86800
CE CheckSum Length(without sector info) = 0x39A0000
Click to expand...
Click to collapse
I have read in the forum that for resolve problem i must do a erase comand.
In the wiki i have found:
erase
Usage:
erase [StartAddr [Len]]
Erase the content of flash ROM.
StartAddr : Start address of ROM(default(hex)=a0040000).
Len : How many bytes will be erased(default(hex)=40000).It should either return "T " for succes, or "F " for failure (encapsulated in the HTCS-HTCE block).
Click to expand...
Click to collapse
So what comand i have to give?
is right this one?
erase 0x0 0x1
thx
How to erase bad block
I have the same problem and due to this problem the extROM won't installed automatically
Anybody have any idea????
in my days with the BlueAngel, mamaich and some other guys created a partition formatting tool. This might be the answer to our dead and unwilling tytn units.
I imagine once you have formatted the partitions, everything would be erased and it would be a fresh unit.
Exactly same problem here, same sectors... Extended ROM?!? But my phone works fine, and extended ROM works fine. Anyway, bad sectors make me worried a bit.
Where is this formating tool you mention? Hermes also has task 28 command which formats something (storage).
These 3 seem to be factory marked bad blocks in NAND, a lot of hermes devices have them. Nothing to worry about.
Block 0x3A8(936) is BAD block !!!
Block 0x3A9(937) is BAD block !!!
Block 0x3AA(938) is BAD block !!!
Click to expand...
Click to collapse
pof said:
These 3 seem to be factory marked bad blocks in NAND, a lot of hermes devices have them. Nothing to worry about.
Click to expand...
Click to collapse
Hi Pof and for the Reversed block ???
pof said:
These 3 seem to be factory marked bad blocks in NAND, a lot of hermes devices have them. Nothing to worry about.
Click to expand...
Click to collapse
So, how come I couldn't install the extended rom?
POF,
I downgraded my unit to spl 1.01 and the first time I wrote command..USB> lnbs SPL-1.01.nbs 500020000 instead of USB> lnbs SPL-1.01.nbs 50020000. I caught this and unplugged my device and reset all appeared great then in 24 hours my device locked up tried to reset upon boot in to wm5 it would give me an error for windows voice command, and lock up m yphoned in 5 seconds. so I reflashed my rom and all appears OK, loaded all my programs, but not VC never reads my appointments or emails like it used to, and yes I have checked the settings so i think i must given my phone some bad sectors. what you think
Hi All
Today I checked my Cruise with mtty info and the result was this:
nfo 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 (0xKirály is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 1023 (0x3FF) is bad block
Partition[0], type=0x20, start=0x2, total=0x3E
Partition[1], type=0x23, start=0x40, total=0x780
Partition[2], type=0x25, start=0x7C0, total=0x8680
Partition[3], type=0x4, start=0x8E40, total=0x12480
CE Total Length(with sector info) = 0x4767200
CE CheckSum Length(without sector info) = 0x4720000
I use Beps 0.54. all flash was perfect. I didin't have any error.
I worry about a little bit.
1, What does it mean this bad block exactly?
2, Should I afraid about this?
3, How can I repair this?
I got other result from "fktsndr":
--- 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 (0xKirály is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x780
Partition[2], type=0x25, start=0xDC0, total=0x7580
Partition[3], type=0x4, start=0x8340, total=0x12F80
CE Total Length(with sector info) = 0x41E1A00
CE CheckSum Length(without sector info) = 0x41A0000
It looks better than my Cruise. He use Bepe 0.53.
Any idea?
Ignor this!
Is normal!
NetrunnerAT said:
Ignor this!
Is normal!
Click to expand...
Click to collapse
Pfhuuuuu ...... Ok. What is this difference between two Cruise?
One with bad block and the other without.
Here is my HTC Nike
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 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) 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 817 (0x331) is bad block
BLOCK 1325 (0x52D) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x700
Partition[2], type=0x25, start=0xD40, total=0x8EC0
Partition[3], type=0x4, start=0x9C00, total=0x116C0
CE Total Length(with sector info) = 0x4E4E000
CE CheckSum Length(without sector info) = 0x4E00000
I have in my Work three other Nike with same error! All work without any problems.
DANGER!
Guys, DO NOT use "task 2a" command in MTTY with Polaris device!
Your device will be a brick.
fktsndr said:
Guys, DO NOT use "task 2a" command in MTTY with Polaris device!
Your device will be a brick.
Click to expand...
Click to collapse
Type(hex) 2A: Check NAND flash and mark bad blocks. (Requires Level!=0xFF)
Can you explane why? I think i know what you mean ^_^
[edit] i have found the Kaiser Thread ...
NetrunnerAT said:
Type(hex) 2A: Check NAND flash and mark bad blocks. (Requires Level!=0xFF)
Can you explane why? I think i know what you mean ^_^
[edit] i have found the Kaiser Thread ...
Click to expand...
Click to collapse
because in the new EVT series, the SPLs are properly written with full ECC checking, task 2a just formats the NAND entirely
Olipro said:
because in the new EVT series, the SPLs are properly written with full ECC checking, task 2a just formats the NAND entirely
Click to expand...
Click to collapse
It's clear but what do you think about the bad block in the firs post? It's normal or not?
thebiker said:
It's clear but what do you think about the bad block in the firs post? It's normal or not?
Click to expand...
Click to collapse
yes, it is normal... its a NAND device. Forget about it and be happy.
About NAND devices
http://en.wikipedia.org/wiki/Flash_memory
About bad blocks of NAND devices:
Most NAND devices are shipped from the factory with some bad blocks which are typically identified and marked according to a specified bad block marking strategy. By allowing some bad blocks, the manufacturers achieve far higher yields than would be possible if all blocks were tested good. This significantly reduces NAND flash costs and only slightly decreases the storage capacity of the parts.
Thax for all answer!!!
my polaris is bricked.
i can enter tricolor screen , but nothing after that.
tried many tricks but still no solution.
1. pressing reset, screen is totally black
2. i can enter normally into tricolor screen
3. i can flash any rom i like , but everytime black screen after reset.
4. hard reset is working fine.
5. hard spl is installed
6. mtty output :
a.
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 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) 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 604 (0x25C) is bad block
BLOCK 1150 (0x47E) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x780
Partition[2], type=0x25, start=0xDC0, total=0xC440
Partition[3], type=0x4, start=0xD200, total=0xE0C0
CE Total Length(with sector info) = 0x6969000
CE CheckSum Length(without sector info) = 0x6900000
b. Cmd>info 9
Storage Start Addr=0x56BA0000, length:0x7090200
c. Cmd>info 0
Platform Model IDOLA10000
Platform HW Board ID:31, PVT1
d. Cmd>info 2
HTCS00000000jR*¥HTCE
e. Cmd>info 3
HTCS;²»ÀA§v³ñ‹+¬úÐx´Wš¿
f. Cmd>boot
InitDisplay: Display_Chip=1
CpldSetSystemLED2 [1],gdwLED2Status=0.
No this System Led2 Behavior [1] polaris locks...
Is there a solution or it's time for Diamond ?
i dont know if he can help you, but hit jockyw a pm
have you tried to revert back to original SPL and ROM?
(i know you are great rom cooker, but just in case you forgot something)
Did you try these?
http://forum.xda-developers.com/showpost.php?p=2003948&postcount=2
http://forum.xda-developers.com/showpost.php?p=2350974&postcount=4
I've tried any possible mtty command ...
finally i think that there is a bad block problem (many bad blocks) ....
p.s. A friend gave me a new polaris, so cooking continues ....
sorry about your loss
any advices on what not to do ?
in order not to get in the same situation.
don't let your children play with those problematic & expensive htc pdas ...
swtos said:
I've tried any possible mtty command ...
finally i think that there is a bad block problem (many bad blocks) ....
Click to expand...
Click to collapse
it could be possible to change the ROM memory?
I recently came across this while looking at solutions to fix bad blocks on my device.. Task29 does not fix bad blocks, and no matter what I try, I get bad block errors (although my device is not completely dead yet, it has begun to worry me)
http://forum.xda-developers.com/showthread.php?t=377389 (read the first part)
Also read this: http://forum.xda-developers.com/showthread.php?t=623356
Could this be a safe or possible solution for fixing bad blocks?
Found out the method was obsolete.. did not fix bad blocks at all..
all I got was a bunch of errors:
(at first running info 8)
(and last run task 2a)
Code:
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_KBY00U00VM
DEVICE ID=0xB3
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x2000
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 57 (0x39) is bad block
BLOCK 413 (0x19D) is bad block
BLOCK 1388 (0x56C) is bad block
BLOCK 2321 (0x911) is bad block
BLOCK 2534 (0x9E6) is bad block
BLOCK 3482 (0xD9A) is bad block
BLOCK 3513 (0xDB9) is bad block
BLOCK 6495 (0x195F) is bad block
OS NOT FOUND !!!
Cmd>task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=497, total block of CE=7695
erase_page - error bad status: 0xB791E960
ERASE block 57 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 413 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1388 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 2321 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 2534 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3482 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3513 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 6495 FAIL !!!
Write 0xFF start page=0x7C40, total page=0x783C0
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
EDIT: I went through the ENTIRE guide, and got everything set up, but even when I run "task 2a", it does not fix the bad blocks..
I'll help you bump this, cause I just ran exactly into the same problem. I have two HD2's, One has a bad screen and using mtty I check it and it was clean no bad blocks, the one thats been working all this time with no issues, not has about 5-7 bad blocks. Using android, it prevently USB syncing to work, and if I download something from market, it reboots the phone, which I know its cause of these bad blocks locations.
I tried mtty and task29, neither has removed the bad blocks or fixed them, and have found nothing else in a whole days search on how to correct them.
I would love some help on this too!
i have a similar problem i have bad blocks in htc tilt 2 but when i put task a2 dont executing nothing.
elojo_8 said:
i have a similar problem i have bad blocks in htc tilt 2 but when i put task a2 dont executing nothing.
Click to expand...
Click to collapse
That was the reason why I am now using SD Android instead of Nandroid. I suspect the Nandroid flashing that has caused bad blocks on my HD2
Nothing you can do
Some says that if your bad blocks are below 10 and can run OS, that is fine and considered normal.
I just hope that there is a tool that can move the badblocks into a location in the NAND cluster such that will not fail any flash attempt.
Cheers
lock my "info 8" report with mtty i have the Sleep of death problem
in the lastest lines see this
i have another tilt 2 and it have a bad block but not says nothing about of partitions
BLOCK 1228 (0x4CC) is bad block
BLOCK 3202 (0xC82) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x980
Partition[2], type=0x25, start=0xFC0, total=0x1A880
Partition[3], type=0x4, start=0x1B840, total=0x1F780
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_kby00n00hm
DEVICE ID=0xBC
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
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 4 (0x4) is reversed block
BLOCK 5 (0x5) is reversed block
BLOCK 7 (0x7) is reversed block
BLOCK 9 (0x9) 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 15 (0xF) 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 20 (0x14) is reversed block
BLOCK 21 (0x15) is reversed block
BLOCK 22 (0x16) is reversed block
BLOCK 23 (0x17) is reversed block
BLOCK 24 (0x18) is reversed block
BLOCK 26 (0x1A) is reversed block
BLOCK 27 (0x1B) is reversed block
BLOCK 32 (0x20) is reversed block
BLOCK 1228 (0x4CC) is bad block
BLOCK 3202 (0xC82) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x980
Partition[2], type=0x25, start=0xFC0, total=0x1A880
Partition[3], type=0x4, start=0x1B840, total=0x1F780
CE Total Length(with sector info) = 0xDCFC200
CE CheckSum Length(without sector info) = 0xDC20000
Cmd>
i
Like AngelDeath, I also have problems with restarts when trying to install apps from market (or also via titanium). These problems happen with all NANDroid builds (Froyo and Gingerbread), and persist despite task 29, task 2a, and after restoring stock WM from SD card. Using MTTY shows a few bad blocks, but not sure if they are related to this problem. Anybody with clues as to what's going on or how to fix? I'm not sure if I'm still under warranty, but regardless I'm not sure if I can duplicate the problems in WM to get the device replaced.
Lukedunk,
Just an update, I just reverted to the EU version of my 1.5 Android rom which uses sd-ext and app2sd (was using Tmous version) and I no longer have the problems, but if I go back to Tmous version they re-surface again, so I do believe the bad block and their location does matter.
My bad blocks are in the data portion which I always use a 445cwr partition. I can almost bet if you go to a eu version which uses a sd-ext, I would almost bet your problem will go away.
This thread might be of some use: http://forum.xda-developers.com/showthread.php?t=405740
Hello, i do not know how to check bad blocks but i am facing serious problem!
I am running NDT MIUI clk.(it works fine)
Also i am unsuccessful booting every other latest MIUI(bootloops).
Although i am successful booting latest NDT booting from clk, but when i try the same version from mag, it bootloops! I always flash ROMs so i know that i am using correct partition layouts & i do clean install. WP7 & WIN mo works fine! Some android ROMs which require ext also works fine!
Firstly i thought may be sd card is the problem but i formatted it and i am sure its fine!
Im worried that i will break my lovely HD2. I think all this is related to the bad blocks.
Please Help!
(I have EU HD2)
sagarjawaress said:
Hello, i do not know how to check bad blocks but i am facing serious problem!
I am running NDT MIUI clk.(it works fine)
Also i am unsuccessful booting every other latest MIUI(bootloops).
Although i am successful booting latest NDT booting from clk, but when i try the same version from mag, it bootloops! I always flash ROMs so i know that i am using correct partition layouts & i do clean install. WP7 & WIN mo works fine! Some android ROMs which require ext also works fine!
Firstly i thought may be sd card is the problem but i formatted it and i am sure its fine!
Im worried that i will break my lovely HD2. I think all this is related to the bad blocks.
Please Help!
(I have EU HD2)
Click to expand...
Click to collapse
Please do not cross post.
http://forum.xda-developers.com/showthread.php?t=1189544&page=18
hi friends
here is my info 8 log and it seems i have 5 BAD Block unfortunately.
when i install some of WP7 roms like xbmod after restart my touch screen stuck and the phone reboots by itself and this loop will go on...
in some android built after installation when its going to boot it reboots 3-4 times as well.
now i know the reason why
really isnt any way to correct them?
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
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 15 (0xF) 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 702 (0x2BE) is bad block
BLOCK 704 (0x2C0) is bad block
BLOCK 1121 (0x461) is bad block
BLOCK 1916 (0x77C) is bad block
BLOCK 3384 (0xD38) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0xA00
Partition[2], type=0x25, start=0x1040, total=0x1DCC0
Partition[3], type=0x4, start=0x1ED00, total=0x18E80
CE Total Length(with sector info) = 0xF776800
CE CheckSum Length(without sector info) = 0xF680000
Cmd>
Bad blocks are unfortunatly not fixable 95% of the time. You can mark them as bad on a HDD so they dont interfere but on your phone I have no idea if you can :-( Only permanent solution is new mainboard with new NAND...
/Anders
Anden1986 said:
Bad blocks are unfortunatly not fixable 95% of the time. You can mark them as bad on a HDD so they dont interfere but on your phone I have no idea if you can :-( Only permanent solution is new mainboard with new NAND...
/Anders
Click to expand...
Click to collapse
thanks for your answer but i know there is a solution by using JTAG boxes like OTR-Riff
but it is expensive and one like me cant do it by itself and it needs some hardwares
i'm just looking for a software based solution which i can do it my self using my usb cable and my pc
That is also correct But as you said yourself it isn't easy... As far as I have found out there is no solution og work-around based on software only I have had problems with reboots myself but solved the problem by filling up the memory with songs, videos and what not... Not pretty but it works for me Only alternative is a SD based Android build.
/Anders
Anden1986 said:
That is also correct But as you said yourself it isn't easy... As far as I have found out there is no solution og work-around based on software only I have had problems with reboots myself but solved the problem by filling up the memory with songs, videos and what not... Not pretty but it works for me Only alternative is a SD based Android build.
/Anders
Click to expand...
Click to collapse
yes, i'm using winmo3.14 (i hate it ) and an ICS and a Froyo and at-last an Ubuntu on SD
afterall thats the good point of it :d u can have multiple builds plus most stable and bugless rom (default winmo)
( i'm kidding for sure , winmo 3.14 is most bugfull rom ever exists)
How to check location of bad block?
Hi,
When I ran info 8 I got following bad blocks. How do I check if it is still have chance to install any ram.
I tried to install stock ram but got stuck at 8%.
Can someone to me how to partition nand and install EU version?
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_KBY00U00VM
DEVICE ID=0xB3
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x2000
BLOCK PAGE=0x40
Checking block information
BLOCK 132 (0x84) is bad block
BLOCK 304 (0x130) is bad block
BLOCK 2483 (0x9B3) is bad block
BLOCK 2541 (0x9ED) is bad block
BLOCK 2636 (0xA4C) is bad block
BLOCK 2689 (0xA81) is bad block
BLOCK 3488 (0xDA0) is bad block
BLOCK 4406 (0x1136) is bad block
BLOCK 4910 (0x132E) is bad block
BLOCK 5822 (0x16BE) is bad block
BLOCK 6268 (0x187C) is bad block
BLOCK 6903 (0x1AF7) is bad block
BLOCK 7366 (0x1CC6) is bad block
OS NOT FOUND !!!
NAND is relatively cheap because it contains bad blocks, there's not much you can do about that, as long as its flagged as bad which it will be before its sold then it wont use it. The problem is blocks that become bad afterwards. But don't try and fix labelled bad blocks, whilst it might work, it may also give you unexpected errors
People have said that Samsung nand chips (tmous) tends to have more bad blocks then hynix (EU) dunno if that's just because of the storage size.
Sent from my HD2 using xda vip edition
thankyou
thankyou for this information
after used my HD2 (EU ver.) with winmo6.5 for 2 years
just decided to flash into nand android
i've try many roms and flash and flash it from saturday till now
this is my info8
--- 2K bytes sector version ---
DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
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 2372 (0x944) is bad block
BLOCK 2707 (0xA93) is bad block
Partition[0], type=0x23, start=0x2, total=0xFE
Partition[1], type=0x0, start=0x0, total=0x0
Partition[2], type=0x0, start=0x0, total=0x0
Partition[3], type=0x0, start=0x0, total=0x0
CE Total Length(with sector info) = 0x80800
CE CheckSum Length(without sector info) = 0x80000
should worried with this 2 bad blocks or not ?
but in 24 hr. mine HD2 still work ok with Dorimanx-ROM-HIGH-END 3.1.9
How to fix this?
<5>[ 2.437072] Creating 6 MTD partitions on "msm_nand":
<5>[ 2.437103] 0x000004320000-0x000004420000 : "misc"
<5>[ 2.438720] 0x000004420000-0x000004860000 : "recovery"
<4>[ 2.442138] ###BAD BLOCK 571 04760000###
<5>[ 2.443481] 0x000004860000-0x000004d60000 : "boot"
<5>[ 2.449005] 0x000004d60000-0x000010160000 : "system"
<4>[ 2.453277] ###BAD BLOCK 652 05180000###
<4>[ 2.453948] ###BAD BLOCK 657 05220000###
<4>[ 2.471923] ###BAD BLOCK 801 06420000###
<4>[ 2.486511] ###BAD BLOCK 918 072C0000###
<4>[ 2.506347] ###BAD BLOCK 1077 086A0000###
<4>[ 2.520080] ###BAD BLOCK 1187 09460000###
<4>[ 2.559967] ###BAD BLOCK 1507 0BC60000###
<4>[ 2.564849] ###BAD BLOCK 1546 0C140000###
<4>[ 2.567138] ###BAD BLOCK 1564 0C380000###
<4>[ 2.576019] ###BAD BLOCK 1635 0CC60000###
<4>[ 2.590820] ###BAD BLOCK 1753 0DB20000###
<4>[ 2.616363] ###BAD BLOCK 1957 0F4A0000###
<4>[ 2.625000] ###BAD BLOCK 2026 0FD40000###
<4>[ 2.628631] ###BAD BLOCK 2055 100E0000###
<5>[ 2.629516] 0x000010160000-0x000010360000 : "cache"
<5>[ 2.632049] 0x000010360000-0x00001e800000 : "userdata"
<4>[ 2.640106] ###BAD BLOCK 2138 10B40000###
<4>[ 2.653442] ###BAD BLOCK 2245 118A0000###
<4>[ 2.672943] ###BAD BLOCK 2401 12C20000###
<4>[ 2.673217] ###BAD BLOCK 2403 12C60000###
<4>[ 2.673767] ###BAD BLOCK 2407 12CE0000###
<4>[ 2.700317] ###BAD BLOCK 2620 14780000###
<4>[ 2.712066] ###BAD BLOCK 2714 15340000###
<4>[ 2.716064] ###BAD BLOCK 2746 15740000###
<4>[ 2.745147] ###BAD BLOCK 2979 17460000###
<4>[ 2.766235] ###BAD BLOCK 3148 18980000###
<4>[ 2.779846] ###BAD BLOCK 3257 19720000###
<4>[ 2.780120] ###BAD BLOCK 3259 19760000###
<4>[ 2.837493] ###BAD BLOCK 3719 1D0E0000###
<4>[ 2.851959] ###BAD BLOCK 3835 1DF60000###
<6>[ 2.861083] PPP generic driver version 2.4.2
<6>[ 2.861328] PPP Deflate Compression module registered
<6>[ 2.861358] PPP BSD Compression module registered
<6>[ 2.862243] PPP MPPE Compression module registered
<6>[ 2.862274] NET: Registered protocol family 24
<6>[ 2.862365] PPPoL2TP kernel driver, V1.0
<6>[ 2.862365] SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
Hello everyone! My hd2 is dead... sigh
i read after threads but nothing worked for now...
- WWE HD2 no brand (bought 2 years ago on eXpansys)
- HSPL2 - HSPL 2.08 (Hard SPL)
- Radio Radio 2_15_50_14 + Leo +2.15.50.14
- 113 magldr
- CWM 5.0.2.6
- XB CM7 MUST SEE. 19
- Sandisk Micro SD 32GB class divided into 2: FAT32 (32K allocation units), 1 GB EXT4, 512 swap the statute did with gparted.
Given that i use my hd2 in a very intensive way with lots of open applications at the same time
(IM +, Meridian for music, oruxmap to follow bike route, facebook, friendcaster pro
camera to take pictures while riding my a bike), so I might have not noticed certain delays
and freeze of the phone, as it has only about half a gb of ram.
When it crashed only IM+, facebook and sygic were running. I was setting a destination on
Sygic when my phone freezed and I had to do a battery pull.
When I restarted, after loading maglder phone got stuck again displaying error:
1Efatal HIT1
This thing had already a couple of times before and after some "recovery AD reset" from magldr,
without using the PC the phone started to work again.
After that I started using CLK 1.4.0.1 and I had a problem of degradation in the rom with the dayly use and
stability problems of data connection, which partially i solved doing a recovery or cwm or flashin the various same rom over.
Although at times it crashed always started it's self without to have fatal errors but losing all programs
in the rom as if it had been just flashed. So i did restorewith CWM to conitnue to use my phone as nothing happened.
Tired of having connection problems a few days ago, I came back to use MAGLDR and 1Efatal HIT1
returned.
To solve it I did : wipe (task29), flashed stock from microsd, all operations that didn't give me errors but the phone is still briked.
Flashing rom to microsd on various stocks gave my only white screen with HTC logo or boot loop.
I can remove or replace HSPL (also version 4), i can install magldr, or clk (sometimes with errors after rebooting ) but can not reach CWM anymore.
It is as if after magldr or clk the phone "fails to write in nand" but it said that he performed the operation successfully.
Last step I tried to do was boot android from microsd with magldr using the right rom obviously. I tryed too different roms and varioud microsd
but i got this error too:
Android LOAD at 11800000
from MicroSD
Load zImage
K: / android / zImage
Load inird.gz
I: / Android / INIRD.GZ
[K] 11808000:2 AE840 12200000:1 B1DFE
Load done!
1EFATAL HIT 1
I don't know what to do. My warranty has expired a 1 month and 8 days ago ... any suggestions?
did you manage to fix this? I have the same problem.
Sounds like you may possibly have bad blocks. I don't know much about this topic though. Their is a thread somewhere around here in Q&A or NAND development, it's called "bad blocks" I think munjeni wrote it.
Maybe that will help some.
1 other idea in case you do have bad blocks is to try clk 1.5 ( I have a guide written in my signature) and change your recovery size to a larger partition.
I tried your method but I have the same issues installing recovery is that when it says restart after installing recovery it doesn't actually restart. In magldr I would get the fatalhit error after and CLK 1.4 I get "cmdline: no_console_suspend=1 wire.search_count=5 clk1.4.0.1"
is there any way to save it?
checking for bad blacks bought back the following, To note I had performed task2a by accident first and then reflashed the 1.66 t-mobile uk winmo software (what came on it) and then performed info 8.
--- 2K bytes sector version ---
DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
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 15 (0xF) 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=0x23, start=0x2, total=0xFE
Partition[1], type=0x0, start=0x0, total=0x0
Partition[2], type=0x0, start=0x0, total=0x0
Partition[3], type=0x0, start=0x0, total=0x0
CE Total Length(with sector info) = 0x80800
CE CheckSum Length(without sector info) = 0x80000
and then I performed task 2a
task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=497, total block of CE=3599
Write 0xFF start page=0x7C40, total page=0x383C0
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
what do reversed blocks mean ?
jabran200 said:
checking for bad blacks bought back the following, To note I had performed task2a by accident first and then reflashed the 1.66 t-mobile uk winmo software (what came on it) and then performed info 8.
--- 2K bytes sector version ---
DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
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 15 (0xF) 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=0x23, start=0x2, total=0xFE
Partition[1], type=0x0, start=0x0, total=0x0
Partition[2], type=0x0, start=0x0, total=0x0
Partition[3], type=0x0, start=0x0, total=0x0
CE Total Length(with sector info) = 0x80800
CE CheckSum Length(without sector info) = 0x80000
and then I performed task 2a
task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=497, total block of CE=3599
Write 0xFF start page=0x7C40, total page=0x383C0
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
what do reversed blocks mean ?
Click to expand...
Click to collapse
You have no bad blocks, that's great.
To the people that does, run a dmesg, find the location of the bad block and increase the partition of the bad blocks.
for example, my partition table is:
Misc 25
System 160
so then why does it not load windows mobile? I do task 2a, and load 1.66 windows from the sd card straight after but I am stuck on the start screen with the circle and loading recovery ends up with fatal hit.