yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] WheresMyDog:
Hey there, so I tried every step as straight forward as possible. I got everything set up but when I run the script, it says "Failed critical step 4 Platform cannot be supported" even though I made sure I did step 4 correctly, making sure not to use Magik Manager APK higher than 7.1.1. Can someone help me get past this step so I can root my restricted Fire 7 9th gen with freedom? I will donate 10 dollars to someone who has a solution.

---------- Post added at 08:53 AM ---------- Previous post was at 08:50 AM ----------

Hey there, so I tried every step as straight forward as possible. I got everything set up but when I run the script, it says "Failed critical step 4 Platform cannot be supported" even though I made sure I did step 4 correctly, making sure not to use Magik Manager APK higher than 7.1.1. Can someone help me get past this step so I can root my restricted Fire 7 9th gen with freedom? I will donate 10 dollars to someone who has a solution.
[Miscellaneous Android Development] diplomatic:
Oh, that's funny. :D Gotcha. (I've been known to attend CS classes myself. Although I prefer working with low-level stuff.) So I think you should have a firm foundation to understand the formulas behind these images. Just start exploring them in a hex editor. There's scattered public info out there for parts you don't understand...
[Miscellaneous Android Development] diplomatic:
Interesting... I found this bit in the FAQ that sounds like your issue:

Does that count as a solution? :)
[Miscellaneous Android Development] tiberian41:
[MENTION=8132642]diplomatic[/MENTION]. I realise I'm being a bit cheaky now, but would it be possible for you to try binary patching my attempt at a TWRP recovery port. I still want to sort you out a beer or coffee for fixing the boot image. I'll message you so I can work something out.

https://mega.nz/#!eKInWIYR!tA4tSAdB3J0xmcHXcYOKQz4kxV9OZP-PKhkvXjbOV-M
[Miscellaneous Android Development] Dat1Developer:
Any chances of the LG Stylo 4 being rooted with this method? (Qualcomm snapdragon verison)
[Miscellaneous Android Development] DB126:
Thread title, OP and subsequent discussion (including other queries on device xxx) say it all - MediaTek only.
[Miscellaneous Android Development] WheresMyDog:
Let me try it out! I will get back to you bother!
[Miscellaneous Android Development] diplomatic:
Uh, the patch I did for the boot image only enables the initial ramdisk. The ramdisk is always loaded in recovery mode anyway. The patch is not needed here. What problem are you having with that recovery? My general advice is to compile a custom recovery from source. Most of the time those auto porting methods make a horribly broken one. Also, I noticed that your FW has vbmeta. Have you disabled vbmeta verification? Otherwise it may not boot even with unlocked BL.

o.O LOL? OK, good luck I guess. :confused:
[Miscellaneous Android Development] tiberian41:
OK, thanks [MENTION=8132642]diplomatic[/MENTION]. I thought it would probably come down to compiling from source, but Blackview don't release source code as a matter of policy. As for vbmeta verification, it's supposed to be patchable after TWRP is installed with the Universal DM-Verity, ForceEncrypt, Disk Quota Disablers, or something similar, assuming you can get it to boot to the flashed TWRP. ~~I'll look into whether I can patch the recovery prior to flashing. That might help to boot at least so I can test it. Anyway, thanks again.

Edit. Possibly found a way of removing the check from the bootloader by flashing an 'empty' vbmeta.img. but I still can,t get the ported twrp to load. Oh, well. I keep digging and see what I come up with.

Edit 2. I flashed 'empty' vbmeta.img without any apparent problems. Then tried 2 different ported twrp's. Neither booted properly, however, instead of causing a boot loop, booted to a blank screen, then after a delay, rebooted to system.
[Miscellaneous Android Development] angeelgar:
[IMG="fullroot mt8163"]https://drive.google.com/file/d/1bwNXIazpSmfwH45_lJw8VBCDu3MnHenN/view?usp=sharing[/IMG]
[Miscellaneous Android Development] MishaalRahman:
Can anyone confirm if this still works on MTK devices as of the latest security patch updates? Eg. Jan. 2020 or Feb. 2020?
[Miscellaneous Android Development] Vortell:
Why not you try and see... It shouldn't hurt anything to try it. :confused:
[Miscellaneous Android Development] MishaalRahman:
I would if I could. I don't have any MediaTek phones, and I'm struggling to find someone who has one on an updated patch level.
[Miscellaneous Android Development] Vortell:
I see u want to find someone for a front page story or something. Gotcha.
[Miscellaneous Android Development] sanchopansa1:
LG stylo 4 mtk

Temporary root by diplomatic@XDA

Home URL:

https://xdaforums.com/android/development/amazing-temp-root-mediatek-armv8-t3922213

--------------------------------------------------

armv7l machine

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

Building symbol table

kallsyms_addresses pa 0x40e59280

kallsyms_num_syms 49742, addr_count 49742

kallsyms_names pa 0x40e89bd0, size 635360

kallsyms_markers pa 0x40f24db0

kallsyms_token_table pa 0x40f250c0

kallsyms_token_index pa 0x40f25450

Patching credentials

Parsing current_is_single_threaded

c04bd014: MOVW R0, #0xacf0

c04bd018: MOVT R0, #0xc142

init_task VA: 0xc142acf0

Potential list_head tasks at offset 0x2b0

comm swapper/0 at offset 0x460

Found own task_struct at node 1

cred VA: 0xdc7bc080

thread_info flags VA: 0xdaf82000

seccomp mode VA: 0xe8c00fb0+2b4

Parsing avc_denied

c045a7d0: MOVW R0, #0xbd44

c045a7d4: MOVT R0, #0xc170

selinux_enforcing VA: 0xc170bd44

Setting selinux_enforcing

Selinux is already permissive

/data/user/0/juniojsv.mtk.easy.su/files

Stack protection detected

starting /system/bin/sh

UID: 0 cap: 3fffffffff selinux: permissive

source type magisk does not exist

Error in: allow magisk (null) (null) (null)

client: launching new main daemon process

Returned 0
[Miscellaneous Android Development] bigrammy:
I reported mtk-su to the Portal months ago and on more than one occasion. :rolleyes:

Well better late than never I guess :laugh:

