yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] prince4p91:
so all i'm supposed to do is flash this patched PIT file one time right after the brick and then formatting /system , /data , etc just once and then can flash as many ROMS i want without the need to repeat above written steps.

i'm asking all dis because i am just getting stuck at BOOTSCREEN after flashing different ROMS like prisetines , Alliance ,etc.

the only ROM thats working for me is the stock GB Rom.

what wrong am i doing here.:eek:
[Galaxy Note GT-N7000 General] forest1971:
You mean you have already recovered from brick with the patched pit file? It is still not clear enough from your description.

in that case you should still be able to install custom roms. Still This Note I can be tricky sometimes.

Let's give more details. cheers.
[Galaxy Note GT-N7000 General] prince4p91:
STUCK at boot screen

okay here's what happened i somehow by mistake did a factory reset in that *****Y stock iCS ROM resulting into brick.

then later i used one of those pit files provided by you (all thanks 2 u) to revive my bricked note.

then flashed stock GB rom using PC ODIN.

and VOILA that worked (but hangs alot and keeps rebooting after small time intervals).

Then i thought of installing a new custom ROM via CWM recovery. so for a new installation what i did was that i first flashed that 4PDAkernel provided in ur post via PC ODIN and then rebooted into CWM recovery and formatted /system , /cache, /data and /sdcard and then flashed the ROM via recovery, it would get flashed(according to recovery) and thne i would reboot it but then it gets stuck on the boot screen.
[Galaxy Note GT-N7000 General] forest1971:
I woulx try to flash a cuafom kernel suutable for that rom via odin and then boot into recovery, wipe again. See if it helps. Some times it did not work well after suffering from this kind of brick. But should try different roms. Light weight cm 9 rom seems to be the best. Cm10 should be good also I guess. I have move on to another device so do not update about roms for Notes. Cheers.

Sent from my LT30p
[Galaxy Note GT-N7000 General] prince4p91:
naaaa kernels of no use still stuck at samsung jelly bean boot screen...

flashed philz safe kernel for ddlsc...

whatever now..

would try to flash paranoid 3.15 lets c wat happens...

naa paranoid 3.15 is of no use either.
[Galaxy Note GT-N7000 General] fenac:
Thnkx
[Galaxy Note GT-N7000 General] djudjix:
Galaxy Note N7100

I have read a lot for today regarding this SDS and PITs and stuff I am not afraid to go technical all the way, but I am advanced user not an expert. I have some questions regarding revival and checking for errors. I am sorry if I turn to be lame about some questions I ask, please don't judge.

My friend brought SGS II N7100 which can only go to download mode and not any other and is stuck on "Samsung Galaxy Note..." screen when turned on.

I tried to flash prerooted stock rom from Dr.Ketan and result when no PIT is specified is fail: "No PIT file specified" and result with PIT File specified is fail too... In one post here you have referred that there are number of reasons why Odin would fail to flash anything and it can be eMMC error that is bad Flash Memory

As I was reading all posts regarding these modified PITs I understand what you do with these steps you put in this thread. If I am not wrong, you do following (shortened in 3 steps).

1. Determine where brick (bad memory blocks) started (through recovery)

2. Determine where brick ends (through recovery)

3. Isolate bad memory blocks with patched PITs so you are able to flash everything so phone can work (noob explanation) (this part is done with Odin)

My question is following: Since I can not go to recovery, is there any way of determining which PIT to use if you can enter only Download Mode, because it can be very dangerous to flash wrong patched PIT almost like flashing GB PIT to JB (kind of). Hidden question: How can I determine 100% that I have bad eMMC (I was trying to flash kernel or recovery through Odin but result is always the same - FAIL).

This phone is (again) Samsung Galaxy Note N7100 International Version, 16 Gb... I am sorry if I have missed some part of this large thread but if u can point me it is start of a solution.
[Galaxy Note GT-N7000 General] forest1971:
Your understand is correct!

About failures there can be many causes. Some common causes have been summarized by Dr Ketan:

-----

- Commonest cause is connection issue.

Solution :

-This can be solve by installing proper driver.

If kies or any similiar PC sync SW running in background, can cause this. Complete close kies from task manage. Even you can uninstall kies from PC

Install just driver from here.

-Dont use USB extention cable, connect device directly to PC (preferable on Motherboard USB port, back side of PC), try changing USB port.

-Close any antivirus SW running on PC, disable firewall.

----

Also you can try to change computers, PC using the old XP seems to be working the best. and should try different cables.

- After all of that it still fail then flashing original Pit and custom Pits (with "repartition box" in odin checked) are the last resort.

Flashing custom pit design for the specific phone is not that dangerous since it leave all the critical partitions (such as boot, recovery, efs, param...) untouched. For most cases you can flash many time different custom pits to find the one that work. Still, sometimes it can cause hard brick and you will need Jag Riff box to revise the phone.

- When custom pit failed then you will need Jtag riff box.

- And sometime the phone memory just broke for some unknown reasons then you will need to replace mother board.

So basically those are the options.
[Galaxy Note GT-N7000 General] claptnei:
Many months ago I suffered a brick situation which I recovered from by using this guide, thus losing approx 3gb of usable memory.

I have tried several times to update to JB, but every time I do, I suffer from my device freezing and having to power of and on again to the point my phone just isn't usable. I then restore my ics and everything is ok again.

Is it possible that because i have pit method revived my phone I am now unable to update to JB due to a different partition structure?
[Galaxy Note GT-N7000 General] ThaiDai:
You lost 3 GB with the workaround and it's known that only small-sized Roms work without problems. Big fat JB doesn't belong to that category.

And now you understand why repartition is called a workaround: the only real solution is mainboard replacement.
[Galaxy Note GT-N7000 General] claptnei:
Ok thanks for the info, I am going to give your slim pristine a go tomorrow.
[Galaxy Note GT-N7000 General] ThaiDai:
My Slim is still a JB. So it is never as slim as a CM/AOSP-based. I do not think you'll get lucky with it. But try it.
[Galaxy Note GT-N7000 General] claptnei:
Ok tried it, very nice and clean, but as you thought there were some freezes still. I will just have to stay with ics, but many thanks for your help.
[Galaxy Note GT-N7000 General] neier24:
You must be very lucky. What did you do exactly?

I'm on slim JB and freezes are constantly. I don't even know how to describe the problem because i'm relatively new...

You've downloaded the zip on sd card? ran the safe kernel before, or after install?
[Galaxy Note GT-N7000 General] claptnei:
I've followed all the guides and used safe kernels (Philz), tried stock un rooted, stock rooted, stock bloat removed, Slim JB roms. JB just won't work on my phone as it has previously been bricked and revived via the pit method. I am stuck on ICS LRK (the last version I liked) which just seems to work almost flawlessly.
[Galaxy Note GT-N7000 General] neier24:
Ok. Strangely, i've tested rocket rom v12 with notecore (safe kernel) before posting here.

Did you by any change flash the Philz after enetering the os, or just before
[Galaxy Note GT-N7000 General] ThaiDai:
No wonder that you didn't succeed with your presumably "double bricked" device. Even really slom Roms won't be stable on it. And your problems will never be solved by changing Kernels or the order of installation.

http://xdaforums.com/showpost.php?p=40133609&postcount=12 (or better read the complete thread again).

You were warned to not buy it and it was clear from the start where it would end.
[Galaxy Note GT-N7000 General] neier24:
At your post count, you should\ve learned by now to abstain from negative remarks which are even judgmental against other people. In case you're not on the same side of the problem, you won't help.

This device isn't only bricked as you may have warned me... is also wifi\network broken. Simply the net won't work on it, i wouldn't care about the apps cause i'd use the device as a kindle or nook for books. I bet you didn't knew this.

This seem the only hope for now: http://xdaforums.com/showthread.php?t=1874485
[Galaxy Note GT-N7000 General] ThaiDai:
Who wrote this?

So please do yourself what you wish from others.

You made a fool out of yourself buying this device when knowing that it was bricked.

And to avoid a war of words I'll stop commenting your posts.
[Galaxy Note GT-N7000 General] neier24:
For those who have severe symptoms... try to shrink the cache partition. At least this way i was able to install apps...

Note: one time os was on a boot loop. The reason might be that the stock gb isn't the best option when formating, as the abyss is.

If i could move the cache, or any I\O that happens on the device, to external sd card, i think i could browse \ use wifi without getting freezes.

http://www6.zippyshare.com/v/5832644/file.html
[Galaxy Note GT-N7000 General] hg42:
Hmm, I also lost 3GB and am using cm10.1 which is kind of jb.

