Database Info

sd storage 0 mb on TWRP

Hi,
I have unlocked the bootloader and rooted my moto g and installed a custom ROM. As the custom ROM had few bugs, i did a restore of my Stock ROM in TWRP.
Now when i see the TWRP to install another custom ROM, it shows the internal Storage is 0 mb . However when the phone is connected to the computer , i can view all the files there, just in recovery it shows 0 mb.
Any Idea guys?
i am using TWRP v2.6.3.3

Try the latest build '2.8.0.1':
http://techerrata.com/browse/twrp2/xt1032

flashed still no luck... and i am not able to wipe the data as well, it says unable to mount

Odd case. It could be partition corruption. Maybe try Phil's Touch.
Alternatively, you could backup contents of 'internet storage' and fastboot fastboot the latest firmware image for your phone. That would fix any partition issues. Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
What model do you have?

i have XT1033 dual SIM version.. when i searched the firmware for umtsds i have only 4.3 available for Asia.. (Android 4.3
Blur_Version.14.85.4.falcon_umtsds.AsiaRetail.en.03) however i am right now running 4.4.4... i have one for 4.4.2 which is of Brazil.. any suggestion which one to flash.
I bought this phone in India so i am looking for Asian firmware...

http://forum.xda-developers.com/showpost.php?p=54487261&postcount=332

flashed.. i ll try flashing TWRP again..

thank you guys..it worked..

ghost9685 said:
thank you guys..it worked..
Click to expand...
Click to collapse
I have the same problem. please tell me which solution worked @ghost9685

ghost9685 said:
flashed still no luck... and i am not able to wipe the data as well, it says unable to mount
Click to expand...
Click to collapse
hey @lost101 I am having the same problem. I tried doing the guide which you have linked but the first two commands come back as failed and then after all other commands have been executed the phone reboots to the android dummy screen which keeps blinking. Please help me out

Saadjamil36 said:
hey @lost101 I am having the same problem. I tried doing the guide which you have linked but the first two commands come back as failed and then after all other commands have been executed the phone reboots to the android dummy screen which keeps blinking. Please help me out
Click to expand...
Click to collapse
Fastboot flash the latest factory firmware image for your phone. Do all fastboot commands mentioned in tutorial
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
Fastboot flash the latest factory firmware image for your phone. Do all fastboot commands mentioned in tutorial
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Didn't work. All commands were OKAY but phone rebooted to android dummy lying on its back and screen keeps turnin pn and off on itself

Saadjamil36 said:
Didn't work. All commands were OKAY but phone rebooted to android dummy lying on its back and screen keeps turnin pn and off on itself
Click to expand...
Click to collapse
Then everything did not obviously go 'OKAY.' It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.

lost101 said:
Then everything did not obviously go 'OKAY.' It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Maybe there is something I am doing incorrectly. These are the screenshots of the command prompt
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Saadjamil36 said:
Maybe there is something I am doing incorrectly. These are the screenshots of the command prompt
Click to expand...
Click to collapse
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then 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:
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then 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
How do i type this command in Twrp? adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
thanks a lot for the help

Saadjamil36 said:
How do i type this command in Twrp? adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
thanks a lot for the help
Click to expand...
Click to collapse
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378

Thank You. It worked

Saadjamil36 said:
I have the same problem. please tell me which solution worked @ghost9685
Click to expand...
Click to collapse
you will have to restore the stock firmware where it re writes the recovery partition and then flash any custom recovery.. thats wat worked

Is anyone having an issue where the sd card is unmountable, shows 0mb and no gapps zip while in recovery... and then also has an eternal black screen when trying to run without recovery?

Unable to flash TWRP

Yo
currently running newest official (12.1-YOG4PAS1N0).
I unlocked the bootloader-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then I put the recovery.img file at the adb path.
then I enter fastboot and typed <fastboot flash recovery recovery.img> and it flashed it.
I disconnected the USB, turned the device off and then immediately booted into recovery (Volume down + Power)... BUT- it takes me to CM stock recovery every time
was wondering if anyone knows what can be done.
CM Recovery update is disabledfrom Dev Options ofcourse.
thanks.

Lidor167 said:
Yo
currently running newest official (12.1-YOG4PAS1N0).
I unlocked the bootloader-
then I put the recovery.img file at the adb path.
then I enter fastboot and typed <fastboot flash recovery recovery.img> and it flashed it.
I disconnected the USB, turned the device off and then immediately booted into recovery (Volume down + Power)... BUT- it takes me to CM stock recovery every time
was wondering if anyone knows what can be done.
CM Recovery update is disabledfrom Dev Options ofcourse.
thanks.
Click to expand...
Click to collapse
Now since this is a straight forward thing you are going to get the basic questions which I suggest you put the exact route you took. was your recovery named recovery.img? Are you sure that its flashing?
Have you tried a toolkit although I agree to try it manually but just as another troubleshooting method.

playya said:
Now since this is a straight forward thing you are going to get the basic questions which I suggest you put the exact route you took. was your recovery named recovery.img? Are you sure that its flashing?
Have you tried a toolkit although I agree to try it manually but just as another troubleshooting method.
Click to expand...
Click to collapse
the recovery is named recovery.img
I tried a toolkit but its too bulky for me

Lidor167 said:
the recovery is named recovery.img
I tried a toolkit but its too bulky for me
Click to expand...
Click to collapse
what do you mean too bulky? did you try the toolkit prior to this or after
Edit: does it show the recovery flash working and being successful?

playya said:
what do you mean too bulky? did you try the toolkit prior to this or after
Edit: does it show the recovery flash working and being successful?
Click to expand...
Click to collapse
prior to this.. says something about not being able to find adb device. but when i open the command prompt and type <fastboot devices> it shows my One. so I gave up on the toolkit

Lidor167 said:
prior to this.. says something about not being able to find adb device. but when i open the command prompt and type <fastboot devices> it shows my One. so I gave up on the toolkit
Click to expand...
Click to collapse
Wugs makes a descent toolkit.. Did you get it fixed

playya said:
Wugs makes a descent toolkit.. Did you get it fixed
Click to expand...
Click to collapse
yeah, appreantly the file name was - recovery.img.img but it didn't show, I had it checked and now it's all good, thanks

Flashing TWRP Berlin (3.1) guides to "Huawei eRecovery" anyway...

Hi guys.
Trying to install TWRP 3.1 for Nougat.
Everything goes fine (flashing, etc..) till the moment I "fastboot reboot".
Instead of prompting TWRP, I enter the "Huawei eRecovery"...
Is the stock rom replacing recovery at boot?
Does anyone know how to fix it?
I need it of course to install SuperSU and get rooted.
Thanks.

Just shut down device, and then press power+volume up button until a message is shown. Then you're in TWRP. You don't need fastboot for that.

Engineer91 said:
Just shut down device, and then press power+volume up button until a message is shown. Then you're in TWRP. You don't need fastboot for that.
Click to expand...
Click to collapse
Thank you for replying, but you do get my point.
after flashing TWRP 3.1, I enter recovery as you wrote.
The problem is that I see this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not TWRP.
I don't understand why the recovery changes to stock one.

I wrote "fastboot mode" because it is part of the procedure to install recovery through ADB.
And everything seems to be fine UNTIL I write the last command to enter recovery (of course I need an ADB command to exit and reboot in recovery).

Probably TWRP isn't being installed properly. What command did you use?

(already installed on my pc drivers and ADB tools)
from the beginning:
adb reboot bootloader
fastboot flash recovery twrp.img
(Once TWRP is successfully flashed) fastboot reboot
Then volume+ and power button

Well, that worked for me always. I don't know what is happening. Maybe a dev could help you.

I hope someone of them is reading this thread...

Engineer91 said:
Well, that worked for me always. I don't know what is happening. Maybe a dev could help you.
Click to expand...
Click to collapse
Are you on Nougat and EMUI 5?
Which TWRP image recovery did u install? Berlin 3.1?

Yes, EMUI 5, TWRP berlin 3.1. It worked with versions B342 and B360. I succesfully used Revolution recovery from P9 lite too, before TWRP 3.1 was released for our device.

Engineer91 said:
Yes, EMUI 5, TWRP berlin 3.1. It worked with versions B342 and B360. I succesfully used Revolution recovery from P9 lite too, before TWRP 3.1 was released for our device.
Click to expand...
Click to collapse
Boh... I don't know then...
I succeded in rooting when I was on android 6 and emui 4.1. After updating to nougat (b360), no way.

You need TWRP 3.1.0-2 and unplug the usb cable...
TWRP_3.1.0-2\EMUI5

YOU ARE THE MAN, bro!
Succeded with new TWRP.
Thanks thanks thanks

power off completely. Hold down : Power + Volume Up. You will see the magic.

Been stuck for two days!! Thanks for the advice on changing to TWRP 3.1.0-2 and unplug the usb cable...That worked.

OTA with Magisk Fails Using Magisk's Suggested Method

I followed Magisk's OTA Installation Tips but it was unsuccessful twice. I was running Magsik v16, restored images in Magisk, started the OTA, once it started processing Step 2 of 2 I installed Magisk to the second slot (after OTA). After the OTA finished installing, I rebooted the phone and it rebooted a second time before getting to the unlock screen. Checking Magisk, I found that I was unrooted and couldn't root via Magisk Manager and the OTA install had also failed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was able to boot to the twrp bootable image and reinstall Magisk v14.3, and repeated the entire process above just to see if it was a fluke, and found myself in the same exact spot - OTA installation failed and I was unrooted again.

Don't try to OTA with any mods it will almost certainly always fail. Just flash factory image without the -w and then mod accordingly after it boots

KittyRgnarok said:
Don't try to OTA with any mods it will almost certainly always fail. Just flash factory image without the -w and then mod accordingly after it boots
Click to expand...
Click to collapse
I don't have any mods. After the first OTA was unsuccessful and I rebooted without root, I retried the standard OTA and it was successful. Then I booted to twrp via adb and successfully installed magisk v14.3 from a thumb drive to regain root. Not sure if there's a better way to regain root, because for this to be successful I have to wipe the sdcard every time.

bobo-the-drunk said:
I don't have any mods. After the first OTA was unsuccessful and I rebooted without root, I retried the standard OTA and it was successful. Then I booted to twrp via adb and successfully installed magisk v14.3 from a thumb drive to regain root. Not sure if there's a better way to regain root, because for this to be successful I have to wipe the sdcard every time.
Click to expand...
Click to collapse
Any particular reason your using 14.3 instead of 16.0?

Can't flash 16.0 from the bootable twrp image. I flash 16.0 once I boot into Android.

bobo-the-drunk said:
Can't flash 16.0 from the bootable twrp image. I flash 16.0 once I boot into Android.
Click to expand...
Click to collapse
I flashed version 16.0 on bootable twrp image today with no issues.

bobo-the-drunk said:
Can't flash 16.0 from the bootable twrp image. I flash 16.0 once I boot into Android.
Click to expand...
Click to collapse
Are you using TWRP 3.2.1-2? I install Magisk 16 after flashing the TWRP zip with a couple reboots in between to make sure everything takes.

mruno said:
Are you using TWRP 3.2.1-2? I install Magisk 16 after flashing the TWRP zip with a couple reboots in between to make sure everything takes.
Click to expand...
Click to collapse
Interesting, can your version unlock storage? I've been using the TWRP bootable from this thread. Based on the filename, I'm betting it's not TWRP 3.2.1-2

bobo-the-drunk said:
Interesting, can your version unlock storage? I've been using the TWRP bootable from this thread. Based on the filename, I'm betting it's not TWRP 3.2.1-2
Click to expand...
Click to collapse
yes it can

mruno said:
yes it can
Click to expand...
Click to collapse
OK, now you've got my attention, but where's the bootable file? All the links I can find are borked.

https://dl.twrp.me/sailfish
get the img to temp flash twrp, then flash the zip in twrp for permanent twrp recovery

mruno said:
https://dl.twrp.me/sailfish
get the img to temp flash twrp, then flash the zip in twrp for permanent twrp recovery
Click to expand...
Click to collapse
Booted to the TWRP bootable, decrypted storage successfully (yay!), (intentionally) didn't unlock system, flashed the TWRP zip, now it only boots to TWRP. I'm guessing I'll need to reflash the April 2018 image?

yea that happens sometimes. extract the boot.img from the april image and reboot to bootloader and then with adb: fastboot flash bootloader bootloader.img
afterwards, flashtwrp img and install twrp zip

[twrp] [v3. 3.1] [micromax infinity n12] [treble recovery] Micromax Infinity n12 TWRP

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Long wait over! Finally working TWRP for Micromax Infinity N12
- Full Treble Support
-Capability to flash all GSI
-ADB fully working
- Latest version 3.1.1
- MTP
- Encryption ( can be fixed but causes problems like battery drain)
-This image didn't boot for some people. This is due to the some vendor patches from an OTA update. To install TWRP just install the stock firmware and follow the steps below. (just don't allow the phone to install the OTA update or else the vendor patches will come back)
- Install stock rom before flashing TWRP.
- Enable OEM Unlocking
- Type the following commands
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot
recovery.img
drive.google.com
https://androidfilehost.com/?fid=8889791610682881821 stock firmware
@lopestom for the base TWRP that I ported

Works well, just encryption needs to be done
Good job. There has been no development for this device. Thanks to you l could install Android 10 gsi!

Thanks for your reply
If you like the recovery that I ported please click the thanks button, this is my first post

SOLVED
JOSHUA....... said:
Good job. There has been no development for this device. Thanks to you l could install Android 10 gsi!
Click to expand...
Click to collapse
Encryption ploblem is solved please check out

After flashing twrp, phone not booting into twrp. What will be the reason?
Fixed

Voolyo said:
After flashing twrp, phone not booting into twrp. What will be the reason?
Fixed
Click to expand...
Click to collapse
Sorry for the late reply.
Which way did you use to flash twrp? Sp flash tool or fastboot mode? If you used fastboot use it in the exact same way
Fastboot oem unlock
Fastboot flash recovery recovery.img
Fastboot reboot
After that don't let the phone reboot. Immidialy after executing the command fastboot reboot, press the power and volume up, and select recovery.
If still not successful, first flash the stock recovery and then the twrp
Edit : oh sorry I didn't see that you fixed it

Tab E said:
Sorry for the late reply.
Which way did you use to flash twrp? Sp flash tool or fastboot mode? If you used fastboot use it in the exact same way
Fastboot oem unlock
Fastboot flash recovery recovery.img
Fastboot reboot
After that don't let the phone reboot. Immidialy after executing the command fastboot reboot, press the power and volume up, and select recovery.
If still not successful, first flash the stock recovery and then the twrp
Edit : oh sorry I didn't see that you fixed it
Click to expand...
Click to collapse
Thanks for the reply .