yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] hg42:
(note I usually don't read the thread any more, because I have a note3 now)

41 MB means starting the gap at the KERNEL partition beginning at 37MB.

This should work well, but the pit is in experimental because:

- I don't have any feedback if this works well and which problems may appear

- you have to format the CACHE partition to get it up and running

formatting CACHE shouldn't be a big problem, you only need a custom recovery for that.

So after applying the pit, you flash CACHE and UMS.

btw.

everything below 29MB should be nearly impossible to fix (boot loaders affected).

below 37MB could work but I don't know anything about the affected PARAM partition and how to restore it.

From what I remember there is not much data in it.

May be it's not critical, may be it's trivial to restore.

But at least *I* do *not* know.

There could be hidden data on it, or something like that.
[Galaxy Note GT-N7000 General] Stefan2142:
Is there a way to run this in download mode? Because I can't get into recovery on my i9100.

---------- Post added at 12:46 PM ---------- Previous post was at 12:35 PM ----------

Is there a way to use this in download mode? because I can't enter recovery mode nor I can flash it in odin or heimdall. I can't flash zImage, cache.img, factoryfs.img, hidden.img, modem.bin, sbl.bin. The only files I can flash via Heimdall are boot.bin and param.lfs.
[Galaxy Note GT-N7000 General] hg42:
should be obvious, if you really read the first post...or think a little bit about how a pit file could be applied, right?
[Galaxy Note GT-N7000 General] Stefan2142:
Pardon me, I am up for 20+ hours here trying to find a solution. I know that what I meant is: Is there a way to find out do I realy have bad sectors with only download mode available?
[Galaxy Note GT-N7000 General] hg42:
ok...sorry

So, perhaps you should sleep some hours, because you need full concentration for this kind of procedures... :)

Generally, if you cannot use a recovery, you should try some pits with higher gap sizes to get your phone up and running (you may use one of the highest first to see if the phone boots), then install and use a custom recovery to scan.

Gap start should be below the start of the first partition that could not be flashed.

But...

I don't know much about sbl.

I think, this is a boot loader and will probably have a critical role in the boot process.

So it's a bit more difficult than the standard procedure (and I never tried this one).

The pits should allow you to move sbl out of the bricked zone.

But you have to restore the contents of sbl to be able to boot.

You said you tried to flash sbl so you seem to have the necessary file.

Remember: you have to restore all partitions, that are moved by the particular pit file.
[Galaxy Note GT-N7000 General] Stefan2142:
Yeah, I should probably get some sleep because I have made one more mistake. I said there that I can't flash sbl.bin file. Well I can, I made a mistake.

So, which one would you recommend me to try with..? Because there are 300+ files and I not too familiar with this method, so I don't know which file with the right gap should I use.

And one more thing. Should I try to flash only .pit file first or should I try to flash whole rom alltogether with .pit file in one command?
[Galaxy Note GT-N7000 General] Stefan2142:
Doesn't even matter Odin won't even flash .pit file
[Galaxy Note GT-N7000 General] hg42:
oh, wow, I never heard of such a situation.

You first mentioned Heimdall and now Odin, so you really used Odin now?

I have mixed experiences with Heimdall, so I would recommend Odin.

Are you sure Odin works generally? you could eventually have driver problems.

There may be other reasons for a non working Odin.

As I said, you have to restore (at least the critical) partitions, before you reboot.

All that has to be done via Odin or Heimdall, if you don't have a working custom recovery.

You should definitely read (and understand) my thread starter before you try to flash a pit.

I generally assume you are familiar with these tools (Odin etc.). Otherwise read more in other threads.

There are definitely too many possible situations, which I cannot cover in this thread.

What is the history of your brick? Did you really use an ICS-kernel?

I'm asking because the emmc brick only occurs in some combinations of software.

Newer software shouldn't trigger this bug.

Without having used an ICS-kernel you would probably have a very different problem.
[Galaxy Note GT-N7000 General] Stefan2142:
Okay, this is history of my problem. Four days ago everything started. Just to say all root apps I had were installed back in July when I installed CM11 M8 with cwm 6.0.5.0(previously coming from Siyah kernel and stock JB 4.1.2), so a root app couldn't trigger this problem. The most recent app I have installed was Checky and that was done nearly two weeks ago.

Ok, now to the problem. Four days ago I took my phone to check for new msgs/notifications and stuff like that and it wouldn't start. I realized that it was powerd off. No bih deal it happened before on thiis rom and even on official JB rom. I tried to turn it on but I faced a bootloop (6-7 months ago I think) so I knew what to do to get out of it. I went to recovery mode and tried to make backup of whole rom but that was the point everything started to go downhill. While doing backup cwm reported an error "couldn't backup /data" (maybe it said couldn't mount /data, I forgot but I can check if it seems important). I tried a couple of times without look. Then(this was a foolish move) I tried to reflash cwm recovery via Odin. Odin got stuck after doing "NAND write start" and after few minutes it showed "Complete(write) operation failed. I was shocked, because I have used Odin many times on this machine and with this phone and that never happened. I tried again-nothing. I rebooted the phone and tried to go into recovery but it was gone. Again, a shocking moment.

Then I tried falshing all kinds of roms/modem/csc/pit files via Odin but nothing. Every attempt resulted in the same error. I even tried flashing only .pit file(with repartition checked) but still, the same error occured.

I learned then about Heimdall and decided to give it a shot. I tried flashing file by file and I had some success. Some files could be flashed and some couldn't. This is the files that I managed to flash: boot.bin; param.lfs; sbl1.bin(taken from a stock GB and JB roms). All other couldn't. Heimdall would go to 100% of uploading the file and then it would write(depending on the file I am flashing):

ERROR: Failed to confirm end of file transfer sequence!

ERROR: KERNEL upload failed!

Ending session...

ERROR: Failed to send end session packet!

Releasing device inteface...

This is it. I think that some of the partitions got somehow corrupted and that is the reason why they can't be flashed. Bootloader is not the problem since I am able to flash some files. I really don't have any idea on what to do next.
[Galaxy Note GT-N7000 General] hg42:
I'm currently on vacation, so please be patient.

From a quick glance I would say the PIT seems to be ok, only the "Unknown" entries look a bit weird, but may be this is normal.

Perhaps someone else can post his heimdall PIT print log to compare both?

I probably don't have access to my N7000 for several weeks.
[Galaxy Note GT-N7000 General] aryaputraz:
many thanks for you !!! :good:

now my samsung gtab p6200 can be used again !!!!

But, my galaxy tab always freezing. i tried cyanogen 10 and stock rom 4.1.2, this problem cannot fixed. its possible to repair this "freezing" problems??

*sorry for my bad english
[Galaxy Note GT-N7000 General] hg42:
you should probably try a custom recovery first, to be able to scan to determine the brick area

efs is only affected if you move starting at a partition below or equal to efs. Luckily efs is one of the first small partitions. So most bricks are somewhere after efs.

you need an efs backup and a way to restore it.

If you have an image of your efs you may flash it via recovery.

If you have a recovery with adb support, you may also restore tar backups created by some efs backup apps.

probably yes

cache is higher than recovery, so you may be able to flash a custom recovery. Then use my scanner.
[Galaxy Note GT-N7000 General] sNiXx1:
Thanks for the information, it seems a lot clearer now. However, I wasn't able to flash a recovery (I tried Siyah-s2-v5.0.1 and PhilZ-cwm6 v5.06.1), as it gets stuck at "NAND Write Start!!" again:

<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!

Can I use one of your pit-files to move everything after PARAM? It seems to me that at least two partitions are faulty.
[Galaxy Note GT-N7000 General] samironearth:
IT WORKED ON MY Galaxy TAB plus P6200 .... thank you so much ... it was bricked for a month and i had lost all hope .. even the SAMSUNG guys had no clue and said that the motherboard had to be replaced ... thank you thank you thank you :) thank you soo much hg42 .. you are my god
[Galaxy Note GT-N7000 General] hg42:
sorry, I cannot follow xda very often nowadays, so this may be a little late...

ok, like you already said, this looks like your KERNEL partition is damaged (the one after PARAM).

I can generate a package with more partitions for your device.

I currently have these i9100* devices in my script:

"i9100_16GB" => { start=>["FACTORYFS", "DATAFS", "UMS"], big=>"UMS" },
"i9100_32GB" => { start=>["FACTORYFS", "DATAFS", "UMS"], big=>"UMS" },
"i9100g_16GB" => { start=>["FACTORYFS", "DATAFS", "UMS"], big=>"UMS" },
"i9100_jb4.1_16GB" => { start=>["DATAFS", "FACTORYFS", "UMS"], big=>"UMS" },

which one do you need?

Additionally, which pit file is your stock pit?

The i9100_jb4.1_16GB uses this pit:

...partitions 1-5...
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 + 204800 blocks 55 + 105 = 159 MB
10 MODEM 311296 + 32768 blocks 159 + 17 = 176 MB
11 HIDDEN 344064 + 1048576 blocks 176 + 537 = 713 MB
12 DATAFS 1392640 + 4194304 blocks 713 + 2147 = 2861 MB
13 FACTORYFS 5586944 + 2097152 blocks 2861 + 1074 = 3934 MB
14 UMS 7684096 + 23085056 blocks 3934 + 11820 = 15754 MB

If you start moving at KERNEL you probably won't have much problems restoring the partitions 7-14:

7 KERNEL no prob
8 RECOVERY no prob
9 CACHE wipe
10 MODEM restore from backup or flash from modem file
11 HIDDEN most critical because contents is unknown (to me)
12 DATAFS wipe or restore from backup
13 FACTORYFS flash rom
14 UMS wipe or restore from backup

(note: as usual, I don't have much spare time, so please be patient)
[Galaxy Note GT-N7000 General] hg42:
and the last that could be flashed?
[Galaxy Note GT-N7000 General] sNiXx1:
...is the one I flashed first. After that I wasn't able to flash anymore. I was wondering whether it was due to "Factory Mode" instead of "Odin Mode" when using the JIG, but I was able to get into Odin mode again and that didn't change anything. I just recently successfully flashed CWM with another i9100 with the same setting.

As an additional remark: When flashing, Odin doesn't get past "Set PIT file"
[Galaxy Note GT-N7000 General] hg42:
so, if the first pit is identical to the one flashed last, the problem probably isn't a damaged/misconfigured pit.

I would assume

- either the emmc brick (if you really have one) extended to some crucial area (like where the pit is stored or something)

- or you have an unrelated prob with flashing pits.

Perhaps you can find other reports of not being able to flash a pit for this model or with odin?

Did you try the Samsung Kies Software to restore factory state? I think, sometimes it can solve such problems. At least it's worth trying.
[Galaxy Note GT-N7000 General] BListein:
Hi hg42, is there anyway that I complete turn off my internal sd and use only external sd card for boot/rom/storage everything. This would avoid the emmc brick bug completely no?
[Galaxy Note GT-N7000 General] :
There are ways to run your system from the external, but not entirely turn off internal storage. This would not prevent the brickbug. You prevent it by following the proper protocols.
[Galaxy Note GT-N7000 General] rajib_sharia:
Need urgent help

hi, im using samsung s3 GT-I9300 16GB. my phone was working and suddenly it stuck. so i take out my phone battery and put back again. since then when i open it shows just a white screen. i can go download mode ut o recovery mode. tried flashing with odin but it says no pit pertition. i got some pit for I9300 online and tried them but then it said repartition operation failed. please help me since im out of warrenty already. can i try custom pit? can u pls help me get a custom pit for I9300. thanks and hope to hear from u soon.
[Galaxy Note GT-N7000 General] garwynn:
This solution does not apply to the S3.
[Galaxy Note GT-N7000 General] hg42:
recently I got several questions according bricks of newer phones.

Please note that the emmc brick bug should be triggered only by a combination of a few conditions:

- an old samsung kernel (from ics)

- wiping or formatting by custom software, usually an old cwm of that time

- most important: an older emmc chip (or firmware)

after the problem was analyzed, all those parts were fixed to prevent the problem, even in case one or two of those conditions were true.

So if you have current hardware (somewhat newer than note1) or current software (newer than ics), the bug will not happen.

so, as an example, S3 should be safe, or Note 3 should be safe because both hardware and software are new enough.

Especially, all current roms or recoveries should be safe.

If you have a brick nowadays, it's very very unlikely to have an *emmc* brick. Instead you probably have some other problem.

So don't look here.

!!! Especially a patched PIT from this thread won't help you.!!!

You don't want to throw some memory away, right?

That is (in short) the method we use here to work around the hardware failure in some memory area. We just don't use it.
[Galaxy Note GT-N7000 General] grwalker:
Hi all

I am reading with interest (and partially understanding) this thread.

My note 2 is stuck on the "Firmware upgrade encountered and error..." screen I cannot get to recovery or download mode.

Will the methods discussed here sort my phone out? I have tried all sorts of flashing with ODIN using different ROMS. Also tried flashing the PIT file.

Always i end up with the following where things get stuck saying there is no PIT partition

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)

Thanks in advance
[Galaxy Note GT-N7000 General] :
No
[Galaxy Note GT-N7000 General] grwalker:
Thanks for the definite reply.
[Galaxy Note GT-N7000 General] RamHa:
yes
[Galaxy Note GT-N7000 General] :
Do not advise people to use the pit from here on a note 2. This is a n7000 thread.
[Galaxy Note GT-N7000 General] RamHa:
Yes , ofcorse, now U did explaine, thank You! :) i did press tnx butt ;)
[Galaxy Note GT-N7000 General] grwalker:
Hi

If yes, then how please?
[Galaxy Note GT-N7000 General] :
The answer is not yes, it is no. He is wrong. This would only potentially work if you had pit files for the n7100. Don't use n7000 pits on the n7100.
[Galaxy Note GT-N7000 General] alb3rto2005:
Enyone who can help me with an Samsung S6 32 Gb NEVERLOCKED pit file pls!!!
[Galaxy Note GT-N7000 General] :
This is the Xperia Z3 battery sellers forum. Wrong planet.
[Galaxy Note GT-N7000 General] yakapa40:
hello

for Samsung S6 you can take a lokk here :

http://xdaforums.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459

for S6 edge it's here:

http://xdaforums.com/galaxy-s6-edge/general/g925-pit-files-multi-thread-download-t3171636

regards
[Galaxy Note GT-N7000 General] Murshad007:
I have GT-I9100 32GB

and I am getting this error

"<ID:0/022> Initialzation..

<ID:0/022> Get PIT for mapping..

<ID:0/022> Firmware update start..

<ID:0/022> boot.bin

<ID:0/022> NAND Write Start!!

<ID:0/022> cache.img

<ID:0/022> Complete(Write) operation failed.

<ID:0/022> Added!!

<OSM> All threads completed. (succeed 0 / failed 1)"
[Galaxy Note GT-N7000 General] Murshad007:
after i flashed 12th pit my phone is totally dead now. its not turning on in normal yellow triangle mode or in Download mode now.. Not powering on at all. Thats All happens after i flashed the 12th patched pit...

Any further help ?
[Galaxy Note GT-N7000 General] :
Who told you it's safe to flash this file? You're in the N7000 forum, your phone is hard bricked already.
[Galaxy Note GT-N7000 General] Murshad007:
I flashed the Patched Pits from 1st post, of My model Gt-i9100
[Galaxy Note GT-N7000 General] User_99:
There are already files for 9100 and should be safe. But I think there is more damaged on your device...
[Galaxy Note GT-N7000 General] xkawer:
Will this help me if I can't repartition in Odin with the stock PIT (Re-Partition operation failed)?
[Galaxy Note GT-N7000 General] KuGeL94:
Hi I have a note 1 n7000 from a friend, lcd is black, digitizer is working, he said this happened 1 month after a software update.

I thought it would be a hardware failure, opened it, checked lcd flex cables, they seem ok.

I installed an old kies for the drivers, put it in download mode, odin has seen the device.

I flashed a stock firmware via odin, it worked but lcd still black.

Here's the flash procedure:

<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLSC_N7000ODDLSC_N7000DDLS6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003> zImage
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

Any ideas?
[Galaxy Note GT-N7000 General] hg42:
unfortunately no...

a patched PIT is only useful if you can flash it via Odin.

if you have access via adb or recovery, you might repartition by command line tools (see forest et. al.)

However, the failure flashing the PIT might point to a more severely damaged partition table. You would need JTAG then.

Also see Adam Outler for another at least theoretically possible way to unbrick via direct access to CPU via USB.
[Galaxy Note GT-N7000 General] Lunarlegends:
Hello, i got a super bricked n7000 16gb here with download mode access but no recovery menu. I just tried flashing the original Q1_20110914_16GB.pit successfully and afterwards stock jellybean but unfortunatly its still in endless bootloop mode. I think i have to use one of the pit files to lock a certain space of the memory where its bricked, but i dont know which pit file to pick, since i cant use the recovery with the emmc scanner, to find out where the brick is.

Is there a part where the brick occurs the most, im thinking of just going ahead and try the 281 MB up to 2428 MB pitfile. The brick occured when trying to flash stock jellybean on a previously installed omnirom kitkat firmware. Any help on this would be greatly appreciated to get my good old n7000 running again, thanks in advance.
[Galaxy Note GT-N7000 General] Lunarlegends:
I just tried flashing the costum pit files from forest1971's thread but none of the 6 worked for me with the blind flashing method without the recovery. They all flashed fine and there was the green android guy on the phones screen after pit repartition and stock firmware installation. It just doesnt boot all the way and still bootloops each and every start.
[Galaxy Note GT-N7000 General] RishiChhikkara:
could you help me modify this attached pit file for my note 4, i read everything, ran your emmc check tools, but no result, i even tried the other thread's methods which you have mentioned, but i couldn't find the bad partition, my device freezes every 10-15min, very badly, i know this is strange that i am not able to find the effected partition even after running everything, but i was thinking if relocating everything could help me, since note 4 has internal storage of 32gb, i don't mind losing 5-10gb, can you please modify this pit file in such a way that partitions start from 6th GB, as i can see right now everything is within 5GB including system.

Update- I tried to create a pit file of the same configuration, but Odin won't let me flash it, saying"secure check fail: pit", maybe I made a mistake, also I tried the alternative method mentioned by you, while using rm command from parted , it won't show any errors, but partition are not getting deleted, they remain the same, whenever I try to create a partition after executing rm , it would just say"are you sure , we can create partition from31.3gb to 31.3gb , which is the end of Emmc, hence I think partition not getting deleted.
[Galaxy Note GT-N7000 General] hg42:
what do mean by "no result"?

The test runs and does not stop?

Then it's not an emmc bug.

with an emmc bug the test will freeze.

a note4 will not have an emmc brick like a note1.

there are many reasons why a device can freeze, let's say 99.9% of them are software. A very small part may be hardware. But only some special conditions lead to an emmc bug.

You did not check all the preconditions for an emmc bug.

A note4 has an emmc chip where the firmware bug was fixed a long time ago. Also, I am quite sure, you never used custom software that

is old enough to trigger the emmc bug.

so why do you still think it's an emmc brick?

as I said, there are many reasons, some of them hardware, but NOT an emmc brick.

don't try to fix an emmc brick that doesn't exist.

you can only make it worse.

search for another reason. relocating partitions will not help you.

other hardware problems may affect the emmc chip, but it will not affect an area of the memory. the emmc brick bug was extremely uncommon.

You don't have the pre-conditions, you don't have any other reason to think it's an emmc brick, so don't go this route.

Fiddling with the pit is the worst thing you can do!

But you already did.

If you cannot use Odin any more, you are lost. So be very very careful with pits.

Odin already protected you from doing bad things.

I think a note4 has more protection mechanisms than a note1.

Several things are write protected and secured.

The good thing is, you don't need to change these, because they will remain original.

In your case I would probably try to flash original samsung software or use kies to restore the device to an original state.

But this might not help, if you have a hardware problem.

There are many, here are some directions:

did the device drop on floor?

all kinds of damage can result from that, may be bad contacts or bad cooling (e.g. because of broken electrical paths).

Did you overclock? did it get too much heat from the sun?

devices getting too hot or otherwise working outside their design specifications can get certain kinds of damage.

The creator of the device did choose the clocks for a reason. Overriding that isn't a good idea.

If you overclock, you need better cooling, and you don't want to install a water cooling system on your phone, right?

Other common reason for hardware failures:

Water, sweat, too much humidity etc.

Bending the phone, e.g. in pocket.

If the device lies on desk without any moving and still freezes after some time, this may be a kind of thermal problem.

You may look for hot spots on the mainboard or other parts.

But it's difficult, because some heat is normal and you don't need normal operation temperatures. You could compare with a working device, but I don't think it's worth the risk.