YT-X705F - Rooting Guide (Android 10.0) - Android Q&A, Help & Troubleshooting

Solution below.

For those with the same device, I was able to successfully root + pass safetynet, without TWRP or custom recovery. Since this device isn't yet on the forums I thought I should share my findings.
At the time of rooting, I was currently updated to the newest version available (10) and did this through the regular OTA updates.
Preparations
1. Download Magisk Manager Beta from https://magiskmanager.com/magisk-beta/
2. Download the stock firmware for your tablet from https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
3. Download kdrag0n's SafetyNet Fix from: https://github.com/kdrag0n/safetynet-fix/releases
Edit: looks like I missed a step, thanks for the feedback! Point 4 has been corrected to include instructions on how to unlock the bootloader specifically.
4. Unlock your bootloader, instructions on how to enable USB debugging which is needed, can be found here: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html, from there you can open your command prompt, navigate to the directory where you have your fastboot and ADB stored, and type "adb devices" to confirm your device is found (a serial number will display on success) - next type "adb reboot bootloader" to force your tablet to restart into it, finally type "fastboot oem unlock-go" to unlock the bootloader. This voids your warranty.
-- end of edit.
5. Enable USB debugging through developer options (go to settings->about->find build # and tap a handful of times until it says you are a developer.
6. Plug the tablet into your PC, and set the default option to Charge only, or go to file transfer mode and enable USB debugging over file transfer.
Steps
1. Unzip the firmware, there should be a folder called Maincode, in it contains "boot.img" as well as adb/fastboot.
2. Copy the boot.img and Magisk apk to the tablet.
3. Install Magisk
4. Tap on "Install" or "Update" beside Magisk in the app and follow the prompts.
5. You will be asked to select a file, select the boot.img you copied earlier.
6. This will generate a file (it will tell you the path) of a patched boot image.
7. Reboot, and copy the patched boot image to the "Maincode" folder from the tablet.
8. In command prompt, type adb devices and make sure your serial number is shown. If not, review the preparations.
9. Type adb reboot bootloader and you'll see a cute little Tux (penguin)
10. Type fastboot devices and ensure your device is shown, if not then it could be bad drivers on your PC or a crappy USB cable. Check device manager on your computer and make sure you see Lenovo ADB. You may have to force it to install it, or you may see a yellow exclaimation mark - right click on the device and force it to install the Lenovo Bootloader option.
11. Next, in the "Maincode" folder where you put the patched image, rename the old "boot.img" to "stock_boot.img" and the patched version to "boot.img"
12. Back in the command prompt, type fastboot flash boot boot.img
13. Reboot by typing fastboot reboot.
Magisk should now be installed, and your tablet should be rooted. Next, you'll want to go into Magisk and do the following:
Steps:
1. Click on the modules button (bottom of the screen, far right option) and at the top you're given an option to install from storage.
2. Navigate to the SafetyNet Fix zip file and select it, then proceed.
3. You will be given the option to reboot - do this. The first time it may go into recovery, but rebooting brings you back to the home screen.
4. Go back to Magisk, click on the gear at the top right - there is an option to hide Magisk from the system, do this and name it whatever you'd like (just not Magisk) - wait a moment, as the app will restart after it installs.
You can check to make sure you pass SafetyNet in the Magisk (now renamed) app, and root status by downloading one of the countless root checking apps on Google Play Store.

Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance

Bobmat34 said:
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Click to expand...
Click to collapse
Thanks for pointing that out! - I've updated my notes above, but if your familiar with fastboot the command is simply "fastboot oem unlock-go", no unlock code needed for these guys. It will wipe your device and void your warranty though, in case you're not already aware.
Cheers!

Thanks for this rooting guide! I was able to root my YT-X705F
Here some comments/hints:
- At first make sure your downloading the right stock firmware. I've tried a different one which results into a boot loop. One way to find out the right version is to start into the recovery mode. In the header you will find the right version. In my case it was YT-X705F_S001130_210508_ROW
- Make sure you have actually unlocked the boot loader. "fastboot flash x y.img" worked, so I didn't recognized that the boot loader was not unlocked. This was reason for "fastboot boot y.img" shows errors "FAILED (status read failed (Too many links))".
- The extracted stock firmware have no "Mainfolder". All files, including boot.img and recovery.img, contained in the root directory of the ZIP file.
- After installing Magisk app (v23.0) it shows me: Installed: N/A, Ramdisk: No, A/B: No, SAR: Yes. According to this Magisk installation guide you have to patch the recovery image instead of the boot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Patching the recovery image was fine with Magisk. No errors was shown. Please note I used the recovery.img
After this I was able to boot the patched image without flashing it:
After "fastboot boot patched_recovery.img" nothing happens. The tablet keeps showing me the Linux Tux image. I have to disconnect the USB cable and then I booted into system.

*Upd. never mind, I download the official rom file from lenovo\
Crap. I patched the boot image with Magisk, and by the time I flashed it - the system got updated from S001133 to S001135, and I'm getting a bootloop. Can someone maybe upload original boot img from S001135?
Or what else can I do? the update isn't on the mirror server yet https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/

Rooting was successful! Thanks for the guide. Since I cannot find any section in the forum for the YT-x705 tablet, I thought I can have a follow up question in here. The reason I rooted was because alexa app keeps getting removed after each reboot. I rooted as I wanted to convert it into a system app.
So far, I've been unsuccessful . I have tried with the systemizer module and titanium backup. Anyone have any idea how we can retain alexa app after a reboot? Interestingly enough, titanium backup shows alexa as frozen after I install alexa from playstore, despite it appearing in my app launcher. I am unable to unfreeze it. Alexa is then removed after I reboot.

Quick question: What do i do if i don't have a "MainCode" folder, on the tablet or in the extracted folder.
or is that just the folder with the maincode, in it?
Thanks, looks like a good guide!
Jim

you're just going into the zip file from step 2 where the boot.img file is. I just followed all these instructions and got my yoga rooted.

ugh...I don't have a device that I can root for a couple of years... and it feels like I'm a complete noob, now!
when i try to flash the boot image I'm getting: FAILED (remote: Partition flashing is not allowed)
When i run fastboot oem device-info i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Finished. Total time: 0.010s
So i don't think i am unlocked. even after following the steps. I've got Developer options, Debugging is obviously working, OEM Unlocking is toggled on.
I feel like on my phones we had to run an adb or fastboot command, and then the device would reboot and reset it and it would then be unlocked.
Am i missing something?
Thanks again!!
Jim
p.s. and once i get it working, what roms can i flash? any of the "yoga" roms? or do i need to look at something specific like the 3 or 4?

answered my own question!
i had to run: fastboot oem unlock-go
the device rebooted and reset
now i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Now on to the next step!

So anyone know what ROMs i should use and how best to install them, i don't think we have a working TWRP, do we?

... after crash of my booting Android 10 system last stock rom my yt-x705F 210909 can't be rooted anymore!
i use some app and this app ask for busybox .... so crash !!!
i reset tablet by system recovery .
"wipe data/ factory reset"
after restart my tablet is working again.
Bootloader is still open
also develover mode is working USB Debugging etc.
but no rooting alowed by patching root img .. see next
now i try to install stock rom NEW but some error
"apply update from external storage " get error
same is from "Apply update from ADB" abd sideload file.img
are this zip files from this server corrupt? mirros lolinet ?
i use magisk 25.2 i try all option with hook on recovery also vbmeta
patch both boot.img and recovery.img
after patch one of these img device runs into the bootloader , tux start up.
if i patch stock boot.img device booting normal but NO ROOT
also twrp can't no flash only option "fastboot boot twrp.img"
"fastboot boot flash recovery twrp.img" not working
if i use twrp by "fastboot boot twrp.img" zip stockrom makes also error
someone knows about RESCUE and SMART ASSISTENT" LMSA Tool ?
any suggestion

how is this working ?
go on settings > about tablet > push a view times on Hardware-Version

NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?

looserintheend said:
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
Click to expand...
Click to collapse
Know where can I find this firmware?

Related

[GUIDE] All Things Phab 2 Pro, Unlock Bootloader, Root, TWRP!

1.
I unlocked the bootloader following the Russians tutorial at http://lenovo-forums.ru/topic/22665-lenovo-phab-2-pro-razblokirovka-bootloader-by-sevenmaxs/
YOU DO NOT NEED TO DISABLE SECURE BOOT, only do the step in that tutorial about how to unlock the bootloader.
Google translate does a good enough job with that page, ask here if stuck.
See post below for English translation on how to unlock the Bootloader.
2
After unlocking bootloader you can load TWRP without actually installing it with fastboot, see https://forum.fairphone.com/t/howto-use-twrp-without-flashing-it-e-g-for-backup/23747
Get TWRP https://drive.google.com/open?id=0B4WxcwjxK2VnZ0tWSl9wUTVoaTg
When you are in this temporary recovery you need to wipe data, this REMOVES ENCRYPTION! yay! :good:
(DO NOT REBOOT! Rebooting would just generate a new encryption key and you would have to repeat this step.)
Then in the same recovery you will be able to mount internal storage, put the SuperSU.zip file on your device and flash it in TWRP.
Congratulations, you are rooted!
3.
To install then TWRP permanently just usual fastboot flash recovery twrp.img
You are done! :highfive:
Get QPST Flash tool, install the Lenovo and Qualcomm USB drives that come with it aswell.
https://drive.google.com/open?id=0B4WxcwjxK2VnM2pvRDk0VzZLVWs
Download the PB2-690M unlock attachmet from this post and unpack it to the root of your drive, aka directly in C:\PB2-690M unlock
Connect your phone by USB, make sure USB debugging is on and your pc is authorised.
Now run the QFIL tool from step 1, in the upper left corner select flat build
In the Select Programmer line, click on the Browse button and specify the path to the unpacked file \ PB2-690M_unlock_7M \ img \ prog_emmc_firehose_8976.mbn
Click on the Load XML button and select rawprogram0.xml first, and then patch0.xml
Run Reboot_QDLoader.bat .
In Windows device manager you should see a device "Qualcomm HS-USB QDLoader 9008" under COM Ports if all is good.
In QFIL click "Download" to execute, should say Download Suceed, Finish Download if it all went well.
Now disconnect the USB cable, power on the device (might have to hold power for a bit) and re enable USB debugging and allow OEM Unlock if needed.
Connect cable again, allow your PC for USB debugging on the device, and run Unlock_Bootloader.bat
The device should reboot to bootloader, and then reboot again to a screen with the Android robot, THIS WIPES YOUR DATA!
That's it, you have unlocked your bootloader! Congratulations!
Yes. Good job.
Mhhh... If something goes wrong, how can we restore the stock firmware? I can't found the last version.
Lenovo often disable the server of ota (i saw that on lenovo's forum).
Maybe a guide for restore can be useful too.
Anyway thank you very much.
vespino75 said:
how can we restore the stock firmware? I can't found the last version.
Click to expand...
Click to collapse
At the moment you need go to russian forum here http://lenovo-forums.ru/topic/23342-proshivka-phab-2-pro-pb2-690m_s200100_170228_row_qpst/ and here https://cloud.mail.ru/public/2B9M/3uV5oLdB1
Sorry. You must know russian or wait/ask for translate.
Elemy said:
At the moment you need go to russian forum here http://lenovo-forums.ru/topic/23342-proshivka-phab-2-pro-pb2-690m_s200100_170228_row_qpst/ and here https://cloud.mail.ru/public/2B9M/3uV5oLdB1
Sorry. You must know russian or wait/ask for translate.
Click to expand...
Click to collapse
Sorry, i am an idiot. This is the last firmware version.
Sorry.
Exelios said:
RESERVED
I will translate the russian tutorial and add a more step by step guide as soon as I have time, this for now should let advanced users do their thing.
Click to expand...
Click to collapse
Pardon. Is it actual?
Can someone who didn't unlock the bootloader yet try step 2? Can you fastboot boot twrp.img with locked bootloader?
I'm really curious
Exelios said:
Can someone who didn't unlock the bootloader yet try step 2? Can you fastboot boot twrp.img with locked bootloader?
I'm really curious
Click to expand...
Click to collapse
Code:
C:\Users\Administrator\Downloads\PB2-690M_unlock_7M\tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4072000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xceb7fbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x140000000
(bootloader) serialno:c9a7e83e
(bootloader) kernel:lk
(bootloader) product:MSM8952
all:
finished. total time: 0.016s
I assume because of "(bootloader) secure:yes" that my bootloader is locked.
Tried to boot "twrp-lenovo-tango.img" from your post#1 section 2
Code:
C:\Users\Administrator\Downloads>PB2-690M_unlock_7M\tools\fastboot.exe boot twrp-lenovo-tango.img
downloading 'boot.img'...
OKAY [ 0.563s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.563s
So i guess bootloader unlock is inevitable.
google translate of h**p://lenovo-forums.ru/topic/22665-lenovo-phab-2-pro-razblokirovka-bootloader-by-sevenmaxs/
[russian]->[german] = horrible
[russian]->[english] = somehow understandable
but this is the result of my testing:
Code:
Programmer Path:C:\PB2-690M_unlock_7M\img\prog_emmc_firehose_8976.mbn
Image Search Path: C:\PB2-690M_unlock_7M\img
RAWPROGRAM file path: C:\PB2-690M_unlock_7M\img\rawprogram0.xml
PATCH file path:C:\PB2-690M_unlock_7M\img\patch0.xml
Start Download
Program Path:C:\PB2-690M_unlock_7M\img\prog_emmc_firehose_8976.mbn
Download Fail:Sahara Fail:QSaharaServer Fail:Der Verzeichnisname ist ungültig
Finish Download
SaharaServer Fail... at this point i have absolutely no **** clue what i'm doing
and i violate the rule set in the second sentence of the russian guide:
"You must understand what you are doing! "
i hope you find the time to write an foolproof guide, since i found only wrong and misleading information about rooting my phone...
Greetz
oRG4ZMo
----------------------------------------------------------------------
edit:
after reviewing all steps i've found the solution for my QFIL error.
In the russian thread is an older version linked:
QPST_&_Drivers.7z
contains QFIL 2.0.0.4 not 2.0.0.5 like on the provided screenshots.
Now i'm stuck at the same step like "pancx 0" from post #6 in the russian thread. :/
i finally got my bootloader unlocked and magisk installed after hours of studying lenovo-forums.ru
this is what i did:
switch from a Windows 2016 Server Workstation to a fresh installed Win 7 x64 on another PC
driver install order:
- phone factory reset
- enable usb debugging
- LenovoUsbDriver_autorun_1.1.33_user.exe from the emulated CD-Drive of the Phab2Pro
- installed newest QPST.2.7.460.zip
EFS Backup described here:
h**p://lenovo-forums.ru/tutorials/article/989-efs-%D0%BD%D0%B0-qualcomm-%D1%83%D1%81%D1%82%D1%80%D0%BE%D0%B9%D1%81%D1%82%D0%B2%D0%B0%D1%85-%D1%80%D0%B5%D0%B7%D0%B5%D1%80%D0%B2%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5-%D0%B2%D0%BE%D1%81%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5/
this seems to fix my error "System cannot find the file specified"
with patched boot partition works the command "fastboot oem device-info" (works now even on my other workstation without changing anything)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after that it is possible to boot TWRP Recovery img without flashing it "fastboot boot twrp-lenovo-tango.img" like described in your link - no problems.
and so on ...
sorry it's late again.
Greetz
oRG4ZMo
oRG4ZMo said:
i finally got my bootloader unlocked and magisk installed after hours of studying lenovo-forums.ru
this is what i did:
switch from a Windows 2016 Server Workstation to a fresh installed Win 7 x64 on another PC
driver install order:
- phone factory reset
- enable usb debugging
- LenovoUsbDriver_autorun_1.1.33_user.exe from the emulated CD-Drive of the Phab2Pro
- installed newest QPST.2.7.460.zip
EFS Backup described here:
h**p://lenovo-forums.ru/tutorials/article/989-efs-%D0%BD%D0%B0-qualcomm-%D1%83%D1%81%D1%82%D1%80%D0%BE%D0%B9%D1%81%D1%82%D0%B2%D0%B0%D1%85-%D1%80%D0%B5%D0%B7%D0%B5%D1%80%D0%B2%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5-%D0%B2%D0%BE%D1%81%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5/
this seems to fix my error "System cannot find the file specified"
with patched boot partition works the command "fastboot oem device-info" (works now even on my other workstation without changing anything)
after that it is possible to boot TWRP Recovery img without flashing it "fastboot boot twrp-lenovo-tango.img" like described in your link - no problems.
and so on ...
sorry it's late again.
Greetz
oRG4ZMo
Click to expand...
Click to collapse
I have one on the way and hopefully what you posted will help me get it rooted.
Do you have the 690m or the 690y?
You who? I have the 690m
ddubz said:
Do you have the 690m or the 690y?
Click to expand...
Click to collapse
Making a proper translation of the russian post today, sorry for the delay, working on 6 devices atm.
PS, Translation done, feel free to suggest edits if anything can make it easier.
Devs complaining English uncommented code is hard to understand
Me be like, hold my beer
Exelios said:
Get QPST Flash tool, install the Lenovo and Qualcomm USB drives that come with it aswell.
https://drive.google.com/open?id=0B4WxcwjxK2VnM2pvRDk0VzZLVWs
Download the PB2-690M unlock attachmet from this post and unpack it to the root of your drive, aka directly in C:\PB2-690M unlock
Connect your phone by USB, make sure USB debugging is on and your pc is authorised.
Now run the QFIL tool from step 1, in the upper left corner select flat build
In the Select Programmer line, click on the Browse button and specify the path to the unpacked file \ PB2-690M_unlock_7M \ img \ prog_emmc_firehose_8976.mbn
Click on the Load XML button and select rawprogram0.xml first, and then patch0.xml
Run Reboot_QDLoader.bat .
In Windows device manager you should see a device "Qualcomm HS-USB QDLoader 9008" under COM Ports if all is good.
In QFIL click "Download" to execute, should say Download Suceed, Finish Download if it all went well.
Now disconnect the USB cable, power on the device (might have to hold power for a bit) and re enable USB debugging and allow OEM Unlock if needed.
Connect cable again, allow your PC for USB debugging on the device, and run Unlock_Bootloader.bat
The device should reboot to bootloader, and then reboot again to a screen with the Android robot, THIS WIPES YOUR DATA!
That's it, you have unlocked your bootloader! Congratulations!
Click to expand...
Click to collapse
I think I am getting lost somewhere during line 10. My phone reboots and (I assume is in it's fastboot mode) I can do fastboot commands at the screen, it DOES NOT make it to the android robot screen. I let it set for a few minutes and nothing happens. It just stays on the Lenovo boot screen.
I did manage to do this and get it to say OK instead of FAILED. I did fastboot flash recovery instead of fastboot boot.
Thank you for your time.
Is support for exfat file system in this twrp?
I tried to backup to my exfat flash drive, but flash drive is unvisible.
Is support for exfat file system in this twrp?
finally! after 3 years with Galaxy Note 3,i got phab 2 pro and successfully rooted,i try to root it from yesterday..today i did it!
hello guys.
1. could someone create a new topic with clear steps and software needed for the bootloader unlock and root of our device?
2. are there any custom roms available for our device? audio lag in videos and some other staff are pretty annoying!!!
@Exelios: it would be much more user friendly if bootloader unlocking, rooting and installing twrp were in seperate topics so users with specific problems could find more direct help. just a suggestion
I finally got TWRP on the 690Y. After following the instructions in post #2, you'll need to do this. After doing the Windows-specific stuff, I rebooted back to Ubuntu, and installed the android-tools-adb and fastboot packages:
Code:
adb reboot bootloader
(wait a few seconds)
fastboot oem unlock
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot reboot
Note: the above commands might wipe your system and reboot again, in which case you have to go through the Lenovo setup, enable dev mode, enable USB debugging, etc all over again. I'm not sure that fastboot flashing unlock_critical is necessary.
After the reboot:
Code:
adb reboot bootloader
(wait a few seconds)
fastboot flash recovery twrp-lenovo-tango.img
fastboot flash recovery twrp-lenovo-tango.img
(I don't know if doing it twice actually matters)
Hold down power until it turns off
Contrary to the above posts, the correct combo to get into TWRP is Volume Up-Power. Once the phone vibrates, you can let go of Power, but keep holding Volume Up until the TWRP screen appears. Also, the very first thing you should do is hit the Select Language button and choose English, otherwise you're going to have a bad time!
Well, I was not smart and didn't back up first, but I got lucky. Thought I'd bricked it, but the problem was SuperSU. I got the "latest" from the internet, but that one is old. You must use this one: UPDATE-SuperSU-v2.79.zip

Help with fixing app force close

I found an app called package signer from https://forum.xda-developers.com/android/software/tool-package-signer-1-0-t3533073 to sign the zip files in android to fix signature verfication error in some recoveries....
Developer stopped development of that app...
and also that thread is closed...
It signs correctly but one issue is, it can't able to sign zips that are greater than 20mb ......
It force closes when working with large zip files...
It is open source is github....
Sir osm0sis i have seen you are helping in zip signers..
Can you please help....
I hope some developer can fix this and post below.....
Please help by fixing that force close error of signing big zip files......
Thanks in advance...!
Edit:- See https://forum.xda-developers.com/t/...-apk-zip-within-android.3835975/post-81324327 for solution.
Nope, you should use zipsigner.jar from my Complete Shell Zip + Signing thread.
osm0sis said:
Nope, you should use zipsigner.jar from my Complete Shell Zip + Signing thread.
Click to expand...
Click to collapse
Since I dont have pc... i am using that sir...
HemanthJabalpuri said:
Since I dont have pc... i am using that sir...
Click to expand...
Click to collapse
It should work on device too if dexed, I'll add it to my thread and post instructions soon.
Reserved this too
DISCLAIMERS (please read !)
The content seen in this thread is targeted at this specific forum's device, the Realme C12, codenamed RMX2189.
Follow the instructions shown in this thread at your own risks, I will not be held responsible for bricking your device, you did this yourself.
That said, the information will be kept up to date relatively frequently, and should you follow the steps and ask questions below when unsure, everything will be fine!
No files will be directly provided. Do not use pre-created/re-uploaded content. Instead I'll teach you to gather the required files from official websites, and create the other ones yourself.​
ROM (GSI) Recommendations:
Ordered by personal preference:
1) CAOS
2) LOSQ (LineageOS GSI)
3) crDroid
I'm more than open to feedback, suggested changes & improvements!
Prerequisites for most manipulations:
Your phone, well charged if possible
The USB cable used to link your phone to your computer (the one on your charger works just fine)
A computer, with recent ADB & Fastboot (Platform Tools)
Some time, patience, and the ability to read and follow instructions!
Unlock your bootloader (otherwise this thread is useless to you as it's required for rooting as well as installing custom ROMs)
Tutorial:
Step 0 - Great! You're ready to go. Make sure to backup your phone's data before continuing on with this tutorial, as unlocking will make it factory reset (wipe)!
Step 1 - Download and Open In Depth Tool ( Attached With the Guide Down)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2 - Click “Start applying”.
Step 3 - Please read the disclaimer in detail, select the checkbox, and submit your application
Step 4 - The Application Will be checked by realme Servers..(Wait 10 mins)
Step 5 - The unlock tool apk will show the status of the unlock request- Successful
Step 6 - You can now click “Start the in-depth test” and the device will reboot automatically. The following string will display on the screen: fast boot_unlock_verify ok
Step 7 - Now Download and install the fastboot tool on your PC and ready to unlock it.
Step 8 - Now in Fastboot Mode type this command
Code:
fastboot flashing unlock
and Press enter.
Step 9 - On your phone press the Volume Up key to select "UNLOCK THE BOOTLOADER” (or press the Volume Down key if you have changed your mind to select "DO NOT UNLOCK THE BOOTLOADER”). When you click the Volume Up, your phone will reboot and enter the in-depth test mode - all user data on the phone will be erased - I recommend you perform a data backup prior to applying.
Step 10 - Now type
Code:
fastboot reboot
And there you go! Your phone will reboot and you can set it all up again, with the ability to follow the rooting tutorial below, and you can also install GSIs/custom ROMs/recovery!
Rooting with Magisk
Tutorial:
The procedure is the same whether you're on the stock RealmeUI Rom or on a custom GSI (treble) one.
Step 1 - Download the latest Magisk Manager on your phone.
Go to the link above, click the latest MagiskManager-vX.X.X.apk you see in the list to start the download, open the file and install.​
Step 2 - Download the latest Realme Official Rom from Software Update - realme depending on your region.
Step 3 - Get your ROM you downloaded above, it should be a .ozip archive. Add .zip extension to it. Extract it.
Step 4 - You should now get a folder like shown below, and..
Copy the boot.img to your phone's /sdcard/ folder (where the Android, DCIM, Download, and more are present, just drop it in there).
And here's how it shoud look inside your phone's storage in the end.
Step 5 - On your phone, open up Magisk Manager.
Click the Magisk Install button as shown below.
Then Select and Patch a File.
Go look for your boot.img you previously copied to your phone and pick it.
Click Let's go! and wait for Magisk to complete the process!
Step 6 - Link your phone to your PC, and grab the file the Magisk Manager created. It's located in your downloads folder, called magisk_patched.img.
Step 7 - Paste it where your ADB & Fastboot (Platform Tools) are located, along with the vbmeta.img file located in Stock ROM's images folder from earlier, where you grabbed the original boot.img.
You should now have a folder like this with:
adb(.exe)
fastboot(.exe)
magisk_patched.img
vbmeta.img
Extra files from the platform tools
Step 8 - Alright, we're ready to root! Turn off your phone, and get in fastboot mode like we did during the bootloader unlocking (Power + Volume Down).
Step 9 - Link your phone to your PC with the USB cable if not done already.
Step 10 - Shift + Right click in an empty space inside the folder we prepared in Step 7, and click Open Command window here.
Inside the Command window, input the following commands line by line, in order.
Code:
adb reboot bootloader
fastboot devices
And make sure your device shows up, should be a bunch of numbers and letters, a couple spaces, and fastboot.
If nothing does, go back to Step 8 and try again.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
You're done! Your phone will reboot, hopefully, without a hitch! Open up Magisk Manager, and check that it's installed.
That said, you will have issues leaving it like this. You need to hide the fact that your phone is rooted, there's no downside to doing it.
Check out the Passing SafetyNet tutorial further down below, it's quick and easy.
Getting EdXposed (Not recommended unless really needed, requires Magisk)
I very much do not recommend to EdXposed your phone unless you have a very good reason for it. It's a pain to pass SafetyNet, doesn't get updated as often as it could/should and has very niche use cases for which it's worth it.
That said, I do include it here for people who know what they're getting into and want the up-to-date instructions on how to do it.
Tutorial:
This procedure requires to be rooted with Magisk. See the tutorial above.
Step 1 - Inside Magisk Manager, go to the Modules tab (4th icon), click the search button (bottom right) and search Riru.
Step 2 - Install the Riru (Riru - Core) module, Activate it and Reboot.
Step 3 - Install the Riru - EdXposed (YAHFA or SandHook, both work fine) module, Activate it and Reboot.
Step 4 - Download and install the latest EdXposed Manager in the exact same way you did with Magisk Manager.
Step 5 - Open it up, it should say EdXposed Framework is active!
You're done! You should now be able to install EdXposed modules.
That said, you will have issues leaving it like this. You need to hide the fact that your phone is EdXposed.
It's a bit more complicated than hiding Magisk, but it's doable! Check out the Passing SafetyNet tutorial further down below, it's quick and easy.
Passing SafetyNet (Only possible with Magisk. Not with SuperSU on GSI's)
Tutorial:
For Magisk Rooted PhonesEnable Magisk Hide inside Magisk Manager's settings.​For EdXposed PhonesAgain, I highly recommend not EdXposing your phone and sticking to just Magisk if you can help it.
You should also know that this method will show you're passing SafetyNet inside Magisk but it's a pain to do and isn't as well hidden as Magisk alone.
Step 1 - Do the step for Rooted phones listed above if not done already.
Step 2 - In EdXposed Manager, get the HiddenCore Module and activate it.
Step 3 - Now, in the side-menu: Compat List > tick HiddenCore Module.
Step 4 - Then, go to Settings > Framework > Enable "App List mode".
Step 5 - Finally, Applications(Black List) and tick: Android Services Library, Chrome, Google Play services, Google Play Store, Google Services Framework​Reboot and enjoy! You're all set and SafetyNet should pass just fine.
Installing GSI's (Custom ROMs)
Tutorial:
Step 1 - Pick your poison in the Treble Forums!
Check the top of this thread if you want to see my recommendations with links to them.
Step 2 - Download the chosen ROM, A/B Arm64 version (usually nicknamed b), with (g) or without GApps (v), rooted (S) or not (N), that's entirely up to you.
It should be an .img.xz file, extract it and you'll get an .img file.​
You're ready to flash. Make sure to backup your phone's data before continuing on with this tutorial, as wiping it is required for installation!
Step 3 - Put your phone into fastboot mode (Power + Volume Up) and link it to your PC.
Step 4 - Move the .img file you downloaded to your ADB & Fastboot (Platform Tools) folder, and rename it to system.img.
Step 5 - Shift + Right click in an empty space inside the folder, and click Open Command window here.
Inside the Command window, input the following commands line by line, in order.​
Code:
fastboot reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot -w
fastboot reboot
Your phone will now reboot on its own, using the new ROM you picked earlier, set it all up and enjoy!
Relock your bootloader
Tutorial:
Step 0 - Back to stock ROM by flashing it in stock recovery.
Step 1 - Download the unlock tool again to apply to exit the in-depth test.
Step 2 - Click “Apply to exit in-depth test”. You should manual operation enter the Fastboot mode(Press both the Volume up button and the Power button when power is off).
Step 3 - In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
- Enter the command: adb reboot bootloader
- Press “Enter” on your keyboard
- Enter the command: fastboot flashing lock
- Press “Enter” on your keyboard​Step 4 - Press the Volume Up button to select the “Lock bootloader” option (or press the Volume Down button to select “Do not lock bootloader" and keep it unlocked).
Step 5 - Then enter command fastboot reboot. The phone will reboot and exit the in-depth test mode. All user data on the phone will be erased - we recommend you perform a data backup prior to applying.
Frequently Asked Questions (FAQ)
Q: Will unlocking my bootloader void my warranty?
A: No, it will not. Unless you brick your device.
Q: Hey, I rooted/edXposed my phone, and now Netflix won't even open, or doesn't work properly, what's up with that?
A: Well, fortunately, there's an easy fix if you have Magisk. Install the liboemcrypto disabler Magisk module, activate it and reboot.​
Q: I tried unlocking my bootloader but, PC doesn't detect my phone, even though it's in fastboot mode and connected. Help?
A: Here are some things you can try:
- Try another USB port.
- Try another USB cable.
- Install the Realme USB Drivers manually from here.​
Q: Alright, I did a bunch of manipulations but something went wrong, or I'm tired of it, how do I reset everything, etc..
A:
Step 1 - Backup all the data you might have on your phone to restore it after the manipulation!
Step 2 - Download the stock ROM corresponding to your region from Software Update - realme.
Step 3 - Put the stock rom in your mobile Internal Storage or in Memory Card.
Step 4 - Put your device into recovery mode (Turn it off, then Power + Volume Down) and flash that in recovery.
Step 5 - Reboot to stock rom, all good and fresh!​

[GUIDE][ROOT] Install Magisk without Root and Recovery

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
NFO:
This Method does not need Root or Custom Recovery
You must have a Stock Boot Image Dump and you also have to be able to flash the patched Boot Image via Fastboot Mode
Requirements:
• ADB and Fastboot on your PC (for example Tiny ADB & Fastboot) [Thread]
•.Stock boot.img of your Device (extract File from Factory Image)
• Magisk Manager [Thread]
• Internet connection
• Bootloader unlocked [Thread]
• Developer Options > USB Debugging [Thread]
Patching the Stock boot.img:
1. Copy the Stock boot.img to your Phone's internal Storage
2. Install Magisk Manager
3. Launch Magisk Manager App
4. If prompted to install Magisk select "No Thanks"
5. Press Install > Install > Patch Boot Image File and select your Stock boot.img
6. Magisk Manager should begin downloading the Magisk.zip file used for patching
7. Once download is complete Magisk Manager will automatically patch the Boot File
Flashing the patched boot.img:
1. Install Tiny ADB & Fastboot
2. Connect the Phone to the PC via USB Cord
3. Copy the patched_boot.img from your Phone's internal Storage to C:\Program Files (x86)\Tiny ADB and Fastboot\
4. Unlock the Bootloader
5. Enable USB Debugging
6. Open Tiny ADB and Fastboot
7. Boot into Fastboot Mode, type:
Code:
adb reboot bootloader
8. Flash the patched_boot.img, type:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
9. Open Magisk Manager and verify Root
10. Enjoy
K3V1991 said:
​
NFO:
This Method does not need Root or Custom Recovery
You must have a Stock Boot Image Dump and you also have to be able to flash the patched Boot Image via Fastboot Mode
Requirements:
1. ADB and Fastboot on your PC (for example Minimal ADB and Fastboot) [Thread]
2. Stock boot.img of your Device (extract File from Factory Image)
3. Magisk Manager [Thread]
4. Internet connection
5. Bootloader unlocked [Thread]
6. Developer Options > USB Debugging [Thread]
Patching the Stock boot.img:
1. Copy the Stock boot.img to your Phone's internal Storage
2. Install Magisk Manager
3. Launch Magisk Manager App
4. If prompted to install Magisk select "No Thanks"
5. Press Install > Install > Patch Boot Image File and select your Stock boot.img
6. Magisk Manager should begin downloading the Magisk.zip file used for patching
7. Once download is complete Magisk Manager will automatically patch the Boot File
Flashing the patched boot.img:
1. Install Minimal ADB and Fastboot
2. Connect the Phone to the PC via USB Cord
3. Copy the patched_boot.img from your Phone's internal Storage to C:\Program Files (x86)\Minimal ADB and Fastboot\
4. Unlock the Bootloader
5. Enable USB Debugging
6. Open Minimal ADB and Fastboot
7. Boot into Fastboot Mode, type:
Code:
adb reboot bootloader
7. Flash the patched_boot.img
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
8. Open Magisk Manager and verify Root
9. Enjoy
___
Click to expand...
Click to collapse
I know I can try this method and see what happens and then report back if needed, but I don't think that this is a thing safe enough to test, so I'll ask before I try: is this for any LG G6 version? Does it work on the H870S (Dual SIMs version)?
P.S: I don't think that this version even has the possibility to unlock the bootloader
Also, isn't a phone that has an unlockable bootloader also rootable?
Mohammad Jebreeni said:
I know I can try this method and see what happens and then report back if needed, but I don't think that this is a thing safe enough to test, so I'll ask before I try: is this for any LG G6 version? Does it work on the H870S (Dual SIMs version)?
P.S: I don't think that this version even has the possibility to unlock the bootloader
Also, isn't a phone that has an unlockable bootloader also rootable?
Click to expand...
Click to collapse
Only for H870, H872 & US997
Please file Stock boot.img?
My device: G6 H872 _H87220d
K3V1991 said:
Only for H870, H872 & US997
Click to expand...
Click to collapse
By saying H870, that means any H870 (like one from Central America) or just the same EU H870 that is listed on the LG Developers page?
CAlbertSM said:
By saying H870, that means any H870 (like one from Central America) or just the same EU H870 that is listed on the LG Developers page?
Click to expand...
Click to collapse
The unlockable G6's
Does this wipe the phone?
EndlessAbyss said:
Does this wipe the phone?
Click to expand...
Click to collapse
Fastboot OEM Unlock will Factory Reset the Phone
K3V1991 said:
Only for H870, H872 & US997
Click to expand...
Click to collapse
Will this work on T-Mobile version of LG G6(H872 TM)? Are you sure it will not do any damage to the phone like hard brick?
Imran5320xm said:
Will this work on T-Mobile version of LG G6(H872 TM)? Are you sure it will not do any damage to the phone like hard brick?
Click to expand...
Click to collapse
This does not work on H872 period.
You will get
writing 'boot'...
FAILED (remote: unknown command)
Does this work on the H871?
Hi, i did exactly what you explain in your post on my h870 with V30b-EUR and all worked fine. My phone is now rooted an i'm very happy. Thank you very much for your wonderfull work
leonlelion said:
Hi, i did exactly what you explain in your post on my h870 with V30b-EUR and all worked fine. My phone is now rooted an i'm very happy. Thank you very much for your wonderfull work
Click to expand...
Click to collapse
Could you tell me how did you get the boot.img file? @leonlelion
--Edit--
Nevermind I found it and rooted my device (H870-V30B-EUR) succesfully. If anyone needs it it's inside the ZIP file: https://forum.xda-developers.com/lg-g6/development/rom-lg-h870-eu-30b-rom-t4007979
leonlelion said:
Hi, i did exactly what you explain in your post on my h870 with V30b-EUR and all worked fine. My phone is now rooted an i'm very happy. Thank you very much for your wonderfull work
Click to expand...
Click to collapse
Me too !! :good:
The simplest, best method!
The simplest, best method! The boot.img I got it from this archive: https://drive.google.com/file/d/1Xxoa2KdcoPTPriZL1IZh056J9rQ7NFiV/view?usp=sharing . My phone: H870 with V30b.
Does this work with H872?
I am interested if this will work on my h870s since i am one of the lucky ones who got 'official' bootloader unlock key, and my bootloader is unlocked now. And if it does when i flash this will i be able to safely modify system files.
Thanks a lot! root easy and fast, I used the boot.img file above, fortunately I had an unlocked bootloader
Would anyone know where to find the boot.img for the US997?
Do you have a modem i could just flash with this h873?

Install su without TWRP via ADB

Hi all,
At my work we are using an android tablet and I need to install root on it. The tablet is a SkyDroid H16. The weird thing is that "adb root" works fine and I can remount /system and add files, but apps cannot see that there is root.
How can I install su and use it.
There is no TWRP for it and the stock image is also not public.
Senna-chan said:
Hi all,
At my work we are using an android tablet and I need to install root on it. The tablet is a SkyDroid H16. The weird thing is that "adb root" works fine and I can remount /system and add files, but apps cannot see that there is root.
How can I install su and use it.
There is no TWRP for it and the stock image is also not public.
Click to expand...
Click to collapse
Root Android Devices without TWRP Recovery​To root your device without TWRP Recovery, you need to perform two steps. Firstly, the device needs to be booted using the patched boot image file. In the next step, this boot image file will be permanently flashed using the Magisk Manager app. Don’t forget to have a look at the ‘Prerequisites’ section below, before beginning with the process. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.
Prerequisites​
Download and install the Magisk Manager APK file on your device: Magisk App [from version 22 onwards, it is known as Magisk App and has both the Magisk ZIP and Manager APK file bundled together].
Next up, check if your device has ramdisk or not. For that, launch the Magisk app and refer to the section under Magisk, if it says YES, then you are good to proceed ahead (see below image). On the other hand, if it says NO, then you will have to head over to our alternative guide: Install Magisk in Recovery and Root Android [No Ramdisk].
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The bootloader of your device should be unlocked. Have a look at our guide on how to do so.
Enable the ‘USB Debugging’ option. Go to ‘Settings’ -> ‘About Phone -> Tap on Build Number 7 times -> Go back to Settings -> Developer Options -> Toggle on the USB Debugging’ switch.
Although rooting is going to wipe your data, still, it is recommended to make a complete backup of all your data.
Keep your device appropriately charged, at least to a minimum recommended level of 50%
Install ADB and Fastboot Tool for entering Fastboot commands.
Also, download and install the USB Drivers for your device. This helps in successfully connecting your device to the PC.
STEP 1: Get Stock Boot.img File from Stock ROM​
To begin with, you will have to extract the stock boot.img file. And as opposed to earlier times, the process is a little bit more complicated nowadays. You cannot simply extract the firmware and get the required partition files (such as vbmeta.img, system.img, boot.img, etc). The reason is that many OEMs packs the ROM’s IMG files inside an encrypted package. For example, OnePlus has these files inside payload.bin, Realme, and Oppo have their files inside the OZIP format, and so on. In that case, you may refer to our below guides to get the stock boot.img file:
Now that you have got hold of the stock boot image file, it’s time to patch it via Magisk and flash it via Fastboot Commands. We have listed the steps for both the older as well as the newer build of Magisk Manager. As far as the difference between them goes, it’s just some UI tweaks here and there, the underlying functionality remains the same. The below update is only for devices running Android 11. If your device isn’t running that version, then you may directly head on to STEP 2A/2B.
UPDATE 1 [FOR ANDROID 11 USERS ONLY]: Quite a few Android 11 users are facing issues while patching the stock boot.img file via Magisk manager. Well, I have found the fix to this issue, please refer to our detailed guide on the same: Fix Magisk patched boot.img issue while Rooting Android 11. If you wish to save a click, then here’s the explanation in short:
You have to install the Magisk Canary build instead of the stable and then change the update channel to Canary from within the app itself. Once you have done the said change, you may then proceed with the below steps to patch the stock boot image file using Magisk and flash it via Fastboot commands. [END OF UPDATE 1]
STEP 2A- Patch the Stock Boot Image File using Older Magisk​
Download the stock firmware for your device.
Extract the boot.img file from it.
Transfer it to the device’s internal storage.
Install the Magisk Manager App on your device.
Open it. Tap on the first ‘Install‘ button, next to Magisk status.
In the next menu, again chose ‘Install‘.
Now select ‘Select and Patch a File‘.
Navigate to internal storage and select the stock boot.img file that you extracted earlier.
Let Magisk do the patching process. When it’s done, copy this patched boot.img file, named as magisk_patched.img, from your device (will be present under Internal Storage > Downloads) to PC where you have installed the ADB and Fastboot Tools (inside the platform-tools folder).
How to Update Magisk ZIP and Magisk Manager (without TWRP)
Disable DM-Verity or Android Verified Boot without TWRP
Fix Magisk Module Bootloop without TWRP Recovery
How to Root Android Devices Without TWRP Recovery
STEP 2B: Patch Stock Boot Image File using Newer Magisk​
Launch the Magisk Manager app on your Pixel device.
Then tap on the Install button situated next to Magisk.
From the Method section, choose Select and Patch a file.
Browse to the extracted boot.img file and select it.
Then tap on the Let’s Go option situated at the top right.
Magisk will now load the boot.img file and will patch it accordingly. Once that is done, you would get the Download Complete message.
The patched boot image file will be saved in Internal Storage > Downloads. The name of the file will be magisk_patched.img.
Now that you have patched the stock boot.img file, it’s time to flash it onto your device and hence obtain root without TWRP. There are two different methods through which you could do this. This patched boot.img file could either be flashed via Fastboot or through Magisk. It is highly recommended that you proceed with the Fastboot Method. Only in case, if you face any issues, then you should proceed with the Magisk Method. The reason being the fact via the Magisk method, we will be using the DIrect Install feature, which seems to be absent in most devices. Hence to avoid any confusion, you should try the Fastboot Method. If you face any error, then only proceed with the Magisk method to root your Android device without TWRP.
STEP 3A- Install the Patched Boot Image using Fastboot​
Connect the device to the PC via USB Cable.
Now transfer the patched boot file from your device to the platform-tools folder on your PC.
Inside the same folder, right-click on an empty area while pressing the ‘Shift’ key.
Select the option ‘Open PowerShell window here’.
Or you could also head over to the platform-tools folder on your PC, type in CMD in the address bar, and hit Enter. This will launch the Command Prompt.
Type in the below code to make sure the device is successfully connected (an alpha-numeric code suggests successful connection):adb devices
Now type in the below code to boot your device to fastboot/bootloader mode:adb reboot bootloader
Next, type the below code to flash the patched boot image file:fastboot flash boot magisk_patched.img
If you get the fastboot: error: Couldn’t parse partition size ‘0x’ issue, as some users have mentioned in the comments, then please refer to our detailed guide: How to Fix fastboot: error: Couldn’t parse partition size ‘0x’.
For devices with an A/B partition, you need to flash the patched boot file to both partitions. Type the below code for the same:fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Now you may Reboot the device by typing the below code:fastboot reboot
If your device is rooted, then you should stop here only. However, if the Fastboot Command method didn’t work out in your case, then only proceed with the next method to install patched boot.img.
If this post is good please thumbs up.
@Senna-chan
Because adb root & adb remount works here is a code example that adds su
Code:
adb root & adb remount & adb disable-verify & adb shell "setenforce 0"
adb push su /system/bin/
adb push superuser.apk /system/app/
adb reboot
jwoegerbauer said:
@Senna-chan
Because adb root & adb remount works here is a code example that adds su
Code:
adb root & adb remount & adb disable-verify & adb shell "setenforce 0"
adb push su /system/bin/
adb push superuser.apk /system/app/
adb reboot
Click to expand...
Click to collapse
So I tried this with a few version of supersu but it didn't work. I tried version 2.76 2.82 and 2.79 and it didn't work. Everytime I get the error no su binary found. The version I uploaded was the arm64 version since I have a ARMv8.
What could be wrong?
Thats great in all but after I flash the boot.img from any version of magisk from v22 onward and the latest canary, it doesn't give me magisk app when i boot back into the os.

Development [ROM][12.1][OFFICIAL] ArrowOS 12.1 for OnePlus 9R [OOS12]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS for OnePlus 9R (lemonades)​ABOUT​ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?​Almost everything.
Bugs: You tell me.
DOWNLOADS​Click here to Download
Tip: Select OEM -> Device, choose Arrow version, choose the build type: "GAPPS" or "VANILLA" to download.
INSTALLACTION​- Please note: Be sure that your phone is already OOS12 based !!!
- Download Recovery here
- Download script here
- Download ROM zip file.
- Reboot phone to Fastboot mode
Code: fastboot boot recovery.img
Install in ADB -> copy-partitions-20220613-signed.zip -> Advanced -> reboot to bootloader
fastboot boot recovery.img -> Factery Reset -> Install in ADB -> ROM.zip
- Reboot
INSTRUCTIONS​Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/ArrowOS-Devices/android_kernel_oneplus_sm8250
The download link seems broken. Also what firmware is ROM based on OOS 11 or 12 ?
With the kebab version should also work
ArrowOS - Downloads
Thanks for your work. Also I want to ask, should I use oos11 or oos12 firmware?
exthomeboy said:
With the kebab version should also work
ArrowOS - Downloads
Click to expand...
Click to collapse
I tried it, but it doesn't work.
slatera18 said:
The download link seems broken. Also what firmware is ROM based on OOS 11 or 12 ?
View attachment 5670887
Click to expand...
Click to collapse
Now it's possible, OOS 11
hiper25 said:
Now it's possible, OOS 11
Click to expand...
Click to collapse
Is also a version only for the 9R. Almost every other rom is flashable on the 8T and 9R, but not here
exthomeboy said:
Is also a version only for the 9R. Almost every other rom is flashable on the 8T and 9R, but not here
Click to expand...
Click to collapse
On my test 9R can't flash 8T ROM
They have to have to separate
hiper25 said:
Now it's possible, OOS 11
Click to expand...
Click to collapse
Yes able to download.
But there is an issue with mic volume when talking on calls. The other person hears feeble voice of me on call.
hiper25 said:
fastboot boot recovery.img
Click to expand...
Click to collapse
Isn't it the code supposed to be fastboot flash recovery <recovery_filename>.img
hiper25 said:
Reboot phone to Fastboot mode
Code: fastboot boot recovery.img
Install in ADB -> copy-partitions-20220613-signed.zip -> Advanced -> reboot to bootloader
fastboot boot recovery.img -> Factery Reset -> Install in ADB -> ROM.zip
- Reboot
Click to expand...
Click to collapse
I'm a newbie here, the last time I have installed a custom ROM on Asus phone over five years ago with lineage os.
Will I be successful if I follow below instructions, as your instructions above are short and suited for pros.
search
Install LineageOS on kebab​keyboard_arrow_left Back to the overview
warning
WARNING: These instructions only work if you follow every section and step precisely.
Do not continue after something fails!
Basic requirements​
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
Make sure that your model is actually listed in the “Supported models” section here (exact match required!)
warning
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 12, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
Unlocking the bootloader​info_outline
NOTE: The steps below only need to be run once per device.
warning
WARNING: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from LineageOS once installed.
Enable OEM unlock in the Developer options under device Settings, if present.
Connect the device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Up + Volume Down + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable and port!
Now type the following command to unlock the bootloader:
fastboot oem unlock
info_outline
NOTE: At this point the device may display on-screen prompts which will require interaction to continue the process of unlocking the bootloader. Please take whatever actions the device asks you to to proceed.
If the device doesn’t automatically reboot, reboot it. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.
Flashing the dtbo partition​warning
WARNING: This platform requires the dtbo partition to be flashed for recovery to work properly, the process to do so is described below.
Download dtbo file from here. Download the file named dtbo.img from the directory named with the latest date.
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Up + Volume Down + Power.
Flash the downloaded image file to your device by typing (replace <dtbo> with the actual filename!):
fastboot flash dtbo <dtbo>.img
Installing a custom recovery using fastboot​
Download Lineage Recovery. Simply download the latest recovery file, named something like lineage-19.1-20220825-recovery-kebab.img.
Connect your device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Up + Volume Down + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable and port!
check
TIP: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ..., fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Flash recovery onto your device (replace <recovery_filename> with the actual filename!):
fastboot flash recovery <recovery_filename>.img
Now reboot into recovery to verify the installation.
Use the menu to navigate to and to select the Recovery option.
Ensuring all firmware partitions are consistent​info_outline
NOTE: The steps below only need to be run once per device.
In some cases, the inactive slot can be unpopulated or contain much older firmware than the active slot, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of the active slot to the inactive slot.
To do this, sideload the copy-partitions-20220613-signed.zip package by doing the following:
Download the copy-partitions-20220613-signed.zip file from here. It should have a MD5 sum of 79f2f860830f023b7030c29bfbea7737 or a SHA-256 sum of 92f03b54dc029e9ca2d68858c14b649974838d73fdb006f9a07a503f2eddd2cd.
Sideload the copy-partitions-20220613-signed.zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload copy-partitions-20220613-signed.zip
info_outline
NOTE: The copy-partitions script was created by LineageOS developer erfanoabdi and filipepferraz
Now reboot to recovery by tapping “Advanced”, then “Reboot to recovery”.
Installing LineageOS from recovery​
Download the LineageOS installation package that you would like to install or build the package yourself.
(Optionally): If you want to install an application package add-on such as Google Apps (use the arm64 architecture), please read and follow the instructions on Google Apps page
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Down + Power.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
check
TIP: Normally, adb will report Total xfer: 1.00x, but in some cases, even if the process succeeds the output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.
(Optionally): If you want to install any add-ons, click Advanced, then Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip those packages in sequence.
info_outline
NOTE: Add-ons aren’t signed with LineageOS’s official key, and therefore when they are sideloaded, Lineage Recovery will present a screen that says Signature verification failed, this is expected, please click Continue.
info_outline
NOTE: If you want the Google Apps add-on on your device, you must follow this step before booting into LineageOS for the first time!
Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.
hiper25 said:
INSTALLACTION​- Please note: Be sure that your phone is already OOS12 based !!!
- Download Recovery here
- Download script here
- Download ROM zip file.
- Reboot phone to Fastboot mode
Code: fastboot boot recovery.img
Install in ADB -> copy-partitions-20220613-signed.zip -> Advanced -> reboot to bootloader
fastboot boot recovery.img -> Factery Reset -> Install in ADB -> ROM.zip
- Reboot
Click to expand...
Click to collapse
Newbie here.
Need instructions from unlocking the bootloader.
It took almost four hours to figure out and use MSM tool
Please do give me instructions from unlocking the bootloader

Categories

Resources