Going forward It would be nice if XDA could support and encourage MediaTek dev's instead of ignoring them. :fingers-crossed:
[Miscellaneous Android Development] MishaalRahman:
Apologies if I missed your message. I get tons of messages that seem spammy (and a LOT of tech support requests), so it may have just gone unnoticed :( Don't worry, though, we're definitely looking into this now.
[Miscellaneous Android Development] DragonFire1024:
Look deep.
[Miscellaneous Android Development] XopmoH:
$ unzip mtk-su_r20.zip
Archive: mtk-su_r20.zip
creating: arm/
inflating: arm/mtk-su
creating: arm64/
inflating: arm64/mtk-su
inflating: readme.txt
$ cd arm64/
$ ls -al
total 72
drwxrwxr-x 2 u0_a97 u0_a97 4096 Jan 1 2019 .
drwx------ 5 u0_a97 u0_a97 4096 Feb 9 13:41 ..
-rwxr-xr-x 1 u0_a97 u0_a97 65136 Jan 1 2019 mtk-su
$ ./mtk-su -v
Failed critical init step 4
This platform cannot be supported
$ cd ../arm
$ ./mtk-su -v
CANNOT LINK EXECUTABLE "./mtk-su": "/data/data/com.termux/files/usr/lib/libtermux-exec.so" is 64-bit instead of 32-bit
$ unset LD_PRELOAD
$ ./mtk-su -v
armv8l machine
Failed critical init step 4
This platform cannot be supported

How to fix it? MT6739 platform…
[Miscellaneous Android Development] DB126:
Vulnerability has likely been patched on your device (which you failed to identify).
[Miscellaneous Android Development] EZIOCOMPAGNONI:
Sirs having a nokia nokia 5.1 can confirm root procedure successful with amazing temp root

regards

ezio
[Miscellaneous Android Development] Divogame:
will this Root method lose data

Let me ask, I have a device that has a lot of data, I want to root without losing data. So, will this Root method lose data or not. thanks!
[Miscellaneous Android Development] rlrevell:
Thanks! You still around? I seem to be the only one on here with a rooted LMX420 device. You'd think there'd be at least as much interest as there was in the Aristo 2/Phoenix 4 given that this phone is also cheap, widely available, and super easy to root...
[Miscellaneous Android Development] Feebee??:
I've tried junior jsv media Tek easy root app and I can say that it's a pretty good one but it's only temporary root....does temporary root have the ability to change custom fonts because that's what I wanna do...if not I'll look for permanent root method
[Miscellaneous Android Development] diplomatic:
[MENTION=10392463]rlrevell[/MENTION], have you downloaded the latest suboot script if using R20? The "c243,c256..." stuff is in the file contexts, and it's not supposed to be there.
[Miscellaneous Android Development] Supermatt01:
It's highly unlikely to cause data loss. It is temp root.
[Miscellaneous Android Development] rlrevell:
That fixed it

Thanks!
[Miscellaneous Android Development] Rortiz2:
Hi [MENTION=8132642]diplomatic[/MENTION],

I need to ask you a question about mtk-su in my tab (Aquaris M8). When I run it, it takes 20~ secs to spawn a root shell.

But in my Umidigi Power takes less than 1 second to spawn the root shell....

Do you have any clue of why is this happening?

NOTE: If i lock and unlock the device (with power key) while mtk-su is running the root shell gets spawned faster (3-5 seconds).

Thanks you.

Best Regards.
[Miscellaneous Android Development] Ashok.Vardhan:
Lenovo Tab M8 (FHD) (TB-8705F)

I am using my Lenovo Tab M8 (FHD) (TB-8705F) as a monitor to control a Mavic 2 Pro drone.

When connected to the controller unit it drains the inbuilt battery of the controller, which significantly decreases operation time. I enabled developer options and under "Default USB Configuration" I selected "File Transfer". However, each time the DJI GO4 app is launched this setting is over-ridden and it starts charging the tablet.

There are a few apps available that can turn off charging if the device is rooted.

I searched all over the internet and could not find a way to root my Lenovo Tab M8 (FHD) (TB-8705F) and then I found this thread.

I used the 64-bit mtk-su version.

Still NO-GO.

Error message:

Failed critical init step 4

This platform cannot be supported

Now I am in a bind.

Is it still possible to root this device? Please suggest a solution.

Some additional details of this tablet:

Lenovo Tab M8 (FHD) (TB-8705F)

Android Version: 9

Build Number: TB-8705F_S100058_191112_BMP

Kernel Version: 4.9.117+ #2 Wed Nov 13 05:11:41 CST 2019

Hardware Version: Lenovo TB-8705F

Software Version: TB-8705F_RF01_191112

Custom Built Version: alps-mp-p0.mp1-V5.140

RAM: 3.00 GB

ROM: 32.00 GB

CPU: MediaTek Helio P22T Tab Octa-core 2.3G (MT6762)

Display: 1920x1200

Camera: Front 5MP/Rear 13MP
[Miscellaneous Android Development] Duhjoker:
I can now proclaim that it works for the lg sp200 using all three ways to deliver the payload but you cannot install modules with out having magisk 19 installed.

Has any one figured out a work around for this? I have sat here for the past two days trying to figure out how to install msgisk manager with out it automatically checking for an update upon installation to be able to use the older modules but with out breaking the app down and removing the update check i see no way.

Yes i have tried installing magisk manager with the wifi and data turned completely off.
[Miscellaneous Android Development] levone1:
Working great on TCL A501DL (Alcatel A1). Now of I can figure out how to get bootloader mode...

Anyone have ideas?

Here's my story - https://xdaforums.com/showthread.php?p=81780645#post81780645

Thanks for your work...
[Miscellaneous Android Development] diplomatic:
You mean it? ;)

Hi there and welcome to XDA. That tablet just came out. There aren't any resources posted for it yet. I actually just ordered that tab myself. There's finally a decently-priced 8" full HD tablet on the market. :laugh: Have you tried unlocking it the usual way? (Check Allow OEM unlock in Settings, then "fastboot flashing unlock" in fastboot mode.) I'll be digging into it when I receive it in a few weeks...

I'm not sure what exactly you're asking with respect to checking updates. Have you entered the custom update URL from the bootless root guide? That will lock the version at 18.1 and download the respective additional setup files for that version. Or are you saying that method doesn't work?
[Miscellaneous Android Development] Ashok.Vardhan:
Tried all the usual methods. Unless there are more methods I am currently not aware.

Yes, I agree. I bought this tablet for USD 120 during the New Year sales. There was nothing quite like it for this price in the market. The only competiton I found with a better performance, and spec, was the iPad mini at almost 3 times the price.

Yes tried unlocking the usual way.

- Enabled Developer Options

- Enabled USB debugging

- Enabled OEM unlocking

- Installed Homebrew for OSX for adb & fastboot

Terminal commands:

fastboot oem unlock

fastboot flashing unlock

fastboot oem unlock-go

fastboot getvar all

fastboot oem device-info

All of them usually end up with a blank screen with no progress for a long time (please check screenshot). So I have to eventually terminate terminal.

Thanks for your reply.
[Miscellaneous Android Development] Duhjoker:
The bootless root method works just fine. But i cannot get magisk manager to lock itself down at version 18. None of the modules will install due to them being only for version 19. Yes i have put it on the custom url and even flipped the check for updates switch off. I have installed the manager with out my data and wifi being turned on as well. No matter what i have tried the manager looks for 19 and fails to install modules.
[Miscellaneous Android Development] diplomatic:
Wait, you were trying the fastboot commands under Android? Uh, your tablet has to be in bootloader mode for those. Reboot to bootloader first with 'adb reboot bootloader'. Then try the fastboot stuff....

OK, I looked into this and could not install any modules either. The modules have been updated to require Magisk 19+. If you want to stick with 18.1, there's a workaround you can do: change the MAGISK_VER_CODE string in util_functions.sh.

This is from a module's update_binary script:

require_new_magisk() {
ui_print "*******************************"
ui_print " Please install Magisk v19.0+! "
ui_print "*******************************"
exit 1
}
....
[ $MAGISK_VER_CODE -gt 18100 ] || require_new_magisk

So not sure if this will work in all cases, but I updated the version code in util_functions.sh and modules installed fine.

sed -i '/MAGISK_VER_CODE/ s/18100/18200/' /data/adb/magisk/util_functions.sh

You can also try to upgrade to 19.x+ and come up with a different solution for mounting the /sbin folder, which would replace the 'magisk --startup' call. I've seen some exploits do this part manually in a script.
[Miscellaneous Android Development] Ashok.Vardhan:
This is the sequence of commands I use:

adb reboot bootloader (phone reboots and displays: => FASTBOOT mode. . .)

fastboot oem device-info

FAILED (remote: 'unknown command')

fastboot: error: Command failed

fastboot oem unlock

After this command the cursor just remains static. No response. On the phone screen it does not progress beyond: => FASTBOOT mode. . .

Attached screenshot:
[Miscellaneous Android Development] Duhjoker:
ok so i removed the sim card from my phone completely then turned off wifi and had it forget my wifi address completely and restarted tge device and re-installed magisk manager. Then i put the url in the custom check for updates and it says its up to date but the modules are still wanting to use magisk 19.

As far as using magisk 19. That does not work and you cannot acquire temp root. I dont really understand why but i tried several different combinations of the mtk-su and magisk files and no go. If you add 19 you dont get su.

At least on my device. Of course if someone knows tjw or has a way to contact him maybe he could keep the module repo from updating then things would be easier.

---------------------------------------------------------------------------

Ashok are you using mac and have you configured the drivers to for fastboot to see the device in fastboot mode. The first command fails because it doesnt exist. The second one hangs because the fastboot comnands do not see your device.

I recomend going to what ever your pc uses as a device manager seeing what the computer recognizes as your device in fastboot then updating the driver so it recognizes it.

This is a common problem and though time consuming sometimes is easily fixed.
[Miscellaneous Android Development] Divogame:
collect DD images of all partitions

After temporary rooting, I want to collect DD images of all partitions, what should I do? What ADB commands do I have to execute on my computer? Thanks.
[Miscellaneous Android Development] Duhjoker:
You dont need adb to run dd commands. You could have backed up your partitions using adb with out root. You need root to run dd commands though.

You should really do some research about what you want and intend before messing around with dangerous commands.

I ask what the point in it is though. If you dd an image into place without an unlocked bootloader you risk bootloop and Bricking.

But if you really want to back up all your partitions now that you have a temp root why not use partitions backup.apk.
[Miscellaneous Android Development] Divogame:
Install SuperUser

There are two issues that will help you guide me:

1. Please guide me a little more specifically about backing up an entire partition, such as "User data". I need to analyze some data in it.

2. Is there any way I can install "Super User.APK" to authorize some of the necessary applications for me to install? Thanks
[Miscellaneous Android Development] Duhjoker:
Ok how are you going to analyze the userdata.img? Have you found a tool that will allow you to extract the files and such? Or are you planning to flash it back to another phone of the same type.

