iSu [V7.6][5.1+] Simple app to deactivate activate LineageOS SU at will

[xXSnowyXx]

Works great on S5 CM14.1. My only wish is for some intents so I can activate or deactivate from Tasker without using clumsy AutoInput scripts.

 

[gpex]

Not working on my OnePlus One with CM 14.1
The app seems to work fine (tested with Root Checker), but Pokemon Go still won't let me in and SafetyNet test still gives CTS Profile match: false

 

[mrkhigh]

Not working on my OnePlus One with CM 14.1
The app seems to work fine (tested with Root Checker), but Pokemon Go still won't let me in and SafetyNet test still gives CTS Profile match: false

I'm guessing you probably have something changed in system from stock?

 

[highmighty]

Hi there, everything looks fine on my LG Nexus 5 running CM14.1 with iSU properly installed (see attached screenshot) but Pokemon won't let me in, any clues? Where should I start my troubleshooting?

Thanks a bunch for your time and support

 

[mrkhigh]

Hi there, everything looks fine on my LG Nexus 5 running CM14.1 with iSU properly installed (see attached screenshot) but Pokemon won't let me in, any clues? Where should I start my troubleshooting?

Thanks a bunch for your time and support

Try dirty flashing cm14.1 over your current build.
I have to wonder if you somehow changed something in system

 

[highmighty]

Try dirty flashing cm14.1 over your current build.
I have to wonder if you somehow changed something in system

I even got your message saying Chuck catch them all in 2 minutes!!
I'll give it a try tomorrow and let you know how it goes, thanks again

 

[highmighty]

I even got your message saying Chuck catch them all in 2 minutes!!
I'll give it a try tomorrow and let you know how it goes, thanks again

Dirty flashing means that I should reboot into Recovery and then flash the same build (in my case cm-14.1-20161205-NIGHTLY-hammerhead.zip) without doing anything else and then reboot to system, right?

 

[mrkhigh]

Yep.

Basically we're just making sure your system is pure.

 

[highmighty]

I did what you advised me to do, I dirty flashed the same build and also the iSu kernel support, I then disabled SU within iSu but unfortunately Pokémon won't still let me in because of an authentication error, any clue as to why?

What are they checking? The build name/version? The fact that the bootloader is unlocked? That SU is enabled? All of those facts? I've also noticed that Busybox is always being installed with this build, could it be the problem?

What else can/should I try? Currently level 27 in Pokémon without having cheated at all, I sure would like to play back, especially this Thursday

Thank your for your time and support again

*EDIT* I uninstalled BusyBox and same issue, can't login and I also did the SafetyNet test which failed the CTS profile match and gave a "Response payload validation failed" error

 

[fgl27]

I did what you advised me to do, I dirty flashed the same build and also the iSu kernel support, I then disabled SU within iSu but unfortunately Pok�mon won't still let me in because of an authentication error, any clue as to why?

What are they checking? The build name/version? The fact that the bootloader is unlocked? That SU is enabled? All of those facts? I've also noticed that Busybox is always being installed with this build, could it be the problem?

What else can/should I try? Currently level 27 in Pok�mon without having cheated at all, I sure would like to play back, especially this Thursday

Thank your for your time and support again

*EDIT* I uninstalled BusyBox and same issue, can't login and I also did the SafetyNet test which failed the CTS profile match and gave a "Response payload validation failed" error

What busybox? that is not default on CM ROM, maybe the ROM you are using not be a stock CM has security problem.

If you can use today POGO on the stock ROM on your device, you flash CM + gapps + iSu app, install POGO don't do any other change, and can't play the game your CM has security problem, explain to the dev and ask if he can assist because I have no idea what was done and he may help to solve.

 

[highmighty]

What busybox? that is not default on CM ROM, maybe the ROM you are using not be a stock CM has security problem.

If you can use today POGO on the stock ROM on your device, you flash CM + gapps + iSu app, install POGO don't do any other change, and can't play the game your CM has security problem, explain to the dev and ask if he can assist because I have no idea what was done and he may help to solve.