Loosing 3GB of internal sd shouldn't make any problems when installing a rom.

Internal sd usually should be nearly empty when purchasing a jb phone, isn't it?
[Galaxy Note GT-N7000 General] hg42:
Everything is possible...

But the brick shouldn't matter here.

Changing from one rom family to another usually needs a clear data partition. That's because several data structures may be changed between major os versions, rendering some saved app data unusable, which often results in loops etc.

So did you clear before installing jb?
[Galaxy Note GT-N7000 General] claptnei:
Yes I formatted the data, cache, system partitions first, and cleared dalvik and cache, using Philz safe kernel, as per many instructions. JB just won't not freeze on my phone, ICS is fine, it may crash occasionally, but I expect that just like a computer does.

I wonder if it is a rouge app that has not been updated to JB possibly?
[Galaxy Note GT-N7000 General] hg42:
my phone doesn't crash occasionally (it was revived, too, loosing 3GB).

Do you restore your apps from a backup after updating from ics to jb? I think you shouldn't...

I don't remember exactly how I updated from ics to jb, but I think I didn't simply restore all apps (I use Titanium Backup) like I do usually.
[Galaxy Note GT-N7000 General] neier24:
Seems to be like gambling for us. Dunno if we're doing something wrong as we may have followed every tutorial around.

This must be a very extreme case of brick we got; a very saturated emmc bad block bug.

When realising you can't recover more then few mb of space, makes me thinking this is the worse case of corruption.
[Galaxy Note GT-N7000 General] paila87:
Q1_*_16GB-patched.pit

I´m looking for "Q1_*_16GB-patched.pit" file por the N7000, i cant get to recovery and i cant now witch memory blocks are damage.

I´ve seen in deferents post that they use the "Q1_*_16GB-patched.pit" file that they found in these threat but i cant find it!!!!
[Galaxy Note GT-N7000 General] neier24:
Which one?
[Galaxy Note GT-N7000 General] kevwiener:
i have run the brick end and the brick start zips, and i have also got the PIT magic program but im a little unsure of how to make the pit file i need.

can someone help me out in creating the pit file to recover my note.

when i run the 120824-151927-emmc_find_brick_start i get this

1023 MiB = 1073MB ...

has frozen at this point

when i run 120824-151927-emmc_find_brick_end i get this

6443MB ...

frozen at this point

any help is muchly appreciated :)

kev
[Galaxy Note GT-N7000 General] hg42:
Please read the thread starter carefully.

The pits are all there...
[Galaxy Note GT-N7000 General] coen22:
I can't het into recovery I9100. Wat do I have tot do? It's bricked. Van only het into download mode
[Galaxy Note GT-N7000 General] :
Uh did you wipe from stock ICS?

You need to give more info... It sounds like you just need to flash a ROM in download mode via PC Odin. Clarify what you have done to get where you are.
[Galaxy Note GT-N7000 General] coen22:
First it was stuck in a boot loop. Restart

Then I didn't even get to see a boot animation

Went to recovery. Could flash any ROMs

Went to download mode. Odin stuck at writing Nand

Researched half xda. What do I need to do?
[Galaxy Note GT-N7000 General] ThaiDai:
Where does Odin stop? When writing factoryfs.img?

Make a snapshot from the error. Your infos aren't really usable.
[Galaxy Note GT-N7000 General] coen22:
It did make it to factoryfs this time, but then it's stuck

https://lh3.googleusercontent.com/-...AAAAAAAEGs/X0TKNJBWakM/w800-h600-no/test2.png

EDIT: and it doesn't turn on anymore :(

I'm gonna send it to samsung

thanks for the help anyway :)
[Galaxy Note GT-N7000 General] neier24:
That should teach samsung a lesson. u show em
[Galaxy Note GT-N7000 General] hg42:
another private message...

i9300 is like i9000:
[Galaxy Note GT-N7000 General] yakie47:
does the i9000 pit file realy works for the i9300? if it it is, where can i find it, i don't see it on the main thread?
[Galaxy Note GT-N7000 General] hg42:
no, I already cited from thread starter:

which means, the PIT method doesn't work for these devices.

That's why you cannot find the PITs...

I also updated the thread starter to include the i9300 as unsupported device.