SuperUser.apk? Arent you using magisk? Your killing me here smalls. You dont need another app to manage superuser permissions. plus the modules that magisk offers far outweigh any other app.

Ok before you get your self in trouble, what is root and what exactly can you accomplish with it. Why do want it? Have you owned a pc before
[Miscellaneous Android Development] Ashok.Vardhan:
Thanks for the tip. You are correct.

When booted into Android and connected to the computer, the device gets recognized properly by Mac OS and displays the correct ID (Lenovo TB-8705F) - Screenshot-1, however, during fastboot mode, in the device manager (called System Report on OsX) the device gets reported with a generic ID (Android) - Screenshot-2.

I don't know where to find the fastboot drivers for this device because it was recently released and there is not much information out there. Any suggestions?

Regards.

Ashok
[Miscellaneous Android Development] Duhjoker:
Just google manually apply fastboot drivers or some variation there of. Not gonna lie they are hard to find nut to be honest you shouldnt actually need specifci adb and fastboot drivers for a device. They are pretty much universal just have to add them as legacy on windows and on linux well you just install the android sdk and they fit for all devices maybe add a new device to 51android.rules. check where your adb drivers are installed in the system folder first then look to see if your devices drivers folder has something like a bootkoader interface driver. Its time consuming and you might have to try individual drivers one by one to find them.
[Miscellaneous Android Development] Ashok.Vardhan:
I have a MacBook Air with Bootcamp installed with Windows 10. So I installed the Android SDK and Google USB drivers and that did the trick. Now I have drivers installed that recognized my Lenovo Tab M8 (FHD) (TB-8705F) in Android mode as well as fastboot mode.

Success!

I was able to unlock the bootloader!

I will try Diplomatic's method once again and see if it works. Update: It still does not. So back to square one. Only advantage now I have an unlocked bootloader.
[Miscellaneous Android Development] Duhjoker:
Hey Diplomatics trick here is really for those devicrs that cant get into fastboot mode and unlock thier bootloaders. If you have an unlocked bootloader, go for the glory and the gold. Flash the twrp for your device and have magisk patch a boot.img or flash the twrp and flash magisk from inside twrp and you would have full root plus a recovery that can back up and restore your whole device.
[Miscellaneous Android Development] Ashok.Vardhan:
That was the first path I had thought about for rooting, however, being a newly released device, there is no TWRP available for this tablet yet. So I searched high-and-low for other methods and stumbled upon Diplomatic's method.
[Miscellaneous Android Development] AstonSmith:
Hello friends,

I have a Lenovo Tab E7 (TB-7104F). Unfortunately the temp-root didn't work, it can't get the kernel symbol table.

C:\Users\Aston\Desktop>adb push mtk-su /data/local/tmp/
4048 KB/s (64780 bytes in 0.015s)

C:\Users\Aston\Desktop>adb shell
TB7104F:/ $ cd /data/local/tmp
cd /data/local/tmp
TB7104F:/data/local/tmp $ chmod 755 ./mtk-su
chmod 755 ./mtk-su
TB7104F:/data/local/tmp $ ./mtk-su -v
./mtk-su -v
armv7l machine
param1: 0x1000, param2: 0x8040, type: 11
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

There is no system image available but the source code is downloadable. Unfortunately I am too new on this forum to post an URL.

But if you imagine download . lenovo . com and then

/consumer/mobiles/tb_e7_7104f_open_source_code_v1.0_201808.zip

that should work.

I think this tablet exposes an ability to unlock the bootloader, but there doesn't seem to be a custom recovery image around for it.

It's not important that I root this device, I was just curious about it really. Thanks for any thoughts and to all your hard work.
[Miscellaneous Android Development] Divogame:
Magisk Install.

thank you. I use Autospy to analyze .img. But there was a problem, after I used "Temp root", even though the device successfully reported, but I couldn't use "Adb Shell" - "Su", which meant I still didn't have root access device after rooting. Regarding the installation of Magisk, I have not yet tried and know how to install it directly with the file "magisk.zip", you can give me the link to install instructions. thank you.

My device is Oppo and there is no Fastboot to install Magisk from TWRP. I don't know how to install "Magisk" directly after "Temp root". looking forward to the tutorial. thanks