Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

PIT file method to revive your phone from a MMC_CAP_ERASE brick

OP hg42

23rd May 2012, 02:14 AM   |  #21  
Member
Thanks Meter: 0
 
49 posts
Join Date:Joined: Oct 2006
More
Thks hg42. Your post is detail and thks for sharing the workaround for ICS brick.

Sent from my GT-N7000 using xda premium
23rd May 2012, 06:59 AM   |  #22  
hg42's Avatar
OP Senior Member
Thanks Meter: 547
 
623 posts
Join Date:Joined: Feb 2011
Donate to Me
More
Quote:
Originally Posted by neos_83

This is the same method here:
http://forum.xda-developers.com/show...7&postcount=12

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...
23rd May 2012, 07:03 AM   |  #23  
hg42's Avatar
OP Senior Member
Thanks Meter: 547
 
623 posts
Join Date:Joined: Feb 2011
Donate to Me
More
Quote:
Originally Posted by Mogi

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!
23rd May 2012, 07:07 AM   |  #24  
hg42's Avatar
OP Senior Member
Thanks Meter: 547
 
623 posts
Join Date:Joined: Feb 2011
Donate to Me
More
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)
23rd May 2012, 07:16 AM   |  #25  
Senior Member
Thanks Meter: 37
 
369 posts
Join Date:Joined: Apr 2006
Great to hear it actually works. Pretty straight forward for those linux versatile guru.

It's fun to read your attempt. Thanks.
23rd May 2012, 07:32 AM   |  #26  
Narada2XK's Avatar
Senior Member
Flag Bridgetown
Thanks Meter: 19
 
394 posts
Join Date:Joined: Aug 2010
~ # 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?
23rd May 2012, 08:32 AM   |  #27  
ukicar's Avatar
Senior Member
Flag Београд
Thanks Meter: 1,649
 
1,525 posts
Join Date:Joined: Jan 2011
Quote:
Originally Posted by hg42

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
23rd May 2012, 08:51 AM   |  #28  
Senior Member
Flag Mumbai
Thanks Meter: 37
 
331 posts
Join Date:Joined: Jul 2010
More
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!
24th May 2012, 10:31 AM   |  #29  
hg42's Avatar
OP Senior Member
Thanks Meter: 547
 
623 posts
Join Date:Joined: Feb 2011
Donate to Me
More
Quote:
Originally Posted by Narada2XK

~ # 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.
Last edited by hg42; 23rd October 2012 at 10:28 PM.
24th May 2012, 10:45 AM   |  #30  
Senior Member
Flag Aix la Chapele
Thanks Meter: 39
 
183 posts
Join Date:Joined: Dec 2006
More
Quote:
Originally Posted by Zamboney

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

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes