After a system update a few months ago the google app on system got upgraded to the new version that got rid of the "swipe to dismiss" cards feature that I really like.
In the past I just disabled store updates to stay on that version, but that doesn't work any more.
I'v got an old apk from apkmirror, but when I try to install it, it just says "app not installed".
This method using ADB doesn't work either (aparrently apps installed this way have to be debuggable now?)
https://www.xda-developers.com/downgrade-an-app-android-no-root/
Is there a way to do it without root? Alternatively is it possible to run the older apk alongside the newer, system apk?
No and it depents.
From withing your recovery yes. But I asume you are fully stock with locked bootloader and default recovery.
reef2009 said:
No and it depents.
From withing your recovery yes. But I asume you are fully stock with locked bootloader and default recovery.
Click to expand...
Click to collapse
Yeah stock recovery and bootloader locked.
I've tried patching APKs and everything.
Related
Hi, I rooted my phone to install the hebrew fonts and it works great.
The phone is factory unlocked, I rooted it as I said and set up recovery. I am pretty sure I saw something about super user while doing that but not sure.
So when I try to install the n1 torch or other mods via the market after installing them I just get a black screen when running them saying it is accesing SU and then it crashes.
Do I need to do anything else or is it possible that there are different ways/versions of rooting the phone?
If I do need to something to update the SU will it delete all my current settings and apps? When I rooted the phone I lost all my installations and settings.
Also, can I safely install any OS updates now that the phone is rooted?
Thanks!
You need to to enable root access to use apps link N1 torch... aka. super user or su... to do this, either flash a cyanogen, enomther or madcao ROM or flash modaco's superboot boot image...
If you want to keep everything as is and just enable su, use the superboot boot image... you won't loose any setting or apps...
As long as you have the stock ROM, you can install all OTA updates even if the phone is rooted... else, if you installed a cooked ROM, you might have to wait for the cook to include that in his ROM (Of course, this is generally earlier than OTA updates)...
Thanks for the reply but I think I already did that while rooting the phone I double clicked on 'install-superboot-windows.bat' while in recovery mode.
Is that what you mean or am I missing something?
Also ,what do you mean by the stock ROM?
Thanks!
Hi Guys,
My company uses Good For Enterprise for email, which requires a phone to not be rooted. Well I was using Xposed and Rootcloak to hide root, but it appears an update patched that exploit. So I flashed the SBF for 4.4.2 and have Good running. Well I wanted to be able to use TWRP to go back to my rooted backups, but once I push TWRP to my device, my STOCK unrooted fresh SBF'ed received a "SuperSU Installer" in my apps and also a persistent notification wanting me to install SuperSU through Google Play or TWRP. Good then failed the Root check and locked me out. So I thought I could push the stock recovery back and it would go away, but nope, no dice. Any ideas? FWIW I'm running a DE Moto X from Verizon, unlocked bootloader on 4.4.2 system and bootloader.
dkoon1987 said:
Hi Guys,
My company uses Good For Enterprise for email, which requires a phone to not be rooted. Well I was using Xposed and Rootcloak to hide root, but it appears an update patched that exploit. So I flashed the SBF for 4.4.2 and have Good running. Well I wanted to be able to use TWRP to go back to my rooted backups, but once I push TWRP to my device, my STOCK unrooted fresh SBF'ed received a "SuperSU Installer" in my apps and also a persistent notification wanting me to install SuperSU through Google Play or TWRP. Good then failed the Root check and locked me out. So I thought I could push the stock recovery back and it would go away, but nope, no dice. Any ideas? FWIW I'm running a DE Moto X from Verizon, unlocked bootloader on 4.4.2 system and bootloader.
Click to expand...
Click to collapse
Seems you did everything right BUT when TWRP ask if you wanna install root or superuser.. forget which it says. Just say no. Then you should be root free. Hope that helps!
drago10029 said:
Seems you did everything right BUT when TWRP ask if you wanna install root or superuser.. forget which it says. Just say no. Then you should be root free. Hope that helps!
Click to expand...
Click to collapse
Thanks, but when I was in TWRP recovery it did ask me to root, and I said no; but it still had the "SuperSU Installer" in the app drawer, and couldn't be removed.
dkoon1987 said:
Thanks, but when I was in TWRP recovery it did ask me to root, and I said no; but it still had the "SuperSU Installer" in the app drawer, and couldn't be removed.
Click to expand...
Click to collapse
hmm, well if you say you came from stock, flashed TWRP and SU installed itself. than maybe just removing root would work. There's a guide for that, probably in the general thread. also, I read that there is a way to load multiple ROMs that's stickied in one of the threads. That could be exactly what you need!!
Don't remember which thread so you have to find it.
Hello all. I have the VZW dev edition of the moto x with an unlocked bootloader. I am trying to update my Moto X to the latest OTA from 4.4.2 but am running into an issue.
I flashed stock recovery and downloaded the latest OTA. When flashing the OTA zip in stock recovery, the installation aborts due to a problem with vznavigator.apk. It says "/system/app/vznavigator.apk" has unexptected contents. Installation aborted.
I am guessing my vznavigator.apk is messed up for some reason. Does anyone have the stock version they can give me so I can try to get past this error? Any other tricks?
Thanks
You can always get it from the Google Play Store.
Or perform the OTA update manually.
I already tried getting from play store. Doesn't work. I don't think the play store version places vznavigator.apk in the system/apps folder.
Regarding updating manually, this is what I am doing... Flashing manually in recovery.
Sent from my Moto X
You could try using mfastboot to flash the system.img from 4.4.2 to fix any inconsistencies in system. Then try the update again.
On the phone... go App Drawer -> Settings -> Apps. Swipe to get to ALL. Scroll DOwn to VZ Navigator and tap it. Hit the button to uninstall updates.
Then try the OTA again.
KidJoe said:
On the phone... go App Drawer -> Settings -> Apps. Swipe to get to ALL. Scroll DOwn to VZ Navigator and tap it. Hit the button to uninstall updates.
Then try the OTA again.
Click to expand...
Click to collapse
I don't think disabled or non-updated apps matter. When I did my update I did reflash /system but all my apps stayed disabled when I was up and running on 4.4.4.
I also did updates on my Razr Maxx that was rooted and while I didn't flash /system, I did undo any changes I had made to it and took standard OTA without re-enabling apps that were disabled.
I'm guessing VZNav was removed or otherwise modified with a method that wasn't the stock disable option.
Flashing /system should work. I don't think installing from the Play Store will because it would be a user app, not a system app.
Just my thoughts.
Reflashing the system.img worked perfectly! Thanks guys!
fury683 said:
I don't think disabled or non-updated apps matter. When I did my update I did reflash /system but all my apps stayed disabled when I was up and running on 4.4.4.
I also did updates on my Razr Maxx that was rooted and while I didn't flash /system, I did undo any changes I had made to it and took standard OTA without re-enabling apps that were disabled.
I'm guessing VZNav was removed or otherwise modified with a method that wasn't the stock disable option.
Flashing /system should work. I don't think installing from the Play Store will because it would be a user app, not a system app.
Just my thoughts.
Click to expand...
Click to collapse
Disabled and non-updated doesn't matter.. UPDATED might. Hence why I suggested to uninstall the updates.
My thinking was that it is possible that Verizon had updated VZNav AFTER they approved the 4.4.4 update (so the update is looking for a checksum of an older version).
Yes, flashing system will always work. I just usually suggest the simple things first (I have a longer list on the pages in my signature), and with the amount of people that are flashing the WRONG system.img and other components (i.e. not paying attention and using the ROM for the carrier, model and version phone they have), and those who don't realize the difference between mfastboot and fastboot, I've been hesitant to suggest flashing system.img until other things have been tried.
So this morning I got this maintenance update and now I'm being told that an update is available and that this install is differed. When I click on "select to continue update" I'm told my system is up to date. I've already wiped cache, which did not help. Anyone else experiencing this?
KWKSLVR said:
So this morning I got this maintenance update and now I'm being told that an update is available and that this install is differed. When I click on "select to continue update" I'm told my system is up to date. I've already wiped cache, which did not help. Anyone else experiencing this?
Click to expand...
Click to collapse
Are you unlocked and rooted?
Nope, totally stock Verizon 4.4.4. I'm so far out of the loop, I didn't even know I could unlock and root in the first place.
Anyone have a fxz for this update? I have it too, but I am rooted with twrp.
Sent from my XT1060 using Tapatalk
T-Keith said:
Anyone have a fxz for this update? I have it too, but I am rooted with twrp.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
There does not appear to be an FXZ for this.
You can try flashing stock Recovery.img onto your phone and take it. Unlike other OTA's that failed due to Xposed, this one did not give me any issues installing with Xposed still enabled.
NOTE: I'm unlocked bootloader, rooted, running TWRP, with Xposed instaled (MotoXNetActivity module installed). I haven't made any other modifications. I only run apps that require root like AdFree, wifi tether for root, Root Explorer, etc.
KidJoe said:
There does not appear to be an FXZ for this.
You can try flashing stock Recovery.img onto your phone and take it. Unlike other OTA's that failed due to Xposed, this one did not give me any issues installing with Xposed still enabled.
NOTE: I'm unlocked bootloader, rooted, running TWRP, with Xposed instaled (MotoXNetActivity module installed). I haven't made any other modifications. I only run apps that require root like AdFree, wifi tether for root, Root Explorer, etc.
Click to expand...
Click to collapse
Thanks, I think this answered my questions in the other thread.
Is there a risk to try running the update with stock recovery and other Xposed modules like Gravity Box? Would they fail similarly to a failed system check like I've had in the past for removing/renaming system apps and such?
I just picked up a used T817T yesterday. I was able to root it with Kingroot. I then found out that I lose root after a reboot. Even worse, without enabling the developer options and enabling the OEM unlock, it would no longer boot. I had to reflash the stock ROM with ODIN to recover.
I purchased and installed SuperSu Me-Pro and that replaced the Kingroot SU with SuperSu. Now I can reboot without losing root.
I'm being prompted to install an update T817TUVS2APB1/T817TTMB2APB1/T817TUVS2APB1. If I install this update, will I lose root? If I install it, can I still root with other methods?
I still have the stock recovery.
I'm currently on T817TUVS2AOL1.
I decided to roll the dice and try the update. I got a message that the software on my device was altered in an unapproved way and that it would not update. At least the nagging icon on the top of the screen is now gone.
DonS said:
I decided to roll the dice and try the update. I got a message that the software on my device was altered in an unapproved way and that it would not update. At least the nagging icon on the top of the screen is now gone.
Click to expand...
Click to collapse
Install it with Flashfire.