In this guide, i'm going to be a bit straightforward on how to install LOS 18.1 on your X00H/X00I device.
For the process, you need:
Your X00H/X00I device;
The following must be unlocked (if you didn't, you can follow the howto over my post);
A rooted phone/tablet with Magisk (any ADB & Fastboot tool is fine, but i suggest using this for simplicity);
In case you have none of the above, even a PC or Laptop with ADB and Fastboot binaries installed will suffice;
If you're on Windows, you can get the installer over GitHub;
If you're on Linux, hop into your package manager and install them via terminal (the following example will be for Debian/Deb-based/Ubuntu/Ubuntu-based distros. If you're on Arch, Fedora, etc.: just search for "fastboot" by using the respective pkg manager's search flag, then install it basing from the name it's repo gives):
Code:
sudo apt install fastboot
An USB cable (should come into the device's box, also must be capable of data transfering);
If you're going to do the process via a rooted device, the Asus device should come in it's packaging with an OTG adapter (be sure to attach the following to the rooted device);
PBRP (Pitch Black Recovery Project) for the device- OG post can be checked here;
Latest version for X00H;
Latest version for X00I;
If your device is an X00I, you can alternatively get TWRP instead;
The Android 9 Beta update (you MUST have the device updated to that version, else you'll risk the device to be bricked- for more info, check the OG post by Seba);
If you want to flash it via stock recovery, you can get the file over ASUS' site on the device;
Download for the X00H;
Download for the X00I;
If you have already flashed a custom recovery on your device, you can get the "custom recovery flashable zip"over SebaUbuntu's site;
.zip file for the X00H;
.zip file for the X00I;
Tiny discalimer on the flashable .zip above: once installed, your device's recovery will be replaced to stock (in other words, you'll lose the custom recovery);
The Lineage OS 18.1 rom and recovery (credits to @miya0405 for finding the site);
ROM and LOS Recovery for the X00H;
ROM and LOS Recovery for the X00I;
If you have all of the things required in the list, let's go!
--------------------------------------------------------------
Installing the Android 9 BetaStock Recovery method:
Download the Android 9 Beta over ASUS' site (any device is fine, even using the phone itself);
Put an SDCard inside the device;
Move the .zip file inside the SDCard;
Turn off the device;
Boot into recovery (do Power + Vol.up combo- if your device's unlocked, tap on the volume button and select "Recovery" by pressing on the power button to confirm);
Select "Update from sd card";
Select the .zip file you've downloaded;
Wait for the update to install;
After updated, go back and select "Power off";
Custom Recovery Method:
Download the Android 9 Beta flashable .zip over SebaUbuntu's site;
Put an SDCard inside the device;
Move the .zip file inside the SDCard;
Turn off the device;
Boot into recovery;
Select "Install";
Select the "External Memory" storage;
Search for the .zip file inside the SDCard;
Tap on it and install it, unchecking everything;
Swipe to continue and let the .zip file install;
The recovery will print you text on the progress (also gives advice on what to do after install);
Reboot to system;
Power off the device;
----------------------------------------------------------------
Unlocking the device:Just a tiny reminder if you haven't yet, check my guide about it: then, resume from this point and proceed;
----------------------------------------------------------------
!!A word of advice!!Don't install PBRP recovery just yet!
If you'll pick PBRP instead of the LOS recovery as the custom recovery of choice, flashing LOS 18.4 with it should make Lineage 100% unbootable and stuck in a bootloop!
Don't reboot back to PBRP if bootloops happen:
neither don't fix the "Cache" partiton with it, else it'll cripple more Lineage and redirect the boot to recovery or fastboot/bootloader!
TL;DR: Don't do my same mistake and flash the recovery partition with the wrong recovery (on the bright side, the device will still be salvageable).
----------------------------------------------------------------
Flashing Lineage Recovery:Before proceeding, do the following firsthand:
Be sure to have the ADB & Fastboot binaries installed;
Your device rebooted to fastboot/bootloader mode (any method is acceptable);
Must have downloaded the recovery for your specific model (links are on the "required" list);
The device must be connected to the host machine (if you're using a rooted phone, be sure to have the OTG adapter connected to it first);
Rooted Android Device Method:
Open the "ADB & Fastboot"tools of your choice;
Whether it is a terminal or the app i've suggested earlier: this portion will purely give instructions if you have the app;
If you're going to do the process via terminal, then jump to the "Linux Method" instead;
If it is the first time you open the tool, it should ask for root perms.- allow them;
Tap on the top right corner of the UI;
Tap on "Fastboot";
Tap on "Refresh";
Go to the "Partition" title, next to it you should see a dropdown menu;
Select "recovery";
Tap on the "Flash" button;
A file manager should open: search where the lineage recovery is (typically you can find it in the "Download" folder. The file should be called "recovery.img");
After selected, the app will automatically flash the recovery for you;
Disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
Linux Method:
Open the terminal (use the shortcut CTRL+ALT+T to open it, preferrably);
Do the following:
Code:
lsusb
# This checks if your asus device is connected proper to the machine
# If it is, lsusb should output something around a "Google" or "Qualcomm" device on the ID Bus
cd Downloads
# If you have put a different language locale, cd into the Downloads folder with it's localized name
ls
# List for the files inside the folder. You should see a file called 'recovery.img' inside
fastboot devices
# Tell fastboot to check if any device on bootloader/fastboot mode is connected
fastboot flash recovery recovery.img
# Gives fastboot the instruction to flash the .img file to the desired device's partition, which is the recovery in this case
After done flashing, disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
Windows Method:GUI Method:
Simply use the "Latest ADB Launcher"executable located on the desktop of your PC;
Just make sure to flash the recovery partition with the "recovery.img" file;
Terminal Method:
Navigate with the File Explorer;
Go to your Downloads folder and find for a file called "recovery.img";
Cut and paste it to where the ADB and Fastboot tools are installed at;
Click on your mouse's right button;
Select "Open terminal here" over the contextual menu;
A terminal should pop-up (Command Prompt, that is);
Type in the following:
Code:
fastboot devices
fastboot flash recovery recovery.img
Wait for the recovery to flash on the device;
After done so, disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
------------------------------------------------------------
Installing Lineage OS 18.1:Before proceeding, do the following firsthand:
Your device must be turned off;
Must have deleted the Android 9 Beta .zip file from the SDCard, for avoiding accidents;
Download the Lineage file off of the "required" list's links for your specific model;
Put the downloaded .zip file on an SDCard;
Insert the SDCard inside the device's slot;
Boot up into recovery mode;
Select with the volume keys "Apply Update" > "Apply from sdcard" and confirm with the power button;
Select the LineageOS .zip file;
Confirm with the power button;
Let the rom install by the recovery;
After install, navigate to the back button with the volume keys;
Select "Factory reset" > "Format cache partition";
The recovery will ask you the following:
Code:
Format Cache?
THIS CAN'T BE UNDONE!
Select "Yes";
Go back;
Select "Reboot system now";
First bootup will take some while, but you'll be greeted by the setup screen in no time.
Congratz, now your device has Lineage OS installed!
-------------------------------------------------------------------
Extras/FAQ Section:Q: Is it possible to get root priviledges on the device?A: Sure! There are different ways to apply root on the ROM, but feel free to pick whichever method you like:
Rooting your device by picking it's 'boot.img' (exactly located on the folder of the respective model) over SebaUbuntu's Lineage site and patch it with an already-rooted device that has the Magisk companion app installed (requires no recovery patching, but it is required to boot the asus device in fastboot mode and patch the boot partition);
Downloading the Magisk companion app over it's GitHub page, rename the .apk file by replacing '.apk' to '.zip' via file manager, patch PBRP over the recovery partition (with one of the methods listed over 2 titles above this one), and install the 'magisk.zip' file like you could usually do on any other device with custom recovery;
If you use an X00I device, you can preferrably install TWRP from here instead of PBRP;
After applied root on the device, patch back on the device the Lineage recovery- just for avoiding any inconvenience if you want to factory reset the device;
Q: My device has Lineage installed, but the bottom buttons don't work. Is there a way to enable a virtual navbar?A: Yep, but it's a bit of a tricky process. You must have either apps like Terminal Emulator or Termux installed for making this work- as an extra, you could get other keyboards like BeHe Keyboard or Hacker's Keyboard: but that is only if you've picked Terminal Emulator as your choice.For direct instructions, follow this (you must be inside the terminal app of your choice and already gave storage perms to it firsthand):
Code:
su
mount -o rw,remount /
vi /system/build.prop
# After come this far, go to the bottom of the build.prop file by scrolling with the touch screen
# On your keyboard, press the I key. This should make vi enter into INSERT mode
# When done so, add the following line on the build.prop file
qemu.hw.mainkeys=0
# For getting out of INSERT mode, find on your keyboard or terminal UI the ESC button
# For quitting and saving the file on vi, type the following
:wq!
# This should make vi quit and save the modifications to the build.prop file
# For rebooting the device straight from the terminal, just type in
reboot
# The device should immediately reboot, and upon unlocking: the virtual navbar should appear
Q: Can it be possible installing MicroG on the device?A: You can! Every method for installing MicroG perfectly works on this ROM;
Q: I have MicroG installed on my device, but i want to apply signature spoofing for extra functionality. Is this possible?A: Sadly, due to the tinkering i've done on my side: the ROM gets a meltdown when modifying the 'services.jar' file is involved (root or non-root). If you follow some guides online (despite being few), the ROM, regardless of what you do or which method you follow: it will end up in a bootloop (or, to be more specific, the SystemUI starts to become picky);
------------------------------------------------------------------
Credits:
miya0405 (for the lineage site)
SebaUbuntu (for the LOS rom, recovery, and PBRP recovery)
Erwin Abs (PBRP Recovery)
aaaaaaziskurnia (TWRP recovery for the X00I)
You, for dedicating your time on reading this long guide!
Related
Alright, I got out of that issue, now its time to tell you how I did this.
Key:
- equals Start of Section
= Equals End of Section
-------------------------------------------- Fixing ADB Recognition (Optional But Vital) ------------------------------------------
First of all, follow my other thread on fixing bootloader being recognized as an android bootloader interface or do this
1. Do steps in this thread up to step 5,1
2. Delete the drivers for the child of Android Device by right clicking the device and press Uninstall Driver, then check the box Delete Driver for this Device. Don't worry, the drivers you installed will not go, it will just delete the watch from being recognized
3. Disconnect your watch then reconnect it
4. You're computer will not recognize this device and it will be placed under the category, in the device manager, as 'other Devices'
5.---- 'Copied from my other thread and changed'------
5,1. Right click on the children of the unknown device
5,2. Go to Drivers and press Update Driver
5,3. Press Browse my computer for driver
5,4. You will be prompted a directory, instead press the button below it called 'Let me pick from a list of Drivers installed on my computer'
6. Locate to ADB Devices or Similar
7. Select any one of the drivers listed inside there
8. Done.
=============================================================================================================
----------------------------------------------------- Installing System and Boot and Recovery (VERY IMPORTANT) -----------------------------------------------
This is where, if you do not change your TWRP to factory recovery, your watch will re boot into TWRP because it cannot mount /data. By flashing the factory Recovery, you will eliminate this and you will have a fresh start into the system.
Prerequisites ( If you Do not have it, which you should):
simple adb here
1. Get the system, boot and recovery from this thread by IntersectRaven
http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
2. Once you have downloaded those, assuming you have done the optional procedure before this, boot/stay into fastboot
3. Place the files into the location where the simple adb is located
{{{ THIS IS THE PROCEDURE YOU SHOULD FOLLOW IN THE FOLLOWING STEPS BECAUSE THAT IS HOW I DID IT }}}
4. first check your device is seen in fastboot by typing
Code:
fastboot devices
5. once your device is seen, active and has a tag fastboot. follow on.
6. Flash the stock system first by using this code
Code:
fastboot flash system yoursystemfilename.img
replacing 'yoursystemfilename' only with the name inside the simple adb
7. Flash your boot by using this code
Code:
[CODE]fastboot flash boot boot.img
[/CODE] where 'boot' is a defined variable in your simple adb folder
8. lastly, flash the STOCK recovery by using this code
Code:
fastboot flash recovery recovery.img
where 'recovery' is a respectable variable in your simple adb folder
9. disconnect and start your system!
=====================================================================================================================
References (for the past 4 weeks):
Emergency Guide
Stock boot,sys and rec
Click to expand...
Click to collapse
Please like and upvote if it helped, as I had to take time off my studies to do this.
Also tell me if there were any mistakes.
Hello,
I finally managed to install a custom GSI Rom with TWRP and Magisk on my Redmi 7A. And I want to share a detailed guide for everyone who is struggling to do the same. Tested with MIUI 10.2.5.0 Global. Cannot guarantee for other versions.
WARNING:
You need to backup your data before installing. I am not responsible for any damage or loss that might occur. Proceed at your own risk.
Prerequisites:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- GSI Rom of your choice. Only a64 A/B (arm32_binder64_ab). No other GSIs will do.
- ADB and Fastboot
- patched boot.img
- TWRP recovery
- vbmeta.img
- Magisk
- Permissiver_v4.zip
- Certification patch
- Treble Overlay file
- GApps (if needed)
Installation guide:
1. Download the files.
GSI Rom:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
I installed Lineage OS 16 GSI (lineage-16.0-20191017-UNOFFICIAL-treble_a64_bvN). Everything works, except for auto-brightness.
https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
Patched boot img file
(You have to choose the correct file according to your system version!)
http://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
vbmeta file
http://www.mediafire.com/file/bgpn9b87b4t8yye/vbmeta.img/file
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Permissiver
http://www.mediafire.com/file/61q8wln4y18ir5k/Permissiver_v4.zip/file
Certification Patch
http://www.mediafire.com/file/fboh2jocqak8cep/Certification_Patch.zip/file
Treble Overlay file (treble-overlay-xiaomi-redmi7a.apk)
http://www.mediafire.com/file/yc7vz3vg13mcrck/treble-overlay-xiaomi-redmi7a.apk/file
GApps (for Lineage OS 16 GSI choose 'ARM' & '9.0')
https://opengapps.org/
2. Unpack Minimal ADB and Fastboot to C:\ drive of your PC
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in ADB folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot flash vbmeta vbmeta.img
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
Code:
fastboot reboot
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
14. Move the downloaded GSI file (*.img) to your phone. (Simply drag and drop in your PC's file manager to SD-card/memory of phone).
15. Flash the GSI Rom: In TWRP choose 'Install' > 'Install Image' and select the GSI. If you put the GSI on your external SD-card you first need to choose Select Storage > Micro SD card. After choosing the GSI file, at Select Partition to Flash Image choose System Image. Then Swipe to confirm Flash.
16. Reboot to Recovery
17. Move Magisk zip and Permissiver_v4.zip to your phone.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
19. Flash Permissiver_v4.zip the same way.
20. Flash GApps if needed
21. Flash Certification_Patch.zip.
22. Go back and choose Reboot > System
23. Fix big rounded corners on home screen:
Once you are in Android and in case you experience big ugly round corners around your home screen, put treble-overlay-xiaomi-redmi7a.apk in System > Overlay directory. You need a file manager with root access if you want to do this from within Android.
24. Fix brightness adjustment issue (no auto-brightness though):
Enable USB debugging in Developer Options menu. To make developer menu appear in Android, you need to tap 7 times on Android's 'build number'.
Now open command prompt from ADB folder on your PC while your phone is still connected via USB. Enter the following:
Code:
adb shell
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
You need to allow adb shell to get root access or the command will throw an error. Your phone should show a confirmation dialog when entering the command. If it doesn't show the dialog, open Magisk Manager app and give root access for Shell in Superuser menu.
25. Enjoy!
Can you please help me have magisk in official rom or stock rom?
DebrupGhosh said:
Can you please help me have magisk in official rom or stock rom?
Click to expand...
Click to collapse
For Magisk on stock Rom:
Your bootloader must be unlocked already!
1. Flash patched boot.img & recovery.img via fastboot
2. Reboot to TWRP
3. In TWRP, go to Wipe > Format Data > "yes"
4. In TWRP, flash Magisk zip
5. Reboot to System
Note: You will lose all your data on the phone. Do a backup of your personal stuff before proceeding.
cg730620 said:
For Magisk on stock Rom:
1. Flash patched boot.img & recovery.img via fastboot
2. Reboot to TWRP
3. In TWRP, go to Wipe > Format Data > "yes"
4. In TWRP, flash Magisk zip
5. Reboot to System
Note: You will lose all your data on the phone. Do a backup of your personal stuff before proceeding.
Click to expand...
Click to collapse
trying the same with miui 11.0.2 indian with repeated reboots and the files on internal storage gets encrypted or something like that.(patched boot image via patcher tool you shared)
after flashing no verity opt encrypt the android sign on boot animation is now showing but this time screen turns off and on
even tried flashing vbmeta.img
DebrupGhosh said:
trying the same with miui 11.0.2 indian with repeated reboots and the files on internal storage gets encrypted or something like that.
after flashing no verity opt encrypt the android sign on boot animation is now showing but this time screen turns off and on
even tried flashing vbmeta.img
Click to expand...
Click to collapse
Did you unlock your bootloader? It must be unlocked before flashing anything.
cg730620 said:
Did you unlock your bootloader? It must be unlocked before flashing anything.
Click to expand...
Click to collapse
Of course i did
WiFi is not working
cg730620 said:
Hello,
I finally managed to install a custom GSI Rom with TWRP and Magisk on my Redmi 7A. And I want to share a detailed guide for everyone who is struggling to do the same. Tested with MIUI 10.2.5.0 Global. Cannot guarantee for other versions.
WARNING:
You need to backup your data before installing. I am not responsible for any damage or loss that might occur. Proceed at your own risk.
Prerequisites:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- GSI Rom of your choice. Only a64 A/B (arm32_binder64_ab). No other GSIs will do.
- ADB and Fastboot
- patched boot.img
- TWRP recovery
- vbmeta.img
- Magisk
- Permissiver_v4.zip
- Certification patch
- Treble Overlay file
- GApps (if needed)
Installation guide:
1. Download the files.
GSI Rom:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
I installed Lineage OS 16 GSI (lineage-16.0-20191017-UNOFFICIAL-treble_a64_bvN). Everything works, except for auto-brightness.
https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
Patched boot img file
(You have to choose the correct file according to your system version!)
http://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
vbmeta file
http://www.mediafire.com/file/bgpn9b87b4t8yye/vbmeta.img/file
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Permissiver
http://www.mediafire.com/file/61q8wln4y18ir5k/Permissiver_v4.zip/file
Certification Patch
http://www.mediafire.com/file/fboh2jocqak8cep/Certification_Patch.zip/file
Treble Overlay file (treble-overlay-xiaomi-redmi7a.apk)
http://www.mediafire.com/file/yc7vz3vg13mcrck/treble-overlay-xiaomi-redmi7a.apk/file
GApps (for Lineage OS 16 GSI choose 'ARM' & '9.0')
https://opengapps.org/
2. Unpack Minimal ADB and Fastboot to C:\ drive of your PC
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in ADB folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot flash vbmeta vbmeta.img
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
Code:
fastboot reboot
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
14. Move the downloaded GSI file (*.img) to your phone. (Simply drag and drop in your PC's file manager to SD-card/memory of phone).
15. Flash the GSI Rom: In TWRP choose 'Install' > 'Install Image' and select the GSI. If you put the GSI on your external SD-card you first need to choose Select Storage > Micro SD card. After choosing the GSI file, at Select Partition to Flash Image choose System Image. Then Swipe to confirm Flash.
16. Reboot to Recovery
17. Move Magisk zip and Permissiver_v4.zip to your phone.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
19. Flash Permissiver_v4.zip the same way.
20. Flash GApps if needed
21. Flash Certification_Patch.zip.
22. Go back and choose Reboot > System
23. Fix big rounded corners on home screen:
Once you are in Android and in case you experience big ugly round corners around your home screen, put treble-overlay-xiaomi-redmi7a.apk in System > Overlay directory. You need a file manager with root access if you want to do this from within Android.
24. Fix brightness adjustment issue (no auto-brightness though):
Enable USB debugging in Developer Options menu. To make developer menu appear in Android, you need to tap 7 times on Android's 'build number'.
Now open command prompt from ADB folder on your PC while your phone is still connected via USB. Enter the following:
Code:
adb shell
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
You need to allow adb shell to get root access or the command will throw an error. Your phone should show a confirmation dialog when entering the command. If it doesn't show the dialog, open Magisk Manager app and give root access for Shell in Superuser menu.
25. Enjoy!
Click to expand...
Click to collapse
I have followed every step. The wifi is not even turning on. I know there must be some small bug. Please help me clear it!
cg730620 said:
Patched boot img file
(You have to choose the correct file according to your system version!)
Click to expand...
Click to collapse
Somehow there is ver 10.2 and 10.4 missing 10.3 which is the one which I have.
What should I do?
Thanks very much for the detailed instructions!
I got it working with lineage-17-arm
Got the beta opengapps from...
https://sourceforge.net/projects/opengapps/
Before copying the treble-overlay-xiaomi-redmi7a.apk file, I had to type...
chmod a+r treble-overlay-xiaomi-redmi7a.apk
mount -o rw,remount /
I followed the steps, and i got stuck on Redmi Logo, My bootloader is unlocked.
Tried to install 2 ROMs without success.
In the second ROM (Lineage 17) when i tried to install gapps, it gave me an error saying insufficient space.
i had to get back to Miui.
Josseda673 said:
I followed the steps, and i got stuck on Redmi Logo, My bootloader is unlocked.
Tried to install 2 ROMs without success.
In the second ROM (Lineage 17) when i tried to install gapps, it gave me an error saying insufficient space.
i had to get back to Miui.
Click to expand...
Click to collapse
Before installing gapps, after installing the rom. Go to TWRP > wipe > "system" > repair > resize fs > reboot. Then install gapps.
It didn't boot after I installed gapps on lineage 16, but it was ok on lineage 17.
Redmi 7A Miui 10.3 Patcher file missing?
Does anyone know where I could find patched file for Miui 10.3, because there is only for ver 10.2 and 10.4, and I can't update miui on my phone that's why I'm asking. Thanks.
in TWRP, after instaling the ROM and trying to install gaps, or whatever I get:
Failed to mount '/system_root' (invalid argument)
I also can't mount system partition in mounting options.
What does it means?
.
After installing TWRP successfully I tried with both roms: lineage-16.0-20191017-UNOFFICIAL-treble_a64_bvN and lineage-17.0-20191117-UNOFFICIAL-treble_a64_bvN
it fails to install any apps (Magisk, permissiver, G-Apps, etc.).
Example from Magisk:
- Mounting /system
! Cannot mount /system
- Unmounting partition
...
Failed to mount "system/root" (invalid argument)
When I now try to reboot again into Recovery TWRP says "No OS Installed".
any help is appreciated!
Same
Hello!,
it's possible with MIUI 11 (PCMINXM) ? or i need to roll back to MIUI10?
Camera records corrupted videos
Any idea how to make camera record videos? Photos work, but when I try to record videos, it seems to be recording, but when I try to play it back it seems corrupted (e.g.: showing length of the video to be over 104h long - so seems like indexing problem). Tried to play with camera_config.xml at root/vendor/etc/camera but no luck so far... :crying:
P.S.: The problem seems to be independent of the app used - Open Camera with Camera2 API enabled does not change a thing.
---------- Post added at 09:16 PM ---------- Previous post was at 09:11 PM ----------
shr!pad said:
Hello!,
it's possible with MIUI 11 (PCMINXM) ? or i need to roll back to MIUI10?
Click to expand...
Click to collapse
Worked for me when flashing from Miui 11 EU - just followed the instructions with little problems.
Blazer291 said:
Any idea how to make camera record videos? Photos work, but when I try to record videos, it seems to be recording, but when I try to play it back it seems corrupted (e.g.: showing length of the video to be over 104h long - so seems like indexing problem). Tried to play with camera_config.xml at root/vendor/etc/camera but no luck so far... :crying:
P.S.: The problem seems to be independent of the app used - Open Camera with Camera2 API enabled does not change a thing.
Same thing with mine, first time i did solve it installing gapps again, but a few days later the problem got back. I´m about to update to last firmware and see if it solves the issue, ill comment later.
Click to expand...
Click to collapse
Same thing with mine, first time i did solve it installing gapps again, but a few days later the problem got back. I´m about to update to last firmware and see if it solves the issue, ill comment later.
Click to expand...
Click to collapse
Don't do that - it's too much work.
Fixed mine by editing camera_config.xml so it has only the config for the model and vendor of the camera that it actually has been fitted with. Now using Open Camera with Camera2 API everything works fine. :victory:
P.S.: So the cause of the problem really seems to be the conflict of different camera configs within the configuration file.
brother please! can you tell me how to do it? like a mini guide, i dont have magisk nor root on my phone. do i need to root it?
would appriciate it so much!!
/*** BEGIN DISCLAIMER ***/
If you follow this procedure and lose every bit of content on your device / end up with a fancy paperweight, I, nor anyone involved with the referenced open source or otherwise licensed projects is responsible. It's all on you, and this will void your warranty. Do not proceed if you don't understand something. Chances are you will have a bad time.
/*** END DISCLAIMER ***/
Hey everyone - my Samsung Galaxy Tab A 10.1" (2019) - SM-T515 - recently applied a security update without my consent (The Samsung Android 11R September 8th 2021 Security update - side note, make sure that you turn off Samsung's push service ), which canned my previous root access. I use server software and internal port forwarding to do... Things on my device, so I needed my root access back.
Here's how I retrieved it, and how I put TWRP in place as my recovery partition in the process.
The Tools
Make sure you have these before you start. Because this is a Samsung device, you'll have to do some things under Windows, like using Frija and Odin (unfortunately).
1.) Frija - Available here - https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/
2.) The latest SM-T515 / SM-T510 firmware from Samsung for your device's CSC (if you use the firmware for the wrong CSC code the most common problem that I have seen as a result is typically incorrect partition sizes after flashing, which can be corrected with TWRP). Frija is listed first, because you'll use Frija to get this directly from Samsung.
3.) Some kind of generic tool that you're comfortable with for working with archives. Ideally whatever tool you choose should be able to work with .tar, .gz, and .zip archives for this process. Personally I like 7-Zip on *Nix and Windows, and ZArchiver on Android.
4.) Odin (firmware flash tool by Samsung) - attached.
5.) The latest Samsung device USB drivers for your environment (they're fine as long as they enable both ADB and MTP correctly) - available here https://developer.samsung.com/mobile/android-usb-driver.html
6.) The latest TWRP image for Samsung SM-T5xx devices - available here https://androidfilehost.com/?fid=14943124697586374577 (and attached)
7.) ADB - downloading / installing and using adb are outside the scope of this post. It is available here - https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
8.) The latest Magisk APK file - available here https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
The Process
0.) Back up your stuff, and remove your SD card if it makes you more comfortable - do whatever you need to do to be comfortable with "I might lose EVERYTHING on this device." If you plan on following this procedure, you should know how to do this, and I'm not going to try to explain it. If you can't get past this part, you should stop while you're ahead and still have a device that boots.
1.) Unlock your bootloader.
2.) Download the most recent firmware package for your device using Frija and extract all of the individual .md5 files which it contains.
2.) Use Odin to flash the most recent firmware to your device, and factory reset / wipe / format partitions and caches until you have a clean device that boots correctly. If your partitions aren't sized properly at this point it isn't something to be too concerned with, as you can correct them later using TWRP.
3.) Turn developer options back on, enable USB debugging, set the default USB configuration to "File Transfer", connect your device to your PC and copy the Magisk APK over to the internal storage of your device.
4.) Remove .md5 from the filename of the AP file that was included in your firmware package from Samsung and extract its contents into its own directory.
5.) Extract the contents of the latest TWRP package for these devices into the same directory where you extracted the individual partition image files contained in the AP file. Overwrite contents in the destination directory as necessary. The TWRP package should contain three files - param.bin.lz4, recovery.img.lz4, and vbmeta.img.lz4 - If there are uncompressed images (.img files) that correspond to the LZ4 compressed images from the TWRP package in the AP file of your firmware package, remove them first. Odin will (understandably) freak out if you try to flash two different images to the same partition in the same flash operation.
6.) Compress the contents of your modified AP directory which now contains the TWRP package's contents into a tar ball on your PC, and then copy it somewhere that Magisk will be able to access it on the Internal storage of your device (the Downloads directory - "/storage/emulated/0/Downloads/" is a good choice).
7.) Copy the latest Magisk APK to your device (again, the Downloads directory is a good choice), and then install it on your device.
8.) Launch Magisk on your device and choose "Install". Be sure to uncheck the "Recovery Mode" option. We don't want to use "Recovery mode" for Magisk's patching process. Even though this is a Samsung device and this would normally be how to proceed, in this case we're using our own custom TWRP recovery partition, and we don't want Magisk to mess with it. So make sure you aren't patching the bootloader or recovery images in unnecessary ways with Magisk.
9.) In Magisk on your device, choose "Select and patch a file" and then choose the AP file that you created and copied to the device which now contains TWRP as its recovery partition.
10). Let Magisk do its patching and when it has completed take note of where the patched file which it generated was written.
11.) Launch a command line / Powershell / Bash terminal where you can perform ADB commands, and issue the command "adb pull "/storage/emulated/0/Download/magisk_patched-23000_xYzXyZ.tar" (replace "XyZxYz" with whatever random sequence of characters that Magisk generated during its patching operations) to use ADB to download the patched AP file from your device.
12.) Power off your device.
13.) Reboot your device into FANCY download mode by holding the volume up and volume down keys simultaneously while inserting a USB cable that is connected to your PC into your device's USB C charger port. Your device should boot as you insert the USB cable and your bootloader should already be unlocked, so when prompted press the volume up button to continue.
14.) Launch Odin on your PC, and choose the BL, CP, CSC, and UserData images from the firmware package that you retrieved from Samsung to flash the corresponding slots in Odin. In the AP file slot, choose the Magisk patched AP file which contains TWRP as its recovery partition which you retrieved previously using ADB.
15.) Start the flash operation in Odin, and wait patiently for it to complete. Stay alert, because if you left "Auto reboot" checked in the Odin options, your device will reboot immediately upon completion, and there are actions that you need to take while the device is in its "off" state before it re-launches itself.
16.) Once the Odin flash operation has completed, boot to recovery mode. If you left "Auto reboot" checked in Odin, immediately as the flash operation completes, press and hold the power key and the volume up key and remove the USB cable from the device. Otherwise press and hold the power button and the volume down button until the device restarts, and while the device is in its "off" state remove the USB cable and press and hold the power button and the volume up button during device restart to enter recovery mode.
17.) Immediately upon entering recovery mode you should see TWRP do a couple of things that ensure that Samsung's device protection solutions don't remove it. Once those operations have completed, reboot into the system partition.
18.) Your device should be BASICALLY ready to go. Go through the steps to "complete" setup as you see fit. If you have not already done so, connect your device to a WiFi or to an LTE network and then launch the Magisk application.
19.) Magisk may want to download updates, if it does, let it do so.
20.) Once any necessary updates / downloads have completed, re-launch Magisk and it should present you with a prompt to the effect of "Magisk is installed, but additional configuration needs to be done on your device for it to work the right way. Do you want to reboot now?" If you've made it this far, the answer is "Yes, please do."
21.) After rebooting, your device will now be configured, and be running TWRP in its recovery partition, along with a properly Magisk rooted system partition.
22.) ????
23.) PROFIT!
I hope this helps some people out!
- The Scarecrow - 2021/09/22
Has anyone besides been successful?
mydjtl said:
Has anyone besides been successful?
Click to expand...
Click to collapse
I can provide screenshots from the device that I did this to if you would like.
It's pretty cool to see the TWRP logo on a Samsung Tab series device that's running Android 11.
I don't even get the little Samsung warning prompt during device bootup that says "This device's software can't be verified" or whatever Samsung's custom ROM message is. All I get is the "This device's bootloader is unlocked" message, no warning about the integrity of the software.
mydjtl said:
Has anyone besides been successful?
Click to expand...
Click to collapse
Follow this simple as he'll no need to read all these things
pankspoo said:
Follow this simple as he'll no need to read all these things
Click to expand...
Click to collapse
Yeah - pretty much exactly that, except I Magisk patched the system image, and then copied the TWRP package's vbmeta and recovery image into the AP file for the Odin flash, and then flashed every slot rather than just the AP.
is it systemless root?
Will this work on Galaxy Tab A sm-t595? on android 10?
or know of a root guide that will work with said device?
If you dont untick auto reboot, how do you fix any issues that happen because of it?
I rooted my t500 but I think it auto rebooted, which then caused a vbmeta error that stopped it booting. It worked again after flashing the stock rom, but now it gives a vbmeta error if I try to flash a modded rom to root it and I cant get oem unlock to appear in the stock os (download mode says its already unlocked tho)
Hello,
Code:
9.) In Magisk on your device, choose "Select and patch a file" and then choose the AP file that you created and copied to the device which now contains TWRP as its recovery partition
Step 9 yields an error on T515 : Unsupported/Unknown image format
I also tried to install AP patched file with Odin, same result.
Any idea ?
Damn this works so nicely, thanks mate! Cheers!
Improving Your Lenovo ThinkSmart View (Custom Recovery, Root, Play Store, Custom Webview)Huge credit to @deadman96385 on how to flash your Lenovo Thinksmart View device and providing access to the firmware files! Credit to @WhyPartyPizza on reddit for the adb enable steps. And also, credit to @Xi07 on providing a way to install TWRP and demonstrating that it is possible to get the Play Store working. And also credit to @garnir4ik on showing us that we can root the device.
The point of this guide is to organize all the information we have on the device and provide a way to make the device more usable (especially since some of the software on the device is outdated).
The guide covers how to:
Install TWRP (optional) and Magisk (recommended) on the device
Install microG and the newest version of the Google Play Store (Magisk required)
Update Webview (needed for Home Assistant)
I'm still trying to figure out how exactly to do certain things on this device so feel free to leave any new information you find!
Installing TWRP (optional) and Magisk (required for Play Store)Quick Blurb:To install TWRP, you will need to flash new firmware onto your tablet. However, since there's currently no way to use the device with the bootloader unlocked, a lot of the features used in TWRP are unusable. It might still be good to install TWRP in case someone finds a way to modify the device to better utilize TWRP.To install Magisk, it will be much easier to do it by flashing new firmware. However, it is also possible to install Magisk without flashing new firmware. I will include the steps to do this below these.Steps:
Download and install the Qualcomm drivers from here
Download and install QPST from here
Download the firmware from this thread (Credit to @deadman96385). I used the 200628.084 version for reference.
Extract the firmware to a folder that you can easily access, like on your desktop.
If you want to install TWRP, download the recovery.img file attached to this post. (Credit to @Xi07)
Open the folder that you extracted the firmware to. In the image folder, replace the recovery.img file with the one you downloaded.
If you want to install Magisk, download the boot.img file attached to this post.
Open the folder that you extracted the firmware to. In the image folder replace the boot.img file with the one you downloaded.
Download the firehose/rawprogram file from @deadman96385's post and flash the package using the instructions provided by @deadman96385. I've included them here for your convenience:
Spoiler: Expand Here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8953_ddr.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram_unsparse.xml and then the patch0.xml when prompted.
Remove the cover on the USB-C port on the bottom right of your device
Plug the USB-C cable into your computer
Unplug the power from the device
Hold vol+ and Vol- and then plug the power into your device (Smart Plugs can make this easier)
If the text at the top of the QFIL application mentions qdloader move on to next step. If it says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you most likely didn't install the drivers properly.
Click the Download Button to begin flashing your device
Once complete it should automatically reboot but sometimes it doesn't so you need to replug your device.
If you get the dreaded "Sahara" error when flashing your device, you may be waiting too long to flash. The device must be flashed moments after it is booted into EDL mode (powering on with Vol + and Vol - held down). Once you plug in your device, hit download the moment the port is recognized at the top of QFIL.
You can also try disabling driver signing (I'm not sure if this makes a difference). To do so:
Spoiler: Expand Here
Open a command prompt as an Administrator.
Run
Code:
bcdedit /set testsigning on
and restart your device
Your computer should say it's in Test Mode (bottom right corner). To disable driver signing, follow the same steps but run
Code:
bcdedit /set testsigning off
instead.
Thanks to HowToGeek's article for the information.
From here, you can go ahead and follow the original method from @deadman96385 for breaking into the device.
Spoiler: Expand Here
When it boots up select Teams (Others seems to try and network boot/download files and fails)
Go through the setup wizard until you get to the Microsoft Teams (Language > Wifi > Bluetooth > Teams)
Select the Gear Icon in the top right of the teams page
Select the "About" settings option
Tap on "CD-18781Y.200628.084" under firmware version a bunch of times rapidly until a prompt comes up saying developer unlocked.
If your usb c cable is plugged, in unplug and replug it in.
You will now have ADB access.
Download your desired Launcher and use the following command to install it:
Code:
adb install APK_FILE_NAME.apk
You will then need to send this adb command to select a new default launcher:
Code:
adb shell am start -a android.intent.action.MAIN -c android.intent.category.HOME
I would recommend getting a navigation bar app. I've attached the one I used to this post.
You can also technically install Magisk without reflashing your device.
Spoiler: Expand Here
Install the Magisk app (use the Magisk APK)
Enable OEM unlocking in Developer Settings
Unplug the device. Hold Vol- and plug in the device to boot into fastboot mode.
In command prompt, execute
Code:
fastboot devices
to make sure the device is discovered. If a device is not listed, you may need to go into Device Manager > Other Devices > Android device with question mark. Right click > Update Drivers > Browse My Local Drivers > Let me pick from a list > Change to Fastboot Drivers.
Code:
fastboot oem unlock-go
This will unlock your bootloader.
Unplug the device. Hold Vol- and plug in the device to boot into fastboot mode.
In command prompt, navgiate to the directory where your Magisk boot.img is downloaded. Run
Code:
fastboot flash boot boot.img
After the boot.img is flashed, you need to lock your bootloader to be able to boot back into the device. If you're not in fastboot mode, you can once again unplug the device. Hold Vol- and plug in the device to boot into fastboot mode.
Run either of the 2 commands to lock the bootloader. You can restart the device and boot into the device once you are finished.
Code:
fastboot oem lockfastboot flashing lock
Steps for Google Play Store and Custom Webview will be in the next post (to reduce clutter).
Installing MicroG and the Newest Version of the Google Play Store (Magisk Required)
Download and install the MicroG Services Core and Services Framework Proxy from the MicroG site.
Install the Magisk app (use the Magisk APK). When you open the app, it should say the version of Magisk installed next to "Installed."
On your Android Device go to Settings > Connected Devices > USB > File Transferring Mode.
Download the NanoDroid-patcher.zip file, BusyBox.zip, and terminal_systemizer.zip. Do not unzip these files. Drag and drop these devices onto your Android device.
In Magisk > Modules > Install from storage, find the .zip files and install all 3 Modules. The NanoDroid-patcher module in particular may take awhile so be patient.
Install the apk of Google Play Store of your choice.
Install Termux. In Termux, issue the command
Code:
su
A superuser popup should show up. Make sure to allow Termux Superuser access. If you miss clicking on it, you can allow access in the Magisk App > Superuser.
Code:
systemize
Follow the dialog prompts to systemize Google Play Store to /system/priv-app
Restart the device.
Open the microG settings app. Register the device in Google device registration. In Self-Check, click on each setting (the words, not the checkboxes) and enable them all. Pay particular attention to System spoofs signature being checked off.
Restart the device again if you want. Google Play Store should be working fine now (may need to clear it's App Data first if it's not working).
Installing Custom Webview (Magisk Required)Some apps such as HomeAssistant won't function without an up to date System Webview. As this tablet is running a quite old version Webview version, this causes these apps to not work. Luckily, there's a Magisk Module to fix that.
Download the Webview_Manager zip file and drag and drop it onto your device. Install it using Magisk. You will need to watch it install as it requires some input on which Webviews you want to install.
After restarting the device, navigate into Settings > System > Developer options > Webview implementation. You should now be able to change your Webview to a updated version.
Note, you may need to unplug and replug in the device after the first restart of installing Webview.
Reserved 2
Chewie610 said:
Download the firehose/rawprogram file from @deadman96385's post and flash the package using the instructions provided by @deadman96385. I've included them here for your convenience:
Spoiler: Expand Here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8953_ddr.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram_unsparse.xml and then the patch0.xml when prompted.
Remove the cover on the USB-C port on the bottom right of your device
Plug the USB-C cable into your computer
Unplug the power from the device
Hold vol+ and Vol- and then plug the power into your device (Smart Plugs can make this easier)
If the text at the top of the QFIL application mentions qdloader move on to next step. If it says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you most likely didn't install the drivers properly.
Click the Download Button to begin flashing your device
Once complete it should automatically reboot but sometimes it doesn't so you need to replug your device.
Click to expand...
Click to collapse
A slightly easier way that may work I haven't validated on the thinksmart specifically is using qfil's partition manager tool. It allows you to dump, erase, flash individual partitions, that way you can flash just the one you want without having to deal with a full qfil flash. Finish all original steps up to 10. Instead of clicking download do the following instead:
Navigate to the top menu: Tools -> Partition Manager -> OK. If all goes well, you will be greeted with a dialog listing all partitions in ~5s. If this is not the case even after a full minute, try re-entering EDL/9008 mode.
Once the partition list is loaded, you can perform the following actions on partitions by right clicking a partition and then clicking 'Manage Partition Data'.
'Erase' (Clear the partition)
'Read Data...' (Dump the partition)
'Load Image...' (Flash the partition)
Click to expand...
Click to collapse
This is also a great way of backing up partitions from your device. The dumped partition can be found in C:\Users\%USERNAME%\AppData\Roaming\Qualcomm\QFIL\COMPORT_##. Note that the name of the file is the raw file locations so you will need to rename the imgs as you go.
Very nice to see Y700 get it's own place on XDA! I myself had just bought the 12GB version and have been very satisfied. The tutorials and info related to this model had been very difficult to come by and mostly in other languages, so I had to do my own research and exploration. So far I was able to flash ROM and extract it's boot image for root thanks to the following tutorial (in Japanese)
boot.imgを入手できない機種でMagiskを導入する方法【DSU Loader】
Android端末のカスタマイズやRoot権限の使用が可能となる「Magisk」ですが、一部例外を除き、導入に…
smartasw.com
The boot image extraction part is trickier as Y700's roms come in GSI form. But with a workaround we can still achieve the same goal. (I heard that you can also use QFIL to do that but I haven't been able to make the tool work, so if someone else can make a tutorial that'd be great)
First you need to prepare:
- DSI-Sideloader from https://github.com/VegaBobo/DSU-Sideloader/releases
- Magisk Manager from topjohnwu's GitHub repo
- a GSI ROM with built in root permission. The one the tutorial was using: https://github.com/phhusson/treble_experimentations/releases/tag/v402 --> go download "system-squeak-arm64-ab-vanilla.img.xz" (~600MB, smallest needed to fulfill the task)
- turn on developer mode and ADB debugging. Get Google SDK platform tools ready and USB drivers installed.
Connect your Y700 to a computer. Check if ADB works.
Next, install the DSI-Sideloader app. Also extract the .xz package you downloaded above to get the .img image (should be ~1.7GB in size)
Copy the image to your Y700 tablet. Open the DSI-Sideloader app, load the image, set userdata size to default (2GB). You can leave image size unchanged.
NOTE: if you have an SD card inserted, click on "config" and check "Unmount SD", or just eject your SD card from tray. Failing to do so will result in error in the install step.
After you're done, click "Install". Once finished there will be a pop-up with commands you need to enter in the terminal of your choosing. On your computer navigate to the directory containing executables of Google SDK platform tools, fire up terminal, enter the 1st command (says non-root) as instructed, and run it.
You will see a progress bar in the drop-down notification area which will complete in a moment and prompt you to reboot. Do that from there.
After reboot you will be running the modded Project Treble ROM, with root access. It's a full fledge OS but once you shutdown / reboot you will go back to your own OS. Treat it as a LiveCD of some sort.
While still connected, turn on dev mode + ADB debugging and go back to terminal for some ADB work. Next we will be extracting boot image under the current environment, made possible by it's built-in root permission.
Run the following line by line:
Bash:
adb shell
Bash:
su
Bash:
cd /dev/block/bootdevice/by-name/
Bash:
mkdir /sdcard/backup_img
Bash:
for file in *; do
if [[ "${file}" = boot* ]]; then dd if=/dev/block/bootdevice/by-name/"${file}" of=/sdcard/backup_img/"${file}".img ; else continue ; fi
done
The 4th command creates a new directory storing extracted boot image, in our case /SD card/backup_img; and the 5th command is the meat of the entire process. It consists of 3 lines, key in one at a time and press "Enter". First line is "for...do", second is "if [[..." to "fi", third is just "done".
After some time the extracted boot image will be stored under the directory specified by the 4th command, in our case /sdcard/backup_img . They are stored in the temporary user space and once you reboot to your original OS you won't be able to access them again. So you need to turn on File Transfer mode, go to the actual directory on your PC and move them to your computer. They have the filenames "boot_a.img" and "boot_b.img" . After you're done, just reboot as usual and you'll get into your old OS.
Now you have the boot images, all that's left is to use Magisk Manager to patch them, enter fastboot mode, and flash the patched images using the following commands:
fastboot flash boot_a patched_img_A.img
fastboot flash boot_b patched_img_B.img
(Rename as needed)
And now your Y700 is rooted.
The linked Japanese webpage also talks about working Android 12 / 13 GSI flavors, patches, and ways to set up your Y700.