PIT file method to revive your phone from a MMC_CAP_ERASE brick

alucard8888

Senior Member
May 13, 2012
233
64
0
Paris
ive flashed pit and it works!!

Finally added patched PIT file (only for 16GB!!!) to first post!
Please read update comments written there.
Many thanks to hg42 my note is now working after ive flashed the pit via pc odin.. then flashed stock GB via pc odin also.. but after using it for 2hrs now, i keep getting forced closed in Facebook.. and ive experienced rebooting 4 times now.. im on stock LC1.... can someone tell me whats the solution on forced closed and rebooting.. again thanks to hg42 my note is Alive now..:D
 

Attlon

Member
Apr 30, 2009
11
2
0
Finally added patched PIT file (only for 16GB!!!) to first post!
Please read update comments written there.
Great thank! Großes Dankeschön!! Огромное спасибо!!!
Is very easy and simple reviev bricked Note with the help of your file.
 

shun2x

Member
Jun 26, 2008
20
1
0
wow man thx a lot

after 3 hours brick i found ur thread and myphone wakeup again

thats so cooooooollllll

thx man

---------- Post added at 05:06 PM ---------- Previous post was at 04:13 PM ----------

after i use ur PIT now my phone so laggy
and i try install the original PIT my phone stuck on Samsung GALAXY NOTE booting
do u know a way to make my phone back to factory reset again??
thx u
 
  • Like
Reactions: crys18

crys18

Member
Dec 29, 2010
37
32
0
Ok i bricked my phone, tried every method to fix and failed.
Flashed your pit.
Flashed SGN_XX_OXA_KJ1_FACTORYFS.tar worked no stuck on NAND Write.
Flashed CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5.tar
Installed XXLC1_CheckROM_NoteHD_V6.zip using CWM.
Stucked at Wizard, retried a couple of times and passed wizard.
Now everything Force Closed, after some minutes manages to go to Settings > Privacy > Factory Data Reset
Check Format USB Storage
And now is working fine no more FC.

Problems.
i only have 8 Gb internal space.
don't update youtube from play store, bcoz the update will FC
a lil laggy.

Is there a way i can revert my phone to original state, fix the bad blocks and have 12 gb internal space like before???
 

Attlon

Member
Apr 30, 2009
11
2
0
and i try install the original PIT
Why do this???
It is enough to make here is this:
The PIT will repartition the phone, but the partitions will not be formatted.
So, before restoring with a recovery you have to format them (usually recoveries allow this, too).
I had made earlier backup LC1 with the kernel Thor v.0.4
After the restoration of the backup and several reboots with removing the battery - Note works just perfectly!

---------- Post added at 10:34 PM ---------- Previous post was at 10:17 PM ----------

i only have 8 Gb internal space.
I have so too.
 
Last edited:

crys18

Member
Dec 29, 2010
37
32
0
Any way of lowering the bad blocks gap?
I mean almost 4 Gb of space is bricked?
Can i use my phone like before, flashing ics, etc??

Thanks :X
 

crys18

Member
Dec 29, 2010
37
32
0
Did it again.... :))) i gues im just stupid:D
Installed LPY using Pc odin, worked fine, but i installed cf-root 5.5 and gues what, i did a wipe and stucked at formating data................and now i ........................
Some1 shot me.
Everything i do, device stuck at boot logo ....GT-N7000...
I can go to Download mode but everything i flash its dead.....
 

Attlon

Member
Apr 30, 2009
11
2
0
Last edited:

thasadar

Member
Jun 13, 2010
13
0
0
Dresden
I managed to un-brick my Gnote using these instructions

Hi all,
Thank you for your helpful comments and hg42 thank you for posting the ADB procedure and the step by step guide. As other here mentioned, there is also THIS POST detailing the parted process.
Just when I lost all hope I found your post and the aforementioned guide.

Let me start off by telling you that I have exactly this type of MMC_CAP_ERASE brick that lets its self solved by following the OP instructions.

