Database Develop

xposed security alert code 2 ( Netmarble games ) fix / solution

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PLEASE BE AWARE THAT THESE SOLUTIONS / SCRIPTS IN THESE POSTS ARE ONLY FOR THE
"SECURITY ALERT CODE 2 [XPOSED]" error message in games....
( they are NOT for OTHER "Security Alert Code 2 [SomeOtherApp]" GAME ERRORS !!! )...
PLEASE TAKE YOUR TIME TO THOROUGHLY READ & UNDERSTAND THESE SOLUTIONS
TO BYPASSING THE "SECURITY ALERT CODE 2 [XPOSED]" game error... Thank you.
I found a good solution to this problem and wanted to share it with the community as many others have encountered this problem...
When trying to play Netmarble games with xposed installed on your android device, the game uses some kind of anti-cheat detection, giving the error message "xposed security alert code 2" and exiting the game.. It appears to be some kind of online detection where the error occurs after it connects online and says its checking for updates. :crying:
GAMES LIKE MARVEL FUTURE FIGHT, SEVEN KNIGHTS, RUSH-N-KRUSH, EVIL BANE, etc detect xposed installer. Xposed modules do not hide xposed from these games either ( such as rootcloak, denying permissions, etc ).
I originally posted the "how-to" responding to another users thread:
http://forum.xda-developers.com/xpo...lertcode-2-t3265279/post67346433#post67346433
I decided to start a new thread and post the solutions here.
There is no need to uninstall xposed, nor is a reboot required!

The basic solution is as follows:
Using a file manager app with root, in the /data/data folder,
simply rename the folder called de.robv.android.xposed.installer
( i rename it to de.robv.android.xposed.installer2 )
Then launch the game, future fight. (Works fine for me)
you do not have to reboot! Just rename the folder.
When you are done with game and exit it, dont forget to rename
the xposed installer folder in /data/data back to de.robv.android.xposed.installer

Here is a way to use scripts instead:
Install from the playstore these 2 free apps ( no ads )
(1) AUTOMATE
(2) TASKER PROCESSES RUNNING (KC)
In AUTOMATE, click on the community icon on top toolbar and from the GAMES category download these scripts I created:
MARVEL FUTURE FIGHT (UPDATED)*
**** UPDATE! **** " bypass Netmarble's XPOSED Security Alert Code 2"
has been updated to "bypass XPOSED Security Alert Code 2 (UPDATED)"
The 1st script is a launcher for Future Fight that automatically does everything in 1 click.
the 2nd script is a toggle on/off ( ie. renaming ) script with toast messages as an alternative solution & will work will ALL netmarble games. The updated version can deal with duplicate folders, caused by a toggle off & restarting your device ( xposed installer creates another folder if the original is renamed and xposed thinks its missing ).
*note: After installing the above scripts in Automate, be sure to install / configure / allow the required things that Automate says it needs for these scripts, or they may not work! This would be the SUPERUSER & STORAGE permissions.
** another thing you may need to do is go to your system settings, accessibility: under Services, turn on Automate and under direct access, turn on the Universal Access.

Last of all, you may use the MARVEL FUTURE FIGHT (UPDATED) script as a TEMPLATE to create launchers for other Netmarble games. Here's how:
In automate, edit the flowchart... long press on a block & select all, then copy the flowchart. Press done.
Create a new flowchart and paste the copied blocks (long press screen)
Then you just need to edit a few blocks:
1. In the flow beginning, change the title to your game. Also, click on the Install Homescreen Shortcut to Add a launcher icon on your desktop.
2. In the Start App Main Activity block, change the package to your game, then change the activity class to your games .main.activity.
3. In the When Running App block, click on the configure button, then select your game in the plugin. Then exit it back to Automate.
Save by clicking Done. You can then edit the properties ( instead of flowchart ) to change the scripts name & description.
Now try out your shortcut on your desktop!
If you upload it to automate community, please include "Thanks DeepPurple72 !" in the description.
*** UPDATE: I noticed after updating the game from playstore, the script kept running after exiting the game & trying to launch it again gave a toast message about automate cannot parallel launch....
*** FIX: Go into AUTOMATE and STOP the script. Then edit the flowchart:
Edit Block #7 ( the processes running plugin ) - click on configure, long press on the
App name & remove, then + ADD the game again from the Installed Apps list.
Save the script, and all is good again. You may need to do this every time you update a game.
PLEASE CLICK THE THANKS BUTTON IF MY SOLUTIONS HAVE WORKED FOR YOU.

Xposed modules continue to run while the data folder is renamed, but you will get an error message if you open xposed installer or change modules settings.
If you have issues, try the toggle script to ensure xposed installers's data folder has its original name.
I am running samsung touchwiz stock rom , deodexed, android lollipop 5.0.2 with unofficial xposed framework for Samsung v83 sdk21 (found also on this XDA website)
If for some some reason your version of xposed installer is using a different folder name under /data/data and the above scripts do not work for you, please
post the name of your xposed installer's /data/data folder's name so that I may update the scripts and re-upload them to the automate community to share.
:good: :laugh:

Netmarble hates Xposed: THE SOLUTION
DeepPurple72 said:
Xposed modules continue to run while the data folder is renamed, but you will get an error message if you open xposed installer or change modules settings.
If you have issues, try the toggle script to ensure xposed installers's data folder has its original name.
I am running samsung touchwiz stock rom , deodexed, android lollipop 5.0.2 with unofficial xposed framework for Samsung v83 sdk21 (found also on this XDA website)
If for some some reason your version of xposed installer is using a different folder name under /data/data and the above scripts do not work for you, please
post the name of your xposed installer's /data/data folder's name so that I may update the scripts and re-upload them to the automate community to share.
:good: :laugh:
Click to expand...
Click to collapse
Very cool! I've been meaning to register here at xdadevelopers for some time now.... my need to deliver a heartfelt THANK YOU has provided me with a good reason!!! :laugh:

Hey, so I downloaded Automate, and your Future Fight scripts. I've tried using the second one you mention (the one that toggles on/off), but it won't let me launch the game. The script executes properly, renaming the Xposed folder to have an additional '2', but I'm getting a "Security Alert(code : 2) [GameKiller2]" error. Any idea?

