yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] CXZa:
These sprint etc. devices don't give you kdz files that might help you to downgrade??

But you might be able to switch to a firmware of similar device.

And then if you have a backup made, you might be able to restore it, IDK...

https://xdaforums.com/android/general/unlock-q710al-gsm-service-apn-t3995769
[Miscellaneous Android Development] Ingorat:
Hi i am having trouble with rooting a huawei y6 pro 2019 with mediatek MT6761, 3GB ram

Tried both bootless method and mtk-su method.

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

armv8l machine

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

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
[Miscellaneous Android Development] BlondeGotti95:
kinda new to this

serre hftgf
[Miscellaneous Android Development] BlondeGotti95:
kinda new to this

after i put in the code : adb push path/to/mtk-su /data/local/tmp/

(am i supposed to copy and paste that exactly or is it just a format example and i need to put my own info)

i keep getting error "Push requires an argument" or it will give error "No such file or Directory"

Im BRAND NEW to this actually lol have a little expierence with adb but not much as you can tell

but yea all advice will be appreciated

:silly:
[Miscellaneous Android Development] Rortiz2:
DON'T REPLACE THAT PARTITION. Automatically bricked my Aquaris M8. It can be recovered with SP Flash tools but if it is a xiaomi it will not have a solution!
[Miscellaneous Android Development] mrmazak:
Wow, see, just another example of how one root solution does not work for all devices.

I have replaced that file on all my phones from 'BLU' and it works to restore locked status. And back to unlocked.

Also when I triggered a RED bootloader state on dm-verity enforced device it restored green status
[Miscellaneous Android Development] Rortiz2:
Well, I flashed the wrong seccfg so thats the reason of why I bricked it but with the correct it worked! you are a genius!!!

Now we can unlock the BL without losing any data!!

Here's the output:

shell@Aquaris_M8:/ # dd if=/sdcard/seccfg of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/seccfg <
512+0 records in
512+0 records out
262144 bytes transferred in 0.024 secs (10922666 bytes/sec)
shell@Aquaris_M8:/ # exit
shell@Aquaris_M8:/ $ exit

C:\Users\rorle\Desktop\Rortiz2\ANDROID\ADB AND FASTBOOT>adb reboot bootloader

C:\Users\rorle\Desktop\Rortiz2\ANDROID\ADB AND FASTBOOT>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1a800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 73800000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:persist: 3000000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: [COLOR="Red"]yes[/COLOR]
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: BQ_AQUARIS_M8
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.308s

C:\Users\rorle\Desktop\Rortiz2\ANDROID\ADB AND FASTBOOT>fastboot reboot
rebooting...
[Miscellaneous Android Development] ahhl:
[emoji106]yea..... i am going to try this....

i am going to dd all the partitions

but what you modify in that seccfg partition?

and step for noob pls...., [emoji120]
[Miscellaneous Android Development] Rortiz2:
Well I unlocked my device and I extracted the seccfg, I relocked again and when I flashed the unloked seccfg the bootloader has been unlocked and I don't losed any data. IDK if it will work in your Xiaomi device..
[Miscellaneous Android Development] diplomatic:
Yes, you can flash that partition with backups from the same device. But there is no chance that copying one from another device will unlock yours. At best, it will restore a default locked state. At worst, it will stop your device from booting. (Thanks for verifying that for us, [MENTION=8978978]Rortiz2[/MENTION]) That's because of the device-specific encryption that's used on the bulk of that data, which MTK calls anti-clone technology.

You don't modify it directly due to the encryption I mentioned. But in theory, it can be done with hacks on MT6xxx phones.
[Miscellaneous Android Development] bigrammy:
I am not sure if this method HERE could be used or not to make locking <> unlocking easy?

If encryption is involved then maybe it wont work for newer MTK's I don't know :confused:

It basically involves comparing partitions byte for byte from a locked device and a unlocked device and looking for the byte changes.

