Hi guys,
It it possible to get OTA with root and xposed? Should i uninstall xposed and unroot device?(how to unroot? uncheck Enable superuser?)
Nope
Flash stock
farid993 said:
Hi guys,
It it possible to get OTA with root and xposed? Should i uninstall xposed and unroot device?(how to unroot? uncheck Enable superuser?)
Click to expand...
Click to collapse
Hi
As long as you have the latest Systemless root and SU by Chainfire (being around for months) you did not modified the system files of your phone and unroot (from SuperSU) yes is possible
Some people said is possible also no unroot necessary if you just fake system status
MAX 404 said:
Hi
As long as you have the latest Systemless root and SU by Chainfire (being around for months) you did not modified the system files of your phone and unroot (from SuperSU) yes is possible
Some people said is possible also no unroot necessary if you just fake system status
Click to expand...
Click to collapse
Thank you. So just uninstall xposed and unroot(or not) and i`m good.
How about TWRP recovery? To install Xposed i should use TWRP to flash it(or could i use FlashFire only?)
Also should i defrost all system apps that i froze them?
farid993 said:
Thank you. So just uninstall xposed and unroot(or not) and i`m good.
How about TWRP recovery? To install Xposed i should use TWRP to flash it(or could i use FlashFire only?)
Also should i defrost all system apps that i froze them?
Click to expand...
Click to collapse
Hi
Option 1 Systemless root and systemless SuperSu ( Chainfire) no xposed (rovo89) , no system modification, no R/W systems, no TWRP , unroot from SuperSu , OTA possible
Option 1.1 use Flashfire guide here
Option 2 ( have not tested it) fake system status
In my experience trying to return Custom status to Official after rooting, even after removing root, is near impossible
That said, with this new systemless root, I haven't tried, but if you have altered any system files, which is generally what people use root for (Adblocking = Hosts file mod etc) then it won't return to Official unless you flash stock over the top again
Not seen this new status spoofer until now, be interested to see if that works
Thanks guys
So i guess with xposed it is impossible to get OTA, because to fake system status we need xposed but to get OTA we need to uninstall xposed.
Also *Detection* is right. We root our device to alter system.
So at the end we need download whole ~2gb firmware(flash, root, xposed, all other changing system thing again) for 20-30mb monthly security patch
farid993 said:
Thanks guys
So i guess with xposed it is impossible to get OTA, because to fake system status we need xposed but to get OTA we need to uninstall xposed.
Also *Detection* is right. We root our device to alter system.
So at the end we need download whole ~2gb firmware(flash, root, xposed, all other changing system thing again) for 20-30mb monthly security patch
Click to expand...
Click to collapse
Basically yep, unless you're not bothered about the security update and just wait for feature/performance updates
With my S5 I used to update every update, download the new ROM, flash with ODIN, TWRP > Root > Mod
Doesn't take too long tbh
*Detection* said:
In my experience trying to return Custom status to Official after rooting, even after removing root, is near impossible
That said, with this new systemless root, I haven't tried, but if you have altered any system files, which is generally what people use root for (Adblocking = Hosts file mod etc) then it won't return to Official unless you flash stock over the top again
Not seen this new status spoofer until now, be interested to see if that works
Click to expand...
Click to collapse
farid993 said:
Thanks guys
So i guess with xposed it is impossible to get OTA, because to fake system status we need xposed but to get OTA we need to uninstall xposed.
Also *Detection* is right. We root our device to alter system.
So at the end we need download whole ~2gb firmware(flash, root, xposed, all other changing system thing again) for 20-30mb monthly security patch
Click to expand...
Click to collapse
*Detection* said:
Basically yep, unless you're not bothered about the security update and just wait for feature/performance updates
With my S5 I used to update every update, download the new ROM, flash with ODIN, TWRP > Root > Mod
Doesn't take too long tbh
Click to expand...
Click to collapse
+ 1 guys
After rooting is very hard to keep system "clean" enough ....if you meet the conditions is possible.....but to my by far *Detection* suggestion is easier...
status spoofer i have not tried ( I have a custom rom) ......
Related
I just had a carrier update(Telus canada) pushed to my phone and i'd like to update however I do not want to loose root/etc.
Does anyone know of a patched version of this OTA zip or how to patch it?
Or where can i find the OTA in my phnoe to try and use flashfire?
Version : G930W8VLU2API1
PDA : G930W8OYA2API1
CSC : G930W8VLU2API1
Phone : G930W8VLU2API1
Size : 178.69MB
kylecore said:
Or where can i find the OTA in my phnoe to try and use flashfire?
Click to expand...
Click to collapse
Should be in /cache or any other cache dir, you can reroot anyway with cfroot.
Never found a way to flash the OTA zip neither in Flashfire nor in TWRP. The only way to update a rooted phone is either to download the whole thing with Samfirm or just unroot and then flash the update as usual. Maybe someday I will know better
Wasn't the vision of Systemless root that you would be able to apply OTA updates despite having root as it didn't modify the system partition? I'm not sure though if either of the root methods for the S7 are systemless roots.
I can't find the ota in cache or really anywhere I look with flashfire even though I've downloaded it. And the ota won't flash regardless because of two. I just want the notification to go away lol
Sea-Wolf said:
Wasn't the vision of Systemless root that you would be able to apply OTA updates despite having root as it didn't modify the system partition? I'm not sure though if either of the root methods for the S7 are systemless roots.
Click to expand...
Click to collapse
Yeah, you can receive OTA with systemless root as long as you didn't debloat your phone, but then there is no reason for me to root. Or did I mistake anything? Would be awesome if you could use systemless root and systemless xposed with a debloated device and still receive OTA via Flashfire or even the stock updater.
Is there any link to an OTA .zip ?
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
buyslake said:
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
Click to expand...
Click to collapse
First of all, no need to use 10D tot file anymore. Download and install 20A kdz front autoprime located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20a-rom-flashable-zips-imgs-t3511294
Once that's installed, set up your system and then follow the following guide to get TWRP an root:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
After you have TWRP and root download the flashable 20F zip and install from TWRP (make sure to delete recovery from boot.p file after installing and also flash root). Here's the link to 20F:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20f-rom-flashable-zips-imgs-t3592855
If you follow all of that, you will be on stock 20F, rooted and with TWRP. After that, I recommend checking out the following custom kernel and installing that and using magisk instead of SuperSU. Kernel located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Hopefully that helps, if you need more help just ask.
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
buyslake said:
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
Click to expand...
Click to collapse
After flashing the 20F version from TWRP, it creates a recovery from boot.p file in the system directory. If you don't delete this file before rebooting, you will lose TWRP. So, after doing the recowvery method to get root and TWRP and then after you flash the 20F from TWRP, after it's done flashing go to main menu of TWRP, click on mount, check system, go back to main menu, click advanced, click file manager and go-to system directory and click on the recovery from boot.p file and then delete. Now you can reboot without losing TWRP. Then you can flash SuperSU or magisk for root
Your Device software cannot be checked for corruption. Lock the bootloader
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
buyslake said:
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
Click to expand...
Click to collapse
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Where is Magisk?
jeffsga88 said:
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Click to expand...
Click to collapse
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
buyslake said:
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
Click to expand...
Click to collapse
No. I said currently there is no way to get rid of that message unless you lock the bootloader and you can't do that after modifying the system (i.e. installing TWRP and root). I said magisk will allow you to pass safety net. All that does is allow you to use apps that won't work with root / unlocked bootloader. If you don't use apps like Android pay or other apps that don't work when rooted, it really isn't necessary to switch from SuperSU to magisk. Anyways, if you're interested in magisk use Google (or XDA search) and search magisk XDA.
Hello Folks,
I need to know a few things about root, can someone explain me what's the difference between normal root and "systemless" root ?
And how do I know what kind of root I am using ?
I'm running SlimX, 5.11 with Xperia XZ SystemUI
I am root but I don't know wich one
Baradoura said:
Hello Folks,
I need to know a few things about root, can someone explain me what's the difference between normal root and "systemless" root ?
And how do I know what kind of root I am using ?
I'm running SlimX, 5.11 with Xperia XZ SystemUI
I am root but I don't know wich one
Click to expand...
Click to collapse
Normal root modifies files on your system partition so that you can have root access. On stock firmware, this breaks dm-verity and causes you to fail SafetyNet checks making AndroidPay and some other apps no longer work. It also prevents you from taking OTA updates because it is no longer recognized as stock firmware. Even if you fully unroot, you will still not be able to take OTA updates because the phone "remembers" that you modified system files and fails dm-verity. The only way to get back to original firmware and take OTA updates is to reflash your entire firmware, wiping all user data in the process.
Systemless root works by intercepting files at the kernel level before the phone fully boots and replaces system files. Once the helper apps are installed you can pass the SafetyNet checks, but you will still not be able to receive OTA updates. The major benefit to systemless root is that you can reflash your stock boot.img (kernel) and your phone will be back to stock firmware, you will bass dm-verity and SafetyNet checks, and you can take OTA updates all without losing any user data. It is very easy to switch between systemless root and stock unrooted by simply flashing the necessary boot.img.
My guess is that since you're on a custom ROM you have normal root. To learn more about systemless root, take a look at Magisk.
Thanks very much bro, yeah I guess I'm on normal root since I can't use android pay and can't download some apps protected by safetynet.
Either way next time I root my phone I'll try systemless method
Baradoura said:
Thanks very much bro, yeah I guess I'm on normal root since I can't use android pay and can't download some apps protected by safetynet.
Either way next time I root my phone I'll try systemless method
Click to expand...
Click to collapse
No, you are on systemless if you use slimx.
Are you sure ? I don't want to try some risky method to know
Baradoura said:
Are you sure ? I don't want to try some risky method to know
Click to expand...
Click to collapse
You can't have custom kernel and use android pay, just forget about it.
As Xposed was officially released for Nougat here is the guide to install on our device with September update ofcourse.
1. First download Xposed Installer from xposed official XDA thread. Below given link.
https://forum.xda-developers.com/showthread.php?t=3034811
2. Open the app and just tap install the latest version available.
3. Then give root access and press reboot when asked after installing process is done.
4. After reboot done.
Then You can Install Gravity Box for Nougat by following below link
https://forum.xda-developers.com/xposed/modules/app-gravitybox-v7-0-0-tweak-box-android-t3653953
Wrong link ...
I got the correct link but i am getting this error while trying to install
zazzy24 said:
I got the correct link but i am getting this error while trying to install
Click to expand...
Click to collapse
I have installed version 88 and it installed fine. Haven't tried 88.1.
rex28818 said:
I have installed version 88 and it installed fine. Haven't tried 88.1.
Click to expand...
Click to collapse
88.1 works well.
zazzy24 said:
I got the correct link but i am getting this error while trying to install
Click to expand...
Click to collapse
Iam also getting same error were you able to install xposed installer at last?
rex28818 said:
As Xposed was officially released for Nougat here is the guide to install on our device with September update ofcourse.
1. First download Xposed Installer from xposed official XDA thread. Below given link.
https://forum.xda-developers.com/showthread.php?t=3034811
2. Open the app and just tap install the latest version available.
3. Then give root access and press reboot when asked after installing process is done.
4. After reboot done.
Then You can Install Gravity Box for Nougat by following below link
https://forum.xda-developers.com/xposed/modules/app-gravitybox-v7-0-0-tweak-box-android-t3653953
Click to expand...
Click to collapse
It is not working for me.
Says system mounted as read only.
Please help
NITRO_100 said:
88.1 works well.
Click to expand...
Click to collapse
Hi, are you still receiving OTA with rooted and Xposed installed?
It seems TWRP disables OTA
I don't mind stock recovery, just need Xposed and OTA
Also, Magisk is optional for me. Don't really need it now
Raven_Yen said:
Hi, are you still receiving OTA with rooted and Xposed installed?
It seems TWRP disables OTA
I don't mind stock recovery, just need Xposed and OTA
Also, Magisk is optional for me. Don't really need it now
Click to expand...
Click to collapse
You won't be able to apply OTA with root. If you perform system modification (like in this guide), you'll have to flash whole system.img before applying new OTA. With Magisk and systemless Xposed it's enough to restore stock boot from within the app to apply OTA.
_mysiak_ said:
You won't be able to apply OTA with root. If you perform system modification (like in this guide), you'll have to flash whole system.img before applying new OTA. With Magisk and systemless Xposed it's enough to restore stock boot from within the app to apply OTA.
Click to expand...
Click to collapse
Thanks for your confirmation
Currently watching some youtube video, seems to know how it works out, thanks
Raven_Yen said:
Hi, are you still receiving OTA with rooted and Xposed installed?
It seems TWRP disables OTA
I don't mind stock recovery, just need Xposed and OTA
Also, Magisk is optional for me. Don't really need it now
Click to expand...
Click to collapse
No u wont get updates after installing xposed framework
Does This method still work on 2018 August security patch? Or Do I risk to brick the phone?
I have Magisk and stock recovery installed
caesar.tasker said:
Does This method still work on 2018 August security patch? Or Do I risk to brick the phone?
I have Magisk and stock recovery installed
Click to expand...
Click to collapse
Just install from magisk repository, Xposed framework for SDK 27 & apk provided with that module info to detect systemless xposed
.:Addicted:. said:
Just install from magisk repository, Xposed framework for SDK 27 & apk provided with that module info to detect systemless xposed
Click to expand...
Click to collapse
Can you link me the link of systemless APK of Xposed installer?
Hey everyone,
I have a Nexus 5 that I haven't updated in a long time that I'd like to get the latest possible OS for. The only modifications I've made which I think might be important are:
Unlocked bootloader
Rooted using SuperSU (v2.8.2 currently)
Installed XPosed (installer v2.6.1, not sure what version of the framework but it should be the latest supported by 4.4.4) with a few modules
Installed App Ops and removed permissions from some apps
Installed StickMount
I don't believe I have any custom recovery installed (I'd used a script to root and install XPosed originally and I don't know if it made any other changes). I'm comfortable using adb if needed but I'm cool with tools like FlashFire too.
My end goal is to have an updated OS with root and XPosed. I assume I'll need Magisk for XPosed, but not sure about root.
How should I go about doing this? I'm cool with losing all of my data (I'll be making backups with Titanium Backup) though knowing ahead of time if that'll be the case would be nice. If it's possible to update without losing data and without affecting anything that'd be nice, but maybe a clean start would be good? The OTA guide on this forum is only for 5, not 6, and most online guides start with 5. I don't want to mess up obviously. xD
Any advice/steps would be appreciated! Thanks!
Aecyl said:
Hey everyone,
Click to expand...
Click to collapse
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
pavik62 said:
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
Click to expand...
Click to collapse
The link you gave doesn't have the latest 6.0.1 build and it also says that it requires a minimum bootloader (HHZ12h) that I don't have (I have HHZ11k). Would it be possible to use the latest build from Google? What do I do about the bootloader? And would using TWRP as the recovery prevent me from passing SafetyNet?
Thanks for replying!
Could I follow this guide with the latest factory image and then install Magisk, root, and XPosed? https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Roxasmaker said:
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Click to expand...
Click to collapse
Would I have to do anything to XPosed or supersu first? I'd like to update to 6.0.1, too. I've seen online that there are OTA updates for it too.
Nope. But you may have to reinstall root, which is very easy once you're updated. Just let the updates do their thing, and you'll be on your merry way! Hope I helped
I think what I'll do is flash stock 4.4.4 keeping user data and then use the OTAs to update to 6. That way I have a clean system install to use Magisk with without losing any user data. (If that doesn't work I'll just flash 6.0.1 for a clean install.)