yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] deneb71:
I tried on a Huawei Y6 2019 MRD-LX1.

The procedure works up to chmod, but when I execute, it says "No such file or Directory".

I don't get it !

HWMRD-M1:/data/local/tmp $ ls -l
total 64
-rwxr-xr-x 1 shell shell 65216 2019-01-01 00:00 mtk-su
HWMRD-M1:/data/local/tmp $ ./mtk-su
/system/bin/sh: ./mtk-su: No such file or directory
1|HWMRD-M1:/data/local/tmp $
[Miscellaneous Android Development] Tech0308:
Hmmm, have you chmod +x (or chmod 755) the file?
[Miscellaneous Android Development] deneb71:
I have chmod 755 just like in the tutorial.
[Miscellaneous Android Development] Joshch96:
Just Tried this on a Motorola Moto G22 & it doesn't appear to be working.

using stock firmware with build number : STA32.79-35

Error is : Failed critical init step 1

not sure if i've gone wrong somewhere or not, followed the instructions and have an okay understanding of how linux command lines usually work.

android version : 12

stock rom link if needed : https://mirrors.lolinet.com/firmwar...waiip_g_user_CID50_sign_20220228045343_S3.zip

chipset is : MT6765
[Miscellaneous Android Development] carlosyoan99:
Don't work with my lg x charge
[Miscellaneous Android Development] mrmazak:
This method has been patched several kernel versions ago. Not surprised it does not work for you now. This was few years ago. I do not have anything to do with the mtksu binary or development of it. Sorry I can't do anything to help
[Miscellaneous Android Development] Antdoid:
is there any plans to support fire hd 8 (2017 edition) with fireos 5.7.0.0 (659662020)? or at least a way to downgrade fireos
[Miscellaneous Android Development] mdhelaluddinsa3456@gmail.:
...

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

UID: 0 cap: 3fffffffff selinux: permissive

Load policy from: /sys/fs/selinux/policy

20.4:MAGISK (20400)

client: launching new main daemon process

Exit value 0
[Miscellaneous Android Development] sam_86314:
Successfully used this to temp-root a Sugar A100 (cheap Chinese phone).

MT6739WW

Android 8.1.0

October 2018 security patch

mtk-easy-su 2.1.0

Magisk 21.4 (app updated to 22.1)

IMEIs did get wiped.

Now I just need to figure out the init.d scripts so that I don't have to manually run mtk-easy-su every time I reboot.

I tried direct installation from Magisk since this phone's bootloader is unlocked by default, but it didn't work.
[Miscellaneous Android Development] OnyAq777:
Hi what does this

Failed critical init step 1

Mean ? My chipset is mt6757 August 2020. I'm using it in terminal emulators.
[Miscellaneous Android Development] Rortiz2:
Your phone is just not supported by mtk-su.
[Miscellaneous Android Development] OnyAq777:
Okay . I have another question . can you tell me where can I get the previous versions of this tool?
[Miscellaneous Android Development] Rortiz2:
Nowhere. The OP probably decided it wasn't a good idea to keep the older versions. I'm not sure why you would need these, considering they wouldn't support your phone regardless of the release date.​
[Miscellaneous Android Development] :
can't wait to try this
[Miscellaneous Android Development] Nicknackpaddywack101:
Hi,

Does this work for post 2020 chips?

Mine uses the mt8768

Thanks.
[Miscellaneous Android Development] gintama_me:
just try.
[Miscellaneous Android Development] pringo:
Ok, so just to let others know about my experience:

It didn't work on my Revvl 4 (w/o plus), all goes fine till last step which I get "Failed critical init step 1"

I tried it even after resetting the phone back to the factory.

Model: 5007W, Android 10 and bootloader is unlocked (phone gives the option to it!!)
[Miscellaneous Android Development] Nicknackpaddywack101:
Yep, did not work

Apparently even if the security patch is below 2020 the chip itself probably got its issue fixed...
[Miscellaneous Android Development] xShx72:
Hello everyone,

Mind if I ask a silly question on whether it's possible to move a file inside the system partition using a root explorer, or would that brick my device?

I am aware that modifying files inside the system partition does not work, but what about this?
[Miscellaneous Android Development] Nicknackpaddywack101:
Hi, I recommend posting this in Android Q&A next time.

You have to gain root "superuser" access to mount the system partition as read write (there are other ways of course) to modify them. If you want to modify a file in here, do at your own risk. If you simply want to put a file in here (why would you want to do so?) then it would not make sense for it to brick your device, unless it is some executable file.
[Miscellaneous Android Development] xShx72:
Thanks for the reply, I'll try posting there. I have acquired temp root through diplomatic's guide, but as it's systemless I am not sure whether I should tamper with the system partition. The reason why is so I can use a spoofing app in expert mode, which in turn needs to be moved to the system.
[Miscellaneous Android Development] alecxs:
Not working tested on Redmi 6 (cereus) Android 9.0 MIUI 11.0.4.0.PCGMIXM (global) all it does is printing armv7l machine and reboot. Just for fun as bootloader is unlocked already :)
[Miscellaneous Android Development] Nurdos1973:
ОOk
[Miscellaneous Android Development] Kilmo3.0:
Please, how to root Huawei Y5 Prime 2018 DRA-LX2 C636
[Miscellaneous Android Development] Nicknackpaddywack101:
Hi, you might have posted in the wrong thread.

Check if you have a "compatible" mtk device and run the tool for yourself to see if it works.
[Miscellaneous Android Development] masterpost2004:
Hi guys

Is there any solution to "failed critical init step 4" ? I am trying to root fire HD8 2018 FireOS 6.3.1.4
[Miscellaneous Android Development] Parrynormal:
Hi Guys Its my first attempt at this I'm using a Mt 6852 Samsung clone android 12 I ran the script in 32 bit and it keeps giving me this error

Mtk-easy-su 2.1.1

extracted magisk-boot.sh

extracted 32/magiskinit

extracted 64/magiskinit

extracted 32/mtk-su

extracted 64/mtk-su

[0]

[0] 12.0

[0] Wed Mar 1 21:38:03 SAST 2023

[1] ls: Unknown option '-1'. Aborting.

[0] Processor : ARMv7 Processor rev 3 (v7l)

processor : 0

BogoMIPS : 32.50

Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x0

CPU part : 0xc07

CPU revision : 3

Processor : ARMv7 Processor rev 3 (v7l)

processor : 1

BogoMIPS : 32.50

Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x0

CPU part : 0xc07

CPU revision : 3

Processor : ARMv7 Processor rev 3 (v7l)

processor : 2

BogoMIPS : 32.50

Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x0

CPU part : 0xc07

CPU revision : 3

Processor : ARMv7 Processor rev 3 (v7l)

processor : 3

BogoMIPS : 32.50

Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x0

CPU part : 0xc07

CPU revision : 3

Hardware : MT6582

Revision : 0000

Serial : 0000000000000000

[0] MemTotal: 985212 kB

MemFree: 42028 kB

Buffers: 3612 kB

Cached: 231476 kB

SwapCached: 5384 kB

Active: 261656 kB

Inactive: 311640 kB

Active(anon): 171088 kB

Inactive(anon): 169872 kB

Active(file): 90568 kB

Inactive(file): 141768 kB

Unevictable: 2820 kB

Mlocked: 1464 kB

HighTotal: 483328 kB

HighFree: 21612 kB

LowTotal: 501884 kB

LowFree: 20416 kB

SwapTotal: 524284 kB

SwapFree: 227928 kB

Dirty: 1948 kB

Writeback: 0 kB

AnonPages: 340692 kB

Mapped: 115900 kB

Shmem: 1216 kB

Slab: 39176 kB

SReclaimable: 11984 kB

SUnreclaim: 27192 kB

KernelStack: 12928 kB

PageTables: 22484 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 1016888 kB

Committed_AS: 27271560 kB

VmallocTotal: 499712 kB

VmallocUsed: 150992 kB

VmallocChunk: 97984 kB

Error running exec(). Command: [free] Working Directory: null Environment: null[0] Linux version 3.10.54 (yanhb@lmkj-S2600CW) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Apr 29 15:03:05 CST 2022

[1] /data/data/juniojsv.mtk.easy.su/files/magisk-boot.sh[13]: dirname: not found

/data/data/juniojsv.mtk.easy.su/files/magisk-boot.sh[113]: cd: /32: No such file or directory

deleted magisk-boot.sh

deleted 32/magiskinit

deleted 64/magiskinit

deleted 32/mtk-su

deleted 64/mtk-su

I believe the previous owner possibly rooted the phone and then unrooted as when I check root status it says root not properly installed ? Is there another method where I can achieve root or am I doing something wrong ? Thanks for all your effort .
[Miscellaneous Android Development] alecxs:
@Parrynormal kindly read the OP first. Note that the app is not a part of this thread. Therefore it's unlikely you will get an answer here.
[Miscellaneous Android Development] Parrynormal:
Sorry it's my first time on here what thread was I supposed to post to?
[Miscellaneous Android Development] Zai23:
Does this work with a Keefe SCORE 7c Tablet?
[Miscellaneous Android Development] HoanG8:
step 1: have computer and use good cable for better

step 2: try to install oppo usb driver, mtk driver and libusb

step 3: use tool like unlocktool or mtk client to unlock bootloader and get the boot.img in rom (if you use oppo chp2020 you can get it from the internet with twrp to install custom rom, or like me use oppo chp2073 you have to read gpt and backup the boot.img inside the rom)

