[Being resolved!] MotoG Bootup Problem - Recovery Mode failed

ravibhat

Senior Member
Feb 16, 2014
59
7
0
Ok,this command worked but there's a new error.
I tried a command "mke2fs /dev/block/platform/msm_sdcc.1/by-name/userdata" which worked.
Here's the output of both the commands.
http://android.stackexchange.com/questions/88277/corrupted-data-partition




Try:
# umount -f /dev/block/mmcblk0p36​


---------- Post added at 09:49 AM ---------- Previous post was at 09:46 AM ----------

Have you considered flashing the v41.19 Falcon Bootloader?
 

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,328
0
Try:
mke2fs -n /dev/block/mmcblk0p36

e2fsck -b 4096 /dev/block/mmcblk0p36

mke2fs -b 4096 -g 32768 -S /dev/block/mmcblk0p36

e2fsck /dev/block/mmcblk0p36

[Yes to any Fix requests]

mount /data
df​
 
Last edited:
  • Like
Reactions: ravibhat

ravibhat

Senior Member
Feb 16, 2014
59
7
0
Ok,i did and 2 of them related to "mke2fs" didn't seem to execute properly.
Here's the output :
X:\IDM Downloads\@@@@MotoI\@TEST\mfastboot-v2>adb shell
~ # ←[6nmke2fs -n /dev/block/mmcblk0p36
mke2fs -n /dev/block/mmcblk0p36
mke2fs 1.42.9 (28-Dec-2013)
/dev/block/mmcblk0p36 is apparently in use by the system; will not make a filesy
stem here!
~ # ←[6numount -f /dev/block/mmcblk0p36
umount -f /dev/block/mmcblk0p36
~ # ←[6nmke2fs -n /dev/block/mmcblk0p36
mke2fs -n /dev/block/mmcblk0p36
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
846976 inodes, 3386336 blocks
169316 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3468689408
104 block groups
32768 blocks per group, 32768 fragments per group
8144 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

~ # ←[6n e2fsck -b 8193 /dev/block/mmcblk0p36
e2fsck -b 8193 /dev/block/mmcblk0p36
e2fsck 1.42.9 (28-Dec-2013)
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
36

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # ←[6n mke2fs -b 4096 -g 8192 -S /dev/block/mmcblk0p36
mke2fs -b 4096 -g 8192 -S /dev/block/mmcblk0p36
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
847872 inodes, 3386336 blocks
169316 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1077936128
414 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8192, 24576, 40960, 57344, 73728, 204800, 221184, 401408, 663552,
1024000, 1990656, 2809856

Allocating group tables: done
Writing superblocks and filesystem accounting information: done

~ # ←[6n e2fsck /dev/block/mmcblk0p36
e2fsck /dev/block/mmcblk0p36
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
36

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # ←[6n mount /data
mount /data
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 445808 32 445776 0% /dev
tmpfs 445808 445808 0 100% /tmp
/dev/block/sda1 15133280 14309984 823296 95% /usb-otg
/dev/block/mmcblk0p33
667328 107216 560112 16% /cache
/dev/block/mmcblk0p36
13543280 9942104 3503016 74% /data
~ # ←[6n

Would you suggest trying the 41.19 bootloader script?
What would be the way ahead after that's done?

Try:
.....
mke2fs -b 4096 -g 8192 -S /dev/block/mmcblk0p36
.....​
 

ravibhat

Senior Member
Feb 16, 2014
59
7
0
@lost101 :
Ok,similar output but new error for that changed command :

~ # ←[6nmke2fs -n /dev/block/mmcblk0p36
mke2fs -n /dev/block/mmcblk0p36
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
846976 inodes, 3386336 blocks
169316 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3468689408
104 block groups
32768 blocks per group, 32768 fragments per group
8144 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

~ # ←[6n e2fsck -b 8193 /dev/block/mmcblk0p36
e2fsck -b 8193 /dev/block/mmcblk0p36
e2fsck 1.42.9 (28-Dec-2013)
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
36

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # ←[6n mke2fs -b 4096 -g 8193 -S /dev/block/mmcblk0p36
mke2fs -b 4096 -g 8193 -S /dev/block/mmcblk0p36
mke2fs: blocks per group must be multiple of 8
~ # ←[6n e2fsck /dev/block/mmcblk0p36
e2fsck /dev/block/mmcblk0p36
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
36

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # ←[6n mount /data
mount /data
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 445808 32 445776 0% /dev
tmpfs 445808 445808 0 100% /tmp
/dev/block/sda1 15133280 14309984 823296 95% /usb-otg
/dev/block/mmcblk0p33
667328 107216 560112 16% /cache
/dev/block/mmcblk0p36
13543280 9942104 3503016 74% /data
~ # ←[6n

@ravibhat- I made an error in the previous commands. Re-do them.
 

