[SOLVED] Moto G Boot Default to Recovery - Moto G Q&A, Help & Troubleshooting

Dear friends.. My Moto G default boot is always going to recovery. The way i could enter the system/rom is just with Bootloader option "Normal powerup". I already try many ways, reflash custom recovery (TWRP, CWM, CM), reflash stock, and reflash custom rom, but they do nothing to this case. Is there any way to change it back to normal? I'm currently on CM 12.1 Unofficial and running TWRP 2.8.6.0. It is not so bad since i still can access the system, it just anoying that couldn't restart device straight to system. Thanks in advance guys..
[SOLVED]
This problem is solved by following demlak post on twofie thread.
Here are the original post from demlak:
on #cyanogenmod channel on freenode user spudowiar helped me..
the problem:
partition /misc is fault.. and twrp (for example) does not mount this partition to wipe it correctly..
you can wipe it manualy by dd it..
adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Click to expand...
Click to collapse
but do a backup before! (just in case)
adb pull /dev/block/platform/msm_sdcc.1/by-name/misc misc.img
Click to expand...
Click to collapse
Click to expand...
Click to collapse
FYI: I do the adb command on the mount twrp

[SOLVED]

Related

[Q] Nexus 5, internal storage 0Mb

Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc
Sounds like uv messed up the partitions. unsure if theres a fix on this
Try
fastboot flash cache cache.img
Where cache.img is from the factory image
jd1639 said:
Try
fastboot flash cache cache.img
Where cache.img is from the factory image
Click to expand...
Click to collapse
This is happening without any problems but it does not change the problem.
I'm lost ...
in TWRP i have
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help
worfeur said:
Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help
Click to expand...
Click to collapse
What version of twrp are you using?
jd1639 said:
What version of twrp are you using?
Click to expand...
Click to collapse
I use twrp 2.6.3.2
worfeur said:
I use twrp 2.6.3.2
Click to expand...
Click to collapse
Try to flash this in fastboot, fastboot flash recovery recovery.img. Where recovery.img is the file below. If it installs, wipe cache within it
http://d-h.st/nbu. It's 2.6.3.4
This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?
N5
1. you unlock it
2. recovery with software.
Thanks
Wergin said:
1. you unlock it
2. recovery with software.
Thanks
Click to expand...
Click to collapse
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.
worfeur said:
Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc
Click to expand...
Click to collapse
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.
WoodburyMan said:
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.
Click to expand...
Click to collapse
Sorry, I do not know the firmware that was installed
It is a device used
habitformer said:
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.
Click to expand...
Click to collapse
when I flash a custom-recovery (stock or cwn) TWRP 2.6.3.2 always returns
I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).
WoodburyMan said:
This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?
Click to expand...
Click to collapse
thank you for your help
I have access to adb fastboot mode by boot recovery.img (recovery stock google)
and using the control slidload ADB
but impossible to get the command line
but when I type ADB Devices, my phone is found
otherwise I can not do a stock restoration because the bootloader does not update (KKX11D then I flashed back KKX11K) when I do well:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
Beauenheim said:
I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).
Click to expand...
Click to collapse
thank you I'll try it tonight but I think I already tried
worfeur said:
thank you I'll try it tonight but I think I already tried
Click to expand...
Click to collapse
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem
jd1639 said:
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem
Click to expand...
Click to collapse
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory
worfeur said:
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory
Click to expand...
Click to collapse
Can you format data in 2.6.3.2? I'm thinking you have a bigger problem as you've already tried to flash the factory image and it did not work.

[Q] [HELP] Stuck at twrp screen cant access to fastboot

Devices == TF700T
I wanna use f2fs , and when I finished installing a ROM I reboot my Tf700t with holding Volum Down,I selected "Wipe Data" (RCK coldboot and wipe data)and the tab gets into twrp screen , It takes very long time about 5 hours so I reboot it forcely ,reboot gets loop ,cant go to fastboot
Brick?
What can I do to solve the problem?
kuzhuhantian said:
Devices == TF700T
I wanna use f2fs , and when I finished installing a ROM I reboot my Tf700t with holding Volum Down,I selected "Wipe Data" (RCK coldboot and wipe data)and the tab gets into twrp screen , It takes very long time about 5 hours so I reboot it forcely ,reboot gets loop ,cant go to fastboot
Brick?
What can I do to solve the problem?
Click to expand...
Click to collapse
Hmm dangerous thing wiping data from the RCK menu with a custom recovery - not sure why you did that? What custom recovery and version were you on. There is a chance here that you have hard bricked it.
kuzhuhantian said:
What can I do to solve the problem?
Click to expand...
Click to collapse
Bootloader version?
TWRP version?
Which ROM (+version) did you install?
Which ROM (+version) was installed before?
Did you wipe any partitions in TWRP?
What else did you do, e.g. which partition(s) did you format as f2fs?
Can you reach your recovery using adb shell?
Here is the detail
_that said:
Bootloader version?
TWRP version?
Which ROM (+version) did you install?
Which ROM (+version) was installed before?
Did you wipe any partitions in TWRP?
What else did you do, e.g. which partition(s) did you format as f2fs?
Can you reach your recovery using adb shell?
Click to expand...
Click to collapse
TWRP V ==2.7.0.0 F2FS
ROM is CromBi--KK
Kernel == That-F2fs
what I did:
using Twrp formatting data then reboot to recovery to wipe cache (select only cache)
then flash That-F2fs kernel
reboot system
failed to start syst so I get fastboot mode
then I select wipe data(not RCK to recovery),is Bootloader wipe data
Now the tab stuck at twrp screen,and cant get in fastboot
PC can connect the tab but adb seems not working
How can I do?
sbdags said:
Hmm dangerous thing wiping data from the RCK menu with a custom recovery - not sure why you did that? What custom recovery and version were you on. There is a chance here that you have hard bricked it.
Click to expand...
Click to collapse
I followed this thread and flash your ROM kk--0617(which support f2fs so I want to use f2fs to get my tab faster)
[MOD] [All ROMS] F2FS for TF700T-- http://forum.xda-developers.com/showthread.php?t=2681775
TWRP V ==2.7.0.0 F2FS
ROM is CromBi--KK
Kernel == That-F2fs
what I did:
using Twrp formatting data then reboot to recovery to wipe cache (select only cache)
then flash That-F2fs kernel
reboot system
failed to start syst so I get fastboot mode
then I select wipe data(not RCK to recovery),is Bootloader wipe data
Now the tab stuck at twrp screen,and cant get in fastboot
PC can connect the tab but adb seems not working
kuzhuhantian said:
I followed this thread and flash your ROM kk--0617(which support f2fs so I want to use f2fs to get my tab faster)
[MOD] [All ROMS] F2FS for TF700T-- http://forum.xda-developers.com/showthread.php?t=2681775
TWRP V ==2.7.0.0 F2FS
ROM is CromBi--KK
Kernel == That-F2fs
what I did:
using Twrp formatting data then reboot to recovery to wipe cache (select only cache)
then flash That-F2fs kernel
reboot system
failed to start syst so I get fastboot mode
then I select wipe data(not RCK to recovery),is Bootloader wipe data
Now the tab stuck at twrp screen,and cant get in fastboot
PC can connect the tab but adb seems not working
Click to expand...
Click to collapse
OK You didn't need to flash the kernel and that maybe why it didn't start. The kernel was already built into the cromnbi-kk package - that was an older version.
Use my adb drivers for recovery below - unzip and install them from device manager whilst you have the device connected in TWRP.
You may need to manually wipe all partitions.
I don't have all the threads handy but look for Buster99 and his fix.
Or contact @lj50036 as he can fix you up
kuzhuhantian said:
Now the tab stuck at twrp screen,and cant get in fastboot
PC can connect the tab but adb seems not working
Click to expand...
Click to collapse
As long as we stay at this level of detail, I can't even try to help you.
What else can I provide?
_that said:
As long as we stay at this level of detail, I can't even try to help you.
Click to expand...
Click to collapse
What else can I provide?
Any thing you need I wanna give you , wish you can help
kuzhuhantian said:
What else can I provide?
Any thing you need I wanna give you , wish you can help
Click to expand...
Click to collapse
Error message? Exactly what you typed in and the response you got back.
I forgot the drivers:
http://www.androidfilehost.com/?fid=23329332407571010
Try those first.
sbdags said:
OK You didn't need to flash the kernel and that maybe why it didn't start. The kernel was already built into the cromnbi-kk package - that was an older version.
Use my adb drivers for recovery below - unzip and install them from device manager whilst you have the device connected in TWRP.
You may need to manually wipe all partitions.
I don't have all the threads handy but look for Buster99 and his fix.
Or contact @lj50036 as he can fix you up
Click to expand...
Click to collapse
I use a needle (about 2 cm down of your sdcard slot) and hold vol-down but I cant enter fastboot
sbdags said:
Error message? Exactly what you typed in and the response you got back.
I forgot the drivers:
http://www.androidfilehost.com/?fid=23329332407571010
Try those first.
Click to expand...
Click to collapse
Hard reset and and adb cant get tf700t to fastboot
ADB just no respond
That is the real problem
kuzhuhantian said:
Hard reset and and adb cant get tf700t to fastboot
ADB just no respond
That is the real problem
Click to expand...
Click to collapse
You should be able to use adb in the recovery mode. What is the feedback when you type "adb devices" at the prompt?
LetMeKnow said:
You should be able to use adb in the recovery mode. What is the feedback when you type "adb devices" at the prompt?
Click to expand...
Click to collapse
12fssdfcvx(something like this) recovery
kuzhuhantian said:
12fssdfcvx(something like this) recovery
Click to expand...
Click to collapse
It is meant that your adb is working in the recovery mode. _that is a linux guru around here. Maybe, he can help you out with adb, good luck...:fingers-crossed:

[Q] Which partition to format to remove CWM ?

Hey,
I have been given Motorola Xoom and when I'm booting into recover it has got broken or wrong CWM. Tablet goes in the loop and I see that CWM Droid with exclamation and parts and pieces coming out of his stomach
I know that partition with CWM can be formatted from ADB, but i haven't done it for long time and never on tablet.
Could someone tell me / confirm which partition installed CWM sits on ?
Also, what's the chance that something will go wrong and I won't be able to flash new CWM ?
birkopf said:
Hey,
I have been given Motorola Xoom and when I'm booting into recover it has got broken or wrong CWM. Tablet goes in the loop and I see that CWM Droid with exclamation and parts and pieces coming out of his stomach
I know that partition with CWM can be formatted from ADB, but i haven't done it for long time and never on tablet.
Could someone tell me / confirm which partition installed CWM sits on ?
Also, what's the chance that something will go wrong and I won't be able to flash new CWM ?
Click to expand...
Click to collapse
If you can boot into Android (and you have root access), you can use Flashify.
Otherwise you can use "fastboot flash recovery you_recovery.img".
AlEsC said:
If you can boot into Android (and you have root access), you can use Flashify.
Otherwise you can use "fastboot flash recovery you_recovery.img".
Click to expand...
Click to collapse
I don't have root. I also cannot flash recovery because CWM sit's there and is broken
birkopf said:
I don't have root. I also cannot flash recovery because CWM sit's there and is broken
Click to expand...
Click to collapse
fastboot will overwrite you broken CWM
1) reboot in bootloader (command : adb reboot bootloader)
2) fastboot flash recovery twrp.img
You can find TWRP image here :
http://forum.xda-developers.com/motorola-xoom/development/recovery-twrp-2-8-0-0-t2880998
AlEsC said:
fastboot will overwrite you broken CWM
1) reboot in bootloader (command : adb reboot bootloader)
2) fastboot flash recovery twrp.img
You can find TWRP image here :
http://forum.xda-developers.com/motorola-xoom/development/recovery-twrp-2-8-0-0-t2880998
Click to expand...
Click to collapse
I don't think I can flash recover over existing recovery. This will most likely lead to soft brick...
Before flashing twrp.img I need to format the partition where CWM sits currently.
- Do you know which partition is it and how to do it ?
birkopf said:
I don't think I can flash recover over existing recovery. This will most likely lead to soft brick...
Before flashing twrp.img I need to format the partition where CWM sits currently.
- Do you know which partition is it and how to do it ?
Click to expand...
Click to collapse
Without root you won't be able to issue a mkfs command (as far as I know).
You can use :
fastboot format recovery
and/or
fastboot erase recovery
AlEsC said:
If you can boot into Android (and you have root access), you can use Flashify.
Otherwise you can use "fastboot flash recovery you_recovery.img".
Click to expand...
Click to collapse
AlEsC said:
Without root you won't be able to issue a mkfs command (as far as I know).
You can use :
fastboot format recovery
and/or
fastboot erase recovery
Click to expand...
Click to collapse
Sounds good. So, just to confirm
- I need to first clear the recovery partition with commands you wrote above
- Flash new recovery from the link you submitted in the post above
- Flash selected ROM from the SD card using new recovery
Does it all sound fine ?
birkopf said:
Sounds good. So, just to confirm
- I need to first clear the recovery partition with commands you wrote above
- Flash new recovery from the link you submitted in the post above
- Flash selected ROM from the SD card using new recovery
Does it all sound fine ?
Click to expand...
Click to collapse
Correct.
Choose carrefully you recovery image (BigPart or non-BigPart) depending on the ROM you wish to install.
AlEsC said:
Correct.
Choose carrefully you recovery image (BigPart or non-BigPart) depending on the ROM you wish to install.
Click to expand...
Click to collapse
Thanks!
Just quick question : what is the BigPart or non-BigPart ?
Googling that doesn't produce any sensible results

partition corrupted. Need help?

This is my friend's phone and when she showed me, it was asking for android's password with the title "Decryption unsuccessful".
I then tried mi-flash and it didn't gave any errors but when it rebooted it went to fastboot screen. It was on latest MIUI7 stable when this happened. I tried formatting again from recovery, I got the below error logs.
/data, /system and /cache - (invalid argument)
Even recovery is gone and it only boots to fastboot screen. I can only go to recovery by doing
fastboot boot recovery.img (recovery is twrp 3.0.2-0) from fastboot.
I think the only possible way is to full format the partitions and bring it to stock but I am not finding any threads to point me to proper directions. Any one here care to help revive this mi4i.
warlord060816 said:
This is my friend's phone and when she showed me, it was asking for android's password with the title "Decryption unsuccessful".
I then tried mi-flash and it didn't gave any errors but when it rebooted it went to fastboot screen. It was on latest MIUI7 stable when this happened. I tried formatting again from recovery, I got the below error logs.
/data, /system and /cache - (invalid argument)
Even recovery is gone and it only boots to fastboot screen. I can only go to recovery by doing
fastboot boot recovery.img (recovery is twrp 3.0.2-0) from fastboot.
I think the only possible way is to full format the partitions and bring it to stock but I am not finding any threads to point me to proper directions. Any one here care to help revive this mi4i.
Click to expand...
Click to collapse
Anyway
Can i ask you,your friend using ext4 or f2fs??
I faced this issue if i format my data partition as f2fs at miui
Yeah, full format is good
faizauthar12 said:
Anyway
Can i ask you,your friend using ext4 or f2fs??
I faced this issue if i format my data partition as f2fs at miui
Yeah, full format is good
Click to expand...
Click to collapse
Thanks for replying.
I have the phone with me so I can answer queries right away. Its in ext4 format. Didn't tried f2fs. but the recovery I have, is not providing me f2fs file system type? How did you get that?
no idea, on doing full format. any thread links, please?
warlord060816 said:
Thanks for replying.
I have the phone with me so I can answer queries right away. Its in ext4 format. Didn't tried f2fs. but the recovery I have, is not providing me f2fs file system type? How did you get that?
no idea, on doing full format. any thread links, please?
Click to expand...
Click to collapse
here is a step
http://forum.xda-developers.com/showpost.php?p=35368127&postcount=7
about recovery here
faizauthar12 said:
here is a step
http://forum.xda-developers.com/showpost.php?p=35368127&postcount=7
about recovery here
Click to expand...
Click to collapse
I followed the format instruction and successfully formatted userdata, system and cache but when I went to recovery to wipe the partitions it again said the same thing (Failed to mount '/system' (invalid argument) and the same error for cache and data.
warlord060816 said:
I followed the format instruction and successfully formatted userdata, system and cache but when I went to recovery to wipe the partitions it again said the same thing (Failed to mount '/system' (invalid argument) and the same error for cache and data.
Click to expand...
Click to collapse
which recovery you're using?
why you wipe your system data and cache?
what do you want to do? (flash a rom,explain it )
faizauthar12 said:
which recovery you're using?
why you wipe your system data and cache?
what do you want to do? (flash a rom,explain it )
Click to expand...
Click to collapse
Recovery - twrp 3.0.2-0
Those mounts were not visible when I check the mounts using df command and for the above errors I tried to format as it showed successful operation.
I have the latest fastboot rom for flashing but unless the mounts work, I am hopeless.
Here are the recovery logs
Below output shows that userdata partition is encrypted. I think this is preventing the partitions to be mounted
warlord060816 said:
Recovery - twrp 3.0.2-0
Those mounts were not visible when I check the mounts using df command and for the above errors I tried to format as it showed successful operation.
I have the latest fastboot rom for flashing but unless the mounts work, I am hopeless.
Here are the recovery logs
Click to expand...
Click to collapse
how about using TWRP unofficial ?
a weird error i ever seen till now
faizauthar12 said:
how about using TWRP unofficial ?
a weird error i ever seen till now
Click to expand...
Click to collapse
I'm eager to try the twrp you have linked but just wanted to ask few qs.
1. The version I am using is also listed in the link you've provided. Is there a way to check or after flashing I would find differences in the functionality?
2. Which version you want me to try?
3. Since I updated my above post with the image showing the encryption flag on data partition, can that be fixed in your unofficial TWRP you've linked?
warlord060816 said:
I'm eager to try the twrp you have linked but just wanted to ask few qs.
1. The version I am using is also listed in the link you've provided. Is there a way to check or after flashing I would find differences in the functionality?
2. Which version you want me to try?
3. Since I updated my above post with the image showing the encryption flag on data partition, can that be fixed in your unofficial TWRP you've linked?
Click to expand...
Click to collapse
well, just give it a try
since i'm using my own unofficial(because it has f2fs )
i'm not face any of those error
which Miui you're using??
i think any of rom and recovery just support miui6
faizauthar12 said:
well, just give it a try
since i'm using my own unofficial(because it has f2fs )
i'm not face any of those error
which Miui you're using??
i think any of rom and recovery just support miui6
Click to expand...
Click to collapse
tried the latest in the twrp folder. I was using just the previous of the latest version and got the same result when tried "Format Data" as it said it will also remove the encryption.
I also tried to flash the latest mokee build below are the screen snaps of the logs
Reboot to recovery is also not working and it loads to fastboot screen.
Edit: Previously when i tried flash_all in miflash it gave me error:
0x80004005: FAILED (remote: failed to write partition) at the line where it invokes flash partition command.
warlord060816 said:
tried the latest in the twrp folder. I was using just the previous of the latest version and got the same result when tried "Format Data" as it said it will also remove the encryption.
I also tried to flash the latest mokee build below are the screen snaps of the logs
Reboot to recovery is also not working and it loads to fastboot screen.
Click to expand...
Click to collapse
okay, now i see you're using otg (case 1)(i never used OTG for flash any files)
how about format data from fastboot ?
which miui you're using?
faizauthar12 said:
okay, now i see you're using otg (case 1)(i never used OTG for flash any files)
how about format data from fastboot ?
which miui you're using?
Click to expand...
Click to collapse
Fastboot MIUI version - ferrari_global_images_V7.5.1.0
I tried the format data command from fastboot. If you are referring to "fastboot format userdata" , then it was successful. I tried again and below is the log.
warlord060816 said:
Fastboot MIUI version - ferrari_global_images_V7.5.1.0
I tried the format data command from fastboot. If you are referring to "fastboot format userdata" , then it was successful. I tried again and below is the log.
Click to expand...
Click to collapse
somebody(i forget who is he)
said to me that when using miui 7,you will got a lots of trouble when using TWRP
use any of miui 6 firmware
faizauthar12 said:
somebody(i forget who is he)
said to me that when using miui 7,you will got a lots of trouble when using TWRP
use any of miui 6 firmware
Click to expand...
Click to collapse
I was thinking of trying this unbrick-qualcomm-mobiles/. but again this phone is not entering into "Qualcomm HS-USB QDLoader 9008" mode.
Tell me which miui version other than 7 I should try? and if possible link me to that.
Edit: Now downloading this: ferrari_global_images_V6.5.6.0.LXIMICD_5.0_global hoping to fix the partitions if this has those files required like
"rawprogram0.xml"
"patch0.xml"
warlord060816 said:
I was thinking of trying this unbrick-qualcomm-mobiles/. but again this phone is not entering into "Qualcomm HS-USB QDLoader 9008" mode.
Tell me which miui version other than 7 I should try? and if possible link me to that.
Edit: Now downloading this: ferrari_global_images_V6.5.6.0.LXIMICD_5.0_global hoping to fix the partitions if this has those files required like
"rawprogram0.xml"
"patch0.xml"
Click to expand...
Click to collapse
do you mean edl?
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
go to fastboot then use that files
since we only can type reboot edl with adb not fastboot, that thread have a modified fastboot to support reboot edl
tried edl. phone is not going into edl. Well i don't know how it will look like if it goes into edl, right now it boots to fastboot. I don't know if I'm missing anything.
warlord060816 said:
tried edl. phone is not going into edl. Well i don't know how it will look like if it goes into edl, right now it boots to fastboot. I don't know if I'm missing anything.
Click to expand...
Click to collapse
Hey Warlord,
I believe I'm facing the same issue as you did. Have you made any progress?..

No OS, internal storage 0 Mb

Sorry for my English... I have a problem with my moto g XT1032 with bootloader unlocked and version recovery latest TWRP, I rooted and was running CM13, until I began to present faults so I decided to restart the phone, from that the phone turned on in recovery mode and when I check if everything is fine, says I have no OS installed, I review the status of the internal storage (all this is from the recovery TWRP) it says it is 0mb,i tried to flash from the bootloader the original firmware and all commands says FAILED when it's gonna write it (failed to erase partition). Anyone who has had this problem before and have fixed or knows how to fix it?
Try this tool: http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522 .
Via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
lost101 said:
Via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
Click to expand...
Click to collapse
I try to do it but it says
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on device
:crying::crying::crying:
Maybe try:
adb shell
cd /dev/block/platform/msm_sdcc.1/by-name
dd if=/dev/zero of=./misc​
lost101 said:
Maybe try:
adb shell
cd /dev/block/platform/msm_sdcc.1/by-name
dd if=/dev/zero of=./misc​
Click to expand...
Click to collapse
Sorry for hijacking the thread but i am afraid that I am with similar problem, when using my G its just rebooted and after that the battery drop to 20% (previous 76%) and a lot of files disappear, like amnesia any idea why?
BryanByteZ said:
Sorry for hijacking the thread but i am afraid that I am with similar problem, when using my G its just rebooted and after that the battery drop to 20% (previous 76%) and a lot of files disappear, like amnesia any idea why?
Click to expand...
Click to collapse
Sounds like classic 'emmc corruption' symptomatology. Fastboot flash the latest factory firmware image for your model. However it may well be game over for your handset.
lost101 said:
Sounds like classic 'emmc corruption' symptomatology. Fastboot flash the latest factory firmware image for your model. However it may well be game over for your handset.
Click to expand...
Click to collapse
Oh sh**, okay thanks for the info!
when I flashed falcon_502_partitions_nomodem.zip on my moto g XT1028 and then I reboot to bootloader nothing is there and when I tried to restart my devices the screen is black and the fastboot mode is also not visible and I'm not able to flash anything to make my device work.
Aditya2512 said:
when I flashed falcon_502_partitions_nomodem.zip on my moto g XT1028 and then I reboot to bootloader nothing is there and when I tried to restart my devices the screen is black and the fastboot mode is also not visible and I'm not able to flash anything to make my device work.
Click to expand...
Click to collapse
Post here and only here: http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
If your model is not supported, then you may never be able to resolve the situation.
Solved
I faced the sane problem with my moto g3. actually after booting it into recovery it went to loop of recovery and off.
Then downgraded twrp to 3.0.2 using fastboot from pc.
Then it booted into recovery but was showing 0mb internal storage.Lastly i used format data under wipe in twrp then it got back to normal.

Categories

Resources