If you don't achieve root on a particular run, the "UID: N cap: xxxxx." line will reflect that. Important: in rare cases, it may be necessary to run the tool multiple times before you hit UID 0 and get selinux permissive. Mtk-su -s: Prints the kernel symbol tableIf you see any errors other than about unsupported or incompatible platform or don't get a root shell, report it here. Connect your device to ADB and push mtk-su to your /data/local/tmp folder.The notable devices that need the arm version are the Fire HD 8 2018, Fire 7, and Fire HD 10 2019. The arm64 one is suitable for most devices. Differences between the flavors:Īrm: 32-bit userspace on a 64-bit or 32-bit kernel (will also work in 64-bit userspace) Inside will be 2 directories: 'arm' & 'arm64' with an 'mtk-su' binary in each. Download the current mtk-su zip file to your PC and unzip it.A PC with ADB installed to interact with your device, orįamiliarity with ADB (if using PC) and basic Linux shell commands.Proficiency with the Thanks button under XDA postsĪ Fire HD tablet based on mt8163 or mt8173 (or another MTK ARMv8 device) No one else is responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software. Note that for Fire OS 5, OS version 5.3.x.x is newer than 5.6.x.x.Īmazing Temp Root for MediaTek ARMv8: expanded thread covering all compatible MTK devicesĪnything you do that is described in this thread is at your own risk. Various phones and tablets up to Android 9.x (see link below for full list) Software root method for Mediatek MT816x, MT817x and MT67xx!Ī tool that gives you a temporary root shell with Selinux permissive to do with as you pleaseįire HD 8 8th gen (2018) (thanks - up to Fire OS 6.3.0.1 onlyįire HD 8 7th gen (2017) - up to Fire OS 5.6.4.0 build 636558520 onlyįire HD 8 6th gen (2016) (thanks - up to Fire OS 5.3.6.4 build 626536720įire HD 10 7th gen (2017) (thanks - up to Fire OS 5.6.4.0 build 636558520 onlyįire TV 2 2015 (mt8173-based) (thanks - up to Fire OS 5.2.6.9 onlyįire 7 9th gen (2019) (thanks - up to Fire OS 6.3.1.2 build 0002517050244 onlyįire HD 10 9th gen (2019) - up to Fire OS 7.3.1.0 only UPDATE: I put the mtk-su file from the ARM folder in the zip file and chmod 755 to it (and ls -l shows that it has the execute permissions) and I get the following error: I just received my new tab yesterday and I am looking into doing what I can toward achieving some sort of root for starters. What am I doing wrong or is this what happens for being 7.3.1.6? I was 7.3.1.2 I think it was last night but then I woke up to the dreaded update to 7.3.1.6 successfull message. mtk-su: syntax error: unexpected ')'Īs a side note, I also get the syntax error unexpected ) error line when trying to execute any other ZIP file such as magisk. Whenever I try to execute the mtk-su on my 9th gen Fire 10 HD via ADB, I get the error below (even though I am in the right directory and I successfully chmod 755'd the file): When flashing mine, I would get an error on the PC, but the tablet would indicate success with the prompt to power off and unplug the tablet.Trying to mtk-su on 7.3.1.6 - I get an error If everything checks out, then run brick.sh and follow the prompts on the PC, and then the tablet. Run all commands as root from linux, either with sudo or login as root with "su -l" The boot loader uses a different driver from adb, so run fastboot devices to ensure all the driver are working. Then run adb reboot bootloader to get to the bootloader (should say "=> FASTBOOT mode." in white text in one corner with a black screen) Then run abd devices to ensure that everything has been set right on the tablet. Once the tablet is connect to the PC, run lsusb to verify that the device is visible. You must use linux, as the script calls an ELF fastboot binary which has been hacked to flash the modified brick.img. I've had problems in the past with fastboot and cables that worked fine for ADB. Use a high quality cable to connect directly to one of the ports on the computer. In linux, extract both archives, you should end up with all files in one directory called amonet. I'm assuming that you downloaded amonet-suez-v1.1.2.zip and brick-suez.zip from the this thread? On my devices, it took about 45 seconds to write, with one taking almost 200 seconds (not sure why one was different, I just moved on). The "brick.img" that is being written is 114MB. It sounds like there is a communication error.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |