yashsingh1/xdaforums huggingface dataset:
[Moto G Q&A, Help & Troubleshooting] pradeeppk:
I think his moto g may not even boot normaly after flashing full sbf. It may be a hardware defect. Just searched "brick" in Q&A thread and found around 98 threads regarding bricked moto g's and most of them are remaing as bricked without solution. Is Our moto g's hardware that delicate. I have a moto defy and moto electrify, I can't found a real bricked history among them especially defy. In this case he is not even unlocked his Boot loader.
[Moto G Q&A, Help & Troubleshooting] ravibhat:
Hey [MENTION=1006674]lost101[/MENTION] : you've always been optimistic about this and i'll be open to trying and testing things you suggest :fingers-crossed:

Please share your thoughts on the way ahead.

I have an exam on Monday,so i'll be making a final decision next week.

[MENTION=6335704]sjandroiddeveloper[/MENTION] : Thanks for being straight about this and yes do i know that there's a very low chance but if there is a way to save data,i want to know,test things out before the default option of unlocking the bootloader.

Also it was said that unlocking the bootloader wipes off the data,so how does saving the data from custom recovery help? Confusing but i'm willing to try this as the last option and listening to what lost101 has to say.

And i did go to the service centre (warranty expired) - they said they will "download" a new software on the phone which will wipe the data anyway.

So if it's going to happen,I want to be one to do it. :cool:

I loved the experience since it was my first smartphone and I want to do the best I can to help it out ~ we have this weird,strange emotional bond :highfive: ~

And guys [MENTION=1006674]lost101[/MENTION] and [MENTION=6335704]sjandroiddeveloper[/MENTION] : Thanks a lot for understanding my problem,taking the time to help me out with this,I really appreciate it. :)
[Moto G Q&A, Help & Troubleshooting] sjandroiddeveloper:
[MENTION=5728533]ravibhat[/MENTION]

You got it wrong, I didn't say a custom recovery can save your data( because you gotta unlock the bootloader which wipes data partition for security reasons) ,but it can save your phone, that is I thing more important than saving the data( even if it was important)

And yes [MENTION=1006674]lost101[/MENTION] is always optimistic which is a good thing

I will still do some searching and try to find a solution for you problem in my free time
[Moto G Q&A, Help & Troubleshooting] ravibhat:
OOPs...yes ...saving the phone is the MAIN TASK.

I felt the phone only had a soft-brick and it'd be resolved soon but this is something more maybe.

Also,it has made me more aware,more grateful towards things that i have :)

One more thing - i kept the phone (black lit screen as in the video/images) on after recharging it completely and the battery drained out today morning.

This happens consistently when i keep the phone on last 2 times this week.

Is it possible that the battery is not letting the phone boot into Android even if it's charged above 50% or full most of the times.

All the flashing,testing which i do from the bootloader is always done at more than 50% battery level,usually above 90% since the phone gets charged through USB while it's connected and not switched on.

Thanks for the support :D
[Moto G Q&A, Help & Troubleshooting] sjandroiddeveloper:
I don't think that battery can stop the system or recovery to boot up

And also just so you know only today I read that moto g 2013 or 2014 has chances of getting into some serious conditions if the phone gets completely discharged ( I have even read some cases like yours)

And also FYI I have opened a discussion thread about different problems people are facing with their devices ( these problems are the ones that I came across on xda threads for moto g)

http://xdaforums.com/showthread.php?t=3128025

[Discussion][Hardbrick][Different cases]
[Moto G Q&A, Help & Troubleshooting] lost101:
[MENTION=5728533]ravibhat[/MENTION] - I'm not convinced you have understood my instruction.

It is possible to access recovery without ever seeing the Fastboot menu. This is done by turning phone off completely, and holding vol down (or up if on Lollipop BL) and pressing power button.
[Moto G Q&A, Help & Troubleshooting] ravibhat:
[MENTION=1006674]lost101[/MENTION] :

Didn't know this.

I tried it just now but it just goes in the booting process and the end result is the same blank black lit screen.

How long do i have to press it and is there any documentation i could read up about this.

I found :

a)

Here,in the comments : http://www.android.gs/enter-recovery-mode-motorola-moto-g/

People have a similar problem and one of them suggest the Power+Vol Up button is used to navigate once inside the Recovery Menu.

b)

To access Bootloader (containing Normal Powerup,Recovery,Factory,etc modes) - i press Vol Down+Power button for 5 seconds,then leave the power button first,Vol down button after that. (mentioned here http://www.teamandroid.com/2015/01/06/enter-recovery-mode-moto-g/ but i get "boot up failed" instead of the expected dead android)

Also i have this s/w called PDAnet which is able to detect the phone but not connect to it properly.

On the phone i see these commands :

USB Connected (once i connect the USB,this is common and expected)

cmd : CNXN (I don't know what this is )
[Moto G Q&A, Help & Troubleshooting] lost101:
[MENTION=5728533]ravibhat[/MENTION] - Apologies, unsure where I got the idea you could boot directly into Recovery from powered off state. Maybe I was thinking about the command: adb reboot recovery.

It looks ultimately like storage / partition corruption has occurred. There is a fastboot format command that could possibly make recovery functional again:

mfastboot format recovery​

I have not used this command and I'm unsure if it will cause any serious long-term harm - but I think it's highly unlikely. If you do the command, you could then try flashing stock recovery and custom recoveries if you wanted.

The other option is to flash the partitions table:

mfastboot flash partition gpt.bin​

This may result in your data apparently being erased if Android now boots, however you could still dump the partition to PC as an img file. This could then be processed in data recovery software. Alternatively, flashing the partition table may have no effect on access to your data.
[Moto G Q&A, Help & Troubleshooting] ravibhat:
[MENTION=1006674]lost101[/MENTION] :

If it means that the partition is corrupt,i'll be willing to unlock the phone,root it and try to recover it.

Here's the output that I got.

I'll be ready for the unlocking,rooting and recovery process from Tuesday and i've started to read up on how to do it the proper way since it'll be my first time.
[Moto G Q&A, Help & Troubleshooting] lost101:
You don't say if Android is now booting since flashing the 'partition table.'

If not, could you try flashing the system.img only as I have previously described.
[Moto G Q&A, Help & Troubleshooting] ravibhat:
[MENTION=1006674]lost101[/MENTION] :

No changes ... it's as if nothing changed despite executing those commands.

I'll try flashing system.img again.

Also,tried flashing stock Kitkat but got a message from bootloader - validation failed.

I assume this might happen since downgrade requires an unlocked bootloader.

Would like to know :

I am planning to try and go for data recovery after unlocking bootloader and using this guide as reference.

[GUIDE] Internal Memory Data Recovery - Yes We Can!

http://xdaforums.com/galaxy-nexus/general/guide-internal-memory-data-recovery-yes-t1994705

a)What's the first thing i can do after unlocking the bootloader?

install custom recovery?which one?

I've come across

a)Clockwork Mod

b)Philz's touch

c)TWRP

b)would you suggest flashing it with Kitkat or Lollipop?

c)What's a good way to root it so that the erased partition will have limited overwrites so that recovery can be better.

d)Anything else i can do to ensure that data recovery would be easier - any softwares,links,etc.
[Moto G Q&A, Help & Troubleshooting] lost101:
[MENTION=5728533]ravibhat[/MENTION] - All you need to do is flash or boot into latest TWRP after unlocking.

adb pull /dev/block/platform/msm_sdcc.1/by-name/userdata​

That should dump to your PC the entire userdata partition.
[Moto G Q&A, Help & Troubleshooting] ravibhat:
WOW!

Thanks [MENTION=1006674]lost101[/MENTION]

I just did this (unlocked the bootloader using instructions from the motorola website and booted using TWRP 2.8.6.0) and my data (internal SD card) was still intact.

Unlocking the bootloader apparently didn't delete the files but TWRP recovery says Internal Storage = 0 MB.

Was able to recover almost everything on the SD Card (pictures,WhatsApp,musics,app data) using :

ADB PULL /sdcard "backup_directory here"

This wasn't accessible earlier but TWRP recovery enabled it i guess :)

I also flashed Android 5.0.2 again but it doesn't boot up,same problem as before.

Got a doubt :

a) where is the data from Google Keep stored? (sync was disabled,so i can't recover)

b) I had 2 profiles and used WhatsApp on both profiles.i was able to recover one of these,where is the other stored?

It only shows "sdcard" and the filesystem on the phone had sdcard/0 and sdcard/1 which i couldn't find.

Also got an error while accessing "userdata" using adb shell command.

Now i have :

a)access to fastboot (as before)

b)TWRP recovery - able to boot up using this,able to flash but doesn't get detected

TWRP also says "cannot mount /data" -> this is the problem i guess?

c)Can use ADB when using TWRP recovery

d)Stock recovery flashed while flashing Android 5.0.2 now WORKS!

I want to :

a)recover WhatsApp data if possible as mentioned above?

b)install fresh OS since current one is corrupt/not booting.

Any tips about the way ahead? :D

Also tagging : [MENTION=4483948]pradeeppk[/MENTION] [MENTION=6335704]sjandroiddeveloper[/MENTION] since they helped as well :)
[Moto G Q&A, Help & Troubleshooting] lost101:
[MENTION=5728533]ravibhat[/MENTION] - You will find more app data / profiles in /data/app and /data/data. Unable to check right now, but I think you can also access SDCARD via /data/media
[Moto G Q&A, Help & Troubleshooting] ravibhat:
Hey [MENTION=1006674]lost101[/MENTION] :

the /data folder in TWRP appears to be empty

Also,adb pull returns this :

X:\IDM Downloads\@@@@MotoI\@TEST\mfastboot-v2>adb pull /data S:\temp

pull: building file list...

0 files pulled. 0 files skipped.

i get this error in the log :

Full Image : http://i.imgur.com/cfkwXeI.png

[URL="http://i.imgur.com/cfkwXeI.png"][IMG]http://i.imgur.com/cfkwXeIt.png[/IMG][/URL]

Do you think my /data partition is corrupted?
[Moto G Q&A, Help & Troubleshooting] lost101:
[MENTION=5728533]ravibhat[/MENTION] - in TWRP > Advanced > File Manager - I can see my /data partition files. Try unmount and remount in TWRP or the command: adb remount

Also alternative way to SDCARD is /data/media/0/
[Moto G Q&A, Help & Troubleshooting] ravibhat:
[MENTION=1006674]lost101[/MENTION] :

Dude,i tried and searched a lot but i'm not able to find out the other WhatsApp folder ( i had 2 user profiles in Android L).

Also made a treelist.txt which helped in the recovery process.Remounting didn't work.

/data appears empty in both TWRP File Manager as well through "adb shell" command.

It also doesn't allow to COPY dev/block files i.e. "adb pull" skips these files and shows "special files skipped".

Do you think the /data partition is corrupt and is there a way to recover it?
[Moto G Q&A, Help & Troubleshooting] lost101:
[MENTION=5728533]ravibhat[/MENTION] - It might be worth trying philz touch recovery if you can.

If you make an image dump of the /data partition - you can process that in data recovery software on PC. Make sure you dump the partition directly to PC Hard disk or OTG USB storage and not internal storage.
[Moto G Q&A, Help & Troubleshooting] ravibhat:
WHOAAAAAAAAAAAAAAAAA!
[MENTION=1006674]lost101[/MENTION] :

Finally recovered everything I had on my sdcard including WhatsApp folders with databases,pictures,videos,etc.

Texts and Contacts were visible in Coolmuster Lab Phone software but i don't have a premium version.

Fortunately,contacts are synced with the Google Account so that's not an issue.

I used a modded version of Philz Touch Recovery i found in one of the threads somewhere here (Will post detailed info a little later).

Philz Touch : http://i.imgur.com/Z5mUTa1.jpg

WhatsApp recovery using adb pull command from /data/media/0 or 11 or 12 or some number depending on your profile