I think, I have to create two lists (working, not working)
[Galaxy Note GT-N7000 General] eyekantbeme:
Haha classy! Hillbilly Blood! LOL!

Now I will let you get back to your regularly scheduled program, lol O_O
[Galaxy Note GT-N7000 General] AgtPower:
Hello again...

I found an original PIT for my Korean GNote. The PIT flashes without problems, but if I try to flash a ROM, it still aborts at NAND write part. The phone itself is still stuck in a boot loop, and download is the only thing that works....any suggestions? :(

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_E160L.FA09.1726_CL867558_REV0000_user_mid_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Note GT-N7000 General] SamuelLG:
OMG.... I can't thank you enough!!!!!!!

Yesterday my friend asked me to upgrade his SII from 4.0.3 to 4.1.2, and after all wipes from keyboard codes and from cell menu, i entered in CWM mode and did the wipes... HARDBRICK...

Fortunately i found this tutorial and used the correct .PIT to 'jump' the crashed sectors and the internal SD loses about 1.9 GB, but its is much better than expend about 300 U$$ to fix it in autorized assistence.
[Galaxy Note GT-N7000 General] hg42:
First you should find out if you have an emmc brick or not.

For this, you need to use recovery mode.

To get a working recovery, try to flash a custom kernel in Odin (so you need a kernel in Odin format, which is a .tar file, you can find one at forest's thread).

If this works, run (= install zip in recovery) my scanner(s).

If this reboots or doesn't scan in under 1 or 2 mins, you should follow the procedure described in this thread.

And don't forget to read, read, read, ...

I always recommend to understand before doing something.
[Galaxy Note GT-N7000 General] shoey63:
I would say definite "superbrick". Seems he wiped on stock kernel with CWM.zip. (Lethal, as you well know). But yes, partition scanner will reveal the truth;)
[Galaxy Note GT-N7000 General] AgtPower:
It must be a problem with the emmc /nand / partitions, since I had tegrak recovery, which doesn't work anymore since the crash. Pressing the button combination for recovery mode makes the phone stuck at Samsung logo. The device connects to usb in this state, but is not visible to adb.

Flashing recoveries/kernels/roms quits with the "fail" message in ODIN. The only thing working is flashing PIT files (at least the only thing returning PASS). I downloaded PIT magic and will try to move the recovery/kernel partition to another part and see if it works...
[Galaxy Note GT-N7000 General] hg42:
your description doesn't seem like the typical emmc/"wipe in cwm on stock ics kernel" issue.

You had tegrak kernel or rom?

These should be emmc/wipe safe if I remember correctly.

(Edit: sorry, I confused this with another kernel)

So I'm not sure it's an emmc brick like discussed in this thread.

Please try to flash some custom kernels in Odin/download mode (e.g. there is a 4pda or cyanogenmod kernel for Odin) and see what happens.
[Galaxy Note GT-N7000 General] hg42:
sorry, I confused this with another kernel

From a quick search, I didn't find exact features of tegrak kernel.

Btw. Did you use the correct one for your specific model?

E.g. on http://xdaforums.com/showthread.php?t=1924535 you find:

"Download the appropriate Tegrak "Recovery" and "Kernel" files that is SPECIFIC to your model"
[Galaxy Note GT-N7000 General] AgtPower:
Hello, yes I did. I rooted the phone successfully with Tegrak kernel and recovery and it worked flawlessly for 3 weeks after rooting. The phone crashed randomly while using it, and since then it's stuck in a boot loop. Flashing from Odin doesn't work. It always fails at NAND write.

I'm starting to think the mainboard/emmc has some serious defect that can't be resolved with flashing...

