Anyone know how to get them running on rooted 5.1, and sidestep rhe whole SafetyNet stupidity? Without losing root, or at most losing it temporarily while they're running?
Tried rootcloak?
Pokemon Go, able to play on root, guarantee
here is a link to instructions on using this app. it is called Magisk!
http://apkquick.com/root-apk-files/magisk-apk-hide-root-for-pokemon-goandroid-pay/
Glitch15 said:
here is a link to instructions on using this app. it is called Magisk!
http://apkquick.com/root-apk-files/magisk-apk-hide-root-for-pokemon-goandroid-pay/
Click to expand...
Click to collapse
I was under the impression magicsk wouldn't work, since the bootloader isn't unlocked, there's no custom recovery available? And apparently rootcloak doesn't work for apps that use the google 'safetynet' code.
Flashfire by Chainfire
christiebunny said:
I was under the impression magicsk wouldn't work, since the bootloader isn't unlocked, there's no custom recovery available? And apparently rootcloak doesn't work for apps that use the google 'safetynet' code.
Click to expand...
Click to collapse
It is a lengthy process, but flashfire can flash zips. I do not recommend doing it if you don't want to lose your data. it is a possibility.
I was afraid of that...
Flashfire CAN flash magicsk and the rest, however as the bootloader is NOT unlocked on the verizon V10, it errors out and bootloops at the LG logo with an 'error 1003', and 'MODIFIED!'
So, I guess Pokemon GO, and Android Pay are both dead unless I decide to unroot completely
And yes, I *did* end up having everything wiped, but fortunately I had backups, although I haven't figured out how to restore a nandroid backup without a custom recovery.... yet!
christiebunny said:
I was afraid of that...
Flashfire CAN flash magicsk and the rest, however as the bootloader is NOT unlocked on the verizon V10, it errors out and bootloops at the LG logo with an 'error 1003', and 'MODIFIED!'
So, I guess Pokemon GO, and Android Pay are both dead unless I decide to unroot completely
And yes, I *did* end up having everything wiped, but fortunately I had backups, although I haven't figured out how to restore a nandroid backup without a custom recovery.... yet!
Click to expand...
Click to collapse
I use nandroid manager.
Related
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Saint Isaiah said:
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Click to expand...
Click to collapse
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
joshm.1219 said:
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
Click to expand...
Click to collapse
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Also, what in the world does it mean to "Loki" a ROM after installing it? Kinda confused there
Saint Isaiah said:
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Click to expand...
Click to collapse
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
joshm.1219 said:
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
Click to expand...
Click to collapse
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Saint Isaiah said:
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Click to expand...
Click to collapse
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
joshm.1219 said:
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
Click to expand...
Click to collapse
Awesome, thanks Josh! This might make a great sticky for the "what is Loki?" newvies and explaining the importance of MDK for those still on it and not sure why.
I have converted my AT&T M8 to stock Dev Edition following this thread. Worked a treat.
http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
I'm going on a vacation and want to use my phone as a transfer spot for photos taken with a DSLR. To do that, I will need to be able to copy/move files from the camera's SD card onto my phone's SD using USB OTG.
I understand that if I keep the stock recovery, loader, etc and only achieve root, then I will be able to get any OTA that becomes available. I will also be able to use one of the methods to enable writing to the SD of the phone.
So, the question is, how to get root without changing anything that will impact the OTA ability?
Hope I was clear in what I have and what I'm looking for.
No Direction?
Nobody?
GHammer said:
Nobody?
Click to expand...
Click to collapse
I've never heard of anyone wanting just root, so I'm not sure. But if your bootloader is unlocked you can try TowelRoot and see if that works and just install SuperSu through the playstore.
Unique
Ha! I'm unique.
Actually, I like Sense, and Lollipop is fine. I just didn't loike all the crap AT&T forced onto the phone and Uber was the last straw.
So, I want to keep the phone 'stock' except for accessing the extrenal SD.
I'll give Towelroot a shot and see how it goes.
GHammer said:
Ha! I'm unique.
Actually, I like Sense, and Lollipop is fine. I just didn't loike all the crap AT&T forced onto the phone and Uber was the last straw.
So, I want to keep the phone 'stock' except for accessing the extrenal SD.
I'll give Towelroot a shot and see how it goes.
Click to expand...
Click to collapse
Maybe I'm just off base here, but once the bootloader is unlocked, can't you just fastboot TWRP recovery, install SU (zip) file via recovery, then fastboot stock recovery and end up with a stock rooted device? Or does Lollipop not allow this?
DanGeorges said:
Maybe I'm just off base here, but once the bootloader is unlocked, can't you just fastboot TWRP recovery, install SU (zip) file via recovery, then fastboot stock recovery and end up with a stock rooted device? Or does Lollipop not allow this?
Click to expand...
Click to collapse
Hmmmm, perhaps just booting a recovery and installing SU would work.
See why I asked?
Guess this will wait for the weekend now. Restoring a phone takes more time than I have and it looks like I'm in uncharted territory.
Again, my objective is to have an OTA acceptable system with root.
Thanks for the two ideas, and of course, I'm open to others.
GHammer said:
Hmmmm, perhaps just booting a recovery and installing SU would work.
See why I asked?
Guess this will wait for the weekend now. Restoring a phone takes more time than I have and it looks like I'm in uncharted territory.
Again, my objective is to have an OTA acceptable system with root.
Thanks for the two ideas, and of course, I'm open to others.
Click to expand...
Click to collapse
I had a rooted device (4.4.2) and when I wanted the OTA to 4.4.4, I kept the root, but re-fastbooted the stock recovery so that the OTA would work. It kept my root (I think), and then I just re-installed TWRP so that I could still do backups..
I hope that someone with more knowledge than I will chime in if I'm wrong (or right).
DanGeorges said:
I kept the root, but re-fastbooted the stock recovery so that the OTA would work.
Click to expand...
Click to collapse
This is what I would suggest. There may be other ways (root without custom recovery). But I know for certain that the following will work: flash TWRP, flash SU or SuperSU to root. Than flash back to stock recovery.
You will be on stock recovery, have root, and should not impact OTA (provided all system files are also stock and not altered by root).
You can also try to fastboot boot TWRP (and then flash SU/SuperSU) without actually flashing TWRP. I'm not certain this will work, but I think it does under LP. I think something on 4.4.4 broke this ability, but then it came back.
Weekend Project
I will try the boot TWRP method first, and if that fails, I'll flash TWRP, get root, then go back to stock recovery.
This is now just an exercise to see which method works as the stock File Manager reads the USB and can copy files to the SD. I had not tried since 4.4.4. but did yesterday and it works for any kind of file.
Also, since it was previously rooted, can I immediately get to installing the OTA updates/most recent At&t updates for my device? Will they even be there? If not, can anyone leave me a link and explain how to do so after I finish the unrooting process? Thank you.
Also, I just found the rom page on HTC, and I think this is correct. I'm still on 4.4.2 anyways That, or 4.2.2 Not quite sure. Is it possible for me to just download this from the website? If that's the case, then I won't unroot it. My only gripe is that I can't uninstall anything on my phone even though it's rooted. When I restart, the app still remains. This is only with stock apps, of course. Anyways, with the HTC rom, if I have to flash this or something, etc., I'd need this to be explained.
Edit: I did find a youtube video in which I can get OTA updates on my phone, but it says that I need to have a twrp custom recovery. All I really did was root my phone and I have the super su app.
You need to relock the boot loader and then select unroot in super su options. You will also need to flash stock recovery if you want to receive OTAs.
This shouldn't delete any data.
I would recommend going s-off and flashing dev edition Rom. Quicker updates and no bloatware to deal with. Worked great for me.
Before doing so, just copy your contacts and messages to ext SD card. Reinstalling your apps isn't too much of an inconvenience considering you get out from under AT&T restrictions.
Sent from my HTC One_M8 in a van down by the river.
chevyjohn01 said:
You need to relock the boot loader and then select unroot in super su options. You will also need to flash stock recovery if you want to receive OTAs.
Click to expand...
Click to collapse
Relocking the bootloader typically wipes data and renders the phone unbootable (expect the RUU).
Also, it seems like you are suggesting the method or return to stock for OTAs. In that case, relocking the bootloader is not necessary. Relocking the bootloader is only required to RUU (not for OTA).
---------- Post added at 02:56 PM ---------- Previous post was at 02:50 PM ----------
Tiffianie said:
Also, since it was previously rooted, can I immediately get to installing the OTA updates/most recent At&t updates for my device? Will they even be there? If not, can anyone leave me a link and explain how to do so after I finish the unrooting process? Thank you.
Click to expand...
Click to collapse
For OTA, you need stock ROM (nothing modified in system partition - but from your subsequent statement it sounds like you were never able to, anyway) and stock recovery.
From there, and also as long as you are on AT&T's network, you should be able to get OTA updates. Root is okay (does not prevent OTA updates in itself). Unlocked bootloader is also ok.
You should be able to return to stock and OTA update without losing your data. However, you should always be backing up your data (and be able to restore it accordingly), if its that important to you. Your data is never guaranteed to be safe, even with normal day to day usage (much less OTA updates or rooting) and you should backup to avoid regret.
Tiffianie said:
My only gripe is that I can't uninstall anything on my phone even though it's rooted. When I restart, the app still remains. This is only with stock apps, of course. Anyways, with the HTC rom, if I have to flash this or something, etc., I'd need this to be explained.
Click to expand...
Click to collapse
Could have easily searched these forums for that answer. System partition (where the stock apps are stored) on this phone is write protected. Even with root, you need to install a kernel mod to disable write protection.
Tiffianie said:
Edit: I did find a youtube video in which I can get OTA updates on my phone, but it says that I need to have a twrp custom recovery. All I really did was root my phone and I have the super su app.
Click to expand...
Click to collapse
If you didn't install custom recovery, how did you root?
chevyjohn01 said:
You will also need to flash stock recovery if you want to receive OTAs.
This shouldn't delete any data.
I would recommend going s-off and flashing dev edition Rom. Quicker updates and no bloatware to deal with.
Click to expand...
Click to collapse
I probably won't unroot if I can try to get ota updates. How can I check what recovery I have installed? I downloaded flashify and backed up the current kernel through my drop box, so I'm not sure if that did a damned thing.
GFE on Rooted Z3v 5.0.2?
Followed the guides for the Verizon Sony Xperia Z3v & managed to upgrade to Android 5.0.2 with root access. I was ecstatic until I was told by my IT Administrators, that Good For Enterprises will not run/work on a rooted device. (Followed this guide exactly Guide)
I know it sucks, but I have to have Good For Enterprises for work. So...
1. What is the best way unroot so I can resume using GFE?
2. What will happen to the XZ Dual Recovery I've installed? Is it possible to keep custom recovery & get rid of root access, so that I can still flash new firmware in the future?
Thanks in advance!
did you try rootcloak?
As I understand it, to get back to stock will require flashtool and flashing the stock sony file.
Delebird said:
did you try rootcloak?
Click to expand...
Click to collapse
Yes, unfortunately rootcloak plus does not currently work for Lollipop & Good For Enterprises. Thank you for the thought though.
Best-
JediDru said:
As I understand it, to get back to stock will require flashtool and flashing the stock sony file.
Click to expand...
Click to collapse
I don't need to get back to stock, rather, I need to "un-root" the device so it will pass the GFE compliance check. In SuperSU there is a Full unroot option. Would that work to unroot the device? If I select that option, what happens to the custom dual recovery I installed per the previously posted guide on how to root & flash Lollipop?
Best-
cofcgrad05 said:
I don't need to get back to stock, rather, I need to "un-root" the device so it will pass the GFE compliance check. In SuperSU there is a Full unroot option. Would that work to unroot the device? If I select that option, what happens to the custom dual recovery I installed per the previously posted guide on how to root & flash Lollipop?
Best-
Click to expand...
Click to collapse
Going back to stock is the way to fully unroot. You can try the unroot function in the SuperSU app but I can't 100% guarantee that is enough for gfe to work.
I am uncertain if you can keep dual recovery when not rooted.
BladeRunner said:
Going back to stock is the way to fully unroot. You can try the unroot function in the SuperSU app but I can't 100% guarantee that is enough for gfe to work.
I am uncertain if you can keep dual recovery when not rooted.
Click to expand...
Click to collapse
Thank you all for the help. Ran the full unroot option in SuperSU, rebooted, installed GFE now works. Hope you all have a Happy Thanksgiving!
So you were on 5.02 rooted and using SuperSU you unrooted and rebooted for it to work? Can you root again using SuperSU just using the app after installing GFE?
pvcdroid said:
So you were on 5.02 rooted and using SuperSU you unrooted and rebooted for it to work? Can you root again using SuperSU just using the app after installing GFE?
Click to expand...
Click to collapse
Yes, that's correct. I used SuperSU to unroot, reboot, & then GFE was able to go through the full activation process. My understanding of GFE is that anytime the GFE Service starts, it does a compliance check & if it discovers root, it will force close the app. This is what was occurring when I tried to activate the GFE license with root access. It would activate & then when it went to start the GFE Service it would force close the app.
I have not tried to reroot with SuperSU to see if GFE will work once activated with root access. My guess from reading different forums is that it will not. I will try in a month or two after some time has passed for the IT guys at my company, to re-root the device & see if I can use GFE with the phone rooted.
cofcgrad05 said:
Followed the guides for the Verizon Sony Xperia Z3v & managed to upgrade to Android 5.0.2 with root access. I was ecstatic until I was told by my IT Administrators, that Good For Enterprises will not run/work on a rooted device. (Followed this guide exactly Guide)
I know it sucks, but I have to have Good For Enterprises for work. So...
1. What is the best way unroot so I can resume using GFE?
2. What will happen to the XZ Dual Recovery I've installed? Is it possible to keep custom recovery & get rid of root access, so that I can still flash new firmware in the future?
Thanks in advance!
Click to expand...
Click to collapse
did you see if that good for enterprise-root module on xposed that may have worked.
I'm running 47A from here:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's got systemless root, I'm using SuperSU and I have TWRP installed. No xposed.
I really don't want to use xposed/magisk and I'm probably willing to lose root (would be nice if it was temporary vs permanent).
If I uncheck enable superuser in SuperSU and reboot, Android Pay still doesn't work.
So what exactly do I need to do in order to get Android Pay working?
lexluthor said:
I'm running 47A from here:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's got systemless root, I'm using SuperSU and I have TWRP installed. No xposed.
I really don't want to use xposed/magisk and I'm probably willing to lose root (would be nice if it was temporary vs permanent).
If I uncheck enable superuser in SuperSU and reboot, Android Pay still doesn't work.
So what exactly do I need to do in order to get Android Pay working?
Click to expand...
Click to collapse
I'm not rooted (anymore), but with bumped TWRP and SuperSU, apparently you can work around this. It appears PokeMon GO is blocking rooted users due to people spoofing their GPS location via Xposed modules, etc. This article explains how to flash something called Magisk that apparently works for both Pokemon GO as well as Android Pay. Again, I'm not rooted so I have no idea if this will work or not, but he lays out the instructions pretty well. I believe that since you are already rooted and bumped with TWRP, and no Xposed, you just need to obtain Magisk and flash from within TWRP.
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Hope this helps. I just happen to come across this article in my Feedly feed and remembered reading your post, so hopefully this helps you.
Let us know!
iBolski said:
I'm not rooted (anymore), but with bumped TWRP and SuperSU, apparently you can work around this. It appears PokeMon GO is blocking rooted users due to people spoofing their GPS location via Xposed modules, etc. This article explains how to flash something called Magisk that apparently works for both Pokemon GO as well as Android Pay. Again, I'm not rooted so I have no idea if this will work or not, but he lays out the instructions pretty well. I believe that since you are already rooted and bumped with TWRP, and no Xposed, you just need to obtain Magisk and flash from within TWRP.
Hope this helps. I just happen to come across this article in my Feedly feed and remembered reading your post, so hopefully this helps you.
Let us know!
Click to expand...
Click to collapse
Hi iBolski,
Did you mean to include a link to an article about installing Magisk with an Verizon LG G3?
I've been looking for a way to install a stock unrooted rom for days but have been coming up short. Magisk would be ideal but I can't seem to find any threads that have a stock (unrooted) firmware image or a guide on how to unroot a pre-rooted firmware. I wish a tutorial specifically for a Bumped VS985 existed to set up a stock firmware or other ROM with Magisk because I have been having trouble piecing information together and am nervous about causing problems with my phone!
If anyone else has a Bump'd VS985 Verizon LG G3 with TWRP installed that is either unrooted or have Magisk running successfully with Android Pay or Pokemon GO, please let us know how you did it!
Thanks!!
EDIT: I just noticed that you yourself are running stock unrooted 46A iBolski... do you have TWRP installed or are you fully stock and accepted an OTA? If TWRP, does Android Pay or Pokemon Go work for you? And how'd ya get to where you are?
eagle132 said:
Hi iBolski,
Did you mean to include a link to an article about installing Magisk with an Verizon LG G3?
I've been looking for a way to install a stock unrooted rom for days but have been coming up short. Magisk would be ideal but I can't seem to find any threads that have a stock (unrooted) firmware image or a guide on how to unroot a pre-rooted firmware. I wish a tutorial specifically for a Bumped VS985 existed to set up a stock firmware or other ROM with Magisk because I have been having trouble piecing information together and am nervous about causing problems with my phone!
If anyone else has a Bump'd VS985 Verizon LG G3 with TWRP installed that is either unrooted or have Magisk running successfully with Android Pay or Pokemon GO, please let us know how you did it!
Thanks!!
EDIT: I just noticed that you yourself are running stock unrooted 46A iBolski... do you have TWRP installed or are you fully stock and accepted an OTA? If TWRP, does Android Pay or Pokemon Go work for you? And how'd ya get to where you are?
Click to expand...
Click to collapse
Sorry about forgetting the link. I updated my previous reply with the article in question.
As to your answer, I do not have TWRP installed. I do have all the official OTAs applied.
iBolski said:
Sorry about forgetting the link. I updated my previous reply with the article in question.
As to your answer, I do not have TWRP installed. I do have all the official OTAs applied.
Click to expand...
Click to collapse
Thanks for updating with the link. I did see that guide but am unsure about how to handle it with BUMP and what ROMs it works with.
If anyone else has a stock unrooted ROM or working Magisk with their TWRP/BUMP'd G3... please let us know!
eagle132 said:
Thanks for updating with the link. I did see that guide but am unsure about how to handle it with BUMP and what ROMs it works with.
If anyone else has a stock unrooted ROM or working Magisk with their TWRP/BUMP'd G3... please let us know!
Click to expand...
Click to collapse
As a follow up to my own post, I was able to pass the SafetyNet check (I used SafetyNet Helper from the Play Store to check) on my CloudyG3 2.5 LG G3 VS985. This was not without it's negatives however (no Xposed or root).
I simply flashed the Xposed Uninstaller and uninstalled the app, then from within the SuperSU app settings selected the option to permanently unroot. I did of course make a nandroid backup before doing this so restoring will not be an issue, but I do now get a green screen / pass to SafetyNet which should mean Android Pay and Pokemon Go will work.
eagle132 said:
As a follow up to my own post, I was able to pass the SafetyNet check (I used SafetyNet Helper from the Play Store to check) on my CloudyG3 2.5 LG G3 VS985. This was not without it's negatives however (no Xposed or root).
I simply flashed the Xposed Uninstaller and uninstalled the app, then from within the SuperSU app settings selected the option to permanently unroot. I did of course make a nandroid backup before doing this so restoring will not be an issue, but I do now get a green screen / pass to SafetyNet which should mean Android Pay and Pokemon Go will work.
Click to expand...
Click to collapse
Did you try Magisk at all? I am on Jasmine ROM (Android 5.1.1) and would love a way to still have Root & Xposed, but be able to pass SafetyNet for PokemonGO and Wallet
Question on XDABBEB's VS985 ROM
Considering that this phone will probably see no more OTA's, I'm ready to go back to root, but I don't want to break Android Pay. Also, I'm not going to use Kingroot. Don't trust it. So, I'll TOT back to 10B to flash XDABBEB VS985 ROM. But i have some questions regarding it (I haven't ran a custom ROM in almost a year).
Does anyone know if removing SuperSU from XDABBEB VS985 ROM will allow Android Pay to work? Curious if so, otherwise, I'll probably just stick with my stock 48A unrooted phone in order to keep Android Pay.
I also miss TiBu as my backup tool. Yes, LG Backup is nice and all, but TiBu is so much more flexible, including the scheduled backups that I like to do as well as pushing to my Google Drive for backing up the files. Also, TiBu doesn't store it in one giant backup file. I really wish LG Backup would store each app as a separate file, rather than one giant, humongous file. Also, if I do upgrade to a new phone that's not LG, LG Backup won't work for me, so I'll need TiBu (and of course, I have to make sure the new phone is rootable).
Thanks!
While I have not tried this (I plan to try magisk later this week) supposedly Reddit says we can use this bump script after applying magisk in order to make everything will boot. I'm reading mixed comments about if/which certain bootloader is needed to have this work (KitKat vs Lollipop vs Marshmallow) or which ROM to start with as a base (though I saw CM 13 mentioned). If anyone tries this, let me know. I'll post my results in the coming days.