RCA Voyager III (RCT6973W43MD) Root Using Magisk_Manager and Stock Boot Image - Android General

First I want to say that I'm not a developer nor in any way an expert and I'm sure that will be apparent as you read my post. I was able to root my Voyager III tablet by reading and following the work of people like diplomatic and topjohnwu, and using the products of their work. I looked everywhere for a specific root method for this little tablet but could never find one. The fact is there has always been a method since topjohnwu's Magisk_Manager's ability to patch stock boot images and re-pack them for use in your specific MTK-based phone or tablet. It just hasn't been obvious that the RCT6973W43MD Android 7.0 was a candidate for that root process...at least not to me. In any case, this is what I did to achieve root. But first...
**Do these steps at your own risk. They worked for me but I won't be responsible for any damage you do to your phone or tablet**
Unlock Bootloader
1. In your tablet, enable Developer Options by going to Settings> About Tablet> Build number. Press "Build number" 7 times to reveal "Developer options." Press Back button to see and enter "Developer options." Enable "OEM Unlock." While you're there, enable "USB Debugging," disable "Automatic system updates" and "Verify apps over USB." Also make sure "Install Apps from Unknown Sources" is enabled.
2. Using adb, after your device is recognized, type:
adb reboot fastboot
fastboot flash oem unlock
fastboot reboot
Your bootloader should now be unlocked. On your boot screen it will say, "Orange State." (never try to re-lock the bootloader because that will put your device into "red state" which is very bad. You've been warned!)
Extract Your Tablet's Boot.img file using MTK-su
1. You need the boot.img file of your specific ROM to allow Magisk_Manager to patch it...in order that Magisk may be installed as superuser. What better place to get that file than your own device? Use diplomatic's MTK-su exploit to gain temporary superuser access to your tablet's root file system. Your boot.img file can be found in /dev.
2. Still superuser under MTK-su, copy the boot.img file to your sd card in at least two locations. The reason for this is to make sure you can easily find it later when you've left MTK-su's root shell. Something like this should work...
cd /dev
cp bootimg /storage/emulated/0
cp bootimg /storage/emulated/0/Download
**Note** In /dev your boot.img file is named "bootimg". When you copy (paste) it to your sd card it will appear as "boot.img".
Patch Your Tablet's Boot.img file with Magisk_Manager
1. Download Magisk_Manager v7.5.1 apk and install on your tablet. Patch your boot.img file. Press Install . Install> "Select and Patch a file". Navigate to your boot.img file and select it. Wait a few seconds for the patching to start and note the location of the newly patched boot image named magisk_patched.img. Flashing this personalized boot image will allow you to install Magisk v20.4.
2. Now using adb and MTK-su again, start a root shell and find the magisk_patched.img file and copy it also in at least two places to make it easy to find and later transfer to your desktop. My experience was that I copied it to my sd card but couldn't find it when i left the root shell and tried to get it onto my desktop. The point is that you want the file in a directory that your desktop file manager can access. I'm a noob so I made a few copies of it.
At this point it might also be a good idea to review topjohnwu's Magisk boot-patching thread here to glean any information that may apply to the Voyager 3, although that tablet is not mentioned by name
3. On your computer using adb fastboot:
adb reboot fastboot
fastboot flash boot /path/to/magisk_patched.img
fastboot reboot
4. Download Magisk.20.4.zip and install it from your tablet's recovery or via adb. You should now be rooted and the Manager app should show both Magisk_Manager and Magisk superuser installed. I know there's probably easier ways to do this, and lots of shortcuts, but this is what worked for me.

akonobi said:
First I want to say that I'm not a developer nor in any way an expert and I'm sure that will be apparent as you read my post. I was able to root my Voyager III tablet by reading and following the work of people like diplomatic and topjohnwu, and using the products of their work. I looked everywhere for a specific root method for this little tablet but could never find one. The fact is there has always been a method since topjohnwu's Magisk_Manager's ability to patch stock boot images and re-pack them for use in your specific MTK-based phone or tablet. It just hasn't been obvious that the RCT6973W43MD Android 7.0 was a candidate for that root process...at least not to me. In any case, this is what I did to achieve root. But first...
**Do these steps at your own risk. They worked for me but I won't be responsible for any damage you do to your phone or tablet**
Unlock Bootloader
1. In your tablet, enable Developer Options by going to Settings> About Tablet> Build number. Press "Build number" 7 times to reveal "Developer options." Press Back button to see and enter "Developer options." Enable "OEM Unlock." While you're there, enable "USB Debugging," disable "Automatic system updates" and "Verify apps over USB."
2. Using adb, after your device is recognized, type:
adb reboot fastboot
fastboot flash oem unlock
fastboot reboot
Your bootloader should now be unlocked. On your boot screen it will say, "Orange State." (never try to re-lock the bootloader because that will put your device into "red state" which is very bad. You've been warned!)
Extract Your Tablet's Boot.img file using MTK-su
1. You need the boot.img file of your specific ROM to allow Magisk_Manager to patch it...in order that Magisk may be installed as superuser. What better place to get that file than your own device? Use diplomatic's MTK-su exploit to gain temporary superuser access to your tablet's root file system. Your boot.img file can be found in /dev.
2. Still superuser under MTK-su, copy the boot.img file to your sdcard in at least two locations. The reason for this is to make sure you can easily find it later when you've left MTK-su's root shell. Something like this should work...
cd /dev
cp bootimg /storage/emulated/0
cp bootimg /storage/emulated/0/Download
**Note** In /dev your boot.img file is named "bootimg". When you copy (paste) it to your sd card it will appear as "boot.img".
Patch Your Tablet's Boot.img file with Magisk_Manager
1. Download Magisk_Manager v7.5.1 apk and install on your tablet. Patch your boot.img file. Press Install . Install> "Select and Patch a file". Navigate to your boot.img file and select it. Wait a few seconds for the patching to start and note the location of the newly patched boot image named magisk_patched.img. Flashing this personalized boot image will allow you to install Magisk v20.4.
2. Now using adb and MTK-su again, start a root shell and find the magisk_patched.img file and copy it also in at least two places to make it easy to find and later transfer to your desktop. My experience was that I copied it to my sd card but couldn't find it when i left the root shell and tried to get it onto my desktop. The point is that you want the file in a directory that your desktop file manager can access. I'm a noob so I made a few copies of it.
At this point it might also be a good idea to review topjohnwu's Magisk boot-patching thread here to glean any information that may apply to the Voyager 3, although that tablet is not mentioned by name.
3. On your computer using adb fastboot:
adb reboot fastboot
fastboot flash boot /path/to/magisk_patched.img
fastboot reboot
4. Download Magisk.20.4.zip and install it from your tablet's recovery or via adb. You should now be rooted and the Manager app should show both Magisk_Manager and Magisk superuser installed. I know there's probably easier ways to do this, and lots of shortcuts, but this is what worked for me.
Click to expand...
Click to collapse
I know the above is not as clear as I would like to make it, and I invite others to refine the method so that people can easily follow it. But the fact is that it works. I've duplicated it after mistakenly factory-resetting my device. I tested it using Fx File Explorer which now has been granted superuser powers. I'll post photos soon to prove root status. Again please feel free to add to, detract from, or in any way help to make my explanation more accurate and concise. Of course all credit goes to the guys who made the tools I used, @topjohnwu and @diplomatic.
The overall thrust of what I've tried to describe is 1) patch your own boot.img file with Magisk_Manager and flash it to your bootloader and 2) load Magisk superuser app in the now friendlier boot environment to obtain root. That's it.

I've been doing taxes lately...years of taxes, but I finally read up on posting images so here. Not exactly like I wanted them to post, but it does the job.

Also it is very important that you do not upgrade MagiskSU within MagiskManager. Flash any updates through your recovery. If by chance you try updating through MagiskManager your root will be gone and if in bootloop you will have to wipe device and start again with the step of extracting your boot.img.

Also, remember to check which processor your tablet has before you try modifying it. RCA came out with many, many confusingly similar part numbers. Only some of them have MTK processors with others being (at the very least) Intel or Rockchip.

Related

[GUIDE] [SUPPORT] How to root, optimize, and repair Xiaomi Redmi Go.

The One-for-All Guide to rooting, improving, and fixing various errors in Xiaomi Redmi Go!​Hello everyone! This thread that I made is for all people who wants to modify and gain full access, as well as to repair their Xiaomi Redmi Go devices the well-guided way, I've noticed that nobody has made an all-in-one guide for this phone so I decided to do it, this thread will keep on expanding depending on what I will discover about this phone, but for now, here is the thread, i expect that you have at least a little amount of knowledge when it comes to phones such as ADB and Developer Options.
What can we do with Xiaomi Redmi Go:
1. We can root it, and the best root manager for this phone is Magisk, SuperSU is also good, but if you're planning to use your phone for mobile banking, then Magisk is right for you. (Unfortunately this isn't true right now due to ctsProfile being hard to manipulate, Redmi Go supports hardware backed key attestation which means your device will definitely be not certified no matter what you do, so until we get a new method, don't root your phone if you want to use apps like Google Pay
2. TWRP is the current custom recovery available for this phone, it has flaws, but its currently the best out there, so its worth the shot to install it, the thread for it will guide you.
3. No custom kernels, people said that they have managed to install AOSP 9 and GSI on this device and made it boot up, but for me, it's better to wait for the official ROM update, after all, the device is still supported.
Prerequisites:
1. Xiaomi Redmi Go
2. An internet connection, a strong one is recommended if you want to download a ROM.
3. A computer with SDK Platform Tools ready to use, this is required, the link is here: https://developer.android.com/studio/releases/platform-tools
Don't forget to also get its driver! The link is also here: https://developer.android.com/studio/run/win-usb
The drivers are tricky to install but I will guide you on doing it in the easiest way possible, please continue on the thread.
4. SD card, your user data will be erased later, better back your files up, this is a warning.
5. Turning on "OEM unlocking" and USB Debugging in Developer Options, this is also really important!
Table of contents:
1. Unlocking the bootloader (and setting up ADB)
2. Rooting
3. Applying the custom recovery
4. Additional modifications
5. Stock ROM links
6. Bonus Section
WARNING: I am not responsible for anything that happens to your device as you follow my guide, do not blame me if you turned your device into a paperweight, made it explode, made it fly or whatever it may be, you chose to modify this phone and you should be accountable for it, you must know the consequences of what you're doing, try to point your finger at me because of what YOU did and I will laugh at you.
I am ready to assist though, so please feel free to ask some questions!
Let us begin, this will take several minutes, so please be patient and avoid rushing.
1. Unlocking the bootloader.
NOTE: This requires your computer to have SDK Platform Tools extracted to any location as long as its easy to access, and its really complicated to talk about it here, this step doesn't include the method where you request a code from Xiaomi, but I've provided a link for it.
A. First, get your phone up, and open the folder on where the SDK Platform Tools are placed, make sure that your in the directory where you see the .exe files of the SDK, now, hold Shift on the keyboard and click "Open Command Prompt here" and type "adb reboot bootloader", without quotes don't forget! This applies to all the steps that I will provide, don't forget to change the USB connection mode of your phone to PTP for it to be detected by ADB! (Only applies to Windows 8/8.1) Once your phone is asking for an authorization, check "Always allow this computer" then tap allow.
B. Once your device has been booted up into Fastboot or the bootloader, check first if your device is being detected, type "fastboot devices", if yes then proceed, if no, then stop here for now.
1B. If this happens then you may have to check your drivers and see if its installed correctly, once your device can be seen at "adb devices" it should also been seen in "fastboot devices" and when the phone is in adb sideload, if not then you have to reinstall ADB, get the proper drivers and do it again.
C. Now, type "fastboot oem unlock-go", the terminal will warn you that all of your user data will be removed, if you have them backed up then and go ahead and enter the command, if not, then just type "fastboot reboot" and start backing up your files, then do this again.
D. The phone will boot up and say "Erasing", to confirm that your phone has its bootloader unlocked, once it boots up again see if it says "Unlocked" on the bottom part of your screen, if there is then congratulations, it should be unlocked at this point.
1D. https://www.getdroidtips.com/unlock-bootloader-xiaomi-redmi-go/, this one particular link provides you on how to unlock the bootloader by entering a certain code, I believe this is a safer method but requires a bit of time, go here if you're interested.
NOTE: The phone supports the command "fastboot flashing unlock_critical" if you are going to unlock your phone with the normal command (fastboot oem unlock_go/fastboot flashing unlock), consider using this 2nd command too, what it does is that it allows you to also flash partitions you supposedly don't have access to, just be very careful not to flash any wrong file! It will be useful to make the "flash_all.bat" script work that you can find on the fastboot ROM for this device, more below!
Once your bootloader has been unlocked, you can now proceed to the other steps that I provided here, don't forget to enable USB Debugging on your Developer Options.
1.2 Setting up ADB
1. Grab your phone, unlock and open your Developer Options then enable "USB Debugging", then change your connection type to "PTP" if you are using Windows 8/8.1, I am not sure if this is required on 7, but it is not needed on Windows 10.
2. Go to this link: https://developer.android.com/studio/releases/platform-tools and download the .zip file, then extract it to a location that is easy to access, like your desktop.
3. Get the official Google drivers here: https://developer.android.com/studio/run/win-usb download the .zip file as well, and extract it too.
4. Go to the extracted folder of your SDK Platform Tools, and go to the directory where you can see various .exe files such as "adb.exe", now, hold the Shift key then click the Right mouse button, then click "Open command prompt here" If this doesn't work for you, open up CMD with admin rights, then type in cd *the location of your platform tools* say on mine, I will input cd C:\Users\James\Downloads\platform-tools_r31.0.3-windows\platform-tools then enter
5. Open your Device Manager by pressing Windows + R, put "devmgmt.msc" without any quotes then Enter, do not close the Device Manager until you're done with all the steps! And please be fast here too or else ADB will not work, now go to your extracted folder of the Google USB driver, and look for the file "android_winusb.inf", copy the location path of it as you will need the exact location path of the file later, in my case it was "C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\android_winusb.inf".
4A. There are 3 main ADB devices that you have to install, Android ADB Interface, Android Bootloader Interface and Android Composite ADB Interface, so I will divide this into 3 sections, have your Device Manager, and the exact location of the .inf.
NOTE: Turn off the internet connection of your computer, why? Because, if you let Windows install the drivers for you, the drivers may be incorrect and will break things apart, as we will encounter several "Unknown devices" in the Device Manager and we have to update them with the extracted files from Google.
Android ADB Interface
1. Now, make sure that USB Debugging is enabled, now plug in your phone and let the drivers install WHILE your computer is offline, now go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark.
2. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android ADB Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go.
NOTE: If you plug your phone and there is no "Android" device with exclamation mark, you can proceed to try and see if adb detects your device by typing "adb devices" in the command right now, it should be since this is what I experienced when setting up my device in Windows 10, this step usually applies only if you are using Windows 8/8.1
Android Bootloader Interface
1. To test, go to the command prompt you opened earlier, and type "adb devices", the device should now be detected at this point, when it does, type "adb reboot bootloader".
2. Now, make sure USB Debugging is enabled on the device before booting it into bootloader, now plug in your phone again and let the drivers install WHILE your computer is offline, Go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark.
3. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android Bootloader Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go.
Android Composite ADB Interface
1. Before proceeding, type "fastboot devices", the device should now also be detected on fastboot, now, type "fastboot reboot", and afterwards, enable "USB Debugging" on the Developer Options, then go your command prompt, then type "adb reboot recovery".
2. Now, now plug in your phone again and let the drivers install WHILE your computer is offline, now go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark.
3. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android Composite ADB Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go.
2. Applying the recovery/custom recovery
A. Open up your phone and ensure that USB Debugging has been enabled, now, open up your command prompt just like in Step 1 in Unlocking the Bootloader and type "adb reboot bootloader"
B. Next up, type "fastboot flash recovery path/to/recovery.img", substitute the path/to/ with the actual location of your recovery, and please make sure that the name of the image is "recovery.img"! Or else it will not overwrite/update the recovery, you can also put your recovery.img directly within the platform-tools folder so that all you have to type is "fastboot flash recovery recovery.img" then press enter.
C. Once your done, reboot the phone and press Volume Up + Power at the same time, and the recovery will start. (You may want to do this else the recovery will be automatically removed and replaced with the stock one)
1C. For the stock recovery, once you press the combination, the phone will say "No command", at this point, hold your Power button and press Volume up one time to get into recovery.
https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282 here is the link of the TWRP recovery, I encourage you to follow the steps mentioned in the post properly.
WARNING: The fix I provided below is now pushed here for 1 certain reason, before you try to root your phone and do everything else, you must decrypt your internal storage first and it is quite easy, first you must get the decrypt.zip linked in this thread (if the .zip cannot be found, I still have a copy of it), go to TWRP and do "format data", not Wipe Data! How so? Once you reboot to TWRP, it will show you the "Wipe" button, tap that, then the "Format Data" button should show up, this will require you to type in "yes" so type it in, then once it is done formatting, go back to the main TWRP screen, tap "Reboot", then "Reboot to Recovery", afterwards you must go to "Install" then proceed to install the "decrypt.zip", after that you can now flash .zip files from your internal storage too, but beware that you must do this every time you update your device!
3. Rooting your phone
A. To get started, install TWRP for your phone first.
B. Get the .zip file of Magisk/SuperSU so you can install them, the links are https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
C. Reboot your phone to recovery or just plug it in, open the command prompt again just like in the previous step and put "adb reboot recovery" without quotes.
D. Tap "Install" on your TWRP recovery and select the respective installation .zip file of your chosen root management app, and wait for it to finish.
1D. The .zip for both SuperSU and Magisk can be installed through "adb sideload", if incase you don't have an SD card! It may also work with fastboot as well but I need someone to confirm this.
E. When it's done, wipe the cache first, then reboot.
1E. If the root management app didn't appear in your phone after boot, just install the APK of it in the Play Store and check if root has been applied, if not, repeat step C and D again.
BONUS: It may be useful also to grab EdXposed or LSposed for Magisk and the link is here: https://forum.xda-developers.com/t/...or-of-xposed-oreo-pie-q-r-2020-07-19.4070199/ and here: https://forum.xda-developers.com/t/...e-magisk-module-edxposed-alternative.4228973/, please choose only one! You will use the normal Xposed if you're using a different root management app such as SuperSU, the link is here: https://forum.xda-developers.com/showthread.php?t=3034811
What this does is that if the app is an Xposed/EdXposed/LSposed framework module, any modifications it does to your phone will be based on memory only, it won't modify your phone directly which means your device will be clean, and if it incase the said modification bricks your phone, you can easily recover from it too!
BONUS 2: I also recommend getting the Busybox module from Magisk itself, it can easily be downloaded from the Magisk app, you will need this module if you want your root applications to work more efficiently and avoid errors, as most of them requires Busybox to work, don't use the Busybox installer apps on Play Store as they modify /system directly, only use it if you are using SuperSU.
4. Additional modifications
Once you've managed to root your phone and everything else, what I recommend you could do with your device is to get the following apps:
Titanium Backup - It has the ability to back up apps on your phone, and even its data! this app could do so much more than with what I just mentioned.
LSpeed - A root boosting app that has almost every root tweak packed into it, its really convenient to use! I do not recommend using Entropy tweaks as I heard it is a placebo.
Greenify - For me, this is the only legit battery saving app aside from LSpeed which also offers tons of battery saving features, it requires Xposed to have more options you have to buy it to gain full functionality
ROM Toolbox - This app pretty much contains everything a rooted user needs, such as a terminal and root-based file manager.
System app uninstaller (optional) - Just in case if you're planning to remove some bloatware (the list of it is below)
Root Browser - An alternative to ROM Toolbox, this root explorer is really popular and gets the job done without any interruptions.
Terminal emulator - This will allow you to enter various commands on your phone, like being able to reboot the phone without using any keys.
In order to make the phone as fluid as possible, just leave it with stock ROM installed, try to also use lite apps like Facebook Lite to reduce RAM and battery consumption.
Kernel Adiutor - Another great root application, it's like LSpeed but it doesn't automate tweaks, it instead allows you to modify most of it on your own, then it reapplies your tweaks every time your cellphone will boot up if you tap the "Apply on startup" switch. the link for the app is here: https://m.apkpure.com/kernel-adiutor-root/com.grarak.kerneladiutor
NOTE: Most of these apps can be found on the Play Store, and please don't install any more similar root boosting apps such as HEBF, scripts such as V6 Supercharger, or modifying files like build.prop, it is due to the fact that this will conflict with LSpeed, as LSpeed contains most of the tweaks that past scripts and apps provide, this will result in your phone slowing down a lot, Greenify will require Xposed Framework which is mentioned above on the Rooting section, the link to LSpeed is here https://github.com/Paget96/LSpeed, because the app has been removed from Play Store.
WARNING: The perf.zip https://forum.xda-developers.com/android/development/-t3935220 here, that was provided in Xiaomi Redmi Go forum section must be applied with extreme caution, you have to make a backup of your build.prop in /system, and build.prop + default.prop in /vendor for easy recovery, you can use ZipMe to easily make a backup for these files.
5. Stock ROM links
https://xiaomirom.com/en/rom/redmi-go-tiare-global-fastboot-recovery-rom/, this link so far provides all the ROMs (both recovery and fastboot) available for download on this phone, and they are actually light enough, so it will be easy to download them.
https://xiaomifirmwareupdater.com/archive/miui/tiare/ a new link I've found recently, this rom contains the .tgz format of the latest ROM for the Xiaomi Redmi Go, which could be used for fastboot and Mi Flash Tool, just search for the model and go for Global.
NOTE: Most of the ROMs for this phone provided on several sites, even on the actual Xiaomi website, has an invalid format of .zip, and doesn't contain a flashall script, as a result, Mi Flash Tool will never be able to use these ROMs, you could not also use adb sideload and fastboot for these ROMs, only the stock recovery of the phone could install the ROM, due to the links provided above finally giving the latest ROM versions for the phone, extracting the stock recovery is very easy now, you can do it yourself but if you need a link, tell me.
5A. Applying the stock ROM
This section will be divided into 2 sections, flashing the ROM through recovery, flashing the ROM through fastboot manually, or automatically with flash_all.bat
Stock recovery method.
A. Download the stock ROM with .zip format and put it into your SD Card.
B. Flash your recovery back to stock with the steps given above, boot into your stock recovery, then using your Power button and volume keys to navigate, select "Apply update from SD card".
C. Select the .zip file and wait for the update to finish.
D. The device will boot up automatically after, if not, just go back to the main menu of the recovery and select "Reboot system", enjoy!
Fastboot manual flashing method.
A. Ensure that you have prepared your device and computer for ADB, now grab the ROM given in this thread in .tgz format, and keep extracting the file until you see the files such as "flash-all.sh" after extraction, as you need to extract the .tgz ROM two times before you could use it properly.
B. Now go to the extracted folder of the stock ROM, go the "images" folder and copy the following image files: boot.img, system.img, recovery.img (make a backup of this file somewhere!), vendor.img, cache.img, userdata.img, persist.img, and splash.img.
C. Paste them to the extracted folder of your SDK Platform Tools where various .exe files are located such as "adb.exe", or in my case the location is "C:\Users\Symphony\Downloads\platform-tools_r29.0.4-windows\platform-tools".
D. Now open your command prompt on this directory, or Shift + Right click, then plug in your phone, now type "adb reboot bootloader" so your phone will go to bootloader, don't forget to enable "USB Debugging" and PTP connection mode before rebooting! (only applies to Windows 8/8.1, it may vary on Windows 7 but it is different on 10, no need for PTP connection mode, you can just turn on USB debugging and that's all)
E. Now, this is a little tricky, but try to follow me as much as you can, make sure first that you are detected with "fastboot devices", input the following commands that I will give so you can flash the ROM to your phone, now go to the command prompt and:
To flash the boot.img to your phone, put the command: "fastboot flash boot boot.img"
For the recovery, the command is: "fastboot flash recovery recovery.img"
For the system or main OS: "fastboot flash system system.img"
For cache: "fastboot flash cache cache.img"
For persist: "fastboot flash persist persist.img"
For the vendor or additional system files: "fastboot flash vendor vendor.img"
For data or apps: "fastboot flash userdata userdata.img"
For splash or probably boot animation: "fastboot flash splash splash.img"
D. After that, type "fastboot reboot", and enjoy!
Fastboot automatic flashing method (NEW!)
A. Extract the fastboot ROM 2 times as instructed, after getting the files, grab all the files and copy it to the directory of your platform tools where files such as "adb.exe" can be found, just copy all the files in there and that's all you have to do.
B. Open the "flash_all.bat" on Notepad and remove the following lines:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *tiare" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *tiare" || exit /B 1
Afterwards, save the .bat file, that should be ready to use now
C. As instructed above, you must also do "fastboot flashing unlock_critical" after unlocking your bootloader the normal way, this will act as your 2nd unlock command, without this, the flash_all.bat will not work as it should be.
D. Boot up your phone in fastboot mode, open up your adb devices and make sure that your phone is seen in "fastboot devices", once it does, type in "flash_all.bat" without any quotes and execute it, the command will now automatically flash everything without you doing anything else, it will also automatically reboot after doing so.
Bonus section:
1. TWRP-compatible stock ROM
For this part, in order for you to generate a TWRP-flashable stock ROM is by basically making it yourself, you have to make sure that your patch is latest, and its pretty much a good idea to just tick everything in the backup selection except for the recovery, as well as the cache as you don't need those.
Once you have it, go ahead and keep it somewhere safe but easy to find, so if case that you need to use it, you could get it immediately, this is extremely useful so please just do it, as of now, I've confirmed that only the /data backup was usable, but please try to confirm if other partition backups are working for you.
Certain custom ROMs that can boot up in this device could be flashed through TWRP though, and the links of them are provided here in this thread.
2. GSI, AOSP 9 and custom ROMs
The link for AOSP is provided here: https://forum.xda-developers.com/android/development/redmi-aosp-9-t3922192
The link for GSI is right here: https://forum.xda-developers.com/android/general/tested-gsi-redmi-t3924705
These images/ROMs can be applied with TWRP, just make sure to follow the steps mentioned in these posts to avoid inconvenience, don't forget to take precautions too! I haven't tried them, but so far I believe that these are stable to use.
There are also custom ROMs released for the device but I am lazy to link all of them, they can easily be found by going here: https://forum.xda-developers.com/tags/xiaomi-redmi-go/
Please take note that I haven't tested these custom ROMs yet and I most likely never will, since the stock ROM for the device is already good enough, you can comment here and tell me what custom ROMs are stable so I can link them here for future reference.
3. Current status
My phone is still working, yes! and it's still staying strong, updated to 2.25 using the fastboot method and it is still fast, the only issue currently is that SafetyNet is a lot more secure than before, so it will be impossible to use stuff like Google Pay for now.
I usually decided to lay low and just stay with my LSpeed, Kernel Adiutor and Greenify, all I had to do is to tinker with these apps and my phone just reached into a whole new level! The performance improvement is nice, that I didn't need to use a custom ROM anymore.
4. How to install a OTA update after rooting your device
Due to the changes made by Google on SafetyNet, and the fact that this device will always require you to wipe the device every update, it is pretty much the same, it doesn't matter anymore if you are certified or not, you will still receive an OTA update even if your device is not certified as long as you are using the stock ROM, you only won't be able to install it, and if you want to install the OTA update you must install it by flashing the updated fastboot ROM, I have links for it above, you can try installing the OTA updates yourself through the settings but you will still have to do a factory reset anyway, you have to also unroot also and revert to stock recovery, else the installation will fail, and your device may slower afterwards.
5. Bloatware you can safely remove (NEW!)
So, like I said above, as much as how lightweight the device is, there are still bloatware that you can remove if you really want, but it's only 3 of them:
Mi Video
Mint Browser
Mi Music
The rest such as Mi Share and Mint Launcher are also bloatware, you can remove them but to me they are useful so I didn't, do not remove the "Cleaner" app, if it however says something like "com.CleanMaster", you can try removing it but take caution as your Play Store may be removed along with it too.
Credits to everyone who made the apps/tools that I mentioned here! such as @topjohnwu for the Magisk, and @YasiR Siddiqui for the TWRP, @Paget96 for the awesome LSpeed app, @rovo89 for the Xposed Framework and many more, you guys totally rock!
Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over...
TheAngryGuitarist said:
Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over...
Click to expand...
Click to collapse
Can you please elaborate all of what you've done so far? I will also ask you a few questions.
1. Is your phone usable with the platform tools? I mean with adb and such.
2. Did you try going into recovery and flashing stock ROM through there?
3. Is your phone being detected by "fastboot devices"? The fastboot mode of Redmi Go is its download mode, and i've provided the link for the stock ROM that's usable thru fastboot mode, as well as on how to apply it.
My phone is usable with adb and such, the recovery mode was not working, only the fastboot. I've tried flashing stock rom with the flash tool but I had no success with a bricked soft and a locked bootloader. I've finally fixed it by going into the edl mode by test point method then I flashed the stock rom, and I've fixed my problem this way. I couldn't unlock the bootloader manually from adb or the unlocker tool, but I've did it in the edl way.
TheAngryGuitarist said:
Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over...
Click to expand...
Click to collapse
TheAngryGuitarist said:
My phone is usable with adb and such, the recovery mode was not working, only the fastboot. I've tried flashing stock rom with the flash tool but I had no success with a bricked soft and a locked bootloader. I've finally fixed it by going into the edl mode by test point method then I flashed the stock rom, and I've fixed my problem this way. I couldn't unlock the bootloader manually from adb or the unlocker tool, but I've did it in the edl way.
Click to expand...
Click to collapse
Can you please elaborate the term "edl mode"?
Good job then, usually, before you modify the phone and start doing something crazy out of stock, your number one step is to really unlock the bootloader, and in order to make things more easier, you should allow your OEM to be unlocked through the developer options, after that you can now unlock the bootloader with fastboot.
_XblackshadowX_ said:
Can you please elaborate the term "edl mode"?
Good job then, usually, before you modify the phone and start doing something crazy out of stock, your number one step is to really unlock the bootloader, and in order to make things more easier, you should allow your OEM to be unlocked through the developer options, after that you can now unlock the bootloader with fastboot.
Click to expand...
Click to collapse
Yes, it's the emergency download mode. You use it when there is nothing you can do about the soft of your device. It automatically unlock the bootloader and you can flash the stock rom. Well, my problem was another. I did not tried to flash roms or recoveries with a locked bl. My phone automatically rebooted into the fastboot mode and from there I was not able to start my phone normally. I've tried rebooting fastboot from adb, unlock bl from adb, no success. I had to dissamembly the phone and make a short-circuit to the test points while slowly pushing in the mtp cable with the battery disconnected. Once I saw the Qualcomm driver on device manager I was able to flash the stock rom. You can search if you want to, for the test pins of this device. Btw, thank for your advice, you are really helpful to the community! ?
TheAngryGuitarist said:
Yes, it's the emergency download mode. You use it when there is nothing you can do about the soft of your device. It automatically unlock the bootloader and you can flash the stock rom. Well, my problem was another. I did not tried to flash roms or recoveries with a locked bl. My phone automatically rebooted into the fastboot mode and from there I was not able to start my phone normally. I've tried rebooting fastboot from adb, unlock bl from adb, no success. I had to dissamembly the phone and make a short-circuit to the test points while slowly pushing in the mtp cable with the battery disconnected. Once I saw the Qualcomm driver on device manager I was able to flash the stock rom. You can search if you want to, for the test pins of this device. Btw, thank for your advice, you are really helpful to the community!
Click to expand...
Click to collapse
Woah, you really had to open the phone before doing it, that's an interesting method!
That part where your phone booted into fastboot was kind of scary, any ideas why it booted into fastboot in the first place? It has to be reported if incase, seems like a dangerous bug.
_XblackshadowX_ said:
Woah, you really had to open the phone before doing it, that's an interesting method!
That part where your phone booted into fastboot was kind of scary, any ideas why it booted into fastboot in the first place? It has to be reported if incase, seems like a dangerous bug.
Click to expand...
Click to collapse
I'm not really sure if a malware caused this issue or a failed system update over-night.
TheAngryGuitarist said:
I'm not really sure if a malware caused this issue or a failed system update over-night.
Click to expand...
Click to collapse
I usually had failed system updates numerous times because when i install them, the phone has already been modified by a lot, and that's actually riskier.
That's why i recommend unrooting and putting back the stock recovery before updating first, still works on mine even with "Device is not certified" by Play Store.
The TWRP linked here is for Pie 9, I couldn't get it to boot on my phone, it shows vertical lines.
This is the older version for Oreo 8...
https://forum.xda-developers.com/android/general/twrp-xiaomi-redmi-beta-t3918993
I formatted the phone from TWRP it so it was no longer encrypted.
Mounted the drive from TWRP and installed the "decrypt.zip" from the other TWRP...
https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282
I unlocked the bootloader successfully.
In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help.
I've attached the screenshot of my device manager,
bhattinb said:
I unlocked the bootloader successfully.
In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help.
I've attached the screenshot of my device manager,
Click to expand...
Click to collapse
Did you try turning on USB Debugging on Developer Options? Did you try installing the USB drivers from Google?
_XblackshadowX_ said:
Did you try turning on USB Debugging on Developer Options? Did you try installing the USB drivers from Google?
Click to expand...
Click to collapse
Yeah, I've done everything you told, I also turned the connection mode to PTP also. Somehow it just not showing that android with an exclamation mark.
after that, I even tried to use the 15-second ADB installer. after installing that I tried to flash recovery but that just didn't do anything. After using that flashing command, I had the same stock recovery.
I'm really thankful you took the time to answer my question.
Help!! My device stuck on screen saying your system has been destroyed. What I had done is locked the bootloader using command fastboot oem lock then this happened. Now i can boot device in stock recovery and bootloader too but when i am trying to unlock bootloader it says device is lock and also i am not able to flash anything. Plz help.
I am not able to flash TWRP on my redmi go
How to update the redmi go to the latest version without formatting/Factory Reset should I just follow Fastboot flashing method and if so which files should I just flash. Thank you
bhattinb said:
I unlocked the bootloader successfully.
In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help.
I've attached the screenshot of my device manager,
Click to expand...
Click to collapse
Hi! sorry for the late reply, if this is the case then it's fine, you can just connect the device, open up adb tools, type adb devices and ensure that your USB debugging is on, and the device will connect immediately, at that point all you need is the adb driver for Fastboot
akki_007 said:
Help!! My device stuck on screen saying your system has been destroyed. What I had done is locked the bootloader using command fastboot oem lock then this happened. Now i can boot device in stock recovery and bootloader too but when i am trying to unlock bootloader it says device is lock and also i am not able to flash anything. Plz help.
Click to expand...
Click to collapse
oh no, but why lock your bootloader? you can try using a recovery ROM, you must have a spare SD Card within you, grab a recovery ROM, put it in your sd card then put it into the phone and use it on stock recovery, you should be able to apply it and boot back into the system, please update me
igpraan said:
I am not able to flash TWRP on my redmi go
Click to expand...
Click to collapse
you must have unlocked bootloader if you want to do so.
niknah said:
The TWRP linked here is for Pie 9, I couldn't get it to boot on my phone, it shows vertical lines.
This is the older version for Oreo 8...
https://forum.xda-developers.com/android/general/twrp-xiaomi-redmi-beta-t3918993
I formatted the phone from TWRP it so it was no longer encrypted.
Mounted the drive from TWRP and installed the "decrypt.zip" from the other TWRP...
https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282
Click to expand...
Click to collapse
that's strange, the TWRP I linked isn't giving me any vertical lines

[Guide] Root Xgody Y28 with Magisk (MT6580) and dump stock rom

I am making the following guide because root guides for the Xgody phones are pretty hard to come by, and documentation is sparse. Enjoy.
First, you will need to setup adb and fastboot on your pc. Download Minimal ADB and Fastboot here. If your PC doesn't find drivers for "adb interface", download MTK adb drivers here, and install it by updating the driver for adb interface in device manager.
Now you will need to boot up your phone, go to about phone -> build number -> tap seven times. Head back to settings home, go to dev options, and enable usb debugging, then connect phone to pc. Open minimal adb and fastboot, and verify that the phone is connected by running "adb devices" command. If you see unauthorized next to the phone's serial, then you need to allow access on your phone in the window that has popped up.
Next step is to unlock the bootloader, so that the phone boots with the Magisk patched boot image we will be flashing later on. In developer options, you will now need to check "oem unlocking". Now in adb, type "adb reboot bootloader". Screen should go black, and "fastboot mode" text should appear on screen. Quick Note - Only boot to fastboot using this method. Shutting down the phone by selecting power off in the power menu and then holding the key combo to get into fastboot will cause the oem unlocking switch to flip back to off, and the next step will fail. Thus, make sure to use the adb command to reboot to fastboot mode. Don't know why this is, but it seems to be some sort of lousy anti-unlock protection by the Chinese devs.
Now in fastboot mode, type "fastboot devices" on your PC. you should see the device serial and "fastboot" next to it. If you do not, check device manager again. If you see an unknown device such as "Android" you will need to again install the driver through device manager. However, this time select "bootloader interface", as you are installing for fastboot mode.
Once you see the device in fastboot, you can proceed to unlock the bootloader. Type "fastboot oem unlock". Check the phone, and accept the warning about unlocking bootloader. Now the command should finish and bootloader should be unlocked. Reboot to system with "fastboot reboot". You will see "erasing" as the phone resets, and then it will boot into Android.
Now you are ready to grab your boot.img. We will need to patch this file with Magisk to obtain root access. To obtain the boot.img, you will need to make a full backup of your phone's rom using SP Flash Tool. A detailed guide here is available to guide you through the process. You can grab the VCOM driver and sp flash tool at https://spflashtool.com/. To follow the above guide, you will need to know the cpu and flash memory type. If you didn't know already, the Xgody Y28 is running on an MT6580 and uses EMMC memory.
You can also obtain a copy of the stock rom here - https://mega.nz/#!6vB0gKSK!RJ9SZ3q-Zp33ZYMjTk42A7cgeubvq-W2C4G7Ln4y8Bo However, I recommend making a backup of your own stock rom instead, as that is the safest option. The rom here may differ slightly differ from your phone's and cause issues. Unlikely, but still a good idea to use your own backup.
Either way, you now have a backup of the Y28's stock rom. We now need the boot.img. Connect your phone to your pc, and on the phone, select media device (MTP). This will allow you to copy files to the phone from your pc. Find your boot.img, and copy it to your phone. It doesn't matter where, just put it in an easy to reach location in your internal storage. Next, you will also need to copy over the Magisk Manager apk to your phone. Download it here. Click on "Latest Magisk Manager". Save the apk, and then copy it to your phone as well.
Next on your phone, open your file manager. Find the Magisk Manager apk, and install it. Note that the next part requires you have an internet connection, as Magisk Manager needs to connect to github to download the magisk zip to patch your boot.img with.
Now open the Magisk Manager you just installed. hit install, and select patch. Find your boot.img and select it. After the process is complete, exit Magisk Manager, and find the magisk-patched.img on your phone that magisk created.
Connect your phone to pc again, and copy the patched boot image to your pc. On your PC, navigate to the folder containing your stock rom, and rename boot.img to boot-original.img. Now, copy the magisk-patched.img to the stock rom folder. Rename magisk-patched.img to boot.img.
Next you will need SP Flash Tool. open it up, and select the android-mt6580-scatter.txt in the scatter-loading file. A list of flashable partitions will load once the scatter file is processed. Uncheck all except the boot.img (as this is the only one we want flashed) Now hit download, and connect your phone to your pc. Make sure the phone is turned off, and the battery is removed before connecting to PC. The SP Flash Tool will then flash the boot.img to the phone. Once complete, you can close the program, and unplug your phone.
Boot your phone back up, and open up Magisk Manager. It should now say Magisk is installed.
Congratulations! If you have successfully followed the steps above, you now have a rooted phone.

Recommended steps for gaining root (10.5.12 IN21AA)

I got my OnePlus 8 (IN2013) yesterday, so the first thing I did was unlock the bootloader. Now I am unsure about the "best" (most simple and foolproof way) to proceed and would like some help.
As mentioned above I am on 10.5.12 IN21AA firmware and would like to gain root access. I'm not interested in flashing a different OS or whatsoever. I'm perfectly able to follow step-by-step guides but am confused by no official TWRP seemingly being available for this device, messages about lost functionality (fingerprint sensor), etc. etc.
Would someone please be so kind to provide the correct steps?
Boot (or flash if you want to keep TWRP. I recommend just booting it) TWRP > flash Magisk from TWRP.
That's it.
i rooted with patching boot.img with magisk, was easy enough and all went smooth
I ended up doing the following (for other inexperienced users with similar questions). This approach is largely based on the steps described here, so many thanks to jacobyo7. I have added links to relevant threads to make it easy to reference all the necessary threads and get all the necessary files, programs etc.
Connect phone to computer and make sure USB Debugging is on
Retrieve the correct firmware, see this thread
Using payload dumper, extract boot.img from payload.bin
Transfer boot.img (extracted in previous step) to device
Install Magisk Manager (not in Play Store but easy to find on Google)
Open Magisk Manager > click "Install" (next to Magisk) > click "Install" > click "Select and patch a file" > select boot.img (transferred to device two steps earlier)
Transfer magisk_patched.img (created in previous step, probably located in Downloads) to computer, rename to boot.img
Open command prompt in folder with the patched boot.img (make sure you have installed this tool, so you can issue adb and fastboot commands from anywhere)
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
make sure device is listed:
Code:
fastboot devices
Boot the patched image:
Code:
fastboot boot boot.img
Wait for the phone to reboot > Open Magisk Manager > click "Install" (next to Magisk) > click "Install" > click "Direct install"
Reboot
Open a terminal app (e.g. Termux) and backup the persist partition:
Code:
su
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/Download/persist.img
Backup persist.img to computer

Custom ROM for Panasonic Tab 8

I want a custom rom and how to root guide for panasonic tab 8 hd. There's an option to unlock bootloader in system settings. So it's easy to unlock it. I think I need to have microG as I have to use Whatsapp for my classes. I can provide you with the details of the device if required.
1. Activate USB debugging
2. Backup all your data.
3. Pull your boot.img and Vemata and save them in your external sdcard.
4. Install Magisk 22.1apk
5. Open it from home page and install the app.
6 now touch Magisk and chose force encryption.and enter
7. In popup dialogue tick selctand patch file and enter
8. Now chose the boot.img file you saved in the external sd card. Now the magisk will process it put the file in your internal sdcard in the download section.
9. Now save the magisk processed boot.ing on your desktop or in any folder and remember the location. It is advisable rename that with 2or 3 letters and paste it in th9/e ADB folder where you have installed the Platform files.
10. Now you open platform folder and open cmd inside the Platform tool. In the ensuing cmd window check for
adb devices.
Your device I'd will come to the next line. Then type
adb reboot bootloader
Now check
fastboot devices
your phone I'd will pop up.
Unlock bootloader:
Type fastboot flashing unlock
then click volume up bottom over.
Not you come again till the step 10.
Rooting process:
Now type
fastboot flash boot " the magisk processed, boot.img which you have renamed.
Now the patched boot.img will relace stock boot.img
Again come back and type
fast boot "-- disable-verification flash vbmeta " put your vbmeta file that earlier you have saved in the Platform folder.
that is all it is rooted.
please note that before starting the root activities you have to unlock your boot loader.
On your own you are doing. I take no responsibility.
by this process only I have rooted the phone. And with WWR MTK Tool and SPFT I have managed to get the stock firmware files. With native preloader. But flashing with this preloader needed patched boot.img file

Guide to Rooting the Infinix Hot 30 Play, With Magisk

Preface​Luckily, it looks like Infinix is following the general trend of Android root solutions being more straightforward than in the recent past. Besides the usual spiel about your warranty being voided, and the annoying chirp each time you boot your phone, this hopefully won't present any problems for you if you do end up rooting your phone.
Notices​
Still, I'm not responsible for anything bad that will happen to your phone if you do this, and there's no support guaranteed either from me or your OEM/support centre.
There's quite a few steps to this, and naturally you're gonna need a few more things to setup before you even start.
Your phone's data will be reset, please backup everything you'd like to keep before rooting your phone (now and in general).
You do need to know some things already, mainly what ADB and Fastboot are, and how to keep your working environment clean and straightforward.
Please do review all the tools you're working with, be sure that you personally trust all the software you're running.
And last but not least, you won't be able to update your phone through OTA updates anymore unless you go back to stock firmware.
The process​
Make an environment for easy access:
Setup ADB and Fastboot (either as a local executable or a global environment variable to that executable).
Setup an easy to access directory with the Google Fastboot driver in it.
Grab your firmware's boot.img file, or grab the one attached to this post, or from here (and skip to the preliminary work section):
1. Download your phone's current ROM.
2. Extract it, as it should be a simple .zip file.
3. Look for the file of the same name (boot.img).
4. Copy it to your phone's storage, anywhere works.
Install the Magisk APK (from their Github).
Once it's installed, Magisk's app frontend allows you to patch your stock boot.img with itself, the gist of it is:
Click on Install within the app, in the "Magisk" section of the main menu.
Click "Select and patch a file", a file selection menu will show up, select the stock boot.img, then start the installation.
Magisk should spit out a patched boot.img named in the format of magisk_patched_[random_strings].img, in your phone's /sdcard/Download/ directory.
Copy that back into our working directory, and rename it to magisk_patched.img for easier usage.
Now, let's do some preliminary work, in any order, really:
Have Powershell or CMD open in the directory of all your tools, alongside the patched image.
Click to expand...
Click to collapse
From here on out, if you have to use adb as a command, and it's not a global environment variable, use ./adb while in the working directory instead, the same goes for fastboot.
Click to expand...
Click to collapse
Make sure that the adb daemon (adbd) is properly detecting your phone:
Enable developer options.
Enable ADB debugging.
Run adb devices to start the server daemon for ADB, and see if ADB detects your phone.
Authorize your PC for ADB debugging if it prompts you to.
Click to expand...
Click to collapse
Infinix's implementation of Fastboot will exit back out of itself and into normal boot after 60 seconds of inactivity, which makes this a tad annoying, although you can simply send it any input to reset that timer.
Click to expand...
Click to collapse
Let's start:
Restart the phone into Fastboot, adb reboot bootloader loader, it'll take a second, the phone is slow.
Unlock flashing 3rd party software, fastboot flashing unlock, the phone will prompt you on the screen to confirm doing this. Yes, this will void your warranty.
Flash magisk_patched.img to both A and B virtual partitions, fastboot flash boot_a magisk_patched.img and then fastboot flash boot_b magisk_patched.img.
That should be it! fastboot reboot to boot normally!
Be sure to also run the Magisk app so it finishes setting itself up, with another reboot, naturally.
Technicalities​The Infinix Hot 30 Play does have a dedicated vbmeta partition, it's advised that you also flash it alongside flashing the patched boot.img for Verified Boot, but that's not necessary if you don't want to tinker with your super partition's crypto keys.
Thank yous​- topjohnwu for their work on Magisk.
- ansh_/ and their post/guide on rooting the Infinix Hot 11, that I used originally.
Addendum​
Using fastboot with MediaTek SoCs will be a bit of a pain as their driver availibilty is limited, if it doesn't get installed by Windows automatically, you have a few options:
Grab the Google's Pixel driver, and install it in realtime during fastboot.
Try to install the VCOM driver from a source you trust.
For grabbing the Google one, you'll have to:
Extract the driver somewhere easy to access.
Open Windows' Device Manager.
Plug in your phone during fastboot to your Windows PC.
Replace the "Unknown" entry for your phone with the Google driver in device manager, within the 60 second window it stays open in.
Note that you'll have to do this every time you go into fastboot.

Categories

Resources