PIT file method to revive your phone from a MMC_CAP_ERASE brick

[parwathy]

first, flash a pit with "kernel" in it's name, because your kernel partition seems to be damaged, too.
Use one with a high number after "moved-by" first, e.g start with moved-by-8192 which is half of your 16gb memory.
Then try to flash a kernel+recovery combo.
If that doesn't flash, try higher numbers after "moved-by".
If none works, you seem to be out of luck...

If the recovery works, use the scanners to find the real brick position.
Then flash an appropriate pit file using the begin and end numbers for selection.

good luck...

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?

 

[hg42]

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?

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.

 

[hg42]

why the gap cannot start at arbitrary positions

Can u pls link/create pit for N7000 emmc bug STARTS 1500 / END 4580?

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...

 

[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?

 

[hg42]

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?

usually not the kind of brick discussed here, search xda (or Google) for kind of (probably) soft bricks

 

[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".

 

[hg42]

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".

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?

 

[bluehawk20]

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?

Tried in recovery failed as well.

Not very familiar or should i say don't know the correct commands for adb shell.

 

[mastro:°]

i have efs partition currped in i9100 wich pit choud i flash with odin ??

 

[hg42]

i have efs partition currped in i9100 wich pit choud i flash with odin ??

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.

 

[mastro:°]

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.

got it thanx you are the men :highfive:

 

[Vegan1983]

MY MT6575 EMMC is Erased and no partitions are there... Please help

Solved by self treatment

 

[hg42]

you are crying very loud...

My MT6575 baseband Chipset mobile phone is now EMMC Bricked. I used SP Flash tool for formatting the flash but It removed all required partitions and now backup download by SPflash tool is useless.

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.

No boot to OS. No recovery partition so no any recovery mode. Please tell me how I can restore partitions back? I have a same mobile phone modal of my friend which is working fine. So I can copy format structure and write it on my EMMC but I need the tool which will do that. Please tell me what is the way of the solution?

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.

 

[Vegan1983]

Thanks but You need to understand it well now...

Solved by self treatment

 

[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!

 

[hg42]

this thread only applies to some samsung devices

 

[hg42]

emmc brick should be triggered by ics kernels only

 

[aetewy]

very good man

 

[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?

 

[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!