ravibhat

Senior Member
Feb 16, 2014
59
7
0
@lost101 : retried.
i did unmount /data before executing them,hope this needs to be done?
output is here :
~ # ←[6numount /data
umount /data
~ # ←[6nmke2fs -n /dev/block/mmcblk0p36
mke2fs -n /dev/block/mmcblk0p36
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
846976 inodes, 3386336 blocks
169316 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3468689408
104 block groups
32768 blocks per group, 32768 fragments per group
8144 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

~ # ←[6n e2fsck -b 8193 /dev/block/mmcblk0p36
e2fsck -b 8193 /dev/block/mmcblk0p36
e2fsck 1.42.9 (28-Dec-2013)
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
36

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # ←[6n mke2fs -b 8193 -g 32768 -S /dev/block/mmcblk0p36
mke2fs -b 8193 -g 32768 -S /dev/block/mmcblk0p36
Warning: blocksize 8193 not usable on most systems.
mke2fs 1.42.9 (28-Dec-2013)
mke2fs: 8192-byte blocks too big for system (max 4096)
Proceed anyway? (y,n) y
y
Warning: 8192-byte blocks too big for system (max 4096), forced to continue
Filesystem label=
OS type: Linux
Block size=8192 (log=3)
Fragment size=8192 (log=3)
Stride=0 blocks, Stripe width=0 blocks
846976 inodes, 1693168 blocks
84658 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1736441856
52 block groups
32768 blocks per group, 32768 fragments per group
16288 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables: done
Writing superblocks and filesystem accounting information: done

~ # ←[6n e2fsck /dev/block/mmcblk0p36
e2fsck /dev/block/mmcblk0p36
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
36

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # ←[6n mount /data
mount /data
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 445808 32 445776 0% /dev
tmpfs 445808 445808 0 100% /tmp
/dev/block/sda1 15133280 14309984 823296 95% /usb-otg
/dev/block/mmcblk0p33
667328 107216 560112 16% /cache
/dev/block/mmcblk0p36
13543280 9942104 3503016 74% /data
~ # ←[6n

@ravibhat- I've edited previous commands. Please retry them.
 

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,328
0
@ravibhat - Commands updated again. Re-try. Also regarding Bootloader - this could be all be directly related to Bootloader corruption. Flashing a new one may fix this situation. It may also hard-brick your phone - as there is corruption - but hopefully not.
 
Last edited:
  • Like
Reactions: pradeeppk

ravibhat

Senior Member
Feb 16, 2014
59
7
0
@lost101 :
ok here's the new o/p
~ # ←[6nmke2fs -n /dev/block/mmcblk0p36
mke2fs -n /dev/block/mmcblk0p36
mke2fs 1.42.9 (28-Dec-2013)
/dev/block/mmcblk0p36 is apparently in use by the system; will not make a filesy
stem here!
~ # ←[6numount /data
umount /data
~ # ←[6nmke2fs -n /dev/block/mmcblk0p36
mke2fs -n /dev/block/mmcblk0p36
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
846976 inodes, 3386336 blocks
169316 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3468689408
104 block groups
32768 blocks per group, 32768 fragments per group
8144 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

~ # ←[6n e2fsck -b 4096 /dev/block/mmcblk0p36
e2fsck -b 4096 /dev/block/mmcblk0p36
e2fsck 1.42.9 (28-Dec-2013)
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
36

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # ←[6n mke2fs -b 4096 -g 32768 -S /dev/block/mmcblk0p36
mke2fs -b 4096 -g 32768 -S /dev/block/mmcblk0p36
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
846976 inodes, 3386336 blocks
169316 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3468689408
104 block groups
32768 blocks per group, 32768 fragments per group
8144 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done
Writing superblocks and filesystem accounting information: done

~ # ←[6n e2fsck /dev/block/mmcblk0p36
e2fsck /dev/block/mmcblk0p36
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
36

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # ←[6n mount /data
mount /data
d~ # ←[6ndf
ddf
/sbin/sh: ddf: not found
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 445808 32 445776 0% /dev
tmpfs 445808 445808 0 100% /tmp
/dev/block/sda1 15133280 14309984 823296 95% /usb-otg
/dev/block/mmcblk0p33
667328 107216 560112 16% /cache
/dev/block/mmcblk0p36
13543280 9942104 3503016 74% /data
~ # ←[6n


I will take this to the service centre and see if those guys can help,if not,i'll try upgrading the bootloader.
BTW how did you infer that the bootloader is corrupt?
I was able to boot directly into TWRP,Philz Touch but not flash them i.e. mfastboot boot twrp.img works while mfastboot flash recovery twrp.img will revert back to stock recovery after reboot.
Also i thought the problem is with the partition table and maybe the internal sd card and not the bootloader as such.
@sjandroiddeveloper : any thoughts on this?