EDIT: I was on rooted stock rom that I found around the forums here...never had problems with it
[Galaxy Note GT-N7000 General] hg42:
btw. this is the expected duration for the all-partitions scanner (on my Galaxy Note (1) it's about 30 sec, should take longer on slower models).

The find-brick scanners run at about 5 MB / sec on my Note.
[Galaxy Note GT-N7000 General] hg42:
Here is some conversation from a private message which should be of general interest:

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

ok, I'll try to speak more slowly :)

there are several ways to patch a pit file.

Basically it's simply a binary file with a certain structure.

You have to change some bytes at certain positions.

The structure contains a header for the whole file and a block for each partition.

The partition blocks also have a structure describing it features, like size, start offset etc.

Now you can write a program in perl, C, C# or whatever, that reads the file changes some bytes and writes the patched file.

It's fairly easy if you are a programmer.

As such you can find a structure definition for pit files as a C header file in the "heimdall" sources which is an open source odin replacement.

Otherwise you may need some GUI Program.

The "Workshop" software is some generic java software for analysing and patching every kind of binary file, but you need a structure definition file (*.str), that tells the program where (that is in which bytes) to find which values. I created such a definition file called pit.str which I told about in the thread.

But that's still for experts/programmers.

The easiest software should be this "PIT Magic" application:

[APP] Updated: 31/10/12 - PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer! - xda-developers

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

It should offer all you need to manually patch a PIT file.

you can patch any value (byte(s)) in the file if you know it's meaning.

But to generate pit files working around an emmc brick, you only need to patch start offset and size for each partition.

there are generally two kinds of PIT files:

1. files providing start offset + size for each partition

2. files providing only the size for each partition, the start offset value is replaced by the block size here

the second variant seems to be older but is also used in some recent phones.

In the second case, you can only define partitions touching each other, because you cannot move them (no start offset).

I still want to know why you want to patch a PIT file.

It's not necessary for phones supported by me. If you have a new phone model I can look at it.

If you have a model that has no start offsets in it's PIT, then you cannot work around an emmc brick, that's why these phones are not supported and they will never be.

You have to partition with other tools then, see forest1971's thread for this (netioned in the thread starter).
[Galaxy Note GT-N7000 General] hg42:
notes about the "PIT Magic" application:

- the start offsets of devices like N7000 are stored in a field called "Block Size"

- the "PIT Entry List" control is used to select the partition (I would prefer a table instead)
[Galaxy Note GT-N7000 General] lyriquidperfection:
Noted! ;)
[Galaxy Note GT-N7000 General] bluedevil678:
Slick Stuff, Little Stuck Thoug

This is some very cool software to scan start and end blocks !!

I did my scan and got this:

Start: 1023 MiB = 1073 MiB (Then Slowed down dramatically)

End: 2047 MiB = 2147 MiB (Then screen flickered and tablet reset itself)

Cant seem to work out the maths for the correct patched PIT file... Maybe I'm just that tiered lol

Any suggestions ?
[Galaxy Note GT-N7000 General] hg42:
note, the second column is MB (without 'i').

Then read, read, read again :)
[Galaxy Note GT-N7000 General] neier24:
would there be a way for the provided scanner (write) to change the depth of bits scanned per second? it goes over the brick area, but that doesn't solve or fills the gap with 0 files, its still unusable. Maybe goes too fast and skips some blocks in the process?

I wonder if i'd leave it to write for about 24 hours, at low speed, but more accurately, if that would make a difference
[Galaxy Note GT-N7000 General] hg42:
The write scanner is only an experimental test to try out if continuously writing blocks changes anything in the wear leveling. It was written for testing for those with moving bricks.

Especially, it doesn't solve any kind of brick!

Also, there never was a report from anyone that it changes anything. So simply don't use it.

To work around an emmc brick, you have to use patched pits or repartition manually.
[Galaxy Note GT-N7000 General] hg42:
It doesn't write in the brick area but simply simulates phone memory usage at a high rate, because using the phone usually triggers a moving brick. The write scanner constantly writes a file and deletes it afterwards. But this doesn't seem to trigger moves of the brick. So the simulation failed.
[Galaxy Note GT-N7000 General] neier24:
I noticed that, but still hits something and then resets...

Pretty straight forward answer. Thanks for reply.
[Galaxy Note GT-N7000 General] hg42:
It probably hits an emmc brick area...writing and reading should both have similar effects on this.

Did you already use the find brick scanners? If so, where do they find start and end?
[Galaxy Note GT-N7000 General] neier24:
Thanks for asking. Its pretty weird.

Running the scanner, from end to start, found a safe route: 15070

reseted at around 15063

and from beggining stuck after 300 - 340 which is pretty random. Now its safe at 1080 - 1090; 1040 1091

14515 15115

14440 15143

14410 15100 - 95

Random ends.

I've usen your pit files, many of them... Its working okay on CM 9, can't complain of freezes if i'm not instaling something new.

The browser is working perfectly if is in incognito mode so leaves no traces on bricked blocks. :good: