yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] hg42:
there's absolutely no reason, why a shifted partition scheme like in the PIT should make the phone laggy.

The alignment of the partitions (that is, if their start is divisible by a certain block size) could have a slight effect on speed, but the scheme is choosen in a way that partition boundaries should be good (because the FACTORY_FS starts exactly where the former UMS started before).

You probably have not recreated all three partitions.

Generally, after flashing one or two partitions via Odin, I would format the others in the recovery. At least the /data partition should be formatted or wiped.

Also wipe cache and dalvik.
[Galaxy Note GT-N7000 General] hg42:
I can't imagine a reason for that.

I would reboot into a capable recovery and start adb and then check my partitions:

/system:

e2fsck -c /dev/block/mmcblk0p9

/data:

e2fsck -c /dev/block/mmcblk0p10

UMS:

e2fsck -c /dev/block/mmcblk0p11

if this hangs somewhere you may have bad sectors in that partitions, too, which probably means your UMS partition was also affected by the brick.
[Galaxy Note GT-N7000 General] hg42:
Ok, I told this several times, but now I documented this behavior in my scanner threads (wasn't aware it was missing).

So, please read the blue titled section about slow performance in the first post of my scanner thread for a complete answer.

In short: the slow down is the result of hitting a bricked block.

Note the numbers when the slow down begins.
[Galaxy Note GT-N7000 General] shoey63:
How come the scanner doesn't simply freeze when it runs into bricked blocks? I thought superbricked areas could not be accessed.
[Galaxy Note GT-N7000 General] Pajorve:
hg42 ... Thank you very much for your tip response ...Friend you see what I have here:

Did the file flash: emmc_scan_all_partitions_infinitely and got the following message:

/dev/block/mcblk0p1/

scanned 19 MIB = 20 MB completed -----> OK

/dev/block/mmcblk0p10

Champion does that mean something?

I believe I'm on the right path to take my Note of brick.

Sorry but how should I proceed now?

could tell me?

Really thank you very much to you my friend ....

Hugs and peace!
[Galaxy Note GT-N7000 General] hg42:
They are inaccessible, but how the OS reacts is different.

I assume we get a freeze, if the OS waits for a reaction without timeouts. If the operation is guarded by a timeout then we get a slowdown.
[Galaxy Note GT-N7000 General] hg42:
Partition 1 is ok (efs), but partition 10 freezes, so you probably have a brick there.

You probably need to pull the battery, to restart the device.

Then use the 'find brick' scanners to determine start and end of the brick, then follow instructions in the first post.
[Galaxy Note GT-N7000 General] Pajorve:
Thanks again ....I'm starting to understand better the problem!

You see, I made the file flash: emmc_find_brick_start and as I said before just above I could not see where it starts this brick and where it ends to determine which blocks are in trouble.

Please, I must apply the emmc_find_brick_start file/emmc_find_brick_end, correct?

but at what point will I know which blocks are in trouble and how should I note them as applied emmc_find_brick_start and not getting any results for hours? This is my biggest doubt really! When knowing that the procedure worked and when jotting down these numbers?

I need only this information to solve my problem!

really thanks for the great help
[Galaxy Note GT-N7000 General] hg42:
You use find_brick_start to find the start of the brick and find_brick_end to find the end :)

Each will freeze or slow down significantly when it hits a bricked block.

You detect a freeze only by seeing the output numbers not changing anymore.

Reading your post, it seems you don't get *any* output from the find_brick_start scanner? No numbers on the screen? No output which device file will be scanned (e.g. mmcblk0)

It should first write a block number and *then* access the corresponding block. So it should write a line with a zero first.

The freeze can only occur after writing the line with the number.

Do you use the same recovery for all scanners? There seem to be recoveries (stock?) where you cannot see any output. But your scan of all partitions was able to output lines.
[Galaxy Note GT-N7000 General] Pajorve:
Friend you see happens:

Actually by making emmc_find_brick_start flash it scans and is very slow after some time ...

Tell how long it takes to get the result, I'm sure well unless 7:0 ... ehehehehhe.

I'll do the flash again and check when it begins to slow down and write down the numbers ...Use the same recovery always .... downloaded from another thread.

Thank you for your support and let's get talking.

Your help is being of great validity to me!

Thank you!
[Galaxy Note GT-N7000 General] badmaash:
I think the last time I couldn't explain you what the issue is. The deal is my N7000 16 GB was bricked and using your tools i installed a ROM and phone started working fine. I lost the 4 GB as you had mentioned and now my internal memory reads 8.24 GB. I have frequent freeze on my phone and I have used your PARTITION SCANNER which does not hang anywhere and gives me all clear results. I also scanned using emmc_scan_all_partitions_indefinitely.zip and it does not hang anywhere. I have reinstalled many different ROMS to see if the issue is ROM related or phone related. The problem persists across all ROMS and so I think there is something else wrong with the EMMC. My phone is under warranty. I want to flash my phone back to bricked mode with full 12 GB partition table as set on default by samsung. If i flash using odin and stock PIT for 16GB will I encounter any new issues or my phone will be reset to factory partition but also in bricked state.

I understand my phone will be bricked if I reset to factory settings. I just wish to take the phone to Samsung center and tell them the phone does not boot up and have to not give any explanation.

Please guide me which PIT to use to get back to system default and safely.

Thank you so much for your effort and time.

I appreciate.

Will donate.

Thank you.

Regards,

Aishwarya Jain
[Galaxy Note GT-N7000 General] travis82:
The original 16gb pit file...:rolleyes: Search you will find it.
[Galaxy Note GT-N7000 General] badmaash:
Thanks friend. I'll look in the forums. Just to confirm once more, my phone will be back to original partition table and as emmc is bricked my phone will also be bricked with only Samsung logo appearing without successful boot.
[Galaxy Note GT-N7000 General] hg42:
that's the way to go.

Note, I cannot change this behavior, because it's a very lowlevel thing (hardware or drivers), so I have no chance in my scanners to fix this.
[Galaxy Note GT-N7000 General] hg42:
1. the stock pit (from which I calculate all the patched pits) is also included in the zip for your device (using a *-stock.pit name)

2. if you flash the stock pit you will not be able to install a ROM as the flash will probably freeze early in the process.

I think, the service center may find traces of custom ROMs etc. because the flash usually stops at the FACTORYFS.

3. a factory reset will fail at the bricked blocks possibly leaving data intact

What changes are made by custom ROMs?

* kernel/recovery

* factoryfs aka. /system

Which traces of custom ROMs may be detectable?

* custom ROM files etc. on internal sd

* ROM Manager and other files on /data (datafs partition)

* files on /cache (cache partition)

You could clear every block from start of the emmc up to the first bricked block by using dd command in adb (in recovery mode).

But it would be better to leave all partitions up to kernel/recovery intact, otherwise you cannot boot into recovery if something fails.

Clearing all bytes from just after the brick up to the end of the emmc may be difficult or impossible, because dd cannot start at high byte addresses due to limited number ranges, which was a problem I had to face in my scanners (I first tried to use dd for this).

It may be possible to create an additional "wiping" scanner, but I am a bit anxious of people completely clearing their devices because they don't read carefully enough. I'll think about that.
[Galaxy Note GT-N7000 General] badmaash:
Ok I have messed up things big time.

2 months back phone got emmc brick. As per your post I downloaded the pit files and patched with custom PITS you had created. Without understanding much, i took a random pit file and flashed. :eek: phone booted and i installed a ginger bread rom. later updated to ICS and started experiencing freeze. Now after spending 2 months on your posts i realize i did everything wrong.

now using your scanner my phone hangs at 2048 when starting from end to start as shown in the picture and phone reboots at 949 when scanning from start to end.

Currently my phone is working and I have Jelly Bean Rocket ROM installed with Philz Kernel. I am experiencing great number of freeze.

Can i repartition correctly now?

If yes which file to use exactly from the list of your patched pit. :confused:

Ok couldn't wait so i read the post 10 times to understand what you meant.

I flashed with N7000_16GB_Q1_20110914--patched--brick-between-00281-and-02160-MB--FACTORYFS-moved-by-01792-MiB.pit and phone has rebooted. I am at the welcome screen right now and will go ahead and check...

now my phone says 9.33 GB of internal storage as prior to 8.24 GB.

Whoa man..i so wish my phone stops freezing i don't need the lost 3 GB space.

Will go ahead and do brick scanner and report.

Thank you so much sir..
[Galaxy Note GT-N7000 General] Pajorve:
Hi friend, all right, I have good news!

I managed to get the numbers needed to have exactly the pit to be flash.

Using the find_brick_start file I got these numbers: 22 MIB = 24 MB (FREEZES at THIS VERY MOMENT) and with the brick and find_brick_end: 3391 MIB = 3556 MB (FREEZES at THIS VERY MOMENT)

Could you tell me what the PIT to be flash .... because there are so many in the folder that I am really confused and do not want to flash a wrong file.

Thank you very much your help is great!
[Galaxy Note GT-N7000 General] hg42:
Please reread the thread starter until you understand how the pits are named.

In your case I think you will not find a working pit in the zip for your device because your brick starts at the very beginning of the emmc.

I have an experimental package for n7000, which starts at lower partitions, but you have to understand exactly what you have to do.

I hope I can look at this more exactly later today, to find out which options you may have.

Please tell us, how you got this brick.

Did you touch (= write to) any of these critical partitions at the start of the emmc memory when using a stock ics or jb kernel?

E.g., did you flash the boot loader/efs or something like that via recovery?
[Galaxy Note GT-N7000 General] badmaash:
I got the brick when I erased and wiped from recovery. now after this flash I am getting freeze more frequent. also when I scan all partition from start to end my phone reboots at 850 block. I also noticed the restart ofthe phone is not at a particular block it happens sometimes in 850+ series sometimes around 930 series but not above 1000 doesnt go that far the phone reboots before that.
[Galaxy Note GT-N7000 General] hg42:
Your brick may still be unstable.

Hopefully it stabilizes at a better start block.

The stabilization is usually triggered by writes to the emmc, so it may be better to start with a preliminary pit to start using the phone.

At this point, I would probably use a patched pit starting at the factoryfs and an end block after your brick end while ignoring the start block for now.

Just keep in mind, the phone may freeze from time to time, so don't store anything important on it.

Instead try to stimulate the wear leveler algorithm.

Copy many big files to the emmc (which you also have at a second place like on the pc), e.g. music files.

Throw them away, copy again and so on.

In short: write often to the emmc memory to trigger the emmc wear leveler. This may stabilize the brick.

In between use the find_brick scanners to see how it moves around.

Write down

* the actions (amount of writes in MB) and

* brick start/end numbers and also

* any freeze

chronologically.

Please post this list here after some days of treating your phone like this, so we can try to find patterns.

Note, we are still researching the emmc brick behavior.
[Galaxy Note GT-N7000 General] Pajorve:
Hello friend ... first of all thanks for the help and patience!

I had my brick in the Note When I went to flash a custom rom.

My appliance was stock with original rom operator Vivo Brazil (im from Brazil)

First of all did the "temporary" flash of CWM Philz's and then when going to make flash the rom when you click Go Back to go to the rom zip simply did not return, froze and the CWM of Philz had the stock Android recovery screen and in the last line of the stock recovery fired a growing number counter ...

As it was, and after a long time waiting for those numbers stop climbing I pulled out the battery and then had the certainty of brick ...

It was like I had my Note brick and searching here I found your thread.

My rom was stock and the kernel was also stock and I was using ICS 4.0.3

This was the situation of my Note before him have that brick.

Just one more question: would it be possible to really make a Pit in the dimensions that I spent? I know that you already looking to my problem and I am really thankful to you for this ¹

Thank you!
[Galaxy Note GT-N7000 General] hg42:
Did you check the start of the brick for another time?

May be the brick already moved away from these lower block numbers?

Otherwise I got these results thinking about the problem:

The first partition (=EFS) starts at 25MB.

The area which has to be moved would include all real partitions in the table and includes the two boot loader partitions sbl1 and sbl2.

I think this cannot be done with the pit method.

You probably will be unable to boot after flashing the pit and as a result you will be unable to restore any of these critical partitions.

I would try to use forest1971's method to move all the partitions after the brick.

In this case it's like voodoo, definitely a work for real experts.

Very risky...

You will have to move the partitions including their contents in one go, because you cannot boot until finished. The move should be partition wise starting at the last partition.
[Galaxy Note GT-N7000 General] Pajorve:
Hello... okay?

Yes, I did start file flash again and gave the same number.

Tell Me What happens if I make the flash of that first PIT file?

I was reading the thread to which you referred and really is something much more complicated

Do you see any problem in doing smaller existing PIT flash?What can cause this?

Thank you!
[Galaxy Note GT-N7000 General] BABAK236:
Hi Dear

---

Can i ask for create new pit file for i9100G....??? for 8GB eMMC...?

--

Actually i have a i9100g-8GB

i did try with create and resize with adb,and try for create pit file,but not done....

----------------------------------------------

Thanks

Edit: Odin hang on "HIDDEN" when writing(Used stock pit)
[Galaxy Note GT-N7000 General] hg42:
I could create a pit starting at the first partition, but I think you would not be able to boot after flashing that pit, because the bootloaders and kernel would be invalidated. Because we don't know how to create flash images for all these partitions for odin, this is not the way to go.

With adb and parted (forest1971's way) it may be possible to move partitions including data (or otherwise save them, move them, restore them one by one).

Then you could first shrink the ums partition, then move datafs, then factoryfs, etc. and last efs. And you have to handle each bricked partition in a different way (delete, create, format) because you cannot access their contents.

Probably nobody has never done this before.

But, ... the fact that you can boot into recovery makes me wonder if a conventional patched pit could also work.

The brick doesn't seem to prevent booting, so these boot and kernel partitions seem to be clean.

Please try a PIT starting at factoryfs and with an end number after your brick.

This may work.

If you are unlucky only the efs has got the brick (and system and/or data). Then you can boot, but not use the phone as usual because the efs contains some data used for cell phone, bluetooth etc.
[Galaxy Note GT-N7000 General] hg42:
Will look at this today, hopefully
[Galaxy Note GT-N7000 General] hg42:
I created pits for your device (attached to first post)...

now, after uploading it, I see your brick is in HIDDEN?

Are you sure?

This case is not handled by those pits.

But is your brick really located in HIDDEN? would be very unusual...

Please use the find_brick scanners first to determine start and end of the brick, then use a correct pit (see first post).

However, if your brick is really outside of the usual range, please report here. Then I would have to extend my pit generator.
[Galaxy Note GT-N7000 General] r0b3rtm:
I'm not an expert and would was hoping I could get some pointers. I have an SGSII Epic Touch 4G that is bricked with this EMMC lockup, and I'm trying to follow the instructions to recover from it using this PIT file method.

I've downloaded the find_brick_start.zip and find_brick_end.zip, but I don't have any way to flash these onto the phone. All I have is Odin, and I believe I need CWM or similar. I've tried to put the zip files onto the root of my SD card, but I don't get any option to install them when I enter recovery (it says ODIN MODE at the top).

I've used CWM on another phone in the past, but it was put onto that phone when I rooted it.

I've been reading for hours and my brain is spinning, so I would really appreciate any help I could get.

I assume that once I've been able to do the 'phase "find brick"', then I should be able to flash an appropriate pit file with a new ROM, thus get my phone unbricked (I already have a clean ROM downloaded and have downloaded the zip for the ET4G that has all the pit files).

PS. I first rooted my phone using one-click odin and retain data (latest FI27 stock image rooted), that worked fine, but since my unwanted freezes and reboots didn't get cured, I tried the same using NoData root in an attempt to get a clean stock ICS ROM, and that is when my phone bricked (it got stuck at Data.img).

UPDATE: Please disregard my inquiry, it seems I didn't have an EMMC brick after all.
[Galaxy Note GT-N7000 General] BABAK236:
Hi

Thank you...

I'll Test Uploaded .Pit One By One For See Which Pit Can Help And Solve .....(Report very Soon)

-----------------------------------------------------------------------------------------------

i Think i need some explain about my problem...

Actually Samsung made i9100g with 16gb-eMMC.....attached .pit it is too

My phone dead suddenly,so after try for all possible method for repair,no luck

So,i had replace eMMC(i am technicians)..but i can't find 16GB-eMMC,,,So,i use 8gb chip...

Then,i did repair phone with new chip....phone turn on and i can flash via odin

--

So,This is exactly my problem:

when i use 3 parts firmware in odin,...stuck at "hidden"

When i use 1 package firmware,with org .pit.,,,odin can done flashing and phone can turn on but "i don't have Mass storage" also "efs" is damage....

--------------------

So,Let me check all maked pit...(But i think i need only one pit with created standard address for 8gb eMMC)

Thanks

---------------

Edit: Can you make 3 new pit with have only 4gb as mass storage(in factoryfs, in datafs, in UMS)

Edit2: after flash phone with this pit,mass storage back and i can mount by pc(but this is 2.86MB and have o as free space)

Edit3: i have 1.25GB as mass storage after use this pit:

i9100g_8GB_omap4_all_20110627_emmc--patched--brick-between-04747-and-15216-MB--UMS-shortened-by-09984-MiB.pit
[Galaxy Note GT-N7000 General] hg42:
oh, then my patched pits are for 16gb, too.

I didn't look at the sizes.

nice...

ok, so this means, the "hidden" partition is outside of your physical emmc?

Odin would also complain at UMS, but usually doesn't include this (there is a 6 part package for N7000, which includes UMS).

I assume efs has no contents...because your emmc is virgin.

I'll see if I can create cropped 8gb pits...

btw. why did you ask for 4gb pits?
[Galaxy Note GT-N7000 General] hg42:
So finally I created a package for your special 8GB device, please download again (same file name)
[Galaxy Note GT-N7000 General] BABAK236:
Hi

ok,i'll download and report

But,I think This address shulde be work....can you make ? Because i think Just need repartition new 8gb-eMMC with correct size and format(file system)...it's same way by stock 16gb-pit file,,,,just need edit for 8gb

1 x-loader
2 ...
3 ...
4 ...
5 ...
6 ...
7 ...
8 ...
9 ...
10 FACTORYFS 180 + 1074 = 1254
11 DATAFS 1254 + 2147 = 3404
12 UMS 3401 + 3500 = 6901
13 HIDDEN 6901 + 537 = 7438
14 GANG

-------------------

i see in normal I9100(not G) :

Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 159MB 105MB ext4 CACHE
8 159MB 176MB 16.8MB MODEM
9 176MB 713MB 537MB ext4 FACTORYFS
10 713MB 2861MB 2147MB ext4 DATAFS
11 2861MB 15.2GB 12.4GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN

----------------------------------------------------------------------------------------------------

So,Maybe needed make partition format file system same as I9100 for i9100g?
[Galaxy Note GT-N7000 General] BABAK236:
Hi Again

For First,Thanks You.....................

----------------------------

All Pit file(2nd-Gen) work......but only with 1package firmware......with 3parts,Always stuck at "HIDDEN"

---------------------------------------------

So,For now,I have 4.08GB-Mass_Storage and 1.9GB as Internall Memory

---

Anyway,Exactly problem for now is "EFS" Partition.......i don't have "IMEI" also "Unknown BaseBand"

I did check "efs" folder by root-explorer and i see all file is there and i think is fine.....So,I Think this problem come from file-system....Maybe need create "efs" partition with "ext4"

B.R
[Galaxy Note GT-N7000 General] hg42:
They have some differences.

Use the "stock" pit in the zip, it's the 16gb file patched for 8gb with same partition sizes and sequence (except UMS).

UMS was shrunk, and HIDDEN was moved.
[Galaxy Note GT-N7000 General] obioan:
Hello,

I'm trying to solve my problem:

- after running for almost an year on original ROM (I9100BVLPD), I decided to try some new custom roms.

- OMEGA rom was first on my list.

What I did (stupid, I know) :

Saved a backup of my curent ROM with CWM and then tried to install directly the OMEGA rom but with no success. After several wipe data factory resets and cashes I got the fantastic idea to install a new original ROM, I9100BVLPH.

After installing that ROM, the phone booted ok. Entered in recovery mod, installed from zip CWN 4 or 5 *i have them both), booted in CWM 4 or 5 and installed the zip ROM from OMEGA. Everything nice and smooth. ROM booted and I was able to play with it.

But wait, I wasn't happy with the ROM, I wanted AOKP version from OMEGA. I entered in CWM v6 from omega ROM and made a backup. After that I did a full wipe and a cache wipe and tried to install AOKP version. After that I couldn't boot in the system.

Now I'm stuck at boot and can't do full wipe from CWM or recovery. No matter what original FW I install I cant do a full wipe. From what I know, I dont seem to have the emcc bug ( I ran an aplication from market that scanned the device for faulty chips and turned up ok).

Do I need to try some other solution or I'm lost and must do a repartition?

I really need to stop getting myself into trouble.... :(

Thanks.