Logue1021 said:
Hey, so I downloaded Automate, and your Future Fight scripts. I've tried using the second one you mention (the one that toggles on/off), but it won't let me launch the game. The script executes properly, renaming the Xposed folder to have an additional '2', but I'm getting a "Security Alert(code : 2) [GameKiller2]" error. Any idea?
Click to expand...
Click to collapse
My scripts are for the "Xposed security alert code 2 error"....
Your message is for "gamekiller", not xposed....
Your game is detecting gamekiller cheat.... you could try exiting gamekiller & starting your game.
I dont use gamekiller personally, but have a similar app called gameguardian, which if I try to run it & launch a netmarble game, the game gives some kind of error - basically, the games uses some kind of online "anti-cheats" blacklist. So long as gameguardian is NOT running, the games I play dont detect it.
If you use any "game cheats" apps ( memory debuggers/editors ), the games will most likely detect them if the cheat app is running in memory ( maybe it autostarts on your device? ). Try to open your "cheat" app, in your case GameKiller2 ( maybe a floating widget icon on your homescreen if its running?), and QUIT it. Then try to launch your game.
If it still gives GameKiller2 error, uninstall GameKiller2, and install GameGuardian instead.
If Gguardian is running, you can exit it from its Settings icon, EXIT. Usually when gguardian is running, there is a floating GG icon you can click on.... GG works fine for me and again, i dont get any game errors so long as GG is inactive. Btw, its free & no ads, and works great!
you can DL gguardian here: https://gameguardian.net/download

*** UPDATED the TOGGLE XPOSED ON/OFF script 7/13/2016 ***
Some users may have experienced this issue:
There turned out to be a case, where if you Toggled OFF ( renamed xposed data folder ) and restarted your device, upon startup Xposed Installer creates a new folder if it thinks its "missing" due to it being renamed...
I have updated the script to handle the duplicates folders case. If there are 2 folders, it will delete the new folder, rename the old folder, and show a toast message - basically, removing the duplicate, restoring original folder, with xposed toggled on. The script can now toggle off/on again as normal.
I have tested the updated script, and verified it is working & handles duplicate folders!
It has been uploaded to Automate Community, Games Category, with the TITLE:
"bypass XPOSED Security Alert Code 2 (UPDATED)"
*note: after downloading & installing the new updated script, (1) remove the old shortcut from your homescreen (2) delete the old script from automate (3) create a new shortcut on your homescreen...
*** to create shortcuts for automate scripts:
In automate, EDIT the flowchart
click on the 1st block ( flow beginning block ),
then click on the Install Homescreen Shortcut button
(Then click OK or CANCEL, and DONE to exit the editor)

It kills my exposed and Gravitybox, why? How to avoid?

when i start.
1 of the block fail
it said "fail java. lang. securityexception: missing com.llamalab.automate.permission.SUPERuser_shell"
what can i do.
from seven knights

Notice the error contains superuser:
You are missing superuser priviledges. You must be rooted, and give the automate script superuser rights in automate. Script requires rooted superuser privileges or it will not work!

The toggle script may work with other games not by netmarble, that also detect xposed.... will test later and post results...

script error
I'm getting java.lang.IllegalStateException: cd failed when it tries to run shell command superuser. Please advise.

jxlah said:
I'm getting java.lang.IllegalStateException: cd failed when it tries to run shell command superuser. Please advise.
Click to expand...
Click to collapse
Are you rooted, and is busybox installed? Did you allow superuser to run automate?
cd is a change directory command...
you could use a TERMINAL app such as TERMUX or similar to test the 'cd' command to see if it can access root only folders/files: or try a root file manager app and see if you can access /data/data folder
in terminal, try:
su (press enter)
cd /data/data (press enter)
* if you get an error, it is a superuser permission issue.
Do have xposed installer v3.0 installed?
Did you ( in automate app ) allow the permissions required to run this script?
Sounds like either a superuser priviledge error or xposed installer is in a different location.
xposed installer is in the /data/data directory - use a root file manager to check on it.

DeepPurple72 said:
Are you rooted, and is busybox installed? Did you allow superuser to run automate?
cd is a change directory command...
Do have xposed installer v3.0 installed?
Did you ( in automate app ) allow the permissions required to run this script?
Sounds like either a superuser priviledge error or xposed installer is in a different location.
xposed installer is in the /data/data directory - use a root file manager to check on it.
Click to expand...
Click to collapse
Yes, I am rooted, busybox installed and permissions/su granted. Xposed is installed, or I wouldn't get that error.
Directory is correct as well. Game works when I rename it manually But the script just gives that error. Is terminal emulator required?

jxlah said:
Yes, I am rooted, busybox installed and permissions/su granted. Xposed is installed, or I wouldn't get that error.
Directory is correct as well. Game works when I rename it manually But the script just gives that error. Is terminal emulator required?
Click to expand...
Click to collapse
Hmmm.... strange. No, terminal is not needed.
Based on what you say, sounds like automate....
are the services turned on in system settings? Under accessibilty, direct access.
i have universal switch & accessibilty turned on
Try deleting the toggle script, redownload it from automate communtiy games, and allow permissions if necessary. Let me know what happens.
Does /data/data/de.robv.android.xposed.installer exist?
Rename folder to de.robv.android.xposed.installer then try script....
Are you running rootcloak, roothide, or similar xposed modules?
If so, could they be interfering with automate?
What rom are you running?

DeepPurple72 said:
Hmmm.... strange. No, terminal is not needed.
Based on what you say, sounds like automate....
are the services turned on in system settings? Under accessibilty, direct access.
i have universal switch & accessibilty turned on
Try deleting the toggle script, redownload it from automate communtiy games, and allow permissions if necessary. Let me know what happens.
Does /data/data/de.robv.android.xposed.installer exist?
Rename folder to de.robv.android.xposed.installer then try script....
Are you running rootcloak, roothide, or similar xposed modules?
If so, could they be interfering with automate?
What rom are you running?
Click to expand...
Click to collapse
Yes, services are on. I'm on LG G4, so direct access isn't an option there. Maybe that is why it doesn't work. Oh well, thank you so much for the help. I'll just do it manually if nothing can be done. It's still a great find, a little troublesome but at least i still get to play my game

Lol. Yes, at least you can play with xposed. Idk why the toggle script doesnt work on yours....
i find it odd you can manually rename folder, but get some kind of shell error using automate...
unless your device has some kind of security setting or app preventing it, the script should work.
Im running lollipop 5.02.... which version android are you running?
The script just uses check if folder exists, rename /data/data/folder_name commands. And toast messages. Thats all.
Script requires ( in automate ) 2 installed privileges: superuser & read sd card.
are these privileges installed & enabled for the toggle script?
Perhaps the script cant read root/system folders/files and gives error.
* in addition, your supersu must grant automate root privileges also.
there is no cd command being used.... i will research your error....
Question? Are you using SuperUser or SuperSU app, or are you running a custom ROM?
Im running SuperSU on stock rom.... i read superuser or built-in superuser on custom roms may not work well with automate. If you dont have SuperSU, perhaps try that.
Another thing that could cause java.lang.IllegalStateException errors is if you have multiple profiles on android... you must be primary user.