step 4: download magisk and patch the boot.img (don't need the vbmeta)

step 5: wait the magisk flash the new boot, it will automatic reboot the phone. you have (70% battery or higher or the battery dead and it will fail with bootlooping and if you don't know how to flash again, you have to waste time and money to flash back and root again)

step 6: if it success download the huskydg bootloader protector and do what ever you can do with your phone

goodluck :3
[Miscellaneous Android Development] notreal456789:
Hello dev, diplomatic ! :)

I'm looking for help with mediatek devices

specifically this one: Infinix zero 5g 2023 TURBO/Ant-Man and the Wasp: Quantumania Edition.

Model: X6815C

Chipset: MediaTek MT6877V/TTZA

Dimensity 1080

Similar: Model#

X6815

X6815B

Can someone help me or guide me on how to he re/build my Kernel with SElinux to PERMISSIVE

Viper4Android-repack:
https://github.com/programminghoch10/ViPER4AndroidRepackaged

Or

James DSP:

GitHub - james34602/JamesDSPManager: Audio DSP effects build on Android system framework layer. This is a repository contains a pack of high quality DSP algorithms specialized for audio processing.

Audio DSP effects build on Android system framework layer. This is a repository contains a pack of high quality DSP algorithms specialized for audio processing. - james34602/JamesDSPManager

github.com

Neither of these 2 DSP mangers will work in the default XOS Android 12 that came with this phone.

Audio </3

Optionally:

I would like to cut up this script to Maby force my SElinux permissive with a start/initscript
[Miscellaneous Android Development] insestito:
Something new for MT8696? (amazon fire tv 4k max)
[Miscellaneous Android Development] Zieku Hades:
somehow, ./mtk-su won't work in mine.

C:\Users\wwwma>adb shell
shell@x6_v5_x50:/ $ cd /data/local/tmp
shell@x6_v5_x50:/data/local/tmp $ chmod 755 mtk-su
shell@x6_v5_x50:/data/local/tmp $ ./mtk-su
CANNOT LINK EXECUTABLE: cannot locate symbol "setns" referenced by "./mtk-su"...

Model: Note10

Manufacturer: Alps

Version: 4.4.2

Non-rooted
[Miscellaneous Android Development] nns3144:
Password:(
[Miscellaneous Android Development] nns3144:
1

pkg install git

2

git clone https://github.com/JunioJsv/mtk-easy-su/[lCODE]
[B]3[/B]
[ICODE]cd mtk-easy-su

4

Done!
[Miscellaneous Android Development] nns3144:
Password: 57g3ubs

Verify: 57g3ubs

Use you with passed on ? Y/n :
[Miscellaneous Android Development] ginger345678:
what is this
[Miscellaneous Android Development] luridphantom:
you didnt upload it properly, try again
[Miscellaneous Android Development] alecxs:
it's recommended to get firm with basic cmd line commands such as cd first!
[Miscellaneous Android Development] marzieiskewl:
Made an account just to say that mtk-su and the old bootless root method worked beautifully on my Alcatel Pixi 4 (6) 3G (8050E) running Lollipop 5.1.

It uses the MT6580 (or MT8321? CPU-Z is giving me conflicting info)

I had to modify the magisk-boot script slightly by removing the -s flag from the cmp commands, but after that, it works.
[Miscellaneous Android Development] InoCityXP:
Hello, i have an LG K10 2017 that have the MT6750, i did that root before and works perfectly but i formatted i because i had an SDK error before, now the root works but i cannot install any magisk modules, anyone can help me?
[Miscellaneous Android Development] belphegor75:
unsolvable problem i really need help

I bought this Chinese tablet last month, it's a BRILLAR T16 - 10 inches - android 12 - 6 G ram - 128 GB Mediatek MT8183 (I've captured the general, soc and system info I've attached)

first of all, I look at the system info, and I see that no updates are available and that the latest security patch dates back to May 2022.

With the information I've obtained, I've searched everywhere on the internet and of course BRILLAR isn't known anywhere, just like INCAR or a correspondence at TECLAST.

to be able to install a gsi I said to myself, I'm going to extract the firmware to recover the boot.img and the vbmeta so I'm going to root this tablet.

1 - I unlocked the bootloader with fastboot result PASS

2 - I've enabled usb debugging

3 - I've looked everywhere but there's no custom recovery available.

4 - no boot.img so no magisk, so I've tried a thousand different ways of rooting this tablet both from my pc and with an apk (kingoroot etc), each time it's the same result ROOT FAILED

in the end I tried with dsuloader and dsu sideloader with and without shizuku and with several different gsi, each time it told me "system update impossible unauthorized access".

that's why I'm posting this message because I don't know what to do anymore and I'm stuck.

If any of you have any advice or solutions, please let me know. I'd be extremely grateful if you could help me.
[Miscellaneous Android Development] jeff_0618:
0000000000000001 is not a valid address
avc_denied not found
selinux_enforcing not found
starting /system/bin/sh
UID: 2000 cap: 0000000000 selinux: enforcing

i guess my phone will never be rooted even if its been in orange state
[Miscellaneous Android Development] Azaze666:
If you are in orange state your bootloader should be unlocked, and even if it isn't you can try mtkclient to unlock it, after that with mtkclient you can backup boot, patch it with magisk app, flash the blank vbmeta in mtkclient and the patched boot and you should be done. Am I missing something?
[Miscellaneous Android Development] Azaze666:
Look at my previous message, you can backup boot and patch it to get root
[Miscellaneous Android Development] stevezmtstudioS:
I'm sorry to have disturbed you. But the existing MTK device I have cannot run MTK-SU. It is a translation pen with less than 500MB memory and only surprisingly 1GB of user storage. It is highly customized, has no bottom navigation keys, no taskbar (but can be opened with adb), and can't even use Lawnchair as the desktop. I have to rely on MTK Logger to launch the Android settings page.

It is running Android 5.0.2, with a security patch from 2016. Executing "adb shell cat /proc/cpuinfo" reveals that its chipset is MT6580, so in theory, it should be able to run this script (or binary file?).

::EDIT::

in build.prop, it said its chip code is mt6582.it makes me confused.

>adb shell cat /proc/cpuinfo
Processor : ARMv7 Processor rev 3 (v7l)
processor : 0
BogoMIPS : 26.00
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 3

Hardware : MT6580
Revision : 0000
Serial : 0000000000000000
>_

Spoiler content hidden.

However, just like my annoying luck, it always fails and reports "Failed critical init step 1: Incompatible platform". I have used the search function of XDA Forums, but I haven't found any failures and discussions about MT6580. I hope to use this temporary root permission to allow me to modify the default installation location of the application. I hope to get help. Thank you.

$ ./mtk-su -v
armv7l machine
Failed critical init step 1
Incompatible platform
1|shell@j20:/data/local/tmp $ _

Spoiler content hidden.
[Miscellaneous Android Development] DaeDae<3:
What about armv7l? Anything on that?
[Miscellaneous Android Development] alecxs:
for Android 5.0.2 there might be other exploits that still work, like CVE-2016-5195
[Miscellaneous Android Development] edmakmobile:
Failed critical init step 3.

I've tried Mtk-su 22 and 23. ver 21 is not available for me to test. Can repost this zip?
[Miscellaneous Android Development] stevezmtstudioS:
I just tried dirty COW, but my device seems like 32-bit ARM only...

Mimicking the infamous ZNIU way of getting root doesn't work either. (iovySU)

So I just welded a set of volume keys through the contacts on the motherboard so that I could press the volume up key when executing the command fastboot oem unlock to allow BL verification to be disabled. Then it's a simple SP tool to read back, patch the kernel, and take a whack from magisk's bootloop ;);

Thank you for your advise:)

