Database Info

Moto G rooted. 4.4.2 upgrade to 4.4.3 how to?

Moto G, currently running 4.4.2 unlocked and rooted with TWRP v2.6.3.0 the firmware is tweaked to my liking with GravityBox. I am also using the Faux123 to over/under clock etc.
Very happy with the performance, features and battery life.
But I am now getting bugged by the Motorola update for 4.4.3
I did try to update and the phone got into a start, reboot loop. So I have restored to my last configuration.
It's been quite sometime since I played with configuring the above and I have gone a bit blank! Can someone please outline the steps that I have to do to complete the upgrade with minimum fuss.
As a side note. I have avoided custom ROMs so far because of all the problems that I was reading about several months ago. But perhaps enough time has elapsed for me to consider going say CM11 now? I would appreciate any comments as to me going down this route. ie. Are all bugs worked out is the Moto G fully functional, does a custom ROM truly provide worthwhile benefits?
Thanks.

I would also like to know this as well as I am currently on 4.4.2 unrooted, but really feel feel like I want to start and get my Moto G rooted and up and running with all the goody's available on the community, but feel like I should wait for the 4.4.3 rollout before I start going through the whole bootloader unlocking, rooting etc.
So I will check back on this post, and thank you to the thread starter as this saves me starting a similar topic.

Rooted 4.4.2 over here as well. Unfortunately I've had no such luck finding a way to update to 4.4.3 while being rooted. I've been through a plethora of guides and suggestions but nothing seems to be working. I'll end up getting an error no matter what I do.
Don't mean to try and hijack your thread, but I've been trying to flash the .zip for the update with both CWM and TWRP but I get an error every time. Anyone have any ideas why? Do I need to configure root-requiring apps beforehand or something?

ugh...same here! Please someone figure this out!

@Kwala Baerr I was hoping for a quick 1,2,3 Guide! I miss posted the question in the General section, then moved it here. I subsequently find a few similar posts in this section. But your message suggests that you may have already tried them which worries me! Anyway I will have a go tomorrow and post here if I get success.
Sent from my Nexus 7 using Tapatalk

@grahamgo oh yea sorry. Well I've tried just about everything. I think I've narrowed down my problem to SoftKeyz messing up my SystemUI.apk so you might still have a chance. Let me know how it goes though!

grahamgo said:
Moto G, currently running 4.4.2 unlocked and rooted with TWRP v2.6.3.0 the firmware is tweaked to my liking with GravityBox. I am also using the Faux123 to over/under clock etc.
Very happy with the performance, features and battery life.
But I am now getting bugged by the Motorola update for 4.4.3
I did try to update and the phone got into a start, reboot loop. So I have restored to my last configuration.
It's been quite sometime since I played with configuring the above and I have gone a bit blank! Can someone please outline the steps that I have to do to complete the upgrade with minimum fuss.
As a side note. I have avoided custom ROMs so far because of all the problems that I was reading about several months ago. But perhaps enough time has elapsed for me to consider going say CM11 now? I would appreciate any comments as to me going down this route. ie. Are all bugs worked out is the Moto G fully functional, does a custom ROM truly provide worthwhile benefits?
Thanks.
Click to expand...
Click to collapse
Put on your phone Us firmware http://forum.xda-developers.com/showthread.php?t=2542219 setup the phone via wifi. Update is about 163mb. After that use Mototool to root the phone and fix the white screen http://forum.xda-developers.com/showthread.php?t=2635706
mabey you can do a beckup of sms https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore and https://play.google.com/store/apps/details?id=com.riteshsahu.CallLogBackupRestore
regards

I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!

tarotsujimoto said:
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
Click to expand...
Click to collapse
What recovery were you on?

Kwala Baerr said:
What recovery were you on?
Click to expand...
Click to collapse
Here's the thread with information on downloading & installing PhilZ Touch recovery:
http://forum.xda-developers.com/showthread.php?t=2639583
Looks like there's a new stable release out, but I still had PhilZ Touch 6.26.6 Falcon installed.

tarotsujimoto said:
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
Click to expand...
Click to collapse
Im rooted running stock rom and using exposed installer with gravity box and a few other modules running and all I had to do to update to 4.3.3 was to use Moto Tool AIO v3.0 to revert back to stock kitkat recovery, after that I just accepted the update, installed it, and then went back to a custom recovery. I lost none of my exposed installs or settings, took maybe 10 minutes start to finish and was painless.

tarotsujimoto said:
Here's the thread with information on downloading & installing PhilZ Touch recovery:
http://forum.xda-developers.com/showthread.php?t=2639583
Looks like there's a new stable release out, but I still had PhilZ Touch 6.26.6 Falcon installed.
Click to expand...
Click to collapse
I have just wasted a lot of time...... I tried Philz Touch 6.43.8, no go, then an earlier version, still no go. Then I found a thread saying that there were bugs in later versions, they recommended the use of 6.26.6
I tried it and it works great. However I wasted almost 2 hours finding this out.

castuis said:
Im rooted running stock rom and using exposed installer with gravity box and a few other modules running and all I had to do to update to 4.3.3 was to use Moto Tool AIO v3.0 to revert back to stock kitkat recovery, after that I just accepted the update, installed it, and then went back to a custom recovery. I lost none of my exposed installs or settings, took maybe 10 minutes start to finish and was painless.
Click to expand...
Click to collapse
I appreciate @tarotsujimoto post and I see the logic of this approach. But I too was thinking that it might be less troublesome (but maybe take longer) to go back to factory, update it to 4.4.3 and then re-install Xposed and apps + data, etc using Titanium.
@castuis I am intrigued by your mention of using a custom recovery. Could you please expand on what you backed up and if possible more details on how you did it etc.
I have wasted too much time today getting a working Philz Touch going, (maybe I should have stayed with TWRP!). But I do like the look of Philz 6.26.6 now its working. But will have to put my 4.4.3 update attempt off for a day or so.
Thanks!

Since none of the methods mentioned works for me, I have tried to extract the system.img from the original ROM archive. But how do I mount that system.img_sparsechunk files on Linux? They can not be converted by simg2img or unyaffs either ...

I had no success with any of the "short cut" methods either. I was hoping that @castuis promise of a 10 minute method would come true, but he hasn't been back to expand on his method. I myself reverted the phone to factory, let it upgrade. Then re-rooted, installed xposed and then let Google play reinstall my apps. It's definitely not a quick method. But at least it gave me a clean install. Significant frustration, caused by using Philz touch, but switched to TWRP. Finally did a system backup with Titanium. I thought that was it. Now it looks like there will be a 4.4.4 soon. I'm thinking to ignore it and wait for the next upgrade. @nodh I would wait for 4.4.4 !
Sent from my Nexus 7 using Tapatalk

I've solved my upgrade problem: I've flashed the 176.44.1 (retail Germany, 4.4.3) stock ROM, as described here. Altough I didn't flash the recovery (to restore root with the ClockWorkMod recovey) and didn't erase userdata. Now I've got the upgrade, with all my settings preserved and even rooted again.

Android Pay error: unable to verify that device is Android compatible

I'm running Cataclysm ROM (the Sept. 10 beta), Franco kernel, and I'm rooted and use Xposed. I receive this error when I try to add a card in Android Pay: "Android Pay cannot be used: Google is unable to verify that your device of the software running on it is Android compatible". I tried disabling root entirely and using RootCloak (Xposed) to hide root from Android Pay and Google Wallet, but I still can't use Pay. Wallet still works as it always has.
I've seen scattered reports of this here and there but no concrete solutions. Has anyone figured out a workaround?

I get this same message on a LG G2, fully stock, rooted, running 5.0.2.

After some searching, I found this, and it did work for me: https://www.reddit.com/r/Android/comments/3k0ge4/android_pay_workaround_without_xposedrootcloak/
Short version: In SuperSU, disable root, goto Android Pay and activate cards. After cards are activated, enable root. Cards still worked.
I'm not sure if you will need to remove the xposed framework (uninstall from inside the xposed installer) and then disable root. I do not use xposed, so I can't confirm this.

This worked perfectly, thanks!
I also recommend using Lockscreen Disabler with Xposed to get rid of the lockscreen requirement.

Do you have to be on the stock kernel? I'm on the latest 5.1.x build of stock lollipop and have Xposed Framework & Franco Kernel installed. I tried full un-root in SuperSu and rebooting, but I still can get Android Pay to complete the card setup. Do I have to re-flash the stock kernel? I figured this was going to be a PITA. lol I understand Googles need for security on the devices with Android Pay, but the check they are doing have to be so hard-core.

Were you able to successfully make a payment with Android Pay? I can add my cards to the app, but Android Pay isn't working for me at McDonald's or Walgreens.

Will Android Pay work on KitKat or only 5.x.x? I have 2 Nexus 5s, one with 4.4.4 and another with 5.1. On the one with 5.1, I have tried the rootcloak method to put both New Google Wallet and Android Pay to the list, force stopped Android Pay, ran it to the end, and it still gives me the error saying that it cannot be used and is unable to verify the device or software running on it is Android compatible. I also had already updated to GPS v8.1.14 and was under the impression that it wasn't functioning properly, so I rolled back to a previous version of 8.1.13, still returns the same error.

Did you even read all of what OP had to say:
"I tried disabling root entirely and using RootCloak (Xposed) to hide root from Android Pay and Google Wallet, but I still can't use Pay. "
So your comment helps not at all since OP said they disabled Root and STILL have this issue. I have the exact same issue at OP so your comment is not the answer to this question. Any one ELSE have any idea how to resolve when you have already disabled root as OP said.
---------- Post added at 09:19 AM ---------- Previous post was at 09:17 AM ----------
Any one who actually READ what OP said have an answer? How to resolve this situation when you have already DISABLED ROOT in SU.

Possible Fix to Android Pay Root + Xposed Issue...
Just found this. Posted last night. Won't be able to test it for a few hours when I get off this plane...
Since it has bothered me for a few days now, I'm going to post this in a few related threads to help others getting the AP rollout. I just found this which looks promising ( http://www.droidforums.net/threads/new-xposed-module-hides-root.284455/ ) Obviously, this requires xposed and is a little bit off topic here, but this approach was not working for me anyway (stock rom and kernel but rooted and with xposed. Also xposed rootcloak did not work either)
I'm on a plane currently, so I cannot test this, but if anyone else can confirm it works / does not work, that would be great. I had gotten to the point that I was able to set up my AMEX card after a clean stock 5.1.1. install and make a purchase before rooting and adding xposed back in the mix. However, now that I am rooted again, I had a purchase denied earlier today. Hopefully this is the solution.

I have not tried it, but heard it did not always work: https://plus.google.com/u/0/114618417341022236593/posts/dUW1QxDjiFH

this didn't work for me, G3 CM12.1

None of this has worked for me.

Yeah I tried root cloak, disabling super user, and all that but none of it work on my G3 running CM 12.1 either

Disabling root in SuperSU did not work for me.

Also seems no one has had this problem, but on a dark layer theme "invertion ui" the text of the card and exp and ccv are white on white, and none of the above has worked for me either.
Nexus 5
Chroma
Xposed
Hells Core b20

same issue with stock nexus 5 that at some point in the past was rooted... after several updates, i never bothered to re-root. SuperSU still there, but doesn't start - no root. But still Android Pay wont work with this error. ugh.

My workaround was to revert to Wallet.
After failing to get Android Pay to work on my rooted Nexus5 with all the suggestions above, I remembered that Google Wallet worked for me last week before updating to Android Pay. I went to Titanium Backup and restored it, and Voila Wallet with all my data! Next, I unchecked the Auto-Update setting in Google Play for the Android Pay app. Then I remembered a Titanium BU Feature that allows you to break the market link of the app. I have not tried a transaction yet, but it sure looks like the old Wallet app will work just fine.
My wife runs a stock non-rooted HTC Mini2 and is perturbed that her loyalty cards are locked out by Android Pay. I think the solution here is to install a version of Wallet that I found on APK mirror/. I'll need to enable "untrusted" apps in settings after gaining developer rights, but it should work without much effort beyond that. I'll try it when she gets home.

I'm rooted with Xposed. I uninstalled Xposed and SU but I still get the error message. Is there any way round this please?

[Q] Sprint Samsung Galaxy S5 Sport SM-G860P L5.0 Root/ROM/Recovery/Kernel

Hello all, I am relatively new to the android rooting scene. I have looked into it before but always became discouraged by the amount of different informaton from different sources. I am a little bit familiar with flashing processes as I used to install CFW onto Sony PSP and PS3 devices. However there's a lot of new terms that I am soaking in and trying to figure out what it all means when it comes to phone rooting. I am currently using a Sprint Galaxy S5 Sport running Lollipop 5.0, with build number, "LRX21T.PVPU2BOH1" and Kernel "3.4.0-4445742 August 6, 2015". I've been looking around and every time I think I find a reliable source for rooting I see a disclaimer saying only works with certain build numbers, and mine doesn't seem to be any of the builds I have seen. A Google search of my build brings a total of 5 searches wit no information regarding it. Anyways I am looking to successfully root my device, install a working recovery mode, and if possible, install a ROM. I have searched through threads and scrounge up some information about the SM-G860P but not enough for me to go through with the process with 100% certainty of success. I also hope that this thread can be useful to other SM-G860P users and a one stop shop for all the files needed to safely root, backup, and restore files. Basically, I know it can be rooted using Odin and CFAR on Lollipop 5.0. But the steps after that I am unsure. Do I install TWRP, CRM, what ROMS can I install, what kernel do I need. Thanks in advance to any developers or members who can provide all the proper links to attain my goal.

I have a very similar build. I have successfully put on root, and CWM recovery, but, any attempts at custom roms have failed (assuming due to kernel), and I am unable to get tethering working, despite having root.
Followed http://forum.xda-developers.com/sprint-galaxy-s5/development/recovery-cwm-s5-sport-sm-g680p-t2907945 for recovery.
I rooted following something like: http://www.android.gs/root-sprint-galaxy-s5-on-android-5-0-lollipop-os/. The key was using the auto root, then flashing the update via CWM. Had to make sure CWM was installed, as flashing using stock recovery caused issues.
Tried to flash CM12 from:
http://forum.xda-developers.com/sprint-galaxy-s5/development/rom-adulterated-cm12-5-0-2-t2987665
But ended up in a boot loop.
I'm also scared to put xposed framework on, since most saying need to use a custom rom or else phone will bootloop.
Using most of the methods to tether, (like adb settings global or sqlite), tether_dun_required keeps resetting back to 1 after turning on tethering, so, I still haven't found a solution to that. I'd love to hear from anyone who's got tethering working on SM-G860P with lollipop.

Nexus 5, Marshmallow 6.0 MRA58N - OTA notification

Hi Guys
After one of the custom 5.1 roms crashed and left me without the phone, I have decided that I will go live with Marshmallow.
I have installed the original stock 6.0 MRA58K which after booting quickly went into MRA58N with OTA update.
Once I have realised how many things I am missing in my phone, due to using the stock ROM, I was looking for a perfect solution and decided that I will no longer be flashing custom ROMs, but use XPOSED as a framework with additional modules.
I have installed the elementalx kernel and added the correct XPOSED framework.
Everything was working fine until yesterday, where I have received notification about OTA update to 6.0.1.
First I thought that I don't really care about emojis, however I do like the option of "Do not disturb until next alarm".
I know that I can achieved by some additional modules to the xposed, however the OTA update is quite annoying.
Because I was on TWRP as a recovery, I have also installed the BusyBox and SimpleRecoverySwitch hoping that this will resolve the issue. Quickly reflashed stock recovery (don't know why, but every time when I was using fastboot to flash recovery with stock recovery.img, TWRP was still there) and found that I still can't use OTA update to 6.0.1. due to error:
"app_process 32 has unexpected contents".
After googling I have found that this is because I have xposed up and running.
Googled than for "unistalling" xposed and found plenty of topics, however none of them have provided me clear answers, especially to the question of "how to uninstall xposed". I have not found any original.img, so I suppose xposed installer have not created any backup, also when I will open xposed Installer - options to "uninstall xposed" are greyed out.
So my question would be - how can I easily remove xposed (temporary) without loosing data/restarting fully the phone, because after 5 days of flashing/reflashing/factory resets I am slowly tired from setting up personal configuration on my phone (even when on Marshmallow is much more easier than on lollipop 5.1).
If this is not possible, how I could remove OTA update from not only notifying me all the time, but also not restarting the phone (wakelock?)

Once you root the phone, you will not be able to upgrade via OTA. Your choices are to follow the instructions on this thread or to completely go back to stock without root and do the OTA.

Stuck in Bootloop and cant get back to stock firmware.

Hey guys, first time on this forum because I've run out of options otherwise. So last night i decided to finally root my phone after reading about it a lot. The root it self went just fine and it was working great. I then tried to download xposed using TWRP. However, that put my phone into a bootloop. It keeps restarted after it comes to the Samsung logo. I did some research and people said to simple put it back to the stock firmware so i downloaded some ( had trouble downloading because sammobile wouldn't work for me) However, now every time I try to flash it back to the stock firmware using odin it says failed and comes up with an error on the phone saying SW REV CHECK FAIL DEVICE 3, BINARY 1. The phone is a SM-G920W8. Any suggestions cause right now I have a $700 paper weight and no back up phone. I'm kinda freaking out haha.
Thanks for the help. I can send screen shots if you guys need them.

same problem.is there a way to install xposed framework without these annoying problems?
how to install the custom recovery and xposed properly?

Yeah, use the correct Xposed for S6.
There's an uninstall tool for the Xposed you've already installed (look in OP for Xposed you installed), that should have been your first step after bootloop. Try now, see if it will uninstall.
There's a Windows tool called SamFirm, or an Android app + website called Updato, use those to download stock ROMs if you still need to.
Then search for Wanam Xposed s6, and use that version.
Sent from my SM-G920W8 using Tapatalk