bitye said:
It kills my exposed and Gravitybox, why? How to avoid?
Click to expand...
Click to collapse
The script disables xposed installer!!!!! Did you read all the previous posts, lol!
With the xposed installers data folder renamed, any modules that try to use
the xposed installers data folder ( or running xposed installer ) while "toggled off"
Will cause errors!!!!! Simply toggle "on" xposed, and all should work fine, without rebooting.
That is the price you must pay to keep xposed installed without reboots,
in order to play netmarble games / or other apps that detect xposed installer installed...
there is no other way. Cant have your cake and eat it too as the saying goes.

MagiskSU version of su fails, saying "Permission denied"

I recently had a problem (see here) with SuperSU, so I decided to give MagiskSU a try. As it turns out, it seems to have the same issue. When I run a process that requires su, it stalls for a while. In the case of MagiskSU, I then get "Permission denied" after about 20 seconds.
Here's what I get with a few basic commands:
Code:
[email protected]:/ $ su
Permission denied
Code:
[email protected]:/ $ su -v
8:MAGISKSU (topjohnwu)
Code:
[email protected]:/ $ su -V
8
Additionally, when I view the log with adb logcat, I see the following message attributed to su:
Code:
exec am failed with 2: No such file or directory
It looks like this is a message produced here, related to loading am.jar. Unlike in my SuperSU situation, this error happens regardless of whether Magisk is set to "prompt" or "grant".
Any idea how I can debug this? Thanks in advance.

Just to make sure: Have you updated the Magisk Manager so that it's just not the stub installed by the Magisk zip?
And if so, does the Manager report you're properly rooted?

I figured it out. In a previous cleanup attempt, I failed to restore the link named /system/bin/app_process that points to /system/bin/app_process64. This fixed it:
From the TWRP terminal:
Code:
mount /system
cd /system/bin
ln -s app_process64 app_process
Frankly I'm surprised this didn't render my phone unbootable! Nothing else was noticeably affected.

I have the same problem, just logcat says:
W/Magisk: su: request rejected (2000->0)

I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.

I found in the Magisk app under Superuser that "shell" had the toggle turned off. Once I turned it on, su worked in ADB.

Lletfrix said:
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
Click to expand...
Click to collapse
You are my Hero...
:good::good::good:Thank You Very Much brooo... :good::good::good:​

Hi all,
I have Magisk v18.1 and I'm also trying to get root access from shell. When I run 'su' in a terminal emulator, I get the message 'Permission denied'.
I did install "ADB & Fastboot for Android NDK" as suggested above. I also checked the root options in the magisk app (v7.0.0) and they are all the default, nothing unusual there.
Could you kindly advice if there is anything I can do in order to get root access from the shell with Magisk?
Thanks a lot in advance

I have a same issue on kitkat

Oh boy, I have *absolutely no idea* what I did but it works now. Well, what I did was that I removed the adb & fastboot module and rebooted. When I ran 'su' again in the terminal, I got a request from magisksu to grant authorization. Not sure what's going on, but it works!

geo909 said:
Oh boy, I have *absolutely no idea* what I did but it works now. Well, what I did was that I removed the adb & fastboot module and rebooted. When I ran 'su' again in the terminal, I got a request from magisksu to grant authorization. Not sure what's going on, but it works!
Click to expand...
Click to collapse
Why did you install the ADB and fastboot module? That's for using that device to control ADB and fastboot of another device as if the device with the module were a computer.

madbat99 said:
Why did you install the ADB and fastboot module? That's for using that device to control ADB and fastboot of another device as if the device with the module were a computer.
Click to expand...
Click to collapse
Honestly, that was a classic case of not knowing what I'm doing and just blindly following what other people tried. But good to know what the purpose of that module was, I was wondering!

Hint: Perfdump is the adb shell program, do not disable SU for it
I add my hint: after getting this error message, I checkd the list of apps in Magisk SU: it turned out that I had disabled the "Perfdump" app, because I did not know what it was. It is the adb shell indeed!

I had exactly the same problem on my Android 6.0 with Magisk v19.3 + Magisk Manager v7.3.1. I tried everything, what you wrote (enabled, disabled the "ADB and fastboot" stuff, checked the symlink, ...), but nothing helped me. FYI: previously, I used LineageOS 16 (Android 9.0) on the same phone with this latest Magisk without any problem (but I decided to turn back to the original OS version to avoid instabilities). But now I'm fighting with this dragon.
My wife has Android 6.0 also w/ Magisk, but she got Magisk v18.0 and this works well now... I tried this at me, and surprisingly, that was worked well. Now, I decided to find out, which is the last working version, where is the bug.
The results:
* the Magisk v18.0 with the bundled Magisk Manager - GOOD
* the Magisk v18.0 with the latest Magisk Manager v7.3.2 - GOOD
* the Magisk v18.1 with the latest Magisk Manager v7.3.2 - GOOD
* the Magisk v19.0 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.1 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.2 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.3 with the latest Magisk Manager v7.3.2 - BAD
I don't know, the freshest working Magisk v18.1 + Magisk Manager v7.3.2 is a good combination for all cases, but looks working.

Lletfrix said:
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
Click to expand...
Click to collapse
Yup thanks it still works up to date

Solved
i had the same problem on my redmi note 7 and the most easiest way is unistall your magisk 20.xxx and install a older one 19.xxx and that should do it but remember bouth zip file (flashibile zip) and magisk apk has yo be older than 20.xxx becouse the devs has made a mistake in the coding( or at leat this is what i think hope im wrong)

just update the magisk manager and install automatically the boot and reboot the phone it will be okay

Solution that works for me GalaxyS9 (starlte)
### restart adbd as root
adb root
### then
adb shell
### WORKS.
### I see '#' in prompt, `whoami` responses: 'root'
### My Magisk version. Reported by `su -v`
23.0:MAGISKSU

[BUG] MagiskHide does not work on Hanabank app. (strace log attached)

Hello, everyone.
Few days ago, I found Hanabank app (com.hanabank.ebk.channel.android.hananbank) detects Magisk hide. I ran strace against Hanabank app, and I got some suspicious openat(2) returns -EACCES and even some files are not filtered by Magisk Hide (returns file descriptor successfully)
Here are openat(2) calls which don't look good.
Code:
[pid 27855] openat(AT_FDCWD, "/sbin_orig/magisk", O_RDONLY|O_LARGEFILE) = 91
[pid 27855] openat(AT_FDCWD, "/dev/magisk/mirror/system", O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied)
[pid 27855] openat(AT_FDCWD, "/magisk", O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied)
[pid 27855] fstatat64(AT_FDCWD, "99-magisk.sh", {st_mode=S_IFREG|0755, st_size=2011, ...}, 0) = 0
Full strace log of Hanabank app:
Code:
https://pastebin.com/BUiViAbK
I think they should return -ENOENT to pass that magisk detection routine.
I'm using Magisk v14.0
BTW, why Magisk Github issue tracker is disabled?

