yashsingh1/xdaforums huggingface dataset:
[G 2014 Original Android Development] mauritzius:
I have partitioned my SD-Card as semi-adoptable storage, i.e. about half of it is used as adoptable storage and the other half is available as SD Card. That works perfectly fine in Android, but TWRP fails to detect my adopted storage. Does anybody have the same problem?

Unfortunately, I do not have a build system at hand, but there might be a patch (actually, a PR) that could fix the issue: https://github.com/omnirom/android_bootable_recovery/pull/99

I also saw a patch that might fix the race condition mentioned earlier (if it's on encrypted storage, might already be included in the latest TWRP release, I didn't check): https://gerrit.omnirom.org/#/c/18254/

Could someone with a working build system try to make a build with the two patches applied?
[G 2014 Original Android Development] iamhar****hdaya:
i tried flashboot boot recovery.img and it boots and moto logo comes thats all.

and if i flash recovery and immediately choose recovery from fastboot menu the phone normally boots.

what should i do?

---------- Post added at 03:54 PM ---------- Previous post was at 03:50 PM ----------

what should i do now? i wanted to flash a custom rom?

---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------

what should i do?
[G 2014 Original Android Development] Wolfcity:
Maybe try to boot into twrp 2.8.5.0 and flash your recovery from there. Or you can try flashify from chainfire but I have no experience with it.

Doesn't matter this was sent from
[G 2014 Original Android Development] LuK1337:
What is the exact model of your phone?
[G 2014 Original Android Development] fasensior:
How can I go back to Motorola's Stock Recovery if I want to update the phone via OTA?
[G 2014 Original Android Development] Wolfcity:
Flash stock firmware of your model.

Doesn't matter this was sent from
[G 2014 Original Android Development] ForgottenDude:
Titan got an update now?!
[G 2014 Original Android Development] fasensior:
Yes. Motorola has released an update with security updates till August 1st and some performance and stability corrections. As I've read, there's better performance in the general use of the phone and the battery lasts a little bit longer.
[G 2014 Original Android Development] mauritzius:
I'm trying to compile TWRP myself, but I ran into some trouble: It boots, but simply reboots to System after a few seconds of showing the main menu. No interaction is possible at this stage, it also didn't ask for decryption.

What I did:

Set up an OmniROM 6.0 compile environment on Ubuntu 16.10, since the TWRP guide mentioned it as preferred environment

Added https://github.com/motog2014devteam/android_device_motorola_titan-twrp to local_manifest.xml with cm-13.0 branch

Added https://github.com/omnirom/android_bootable_recovery to local_manifest.xml with android-7.1 branch

Tried to compile it with breakfast titan; lunch titan; make -j4 recoveryimage, which went fine

Any ideas?
[G 2014 Original Android Development] mauritzius:
I'm still trying to figure this out: It seems that the repos were wrong and that I mixed up TWRP-7.1 and the device tree for 6.0. So I changed repos to:

https://github.com/TeamWin/android_device_motorola_titan with branch android-6.0

https://github.com/omnirom/android_bootable_recovery with branch android-6.0

I am one step further in that it now asks for the decryption and decryption works fine. Afterwards, no interaction is possible at the main screen and TWRP reboots after a few seconds to System.

EDIT: I also compared the resulting recovery.img with the latest build from twrp.me: My version includes SuperSU, which is not included in the downloaded build. Correct me if I'm wrong, but I suspect that the device information on github is not completely up to date!?

EDIT2: Nevermind, after doing a "make clean" and rebuilding, it works now! Continuing with adding patches...
[G 2014 Original Android Development] Wolfcity:
After trying to update TWRP recovery from twrp-3.0.0-0-titan to twrp-3.0.2-4-titan by flashing img instead of zip inside of TWRP3.0.0-0 I got the error message "failed to validate recovery image" Fastboot Reasons: Fall Through from recovery boot mode Boot up failed.

After that I ended up in fastboot mode and could boot to system.

But TWRP wasn´t flashed and it seems to be no recovery present at all. I tried it with flashfire and Official TWRP app, same result, also with TWRP 3.0.2-4.

Because I am not at home I couldn´t check the the method with minimal adb & fastboot and the command

fastoot flash recovery twrp-3.0.2-4-titan.img

What´s going wrong there?
[G 2014 Original Android Development] jackcicci:
I have this recovery but used adb to install and I had no problem
[G 2014 Original Android Development] Wolfcity:
Yes, I know that the recovery is working. I tried it via fastboot command on PC now, same error message. Can somebody tell me what the meaning of this message is?

I´m not able to flash any TWRP recovery. Maybe it´s something about superSU? I flashed rom-gapps, then reboot, after that superSU 2.7.9. Everything working fine.

After that I wanted to update the recovery from 3.0.0-0 to 3.0.2-4 and got that message "failed to validate recovery image" Fastboot Reasons: Fall Through from recovery boot mode Boot up failed.

When trying to flash TWRP via PC I got that error message too.

Maybe I have to clean flash the rom again and change the order to rom-gapps-recovery-superSU?
[G 2014 Original Android Development] gourabpa:
update ur bootloader..........problem....will be fixed......
[G 2014 Original Android Development] Wolfcity:
Hmm, IÂ´ve got a second device with bootloader 4882 and flashed nougat roms and TWRP 2.0.2-4 recovery on it. But I will give it a try if I find an updated bootloader.
[G 2014 Original Android Development] Rajmohanty7:
Problem during flashing the "Supersu". The handset bricks down with the moto Logo, not moving forward after so may tried and I installed Custom ROM again and again to get my phone switch on.

How the problem can be fix ?

How can I successfully flash the "supersu" ???
[G 2014 Original Android Development] doppelhelix:
SuperSU and cm14.1 is not compatible. Use cm inbuilt root.
[G 2014 Original Android Development] gourabpa:
If u want to flash supersu then flash the latest version v2.79 SR1 in Nougat OS.......flash this zip file after rom flashing....& if u r using custom kernels..... Then after that flash this SuperSU...........LINK

I am using it in RR N ROM........latest build working fine for me....no bootloop.....or other problem......

I have uploaded one screenshot...... Using multi window..... In vatsal......RR N ROM......checkit......SuperSU working fine in OS v7.1.1
[G 2014 Original Android Development] hoshang.govil12:
I am Using TWRP 3.0.2-4 in Titan, but Sometimes, While Booting into Recovery, It reset tofactory default, means I have to Choose Read Write, Set UpTime Zone again, Brightness etc. Why is it happening so??
[G 2014 Original Android Development] vygavedha:
i have flashed the latest twrp-3.0.2-4-titan.img in my moto g 2.When i tried enter to recovery from fastboot, it is stuck in bootloader message.What can be the reason, i have unlocked my device, flashed twrp using adb

---------- Post added at 04:15 PM ---------- Previous post was at 04:07 PM ----------

edit: even though i flashed twrp, when i tried to enter recovery from adb, it is loading into a screen, showing no command found..Any suggestion?
[G 2014 Original Android Development] ForgottenDude:
Android version?

I think, on that no command page you have to press and hold Power button and Volume UP button. Then fastboot mode will appear. You have to press Volume DOWN to scroll to Recovery option and use Volume UP to select it. Now you boot into TWRP.
[G 2014 Original Android Development] vygavedha:
I figure it out the issue, stock recovery is the culprit, while rebooting, it replaces the twrp flashed..As per the twrp instructions, i tried to use the key combo to boot the device to recovery after typing fastboot reboot.I was not quick enough to do the same, and failed..After some googling i found a two work around, i tried first one and it works

1) After flashing twrp, instead of typing fastboot reboot for rebooting,

type the following

fastboot boot twrp.img

device will boot to twrp recovery, from there reboot to recovery so that the twrp recovery by stock recovery can be avoided

2) Go to fastboot mode, enter the following in adb

fastboot boot twrp.img

Install superSu from twrp

reboot to system, install flashify after getting root access.flash twrp from flashify
[G 2014 Original Android Development] V.Mr.Gamer:
Actually, when you flash TWRP for the first time you'll need to boot into recovery, or else the TWRP won't get flashed, it's like reset to stock recovery.

In short flash TWRP recovery and do "fastboot reboot bootloader",

Select the recovery option..

And congrats you have successfully flashed a custom recovery
[G 2014 Original Android Development] vygavedha:
Thanks bro.
[G 2014 Original Android Development] Canty90:
the adb tool don't recognize mi phone

please somebody help me, when my moto g is turned on the adb tool work's fine but when reboot in bootloader to flash the twrp the adb doesnt recognize the phone, on the phone screen appears "conect usb data cable", i've tried everything than i know like looking for drivers and diferent adb tools but anyone work's...

sorry for my english :silly:
[G 2014 Original Android Development] vygavedha:
Boot to fastboot mode using power +vol(-) key combination..Then try to connect usb cable..Make sure the proper drivers are installed..

Check connectivity using fastboot devices command..

