yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] badmaash:
EMMC Brick Re-Partition to Original State

Hello, I have N7000. Went through your post a few months back and successfully could active my emmc cap bricked phone. As mentioned my phone has 8.24 GB internal space and rest is all lost. I do not mind the lost 4 GB but ever since i revived my phone my phone has been freezing. I have installed various new firmwares wiped my phone several times but the issue doesn't go. I think the phone freezes when it tries to access some data on emmc that is still corrupt and so it freezes. I also used your new scanner to find out which partition may be corrupt. The start to end and end to start scanner shows no issue and is completed but I think indepth scanner shows some issue. The scan is too slow and could not locate where exactly the scanner stops and reboots the phone. Nonetheless my question is now is it possible to go back to previous stock partition and brick my phone as it was. The samsung guys don't agree to change my motherboard even though my phone is under warranty. I want to brick the phone again and give them the phone telling them I don't know what happened. Will let them fix it for me.

Please tell me can I again repartition the device to its original state?

Sorry for long message thought it would give you some info on what i am trying to do before going ahead with your suggestions.

Thank you very much.
[Galaxy Note GT-N7000 General] Gotcher:
So I bricked my Samsung Galaxy Tab Plus N (P6201) yesterday. :(

I ran the EMMC tests and it looks like that I have the bricks between START 5120=5369 and END 7166=7515.

There is a .pit file in your .zip which uses START 05007 and END 15208. When I got everything in the correct way, this would likely fix my EMMC brick but will cost me a lot of space on the internal SD.

What can/should I do now? Thanks for your help and this whole thread!!! :)
[Galaxy Note GT-N7000 General] hg42:
You mean the 'find brick' scanners run continuously fast(!) through all blocks, but the partition scanners don't?

This shouldn't happen, because they basically do the same and the 'find brick' scanners scan more blocks.

Only difference is the starting address, may be they scan in a different raster. This would mean I have to reduce the step size.

Theory is, that flash memory is organized in bigger blocks, which are the unit of allocation (let's call it chunk) and for the internal tables, say something like 256KiB. So I assume(d), it doesn't matter which exact byte is touched in the chunk. If the chunk is badly assigned, the memory in inaccesible afterwards. So stepping in chunks should be ok.

Your report suggests that either the chunk size is too small or my theory is wrong.

Flashing the stock pit should restore the original partition scheme, but you won't be able to flash content to partitions with a brick.

I think there are other threads how to get a bricked phone through repair services.

I think, after flashing the stock pit, I would clear the first blocks of each bricked partition, something like dd if=/dev/zero of=/dev/block/mmcblk0p9 for at least some minutes or until it freezes/reboots.
[Galaxy Note GT-N7000 General] hg42:
So, you used / want to use one of the new "BIG"-shortened (=UMS-shortened etc.) PITs, right? Please report the results.

My PITs use these principles:

* do not change a partition number

otherwise the ROM will/may not mount the partitions to the correct directory e.g. partition 9 to /system etc.

also, the recovery will not work correctly

* do not change the size of any partition but the biggest one (called "big" partition in my descriptions and posts)

most partition sizes are designed by the manufacturers to hold specific content.

Custom developers usually try to fit their modified contents into these limits.

So, keeping the size gives maximum compatibility.

So my strategy is to move partitions around the brick, shifting all following partitions, too. The big partition (which is empty at the beginning and meant for user data a.k. internal sd) is then shortened by the same amount the other partitions are shifted, which means all partitions after the "big" one (if any) stay in place (because they cannot be shifted without changing their size).

The new "BIG-shortened" PITs are meant for a brick solely in the "big" partition. They don't shift any partition but only shorten the "big" partition, which means everything after the new partition end up to the former end will be unused after repartitioning.

Generally it would be possible to use the space after the brick for one more partition, but this would only be used, if some software makes it available (by mounting it to a directory). This could be done by a scipt using something like Script Manager or the userinit script in CyanogenMod.

Because inserting a partition after the internal sd would increment the following partition numbers, a working strategy would shift all following partitions in front of their former position and add the additional partition after the last former partition.

It could then be mounted by a script like this (if the new partition is number 13):

mkdir /mnt/extra

mount /dev/block/mmcblk0p13 /mnt/extra

or perhaps

mkdir /sdcard/extra

mount /dev/block/mmcblk0p13 /sdcard/extra

this should be done according to the principles of the ROM, e.g. Jelly Bean mounts such partitions in the /storage directory.
[Galaxy Note GT-N7000 General] Gotcher:
First of all, thanks for the quick answer! :) I'm not as deep in messing with Android since this is my first device with this OS.

