Related
Hi,
So i have a Moto G 2 XT-1068 with Android 5.0.2 and system version 22.21.28.titan_retaildsds.retaildsdsall.ex.03 reteu.
I rooted it and installed Xposed.
Since some days, my phone notify me that there is a new (official) update avalaible :
22.56.3.en.03
My first reflex was to post in the Xposed forum :
I have a Motorola Moto G 2nd edition (2014 XT-1068) with Android 5.0.2 and these xposed versions installed :
XposedInstaller_3.0_alpha4.apk
xposed-v75-sdk21-arm-1
This morning, my phone notify me that there is a newsoftware update available :
22.56.3.en.03
Can i update ?
Will Xposed still running or do i have anything to do before or after update ?
Click to expand...
Click to collapse
then :
Yes i'm rooted (i didn't know i could install exposed without root ?!) and i ask the question to rooted users : what is the recommended behavior to have when we are rooted and there is an official update like this one ? Should i ignore it ? Should i wait ? Should i update (with one of your solutions) ?
Click to expand...
Click to collapse
and this is the reply i had :
You'll have to ask how an OTA works for that in your device forum.
For Google Android (untouched by OEM) in Kitkat, OTA used to check each important file individually and if one was modified, OTA would fail. This did not check all existing files or added files such as root, so as long as you uninstalled Xposed properly (restoring the original app_process files etc) then an OTA would be fine.
Since Lollipop, OTA checks the /system partition as a single item so any modification in any file, or any additional file will make the OTA fail. In which case, the only way to update would be to flash a stock ROM.
You will need to find out in your device forum which of these applies to your device.
Click to expand...
Click to collapse
So this is it, i make a post in this Moto G 2014 forum
Doing the OTA will most likely delete the XposedBridge.jar so you will have to flash it again.
Else the Xposed app will still be available but the Framework won't be installed.
If it doesn't update because the /system partition has been modified, you'll have to flash the whole rom to update.
Ok, so i can try without risk ?
And what about my root ?
nonobio said:
Ok, so i can try without risk ?
And what about my root ?
Click to expand...
Click to collapse
Root will be gone too. You'll have to root it again by flashing SuperSu Zip though a custom recovery. (TWRP)
Restore the nandroid backup of the stock system you made in TWRP before you rooted.
You also need the stock recovery for the OTA to install.
You made a backup of your system before you rooted, right?
Hi
TheKill69 said:
Root will be gone too. You'll have to root it again by flashing SuperSu Zip though a custom recovery. (TWRP)
Click to expand...
Click to collapse
Ok.
Seriously said:
Restore the nandroid backup of the stock system you made in TWRP before you rooted.
You also need the stock recovery for the OTA to install.
You made a backup of your system before you rooted, right?
Click to expand...
Click to collapse
I'm note sure i made a backup before i rooted cause i'm note sure i knew i could install recovery without root but i checked my backup plan and my oldest backup is post root
So, what do you recommand when there is OTA like this ? Should i ignore them ?
It seems to be a hard process (flash stock recovery and root again and not sure if it will be possible anyway, is it ?) for maybe a little update ?
Maybe i should wait for the next big OTA like Android 6, then be sure that a new rooting process exist before update, and also be sure that Xposed will be supported ?
So if i ignore this 22.56.3.en.03, will i be notifyed for others newer OTA (like Android 6 for instance) ?
Thanks
nonobio said:
Hi
Ok.
I'm note sure i made a backup before i rooted cause i'm note sure i knew i could install recovery without root but i checked my backup plan and my oldest backup is post root
So, what do you recommand when there is OTA like this ? Should i ignore them ?
It seems to be a hard process (flash stock recovery and root again and not sure if it will be possible anyway, is it ?) for maybe a little update ?
Maybe i should wait for the next big OTA like Android 6, then be sure that a new rooting process exist before update, and also be sure that Xposed will be supported ?
So if i ignore this 22.56.3.en.03, will i be notifyed for others newer OTA (like Android 6 for instance) ?
Thanks
Click to expand...
Click to collapse
You might have to flash the whole stock firmware back to get the stock recovery. Big waste of time.
Then rooting back means using CF Auto Root Commands again..
You have to update to it though if you want Android 6.0.
Since it won't be soon, you rather go for CM13 once it gets really stable.
Also by the way, Xposed is already supported on MM.
Thanks for these precisions.
So if i can resume : a custom rom is easier for enjoy Android updates than just Xposed.
Hi,
Can you confirm :
For someone searching advanced features like customize status bar, quick settings, shutdown menu, hardware buttons, etc : customs roms and "stock rom + exposed" are two solutions. BUT, for someone searching these same advanced features but also keep his device up to date : custom rom is really a better solution. Isn't?
I was happy when i discovered xposed as it seemed to be a easier process that flashing a custom rom, but i didn't know that i couldn't update easily..
So, what is the advantage to use xposed instead of custom rom?
Hi,
I am always thinking if i will update my stock rooted xposed rom, or if i will install a custom rom prerooted like Cyanogen mod (o have easier future updates).
i have some questions :
1- Is it possible to install xposed and modules on a custom rom like cyanogen mod ? I think yes but can you confirm ?
I know that CM come with inbuilt tweaks but i discover some great xposed module i would continue to use, even if i install CM.
2-If i keep my stock rooted xposed rom, and don't make this "little" Android 5 OTA update, will be i notified for "Android 6" ?
(i don't want to lose my time to reflash my rom, reroot mydevice, etc.., just for a little update, but i could do that for a more important update like Android 6...
3- We are agree that if i flash a custom rom like CM, it will resolve my "ota update" problem, cause there won't be "Motorola OTA" anymore, but there will be CM updates easy to make, isn't ? If yes, what could be the advantage to use stock rom rooted + xposed vs custom rom + xposed ?
Thanks
Hello. Please be gentle. I'm new to Systemless Root and need some clarification. I've done a lot of reading about it but still need some info. Im not bashing anything or anyone, I'm not trying to be a wise ass, I'm genuinely confused. From the vague installation process I read somewhere it seems that u already need to be Rooted with TWRP installed to install Systemless Root. Right? So what's the point of rerooting a phone thats already rooted? I would think it would be more useful to have it as another root method. So we can start off Locked and Unrooted, then use Systemless to root. Currently my N6 is locked and Unrooted because I have no use for Root at the moment yet all of my previous Android phones have been unlocked and rooted. Please explain to me what I'm missing here. Thanks guys. Happy New Year to u.
TokedUp said:
Hello. Please be gentle. I'm new to Systemless Root and need some clarification. I've done a lot of reading about it but still need some info. Im not bashing anything or anyone, I'm not trying to be a wise ass, I'm genuinely confused. From the vague installation process I read somewhere it seems that u already need to be Rooted with TWRP installed to install Systemless Root. Right? So what's the point of rerooting a phone thats already rooted? I would think it would be more useful to have it as another root method. So we can start off Locked and Unrooted, then use Systemless to root. Currently my N6 is locked and Unrooted because I have no use for Root at the moment yet all of my previous Android phones have been unlocked and rooted. Please explain to me what I'm missing here. Thanks guys. Happy New Year to u.
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 and this http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 for starters. BTW Google is your friend and you can`t be rooted to use systemless root and obtain root.
I'm probably a lot less experienced than gee2012 and many others in the forum, but here's my very high-level understanding. I hope that the more knowledgeable members can add to or correct this as necessary.
First, you need to unlock the device (fastboot oem unlock), since you can't do much with a locked device. Not only that, but time and time again I've read pleas from users saying "My device is bricked and I didn't unlock it so I can't now enable developer options" - the responses have been generally "Sorry, you're stuffed then, send it back". Unlocking wipes the device, so make backups of whatever essential data you have.
You don't need to install TWRP permanently in order to root. I myself (after asking members for advice) temporarily booted into TWRP (fastboot boot twrp.img - when you reboot from TWRP it disappears and you're back to stock recovery). While TWRP is temporarily running, you can use it to install SuperSU.
The benefit of the new SuperSU (and also doitright's systemless root method) is that it maintains a stock system image, so in theory you have the benefits of superuser root but you can still get OTA updates, which are now much more frequent because of the security amendments. Chainfire (the SuperSU creator) says that he was able to install an OTA after having used the SuperSU unroot function, though he then had to re-root.
Hope this helps - and that it's correct...
dahawthorne said:
I'm probably a lot less experienced than gee2012 and many others in the forum, but here's my very high-level understanding. I hope that the more knowledgeable members can add to or correct this as necessary.
First, you need to unlock the device (fastboot oem unlock), since you can't do much with a locked device. Not only that, but time and time again I've read pleas from users saying "My device is bricked and I didn't unlock it so I can't now enable developer options" - the responses have been generally "Sorry, you're stuffed then, send it back". Unlocking wipes the device, so make backups of whatever essential data you have.
You don't need to install TWRP permanently in order to root. I myself (after asking members for advice) temporarily booted into TWRP (fastboot boot twrp.img - when you reboot from TWRP it disappears and you're back to stock recovery). While TWRP is temporarily running, you can use it to install SuperSU.
The benefit of the new SuperSU (and also doitright's systemless root method) is that it maintains a stock system image, so in theory you have the benefits of superuser root but you can still get OTA updates, which are now much more frequent because of the security amendments. Chainfire (the SuperSU creator) says that he was able to install an OTA after having used the SuperSU unroot function, though he then had to re-root.
Hope this helps - and that it's correct...
Click to expand...
Click to collapse
Thanks man. That makes certain things more understandable. The thing I still don't understand is the actual install process. I'm am stock, so ur saying I would just have to unlock BL then temp flash TWRP to flash the SU zip? If not what are the exact steps for installing?
BTW I'm on 6.0.1 MMB29K
TokedUp said:
Thanks man. That makes certain things more understandable. The thing I still don't understand is the actual install process. I'm am stock, so ur saying I would just have to unlock BL then temp flash TWRP to flash the SU zip? If not what are the exact steps for installing?
BTW I'm on 6.0.1 MMB29K
Click to expand...
Click to collapse
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.
gee2012 said:
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.
Click to expand...
Click to collapse
I don't want to be that guy but USB debugging is not needed to unlock the BL,it is only needed while in Android os
holeindalip said:
I don't want to be that guy but USB debugging is not needed to unlock the BL,it is only needed while in Android os
Click to expand...
Click to collapse
True, but i always enable it by default
gee2012 said:
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.
Click to expand...
Click to collapse
Thank you so much!
TokedUp said:
Thank you so much!
Click to expand...
Click to collapse
Tip: instead of flashing TWRP you can also boot it up ( fastboot boot nametwrp.img) to flash zip files and keep your stock recovery if you want to.
@gee2012 - "Install BusyBox from Play and you`re done"
I still don't get what exactly Busybox offers. I've been running fine on Marshmallow for several months without it. I installed it once because it was suggested as a fix for the constant nagging of AutomateIt Pro to reboot, and it made no difference, so I uninstalled it again.
Can you (or anyone) give me specific examples if where it actually makes a difference? Which functions won't work without it? I haven't come across any yet as far as I know.
Busybox is the space efficient way of the basic Unix commands like ln, pwd, chown, chmod, etc. So all apps that want to do some low level file system dabbling, like Android terminal, Titanium backup, or Linux installs, they need it. https://en.wikipedia.org/wiki/BusyBox
From Marshmallow, Android now uses toybox instead by default, which is quite the same, with a little different licensing. It's also in the AOSP source, so all user built AOSP roms already have toybox, so there's no need for busybox to install.
dahawthorne said:
@gee2012 - "Install BusyBox from Play and you`re done"
I still don't get what exactly Busybox offers. I've been running fine on Marshmallow for several months without it. I installed it once because it was suggested as a fix for the constant nagging of AutomateIt Pro to reboot, and it made no difference, so I uninstalled it again.
Can you (or anyone) give me specific examples if where it actually makes a difference? Which functions won't work without it? I haven't come across any yet as far as I know.
Click to expand...
Click to collapse
Apps like Rom Toolbox Pro, Franco Kernel Updater and Kernel Adiutor and lots of other application like Xposed framework (and its modules) and most (if not all) of the custom roms will not work (correctly) without BusyBox. All custom roms anyway have a BusyBox version by default installed Busybox https://en.wikipedia.org/wiki/BusyBox and https://www.google.nl/url?sa=t&rct=...6Z0ltw&usg=AFQjCNG-nKYoEI3kiDm4pgtRWbXFRTpI6A for instance.
Its an essential app for when you are rooted and want to do more with your phone and its not smart to not install it
Thanks, both. I like istperson's comment best : "there's no need for busybox to install." That would be why I haven't seen any negative impact from not having Busybox then. Still, money well spent to help development...
Hello all,
so I have a op3t with SuperSU. I was wondering when the android P update comes out eventually will I be able to OTA update and keep root, or will I have to reflash SuperSU(Using temp TWRP environment).
bradcubed said:
Hello all,
so I have a op3t with SuperSU. I was wondering when the android P update comes out eventually will I be able to OTA update and keep root, or will I have to reflash SuperSU(Using temp TWRP environment).
Click to expand...
Click to collapse
You will definitely have to reflash SuperSU.
Sent from my OnePlus 3T
BillGoss said:
You will definitely have to reflash SuperSU.
Click to expand...
Click to collapse
What he said. That goes for most updates of most Android devices (need to root again after an update).
Further, a new Android build (particularly a major update, like Oreo to P) will often require updated root methods. Since SuperSU development is basically dead, it may not work on Android P. You may need to move to Magisk root method (not a bad thing).
Best way to apply updates on rooted 3T, is to get it from the following thread and basically follow the install instruction for root users on Post #3 of that same thread:
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
I would also advise to backup your data before updating, as a clean install (wipe data) is not unheard of (possibly even recommended), when installing major updates.
Note that failure to flash Magisk/SuperSU after applying the update, will not only cause you to lose root, but also lose TWRP (will be overwritten by stock recovery if you reboot before flashing a root file or alternately a modified kernel).
Hi,
I am all new to Xiaomi (so a big noob into this).
I would like to flash the TWRP and to root the phone.
So here are my questions:
1.After that, will my phone received the OTA updates?
2.Or is better to take the rom from the xiaomi.eu and install them?
3.But with this, will I lose all the settings/application from the phone?
Thank you in advance for the answers.
A little up for my question :angel:
ozzii said:
Hi,
I am all new to Xiaomi (so a big noob into this).
I would like to flash the TWRP and to root the phone.
So here are my questions:
1.After that, will my phone received the OTA updates?
2.Or is better to take the rom from the xiaomi.eu and install them?
3.But with this, will I lose all the settings/application from the phone?
Thank you in advance for the answers.
Click to expand...
Click to collapse
If you unlock you receive ota updates, but if you install twrp and magisk root you can't have ota. You should use a patched boot image maybe.
It is better you install xiaomi eu rom, it updates via ota with twrp also installed.
If you pass to xiaomi eu you have to format data, so you lose your apps and settings just first time
Thank you @HTCDevil for the explanation.
So sad that the root can't be kept.
So I will install twrp and the eu rom. With this I have 2 on the 3 things.
The phone is new so no data yet.....
Thank you again.
ozzii said:
Thank you @HTCDevil for the explanation.
So sad that the root can't be kept.
So I will install twrp and the eu rom. With this I have 2 on the 3 things.
The phone is new so no data yet.....
Thank you again.
Click to expand...
Click to collapse
You can root after installing xiaomi eu.
HTCDevil said:
You can root after installing xiaomi eu.
Click to expand...
Click to collapse
Yes you are right, but I will need to do this on every update, right?
If I understand correct I will need to do if rooted:
-manual update of the rom
-new root of the new rom
Also, will I lose all the settings after an update of the xiami eu image?
ozzii said:
Yes you are right, but I will need to do this on every update, right?
If I understand correct I will need to do if rooted:
-manual update of the rom
-new root of the new rom
Also, will I lose all the settings after an update of the xiami eu image?
Click to expand...
Click to collapse
Xiaomi eu has ota update, it flashes rom in twrp and wipe dalvik / cache automatically, so you don't lose data or settings. If you lose magisk you simply reinstall in twrp, related app and settings stay there
Thank you again @HTCDevil for your help.
Now I am ready for working with my MI9.
Hi!
I know this looks like a very basic questions. But I'd rather ask first rather than having regrets later on.
This is my current situation:
1. I have TWRP recovery installed.
2. I have unlocked bootloader.
3. I have root.
4. I have installed Custom ROM (crdroid (Android 10).
My objective(s) with questions:
a. Am I able to unroot but retain the crdroid ROM?
b. If I cannot retain it, what are the steps to:
- unroot
- back to stock recovery
- installing stock rom
Any helps, tips and pointers are very much welcome and I appreciate it in advance.
Thank you!
ompocong said:
Hi!
I know this looks like a very basic questions. But I'd rather ask first rather than having regrets later on.
This is my current situation:
1. I have TWRP recovery installed.
2. I have unlocked bootloader.
3. I have root.
4. I have installed Custom ROM (crdroid (Android 10).
My objective(s) with questions:
a. Am I able to unroot but retain the crdroid ROM?
b. If I cannot retain it, what are the steps to:
- unroot
- back to stock recovery
- installing stock rom
Any helps, tips and pointers are very much welcome and I appreciate it in advance.
Thank you!
Click to expand...
Click to collapse
Magisk application should have an uninstall option that reverts your device back to what it was before rooting, all your root modules will be lost obviously. You should be able to retain your rom and not require a clean install, since when I unrooted my pixel experience rom (android 13) I could retain all my device data, though you might still want to back up stuff you don't wanna lose.
thelakeman said:
Magisk application should have an uninstall option that reverts your device back to what it was before rooting, all your root modules will be lost obviously. You should be able to retain your rom and not require a clean install, since when I unrooted my pixel experience rom (android 13) I could retain all my device data, though you might still want to back up stuff you don't wanna lose.
Click to expand...
Click to collapse
Hey, thank you for the reply.
At least I wasn't the only one with these kind of doubts. Will do for the backup, since there's no harm doing it.
Thanks again!
Cheers!