Accessing /sdcard also redirects here.

TWRP wasn't able to mount /data partition successfully but fortunately i got the Philz CWM mod.

Will post a brief summary of the things that i did again for people facing the same issues :D

My phone is now unlocked and rooted (Supersu flashed in TWRP using .zip file) and i'll also install a CLEAN Android 5.0.2 in the next few days.

Hopefully,will mark this thread as "RESOLVED" by then :D

A lot of people including the Motorola Support (online chat and forums both),Motorola Local Service centre,Advanced Android users,etc told me that there's very little I could do to save my data but it never made sense to my newbie mind,maybe this a miracle but it feels really good to make it happen.

A BIG SPECIAL THANKS to [MENTION=1006674]lost101[/MENTION] who has been a kickass guy for being so supportive to a newbie like me throughout the entire process in the last few weeks :laugh: (will pm you in a bit dude,it's been great experience to learn so much from you :) )

Also thanks to the people here @ XDA,my friends and all those who saw my thread and gave their advice.

If you are facing similar issues,feel free to contact me so that we can find a solution.I'll be glad if I could be of any help.
[Moto G Q&A, Help & Troubleshooting] lost101:
You deserve a cigar after all that. Congratulations - with enough patience and determination, the impossible becomes possible.
[Moto G Q&A, Help & Troubleshooting] spanda12:
Same issue.

Hello Ravi.

I've having the exact same issue as yours,down to the last dot

Could you please explain how you recovered your phone? I don't mind losing my data(I probably have as I did try a factory reset).

I did try flashing the stock rom but to no avail.

TIA
[Moto G Q&A, Help & Troubleshooting] animesh1558:
[MENTION=252131]lost[/MENTION] pls help on my issue..... pls....!!

http://xdaforums.com/moto-g/help/help-please-moto-g-weird-brick-t3145082
[Moto G Q&A, Help & Troubleshooting] ravibhat:
Of course dude,i'll pm you in about 5mins from now.
[Moto G Q&A, Help & Troubleshooting] ravibhat:
Thanks [MENTION=1006674]lost101[/MENTION] Man.

Data recovery was very successful.

I am facing another challenge with the installation now.

Able to access : Stock recovery,boot directly from the .img of TWRP and Philz but flashing them and then going into recovery doesn't help as it goes into the default stock recovery.

I tried installing STOCK ROM available in one of these threads both manually as well through recoveries here but it didn't help.

No errors while flashing manually but did get a few while using recoveries :TWRP and Philz Touch

Tried to install through USB OTG,then ADB Sideload.

Here are the pictures of the o/p @ the terminal screen :

http://i.imgur.com/3RZBV4gundefined.jpg

http://i.imgur.com/p0rsznZundefined.jpg

http://i.imgur.com/yrzLTKNundefined.jpg

http://i.imgur.com/MiB4CmLundefined.jpg

Let me know what i can do.

Also tagging : [MENTION=4483948]pradeeppk[/MENTION] [MENTION=6335704]sjandroiddeveloper[/MENTION] since they might have a solution.
[Moto G Q&A, Help & Troubleshooting] lost101:
@ ravibhat - have you tried formating /data in TWRP?
[Moto G Q&A, Help & Troubleshooting] ravibhat:
Yes,that's one of the first things i did after the backup.

But it says "Failed" when i try to do that.

The "mfastboot erase userdata" works without any error.
[Moto G Q&A, Help & Troubleshooting] lost101:
[MENTION=5728533]ravibhat[/MENTION] - Make sure /data is unmounted in TWRP. Then try formating, or changing format from EXT4 to F2FS or vice-versa.

If you still make not progress, use the follow commands to manually format /userdata: (again ensure /data is unmounted)

adb shell

killall -19 recovery

make_ext4fs /dev/block/mmcblk0p37

reboot​

/data (userdata) will now be formated to EXT4, so either boot the XT1032 GPE ROM zip or try changing the format to F2FS to boot XT1033 Retail Asia Stock ROM zip - both are available here: http://xdaforums.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
[Moto G Q&A, Help & Troubleshooting] Pours:
Guys can i have your help? I was fine with my MOTO G X1309 and had the TWRP recovery until i tried to install the new version and messed up. I flashed official stock 5.1, but i can't flash custom recovery.!!! It finishes everything good when i flash but when i try to hit recovery it says Boot up failed! I have tried every custom recovery but nothing seems to work! Please help me!
[Moto G Q&A, Help & Troubleshooting] ravibhat:
[MENTION=1006674]lost101[/MENTION] : Hey man,directly changing file format did not work in TWRP.

Also i got this error while following the steps you mentioned :

Also i had earlier found a post mentioning the partition table for the device :

http://xdaforums.com/showthread.php?t=2540799

Can't find "mmcblk0p37" in the first few posts,it's there for GPE devices which mine isn't - could this be the reason?

Also in TWRP internal storage is shown as 0 MB and E:cant mount /data error exists as well.

Images from adb shell:
[Moto G Q&A, Help & Troubleshooting] lost101:
Apologies. With non-GPE, /data (userdata) is:

/dev/block/mmcblk0p36​
[Moto G Q&A, Help & Troubleshooting] ravibhat:
Ok...it does this and is now stuck for a while :

Will it take like a few hours or something,i read this in another thread for a similar command?

Also,internal storage shows 0 MB and i was unable to format it.

Also,i am supposed to flash "XT1032_GPE_5.1_Untouched.zip" after this is sorted,correct?
[Moto G Q&A, Help & Troubleshooting] ravibhat:
Hey [MENTION=1006674]lost101[/MENTION],

I executed all the commands and it rebooted to recovery mode probably since no O.S. exists.

Internal storage still shows 0 MB.

You said "make sure /data is not mounted" - how do i do that exactly in TWRP or by adb or by mfastboot?Please explain this step.

Tried flashing ""XT1032_GPE_5.1_Untouched.zip" from the link you gave but got this error.

FULL CLEAR IMAGE HERE : http://i.imgur.com/MnnrKVJ.jpg
[Moto G Q&A, Help & Troubleshooting] lost101:
TWRP > Mount > Unselect Data
[Moto G Q&A, Help & Troubleshooting] lost101:
[MENTION=5728533]ravibhat[/MENTION] - Something else to try: (unmount /data first)

adb shell

e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata

(You should now be prompted to repair or fix errors. Press [Enter] key to use the default answer of (y) for yes.)

(Continue pressing [Enter] until the process completes.)

(mount /data as read-only for now)

mount /dev/block/platform/msm_sdcc.1/by-name/userdata /data

(browse to your /data and /sdcard partitions - ‘cd /data’ for /data, and ‘cd /data/media/0’ OR ‘cd /sdcard’ for your /sdcard)​

Source: http://xdaforums.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447
[Moto G Q&A, Help & Troubleshooting] ravibhat:
Ok [MENTION=1006674]lost101[/MENTION],i deselected everything 'Mount' section of twrp and data wasn't selected earlier as well.

Is there a manual command to unmount /data to solve the ^ issue?
[Moto G Q&A, Help & Troubleshooting] lost101:
adb shell

umount /data​

I just tested to confirm this is working.
[Moto G Q&A, Help & Troubleshooting] ravibhat:
Says "invalid arg"
[Moto G Q&A, Help & Troubleshooting] lost101:
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?

http://xdaforums.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793​
[Moto G Q&A, Help & Troubleshooting] ravibhat:
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
[Moto G Q&A, Help & Troubleshooting] lost101:
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​
[Moto G Q&A, Help & Troubleshooting] lost101:
[MENTION=5728533]ravibhat[/MENTION]- I made an error in the previous commands. Re-do them.
[Moto G Q&A, Help & Troubleshooting] ravibhat:
[MENTION=1006674]lost101[/MENTION] :

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
[Moto G Q&A, Help & Troubleshooting] lost101:
[MENTION=5728533]ravibhat[/MENTION]- I've edited previous commands. Please retry them.