I hope you have enabled usb debugging and your device is authorised..
[G 2014 Original Android Development] revoluazul:
It's occurring for me every time I boot into recovery. Backups are also being deleted. Anybody else with this issue? Any idea? I'm using nougat roms with last twrp version by the way.
[G 2014 Original Android Development] Rajmohanty7:
I m using a MOTO G 2nd 2014 version phone whose bootloader has been unlocked by TWRP rooting. And its running on the Android 6.0 stock ROM.

Its running perfectly.

Then I got the OTA on 20th Jan 2017 and unable to update the maintainance & security update released on January 2017.

Its getting downloaded over the air of file size 45.3 mb successfully, but its showing error that software couldn't updated.

Why this problem ?

Canany 1 give me d perfect solution for this ? But it should b without unrooting.
[G 2014 Original Android Development] V.Mr.Gamer:
Firstly, your bootloader is unlocked using OEM unlocking via fastboot

Secondly, you are on stock meaning you'll need to unroot to OTA update... And it's not that tedious

Alas I don't think it's that important update (correct me if I'm wrong)
[G 2014 Original Android Development] vygavedha:
Not sure about the unroot for OTA update.You had to flash original stock recovery for taking OTA is sure....
[G 2014 Original Android Development] V.Mr.Gamer:
Yeah but if you are on stock then flashing on root binaries would cause errors
[G 2014 Original Android Development] GCalzo:
One must un-root too

https://xdaforums.com/showpost.php?p=55417257&postcount=2 Q18
[G 2014 Original Android Development] ashlp2904:
hi bro..... i m on twrp 2.8.6.0 and need to update the latest one.... could you please assist.

the last time i updated was more than a year so i forgot.....
[G 2014 Original Android Development] Wolfcity:
I don't know if the 2.8.6.0 version already had the option to flash img files. If yes there should be a toggle inside the install tab to change from zip to img install.

Then you can flash the TWRP recovery right from there. Put it into your internal/external storage and flash it through your old recovery.

If the option isn't present put Minimal ADB&Fastboot or mfastboot.exe on your PC, make sure to have the latest Motorola drivers installed (check Motorola website),copy the recovery file into the folder where adb/fastboot resist,plug in your phone via USB,boot into fastboot mode, open a cmd prompt in that folder and enter the following commands:

fastboot devices

(You should see a device number than like ABC45DE)

fastboot flash recovery "name of your recovery.img" (for example

fastboot flash recovery twrp.3.0.2-4-titan.img)

Then boot into recovery again (you should see the new recovery) to make it stick and after that into system.

Done.

You can do that with flashify too but I don't know the steps exactly as I always do it like above.
[G 2014 Original Android Development] riancarlos18:
Great!

I recommend this version of TWRP. It runs flawlessly on my titan device. :)
[G 2014 Original Android Development] J4jks:
Flashing latest image 3.1.0-0 from recovery given problem

Shown "recovery size error" staying in Fastboot mode only

then I flashed using Platform Tools and it worked fine

it is giving prompt for TWRP app installation
[G 2014 Original Android Development] JD154:
working pushing with fasboot from pc? I don't want to break my titan :(
[G 2014 Original Android Development] mankokoma:
For me no problem flashing 3.1.0-0 from inside TWRP 3.0.2-4 downloaded to sdcard. Had also the md5 file in folder (Only to mention).
[G 2014 Original Android Development] J4jks:
Yes it worked Fine for me
[G 2014 Original Android Development] @anonymous94:
Phone going to blank screen after selecting it from fastboot
[G 2014 Original Android Development] MariusKrs:
USB OTG don't work with NTFS formatted devices. I cannot mount them. With FAT32 formatted devices no issues. My MBM version is 48.87, TWRP 3.1.0-0 and have installed CM13 or LineageOS. Android system mounts NTFS devices.
[G 2014 Original Android Development] Mehul03:
I am randomly facing these errors while flashing. Also while flashing sometimes when these errors appears the recovery becomes excessively laggy and shows some mount errors
[G 2014 Original Android Development] Wolfcity:
I have the same errors but on twrp 3.0.2-4. I use a themed recovery and everytime when this error appears randomly (can not mount xxx) the theme is not active. If I reboot into recovery or flash the twrp theme again everything works ok. I always know if I don't see my twrp themed this error appears. I will attach a log when it happens again.

Are you using any twrp themes?
[G 2014 Original Android Development] vayavalla:
I don't have any theme installed and this happens to me also, with latest twrp and before. Just a reboot to recovery and it works again
[G 2014 Original Android Development] Wolfcity:
I always thought that it's somehow theme related but it seems to be just an twrp issue than. Would be interesting to know why this mounting problems appear and why it's fixed with just a reboot.

