yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] hg42:
you should take the lowest number with any problems (slowdown, reset or hanging) as start of the brick and the highest number as end, so the gap should be from START15143

Btw. don't mix MB and MiB...which numbers did you write down above? If they have the wrong unit (not the one given for start and end in the pit file name) you have to convert them

(1 MiB = 1000*1000/1024/1024 MB )

Your freezes most probably come from taking a too narrow pit.

You are quite unlucky, because 15143 (MB? ) is unusual high (very near to the end of your emmc assuming you have 16GB ).
[Galaxy Note GT-N7000 General] herna:
I am gonna JTAG my hardbricked device, is n7000 16 GB. After make JTAG, do I must repartition the phone with that tutorial? And sorry anyway but I don´t understand any of that tutorial :( I saw on Official JB thread that there is a pit for 16 GB version but not sure if I have to use it after JTAG my phone for install STOCK JB , THANKS!
[Galaxy Note GT-N7000 General] hg42:
This thread is only for emmc bricks!

You usually get it when wiping in an older cwm while on a stock kernel (ics or jb).

I don't have any experience with JTAG procedures, so no help here. I assume JTAG doesn't remove an *emmc* brick, so if you really have an emmc brick, then you may have to work around the bricked areas, either with my patched pits or by partitioning manually.

If you don't understand all that, you probably should not do this yourself.
[Galaxy Note GT-N7000 General] herna:
[MENTION=3597010]hg42[/MENTION] I finally tried JTAG and didn't recognize my device, also tried JIG, no luck. I finally took it to service centre saying them it failed while I was doing OTA and appeared Android Logo and phone stopped :) They must send me fixed couse I have Samsung warranty and Vodafone(carrier) warranty, crossing fingers...

Enviado desde mi LG-E610 usando Tapatalk 4
[Galaxy Note GT-N7000 General] shoey63:
Good luck bro :thumbup:
[Galaxy Note GT-N7000 General] grandcity89:
Sorry about i not really understand the tutorial....

is it from the first i just flash stock 16gb pit for my 16gb note and go thought the recovery to run " 120824-151927-emmc_find_brick_start " and " 120824-151927-emmc_find_brick_end " correct?
[Galaxy Note GT-N7000 General] hg42:
Yes, but no need to flash a stock pit.

You simply need a custom recovery to run the start/end scanners.

With these you find the location of your brick, so you can select a patched pit with fits to that.

With the patched pit, the bricked area will not be used anymore.

If you can not manage to install and start a custom revovery, you still can use trial and error, by flashing different pits and try to install a rom (or only kernel) for each. At some point you will have a working recovery and you can fall back to the standard method running the scanners.
[Galaxy Note GT-N7000 General] grandcity89:
thank for reply ...

Scan start to end: it slowdown at 1107mb

Scan end to start :it stopped at 4580mb

so i flash <N7000_16GB_Q1_20110914--patched--brick-between-00281-and-04844-MB--FACTORYFS-moved-by-04352-MiB> for my pit with stock rom (N7000XXLSA_N7000OXALSA_DBT) ,am i right?

it didnt stop/freeze at odin process...

---------- Post added at 02:44 PM ---------- Previous post was at 02:42 PM ----------

but when my phone still freeze randomly on 4.1.2...any solution please?
[Galaxy Note GT-N7000 General] hg42:
The selected pit is correct for those values.

From what I know, a fresh brick first hops around a little and then after "a while" (days, weeks, depending on your usage of the phone, mainly writes should matter) it stabilizes.

My own brick also moved around for some time (some weeks) but it always stayed between a lower and an upper bound.

So rescanning from time to time and writing down the values should help in finding a pit including all these values in it's unused area.

There also seem to be some unlucky people with heavily moving bricks, which don't stabilize. But even then I would assume there are upper and lower bounds. But I have no prove for this assumption.
[Galaxy Note GT-N7000 General] grandcity89:
If brick fixed, it will stable when using JB 4.1.2 ???
[Galaxy Note GT-N7000 General] hg42:
Btw. If I scan nowadays I still get slightly different values for start and end values. But my selected pit stays away from those. If unsure simply take one with a bigger gap. In your case the start 281 should be safe, so take a higher end value, if you still see freezes.

I assume you are using a known good stable rom and no overclocking, undervolting or suspicious apps (e.g. games) etc., otherwise you never know who causes a freeze, is it the brick? is it some other reason?

I also had a damaged sdcard recently, which also caused random freezes.

So try to keep on the safe side for all these.

Use only stable well known apps while testing and don't do unnecessary things with your phone (e.g. don't install new roms etc.).
[Galaxy Note GT-N7000 General] grandcity89:
thank....:D
[Galaxy Note GT-N7000 General] hg42:
I think so :)

generally, if it is fixed, you will not notice anything of the brick other than missing some memory space in the internal "sdcard".

It's like partitioning a hard disk on a PC.

It doesn't matter how big the partitions are and where they are located on the disk, as long as all files fit into the partition.

The patched pits (apart form some experimental pits) generally follow the scheme to leave all system partition sizes the same and only shrink the biggest partition which is the internal sdcard which is empty when buying the phone. So everything should fit exactly like before (ROMs, cache etc.), only the user area where you place your music, videos etc. is reduced by some GB (you see how much in the PIT name).

Btw. you can test the new partition scheme by scanning with the all-partitions scanner. So after applying a pit you don't even need to install a ROM to see if any partition is still hit by the brick, just scan the partitions.

Installing a ROM only tells you if the ROM areas (kernel, system) are hit by the brick, which is neither the complete partition space nor all partitions.

So scanning all partitions should be mandatory after installing the workaround.

What about your stock ROM, is it safe? I didn't follow Samsung ROM development lately. Be careful to not get another brick.
[Galaxy Note GT-N7000 General] grandcity89:
so i try 120824-151927-emmc_scan_all_partitions_once.zip now ...
[Galaxy Note GT-N7000 General] hg42:
I upgraded to a sgn3 recently.

Now my sgn1 now has gotten those misterious freezes, too.

Looks like it's a bit jeallous.

If I clear all data and install a pure cm10.2 all seems to work.

But if I install more and more apps it gets unstable (1-5 freezes/day).

I tried this with very different pits with similar results.

So I assume it doesn't depend on positions but on how much of the flash is used.

Best strategy would be using the external sd for any partition frequently written to (/data, /cache, etc.).

There are solutions to swap internal and external sd, but I don't know of a solution for putting /data etc. on external sd.

Should be relatively easy, though.

Just some remounts executed in init.d or some kind of modified fstab.

But I think I will concentrate on my new toy instead.
[Galaxy Note GT-N7000 General] :
I think you should microwave it for 25 seconds and see if it fixes the issues :)
[Galaxy Note GT-N7000 General] neier24:
123

Same situation here. Been on PA 3.69 with quite a few apps installed. Recently I've increased the quota, and the bad luck stroke. What i noticed though, as you install different kernels, for example, phillz kernel... with scan tool provided, finds the freeze areas much farther, while the cyanogenmod, or even stock gb and abys kernel, can find them closer, almost randomly, like they move around. Interesting.
[Galaxy Note GT-N7000 General] hg42:
instead of links you can use "mount -o bind ..." which can mount a directory to another directory, then it behaves like any other mount for applications and system.

This has to be executed early in the boot process (before any of those folders is used by the system), so use init.d.

Unfortunately (I think), different ROMs do this differently (existence of init.d, contents etc.).

You could create a zip for flashing in recovery, which would add the script to init.d or wherever it should be placed.

I assume there are only a few categories of roms, which could be addressed by a few different zips.

I once had such a script for my HTC Desire, which mounted my data/app folder from a folder on sdcard.

Later I used s2e which essentially did the same with more comfort.
[Galaxy Note GT-N7000 General] neier24:
Could you look into it? there is a way to access an ext2 partition, and also a way to mount directories... so should work.

I got crashes since a couple of days. I can't fix this **** myself.
[Galaxy Note GT-N7000 General] edipoReboucas:
Thanks :)

Thanks, You save my mobile!
[Galaxy Note GT-N7000 General] edipoReboucas:
Phone Stable.
[Galaxy Note GT-N7000 General] hg42:
sounds nice...

How old is your brick?

how long has it been stable now?

Now that I have my note3, I reduced my note1 to have a minimal partition setup (so a huge amount of unused flash memory). Then I installed only cyanogenmod rom without any additional apps. This is running and running now. But I don't do anything with the phone, it's only sitting on my desk.

Before, I also had the same minimal partition setup but added more and more apps until at some point it switched to unstable mode.

Note, I usually have >250 apps installed.

All without finding any brick in my partitionswhich I checked frequently.

So I still think that writing to the flash memory triggers the freezes etc. which seems to be logical considering it's a problem of the wear leveling.

As a conclusion putting only read only partitions like modem, system, etc. on the internal memory and partitions like cache, data, and ums on external sdcard should be optimal, because then apart from installing a rom all writes go exclusively to the external sdcard.

Unfortunately, I have no time to dive more deeply...
[Galaxy Note GT-N7000 General] edipoReboucas:
How old is your brick? 1 week

how long has it been stable now? 8 hours.

With all step of your tutorial, my phone freeze every moment. Using Mount2Sd, my phone works very nince, on install a big app, like Rayman Jungle Run, my phone freeze on half of the install. Using write scan I solve this problem, but, the phone is instable, random freezes.

With the last trick, the phone is more stable, no crash until now.

I want put cache, data, dalvick cache on external sdcard too, but I'm tired.

Thanks.
[Galaxy Note GT-N7000 General] hg42:
so very very short :)

I think you cannot take conclusions after 8 hours.

Test at least some days without changing your test configuration and use the phone as much as you can.

My note1 worked without any problem for 1.5 years after reviving (3 gb lost).

But now it's getting freezes about 2 times a day (on normal operation).

I always wondered why some of the bricked phones freeze so often.

Now I have one of them...
[Galaxy Note GT-N7000 General] neier24:
cm 10.2 appeared recently
[Galaxy Note GT-N7000 General] neier24:
Appears to me that cm10.2 is making the system unstable.
[Galaxy Note GT-N7000 General] AA1973:
Any proof? Or just speaking out loudly?
[Galaxy Note GT-N7000 General] neier24:
I don't see no one speaking 'loud' here, rather then writing his real exprerience. But yeah. Had the same situation Hg42 seems to have encountered with cm10.2 after a while.
[Galaxy Note GT-N7000 General] hg42:
I think I got freezes before cm10.2 nightly appeared...but I'm not sure.

After some freezes I restored a cm10.1 backup and got freezes, too.

So I wouldn't blame cm10.2
[Galaxy Note GT-N7000 General] hg42:
I think the wiki entry lists the general emmc problems, but they are already addressed in device specific cm source for well known devices like n7000.
[Galaxy Note GT-N7000 General] neier24:
You mention CM 10.1. Well yeah, i had freezes with that one, but sometimes depends on the kernel? Never say never, though, nx kernel specifically, wasn't stable at all.
[Galaxy Note GT-N7000 General] :
CM9 would probably be best....
[Galaxy Note GT-N7000 General] neier24:
What rom are you using?
[Galaxy Note GT-N7000 General] :
I didn't brick my phone.
[Galaxy Note GT-N7000 General] hg42:
cm10.1 worked a long time before (I'm on nightlies), so I don't think cm10.1 is a problem.

I still think the brick striked back when my flash memory filled up with files. I had 80-90% filled at that time.
[Galaxy Note GT-N7000 General] :
Hey man. what device are you using now?
[Galaxy Note GT-N7000 General] hg42:
see my signature?

SGN3 = Samsung Galaxy Note 3, model N9005
[Galaxy Note GT-N7000 General] Hassan_Elyas:
I flashed JonRom V14.5 last night and today morning when i woke up i saw my phone stuck at boot logo..i then flashed stock lt6,lt9,lt5 and i still cannot boot..its stuck at the logo and when i access the recovery mode i get this error (photo) i cannot access recovery mode it shows all this kind of error.

An hour back I flashed stock ics firmware and everything was fine..i then flashed xxlt6 firmware and i got the error again..why is that so?

ICS is fine but jellybean gives error in recovery.

i've tried this multiple times.

THIS IS THE ERROR.

Please. help.
[Galaxy Note GT-N7000 General] hg42:
this doesn't look like an emmc brick.

Your phone would get stuck instead of listing multiple errors.

Also, the emmc brick is independent of the ROM (apart from the data size).

So, I think no help in this thread...
[Galaxy Note GT-N7000 General] Hassan_Elyas:
okay, thanks for your reply.
[Galaxy Note GT-N7000 General] rutberg:
Unable to mount /emmc

Hi,

I've had a complete nightmare with this but i think i finally sorted it out. I experienced the problem where /emmc is unable to mount or format through PhilZ.

After a lot of trial and error, I noticed that i was able to format /emmc if I selected ext2 as filesystem. Then i formatted it again, selecting default as filesystem. Now I've succeeded with installing a rom in my N7000 for the first time in almost a year.:laugh:
[Galaxy Note GT-N7000 General] bluedevil678:
Almost Done but Stuck for PIT choice

Great post! I need some help choosing the correct PIT File. My results are as follows:

Samsung GT-P6200

CWM V6.0.2.7

Current Firmware: XFE-P6200XXKL7-20111228172735

Region: South Africa

Currently stuck at Samsung Logo when booting.

CWM is unable to do a factory wipe - Fails (unable to format /data ... skipping... etc)

Results for emmc_scan_all_partitions_once.zip

----Scanning...

mmc=mmcblk0

/dev/block/mmcblk0p1

scanned 19Mib = 20 MB completed --> OK

/dev/block/mmcblk0p10

At this point CWM seemed to freeze.

Results for emmc_find_brick_start

Scanning 57 MiB = 60 MB then CWM -restarted on its own

Retried and then the following result:

Scanning 1024 MiB = 1074 MB...

Seemed to freeze at this point.

I repeated the above scan and got similar results (Scanning 1023 MiB = 1073 MB..), thus the start of the brick seemed to be 1023 MiB.

Results for emmc_find_brick_end

I got the following result:

Scanning 2046 MiB = 2146 MB... (Then slowed down and displayed Scanning 2045 MiB = 2145 MB)

Seemed to freeze at this point.

I repeated the above scan and got similar results (Scanning 2047 MiB = 2147 MB..), thus the start of the brick seemed to be 2047 MiB.

Now I have the list of PIT files for the P6200 Plus but cant seem to put two and two together, thus I am confused as to which file to use, Can anyone advise???

My deduction was P6200_tabplus--patched--brick-between-01086-and-02160-MB--DATAFS-moved-by-01024-MiB.pit ?
[Galaxy Note GT-N7000 General] hg42:
end value is ok, but 1073 is less than 1086, so the part of the brick from 1073 to 1086 is outside of the gap (the area not used afterwards). This part will freeze your phone when used by any software. This depends on the size really used of the partition in front of DATAFS. If there is a PIT with a lower start value, you should use this instead (if it's not ecperimental).
[Galaxy Note GT-N7000 General] hg42:
P6200_tabplus--patched--brick-between-00281-and-02160-MB--FACTORYFS-moved-by-01792-MiB.pit

sorry I have no Windows here...so no Odin...

please search for flashing *pit* files, there should be an entry for a pit file in odin and a check box, but read carefullly
[Galaxy Note GT-N7000 General] bluedevil678:
Update

I will give it a bash a little later, I too have no windows and am using Odin via VirtualBox which seems to be working fine as long as one sets up the interface for USB correctly.

Thanks for the advice!!

:victory::victory::victory:
[Galaxy Note GT-N7000 General] hg42:
Nice to hear that Odin works on Virtualbox.

I usually dual boot with windows when I have too, to stay on the safe side.

However, will be nice to have another option.

Heimdal is another one, but I had mixed results with it.

Would also like to use wine, which should work too, if usb interface can be assigned to it.
[Galaxy Note GT-N7000 General] hg42:
did you follow my instructions in the thread starter?

e.g. did you install a rom after flashing the pit?

Each moved partition has invalid data after flashing the pit and has to be rewritten somehow, either restored from a backup, installed by a rom (e.g. system) or cleared (like cache)

yes, the brick should now sit outside any partition (that's why the pit has to create a gap in the partition table around where the brick was found).

The partitions should be fully usable then.

The all-partitions scanner should report ok for each partition and not freeze or crash. The scan time for each partition should roughly follow it's size.
[Galaxy Note GT-N7000 General] Nipa-it:
Hi all,

Yesterday my Galaxy S2 i9100 shutdowned and never restarted.

At start up phone stops to Samsung Galaxy SII and don't proceed.

I went to recovery mode and tried to clean cache but without resolve. Tried also to format data/ (phone freeze and get off battery to access again in recovery), same thing for system/.

Tried to flash via recovery both kernel, roms but all operation and aborted.

So I tried to flash via Odin, each operation stucks in "NAND write start!!".

Tried also deep clean with pit, operation stucks to Set Partitioning.

Now only download mode works, recovery doesn't.

Tried some pits downloaded from the first post among larger available (from 730 to 12xxx) and both of jb version and not for jb version.

With any pits Odin flash ends, it stuck so to Set Partitioning and I have get off battery to interrupt operation.

But reading this thread if my was a EMMC brick bug I have to solve flashing some pit, but flash doesn't work...

Suggestions, please?

Is a EMMC bug or the problem is more complicated?

Sorry for my english
[Galaxy Note GT-N7000 General] hg42:
if you read a bit, you should be able to figure out, what causes an emmc brick.

Roughly, it's ics stock kernel + custom recovery from that time.

So if you used current software, it shouldn't be an emmc brick.

However, if you cannot flash via Odin, this could theoretically be an emmc brick.

But, because you cannot flash a recovery, you seem to have done bad things to your lower, essential partitions.

You could try to flash a pit which also moves the recovery partition, and if you are lucky, you may br able to flash a recovery afterwards.

BUT, note this is definitely an expert procedure then, and if you don't understand the first post of this thread completely, you may make the situation even worse. It's not a matter of simply flashing the pit, you also havevto restore all moved partitions.

So it's not a matter of try this try that, instead you should know which does what and develop a complete plan, how to solve every upcoming problem, BEFORE flashing anything.
[Galaxy Note GT-N7000 General] churi14:
ayuda

Hello

I have a samsung galaxy s2 i9100, and was repaired and says the tread by another person (so buy it.) and have a question.

Currently this with android 4.0.4 ics (neatrom lite rom with siyah kernel).

If I want to upgrade to a more current version of android also updating the recovery, kernel, and so on. Am I at risk of the arrangement of the internal memory is lost and then brick phone?

I hope answers and apologize for using the google translator because my English is basic medium

thanks
[Galaxy Note GT-N7000 General] hg42:
in short: no

unless you flash a pit (or use a partition editor) the partition will be kept.

In theory an update zip could also change partitioning, but I never saw such a package.
[Galaxy Note GT-N7000 General] churi14:
Thanks

that's the rom that I have on my phone

http://imgur.com/nRR9o3u

and I am going to install this rom tomorrow http://xdaforums.com/showthread.php?t=1569686

I hope I never have problems then

thanks
[Galaxy Note GT-N7000 General] hg42:
being a cyanogenmod fan I cannot say anything about this rom.

But usually custom roms don't change partitions, otherwise they would explicitly tell you, because it's critical for your data.

So don't worry (but make backups anyway when trying new roms etc.).
[Galaxy Note GT-N7000 General] akhil17kr:
My galaxy s2 i9100 is Hard Bricked when i am transferring some data to the internal SD card... during transferring it crashes and restart and stuck on samsung boot logo .. Cannot access recovery mod but can access download mod.. so installed siyah kernel v6 .. but still go stuck on boot logo so after trying again after 2 times more(OFCOURSE through ODIN).... Phone switched off and never turned ON again..

Its completely Dead... No charging animation too..

Took it to local repair center as the warranty was over and after 2 days inspection he said It is EMMC Corruption problem instead of POWER IC problem(earlier though it could be POWER IC Problem).... and it need to be replaced or motherboard replacement..

SO in any way can i use this method to save my phone ??
[Galaxy Note GT-N7000 General] :
You can see if the computer recognizes it and try to force download mode. But if it doesn't turn on at all, I don't see how you would do that.

Sent from Nexus 5 on Slimkat
[Galaxy Note GT-N7000 General] akhil17kr:
Well i didn't try Jig..

But normally phone neither cannot enter into download mode nor recovery mod .. No charging animation on connecting charger and also The right side of camera gets HOT...

BTW the local repair center guy told me its not power ic problem its EMMC chip problem ..as he explained in non-technical language the computer can detect its software or something like that... I'll ask him again tomorrow what he meant by this ...
[Galaxy Note GT-N7000 General] jamy862004:
Hi. can you please help me to revive my note..

http://xdaforums.com/showthread.php?t=2641540&page=3

I Can boot only into download mode.. but cannot boot into recovery and stuck with startup screen.

Tried to flash a stock kernel but stuck at nand write start.

Tried to flash n7000 16gb pit but getting repartition failed.

I wanted to ask that OP has patched pit files for 16gb N7000 but there are around 344 pit files.. so which one do i flash? As i cannot boot into recovery mode, i cannot use the scanner.
[Galaxy Note GT-N7000 General] hg42:
first, flash a pit with "kernel" in it's name, because your kernel partition seems to be damaged, too.

Use one with a high number after "moved-by" first, e.g start with moved-by-8192 which is half of your 16gb memory.

Then try to flash a kernel+recovery combo.

If that doesn't flash, try higher numbers after "moved-by".

If none works, you seem to be out of luck...

If the recovery works, use the scanners to find the real brick position.

Then flash an appropriate pit file using the begin and end numbers for selection.

good luck...
[Galaxy Note GT-N7000 General] FARSHOOD:
dear sir would you say what was your problem and now is your sd16gb full capacity is available and finally please write down step by step what did you do(procedure for repairing). thanks