Related
Hi friends,
had some queries regarding when to do the root+CWM and if it will conflict with new updates from samsung.
1. is it best to root as soon as i buy a fresh phone? or should i apply all the updates (if any) and then proceed for the root.
2. should i do a clean format before root. will it conflict with any install of apps. should i install apps after root?
3. what about future updates? will i be able to continue receiving new updates?
4. what is the specific files required to unroot and go back to stock? where can i find my stock zimage. any other files and apps required please inform. I'm using Indian version.
i went through http://forum.xda-developers.com/showthread.php?t=1424997
this dr.ketans stock roms list but im not very clear about it.
thanks a lot
anjath said:
Hi friends,
had some queries regarding when to do the root+CWM and if it will conflict with new updates from samsung.
1. is it best to root as soon as i buy a fresh phone? or should i apply all the updates (if any) and then proceed for the root.
2. should i do a clean format before root. will it conflict with any install of apps. should i install apps after root?
3. what about future updates? will i be able to continue receiving new updates?
4. what is the specific files required to unroot and go back to stock? where can i find my stock zimage. any other files and apps required please inform. I'm using Indian version.
i went through http://forum.xda-developers.com/showthread.php?t=1424997
this dr.ketans stock roms list but im not very clear about it.
thanks a lot
Click to expand...
Click to collapse
1. Better to update to new firmware then to root (Update only to Rootable FW)
2. No need to clean format before root.
3. After rooting you wont receive any updates from Samsung.
4. Stock ROM and odlin, KL3 is the last update found in India and its rootable
3. so we'll have to unroot, update to new version and then try to root again?
After unroot u need to factory reset to get updates i guess.
anjath said:
Hi friends,
had some queries regarding when to do the root+CWM and if it will conflict with new updates from samsung.
1. is it best to root as soon as i buy a fresh phone? or should i apply all the updates (if any) and then proceed for the root.
2. should i do a clean format before root. will it conflict with any install of apps. should i install apps after root?
3. what about future updates? will i be able to continue receiving new updates?
4. what is the specific files required to unroot and go back to stock? where can i find my stock zimage. any other files and apps required please inform. I'm using Indian version.
i went through http://forum.xda-developers.com/showthread.php?t=1424997
this dr.ketans stock roms list but im not very clear about it.
thanks a lot
Click to expand...
Click to collapse
1. I dont see any reason to w8, I have rooted in half n hr of my purchase. I wrote the post how to Root before my purchased (Available in India quite later). But it is your nice question regarding pre or post update, First you updates if any available so you may not need to Re-Root. Just keep in mind If your updates is KL7/KL8, then you have to Root it first.
2. It is always better to Root in clean condition(as soon update ROM), though there is no Rule.
3. No and Yes, No incase you want updates from Kies
Yes in case you can Flash any ROM with Odin
4. You are Indian then I can confirm few more thing, Your last update is KL1
purchased state you may have KK1, just update over OTA, now you will have KL1
Now Root. Dont worry regarding Stock Kernel, Just send Me PM whenever you may need Indian Kernel
To Root , use link in my signature.
dr.ketan said:
1. I dont see any reason to w8, I have rooted in half n hr of my purchase. I wrote the post how to Root before my purchased (Available in India quite later). But it is your nice question regarding pre or post update, First you updates if any available so you may not need to Re-Root. Just keep in mind If your updates is KL7/KL8, then you have to Root it first.
2. It is always better to Root in clean condition(as soon update ROM), though there is no Rule.
3. No and Yes, No incase you want updates from Kies
Yes in case you can Flash any ROM with Odin
4. You are Indian then I can confirm few more thing, Your last update is KL1
purchased state you may have KK1, just update over OTA, now you will have KL1
Now Root. Dont worry regarding Stock Kernel, Just send Me PM whenever you may need Indian Kernel
To Root , use link in my signature.
Click to expand...
Click to collapse
thanks a lot for the clarification. I'll definitely message you when i need the Indian kernel.
for 3. while my phone is rooted i received KKA update from kies.
Hej guys,
recently i got an OTA Push for a new firmwareversion.
I denied, because my system is stock, but rooted and with cwm and framework...
1. Does anyone have any information, about the changelog for this update?
http://www.sammobile.com/firmwares/download/40580/I9295XXUCNK4_I9295NEECNL1_NEE.zip/
2. How can i disable the OTA Message? I can just throw it back for max 3 hours..
3. I presume, that if I would install this stock-rom from sammobile via ODIN, I would loose root and CWM?
What do you guys think of these small (?) updates? Do you use them?
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 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).
I rooted my phone with Magisk using the Magisk image patching method so now my phone is everything stock + magisk root (no custom kernel or recovery) and a few root applications/modules such as Vanced, ViperFX and adAway.
Oddly enough, I have received a push notification from Samsung about the availability of the Android 11 update. But I don't feel safe to OTA update my phone because of root. So is there any way I can update it without losing any data and without losing root?
Thanks in advance!
Yes, I am looking for that also.
Any one?????
First, you never should update when you are rooted. It may soft-brick your device. And also, if you are looking to root after OTA update, the best thing you can do is downloading the stock firmware and flashing it through ODIN. Then, you can patch Magisk. I don't know if you will lose data, but I recommend you to backup your files.