FORUMS
Remove All Ads from XDA

Amazing Temp Root for MediaTek ARMv8 [2019-12-28]

1,201 posts
Thanks Meter: 1,572
 
By diplomatic, XDA Ad-Free Senior Member on 17th April 2019, 01:51 PM
Post Reply Email Thread
9th January 2020, 06:44 PM |#771  
This works on the Southern Telecom tablet from Walmart, android 7.0, MT8167B https://forum.xda-developers.com/and...artab-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.
The Following User Says Thank You to DragonFire1024 For This Useful Post: [ View ] Gift DragonFire1024 Ad-Free
10th January 2020, 11:39 AM |#772  
Senior Member
Flag Surabaya
Thanks Meter: 73
 
More
Love your work, bro. Version 20 boot loops my F11. I truly hope for an unlocked bootloader someday.
The Following User Says Thank You to Supermatt01 For This Useful Post: [ View ] Gift Supermatt01 Ad-Free
10th January 2020, 01:41 PM |#773  
Junior Member
Thanks Meter: 0
 
More
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?
11th January 2020, 01:16 AM |#774  
Senior Member
Thanks Meter: 114
 
More
Has anybody tried this on the alldocube x1..it has the 6797 Helio x20 so it should work?
12th January 2020, 08:14 PM |#775  
Member
Flag HH
Thanks Meter: 18
 
More
Quote:
Originally Posted by elshaera

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?

similar error here:

Failed critical init step 4
This platform cannot be supported

(also fire 7 Build 0003188263812)
17th January 2020, 04:41 PM |#776  
Junior Member
Thanks Meter: 4
 
More
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:

Code:
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-r...hones-142.html )

Thanks for your work!
18th January 2020, 12:23 PM |#777  
bigrammy's Avatar
Senior Member
Flag huddersfield
Thanks Meter: 2,411
 
More
Quote:
Originally Posted by cip91

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 would not of thought mtk-su would have any problems whatsoever working on that device.
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.

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
The Following User Says Thank You to bigrammy For This Useful Post: [ View ] Gift bigrammy Ad-Free
18th January 2020, 12:41 PM |#778  
OP Senior Member
Thanks Meter: 1,572
 
Donate to Me
More
Yo, @bigrammy! 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...
The Following User Says Thank You to diplomatic For This Useful Post: [ View ] Gift diplomatic Ad-Free
18th January 2020, 07:36 PM |#779  
bigrammy's Avatar
Senior Member
Flag huddersfield
Thanks Meter: 2,411
 
More
Quote:
Originally Posted by diplomatic

Yo, @bigrammy! 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...

I never left mate I just didn't feel the need to comment because you handle everything so efficiently
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.
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.

Thanks As Always diplomatic the MediaTek user community owe you a Massive debt of Gratitude
The Following 2 Users Say Thank You to bigrammy For This Useful Post: [ View ] Gift bigrammy Ad-Free
19th January 2020, 10:11 PM |#780  
Quote:
Originally Posted by DragonFire1024

This works on the Southern Telecom tablet from Walmart, android 7.0, MT8167B https://forum.xda-developers.com/and...rtab-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.

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.
19th January 2020, 11:38 PM |#781  
Senior Member
Thanks Meter: 114
 
More
Anyone tried the Helio x20 for root?
Post Reply Subscribe to Thread

Tags
mediatek, mt67xx, root

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes