yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] ahenderson223:
To be honest i tried so many different things i tried the pit file with odin then used odin to load a stock rom and my note works again b4 this nothing would work i could get into download mode flash abyss but could not load a rom now it works i lost about 7gb of internal memory but im happy it works again
[Galaxy Note GT-N7000 General] hg42:
hmm, from what do you read that number? Do you mean the size of your internal SD?

no...

let me summarize it:

* you have a phone with 16GB internal flash memory

* roughly 5 GB are used for internal partitions like /system, /data, modem, recovery etc.

* the rest of it is made available to you as internal SD (about 11 GB?)

* you bricked your phone, which damaged some blocks somewhere from the 3. to the 5. GB

* my "standard" PIT simply skips these 3 GB in the partition scheme (by not placing a partition there), so the bad blocks are not used by android

* e.g. the 1024000 PIT skips only 2 GB, so 1 GB at the end of the former data partition will be regained.

this is the opposite direction...

you would loose for example 1GB more than the standard scheme. This is only for people whose bricked blocks are not skipped by the my standard PIT, because they also have bricked blocks in the former UMS partition.

So these people need a bigger hole in their partition table.
[Galaxy Note GT-N7000 General] nuramohammed26:
I appreciate the work of Hg42 more than he realizes.thanks alot. I have read all the posts twice some 4 or 5 times but still i have a bit of a problem,my SGN came back to life:D but each time i start downloading apps from the market, the phone will freeze,if i am transferring files from my PC to the USB storage it will start normally but it will freeze halfway especially when the files are large.when am using the browser after a while the phone will also freeze,i only use N7000DDLP8_N7000ODDLP5_N7000DDLP4_HOME.tar.md5 to flash.so please kindly tell me what am doing wrong because after flashing if i enter recovery mode i don't have the option of formatting /system or /data,and i always get 9.21GB.THANK YOU
[Galaxy Note GT-N7000 General] hg42:
with my provided PIT files it should be max. 3GB (exact: the size of the former factoryfs and datafs together).

Most people seem to think they should have an internal SD of 16GB?

This is not true, they get the remaining size after subtracting all those other partitions.

Partition scheme before implementing the workaround:

Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
...
9 281MB 1174MB -->893MB<-- FACTORYFS
10 1174MB 3322MB -->2147MB<-- ext4 DATAFS
11 3322MB 15.2GB --->11.9GB<---- fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN

so you will loose 893MB + 2147MB with my "standard" patched PIT (without a number), these will not be used afterwards, as they may contain damaged blocks.

Here the numbers from the PIT (stock and patched without a number):

16GB original (Q1_20110914_16GB.pit)

FACTORYFS 548864 1744896 ->Fs
DATAFS 2293760 4194304 ->Ds
UMS 6488064 ->Uo 23232512 ->Us
HIDDEN 29720576 ->Ho 1048576

16GB MMC_CAP_ERASE brick fixed

FACTORYFS 6488064 =Uo 1744896 =Fs
DATAFS 8232960 =Uo+Fs 4194304 =Ds
UMS 12427264 =Uo+Fs+Ds 17293312 = Ho-(Uo+Fs+Ds)

these numbers are in 512 Byte blocks:

UMS was 23232512 (Us) = 11895046144 Bytes = 11.9 GB = 11 GiB
UMS after 17293312 (Us-Fs-Ds) = 8854175744 Bytes = 8.9 GB = 8.2 GiB

(with GB = 10^9 = 1000*1000*1000 and GiB = 2^30 = 1024*1024*1024)

so you loose exactly 11895046144 - 8854175744 = 3040870400 Bytes

or simple 11.9 GB - 8.9 GB = 3 GB
[Galaxy Note GT-N7000 General] FARSHOOD:
dear sir i am confused and i have some questions

1- is my note healthy now and will work healthy after now?

2-how much capacity i have lost?

3-why i could not to gain sd by your standard patch and succeed by 1024000 pit file is it any difference which pit file to select to reach better gain or selection of all pits included has the same and 1 constant result?

4- would you please describe how many memories are included in n7000 i think there is 3 memories: 842 mb for rom installation and another 2gb for system activities and 16gb sd for programs installation and storing medias like music videos photos?

5-before 16gb internal sd damage i always saw the amount of that before installing any program= 14.9gb but you say 11gb, there is a screen shot of my present sd capacity i did not installed any program would you say what is miscellaneous files on that picture and why when i delete that 1.5gb files after deletion why it returns back and show again the already amount why can not to delete it ?

Thanks so much
[Galaxy Note GT-N7000 General] hg42:
this normally goes to a download folder on the UMS partition ( aka. internal "SD", or may be to your external sdcard depending on your browser configuration)

this also uses the UMS partition or the external SD

the cache for the browser is usually placed on UMS, too.

Assuming it's the UMS in all three cases, I would conclude you have bad blocks in your UMS partition.

That's a little bit more complicated than having the bricked blocks only in /system and /data, because the UMS is much bigger and you have to determine which part(s) of the UMS can still be used.

In a worst case scenario, for a workaround by simply repartitioning, you would need at least enough space to place the /system and the /data partitions somewhere.

The general idea in repartitioning is to place all partitions in the correct sequence and correct sizes (except UMS, which gets a different size).

This way all standard procedures work like before.

e.g. /dev/block/mmcblk0p9 doesn't change it's partition number (as the sequence is retained) and flasching an image to it still works because the size is also retained.

The UMS partition's size doesn't matter, because nobody assumes a specific size for it. 1. UMS is user land. 2. UMS also differs between 16GB and 32GB SGNs.

hmm, isn't that an ICS ROM? then please don't flash anything in recovery or wipe anything anywhere! You will probably get a second brick.

When still on ICS you could flash a current speedmod kernel via Odin(!) (this kernel has MMC_CAP_ERASE disabled, but it's not really sure if that's enough to be safe).

Use PC Odin, because other ways use the critical kernel.
[Galaxy Note GT-N7000 General] brockyneo:
I have a total space of 11.07 gb does this mean I have bad blocks sorry totally novice with this
[Galaxy Note GT-N7000 General] hg42:
no

you wouldn't see bad blocks in those capacity numbers.

the system thinks the blocks are ok until it tries to access them.

If it are "normal" bad blocks, like from switching off the phone a clean shutdown (e.g. by pulling the battery), accesses would be detected after a timeout and should be reported somehow (not sure if you get an error dialog?), at least in the logcat.

But with those bricked blocks, the program accessing them seems to lock up.

Also, flashing partition images writes every block in a partition, so it would lock up at the point where it comes to the bad blocks.

Writing files to a partition with bad blocks will work in general until the writing process gets to the bad blocks. This is a random process, so it might work some time and then something goes wrong (download stops etc.).

So, you don't really know, if you have some bad blocks until you scanned every block in the partition. For this we can use "e2fsck -c ..." e.g. in adb which looks at each block and tries to find bad ones which it writes to a bad blocks list (which fails at bricked blocks, because unfortunately e2fsck locks up).
[Galaxy Note GT-N7000 General] alucard8888:
i want to flash a stock ICS via PC Odin.. should i flash the patched pit again then the stock ICS... thanks
[Galaxy Note GT-N7000 General] FARSHOOD:
did you have the same OS installed before the brick?

I think, you had an ICS ROM installed when you got the brick and now you're hopefully back to a GB ROM, right?

(the screen shot doesn't look like CM9)

Then it might be a concept change in between.

sir b4 brick & after that i have ics lpy. in addition after brick at first i installed GB then execute your file and got ics lpy again. but again why i cannot execute your standard patch and obliged to patch via 102400 also what is your opinion about better android GB or ICS or CM and why .thanks
[Galaxy Note GT-N7000 General] thasadar:
Restored...but

Hi again!

Here is my brick-story and how this thread helped me.

*installed custom ROM, flashed under LPY CWM ->BRICK*

After searching all the corners of the Internet, starting and ending with XDA :) I found this awesome Thread.

I got the 1024000-kB PIT-> flash via Odin

Used 4pda_kernel to get CWM -> recovery menu via CWM, formatted ALL PARTITIONS that were available for formatting

Got the stock LPY (German official unbranded ICS ROM )-> flash via Odin

I managed to buy a JIG device, used the JIG to reset the Custom binary counter (The yellow triangle has been deleted automatically just by installing the Stock Rom with the included stock kernel)

Now I got a functional Galaxy Note stock ICS BUT

I don't like the fact that the phone is defective , the flash storage IS BROKEN and limiting/repartitioning is a workaround that enables me to bring it for warranty and repair.

Now, my problem with achieving that is , in recovery mode, the following text appears.

# MANUAL MODE #

--Appling Multi-CSC...

Applied the CSC-code : KOR

Successfully applied multi-CSC.

I am aware that this is a positive response but it's a relic from a flash I did using a MULTI CSC , therefor EVIDENCE .

How can I get rid of it?

Reflashing other CSC DID NOT WORK!
[Galaxy Note GT-N7000 General] evangelism:
i got the Q1_20110914_16GB-patched.pit work

with stock N7000DXLP9_N7000OLBLP6_N7000DXLP5_HOME.tar (malaysia stock)

by Odin 1.83 (as some said 1.85 problem)

i manage to revive my phone, (1st boot stuck at samsung boot animation, 2nd stock at "update 3/17", third time boot up)

i checked my storage, internal storage 1.97GB, USB storage 8.24GB

correct?
[Galaxy Note GT-N7000 General] alucard8888:
Same thing happen to me but after i have 8.34gb usb storage and 1.97gb internal storage.. im runnin XXLQ2 ICS..
[Galaxy Note GT-N7000 General] anthony8655:
Here's how I unbricked mine so hopefully someone can benefit from it.

I flashed the DAFUQ to get rid of the yellow triangle. That worked great. Then I flashed the ABYSSKERNEL using the PC odin trying to go to the ics lite rom. It got stuck in the start screen on reboot.

From this thread, after loading different combinations of roms and pits, no luck.

Then I read the post by bezeq, and got it to work.

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

---------- Post added at 07:41 AM ---------- Previous post was at 07:21 AM ----------

Right now, I'm down 3 GB from running this procedure. I don't believe my problem was corrupted partition. Is there a way to get back to my original partition size?
[Galaxy Note GT-N7000 General] thasadar:
Anthony, I am afraid you can't get your Note to have ALL its flash memory available. Sectors are damaged and that can't be reversed so easily (you can just avoid the corrupt regions by using these PIT files).
[Galaxy Note GT-N7000 General] hg42:
As I said before, some ROMS call the UMS=internal SD "usb storage" (while it has nothing to do with USB! (EDIT: perhaps, because it can be mounted via USB to the PC?)).

The so called internal storage is /data

Otherwise the numbers are correct, before the brick you had about 11.9GB.

Note: the numbers simply reflect the sizes you choose with the PIT.

There's nothing that could be done wrong, that would show up in those numbers.

You see, if the blocks inside each partition are working (=not bricked) when doing one of these things:

* flashing the partition image by Odin

* formatting the partition in recovery

* formatting the partition in adb (mkfs.ext2, mke2fs, mkfs.vfat etc.)

* checking the partition's file system with

e2fsck -c /dev/block/mmcblk0p9

(-c = check bad blocks)

* reading the partition with

dd if=/dev/block/mmcblk0p9 of=/dev/null

or simply

cat /dev/block/mmcblk0p9 >/dev/null

(/dev/block/mmcblk0p9 is /system, replace with appropriate number)

If there are bad blocks one of these operations would lock up.
[Galaxy Note GT-N7000 General] hg42:
Normally you need to flash the PIT only once.

Most ROM install/update procedures don't change the partition scheme.

If the procedure uses an own PIT, then this will not work.

Then we would have to create a new patched PIT for it.

This seems to be rare.

Theoretically an update via "install zip" in Recovery like cm9 could do anything including repartitioning, but they normally don't do it, because this would break all other ROMs which rely on the stock partition scheme.

I think this would be emphasized very bold in the installation procedure.
[Galaxy Note GT-N7000 General] hg42:
so you never had ICS on your phone?

So you probably didn't make any wipe or CWM restore when on ICS, which means you cannot have the kind of brick which is topic in this thread.

ok, so you are on a patched partition scheme.

which means, you asked Kies to troubleshoot the connection?

well...just

* make a complete backup of the affected three partitions

e.g. system + data via a nandorid backup

internal SD by copying all files to the PC

* flash a stock PIT (in my pits.zip you find two PITs without "patched" in their names, these are the stock PITs)

* restore your backup

The backup is needed because repartitioning doesn't move the data inside the partitions, it only sets some numbers in the partition table where each partition begins and how long it is etc. So the file systems insides are meaningless afterwards.

Additionally, I recommend to also make a backup of the external SD, because if you format the internal SD after repartitioning, this could eventually format the wrong SD (ROMs and Recoveries sometimes use different or wrong names for them, eg. the current cm9 recovery calls the external SD "internal SD").

Or, much easier, you could simply remove the external SD before formatting the internal SD.
[Galaxy Note GT-N7000 General] parwathy:
Hey HG42. My problem is similar to this user you were answering to : I got a N7000 device with eMMC brick, no access to a working recovery, only download mode.

Here's a brief history of what I did :

I tried re-partitionning using Odin 1.85 and Odin 3.XX + Windows XP : I tried to use the stock n7000 16gb pit file, and the custom pit "forest1971" provided in his guide (5 different ones). I didn't know about your thread at that moment. Anyway, the flash would alway fail. Then I tried the same with heimdall+linux, also failing. I also tried flashing some kernels, with the help of forest1971, but i would get errors everytime. If you need more details, just ask (I posted logs and details in another thread).

TLDR : No access to recovery so I can't use the scanner. I got a dump of my pit. Attached is the differences between stock pit and my pit. Would it help to find which of your custom PIT I could use?
[Galaxy Note GT-N7000 General] hg42:
if you cannot scan, your only chance is to use trial and error method.

If the recovery cannot be flashed via odin, the brick is also in this partition (kernel/recovery). So choose a pit which skips this. If you are unlucky, you have damaged even lower partitions, then it gets very dirty. Problem isn't the repartitioning but to restore the data of these partitions. Perhaps you can copy them from another n7000 e.g. using dd.

Btw. my own n7000 has finally become instable, it's not working anymore, so I switched to a note3.

So I have lost most of my interest in this problem.

Good luck.
[Galaxy Note GT-N7000 General] hg42:
why the gap cannot start at arbitrary positions

if you read this thread carefully, you will find that I won't create more pits for the supported devices, because all possible are already there (well, with a granularity of 256MB).

The size of the gap is in steps of 256MB which should be small enough.

The start of the gap cannot be chosen freely.

I will describe the reason another time in different words:

To be able to install any ROMs without hassle (taht is like in the original scheme), the partitions have to stay at their original sizes.

The only partition to be tweaked is the biggest one (e.g. userdata). This is the partition which also has different sizes between model variants with different memory size.

Now, think of the partitions to be wood blocks for kids.

[--A--][---B---][------C----][----D---][----------------E--------------]

The first x partitions stay in place and you shift the other to the right, so that you get one single gap:

x=0 [--A--][---B---][------C----][----D---][----------------E--------------]

x=1 [--A--] [---B---][------C----][----D---][----------------E-------]
x=2 [--A--][---B---] [------C----][----D---][----------------E-------]
x=3 [--A--][---B---][------C----] [----D---][----------------E-------]
x=4 [--A--][---B---][------C----][----D---] [----------------E-------]

the biggest block (the last E in the example) is cut to have the right end at the same place as before (which is end of memory in reality).

As you see, you can not freely place the start of the gap, you can only start it at the original partitions' borders.

In case x=1 the PIT is called ...B-moved-by...

in case x=2 the PIT is called ...C-moved-by...

etc.

Because the first partitions are usually the most critical, and some of them may be impossible to restore (because you need them to even get into download mode, recovery etc.), you will always try to leave as much of the first partitions in place as you can.

I think the main problem people have is thinking of moving the gap, but in reality you are moving the partitions, which have fixed sizes.

So the gap is dependent on their sizes.

Oh, you might think, you could eventually increase the size of one of the partitions in front of the gap?

Well, usually none of the first partitions will gain any benefit from being bigger than original.

E.g. a big kernel partition doesn't help anyone, you could install bigger kernels, but from where do you get them and for which purpose?

Even a bigger system partition could only help to install bigger ROMs, which you won't get from anyone, because everyone else has the smaller original system partition size.

Hope that helps...
[Galaxy Note GT-N7000 General] oussama111:
When i have tried to install philz cyanogenmode on samsung galaxy note 1 gt n7000 the samsung galaxy note gt n7000 logo shows up

PLEAS HELP !!!!

WHAT CAN I DO?﻿:confused:
[Galaxy Note GT-N7000 General] hg42:
usually not the kind of brick discussed here, search xda (or Google) for kind of (probably) soft bricks
[Galaxy Note GT-N7000 General] bluehawk20:
Thanks for taking the time to reply.Flashed a patched pit of yours and i able to boot into stock rom now.:good:

But the problem now is "culdn't see internal storage".Got a warning once phone booted "blank usb storage" (tried to format but fails)

When i tried to use camera "Turn off usb storage before using camera".
[Galaxy Note GT-N7000 General] hg42:
looks like userdata cannot be mounted.

This is normal, if you couldn't format it.

Did you try in recovery?

or adb shell and some mkfs command?
[Galaxy Note GT-N7000 General] bluehawk20:
Tried in recovery failed as well.

Not very familiar or should i say don't know the correct commands for adb shell.
[Galaxy Note GT-N7000 General] mastro:°:
i have efs partition currped in i9100 wich :confused: pit choud i flash with odin ??
[Galaxy Note GT-N7000 General] hg42:
if you don't know this yourself, you are probably not familiar enough with the method -> read much more.

It should be clear from the thread starter.

The whole thing is not about flashing a pit and being happy afterwards. Instead the real work begins after the pit.
[Galaxy Note GT-N7000 General] mastro:°:
got it thanx you are the men ;) :highfive:
[Galaxy Note GT-N7000 General] Vegan1983:
MY MT6575 EMMC is Erased and no partitions are there... Please help

Solved by self treatment
[Galaxy Note GT-N7000 General] hg42:
you are crying very loud...

so it's probably not emmc bricked (in our sense -> damaged hardware).

Don't know mt6575 (seems to be a chipset number used for s3?).

Don't know SPFlash.

if download mode works, your way should be Odin.

You probably need a firmware which includes all partitions (usually a developer firmware, for n7000 it's a six part firmware). You may look on samfirmware, but it's not easy to find. So look in web if this exists and which file to look for.

Your biggest problem will probably be the efs partition, because it contains(contained) data specific to your particular device (imei, bt mac, etc.). You need a backup of your own efs to restore this correctly. The dev firmware usually contains generic version of this, so you get a generic imei.

I don't know how you could copy partitions from one phone to another with only download mode working.

If would try to

- get the phone running with the dev firmware

- eventually need to root

- install a more powerful recovery

- use adb to fix thing

(e.g. dd to copy missing partition contents, or adb push to copy missing files, etc.)

Without download mode: probably jtag etc.
[Galaxy Note GT-N7000 General] Vegan1983:
Thanks but You need to understand it well now...

Solved by self treatment
[Galaxy Note GT-N7000 General] Green-Bot:
Only Download Mode is working on Galaxy Note, What to do now?

Hello,

I was running samsung JB stock firmware 4.1.2 with Root access. Due to swollen battery(its out of shape) issues, my phone was restarted many times. This happened for 10-12 times and after that my phone got stucked at samsung logo, went to bootloop state.

I tried to enter recovery but it also freezed at green robo and wheel spinning image. So recovery mode stopped working.

As of today, only Download mode is working. I tried re- flashing custom PIT files with stock firmware but none of them worked for me. I did flashed sppedmod kernel, hoping it would land me into recovery but it didn't. Then again i flashed with official PIT file and stock firmware but nothing is happening. Odin seems to hanged and NAND write start operation has failed everytime earlier.

Can someone please help me? Any suggestions would be highy appreciated!
[Galaxy Note GT-N7000 General] hg42:
this thread only applies to some samsung devices
[Galaxy Note GT-N7000 General] hg42:
emmc brick should be triggered by ics kernels only
[Galaxy Note GT-N7000 General] aetewy:
very good man
[Galaxy Note GT-N7000 General] panda822:
hi

Hello,

I have scanned my internal sdcard but there are no errors, but I can not access it from Android 4.4.2 and I can not mount it in CWM. I could mount it and access it in CWM from Cyanogen 10.2 for Samsung Galaxy 2 older version of CWM but the OS could not be installed. What can be the problem and how can I fix it?
[Galaxy Note GT-N7000 General] dharmabum:
I just wanted say thank you for both of your discussions. I had previously payed to get my N7000 serviced, I assume they had the necessary tools to rebuild the unresponsive system partitions after the brick bug. I continued to have random freezes and reboots a few months after it being returned. I believe they did not really scan for the damaged errors, but only assumed where the damage was occuring because they only used approx 8gb of available space when they repaired it. Using your method I was able to recover nearly 12gb for all of the partitions.

Using your methods I noticed a minor hesitation when the script read the sectors when reading down from the top. I omitted this portion, it has previously been used in the repair, when selecting the new PIT and have been using the device without the previous issues for a week.

Awesome post- Thanks again!
[Galaxy Note GT-N7000 General] nip123:
HI provide me information please

Hi im trying the pit method through cwm,

where emmc_find_brick_start.zip freezes came out to be BRICK_START 39MIB = 41MB

im still scanning for where emmc_find_brick_end.zip freezes -> BRICK_END ,

my question is since it starts with 41MB should i use one of the expert PIT files? or should i try the ADB method?