yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Silmedil:
I'm not 100% how to get the exact version, the version of the phone I have is M320n so I believe it should be the one mentioned in this thread:

https://xdaforums.com/x-screen/development/european-lg-x-power-2-lg-m320n-received-t3830345

as I indeed updated it about a year ago (Nougat to Oreo)
[Miscellaneous Android Development] ineedroot69:
this guy ported mtk-su as apk and i think he did pretty good job https://github.com/JunioJsv/mediatek-easy-root
[Miscellaneous Android Development] diplomatic:
[MENTION=10301657]ineedroot69[/MENTION], to be clear, he did not port mtk-su's functionality. He made a GUI wrapper around the bootless root script and included my mtk-su in his app as-is, which I did not give him permission for.
[Miscellaneous Android Development] alecxs:
even more annoying, he misuses John Wu and your names for his donation (in app)
[Miscellaneous Android Development] martyfender:
And just as bad, he linked to the unofficial Magisk Manager site that John Wu has stated:
[Miscellaneous Android Development] superdragonpt:
Hi, cool tool haha

Actually due to ( some cool ...) MediaTek engineering ...

You can actually flash unsigned images on locked BL's on MT65** / MT67** and their tablets variants running MTK kernel(s) 3.4.0/3.4.5/3.4.67/ 3.10.**

( up to LP, don't remembered if I tested MM)

these where the ones I remembered testing.

It involves using an engineer mtk spflashtools, and wiping SECRO(s) partition, an address on preloader, and also changing ramdisk/ repacking kernel

This even worked with an older Motorola using FLEX ( Motorola partition) something similar to Sony's TA

Cheers
[Miscellaneous Android Development] awhpaul:
Having issues running r19 on my tablet. System updates is showing the device has 6.3.1.2 install on November 30th build number is 0002517057924.

Output from mtk-su is:

mustang:/data/local/tmp/mtk-su_r19/arm $ ./mtk-su

Failed critical init step 4

This platform is not supported

Any suggestions?
[Miscellaneous Android Development] tiberian41:
Script runs with mtk-su64 but can't acquire root privileges on;

MT6761 Blackview BV6100 (2019 model BV6100_EEA)

Android 9

Kernel Arch: arm7l

Kernel Ver: 4.9.117

Security update: June 5, 2019

- see attached image.

mtk-su 32 causes a bot loop. Any ideas please?
[Miscellaneous Android Development] M4XXX:
HUGE Thank you!

I also have a Question: Is it possible to upgrade to Magisk v19.0 afterwards?
[Miscellaneous Android Development] shashidharskv:
Any temp root binray available for G90T

Any update on the temp root for Mi Note 8 pro device based on MT6785 SOC(G90T)
[Miscellaneous Android Development] diplomatic:
That firmware can't be supported. Find your Fire tablet's corresponding unlock thread and look for any alternative solutions.

Well, I hope it's not a boot loop, but just a simple reboot. The arm build is the correct one for your phone. I will have to see the 'mtk-su -v' log from adb and probably the firmware to determine what's wrong with it. I'd also like to know if it reboots in adb. If it only crashes in terminal emulator (or any app), then it might have something to do with seccomp, or possibly some exploit defense mechanism, but that's getting ahead of myself.

No problem :)

No. The second time Magisk is launched is the same as the first.
[Miscellaneous Android Development] M4XXX:
Thanks for clarifying but well its what i thought.

Can you tell me how dangerous it really is to access the system partition? And i am not talking about "actively" trying to gain access you know.. more like some simple pulls with adb. I want to access "System/Apps" if possible have not tried yet but would be happy about any tip in the right direction. will come back to the tablets this evening.

Have a good one :good: :)
[Miscellaneous Android Development] ineedroot69:
i only have backup of the 3 top most easily overwritten partition

boot.img , recovery.img and system.img

i did alot of experiment on this phone and so far i never brick it

also why you want to use ADB pull on System/Apps just download Apps Movable by clockworkmod on playstore it can pull system app apk
[Miscellaneous Android Development] tiberian41:
Well, I hope it's not a boot loop, but just a simple reboot. The arm build is the correct one for your phone. I will have to see the 'mtk-su -v' log from adb and probably the firmware to determine what's wrong with it. I'd also like to know if it reboots in adb. If it only crashes in terminal emulator (or any app), then it might have something to do with seccomp, or possibly some exploit defense mechanism, but that's getting ahead of myself.

Using ADB: './mtk-su -v' as in the first section

Running ADB with Arm:

C:\adb>adb devices

List of devices attached

E937L2ZM9A060A19 device

C:\adb>adb push mtk-su /data/local/tmp/

2147 KB/s (34312 bytes in 0.015s)

C:\adb>adb shell

BV6100:/ $ chmod 755 mtk-su

chmod: mtk-su: No such file or directory

1|BV6100:/ $ cd /data/local/tmp

BV6100:/data/local/tmp $ chmod 755 mtk-su

BV6100:/data/local/tmp $ ./mtk-su -v

armv7l machine

No other output, phone just reboots.

Running ADB with Arm64:

C:\adb>adb devices

List of devices attached

E937L2ZM9A060A19 device

C:\adb>adb push mtk-su /data/local/tmp/

1340 KB/s (42832 bytes in 0.031s)

C:\adb>adb shell

BV6100:/ $ cd /data/local/tmp

BV6100:/data/local/tmp $ chmod 755 mtk-su

BV6100:/data/local/tmp $ ./mtk-su -v

/system/bin/sh: ./mtk-su: not executable: 64-bit ELF file
[Miscellaneous Android Development] diplomatic:
OK, thanks. It's not clear to me yet why it's doing that. I'll need to dig into the firmware when I have the time. If you don't mind risking another crash, can you try 'mtk-su -s' with arm? It will probably reboot from this too, but if it doesn't, it will narrow down the problem for me.
[Miscellaneous Android Development] tiberian41:
Thanks diplomatic for the quick response. './mtk-su -s' causes a reboot and no output to adb.

I've included the scatter file in case that sheds any light on it.
[Miscellaneous Android Development] diplomatic:
OK, so I looked at the firmware that was available on the web. And the verdict is kind of bad news. That FW already blocks mtk-su, I believe. If it didn't crash, it would have said, "This platform is not supported". But because of a bug in the kernel, it makes it panic. So there won't be root support for your phone. I hope you find some other way to crack it....
[Miscellaneous Android Development] tiberian41:
Thanks diplomatic. That's disappointing. There is an OTA update, but it always fails when the phone to reboots and tries to run the update (it's a common issue with other phones). Their advice to other user was to change the language to the default English and try again. That worked for some, but not for myself and others. I messaged Blackview via their forum and asked for a direct link, but they are notorious for not responding. Maybe if I could somehow get the link for the update, they will have hopefully done some improvements. I've pulled the debug report, would that be useful?
[Miscellaneous Android Development] diplomatic:
What about flashing the full FW package that's up on the web first? Then maybe the OTA update will take. This could happen if some of the blocks on system or vendor are not exactly what the update expects...
[Miscellaneous Android Development] tiberian41:
I've tried that, and it doesn't work, even with just accepting default language etc. Looking at the ota text, it looks like it's trying to download separate bug fixes, rather than a single .zip, then moving them to their desired locations. I've been looking at ota.txt as well as interactive and full bug reports but where I'm not seeing a normal .zip or .tar, I'm not sure what to make of the results. Rather frustrating is the fact, I can't seem to locate what ota has downloaded, even when I choose to I install later. Maybe that's the lack of root function, but I'm not sure. The only indication I get at all is the exclamation mark when the phone reboots and tries to install the updates.
[Miscellaneous Android Development] diplomatic:
[MENTION=4134151]tiberian41[/MENTION], this is very specific to your phone model/vendor. Your experience is probably more typical than not. I'm sure there are other users (possibly most/all of them) in the same boat. You probably did nothing wrong to mess up the update process. So the vendor needs to take care of it. But this may be problematic for an obscure phone maker with a paper-thin support budget. The only thing I can suggest is to try to clear the data of the OS updater app and download the update again. Or possibly just do a factory reset. (Which rarely fixes anything that can't be fixed otherwise.)
[Miscellaneous Android Development] diplomatic:
Hi [MENTION=995279]komandantemario[/MENTION],

TY for your interest in mtk-su. About your tablet, there may be a way to crack it by downgrading the FW. Check your device's appropriate unlock thread(s). As for mtk-su development, there will not be updates to bypass that "not supported" roadblock, whether or not I come up with a solution. It would simply not be worthwhile for me to release it, at least not for free in the same way I had been updating mtk-su....

My main advice about custom ROMs is only for the hindsight. If you have any thoughts about trying them out (or just rooting), please do your research before buying the device. And stay away from any locked down devices. Amazon is among the worst brands you can choose if you want to go down that route...
[Miscellaneous Android Development] rlrevell:
Add the LG Xpression Plus 2

Just got one today at wally world and had it rooted in 5 minutes with some pointers from tecknight. Good stuff
[Miscellaneous Android Development] tecknight:
Great job !!

From out of the box to perma-root in what, a couple hours ?

Mad props to you, [MENTION=8132642]diplomatic[/MENTION], on this amazing exploit. Way to stick it to the man !!

This proves that there is still some serious fun to be had with off the shelf electronics !!

I definitely could have used this exploit when I was working on rooting an RCA Voyager III

---------- Post added at 04:57 PM ---------- Previous post was at 04:12 PM ----------

Yes, he did a pretty good job of using your script without permission.
[Miscellaneous Android Development] rlrevell:
5 minutes for the temp root, then another few hours to perma-root, and honestly if XDA was easier to navigate and/or better indexed by Google it would have been a couple hours. Can't thank [MENTION=8132642]diplomatic[/MENTION] enough.

It's still not working perfectly, it looks like magiskd crashed at some point, which a restart fixed but magisk-manager now thinks it isn't installed, but those are minor compared to cracking it in the first place.

Anyone know if the magisk developers would be open to adding official support for this root method so we don't have to run old versions?
[Miscellaneous Android Development] diplomatic:
Thanks man. Appreciate your enthusiasm for this project. :)

The RCA Voyager, if it has a 64-bit mt81xx, this root should work on it. But if it's mt8127, then it's out of luck.

Heh... true. It's not actually the suboot script I care about. It's the mtk-su executable (as well as magiskinit) that's bundled with it. I'm fine with people making tools around it, as I say in the FAQ, just make sure users download the mtk-su zip from this thread themselves.

Glad you're a fan of this root method... Have you tried Magisk Manager 7.1.0 or 7.0.0 with Magisk 18.1? Not sure why it's unstable. If you've been mixing different versions of Magisk, you may need to clear out the /data/adb/ directory (without Magisk running).

For the newer versions to work, they have to add some kind of a call to replace 'magisk --startup'. The /sbin tree setup code has been moved to magiskinit, but that only runs as a standin for init. It's not good for exploit-based launches. There would need to be some option like 'magiskinit --manual-start' for this to work. You can try to ask topjohnwu to add this if you want.
[Miscellaneous Android Development] diplomatic:
Release 20

A new version has dropped. It's basically a rollup of all the test versions floating around with a couple of fixes. MT6580 support comes standard. Let me know if there's anything wrong with it, especially since it was made with a new build system.

If you use this for bootless root, make sure you also update the suboot script, especially for Android 9. Some functionality was moved from mtk-su to the script.
[Miscellaneous Android Development] diplomatic:
Wow, nice. That would be sweet if they could add that feature. Then we could use the latest Magisk version in bootless root. Go for it, dude :)

What they'd need to do, in a nutshell, is to add back the former functionality of 'magisk --startup' (probably within magiskinit). That's what sets up the /sbin tree for magisk, su, etc. Then any root exploit would be able to use it.

Oh, that looks like it's Intel. So not even close for this :)
[Miscellaneous Android Development] lilinbo:
PD1813:/data/local/tmp $ ./mtk-su -v

./mtk-su -v

param1: 0x1000, param2: 0x8040, type: 13

Building symbol table

kallsyms_addresses pa 0x40f22e00

kallsyms_num_syms 53736, addr_count 53736

kallsyms_names pa 0x40f8bf00, size 701997

kallsyms_markers pa 0x41037600

kallsyms_token_table pa 0x41037d00

kallsyms_token_index pa 0x41038100

Patching credentials

Parsing current_is_single_threaded

ffffff800837f7f8+58: ADRP x2, 0xffffff800980d000

ffffff800837f7f8+5c: ADD xd, x2, 1472

init_task VA: 0xffffff800980d5c0

Potential list_head tasks at offset 0x3c8

comm swapper/0 at offset 0x690

Found own task_struct at node 1

cred VA: 0000000000000000

0000000000000000 is not a valid address

avc_denied not found

selinux_enforcing not found

starting /system/bin/sh

UID: 2000 cap: 0000000000 selinux: enforcing

PD1813:/data/local/tmp $
[Miscellaneous Android Development] Dicekido:
When I try to install Magisk modules I get installation failed please install Magisk v19, how can I solve this?
[Miscellaneous Android Development] martyfender:
I'm not sure what this has to do with mtk-su?

I recommend that you post this in the Magisk general help forum instead. You should post device info, Magisk version and logs.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382

https://www.didgeridoohan.com/magisk/MagiskHelp
[Miscellaneous Android Development] mrimpli:
Hi,

I've tested two method (mtk-su & suboot/magisk) and I havent got any error message.

selinux is permissive in terminal (adb shell & Termux) and I have root access in terminal.

But, when I test root access whith Root Checker, I have a "Root access is not properly installed" message and I haven't got any root notification from magisk after root terminal access.

So, I don't really understand my case.

How can I have a true root access with command line or a verified root access with Root Checker ?

Sry for my poor english, not native and i'm a newbie on android rooting.

Regards.
[Miscellaneous Android Development] Supermatt01:
Yes, this version is not compatible with modular add-ons from the repo at all. I don't think there is a way around that though.
[Miscellaneous Android Development] diplomatic:
It's best not to run bootless root with permissive. That may lead to the Magisk daemon being killed. Just reboot and try again without involving an mtk-su command line shell. Or for a quicker resolution, restart Magisk from root with 'magisk --daemon' followed by 'setenforce 1'.

What do you mean? It's compatible with some modules, ones that work with 18.x and don't need to be loaded at boot time. For example, Systemless Hosts (which is built into MM, but is a module), Viper4android, busybox, etc.
[Miscellaneous Android Development] mrimpli:
Thank a lot. Work fine on Echo Feeling (another chinese smartphone) with MT6739, Android 8.1.

Great job, man. Love you.
[Miscellaneous Android Development] Herrie82:
Doesn't seem to work on Unihertz Titan MT6771V/C with Android 9, security patch 2019-08-05 and Kernel Linux 4.4.146

I get:

Failed critical init step 4

This platform cannot be supported
[Miscellaneous Android Development] Supermatt01:
I mean on my OPPO, I can't get any module to install now and when I could get them to install they did nothing or jacked up root access. I had been running YouTube vanced. It won't install now even though it is the same version number. Viper and busybox never worked. It is likely an OPPO device issue. You're work is great. OPPO just sucks.

What do you mean? It's compatible with some modules, ones that work with 18.x and don't need to be loaded at boot time. For example, Systemless Hosts (which is built into MM, but is a module), Viper4android, busybox, etc.[/QUOTE]
[Miscellaneous Android Development] Vortell:
No clue about the issue. For YouTube though there are many other clients. I prefer newpipe personally, there are others though that ingrate with YouTube better.
[Miscellaneous Android Development] zaibansari20:
Works great on OPPO F5, but I want to obtain permanent root after this. Is there any guide or suggestion to do so with magisk or something
[Miscellaneous Android Development] DragonFire1024:
This works on the Southern Telecom tablet from Walmart, android 7.0, MT8167B https://xdaforums.com/android/help/southern-telecom-smartab-t3509522. The problem is, you can't install anything into system because when you mount it, an error message pops up saying the device is busy. So I had to unlock the bootloader and have magisk patch the image.
[Miscellaneous Android Development] Supermatt01:
Love your work, bro. Version 20 boot loops my F11. I truly hope for an unlocked bootloader someday.
[Miscellaneous Android Development] elshaera:
Fatal error

I got this fatal error:

Failed critical init step 4: Bad address

setns failed:: Permission denied

New UID/GID: 2000/2000

Device: Kindle Fire 7 (2019)

Build number: 0003188263812

One more question, plz: Is there a plain vanilla Android stock ROM for this tablet?
[Miscellaneous Android Development] russy23:
Has anybody tried this on the alldocube x1..it has the 6797 Helio x20 so it should work?
[Miscellaneous Android Development] A.D.I.O.S:
similar error here:

