Related
Does anyone know why the Moto X is not listed on TWRP's supported devices page?
http://teamw.in/twrp_view_all_devices
I would really like to have twrp 2.7 for USB OTG mounting. Anyone know why it's not available?
Moto x is not supported by twrp. So someone needs to make a Moto x version. Just like the other versions we have.
Sent from my N5 cell phone telephone....
TWRP 2.6.3.1 works just fine with the Moto X. USBotg works natively with v4.4.2 but leaves a notification that cannot be cleared. Using Stickmount, unmounting leaves a notification error, but that can be swiped away.
TWRP encrypted /data support for Moto X ?
I have the latest (2.6.3.2 twrp motox from dhacker) and have recently encrypted /data.
As a result, when I go to do a backup twrp is unable to mount /data and therefore fails.
I've googled various things (twrp, encryption, motox, various combinations) and this
was the most promising thread.
As mentioned (above) twrp doesn't support the motox devices...
Does anyone have any suggestions how to
a. take a backup of the encrypted /data partition
b. find a twrp for motox that will do so
or worst case
c. where to find instructions on how to build twrp for the xt1053/58/60...
Thanks in advance.
Ehud
Tucson AZ US
Groid said:
TWRP 2.6.3.1 works just fine with the Moto X. USBotg works natively with v4.4.2 but leaves a notification that cannot be cleared. Using Stickmount, unmounting leaves a notification error, but that can be swiped away.
Click to expand...
Click to collapse
Are you talking about OTG in recovery or in the actual android OS? I'm talking about twrp recovery... didn't know there was a way to use stick mount in recovery... anyway otg works within cwm recovery but not twrp for me.... why isn't the Moto x officially supported by TWRP? There are a lot more less popular devices that are... Thanks
dkoon1987 said:
Are you talking about OTG in recovery or in the actual android OS? I'm talking about twrp recovery... didn't know there was a way to use stick mount in recovery... anyway otg works within cwm recovery but not twrp for me.... why isn't the Moto x officially supported by TWRP? There are a lot more less popular devices that are... Thanks
Click to expand...
Click to collapse
Yeah, sorry, I didn't get that you were only specifically looking for otg in recovery. I've never tried it in recovery. Also, I don't have an encrypted phone.
http://androidhosting.org/Devs/Dhacker29/MotoX/TWRP-2.7.0.0-moto_msm8960dt.img
Moto X Finally Gets Official Build Of TWRP Custom Recovery :
http://www.androidpolice.com/2014/06/10/moto-x-finally-gets-official-build-of-twrp-custom-recovery/
http://teamw.in/project/twrp2/234
hotsync100 said:
Moto X Finally Gets Official Build Of TWRP Custom Recovery :
http://www.androidpolice.com/2014/06/10/moto-x-finally-gets-official-build-of-twrp-custom-recovery/
http://teamw.in/project/twrp2/234
Click to expand...
Click to collapse
Link is currently broken for moto x (ghost)... :/
samwathegreat said:
Link is currently broken for moto x (ghost)... :/
Click to expand...
Click to collapse
When the link gets fixed should a new post be added to the Android Development subforum?
Link is working fine. Here's a direct link to the img: http://techerrata.com/browse/twrp2/ghost.
thehockeydude44 said:
When the link gets fixed should a new post be added to the Android Development subforum?
Click to expand...
Click to collapse
A new post, yes. A new thread isn't necessary. Just forewarning those who might jump to download only to find the link broken...
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
klobkelosh said:
Link is working fine. Here's a direct link to the img: http://techerrata.com/browse/twrp2/ghost.
Click to expand...
Click to collapse
The link from within twrp manager is what is broken (still):
Warning: md5_file(ghost/openrecovery-twrp-2.7.1.1-ghost.img): failed to open stream: No such file or directory in /home/mazwoz/public_html/recovery/file/twrp2/download.php on line 70 MD5:
samwathegreat said:
A new post, yes. A new thread isn't necessary. Just forewarning those who might jump to download only to find the link broken...
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
The link from within twrp manager is what is broken (still):
Warning: md5_file(ghost/openrecovery-twrp-2.7.1.1-ghost.img): failed to open stream: No such file or directory in /home/mazwoz/public_html/recovery/file/twrp2/download.php on line 70 MD5:
Click to expand...
Click to collapse
One could flash the img via fastboot. Or, download the img and flash on device with the flashify app.
klobkelosh said:
One could flash the img via fastboot. Or, download the img and flash on device with the flashify app.
Click to expand...
Click to collapse
Absolutely, one could definitely flash the img via fastboot.
The point is, now that Moto X has official support of TWRP, the OFFICIAL TWRP page recommends using the Official "TWRP Manager" app.
This is a great idea, because you can easily flash any new updates from directly within the app.
So: Anyone interested in updating to the new version, go ahead and flash via fastboot as @klobkelosh has suggested.
But it would still be nice for the "TWRP Manager" link to be fixed so that we can use the app, as the developers intended.
Information on the app here: http://teamw.in/project/twrp2/234
As for "Flashify", that app was reported in another Moto X forum to NOT work on the Moto X. If you have personally used it and it does indeed work for flashing recovery to Moto X, please post back here and let us know. I have not recommended the app to anyone because it was reported to fail while attempting to flash recovery on the X.
samwathegreat said:
As for "Flashify", that app was reported in another Moto X forum to NOT work on the Moto X. If you have personally used it and it does indeed work for flashing recovery to Moto X, please post back here and let us know. I have not recommended the app to anyone because it was reported to fail while attempting to flash recovery on the X.
Click to expand...
Click to collapse
My bad. I have not tested flashify on Moto x. I used it on a gnex and made the unfounded assumption that it works on Moto x. Apologies.
On the other hand... http://forum.xda-developers.com/showthread.php?p=53311645
Hopefully the twrp manager developers can fix the problem.
Flashed 2.7.1.1 with flashify just recently and all is good. Nice not having to plug in using the fastboot method.
ConstantHero said:
Flashed 2.7.1.1 with flashify just recently and all is good. Nice not having to plug in using the fastboot method.
Click to expand...
Click to collapse
Thanks for the info. Now we know this is a working alternative.
Also, sent a message notifying the TWRP team of the broken in-app link. I imagine it will be fixed soon.
Flashed mine with rom toolbox pro.
Sent from my Nexus 7 using Tapatalk
samwathegreat said:
A new post, yes. A new thread isn't necessary.
Click to expand...
Click to collapse
Why not a new thread? I'm not trying to start an argument, just curious... The current thread about TWRP is titled with version 2.6.3.1 with 489 replies, making a new one would clean it up.
thehockeydude44 said:
Why not a new thread? I'm not trying to start an argument, just curious... The current thread about TWRP is titled with version 2.6.3.1 with 489 replies, making a new one would clean it up.
Click to expand...
Click to collapse
Sure...do it. I agree that it should clean things up.
You might even include info about the new version of SuperSU. This could be useful since those on 4.4.3 are recommended to use the latest versions of both TWRP and SuperSU.
Hey guys,
I use the encryption feature of the stock Android 4.4.4 at my Moto G2 XT1068.
The problem is TWRP and CWM don't decrypt the data partition. Therefore I can't do basic things like wipe cache/dalvik or access the internal storage.
Does anyone know a solution to decrypt the data partition? I don't want to forego the encryption feature.
If I get instructions for modifying the source code I can do this too. But be considerate of me, I have only basic skills about bulding from source.
Thank you for your help.
-ratt3
ratt3 said:
Hey guys,
I use the encryption feature of the stock Android 4.4.4 at my Moto G2 XT1068.
The problem is TWRP and CWM don't decrypt the data partition. Therefore I can't do basic things like wipe cache/dalvik or access the internal storage.
Does anyone know a solution to decrypt the data partition? I don't want to forego the encryption feature.
If I get instructions for modifying the source code I can do this too. But be considerate of me, I have only basic skills about bulding from source.
Thank you for your help.
-ratt3
Click to expand...
Click to collapse
Try multirom TWRP.
Big thanks to you LuK1337. Your Multirom TWRP is working flawless. Decryption is working perfectly. :good:
-ratt3
LuK1337 said:
Try multirom TWRP.
Click to expand...
Click to collapse
Hi, I have a similar issue with the decryption. My Phone is Sky Vega IM-A880S. This makes it a lot harder to get hold of ROMS and recoveries . I have been able to find just one recovery that works for it. But it won't decrypt the phone when I give in my PIN.
Is there anyway I can maybe get around this ?
Thanks.
Can you please help me. My friend has a Moto G (2014). He had rooted his phone recently and installed TWRP. By mistake he has wiped his Internal Storage. Now there is no OS in his phone.
Please help me on how can i install the stock firmware back in his phone.
It's okk
.just download any available custom roms from xda
If you are in kitkat try some kitkat rom
And for lolipop try some lp roms
1)Just download the zip
2)place it in sd card
3)open twrp
4)select the zip
5)install gapps for lp otherwise don't
6)reboot to system
Thats all mate
You can try cm,candyrom,blisspop,slim,carbon. And lots of other roms......
Hope it helps
Shawn5162 said:
HI FRIENDS!
So I just got my Moto G 2014 (XT1064) a few days ago. Previously I had only Samsung Smartphone and tablets. Well, with Samsung devices running on android, to restore to stock is very easy using a program called "Odin". All you do is open up Odin and select the firmware tar.md5 file and wait about 10 min. Then your on stock. But sadly, Odin is only for Samsung devices. So for anyone like me who wants a one-click restore to stock method, I've got u covered.
Introducing my new "Restore to Stock" tool for Windows! This is tool currently supports XT1063, XT1064, and XT1068. I will be supporting the XT1069 soon!
So how do u restore to stock?
***This will wipe all your data***
Step 1)
Download the "Moto G 2014 Restore to Android 4.4.4" zip from here:
XT1064:
1) Firmware 21.85.17 [4.4.4] - https://mega.co.nz/#!E1Jw0CTA!mCirOvVNFBSs0fgzcq5Xc1K4LIvRz6v3p0knMeV9iuM
2) Firmware 21.85.23 [4.4.4] -
XT1063
1) Firmware 21.85.23 [4.4.4] - https://mega.co.nz/#!wo4AxQbK!l0McMzx7iHTCjJzb7axDpyPhVBld0fCGAGxbL5-1UBg
XT1068
Firmware 22.99.16 [5.0.2] - https://drive.google.com/file/d/0B_OYdZXdfmnbY092bUIxaTkxRjg/view?usp=sharing
Firmware 21.85.27 [4.4.4] - https://mega.co.nz/#!kxpnEBIZ!NWF7n_-90o_oQQt8lZ9EsWAkN8QL2ITltn4QDD4FsBs
Step 2)
Extract the .zip to a location on your PC/Laptop you can easily access
Step 3)
Plug your Moto G 2014 into your computer
***Make sure all the proper device drivers are installed***
Step 4)
In the extracted folder, find a file called "Auto Restore Script" and click it (It is a Windows batch file)
Step 5)
In less than 5 min. your Moto G 2014 XT1064 will be restored to stock android 4.4.4 (firmware 21.11.17)
NOTE: I RECOMMEND YOU TRY THIS TOOL OUT ON YOUR MOTO G, SO JUST IN CASE IF YOU EVER ARE IN A PROBLEM (BOO-LOOP, CORRUPT PARTITION, ETC.) YOU KNOW HOW TO USE THIS TOOL AND U ARE ASSURED THIS TOOL WORKS!
If you like my work please donate by clicking "DONATE TO ME" on the left side of this post under my XDA username.
ALL DONATIONS ARE GREATLY APPRECIATED!
XDA:DevDB Information
[Windows Tool] Moto G 2014 XT1064 Restore to to Stock Android 4.4.4, Tool/Utility for the Moto G 2014
Contributors
Shawn5162, Shawn5162
Version Information
Status: Stable
Current Stable Version: v1.0
Stable Release Date: 2014-11-29
Created 2014-11-29
Last Updated 2014-11-29
Click to expand...
Click to collapse
rahul0209 said:
Can you please help me. My friend has a Moto G (2014). He had rooted his phone recently and installed TWRP. By mistake he has wiped his Internal Storage. Now there is no OS in his phone.
Please help me on how can i install the stock firmware back in his phone.
Click to expand...
Click to collapse
Try this.
Ragarianok said:
Try this.
Click to expand...
Click to collapse
Thank you for the steps. Will this work for Lolipop too? Or should u install Kitkat first and then upgrade to Lolipop?
rahul0209 said:
Thank you for the steps. Will this work for Lolipop too? Or should u install Kitkat first and then upgrade to Lolipop?
Click to expand...
Click to collapse
Not really sure. It just seems easier just to restore stock KK and update to Lollipop since the internal storage is already gone; no need to back up files.
---------- Post added at 02:08 AM ---------- Previous post was at 02:00 AM ----------
Do you know if your friend's phone was on stock KK or Lollipop? If it was on stock KK, it's just easier to restore to stock using the links above. I suppose the real question here is whether if your friend had an external SD in the phone. If they had already installed a third party KK or Lollipop ROM, they could just download the ROM again and place it on the the external SD and use TWRP to flash it.
Are you able to boot into TWRP at all?
any tools which will help restore internal storage from mac?
rahul0209 said:
Thank you for the steps. Will this work for Lolipop too? Or should u install Kitkat first and then upgrade to Lolipop?
Click to expand...
Click to collapse
Here is the Lollipop version you are looking for. You can easily install the stock ROM with locked or unlocked bootloader.
Rest will be taken care later as usual.
You can root with CF Autoroot. Flash the twrp image using Flashify and you're good to go.
So I was working on an LG L90 (D415) which is now off to repair because it looks like the SIM card reader is non-functional. I have a LG L70 (LGMS323) which hasn't been touched in couple of years, and I was curious, can this device have custom ROMs installed on it too? For instance, I'd like to install CM13 (in this case, Lineage OS 13) but would it even be possible? I am a bit confused as well as it looks like the LG L70 is basically the Metro PCS version of the LG L90, correct? So would essentially the same ROMs that worked on the LG L90 work on the LG L70?
darkgiant said:
So I was working on an LG L90 (D415) which is now off to repair because it looks like the SIM card reader is non-functional. I have a LG L70 (LGMS323) which hasn't been touched in couple of years, and I was curious, can this device have custom ROMs installed on it too? For instance, I'd like to install CM13 (in this case, Lineage OS 13) but would it even be possible? I am a bit confused as well as it looks like the LG L70 is basically the Metro PCS version of the LG L90, correct? So would essentially the same ROMs that worked on the LG L90 work on the LG L70?
Click to expand...
Click to collapse
Go to lineage os download page.. You havê lineage 14.1 official for your l70 (w5)
Warimation said:
Go to lineage os download page.. You havê lineage 14.1 official for your l70 (w5)
Click to expand...
Click to collapse
Woah, that's crazy, so there is no official variant of lineage OS for the L90, but there is one for this L70, lol that's kind of crazy because I thought the L70 was superior (at least in total amount of people using the device).
Warimation said:
Go to lineage os download page.. You havê lineage 14.1 official for your l70 (w5)
Click to expand...
Click to collapse
So I was able to root the device, and install Lineage OS 14.1! Though, I am running into an issue: I thought with Android 7.1.1 we were now able to use MicroSD cards as internal storage, where all apps can be installed to the SD card, correct? I for some reason can only move very few apps to the MicroSD card, and the rest are in internal storage, and as you can imagine, my internal storage is now absolutely full. Any idea if there is anyway to fix this? Or would using an alternative option like Linked2SD be my best option?
darkgiant said:
So I was able to root the device, and install Lineage OS 14.1! Though, I am running into an issue: I thought with Android 7.1.1 we were now able to use MicroSD cards as internal storage, where all apps can be installed to the SD card, correct? I for some reason can only move very few apps to the MicroSD card, and the rest are in internal storage, and as you can imagine, my internal storage is now absolutely full. Any idea if there is anyway to fix this? Or would using an alternative option like Linked2SD be my best option?
Click to expand...
Click to collapse
Dont know.. Never did that..
darkgiant said:
So I was able to root the device, and install Lineage OS 14.1! Though, I am running into an issue: I thought with Android 7.1.1 we were now able to use MicroSD cards as internal storage, where all apps can be installed to the SD card, correct? I for some reason can only move very few apps to the MicroSD card, and the rest are in internal storage, and as you can imagine, my internal storage is now absolutely full. Any idea if there is anyway to fix this? Or would using an alternative option like Linked2SD be my best option?
Click to expand...
Click to collapse
I updated my friends twrp to 3.0.3 and flashed the latest rom from lineage for the lg l70 msm323 phone but now when i reboot im stuck in a boot loop . Any info on how you did yours ? I upgraded it from CM 13 .
I'm using EMMC CWM-based recovery v6.0.4.6 and my rom is Cyanogenmod 11-20141008-SNAPSHOT-M11-ovation.
I would love to upgrade to a faster and more stable rom if there is such a thing. I definitely don't need bleeding edge up to date stuff. I just want speed and stability. Advice appreciated, thanks!
Hi, I've tried various Marshmallow and Nougat ROMS but from my experience they are not as fluid as the CM 11 ROMs - so I've gone back to these as they do everything I need them to do (apart from using the SDCARD as internal storage).
I would be happy to hear other people's experiences though.
herges said:
Hi, I've tried various Marshmallow and Nougat ROMS but from my experience they are not as fluid as the CM 11 ROMs - so I've gone back to these as they do everything I need them to do (apart from using the SDCARD as internal storage).
I would be happy to hear other people's experiences though.
Click to expand...
Click to collapse
I finally convinced my husband to let me update his stock HD to CM 11 (the version archived at the very end of that thread). It was fine except for the need to hold in the power button to make sure it shut down, but he got used to that.
We began to run afoul of a few apps (like our local newspaper) that really wanted Lollipop or better, so I decided to take the plunge and installed the CM 12.1 in @amaces obsolete folder (and a pico GApps). For my husband, it's all good as long as the HDMI port still works
So far no complaints or odd behaviors with the CM 12.1 (same power button issue which apparently is like the poor--it will always be with us). I can't speak to relative speed (are any of these ROMs truly fast?) but it's certainly faster than AOSP 7.0 which I am running on my Nook Tablet, although I would not have known the difference if I had not been tweaking his tablet for him
So we're both happy.
Edit: oh, and that thing about using the SD card as internal storage? I got sucked into that with my AOSP 7.0. The thing is, any backup I make with TWRP is trapped on the tablet. It can't be copied off--can't even be seen outside of TWRP. It eats up at least 2 gb of space that I begrudge. I would not recommend that option and would opt for portable storage if I were setting it up again.
nmyshkin said:
I finally convinced my husband to let me update his stock HD to CM 11 (the version archived at the very end of that thread). It was fine except for the need to hold in the power button to make sure it shut down, but he got used to that.
We began to run afoul of a few apps (like our local newspaper) that really wanted Lollipop or better, so I decided to take the plunge and installed the CM 12.1 in @amaces obsolete folder (and a pico GApps). For my husband, it's all good as long as the HDMI port still works
So far no complaints or odd behaviors with the CM 12.1 (same power button issue which apparently is like the poor--it will always be with us). I can't speak to relative speed (are any of these ROMs truly fast?) but it's certainly faster than AOSP 7.0 which I am running on my Nook Tablet, although I would not have known the difference if I had not been tweaking his tablet for him
So we're both happy.
Click to expand...
Click to collapse
nmyshkin said:
Edit: oh, and that thing about using the SD card as internal storage? I got sucked into that with my AOSP 7.0. The thing is, any backup I make with TWRP is trapped on the tablet. It can't be copied off--can't even be seen outside of TWRP. It eats up at least 2 gb of space that I begrudge. I would not recommend that option and would opt for portable storage if I were setting it up again.
Click to expand...
Click to collapse
I have Nook HD for a few days so you will not be surprised by my questions.
Do you use twrp-3.0.1-0-hummingbird.zip / twrp-3.1.1-0-hummingbird.img (experimental) from amaces or twrp-3.1.1-0-hummingbird.img from twrp.me?
Is there any USB OTG or Enable MTP in the Mount menu and none of it works?
Does any of these versions have Select Storage in the Backup menu and does not work?
ze7zez said:
I have Nook HD for a few days so you will not be surprised by my questions.
Do you use twrp-3.0.1-0-hummingbird.zip / twrp-3.1.1-0-hummingbird.img (experimental) from amaces or twrp-3.1.1-0-hummingbird.img from twrp.me?
Is there any USB OTG or Enable MTP in the Mount menu and none of it works?
Does any of these versions have Select Storage in the Backup menu and does not work?
Click to expand...
Click to collapse
No, if it concerns TWRP, I am not surprised. I flashed 2.8.7.5 to emmc when I did the CM 12.1 upgrade, but did not use it. Thankfully that install can be accomplished with CWM from the SD card. I have not even looked at the TWRP, but on my Nook Tablet I have had nothing but trouble with TWRP (now 3.0.2-0 I think). You have to touch things twice--sometimes. When you touch something you often get something entirely different. Sometimes it can't see the SD card until you boot several times into recovery. I hate it. Too bad CWM just didn't keep going. I don't care about the clunky interface. What good is a touch screen UI if the result is often random?
[Vent]