Maybe [MENTION=5778309]luca020400[/MENTION] could say something that brings some light into this issue.
[G 2014 Original Android Development] Mehul03:
I downloaded the official 3.1.0-0 image from the site without any themes. BTW do you mean that a twrp theme would solve this issue?

I so badly want to solve this because it is due to these errors that I am not able to install sailfish OS on my device.

Thanks a lot.
[G 2014 Original Android Development] Wolfcity:
No, I thought that my theme caused that problem because everytime it appears my theme wasn't working.

But it seems to be an issue of twrp 3.0.2-x and up in general. Maybe someone from twrp could clarify that.
[G 2014 Original Android Development] Mehul03:
But I had 3.0.2-4 earlier and I didn't face any such issues. It is after this update to 3.1.0-0 that this problem is showing up.
[G 2014 Original Android Development] Wolfcity:
[MENTION=4457415]vayavalla[/MENTION] had it on 3.1.0-0 and before and I am on 3.0.2-4 and have it too.
[G 2014 Original Android Development] J4jks:
I am also facing this issue when my phone get more heat.

After refreshing the sizes it mounted all partitions fine.

Has anybody observed that we get this issue in over heated situations(say CPU temp. >50°C) only? Or anybody getting this in normal CPU temperature also?
[G 2014 Original Android Development] Mehul03:
But my phone is normally on usual temperature only

It's quite rare that its high but still I'm facing this issue
[G 2014 Original Android Development] Wolfcity:
Someone experience with the latest twrp 3.1.1-0?

Is remote backup via adb working?
[G 2014 Original Android Development] danyprasad:
Need help

me using twrp 3.0.2.4 how to update the new 3.1 version.. any apk using update.. please send guys
[G 2014 Original Android Development] minodroid:
https://twrp.me/devices/motorolamotog2014.html
[G 2014 Original Android Development] adilrenzu:
Recovery flashable
[G 2014 Original Android Development] MarcusBremen:
after flashing 3.1.1 i can't wipe...

error "can't mount storage"

anyone with a solution...
[G 2014 Original Android Development] vayavalla:
Just reboot to recovery and try again. Known and already commented bug.
[G 2014 Original Android Development] MarcusBremen:
[MENTION=4457415]vayavalla[/MENTION]

reflashed 3.0.2v4 and i'm good.

thx pal
[G 2014 Original Android Development] vayavalla:
It's a rare problem that you will probably also face on that version. No need to go back
[G 2014 Original Android Development] iyer78:
unlocked my titan, flashed twrp latest... but am not able to get into twrp.... whenever i select revovery, it comes to a android sign......help me out
[G 2014 Original Android Development] vayavalla:
How did you flash it? What are you doing? More info you give, will be easier for someone to help you
[G 2014 Original Android Development] iyer78:
all done...... twrp latest installed and flashed remix resurrection.... works smooth
[G 2014 Original Android Development] imbassahy:
How can I reinstall TWRP?

Hey guys. This is my first post.

Last year, I've unlocked, rooted and installed Cyanogenmod 13. But my cellphone (Moto G, 2014, titan) was getting worse and worse. So this week I decided to change its ROM, but now it's bricked and I cannot launch TWRP. Before it bricked, I downloaded the app and also I installed the latest version (twrp-3.1.1-0-titan.img) via adb fastboot flash recovery. I use debian stretch.

The thing is that when I'm on the fastboot screen and select the recovery option, it doesn't get past the blue teamwin screen.

Is there a way to uninstall and reinstall TWRP via terminal?

Thanks a lot :o
[G 2014 Original Android Development] mauriciognr:
Hi guys, this is a video a made some time ago about installing TWRP and CM13 in the Titan. Just use the msot recen TWRp version instead of the one i used in the video and youre golden.

[YOUTUBE]9HWbRq_ovFk[/YOUTUBE]

PS: Is in spanish. Hope this is ok with op.
[G 2014 Original Android Development] jean-luc100:
Cannot start TWRP from Fastboot mode

Hi,

I have unlocked my Moto G2 and flashed TWRP 3.1.1 using "fastboot flash recovery twrp-3.1.1-0-titan.img". Issue is I can't go into TWRP Recovery from Fastboot mode. When I try to do so the phone just shuts down.

I was able to start TWRP via "fastboot boot twrp-3.1.1-0-titan.img" though and from there was able to install LineageOS. Now I have the ability to start LineageOS and from there reboot into TWRP. Yet I would like to fix not being able to go into TWRP directly from fastboot mode. I have re-flashed TWRP a few times but the issue remains.

