Tested with D838 - 16GB
1. If you are not in stock rom, using computer flash with LG Flash Tool 2014. Using D83820d_00.kdz rom. (Lollipop rom)
2. Once done, enable developer option, enable USB debug mode, and connect to computer MTP option.
3. Root the device using one-click root software for LG G PRO 2.
http://forum.xda-developers.com/lg-g...lipop-t3056951
4. After rooted, restart the phone and copy the cyanogenmod 13 zip file to internal SD main directory of the phone.https://mega.nz/#!MNNQWABB!tsc_dxAW8_WWvfyVOGflOoQRJjk3l3z6mqMro8_cojQ
5. Then, we need to flash with custom recovery - D838 LP Recovery. This is chinese version. Connect to USB again and unzip the RAR then run the bat file.
https://www.dropbox.com/s/c6yfckg1gakys5u/D838 lp recovery.rar?dl=0
https://drive.google.com/file/d/0B4k...ew?usp=sharing
6. After flashed the custom recovery, it will start up at recovery mode. 1)Clear the cache, 2)clear the dalvik cache, 3)clean/erase phone for new rom.
7. The flash the zip file of cyanogenmod 13 zip. And restart.
8. The phone will start with CM 13 now. You need to visit to gapps in order to install google play. Select ARM, Android 6 and PICO option to download the zip file.
http://opengapps.org/
9. Off phone and boot up in recovery mode again (Press vol up and power button at the same time). Then flash the zip file.
10. Once done, boot up the phone as usual. Then you will find Google Play in the CM 13 OS. Register google mail to complete.
11. Now when you download safetynet test, you found it failed because the phone has root feature in Developer Option and SelinuxModeChanger is exist in CM13.
12. Goto Developer Option to enable root. Then install "System app remover (ROOT)" from google play (grant root priv). Once installed, use this app to uninstall SELINUXModeChanger.
13. Once uninstalled, install SuperSU from google play (grant root priv). Go to setting of SuperSU and choose unroot phone. The SuperSU will remove root feature from Developer Option.
14. Now your CM 13 is clean. Rerun the safetynet to test again. It should be GREEN this time.
The safetynet test is important to ensure your phone is totally clean from alter and can install sensitive application.
Cant download
Hi,
Sorry I can't download the custom recovery file mentioned in step 5. Any help please...
TIA.
bkcheah75 said:
Tested with D838 - 16GB
1. If you are not in stock rom, using computer flash with LG Flash Tool 2014. Using D83820d_00.kdz rom. (Lollipop rom)
2. Once done, enable developer option, enable USB debug mode, and connect to computer MTP option.
3. Root the device using one-click root software for LG G PRO 2.
http://forum.xda-developers.com/lg-g...lipop-t3056951
4. After rooted, restart the phone and copy the cyanogenmod 13 zip file to internal SD main directory of the phone.https://mega.nz/#!MNNQWABB!tsc_dxAW8_WWvfyVOGflOoQRJjk3l3z6mqMro8_cojQ
5. Then, we need to flash with custom recovery - D838 LP Recovery. This is chinese version. Connect to USB again and unzip the RAR then run the bat file.
https://www.dropbox.com/s/c6yfckg1gakys5u/D838 lp recovery.rar?dl=0
https://drive.google.com/file/d/0B4k...ew?usp=sharing
6. After flashed the custom recovery, it will start up at recovery mode. 1)Clear the cache, 2)clear the dalvik cache, 3)clean/erase phone for new rom.
7. The flash the zip file of cyanogenmod 13 zip. And restart.
8. The phone will start with CM 13 now. You need to visit to gapps in order to install google play. Select ARM, Android 6 and PICO option to download the zip file.
http://opengapps.org/
9. Off phone and boot up in recovery mode again (Press vol up and power button at the same time). Then flash the zip file.
10. Once done, boot up the phone as usual. Then you will find Google Play in the CM 13 OS. Register google mail to complete.
11. Now when you download safetynet test, you found it failed because the phone has root feature in Developer Option and SelinuxModeChanger is exist in CM13.
12. Goto Developer Option to enable root. Then install "System app remover (ROOT)" from google play (grant root priv). Once installed, use this app to uninstall SELINUXModeChanger.
13. Once uninstalled, install SuperSU from google play (grant root priv). Go to setting of SuperSU and choose unroot phone. The SuperSU will remove root feature from Developer Option.
14. Now your CM 13 is clean. Rerun the safetynet to test again. It should be GREEN this time.
The safetynet test is important to ensure your phone is totally clean from alter and can install sensitive application.
Click to expand...
Click to collapse
Get Edxposed, Magisk, and GPay to work together.
1. Install or make sure you are on latest Magisk Manger (7.5.1 or newer)
2. Install or make sure you are on latest Magisk (20.3 or newer)
3. Hide the following in Magisk Hide
-Google Pay
-Google Play services, only select the following
-com.google.android.gms
-com.google.android.gms.unstable-Google Play Services for AR
-Google Play Store, select everything but com.android.vending
-Google Services Framework
-Nfc Service
4. Install the following modules
-GPay SQLite Fix (Full Edition)
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176-SQLite for Arm aarch64 devices via Magisk Manager
-hardwareoff by @Displax (Thanks to @Kris Chen for making me aware of it) or use MagiskHide Props to set check to basic and fingerprint to Pixel 3a
5. Reboot
At this point make sure you have GPay working before installing edxposed. If for some reason you are unable to use GPay try deleting data for Google Play Services/Google Play Store/Google Pay
After you confirm that GPay is working then move on to installing edxposed
1. Download and install Riru - Core via Magisk Manager
2. Download Edxposed Manager (4.5.4 or newer) (Don't Install Yet!)
https://github.com/ElderDrivers/EdXposedManager/releases/3. Download Edxposed (4563) (Don't Install Yet!)
I'm personally using the YAHFA version.
https://ci.appveyor.com/project/ElderDrivers/edxposed/history
4. Once you have all these files downloaded turn on Airplane Mode and install the Edxposed Magisk Module (Magisk -> Modules and press the + sign, find the downloaded zip and select it, Magisk will install it) and Edxposed Manager APK and reboot
5. Once booted up remain in Airplane Mode
6. Open Edxposed Manger and go to Settings and turn on "App List mode"
7. Exit and reopen Edxposed Manager
8. Go to Applications on the side menu (should say "Black List" on top) and select the following apps
-Google Pay (may not be needed)
-com.android.nfc.auto_generated_rro_product_
-com.android.nfc.auto_generated_rro_vendor_
-Nfc Service
-pixelnfc (new in Android 11)9. Go to Settings on the side menu, at the bottom of settings find and enabled "Pass SafetyNet"
10. Reboot and turn off Airplane Mode
11. Optional* Hide Magisk Manager
Note. Steps 4-9 should be done in Airplane Mode, this will keep anything tripping safety net during the setup process.
eg1122 said:
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Click to expand...
Click to collapse
Here are some screen shots of it working
Thanks for this @eg1122.
After soft-bricking on my first try, I've been wondering what the working version combination is.
The one that is available to me is an older version maybe that's what caused my bootloop? Why does my screenshot look like crap?
Sent from my Pixel 4 XL using Tapatalk
View attachment 4858559
Finally got exposed/gravitybox installed.
Anyone know any tweaks for the home screen grid size?
Sent from my Pixel 4 XL using Tapatalk
xdeslitx said:
Finally got exposed/gravitybox installed.
Anyone know any tweaks for the home screen grid size?
Click to expand...
Click to collapse
Check my thread in Themes and Apps section
https://forum.xda-developers.com/pixel-4-xl/themes/substratum-pixel-launcher-editor-t3990687
xdeslitx said:
The one that is available to me is an older version maybe that's what caused my bootloop? Why does my screenshot look like crap?
Click to expand...
Click to collapse
Use the link I posted to get 0.4.5.5
eg1122 said:
Check my thread in Themes and Apps section
https://forum.xda-developers.com/pixel-4-xl/themes/substratum-pixel-launcher-editor-t3990687
Click to expand...
Click to collapse
That looks pretty nice...thanks
Sent from my Pixel 4 XL using Tapatalk
eg1122 said:
I've been reading a lot of our forums and many are asking about Xposed. Decided to make this thread to try to keep all discussion in one place and make it easy to find information.
I am currently running Xposed and I'll lay out the steps I took to get it working.
1. In Magisk Manager find and install Riru - Core v19.5
2. Reboot
3. Download and install Riru - EdXposed v0.4.5.5_beta (YAHFA) via Magisk
https://github.com/ElderDrivers/EdXposed/pull/354
4. Install EdXposed Installer
https://github.com/solohsu/XposedIn...d_v2.2.5/EdXposedInstaller_v2.2.5-release.apk
5. Reboot
6. Enjoy
Click to expand...
Click to collapse
This won't trip Safety net right i assume?
varun.gid said:
This won't trip Safety net right i assume?
Click to expand...
Click to collapse
Nope
Disregard...
How does using Xposed affect monthly security updates? Do you have to disable or whatever? I'm not sure I want to do this, I'd rather not cause problems.
Got xposed installed and running thanks to this thread, but the module download screen is empty - just shows the refreshing icon and "module list will be loaded in a few seconds" forever. Anyone else seeing this?
gettinwicked said:
How does using Xposed affect monthly security updates? Do you have to disable or whatever? I'm not sure I want to do this, I'd rather not cause problems.
Click to expand...
Click to collapse
I disable big modules like Xposed when I update. Then re-enable them once update is completed. I'll put a step by step here.
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
tardis_42 said:
Got xposed installed and running thanks to this thread, but the module download screen is empty - just shows the refreshing icon and "module list will be loaded in a few seconds" forever. Anyone else seeing this?
Click to expand...
Click to collapse
Try the following
Try clearing app data and cache for edxposed.
Uninstall Edxposed installer and reinstall
Reinstall any Xposed modules not showing up
eg1122 said:
Try the following
Try clearing app data and cache for edxposed.
Uninstall Edxposed installer and reinstall
Reinstall any Xposed modules not showing up
Click to expand...
Click to collapse
Clearing data did it, thanks!
How do you install edexposed via magisk? I haven't rooted since the P1 so I'm out of the loop here sorry.
madgooner2810 said:
How do you install edexposed via magisk? I haven't rooted since the P1 so I'm out of the loop here sorry.
Click to expand...
Click to collapse
In Magisk, go to Modules and press the + button, then find the zip and select it.
Thanks...
FYI, Riru - EdXposed v0.4.6.0_beta (YAHFA) via Magisk also works.
@eg1122 great instructions worked perfectly. Thanks!
This is an advanced guidance.
I will explain exact procedure presuming other things are already known for those who are know what are they doing.
Therefore, if anything goes wrong I don't feel responsible for whatever you do.
1. Unlock bootloader
2. Device will, format itself. Do initial setup without setting anything because you will need it to format again.
3. Boot device and turn on OEM unlock and USB debugging in to developer options in system settings.
4. Reboot device again.
5. Download stock firmware (you can use FRIJA or SAMFIRM tool from XDA.)
6. Unpack firmware zip
7. Connect tablet to your PC
8. From folder of unpacked firmware COPY AP file to your tablet SDCard/Documents folder.
9. Download and install latest Magisk Manager.apk on tablet.
10. Open Magisk Manager you will see "Magisk is NOT installed" in red letters but no problem.Set it EXACTLY like on picture 1.
11.Click "install" and you will see screen on picture 2.
12. Select "SELECT AND PATCH A FILE" and select that AP firmware file you previously copied from your PC
13. Magisk will start to patch a file. When patching is done...
14. Close Magisk Manager and open your SDCard/Documents folder on tablet. You will find there "MAGISK_PATCHED.TAR" file.
15. Copy that file from tablet to PC
FLASHING
Turn off tablet and put it in download mode
1. Open on PC patched ODIN 13.3 or 13.4 and UNTICK "reboot automaticly" on ODIN settings
2. Select files for flashing BL to BL, CP to CP, CSC to HOME_CSC....
BUT EXCEPT ORIGINAL AP FILE SELECT "MAGISK_PATCHED.TAR" FILE !
3. Flash all files to your tablet and disconnect from PC when ODIN finished
4. Reboot tablet into recovery and format data and cachee ! Restart tablet and wait few minutes to load
5. Set up tablet as usually.
6. Install Magisk Manager.apk and open it...It will do some patching updates then reboot itself.
7. Open Magisk Manager again and install Magisk zip from manager. Manager will root and reboot device itself.
8. You have a root without TWRP
.
To keep this guide short, same video procedure I found here...It is for S10+ but applicable for this tablet as well.
ROOT WITH MAGISK
.
Thank for that clarity .. i just get an Tab s6 and i needed i simple and recent tutorial.
This guide worked perfectly. The one with twrp didn't.
Thank you.
This didn't work for me.
3. Flash all files to your tablet and disconnect from PC when ODIN finished
4. Reboot tablet into recovery and format data and cachee ! Restart tablet and wait few minutes to load
I can't get into Recovery Mode to format. It freezes on the boot logo, I'll hold Volume Down + Side Key to power off, Volume Up + Side Key to boot into Recovery Mode but it just tried to boot normally and freezes on the boot logo.
Is it better to root first or flash TWRP.
EDIT: Duh!!
tin2404 said:
This is an advanced guidance.
I will explain exact procedure presuming other things are already known for those who are know what are they doing.
Therefore, if anything goes wrong I don't feel responsible for whatever you do.
1. Unlock bootloader
2. Device will, format itself. Do initial setup without setting anything because you will need it to format again.
3. Boot device and turn on OEM unlock and USB debugging in to developer options in system settings.
4. Reboot device again.
5. Download stock firmware (you can use FRIJA or SAMFIRM tool from XDA.)
6. Unpack firmware zip
7. Connect tablet to your PC
8. From folder of unpacked firmware COPY AP file to your tablet SDCard/Documents folder.
9. Download and install latest Magisk Manager.apk on tablet.
10. Open Magisk Manager you will see "Magisk is NOT installed" in red letters but no problem.Set it EXACTLY like on picture 1.
11.Click "install" and you will see screen on picture 2.
12. Select "SELECT AND PATCH A FILE" and select that AP firmware file you previously copied from your PC
13. Magisk will start to patch a file. When patching is done...
14. Close Magisk Manager and open your SDCard/Documents folder on tablet. You will find there "MAGISK_PATCHED.TAR" file.
15. Copy that file from tablet to PC
FLASHING
Turn off tablet and put it in download mode
1. Open on PC patched ODIN 13.3 or 13.4 and UNTICK "reboot automaticly" on ODIN settings
2. Select files for flashing BL to BL, CP to CP, CSC to HOME_CSC....
BUT EXCEPT ORIGINAL AP FILE SELECT "MAGISK_PATCHED.TAR" FILE !
3. Flash all files to your tablet and disconnect from PC when ODIN finished
4. Reboot tablet into recovery and format data and cachee ! Restart tablet and wait few minutes to load
5. Set up tablet as usually.
6. Install Magisk Manager.apk and open it...It will do some patching updates then reboot itself.
7. Open Magisk Manager again and install Magisk zip from manager. Manager will root and reboot device itself.
8. You have a root without TWRP
.
To keep this guide short, same video procedure I found here...It is for S10+ but applicable for this tablet as well.
ROOT WITH MAGISK
.
Click to expand...
Click to collapse
Before step 10 ensure that you have a Wi-Fi connection. I think Magisk requires it. Magisk would not produce the drop-down till I connected to the internet. Then everything worked fine.
Good man, thanks so much!
Sent from my Pixel 4 XL using Tapatalk
I wish this worked for the TMobile version
noxarcana said:
This didn't work for me.
3. Flash all files to your tablet and disconnect from PC when ODIN finished
4. Reboot tablet into recovery and format data and cachee ! Restart tablet and wait few minutes to load
I can't get into Recovery Mode to format. It freezes on the boot logo, I'll hold Volume Down + Side Key to power off, Volume Up + Side Key to boot into Recovery Mode but it just tried to boot normally and freezes on the boot logo.
Click to expand...
Click to collapse
You need to restart tab after flashing BUT again in DOWNLOAD MODE...not in recovery ! Then flash TWRP and restart in twrp recovery.You need to untick AUTO REBOOT in Odin before flashing TWRP.
Not able to shutdown
After rooted with Magisk,my Tab S6 is not able to shutdown,no matter which methode I use,it just restart itself.
Does anyone have this issue?
worked perfect on oneui 3.1 aswell thank you
I rooted my Galaxy Tab S6 using the Magisk-only method after updating to Android 11. I had trouble with the post-Odin step (pressing power and volume up right after screen turns off) so I had to do the flash a couple more times before I got that right, and everything shows as rooted now.
However, my 256GB internal storage is only showing up as 32GB! Is that a firmware thing, or a partitioning thing? How can I fix it?
Used ther same method on my rooted tab with the May update (T865XXU4CUE1_T865OXM4CUE1_DBT) - magisk-patch AP, flash all files in Odin, after reboot the device is rooted.
BUT after another reboot (or rather shutdown and boot), root access is lost and cannot be restored in any way until I re-flash the device with the same firmware again.
Any solution to this?
6. Install Magisk Manager.apk and open it...It will do some patching updates then reboot itself.
7. Open Magisk Manager again and install Magisk zip from manager. Manager will root and reboot device itself.
Click to expand...
Click to collapse
This never happens. I even uninstalled Magisk Manager after patching, flashed the firmware, reinstalled the latest Canary Manager, still no patching or reboot happening.
Edit: just rebooted and shutdown a few times, root sticks. Before, I held VolUp as described in many guides until the "secured by Knox" logo appears, now didn't touch any button except Power.
Oh well...
[Guide] Root Pixel 3 XL Android 12 Unlock/Lock Bootloader + Install/Flash Custom ROMs
Introduction
This Guide is for Pixel 3 XL owners that want to Instal a Custom ROM, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel 3 XL phone with an unlocked bootloader.1
A Computer with the latest working SDK Platform-tools 33.0.3 installed.
Important Notes:
a. Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.
b. Update Platform Tools, regularly, for optimal performance.
c. Need Google's USB Drivers for your Pixel Phone?
Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.
Update Platform Tools, regularly, for optimal performance.
Need Google's USB Drivers for your Pixel Phone?
NEW
Waiting . . .
Update(s)
Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
Magisk Beta - Magisk v26.1.apk 11 Apr
Magisk Canary - app-release_a8c4a33e-26103.apk 23 Jun
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta -
app-release
Magisk Stable - Magisk v26.1.apk 11 Apr
SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.3 17Jun
SDK Platform-tools 33.0.3 Aug 2022
Custom Kernels
Note: If you want to use a Custom Kernel, please follow the Installation instructions in the OP of the Custom Kernel you want to install.[[/I][/U]a. Google Pixel 3 XL ROMs, Kernels, Recoveries, & Otherb. ElementalX Kernel Manager
My Other Guides
Pixel 7 Pro
Pixel 6
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 1 XL
Credits/Thanks/Recognitions
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
Notes:
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes:
After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Use the Android flash tool:
select Wipe => Force Flash Partitions => Lock Bootloader.
Lock Bootloader
If your phone is not 100 percent stock do Return Phone to Stock. If you don't you may brick your phone.
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt in the SDK Platform- tools folder, and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Install/Update Factory Image keep data or wipe data
Important Note(s):
If you haven't updated your phones Factory image in awhile. It is not necessary to flash all the images in succession. Flash the latest Factory image.
If you are uncomfortable manually flashing the factory image, Try installing it with PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones..
If the previous factory image was rooted (you used Magisk to patch the boot.img of the previous factory image). Open Magisk manager and disable all Magisk modules.
If you want to Upgrade to Android 13 or update the Factory Image without wiping your phone: Do Flash Factory Image Keep Data (below).
Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 3 XL - crosshatch.
If you get an error: while flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
If you phone bootloops
Press the Power button until the phone turns off.
Press the Power and Volume Down to boot the bootloader.
Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
Then type: fastboot Reboot
If you are uncomfortable manually flashing the factory image. Try PixelFlasher by badabing2003.
Please post Comments/Discussions/Questions about PixelFlasher on that thread.
Backup your data
Download the latest Factory Image: Pixel 3 XL - crosshatch to your Computer.
Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the flash-all.bat file.
Flash Factory Image Keep Data
Navigate to the folder you extracted the Factory Image to and open the flash-all.bat file with a file editor i.e., Notepad app and edit the flash-all.bat file:
Change this line: fastboot -w update image-crosshatch-aa1a.999999.999.zip
to this: fastboot update image-crosshatch-tp1a.999999.999.zip
Note: This removes the -w so your Internal Storage will NOT be wiped.
After, you have edited the flash-all.bat file. Copy/Move these files to the [U[Platform-tools[/U] folder:
bootloader-crosshatch-....img
flash-all.bat
image-crosshatch-....zip
radio-crosshatch-....img
On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Flash Factory Image Wipe Data
This will wipe your phone's Internal Storage.
Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
bootloader-crosshatch-....img
flash-all.bat
image-crosshatch-....zip
radio-crosshatch-....img
On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Setup phone
Enable Developer Mode and USB Debugging
Setup => About phone => Tap Build number 7 times or untill you see you are a 'Developer'.
Setup => System => Developer options => Enable Developer options => enable USB Debugging
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
(NEW) Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.
Before you start
Backup your data
Make sure that there is no pending OTA update, by going to Settings > About phone > System updates, which should say Your system is up to date.
Download the latest Factory and OTA image for your device.
Verify the checksum of the Factory and OTA image. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is shown next to the download link.
Extract the boot/init_boot.image from the Factory image:
Extract the Factory Image file that you downloaded (crosshatch-a9a9a.999999.999-factory-99a9a99a.zip) into a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-crosshatch-aa9a.999999.999.zip) into a folder. The stock boot/init_boot.img file should be in this folder.
Patch the boot/init_boot.img:
Open the Magisk Alpha/Beta/Canary/Delta/Stable App
The Update Channel should be set to Alpha/Beta/Canary/Delta/Stable, depending on the version you installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot/init_boot.img file you extracted from the factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot/init_boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
Reboot
Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume button up once. The recovery text menu will appear.
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
Run the following command: adb devices check that your device shows up with "sideload" next to its name.
Sideload the OTA zip file
Connect the phone to the PC via USB cable
On the phone: boot bootloader/fastboot mode
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type:
adb sideload crosshatch-ota-tq3a.230605.012-f32168af.zip and press enter.
Once sideloading finishes, reboot the phone by choosing Reboot system now option on the The recovery text menu.
Sideload the OTA zip file to the other slot and Root it.
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should appear on screen.
Access the recovery menu:
Hold the Power button and press Volume up button once.
The recovery text menu will appear.
Enter sideload mode:
Select the Apply update from ADB option on the recovery text menu.
[*]Sideload the OTA zip file
Connect the phone to the PC via USB cable
On the phone: boot bootloader/fastboot mode
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: adb sideload crosshatch-ota-tq3a.230605.012-f32168af.zip at the prompt and press enter.
Once sideloading finishes, choose Reboot system now option on the The recovery text menu.
Flash boot/init_boot.img to root
On the phone: Boot bootloader/fastboot mode
Connect the phone to the Computer with USB cord.
On the PC:
Open a Command Prompt in the SDK Platform-tools folder.
Type: fastboot flash boot/init_boot magic_patched....img at the Prompt and press enter.
Type: fastboot reboot at the Prompt and press enter.
Disconnect the phone from the PC.
Notes:
This slot is bootable and rooted. The other slot is bootable without root.
Check that the other slot is bootable and not rooted
On the Phone: Boot bootloader/fastboot mode
Connect the phone to the PC via USB cable
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: fastboot --set-active=other at the prompt and press enter.
Type: fastboot reboot and press enter.
Disconnect the phone from the PC.
To return to the other slot that is bootable and rooted
On the Phone: Boot bootloader/fastboot mode
Connect the phone to the PC via USB cable
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: fastboot --set-active=other at the prompt and press enter.
Type: fastboot reboot and press enter.
Disconnect the phone from the PC.
Done!
Extract Files from Factory Image/Flash boot.img
Extract Files from Factory Image
Extract flash-all.bat and boot.img file
Download the latest Factory image to your phone.
Extract the Factory Image file (crosshatch-r2d1a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
Open the folder you extracted the Factory image to and, extract the Image file (image-crosshatch-aa9a.999999.999.zip) into the folder. The, stock, boot.img file should be in this folder.
Flash boot.img
Flashing the boot.img removes root.
Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Pass SafetyNet with Magisk moduke.
Pass Safety Net with SafetyNet Fix with Magisk module
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
Install Displax's safetyNet Fix
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the Displax's SafetyNet Fix file you downloaded.
Tap the Displax's SafetyNet Fix file.
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk.
Enable Denylist
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
(Optional) Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for any app that needs Device Certification i.e., Google Play Services, Google Pay, Google Wallet, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification
It may take 24 hours for Device Certification to be updated.
Note: If after completeting Get Device Certified and Check Device Certification you've waited 24 hours your Device is not Certifed or your Device is Certified and certain Google Store apps (Google Pay, NetFliks, etc.) are not working. Use the Play Integrity API Checker app or the TB Checker - Safetynet and Root app to verify you are passing Play Integrity.
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Install/Update Magisk Modules
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Androidacy Module Manager
Open Androidacy Module Manager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Androidacy Module Manager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 11 (R) T.W.R.P
~ ~ ~ Part III - OTHER ~ ~ ~
Custom ROMs
Need help with a Custom ROM?
If you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread or try installing it with PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones..
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMs
Google Pixel 3 XL ROMs, Kernels, Recoveries, & Other
Other Custom ROMs
[ROM] [Android 13] [blueline/crosshatch] ArrowOS 13.0 | UNOFFICIAL | BETA by ReallySnow
Themes, Apps, and Mods
Google Pixel 3 XL Themes, Apps, and Mods
T.W.R.P.
Android 12 - 370_12.0... 10Oct
Attempted the update last night, when flashing Magisk Canary Patched boot.img, the touchscreen is non-responsive on boot.
Flashing the stock boot.img and the touchscreen works.
Tried flashing the full image (no -w) and OTA with same result both times. Tried switching between active slots as well, no dice.
Any ideas?
JONBOY345 said:
Attempted the update last night, when flashing Magisk Canary Patched boot.img, the touchscreen is non-responsive on boot.
Flashing the stock boot.img and the touchscreen works.
Tried flashing the full image (no -w) and OTA with same result both times. Tried switching between active slots as well, no dice.
Any ideas?
Click to expand...
Click to collapse
Are you using:
- Magisk 20-4.zip (Stable)?
- Magisk Manager Canary 424 to patch September 2020 boot.img?
Homeboy76 said:
Are you using:
- Magisk 20-4.zip (Stable)?
- Magisk Manager Canary 424 to patch September 2020 boot.img?
Click to expand...
Click to collapse
Yes. Using Magisk 20-4.zip stable, but I've not used that zip in anyway...
Magisk Manager app is Canary from: https://github.com/topjohnwu/magisk_files/find/canary?q= and using it to patch the boot.img
Also updated platform tools to latesst.
JONBOY345 said:
Yes. Using Magisk 20-4.zip stable, but I've not used that zip in anyway...
Magisk Manager app is Canary from: https://github.com/topjohnwu/magisk_files/find/canary?q= and using it to patch the boot.img
Also updated platform tools to latesst.
Click to expand...
Click to collapse
Ok. I guess it's the Gremlins are preventing it from working.
Seriously, I don't know why it is not working.
Maybe @sliding_billy has some advice.
Homeboy76 said:
Ok. I guess it's the Gremlins preventing it from working.
Seriously, I don't know why it is not working.
Maybe @sliding_billy has some advice.
Click to expand...
Click to collapse
For giggles, can anyone share a patched boot.img?
JONBOY345 said:
For giggles, can anyone share a patched boot.img?
Click to expand...
Click to collapse
Sure, Let me know if this works for you!
Edit: posted an actual patched img. Grabbed the wrong file at first
https://drive.google.com/file/d/13VhMOr3XqFsIQUmZo3sG3LRATlV-hju8/view?usp=sharing
laxattack said:
Sure, Let me know if this works for you!
https://drive.google.com/file/d/1dcXyMv0sttfyGno496Tbo6MFuUIuii2w/view?usp=sharing
Click to expand...
Click to collapse
Hmm. That one didn't work. It booted, touchscreen worked, but no root.
For giggles I reran by steps again this morning, and now the new Magisk patched image works.
Here's a link: https://drive.google.com/file/d/127G2MZ_Jq8cPPKs50rtTiOijSkk7DbtU/view?usp=sharing
I noticed that your patched image is 67.1MB, while the one that Magisk created/patched on my phone (and I uploaded just above), is only 32.8MB...
Thanks for your help!
JONBOY345 said:
Hmm. That one didn't work. It booted, touchscreen worked, but no root.
For giggles I reran by steps again this morning, and now the new Magisk patched image works.
Here's a link: https://drive.google.com/file/d/127G2MZ_Jq8cPPKs50rtTiOijSkk7DbtU/view?usp=sharing
I noticed that your patched image is 67.1MB, while the one that Magisk created/patched on my phone (and I uploaded just above), is only 32.8MB...
Thanks for your help!
Click to expand...
Click to collapse
I uploaded the wrong one at first and edited my original post, lol sorry about that
Is anyone that is on latest android 11 able to use Google Pay? Mine won't work and CTS Profile fails safetynet check. Bootloader is unlocked but not rooted.
Homeboy76 said:
Ok. I guess it's the Gremlins are preventing it from working.
Seriously, I don't know why it is not working.
Maybe @sliding_billy has some advice.
Click to expand...
Click to collapse
JONBOY345 said:
Hmm. That one didn't work. It booted, touchscreen worked, but no root.
For giggles I reran by steps again this morning, and now the new Magisk patched image works.
Here's a link: https://drive.google.com/file/d/127G2MZ_Jq8cPPKs50rtTiOijSkk7DbtU/view?usp=sharing
I noticed that your patched image is 67.1MB, while the one that Magisk created/patched on my phone (and I uploaded just above), is only 32.8MB...
Thanks for your help!
Click to expand...
Click to collapse
Sorry I missed all this. I just got back in front of a computer and got no emails of the @ mention. Is everything working now? My two thoughts for what it's worth would have been to sideload the OTA twice so that it hit both slots and to be sure to update the Magisk path to canary after installing the .apk and then to be sure to update magisk after changing the path.
berndt_toast said:
Is anyone that is on latest android 11 able to use Google Pay? Mine won't work and CTS Profile fails safetynet check. Bootloader is unlocked but not rooted.
Click to expand...
Click to collapse
are you using a custom kernel to hide the unlocked bootloader?
laxattack said:
are you using a custom kernel to hide the unlocked bootloader?
Click to expand...
Click to collapse
Nope, I was on stock. I realized that I wasn't using any rooted apps anymore, so the need to have my bootloader unlocked was null and void. I re-locked my bootloader and now google pay works like a charm.
I'll add my observation here:
OTA update via magisk OTA update method works, but for some reason I kept having frozen screen after a few minutes usage. Rebooted at least 4-5 times and it worked.
I was using Taichi and its Magisk module doesn't work. Reflashing the module causes bootloop.
So I flashed again factory image without "-w", booted fine. But installing root via magisk_patched.img from R boot.img causes bootloop.
Don't understand why.
EDIT: Is there a way to clean up magisk modules now that I am on stuck on bootloader whenever I flash magisk_patched.img?
ultimatepichu said:
I'll add my observation here:
OTA update via magisk OTA update method works, but for some reason I kept having frozen screen after a few minutes usage. Rebooted at least 4-5 times and it worked.
I was using Taichi and its Magisk module doesn't work. Reflashing the module causes bootloop.
So I flashed again factory image without "-w", booted fine. But installing root via magisk_patched.img from R boot.img causes bootloop.
Don't understand why.
EDIT: Is there a way to clean up magisk modules now that I am on stuck on bootloader whenever I flash magisk_patched.img?
Click to expand...
Click to collapse
Tulsadiver's [Guide] Magisk Modules Disabler for Modules gone wrong by tulsadiver would fix it. I don't know if he has had the time to update it for Android 11 (R).
Maybe Support Safe Mode detection would help.
Do you have to use Magisk canary with Android 11? I just updated to 11, lost root, and want to add it back.
Thanks,
Rick
C5Longhorn said:
Do you have to use Magisk canary with Android 11? I just updated to 11, lost root, and want to add it back.
Thanks,
Rick
Click to expand...
Click to collapse
Magisk Canary Manager 20424
Yes!
I upgraded from like June 2020 build to 11 via OTA, do I just have to sideload patched boot.img as I always have been for previous monthly Android 10 updates? The only difference is using the canary version of Magisk (i'm on stable channel at the moment)
walle4893 said:
I upgraded from like June 2020 build to 11 via OTA, do I just have to sideload patched boot.img as I always have been for previous monthly Android 10 updates? The only difference is using the canary version of Magisk (i'm on stable channel at the moment)
Click to expand...
Click to collapse
pretty much
Android 11, Magisk & SafetyNet
berndt_toast said:
Is anyone that is on latest android 11 able to use Google Pay? Mine won't work and CTS Profile fails safetynet check. Bootloader is unlocked but not rooted.
Click to expand...
Click to collapse
I lost root when I upgraded to Android 11 Beta and I forgot to uninstall Magisk beforehand. I left it that way with the Magisk Manager app still installed because I didn't want to do a full wipe. I didn't have any SafetyNet problem until I took the latest rp1a.200720.009 OTA and got a warning message on the first boot. I decided to try installing the latest Canary Magisk again by sideloading the patched boot.img and now I have root again and can pass the SafetyNet check.