Develop Bugs

[HOW-TO][LS-980] Restore, Downgrade, Install CyanogenMod on LG G2

READ ME FIRST I am more than willing to help you guys, so if you have questions, please ask me via my facebook page, as I get notifications there instantly. http://facebook.com/vacationlandtech
Also of note, I no longer have a LG G2, and it has been a long time since I made this, if you can be as descriptive as possible when asking questions, that would help a lot. Also, because it has been quite a while since I've been in the G2 community, I'm not up to speed on anything newer than early November, 2014. I don't have experience with ZVE+, CM12+, CloudyG3, etc. so if you have problems with new ROMs and software, get help from the people who make/support those ROMs and software.
Good luck!!
So I've been helping around the forums with people trying to install CyanogenMod on the Sprint LG G2 (LS-980). I have done this successfully and will outline my steps to do so below. A small caveat – I've only gotten this to work the way I'll outline below. I've tried getting CyanogenMod after the LS980ZVA/C/D OTA and no matter what I do I cannot get it to work. That being said, let's get to it.
Edit: I've added videos!!
Part 1: http://youtu.be/NRwlxeUprZE
Part 2: http://youtu.be/7rohyf_W13k
Part 3: http://youtu.be/Uw3J5ZTb3ro
*REMEMBER* - Always create Nandroid backups before flashing a ROM or doing anything, really.
Required Materials (some of these files (LS980ZV8_13.TOT) are over 2GB, FYI):
EDIT: I have put all the required files into a .ZIP archive and uploaded it to Mega
There has been a report that that the CyanogenMod .zip in my file is corrupt. You can still download the file I uploaded, just get CyanogenMod from the link below.
Update: I uploaded *just* the LS980ZV8_13.TOT file to Mega. Here is the link (beware it's not zipped, it's over 3GB).
Code:
* LS980ZV8_13.TOT - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LS980ZV8_13.zip[/URL]
* LGLS980_20130904_LGFLASHv151.dll - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LGLS980_20130904_LGFLASHv151.dll[/URL]
* LG Flash Tool - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/Setup_LGFlashTool_1.8.1.1023.exe[/URL]
* MegaLock.dll - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/MegaLock.dll[/URL]
* IOroot25 - [URL]http://downloads.codefi.re/autoprime/LG/ioroot/ioroot.zip[/URL]
* LG G2 (Verizon) USB Driver - [URL]http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427[/URL]
* GApps - [url]https://s.basketbuild.com/gapps[/url]
Now, back up any files you want to keep from your phone. This process will remove EVERYTHING from your phone INCLUDING Internal Storage! Also install the USB Driver.
Let's get to it (please read all instructions before doing anything):
Resetting to Stock
Required files: LG Flash Tool, MegaLock.DLL, LS980ZV8_13.TOT, USB Drivers.
1. Install LG Flash Tool , but don't launch it yet!
2. Copy MegaLock.DLL to the root of the installation directory of LG Flash Tool.
3. Launch LG Flash Tool.
4. Check “Manual Mode”
5. Browse to the .DLL file you downloaded by clicking the “...” button to the right of the first text box.
6. Browse to the .TOT file (it'll have to be unzipped) by doing the same thing for the 2nd box.
7. Click okay, then click the green arrow at the top right of the window.
8. Wait for one of the boxes to turn green and say “Ready”
9. Turn off your phone.
10. Plug in the phone to your computer while holding the Vol+ key to put your phone in download mode.
11. Open Device Manager on your computer by pressing Win+R and typing “devmgmt.msc” without the quotes, then pressing enter.
12. Scroll down to “Ports” and expand it.
13. There will be an Android entry, right click it and select “Properties”
14. Select the Port Settings tab, and select Advanced.
15. Change the port number to 41.
16. You may have to unplug and reconnect your phone.
17. The box that said ready should now have some messages inside it (ie. “Waiting for connection.” and stuff about phone checks).
18. Allow the flash tool to do its job, after anywhere between 10 minutes and half an hour the phone will be done resetting. In my experience, the flash tool will always say there was an error after the phone reboots, this is because the phone reboots into Android, but the flash tool has done everything it needs, don't worry!
19. You can now unplug your phone and close LG Flash Tool.
20. Your phone is now on stock LG firmware LS980ZV8!
** - If you're going on to flash CyanogenMod, get through the initial set up, let the phone activate, but don't worry about getting apps or settings, they'll be gone after we flash CM.
Rooting
Required files: IOroot25, USB Drivers
** - I'm going to write this as if you've just reset to stock firmware.
1. Navigate to Settings > About Phone > Software Information
2. Tap on Build Number 7 times, or until there is a pop-up stating that “You are now a developer!”
3. Go back to Settings
4. Go into Developer Settings
5. Enable USB Debugging
6. Plug your phone into your computer.
** - If there is a RSA Fingerprint pop-up, accept it and check Remember this fingerprint
7. Navigate to Ioroot (you may have to extract/unzip the files) and execute root.BAT
8. Follow the on-screen instructions.
** - Note that Ioroot automatically backs up your EFS partition, make sure to keep these files in a safe location, as they can come in handy if something goes wrong.
9. After Ioroot is finished, you can close the program, unplug your phone and disable USB debugging.
10. You're now rooted, you may verify by downloading a Root Checker app from the Google Play Store.
Installing a Custom Recovery
Required Files: None
1. On your phone, navigate to the Google Play Store.
2. Search for FreeGee and install it.
3. Open FreeGee and allow it to download the device list.
4. After the download is finished, you will see a changelog list, close this.
5. Tap on install TWRP (or CWM if you're more comfortable with ClockWork Mod).
** - I recommend TeamWin Recovery Project for newer users because it is more end-user friendly, touch-capable, etc.
6. Wait for FreeGee to do its thing, then you have a custom recovery installed.
7. If you want to, let FreeGee reboot you into Recovery in order to verify.
Installing CyanogenMod 11
Required Files: CyanogenMod 11 ZIP, USB Drivers
** - Get the CyanogenMod 11 ZIP from https://download.cyanogenmod.org/?device=ls980 I recommend using the latest SNAPSHOT – get the NIGHTLY only if there are problems with the SNAPSHOT.
1. Place the CM 11 ZIP on the root directory of your internal storage.
2. Power off your phone (without it plugged in).
3. Turn on your phone holding PWR+VOL-Down until the screen says “Recovery mode”
** - The screen may say something about a factory reset, in this case press the power button 3 times and you'll be brought into recovery.
4. Tap on install
5. Scroll down to the CM 11 ZIP and tap it
6. Follow the instructions and when prompted to wipe the dalvik and cache, select yes.
** - you may have to do an advanced wipe and select everything except for internal storage, but do this only if CyanogenMod doesn't install properly.
7. You now have CyanogenMod 11 on your phone!
**- You will have to install GApps in order to access the Google Play Store and other Google Apps. You can download it using the browser on your phone or by transferring the .zip file to the root of your phone.
**- To install GApps just boot into recovery, select Install, and navigate to the GApps .zip. Swipe to install.
If you have any questions or any issues, just let me know. Not everything is accurate as I don't have access to Windows right now so I'm going based off memory. I plan on reinstalling Windows 8.1 Professional and making a video to go along with this. If at any point throughout this walkthrough you find inaccurate information or something goes wrong, let me know and I'll help out/update the article. Good luck!

Thanks so much for your sharing this. I have downgrade my phone from ZVD to ZV7 and get it rooted and CM11 installed. However, I found CM11 is not stable and my GPS module didn't work now. Could you recommend a everyday-use ROM with tethering capability? Many thanks.

damiloveu said:
Thanks so much for your sharing this. I have downgrade my phone from ZVD to ZV7 and get it rooted and CM11 installed. However, I found CM11 is not stable and my GPS module didn't work now. Could you recommend a everyday-use ROM with tethering capability? Many thanks.
Click to expand...
Click to collapse
I use CyanogenMod 11 as my everyday ROM, never have any issues (besides some personal preferences). To confirm that you have a good stable build, check your build number and info. I will post mine below for you to compare to.
To check your build number navigate to Settings > About Phone
Code:
Model Number.................LG-LS980
CyanogenMod Version..........11-20140804-SNAPSHOT-M9-ls980
Android Version..............4.4.4
Baseband Version.............M8974A-AAAANAZM-1.0.190034
Kernel Version...............3.4.0-CM+
[email protected] #1
.............................Sun Aug 3 22:34:14 PDT 2014
I used this download for my CM: Direct Download from CyanogenMod

official.xian said:
I use CyanogenMod 11 as my everyday ROM, never have any issues (besides some personal preferences). To confirm that you have a good stable build, check your build number and info. I will post mine below for you to compare to.
To check your build number navigate to Settings > About Phone
Code:
Model Number.................LG-LS980
CyanogenMod Version..........11-20140804-SNAPSHOT-M9-ls980
Android Version..............4.4.4
Baseband Version.............M8974A-AAAANAZM-1.0.190034
Kernel Version...............3.4.0-CM+
[email protected] #1
.............................Sun Aug 3 22:34:14 PDT 2014
I used this download for my CM: Direct Download from CyanogenMod
Click to expand...
Click to collapse
I am using the same ROM as yours. I will flash back to Stock ROM and if the GPS still doesn't work, I have to contact LG to get a replace one.

damiloveu said:
I am using the same ROM as yours. I will flash back to Stock ROM and if the GPS still doesn't work, I have to contact LG to get a replace one.
Click to expand...
Click to collapse
Sounds good. I can confirm that my GPS works fine on this ROM so... Good luck. Let me know if you have any questions!

Can U help me with this....
I have LG G2 LS980ZVC Rooted device, and SuperUser is installed.
I want to migrate from stock ROM to CyanogenMod ROM.
But I want the device to work as of the LG G2 D802 (International).
As I will be using it in INDIA (GSM 850/900/1800/1900).
I am very much new to Android and confused to pick the ROM and about the installation procedure.
Seek expert advice about this concern.
Plz suggest... ( attach Hyper link of threads / Videos about the procedure of installation and ROM download link while replying).
Thanks in Advance.......

AJ, I will do some research as to unlocking this phone. I am a bit busy right now but I'll reply by the end of the day.

This phone is already unlocked and works fine with Indian SIM
This phone is already unlocked and works fine with any Indian SIM. I Just want to migrate to CyanogenMod ROM.
official.xian said:
AJ, I will do some research as to unlocking this phone. I am a bit busy right now but I'll reply by the end of the day.
Click to expand...
Click to collapse

I can't find any information regarding unlocking on CyanogenMod specifically, but maybe you could do the same steps at: http://forum.xda-developers.com/showthread.php?t=2655133 after you follow my instructions to install CyanogenMod.

:Confused
This phone is already unlocked and works fine with any Indian SIM.
I am Just confused to pick between these two CyanogenMod ROMs :
1. (ls980 LG G2 (Sprint))
https://download.cyanogenmod.org/?device=ls980
https://download.cyanogenmod.org/get/jenkins/78482/cm-11-20140804-SNAPSHOT-M9-ls980.zip
OR
2. (d802 LG G2 (Intl))
https://download.cyanogenmod.org/?device=d802
https://download.cyanogenmod.org/get/jenkins/78458/cm-11-20140804-SNAPSHOT-M9-d802.zip
And any guidelines to install the CynogenMod ROM, as I am New to this.
Thanks in Advance. .
official.xian said:
I can't find any information regarding unlocking on CyanogenMod specifically, but maybe you could do the same steps at: http://forum.xda-developers.com/showthread.php?t=2655133 after you follow my instructions to install CyanogenMod.
Click to expand...
Click to collapse

Never, I repeat NEVER flash or install ANYTHING that is not specifically for your phone!! This is the fastest way to brick your device, possibly permanently. I understand that you have already unlocked your phone, but you've done so on a stock ROM. What I was saying is follow my instructions to install CyanogenMod (the LS980 version) on your phone, then (re)unlock it following the instructions at the thread I linked to. I'm not sure how to unlock on CM11, but it can be done: LG G2 LS980 GSM UNLOCKED!: http://youtu.be/r8XCpm046-k

damiloveu said:
Thanks so much for your sharing this. I have downgrade my phone from ZVD to ZV7 and get it rooted and CM11 installed. However, I found CM11 is not stable and my GPS module didn't work now. Could you recommend a everyday-use ROM with tethering capability? Many thanks.
Click to expand...
Click to collapse
I did try and after a lot of got it to work CM11, you only need ZV8 modem/radio.
Had problems with the GPS even try a lot of apps none of them got it to work, then change the gps.conf file for the orginal LG conf and worked great. The only ROM that the GPS worked since the start was PA all of the others are based on CM so the file wont work, at least for me.
The gps.conf file its on "etc" folder.
CM really its great but to me Omni and most of all that i try in this days (trying to get a good GPS just to play Ingress) Its PA
Good luck

emi_fer said:
I did try and after a lot of got it to work CM11, you only need ZV8 modem/radio.
Had problems with the GPS even try a lot of apps none of them got it to work, then change the gps.conf file for the orginal LG conf and worked great. The only ROM that the GPS worked since the start was PA all of the others are based on CM so the file wont work, at least for me.
The gps.conf file its on "etc" folder.
CM really its great but to me Omni and most of all that i try in this days (trying to get a good GPS just to play Ingress) Its PA
Good luck
Click to expand...
Click to collapse
I've never had an issue with CyanogenMod. If you wipe before you install and don't do anything funky with it you shouldn't have a problem. Following my instructions CyanogenMod works flawlessly (for me at least).

official.xian said:
I've never had an issue with CyanogenMod. If you wipe before you install and don't do anything funky with it you shouldn't have a problem. Following my instructions CyanogenMod works flawlessly (for me at least).
Click to expand...
Click to collapse
Always Wipe data/Factory reset when change to a different ROM, as i said the only one that worked for me its PA because uses the stock gps.conf thats all

emi_fer said:
Always Wipe data/Factory reset when change to a different ROM, as i said the only one that worked for me its PA because uses the stock gps.conf thats all
Click to expand...
Click to collapse
How long ago did you have problems?

official.xian said:
So I've been helping around the forums with people trying to install CyanogenMod on the Sprint LG G2 (LS-980). I have done this successfully and will outline my steps to do so below. A small caveat – I've only gotten this to work the way I'll outline below. I've tried getting CyanogenMod after the LS980ZVA/C/D OTA and no matter what I do I cannot get it to work. That being said, let's get to it.
*REMEMBER* - Always create Nandroid backups before flashing a ROM or doing anything, really.
Required Materials (some of these files (LS980ZV8_13.TOT) are over 2GB, FYI):
Code:
* LS980ZV8_13.TOT - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LS980ZV8_13.zip[/URL]
* LGLS980_20130904_LGFLASHv151.dll - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LGLS980_20130904_LGFLASHv151.dll[/URL]
* LG Flash Tool - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/Setup_LGFlashTool_1.8.1.1023.exe[/URL]
* MegaLock.dll - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/MegaLock.dll[/URL]
* IOroot25 - [URL]http://downloads.codefi.re/autoprime/LG/ioroot/ioroot.zip[/URL]
* LG G2 (Verizon) USB Driver - [URL]http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427[/URL]
Now, back up any files you want to keep from your phone. This process will remove EVERYTHING from your phone INCLUDING Internal Storage! Also install the USB Driver.
Let's get to it (please read all instructions before doing anything):
Resetting to Stock
Required files: LG Flash Tool, MegaLock.DLL, LS980ZV8_13.TOT, USB Drivers.
1. Install LG Flash Tool , but don't launch it yet!
2. Copy MegaLock.DLL to the root of the installation directory of LG Flash Tool.
3. Launch LG Flash Tool.
4. Check “Manual Mode”
5. Browse to the .DLL file you downloaded by clicking the “...” button to the right of the first text box.
6. Browse to the .TOT file (it'll have to be unzipped) by doing the same thing for the 2nd box.
7. Click okay, then click the green arrow at the top right of the window.
8. Wait for one of the boxes to turn green and say “Ready”
9. Turn off your phone.
10. Plug in the phone to your computer while holding the Vol+ key to put your phone in download mode.
11. Open Device Manager on your computer by pressing Win+R and typing “devmgmt.msc” without the quotes, then pressing enter.
12. Scroll down to “Ports” and expand it.
13. There will be an Android entry, right click it and select “Properties”
14. Select the Port Settings tab, and select Advanced.
15. Change the port number to 41.
16. You may have to unplug and reconnect your phone.
17. The box that said ready should now have some messages inside it (ie. “Waiting for connection.” and stuff about phone checks).
18. Allow the flash tool to do its job, after anywhere between 10 minutes and half an hour the phone will be done resetting. In my experience, the flash tool will always say there was an error after the phone reboots, this is because the phone reboots into Android, but the flash tool has done everything it needs, don't worry!
19. You can now unplug your phone and close LG Flash Tool.
20. Your phone is now on stock LG firmware LS980ZV8!
** - If you're going on to flash CyanogenMod, get through the initial set up, let the phone activate, but don't worry about getting apps or settings, they'll be gone after we flash CM.
Rooting
Required files: IOroot25, USB Drivers
** - I'm going to write this as if you've just reset to stock firmware.
1. Navigate to Settings > About Phone > Software Information
2. Tap on Build Number 7 times, or until there is a pop-up stating that “You are now a developer!”
3. Go back to Settings
4. Go into Developer Settings
5. Enable USB Debugging
6. Plug your phone into your computer.
** - If there is a RSA Fingerprint pop-up, accept it and check Remember this fingerprint
7. Navigate to Ioroot (you may have to extract/unzip the files) and execute root.BAT
8. Follow the on-screen instructions.
** - Note that Ioroot automatically backs up your EFS partition, make sure to keep these files in a safe location, as they can come in handy if something goes wrong.
9. After Ioroot is finished, you can close the program, unplug your phone and disable USB debugging.
10. You're now rooted, you may verify by downloading a Root Checker app from the Google Play Store.
Installing a Custom Recovery
Required Files: None
1. On your phone, navigate to the Google Play Store.
2. Search for FreeGee and install it.
3. Open FreeGee and allow it to download the device list.
4. After the download is finished, you will see a changelog list, close this.
5. Tap on install TWRP (or CWM if you're more comfortable with ClockWork Mod).
** - I recommend TeamWin Recovery Project for newer users because it is more end-user friendly, touch-capable, etc.
6. Wait for FreeGee to do its thing, then you have a custom recovery installed.
7. If you want to, let FreeGee reboot you into Recovery in order to verify.
Installing CyanogenMod 11
Required Files: CyanogenMod 11 ZIP, USB Drivers
** - Get the CyanogenMod 11 ZIP from https://download.cyanogenmod.org/?device=ls980 I recommend using the latest SNAPSHOT – get the NIGHTLY only if there are problems with the SNAPSHOT.
1. Place the CM 11 ZIP on the root directory of your internal storage.
2. Power off your phone (without it plugged in).
3. Turn on your phone holding PWR+VOL-Down until the screen says “Recovery mode”
** - The screen may say something about a factory reset, in this case press the power button 3 times and you'll be brought into recovery.
4. Tap on install
5. Scroll down to the CM 11 ZIP and tap it
6. Follow the instructions and when prompted to wipe the dalvik and cache, select yes.
** - you may have to do an advanced wipe and select everything except for internal storage, but do this only if CyanogenMod doesn't install properly.
7. You now have CyanogenMod 11 on your phone!
If you have any questions or any issues, just let me know. Not everything is accurate as I don't have access to Windows right now so I'm going based off memory. I plan on reinstalling Windows 8.1 Professional and making a video to go along with this. If at any point throughout this walkthrough you find inaccurate information or something goes wrong, let me know and I'll help out/update the article. Good luck!
Click to expand...
Click to collapse
I am in the process of resetting everything back to stock. However, I was reading other articles and it mentioned that you must choose the correct files that correspond to either the 16gigs or 32 gigs. In this set of instructions however, it only provides users with one zv8 file for download. I just don't want to mess something up by using the incorrect files. Would appreciate someone's help. Thanks

Robles23 said:
I am in the process of resetting everything back to stock. However, I was reading other articles and it mentioned that you must choose the correct files that correspond to either the 16gigs or 32 gigs. In this set of instructions however, it only provides users with one zv8 file for download. I just don't want to mess something up by using the incorrect files. Would appreciate someone's help. Thanks
Click to expand...
Click to collapse
I have seen what you're talking about elsewhere but I don't believe that this applies in this situation. I have the 32GB LS980, and haven't had an issue, still have all my storage space. From everything that I've gathered from the internet when learning how to do everything a wrote the size doesn't matter. If you're still concerned I can do some more digging, but I don't think you'll have a problem.

official.xian said:
I have seen what you're talking about elsewhere but I don't believe that this applies in this situation. I have the 32GB LS980, and haven't had an issue, still have all my storage space. From everything that I've gathered from the internet when learning how to do everything a wrote the size doesn't matter. If you're still concerned I can do some more digging, but I don't think you'll have a problem.
Click to expand...
Click to collapse
Very much appreciate your answer brother. I also have a 32gb model. No need to do more research. I will try this method ones I get home from work today. Ones again, I appreciate your repay and tutorial.

Robles23 said:
Very much appreciate your answer brother. I also have a 32gb model. No need to do more research. I will try this method ones I get home from work today. Ones again, I appreciate your repay and tutorial.
Click to expand...
Click to collapse
Glad to help. If you feel unsure about anything I'm also working on a video to upload to YouTube as well (after I finish it I'll edit the OP) that goes over the process. Good luck.

official.xian said:
Glad to help. If you feel unsure about anything I'm also working on a video to upload to YouTube as well (after I finish it I'll edit the OP) that goes over the process. Good luck.
Click to expand...
Click to collapse
Hell yeah I will love to watch and follow that tutorial. I will wait for it. Thank you!

Samsung Galaxy Tab 3 7.0 SM-T210 problem

I recently found my old tablet and it had kingoroot installed and then I flashed stock rom to my tablet but now it randomly restarts and every time i try to setup it i got error "Unfortunately, the process com.android.systemui has stopped" and "settings has stopped"
Here is the tutorial I followed:
Code:
The following instructions are for Windows only. Please don't use a virtual machine as these can cause problems communicating with the device. There is an alternative method for Linux or macOS. Just tell me if you aren't on Windows, I can easily change the instructions. Please make sure you have Windows set to display all file extensions. This can really help for debugging purposes.
First we need to download the tool that downloads the stock firmware. It's called SamFirm and it downloads it using Samsung's servers. You can download the latest version [here](http://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462). Please also make sure you have the [Microsoft Visual C++ 2008](https://download.microsoft.com/download/1/1/1/1116b75a-9ec3-481a-a3c8-1777b5381140/vcredist_x86.exe) and [Microsoft Visual C++ 2010](https://download.microsoft.com/download/5/B/C/5BC5DBB3-652D-4DCE-B14A-475AB85EEF6E/vcredist_x86.exe) x86 Redistributable packages installed. Now to download the tool that flashes to the devices different partitions. On most devices you use a tool called fastboot, but Samsung devices aren't like most devices (excluding the Galaxy Nexus). This tool is called Odin, it's Windows only and leaked from Samsung so you need to get it from a trusted source. You can download the latest version [here](https://build.nethunter.com/samsung-tools/Odin_3.12.3.zip). Extract the "Odin_3.12.3.zip" file. You should now have a folder called "Odin_3.12.3". Treat this as your working directory and download all other files to this folder. While you're here, extract the contents of "SamFirm_v0.3.6.zip" into this folder.
Now to download the stock firmware. Open "SamFirm.exe" and make sure "Auto" is checked and "Manual" and "Binary Nature" isn't checked. In "Model" put `SM-T210` and in "Region" put `BTU`. Click "Check Update" and wait for it to find the firmware on the server. Now check "Check CRC32" and "Decrypt automatically". Then click "Download" and save it. Let it finish downloading, checking, and decrypting. Once it finishes you can now close SamFirm. Extract the zip file it gave you. You should now have a single file ending in `.tar.md5` (you may also have `.dll` file, ignore it). This tar.md5 file is your firmware. Do not modify it. If you have more than one .tar.md5 file, tell me.
Now shutdown the device and then hold the Volume Down, Home/Bixby, and Power buttons. This should put the device into download mode. Accept any warnings then plug the device in. Open "Odin.exe" from the "Odin_3.12.3" folder. In the log, it should say `Added!` and have a blue COM thing near the top, meaning it detected your device. If it didn't detect it, then you may need to configure drivers (you can ask me for the drivers if you need them). Click the "Option" tab and make sure "F. Reset Time" and "Auto Reboot" is enabled. Also check the checkbox next to the "AP" button and then click the button. Select the tar.md5 file. Now click "Start" in Odin.
It should now reboot and go to the boot animation. If it doesn't boot in 15 minutes, shutdown the device. Then hold the Volume Up, Home/Bixby, and Power buttons. Then use the keys to select "Factory reset". Please note this will wipe all user data. Once it finishes you can select "Reboot" and now it should boot correctly.
I have been battling with this problem so long I only wanted to root my tablet to have some fun with root required apps
Any help with the problem? I only need to root the device or get it to work with stock rom

[ROM][SHT-AL09][Fenris_SHT-AL09]

{
"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"
}
Fenris Features
Built in current MicroG
Built in Magisk
Built in BusyBox
Built in GNU Utils compiled for android ( bash etc )
Radically debloated
Built for Lucky Patcher ( lvm already patched and modded playstore in place )
Working Desktop Mode ( PC mode ), Yes you read that right
320 DPI and working camera UI etc.
Better sized Launcher icons.
Shipped as a old school zip so fully customisable by anyone with winrar
Bugs
Wallpapers etc missing ( belongs to an apk i deleted and cant be bothered to track it down ) fixed in beta 2
Standard filemanager is replaced by CM native file manager ( dont want the big H knowing whats on your drive ) so some share functions may not be available
but SMB over the network is fine and thats all im interested in.
Both the TWRP 's are flaky, this version https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917 has just refused to boot on me twice despite a decrypted data partition. But thats not down to Fenris in any way. The second twrp ( view 10 ) is no longer possible. It requires formating /data and by doing that wipes all the themes/wallpapers and screws the theming engine so i am having to stick with the first TWRP.
Unfortunately it BARELY works, just good enough to flash Fenris and associated zip kind of correctly.
Because of a crap TWRP Magisk needs to be setup on first use and download the manager, ie internet needed. It also can not update its zip so that has to be flashed by hand
Battery.... Tablet manager had to go, it deliberately interferes with LP in-app spoofing, but it also provides battery statistics and possibly with it missing, battery life could be worse than stock
( memory handling could also be compromised ). Its a damn hard thing to check since i have never run the tab stock. Tablet manager is back, it controls the recents screen which is broken without one of tablet managers services. Writing a startup script to disable some TM services, but at moment i use MyAndroidTools to do same
Maybe more, this is a beta.
Dev Info.
Huawei have done a good job with their Andfroid shell, its very memory aware and frugal ( unlike samsung and HTC ), its a very good base for Fenris
I would have kept a lot more native apk's but then there are some security concerns so anything with a free line out had to go ( except HwShare, use at your own risk )
If there is demand i will release a total stock zip so peeps can mix-match and roll their own.
Information
Based on MediaPad M5 8.4 SHT-AL09 hw eu Schubert-AL09A 8.0.0.196(C432) Firmware 8.0.0 r1 EMUI8.0 05014XYF.
the link for this firmware https://androidhost.ru/tuA
You must be on this firmware to grantee Fenris operating correctly ( currently Fenris does not ship the vendor or kernel due to issues with the TWRP available being flaky )
, fenris may work on other firmware ( Android O ) but this is for you to try.
I will most prob keep Fenris SHT-AL09 updated as i find stuff i like/do not like, but i AM NOT a Dev, i only get my hands dirty when i need to, so as far as support goes, dont expect much and you will not be disappointed.
My tested method of getting fenris on your SHT-AL09
......download Fenris from here https://mega.nz/#!BKpX2YpT!DhotPKAkJvASYQUPeUlNz3MrZanmFNCxmm6tcd4qcE4
......download Huawei MediaPad M5 8.4 SHT-AL09 hw eu Schubert-AL09A 8.0.0.196(C432) Firmware 8.0.0 r1 EMUI8.0 05014XYF from here https://androidhost.ru/6n0
......downgrade using the dload method
......Get a bootloader unlock code using DC unlocker method ( keep the bootloader unlock code, you will friggin need it )
......Unlock bootloader using Fastboot Unlock Method
......download MediaPad M5 8.4 SHT-AL09 hw eu Schubert-AL09A 8.0.0.196(C432) Firmware 8.0.0 r1 EMUI8.0 05014XYF. from here https://androidhost.ru/tuA
......Upgrade using the Dload method
......Unlock bootloader using Fastboot Unlock Method ( dont worry the code is the same )
......Go into you new 196 system and Activate ADB and OEM-Unlock
......Flash this TWRP https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825 using TWRP fastboot method
......DO NOT LET IT BOOT INTO SYSTEM, BOOT INTO TWRP INSTEAD
......Have a OTG USB adapter ( you can also use the sd card but that is a pain ) and Stick ready , copy all the files your going to need in the further steps onto it
......Hook up the stick and Flash Disable_Dm-Verity_ForceEncrypt_Quota_05.21.2019.zip from here https://zackptg5.com/android.php#disverfe
......Also Kernel-Sepolicy-Patcher.zip from here also https://zackptg5.com/android.php#disverfe
......THen finally flash Fenris
......Boot ito Fenris
TWRP fastboot method
1.... Make sure you have latest HW adb drivers installed ( check by getting an adb shell to work )
2.... Download latest Android platform tools https://developer.android.com/studio/releases/platform-tools
3)... Decompress etc, get to fastboot dir, open a CMD there
4)... Copy your TWRP image to same dir
5).... Boot into Download mode ( vol down while plufgging USB into computer with drivers set up )
5).... fastboot.exe flash recovery_ramdisk xxxxxxxxxx.img
6).... Get frigin ready to pull the usb and hold power + vol UP ( to reboot int TWRP you just flashed ) DO NOT LET IT BOOT INTO SYSTEM
7).... fastboot.exe reboot
8).... Pull USB, Boot into TWRP
9).... TWRP reboot Menue to shutdown
Dload Method
1.... extract the archive
2.... copy dload folder to root of a fat32 formated sd card
3.... boot up, enable dev options
4.... In dev options enable OEM-unlock ( you will need to be on internet from setup onwards ) unlock and adb
5.... In phone dialer dial *#*#2846579#*#*
6..... Get to upgrade from sd card and hit it.
7..... Phone reboots and does the ****
8..... If you have used online Erecovery downgrading may fail but if setting up from new ( unboxing) this will def work
Dc Unlocker Method ( copied from a p20lite thread , but works for m5 identically )
1)First connect your phone to the PC using the original USB cable.
2)When drivers are installed a popup screen would appear to view the "HiSuite" drive. This is a created drive-letter which contains a HiSuite Software downloader. Click to open or use the Windows Explorer to browse to this virtual drive.
3)Install the HiSuite software - this is important to get the correct drivers AND correct COM ports installed on your system. Skipping this step will result in non working DC Unlocker software.
4)When all is done go to the settings in your phone and open: System -> About Phone and tap the Build-number line about 7 to 8 times. Most likely the phone will ask for a PIN to active the developers mode. This is the code you've setup to use your phone. If you're already have a "developers option" you can skip this step.
5)Now click the "back" arrow once and select "Developer options".
6)Tap OEM-Unlock to activate it (confirm if needed), scroll down and tap USB Debugging to turn it on.
7)Your phone should ask permission to connect your PC (with some MAC address). Confirm it so the connection is approved. If that doesn't show up disconnect the USB cable and check if the USB debug mode is still active in the "Developer options". Than reconnect the cable to your PC.
ready to use the DC-Unlocker software to get our unlock code:
8)First you need some credits and you can buy the using this link: https://www.dc-unlocker.com/buy
9)Just fill in the the fields User-name, E-mail and Credits. Leave the "New user account" option selected if you are a new user.
10)For the Credits you only need 4 of them. I, initially, bought 5 so I still have one left
11)You'll receive a confirmation e-mail with a username and password. These are needed a bit later.
12)Extract the DC-Unlocker client to a fold and start it by clicking dc-unlocker2client.exe using the Windows Explorer (or any other file manager). To be sure you can also right-click the file and start the program using Administrator credentials.
13)Select in the right portion of the program the tab "Server" and enter the username and password you've received by mail. Check the "Remeber" box and click "Check login" to verify your account.
14)Click in the left portion of the program the dropdown list below "Select manufacturer" and choose "Huawei phones".
15)Leave the droplist "Select model" selected at "Auto detect (recommended)".
16)Grab your phone and open your dialer to type this code: *#*#2846579#*#* - this will get you into the service menu of the phone.
17)Tap 1. Background Settings -> USB Port Settings and select Manufacture Mode and than tap Close.
18)Put the phone done and let your PC install the newly found drivers.
19)If that's done click the Magnifying glass in the DC-Unlocker client software.
20)If all is connected correctly your phone is detected and a message in the white part of the program will tell you so. Also the "Select Model" field should display Huawei HiSilicon Kirin Android if the detection is succesfull.
**ready to read the unlock code! Yeah!
21)Click in the right portion of the DC-Unlocker client on the tab Unlocking.
22)Several buttons are visible but just click Unlock which could take a few moments before something is displayed in the white area at the bottom of the program window.
23)The unlock code can be copied and pasted - so please do copy the number to a text file and store it savely on your computer or in your cloud.
Fastboot Unlock Method
1).... Make sure you have latest HW adb drivers installed ( check by getting an adb shell to work )
2).... Download latest Android platform tools https://developer.android.com/studio/releases/platform-tools
3)... Decompress etc, get to fastboot dir, open a CMD there
5).... Boot into Download mode ( vol down while plugging USB into computer with drivers set up )
6).... fastboot oem unlock xxxxxxxxxxxxxx