Having the same issue but with another app.
https://forum.xda-developers.com/showpost.php?p=73968022&postcount=19348
How did you run strace? I used strace -f -p PID-o /sdcard/strace.txt but no reference to Magisk is shown.

olivercervera said:
Having the same issue but with another app.
https://forum.xda-developers.com/showpost.php?p=73968022&postcount=19348
How did you run strace? I used strace -f -p PID-o /sdcard/strace.txt but no reference to Magisk is shown.
Click to expand...
Click to collapse
First, sorry for late reply. I was on vacation.
I used this script to attach strace to fresh app process.
Code:
while true; do
while ! ps | grep -q -i $1; do :; done;
ps | grep -i $1 | while read a b c; do
strace -e open -f -e trace=file,ptrace -p $b 2>&1;
done;
done
For example, if you saved this script as /sdcard/strace.sh, The procedure I take to attach strace to the app is;
1. use killall command to kill all app process. Android pre-forks app, so we need to kill that first.
2. run script using sh /sdcard/strace.sh <app_process_name>. This will attach strace to the app and redirects strace's stderr output to stdout.
2-1. Do whatever you want (use tee or just redirect it to file, etc..) with stdout stream.
3. Analyze collected result.
That's all.

perillamint said:
First, sorry for late reply. I was on vacation.
I used this script to attach strace to fresh app process.
Click to expand...
Click to collapse
Hi
Just now I realised that I responded in the other thread. However your script never worked
I ran the script in a shell with root permission using
Code:
sh /sdcard/strace.sh com.barclays.android.barclaysmobilebanking
Unfortunately this is what I get when I try to run the script
Code:
/sdcard/strace.sh[5]: syntax error: 'done' unexpected
What have I done wrong?
EDIT: I've done this test on another device, a Nexus 5X stock 7.1.2 + Magisk v14. If I run strace it is not found, I have installed busybox but nothing! WAT??? I'll test with the other device later which has strace (Nexus 5).
EDIT2: Nope, I get the same error on the device which has strace.

olivercervera said:
Hi
Just now I realised that I responded in the other thread. However your script never worked
I ran the script in a shell with root permission using
Code:
sh /sdcard/strace.sh com.barclays.android.barclaysmobilebanking
Unfortunately this is what I get when I try to run the script
Code:
/sdcard/strace.sh[5]: syntax error: 'done' unexpected
What have I done wrong?
EDIT: I've done this test on another device, a Nexus 5X stock 7.1.2 + Magisk v14. If I run strace it is not found, I have installed busybox but nothing! WAT??? I'll test with the other device later which has strace (Nexus 5).
EDIT2: Nope, I get the same error on the device which has strace.
Click to expand...
Click to collapse
Hmm, I used sh which included in LineageOS.... I think Android's default sh couldn't handle that script's syntax properly. Default sh is quite crippled compared to GNU/Linux's one (bash, zsh, etc..)
Could you try running this script using bash instead of sh? If you don't have bash on your Android system, this Magisk module could inject bash binary into your system. https://forum.xda-developers.com/apps/magisk/module-magisk-bash-shell-t3609988

perillamint said:
Hmm, I used sh which included in LineageOS.... I think Android's default sh couldn't handle that script's syntax properly. Default sh is quite crippled compared to GNU/Linux's one (bash, zsh, etc..)
Could you try running this script using bash instead of sh? If you don't have bash on your Android system, this Magisk module could inject bash binary into your system. https://forum.xda-developers.com/apps/magisk/module-magisk-bash-shell-t3609988
Click to expand...
Click to collapse
Thanks for your suggestion. In the end I installed LOS on my test device and ran the script.
The funny thing is that I can't find a single reference to Magisk or Root...
The output is attached.

olivercervera said:
Thanks for your suggestion. In the end I installed LOS on my test device and ran the script.
The funny thing is that I can't find a single reference to Magisk or Root...
The output is attached.
Click to expand...
Click to collapse
Indeed. However the app dies shortly after reading the two property files:
/dev/__properties__/ubject_r:default_prop:s0
/dev/__properties__/ubject_r:logd_prop:s0
I would try to get the output of getprop with and without Magisk installed and see if there are any properties being leaked that could give a hint that Magisk is installed.

Fif_ said:
Indeed. However the app dies shortly after reading the two property files:
/dev/__properties__/ubject_r:default_prop:s0
/dev/__properties__/ubject_r:logd_prop:s0
I would try to get the output of getprop with and without Magisk installed and see if there are any properties being leaked that could give a hint that Magisk is installed.
Click to expand...
Click to collapse
You are the man! You definitely spotted the method being used by this app. Thanks.
I had to leave LOS ROM because even without Magisk it would not run, so I installed another ROM. I verified the app runs, got props, installed Magisk and got new props.
There are all changes:
1. [ro.build.selinux]: [1] is changed to [ro.build.selinux]: [0] when Magisk is installed
2. [ro.runtime.firstboot] shows different values but I believe it's fine
3. The following are entirely missing when Magisk is installed
[selinux.reload_policy]: [1]
[service.adb.tcp.port]: [-1]
[sys.retaildemo.enabled]: [0]
[init.svc.clear-bcb]: [stopped]
I have the feeling that [ro.build.selinux]: [1] and [selinux.reload_policy]: [1] are key elements and Magisk is not hiding them properly. I would suppose these elements show that SELinux is not enforcing anymore. I tried changing these values, but at reboot they don't change.
I know obviously Magisk does not enforce SELinux, but hides that got set to Permissive. System thinks that is enforcing, and using command getenforce i get as a result Enforcing, but Barclays (and possibly other apps) are reading that SELinux is not actually being enforced.
Interesting. Will post these finding in the main thread.
Do you have anything to add that could be helpful?