The main problem is that the manual way (with adb) doesn't work for me. I installed KIES and all necessary drivers (they are coming with the program, right?). My PC recognizes my Tab somehow since I can hear the typical KIES connection sound. Nevertheless, it doesn't show up in the command line at all when I use "adb devices"... =/ Im quite worried about this problem because you wrote in the first post that I need the IMEI number etc. to use the phone functions again. Is there any other way to backup the files with the adb way for me (somehow fixing it that my PC recognizes my tab again) or (maybe that's easier) a completely different way to save the files to safe place?

Is the device really "useless" after trying to unbrick the Tab without those mentioned files? I'm pretty confused about this since I really don't want to loose hardware compatiblities of my device but I don't know how to fix this adb problem. :(

So when I now use the .pit file that you provided in the .zip for the P6200 (START 05007 - END 15208), can/should I edit something on this file? I'm not 100% sure that I understood your whole post above. :( Is it possible for you to create a custom .pit file for me? I would love to do it myself, but I'm not even sure which program I have to use to edit the .pit files in the correct manner: I'm quite a newbie with Android and I don't want to destroy my device completely ;)

Greetings from Germany and thanks again! :) :good:

Edit: I tried to sent you a PM where I explained this post on german (because I fear that something remains a bit unclear), but I think that this didn't worked, did it? Of course I'd post the results of the try to unbrick my device.
[Galaxy Note GT-N7000 General] hg42:
you know and tried the "three finger salute" to get into the recovery?:

(Vol-up + Home + Power until the recovery appears)