Any help is much appreciated.
[G 2014 Original Android Development] alligator_asl:
Try to update your bootloader, look at this tutorial.
[G 2014 Original Android Development] jean-luc100:
Thanks for your advice... unfortunately, still same issue.

For your record, this is the output from my CMD window (admin):

D:\Downloads\Android Custom ROMs\Motorola Moto G 2014 (titan)\Flashed on 2017-08-16 - Android 7.1.2\Bootloader files for XT1068>fastboot flash partition gpt.bin

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:partition: not found

target reported max download size of 536870912 bytes

sending 'partition' (32 KB)...

OKAY [ 0.047s]

writing 'partition'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.372s

D:\Downloads\Android Custom ROMs\Motorola Moto G 2014 (titan)\Flashed on 2017-08-16 - Android 7.1.2\Bootloader files for XT1068>fastboot flash motoboot motoboot.img

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:motoboot: not found

target reported max download size of 536870912 bytes

sending 'motoboot' (2184 KB)...

OKAY [ 0.148s]

writing 'motoboot'...

(bootloader) Motoboot: Preflash validation for tz

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.478s

D:\Downloads\Android Custom ROMs\Motorola Moto G 2014 (titan)\Flashed on 2017-08-16 - Android 7.1.2\Bootloader files for XT1068>fastboot flash modem NON-HLOS.bin

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:modem: not found

target reported max download size of 536870912 bytes

sending 'modem' (49356 KB)...

OKAY [ 1.635s]

writing 'modem'...

OKAY [ 1.322s]

finished. total time: 2.957s

D:\Downloads\Android Custom ROMs\Motorola Moto G 2014 (titan)\Flashed on 2017-08-16 - Android 7.1.2\Bootloader files for XT1068>fastboot erase modemst1

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:modemst1: not found

erasing 'modemst1'...

OKAY [ 0.063s]

finished. total time: 0.063s

D:\Downloads\Android Custom ROMs\Motorola Moto G 2014 (titan)\Flashed on 2017-08-16 - Android 7.1.2\Bootloader files for XT1068>fastboot erase modemst2

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:modemst2: not found

erasing 'modemst2'...

OKAY [ 0.078s]

finished. total time: 0.078s

D:\Downloads\Android Custom ROMs\Motorola Moto G 2014 (titan)\Flashed on 2017-08-16 - Android 7.1.2\Bootloader files for XT1068>fastboot flash fsg fsg.mbn

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:fsg: not found

target reported max download size of 536870912 bytes

sending 'fsg' (651 KB)...

OKAY [ 0.125s]

writing 'fsg'...

OKAY [ 0.078s]

finished. total time: 0.203s
[G 2014 Original Android Development] UzikUA:
Hey guys,

Trying to flash recovery, everything is fine but after flash can't login to TWRP because stock recovery loading :(

Have XT1068, unlocked bootloader (Status Code 3), bootloader 4882.

Using miniadb, cmd from administrator.

C:\adb>fastboot flash recovery twrp-3.1.1-0-titan.img

target reported max download size of 536870912 bytes

sending 'recovery' (8124 KB)...

OKAY [ 0.273s]

writing 'recovery'...

OKAY [ 0.174s]

finished. total time: 0.451s

No error on the phone...

Tried different versions of TWRP - same issue.

I want change firmware on my device because it is not working after motherboard replacement.
[G 2014 Original Android Development] vygavedha:
This is because twrp is replaced by stock recovery..

You have to boot to twrp recovery using fastboot command to prevent this..
[G 2014 Original Android Development] UzikUA:
Thanks! I tried to boot with buttons unsuccessfully. But now I did fastboot boot recovery.img from cmd and it works!

Now I have issues with TWRP backup and advanced wipe. A lot of errors appeared:

Error opening: '/data/data/com.android.facelock' (I/O error)

Error opening: '/data/data/com.google.android.deskclock' (I/O error)

etc...

It seems partition errors?
[G 2014 Original Android Development] Wolfcity:
Seems the partion is corrupted. Try to reformat /data and maybe following partitions.
[G 2014 Original Android Development] UzikUA:
I tried to use advanced wipe from TWRP menu.

Do I need launch reformat from fastboot?

Do you know any commands?
[G 2014 Original Android Development] :
fastboot flash partition gpt.bin

i think you must repair your filesystem in twrp options

whe doesn't help, you can try install stock-rom via adb. whe this works you can install twrp and lineage too