I looked into this for the Fire Phone but a bootloader unlocked fire phone did not exist to make the comparison so a none starter for that Phone. :(
[Miscellaneous Android Development] diplomatic:
OK, a lot of things to unpack here. That thread you noted is about some pretty old Android 4.x era Qualcomm devices. I remember looking at it a while back. From what I could tell, the lock state was stored at some offset on the aboot partition. It was a simple byte change to go between locked and unlocked. But that had nothing to do with MTK. And moreover, I don't think that's how the lock state on Qcom is controlled these days. It has to be much more secure now. (I can't find much info on that but I'm guessing the default method involves storing it in the RPMB region with help from TrustZone. Some OEMs (coughSamsungcough) set efuses on the SoC, which are permanent flags burned into the chip. That's pretty well known.)

But back to Mediatek.... that vendor always used encryption on the lock state since the mt65xx days. This isn't anything new. (I think that's because they don't shy away from letting users write to the emmc with SP Flash Tool.) Fortunately, that encryption can be accessed from within Android with root access. I've done it in my ZenPad Z500M unlock tool. However, that particular method only applies to tablets. It will need a different approach to be ported to phones. I can probably make a universal unlock tool for root. (But not feeling extremely motivated to tackle that due to the underwhelming response to this tool here.)

The Fire Phone, that may not even have been unlockable with simple emmc writes. Amazon likes to replace the default bootloader security system with their own. I don't know if that phone was too old for that or not. For modern devices, their unlock method involves flashing a signature file unique to the device that only their key can generate.
[Miscellaneous Android Development] bigrammy:
WOW thanks for the detailed info very informative indeed :good:

I wouldn't feel too demotivated as what you have achieved is really outstanding work and you should get some recognition for this without a doubt.

Speaking for myself I can only say that I think your mtk-su is Fantastic!! and a god send for any popular OEM mediatek device owners like Sony Nokia HTC LG Amazon and others.

At the moment there are many MediaTek haters here on xda without any good reason it seems :mad: so many dev's seem to shy away from this SoC but with the Big OEM's producing quality devices at a pretty low cost using MTK chips it will only be a matter of time before it becomes too irresistible for them to take on this SoC then everyone will be worshipping the ground you walk on :laugh:

Yes Amazon did a bang-up job on locking down the Fire Phone sadly. :( It was a good phone at the time with Great radio band support so an ideal when travelling around the globe. :cool:

:highfive:
[Miscellaneous Android Development] ahhl:
no chance for q-su?

i got vivo. qualcomm. bootloader lock.

no development at all. dead phone.
[Miscellaneous Android Development] DelphinusMinor:
Will this method work for the Canadian Fire HD 10 running the latest OS of 5.6.4.0 from March 29th?
[Miscellaneous Android Development] diplomatic:
[MENTION=4880512]DelphinusMinor[/MENTION], yes, as long as it's not that awful Quebec version.
[Miscellaneous Android Development] DelphinusMinor:
How would I know if it was?
[Miscellaneous Android Development] bigrammy:
:laugh:

Just try it and see if it works as far as I know it wont do any damage and the worst thing that can happen is that you wont get temp root so give it ago. ;)
[Miscellaneous Android Development] DelphinusMinor:
I may just do that sometime soon.
[Miscellaneous Android Development] diplomatic:
IDK, I heard it's the one that tends to secede from the Amazon ecosystem.

But no, all nationalities of that tablet should be compatible. ;)
[Miscellaneous Android Development] ahhl:
i have been playing with AIK on my stock images. certain files, which i backup previously, cannot be unpack with android kutchen. surprisingly seccfg partition can be unpack by AIK

i am still not able to autoboot on charger. changing few lines in init.rc not successfully to autoboot it. [emoji22]
[Miscellaneous Android Development] mrmazak:
There is sometimes a fastboot command that MAY

enable that.

Something like "fastboot oem off-mode-charge 0"

To make off mode chargeing off, which makes device boot up on USB power

And "fastboot oem off-mode-charge 1" would allow chargeing when off and not automatically boot up
[Miscellaneous Android Development] bigrammy:
dd backup helper script updated :)

https://xdaforums.com/showpost.php?p=79469145&postcount=91

Let me know if anyone encounters any issues.
[Miscellaneous Android Development] AmoKun:
You should push the mtk-su file to /data/local/tmp

the thing that will change is the Mtk-su repertoire

Just copy mtk-su where you have the adb then type

adb push mtk-su /data/local/tmp

adb shell

cd /data/local/tmp

chmod 755 mtk-su

./mtk-su
[Miscellaneous Android Development] Mistercatapulte:
Dump Wiko Jerry 3 done with last update!
[Miscellaneous Android Development] alecxs:
[MENTION=7825384]AmoKun[/MENTION] it is really nice from you to help out.. however, mtk-su requires some basics, this root method is for advanced users and not a copy&paste solution for everyone. there is a reason why such questions like this example from BlondeGotti95 should remain unanswered ;)

[MENTION=10594261]BlondeGotti95[/MENTION] this method is not for Samsung
[Miscellaneous Android Development] djcal1985:
Working good stylo 4 mtk
[Miscellaneous Android Development] diplomatic:
I'm not sure why it failed to get the symbol table. But the bigger problem with that phone is that the kernel does not support selinux permissive mode. Even if I fix the symbol table detection, selinux will still be active and will negate all administrative privileges. That's why recent Huawei phones are listed as "Support Problematic." There's a way around this by patching some kernel code but you would have to somehow persuade me to do this. PM me if you want to pursue this...

