yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] MohElShafei:
First of all I would like to thank you so much for your help and for your great support helping others fixing the Note brick issue.

Unfortunately, I just bought a Note phone 3 days ago and I got bricked! ,, I'm so disappointed really and I tried the method you described very carefully but with no luck .. every time I try to create the DATAFS partition an error appears (like Error: Input/output error during write on /dev/block/mmcblk0

Retry/Ignore/Cancel?) I tried to use the partition table you advised (starting from 4215 6362) but with no luck at all.

I can install any ROM from ODIN or recovery .. but every time I do that the installation completes but it stuck on Samsung Logo.

Now I'm out of warranty, an I heard the Samsung are working to fix this issue. Do you think I should go and replace my Motherboard, or wait for Samsung solution, or what do you think the correct discussion here?

Thank you a lot.

Regards,

Mohamed ElShafei
[Galaxy Note GT-N7000 General] hg42:
@Mohamed

looks like you used parted?

Please try the method at the end of my first post after flashing the patched-standard PIT:

* Flash a known good ROM via Odin (especially not one of the faulty ICS ROMs)

* reboot into recovery (just hold Vol-Up + Home + Power until you arrive there)

* wipe cache

* wipe data

* format internal SD (first remove the external SD, to be sure you are handling the internal SD)

sounds like you missed the wipe steps after flashing via Odin.

From what I read, many have used their warranty for repair. But I think you have to remove all traces of custom ROMs, kernels, recoveries etc. Especially reset the flash counter if you have the yellow triangle. I am sure you'll find a lot of info how to do that.
[Galaxy Note GT-N7000 General] Shanava:
Hi hg42

Thanks a lot for release good method for repair bricked n7000

i have exactlly problem via i9250

phone stop flashing on "userdata" via odin and error when flashing by "galaxy tool kit"

Any way,Can i Ask for make patched .pit file for I9250...?

Please work on and make good .pit if you have free time....

or maybe, if you can tell me ,how can i edit and make i9250 .pit file...

Thanks Advance

here is orginal pit for i9250:
[Galaxy Note GT-N7000 General] MohElShafei:
Sir, thank you very much for your interest and for your reply.

I followed the steps you advised, but it stacked at the Samsung Logo too .. what do you think?

BTW I bought the phone without a warranty, so I can't fix it from SAMSUNG .. Do you think I should wait for a fix from SAMSUNG as they said before (they said soon they will release a bug fix in the next rom)? or I go and replace my motherboard?

Thank you so much.

Mohamed
[Galaxy Note GT-N7000 General] MohElShafei:
I saw this video:

http://www.youtube.com/watch?v=d0SX3iDuIZc

I don't know if this method will fix our bricked devices or not.

Thanks.

Mohamed
[Galaxy Note GT-N7000 General] hg42:
From what I know this JTAG solves issues where you are unable to flash your device, because e.g. if your boot process is boken very early (no download mode, no recovery).

Soms kind of JTAG process could be applied to the flash chip, too, I was told, but would be too expensive. So changing the motherboard is cheaper.

I am not up to date according the samsung fix, the last thing I read was a fix to the kernel, so it would no m9re brick our notes, but no repair of the flash memory.
[Galaxy Note GT-N7000 General] hg42:
2

did you scan your partitions with dd?

It all depends on where your bricks are located.

If you have bricks in your ums partition, you need one of the ums pits, but you should know more exactly which areas are damaged.

The problem is, you need a contiguous area with no brick inside at which you can place the three partitions.

You can flash the stock PIT and use dd to find the sane area:

dd if=/dev/block/mmcblk0p11 of=/dev/null bs=1024M skip=X count=N

with X and N you can control which Gigabytes (bs=1024M) to scan. With X=0 N=12 you would scan the whole ums.

Start with X=11 N=1, then change X to 10, 9, ... until dd fails.

"Fail" means, dd doesn't find an end. Unfortunately it doesn't tell what it does.

But you learn from the first try, how long you have to wait (allow at least 50% tolerance).
[Galaxy Note GT-N7000 General] jayaka:
Hello

I followed each step at your first post. After using a Pit file from the zip (I've tried all of them 1 by 1) i realised that i cannot do wipe data /factory reset. The phone waits too long and at the end it restarts. If i use a regular pit file, wipe data/factory reset is available.

I used another pit file for ums brick. Then i wipe data/factory reset and flashed a cm9 rom. it runs since yesterday without any problem, right now i have a fc and phone restarted.

I tried wipe data / factory reset with stock GB kernel, abysse kernel and thor kernel. all without any succes.

I also used Odin as well as heimdall to be sure that it's not because of heimdall ;)
[Galaxy Note GT-N7000 General] hg42:
sounds like a bricked block, where the data partition is located after repartitioning, so if you used patched-standard PIT, this would be in the former UMS.

regular = stock? or = patched-standard?

from my own experience I never got a fc from bricked blocks, so this might be another problem.

I assume this relates to the patched-standard PIT (or regain PITs), right?

Then, you should try the ums PIT, which already worked, then flash your ROM or kernel via Odin, then wipe data + wipe internal sd in recovery.

If you only flash a kernel you should also "format system".

hmm, may be a wipe data doesn't do a format all the times / in all recoveries?

Then "format data" should be better.
[Galaxy Note GT-N7000 General] jayaka:
hello

Yes, not being able to format /data is only after i flashed patched or regain PIT.

I've tried UMS pit (16 gb, 1048576 kb) and everything went well. Although i had once a fc, as you said it could have been because of an app rather than the brick issue since after a restart everything works fine. I m on cm9 based android rom.

Thank you very much for your help and patience ;)
[Galaxy Note GT-N7000 General] hg42:
that's fine, good luck...

Summary:

after flashing a PIT:

if any of these hangs

* flashing a ROM via Odin/Heimdall

* installing a ROM

* wipe data

* wipe internal sd

then use a PIT with a higher start address

from low to high:

* regain-high,...,regain-low,standard,ums-low,...,ums-high)

so e.g. if standard hangs, use ums, then higher ums etc.
[Galaxy Note GT-N7000 General] hg42:
if I find some time, I'll see what I can do.

May be this weekend...but not sure
[Galaxy Note GT-N7000 General] MohElShafei:
Thank youuuuuuuuuuuuuuuuuu

Dear hg42,

I can't find words to thank you for the efforts you did to me .. finally I can't tell you how happy I'm .. after 3 days non sleep, , my Note starts :D :D :D

I did the following steps:

1. Start the Download mode, then from Odin I flashed the PIT file (Q1_20110914_16GB-patched-ums-bricked+7864320-kB.pit).

2. Start the Download mode again, then from Odin I flashed the (4pda_kernel.tar) kernel.

3. Go to the Recovery mode, then flash the (cm-9-20120621-NIGHTLY-n7000.zip) ROM.

4. Format Cash, Data, and SD Card.

5. Restart the phone.

6. WOW .. unbelievable ..The magic comes true and the phone just starts :) :) :)

My problem is that the internal memory is only 1 GB almost .. Now I have a few questions ..

1. Can I repeat the above steps and try another PIT file with more internal space .. or it is-not recommended and it is better keep the situation as it is now (I doubt it can start again).

2. Can I install any ROM now, or because the CM9 rom is small in space it is better to be used now ,and hence if I kept the situation as it is, I will live all my life with the CM9 rom only?

3. Can I install (XXLC1_CheckROM_NoteHD_V6.zip) rom, or it will not boot.

Thank you so much for your help, I believe I will stay as I am and buy a bigger SD Memory Card, and wait for a fix from Samsung, or I will replace the motherboard in the future.
[Galaxy Note GT-N7000 General] hg42:
wow, I didn't even know, that this high number (7864320) really works...

:-) yes, it's probably not the optimum.

I thought people with bricks in former ums partition for which the patched-standard PIT doesn't work should use the ums PITs this way (but didn't try anything):

* start with the ums PIT with the lowest number
===loop
* flash PIT
* flash any FACTORYFS via Odin
* if that hangs in Odin
* press [Vol-Down]+[Home]+[Power] until in download mode again
* Odin will notice that and be ready again
* get next higher PIT
* restart at ===loop
* else (if FACTORFS flashed ok)
* goto recovery mode
* wipe data
* format internal sd
* if any of these hang
* get next higher PIT
* restart at ===loop
* else (if anything was good)
* hurrrrray! your phone should work now
* install a known good ROM now and try some days

because a FACTORYFS is bigger than those 0.5 GB steps, it will check if each area is ok. If it was ok, the rest is still unchecked, so wipe data and format ums will check this in the next step.

you can, but what I described above is a little bit faster

As I wrote in my first post, with all partitions at non bricked places you will not notice a difference, you just have a smaller ums partition (just buy a big sdcard!). But one thing, you should avoided flashing any stock PIT. If it is really needed, then you need a new patched PIT.

I think so, but I don't know the ROM myself, so just try, you can always go back if it doesn't work.

But I would recommend to first use a known good ROM until you know your partitions are all in sane areas.
[Galaxy Note GT-N7000 General] MohElShafei:
I tried all other remaining .PIT files but with no luck .. add to that that the device freezes most of the time and didn't accept neither Kernel or anything from Odin, I don't know why .. Now I'm trying to go back to what I was before and stay with CM9 at least .,. wish me luck.

i managed to get it back .. finally .. I WILL STAY AS I AM ..:angel:

Just a question .. the second time I tried to install the CM9 ROM, the device refused to install it from the 4pda_kernel.tar kernel .. always showed an error .. why I don't know .. I was disappointed .. I couldn't even install it back .. then I tried another kernel (thor-kernel-v0.14-BURN-GNOTE.zip), and from there I managed to install the CM9 ROM again .. thanks to GOD.. It is really a hard process and made me really very extremely tired .. sometime I feel that I can manage things and everything is under control .. then after a second .. I found myself unable to do anything !!!

I will stay as I'm for a week or two .. then maybe i can try it back.

thanks a lot for your patient and for your support.

Mohamed
[Galaxy Note GT-N7000 General] hg42:
After a hanging Odin I always managed to restart the phone by pressing the three keys for download mode.

May be after a freeze somewhere else you have to power off the phone by removing the battery. Else the eMMC seems to not work correctly if at all.

hmm, no question in there?

Which error did you get?
[Galaxy Note GT-N7000 General] MohElShafei:
Dear hg42,

I can't found words to thank you for your continuous support, I was really extremely disappointed and really with no hope at all that the phone would start again one day, but after your instructions, it works finally. Thank you a lot :)

Now finally I managed to get the system works with the following specs:

1. cm-9-20120622-NIGHTLY-n7000.zip ROM .. For anyone you can get it from here.

2. The only Kernel that worked with this ROM was thor-kernel-v0.14-BURN-GNOTE.zip, I used several kernels but no one works like this one.. I used the following kernels with no luck, I don't know why .. do you have an explanation?:

4pda_kernel.tar - it didn't boot the ROM and stuck at Samsung N7000 Logo.

speedmod-kernel-n7000-ics-k3-3-Odin.tar - it didn't boot the ROM and stuck at Samsung N7000 Logo.

cm9_safe_kernel.tar - Works and make the ROM boot, but the Wireless was disabled.. I don't know why.

Question: What is the Kernel and the ROM you recommend? In addition, can I install "Litening ROM Note v2.0" from Odin without problems?

3. I used the Q1_20110914_16GB-patched-ums-bricked+7340032-kB.pit file and it worked well. Now my space is 1.25 GB when I connect my Note to the PC.

Thanks to GOD then you, my Note finally works :victory:. I took a long time to understand the bug in the Odin flashing (sometimes it freezes and the fix of it is to restart the phone while it is connected to the PC), this bug made me go crazy trying other .PIT files, because sometimes I was able to flash the PIT file, then the moment after that I cannot flash a kernel .. even when I tried to go to the configuration that worked with me .. it didn't accept.

I believe I will give it another try but not today or this week at all .. I'm done .. and I'm extremely tired .. three days non sleep :crying:, but for sure I learned a lot.. i was flashing any ROM without reading for all my previous android phones, but really SAMSUNG was a shock to me doing this bug .. a device 600$ price with this bug .. SHAM ON YOU SAMSUNG :mad: :mad: :mad:

Final question, what is the price of replacing the Motherboard, I can manage send my phone to a friend of mine lives in USA, what do you think would be the cost of changing the motherboard?

Thank you a lot .. you are the best.

Mohamed
[Galaxy Note GT-N7000 General] MohElShafei:
Update ..

It looks like I will never stop ;)

I managed to flash the (Q1_20110914_16GB-patched-ums-bricked+7340032-kB.pit) file .. then installed the (speedmod-kernel-n7000-k2-12-Odin.tar) Kernel from odin .. and from there wiped Cash, Devl, System, Data, and SD Card. Then finally flash the (KingDroid_ICS_NoteMania_Edition_v3.0.zip) ROM ..

Now my Note runs this ROM and works like a charm :cowboy: .. just I wanted to update you with the progress .. :good:
[Galaxy Note GT-N7000 General] asafki:
It Fixed mine!!!

Thanks a lot!
[Galaxy Note GT-N7000 General] prakashraobs:
Thanks

Hi HG42,

I don't have any words to say except a very big thanks. this thread has helped me a lot.

Good explanation to re gain the internal memory.

this thread really bought my SGN working.

now searching for binary count reset and hoping for solution from Samsung to regain full memory.

Thank you once again.:good: :D

P Rao
[Galaxy Note GT-N7000 General] rraaka:
i still get goosebumps when i go through this thread. best thread of community IMO.

thanks to all who contributed....
[Galaxy Note GT-N7000 General] hg42:
I looked into this today.

Your PIT is very different.

Which partitions are usually damaged by the brick?

Where do you have bad blocks?

Generally I don't know anything about your phone.

Especially the partition sequence is much different, I have no clue how a patched PIT would affect other partitions.

PIT file partition-table-0915.pit

id	offset	size	name	filename
0	0 kB	0 kB	gang	emmc.img
1	0 kB	0 kB	gptder	partition-table.img
2	0 kB	0 kB	xloader	xloader.img
3	0 kB	0 kB	sbl	sbl.img
4	4096 kB	20480 kB	efsory	efs.imgimg
5	24576 kB	8192 kB	param
6	32768 kB	4096 kB	misc
7	36864 kB	4096 kB	dgs
8	40960 kB	8192 kB	boot	boot.img
9	49152 kB	12224 kB	recovery	recovery.img
10	61440 kB	16384 kB	radio	radio.img
11	77824 kB	669696 kB	system	system.img
12	747520 kB	442368 kB	cache	cache.img
13	1189888 kB	15587328 kB	userdata	userdata.img
14	16777216 kB	0 kB	efs-cdma	efs-cdma.img
15	16777216 kB	0 kB	radio-cdma	radio-cdma.img
16	0 kB	0 kB	bootloader	bootloader.img
17	61376 kB	64 kB	metadata

I am especially puzzled by the partition-table.img and those partitions following userdata.

Sorry, I think, you should better use parted method (like user forest1971).

Or you find someone, who knows your phone and understands it's PIT.

I can help with what I know, though.
[Galaxy Note GT-N7000 General] levis333:
Man U r GOD!!!

YOU resolved our biggest problem. i can't say enough THANK YOU 4 this.THX, THX AND AGAIN THX.

GOD BLESS YOU 4 this post. :D:D:D
[Galaxy Note GT-N7000 General] MohElShafei:
Hi hg42,

I was giving my Note another chance by trying re-partitioning the internal memory, but I noticed the following issues that I didn't understand.

1. When I try to create more than one partition (one after one) always I got an error in the second creation process, error that shows it is a damaged part.

2. If I created a partition, then restarted the phone and logged in the Recovery mode again, then created the second one (in the same place that displayed an error before), the creation process continue without errors!!!!!! why?

That made me crazy, because sometimes a sector shows an error, another time the same sector shows that it is clear and fine!!

Notes:

I always flash the (4pda_kernel.tar) from odin, then go into the Recovery mode.mode.

I always delete all the partitions that I will change first.

Do you have an explanation? .. also if I want to delete partition 8, and create it again knowing that it has no file system, what is correct command for that?

Thanks,

Mohamed
[Galaxy Note GT-N7000 General] hg42:
I think any access to a bad block locks up the whole flash mem, so any further mem operation fails afterwards. As it seems, the software need not freeze everytime.

a restart unlocks the flash.

help

...

mkfs NUMBER FS-TYPE make a FS-TYPE file system on

partititon NUMBER

mkpart PART-TYPE [FS-TYPE] START END make a partition

mkpartfs PART-TYPE FS-TYPE START END make a partition with a file system

...

[Xxx] means optional

So

mkpart ptype start end

creates a partition without file system
[Galaxy Note GT-N7000 General] MohElShafei:
Thank you sooooooooooo much .. Now I understand that if I faced any freeze/luck/hangs/error during the creating of any partition .. I should stop everything .. restart the phone .. then try again :)

Thank you

and for Partition 8, ptype is Primary .. correct?
[Galaxy Note GT-N7000 General] hg42:
I think the chip locks up and if some software unconditionally waits for a block (which is reasonable for a memory device) it freezes. Some software might detect an error and goes on.

E.g. on my sgn the emmc check app continues the scan but doesn't increase the counter.

Why do you handle partition 8? Anyway, I think they are all primary.
[Galaxy Note GT-N7000 General] thasadar:
problem solved = new problem

I want to thank you for helping me solve this issue with my note; I just got my Note back from service , it got a free motherboard change. Reading over the forums that this bug is still present on other samsung galaxy devices runing android ICS ( galaxy S2 for example) I have told myself I will stay put in regards of flashing a custom ROM until this situation is settled.

I have rooted my Note but found someting suspect on my internal storage;

It seems I am missing around 400MB from my internal storage. So this is what I did:

I installed a custom Storage analyzer and compared the results with the stock space analyzer.