olivercervera said:
You are the man! You definitely spotted the method being used by this app. Thanks.
I had to leave LOS ROM because even without Magisk it would not run, so I installed another ROM. I verified the app runs, got props, installed Magisk and got new props.
There are all changes:
1. [ro.build.selinux]: [1] is changed to [ro.build.selinux]: [0] when Magisk is installed
2. [ro.runtime.firstboot] shows different values but I believe it's fine
3. The following are entirely missing when Magisk is installed
[selinux.reload_policy]: [1]
[service.adb.tcp.port]: [-1]
[sys.retaildemo.enabled]: [0]
[init.svc.clear-bcb]: [stopped]
I have the feeling that [ro.build.selinux]: [1] and [selinux.reload_policy]: [1] are key elements and Magisk is not hiding them properly. I would suppose these elements show that SELinux is not enforcing anymore. I tried changing these values, but at reboot they don't change.
I know obviously Magisk does not enforce SELinux, but hides that got set to Permissive. System thinks that is enforcing, and using command getenforce i get as a result Enforcing, but Barclays (and possibly other apps) are reading that SELinux is not actually being enforced.
Interesting. Will post these finding in the main thread.
Do you have anything to add that could be helpful?
Click to expand...
Click to collapse
If you use "resetprop ro.build.selinux 1" in a root shell, does the app start?
That will disappear at reboot of course, but it's easy to add to /magisk/.core/props to make it stick until Magisk is fixed.
Now, I don't think Magisk disables SELinux, why do you have it disabled?

Fif_ said:
If you use "resetprop ro.build.selinux 1" in a root shell, does the app start?
That will disappear at reboot of course, but it's easy to add to /magisk/.core/props to make it stick until Magisk is fixed.
Now, I don't think Magisk disables SELinux, why do you have it disabled?
Click to expand...
Click to collapse
Yes, Magisk changes SELinux to Permissive and hides this status.
Although my findings would be legit and those props should be hidden, in my Bank's case is not the issue.
I have discovered that if I uninstall Magisk Manager (but not uninstall root, just the app) my bank app works. However it does not work if I use "Hide Magisk".
Since the hidden app is called Unhide Magisk Manager, probably this app is looking for Magisk keyword.
For whatever reason when I run strace the app does crash and always reports that message (crash after reading prop).
I will post these findings in the support thread.
I don't know how to do it, but I would recompile Magisk Manager changing package ID and name, in theory should work.

I am having the same issue on my Galaxy S8 with the Barclays Mobile Banking app. I have tried using every option in Magisk but nothing seems to be working. In fact, the Barclays app actually asked for SU permissions when I first ran it which is odd to me.
Did anyone find a workaround for this? I read the posts in this thread but I am not savvy enough to understand all the codes and technical information written, so please excuse my ignorance in the matter. Is reverting to a completely stock ROM my only option at this point? I really need to start using this application as soon as possible.
Thank you.

Quick update guys!
The great Topjohnwu is working on a new update that includes a key feature for us: reinstalling Magisk Manager with a random package ID.
These changes are in his Github Repo. On this thread you can find unofficial versions of Magisk compiled from Github.
I have tested Magisk-v14.4-20171102-091345.zip: HELL IT WORKS!
In Magisk Manager: go to settings and you will have the option to reinstall Magisk Manager with a random package ID
Install Barclays from Play Store
Add Barclays to Magisk Hide
Open Barclays, it will behave correctly and will work!
This solves my problem, so I will be able to use the latest version of this app very soon (will wait for public beta).
On a side note, this update should als hide /Magisk partition, which was detected by @perillamint banking app, so might be worth trying it.
I have installed this Hanabank app (hopefully is the right one!) and added it to Magisk Hide. The app opens up correctly but I can't understand anything. I see some stuff moving on screen and on the upper left I see a lock icon (to login?)
If I don't add the app to Magisk Hide it shows an incomprehensible message and closes.
Hope you find this helpful.
Please see photos below.

@olivercervera
What are your exact steps? I installed the latest version from this thread, and added barclays to magisk hide, and then in settings, clicked in hide magisk manager. When I clicked in unhide magisk manager, it asked me for root permision for something with a random name, so I guess it worked, but I couldn't get the Barclays app to run. Is that a fresh install of your phone? I remember that if it detected your root once, it would be blocked forever, until you get a new ID. Did you call barclays to get your app working again?
On top of that, I clicked on hide magisk manager again, and now I can't unhide it, the app does nothing when I click on it... :crying:
Thanks for your help in any case, and thanks for the tip regading the new functionality!

mundodisco8 said:
@olivercervera
What are your exact steps? I installed the latest version from this thread, and added barclays to magisk hide, and then in settings, clicked in hide magisk manager. When I clicked in unhide magisk manager, it asked me for root permision for something with a random name, so I guess it worked, but I couldn't get the Barclays app to run. Is that a fresh install of your phone? I remember that if it detected your root once, it would be blocked forever, until you get a new ID. Did you call barclays to get your app working again?
On top of that, I clicked on hide magisk manager again, and now I can't unhide it, the app does nothing when I click on it... :crying:
Thanks for your help in any case, and thanks for the tip regading the new functionality!
Click to expand...
Click to collapse
Yes, a fresh start from a stock Nexus 5X I have at work. I did not register the app with my account during the test, all I needed to do was to get to the Welcome Screen: if Barclays detects root you don't get anything. Probably you need to reinstall Barclays App.
Once Magisk Manager is hidden with the new ID you can't go back to the original: you don't have any option. So if you still have it means there is a problem.

mundodisco8 said:
@olivercervera
What are your exact steps? I installed the latest version from this thread, and added barclays to magisk hide, and then in settings, clicked in hide magisk manager. When I clicked in unhide magisk manager, it asked me for root permision for something with a random name, so I guess it worked, but I couldn't get the Barclays app to run. Is that a fresh install of your phone? I remember that if it detected your root once, it would be blocked forever, until you get a new ID. Did you call barclays to get your app working again?
On top of that, I clicked on hide magisk manager again, and now I can't unhide it, the app does nothing when I click on it... :crying:
Thanks for your help in any case, and thanks for the tip regading the new functionality!
Click to expand...
Click to collapse
He's talking about a new Hide Manager feature that is much improved from the current implementation. It's not yet available officially, so you'll have to build yourself from the GitHub repo, or download from the unofficial snapshots thread that @olivercervera linked.

Didgeridoohan said:
He's talking about a new Hide Manager feature that is much improved from the current implementation. It's not yet available officially, so you'll have to build yourself from the GitHub repo, or download from the unofficial snapshots thread that @olivercervera linked.
Click to expand...
Click to collapse
I didn't even consider the possibility he didn't realise I was using the unofficial/self compiled version... I even linked it!!!
Thanks

olivercervera said:
I didn't even consider the possibility he didn't realise I was using the unofficial/self compiled version... I even linked it!!!
Thanks
Click to expand...
Click to collapse
It's actually quite apparent that he's talking about the current implementation, since the updated, unreleased, feature doesn't have anything named "unhide" to click.
With the new implementation you unhide the hidden Manager by reinstalling and opening it.

Hi guys,
Yes, I installed the latest version, following the link OliverCervera linked. I hid it using the usual method of going to options/hide magisk, and I got a new app, as usual. clicking on it to unhide prompted for root permissions for an app with a random ID (as expected). The next time, I wasn't that lucky, and the whole thing crashed. Anyway, it's a nightly, so I won't complain, and I will check it later, as sadly I don't have time to do it now.
In any case, my app was marked, because I opened it with the official release of Magisk and it detected root, and once it does, it keeps the "this phone is rooted" status until you do a factory reset. I think you can call them to tell them that it was a mistake, and they can unlock it but I'm not 100% sure about this last point.
Thanks for the work, anyway!

mundodisco8 said:
Hi guys,
Yes, I installed the latest version, following the link OliverCervera linked. I hid it using the usual method of going to options/hide magisk, and I got a new app, as usual. clicking on it to unhide prompted for root permissions for an app with a random ID (as expected). The next time, I wasn't that lucky, and the whole thing crashed. Anyway, it's a nightly, so I won't complain, and I will check it later, as sadly I don't have time to do it now.
In any case, my app was marked, because I opened it with the official release of Magisk and it detected root, and once it does, it keeps the "this phone is rooted" status until you do a factory reset. I think you can call them to tell them that it was a mistake, and they can unlock it but I'm not 100% sure about this last point.
Thanks for the work, anyway!
Click to expand...
Click to collapse
If you install the correct version of the Manager you won't have an unhide app after hiding the Manager. That's changed...
Your problem is probably that the unofficial Manager has a different signature, so it won't install over the official Manager. Solution: Uninstall the official Manager before installing the unofficial snapshot.
Have you tried just clearing all data for the app after it detects root? That usually works for an app that "remembers" root. But, I've never tested the app in question so...

Didgeridoohan said:
If you install the correct version of the Manager you won't have an unhide app after hiding the Manager. That's changed...
Your problem is probably that the unofficial Manager has a different signature, so it won't install over the official Manager. Solution: Uninstall the official Manager before installing the unofficial snapshot.
Have you tried just clearing all data for the app after it detects root? That usually works for an app that "remembers" root. But, I've never tested the app in question so...
Click to expand...
Click to collapse
I think they keep your signature and store it on their servers. Barclays is really focused when it comes to not allowing people to use their app on rooted phones, but as I said, I would need to double check. And I kind of get why they do it, as they went all the way to avoid to pay Android to use Android Pay and they developed their own platform to pay over NFC (not judging here, it's up to them if they think it's the best solution). At the end of the day, root is exploited through a security flaw, and "the bad guys could get your moneys", and even though they could display a message at launch that says "hey, you are rooted, the bad guys could get AAAALLL of the moneys, it's up to you" people would still want to sue them if they mess up... but it's funny that they allow you to get into the online banking web on a rooted phone, where the bad guys could see your password...

remove magisk modules (READ FIRST)

Hi! got my new pixel 3a because i broke my last one. ive rooted and have magisk installed. i tried to install youtube vanced which didnt work because they removed the module so i found it on here somewhere. it wont uninstall. i installed busy box and debloat terminal uninstaller to uninstall youtube and the module and now those wont uninstall. I have 4 modules that ive set to delete and restarted 10 times and no delete. i tried "adb shell magisk --remove-modules" and modules are still there. i cant use twrp because android 10 doesnt have twrp support. SO IF SOMEONE COULD PLEASE tell me how to manually delete magisk modules that would be AMAZING. other suggestions are welcome too!

AudibleDruid said:
Hi! got my new pixel 3a because i broke my last one. ive rooted and have magisk installed. i tried to install youtube vanced which didnt work because they removed the module so i found it on here somewhere. it wont uninstall. i installed busy box and debloat terminal uninstaller to uninstall youtube and the module and now those wont uninstall. I have 4 modules that ive set to delete and restarted 10 times and no delete. i tried "adb shell magisk --remove-modules" and modules are still there. i cant use twrp because android 10 doesnt have twrp support. SO IF SOMEONE COULD PLEASE tell me how to manually delete magisk modules that would be AMAZING. other suggestions are welcome too!
Click to expand...
Click to collapse
Modules are installed in /data/adb/modules/.
1. Get into that directory.
2. Identify the modules you want to remove.
3. Write down the respective DIRECTORY NAMES, separated by spaces.
4. On a root terminal, paste and run:
Code:
cd /data/adb/modules; for module in NAMES FROM STEP 3; do test -d $module || continue; (sh $PWD/$module/uninstall.sh) 2>/dev/null; rm -rf $module; done

[Temp ROOT] - [BOOTLESS MAGISK] - [UNLOCK/MAGISK/TWRP] FireTV 2nd gen Cube (raven) > PS7624

Overview
This rooting method is based on a vulnerability in the ARM Mali GPU driver (CVE-2022-38181) discovered by security researcher Man Yue Mo at GitHub Security Lab, to gain root access to the 2nd gen Cube that is on firmware PS7624/3337 or older. Newer method for PS7633 and PS7646 here.
The exploit program (raven_shrinker) is run directly on the Cube to spawn a temporary root shell for quick access. It can also be run automatically on every boot in combination with @diplomatic's bootless Magisk script to grant apps root access. Cubes that are on firmware PS7292/2984 or older, are able to use @Functioner's bootloader exploit used in the previous Raven Root bootloader unlock to install TWRP & full Magisk without a DFU device.
For best results, run raven_shrinker 30-90sec after boot up, when loading is complete and the device is idle.
Three options for root depending on your needs & comfort level
1) Temporary ADB root - Open an adb root shell to for quick access (PS7624/3337 or older)
Pros:
Access all files and folders from ADB
Simple to use, runs in RAM and doesn't make any changes to the Cube, no chance of bricking.
Remove app package protection so that you can enable/disable any app even without root (eg custom launchers, disabling updates, debloat, etc).
Cons:
Only enables ADB root
raven_shrinker occassionally crashes/reboots the Cube when being run. Run it 30-90sec after bootup for greater reliability.
NOTE: raven_shrinker won't brick your device, but what you do with that root access can. DM-verity is still in place checking the integrity of the system/vendor partitions, do NOT modify anything in those directories, or the boot partition!!
2) Bootless Magisk - Automatically start a lite version of Magisk that runs entirely from the data partition, (PS7624/3337 or older).
Pros:
Both ADB root and ability to grant root to apps through Magisk Manager
Once the Magisk dameon has started, root can be granted stably whenever needed
Doesn't modify boot or system/vendor partitions, DM-verity is preserved
Cons:
This is experimental, use at your own risk! It's been working stably during my testing but it's impossible to foresee every issue.
Still relies on raven_shrinker to start, and may occasionally crash when raven_shrinker runs at boot
Most Magisk modules don't work.
NOTE: Be careful of what apps you give root access to. Giving root access to an app that modifies the boot, system or vendor partitions will brick your device. Again, DM-verity is still actively checking that no changes have been made to system/vendor directories.
3) Bootloader Unlock - Install Magisk & TWRP, and enable many more features (PS7292/2984 or older)
Pros:
Use the latest version of Magisk, with Zygisk & module support
Use TWRP for backups & upgrades
Unrestricted use of Fastboot and the U-Boot command line (Amlogic Update)
Only requires raven_shrinker for the initial installation, more stable and tested than bootless Magisk
Remap Cube buttons to allow booting to fastboot, TWRP, Amlogic update.
Possible to update firmware to PS7624/3337 through TWRP and keep device unlocked
Cons:
There is no recovery option in case of a brick.
Requires older firmware to work
NOTE: It's very important to NEVER allow the Amazon OTA app to update the firmware. NEVER run the factory reset option in FireOS settings. If either of these occur, the Cube will be bricked.
Contributors:
Man Yue Mo, @Functioner, @Pro-me3us
Thanks to @Michajin & @mavsman13 for testing & feedback
Thanks to @diplomatic for bootless Magisk script, and @SweenWolf for Launcher Manager
Thanks to @Renate for many great tools
Thanks to all the folks who have worked on TWRP & Magisk

Temporary ADB root (PS7624/3337 or older)
Disclaimer: Use this at your own risk, I'm not responsible for any data loss or corruption to your device. There is a nonzero chance of bricking the Cube, and little to no recovery options.
Instructions
Enable ADB debugging in FireOS settings
Download, unzip and copy raven_shrinker to your Cube
Code:
adb push raven_shrinker /data/local/tmp/
Give raven_shrinker execution permission (only needs to be done once)
Code:
adb shell
chmod +x /data/local/tmp/raven_shrinker
Run the program
For best results, run raven_shrinker 30-90sec after boot up, when loading is complete and the device is idle.
Code:
adb shell
/data/local/tmp/raven_shrinker
NOTE: Some functions do not work with this root shell. Services can't be accessed, so package manager 'pm' commands can't be run as root. However, package protections can still be removed so that you can enable/disable any app without root. Use bootless Magisk option if you need to access services as root.
How to disable package protection
Use raven_shrinker to open a root shell and delete all the apps listed in the file /data/system/PackageManagerDenyList
Code:
echo '<?xml version="1.0" encoding="utf-8" standalone="yes" ?><map><set name="DenyListKeyPackages"></set></map>' > /data/system/PackageManagerDenyList
Exit out of the root shell, and clear Arcus Proxy
Code:
exit
pm clear com.fireos.arcus.proxy
A reboot is required before the changes take effect, but FireOS will attempt to connect to Amazon servers on bootup and rebuild PackageManagerDenyList. Temporarily disable your internet, so that the Cube can't connect to the internet, then reboot.
Package protections are now removed, and Arcus Proxy needs to be disabled to prevent it from being re-activated
Code:
pm clear com.fireos.arcus.proxy
pm disable-user com.fireos.arcus.proxy
Re-enable your Internet. You should now be able to enable/disable any app. Verify that any apps you disable are actually disabled. Then reboot, and verify again!
Code:
pm list packages -d
It's strongly recommended that you disable updates immediately
Code:
pm disable-user com.amazon.device.software.ota
pm clear com.amazon.device.software.ota
pm disable-user com.amazon.device.software.ota.override
pm disable-user com.amazon.tv.forcedotaupdater.v2
Changelog:
v1.1 April 23th, 2023​
Fix for PS7608/3614
v1.2 May 4th, 2023​
added support for PS7206/1098
v1.3 June 23rd, 2023​
added support for PS7201/942

Bootless Magisk (PS7624/3337 or older)
These instructions use an adapted version of @diplomatic's bootless Magisk script, it's recommended you read the original post to better understand how it works, and it's limitations.
Disclaimer: Use this at your own risk, we're not responsible for any data loss or corruption to your device. There is a nonzero chance of bricking the Cube, and little to no recovery options.
There are two reports of a possible compatibility issue with PS7614/3227, so we aren't recommending this method for that firmware at this time.
Instructions
Enable ADB debugging in FireOS settings
Download raven_bootless_magisk, unzip it, and copy it to your Cube keeping the same directory structure
Code:
adb shell mkdir /data/local/tmp/bin
adb push raven_bootless_magisk/* /data/local/tmp/
adb shell pm install -r /data/local/tmp/magisk_manager.apk
Give scripts & binaries execution permissions
Code:
adb shell
chmod +x /data/local/tmp/start.sh
chmod +x /data/local/tmp/magisk-boot.sh
chmod +x /data/local/tmp/bin/raven_shrinker
chmod +x /data/local/tmp/bin/magiskinit
Install Launcher Manager on your Cube, open, navigate to 'other settings', 'ADB Commands'
Tap on the + icon in the top right corner to create a new command
Enter Name: Start Magisk
Enter Command: sleep 30 && /data/local/tmp/start.sh
Check 'Execute on Boot'
Save
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When you reboot your Cube, bootless Magisk will automatically start ~30sec after your homescreen loads. It's important that FireOS has loaded and that the device isn't busy, so don't open any apps until after Magisk has loaded. There's a greater chance that raven_shrinker will fail or reboot the Cube while launching Magisk if the device is busy.
TO AVOID BRICKING YOUR DEVICE:
Be careful of what apps you give root access to. Giving root access to an app that modifies the boot, system or vendor partitions will brick your device. DM-verity is still actively checking that system/vendor directories haven't been tampered with.
Don't run the boot-magisk.sh script (from either ADB or Launcher Manager) more than once per boot. Doing so will mess up the mounting and module initiation.
Never toggle ADB debugging off/on in the Developer's menu while Magisk is running. This will kill the Magisk daemon running in the background, and could corrupt your device if it's in the middle of an important process.
Only use WiFi ADB, not USB ADB. Booting the Cube with an USB attached computer puts USB in device mode, and ADB will close and kill Magisk when the Cube sleeps in device mode.
This release includes Magisk v21.4 (magiskinit) and Magisk Manager v8.0.7. Don't update Magisk! Patching your boot image will brick your device!
Changelog:
v1.1 April 23th, 2023​
Fix for PS7608/3614
v1.2 May 4th, 2023​
Added support for PS7206/1098
v1.3 June 23rd, 2023​
Added support for PS7201/942

Bootloader unlock, install TWRP & Magisk (PS7292/2984 or older)
This rooting method will put your Cube on the same exploit and software versions used in the original Raven Root, without a DFU recovery option. Please post any questions or problems regarding this post & it's process, on the Raven Root thread.
Disclaimer: Use this at your own risk, I'm not responsible for any data loss or corruption to your device. There is a nonzero chance of bricking the Cube, and little to no recovery options.
NEVER FACTORY RESET YOUR CUBE!!!
NEVER ALLOW AN AMAZON OTA UPDATE!!!
Both of these will brick your Cube!
To avoid any potential conflicts, if you were previously using a different version of Magisk, such as bootless Magisk (v21.4), first delete /data/adb/magisk.db before proceeding.
Instructions
Enable ADB debugging in FireOS settings
Download the raven_root_shrinker, unzip, and copy the 7 files to /data/local/tmp on the Cube
Code:
adb push raven_root_shrinker/* /data/local/tmp/
Give raven_shrinker & install script executable permissions
Code:
adb shell
chmod +x /data/local/tmp/raven_shrinker
chmod +x /data/local/tmp/install_root.sh
Open a root shell and run the install_root.sh script
Code:
adb shell
/data/local/tmp/raven_shrinker
/data/local/tmp/install_root.sh
Finish by typing 'exit' to switch root back to regular shell, install Magisk Manager, and reboot to TWRP
Code:
exit
pm install -r /data/local/tmp/magisk.apk
reboot recovery
The Cube will reboot to TWRP, automatically flash Magisk and Amazon OTA blocker module, then reboot back to FireOS.
NOTE: It's very important to NEVER allow the Amazon OTA app to update the firmware. NEVER run the factory reset option in FireOS settings. If either of these occur, the Cube will be bricked.
Read here for TWRP firmware flashing instructions
Changelog:
v2.2.1 April 23th, 2023​
Added additional Magisk script to help prevent user from accidentally initiating FireOS factory reset.
If you already installed v2.2, you can copy and paste the following as one ADB command to add this script to your Cube:
Code:
echo '#!/sbin/sh
# Rename misc partition
mv /dev/block/misc /dev/block/misc_real
# Create symbolic links
ln -s /dev/null /dev/block/misc' > /data/adb/post-fs-data.d/misc_hide.sh && chmod +x /data/adb/post-fs-data.d/misc_hide.sh
v2.2.2 May 4th, 2023​
Added support for PS7206/1098
v2.2.3 June 23rd, 2023​
Added support for PS7201/942

reserved

to bad: mine was already on PS7633/3445

Hey @Pro-me3us . I've been trying to use the 2.2 update with no luck. My cube is on version PS7292/2984. I keep getting the message "/data/local/tmp/raven_shrinker: can't execute: Permission denied." Not sure what I'm doing wrong. Any help would be greatly appreciated.

coltxL2717 said:
Hey @Pro-me3us . I keep getting the message "/data/local/tmp/raven_shrinker: can't execute: Permission denied."
Click to expand...
Click to collapse
I didn't need to change the permissions on raven_shrinker while testing, but maybe that's different on other firmware versions.
Try this:
Code:
chmod +x /data/local/tmp/raven_shrinker
This will give the file execution permission. Let me know if that works, then I'll add it to the instructions. You only need to do this once for that file.
You may also need to do the same for install_root.sh in that case. Try running it first without, and if needed use:
Code:
chmod +x /data/local/tmp/install_root.sh

Pro-me3us said:
I didn't need to change the permissions on raven_shrinker while testing, but maybe that's different on other firmware versions.
Try this:
Code:
chmod +x /data/local/tmp/raven_shrinker
This will give the file execution permission. Let me know if that works, then I'll add it to the instructions. You only need to do this once for that file.
You may also need to do the same for install_root.sh in that case. Try running it first without, and if needed use:
Code:
chmod +x /data/local/tmp/install_root.sh
Click to expand...
Click to collapse
That did it. Thank you so much. I had to chmod both files for the root to work.

coltxL2717 said:
That did it. Thank you so much. I had to chmod both files for the root to work.
Click to expand...
Click to collapse
Thanks for confirming, added granting executable permissions to the instructions

How to block future updates?

errut said:
How to block future updates?
Click to expand...
Click to collapse
Post #2 (needs root). unless you are on PS7633/3445 +, then you have to do it on a network router blocking the OTA webwites.

Good afternoon . I would like to clarify whether it is possible to install TWRP on my Cube?

teschke said:
Good afternoon . I would like to clarify whether it is possible to install TWRP on my Cube?
Click to expand...
Click to collapse
Yes, your firmware is older than PS7292 so you can use these instructions
This will install TWRP 3.7.0-9.0 + Magisk 25.208.

Hi all,
where can I DL "The exploit program (raven_shrinker") ?

u_no_fr said:
Hi all,
where can I DL "The exploit program (raven_shrinker") ?
Click to expand...
Click to collapse
It's part of each of the three methods listed in the OP
1) Temporary root (raven_shrinker only)
2) bootless Magisk
3) bootloader unlock
Check the post attachments

Hi,
Thanks for posting this.
I have two Gen 2 Cubes that are on Fire OS 7.2.4.2 (PS7242/2906). Both have updates blocked.
If I installed TWRP and Magisk, what can I do? Are there and roms you recommend I install?
Sorry for asking. I have installed roms on old Samsung and LG phones but never done anything like this on Fire TV products.
Thanks

Osaka_23 said:
I have two Gen 2 Cubes that are on Fire OS 7.2.4.2 (PS7242/2906). Both have updates blocked.
If I installed TWRP and Magisk, what can I do? Are there and roms you recommend I install?
Click to expand...
Click to collapse
There aren't any custom ROMs for the Cube at the moment. TWRP would let you update to PS7624/3337 while maintaining root, but honestly I don't see a whole lot of benefit to the post PS7273 firmware. There are a handful of small new features, nothing particularly great IMO.
Magisk might actually have more of a functional benefit for you. With that you can grant apps root, and use modules. Exposed Edge is very nice, and will let you completely remap your remote buttons, including double and tripple clicks, overlays, shortcuts, etc. You can change the bootup logo, use file explorers with full system access etc. TWRP/Magisk are just the tools, what you do with them is up to you

Hello Pro-me3us, my cube is running PS7633/3445. I followed the instructions #2 to Temporary ADB root (PS7624/3337 or older)
I was able to push the file (or i had to push the folder???)
Well, then after
raven:/ $ /data/local/tmp/raven_shrinker
fingerprint: Amazon/raven/raven:9/PS7633.3445N/0027347744000:user/amz-p,release-keys
/data/local/tmp/raven_shrinker: flags_change failed
: Invalid argument
what can i do now?
any help ?
thanks
Note: the file was pushed because:
1|raven:/ $ cd /data/local/tmp/
127|raven:/data/local/tmp $ ls
raven_shrinker

yakovperelman69 said:
my cube is running PS7633/3445
Click to expand...
Click to collapse
The vulnerability was patched in PS7633/3445, so it won't work on any firmware newer than PS7624/3337. There's no workaround.