yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] Zarvox:
For my part I've discovered approximatly where bad block is in my /data partition.

1070<---- around 3 BG -------->4096<---- bad blocks ----->6500<---------- around 8 GB ------->15204

I'll try your pit soon :o
[Galaxy Note GT-N7000 General] travis82:
Damn ok no wories ill let my buddy know
[Galaxy Note GT-N7000 General] Zarvox:
Sadly I think my tablet is badly damaged.

The partition data is corrupt, but once I've repartitionned the tablet reboot, FC or freeze.

(sorry for my english google translate help me a bit)
[Galaxy Note GT-N7000 General] xpomar:
I will wait till the trick for scaning all blocks ! cuz my note work now i just have some freez and some FC :(
[Galaxy Note GT-N7000 General] ourtech:
Here is where I am at. I had gone for 2 days without lockups, but noticed that I still had the yellow triangle from a previous kernel flash. So I used the Triangle Away program from Chainfire. My lockups have returned. Today I followed the instructions to use the info in this post here to load a different kernel on the unit and manually test each partition with dd. Each partition tested (7, 9, 10, 11) passed with flying colors, no lockups on the test. But I still have random lockup, usually at night when charged. So here are my questions.

1) As I understand it, if those partitions pass then I am clean, correct?

2) Is there anything that the Triangle Away utility that could open up a corrupted area?

3) Is there anything that changes when sitting and charging that could access an otherwise blocked off area?

Otherwise I would think that my issues are somewhere else. I am just trying to figure what changed when I cleared the yellow triangle.
[Galaxy Note GT-N7000 General] hg42:
from all I know about the brick

1 - your repartitioning was successful

2 - very very improbable

3 - very improbable, too

Said that, I think nobody knows exactly in which ways a brick can show up, so you never know. There are lots of unexplained report of problems which were related to the brick (by the reporters).

Generally, people tend to blame the brick for all kinds of problems. They have forgotten, that all these existed before.

That is exactly the reason why I say "use a known good ROM" (like cm9) and "use a very clean and fresh installation" (only absolutely necessary apps, no tweaks, no mods, especially no oc, no uv, etc.) first.

This will give you some more certainty feeling.

Also, you can never say "if it works currently, it will do in the future".

This is only a statistical assumption with only a few samples, which is absolutely worthless.

Using a ROM for some days is not much for such assumptions.

It's another thing, if a bug is fully understood or at least easily reproducible. Then you have a much higher certainty, if you cannot reproduce it any more.
[Galaxy Note GT-N7000 General] ourtech:
Exactly why I say that my problems may lie in some other area. I may have some misbehaving program. I just wanted to make sure that in clearing the Triangle that I didn't reopen an old wound. Now, on to other steps to stop the lockups. You have been a great help. Thanks.
[Galaxy Note GT-N7000 General] Zarvox:
I've bad news :(

I'll try pit file for P6210 and now my tab didn't work at all (no samsung logo, no download mode).

But I'm not to say the pit is the culprit because after the brick my tab is more hotter.

All device became hot while charging but my tab is hotter than normal.
[Galaxy Note GT-N7000 General] hg42:
emmc partition scanner

I just added a topic for the emmc partition scanner

It should be very useful for all asking themselves if all partitions are brick free.
[Galaxy Note GT-N7000 General] tannykim:
hg42,

Thank you for your hard work.

However, I would like to get some more help from you since my experience is little different...

When I flashing STOCK ICS via Odin, my factoryfs do not getting stuck....

However, after the reboot it randomly freeze and sometime reboot or boot loop.....

Even with GB, I have same issue....

Is there any other way I can bring my note back?

Please help and any suggestions....
[Galaxy Note GT-N7000 General] hg42:
did you read and do all necessary steps from the thread starter?

Especially, repartitioning alone doesn't work (therefore don't check autoreboot in Odin).

You have to fill all affected partitions with something (flash image or format).

You may pull the battery for some time and start from the beginning.

I assume it's getting hot because of running in a loop, trying something again and again.
[Galaxy Note GT-N7000 General] hg42:
please use my new partition checker after repartitioning, to easily check if any brick remains in one of the partitions.
[Galaxy Note GT-N7000 General] hg42:
next I am working on a brick finder (start and especially the end), but my time is very limited...so please be patient.

This will allow to know where the bricked area is, and to directly choose the right pit files without trial and error.

May be I have to change the pit file numbering scheme then to reflect these numbers.
[Galaxy Note GT-N7000 General] Zarvox:
Yes I've read all steps and I've little experience with my previous samsung phone (SGS) and Odin.

I'll try some pit file in Odin and a stock Honeycomb rom.

When the flash is done I reboot in recovery and factory reset.

After some tries a pit file work cause the tab format data/sdcard but I've only 3GB of storage !

With the next pit the tab format data but is extremely slow and unstable (is rebooting automatically).

The next reboot my tab is dead :(

On Galaxy Tab you can't pull the battery as a phone.

I think pull the battery must solve the problem but I can't.

I try different things but with only two physical button (power + vol +/-) is difficult :)
[Galaxy Note GT-N7000 General] hg42:
then there's no hole with a reset button/contact below/inside?

most devices either have removable battery or reset switch (err - let's say some kind of).

If not, it's a design fault in my opinion, then it's getting more difficult.

Last time I had such a device (a tomtom navigator), I let it run until battery was empty (a whole night). After that it ran flawless again...

What about warranty?

If you don't care, can you open the Tab? perhaps you can pull a connector of the battery...
[Galaxy Note GT-N7000 General] ayman.maestro:
HIIIIII

Hiii men

1st, thank you for all u doing to fix this problem

i have brick my phone many times (more than 6)

before one week i have hard brick (no downloadmod,no recovery), fix boot with RIFF BOX and use ( N7000_16GB_Q1_20110914-patched-ums-bricked+5242880-kB.pit) and brick it again and so on ^_^

I notice that:

1- when use any of (

patched-ums-bricked

) pits and then try to use (

standard patched pit file

) will

brick the boot

( no downloadmod, no recovery,dead phone, require RIFF BOX)

2-when use

GB with (patched-ums-bricked) pits

, there's no problem ( i use

Cassies XtraLiteRom X LC1

, that nearly perfect with bricked phone)

3- when use

ICS

( stock, other roms , i try more than 4 ics roms) with

(patched-ums-bricked) pits

,

____a. the phone was unstable, stop frequently, i dont kown why?

____b. no lock screen,

____c when press power, the mobile turn off ( no power menu)

_____________ any one know how to fix this???? with ics?

thank ___ again

sorry for my bad English ^_^
[Galaxy Note GT-N7000 General] Mario1968:
Hi, for the point 3 b and c I've read it's caused by a efs corruption, can you try using Google to search the user Odia and efs, seems he has a solution for this.

For the other points, sorry I'm unable to help you:(

Good luck and Bye

Mario

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 3.5.2

Jkay V14.1
[Galaxy Note GT-N7000 General] tannykim:
Thank you for the information.

However, your information need to be updated.

I tried many times with patched-ums-bricked pit files, so I can update your data.

When I tried to install stock GB ROM with patched-ums-bricked pit files, there was no issue when I flash GB stock ROM with PC odin.

Also, when I flashing stock ICS ROM with PC odin, there was no issue when flashing.

However, both Stock ROM had issue with unstable and freezing. Random re-start is common on both system.

Therefore, I tried little different approach....

I flashed random patched-ums-bricked pit file [3145728] and flashed CM9_safe_kernel and reboot with recovery.

With CM kernel, I wipe all system and format Data / system / emmc....

After that, I flashed STOCK ICS ROM [N7000XXLPY_N7000OXALPY_DBT].

I still have some issue with freezing and random shut down, but it is better than other method.

Anybody have other process?

---------- Post added at 08:31 AM ---------- Previous post was at 08:23 AM ----------

Please put the information responsibly....

His issue is not related with IMEI code since I do not have issue with IMEI.

I have same IMEI before I bricked my note, but I have same issue.

Thank you
[Galaxy Note GT-N7000 General] Mario1968:
Hi, I've never says that problem is imei related, only that the possible cause was on the efs folder (sorry, I not remember the exact thread), what I say is that for the "power button turn off the phone immediately" and "no lock screen when turn on the display" behaviors this Xda user Odia could help, if I remember the exact procedure I will post.

Bye

Mario

Edit: found: XDA link

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 3.5.2

Jkay V14.1
[Galaxy Note GT-N7000 General] Zarvox:
Fortunately my tab is under warranty :)

If Samsung refuses to fix it then I certainly would consider it apart (I already have a disassembly guide).
[Galaxy Note GT-N7000 General] MohElShafei:
Dear hg42,

As tannykim said, I don't know what is happening with may Note too, it do exactly that same as his SGN !!!!!!!!!

Now I'm able to locate the bad blocks .. and I'm surly out of these blocks in my eMMC structure now. I did everything to make sure that FACTORYFS, DATAFS, and UMS partitions are in clear blocks, even though, random restarts, freezing, and hanging all the time.

Note: RECOVERY, CACHE, and KERNEL are also in clear blocks (after running the Partition Scanner app).

I also did a check that certainly made me sure that the I'm in a clear area in UMS. I mounted my SGN in the PC after flashing a ROM, then I copied to/from anything in the UMS partition till its full (more than a time) and it works like a charm, with no hangs at all. That made me certain that these blocks are OK. Even though, it hangs!!!!!. In addition I did the following checks:

Run the Partition Scanner app and shows no errors at all.

Did the DD command scan method, and shows no errors in all partitions (from forest1971 post)

Did the e2fsck check method, and shows no errors (from forest1971 post)

I can wipe all partitions in Recovery without any errors or hangs at all

I can install all types of roms without errors, no hangs in FACTORYFS image in odin at all

Now I'm about to go mad, everything is fine, I'm out of bad blocks, even though; freezing all the time and Force Close !!!!!!!!!!!!!!! WHY??

I noticed also that ICS stock ROM installed without the Lock Screen, strange!!!

Is there any explanation of what my phone is doing?

Thanks a lot for your efforts hg42, you rock :)

Mohamed
[Galaxy Note GT-N7000 General] hg42:
now does the imei/keystr fix change that?

Please look what's in the file before changing it.

Make a backup.

If the file was changed by something, there may be other files with wrong content etc.

You could make an efs backup and try flashing xxkl8-efs image. If that works, find the difference file wise, by copying file by file from the backup.

But depends on how reproducible the errors are.
[Galaxy Note GT-N7000 General] forest1971:
Hi Mohamed,

Should also consider to use trick recommended by Mario in the post above. It seems to help fix the problem of lock screen which is also related to efs. And how about using gb and cm9 rom? They should be more stable than ics. Cheers.

Sent from my phone
[Galaxy Note GT-N7000 General] hg42:
I still don't get, why all those emmc bricked people still install stock ics...(unless they also immediately install a safe kernel).

I think, "stock ics" and "wipe" should never be mentioned in one sentence unless it is a strong warning :)

When I say a known(!) good ROM, I usually mean cm9 or sonething like that.

There is a big community testing these and usually all issues are known, so you can easily identify the problem.

*AND* there is source for it, so you and we have a chance to find out what's going on.

Well, stock ROMs are known to the community, too, but there is a lot of guesswork around them, much lesser certainty about the reasons.
[Galaxy Note GT-N7000 General] forest1971:
Agreed. I find ics consume more ram, more battery and not to mention the brick bug and many other issues that users reported almost everyday in the forum after upgrading from gb!

Sent from my phone
[Galaxy Note GT-N7000 General] MohElShafei:
Dear hg42 and forest1971,

I'm really extremely happy that you answered me that fast. You are SGN heroes. Thank you really for your continuous support and for everything you do for us.

I was really shocked that EFS could be the reason for doing these errors, I'm wondering if it could freeze the device and hangs it!!. I lost my IMEI earlier and I'm working with the Generic IMEI after flashing the stock XXKL8 EFS .tar file. Is the Generic IMEI can cause the device to hang and Force Close on stock ROMs or on any type of roms?

[*]Do you think that if I fixed my IMEI with my original one (using ZX box for example), all errors, hangs, and freezes will disappear

I thought that after repartitioning the SGN and avoid the bricked blocks, I can install any ROM I like, even the stock ones; but it appears that I'm wrong

[*]Are the bricked devices will never be normal even after avoiding the bad blocks?

Usually all wipes I do are done from the 4pda_kernel or CM9 safe kernel, then I install any rom after that. Never wipe from ICS kernel, even the cooked ones

Stock GB rom was semi-stable, some times it works fine; others it shows FC and hangs.

Currently, I'm on the CM9 latest rom for about 20 hours with no FC or freezes. Will report in two days if I faced any further errors.

Thanks again for your terrific support, and wish you a wonderful day :)
[Galaxy Note GT-N7000 General] kontdracula:
HG42 i want to ask something.

Here i spoke with phone repair centers , also who made it on his own, they can repair this brick in 1 day with a box named Jtag and it has a price, also i see a video on youtube about this you can search as "galaxy note brick repair" the first video with jtag , is it possible to repair all emmc(without any bad block)(the state before bricked) with these boxes(JTAG)?

Thanks so much HG42 for your hard work , now my SGN is alive :)

I followed this steps..

1-)I selected patched Pit file From PIT(Make sure repartition selected)

2-)Selected last stock ICS from PDA section.

-And flashed it did not stuck on factoryfs.img and phone opened.

3-)Then to make it safe i flashed notecore v13 kernel with ODIN

---------- Post added at 10:20 AM ---------- Previous post was at 09:58 AM ----------

Also i want to say that before applying patched PIT , i had to backup my internal sd , so i searched and find a good solution in the xda ,it is a CWM program named "[CWM-APP][1.01] AROMA Filemanager :: 120810-003 :: Open Source", i opened the app with CWM and easily backed up all my files(7.5gb) to external sd.it will be usefull for bricked users who wants to backup his/her pictures,musics,saved game datas etc.. to external_sd.

---------- Post added at 10:28 AM ---------- Previous post was at 10:20 AM ----------

1 important detail for Backing up internal_sd , before openin the aroma file manager , i went to CWM advanced settings -->mount and storage --> mount emmc after this selection Aroma file manager see my internal_sd files.Please be sure that you use the last version of CWM.
[Galaxy Note GT-N7000 General] hg42:
If I have time to write...but this differs extremely

oh, I remember now...unfortunately I don't know much about the efs partition.

don't know, but from I read these files are really "precious" (finical?).

could be possible, but I assume only some weird things would go away

if the bad blocks are really circumvented (don't play any role no more), this should be the case (at least in theory).

For my PITs, all partitions have the same size and the partition number. Nearly all kind of software will not know they are moved to another place (and also are not interested in this information).

That's the theory. I for myself am flashing often, but mostly cm9 or derived ROMs, I never had a stock ROM on my Note after the brick.

So I didn't test it. But it seems there are several people where it works.

But as I said in one of my last posts, I guess the brick could also behave very strangely. May be I am only one of the very lucky persons, where the brick behaves calculable.

at least my Note behaves absolutely normal. I never had any difference to the behavior before the brick.

this could(!) be because of memory usage etc. If there really were that strange behavior I am thinking of, it would be completely random.

The wear leveler assigns bocks to write requests, so sometimes bad blocks might be assigned and you would get a freeze because of that.

Also the file would probably be corrupted afterwards and should freeze every time it is accessed.

then, this would argue against the "strange behavior" theory
[Galaxy Note GT-N7000 General] hg42:
I don't have any knowledge about JTAG from my own experience.

Please note the difference between brick and *emmc* brick.

I never found a video of an emmc brick repair, did you? Then please give me a direct link.

It seems like it is possible to repartition with JTAG, so it might also be possible, that this isn't a real repair, but also another work around by repartitioning and I heard of such before.

That said, it should also be possible to reinitialize the flash chip by JTAGging to it.

The chip should be completely(!) empty afterwards (no boot loader etc.). So saving the whole phone contents and restoring it afterwards should be mandatory.

If I remember right from somewhere on xda, Samsung had already considered to give us a procedure to reinitialize the chip by software but canceled that, because you can't handle a completly emty flash chip after that without JTAG. May be these guys have access to such a procedure?

so, you are one of the guys for which the method worked? no flaws since then? please keep us up to date...

May be others could also post their experiences, if the phone worked like a charm afterwards?

From all the late posts I get a feeling the method doesn't work for most, I really hope it's not this way...

I already mentioned it in the OP:

anyway, thanks for reporting success
[Galaxy Note GT-N7000 General] hg42:
To clarify something:

tannykim and others say something like

I don't instruct to install the final ROM via Odin:

For unexperienced users, I offer two ways in bold letters, one with Odin and one with Zip flashing.

However, the flashing to find an unbricked area goes via Odin because it's faster that way. This doesn't mean this has to be the final ROM.
[Galaxy Note GT-N7000 General] ZiDanRO:
Let me say that JTAG will not repair emmc brick. I have JTAG boxes Riff and GPG Jtag Pro and they will not repair this. Only the boot sector.

When I am repairing a phone always I put GB stock and Speedmode kernel (Note or S2) and I never had a problem. No freeze or hangs or power button problems. And I never had to repair first the EFS partition.
[Galaxy Note GT-N7000 General] kontdracula:
I can still using my SGN without any problems like in the old days :) thanks again HG42 ..

i also find a post on ebay , who gives JTAG service here is the post:

""""ATTENTION: Lately I've received several Galaxy Note and Galaxy S2 phones that had the internal memory chip dead (EMMC CHIP) because of flashing kernels with the EMMC BUG that kills the CHIP, this phones are unrepairable and I can't refund the money paid if I receive a phone bricked this way."""""""""""""

""""""""""Please ensure that the phone is not bricked because of hardware failures before buying my JTAG Service...""""""""""

because of this, if anyone had emmc brick they have two options, First one is trying HG42's PIT method , other one is to change the motherboard from guarantee or service.
[Galaxy Note GT-N7000 General] MohElShafei:
Thanks hg42 for your interest and for your replay .. Till now, almost two days with no freezing or hangs with my SGN running the latest CM9 rom and with the following partition structure:

I have never stayed that long with any ROM after the brick without getting errors, hangs, or freezing. I'm very optimistic that this time my SGN will work fine. Wish me luck :) :)

Will report after a few days with the situation.

Mohamed
[Galaxy Note GT-N7000 General] tannykim:
Could you please share your process with me?

I am still have issue with freezing and restart....

Thank you
[Galaxy Note GT-N7000 General] hg42:
I edited the thread starter:

* cleanups, e.g. removed "Update:" from sections

* changed some texts to be more general for multiple devices

* added section about partition scanning/checking and my emmc partition scanner
[Galaxy Note GT-N7000 General] tannykim:
Here I am again......

I did all possible solution to bring my note back as like before the BRICKED......

I did all step again to find better spot to install Rocket Rom V10.

I check with EMMC partition scanner and result was good. [I was expecting to have better than last attempts...

I flash CM9 safe kernel to flash Rocket Rom V10, I did clean install [wipe the data/system/cache...].

However, I still have issue with force to close and re-start and freezing....

I believe emmc block is not the only issue with my GN.

I am not expert so I can not go further
[Galaxy Note GT-N7000 General] hg42:
I am thinking of changing the emmc partition scanner to do an endlessly repeated check (or create a once-only and a continuous version), so we can let it run for a long time without manula interaction.

This might catch emmc brick effects only occurring sporadically.
[Galaxy Note GT-N7000 General] hg42:
Please look at the updated emmc scanner thread (first post).

I added three more tools (indefinite scanner, and brick finders for start and end).
[Galaxy Note GT-N7000 General] hg42:
@raakaa, searching for a FACTORYFS for flashing in Odin

take this for example:

$ unzip -l /media/windata/import/android/samsung/galaxy-note/stock/N7000XXLC1_N7000OXALC1_OXA.zip

Archive: /media/windata/import/android/samsung/galaxy-note/stock/N7000XXLC1_N7000OXALC1_OXA.zip

Length Date Time Name

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

0 2012-03-14 20:26 N7000XXLC1/

906741844 2012-03-13 11:23 N7000XXLC1/CODE_N7000XXLC1_CL1003701_REV02_user_low_ship.tar.md5

11468864 2012-03-13 11:27 N7000XXLC1/GT-N7000-MULTI-CSC-OXALC1.tar.md5

12585032 2012-03-13 11:26 N7000XXLC1/MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5

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

930795740 4 files

The CODE_*.tar.md5 is the FACTORYFS

There are also other stock ROM updates (single file), which include more than FACTORYFS in one file:

e.g.

$ unzip -l /media/windata/import/android/samsung/galaxy-note/stock/N7000XXLPY_N7000OXALPY_DBT.zip

Archive: /media/windata/import/android/samsung/galaxy-note/stock/N7000XXLPY_N7000OXALPY_DBT.zip

Length Date Time Name

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

999823437 2012-05-04 08:04 N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.tar.md5

276480 2012-05-04 07:58 SS_DL.dll

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

1000099917 2 files

the tar.md5 (which is a tar file, with a checksum attached after it) contains:

factoryfs.img

zImage

hidden.img

modem.bin

cache.img

You can use this tar in Odin (in PDA), but it flashes more than factoryfs.

This will not harm, but it's inefficient if you are searching for a good PIT (e.g. in the big-bricked line of PITs).

So I would first use one with a .tar.md5 for only FACTORYFS.

After finding the right PIT, you can use any ROM you want (but don't forget to format/wipe).
[Galaxy Note GT-N7000 General] kontdracula:
I was using the the 16gb_standart_patched_PIT file , now i tried regain method 1 by 1, i gained 1GB :) now i have 2GB DEAD ZONE..