Related
I noticed that the pro version of SuperSu has a survival mode option. Should I have this enabled all the time? or should it only be enabled when I am ready to make a OTA update?
Just leave it where it is. I'm not even sure if it'll work with an ota. The nexus 5 is so easy to root that I've never tried it. It had been helpful on some other devices butt it's not needed with the n5
gee2012 makes a good point for cm roms of you want to maintain supersu
Edit out of curiosity I did enable survival mode on 4.4. It does survive update to 4.4.2
Sanvido said:
I noticed that the pro version of SuperSu has a survival mode option. Should I have this enabled all the time? or should it only be enabled when I am ready to make a OTA update?
Click to expand...
Click to collapse
You can turn it on all the time, also when you flash CM superSU will remain the main superuser app.
You leave it on all the time as I assume it has scripts to reinstall SuperSU if certain files are removed. It currently works fine for me with OmniROM OTA updates.
Thanks guys for the answer.
Charlular said:
You leave it on all the time as I assume it has scripts to reinstall SuperSU if certain files are removed. It currently works fine for me with OmniROM OTA updates.
Click to expand...
Click to collapse
^^^
Well, of course you would keep root with OmniROM, since it is a rooted rom.
Why wouldn't it keep root when you're using a ROM that requires root to begin with?
Forgive me for being a compleat (sic) Nitwit... but I thought that Rootkeeper and Survival Mode in SU were supposed to keep root through an OTA update for the stock ROM, like going from 4.3 to 4.4 which I think is impossible because when I tap 'check for updates', the message comes up that (and I'm paraphrasing here'... can't be updated because your system has been modified.
When reading through all the caveats in OTARootkeeper in the Play Store, it seems to say that you can un-root temporarily in order to install a new ROM update, and then re-enable root.
Of course, then the Dev. goes on to say that OTARootkeeper won't work with SuperSU installed because OTARootkeeper has it's own version of SU built in.
Am I right or wrong... and if I'm wrong, I wish that somebody would explain it to me exactly where.
Am I correct in assuming that OTARootkeeper will allow temporarily un-rooting for the purpose of installing let's say, an update to the stock ROM which I happen to be running, and then re-rooting and still keep root status?
I've had OTARootkeeper installed for quite a while, but I read that it no longer works with 4.3 to 4.4 stock ROM updates anyway, so I guess my comments become moot.
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.
So I can successfully install superuser v2.40, but it's not working with one of my apps (puzzle and dragons). I have been told me to downgrade to 2.25, but I have been having issues.
The problem is no matter what, when I flash 2.25 it gets stuck in a bootloop. Flashing it on stock, and even flashing it over 2.40, and flashing it over 2.40 when clicking the replace button in the superuser app. What am I doing wrong? Is 2.25 not compatible with my phone?
Hi First of all, if you have any compatibility issues with apps try upgrading them rather than downgrading. In this case SuperSU v2.46 would be the current version. Anyways, I just googled a bit and that's not the problem at all.
The developers of the game implemented a function which doesn't let the app start on a rooted device. It will check if you have Superuser-rights and automatically close the game at the splash screen if so.
So actually what you need is something that "hides" your root. There are several methods. I heard about Xposed modules like RootCloak for example. I even read on the xda News page that it's Lollipop compatible
experience7 said:
Hi First of all, if you have any compatibility issues with apps try upgrading them rather than downgrading. In this case SuperSU v2.46 would be the current version. Anyways, I just googled a bit and that's not the problem at all.
The developers of the game implemented a function which doesn't let the app start on a rooted device. It will check if you have Superuser-rights and automatically close the game at the splash screen if so.
So actually what you need is something that "hides" your root. There are several methods. I heard about Xposed modules like RootCloak for example. I even read on the xda News page that it's Lollipop compatible
Click to expand...
Click to collapse
Thanks for the reply. On the game's forums, I have been told that masking does not work (if you look at xposed rootcloak it says it's not compatible). And some users have been able to get the game to work with certain versions. I am on the latest binaries and it still doesn't work. The only way to get it to work is to unsinstall SuperSU and reflash it every time I want to play.
On some forums I've read that SuperSU has got a function to "hide" or "temporarily disable" it... Take a look at the app. Hopefully this feature hasn't been removed and maybe that's enough for you to get the game working. It's not a perfect solution but at least you don't have to uninstall / reflash every time. Let me know if it worked
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.
When Android 7.0 ( Nougat ) is finally released for Motorola X Pure (2015) XT1575 ( Hopefully by the end of the year ), will SystemLess Root still work as is it does now for 6.0 or should we wait for someone to run it in a sandbox? Should we wait for the First Quarter of 2017 before we get anxious and upgrade to the newest Android, to give all of the developer time to perfect they're processes.
We all know now that it will be released as a STOCK image, but I have a lot of Root Apps (i.e. Titainium, Backup, Root Explorer, Xposed, Gravity Box for MM, etc) which I would still like to use. From what I can see of 7.0 it's not much different than 6.0 except for split screen and some other features that I'm sure we.re not aware of yet..
All I can say it It doesn't work on the G4... yet. I maintain a root thread on the G4, haven't found a viable way to root it on Nougat, all methods mess up data and a bunch of framework stuff (like settings menu). I assume the Nougat on this will be roughly the same. Don't worry, it will come though.
And Xposed isn't available for Nougat, it isn't known yet if it will be. Remember when Marshmallow came out they almost dropped Xposed completely, they were so close they had actually said they shutting down development of Xposed then had a unexpected breakthrough. The developers of Xposed have said that it will die in the hear future due to changes in Android.
Yeah, xPosed isn't something I would rely on moving forward. Right now AICP & CM are making great strides with N 7.1 and including Root so you can go that route and get the Root you desire. I'm on TurboROM which is still an MM base and will move to AICP N 7.1 once things settle in some more, but as of right now AICP is pretty darn nice as is. I've tested it every few days to see the progress, but for daily, revert to my most current backup of Turbo for now. AICP usually includes a LARGE amount of customizations. I go that route normally and remove all the AOSP stuff I can replace with Google APPs directly and use Moto Camera instead as well giving me a really clean and functional bug-free experience. GravityBox becomes mostly unnecessary with AICP or CM. Boy I'm rambling worse than normal today...
Back on track... Try out AICP with N 7.1 or wait for a Stock Rooted
Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!
CLETjB said:
Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!
Click to expand...
Click to collapse
Pixel bootloader is unlockable. Verizon Pixel has bootloader unlock tool from the Sunshine team free of charge. Also It is rootable via newest SuperSU beta I believe.
I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.
roadrun777 said:
I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.
Click to expand...
Click to collapse
Yes, lots of people have rooted it... latest TWRP and Magisk, nothing special to do at all... Flash or boot TWRP and flash Magisk zip file, reboot and go.
Unlocked bootloader must have.
1st method:
Boot twrp - fastboot boot twrp3x.img
Do full backup,
Restore boot only,
In twrp install magisk14.zip, optionally wipe cache+dalvik, reboot.
2nd method
...the same steps,
Twrp terminal - type + ok:
echo SYSTEMLESS=true>>/data/.supersu
Install SuperSu2.82.zip, opt.wipe..., reboot.
Both method works.
I finally find magisk and it worked first time for me.
I tried SuperSU about 10 times in a row, systemless false, systemless true, etc, without it, and it always ended the same way boot loops.
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.
roadrun777 said:
...
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.
Click to expand...
Click to collapse
I wrote here(#8):
1st December 2017, 02:11 PM,
Here:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
30. November, 2017...rooted 29.
SuSu 2.82 is compatible.
Magisk Framework comes with SuperUser built in.. so when you flash another superuser, you mixing Binaries and it doesn't know which one to use.