What are bad blocks and how to clear them??
Sent from my HTC HD2 using xda premium
Bad blocks usually refers to very small parts of your internal storage that are broken and can't retain data properly anymore. You can't fix them and can only let the system store the data somewhere else by reflashing.
hengsheng120 said:
Bad blocks usually refers to very small parts of your internal storage that are broken and can't retain data properly anymore. You can't fix them and can only let the system store the data somewhere else by reflashing.
Click to expand...
Click to collapse
How do we know about a bad block??
Sent from my HTC HD2 using xda premium
Here is an (almost) complete reference for bad blocks :
http://forum.xda-developers.com/showthread.php?t=1189544
Anurag pandey said:
How do we know about a bad block??
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
Well, if you don't specifically check for bad blocks with tools, you won't know that you have them until you flash a rom. One of the symptoms of having a lot of bad blocks is that many fully working roms don't work (doesn't boot, or lots of errors) on first try, despite following instructions exactly.
The only practical solution is to flash roms a few times to see if the problem is because you did something wrong, or the rom really doesn't work.
Sent from my HTC HD2 using XDA
Anurag pandey said:
How do we know about a bad block??
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
^What he said, and sometimes the ROM simply won't boot on the normal partition size as it can't write to these blocks, so you'd have to increase the size of the partition in order to boot a ROM.
Ok so now i understand it
Sent from my HTC HD2 using xda premium
Hey dude, I need a binary of badblocks for armv7 in android, how could I get it?
Related
Hey there
I need your help guys
Everytime i restart my hd2 all settings are lost and many apps wont work anymore.
I use the magldr 1.13 , this nand build HD2_Core_Droid_Desire_HD_V1.2.
After every restart i have to restore all apps and settings with titanium Backup, it sucks.
Has anyone else the same problem or am i the only one.
Im thankful for every help and solution.
If you need any other informations say it.
Thanks guys
Sent from my HTC HD2 using XDA App
No One any idea or solution ?
Sent from my HTC HD2 using XDA App
weezybaby307 said:
No One any idea or solution ?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I am currently using that rom and I have none of those problems. I think you need to fresh install and make sure you follow all of the instructions from the download DO EXACTLY AS IT SAYS you cant go wrong. You must have missed a step like sd card partition or something
Ok i will try it.
But ive followed all instructions.
Thank-you for answering.
Sent from my HTC HD2 using XDA App
I did a hot restart and a few hours later i pulled my bat off because the phones wiped.
And now is everything ok i dont understand it xD but its fine
A few apps disappeared but Thats not necessary.
Sent from my HTC HD2 using XDA App
My touch calibrated and the buttons stopped working shortly after the partitioned sdcard by recouvery, I tried everything and nothing so far (full wipe, stock rom, rom custom) believe that the problem is in the lowest internal drivers in
Anyone have any ideas?
Peoples ????????
Sounds like you formatted your pds partition. A Google search should point you in the right direction.
Sent from my MB860 using xda premium
maulich said:
Sounds like you formatted your pds partition. A Google search should point you in the right direction.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
+ 1 that's what has happened, google pds partition fix, there is a thread here in the atrix forums that has a flashable fix, just be sure if you are on GB based rom to flash the GB based fix. I have had to do it and it worked for me.
Found the link forum.xda-developers.com/showthread.php?t=1131649&highlight=pds
Sent from my MB860 using xda premium
I'm trying it right now
Thank you, yes you guys decided not imagine how I was worried if you can add me on msn [email protected]
curumasm said:
Thank you, yes you guys decided not imagine how I was worried if you can add me on msn [email protected]
Click to expand...
Click to collapse
Glad it worked out for you
Sent from my MB860 using xda premium
Hi
Everyone someone plz help me my galaxy note is dead not because iam installing rom in recovery but it stuck in installing so i remove battery but now it is not turning on nor in download mode ,nothing key is working pkz help me out ot this bro plz.....
Sent from my GT-I9300 using xda premium
Help me how i flash my samsung galaxy note nor it is showing anything while iam connecting yo pc ill try many time remove battery and many times trying to go in downloading mode nothing help me plz help me guys....
Sent from my GT-I9300 using xda premium
Why no one i helping me .....?
Sent from my GT-I9300 using xda app-developers app
Because you didn't elaborate.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
cocaino said:
Why no one i helping me .....?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I Know Your Language A´int English But Try Google For Translation And Just Paste What Really Happened. Because If We Don´t Know Then How Can We Help You ? Yeah You Feeling Kinda Stressed Right I Do Feel You But Elaborate What Went Down.
cocaino said:
Hi
Everyone someone plz help me my galaxy note is dead not because iam installing rom in recovery but it stuck in installing so i remove battery but now it is not turning on nor in download mode ,nothing key is working pkz help me out ot this bro plz.....
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
i can undesrtand your problem dude.. ihave just suffered it from.. your motherboard is blown up now it is needed to be replaced with a new one.. now no one can help you asap go to a nearest samsung service centre to get it fixed.. good luck
Sent from my GT-N7000 using xda premium
His motherboard has not "blown up", but it is possible that if he was flashing from a stock rom, wiping and flashing a new ROM triggered the emmc bug. Thus resulting in an 'unusable' internal storage chip.
If this is the issue, only way to fix this is to take it to a Samsung service center (there are various 'alternative' methods out there, but non of which are guaranteed).
Best of luck!
Sent from my paranoid GT-N7000
Thx guys thx a lot
Sent from my GT-I9300 using xda premium
My language is english .. but bad english sorry
Sent from my GT-I9300 using xda app-developers app
dude in emmc bug the partition get disturbed but the phone still gets in to recovery or download mode but here the phone is not showing any sign of life read carefully so it's a clear issue of motherboard
Sent from my GT-N7000 using Tapatalk 2
abhinav quietly brilliant said:
dude in emmc bug the partition get disturbed but the phone still gets in to recovery or download mode but here the phone is not showing any sign of life read carefully so it's a clear issue of motherboard
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
This is not always true. It can sometimes affect the recovery partition as it is a PARTITION of the eMMc chip. Because the error causes a bad block on the chip while calling upon the firmware to format a region of it, the affected block can render the entire chip useless (unless one were to come into possession of some of Samsung's proprietary tools to fix an issue like this; in which case, would fix the chip).
andreww88 said:
If your phone is "superbricked" hard brick, then a JIG won't work because it damages the eMMc chip.
Even if the JIG gets you in download mode though, if Odin fails at factoryfs.img or NAND write start then it will still be bricked.
Click to expand...
Click to collapse
P.S. The eMMc bug is also known as the 'superbrick' bug
Because of this in many cases one cannot even revive their their note using a JIG. Therefore it must be sent in for a MOTHERBOARD replacement (seeing that the emmc chip is soldered onto it)
Please search the forums for "superbrick bug" for more information.
Please be more knowledgeable before attempting to correct somebody..
Ranafram said:
This is not always true. It can sometimes affect the recovery partition as it is a PARTITION of the eMMc chip. Because the error causes a bad block on the chip while calling upon the firmware to format a region of it, the affected block can render the entire chip useless (unless one were to come into possession of some of Samsung's proprietary tools to fix an issue like this; in which case, would fix the chip).
P.S. The eMMc bug is also known as the 'superbrick' bug
Because of this in many cases one cannot even revive their their note using a JIG. Therefore it must be sent in for a MOTHERBOARD replacement (seeing that the emmc chip is soldered onto it)
Please search the forums for "superbrick bug" for more information.
Please be more knowledgeable before attempting to correct somebody..
Click to expand...
Click to collapse
whatever the issue is ultimately the motherboard is need to be replaced.. am i still wrong?
Sent from my GT-N7000 using xda premium
Hey Users,
I think I have a problem with badblocks on my Leo, is anywhere here, with a solution for this prob?
Sent from my PIXELDROID HD2 using xda premium
You cannot fix bad blocks once they are there..
All you can do is to use bigger partition size on NAND roms or use NativeSD roms.
landcruiser76 said:
Hey Users,
I think I have a problem with badblocks on my Leo, is anywhere here, with a solution for this prob?
Sent from my PIXELDROID HD2 using xda premium
Click to expand...
Click to collapse
I don't think there is a fix, all you can do is to enlarge the partition that has bb.
Hi,
I searched all the thread about the same but no solution exactly to resolve it. Flashing a stock WM6.5 ROM may help some cases to clear bad nand blocks. But most of the cases only one solution to increase the memory +10 mb more for the ROM required while flashing the recovery.
Sent from my NexusHD2 using xda premium
AW: BadBlocks
@[email protected] said:
Hi,
I searched all the thread about the same but no solution exactly to resolve it. Flashing a stock WM6.5 ROM may help some cases to clear bad nand blocks. But most of the cases only one solution to increase the memory +10 mb more for the ROM required while flashing the recovery.
Sent from my NexusHD2 using xda premium
Click to expand...
Click to collapse
Du you have also that problem? My last wm6.5 was at 2010 on my device, than I flash only android customs and since august of the last year is it the problem, when I flash the rom with the layout from the cook, than hang over the leo in bootloop.
Sent from my PIXELDROID HD2 using xda premium
Yes that because of bad nand blocks. I also have the same problem so I always make +10 mb from the ROM thread mentioned I choose to install. When I install suppose a 170 mb nand partition ROM it occupies 175 mb system space always as I presume I have bad blocks.
Sent from my NexusHD2 using xda premium
landcruiser76 said:
Hey Users,
I think I have a problem with badblocks on my Leo, is anywhere here, with a solution for this prob?
Click to expand...
Click to collapse
Read the second half of this post:
http://forum.xda-developers.com/showthread.php?p=33065124
---
Ask me about my vow of silence....
AW: BadBlocks
I have read the lumberjack log, but I can't find bad blocks
Sent from my PIXELDROID HD2 using xda premium
landcruiser76 said:
I have read the lumberjack log, but I can't find bad blocks
Click to expand...
Click to collapse
Does you device have the Samsung or Hynix chip set?
AW: BadBlocks
Good question, can I find this on Device, when it is on?
Sent from my PIXELDROID HD2 using xda premium
AW: BadBlocks
I'm so sorry for my question, but I'm in the phase to learn to understand the codes from roms.
Sent from my PIXELDROID HD2 using xda premium
landcruiser76 said:
Good question, can I find this on Device, when it is on?
Click to expand...
Click to collapse
The HD2 aka Leo is manufactured with 2 different NAND Flash ROM chipsets.
You can find the type by entering the tri-color boot mode.
If you see PB81120 SS-B3 on the first line that means your NAND Flash ROM is from Samsung (KBY00U00VM)
If you see PB1120 HX-B3 on the first line your NAND Flash ROM is from Hynix (H8BFS0WU0MCR)
After about one year of usage the Samsung chipset usually has a dozen or so bad clusters.
Hynix normally has none of them or just a couple.
AW: BadBlocks
It is an hynix memory
Sent from my PIXELDROID HD2 using xda premium
landcruiser76 said:
I think I have a problem with badblocks on my Leo, is anywhere here, with a solution for this prob?
Click to expand...
Click to collapse
landcruiser76 said:
I have read the lumberjack log, but I can't find bad blocks
Click to expand...
Click to collapse
landcruiser76 said:
It is an hynix memory
Click to expand...
Click to collapse
Since you have a Hynix and you cannot seem to find any bad blocks it is possible you don't have any (many) to worry about. What made you think you had bad blocks you had to deal with?
landcruiser76 said:
Du you have also that problem? My last wm6.5 was at 2010 on my device, than I flash only android customs and since august of the last year is it the problem, when I flash the rom with the layout from the cook, than hang over the leo in bootloop.
Sent from my PIXELDROID HD2 using xda premium
Click to expand...
Click to collapse
NYLimited said:
Since you have a Hynix and you cannot seem to find any bad blocks it is possible you don't have any (many) to worry about. What made you think you had bad blocks you had to deal with?
Click to expand...
Click to collapse
To answer your question he had a bootloop. @OP Just flash a slightly larger /system partition, you should be fine. Try flashing a different ROM with the recommended partition size, that could help determine if it's somehow a ROM specific issue.
AW: BadBlocks
At all roms, I must make the layout bigger then the cook write, that I make not - - - > bootloop
Sent from my PIXELDROID HD2 using xda premium
I have mentioned same in my first post reply. You still got good experience.
Sent from my NexusHD2 using xda premium
Status bar disappeared and I get a message saying android UI has stopped working. I did a factory restart but still no difference.
Sent from my NexusHD2 using xda app-developers app
Might be time to change ROMs, did that ROM used to work and only now doing it?
orangekid said:
Might be time to change ROMs
Click to expand...
Click to collapse
boy, that escalated quickly.
---
I think he should tell us the last thing he did before the error's occurrence. @5warafat1 What was the last thing you had done before this error appeared?
Marvlesz said:
boy, that escalated quickly.
---
I think he should tell us the last thing he did before the error's occurrence. @5warafat1 What was the last thing you had done before this error appeared?
Click to expand...
Click to collapse
lol, yeah I suppose it did.
I think I inferred that this was at the inception of the flash, and not something that just started happening.
He did factory reset and it is still doing it, which tells me it must just be the ROM.
Re: Status bar disappeared
Didn't do anything. I think i just tried to open an app and it suddenly closed and I got this error message, then status bar went.
Sent from my NexusHD2 using xda app-developers app
5warafat1 said:
Didn't do anything. I think i just tried to open an app and it suddenly closed and I got this error message, then status bar went.
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
You could try to just dirty flash your existing ROM, or is this an SD ROM?
Its not on SD its on nand
Sent from my NexusHD2 using xda app-developers app
5warafat1 said:
Its not on SD its on nand
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
i would try what orangekid said
then if it stll doesnt come back.. backup the apks you dont want to download
again and do a fresh install
5warafat1 said:
Its not on SD its on nand
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
Yeah dirty flash the same ROM, that should fix any system stuff that got corrupted while leaving your apps / data intact.
What do you mean by dirty flash sorry
Sent from my NexusHD2 using xda app-developers app
5warafat1 said:
What do you mean by dirty flash sorry
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
Flash the same rom again from recovery without wiping anything.
Edit: I was too late.
I wouldn't want to flash a rom because in the past I nearly ended up bricking my phone. I got Android on this phone through someone else. Isn't there another way around this, something more simple
Sent from my NexusHD2 using xda app-developers app
5warafat1 said:
I wouldn't want to flash a rom because in the past I nearly ended up bricking my phone. I got Android on this phone through someone else. Isn't there another way around this, something more simple
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
Nope.
Since the problem originated without apparent reason, we don't know what caused it; we can't really tell you how to fix it without a re-flash.
And by the way, you can never brick your phone through CWM. So just re-flash the ROM. Besides, that "someone" had already done the hard part. He installed everything for you, now you just need to put the zip on your sdcard, boot into recovery and "install zip from sdcard".
So can i install any rom or just the same one and is there any thread on this.
Sent from my NexusHD2 using xda app-developers app
5warafat1 said:
So can i install any rom or just the same one and is there any thread on this.
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
You can flash any ROM and you will not brick your phone. You literally cannot brick an HD2 with anything android related, ONLY with radio stuff and WM6.5, so just read up on how to flash one and flash another ROM.
orangekid said:
He did factory reset and it is still doing it,
Click to expand...
Click to collapse
if something has been installed into the system partition, then it will still be there after a hard reset. Example, if you install a data2ext script, then do a hard reset, it will still be there when the phone restarts.
samsamuel said:
if something has been installed into the system partition, then it will still be there after a hard reset. Example, if you install a data2ext script, then do a hard reset, it will still be there when the phone restarts.
Click to expand...
Click to collapse
Yeah, that's why I told him to dirty flash the same ROM, but he has no clue which ROM he flashed, so at this point I think he should just find a ROM he thinks he'll like and clean flash it.
As long as he's messing with Android he can't do any actual harm.
5warafat1 said:
So can i install any rom or just the same one and is there any thread on this.
Click to expand...
Click to collapse
What I meant is, you can install your previous ROM without having to do anything to your device aside of putting the previous ROM on the sd and flashing.
However, that DOES NOT mean you can install any other ROM without modifying the partitions.
And yes, there's a thread for this, it's called search.
P.S: Pay attention to the italicized keywords.
Do this as the easiest thing,
go to settings > about phone, and scroll all the way till you see the kernel version and build version.
Take a screenshot of that and upload it if you can.
This will tell us what ROM you have and you can dirty flash it.