It helped me understand the maneuver and I managed to save my gNOTE :p

Now, after reading more topics regarding corrupted sectors, re partition and flashing I am now to understand that through bricking sectors from our flash memory are damaged and can't be recovered.

I still need some clarifications to get the whole picture.

Through this particular type of bricking, sectors from our flash memory are damaged and can't be recovered...right
Is that why the size of the UMS partition shrinks from the initial size of 11GB to 8?
Is it possible to recover the missing sectors? I do hate the fact that I am missing almost 4 Giga from the internal SD

Also is it now possible to RESTORE my GNOTE to the former stock rom ?(by that I mean flashing back to gingerbread or a non wipe ics stock rom, repartition and use of all available UNCORRUPTED space )
 

hg42

Senior Member
Feb 1, 2011
647
551
93
repartitioning with a PIT does *not* format!

@alucard8888 and others with FCs...

flashed the pit via pc odin.. then flashed stock GB via pc odin also.. but after using it for 2hrs now, i keep getting forced closed
I never switched between ICS and GB, so I can only speculate...

I think, I should make more clear that flashing the PIT does only repartition the internal flash device (/dev/block/mmcblk0), this does not format those new partitions. The new partitions are /system, /data, and also the internal sdcard (which is also called UMS). Without formatting these partitions don't have a file system, or even worse they have some random data on them, which may create trouble, as the system tries to read a file system out of this random data.

So to make it very clear: you have to put some contents on those three partitions before using them.

There are at least two ways to accomplish this:

1. if you have CWM or other recovery which allows to format partitions, this should work (but I didn't test myself!). Choose "format /system" and "format /data" first. The internal sdacard is a speacila thing, because each ROM *and* each recovery calls them different. E.g. cm9 recovery has /emmc and /sdcard and cm9 ROM itself uses them different as the recovery, Samsung mounts internal sdcard to /sdcard and external on /sdcard/external_sd, ans so on...
So, do yourself a favour and first backup your external sdcard, then check which one is the internal sd (e.g. by using "install zip from sdcard" and see where you find the correct files) and only then start to format it.

2. you flash partition images to all three partitions in PC Odin or Heimdall.
Partition images include the formatting, so flashing an image also creates a file system on the partition.

Additionally you could mix both method, e.g. flash /system (FACTORY_FS) and /data (DATA_FS) in Odin and then boot into recovery and format the internal sd (again: *after* checking!).

Advanced users could also flash the PIT and then go to a capable recovery and use adb to format the partitions.

From my experience switching between very different OSes like ICS and GB or even stock ICS and cm9, you should wipe the cache partition and/or the Dalvik cache.
 
  • Like
Reactions: A.S._id

hg42

Senior Member
Feb 1, 2011
647
551
93
after i use ur PIT now my phone so laggy
there's absolutely no reason, why a shifted partition scheme like in the PIT should make the phone laggy.

The alignment of the partitions (that is, if their start is divisible by a certain block size) could have a slight effect on speed, but the scheme is choosen in a way that partition boundaries should be good (because the FACTORY_FS starts exactly where the former UMS started before).

You probably have not recreated all three partitions.

Generally, after flashing one or two partitions via Odin, I would format the others in the recovery. At least the /data partition should be formatted or wiped.
Also wipe cache and dalvik.
 
  • Like
Reactions: A.S._id

hg42

Senior Member
Feb 1, 2011
647
551
93
i flashed with your pit and i cant get passed the wizard to setup the droid without it rebooting even after wiping and reseting it.
I can't imagine a reason for that.

I would reboot into a capable recovery and start adb and then check my partitions:

/system:
e2fsck -c /dev/block/mmcblk0p9
/data:
e2fsck -c /dev/block/mmcblk0p10
UMS:
e2fsck -c /dev/block/mmcblk0p11

if this hangs somewhere you may have bad sectors in that partitions, too, which probably means your UMS partition was also affected by the brick.
 
  • Like
Reactions: A.S._id