And this is what I mean:

I haven't seen this before and I was wondering that is happening with these 400MB?!

Exactly this part is missing from my Android built-in Storage analyzer although it's marked as free on the installed Storage analyzer.

How can I recover that ?!

I know it's not much but I don't like the fact that 1/4 of my internal storage is "stuck" somewhere and is not being used.

Could you please offer some insight?!
[Galaxy Note GT-N7000 General] hg42:
however, in this case a custom ROM might be safer...unless you stay on GB.

Samsung didn't fix their ICS kernel, yet, but all important custom ROMs did.

If flashing a custom ROM, please first flash a safe kernel via Odin.

At least dalvik cache is located on /data, so this might be the "system"-data block. You probably cannot get this back...
[Galaxy Note GT-N7000 General] thasadar:
I know it's a mater of taste and preference but what main Note ROM would you recomend? I am looking for stability before everything... and from my experience ( before I bricked my note) I got to play around with 7-8 custom ROMS but each had their game-braking faults ( black screen of death/not resuming from standby, insane battery consumption,crashing core apps etc.)

Do you know something that is as stable as the stock ROM?

Now that is bad! Because I just got this fresh out of service like "this". and I do mind missing almost 500MB . The factory reset option from the Settings menu should wipe and reset the device right?!

And with wipe a good chance to get that back...or?!
[Galaxy Note GT-N7000 General] hg42:
for my usage CM9 is best, but no fancy gimmicks, instead a clean interface.

Stable for me, but I do NO gaming.

dalvik cache would be recreated, e.g. mine is 100MB.

It depends on what is gathered in "system data".

My "Storage Analyser" app shows a detailed list of who uses what, and I can go into each section.

Which "Storage Analyser" did you use? can't you click on the "system data" area?
[Galaxy Note GT-N7000 General] theunborn:
still stuck...even worse now..

hello,

Im new here

I've been upgrading to ICS from the official update which is N7000DXLP9-----------------------2012 May-----------N7000OLBLP6-----------Indonesia from http://xdaforums.com/show....php?t=1424997

it works great, until I see some red frame around and tried to fix it by going to buildprop and editing the buildtype from dev to user (what I found on the internet), but then I found out that mine is already user so I tried changed it to dev and when I restart, the phone stuck on samsung logo,but I am still able to go to recovery mode,the problem is I cant get odin to flash any rom to my note, it always stuck at factoryfs.img. then I installed abys kernell to wipe my factory reset, cache, dalvik, then I started to flash with odin again, with the patched pit file I got from http://xdaforums.com/show....php?t=1667886, and the official update from http://xdaforums.com/show....php?t=1424997, suddenly it works, and I tried to restore data from CWM ( stupid me)....turns out it got back again on the logo samsung and stuck there and so i tried flashing again and it started to stuck around factoryfs everytime, I tried to use abyss but this time after I wiped everything and used the patched pit file like before, it still stuck, so I found a post from the internet, it was custom ICS, i forgot where i got it but i have the file if you'd like to know, and so i tried, then it leaves me with my counter started to count 1 and still stuck at factoryfs....and I cant even go to recovery mode now, I have tried USB JIG and I succeeded to turn the counter back to zero but still stuck at factoryfs.img and still cant go to recovery mode even through bootloader,..... please help! i love my gnote
[Galaxy Note GT-N7000 General] hg42:
If you installed this unsafe ics rom both times, you have probably bricked your revived gnote again.

So you loose another memory area.

First you should read about the whole emmc brick thing until you understand what it is.

In this case: restore will also wipe first -> brick

Generally don't use stock rom without flashing a safe kernel first!!!

To revive your phone again, first take a ums pit with a number around 3GB. Follow instructions at end of first post.

Install the ics rom along with a good kernel, e.g. a recent franco kernel. Never wipe or cwm restore on top of a stock kernel.

If that works, use "emmc check" app to scan your flash completely. If it stops at some count, you have the brick.
[Galaxy Note GT-N7000 General] garwynn:
@hg42, forest,

In order to build a custom .PIT for the Epic 4G Touch what would you need?

I'm guessing a current .PIT as well as a dump of each partition, starting position and size.

Reason being the proverbial cat is out of the bag and users are restoring E4GTs using the Note modified .PITs. This takes out half the memory whereas I believe our tests indicated that it can be done by simply avoiding the current /data block on our device - 2GB. And if people are going to use this we might as well do what we can to help at this point. (There are enough people not covered by warranty or free/cheap repair that interest has reached a point of use now.)

I'd appreciate any help you could offer. Thanks in advance.