yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] hg42:
Ok, so the small remaining memory corresponds to the pit with the big brick area? this was the one with the biggest brick area, right? then the small remaining memory is natural.

You used the find brick scanner for the start of the brick (result around 1000, so 281 as lower end of the gap is ok), what about the end? Seems you didn't find the end of the brick?

Both start *and* end of the brick together are necessary to select a correct and optimal pit (should be clear from my thread starter, isn't it?).

Please read more careful before doing and make the facts more clear, so I can derive proper conclusions (here: which pit leads to which results, I did this and got that result).
[Galaxy Note GT-N7000 General] ntony17:
good job:)
[Galaxy Note GT-N7000 General] walwyn:
Samsung GT-P6200 superbrick stuck on ODIN flash factoryfs.img

hehe yes sir sorry for being kinda lazy or maybe just too worried to fix things sooner, I've been troubleshooting this for 3days already and i mean i even sleep around 3-4am even if i have work early morning XD

but uhmm just an idea, is it possible for making a custom pit with 2 null partition but separate? like to make the null gap memory, you know what i mean is just to jump on the precise bad blocks but can still use the good blocks in between them...? and btw whats the main purpose of emmc scan write.zip...sorry i just didnt get what it means on the decription,wil it make changes or its same as the emmc scan end and start brick that's safe?

here's my results:

emmc scan brick start

scanning 1042 MiB = 1093 MB . . .

emmc scan brick end

scanning 2024 MiB = 2123 MB . . .

this are the scans that started to show slower scanning like 10 seconds each MB

what's the best patched pit for this sir? im not sure but is it this one?

P6200_tabplus--patched--brick-between-1086-and-2160-MB--DATAFS-moved-by-1024-MiB.pit

uhmm can you also give me a dload link of a good safe kernel (if u think ill need it) and a good ICS custom ROM w/ root so I can flash the Paranoid Android w/ safe sytem factory reset on CWM w/o bricking :) Thank You So Much
[Galaxy Note GT-N7000 General] hg42:
today I found the time to look into your pit file.

Because I didn't find the extracted PIT in any post, I repacked my former copy and attached it to this post.

It is falling into the category of the i9000 like pits. The offset values are missing, so it seems all partitions have to be contiguous, which means I don't know a way to create a gap in the partition table (or hole? which is the better word in US english?).

I would try the Partition Magic program to compare how it interprets this PIT file, but currently I have no working windows available (with a running DotNet installation) and not enough time (and motivation) to bring windows up again (which means recovering windows from a severe crash, I sometimes hate it because it is often stealing too much of my time).

May be someone can post a screenshot (of a table or so showing the attached PIT)?
[Galaxy Note GT-N7000 General] mpt123:
hard brick

Thanks a lot for this excellent post.

Really appreciate your efforts on making your work in to a thread like this which is priceless.

I had bricked my phone few times due to full wipe on ICS. Had gone through the steps mentioned by

you to identify the fault partitions and found that the 9,10,11 partitions have corrupted areas.

Finally i was able to recover my phone by using the standard pit for galaxy note gt n7000 with 3GB less.

After this i experienced that my note hangs many times while using youtube , daily motion and some times

playstore. the screen will be on without any response. I have to press power button long to restart phone again.

I tried changing roms custom(CM,MIUI....), stock. The result was same. Now iam using the leaked JB version

and my phone getting stuck at some app every time.

Is there any solution for this problem.

Thanks a lot in advance.

Mathew
[Galaxy Note GT-N7000 General] hg42:
did you use the find brick scanner to get the start and end of the bricked area?

did you select a pit which completely covers this area with the gap (a.k.a. ...brick-from-x-to-y...pit)?

I you already did these steps, you should try them again, because the emmc may not be stabilized, yet (if it will ever be, seems that some people have kind of "moving bricks"). The stabilization (and also the moving brick) process seems to be driven by writing data to the memory. So after using the phone for some time there still may be changes to the brick area location. You probably need to be patient before claiming a working phone or a moving brick or any other final result. So don't use it with important data, at least not without a good backup strategy.
[Galaxy Note GT-N7000 General] hg42:
yes this is the correct PIT, because 1086 < 1093 and 2123 < 2160 are both true and the gap start and end numbers are close to the brick area numbers, so you loose a minimum amount of memory (for this brick).

sorry, I only know N7000 ROMs etc.
[Galaxy Note GT-N7000 General] mpt123:
brick

Thanks a lot for your reply.

I will try brick scanner to get start and end area.
[Galaxy Note GT-N7000 General] hg42:
*Which* pit? There are many pits in the zip.

Looks like you did not use the scanner before selecting a correct pit. Is it because you cannot use cwm?

Flashing a rom doesn't work while having bad blocks in the partitions. This means you cannot install a recovery together with a rom.

Instead you have to flash a recovery or for some devices like n7000 a kernel with integrated recovery.

To do this in download mode you need an odin flashable package, which is a tar file in this case. Sometimes the tar file may be packaged in a zip for uploading, so read the description, it should mention odin explicitely.

As there are only few odin flashable packages, you shouldn't look for your favorite one, instead you can use any suitable as a temporary solution (which will often be from gingerbread).

The same is to be used for the rom. Use a well known package instead of your final target, to avoid new unknown problems.

First aim is to get the phone up again.

Then you have your hands free for optimizations (meaning you can use better tools from there).
[Galaxy Note GT-N7000 General] walwyn:
Samsung GT-P6200 superbrick stuck on ODIN flash factoryfs.img
[Galaxy Note GT-N7000 General] hg42:
the moved-by-1792-MiB corresponds to the memory lost.

Note the units

1 MB = 1000*1000 = 1000000 and

1 MiB = 1024*1024 = 1048576
[Galaxy Note GT-N7000 General] walwyn:
Samsung GT-P6200 superbrick stuck on ODIN flash factoryfs.img

so 1 MB - 1 GMiB? so i lost just a little memory less than 1MB? sorry for being noob on this MiB is new term to me :P

but thanks alot, not for your help and your thread i cant revive my tab super bricked p6200 :)

i'll make a summary of my struggle on that superbrick on this thread for noobs like me to understand it easir step by step ^^ credits to Sir hg42 :highfive:
[Galaxy Note GT-N7000 General] hg42:
KiB / MiB etc are computer units, because computers 'think' in powers of 2 .

2^10 = 1024 = 1 KiB

2^20 = 1 MiB

2^30 = 1 GiB

etc.

Many years ago all numbers in IT area were given in powers of two and MB for computers was 1024x1024, so MB had different meanings for the computer world and for the real world.

Today these worlds are much more intermixed, so they created the MiB etc. units to be more precise.

Originally I wanted to say this:

1792 MiB = 1792x1024x1024 = 1879048192 ~ 1.88 GB
[Galaxy Note GT-N7000 General] amirhashim:
i have the same problem!!
[Galaxy Note GT-N7000 General] walwyn:
Samsung GT-P6200 superbrick stuck on ODIN flash factoryfs.img

is there a way I can make my own pit partition that covers area of my brick coz

P6200_tabplus--patched--brick-between-1086-and-2160-MB--DATAFS-moved-by-1024-MiB.pit didn't flash maybe because he's too close from 1086 to 1093 start brick, maybe if a pit of starting lesser than 1042 or between 900-1000? so I can still revive a lil more memory sacrificed :confused: I hope the Samsung won't notice the device total memory i sent it to repair the usb port loose :( will it void the warranty?

emmc scan brick start

scanning 1042 MiB = 1093 MB . . .

emmc scan brick end

scanning 2024 MiB = 2123 MB . . .
[Galaxy Note GT-N7000 General] mpt123:
emmc scanner result

I tried using your emmc scanner and got result as

brick start-----750 MB (Phone restarts at 780 MB)

brick end ----2145 MB (freezes at 2144 for long time)

Could you please suggest appropriate pit file for this

Thnx
[Galaxy Note GT-N7000 General] Ajsk:
Ow, thank you for your help, yes, i deleted the file from the post by mistake (((( when editing the post ((((, I’m going to ad it to my next post, and will really appreciate, if you will try to find an extra free time to have a look at my PIT.
[Galaxy Note GT-N7000 General] hg42:
I found a way to try PIT Magic and also got a response from it's author about your pit file.

The result is, there is currently no way to describe a gap in the partition table with this kind of PIT.

The only hope I have is something like defining a partition in a way that it will be ignored by the os.

It mainly depends on which data is used by the os to mount it's partitions. If it uses the partition number (count, something like the 10 in mmcblk10) then an additional inserted partition would not work. If the partitions are mounted symbolically (name, id etc.) then it may work.

One problem will be how to test it.

I don't have a spare phone for testing.
[Galaxy Note GT-N7000 General] hg42:
i9000 PIT scheme, Samsung download mode

Hi,

I looked into how partitions are mounted on android.

Seems like all (or most) devices mount there partitions directly by number, e.g. for the N7000:

android/cm10/out/target/product/n7000/root/init.smdk4210.rc, line 40:

mount ext4 /dev/block/mmcblk0p9 /system noatime wait ro

mount ext4 /dev/block/mmcblk0p7 /cache nosuid nodev noatime wait

mount ext4 /dev/block/mmcblk0p10 /data nosuid nodev noatime wait noauto_da_alloc

mount ext4 /dev/block/mmcblk0p12 /preload nosuid nodev noatime wait

mount ext4 /dev/block/mmcblk0p1 /efs nosuid nodev noatime wait

so inserting a partition is not an option (without changing kernel).

The last possibility I see to get an i9000 PIT working is describing a partition in the PIT which is not really created but only counted for space calculations.

This may be possible by seom special partition parameter combinations.

I think the part of the phone firmware using the PIT structure to create partitions is in Samsung specific download mode.

It's proprietary and we will not get any info about it.
[Galaxy Note GT-N7000 General] hg42:
I doubt that it's too close to the brick start.

May be you have other problems, please check the partitions with the all-partitions scanner or the dd method (see forest1971)

The emmc brick usually affects partitions been written to, in your case it starts at the /system partition:

name start size start size end
----------------------------------------------------------------------
1 GANG 0 + 0 blocks 0 + 0 = 0 MB
2 BOOT 0 + 0 blocks 0 + 0 = 0 MB

unused 0 + 8192 blocks 0 + 4 = 4 MB

3 EFS 8192 + 40960 blocks 4 + 21 = 25 MB
4 SBL1 49152 + 2560 blocks 25 + 1 = 26 MB

unused 51712 + 1536 blocks 26 + 1 = 27 MB

5 SBL2 53248 + 2560 blocks 27 + 1 = 29 MB

unused 55808 + 1536 blocks 29 + 1 = 29 MB

6 PARAM 57344 + 16384 blocks 29 + 8 = 38 MB
7 KERNEL 73728 + 16384 blocks 38 + 8 = 46 MB
8 RECOVERY 90112 + 16384 blocks 46 + 8 = 55 MB
9 CACHE 106496 + 409600 blocks 55 + 210 = 264 MB
10 MODEM 516096 + 32768 blocks 264 + 17 = 281 MB
11 FACTORYFS 548864 + 1572864 blocks 281 + 805 = 1086 MB
12 DATAFS 2121728 + 27582464 blocks 1086 + 14122 = 15209 MB
13 HIDDEN 29704192 + 1048576 blocks 15209 + 537 = 15745 MB
14 FOTA 30752768 + 16384 blocks 15745 + 8 = 15754 MB
15 0 + 0 blocks 0 + 0 = 0 MB

The gap in the partition table that should cover the brick area can only start at a partition start, so 1086 MB is FACTORYFS and next lower is MODEM at 281MB. I can create such PITs, but you then have to do an additional step and flash the MODEM partition from Odin.

I am not sure if I should release these PITs for everyone, because the MODEM partition is an additional problem for unexperienced users.

Fortunately it's not a very big problem.
[Galaxy Note GT-N7000 General] hg42:
N7000_16GB_Q1_20110914--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB.pit

should work (from what I remember you have a n7000 16GB, right?).

because of these relations: 281MB < 750MB and 2145MB < 2160MB

which means the gap from 281MB to 2160MB completely includes the brick area from 750MB to 2145MB (or in other words the brick is between 281MB and 2160MB).
[Galaxy Note GT-N7000 General] hg42:
sorry, I think I forgot to answer this...

look at this stock pit:

name start size start size end
----------------------------------------------------------------------
1 GANG 0 + 0 blocks 0 + 0 = 0 MB
2 BOOT 0 + 0 blocks 0 + 0 = 0 MB

unused 0 + 8192 blocks 0 + 4 = 4 MB

3 EFS 8192 + 40960 blocks 4 + 21 = 25 MB
4 SBL1 49152 + 2560 blocks 25 + 1 = 26 MB

unused 51712 + 1536 blocks 26 + 1 = 27 MB

5 SBL2 53248 + 2560 blocks 27 + 1 = 29 MB

unused 55808 + 1536 blocks 29 + 1 = 29 MB

6 PARAM 57344 + 16384 blocks 29 + 8 = 38 MB
7 KERNEL 73728 + 16384 blocks 38 + 8 = 46 MB
8 RECOVERY 90112 + 16384 blocks 46 + 8 = 55 MB
9 CACHE 106496 + 409600 blocks 55 + 210 = 264 MB
10 MODEM 516096 + 32768 blocks 264 + 17 = 281 MB
11 FACTORYFS 548864 + 1744896 blocks 281 + 893 = 1174 MB
12 DATAFS 2293760 + 4194304 blocks 1174 + 2147 = 3322 MB
13 UMS 6488064 + 23232512 blocks 3322 + 11895 = 15217 MB
14 HIDDEN 29720576 + 1048576 blocks 15217 + 537 = 15754 MB
15 0 + 0 blocks 0 + 0 = 0 MB

so 34-36MB is in the PARAM partition. I can create such pits, but using it, you need to restore the contents of PARAM, KERNEL, RECOVERY, CACHE, MODEM, FACTORYFS, DATAFS and UMS.

CACHE, DATAFS and UMS can be formatted (empty partition is ok).

KERNEL, RECOVERY and FACTORYFS will be restored by installing the ROM.

MODEM can also be flashed via Odin from publicly available files.

PARAM is the only one I never touched.

It probably only contains some images for the boot process, so it seems to be uncritical.

But, because they are used in the boot process (also download mode?) errors may prevent the device from booting, which is indeed very critical.

Does anyone have any experience with damaged or empty PARAM partitions?

From another phone I found this description:

which could (at least in parts) apply to our phones, too.

So we have to face hidden structures in the partition (so restoring all files may not be sufficient).

with adb we can create an image like this (untested):

dd if=/dev/block/mmcblk0p6 of=/sdcard/PARAM.img

but this cannot be handled in download mode.

The only stock (developer) ROM with 6 parts I know of is XXKL8, which contains these files:

CODE_N7000XXKL8_CL840182_REV02_user_low_ship.tar.md5

EFS_N7000XXKL8_CL840182_REV02_user_low_ship.tar.md5

GT-N7000-MULTI-CSC-OXAKL8.tar.md5

KERNEL_N7000XXKL8_CL840182_REV02_eng_mid_noship.tar.md5

MODEM_N7000XXKL8_REV_05_CL1089796.tar.md5

UMS_N7000XXKL8_CL840182_REV02_user_low_ship_16GB.tar.md5

unfortunately there's no PARAM included.
[Galaxy Note GT-N7000 General] hg42:
In a german forum I read that someone cleared a PARAM partition for an Galaxy S Plus by writing zeros via dd command to stop a recovery boot loop. So it may be possible...BUT...
[Galaxy Note GT-N7000 General] mpt123:
PIT File

Thanks, i tried using this PIT file but its the same response( freezes again and again).

Infact i tried using PIT files of gap ranging from ......

281---2160 to 281-- 7260 PIT files and the result was same.

At the moment iam using 281----7528 PIT file .Now my GNOTE freezes less but occuring sometimes.

Yes iam using GT N 7000 16GB with the leaked JB version.

(iam flashing the Pit file with GB deodexed rom through ODIN and then full wipe( data/factory,cache,dalvik)and format system and then installing JB leaked version through CWMR, is it right?)

Is there any way to find the exact block or to block that particular brick area.

Please help.

Thnx.
[Galaxy Note GT-N7000 General] hg42:
you might have an ever moving brick or it's still not stabilized.

You can check the partitions with my all-partitions scanner or by using dd in adb (see forst1971's thread).

Eventually you may use an even higher brick end and swap internal and external sd?

looks ok, however I would feel bad still having a dangerous kernel on my device. Everyone makes mistakes meaning you live on risk all the time.

I think, with my find-brick scanner you get near enough. A more exact scan would involve rebooting after each found block, which would be extremely time consuming (especially because you have to do all the rebooting manually).
[Galaxy Note GT-N7000 General] mpt123:
EMMC SCAN

Thanks a lot. Well noted.

Iam grateful for your kind help.

I will try your emmc scanner method and let you know.

By the way just one doubt about the memory swap. Is it possible with GT N 7000 .If so please advise where i can get

the memory swap procedure details.
[Galaxy Note GT-N7000 General] hg42:
sorry, I read this somewhere, but wasn't interested, so I didn't bookmark it.

Some try to increase /data size and use external sd instead of internal.

CyanogenMod 10 and derived ROMS (like Parandroid) are also able to swap internal and external.

That's why I don't need such a (script based) solution.
[Galaxy Note GT-N7000 General] hg42:
searching for e.g. "n7000 swap sd" finds several posts for n7000, so you only have to read...
[Galaxy Note GT-N7000 General] hg42:
I attached two experimental zips to the first post. They both contain PITs which move lower partition numbers (e.g. MODEM or PARAM!), so you have to know how to restore them (see latest discussion).

DON'T USE THEM, IF YOU DON'T COMPLETELY UNDERSTAND WHAT YOU ARE DOING

and of course NO GUARANTY FOR ANYTHING

if you are crazy/knowledgable enough, please report your experiences here.

good luck!
[Galaxy Note GT-N7000 General] hirurg:
I have a problem with the wipe / data. phone worked well, I want to change the custom rom. I do wipe and there are very long. Remove the battery .. and do not flash official rom using odin. I work using your program start brick and brick end. Start brick fit to 23MB. Is there any help that the phone is working properly?

remark

phone has been great, copy and painting a good row to the internal memory, there was no problem
[Galaxy Note GT-N7000 General] hg42:
sorry, your information is incomplete...start is at 23MB and where's the end of the brick?

If I understand correctly, you think you have an emmc brick, but the phone is working correctly, right?

Generally the brick is only noticed if you access the bricked area.

According to the partition table (see some of the latest posts or the stock .pit.txt file in the zip), 23MB is in the EFS partition.

Probably, this is not used all the time, but only in some occasions, I think when using the phone and bluetooth etc.

So, do you already have a backup of your EFS partition?

Anyways, I would do an additional backup of the current partition contents now. There are several apps for this and also methods via adb or in a terminal.

Generally, there are two kinds of efs backup, one uses a byte wise partition image, the other uses a file copy (e.g. in a tar file).

The image backup will freeze, if you have a bricked block in the partition. A file backup will only freeze if any of the files covers a bricked block. So, if the image backup freezes but the file backup doesn't, this would tell you, that none of the files in the efs partition is affected. Then you are (partly) lucky because you should then have a working backup of the efs partition.

You should also try the eMMC Brickbug Check - Android Apps on Google Play to obtain a second opinion about the existence of the brick.
[Galaxy Note GT-N7000 General] hirurg:
hi

ok i fixed with the methods you have written, i m interested in one thing, to come up with this fault what is the cause? permanent flash? or some other reason...i was totally incomprehensible...
[Galaxy Note GT-N7000 General] hg42:
from what I know, it's a bug in the wear leveler of the emmc chip firmware.

Probably the administration structures get corrupted.

The structures can be cleared, but then the chip is totally empty, so jtag would be required to restore the boot partitions.

Samsung seems to have a tool to reset the chip, but doesn't publish it, because it doesn't make sense for end users.

They also seem to think the bug doesn't effect users using only Samsung software and therefore don't work around it in their ROMs.
[Galaxy Note GT-N7000 General] hirurg:
do you want to say that this could be arranged in such a way that all the contours and then jtag? or no hope for us for this repair? I have a feeling that this is more spread by memory. Am I right?
[Galaxy Note GT-N7000 General] harry_fine:
Hello hg42

Amazing job you have done here with this post. I'm hoping you can help me.

I have a Galaxy Tab P7300. Not on your list. Like to give you a pit file with start-bad and end-bad sectors, but I'm a bit confused about how to scan. I'm moderately geeky, with a bit of Linux knowledge.

Reason I'm confused or helpless here is two-fold.

First, I can't get a root command prompt from adb, only get the $. I try adb root, and it says:

- exec '/system/bin/sh' failed: No such file or directory (2) -

Second, I've downloaded your scan pseudo-zip files, but how can I run them from CWM, when CWM can't see the data directory since the /data partition is corrupt? If I go adb push scriptname /sdcard, it won't copy as the sdcard partition is junked. I suppose I could go adb push scriptname /system, but I don't think I can run a zip from CWM in the system partition.

Any tips? BY THE WAY, I would be willing to pay you a fee of $50 if you could get me through this with at least 1/2 of my space free on the data partition.

Thanks

Harry
[Galaxy Note GT-N7000 General] hg42:
then your system partition may be unmounted. Try to mount it in cwm. Or may be it can't because it is also bricked.

yes, this is a little bit difficult.

Try if you can mount one of the partitions or the external sd.

Then push the file to it.

Or you may flash a pit with a bigger hole first and optimize your space afterwards. Most bricks seem to need a gap of at least 2-3gb, I would try around 6gb first, hopefully you are able to install a ROM and use all partitions. Then you may scan for the brick and choose a better pit.
[Galaxy Note GT-N7000 General] hg42:
Ok, I forgot this for a moment, please attach your stock pit, I have to take a look, if it can be patched. I don't need the brick position for that, because I generate a bunch of files for most situations.
[Galaxy Note GT-N7000 General] okrup:
ntailDo 28St

SO.. What do you suggest? the phone is not working so good, a lot of freezes and problems... not a lot to lose...
[Galaxy Note GT-N7000 General] hg42:
I think I said it already...

Are you able to use adb?

Then first try (all as super user = su):

dd if=/dev/block/mmcblk0p4 of=/sdcard/PARAM.img

then try:

tar cvf /sdcard/PARAM.tar /mnt/.lfs

This will tell us something about the state of the partition.

Unfortunately I currently don't know how to make an Odin image from a partition image or a tar file.

And because I don't have a windows available, I am also unsure if the param partition can be flashed via Odin at all.