Failed critical init step 4

This platform cannot be supported

(also fire 7 Build 0003188263812)
[Miscellaneous Android Development] cip91:
Oukitel U18

Hello diplomatic, I tried the tool on an Oukitel U18, it should have a MTK6750t, Android 7.0, January 2018 patches, kernel 3.18.35

I only tried from a terminal emulator as the USB doesn't work on this phone.

Running with -v it gives me this messages:

param1: 0x1000, param2: 0x8040, type: 4
Building symbol table
Can't find kallsyms addresses or offsets
Unable to get kernel symbol table
setns failed: No such file or directory
starting /system/bin/sh
UID: 10089 cap: 0000000000 selinux: enforcing

I didn't manage to find the kernel sources, but the updated firwmare is here https://mega.nz/#F!itUzXCqS!gtbEt8ahL2T_o8U7ClEbpQ (took it from http://oukitel.com/latest-software-rom-for-all-oukitel-smartphones-142.html )

Thanks for your work!
[Miscellaneous Android Development] bigrammy:
I would not of thought mtk-su would have any problems whatsoever working on that device. :confused:

arm or arm64 version used? A more detailed output from the terminal app would be nice so people can see if everything was placed correctly and permissions granted. :good:

Just to report back & I know it's on the list already but just for confirmation.

MTK-SU Working with zero issues on:

Nokia 3.1 Plus (UK)

Firmware Release= 00WW_1_26F

Version= Android 8.1.0

Security_patch= 2018-09-05

CPU = MT6765 (MT6762 is slightly under clocked) Different to USA Model of the same name which is Qualcomm I think.

New Partitioning Scheme is implemented on this model.

Code Name= ROON_sprout

I spotted this Factory refurbished (as new) phone at a bargain prices and actually thought it was the older Nokia 3.1 (mt6750) which I was getting for porting purposes.

Low and behold they sent me this PLUS version :laugh:
[Miscellaneous Android Development] diplomatic:
Yo, [MENTION=3924647]bigrammy[/MENTION]! Good to see you on this thread again. Thanks for reporting the new phone. About the Oukitel, I already requested more info. You're right, it should handle it just fine. That log is the detailed output. I don't see what's wrong yet.

EDIT: Oh wait, I already have Nokia 3.1 Plus noted down. LOL...
[Miscellaneous Android Development] bigrammy:
I never left mate I just didn't feel the need to comment because you handle everything so efficiently :o

I left the info for the 3.1 plus just in case there was any confusion between the Nokia devices eg 3.1, 3.1 plus, 3.1 plus USA all of which have different CPU's and could be confusing for a novice. :eek:

As said I ended up with this Plus Model even though the description given in the ad was for 3.1 ordinary version, now if that's a good thing or bad thing only time will tell. :laugh:

Thanks As Always diplomatic the MediaTek user community owe you a Massive debt of Gratitude :highfive: :highfive: :highfive:
[Miscellaneous Android Development] DragonFire1024:
By the way maybe was just a fluke on this tablet but I had to return it because these new versions of mediatek devices have weird things going on with the battery where it either doesn't want to charge or charges way too quick and gets really hot. Anyways I was left with the version of it didn't want to hold a charge at all. So it had to go back unfortunately. But I've got a sweet Nexus 10 coming in the mail in a few days.
[Miscellaneous Android Development] russy23:
Anyone tried the Helio x20 for root?
[Miscellaneous Android Development] diplomatic:
Well, I think you got your answer. Your phone's locked bootloader doesn't support unsigned images. So I don't think you should mess with flashing it anymore, especially if you have a chance to unlock the BL. Is there anything specific you want to do with root? We might be able to tell you how to do it from the shell.

Awesome!
[Miscellaneous Android Development] ahhl:
well, it a 2nd hand phone i got to run android auto permanently.

i want to insert reboot on charge command in the init file so that the phone reboot on power. it will auto off when power off. without root, this cannot be done.

i have done in on S4. unfortunately S4 got overheat problem until S4 freeze because too hot.

the next stage is to use magisk to hide root.
[Miscellaneous Android Development] Rortiz2:
IDK if it can work but have you tried editing the init.rc and the copying it with root shell?