Amazing Temp Root for MediaTek ARMv8 [2020-08-24]

[bjpafa]

Riru core/disapeared from 21.1 Magisk. Installation via Git is a joke 10.0.0.1 Oxige

Is anyone using the Riru Core module? Is it possible? My ignorance of this stuff is showing. My goal is to install Riru so I can then install EdXposed, then, hopefully a few modules.

I installed Riru Core via Magisk Manager, rebooted, and now when I run the script to root, my device freezes and requires a hard reboot (PWR&VOL+).

Also, how do I uninstall Riru to get back to just Magisk if I don't have root? I'll just reflash my stock and start from scratch if I have to.

I have problems with activation of web view implementation, modules from browsers disappeared. Thaf was kown. Sistemless via Magisk freezes.
Installed from Git... I have seldom assist to such a sydtemwide problem.
So i am thinking format system etc,
Two more consistent tries and FtheSystem...

Congrats and suggestions ???

 

[Koushiroue]

130|[email protected]:/data/local/tmp $ ./mtk-su
0000000000000000 is not a valid address
UID: 2000  cap: 0000000000  selinux: permissive
[email protected]:/data/local/tmp $

im using vivo v5 , put the mtk-su in the tmp folder, give it chmod 755, and attemped to run it while my phone is on. and i got the output above. any ideas?

$ adb shell
[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ ls
mtk-su
[email protected]:/data/local/tmp $ ./mtk-su
0000000000000001 is not a valid address
UID: 2000  cap: 0000000000  selinux: permissive
[email protected]:/data/local/tmp $ ./mtk-su -v
armv8l machine
param1: 0x1000, param2: 0x8040, type: 7-4
Building symbol table
kallsyms_addresses pa 0x40c97900
kallsyms_num_syms 60749, addr_count 60749
kallsyms_names pa 0x40d0e500, size 719903
kallsyms_markers pa 0x40dbe200
kallsyms_token_table pa 0x40dbea00
kallsyms_token_index pa 0x40dbee00
Patching credentials
Parsing current_is_single_threaded
ffffffc00030d9a0+50: ADRP x0, 0xffffffc00107e000
ffffffc00030d9a0+54: ADD Rd, x0, 0x950
Possible list_head tasks at offset 0x368
comm swapper/0 at offset 0x5f8
Found own task_struct at node 1
cred VA: 0000000000000000
0000000000000000 is not a valid address
Parsing avc_denied
ffffffc0002b2464+20: ADRP x0, 0xffffffc00126c000
ffffffc0002b2464+24: LDR [x0, 0x26c]
selinux_enforcing VA: 0xffffffc00126c26c
Setting selinux_enforcing
Selinux is already permissive
starting /system/bin/sh
UID: 2000  cap: 0000000000  selinux: permissive
[email protected]:/data/local/tmp $

running it with -v verbose got this output
Edit : seeing some vivo phones also got this output as well means mine is also have a modified kernel, hurmmm

 

[LupusCoding]

I have a fire 7 9th gen with build number 0002517057924
Is there any change to get mtk-su working on this build? How can I help with it?

 

[DragonFire1024]

I'll be acquiring a Samsung Galaxy note 3 (SM-A315G). The security patch is October 2020 however I don't get an error that says the firmware is not possible to be adapted, rather it just fails straight up at line one. Doesn't give any real information on why. Don't have the device in front of me at the moment.

 

[bobkaas]

Well, I can confirm that this works on the Acer Iconia one 10. (B3-A50FHD wth MTK MT-8167A on android 8.1) This, along with unlocking the bootloader, also allowed me to gain perm root with magisk. Thanks for the discovery! I'm going to do some tinkering with porting TWRP over to it and see where I can go from there. I'll post my results in a different thread later. Thanks again!

It has been a while but do you remember how you gained permanent root on your aconia 1 10?

 

[YAn Sophearith]

My Oppo a5s not root yet

 

[guadalupeleopard105d1]

Is there any chance of getting root for red pepper ghost phone?

hpp-gs1

If I am not wrong it has a helio p22 mediatek chip.

 

[nikki540615]

I second this also wondering

 

[macgealai]

Hello all. I have a Tinno/Wiko Ride (U307AS), rocking the MT6739 chipset. I have seen this device work for a few of you, verifying with @diplomatic. I just cannot seem to get it going. I used to do a lot of Samsung and Motorola unlocking back in the day using tools like Odin, but now I am running KDE Neon instead of Windows.
In the terminal, with ADB, mtk-su gives me this:

[email protected]:~$ adb devices
List of devices attached
QW7S8TEYMJSWKZMN device
[email protected]:~$ adb push /home/wytdeer/Documents/rootwiko/mtk-su_r23/arm64/mtk-su /data/local/tmp/
/home/wytdeer/Documents...(65144 bytes in 0.037s)
[email protected]:~$ adb shell
U307AS:/ $ cd data/local/tmp/
U307AS:/data/local/tmp $ chmod 755 mtk-su
U307AS:/data/local/tmp $ ./mtk-su -v
Failed critical init step 1
./mtk-su
Failed critical init step 1

Same result or less thru terminal emulator on device.
attached is the CPU-Z verification page to give thorough device info. Help would be fucking tits, from anyone

 

[fr4nk1yn]

It's an old one, however I'm trying a usage that would need root. Can confirm this, and the "Magisk method" works with the Verizon ellipsis 10 hd.

 

[Rfoletto]

Iae

 

[染ACE]

活体 y13il Lack(setns)

 

[texsd123]

i succeeded in rooting my philips e518, and used dd command to get full magisk support. HOW AMAZING!

 

[Ratul2002]

Everytime I try to run the file, it says
Failed critical init step 1
i also tried mtk easy su, all the versions and all versions of magisk, but still the same issue... Previously it worked and I rooted my phone easily, but after installing an ota update I can't root it again.
Device: Oppo A5S, oreo
Developer options, oem unlock, usb debugging and disable permission monitoring are enabled

 

[diplomatic]

Everytime I try to run the file, it says
Failed critical init step 1
i also tried mtk easy su, all the versions and all versions of magisk, but still the same issue... Previously it worked and I rooted my phone easily, but after installing an ota update I can't root it again.
Device: Oppo A5S, oreo
Developer options, oem unlock, usb debugging and disable permission monitoring are enabled

After you've started using mtk-su, the first thing you should have done is disabled all FW updates and avoided applying any optional OS updates from that day forward. Your firmware has been patched against this tool for months. I have had the following warning posted here for a long time. Unfortunately, most people who install mtk-easy-su never bother to check this thread for information and find out where mtk-su actually comes from (and who made it).

NOTE: Any firmware update released after March, 2020 is bound to block this temp root. Think twice before updating your device if you would like to keep using mtk-su.

Oppo A5s -- up to A.30 only

The good news is that rumor has it your phone lets you downgrade the firmware. If you manage to do that, then mtk-su will work again...

- D

 

[diplomatic]

i succeeded in rooting my philips e518, and used dd command to get full magisk support. HOW AMAZING!

Wow, that phone is very recent to be compatible. I like the old school style. It sounds like it doesn't come with much security on it...

 

[Raggamuffin17]

I have a cubot note 7 chip MT6738, guess this will work?
What root is it?? Can I get twrp working and magsik? Thanku

 

[XxxketaminekidxxX423]

First of all thank you for you work on developing such an awesome tool...

However, I am encountering this error. And I followed instructions to a T

"
Can't acquire root privileges (Dec 22, 2020 3:21:45 AM)



Executing scripts from /storage/emulated/0/init.d (Dec 22, 2020 3:21:45 AM)



magisk-boot.sh

/data/user/0/com.ryosoftware.initd/files/script-1044225735855930085[139]: ./mtk-su: inaccessible or not found. "

Any help or directions you could give would be greatly appreciated.
Thank you once again

 

[diplomatic]

@XxxketaminekidxxX423, have you copied mtk-su to the init.d/bin subdirectory?

 

[TomJ2]

"Failed critical init step 4 - This firmware cannot be supported"

LG K40 Android 9.0, Kernal 4.9.117, SW version X420AS10