5,594,564 Members 32,936 Now Online
XDA Developers Android and Mobile Development Forum

PIT file method to revive your phone from a MMC_CAP_ERASE brick

Tip us?
 
Mogi
Old
#21  
Member
Thanks Meter 0
Posts: 49
Join Date: Oct 2006
Thks hg42. Your post is detail and thks for sharing the workaround for ICS brick.

Sent from my GT-N7000 using xda premium
Samsung Galaxy N7000

Firmware: DXLC2
Kernel: DXLC1 CF-Root
 
hg42
Old
#22  
hg42's Avatar
Senior Member - OP
Thanks Meter 537
Posts: 609
Join Date: Feb 2011

 
DONATE TO ME
Quote:
Originally Posted by neos_83 View Post
thanks for the link.

I searched for similar kinds of solutions and didn't find one, but probably searched in a slightly different direction. So again, your always wiser after the event...:)

That post has some better discussion of backgrounds and reasons about what to move where. Also the conversion from ext2 to ext4 has more details, also different options to e2fsck. And finally, there are two packages attached, which could be useful for the fix.
Generally it is worth reading. Thanks neos...
 
hg42
Old
#23  
hg42's Avatar
Senior Member - OP
Thanks Meter 537
Posts: 609
Join Date: Feb 2011

 
DONATE TO ME
Quote:
Originally Posted by Mogi View Post
Your post is detail
well, it could be much more detailed.
But most people don't like my generally really long posts.
So I cropped it in many ways.

If someone wants to discuss some points, please just ask!
 
hg42
Old
#24  
hg42's Avatar
Senior Member - OP
Thanks Meter 537
Posts: 609
Join Date: Feb 2011

 
DONATE TO ME
btw. should I move the real content of my thread from my second post into the first?
What do you think? That wouldn't make the real content more visible, but would make all those funny small comments look like nonsense :) (which is nice, ha ha)
 
stephencwl
Old
#25  
Senior Member
Thanks Meter 34
Posts: 356
Join Date: Apr 2006
Great to hear it actually works. Pretty straight forward for those linux versatile guru.

It's fun to read your attempt. Thanks.
Previous PDA/Phones:
Handspring Visor Delux ->HP2100->Mio8390->Dopod818Pro->HTC Hermes->Touch HD--> galaxy S --> Galaxy Note
 
Narada2XK
Old
#26  
Narada2XK's Avatar
Senior Member
Thanks Meter 17
Posts: 388
Join Date: Aug 2010
Location: Bridgetown
~ # e2fsck -c /dev/block/mmcblk0p9
e2fsck 1.41.12 (17-May-2010)
/dev/block/mmcblk0p9: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 46753, block #0, offset 0: directory corrupted
Salvage<y>?

Is this supposed to happen or do I indeed have a corrupted directory?
 
ukicar
Old
#27  
ukicar's Avatar
Senior Member
Thanks Meter 1634
Posts: 1,510
Join Date: Jan 2011
Location: Београд
Quote:
Originally Posted by hg42 View Post
btw. should I move the real content of my thread from my second post into the first?
What do you think? That wouldn't make the real content more visible, but would make all those funny small comments look like nonsense :) (which is nice, ha ha)
not necessary but it would be useful


 
prasad.adam
Old
#28  
Senior Member
Thanks Meter 37
Posts: 319
Join Date: Jul 2010
Location: Mumbai
Seems a simple to follow process. I am, luckily, not the bricked one but good to know that the fix is now available. Great contribution!
 
hg42
Old
(Last edited by hg42; 23rd October 2012 at 09:28 PM.)
#29  
hg42's Avatar
Senior Member - OP
Thanks Meter 537
Posts: 609
Join Date: Feb 2011

 
DONATE TO ME
Quote:
Originally Posted by Narada2XK View Post
~ # e2fsck -c /dev/block/mmcblk0p9
e2fsck 1.41.12 (17-May-2010)
/dev/block/mmcblk0p9: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 46753, block #0, offset 0: directory corrupted
Salvage<y>?

Is this supposed to happen or do I indeed have a corrupted directory?
you have a corrupted directory structure, but you don't know the reason.

This is often repairable, but...
If you have bad blocks from a MMC_CAP_ERASE brick, e2fsck will probably get stuck somewhere.
From what I read, there seem to be people having only blocks overwritten with zeros but not damaged ones.
Also, I don't really know what kind of bad blocks my phone has now, they can't be read nor written to. Each software accessing them seems to get stuck.

In general such an fsck error can only occur when the system is stopped suddenly somewhere in the middle of some kind of writing to disk or the system has a bug somewhere.
Some standard PC scenarios do not apply or should be uncommon:
- power switched off
You can't do that with the power switch. When battery is running out of power you get a warning and if you ignore this the phone finally shuts down itself in an orderly manner.
But you can indeed pull the battery, so beware, don't do this if you don't need to and always wait some minute or two.
- system crash, blue screen etc.
I never saw something like this on android, did you?
Linux is generally very stable and most instabilities have to do with crappy PC hardware or undocumented hardware interfaces etc. Android hardware seems to be designed much cleaner.
But there are also some critical items: overclocking or undervolting if not tested thoroughly, patching and tweaking kernels and root apps accessing hardware or disks may lead to disk failures too.
 
breckbit
Old
#30  
Senior Member
Thanks Meter 39
Posts: 176
Join Date: Dec 2006
Location: Aix la Chapele
Quote:
Originally Posted by Zamboney View Post
Wow man, that seemed really simple and straight forward. Next week well learn how to copy a file in Android, now that will be much trickier...


Thanks anyway for your efforts!

Sent from my GT-N7000 using Tapatalk 2
Seems you donīt realize what the thread-opener is writing about... Itīs not that simple to repartition the emmc...

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes