yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] ahhl:
it seems that i cannot use this pit file

N7000_16GB_Q1_20110914--patched--brick-between-00281-and-07528-MB--FACTORYFS-moved-by-06912-MiB

even though the block is within 00281(1023) / 07528(7168). in the () is my start/end block. i ve tested the start/end block to ensure it doesnt move. it still show start/end at the same point.

after i flash pit, i cwm'ed phill's kernal. when the kernal reboot it says the mmblck0p11 cannot access

then i have to use the next available pit file which is working

N7000_16GB_Q1_20110914--patched--brick-between-00281-and-07797-MB--FACTORYFS-moved-by-07168-MiB

i am doing another test

i flash back N7000_16GB_Q1_20110914--patched--brick-between-00281-and-07528-MB--FACTORYFS-moved-by-06912-MiB

then i flash stock JB4.04. the phone boots and run nicely.

then i went to stock recovery and run the scanner (start/end/all partition) all just end nicely. no error show. scanning in stock recovery doesnt have any output.

i am flashing back phill's 3.99 directly from stock recovery and reboot recovery back in it show some of kernal file not install or cannot be found

i run the scanner inside phill's recovery the start point is at 1023Mib=1073MB and it reboots. since it reboot i use adb shell to scan the end block and the end point is still at 7168Mib=7157MB.

i scan all the partition individually from 1 to 12 , all without error

why then there's error in UMS block?. this error did not happen if i flash this pit file

N7000_16GB_Q1_20110914--patched--brick-between-00281-and-07797-MB--FACTORYFS-moved-by-07168-MiB

edit

unless my kenal corrupted. let me check
[Galaxy Note GT-N7000 General] hg42:
To be clear:

It's not a fix, it's a workaround (I assume that's why you used the " above?)

Yes, you can indeed brick again (more blocks corrupted).

I (we) don't know exactly, what causes the bricked blocks.

The corruption seems to be in tables assigning real memory "cells" to addressable blocks. The tables are used to wear out all cells evenly over time, even if always writing the same block. This is called "wear leveling". Otherwise the cells would be damaged after short time (they have a limited number of writes).

There is an algorithm that calculates these assignments.

It will probably use some sort randomness to achieve an even distribution.

The bug is in this algorithm.

I assume the tables get corrupt in a way that the wear leveler algorithm assigns non-existent cells *or* it simply hangs because of wrong values.

I think the "moving" blocks may come from the randomness.
[Galaxy Note GT-N7000 General] hg42:
Re: PIT file method to revive your phone from a MMC_CAP_ERASE brickPIT file method to

1 MiB = 1024 x 1024

1 MB = 1000 x 1000
[Galaxy Note GT-N7000 General] megosu:
yes that's why I used the quotes :)

and what about you, you fixed your device a while ago, don't you suffer moving blocks too ?
[Galaxy Note GT-N7000 General] hg42:
Just some thoughts:

I wonder, if you followed my instructions? You didn't mention formatting or restoring.

If you didn't format or restore the partitions, they cannot be used by the system (they have no file system and therefore cannot be mounted).

I don't know phill's kernel. It may be incompatible with the ROM. Ensure the kernel fits to the ROM if you use it together.

Are your numbers 1023 and 7168 really the MB values? if they are MiB, then 7168 MiB would be 7516192768 = 7516 MB, which is near 7528 MB

If the recovery doesn't show output of the scanners, you have to fake flash CWM.zip and run (= install zip) the scanner from there.

But: be careful (with that ax Eugene :)), stock ICS or JB and wiping in this CWM.zip causes emmc brick, so never wipe or format from CWM.zip!!! never ever!

Anyways, loosing 256 MB shouldn't matter much, right? So simply use the one that works.
[Galaxy Note GT-N7000 General] hg42:
Sorry, I am lost...

"there is no pit partition" may indicate that you bricked some important portions of your flash memory.

Can you flash a recovery (without flashing the pit)?

May be you could first scan for a brick to know where it is.
[Galaxy Note GT-N7000 General] hg42:
After some short time of movement (about a week) it remained stable.

I measured several times in about the first three months.

Since then I never had any problem (and didn't measure again).
[Galaxy Note GT-N7000 General] hg42:
You can also flash a ROM if you don't have other kernels.

I don't know your device, but usually ( that's for my SGN :) ) adb works in the ROM or in the recovery.

When reviving my own device, I cleared my system partition (by repartitioning) and this made adb unusable. I think that's because it used the shell from the system partition. I solved this by using a self-contained recovery (with it's own shell and other commands).

May be you should look for another recovery.

Alternatively, you may install a complete (custom) ROM, which should contain everything you need.
[Galaxy Note GT-N7000 General] ahhl:
hg thanks for the reminder

yes i did format and restore as per procedure "standard"

that not loosing 256mb, its actually loosing 7168Mib from (00281mb-and-07797mb) internal sd left only 4GB from 11GB!!. i AM crying.

should i try the emmc_scan write. who kows it just few bad block within that 7GB range.

edit

i think the brick hole getting larger, eventhough i manage to pc odin the modded pit, (while i in custom safe kernal) i still cannot format the /data, /sdcard. that makes the rom cannot run even its successfully installed. i am now at pit 281 to 8334, only manage to format /sdcard not /data

but the emmc scanning shows the start/end never change.

how to format the partition. format thru cwm does,nt work,
[Galaxy Note GT-N7000 General] hg42:
Hmm, I really hope, you don't wipe (e.g. in cwm.zip) while running on a stock kernel? Then the brick would indeed get larger and larger because the relocated partitions will brick again...

256MB was meant as the difference between the two PITs...

For my own phone, I bought a 64GB sdcard and mount all directories on the external card to the internal sd on boot (using Script Manager).

I move all big directories to the external sd (and then reboot).

So my internal is only a kind of base dirrectory for the mounts (altough I still have 8 GB).

emmc scan write will probably have no effect.
[Galaxy Note GT-N7000 General] hg42:
you don't need adb for the pit method (that's one reason for which I created these pits).

Or do you want to make backups?

After flashing a good kernel via Odin, you will probably be able to use adb.

Hmm, what do you mean with "dead device", can you get into download mode? or even into recovery?

Which ROM was installed before? how did you get the brick (if you really have one)?
[Galaxy Note GT-N7000 General] shoey63:
I think he is a victim of SDS (Sudden Death Syndrome). A brick peculiar to SGS3, and unrelated to emmc super brick (supposedly "safe" chip set). Samsung is aware of the problem and replacing devices.
[Galaxy Note GT-N7000 General] ahhl:
i only do wipe in safe kernal

i rescan again using your scanner. the start/end point never move. but why i still cannot format /data, /emmc, /sdcard ? how to format using adb shell?

i have scan partition by partition using adb shell after flash modded pit, there's no error

what else i should do

when oot into recovery mode

this error appear

E:failed to mount exfat /dev/block/mmcblk1p1 /sdcard

E:failed to mount exfat /dev/block/mmcblk1p1 /sdcard

E:failed to mount exfat /dev/block/mmcblk0p11 /emmc

E:failed to mount exfat /dev/block/mmcblk0p11 /emmc

edit

i've use dd comand for all partition, the result ok but when i run the e2fsck command, it cannot read the partition. for pit i've resorted using forest1971 custom3.

any advise needed. thanks

edit

how to calculete partition size? at the moment i only have problem with partition 11. when doing dd or e2fsck it says directory not found. i have manually move the partition one by one from factoryfs,datafs,ums ( checking the error by formatting each individual partition and using the percentage stuck as a guide)

i manage to create UMS partition and format it but when i e2fsck, it says cannot find partition 11

heres the partion

Number Start End Size File system Name Flags

1 4194kB 25.2MB 21.0MB ext4 EFS

2 25.2MB 26.5MB 1311kB SBL1

3 27.3MB 28.6MB 1311kB SBL2

4 29.4MB 37.7MB 8389kB PARAM

5 37.7MB 46.1MB 8389kB KERNEL

6 46.1MB 54.5MB 8389kB RECOVERY

7 54.5MB 264MB 210MB ext4 CACHE

8 264MB 281MB 16.8MB MODEM

9 7936MB 8829MB 893MB ext4 FACTORYFS

10 9044MB 11.2GB 2147MB ext2 DATAFS

11 11.3GB 15.1GB 3800MB ext2 UMS msftres

12 15.2GB 15.8GB 537MB ext4 HIDDEN

partition 11, i manage to format it to check any error but unfortunately the CWM i am using do not have tune2fs to convert it to ext4. where can i get it? please guide my i a simple way as i have no knowledge of programming and this is desperate trial and error
[Galaxy Note GT-N7000 General] hg42:
now, at least, you should have wiped the data partition...which you catched up afterwards...

Ok, thanks, so the wizard problem comes from having an unformatted data partition.

But why formatting USB-storage?

I heard there are ROMs which call the external sd "USB storage"?

I think, probably Factory Reset (which should be more or less equal to "wipe /data" or "format /data") should be enough here.

nice

Note: this is a work around, it's not a real fix.

Your internal flash memory has bad blocks, and from what I know no one managed to repair them. So most people probably should ask Samsung for repair service (on guaranty).

The fix works by moving the old /system and /data into the start of the UMS partition (internal sd) and therefore shrinking the internal sd by about 3GB.

this should be unrelated to my workaround.

May be your internal sd is still unformatted?

Can you see files on it?
[Galaxy Note GT-N7000 General] alucard8888:
@hg42

thank you.. my note is working fine now after wiping data/ factory reset and wiping cache partion in orig cwm.. but im still experiencing random rebooting,, i think once a day...but still im happy my note is working and stable enough to use everyday.. again thanks to you..:)
[Galaxy Note GT-N7000 General] hg42:
with a different partition scheme you could probably shrink the unused area.

But that's a lot of work (trial and error, which means installing the OS multiple times) and it's a individual solution, because ever one has a different set of blocks bricked. So you have to try for yourself.

Eventually I could write a little perl script to allow creating different PITs for different schemes. But my spare time is very limited.

For myself I think it's not worth the hassle.

I just bought a 64GB sdcard, which should be enough for all my purposes.

And, after the brick, I tend to put important data on external storage.

Also read the whole thread...

I just explained what you can do and what you can not.

I get a little tired of repeating myself :-)
[Galaxy Note GT-N7000 General] hg42:
well, that's because I wrote it...because I was in the same situation and didn't find anything useful. Everyone told me about repairing the motherboard.

I chose this way because I cannot know which blocks are damaged for all users together.

So I used a scheme which should work out of the box for all users having brickes their /system and or /data *anywhere*.

You can see the partition scheme in my first post (the ascii graphics).

If you want to try, you could start the three new partitions at any block inside the suspicious area.

To find the best starting point, I would first remove partitions 9, 10, 11.

Then I would create a partition in the second half of the suspicious area and run e2fsck -c /dev/block/... on it. After that remove the partition.

If that e2fsck worked (no bad blocks found, especially not stuck spomewhere),

I would create a partition in the second half of the first half...

otherwise,

I would create it in the second half of the second half...

etc. This should be the quickest method to find the working part of the suspicious area.

You can open two adb consoles, one to stay in parted and the second to run e2fsck.

From what I know: NO, but...

I am not on topic in all those xda threads (no spare time left), so read yourself.

And please tell me, if you find newer info.

I didn't test myself, but in this thread there seem to be success stories on this.
[Galaxy Note GT-N7000 General] hg42:
again, I cannot imagine why random reboots should originate in the new partition scheme.

I think, either you had additionally bad blocks (from the brick) inside the UMS partition, which are not worked around by the new partition theme (which only addresses system and data bricks).

Or you might have some (soft) bad blocks in any of your partition (which would mean a slightly corrupted partition; I read somewhere, that zero data can also be written somewhere while bricking).

Or the problem is even totally unrelated to the brick...

I would start adb and run e2fsck -c /dev/block/... on all ext4 partitions.

There should also be a fsck for fat32 partitions in the ROM, sometimes called fsck.vfat or may be dosfsck etc., just look for command names containing "fsck" and "fat" or "dos" in /*bin, /system/*bin, as these commands depend on the recovery or the ROM (note: you can run adb in recovery mode or while the firmware is up and running in GUI).
[Galaxy Note GT-N7000 General] A.S._id:
HI hg42, and can you make a tool, for Linux, the script to run in the terminal, or bat file for windows command string, with perhaps change the parameter partition has been, and that creates a pit file? Thanks in advance!
[Galaxy Note GT-N7000 General] alexdumitru:
I flashed your PIT and SGN_XX_OXA_KJ1_FACTORYFS.tar and it works like new :)

Thanks !

UPDATE: Upgraded to ICS through recovery and it didn't recognize my SIM. I restored to an older backup ( which probably broke my partitions again ) and the phone is stuck at boot. Now I flashed your PIT and SGN_XX_OXA_KJ1_FACTORYFS.tar again, but it's still stuck at boot. Also it won't enter recovery mode. Any ideas ?

UPDATE 2: It didn't recognize the SIM because I lost the EFS partition. Which means the device is 100% bricked. So make sure you backup the EFS partition !!!
[Galaxy Note GT-N7000 General] pjotrek90:
The method you provided worked fine for me dude. Thanks a lot for your job :)
[Galaxy Note GT-N7000 General] hg42:
NEW: bunch of PIT files and also 32GB

Hi,

I hacked a little perl script, which generated a bunch of PIT files for me.

This at first addresses 32GB SGNs.

The second purpose is to regain more of the free space (again, please read the update at the end of first post).

Good luck everyone...and please also report success.
[Galaxy Note GT-N7000 General] Archangel919:
bad blocks fix ?

Hi hg42 , Is there any fix for bad blocks ? like we have defragmenting tool for windows , so any such thing in android so that i can recover back the bad blocks from the memory ? Can my phone ever have full 12 Gb as new one ?
[Galaxy Note GT-N7000 General] FARSHOOD:
Hi hg42 i have the same problem and used your patched pit file but no success would you recomend any other pit ,the pit list is too long to test.
[Galaxy Note GT-N7000 General] hg42:
Are you sure, it doesn't work for you?

Odin gets stuck somewhere (no movement of the bar in Odin and progress on your phone) and you waited at least 5 minutes to be sure?

The *-patched.pit files are the ones with the most chances.

If they really don't work, then you may also have bad blocks in your UMS partition.

I currently don't have a workaround for this.

However it would be possible to calculate a PIT to move the start of the three partitions somewhere inside of the former UMS partition if it is damaged at it's start.
[Galaxy Note GT-N7000 General] alexdumitru:
You should trying flashing a stock ROM along with it. I don't know why, but it doesn't always work for the first time. Try again and maybe with another ROM. I made a guide of repairing your device using hg4's PIT files: http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/
[Galaxy Note GT-N7000 General] dark11b:
tried the new pit files and was able to recover about 1GB :)
[Galaxy Note GT-N7000 General] hg42:
I was told a soft repair (JTAG on the flash chip or so) would require about 12 hours, so exchanging the motherboard is cheaper (which costs about 280EUR they say).

You could write a bad blocks file and feed it to mke2fs when formatting the partition. But then you can no more use standard procedures.
[Galaxy Note GT-N7000 General] FARSHOOD:
any difference between pit files i mean that is it any relation between various pit files and amount of capacity we can achieve.
[Galaxy Note GT-N7000 General] hg42:
sorry, I don't completely understand what you are asking for...

But let try to answer anyway...

As I wrote in my first post:

"The number after "regain" describes how much kBytes are regained by this scheme compared against the original workaround."

My "standard" workaround leaves the complete former /system and /data partitions unused, because they can be bricked anywhere, so you loose about 3GB.

So, if you select the PIT with 1024000 in it's name, you loose 1GB less than that, 3GB - 1GB = 2GB.

We can do this, because in most cases the brick seems to "prefer" the beginning of the /data partition, so the end may be undamaged.

Note: there may be damages of other partitions, too.

So better check *all* partitions in adb with an appropriate file system check command (parted, e2fsck, fsck.vfat etc.).
[Galaxy Note GT-N7000 General] hg42:
is there anyone with a bricked UMS partition (internal SD)?

Where are the bad blocks? at the beginning?

should I also generate PITs with a scheme like this?:

before: ...-|-FAC*ORYFS-|**ATAFS-|-UMS------------------------------------|...
after: ...-| empty space |-FACTORYFS-|-DATAFS-|-UMS---------------|...
(* = bad blocks)

This scheme would start the three changed partitions at different offsets *inside* the former UMS partition, working around bricked blocks at the start of the UMS partition.
[Galaxy Note GT-N7000 General] FARSHOOD:
Originally Posted by FARSHOOD

any difference between pit files i mean that is it any relation between various pit files and amount of capacity we can achieve.

sorry, I don't completely understand what you are asking for...is there anyone with a bricked UMS partition (internal SD)?

Where are the bad blocks? at the beginning?

should I also generate PITs with a scheme like this?:

Code:

before: ...-|-FAC*ORYFS-|**ATAFS-|-UMS------------------------------------|...

after: ...-| empty space |-FACTORYFS-|-DATAFS-|-UMS---------------|...

(* = bad blocks)

This scheme would start the three changed partitions at different offsets *inside* the former UMS partition, working around bricked blocks at the start of the UMS partition.

dear sir how are you today any way i did your pit file 1024000 and recovered 8.3 GB FIRST THANKS A LOT BUT MY QUESTION IS IF I TRY ALL OF YOUR PIT FILES IS IT POSSIBLE TO RECOVER ALL OF 16GB SD ,ALSO BY YOUR DEFAULT PIT=Q1_20110914_16GB-patched.pit I DID NOT GET ANY RESULT IS IT ANY WAY TO RECOVER WHOLE OF THE SD AND WITH REGARD POST 98 WOULD YOU MORE EXPLAIN WHAT DO YOU MEAN AND HOW CAN I REACH TO THAT SCHEME GUIDE ME TO FIND THE SCHEME ADDRESS. BEST REGARDS
[Galaxy Note GT-N7000 General] ahenderson223:
First let me say thank you for your work has helped me bring my note back to life i was wondering is there any way to reset the binary counter
[Galaxy Note GT-N7000 General] htaylay:
If I flash a recovery, odin show fail and there is no pit partition. How do I do? :(
[Galaxy Note GT-N7000 General] Hakan 3:
can u do a pit file for repartition on sdcard for i9003

like swapping memory but without hardware ?
[Galaxy Note GT-N7000 General] hg42:
From what I know, switching internal and external memory is not possible with PIT files.
[Galaxy Note GT-N7000 General] ahhl:
hg

i am bumping this, almost there, but still need some guide
[Galaxy Note GT-N7000 General] hg42:
"exfat"?

Who tries to mount them as exfat? and why?

Either the system (from where you get these messages, which seems to be the recovery [which?] or some boot process) wants to mount an exfat file system, meaning you have to create exfat file system.

Or, you created exfat partitions and the system detects this (e.g. by some signature) but cannot handle this file system.

Or, "someone" wrote an exfat signature but the real file system is ext2?

in this line you made an ext2 partitions:

11 11.3GB 15.1GB 3800MB ext2 UMS msftres

exfat is Microsoft's new incarnation of the stone aged FAT file system (from old DOS days).

How do you format (mk*fs) the partitions?

I don't know which PITs forest uses.

I would recommend to use my PITs, which are more fine grained.

really, no other output from e2fsck or dd?

I think this has nothing to do with the partition, because at least dd doesn't deal with directories, it only uses the raw device.

Which dd or e2fsck do you use? from where did you get them? how do you invoke these commands?

Perhaps they use directories in the system to find the devices or something like this (e.g. /dev/disk/... but only /dev/block/... exists).

The commands may not be compatible to your recovery or rom.

If you currently only have problems with UMS, then you can boot your ROM and format both SDs from there.

You may also use a ROM like cyanogenmod 10 or 10.1 which has it's own recovery (better compatibility between ROM and recovery).
[Galaxy Note GT-N7000 General] hg42:
Ok, sd is usually formatted as fat32, may be phils kernel has exfat and this file system driver is able to mount fat32, too.

Note: mount shows it as vfat here, because of long file name support.

I assume formatting as ext2 is simply wrong, format it as fat32 instead. I think there's no commandline tool for this in some recoveries. That's why formatting from rom is the usual way. But if your recovery has a menu for format sd then this should work.

Btw. ext2fsck etc. don't scan each block, only if there's an option for surface scanning (and you use it).

Use dd or my scanners for block checking.

The real question seems to be: why can't you format in recovery? I have no clue, currently.
[Galaxy Note GT-N7000 General] shoey63:
Correct. Phil3759 added ex fat support to his recovery (whilst still supporting fat32) to cater for users who don't want 4GB file size limitation.
[Galaxy Note GT-N7000 General] eljuggy:
Hello,

I superbricked and want to use my warranty. emmc_scan the brick between 580 and a little under 2970 MiB. (no freeze for me but a quick reboot !)

I want to use my warranty that is still valid, my phone says Samsung Official and no custom binary, but I'm rooted with Philz kernel now (to back up my internal SD)...

I can't flash a stock rom in odin because I get write NAND stucked... surely because of the brick.

Should I flash a stock ICS rom with an appropriate pit file ? but then.... how will I send my phone to warranty... since it'll be working ?

I thought about flashing again a stock ICS rom (after reviving the phone) but this time with the default 16GB pit file ... is it a good idea ?

Thanks.
[Galaxy Note GT-N7000 General] megosu:
you shouldn't touch your default pit, just flash your stock ICS rom (from sammobile), and you are good for warranty.

It should flash the stock rom but your phone will not boot. And you won't have a yellow triangle, or anything non official so all clear IMO.