Glad to read that the development of our Schubert isn't dead

massima said:
Glad to read that the development of our Schubert isn't dead
Click to expand...
Click to collapse
Not sure about that Seems barren in terms of real development. But in this case stock is a very good base, and in terms of memory usage very competitive with LOS, so in this case do not miss real open source code for the device.
The TWRP for our device is not great, and thats something i will get hands dirty fixing.

Any chance you could upload few pictures to show us how pc mode looks on smaller device, and will ever update your rom to 9.0?
Thanks in advance.

xabat said:
Any chance you could upload few pictures to show us how pc mode looks on smaller device, and will ever update your rom to 9.0?
Thanks in advance.
Click to expand...
Click to collapse
Yes sure will get a few screenshots out.
Will update to 9 when the dev community ( LP, Xposed, and all the other projects ) catches up.
At the moment we are prob a year away. ( Xposed barely works on EMUI 8 ).
Fenris is not your normal developers rom, its not about the latest version or untested beta code. Its about providing a stable platform for "alternative" open source code projects focused on Penetration testing, and pushing the boundaries.

any chance you could tell us how to activate desktop mode on stock rom ?

Are you rooted with the TWRP mentioned in the post ?
If not not much point in going further, plus its not an easy job mate, you good at messing around with your internal files ? Permissions and selinux contexts ? Edify script ? If so then you prob could do it. Otherwise best not even start.

vecna said:
Are you rooted with the TWRP mentioned in the post ?
If not not much point in going further, plus its not an easy job mate, you good at messing around with your internal files ? Permissions and selinux contexts ? Edify script ? If so then you prob could do it. Otherwise best not even start.
Click to expand...
Click to collapse
Yes, I unlocked bootloader months ago and I have root.

xabat said:
Yes, I unlocked bootloader months ago and I have root.
Click to expand...
Click to collapse
And twrp ? Cos your going to have to write an edify script to flash everything.

vecna said:
And twrp ? Cos your going to have to write an edify script to flash everything.
Click to expand...
Click to collapse
No I don't have twrp at the moment. I can't find working recovery for emui 9.
I wanted to see if desktop mode will work on android 9

xabat said:
No I don't have twrp at the moment. I can't find working recovery for emui 9.
I wanted to see if desktop mode will work on android 9
Click to expand...
Click to collapse
Well on EMUI 9 not happening, and not happening without TWRP anyway.
So why exactly are you on EMUI 9

I guess there is no external monitor support as I dident read that anywhere.
Is it a hardware limitation?

Well, this ROM is clean and awsome, i have the 10 inch tablet but i envy those who have the Schubert model as they can try this ROM??

Fenris is now at Beta 4, front post updated.

any development for this rom?

How To Guide June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]

Pixel 6 Pro [Raven]​
Updated May 13, 2023
Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes)
Someone reported it to Google (added a comment about 34.0.1 to the existing 34.0.0 report).
Spoiler
b0uNz said:
tried to flash the latest build of AncientOS with it, did not work. Back to r33.0.3 and it worked fine
Click to expand...
Click to collapse
Aphex13 said:
platform-tools_r34.0.1-windows is not functioning properly. Back to 33.0.3 we go...
Click to expand...
Click to collapse
budmannxx said:
Add me to the list of users that had a problem with platform-tools 34.0.1. I got into a bootloop after running flash-all.bat. Downgraded to 33.0.3, reran the new (old) flash-all.bat, and was all good.
Using 34.0.1, the phone never even got to the fastbootd part of the process
Click to expand...
Click to collapse
May 10, 2023 binary update of 34.0.1:
Homeboy76 said:
Update
I tested SDK Platform-tools r. 34.0.1 it is not fixed. There are still problems with fastbootd. Use SDK Platform-tools r. 33.0.3
Click to expand...
Click to collapse
Namelesswonder said:
Anyone that updated their platform tools and needs to downgrade can use these links.
Windows
https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip
Mac
https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip
Linux
https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google Pixel Update
Android Security Bulletins | Android Open Source Project
source.android.com
Regarding Developer Support Android 12 images, see @Lughnasadh's post here.
I am not linking directly to the Developer Support Android 12 images because I don't want them to be confused with Stable Android 12, and since the Developer Support images won't receive any OTAs...ever. They likely also will never be manually updated on the Developer Support images site, so they will forever be stuck with the security patch level they're currently on, which will become further out of date every month. You can Google search Developer Support Android images if you want to find them.
TL;DR regarding the PSA. If you update one slot to Android 13, you can fastboot reboot bootloader after and then fastboot --set-active=other to change slots in order to flash Android 13 to the new slot, but IF you have Android 13 on one slot and still have Android 12 (including Android 12 bootloader) on the other slot and you try to fully boot into Android 12, you will be permanently bricked and have to seek repair from Google. No one has yet found a way to repair this on our own. I will update if there is any progress. At least a small handful, and probably more, people have done this already.
At a minimum, do this first: fastboot flash bootloader --slot all bootloader-devicename-slider-1.2-3456789.img (change the name of the bootloader file to the one for your device), then you *should* be much safer than without doing that first. Also note that the bootloader is NOT the same as boot.img (kernel). The bootloader image file has "bootloader" in the filename.
IF you have already bricked your phone and the screen is blank - there is likely nothing we can do to help. You should seek to get a repair from Google, possibly under warranty.
You CANNOT go back to Android 12 Stable. It *seems* as if you can, but Android 12 will not work 100% correctly after updating to the Android 13 bootloader.
My tiny, early, very mini-review of Android 13 is here.
Note that this is mainly for the officially listed "Unlocked" Pixel 6 Pro, available directly from the Google Store. All of this will also apply to any other (carrier-specific) variant of the Pixel 6 Pro which you can achieve an unlocked bootloader on. This includes T-Mobile and AT&T variants. It's likely Verizon variants will never be able to unlock their bootloader, or if so it will require paying the right person to do so.
Feel free to ask about general questions, but for anything that's specific to your variant, you should use one of the other already existing threads. You'll find Verizon, AT&T, and T-Mobile-related threads in those respective search results.
Click to expand...
Click to collapse
Here there be dragons. I am not responsible for anything at all.
Spoiler: Warnings / FYI
Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device.​
Click to expand...
Click to collapse
Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, your local bank's app, or even the ability to install some apps like NetFlix. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12​
Click to expand...
Click to collapse
If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it.​
Click to expand...
Click to collapse
There are no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. You will also continue to receive updates (if you've merely unlocked the bootloader, you can take updates as normal) unlike Samsung, Sony, et cetera, which have permanent major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to manually update each month, and to keep root/re-root.​
Click to expand...
Click to collapse
All posts about Google Pay or banking will be reported to be deleted. Please keep this thread on-topic. There are at least one or two other How To Guide threads in this section in which folks discuss how to get around banking app restrictions when you're rooted or just have an unlocked bootloader. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12
Click to expand...
Click to collapse
If users persist in discussing banking apps in this thread, I will have this thread locked and only update this first post when there is new and updated information regarding the subjects of the title of the thread: Unlocking the Pixel 6 Pro bootloader, rooting, and TWRP. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12
Click to expand...
Click to collapse
Honorable mention to @Jawomo's aodNotify - Notification Light / LED for Pixel 6 Pro! (XDA link) / Notification light / LED for Pixel - aodNotify (Play Store link), which in my opinion restores useful functionality missing in most phones these days. It also solves some subjective issues some folks have with AOD (Always On Display), and/or solves/works around the problem where AOD is required for the optical fingerprint reader to work without the screen being on.​
Click to expand...
Click to collapse
Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
Official Google Pixel Update and Software Repair (reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro yet)
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
Lughnasadh said:
OEM unlocking in developer options needs to be toggled on. I don't "believe" you have to actually do the "fastboot flashing unlock" command.
Click to expand...
Click to collapse
ADB/Fastboot, Windows Drivers, and unlocking the bootloader (thanks @sidhaarthm for confirming unlocking the bootloader works as intended, be sure to thank him in his post)
You'll need this if you're going to unlock the bootloader on your Pixel 6 Pro: SDK Platform Tools (download links for Windows, Mac, and Linux). Note that you can find links to download the tools elsewhere, but I wouldn't trust them - you never know if they've been modified. Even if the person providing the link didn't do anything intentionally, the tools could be modified without them being aware. Why take a chance of putting your phone security further at risk?
You can alternately use the tools from the SDK Manager, but most of us will want to stick to the basic tools-only without the complications of the full development manager.
For Windows, get Google's drivers here Get the Google USB Driver (ADB will likely work while the phone is fully booted, but if you're like me, you'll need these drivers for after you "adb reboot-bootloader", to be able to use ADB and Fastboot.
Thanks to @96carboard for posting the details of unlocking the bootloader, be sure to thank him in his post. Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device. Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, or your local bank's app. If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it. My experience on my Pixel 1 was that there were no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. All of this should still be the case. You will also continue to receive updates. Unlike Samsung, Sony, et cetera, which have major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to keep root/re-root.:
The unlock process works like this:
1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on (you can put a SIM card if you want, you just don't have to).
2) When it starts harassing you to join Google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
3) Settings --> About --> Build number. Repeatedly tap it until it says you're a developer.
4) Back --> Network --> WiFi and connect it.
5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize on the phone when requested.
Using the Platform Tools previously mentioned in command line/terminal:
6) #
Code:
adb reboot-bootloader
7) #
Code:
fastboot flashing unlock
Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.
Official Instructions for Locking/Unlocking the Bootloader
Click to expand...
Click to collapse
roirraW edor ehT said:
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
Click to expand...
Click to collapse
Alekos said:
I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).
Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.
Fastboot/ADB Driver Interface - Official Download Link:
When flashing a full image or unlocking your bootloader, the fastboot interface is being used.
First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.
Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.
Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
Official Download Page
"Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"
It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).
Click to expand...
Click to collapse
Rooting-related​
@Az Biker's thread [How To Guide] [Pixel 6 Pro] Easy STEP BY STEP Unlock-Root.​
OR
@V0latyle's thread [How To Guide] Root Pixel 6 Pro with Magisk
Click to expand...
Click to collapse
No longer applies - Things that make rooting more complicated on Android 12
@V0latyle posted a new thread with some very important and fascinating information about the increased difficulty to root Android 12: Read this before rooting. Be sure to thank him there.
Click to expand...
Click to collapse
A list of the other important guides - be sure to thank the respective OPs
For all relevant guide threads just click the yellow "How To Guide" quick filter above the list of threads in the Pixel 6 Pro section.
Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub. The most recent Magisk Stable is what's recommended these days.
@sean222's thread Restore WiFi and Cellular Data in Quick Settings (Root Required)
@rickysidhu_'s thread HBM (High Brightness Mode)
@gururoop's thread Probable method to upgrade every month, without wiping data and retaining root
@rickysidhu_'s thread Limit Charge
@Typhus_' thread [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
@siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ - a mod that compliments @Typhus_' mod above, and may eventually completely replace it.
@TotallyAnxious' thread [MOD] Collection of "Anxious" Modules for Pixel 6/Pro Series
Every single one of @foobar66's posts.
TWRP (not made for the Pixel 6 Pro yet - will update when it has)
I would guess that this should be the appropriate URL for official TWRP custom recovery for the Pixel 6 Pro, but who knows when/if that will actually be made available, and it may become available unofficially in these forum sections before being made official. I'll adjust this URL as needed. https://twrp.me/google/googlepixel6pro.html.
Click to expand...
Click to collapse
Custom kernels for stock ROM(s)
@Freak07's Kirisakura-Kernel for the Pixel 6 Pro (and possibly the Pixel 6)
@DespairFactor's Despair Kernel (I believe also for both the P6P and P6)
@tbalden's CleanSlate Kernel
@acuicultor's Radioactive Kernel
Click to expand...
Click to collapse
Factory Images (requires an unlocked bootloader)
It's also handy to have to the full official firmware available, whether it's to recovery from accidents or for actual development. Note the official link to the general Factory Images for Nexus and Pixel Devices page. The following link goes directly to the Pixel 6 Pro (Raven) section: Pixel 6 Pro Factory Images. I prefer to actually bookmark a link to the device listed immediately below the device I want the firmware for, because Google dumbly (in my opinion) puts the latest firmware at the bottom of the list for each particular device, and that ends up making you scroll a lot after a year or two of monthly updates.
Note: You can still get the December 2021 Factory Images and OTA from this thread, if you need them for any reason: Alternate links to December - all full factory images and OTAs available
Click to expand...
Click to collapse
Full OTA Images (doesn't require an unlocked bootloader)
Full OTA Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
The usefulness of having Verity and Verification enabled (now that it's not needed for root) - post #2 below.
Regarding P6P 5G model numbers and capabilities - post #3 below.
List of all Pixel monthly security bulletins and Play System Updates - post #4 below.
How I root and update (which is identical whether rooting the first time or updating):
Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)
Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)
Extracted the new boot.img
Copied new boot.img to the phone
Patched the new boot.img with Magisk Stable
Renamed Magisk'd boot.img so I know what version of firmware it's for
Copied the Magisk'd boot.img back to the computer
Disabled all my Magisk Modules
Removed the "-w " from the flash-all.bat
Re-edited the flash-all.bat to verify I saved it with the "-w " taken out
Open a Command Prompt, navigated to S:\platform-tools
adb reboot bootloader
flash-all.bat
Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)
adb reboot bootloader
fastboot flash boot kernel.img (renamed Magisk'd boot.img)
fastboot reboot
Unlock, check everything's working
Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue
Reboot, unlock, made sure everything's working
Back to modding!
Click to expand...
Click to collapse
I may append these first four posts with further useful information or links as needed.
Click to expand...
Click to collapse

Disabling Verity and Verification isn't required except for use with some custom kernels, but just rooting those custom kernels with the latest Magisk Stable v24.1 or higher should make them not require disabled Verity and Verification anymore.
A reminder that disabling Verity and Verification, at least if you've never disabled them before, will cause you to need to factory reset the device otherwise there will be corruption.
prokiller1199 said:
if you didnt disable before then it is enabled since the beginning. Disabling requires a full wipe.
It will show this image if you try to disable.
You can also verify it using adb shell with:
adb shell
su
avbctl get-verity
avbctl get-verification
{
"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"
}
Click to expand...
Click to collapse
The usefulness of having Verity and Verification enabled (now that it's not needed for root but IS still required for some custom kernels):
jwoegerbauer said:
1. DM-Verity ( VB 1.0 ) verifies /system and /vendor - it was introduced with Android 4.4, modified with Android 7
2. Android Verified Boot ( VB 2.0 aka AVB ) additionally verifies /boot - it was introduced with Android 8, works on Project Treble enabled devices
Both are running a hash on the memory blocks mentioned of your device to ensure the integrity of your software and help prevent rootkits and the like.
If you disable VB 1.0 and/or VB 2.0 your Android device becomes vulnerable to malware of any type: IMO only those do it who do not care about the built-in protection.
Click to expand...
Click to collapse
V0latyle said:
Yes - this is covered on Android Source.
The basics:
Android Verified Boot ensures that the boot code is legitimate, by using a boot image "signature" compared to a signature stored in the key registry.
Dm-verity is a method by which the code on the block devices is hashed; this hash is then compared to a reference hash to determine its authenticity before the image is loaded, thereby preventing rootkits from declaring themselves legitimate.
Vbmeta verification is a method of storing those reference hashes to which the generated hashes are compared. This can be and often is used for any critical partition, such as /boot and /system.
These aren't new concepts and indeed have been integral to Android for some time. What is new is how the Android 12 AVB headers were handled.
We still don't know exactly where in the process the problem occurred when trying to run custom boot images with Android 12. I suspect that the issue wasn't custom software itself - after all, you could still flash a custom ROM and run it without issues - but rather, trying to use a modified boot image with otherwise stock Android 12 system. Don't take my word for it, though, because I don't know for sure.
Click to expand...
Click to collapse
Freak07 said:
It has nothing to do with the kernel itself. The anykernel.zip uses magiskboot to "repack" the kernel during the flashing kernel.
Click to expand...
Click to collapse

Regarding P6P 5G model numbers and capabilities:
There are three hardware versions:
G8VOU (AU, US); also listed as G8V0U - zero instead of "oh" on some sites, Google shows the former, G8VOU) - has mmWave 5G support
GF5KQ (JP) - has mmWave 5G support
GLUOG (CA, DE, FR, GB, IE, TW) - no mmWave 5G support
For instance, my factory unlocked direct from Google in the United States Pixel 6 Pro 512 GB is a G8VOU. As far as I know, all other variations in each individual phone are controlled by software (which firmware is loaded) and over the internet (which IMEIs are Carrier Unlocked or not, and OEM Unlockable or not).
Check carriers, their 5G networks & their 5G roaming support for Pixel phones. Make sure and choose your country from the drop-down to see the list of carriers beneath.
There's also the section above that Learn which Pixel phones can work with which kinds of 5G.

My personal advice for how to get your device back up and running like you had it previously after a factory reset:
I use Nova Launcher Prime, so I do backups anytime I change my home screen or app drawer/tabs setup, so widgets and app icons and other Nova-specific configurations are easier to restore.
Go to Android Settings and use Settings' search box for Backup. Make sure that your Google account is set up to backup your apps (and app data for the apps that developers have configured to use Google's Backup API). Make sure things are backed up. Note, this doesn't backup the apps themselves, only the list of apps, so only applies to apps installed from the Play Store. As I said in parentheses, developers have to choose to integrate Google's Backup API into their app, and those apps only will get their app data backed up into Google's cloud.
If you're rooted also, then you could use something like Swift Backup to backup to the cloud. I do so, although I still restore as much as possible through Google's backup, and I only restore through Swift on a case-by-case basis, as needed when I discover an app that's tough to set back up doesn't have it's data restored by Google.
If you've used Google Photos to backup your photos to Google's cloud, then hit the button in Google Photos to free up space. This will automatically and only delete your local copies of photos and videos that it's already backed up.
Once that ^ is done, look at your internal storage with your favorite File Manger and see if there's anything left that you want to back up manually, since a factory reset will wipe everything. Copy them to your computer or a flash drive.
When you're just starting the out of the box setup after the reset, when it asks you if you want to use a cable to restore things from an old phone, choose No, and that will lead you to Google's cloud backup where you can choose to restore everything, or you can select what you want to restore.
I think you can figure out the rest.

Reserved.

Reserved.

Reserved.

Reserved.

If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.

dj24 said:
If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.
Click to expand...
Click to collapse
This one's kinda long for what it is, and this is for the Pixel 1, but it should be similar for the Pixel 6/Pro. I won't add it to the first post just yet in case there are differences, and I don't want to recommend something I can't actually try on the 6 Pro (since I won't get mine for likely another two days). Unlocking the Bootloader of the Pixel and Pixel XL
Good luck!

roirraW edor ehT said:
This one's kinda long for what it is, and this is for the Pixel 1, but it should be similar for the Pixel 6/Pro. I won't add it to the first post just yet in case there are differences, and I don't want to recommend something I can't actually try on the 6 Pro (since I won't get mine for likely another two days). Unlocking the Bootloader of the Pixel and Pixel XL
Good luck!
Click to expand...
Click to collapse
This is great. I won't be getting mine for a while as well so please come back and update this thread.

dj24 said:
If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.
Click to expand...
Click to collapse
Generally YouTube video guides for software related things aren't particularly helpful, as they can often get outdated very quickly; especially in the early days of a device as they can't be updated when new things are found out.
It would probably be best to carefully read through guides

@sidhaarthm reports here (be sure to thank him on his original post):
Bootloader successfully unlocked. I will just run everything stock for now - this is just so I don't have to wipe the device later after I have completed full setup and transferred all my data.
View attachment 5441915
Click to expand...
Click to collapse

dj24 said:
This is great. I won't be getting mine for a while as well so please come back and update this thread.
Click to expand...
Click to collapse
FYI, I'm reminded by several members in these forums that unlocking the bootloader (the first step before being able to root your Carrier-Unlocked Pixel 6 Pro) wipes the device - so does re-locking it. So I highly recommend unlocking it as the first step when you get the phone, otherwise, you'll have to back up anything that doesn't normally get backed up, and go through the initial setup process again. Not a big deal for some, but would likely not be optimal for a new user.
Instructions for Locking/Unlocking the Bootloader (note that unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device).
Click to expand...
Click to collapse

roirraW edor ehT said:
FYI, I'm reminded by several members in these forums that unlocking the bootloader (the first step before being able to root your Carrier-Unlocked Pixel 6 Pro) wipes the device - so does re-locking it. So I highly recommend unlocking it as the first step when you get the phone
Click to expand...
Click to collapse
This! It's the first thing you should do out of the box if you plan on rooting later.

@V0latyle posted a new thread with some very important and fascinating information about the increased difficulty to root Android 12: Read this before rooting. Be sure to thank him there.

That's great news about Unlocking the bootloader! I'll be doing that first thing to be ready for the future...

Does this mean to say there is no OEM unlocking switch in the developer options screen?

biTToe said:
Does this mean to say there is no OEM unlocking switch in the developer options screen?
Click to expand...
Click to collapse
There is, its there and you need to flip it.

The unlock process works like this;
1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.
2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
3) Settings --> About --> Build number. Tap it until it says you're a developer.
4) Back --> Network --> Wifi and connect it.
5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.
6) # adb reboot-bootloader
7) # fastboot flashing unlock
Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.

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) ???