Develop Bugs

ASUS ZenPad Z8 (ZT581KL) (P008) (Verizon) - Firmware

I found some firmware files for the Asus Zenpad Z8 ZT581KL for Verizon. Neither Asus or Verizon host any firmware for this device, despite having other similar device firmware available (like the ZT500KL, etc), which sucks.
VZW_ZT581KL_V3.4.16_all_user_M101901_16.0.0_160519.zip
ASUS Factory VZW_ZT581KL_V5.4.1_all_user_M101901_16.0.0_170202 androidhost.ru.zip
ZT581KL_T3.3.8_pre_burn_image_20160516.zip
ZT581KL_Z581KL_EMERGENCY_DLOAD.7z
ZT581KL_FUSE_Security_Keybox_160728.rar
Z581KL_initrd_diff.zip
ASUS.Flash.Tool.v1.0.0.45.zip
Running a stock, factory reset device, I was able to flash VZW_ZT581KL_V3.4.16_all_user_M101901_16.0.0_160519.zip using Asus Flash Tool 1.0.0.45, which successfully downgraded Tablet from V3.4.23 to V3.4.16.
I tried flashing ZT581KL_T3.3.8_pre_burn_image_20160516.zip but it did not work and error-ed out with no brick or anything. Usually the firmware is in a .raw format so you can flash either via zip file which has raw file in root folder of archive, or via the raw file itself. I tried both and was not successful. For some reason this archive had a .bin file instead of a .raw file. I tried renaming them but still didn't work. However, I was able to extract the .bin to find the firmware files inside just like the other version firmwares (that were in raw). One thing I have not tried yet, is to try manually flashing the individual firmware files from the extracted bin, and see if that works--or if someone else with this tablet wants to try, here are the files. If successful, it might lower kernel version down more to allow root exploits to root device.
I have not tried flashing V5.4.1, but I'm confident it will work. I do not know if via the Asus Flash Tool/Asus Tablet will allow doing a flash to V5.4.1 and downgrade back down to V3.4.16, but just did V.3.4.23 (stock orig fw already on device) to V.3.4.16 and it worked. I did receive an OTA to upgrade to V3.4.18 (or was it V.3.4.21, I can't remember) and took the upgrade (then flashed back to V.3.4.16), so it appears that when doing an OTA it will "leap-frog" to the next higher version release until you are on the newest build, so the first OTA you get won't do a direct upgrade from V3.4.16- to V5.4.1 or V5.4.5, but will upgrade it in an incremental way, via the next higher version release.
Hopefully someone can try to root their tablet if any of these files are of any help. I might work up courage to try 3.38 again via manual fastboot, but if you do it and succeed, I would love to hear about it.
The other files hosted ZT581KL_Z581KL_EMERGENCY_DLOAD.7z and ZT581KL_FUSE_Security_Keybox_160728.rar have to do with re-flashing the Qualcomm Snapdragon SoC (un-bricking), and the other one something to do with clearing/setting FUSE when the phone leaves factory or something, I'm not sure. Hopefully they can be of some use to someone to unlock this device. It would be nice. So here u go.
https://www.androidfilehost.com/?w=files&flid=289525 - link to ASUS_ZenPad_Z8_ZT581KL_P008_Verizon files

Has anyone tried flashing 'ZT581KL_T3.3.8_pre_burn_image_20160516' yet? Just wondering if it was successful; I haven't tried it yet.

smokejumper76 said:
Has anyone tried flashing 'ZT581KL_T3.3.8_pre_burn_image_20160516' yet? Just wondering if it was successful; I haven't tried it yet.
Click to expand...
Click to collapse
can you tell me how to extract the .raw from .bin, I will try to flash the device.

fuyangui said:
can you tell me how to extract the .raw from .bin, I will try to flash the device.
Click to expand...
Click to collapse
I used 7zip to extract the firmware from the archive.. Open 'ZT581KL_T3.3.8_pre_burn_image_20160516.zip' with 7zip. It should come up with a folder named 'ZT581KL_T3.3.8_pre_burn_image_20160516'. Go in that folder. There will then be a file shown called 'userdata.bin'. In 7zip, if you right click that file, then select 'Open Inside', it should open inside the .bin file and show the firmware files. From there, you can extract them somewhere. Hopefully, you can try to apply each .img file separately (fastboot), one at a time, and see if it works. Thank you!

Sorry to resurrect this old thread but I might have some info that will help others.
First off thanks for the OP for the download links as I cannot find the OEM ROMS anywhere for this device.
Second here are some more instructions that you may need if you are having issues with this device.
Use ASUS FLash Tool v1.0.0.45, it has the device model that you need and was the one that worked for me. Then download ASUS Factory VZW_ZT581KL_V5.4.1_all_user_M101901_16.0.0_170202 androidhost.ru.zip from the link the OP posted, it should be the first file, then this is the step that I missed and took forever to figure out. You have to open that zip file and extract the .raw file, so you should have a file called ZT581KL_all_VZW_user_V5.4.1.raw. That is the file that you need to select in the Asus Flash Tool by clicking the little box with a down arrow inside it, then boot your tablet into Fastboot (Hold down the Power and Volume Down buttons) then once in fastboot, make sure you select the right model for this tablet it should be, ZT581KL, then I left Wipe Data as no, then connect your tablet to your computer with a USB cable, and you should see your Serial Number and a round icon under the State column. Then once that is all correct click the Start button, you may get an error about some FPS thing that can't be downloaded or something just hit OK, then you should see under the Description column that it's flashing the ROM, wait for a while and you should then have a "Flash Image Successfully (The serial number for your device will show here)" under the description and your tablet will reboot.
My tablet was originally on v5.4.5, this ROM will take you back to v5.4.1 but then through the tablet settings you can do an upgrade to v5.4.4 then do another one and it will be at v5.4.5 then you are all set.
So the issue I was having with the tablet was after a factory reset it would freeze at the setup screen and not let me continue, it took me forever to find out how to get it fixed and the instructions above worked for me, so if anyone else is having similar issues then hopefully this will help. I literally spent days and searched through about 70 forums to try and find a fix for it, I even reached to Asus for help, which they basically told me I had to pay to send it in and have it fixed, I was just about to give up when I came upon this thread and the OP's download links, so thanks again smokejumper76. If anyone has any questions about my instructions feel free to reply/comment.
Thanks!

Downgrade success
I used the files provided by OP and was able to successfully flash from 5.4.1 to 3.4.16. I got this tablet from a friend a few years back that he acquired from his work when it went out of business. It has the frp lock on it and im looking at the few available options. So, since this tablet had been sitting for two years. Its Guinea pig time. I'll flash the 3.3.8 and check back. It seems you can go forward or backward in so versions with the flash tool. So I'm not too worried about brick. If I can just get usb debugging on I'll be gold. Possible exploits if it runs.

Well. The 3.3.8 is not packaged properly for flashing. And that 600mb file expands to 9gb. There is a file "system.img" inside that's roughly the right size as the system and has the correct file structure. I have a friend who is going to help me repack that rom correctly for flashing. Meanwhile I am going to look into the 3.4.16 rom and see if I can't set usb debug to on and flash the modded image. From there I should be able to sideload su. I'll report back.

mofugggz said:
Well. The 3.3.8 is not packaged properly for flashing. And that 600mb file expands to 9gb. There is a file "system.img" inside that's roughly the right size as the system and has the correct file structure. I have a friend who is going to help me repack that rom correctly for flashing. Meanwhile I am going to look into the 3.4.16 rom and see if I can't set usb debug to on and flash the modded image. From there I should be able to sideload su. I'll report back.
Click to expand...
Click to collapse
Any update? Thank you for your efforts!

smokejumper76 said:
Any update? Thank you for your efforts!
Click to expand...
Click to collapse
I have the same tablet as well. Root would be great, any chance of unlocking the BL?

klister said:
I have the same tablet as well. Root would be great, any chance of unlocking the BL?
Click to expand...
Click to collapse
hi
any advance with this?
Enviado desde mi P008 mediante Tapatalk

WHat is the password to the files

I used the emergency download file to unbrick the Japanese version of z581kl. However, maybe the partition structure is different, when I try to write to the system partition, it says that there is no partition. What should i do? I'm sorry for my bad English.

allisondanielle said:
WHat is the password to the files
Click to expand...
Click to collapse
https://www.asusflashtool.com/ - Description Page with Password
Unzip Password: asusflashtool.com

I installed ZT581KL_T3.3.8_pre_burn_image_20160516.zip on my z581kl.
That resulted in Android 6.0 AOSP working!
There is a bug that screen rotation is not possible, but everything else is fine.
There is a bug that the screen cannot be rotated, but other than that, everything is fine. After installing TWRP, you need to mount /system and the location of system.img, and then execute the following command from the TWRP terminal.
mkdir new-system
mount system.img new-system
cp -a -R -p new-system/* /system
Translated with www.DeepL.com/Translator (free version)
{
"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"
}

清水侑磨 said:
I installed ZT581KL_T3.3.8_pre_burn_image_20160516.zip on my z581kl.
That resulted in Android 6.0 AOSP working!
There is a bug that screen rotation is not possible, but everything else is fine.
There is a bug that the screen cannot be rotated, but other than that, everything is fine. After installing TWRP, you need to mount /system and the location of system.img, and then execute the following command from the TWRP terminal.
mkdir new-system
mount system.img new-system
cp -a -R -p new-system/* /system
Translated with www.DeepL.com/Translator (free version)View attachment 5251235View attachment 5251237View attachment 5251239
Click to expand...
Click to collapse
I flashed the zt581kl image using EDL mode as described in this blog because the partition structure of the zt581kl is different from that of the zt581kl.
z581klでEDLモードに入る方法
xxxxx
itgameinfo.blogspot.com

Hi. New to the forum. I’m looking to downgrade my asus zt581kl so that I can root. Can someone show me the exactly step by step to downgrade my table? The above replies are a bit confusing to follow.

Tmupt said:
Hi. New to the forum. I’m looking to downgrade my asus zt581kl so that I can root. Can someone show me the exactly step by step to downgrade my table? The above replies are a bit confusing to follow.
Click to expand...
Click to collapse
Maybe start here:
https://www.getdroidtips.com/v5-4-1-nougat-verizon-asus-zenpad-z8/

I've been messing around with some of the files, and I was able to brick and unbrick the device following the firehose SOP PDF instructions. It basically flashes a barebones boot w/o any OS, and you have to flash a complete firmware to it to restore it back.
I was also able to install TWRP but it showed 0 space avail, I think because I didn't wipe it. I'll play with that later.
Used these links (use google translate)
z581klでEDLモードに入る方法
xxxxx
itgameinfo.blogspot.com
zenpad 3 8.0に簡単にTWRPを導入する+fastbootの裏技
xxxxx
itgameinfo.blogspot.com
I need to ask @清水侑磨 about how to flash ZT581KL_T3.3.8_pre_burn_image_20160516.zip. I think the userdata.bin file is a NAND dump created by Chinese Miracle 2 / Infinity Box but I'm having problems getting it to read the partitions. I was able to get the tablet in EDL mode, so I'm not sure what I'm doing wrong.

Anyone have a QPST .QCN file for ZT581KL for this device? Flashing 3.3.8 from that preburn file will nuke your IMEI. Mine got changed to all 1s and lost provisioning connectability w/ carrier. in fastboot/adb, so I need to restore it. If anyone could make a QCN (with your IMEI removed of course) so I can do that I would be most appreciative.

smokejumper76 said:
I've been messing around with some of the files, and I was able to brick and unbrick the device following the firehose SOP PDF instructions. It basically flashes a barebones boot w/o any OS, and you have to flash a complete firmware to it to restore it back.
I was also able to install TWRP but it showed 0 space avail, I think because I didn't wipe it. I'll play with that later.
Used these links (use google translate)
z581klでEDLモードに入る方法
xxxxx
itgameinfo.blogspot.com
zenpad 3 8.0に簡単にTWRPを導入する+fastbootの裏技
xxxxx
itgameinfo.blogspot.com
I need to ask @清水侑磨 about how to flash ZT581KL_T3.3.8_pre_burn_image_20160516.zip. I think the userdata.bin file is a NAND dump created by Chinese Miracle 2 / Infinity Box but I'm having problems getting it to read the partitions. I was able to get the tablet in EDL mode, so I'm not sure what I'm doing wrong.
Click to expand...
Click to collapse
Sorry for the late reply.
To boot AOSP, instead of burning the system.img from edl or fastboot, use adb.
The method is as follows
1、Start TWRP.
2、Connect your PC to USB.
3、Go to the directory where system.img is located, and press
adb push system.img /sdcard/
4、Enter the shell
adb shell
5、Mount system.img.
mkdir new-system
mount system.img new-system
6、Copy the contents of the mounted system.img to the system partition.
cp -a -R -p new-system/* /system
(If this fails, check that the system partition is mounted. If the system partition is mounted but you cannot write to it, format the system partition.)
7、After rebooting, you should see an Android message
Translated with www.DeepL.com/Translator (free version)

[GUIDE] 8.2.3 + Magisk root + MagiskHide + TWRP

Based on the work done in https://forum.xda-developers.com/t/how-to-root-and-install-magisk-on-nstv-2019-pro-v8-2-0.4189567/
User friendly guide written for Windows. Bash script for Linux flashing edited as well, but guide is focused on Windows users.
Enhanced upscaling is confirmed to work, have not been able to confirm AI upscaling (Unsupported content). Dolby Vision unconfirmed as I do not yet have a TV that supports it. If someone can verify if this works or not I will update this post accordingly.
Prerequisites:
USB-A male to USB-A male cable.
USB mouse.
USB drivers: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Android SDK: https://developer.android.com/studio/releases/platform-tools
Premade archive: https://drive.google.com/file/d/1XDzQyWviwVbjxNRsWJ8pG-HPSKW-Kzyl/view?usp=sharing
Unlocking the bootloader:
Go into Settings > Device Preferences > About.
Select "Build" several times until "You are now a developer!".
Go into Settings > Device Preferences > Developer options.
Activate USB debugging.
Connect one end of your USB-A to USB-A cable into the port furthest away from the HDMI on your SHIELD TV and the other into your computer.
Open a command shell (command prompt, powershell, bash, etc) on your computer.
Navigate to where you extracted the Android SDK.
Run command:
adb devices
Confirm that your device appears in the list of devices. If not this may be due to:
USB cable not connected properly. Check cable.
Device not recognized. Reinstall drivers/restart computer. Generic Android USB drivers may work if NVIDIA doesn't.
Run command:
adb reboot bootloader
Wait for fastboot to start.
Run command:
fastboot devices
Confirm that your device appears in the list of devices. If not see above reasons.
Run command:
fastboot oem unlock
Flashing:
On your computer navigate to where you have extracted the archive from the post.
Run command:
flash-all.bat
If all goes well you should be rebooted into TWRP recovery once the procedure is done.
Connect your USB mouse to the USB port closest to the HDMI port on your SHIELD TV.
Slide to unlock.
Go into Mount.
Select "Enable MTP".
Move "Magisk-v23.0.zip" from the downloaded archive to your SHIELD TV.
Select "Disable MTP".
Go into Install.
Select "Magisk-v23.0.zip" and install it.
Go into Reboot.
Select "System".
Getting Magiskhide to work:
Install Termux from Google Play.
Open Termux and run:
su
cat >/data/post-fs-data.d/bootfix-post.sh
resetprop ro.boot.verifiedbootstate orange
Press Ctrl+d.
Run:
chmod +x /data/post-fs-data.d/bootfix-post.sh
cat >/data/service.d/bootfix-service.sh
resetprop ro.boot.verifiedbootstate green
Press Ctrl+d.
Run:
chmod +x /data/service.d/bootfix-service.sh
Open Magisk (Settings > Apps > See all apps > Magisk > Open)
Select the shield icon on the bottom bar.
Enable MagiskHide
Reboot system
ALL DONE!
Sources of the premade archive contents are the following:
Android SDK: https://developer.android.com/studio/releases/platform-tools (fastboot)
The following Shield ROMs from https://developer.nvidia.com/gameworksdownload#?search=2019&tx=$additional,shield:
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.1.0 (vbmeta_skip.img)
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.2.0 (mdarcy.dtb.img)
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.2.3
Latest TWRP recovery from https://twrp.me/nvidia/nvidiashieldandroidtv2019.html (recovery.img)
Latest Magisk from https://github.com/topjohnwu/Magisk/releases

reboot to recovery command fails with error and doesnt reboot to twrp. manually booting twrp from fastboot via fastboot boot recovery.img works

can someone explain the "MagiskHide" section of the guide? i dont have those .sh files present in /data/ . Should i just create them with the resetprop commands as the content? i just dont see where you even got those from

{
"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"
}
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes

Can this work on the 2017 model?

Is this the most updated guide also for the magisk hide section whats the easiest way to copy and paste this all in terminal .

albinoman887 said:
View attachment 5402781
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes
Click to expand...
Click to collapse
Did you get around to make that guide?
Im struggling getting around the cts check.

albinoman887 said:
View attachment 5402781
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes
Click to expand...
Click to collapse
Did you get around to make that guide?
Im struggling getting around the cts check.

bolme123 said:
Did you get around to make that guide?
Im struggling getting around the cts check.
Click to expand...
Click to collapse
Ahh crap... I'll be totally honest I completely forgot . I'll get that done by the time I go to bed today. . to be honest though I think what might have done it was I changed my device fingerprint using MagiskPropsConfig module and chose the one for sheid that's included with your IPTV service ... Other than that I just made sure there was no like things exposed that didn't need to be and removed

albinoman887 said:
Ahh crap... I'll be totally honest I completely forgot . I'll get that done by the time I go to bed today. . to be honest though I think what might have done it was I changed my device fingerprint using MagiskPropsConfig module and chose the one for sheid that's included with your IPTV service ... Other than that I just made sure there was no like things exposed that didn't need to be and removed
Click to expand...
Click to collapse
Thank you man, you nudged me in the right direction.
I was able to successfully pass the ctsCheck, and i accumulated new knowledge, thanks man!
Have a blessed day.
Before i go along with my day, did you have any success with LSPosed?
I''m gonna check now if i'm able to disable the SECURE_FLAG without tripping the SafetyNet.

bolme123 said:
Thank you man, you nudged me in the right direction.
I was able to successfully pass the ctsCheck, and i accumulated new knowledge, thanks man!
Have a blessed day.
Before i go along with my day, did you have any success with LSPosed?
I''m gonna check now if i'm able to disable the SECURE_FLAG without tripping the SafetyNet.
Click to expand...
Click to collapse
has anyone gotten AI- Upscaling to work ?

tokoam said:
has anyone gotten AI- Upscaling to work ?
Click to expand...
Click to collapse
no just the enhanced

Nvidia Shield TV pro 2019 :
I did all the steps and I have this error
I start again several times the same problem
Pasteboard - Uploaded Image
Simple and lightning fast image sharing. Upload clipboard images with Copy & Paste and image files with Drag & Drop
pasteboard.co
in start there is the following message...
Photobox | Online Photo Printing & Personalised Photo Gifts
Make stories from your photos. Print photos online or create personalised gifts with Photobox, the photo specialists. Photo Books, Prints, Canvases, more.
www.photobox.co.uk

So, any idea what to do when having diligently followed along and the result is those errors and now a Shield that can't boot and doesn't respond to ADB/Fastboot calls...
I can't believe I just blindly followed along and now my favourite thing in existence is bricked. I use it literally 24/7. Any ideas?

jamiethomaswhite said:
So, any idea what to do when having diligently followed along and the result is those errors and now a Shield that can't boot and doesn't respond to ADB/Fastboot calls...
I can't believe I just blindly followed along and now my favourite thing in existence is bricked. I use it literally 24/7. Any ideas?
Click to expand...
Click to collapse
its not bricked, and you didnt follow along else you wouldn't be in your current state. I literally just did this on my 2019 shield pro coming from the private beta without issue. The OP instructions need a few updates but most of those steps you should be familiar with anyway if you're going to be modding your devices
I lied, infinite loop, seems some derpy protection is getting tripped
0bin - encrypted pastebin
0bin is a client-side-encrypted alternative pastebin. You can store code/text/images online for a set period of time and share with the world. Featuring burn after reading, history, clipboard.
0bin.net

aouamed said:
Nvidia Shield TV pro 2019 :
I did all the steps and I have this error
I start again several times the same problem
Pasteboard - Uploaded Image
Simple and lightning fast image sharing. Upload clipboard images with Copy & Paste and image files with Drag & Drop
pasteboard.co
in start there is the following message...
Photobox | Online Photo Printing & Personalised Photo Gifts
Make stories from your photos. Print photos online or create personalised gifts with Photobox, the photo specialists. Photo Books, Prints, Canvases, more.
www.photobox.co.uk
Click to expand...
Click to collapse
its because Android is retarded and the script needs modified. After that error it should have booted into system setup, simply reboot into bootloader and `fastboot boot recovery.img` then continue onto installing magisk

Thank you for your reply...
I succeeded rooted my NSTV 2019 Pro v8.2.3
NVIDIA SHIELD ANDROID TV 2019 Pro Recovery OS Image 8.2.3
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.1.0 (vbmeta_skip.img)
TWRP : twrp-3.5.2_9-0-mdarcy.img
Magisk : Magisk v23.0 'beta'
Tested :
Safetynet checks pass fine...
reboot with magiskhide without probleme script 'bootfix-post.sh' 'bootfix-service.sh'
Demo mode work only Enhanced Mode
Other work well ...
Thank xda

Any solution for unlimited loading android splashscreen after enabled MagiskHide in Magisk after reboot shield?

Enable MagiskHide :
open PowerShell :
adb shell
su (confirm permission with remote control )
cat >/data/adb/post-fs-data.d/bootfix-post.sh
resetprop ro.boot.verifiedbootstate orange
Press Ctrl+d:
chmod +x /data/adb/post-fs-data.d/bootfix-post.sh
##############################
cat >/data/adb/service.d/bootfix-service.sh
resetprop ro.boot.verifiedbootstate green
Press Ctrl+d:
chmod +x /data/adb/service.d/bootfix-service.sh
Reboot system

do i need to have the nvidia controller/gamepad for this? everything that needs to adb or fastboot, so far, works but ill get to a screen and itll ask to confirm something and so on. except i dont have the gamepad. if you guys say i need one, of course ill go buy one but in the mean time, if not, how are you going through it?
edit:
also, does 8.2.0 or 8 .2.3 matter? the first time, i did do it on 8.2.3 but had to restart because i didnt have a gamepad.

How To Guide Simple Guide How To Root

Alright so a lot of people seem to have issues with rooting their device and creating a lot of spam on this forum because they don't know how to read.
This guide is for Windows PCs and will be for the people who don't want to read complicated guides.
What you Need:
A Device that has an unlocked Bootloader
The Factory Image of the ROM you are using or updating to Download Here
The Latest STABLE Magisk Download Here, if you are opting for a Beta/Canary then have fun.
7-zip or similar file extractor
ADB and Fastboot, I use Minimal ADB and Fastboot but this Script Here will download the latest version and add it to your PATH.
Way to Transfer Files to Phone (USB Cable?)
Steps:
Update to the Latest ROM. This can be done via Sideloading (personal preference) or OTA
Confirm you are on the same version as the factory image. Current is SP2A.220305.013 aka March 2022 Update
Extract the Zip File to a Folder. Current filename is raven-sp2a.220305.013.a3-factory-87b3bf0a.zip
Go in to the folder and extract the Image ZIP into a Folder. Current Name is image-raven-sp21.220305.003.zip
Find the Boot.img and transfer it to your device.
Install the Magisk Manager APK on the Device
Open Magisk and press Install.
Select "Select and Patch a File" and select the Boot.img you transferred to your device.
Magisk will patch the file and place the new .img file in your downloads. The filename will look like "magisk_patched-24300_abcde.img".
Transfer the patched file from your Downloads folder to your PC.
Reboot your phone to Fastboot mode Youtube Tutorial
Locate the patched .img file and press SHIFT+RightClick, click the option "Copy as Path"
On your PC open Command Prompt. If you dont know how to do this, you shouldn't be rooting your device.
In command prompt type "fastboot flash boot" and then paste the location of your patched .img file.
The whole command should look like "fastboot flash boot "C:\Users\Admin\Downloads\magisk_patched-24300_abcde.img"
Reboot the phone with the command "fastboot reboot"
Once the device is booted up, go to Magisk and see if you are rooted.
If there is enough demand, I can provide photos to help.
If I messed up along the way, let me know and I can change the guide.

Saved

{
"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"
}
I can't find my Downlaods folder. Idk what that is.

Gytole said:
View attachment 5574243
I can't find my Downlaods folder. Idk what that is.
Click to expand...
Click to collapse
Fixed lol

vassosman said:
Alright so a lot of people seem to have issues with rooting their device and creating a lot of spam on this forum because they don't know how to read.
This guide is for Windows PCs and will be for the people who don't want to read complicated guides.
What you Need:
A Device that has an unlocked Bootloader
The Factory Image of the ROM you are using or updating to Download Here
The Latest STABLE Magisk Download Here, if you are opting for a Beta/Canary then have fun.
7-zip or similar file extractor
ADB and Fastboot, I use Minimal ADB and Fastboot but this Script Here will download the latest version and add it to your PATH.
Way to Transfer Files to Phone (USB Cable?)
Steps:
Update to the Latest ROM. This can be done via Sideloading (personal preference) or OTA
Confirm you are on the same version as the factory image. Current is SP2A.220305.013 aka March 2022 Update
Extract the Zip File to a Folder. Current filename is raven-sp2a.220305.013.a3-factory-87b3bf0a.zip
Go in to the folder and extract the Image ZIP into a Folder. Current Name is image-raven-sp21.220305.003.zip
Find the Boot.img and transfer it to your device.
Install the Magisk Manager APK on the Device
Open Magisk and press Install.
Select "Select and Patch a File" and select the Boot.img you transferred to your device.
Magisk will patch the file and place the new .img file in your downloads. The filename will look like "magisk_patched-24300_abcde.img".
Transfer the patched file from your Downloads folder to your PC.
Reboot your phone to Fastboot mode Youtube Tutorial
Locate the patched .img file and press SHIFT+RightClick, click the option "Copy as Path"
On your PC open Command Prompt. If you dont know how to do this, you shouldn't be rooting your device.
In command prompt type "fastboot flash boot" and then paste the location of your patched .img file.
The whole command should look like "fastboot flash boot "C:\Users\Admin\Downloads\magisk_patched-24300_abcde.img"
Reboot the phone with the command "adb reboot"
Once the device is booted up, go to Magisk and see if you are rooted.
If there is enough demand, I can provide photos to help.
If I messed up along the way, let me know and I can change the guide.
Click to expand...
Click to collapse
It should be fastboot reboot

fil3s said:
It should be fastboot reboot
Click to expand...
Click to collapse
Good call, I was writing this on the fly and wasn't actually doing it as I was writing the guide.

fil3s said:
It should be fastboot reboot
Click to expand...
Click to collapse
Rather than saying they don't know how to read", it might be that they don't understand the "meta-language" of any given discussion or explanation!

EdBurger l said:
Rather than saying they don't know how to read", it might be that they don't understand the "meta-language" of any given discussion or explanation!
Click to expand...
Click to collapse
Goodo bruh.

vassosman said:
Saved
Click to expand...
Click to collapse
Do you really think this guide is too hard to follow? It's thoughtful that you typed out the steps but is it really less confusing or difficult?
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com

Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.

.

dmarden said:
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
Click to expand...
Click to collapse
They are not required to change if you plan on running Magisk 24.3. I did not change anything when I updated my P6P (bought in Feb) and rooted it.

dmarden said:
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
Click to expand...
Click to collapse
not needed anymore with latest magisk

That's great news, I've been missing it.

I am going to do this on S3B1.220218.006 (QPR3 Beta 1.1). Fingers crossed!

Worked perfectly, the only thing I might add is a link to the Google USB Drivers (since they must've updated). I had them installed originally (to have unlocked my device in the first place) but needed to update them.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Thanks a ton! I would've never noticed that the wipe step was no longer needed.

I recognize I am replying a lot, haha... sorry about that.
Presumably the update method for this should work exactly like past Pixel devices, yeah?
For me, this method was as follows:
1. Download the full image and edit the script to remove the "-w"
2. Install the modified image
3. Boot up once
4. Then basically follow the original procedure from this thread again
I know on OnePlus devices I was always able to uninstall Magisk root via the Magisk app, take the OTA, then reinstall Magist root via the Magisk app before rebooting, but that never seemed to work on Pixel devices (at least for me).

Just to share...
I decided to give the Magisk restore images, OTA, install again before reboot method a try and it worked perfectly going from QPR 1.1 to 2.

Thank you for this post. I would like to root my phone. I am a noob and it’s a little intimidating. If you would add pictures, I for one, would really appreciate that. Thanks again!

[EOL][ROM][UNOFFICIAL][12.1] LineageOS 19.1 for Galaxy Note10 5G [d1x][N971N][ENCRYPTION]

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Known Issues
You tell me
Requirements
Required firmware version is N971NKSU2HVE9.
Instructions
You can follow the instructions on the wiki page for d1: https://wiki.lineageos.org/devices/d1/install
Please remember to upgrade your firmware through Odin. Put the provided file in the BL slot.
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads
Builds: https://sourceforge.net/projects/lineageos-samsung-note10-5g/files/lineage-19.1/
GApps: https://wiki.lineageos.org/gapps.html
Firmware: https://sourceforge.net/projects/firmware-samsung-note10-5g/files/
Source
https://github.com/Rocky7842/android_kernel_samsung_exynos9820/tree/lineage-19.1
Contributors
Rocky7842
Linux4 for maintaining the trees for exynos982x devices.
LineageOS team

About Safetynet
The safetynet on this ROM can pass basic integrity, but not CTS.
Due to the official stance of LineageOS team, and spoofing the build fingerprint may causes issues because Android uses build fingerprint changes as a signal to clear and rebuild several caches, I will not put the modifications in the ROM itself. Instant I'll put the information here, you can choose to do it or not.
To pass CTS:
We have to install Magisk(or Lygisk), then install both Universal SafetyNet Fix and MagiskHidePropsConf modules.
Reboot, enter adb shell.
In adb shell, type in "props". Now Magisk should ask you for su, accept it.
Type in "1". Which is edit device fingerprint.
Type in "samsung/d1xks/d1x:12/SP1A.210812.016/N971NKSU2HVE9:user/release-keys".
Type in "y" to confirm.
Type in "n" to avoid reboot now.
Type in "b" to go back to main menu.
Type in "5". Which is add/edit custom props.
Type in "n". Which is new custom prop.
Type in "ro.build.version.security_patch".
Type in "2022-05-01".
Type in "y" to confirm.
Type in "y" to reboot.
Now the security patch date and build fingerprint should be what we set, and Safetynet should pass now.

Working, I can confirm

A working rom for d1x, am I dreaming?

jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Give it a try and you'll know if it's a dream or not.

jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Thanks to Rocky7842

jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Please give some feedback if you already try it.

Rocky7842 said:
Please give some feedback if you already try it.
Click to expand...
Click to collapse

Bro can you give me rooting tools for note 10 N971N? Please or even just the link bro please!

JÅ“508 said:
Bro can you give me rooting tools for note 10 N971N? Please or even just the link bro please!
Click to expand...
Click to collapse
What do you mean...? Just use magisk.

Rocky7842 said:
What do you mean...? Just use magisk.
Click to expand...
Click to collapse
i want to root my samsung note 10 n971n version. Maybe you can help me

I don't know where to download the root files.

Enable Developer Options
Under developer options enable OEM unlock
Download latest firmware for your phone
Go-to https://galaxyfirmware.com/model/SM-N971N/
Download the right file for your device (just choose one)
Download magisk
Once this is downloaded, we can install it.
With that done, extract. The contents of the firmware you downloaded earlier.
Copy the AP file onto your phone.
Now open magisk app and tap on the install button and, make sure that the recovery mode Option stays checked, now tap the next option to bring us to the method which lets us select and patch a file.
Locate that AP file and then load it up into magic before tapping. The, let's go button.
After magisk is done patching the files..
Now you're going to be told that there is an output file, You just need to make sure that we look at where this file is and copy it to your PC.
Put the device into download mode,
Now extract the Odin program and open it
connect phone to PC
disable the auto reboot option under options tab
Locate the firmware that was downloaded and the patched file.
start loading these files into Odin.
click the BL button and load the file that begins with the letters BL.
Remember the same with the CSC and we need to load the CSC file (not the home CSC file).
Now click the AP button right here, but instead of loading, the AP file, instead we're going to load the AP file magisk patched.
there is a progress bar on the phone itself as well on the PC.
So once you get a green pass message
Device is not going to reboot because we need to manually reboot to instantly however.
With Odin finished, unplug USB cable. now, We're going to press the VOLUME DOWN and the SIDE BUTTON till the screen go black, let go of the VOLUME DOWN button while still holding the SIDE BUTTON and press and hold the VOLUME Up button. So you're gonna press these two buttons to force the device to reboot.
After reboot locate and open magisk

VoLTE Supported?

Alexis Levin said:
VoLTE Supported?
Click to expand...
Click to collapse
VoLTE is not supported.

New build uploaded. Security patch date is now 2022-11-05.

I flashed recovery using Odin and can enter Lineage recovery mode successfully.
But when I use adb sideload <ROM.zip>, it cannot detect my devices to sideload the custom ROM.
There's no devices under adb devices either.

ngfuong said:
I flashed recovery using Odin and can enter Lineage recovery mode successfully.
But when I use adb sideload <ROM.zip>, it cannot detect my devices to sideload the custom ROM.
There's no devices under adb devices either.
Click to expand...
Click to collapse
If you sure you have put the phone into sideload mode, check your cable/driver or change a computer.

Rocky7842 said:
If you sure you have put the phone into sideload mode, check your cable/driver or change a computer.
Click to expand...
Click to collapse
Thank you for replying. I changed to Linux and now I can sideload the .zip file.
However, after sideloading using this command:
adb sideload lineage-19.1-20221113-UNOFFICIAL-d1x.zip
The phone returns this:
E: Signature verification failed
E: error: 21
Then I choose Install anyway, and receive:
Installing update...
E: Failed to find update binary META-INF/com/google/android/update-binary
Any idea what I missed?

ngfuong said:
Thank you for replying. I changed to Linux and now I can sideload the .zip file.
However, after sideloading using this command:
adb sideload lineage-19.1-20221113-UNOFFICIAL-d1x.zip
The phone returns this:
E: Signature verification failed
E: error: 21
Then I choose Install anyway, and receive:
Installing update...
E: Failed to find update binary META-INF/com/google/android/update-binary
Any idea what I missed?
Click to expand...
Click to collapse
Please try re-download the file. If it still fails, try install the "20221023" build.
I didn't test the "20221113" version since I'm doing the bring up of A13. There's a possibility that the file was corrupt in the uploading procedure. No one reports that so far, though.

How To Guide CPH2451 Rooters Please refrain to g96818 guide to Improve the Init_boot method.

Hey guys, i have tested the new method posted by g96818 and it works perfect.
Since he has more experience than me with OnePlus rooting I'll delete this post soon.
My fear is the future proofing of my method and i understand that his method is better in the case of future updates and less risky.

Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.

hitzzzzzzzz said:
Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.
Click to expand...
Click to collapse
Hey man, but there is a full OTA for that, you just need to subtract the info you need from it.
Since i dont have that device, i dont want to tell you what to do.

Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451

scott.hart.bti said:
Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451
Click to expand...
Click to collapse
Yeah that's true that would be nice.

Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device

scottlam1 said:
Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device
Click to expand...
Click to collapse
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable

blasbenoit said:
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me and other guys in this forum.
Important notes to consider: A big thanks to azsl1326 he got us the Patched Init_boot to make this possible.
-You need to unlock the bootloader of your device. This means you'll lose the data ect ect ect.
-People are losing Netflix access after this process, right now we haven't found a "cure" for this, but is pretty normal if you have root a Oneplus device before, when i found the fix i'll edit this right away.
-I'll write this for experts and newcomers a like just in case so they don't have to start asking for simple questions.
-After the root some people have the issue that they cant use security like passwords, fingerprint...ect ect. (as of now the only fix they have is to reset everything and doing the rooting again for 2+times). If i find the "cure" i'll let you guys know.
Spoiler: Issues connecting your device to the PC?
To some people the USB debugging is not working at all, because the phone turn it off after you try to use it or connect it to the PC.
I personally had this issue so i just workaround it. This is what i did:
1- Connect the OnePlus to the same network as your PC.
2- Turn On Wireless debugging on your OP11 and select Pair device with pairing code:
3- Then use this on your PC after you open CMD of course:
Then put the code you have.
The check with this command to see if it is connected:
Now that it is connected you can enter bootloader and connect it to your PC in that mode normally with:
OK now back to the deal:
1- Download the latest platform tools from here:
-Unzip it and put it in the desktop for easy access.
2-The bootloader
Spoiler: Unlock the Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"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"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
3- Flashing the Init_Boot.img
In this case i'll provide the already patched Init_boot.img for A07!!! so you don't have to look for it, is attached to this thread.
Download the img and put it in the same folder as the platform tools for easy access.
Spoiler: Magisk Canary
After you enter the device.
1. Dowload the Magisk Canary version from this link:
2. Install it on you device.
Spoiler: Opening CMD (Command Prompt)
After you got everything in place open the platform folder and type CMD on the location box, then press Enter.
If that doesn't work, just open CMD and type:
CD and write the location of the platform folder to get it to work.
Now to the "flashing"
Enter the bootloader like before to start, now type this:
The above command should automatically flash the init_boot to both the slots. However, if you face any issues while executing that command, then you could also manually specify the slots while flashing. Like this:
And
4-Restart your phone and check the magisk canary app that everything is OK.
Spoiler: Bypassing Safetynet
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
Download a safetynet check just to be sure.
And thats pretty much it, if you guys find some issues after the root, please post them here so i'll start adding more and more info about it for future references and fixes.
Click to expand...
Click to collapse
You are so helpful! This worked flawlessly!

ChrisFeiveel84 said:
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable
Click to expand...
Click to collapse
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key

scottlam1 said:
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key
Click to expand...
Click to collapse
i never use adb over wifi sorry

Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?

H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first

ChrisFeiveel84 said:
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first
Click to expand...
Click to collapse
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated

H4X0R46 said:
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated
Click to expand...
Click to collapse
I didn't have an issue with my lock screen and stuff. I also didn't do anything to the phone other than unlock bootloader and root. Once I did this my lock screen and fingerprint and stuff wasn't an issue at all. Maybe I got lucky.

H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
The password issue has nothing to do with rooting, it is caused by unlocking the bootloader. Before you do any rooting, first lock and unlock the bootloader 3 times. After the third time, you can set the password (or pin, or pattern/etc) and THEN do the actual rooting.

Do you have boot.img instead i rather have temp root

i accidentally pushed the patched init boot img to phone before updating, now i keep getting failed system update, any way to revert back to original A06 init_boot.img so i can take update and then come back and root

SappyHanger said:
Do you have boot.img instead i rather have temp root
Click to expand...
Click to collapse
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.

blasbenoit said:
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.
Click to expand...
Click to collapse
can you point me to the init boot image on A06, i accidentally pushed the patched a07 version to a06 w/o updating to a07

So I did the above and magisk turns into a green android icon and won't start. It did start before I flashed the init boot.... ?? Tried to re-install magisk, same thing. green icon.....
Do I need to sideload magisk? (adb sideload Magisk-v25.2.zip) ???