Related
For some reason when I try to backup my ROM with nandroid it says it can't mount /data or /system. I have /data encrypted and its not asking me for a password. I reflashed TWRP and CWM and I got the same error in CWM. I checked and write protection isn't on. Its a Dev Edition GSM. Anyone know how to fix it?
*Bump* help please
which version of TWRP are you using? which version of android?
beelzebu said:
which version of TWRP are you using? which version of android?
Click to expand...
Click to collapse
2.6.3.1. I'm on KitKat. I think TWRP can't mount encrypted /data
spyz88 said:
2.6.3.1. I'm on KitKat. I think TWRP can't mount encrypted /data
Click to expand...
Click to collapse
I'm having the same issue. I really hope we can find a way to make this work on the Moto X.
Is 2.6.3.1 officially from TWRP or is it something someone forked? Their site shows changes up to 2.6.3.0 only.
that is the correct recovery for 4.4 on any unlocked bootloader device.
only thing i can think of to try removing the encryption and try backing it up
i just ran a nandroid backup 2 days ago on 4.4 so i know it works
dray_jr said:
that is the correct recovery for 4.4 on any unlocked bootloader device.
only thing i can think of to try removing the encryption and try backing it up
i just ran a nandroid backup 2 days ago on 4.4 so i know it works
Click to expand...
Click to collapse
Yeah it works without encryption (removing it requires factory reset btw) but I want to be able to backup while encrypted. I know TWRP was able to mount encrypted partitions on the Nexus 4, I was hoping someone could help get that working on the Moto X.
fbiryujin said:
Yeah it works without encryption (removing it requires factory reset btw) but I want to be able to backup while encrypted. I know TWRP was able to mount encrypted partitions on the Nexus 4, I was hoping someone could help get that working on the Moto X.
Click to expand...
Click to collapse
that is something i didnt know i have never encrypted my data. i agree hopefully someone will but with little Dev support it could take awhile.
Hi All! I've installed the rooted stock 4.4.4 image that @gokart2 has made available (great work, btw!) and it's working great, except for one thing -- the built-in version of Titanium Backup is having problems reading my license file, and even after buying the PRO version from the play store, it still doesn't make any of the PRO/donate features available. Is anybody else having this problem or know how to fix it?
Thanks!
Dave
RobinATL said:
Hi All! I've installed the rooted stock 4.4.4 image that @gokart2 has made available (great work, btw!) and it's working great, except for one thing -- the built-in version of Titanium Backup is having problems reading my license file, and even after buying the PRO version from the play store, it still doesn't make any of the PRO/donate features available. Is anybody else having this problem or know how to fix it?
Thanks!
Dave
Click to expand...
Click to collapse
Did you try uninstalling TiB/U and the Pro key and then reinstalling them from the playstore?
Wansanta said:
Did you try uninstalling TiB/U and the Pro key and then reinstalling them from the playstore?
Click to expand...
Click to collapse
Because @gokart2 made it built-in, you can't uninstall it, at least I haven't found a way to do it yet.
RobinATL said:
Because @gokart2 made it built-in, you can't uninstall it, at least I haven't found a way to do it yet.
Click to expand...
Click to collapse
Is your bootloader unlocked?
Wansanta said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes
RobinATL said:
Yes
Click to expand...
Click to collapse
is there some reason you need to use a rooted stock image? Why not just root your phone by hand? It takes all of 10 minutes to do it and you can install TiBU from the playstore and it will work fine.
Wansanta said:
is there some reason you need to use a rooted stock image? Why not just root your phone by hand? It takes all of 10 minutes to do it and you can install TiBU from the playstore and it will work fine.
Click to expand...
Click to collapse
Because when I went looking for a stock image to revert to from the CM11 nightly, that was the only one that I could find. If you can point me to a fully stock version of 4.4.4 for the Sprint 1st Gen, I'd be happy to flash that
RobinATL said:
Because when I went looking for a stock image to revert to from the CM11 nightly, that was the only one that I could find. If you can point me to a fully stock version of 4.4.4 for the Sprint 1st Gen, I'd be happy to flash that
Click to expand...
Click to collapse
Just checked here and it looks like 4.4.2 is the last sbf for Sprint. Has Sprint Moto X not been updated to 4.4.4 yet?
According to Sprint, 4.4.4 was released on 8/20/2014
RobinATL said:
According to Sprint, 4.4.4 was released on 8/20/2014
Click to expand...
Click to collapse
OK, well I don't know why there is no sbf yet. I know a poster here would make unofficial FXZs before the SBFs were released but I don't know how he did it.
I think I am going to test returning to stock 4.4.2 after having my bootloader upgraded to 4.4.4 and then either taking the 4.4.4 OTA or using the Motorola Device Manager to update me to 4.4.4 on an unlocked Verizon device. If it works I will let you know.
I still have to make sure I understand how the OTA updater script works versus Motorola Device Manger b/f I do it.
I have a 4.4.2 rooted nandroid that I can return to and unroot. Do you have any nandroids of your system on 4.4.2?
Edited - just found what I was looking for:
http://forum.xda-developers.com/showpost.php?p=50721066&postcount=18
Q9Nap said:
you CAN reapply the ota after flashing back to 4.4. the updater script sees that the motoboot parts and gpt are already upgraded and just skips them; you will not brick.
Click to expand...
Click to collapse
Sprint 4.4.4 fxz:
http://www.filefactory.com/file/6ti...4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
all thanks to daywalker04
Q9Nap said:
Sprint 4.4.4 fxz:
http://www.filefactory.com/file/6ti...4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
all thanks to daywalker04
Click to expand...
Click to collapse
Thanks - can you confirm for me that I can revert back to a 4.4.2 nandroid and take the 4.4.4 OTA again on Verizon unlocked bootloader? I know I can go back to my 4.4.2 nandroid after upgrading to 4.4.4 b/c I have done it several times. When I do, presumably everything goes back to 4.4.2 but the bootloader and partition table, which stay on 4.4.4. And since the OTA updater script will see that I am on 4.4.4 bootloader and partition table, it will just skip patching those and just patch the files that are on 4.4.2., so I can take the 4.4.4 OTA again, correct?
Thanks!
Wansanta said:
Thanks - can you confirm for me that I can revert back to a 4.4.2 nandroid and take the 4.4.4 OTA again on Verizon unlocked bootloader? I know I can go back to my 4.4.2 nandroid after upgrading to 4.4.4 b/c I have done it several times. When I do, presumably everything goes back to 4.4.2 but the bootloader and partition table, which stay on 4.4.4. And since the OTA updater script will see that I am on 4.4.4 bootloader and partition table, it will just skip patching those and just patch the files that are on 4.4.2., so I can take the 4.4.4 OTA again, correct?
Thanks!
Click to expand...
Click to collapse
yes.
you just quoted me saying that in post #10 of this thread; am i missing something?
why would you want to bother with the 4.4.4 ota when the 4.4.4 fxz is available?
Q9Nap said:
yes.
Click to expand...
Click to collapse
Q9Nap said:
you just quoted me saying that in post #10 of this thread; am i missing something?
Click to expand...
Click to collapse
Sorry those quotes were from other threads - I was just quoting you b/c I have never done these things myself yet and I am going off of what you were saying and you were saying it in those posts better than I could and so I quoted you. I just wanted to make sure I understood what you were saying b/c a lot of people here claim you will brick your device if you do that. I don't think that is true just confirming it.
Q9Nap said:
why would you want to bother with the 4.4.4 ota when the 4.4.4 fxz is available?
Click to expand...
Click to collapse
Because when I was on 4.4.2 rooted, I did a nandroid but then flashed the 4.4.2 system and recovery to return to stock and then took the 4.4.4 OTA. Then when I went to restore my texts messages using Titanium Backup from my 4.4.2 nandroid, it restores them perfectly BUT I can no longer receive texts. I can send texts fine, but I can't receive them.
When I restored my texts I selected data only and also had the correct settings in preferences but for whatever reason no one has been able to tell me, Titanium B/U messes with the 4.4.4 messanging app or maybe my APNs? Idk, but I have reproduced this about 5 times now everytime it is exactly the same - I cannot receive texts after restoring my texts from my 4.4.2 nandroid.
I then tried SMS b/u and restore and it can't restore all of my old texts. So now I want to go back to my 4.4.2 nandroid, unroot, return to stock recovery and then take the 4.4.4 OTA to keep my texts. I can't think of any other way to do it.
Wansanta said:
Sorry those quotes were from other threads - I was just quoting you b/c I have never done these things myself yet and I am going off of what you were saying and you were saying it in those posts better than I could and so I quoted you. I just wanted to make sure I understood what you were saying b/c a lot of people here claim you will brick your device if you do that. I don't think that is true just confirming it.
Because when I was on 4.4.2 rooted, I did a nandroid but then flashed the 4.4.2 system and recovery to return to stock and then took the 4.4.4 OTA. Then when I went to restore my texts messages using Titanium Backup from my 4.4.2 nandroid, it restores them perfectly BUT I can no longer receive texts. I can send texts fine, but I can't receive them.
When I restored my texts I selected data only and also had the correct settings in preferences but for whatever reason no one has been able to tell me, Titanium B/U messes with the 4.4.4 messanging app or maybe my APNs? Idk, but I have reproduced this about 5 times now everytime it is exactly the same - I cannot receive texts after restoring my texts from my 4.4.2 nandroid.
I then tried SMS b/u and restore and it can't restore all of my old texts. So now I want to go back to my 4.4.2 nandroid, unroot, return to stock recovery and then take the 4.4.4 OTA to keep my texts. I can't think of any other way to do it.
Click to expand...
Click to collapse
Hmm, did you at any point switch from stock mms app to hangouts app for sms?
Maybe go back to working config and switch to hangouts for sms, then reply to the texts through hangouts so they are backed up that way.
Not sure this will work, but worth a shot...
I don't have a problem with you quoting me, just don't understand why you were asking for verification.
Q9Nap said:
Hmm, did you at any point switch from stock mms app to hangouts app for sms?
Click to expand...
Click to collapse
I did but then I undid that and same result. Then I restored from a 4.4.4 nandroid that was made before I did that. After restoring my texts again using TiBU, still the same problem.
But if I restored using SMS B/U and Restore, I could send and receive texts but SMSBU&R can't restore all of my texts for me nor can it tell me which texts it can't restore. It just tells me the number that it can't restore.
Clearly TiBU is doing more than just restoring my texts but I can't figure out what it is doing.
Q9Nap said:
I don't have a problem with you quoting me, just don't understand why you were asking for verification.
Click to expand...
Click to collapse
Because you are the only poster here who will say you won't brick if you downgrade your system after upgrading your bootloader and who will say that trying to downgrade the partition table and bootloader won't brick, it will just fail. Everyone else tells people they will brick. I just wanted to confirm that I really understood what you were saying b/c what you are saying is the complete opposite of what every other person here who gives advice says.
The others just say across the board - downgrading or attempting to downgrade will brick.
I realize that your comments are specific to those with unlocked bootloaders, but others here will make no distinction and say across the board that you will brick if you attempt to downgrade or if you upgrade then go back to an earlier system and then take the OTA.
Basically what has happened is a guy who used to post here and no longer does said that even those with unlocked bootloaders can't downgrade without bricking, which is false, but it has been repeated here so many times in all of the stickies and so many threads that people think it is true and just keep repeating it and repeating it and repeating it.
I just needed more reassurance that I understood you correctly given that others have posted misinformation here repeatedly to the point it is now accepted as fact when it is not true. Thanks.
Q9Nap said:
I don't have a problem with you quoting me, just don't understand why you were asking for verification.
Click to expand...
Click to collapse
SUCCESS!!! Kind of.
I returned to my 4.4.2 nandroid, disabled the Xposed Installer, flashed the stock recovery, unfroze all of the apps I had frozen, including Motorola OTA, and unrooted. Then I took the 4.4.4 OTA again and had all of my texts, woot!!
HOWEVER, I still can't receive texts!!!!!! I found this thread on AC and it seems like others have this problem too after taking the 4.4.4 OTA. Drats. At least now I know it isn't TiBU.
Well at least I know I can downgrade and take an OTA fine.
RobinATL said:
Hi All! I've installed the rooted stock 4.4.4 image that @gokart2 has made available (great work, btw!) and it's working great, except for one thing -- the built-in version of Titanium Backup is having problems reading my license file, and even after buying the PRO version from the play store, it still doesn't make any of the PRO/donate features available. Is anybody else having this problem or know how to fix it?
Thanks!
Dave
Click to expand...
Click to collapse
I apologize for just seeing this. You should have PM'd me, I would have walked you through it. All you need to do is download a file explorer app (like ES file explorer), and go to system/app/com.keramidas.TitaniumBackup.apk and delete it. Then re-install from the play store.
Q9Nap said:
Sprint 4.4.4 fxz:
http://www.filefactory.com/file/6ti...4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
all thanks to daywalker04
Click to expand...
Click to collapse
I don't know if it was a bad DL, since I only tried the free DL option, but it wouldn't let me run the zip using TWRP. i did the normal wipes and it failed. do I need to do something different?
agentcelsius said:
I don't know if it was a bad DL, since I only tried the free DL option, but it wouldn't let me run the zip using TWRP. i did the normal wipes and it failed. do I need to do something different?
Click to expand...
Click to collapse
This isn't a flashable zip, it's a collection of fastboot partition images a.k.a Fastboot Xml Zip (FXZ). There are many tutorials on how to use them...
I accidentally did a number on my Moto G. Is there anyone who has a way to restore like you would on Kitkat?
I was in the middle of sideloading the Lollipop update and was on 21.85-17 before that. It seems like my phone thinks it was partially updated...
Thanks for the help!
esodak said:
I accidentally did a number on my Moto G. Is there anyone who has a way to restore like you would on Kitkat?
I was in the middle of sideloading the Lollipop update and was on 21.85-17 before that. It seems like my phone thinks it was partially updated...
Thanks for the help!
Click to expand...
Click to collapse
What exactly is your problem?
I don't think you can restore the using a 4.4 system image according to this post on the motorola forums.
I figured it out.
Since the update failed, the system just needed to be restored. When I was following the instructions, I skipped a file. I fixed it up now. Thanks for the help though, surenzxx!
esodak said:
I figured it out.
Since the update failed, the system just needed to be restored. When I was following the instructions, I skipped a file. I fixed it up now. Thanks for the help though, surenzxx!
Click to expand...
Click to collapse
Did you end up skipping the sparsechunk.3 file? I did when I was restoring to stock so I could flash the OTA.
Glad to hear your problem's solved!
Hey guys i just a thread in the Android Development forum about a guy possibly making Lollipop work on many devices! It is a great news and can someone upload the CWM/TWRP Backup here? Needed to make a flashable zip!!
I actually need this kinda backup too. Whenever I try to flash this http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881 via stock recovery, it says "/system/lib/hw/sensort.MSM8226.so" has unexpected contents.
I'm trying hard to find a way on how to make a flashable zip, no luck though...
savnex said:
I actually need this kinda backup too. Whenever I try to flash this http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881 via stock recovery, it says "/system/lib/hw/sensort.MSM8226.so" has unexpected contents.
I'm trying hard to find a way on how to make a flashable zip, no luck though...
Click to expand...
Click to collapse
there are 2 sensors.msm8226.so files in the zip. the folder path is /patch/system/lib/hw/... open the zip delete it and ur done!
I reflashed stock for the third time and the update via stock recovery worked. Don't know what did the trick, but I have lollipop now lol.
savnex said:
I reflashed stock for the third time and the update via stock recovery worked. Don't know what did the trick, but I have lollipop now lol.
Click to expand...
Click to collapse
could u please take a twrp backup without including data and upload it somewhere and give me the link?
Follow this guide, it's easier http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340
savnex said:
Follow this guide, it's easier http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340
Click to expand...
Click to collapse
i dont own an G2 i own G1 wanna port this update to G1 and hence the sump request bro.
yeshwanthvshenoy said:
Hey guys i just a thread in the Android Development forum about a guy possibly making Lollipop work on many devices! It is a great news and can someone upload the CWM/TWRP Backup here? Needed to make a flashable zip!!
Click to expand...
Click to collapse
Hi, I uploaded a backup to Google Drive https://drive.google.com/open?id=0B-51lsOzTcp5amJuQklLZjBlckE&authuser=0
I make 2 backups, one with XT1063 firmware and the second with XT1064 firmware, boot with the build.prop edited to work with 2 SIMS.
Let me know if it works for you
luisjoseb said:
Hi, I uploaded a backup to Google Drive https://drive.google.com/open?id=0B-51lsOzTcp5amJuQklLZjBlckE&authuser=0
I make 2 backups, one with XT1063 firmware and the second with XT1064 firmware, boot with the build.prop edited to work with 2 SIMS.
Let me know if it works for you
Click to expand...
Click to collapse
working on it! boot.img issues!!
luisjoseb said:
Hi, I uploaded a backup to Google Drive https://drive.google.com/open?id=0B-51lsOzTcp5amJuQklLZjBlckE&authuser=0
I make 2 backups, one with XT1063 firmware and the second with XT1064 firmware, boot with the build.prop edited to work with 2 SIMS.
Let me know if it works for you
Click to expand...
Click to collapse
Can I use this on my XT104 running KitKat with an unlocked boot loader? Can I just copy it to my SD card and restore it without issue?
those xt1063 backups works with trwp custom recovery installed and the gsm global versio bought at USA?
No
luisjoseb said:
Hi, I uploaded a backup to Google Drive https://drive.google.com/open?id=0B-51lsOzTcp5amJuQklLZjBlckE&authuser=0
I make 2 backups, one with XT1063 firmware and the second with XT1064 firmware, boot with the build.prop edited to work with 2 SIMS.
Let me know if it works for you
Click to expand...
Click to collapse
Hi first off i wanna say thank you!
I have an XT1064 that was rooted and bootloader unlocked, i downloaded the right version and restored it using TWRP and it worked! I am now on 5.0 with out using any PC or anything..the only thing is i cant send a text...calls work fine just no text messages...can you help me? I also want to get rid of the dual sim feature as my phone only has one sim. Please help!
Okay so I tried to download and flash the OTA.zip for my phone and flash it through stock recovery and it aborts when verifying my current system because of the edited build.prop in this build. Is there any way to fix this without a PC? I don't have access to one right now. Feel free to PM me! Thank you XDA
Dual SIM Removal
Robertleehadley said:
No
Hi first off i wanna say thank you!
I have an XT1064 that was rooted and bootloader unlocked, i downloaded the right version and restored it using TWRP and it worked! I am now on 5.0 with out using any PC or anything..the only thing is i cant send a text...calls work fine just no text messages...can you help me? I also want to get rid of the dual sim feature as my phone only has one sim. Please help!
Okay so I tried to download and flash the OTA.zip for my phone and flash it through stock recovery and it aborts when verifying my current system because of the edited build.prop in this build. Is there any way to fix this without a PC? I don't have access to one right now. Feel free to PM me! Thank you XDA
Click to expand...
Click to collapse
Thanks for this Recovery. I really appreciate it. However, I am stuck with the phone thinking it's a Dual SIM phone.
How do I make it recognize that it's just one SIM Card.
Thanks.
Damionix said:
Thanks for this Recovery. I really appreciate it. However, I am stuck with the phone thinking it's a Dual SIM phone.
How do I make it recognize that it's just one SIM Card.
Thanks.
Click to expand...
Click to collapse
Sir..you will need to flash, via adb, the stock firmware for your device..then flash the 5.0 update zip via stock recovery..
sent from my
5.0_22.11.6 Lollipop
XT1064 Moto G (2nd Gen.)
I was running Cyanogenmod 12.1 on my Moto G 2014 (second gen). After installing an app, I rebooted, and got stuck in a boot-loop. I booted into recovery (TWRP) and wiped my Dalvik Cache, Data, Internal Storage (whoops), Cache, and System. Afterwards, I got a mount error on /data, dalvik, and internal storage. I ran the "df" command in the recovery terminal to list the partitions. I got a table listing /dev, /tmp/dev/block/mmcblk0p35, /cache/dev/block/mmcblk1p1, and /sdcard1. I am pretty sure I have deleted some partitions. How do I repartition my phone on a Windows 10 laptop? Any help is greatly appreciated. I have found a guide here describing how to do this on a Linux laptop, but I do not know the equivalent Windows commands. That thread is located here. Thank you!
swolff1234 said:
I was running Cyanogenmod 12.1 on my Moto G 2014 (second gen). After installing an app, I rebooted, and got stuck in a boot-loop. I booted into recovery (TWRP) and wiped my Dalvik Cache, Data, Internal Storage (whoops), Cache, and System. Afterwards, I got a mount error on /data, dalvik, and internal storage. I ran the "df" command in the recovery terminal to list the partitions. I got a table listing /dev, /tmp/dev/block/mmcblk0p35, /cache/dev/block/mmcblk1p1, and /sdcard1. I am pretty sure I have deleted some partitions. How do I repartition my phone on a Windows 10 laptop? Any help is greatly appreciated. I have found a guide here describing how to do this on a Linux laptop, but I do not know the equivalent Windows commands. That thread is located here. Thank you!
Click to expand...
Click to collapse
Hi, that thread is for another phone, in this case for the Samsung Galaxy Ace.
Pay attention at what you search
I suggest you to try to downgrade to kitkat. Here's the guide
h4ck3r00 said:
Hi, that thread is for another phone, in this case for the Samsung Galaxy Ace.
Pay attention at what you search
I suggest you to try to downgrade to kitkat. Here's the guide
Click to expand...
Click to collapse
Thank you. I'll give it a go.
h4ck3r00 said:
Hi, that thread is for another phone, in this case for the Samsung Galaxy Ace.
Pay attention at what you search
I suggest you to try to downgrade to kitkat. Here's the guide
Click to expand...
Click to collapse
The links are broken on that thread. Any idea where I can get the ROM and tool elsewhere?
I'll upload them ASAP, then i'll post you the link
h4ck3r00 said:
I'll upload them ASAP, then i'll post you the link
Click to expand...
Click to collapse
Thank you!
swolff1234 said:
The links are broken on that thread. Any idea where I can get the ROM and tool elsewhere?
Click to expand...
Click to collapse
swolff1234 said:
Thank you!
Click to expand...
Click to collapse
I forgot to ask you which model do you nave, because i only have the XT1068 files..
This should help: http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
It has stock firmware for XT1063, XT1064, XT1068, and XT1069.
Hope this helps.
ethanbmnz said:
This should help: http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
It has stock firmware for XT1063, XT1064, XT1068, and XT1069.
Hope this helps.
Click to expand...
Click to collapse
I have the XT1064. Sorry for replying late. I'll try the link with the stock firmware. Will this restore the /Persist partition? I have everything else working now.
I do not know what the /persist partition is, sorry.