@ravibhat - Commands updated again. Re-try. Also regarding Bootloader - this could be all be directly related to Bootloader corruption. Flashing a new one may fix this situation. It may also hard-brick your phone - as there is corruption - but hopefully not.
 
Last edited:

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,328
0
@ravibhat - The Bootloader plays a role in how the Kernel functions - it's not an isolated partition. I'm seeing the problem you are experiencing when people apply an OTA Update - which includes Bootloader patching.

EDIT: I would flash the entire GPE 5.1 Firmware Image - which includes a different Bootloader and gpt.bin. That might be a dramatic enough change to resolve this. Normally it is easy to convert back to Dual-SIM.
 
Last edited:
  • Like
Reactions: ravibhat

ravibhat

Senior Member
Feb 16, 2014
59
7
0
Ok man,will do this after a trip to the service centre to see if they can help since i've recovered my data thanks to you :)
Will report back in a week or two.
Thanks a ton for helping out massively along the journey :)
@ravibhat - The Bootloader plays a role in how the Kernel functions - it's not an isolated partition. I'm seeing the problem you are experiencing when people apply an OTA Update - which includes Bootloader patching.

EDIT: I would flash the entire GPE 5.1 Firmware Image - which includes a different Bootloader and gpt.bin. That might be a dramatic enough change to resolve this. Normally it is easy to convert back to Dual-SIM.
 
  • Like
Reactions: lost101

mrawal031

Member
Aug 9, 2015
8
0
0
please help

i am facing the exact same problem as u were facing.
please can u help me by posting a step by step instruction on how to recover my data from my semi dead phone.
please help me if u can i am quite new at all this so please save my phone.

thanks a ton in advanced @ravibhat
 

ravibhat

Senior Member
Feb 16, 2014
59
7
0
The reason i was able to recover my data was only due to the helpfulness of the people out here.
And i would love to help out in any way that i can to help you get your data as well.

Ok @mrawal031 first create a new thread on this forum and tag me so that i can see the similarity and help you.
See my first post and add complete details so we can get started.
As you do that,read this entire thread and you'll get the answer - basically you have to unlock your bootloader,install custom recovery,use ADB - the entire how is documented in detail in this thread itself.

If you still need more help,tag me in a comment in your thread and i will respond as soon as i can.
All the best man! :D

i am facing the exact same problem as u were facing.
please can u help me by posting a step by step instruction on how to recover my data from my semi dead phone.
please help me if u can i am quite new at all this so please save my phone.

thanks a ton in advanced @ravibhat
 
  • Like
Reactions: gabriel32mty

ravibhat

Senior Member
Feb 16, 2014
59
7
0
So i finally went to the service centre again and they claimed that the motherboard is damaged.
I don't know whether this can be classified as a hard brick or not since i am able to access the bootloader.
Will try flashing the latest bootloader as suggested by @lost101.
 

rohit1111

New member
Aug 31, 2015
2
1
0
I'm Also GEtting SAme Problem in moto g 2 XT1068

I Have unlocked boot-loader and rooted also but when i installed chain-fire 3d and installed update my phone suddenly turn off then i installed twrp recovery then when i select recovery it says "boot up failed" plzz help :(:(@ravibhat
 
Last edited:

gabriel32mty

Member
Aug 19, 2015
22
2
0
So i finally went to the service centre again and they claimed that the motherboard is damaged.
I don't know whether this can be classified as a hard brick or not since i am able to access the bootloader.
Will try flashing the latest bootloader as suggested by @lost101.
What happened did it work???
im having the same issue can you explain how did you unblock the bootloader that is the first step but you did not mentioned how to do it or if you followed another post threat
please help me i have a moto g xt1032 and i want to recover the photos i have in there
:good:
 
May 3, 2015
10
1
0
Has solution?

My moto G has a the same problem but I don't know how to fix it. You can fix it? You can help me? What's the solution?

---------- Post added at 10:36 PM ---------- Previous post was at 10:16 PM ----------

So i finally went to the service centre again and they claimed that the motherboard is damaged.
I don't know whether this can be classified as a hard brick or not since i am able to access the bootloader.
Will try flashing the latest bootloader as suggested by @lost101.
My moto G x1032 has the same problem. I don't care the information, I want my cell with life T:T Help me
 

gabriel32mty

Member
Aug 19, 2015
22
2
0
@rohit1111 - @gabriel32mty - @alfredo_figueroa - If you want solutions, I recommend you start new threads in Q & A providing incredible amounts of detail about everything that has happened and everything you have done to try to resolve it.
do i have to start a new thread?? since we all have the same issue,
anyway what happened with the cellphone did it come back to life ornot??
im about to unlock the bootloader since my cell does not have guarantee anymore