That phone works with mtk-su, is that what you're saying?
[Miscellaneous Android Development] byfgjk:
Possible to root 5.3.7 yet? Or downgrade to a rootable version?

This is on suez
[Miscellaneous Android Development] BloodStormm:
Not Working on Lenovo A5 L18021 (Android 8.1)

I installed Magisk 7.1.1

In my phone Bootloader Locked.

Security Update 5 January 2020

I did everything according to the instructions(Bootless root with Magisk and MTK-SU) and ran the script.

[IMG="Screenshots"]https://c.radikal.ru/c10/2003/f9/04bbbea28da8.jpg[/IMG]

It seems the Script is installed correctly, the Magisk too.

But Root not worked. Root Checker says you have no root permission.

And even the Magisk window does not open to confirm the root.

I also tried the mtk-easy-su program.

github.com/JunioJsv/mtk-easy-su/issues/29

Also, the root did not work.

What could be the problem and is it possible to get root on this device?
[Miscellaneous Android Development] diplomatic:
Hmm, that's hard to say. All the logs look fine. You should check some things in a temp root shell. Run mtk-su in adb or terminal. Check if you have root permissions with some commands (e.g. 'ls /data/data'), although I think that part is fine. Also check if magisk daemon is running (after having started bootless root):

ps -eZ | grep -w magiskd

If that doesn't give you a line containing magiskd, then try to start it manually:

magisk --daemon

Check root again. If fails, recheck for magiskd to see if it crashed. After you're done with mtk-su shell, do a 'setenforce 1' before exiting.

It may be a glitch in the OS or Magisk, or possibly some general anti-exploit defense.
[Miscellaneous Android Development] BloodStormm:
I executed the mtk-su script through adb.

But when checking the magisk, writes magisk not found.

[IMG="Screenshots"]https://c.radikal.ru/c09/2003/e7/1752a0b9734d.png[/IMG]

And yes you are right, the first time during check ls /data it was written that there are no permission.

But after running the script it worked.

After I start init.d script in my phone and Magisk started.

And again checked Magisk through ADB.

[IMG="Screenshots"]https://a.radikal.ru/a39/2003/71/3f40ad925f09.png[/IMG]

Magisk on the phone shows is installed, and it seems to work.

But Root Checker is still silent.
[Miscellaneous Android Development] diplomatic:
[MENTION=8778677]BloodStormm[/MENTION], so Magisk Manager does show that root is installed? I thought you said it doesn't. So is the problem that MM does not show prompts for superuser requests? In that case, make sure that MM is off of any battery optimizations. If you still can't get it to show prompts, then go to MM settings and set it to grant by default...
[Miscellaneous Android Development] BloodStormm:
[MENTION=8132642]diplomatic[/MENTION]

I don’t know what exactly is the problem.

I installed a magisk manager.

[IMG="Screenshots"]https://c.radikal.ru/c09/2003/70/faab1b5d5825.jpg[/IMG]

And after running the script. It shows that everything is installed.

[IMG="Screenshots"]https://a.radikal.ru/a25/2003/60/ec92e1ee1c19.jpg[/IMG]

I tried everything, turned off the pop-up window, provided the default root.

But still, the root for applications does not work.
[Miscellaneous Android Development] martinbrecko:
Hello, is there the possibility to downgrade the Fire HD 10 7th generation to use the temporary root? At the moment the firmware 5.3.7.0 is on it. Perhaps via ADB sideload? Or is there another way to root this firmware?
[Miscellaneous Android Development] juanantofb:
Hi, can anybody help me with:

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

I only want install Viper legacy 4.4.

Thanks.
[Miscellaneous Android Development] diplomatic:
Check the unlock thread for suez. I think there may be a way to root/unlock with software still.

Just run that command once in a root shell. Open a terminal app or adb shell, call 'su'. Then in the prompt enter the sed command, then exit.
[Miscellaneous Android Development] jumio:
It's working !!!!

Acer Iconia B3-A40 , with MTK 8127 processor. Worked like a charm! Many, many thanks :D:o:o:D:):):D
[Miscellaneous Android Development] Sahil/nain:
Tested on oppo f5 Stuck on step 4

It said that this script can not work for my device platform

So,i was looking for new rooting methods on xda and i came accross mtk-su somehow. I immediately tried to run this on my device but it sadly failed for me . And for sake of my sanity to my knowledge there is no oppo f5 with Android 8.1 its current version is Android 7.1 .. But thank you for giving this awesome script to us .

Btw if you ever find any new advancements on any oppo f5 devices or need something tested please let me know .

I am sick of color os.please find root for this device someone...
[Miscellaneous Android Development] diplomatic:
[MENTION=6869221]Sahil/nain[/MENTION], ok, good to know. It was probably the last update that blocked mtk-su. If you can find a way to downgrade, that would be your ticket to temp root. Do you remember what FW version you had before? It says A.41 is the latest on the site, and the previous one was A.39. Guessing it worked up till that one...
[Miscellaneous Android Development] realali:
When I run mtk-su in OPPO A7x 4G 128G

The android 7 is success，but android 9 is failed.

Failed critical init step 4

This platform cannot be supported.

It's the android 9 not support?

Can you adapt it?
[Miscellaneous Android Development] diplomatic:
Android 9 is technically supported. In that FW, the loophole that mtk-su uses has been sealed off. Same scenario as Oppo F7, F9, etc. In case you weren't aware, phones and firmwares that were released late last year are already "fixed". As are updates starting with the March 2020 security level. So this goes for everyone: do not update your devices if you want to keep using mtk-su. For most supported devices, the cutoff will be March 2020. For others, it has already happened months ago.
[Miscellaneous Android Development] Force of Fire:
is there a way to backup and restore partition

hi diplomatic I have nokia 5.1 plus and i was able to disable OTA updates by disabling the app responsible for checking for the updates. i disabled the update because android 10 sucks because (Storage Access Framework). and i fully understand why i can't use your root method to write to the system partition. and that because Cryptography. any phone runs android 6+ has a mechanism the check if the system partition has been modified. and if the system partition has been modified it will not match the signature and the phone will refuse to boot. so is there a way to back up the system partition and restore it in case anything bad happens. and it will also make me feel at ease and comfortable about rooting my phone. right now i have not used your tool because i want to create a backup before using it although i fully know that it is a temp root that isn't written inside the system partition. I have seen some posts about partition backups but without any mention of a way to restore the backup. the phone does have a recovery and a download mode. maybe i can use the recovery or the download mode to flash my backup of the system partition if anything bad happens because maybe the system partition has been signed with the same signature that the recovery has been signed with so maybe i can use the recovery to flash my backup. so do you know of any way to back up the partition and restore the backup if anything bad happens
[Miscellaneous Android Development] rlrevell:
Aw man... and I *just* broke the screen on my Xpression Plus 2. If I can get past the startup PIN screen with a mouse/OTA cable or something, I'll try to test this headless. If my dumb ass hadn't power cycled it before realizing the touchscreen was all the way dead...

Then again the K40 looks like a nicer phone anyway...
[Miscellaneous Android Development] Sahil/nain:
My software version is 4.2 right now..my dumb self updated 1 week ago ..And surprise they intensionally slowed down the phone and decreased the battery life by a lot :(
[Miscellaneous Android Development] realali:
My phone's update is 2019-09-05.

I think it's not fixed.

How can I do for you to detect it?
[Miscellaneous Android Development] diplomatic:
Hi Force of Fire,

IDK about that phone in particular. Maybe someone with a Nokia can give you a better answer. Those backups are mostly meant for restoration in Android or a custom recovery. If you have SP Flash Tool access on that phone, you can use that program as well. But having said that, it's pretty hard to change a system or vendor partition. Android does not let you make a dm-verity partition writable. You should also check out if you can install a stock zip package through the stock recovery.

Ouch... I hate it when that happens. Not sure it's worth messing with. You'll need the touchscreen to use it anyway...

mtk-su already detects it. "This platform cannot be supported" means what it says. All of the Oppos that were upgraded from 8 to 9 had the "patch" already integrated when they switched to the new board OS from MTK. A7x looks like the same phone as F7 F9. So that means Android 8 compatibility only. You should have checked the list before applying the OTA...
[Miscellaneous Android Development] Force of Fire:
how can i use SP Flash Tool

the stock recovery only allows to upgrade not downgrade. I am trying to understand how SP Flash Tool works can you tell me what is a (Scatter File) and even if android will not let me write to the system partition but maybe a mistake happens and the system partition will be modified the and then android will refuse to boot and you know the old saying (better safe than sorry)
[Miscellaneous Android Development] DB126:
This question is best answered in your device forum; OT here. Good luck.
[Miscellaneous Android Development] BlondeGotti95:
I Dont have samsung. it is a amazon kindle fire hd 8 7th generation
[Miscellaneous Android Development] Force of Fire:
please the question isn't directed to you

I am not talking to you. so I hope you will be a nice person and stop replying to my posts
[Miscellaneous Android Development] diplomatic:
You're gonna have to do your own homework on that. Check if there are FW packages for SPFT for your phone. (A quick search seems to show there are.) There are also plenty of guides about using that tool. You would use it to restore the FW if the phone does not boot.