yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Danny642:
how to fix the module does not work, try soft reboot, I already tried and the results are working :)
[Miscellaneous Android Development] CarbonGTR:
Worked really well on an old Gionee F103 Pro with MTK 6735, Used this to get my IMEI back!

Thanks for this great tool!
[Miscellaneous Android Development] akiraww:
me too，the same OS

failed at the last step.
[Miscellaneous Android Development] bpaxda:
Init.d problem UPDATE: For those of you that don't have problem with Init.d running mtk-su at bootup, feel free to skip this post.

Otherwise, I was able to figure out how to get Init.d to properly respond to the ACTION_BOOT_COMPLETE message. FWIW: bootup-time logcat messages didn't make any sense here. When Init.d WAS NOT responding to the boot complete message, I remember seeing a message from the ActivityManager that the init.d process wouldn't be forked due to a low frequency count. Couldn't find any search hits on this one, as I only got articles/topics about "radio frequencies", wifi and the like. The problem seemed as if Android wasn't going to run it because it thought the app wasn't used enough to deserve launching at boot. Anyway, strange.

One of the reasons I use root is to have the ability to enable/disable system services like "Google Play Services" which on this newer device manage to sneak ads around my root firewall (which I'm currently working on by appending some extra iptables rules to [MENTION=8132642]diplomatic[/MENTION] 's script along with some other startup stuff), however at times I need "Google Play Services" enabled for some apps like CPU-Z to not crash.

On to the fix. If you frequently enable and disable system services and init.d stops running the mtk-su script at bootup, the following workaround has worked multiple times for my device: 1> uninstall and then reinstall init.d. 2> Reconfigure init.d as described here which is a snap because the files in /sdcard/init.d will remain. 3> don't forget the uid will change, so Magisk Manager will need to re-authorize SuperUser access for the new installation of init.d. NOTE: on my device, sometimes I don't get the "grant" dialog, but need the SuperUser attempt to happen so I can go in and manually grant it access through Magisk Manager, thus 2 reboots may be needed. This did the trick for me. Good luck!
[Miscellaneous Android Development] Danny642:
Tested Module ViPER4Android:
[Miscellaneous Android Development] DirkStorck:
Hi,

trying to root my device.

Hardware : MT6582

Model : TAB910

Build number : TAB910_vEN52S3_20200416

Build date UTC : 20200416-030216

Android v : 9.0

Baseband v: MOLY.WR8.W1315.MD.WG.MP.V54, 2020/04/01 11:16

Kernel v : 3.4.67 (buildserver@buildserver6) (gcc version 4.7 (GCC) ) #1 SMP Thu Apr 16 10:47:37 CST 2020

Did all steps from your guide but when I run the scrip I get

magisk-boot.sh[139]: ./mtk-su: not executable: magisk 7F45

How can I fix this? Thank you!
[Miscellaneous Android Development] diplomatic:
[MENTION=2006309]DirkStorck[/MENTION], there's almost no chance it'll work on MT6582. You can try the adb instructions with the arm version if you want to be absolutely sure. BTW, did they really put Android 9 on top of that ancient kernel and chip? That platform used to run Android 4.x.
[Miscellaneous Android Development] CXZa:
It is one of those tablets having fake specs, like that mt6580 of mine...

https://xdaforums.com/android/softw...m-add-root-t3877701/post78458949#post78458949
[Miscellaneous Android Development] diplomatic:
OK, cool. V4A is one of a few modules actually known to work with this method.

LOL... yeah, that seems more plausible. It's probably just Android 4.x, just like the reports in that thread. The surest way to know is to get the SDK version...
[Miscellaneous Android Development] feel2death:
i need help with chinese android tv with dont know where is firmware

using mt 5886

android tv os 8.0

type tv : coocaa 40s5g

kernel 3.18.66 mar 2019

get error

Failed critical init step 1

Incompatible platform

hope it getting support soon :(
[Miscellaneous Android Development] diplomatic:
Test version

Here is the current test version of mtk-su. This adds support for some early MT81xx tablet firmware.

EDIT: File removed. Grab the latest from the OP.
[Miscellaneous Android Development] feel2death:
is that include mt 58xx too ? :(
[Miscellaneous Android Development] diplomatic:
[MENTION=8702668]feel2death[/MENTION], no, it will never support it. That chip is completely out of the scope of this root method.
[Miscellaneous Android Development] baerenbisch:
I can confirm exploit works fine on my LG K40 device. (ie. LG K40 (LM-X420EMW) Android 9 Kernel 4.9.117 Patch Level January 1, 2020 Build Nr. PKQ1.190522.001 Software-Vers. V20d-EEA-XX )

Thnx a lot for this great work !!!
[Miscellaneous Android Development] s4goa:
of course not. because nothing ever works. you get root, but none of the apps work as root. how much fun is that. :confused:

got root on Lumigon T3 but still looking for an app: the stuff by JRummy is a complete fail.
[Miscellaneous Android Development] bigrammy:
Why are you complaining here now?

You can have full root on the Lumigon T3 via TWRP & Magisk

Bootloader unlocking is Not required on the T3 to flash TWRP then flash Magisk. As you should well know.

This Root is only for apps and mods that do not need to make /system changes.

If you are struggling then just ASK for help in the T3 thread instead of just complaining and I will help you.

With this mtk-su you can flash TWRP without the need of SPFlashtool if that's where your problem lay.
[Miscellaneous Android Development] superdragonpt:
^this
[Miscellaneous Android Development] gumis1986:
ATM testing it on Htc Desire 12 based on mtk mt6739. And only have one problem some times when im use Xposeda they lost permission to storages. then i must enable it again. Idk if its fault on my device or its possible to give permanent permission to directores
[Miscellaneous Android Development] Gisin:
No mt8168 support? Did mediatek fix it? I tried v23a on the latest Fire HD 8.

onyx:/data/local/tmp $ ./mtk-su -v
armv8l machine
Failed critical init step 4
Firmware support not implemented
[Miscellaneous Android Development] s4goa:
root the Lumigon T3 with mtk-su

Well yes, I was aware of Magisk and tried Magisk but did not feel like getting very far.

flashing TWRP will erase ALL STORAGE (else the write-protection won't come off prior to flashing using "fastboot"). Ideally I would like to stick in Linux, without any Windows flasher-tools.

Given that the Lumigon keeps getting the "optimizing app 1 of 1" boot-delay disease - which can be remedied seemingly only with a factory reset, I will however press on with TWRP on my Lumigon.

The T3 is really nice, AMOLED and all so I am also somewhat reluctant to brick it. Still have a rooted gingerbread from the days when seemingly stuff just worked.

You have to excuse people for complaining though, since writing on this forum ridden with those GODAWFUL captchas is a goddamned ordeal.
[Miscellaneous Android Development] bigrammy:
Flip to the T3 thread Please this is OT in here.

No need for fastboot, Windows, etc etc.
[Miscellaneous Android Development] s4goa:
dammit!

well we might flip to here: https://xdaforums.com/android/development/root-lumigon-t3-nonsense-approach-to-t4129959 but I cannot tag that thread as "

Lumigon

" . You gotta be ready for more complaints over such needless chicanes. :( if I can bring myself to go thru more of these godawful captcha crappies.
[Miscellaneous Android Development] old_fart:
my pc complains about this zip . . .

Access blocked

The requested URL cannot be provided

Object URL:

https://dl.xda-cdn.com/5/0/4/6/8/0/3/mtk-su_20200623a.zip?key=QkUR_XrBoNVoInNobujFPA&ts=1594250828

Reason: the object is infected by HEUR:Exploit.AndroidOS.MtkSu.a

Message generated on: 7/8/2020 4:26:28 PM

so actually is necessary / okay ?
[Miscellaneous Android Development] diplomatic:
Before resorting to complaints, have you even seen the guide to load Magisk using this temp root (linked from post 3)? I ask because your new thread implies that apps should somehow be getting root access automatically after running /data/local/tmp/mtk-su. What happens in between calling mtk-su and requesting SU permissions? And also this message does not give confidence that you searched for an answer before making conclusions about this tool:

That's not what mtk-su does at all. To enable root privileges for apps, you need to load Magisk using bootless method first.

FWIW, this FAQ already answers your question:
[Miscellaneous Android Development] diplomatic:
It's all good... just make an exception in or disable your anti-malware app. Try this link: https://xdaforums.com/attachment.php?attachmentid=5046803
[Miscellaneous Android Development] s4goa:
FWIW there are easier methods than your’s

I had read that post you refer to earlier on. It requires an "init.d app" among other things.

The point I was trying to make here --> (( link :( )) already is this: On supported phones, the quickest way to root is to use the Magisk...apk in conjunction with mtk-easy-su as suggested here. :cyclops:

This is the point I want to drive home! Many guides out there point to tedious methods meanwhile

quicker ones are readily available

on supported phones. And as soon as someone like me tries to point out a shortcut to root, the thread gets closed as in the (( link:()) given above.

Now, I retract my above statement - which you quote - about the JRummy root-apps not working. Following the above :cyclops:-link everything from JRummy works like a charm, just like in the good old Android-gingerbread days.

So, to reiterate: On supported MediaTek phones such as my Lumigon T3 there is no need for adb shell, fastboot, nor the SPFT Win-flasher or Linux-flasher nor the init.d-App which your post suggests to employ.

It is much easier: just run the 2 .apk's Magisk and mtk-easy-su from github and you are rooted!

end of story!

I don't think there is any quicker way to root on supported MTK phones. :good::good::good:

All those more tedious methods suggested at XDA, such as those using TWRP could use a pointer to this simplified rooting-methodology. Those tedious methods still have their merit, of course. But they also are somewhat prone to infeasibility on certain installations et cetera.
[Miscellaneous Android Development] alecxs:
[MENTION=9580658]s4goa[/MENTION] you missed the point. your (off-topic) advertised 3rd party app is just a wrapper for the exact same method. It wouldn't even exist without [MENTION=8132642]diplomatic[/MENTION]

Furthermore bootless root is recommended as last option for un-unlockable bootloader in first place. because of dm-verity, on locked bootloader you can easily brick your device, especially when given easy root method is in hands of unskilled users

Who is giving support to users of this app then?

You can use this method for backup purposes, but traditional rooting is highly recommended
[Miscellaneous Android Development] s4goa:
un-unlockable bootloader

There is some ambiguity in the term "unlockable bootloader ".

could you please clarify, do you mean:

1. the option "unlock bootloader" from the Developer Menu in the phone

2. the "ORANGE STATE" situation of the phone after: fastboot flashing unlock_critical # (bootloader) Start unlock flow

______________________

after " 2. " one usually reads on the phone after reboot:

"orange state

your device has been unlocked and cannot be trusted

device will reboot in 5 seconds"
[Miscellaneous Android Development] old_fart:
thank you.

.

my kaspersky went wonkie, looped around twice, called me a dumb $hit if I continue with such foolishness. I suppose I'm on their list now, along with uncle sam . . .

.

looping more... wow, it really didn't want to listen to me saying 'bug off' . . .
[Miscellaneous Android Development] s4goa:
wrapper

... and yes, mtk-easy-su is a GUI wrapper around the mtk-su CLI tool.

but I think it really adds usability since usage is super intuitive now!

root an MTek phone with just 2 .apk’s

rooting never was easier, thanks to [MENTION=8132642]diplomatic[/MENTION] who delivered a reliable core CLI tool to base a GUI on. Cannot thank [MENTION=8132642]diplomatic[/MENTION] enough for making this possible! :highfive:
[Miscellaneous Android Development] theOriginalSuperl2:
Thanks for the guide!

I see that SafetyNet passes on Android 9, but is there any chance of it breaking on Android 8? If so, would a data wipe fix it? I want to try this, but I don't want to lose Netflix on my Android TV...
[Miscellaneous Android Development] tom1807:
Similar problem here but with Lenovo M8:

Model: TB-8505F

Hardware: MT8166B (according to Lenovo Mobile Assistant) (AIDA and CPU-X report MT8766)

Platform: MT6761

Android: 9, latest update dated March 16, 2020 (TB-8505F_S100133_200316_BMP)

TWRP: not available

Bootloader: unlocked

Failed critical init in Step 4

This firmware cannot be supported

Cheers

Tom
[Miscellaneous Android Development] DB126:
Both devices have been patched for several months.
[Miscellaneous Android Development] diplomatic:
This method is actually not compatible with Android TV devices (TVs or set top boxes). But yeah, the SafetyNet feature should work on all Android versions...
[Miscellaneous Android Development] theOriginalSuperl2:
Interesting, what's stopping it working on this devices?
[Miscellaneous Android Development] diplomatic:
[MENTION=7501045]theOriginalSuperl2[/MENTION], if it's MTK you're talking about, the vulnerable components are just not there in the hw/sw.
[Miscellaneous Android Development] bigrammy:
Interesting is it confirmed not to be working on the amazon firestick's (mtk) :confused:
[Miscellaneous Android Development] leezer3:
Works perfectly on a Teclast M30 (M5P4 variant)

Top man :)
[Miscellaneous Android Development] Israel texera:
Lg k12 consegui da permison uma ve depois nao deu mais
[Miscellaneous Android Development] diplomatic:
Yeah, it has never been compatible with any Fire TV sticks. It has to be a mobile chipset that's recent enough. MT8127 or MT5xxx (or whatever) have never been supported...
[Miscellaneous Android Development] zex_mais:
It's work with my tablet Alldocube Iplay10 Pro with Android Pie 9 and Magisk 20.4.
[Miscellaneous Android Development] diplomatic:
No, you can update Magisk Manager without a problem. It's updating Magisk (core) itself that should be avoided. MM is just a regular app/APK that the OS installs like any other. You can find the latest version in Magisk releases on Github. What that step means is if MM detects a new version of Magisk, and you tap Update, it will give you a menu option that does a direct install onto the boot partition. That's the thing you should not do. But even selecting that should not brick the device. There is noob protection built into the script...

If a factory reset restored the tablet, then the locked bootloader was not the cause of the boot fail. The problem lied in the userdata partition, whatever it was. Same thing would have happened if you installed Magisk the intended way...

BTW, thanks for not quoting my whole post with the guide ;)
[Miscellaneous Android Development] :
Working on LG Harmony 3 with Android 9 Stock.

MT6765 Soc

12-2019 Security Update

4-2020+ Updates have the X-Ploit Blocked
[Miscellaneous Android Development] goapunk:
Getting

/data/local/tmp $ ./mtk-su -v
armv8l machine
param1: 0x3000, param2: 0x10000, type: 4
Building symbol table
Can't find kallsyms addresses or offsets
Unable to get kernel symbol table
starting /system/bin/sh
UID: 2000 cap: 0000000000 selinux: enforcing

on my Snopow M10W

MTK6757

Android 7 Kernel 4.4.15

Any chance to fix the offset?

Thanks for your work!
[Miscellaneous Android Development] diplomatic:
Thanks for the update, Pizza. I believe that phone is the same as the LG Xpression Plus 2. I hope there's a way for users to roll back the FW. What is the last FW version that worked, so I can put it up on the board?

OK, I'll take a look at it. That's a strange HW configuration with 6GB of RAM. I didn't think that chip supported more than 4GB. In the meantime, you did use the latest mtk-su release, right? Because I recently fixed a similar problem that affected that chipset...
[Miscellaneous Android Development] goapunk:
It's a weird phone ;) thanks

r22, so yeah
[Miscellaneous Android Development] Luke'sFather:
Reply to:

Original Post:

&

[/B]

Up-to-date bootless root for Magisk 20+!

:

Working perfectly on HomTom HT20 w/ specs:

CPU: MediaTek MT6737

Board Name: HT20 [64-bit]

RAM ~ 2 GB

ROM ~ 16 GB

Android 6.0

Build ID: MRA58K

Latest Security Patch: 2016-10-05

:good: :cool: Thanks!

|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

Lol

Yes, since factory reset deletes userdata content.

I only meant the program which I ran, which requires root to run, tries to run something during the bootup process <from the userdata partition> which requires the bootloader to be unlocked or it gets suck during the bootup process, when it tries to run whatever it is, during the bootup process.

The same program runs perfectly on several other rooted devices, which have custom ROMs and custom bootloaders. But fails on this device which was my only rooted device still running the OEM locked bootloader and OEM ROM.

Of course. And thank you, for responding.
[Miscellaneous Android Development] colnix:
alcatel 5028Y, mt6762,

armv8l machine

Failed critical init step 4

Firmware support not implemented
[Miscellaneous Android Development] diplomatic:
Great! Good 2 know... I'll add it to the list.

OK, so if it needs root (su program) to be there at bootup, it will have trouble with this root method just like most system mods. The bootless root doesn't become available until the init.d program runs the script. I guess having the BL unlocked is relevant in the sense that you would be able to install Magisk to the boot image.

That's an Android 10 phone that came out just recently in 2020. It's very unlikely to have this vulnerability regardless if I implement support for that firmware....
[Miscellaneous Android Development] colnix:
seems like. though, firmware was from march
[Miscellaneous Android Development] bachboi77:
i got the error UID: 0 cap: 3fffffffff selinux: permissive
[Miscellaneous Android Development] moleg:
Amazon Fire HD 10 FireOS 7.3.1.2

Failed critical init step 4

Firmware support not implemented
[Miscellaneous Android Development] Toberius:
Runs successfuly on ION Gravity tablet with MTK8163 Quad core 64bit 1.3GHZ

:laugh:

127|shell@ION_Gravity:/data/local/tmp # ./mtk-su -v
param1: 0x3000, param2: 0x18040, type: 1
Building symbol table
kallsyms_addresses pa 0x40c3cb00
kallsyms_num_syms 48713, addr_count 48713
kallsyms_names pa 0x40c9bf00, size 596206
kallsyms_markers pa 0x40d2d800
kallsyms_token_table pa 0x40d2de00
kallsyms_token_index pa 0x40d2e200
Patching credentials
Parsing current_is_single_threaded
ffffffc0002fd298+50: ADRP x0, 0xffffffc000ede000
ffffffc0002fd298+54: ADD xd, x0, 2576
init_task VA: 0xffffffc000edea10
Possible list_head tasks at offset 0x340
comm swapper/0 at offset 0x5c0
Found own task_struct at node 1
cred VA: 0xffffffc0370c4f00
Parsing avc_denied
ffffffc0002a4634+20: ADRP x0, 0xffffffc00100b000
ffffffc0002a4634+24: LDR [x0, 3836]
selinux_enforcing VA: 0xffffffc00100befc
Setting selinux_enforcing
Selinux is already permissive
starting /system/bin/sh
UID: 0 cap: 3fffffffff selinux: permissive
[Miscellaneous Android Development] 19moh4m3d:
thanks. work on cph1909.
[Miscellaneous Android Development] Mksdinha:
MTK doesn't want to get on my moto g8 play I try to use the temporary root but it won't go wrong and I already unlocked my bootloader on the PC and my phone's Midiatek is compatible even more so it doesn't start
[Miscellaneous Android Development] silent-ice:
Thank you so much!

Works on moto c plus XT1725 :)
[Miscellaneous Android Development] sumitarora2:
Can we install system less xposed using magisk after using temp root??
[Miscellaneous Android Development] stargam:
I think yes but idk

---------- Post added at 11:15 AM ---------- Previous post was at 11:09 AM ----------

Why my can't ? I'm use Oppo f11 Android 10
[Miscellaneous Android Development] sumitarora2:
I've taken risk and tried it but it always shows installed but not activated??*♂️
[Miscellaneous Android Development] Anujpatel1525:
Can i install the magisk modules zips after tmp root?
[Miscellaneous Android Development] DB126:
Depends; see previous posts on topic for details (use XDA search function)
[Miscellaneous Android Development] Y83Bricked:
helooo

i executed it on android v8.1.0 (android security patch level- 2019-07-05)(Kernel version 4.9.77+)

Device firmware - https://vivofirmware.com/vivo-y81-odm-pd1732f (v2.3.4_22072019) (funtouch OS_4.0)(MT6765)

when executed through init.d apk it shows -

0000000000000000 is not a valid address

UID: 10206 cap: 0000000000 selinux:permissive

Root user only

& when executed through adb, it shows the same :(

tried it executing several times... no change
[Miscellaneous Android Development] diplomatic:
That phone is on the problematic list. See the bottom of post 4....
[Miscellaneous Android Development] axelxlow:
Unsupported Firmware

OPPO a77 (mediatek)

Model Number: CPH1715

Processor: mt6750

Firmware Version: CPH1715EX_11_A32_191228

Kernel Version: 3.18.22-G201912280043

link:(sorry can't find link to firmware)

when i hit " ./mtk-su " appeared words below:

"Failed critical init step 4

This firmware cannot be supported"
[Miscellaneous Android Development] aryanhington:
how can mtk temp root be used with a mt6771 device to create a scatter file and backup all the partitions?
[Miscellaneous Android Development] aryanhington:
edited
[Miscellaneous Android Development] slowspeedchase:
Fire 7in (9th Gen) Error at ./mtk-su

Current OS is 6.3.1.5

mustang:/ $ cd /data/local/tmp
mustang:/data/local/tmp $ chmod 755 mtk-su
mustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4: Bad address
setns failed:: Permission denied
New UID/GID: 2000/2000

My guess is that the OS is too new and no update has been posted; but I am not a deep enough developer to prove this.
[Miscellaneous Android Development] aryanhington:
The fire 7 9th generation is from june 2019 but the patch only came out in March 2020?
[Miscellaneous Android Development] Pachacouti:
No. The bootloader does not boot, shows black screen, and bootloops after, but by getting phone back into fastboot and reflashing boot/recovery (i tried both partitions), showing we're simply using a wrong boot or recovery, I found that the fone restored, no wiping etc, tested booting 8 different twrps and boots using this method, , just dont have a twrp for my fone to test, but I read of a johnwu post about resizing a partition i'd like to try... I'm on a 6765 mtk, and I understand the problem so far is all partitions are dynamic, and even the apps get mounted in their own 'sandbox' type structure, dunno enuff about all this new dynamic stuff, except it's technically like dynamic configs for modems..

All attempts at mtk-su make mine appear I have root, but I dont.. someone please input the 6765 files, they are the same as another, but I forget which at this time of morning... arm64-v8a

Edit, I'm sitting on android 10 q and open to suggestions, test in particular, dont care much for a google fn 2 b honest, would love to work on an up to date os, all ive read is the work concentrating on older devices, focus on the latest to break em all (devide n conquer style), i'll load anything knowing my way out of a brick...

---------- Post added at 04:39 AM ---------- Previous post was at 04:14 AM ----------

think about what your doing, exploiting your fone, in this case I would call it a false positive, being what you need to exploit... right click your link and download without that warning?

---------- Post added at 04:43 AM ---------- Previous post was at 04:39 AM ----------

this scream's your 2 up to date, nothing more, when your gotten round to, (and mine) ... are available lol...