The device has different modes (recovery=adb / download / rom) and you have to put it in the mode you want before you can use it this way (adb usually works in rom or recovery, so recovery must be used when rom doesn't boot).

I'm sorry having confused you. I only wanted to make some things clear, so I wrote a lengthy post, seems it was too lengthy.

The pit repartitioning should work well in your case, because none of the critical partitions are affected.

All pits are already there in the zip, you only have to choose the correct one (looks like you already found one).

The pit for your case is very new, so no one has used it before, so it is completely untested, but I think it should work.

Of course, there's always a risk and everybody makes mistakes from time to time, but it's not a higher risk than installing a custom rom, especially in your case.

A backup would always be better, but only to be safe if something goes wrong.
[Galaxy Note GT-N7000 General] infernalMan:
hi hg42 i just want to ask.

my galaxy nexus cannot unmount sd card.

so cannot read external storage (which is i9250 doesn't have sd card slot)

is it mmc problems??

can i use pit to get back my usb storage??

thanks.
[Galaxy Note GT-N7000 General] Gotcher:
The problem now is, that I'm not really sure about the lost space of my internal SD. As I said, I'd use the file "P6200_tabplus--patched--brick-between-05007-and-15208-MB--DATAFS-shortened-by-09728-MiB". Does the part "shortened-by-09728-MiB" actually really mean that I'll loose nearly 10GB of my internal SD? :( :( BTW: Do I have to check "Re-Partition" in Odin?

When I now take a look into Odin (the Downloadmode of Galaxy Tab works fine btw), it's clear where I have to put the .pit file. But when it comes to flashing the new ROM (preferably Cyanogenmod as you said in the first post of this thread), I really have no clue what I have to do now. I know that I need either a .md5 or .tar file, but none of both can be downloaded in the CM10 thread over at the Samsung Galaxy Tab Plus section of xda (here's the link, I may have missed something: http://xdaforums.com/showthread.php?t=1842090). Where can I get the most updated version of CM10 for my device that is flashable with Odin?

I've sent you a quick PM once again. Thanks a bunch for your help! :good:

P.S.: I hope that these are the last questions before I can start unbricking my tab, it would be awesome if you can also help me with these. Especially where I can find the .tar version of the ROM and which things I have to set in Odin (maybe with a screenshot?).
[Galaxy Note GT-N7000 General] hg42:
I don't think so.

Unable to unmount? May be some app uses the partition?

Did you reboot already?
[Galaxy Note GT-N7000 General] infernalMan:
yes i already reboot and still cant read.

but i've solved this.

just flash stock factory image and its come back.

thanks.
[Galaxy Note GT-N7000 General] hg42:
Yes, may be another pit looses less space (those without shortened in their name)?

Yes

If you cannot get a tar file, you can first install a kernel with a cwm recovery (or is the recovery separate for your device?), then install the rom from there (after formatting).

You can use any custom kernel/recovery, because it will be overwritten by installing the rom. If it's like the n7000, better use a signed kernel, because otherwise the flash counter will be increased (yellow triangle). And stay away from older ics kernels/recoveries, they should mention to be emmc brick free.
[Galaxy Note GT-N7000 General] Gotcher:
There are several other .pit files for the p6200 that you uploaded which have "moved by ... MB" in their filenames. Is it maybe better to choose one of them? Problem is that I have the brick between 5120 = 5369 and 7166 = 7515, and the most fitting file with "moved by" seems to be "P6200_tabplus--patched--brick-between-01086-and-07797-MB--DATAFS-moved-by-06400-MiB". Is this the better choice?

I'm asking because there is quite a lot of space between my brick start at 5369 and the begin of the .pit repair file @ 1086... Is there something that can be improved?

Alright, thanks! :)

Have you found a .tar file in the linked thread? It's a bit strange because I'm really not able to find a flashable .tar file for the P6201... I also can not find a kernel, although I searched for it for a long time (maybe I'm overlooking something, but it seems that I won't find the correct files to revive my tab without further help/direction). :(

Sorry for being so annoying/helpless, but that's just the way it is. I'm really trying to understand all of this. :o

BTW: Is it also possible to revive the tab with the stock Honeycomb version (3.2)? Or are the .pit files only usable with a 4.x firmware? I'd install the stock Honeycomb with the .pit file and would follow the instructions of post #1 first and after that, I would try to flash CM10 via CWM recovery. Would this work?

EDIT: It seems to be that I finally have the kernel with the custom recovery (CWM version 6.0.1), thanks to dannyyung:

I flashed it via Odin, the CWM just works fine. Now I just need the correct .pit file that's preferably built exactly for my case. It would be mega-awesome if you could make me that .pit file, using the needed hole (START @ 5120 = 5369 and END @ 7166 = 7515). I really don't know how to edit those .pit files that you made available in the first thread but I also don't want to loose 10 or 7GB of internal sd space (although the hole in my case is pretty small). If I'm able to revive my tab with a custom .pit, I'll definately take a look into donating! ;)

BTW: With the new kernel + recovery, I was able to run ADB and get some more infos, does this help?

Model: MMC MAG4FA (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
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 281MB 1086MB 805MB ext4 FACTORYFS
10 1086MB 15.2GB 14.1GB DATAFS
11 15.2GB 15.7GB 537MB ext4 HIDDEN
12 15.7GB 15.8GB 8389kB FOTA

I ran the faulty block tests of the Partitions 7,9,10 and 11 twice (using forest1971's manual method) and it gives me I/O reading errors at partition 10 and 11. I'm so close to reviving my tab, I just need a fitting .pit file.
[Galaxy Note GT-N7000 General] hg42:
You can directly compare the X in moved-by-X with the Y in shortened-by-Y, 6400 is less then 9728

In theory it would be possible to assign the lost space to some partitions like system or data, but this would be for your special case. I don't have time to create special pits for several hundreds of people.

But anyway, something like a bigger system partition wouldn't help you much (for samsung devices).

I thought about a pit creator page on some server, but each case has it's special conditions. I doubt I can put together an automatic pit creator which cavers all these.

My general advice is to buy a bigger sdcard (e.g. 64gb)

Sorry, I have no spare time to look for other devices. Please ask in threads for your device.

Generally the patched pit files are designed for all roms.

This is why I keep the partition sizes and their sequence.

So yes this should work.

I'm sorry, but I think you have to...

Would be nice but doesn't change much about the facts

First revive your device, then see if it is working or if you got a moving brick
[Galaxy Note GT-N7000 General] Gotcher:
I was finally able to revive my tab, yesssss!!! :) Thank you so much! :) I now have CM10 installed.

The problem now is that I have 6,7GB free space on the internal sd. How hard is it to bring the unformatted space back and format it via CM10? Can this be done completely within the Cyanogenmod 10 ROM?

Sadly, App2SD doesn't work for the Samsung Galaxy Tab Plus N. Therefore every MB is useful ;)
[Galaxy Note GT-N7000 General] hg42:
Your internal sd is also your data partition.

Do you have an external sd?

If you keep your music, images, videos etc. on your external sd, you should have plenty of room on your datafs.

If you don't have an sdcard slot, it's more difficult.

It is possible to create an additional partition in the space after the brick and mount it in an init script (rom dependent) or a scripting app (should work on any rom but the partition is available much later in the boot process).

I personally use a script that mounts all directories from the external sd to equally named directories on my internal sdcard.

This way I can choose which directories live on which sd, but can access all via /sdcard/xxx.
[Galaxy Note GT-N7000 General] Pajorve:
Hello hg42'm pretty sure my problem relates to your topic.

My note was stuck on the boot screen and I can not quaquer form of clean data / cache'm finally using the zip descobir to the beginning of the error on the partition but he is scanning more than 7 hours without finding anything. There is no telling if freezing hesitate any corrupted block.

Could you help me?

Thanks because I do not know if I'm doing something wrong!

Thank you!
[Galaxy Note GT-N7000 General] alucard8888:
ive flashed pit and it works!!

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
[Galaxy Note GT-N7000 General] Kikasa23:
Thanks your are my hero!!!

Just saved me a trip to SSC :p
[Galaxy Note GT-N7000 General] panyan:
my mistake :p

i misread the OP :)
[Galaxy Note GT-N7000 General] travis82:
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.
[Galaxy Note GT-N7000 General] Attlon:
Great thank! Großes Dankeschön!! Огромное спасибо!!!

Is very easy and simple reviev bricked Note with the help of your file.
[Galaxy Note GT-N7000 General] shun2x:
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
[Galaxy Note GT-N7000 General] crys18:
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???
[Galaxy Note GT-N7000 General] Attlon:
Why do this???

It is enough to make here is this:

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 have so too.
[Galaxy Note GT-N7000 General] crys18:
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
[Galaxy Note GT-N7000 General] Attlon:
Why not? I guess you can - just less internal memory.

"No wipe" firmware. :)

Also I have a 32 GB of external memory MicroSD for video, music.. etc.
[Galaxy Note GT-N7000 General] crys18:
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.....
[Galaxy Note GT-N7000 General] Attlon:
cf-root 5.5??? For LPY is http://xdaforums.com/showthread.php?t=1647148
[Galaxy Note GT-N7000 General] alucard8888:
can i flash stock ICS via pc Odin? thanks..
[Galaxy Note GT-N7000 General] Attlon:
alucard8888

LPY is no wipe firmware ICS Oрen Germany http://xdaforums.com/showpost.php?p=20963707&postcount=1
[Galaxy Note GT-N7000 General] Attlon:
Probably, you will get the CWR (CWM Recovery) users kernel http://touristinparadise.blogspot.com/2012/01/samsung-galaxy-note-download-speedmod.html, and the restoration of the CWR previously made backup 2.3.6.

Read post №1.
[Galaxy Note GT-N7000 General] dark11b:
Thanks

Thank you very much man, Just fixed my Gnote with your pit file!
[Galaxy Note GT-N7000 General] thasadar:
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 )
[Galaxy Note GT-N7000 General] hg42:
repartitioning with a PIT does *not* format!

@alucard8888 and others with FCs...

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.