I sure want to give this a try! Please tell me if those steps would be the right ones?

1) Reboot into recovery (TWRP 3.0.2) and wipe/reset everything
2) Flash the stock ROM for my LG Nexus 5. Is the stock ROM the original ROM that came with the phone back in 2013 (with Android 4 I think?) or I could use the latest one officially sent from Google to my device (Android 6.0.1)?
3) Test the build with POGO
4) Reboot into recovery to flash a CM14.1 build + gapps + iSu and test again POGO

Thanks again for your time and support

 

[mrkhigh]

I sure want to give this a try! Please tell me if those steps would be the right ones?

1) Reboot into recovery (TWRP 3.0.2) and wipe/reset everything
2) Flash the stock ROM for my LG Nexus 5. Is the stock ROM the original ROM that came with the phone back in 2013 (with Android 4 I think?) or I could use the latest one officially sent from Google to my device (Android 6.0.1)?
3) Test the build with POGO
4) Reboot into recovery to flash a CM14.1 build + gapps + iSu and test again POGO

Thanks again for your time and support

Yep
Just try and flash an official cm. I'm guessing you were using a modded version.

If it doesn't work on lg stock, I am guessing they're is a bootloader issue. In which case you should probably look into a kernel solution

 

[fgl27]

I sure want to give this a try! Please tell me if those steps would be the right ones?

1) Reboot into recovery (TWRP 3.0.2) and wipe/reset everything
2) Flash the stock ROM for my LG Nexus 5. Is the stock ROM the original ROM that came with the phone back in 2013 (with Android 4 I think?) or I could use the latest one officially sent from Google to my device (Android 6.0.1)?
3) Test the build with POGO
4) Reboot into recovery to flash a CM14.1 build + gapps + iSu and test again POGO

Thanks again for your time and support

Just to be shore that the device can pass a safety check, I need you to tell me if using the latest stock ROM form google you can pass and play the game...

I'm assuming you can, but safety related things change everyday and something on the device may be affecting.

Then after be shore of the good result, go back and flash the CM if a official exit try that and report back...

something like this...

1) Reboot into recovery (TWRP 3.0.2) and wipe/reset everything
2) Flash the stock ROM for my LG Nexus 5... Android 6.0.1 or latest
3) Test the build with POGO
4) Reboot into recovery to flash a CM14.1 build + gapps + iSu and test again POGO with SU disable via app.

 

[SkyLkr]

I'm having troubles to install the kernel support

I'm running CM 13 on a Moto X (XT1097), and your app works fine, but I can't flash the kernel suport. I aways have the same error "Unpacking ramdisk faild. Process ended with ERROR: 1".

 

[fgl27]

I'm running CM 13 on a Moto X (XT1097), and your app works fine, but I can't flash the kernel suport. I aways have the same error "Unpacking ramdisk faild. Process ended with ERROR: 1".

Can you share the TWRP log and print screen of TWRP? after that problem.

 

[highmighty]

Just to be shore that the device can pass a safety check, I need you to tell me if using the latest stock ROM form google you can pass and play the game...

I'm assuming you can, but safety related things change everyday and something on the device may be affecting.

Then after be shore of the good result, go back and flash the CM if a official exit try that and report back...

something like this...

1) Reboot into recovery (TWRP 3.0.2) and wipe/reset everything
2) Flash the stock ROM for my LG Nexus 5... Android 6.0.1 or latest
3) Test the build with POGO
4) Reboot into recovery to flash a CM14.1 build + gapps + iSu and test again POGO with SU disable via app.

Here are my results, I put back the stock rom 6.0.1 for the Nexus 5 and POGO ran just fine and I saw the Christmas Pikachu loading page and then the game

I then flashed this CM14.1 build (cm-14.1-20161212-NIGHTLY-hammerhead.zip) taken from https://download.cyanogenmod.org/?device=hammerhead, enabled the root access within CM settings, installed iSu apk, rebooted into recovery to install the kernel support for iSu, went back to iSu to make sure everything looked right (it did), I disabled SU in it and then I started POGO but it wouln't authenticate me

And of course, the SaferyNet helper apk tells me something went wrong but at least I now know my account hasn't been banned by Niantic for some reasons...

And for your information, only NIGHTLY builds are available for CM14.1 on a Nexus 5, it looks like it's not a "stable/release" build, the most recent "release" build is version CM13 (with 6.0.1 I guess), which is the "same" Android version offered OTA from Google.

What should I do next?

Thanks again for your time and support

 

[fgl27]

Here are my results, I put back the stock rom 6.0.1 for the Nexus 5 and POGO ran just fine and I saw the Christmas Pikachu loading page and then the game

I then flashed this CM14.1 build (cm-14.1-20161212-NIGHTLY-hammerhead.zip) taken from https://download.cyanogenmod.org/?device=hammerhead, enabled the root access within CM settings, installed iSu apk, rebooted into recovery to install the kernel support for iSu, went back to iSu to make sure everything looked right (it did), I disabled SU in it and then I started POGO but it wouln't authenticate me

And of course, the SaferyNet helper apk tells me something went wrong but at least I now know my account hasn't been banned by Niantic for some reasons...

And for your information, only NIGHTLY builds are available for CM14.1 on a Nexus 5, it looks like it's not a "stable/release" build, the most recent "release" build is version CM13 (with 6.0.1 I guess), which is the "same" Android version offered OTA from Google.

What should I do next?

Thanks again for your time and support

OK, that at least tell that the device is OK to pass, and the problem is in the ROM SW, those problem that can be breaking the safety pass are unknown, unfortunately google api only tell you that you did not pass, doesn't tell you exactly way, with makes really hard in to fix things, they probably do this to avoid specific hacks, but I find it very disturbing because most user only wanna to have a safe device and be free to choose they OS but we can't even know what is not safe on the OS we are running so how to fix.

The only solution here is post on the XDA CM thread and ask the dev to take a look, maybe he knows something that he had change and can be the cause of a security breech and can fix after all others CM ROM 13 14.1 etc are working so others devices are OK running CM, but those things are hard to find as the safety api doesn't tell what is the problem...

Any way any future update of the ROM also may bring a fix without a warning so test future update, if I find something I update the app and the thread...

:good:

 

[highmighty]

OK, that at least tell that the device is OK to pass, and the problem is in the ROM SW, those problem that can be breaking the safety pass are unknown, unfortunately google api only tell you that you did not pass, doesn't tell you exactly way, with makes really hard in to fix things, they probably do this to avoid specific hacks, but I find it very disturbing because most user only wanna to have a safe device and be free to choose they OS but we can't even know what is not safe on the OS we are running so how to fix.

The only solution here is post on the XDA CM thread and ask the dev to take a look, maybe he knows something that he had change and can be the cause of a security breech and can fix after all others CM ROM 13 14.1 etc are working so others devices are OK running CM, but those things are hard to find as the safety api doesn't tell what is the problem...

Any way any future update of the ROM also may bring a fix without a warning so test future update, if I find something I update the app and the thread...

:good:

Ok I will post in that thread but in the meantime I will have to go back to stock if I want POGO to work, right? And when a "release" build 14.1 will be available for Nexus 5 (vs a NIGHTLY build) I should test again but will that ever happen?

Thanks

 

[mrkhigh]

Ok I will post in that thread but in the meantime I will have to go back to stock if I want POGO to work, right? And when a "release" build 14.1 will be available for Nexus 5 (vs a NIGHTLY build) I should test again but will that ever happen?

Thanks

Did you try activating se Linux in the app?

 

[highmighty]

Did you try activating se Linux in the app?

Yes se Linux is activated and SU is disabled but I still can't authenticate