yashsingh1/xdaforums huggingface dataset:
[Android Software Development] hg42:
insane chip + insane emmc firmware = brick bug

brick bug + stock ics kernel + wipe = brick (eventually)

Press the button (check?), then it scans every byte in your emmc flash memory.

If it freezes (or may be heavily slows down) at some point, you habe the brick.

If it finishes scanning at normal speed, you are lucky.
[Android Software Development] Daruka:
It scanned the entire memory and said 'Congratualions''.

I guess I am lucky.
[Android Software Development] Alahdal:
what is your mobile version 16gb 32gb... how long does it take to scan
[Android Software Development] Daruka:
16GB and I bought 32GB Sandisk, external card.

My question now is,.

If the Bug check says YES, I have insane chip. are there any remedies?

Or shall I just stick with the ROM I am using now. ,RocketRom V11.?

Everything is working fine but you got me thinking with the brick ''eventually''' thing.

Please let me know/

It took about 5 minutes to scan.
[Android Software Development] Daruka:
If I take out my 32GB external microcard, Reboot and then go into Recovery and run your WRITE scan app, is that okay?
[Android Software Development] Alahdal:
I was hesitant to make any change on my device such as root, kernel or custom Rom. I couldn't hold myself.. :)

Finally, I flashed HC 4.3 to try emmc bug check and result as follows:

Brick Bug?

Yes, insane chip.

Scan: Completed with "Congratulation" :)
[Android Software Development] hg42:
the write scanner constantly creates a file and deletes it again and so on, so it doesn't harm (creating files is a very usual).

Do you need it? it's only an experimental scanner for people with "moving bricks", that is bricks that change there occurrence/position all the time.

It doesn't tell you anything about having a brick or not.

Btw. did the brickbug check app report an insane chip?

Anyways, if it says Congratulations you should be brick free.
[Android Software Development] asafki:
Hi,

Running the find start script hangs (actually reboots) my device, but at a different location every time. what does it mean?
[Android Software Development] aletheus:
The superbrick bug is in the internal memory's firmware, not in the physical memory. EMMC_CAP_ERASE corrupts the firmware so it thinks there's a bad physical block when, in fact there is not. So its a moving target. Ultimately that's why you have to make your /data partition as small as possible, it decreases the likelihood of the superbrick randomly assigning the 'bad' ghost block to your redefined partition.

The best solution is to get your device running, then trick your device into booting from your extSdCard.

One moment, and I'll post the link to the thread where they successfully accomplish this.

Here u go! Good luck, I have yet to try this, I just went and got the note 10.1 last week.

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

GT-P6800

GT-N8013
[Android Software Development] hg42:
as aletheus already said your brick is a moving target.

As I understand it, the brick is caused by corrupted administration data kept somewhere in the flash memory chip, which seems to be damaged by the (secure?) ERASE command. This can only be repaired by completely clearing the chip, so you would need JTAG equipment to reinstall.

Some people seem to have the brick position changing all the time (I'm not sure if it stabilizes after a longer time?).

But many have a stable brick which doesn't move at all (fortunately including me).

This kind works well after repartitioning with the correct PIT (or parted).

I for myself didn't have any problem after repartitioning, it's behaving completely regular (of course I cannot flash a stock PIT and have 2 GB less memory).

The stable bricks may be moving for some time at the beginning, so you may still get a stable brick. The stabilization process seems to be dependent on writing to the device, so simple read tests don't help.

You may write to the partitions/install ROMs/etc. to see if it changes...please share your observations here...
[Android Software Development] citifone:
How long is it supposed to run after you install emmc scan find brick? I let it run and it was running about 24hrs and still running so I removed battery because I thought something must be wrong. I bricekd my phone the way you did yours, can flash original PIT and when flashing rom, it stops flashing at factoryFS..

Im wondering which patch PIT file did you use to repair your phone?

Thanks
[Android Software Development] aletheus:
Justin s you know, once te partition scanner stops running at a steady pace, that's where your brick starts/ends... just remember it's imaginary, there's not anything wrong with your physical memory, but the DMC firmware thinks there is. Once you stop getting a MB/s scan speed, you've found your start/end.

GT-P6800--Superbricked...

GT-N8013--Daily Driver
[Android Software Development] halim8051:
hi .. i have a samsung p6200, may be bricked, after wipe from android recovery. i've tested with stock rom P6200XXLQ1_P6200OXALQ1_ATO, it wont boot, stuck on Samsung logo.

and the , i see this thread, tried to run 120824-151927-emmc_scan_all_partitions_once.zip , and stuck on /dev/block/mmcblk0p10.

please help me , i have tested to flash several stock rom, it won't work..

Thank you, sorry if my English , bad
[Android Software Development] hg42:
You probably have an emmc brick, like so many others.

First option is to try to remove all traces of custom installations and then use your warranty.

Or, if you don't have warranty or don't want to use it, you should read my PIT thread (link in my signature).

Note that this is a workaround, but no real fix/repair.
[Android Software Development] thangphysk48:
I've install OS on extSDcard, so, how to scan internal emmc, please help.
[Android Software Development] hg42:
usually, the 'all partitions' scanner scans internal and external sd.

The 'find brick' scanner should scan internal sd, seen from recovery configuration.

Did you already try and it didn't work or are you asking before trying?
[Android Software Development] thangphysk48:
Yes, i've try before ask because it just seen my extsdcard. It mean that my internal emmc completly gone, right? Or there any way to recover it?
[Android Software Development] hg42:
if the emmc brick is in the beginning of a partition it cannot be mounted, so it looks like completely gone.

You probably can recover a big part of it.

Just read my pit thread (first post or complete if you want more details).
[Android Software Development] thangphysk48:
Thanks for your answer. But there are anyway to fix it? Now I run on class 10 extsdcard. It's not too slow, but my phone is very hot and battery drain too fast. I'm using SGS Captivate, so I cannot use your PIT file :(
[Android Software Development] halim8051:
thanks sir, for the advice, i will try the warranty way. wish me luck
[Android Software Development] hg42:
Sorry, I currently don't remember, did I say it doesn't work, or is it only because there are no patched pits for it (currently)?

In the latter case I may be able to generate them.
[Android Software Development] thangphysk48:
Yes, currently dont have patch for i9000, and you said that i9000 model has another partition structure. I think that my sgs captivate (sgh-i897) has same struture as i9000. One more thing, I've try to use n7000 patched pit in odin, resull was failed.
[Android Software Development] hg42:
This is very dangerous.

If the lower partitions <system have a different structure, your boot partitions will be unusable.

This would require jtag.
[Android Software Development] thangphysk48:
Yes, I know. Anyway, I think my phone almost dead :p.

But, lucky that my boot partition still there.
[Android Software Development] hg42:
Note: it may be possible, that I am only missing some knowledge about the PIT structure, meaning a patched PIT could be created, but I don't know how.

Recently someone created a program for editing PITs: PIT Magic v1.3.10 - Samsung PIT Creator, Editor and Analyzer

which may be able to create such a patched PIT, but I still didn't try (I'm a linux guy, currently no usable windows and no time to bring it up again).

You may use the manual method using adb/parted etc., see forest1971 thread mentioned in my PIT thread (in first post):
[Android Software Development] radx:
Sorry for being dumb here but I have a bricked S2. As in it's dead. How can this help me? I cant start the device nor get into any recovery mode?

Is this for people who haven't yet bricked their devices or am I missing the picture here somehow? Again, sorry for asking dumb questions but I read the whole first post and I still don't get it.
[Android Software Development] hg42:
It's mainly created for people with emmc brick, which are able to boot into recovery. Most n7000 emmc bricks are in this category.

If they can't, they can try repartitioning with a rough estimate (see my pit thread) and optimize later by using the "find brick" scanner.

Second usage is to check if the repartitioning worked. Then scanning all partitions should completely work flawlessly (without freezes or slowdowns).
[Android Software Development] cooldoud:
Great stuff! Was busy doing a dd to check on my side (getting fsck errors in recovery), but found your thread in the meantime. Much quicker :)

Looping your script from recovery now, and also seems like I don't have corruption, so that's good too :highfive:
[Android Software Development] hg42:
Using an 'infinite' scanner?

In the mean time I think the looping doesn't help much, because there is no write between the loops.

I assume, only writing changes something in the flash (and the wear leveler).

Also beware that those scanners don't scan all bytes, but only in steps, it's designed to find bad flash blocks.

This is the right thing for emmc bricks, but I don't know which other errors can occur in flash memories.

To be sure I would scan with dd.

Btw. fsck errors usually don't imply corrupted flash blocks, at least not emmc bricked blocks.

Emmc bricks freeze or slow down significantly or reboot, but you would not get through to fsck error messages.

So I think you're safe according to emmc brick.
[Android Software Development] angello2299:
wrong thread
[Android Software Development] diamondheart:
Please give me some advise

I asked this question on forest1971's Thread 'How to revive your bricked Gnote'

I want to know your opinion and want some advise from you too.

My Note is running Cassies Xtralite LRQ V8 ROM. I think I can install app and games to certain amount like 350 Mb after that amount, if I install something, my Note freeze, when I restarted, sometimes setup wizard appear, after finishing setup-wizard, the latest installed app disappear. It's really annoying me. My previous Rom is Paranoid Android 1.6 it is same in that ROM too I can't install apps a lot. I used Rocket MIUI before that, same freezing after installed apps reached certain amount. There's not bad block check using dd in all partitions. I checked using your partition scanners too, no freezing on all partitions. The only one I still need to try is emmc_scan_write.zip. I will try that zip after my Note is fully charged. What do you think about this situation ? And I want to know is your note freeze or never freeze :good: ?
[Android Software Development] hg42:
I think, this is a question more suitable for the pit thread...(see my signature).

Please head over there...
[Android Software Development] chesus05:
Hi!

I trying to use this test for i9100, its flash ok in the stock recovery but nothings more happens.

Is it comptible with i9100?

Thanks a lot
[Android Software Development] hg42:
It's compatible with 9100 as far as I know.

But stock recovery may have different kinds of problems including no output at all.

You may fake flash CWM.zip, I think it's available for your device. From there fake flash my scanners...

(but never wipe from this cwm on a stock kernel!!!)
[Android Software Development] chesus05:
Excelent, Its works.

It take about a hour to scan the 16 gb.

unfortunately from 300MB up to 3500mb were corrupt :(

But the best news is that it worked, I put the "pit" closer to those values ​​and works like a charm

Thanks to your work get my phone back!

Thanks a lot!
[Android Software Development] hg42:
Not necessary, this one is only experimental for trying to trigger reordering of bad blocks by the wear leveler.

It's NOT a scanner to determine brick.

Apart from that, it never reached it's target. Seems the memory allocation isn't stimulated by this method.
[Android Software Development] hg42:
Nice to hear...

One hour seems to be quite high for a scan.
[Android Software Development] hg42:
My remaining 14gb need less than a minute with my all-partitions-once scanner.

Note, when the scanner suddenly slows down, you have found the beginning of the emmc brick, not only when it freezes.
[Android Software Development] chesus05:
I scanned once and got an error between 300 and 3500.

I used the pit which best fitted that, and scanned with "scan_all_partitions_once", which turned up ok.

Now I'm re-scanning with "emmc_find_brick_start/end", and I got an error between 1073/2148, so I want to know if the scanner scans all 16gb or just the pit-patched memory.

How do I interpretate an error in the complete scan if I have already pit-patched?

thanks
[Android Software Development] hg42:
The find-brick scanners scan the whole raw device up to the end (or until a freeze occurs). They work independent of the partitioning. In fact they also scan the partition table itself etc.

The all-partitions scanners scan only the partitioned space (that is inside the partitions), so the gap in the partitioning (where the brick is) will be left out.

If you get different values, your brick has moved.

Either it stabilizes after some (write) usage of the flash memory or it keeps moving all the time.

It seems that most emmc bricks stay in a certain area even if moving a bit, but some seem to always jump around.

However, I don't have enough feedback to make statistical assumptions.

You should keep the device as it is and scan from time to time.

Write down the values and see if there is a pattern.

You probably will be able to choose a gap that fits around it.

If the brick jumps out of it's prison, you might get freezes.

So keep backups around.

Then you should repartition with a new pit to catch up with the new brick position.
[Android Software Development] ahhl:
o.. i have been waiting to get freeze situation, 3 hrs, still moving slowly still a 2181, at lease 15sec/MB. is this consider brick section?

look like i have to rescan again

-------------------add

start brick 1023mib = 1073 mb

end brick 7168mib=7517mb

so which pit file i should use?

N700016GB
[Android Software Development] hg42:
'slow down'

So you didn't read the thread starter?

This behaviour has it's own section.

'which pit'

Read the pit thread for the pits, the starter should contain all info, and it's explained several times in that thread.
[Android Software Development] tab0reqq:
Hm. Im SGS2 16GB user.

As many others i bricked my phone because of "wipe factory reset" from stock 4.0.4 ROM recovery.

So far after few scans from beginning i was able to find start point at 1073 (blocks).

Sadly im not able to verify end of bricked/blocked memory. Once it was 3391, other times 3222 and 4614. Is it possible that it's moving bad block?

is there a way to fix it? My warranty is over, so im not able to get free replace.

p.s After few PIT's i was able to install many times 2.3.5 and 4.0.4 rom. I never succeed to install any kind of 4.1.2 ROM (stock nor neatrom). That's strange.
[Android Software Development] hg42:
yes, may be it's a moving brick, but that's also usual at the beginning. It may stabilize after "some" time.

I am not aware of a difference between 4.0.4 and 4.1.2 rom.

May be it uses more space of the partition and you still didn't skip all your (current) bricked blocks (so a "bigger" PIT would be needed)?

Did you scan with the all-partitions scanner? After repartitioning it should run completely OK (no freeze, no slow down).

Perhaps you should take a PIT with gap end around 5000 or 6000.

First keep far away from the known bricked areas and see if it work reliable.

You can optimize after using your phone for at least some weeks.

Repeat scan in the mean time and note the values.
[Android Software Development] eljuggy:
reboot at second partition when scanning with 120824-151927-emmc_scan_all_partitions_

Hello,

I just superbricked my Note by wiping/flashing under CF Root LRQ... (I didn't realised I was back there after flashing back to ICS...)...

well, I tried to flash 120824-151927-emmc_scan_all_partitions_once.zip, I got OK at the first partition scan then after a few seconds on the second one (looked like "mmckl01" something - I can try again if needed)... the phone rebooted...

I think this ain't good.

I tried scan "start" under recovery and the reboot occurs above 580 MiB

I launched scan "end" the reboot occurs under 2970 MiB (is there a log somewhere cause it took almost 2 hours ?)

my questions are :

Shouldn't I go for warranty right now ? or after which modifications to increase my chance of being taken care of (download screen says SAMSUNG OFFICIAL, no custom binary or triangle) - but I'm under Philz kernel rooted and custom rom - should I try to flash a stock kernel at least (or stock firmware -

but odin won't flash yet till I partition again

) ?

And if I create the appropriate pit file and flash a stock rom... will I be good for warranty with a working phone !!!

(or should I brick it again to send it to warranty !!! that's half crazy...)

If I happen to correctly repartition my device and fix it will I be completely good with my device (apart for the lost space) ? no problem with future upgrades ? performance or stability with internal NAND ? (I read about the moving brick and need to stabilize the partitionning... but once/if it is done the device is good for service ?)

Any help much much appreciated ....

Thank you for this thread anyway !
[Android Software Development] :
Trying to sort out friends emmc bricked phone.

Hi all! Just wondering if someone may be able to help me here.

A friend of mine recently got hold of a second hand Galaxy Note, and decided he would have a go at putting a custom rom on. He was aware of the emmc bug, but hadn't really researched it properly and just assumed if he stuck with latest roms etc. he would avoid any issues (daft sod). As expected, at some point he has now damaged the emmc and he could not get anything to flash to the device, and recovery was no longer working - download mode still working fine.

Having had a Note myself, and used to putting custom roms on my various devices, I've said I would have a go at getting it up and running. I first of all tried both windows and linux with clean driver installations and direct usb connection to back ports on my pc and attempted to flash stock roms (ICS rom first, then GB rom). ICS rom would get 98% across and then just stick. GB rom would complete but never boot and still no recovery.

I then used forest1971's pit files, going through each one until I managed to successfully flash the ICS rom. Custom PIT option 2 worked for me. However, rom still not booting fully, just stuck on pulsing logo, then would go back to bootanimation -> pulsing logo in a loop. Realised this may be probably due to me not doing a full wipe.

I then installed a safe recovery, did a wipe and decided that for now I would install Cyanogen as it has a smaller footprint, for testing. So we now have Cyanogen up and running with no issues (so far).

I have then used the scanner from here to try and work out the parts of the emmc which are damaged. In the instructions, it states that the scanner will freeze when it encounters issues - I found that instead of freezing however the phone just restarts. (This is using the scanner that scans the whole device from the beginnning). It rebooted at different parts of the scan which is weird - first at 702, then 778, then 802. I haven't ran it again after those times, as I'm assuming that the damage is probably past the 700 mark - so the start of the area I probably need to block off.

I am currently running the reverse scan, and down to 9224mb at the moment with no restarts. My question is: should it freeze, or would it possibly restart when encountering issues? Just out of interest more than anything else. Also, if my friend is able to contact the person he got it from and can send for warranty replacement, is there a pit file available that will restore the original layout - or do I just flash a stock rom and not specify a pit file?

Cheers,

Jamie

ADDITIONAL:

On the backward scan, it got stuck on 3479 for some time. Because I was working on something else at the time I don't know how long it got stuck but I left it and it has carried on. Is this necessarily a bug? Am I doing something wrong?
[Android Software Development] kopiko09:
Hi Hg42,

I have SG2. I recently found it bricked without any apparent reason. But after tried everything, I came to conclusion that this is partition problem. I want to try one last resort before bitting the bullet and send it to Samsung (and probably will be told it is unrepairable anyway)

Noob question: My phone is bricked that only can access download mode, can't get into recovery mode. Is there any way to scan the partition in this condition? I tried running ADB driver, but my PC does not recognise this devise since it is under Samsung driver.

Thank you very much

Edited: Nevermind the question above. I found the premade PIT files at the end of your first post. As I'm flying blind here, I tried the first PIT file with the least amount of gap. I have flashed it for almost an hour with no result. Wondering if this is normal for SG2 16GB

Edited2: After waiting 4 hours without any results, I shut down the Odin, and pull out the cable. Now my phone is total bricked, can't even turned on. MISSION FAILED
[Android Software Development] tab0reqq:
Hi again!

After another few days i found out that my bricked are is between: 1023 MB (1073 blocks) and 5120 MB (5369 blocks).

After many (really over 10 different PITs) I've used this one: i9100_u1_02_20110310_emmc_EXT4-patched-big-bricked+5767168-kB

Sadly my phone still get's freezes, especially on app that heavily use internal memory (like saving images from Dropbox to internal sdcard, running GTA3). In many cases it's frozen with last app view on screen.

Sometimes even when i leave it on my desk, after 1-2h when i pick it up, phone is frozen with screen off. Holding power button for longer time (turning it off) helps. Then it reboots normally.

Humble Question:

Would You be so kind and prepare me good PIT file based on stock i9100 PIT?

Im complitely noob in those kind of stuff.

Flashing ROM's was enough. :(

What i did so far:

- tried flashing many S2 i9100 PIT files... still getting freezes

- every kind of 4.1.2 ROM i've installed was getting freezes even before i managed to configure it properly

- flashing PIT, flashin stock 4 file 2.3.x ROM (bootloader, pda, phone, csc), flashing stock 4.0.4 (runs ok as long as internal memory is't used that much), formatting internal USB card, factory reset (from Android not recovery).

- with ODIN 1.8.5 and every kind of PIT (besides stock) i was able to install almost all ROMs (but boot only few)

Please help!

Here are my scanning short-videos:

From beginning:

[YOUTUBE]XGE_bqi2k3M[/YOUTUBE]

http://www.youtube.com/watch?v=XGE_bqi2k3M

From end:

[YOUTUBE]laiNQceGUiY[/YOUTUBE]

http://www.youtube.com/watch?v=laiNQceGUiY
[Android Software Development] seth1836:
Nice.. Testing
[Android Software Development] hg42:
1023 MiB = 1073 MB etc.

(MiB = 10254*1024 MB = 1000*1000)

looks like an old one (very old), please read my pit thread.

That's why I don't like copies of my packages in so called "easier" derived threads.
[Android Software Development] hg42:
The brick can lead to a freeze, a reboot or a slowdown. I don't know reasons when it causes which behavior.

Just take the last "normal" (that is fast) OK message as the start or end.

You can see on a video some posts below, how fast the scan usually runs.