(No, my device doesn't bricked. just my OEM made too much customization.)
[Miscellaneous Android Development] remyxk:
Hey I have some questions.

Just to make it clear, I'm new to the community and I have no experience with rooting or Magisk at all. I'm trying to root my tablet to install some apps and test it out.

I have a Dragon Touch K10 (Build number: Dragon_Touch_Notepad_K10_20210311, running Android 9) and it's in the list of compatible devices for this method.

I'm using Windows 11. I have ADB installed and I was able to successfully unlock the bootloader.

Can anyone let me know if it's possible to root the tablet using this method and guide me on how I could do that? (using Magisk)

Also sorry if I'm asking a very obvious question, as I said I have no experience rooting so I have no idea what to do. I read the whole thread and I'm still pretty confused and I don't want to brick my tablet.
[Miscellaneous Android Development] luridphantom:
if your device bootloader is unlocked then its safe, if not then a small risk of bricking
[Miscellaneous Android Development] remyxk:
It won't work for me, here are the outputs:

Spoiler content hidden.

Spoiler content hidden.

Here's some information about my device:

> Notepad_K10:/ $ cat /proc/cpuinfo

processor : 0
Processor : ARMv7 Processor rev 3 (v7l)
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 26.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 3

Hardware : MT8163
Revision : 0000
Serial : 0000000000000000

> Notepad_K10:/ $ getprop | grep product

[ro.build.product]: [Notepad_K10]
[ro.product.board]: [w096a12_wxga]
[ro.product.brand]: [Dragon_Touch]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abilist]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: []
[ro.product.device]: [Notepad_K10]
[ro.product.first_api_level]: [28]
[ro.product.locale]: [en-US]
[ro.product.manufacturer]: [Dragon_Touch]
[ro.product.model]: [Notepad_K10]
[ro.product.name]: [Notepad_K10]
[ro.product.vendor.brand]: [Dragon_Touch]
[ro.product.vendor.device]: [Notepad_K10]
[ro.product.vendor.manufacturer]: [Dragon_Touch]
[ro.product.vendor.model]: [Notepad_K10]
[ro.product.vendor.name]: [Notepad_K10]
[Miscellaneous Android Development] alecxs:
How can Allwinner device be in the list of compatible devices for this method?
[Miscellaneous Android Development] remyxk:
Sorry I didn't see it said Allwinner and I thought that was the same tablet as mine lol. I was just asking for a way to root this tablet and I referenced that thread because I thought it could help.

I provided some more information about my device here: https://xdaforums.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/post-89186764

Also I wasn't asking for a way that was specific to this method, I was just asking if it was possible to root my device (with mtk-su or not).
[Miscellaneous Android Development] luridphantom:
your device is too new to support mtk-su. only older devices up to 2019 and maybe 2020 can support this
[Miscellaneous Android Development] alisha15j90:
Which method should I try on MT6833 model( Redmi note 11T 5G)
[Miscellaneous Android Development] ukw9wp2k:
Dhjeie
[Miscellaneous Android Development] teegrix:
sony xperia l2 is not compatible even though it has a security patch of 2019 and android 7? please help
[Miscellaneous Android Development] connor11016:
how do i put mtk-su into path/to/
[Miscellaneous Android Development] ZG_DEV:
Well, firstly let me congratulate you for this great achievement, your temp. Root access works with that device up to a.39.

thanks a lot for what you did, you gave me the passion to finally root this phone with a guide I typed it myself, with some pieces of advice from @Anonymous V .

-ZG089, the first rooter for OPPO A5s device in the world 🌍 ❤️
[Miscellaneous Android Development] ambushed:
Unlockable bootloader Visible ZTE Blade 10 Prime Z6530V Android 9 Pie Z6530VV1.0.0B07 can get root access using https://xdaforums.com/attachments/mtk-su_r23-zip.5085853/ from OP as somebody else had confirmed earlier per https://xdaforums.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/post-79354359.

Tried following Full bootless root with Magisk for 22.x+ by @HemanthJabalpuri to get bootless root using https://github.com/topjohnwu/Magisk/releases/download/v27.0/Magisk-v27.0.apk.

magisk-boot.sh didn't get far due to /sbin being in a read-only FS.

# This may crash on system-as-root with no /root directory
./magisk -c >&2
Segmentation fault

touch /sbin/.init-stamp
touch: cannot touch '/sbin/.init-stamp': Read-only file system

Is there any possibility to get bootless root with Magisk on this Z6530V?

Suggestions on how to proceed?

Running

mtk-su -v

in Termux shows:

param1: 0x1000, param2: 0x8040, type: 14
Building symbol table
kallsyms_addresses pa 0x40ee5e00
kallsyms_num_syms 51523, addr_count 51523
kallsyms_names pa 0x40f4aa00, size 659974
kallsyms_markers pa 0x40febd00
kallsyms_token_table pa 0x40fec400
kallsyms_token_index pa 0x40fec800
Patching credentials
Parsing current_is_single_threaded
ffffff80083f7e14+44: ADRP x8, 0xffffff800983d000
ffffff80083f7e14+48: ADD Rd, x8, 0x5c0
Possible list_head tasks at offset 0x480
comm swapper/0 at offset 0x758
Found own task_struct at node 1
cred VA: 0xffffffc026cc2900
thread_info flags VA: 0xffffffc00ab65000
seccomp mode VA: 0xffffffc00ab65480+370
init_task VA: 0xffffff800983d5c0
Parsing avc_denied
ffffff800837c5b0+10: ADRP x11, 0xffffff8009a97000
ffffff800837c5b0+14: LDR [x11, 0xb20]
selinux_enforcing VA: 0xffffff8009a97b20
Setting selinux_enforcing
Selinux is already permissive
Trying seccomp-filtered syscall
Caught SIGSYS
Disabling seccomp
thread flags: 0x00000800
Trying seccomp-filtered syscall
TIF_SECCOMP deactivated
seccomp mode: disabled
starting /data/data/com.termux/files/usr/bin/bash
UID: 0 cap: 3fffffffff selinux: permissive
[Miscellaneous Android Development] qfox9:
The mtk-su arm binary not working on

Xiaomi Redmi 6, armv7l, MT6762V/CB.

It crashes the system.

Is there any older version for this 32 arm architecture?