Related
1. To extract the image collection from your downloaded rom :
Download Payload Dumper from here (It's a zip file but it's not flashable) to your computer
Extract the zip file to a folder, make it a folder you can use regularly because this is the default tool you would use from now on
Download the rom version you want to root
Unzip the rom to a folder, you will find a file within it called payload.bin
Copy and paste that file into the "payload_input" folder within the Payload Dumper folder you created
Execute the payload_dumper.exe file within Payload Dumper folder, you will not have to specify any options as it always extracts from any payload.bin file in payload_input and outputs the image files to payload_output.
Leave the extraction to be completed, the program will automatically close itself once it's completed
Your extracted .img files will be shown within the payload_output folder
2. If you need to root the boot image you extracted :
Copy the boot.img file from the payload_output folder to a folder on your phone storage (Best to name it appropriately if you will be doing this regularly)
Download and Install the latest Magisk apk from the release site (Accept any prompt to allow install from external source)
Launch the app and then choose Install under the top "Magisk" section
Choose Select and Patch a File then browse to where you copied the boot.img on your storage
Magisk will then apply root to the boot image you specified, Your rooted image file will be output to your phone's Download folder : /sdcard/Download
You don't need to keep the default filename of the rooted image file so you can rename it appropriately for the rom version after you copy it to your computer, just ensure to keep the .img file extension
If you rename the rooted boot image, try not to use spaces in the filename, rather use _ or - as spaces make it more difficult to use in a command window although when you start typing the filename you can use TAB to autocomplete it, always ensure the filename shows .img as the extension and at the end of any commandline
3. If you need to use your rooted boot image to apply root to your phone :
Install the drivers from the mounted drive you should get when connecting the phone to your computer
On Windows you should then have a folder in C:\Program Files (x86)\OnePlus USB Drivers\Android with the platform tools (ADB.exe and Fastboot.exe) you will need, you can obviously copy the content from that folder somewhere else if you wish.
Connect your phone to your computer
Copy your rooted boot image to the folder that has adb.exe and fastboot.exe
Open a command window on your computer by right clicking in that folder and choosing Open command window here
In the command window, Type or copy/paste the command ADB devices and press enter
If you see a prompt on your phone to allow the computer connection then accept it, better still, tell it to allow from now on also.
You should see a string of characters shown in the command window, if you don't see that, then try another cable or re-install your drivers and reboot the computer.
Reboot your phone into Fastboot either by using ADB on your computer ( ADB Reboot Fastboot ) or by enabling Advanced reboot in your developer options in settings and then hold down the power button and use the 3 dot menu on the top right and choosing "Bootloader"
In the command window type Fastboot Boot <filename.img> i.e. Fastboot Boot rooted_boot.img and press enter
You should see a couple of lines in the command window telling you it's copying over to the phone, don't worry it's not being flashed or replacing your existing installed boot image
The phone should then restart and boot using the image from your computer, it will be a slightly slower boot than usual, your existing unlock method should still work
Launch the Magisk app, it should already have root access because the boot image you've used is already rooted
Go to Install under the top Magisk section
Choose Direct Install (Recommended)
Magisk will then apply root access to the boot image on the actual phone
You will be prompted to reboot the phone on the bottom right, do this to complete the process
You don't need the phone connected to your computer anymore as the installed boot image on the phone should now have root access
You can check for root either using any app which requires root or by using an app like Root Checker
Remember to empty the contents of payload_input and payload_output once you have finished, leaving them ready for any future rom versions
4. To retain root access after ROM/OTA update :
Install the update either from Oxygen Updater or from Settings > System > System updates
DO NOT REBOOT when prompted
Go to the Magisk app
Go to Install under the top Magisk section
Choose Install to Inactive Slot (After OTA)
Magisk will apply root to the newly installed boot image for the next version
Reboot when prompted by the Magisk app
The phone should reboot into the updated version with root already applied
Very nice write up! Hopefully many will read this and follow instructions. Too many threads being created with issues because they never bother to read.
Quick question as this is my first OnePlus device.
Will I lose root after a system update and will have to it all over again?
Levi4cyber said:
Quick question as this is my first OnePlus device.
Will I lose root after a system update and will have to it all over again?
Click to expand...
Click to collapse
Just added a new section to my original post for this.
Does flashing magisk change anything in encryption?
Does it wipe anything?
How do I get my ROM to extract the boot img?
Levi4cyber said:
Does flashing magisk change anything in encryption?
Does it wipe anything?
Click to expand...
Click to collapse
No and No
Levi4cyber said:
How do I get my ROM to extract the boot img?
Click to expand...
Click to collapse
Read the first post.
djsubterrain said:
Read the first post.
Click to expand...
Click to collapse
I'm asking where to get my ROM file, in order I should be able to extract the boot img?
A link? Somewhere on my phone?
Levi4cyber said:
I'm asking where to get my ROM file, in order I should be able to extract the boot img?
A link? Somewhere on my phone?
Click to expand...
Click to collapse
It's pinned at the top of the entire forum :
[OnePlus 9 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
They're also posted on OnePlus's site (eventually) :
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Make sure the version matches the one you're using
I updated to latest version 11.2.4.4.LE15AA
Since there's nowhere to download the OTA package and extract the boot img, can I use the boot img of a lower version - 11.2.2.2 ?
Levi4cyber said:
I updated to latest version 11.2.4.4.LE15AA
Since there's nowhere to download the OTA package and extract the boot img, can I use the boot img of a lower version - 11.2.2.2 ?
Click to expand...
Click to collapse
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom.
If you were already rooted though, you should've been able to retain it by following the last section in my original post.
If not, then follow the first 2 sections
djsubterrain said:
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom
Click to expand...
Click to collapse
Since I'm completely new to OP, is Oxygen updater an app (if yes, is it this; https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater)? Or is it built into the phone?
Levi4cyber said:
Since I'm completely new to OP, is Oxygen updater an app (if yes, is it this; https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater)? Or is it built into the phone?
Click to expand...
Click to collapse
I've linked it, it's not a default app
djsubterrain said:
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom.
If you were already rooted though, you should've been able to retain it by following the last section in my original post.
If not, then follow the first 2 sections
Click to expand...
Click to collapse
In the oxygen updater app, if I select "full update" in update method it only gives me version 11.2.2.2., if I select "incremental update", it lets me download 11.2.4.4, and when I unzipped it I have a file payload.bin (it's only 105MB).
Should I use that? Or do I need a full OTA package to extract the boot IMG?
Levi4cyber said:
In the oxygen updater app, if I select "full update" in update method it only gives me version 11.2.2.2., if I select "incremental update", it lets me download 11.2.4.4, and when I unzipped it I have a file payload.bin (it's only 105MB).
Should I use that? Or do I need a full OTA package to extract the boot IMG?
Click to expand...
Click to collapse
Are you choosing the correct OnePlus 9 Pro? It'll show you different variants under the model lookup.
To be honest, If I get the update pushed via OnePlus I always copy/paste it somewhere else cos I think it gets deleted once the upgrade is done.
If you extract the payload.bin and it shows a boot.img then that should suffice. I think it should be around 105MB (I'm on my work PC at the moment so can't check)
Thanks. I'm on the T-Mobile version of the OnePlus 9 Pro, technically my phone is currently on "11.2.2.2.LE5ACB" and the one on OnePlus's support site is "11.2.2.2.LE15AA". I'm not sure the difference but I assume T-Mobile bloatware. Hopefully they didn't do anything else to make the phone work "slightly better" on their network.
I'm not sure if the boot.img I extracted from 11.2.2.2.LE15AA will work with my currently-installed "11.2.2.2.LE5ACB"; any ideas?
Might be better to create a boot.img from my existing version and patch that. Do you know the dd command for me to just create the boot.img from my existing partition? In the past with other phones I've done something like "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/boot.img bs=4096 count=4096 skip=7552" or "dd if=/dev/block/bootdevice/by-name/boot of=boot.img" but I don't know which partition on the OnePlus 9 Pro to image. Any ideas?
--- Update 1 ---
Code:
OnePlus9ProTMO:/ $ ls -l /dev/block/bootdevice/by-name/*boot*
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/boot_a -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/boot_b -> /dev/block/sde43
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vendor_boot_a -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vendor_boot_b -> /dev/block/sde55
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vm-bootsys_a -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vm-bootsys_b -> /dev/block/sde51
Then looking at my active mounts I saw this:
Code:
OnePlus9ProTMO:/ $ mount | egrep "sde16|sde43|sde28|sde55|sde24|sde51"
/dev/block/sde51 on /vendor/vm-system type ext4 (ro,seclabel,nosuid,nodev,relatime)
Which indicates that I'm on the "b" side. So I would want to create a boot.img from `/dev/block/bootdevice/by-name/vendor_boot_b` potentially. So this command "should" work, right?
Code:
dd if=/dev/block/bootdevice/by-name/vendor_boot_b of=/sdcard/Download/stock_boot.img
I might try that instead of the boot.img I extracted from 11.2.2.2.LE5ACB since it doesn't technically line up with the T-Mobile supplied ROM version.
--- Update 2 ---
Yeah, that didn't work.Turns out dd needs to be elevated to do its thing. Got a "Permission denied" when i tried to create the image. So yeah, ironically I need root to run said command and that's why I was trying to run the command, to get the boot.img to root. lol. oh well.
Thank you very detailed.
When I click on the payload_pumper.exe file, the cmd window flashes and nothing else happens.
glitchsys said:
Turns out dd needs to be elevated to do its thing.
Click to expand...
Click to collapse
Try watching this, man, I think this is exactly what you are missing:
Code:
https://www.youtube.com/watch?v=DyUainEJwLM
I'm not sure why no one has posted this on here yet. I see the unstable google drive linked Android 11 Lineage but not the official download links and instructions...
i run this rom on my daily driver.
here is the link:
https://download.lineageos.org/walleye
the instructions are what you should foolow as they know alot more than me about all this but they say to temp flash the recovery, that has never worked for me.
WARNING!!!
IT IS NOT RECOMENDED BY LINEAGE TO USE GAPPS, AS SOME OF THEM WILL OVERWRITE/REMOVE OPTIMIZED LINEAGEOS SYSTEM APPS, AND REDUCE SECURITY/STABILITY!
THE SYSTEM WORKS JUST FINE WITHOUT GAPPS BUT IF YOU CHOOSE TO USE THEM LIKE I DO HERE IS THE INSTRUCTIONS I FOLLOW:
-----------------------------------------------------------------------------------------------------------------------
1. remove password on system
2. copy the downloaded system zip to sdcard
Google usb driver found here: https://developer.android.com/studio/run/win-usb
3. adb reboot-bootloader
google platform tools adb & fastboot found here: https://developer.android.com/studio/releases/platform-tools
4. fastboot boot [twrp]
do not allow modifications, do not change any settings and do not install twrp to recovery
Twrp found here: https://dl.twrp.me/walleye/
5. install [Lineage.zip]
sometimes you can sideload this pkg but others not so i just send it to the sdcard and install from there in twrp, ive had issues with usb 3.1 ports with system pgk but not with gapps.
6. reboot to bootloader and fastboot boot [twrp]
if you do not do step 6 the boot slot will not be correct for installing the gapps and will not be able to boot the system
7. adb sideload [gapps-core] and then adb sideload [addons] (without booting system before all gapps installed)
i get these from here: https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/
i only do the core first, then i have a short batch file sideload all the addons i want from here:
https://sourceforge.net/projects/nikgapps/files/Releases/Addons-R/ choosing which ones i need because there is not always enough space.
the ones i sideload in order are named like this [NikGapps-Addon-11-*-signed.zip] below:
GBoard
Gmail
GoogleClock
GoogleContacts
GoogleDialer
GoogleMessages
GoogleCalculator
GoogleCalendar
GooglePhotos
Velvet
GoogleChrome
GoogleFi
GoogleTalkback
GoogleTTS
8. reboot system, and let boot up.
9. adb reboot-bootloader
enable usb debugging first
10. fastboot boot twrp
if you wanted to install twrp to system as recovery do it before magisk at this step.
11. adb sideload magisk.zip
magisk.zip is the magisk.apk, just rename the apk found here: https://github.com/topjohnwu/Magisk/releases
12. reboot
If magisk doesn't seem to want to work at this step:
open app while online, reboot, test again, if still no:
adb install -g [magisk.apk]
did i do something wrong? miss something? want me to take this down? make this better?
any feedback is welcome as this is mainly because i've spent many hours trying to figure all this out so i hope it helps someone.
The original post it's at Pixel 2 XL forum
Tony Ronaldo Matute said:
The original post it's at Pixel 2 XL forum
Click to expand...
Click to collapse
why, because the walleye and taimen kernel merge?
link please?
Solomon M said:
why, because the walleye and taimen kernel merge?
link please?
Click to expand...
Click to collapse
Here is the link
[ROM][OFFICIAL] Lineage OS 18.1 for Pixel 2 / 2 XL
When will it be getting official and updated to December patch?
forum.xda-developers.com
Maybe you can ask permission to @Eamo5 for make thread in P2 session
kurokuroninja said:
Here is the link
[ROM][OFFICIAL] Lineage OS 18.1 for Pixel 2 / 2 XL
When will it be getting official and updated to December patch?
forum.xda-developers.com
Maybe you can ask permission to @Eamo5 for make thread in P2 session
Click to expand...
Click to collapse
Oh! This is a duplicate. My apologies.
I'm not sure how to delete this. Also maybe they should post in the Walleye form instead of the other to help people find walleye related roms or rom info.
Whoever decided to put all walleye stuff with taimen just because they are both wahoo is dumb.
That's like saying let's put all the phone a with b just because some of it is the same. If they where the same then at least they would both be made by the same hardware manufacturer LG != HTC nor vice versa.
Solomon M said:
Oh! This is a duplicate. My apologies.
I'm not sure how to delete this.
Click to expand...
Click to collapse
Thread has been closed.
Ready to Unlock, Root, and Update factory images on your Pixel 6 Pro?
There are some really good guides by V0latyle here, and by roirraW "edor" ehT here which are great for veteran/regular users who are really familiar with adb/fastboot and the commands, steps used in the unlocking, rooting environment.
This step by step is for people like ME who are not adb/fastboot gurus, who need every step spelled out so we don't brick our over-priced flagship devices
* * *P L E A S E READ THIS FIRST B E F O R E UPGRADING TO ANDROID 13* * *
What You Need On Your PC:
Factory Image
MAGISK - Canary 24310
SDK Platform Tools & USB Drivers (first time installation)
(additional files I use: optional)
Working SafetyNet @Pekempy
Kirisakura Kernel @Freak07
*** MAKE SURE YOU EXTRACT THE CORRECT BOOT.IMG FILE TO PATCH IN MAGISK ***
-download latest factory image, unzip the MAIN image.zip, then unzip the SECONDARY image.zip , copy the contents of the SECOND image.zip into the same platform tools folder that has the fastboot application in it, then open the image.zip you just copied into the fastboot folder and copy the boot.img and paste it somewhere on your PC.
Device Setup PRIOR To Starting Fastboot:
Settings>About phone>Build Number (click build number until you see YOU ARE NOW A DEVELOPER)
Settings>System>Advanced>Developer Options
Enable OEM Unlocking & USB Debugging & USB Configuration> enable FILE TRANSFER
Unlock the Bootloader, Update Factory Image, and Get Root:
1- Boot your device into bootloader/fastboot (hold power / vol down)
2- Connect USB cable to device and PC ( have diff USB cables available for troubleshooting)
3- From address bar in the platform tools folder where the fastboot application is located on your PC, type CMD to open command prompt window
4- Type FASTBOOT DEVICES, if you see a serial number(s) you are ready, if you don't, verify you've properly set up platform tools folder, change cable, check command, try again)
5- TO UNLOCK BOOTLOADER- type fastboot reboot bootloader (***YOUR DATA WILL BE WIPED***)
6- Type fastboot flashing unlock
7- Type fastboot reboot bootloader
IF UPDATING TO ANDROID 13 FOR THE FIRST TIME IT IS HIGHLY RECOMMENDED YOU FLASH THE 13 BOOTLOADER TO BOTH SLOTS BEFORE UPDATE (read warning at top of page) Follow step 7a to accomplish updating both slots to the Android 13 bootloader:
7a. Type fastboot flash bootloader --slot=all <bootloader image in platform tools>
PRIOR TO FLASHING THE FACTORY IMAGE:
-if you want a clean install, WIPING ALL DATA, skip to step #8
-if you want to SAVE data, edit the FLASH ALL.bat file, REMOVING the -w (leaving just ONE space between the remaining text) and SAVE the file (reopen file to verify -w is removed)
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. click HERE for more
8- Flash the factory image by typing FLASH-ALL
9- After the install, it will reboot into system, let everything settle, skip start up options and get to where you can download the latest MAGISK apk on your device (downloads folder)
***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***
10- Connect your device and PC and put the extracted BOOT.img file (from the CURRENT factory image you are flashing FOUND IN THE SECOND ZIP FOLDER) that you placed on your PC, put it on your mobile device where you can easily find it (I created a folder FILES TO FLASH)
11- Install Magisk (use Canary 24310 linked above), follow instructions to allow files like this to be installed) ***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***
12- Open Magisk and choose SELECT AND PATCH FILE (select the BOOT.img you just put on your device
13- Copy the new PATCHED BOOT.img from your download folder back into your PLATFORM TOOLS folder where the fastboot application is located on your PC
14- Boot device into fastboot/bootloader, connect device and PC
15- Type CMD in address bar and verify fastboot connection (step 4)
16- Type fastboot reboot bootloader
17- Type fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img)
18- Reboot into System
UPDATE Factory Image WITHOUT Wiping Data:
1- Within the Platform Tools folder, find the FLASH-ALL (.bat) file
2- Open it with text editor and remove the -w (keep ONE space between remaining text, SAVE file, reopen to verify -w is removed)
3- Verify FASTBOOT DEVICES by typing CMD in the address bar of the same platform tools folder
4- Type FLASH-ALL
5- Let it boot into system and settle for a minute
6- Patch the boot image (follow steps 10, 12 -18 above)
*** Thanks to V0latyle, roirraW "edor" ehT, and Lughnasadh for the foundations of these instructions! ***
Please let me know if any part of this process is incorrect, has been updated, or is no longer necessary
This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?
dipole said:
This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?
Click to expand...
Click to collapse
+1
Your guide is exactly what I have been summarizing in one of the threads already.
They keypoint now is on how to apply monthly updates without wiping the phone all the time while also still getting root
Az Biker FTW! Good to see you here buddy! (I remember you from the Pixel 2/4 XL forums)
Thanks @Az Biker! I'll update the OP of my thread to link to this thread just as soon as I can find the time.
dipole said:
This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?
Click to expand...
Click to collapse
I've never done the OTA method, so I don't have a step by step for that. Sorry.
How can I re-lock the bootloader?
I'm getting a "command error" with fastboot flashing lock
dipole said:
This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?
Click to expand...
Click to collapse
You can find the OTA sideload method here...
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Maybe it makes more sense to combine and improve upon existing tutorials, instead of creating a load of new ones. It's getting a bit confusing here, ESPECIALLY since we don't have any sub-threads/forums.
Why is that, anyway? it makes sifting through threads here a nightmare, since you have to scroll through dozens of threads to find one that suits your interest. Instead of just giving us, like, an overview labeled "mods", "kernels", "camera", "discussion", "flame" - like, in every other previous XDA Pixel forum?!
Morgrain said:
Why is that, anyway? it makes sifting through threads here a nightmare, since you have to scroll through dozens of threads to find one that suits your interest. Instead of just giving us, like, an overview labeled "mods", "kernels", "camera", "discussion", "flame" - like, in every other previous XDA Pixel forum?!
Click to expand...
Click to collapse
Did you see the responses about this subject starting here?
Personally, I haven't had a problem with the way they're doing the forums now. The Quick Filters at the top have been good enough for me when I want to concentrate on one of those particular types of posts.
FYI, although I'm a proponent of the new way, I'm not particularly against the old way. That's what I got used to, too, but things change.
roirraW edor ehT said:
Did you see the responses about this subject starting here?
Personally, I haven't had a problem with the way they're doing the forums now. The Quick Filters at the top have been good enough for me when I want to concentrate on one of those particular types of posts.
FYI, although I'm a proponent of the new way, I'm not particularly against the old way. That's what I got used to, too, but things change.
Click to expand...
Click to collapse
Good to know. Nope, I did not notice that. And I don't really like the filters. I'm used to , uhm, use XDA on my PC with multiple monitors, and the old style forums allowed me to just middle mouse button Press every sub forum, enabling me to open all of them in separate browser threads in the course of a second, which made quickly tabbing / shifting through sections /threads extremely quickly / efficient, at least for someone used to that kind of usage. Now I'm stuck with the heck load of filters and that just slows down the way I browse by factor three, if not more.
This new system is also quite confusing. Back in the days whenever you open a sub forum, you had an easily distinguishable sort of sticky threads. Now it just feels all cluttered together. It made browsing XDA less fun and it just feels tedious.
vibrantliker said:
How can I re-lock the bootloader?
I'm getting a "command error" with fastboot flashing lock
Click to expand...
Click to collapse
Check to be sure you only have one space between each word, and no typos.
I believe fastboot oem lock will work as well.
Make SURE you are running a stock, factory image before doing this (just in case you weren't aware).
Morgrain said:
...use XDA on my PC with multiple monitors, and the old Style forums allowed me to just middle mouse button Press every sub form to me to open all of them in separate browser threads, which made quickly tabbing / shifting through sections /threads extremely quickly, at least for someone used to that kind of usage.
Click to expand...
Click to collapse
Ha! Now that you've reminded me, I used to do the exact same thing here (I too middle mouse button, in general, a lot). Maybe it's been beneficial to me that I've barely had any activity on XDA for the last five years, and especially the last three years.
Thank you, however readability is very bad on a light background. Please change font color.
Tomatot- said:
Thank you, however readability is very bad on a light background. Please change font color.
Click to expand...
Click to collapse
Changed the font to "brown", let me know if that helps with the light theme.
I'm on Xda-dark and hadn't thought about the readability using light theme, thanks!
Az Biker said:
Changed the font to "brown", let me know if that helps with the light theme.
I'm on Xda-dark and hadn't thought about the readability using light theme, thanks!
Click to expand...
Click to collapse
I thought of that, that's why I dared to mention it.
It's better indeed!
Morgrain said:
Maybe it makes more sense to combine and improve upon existing tutorials, instead of creating a load of new ones. It's getting a bit confusing here, ESPECIALLY since we don't have any sub-threads/forums.
Why is that, anyway? it makes sifting through threads here a nightmare, since you have to scroll through dozens of threads to find one that suits your interest. Instead of just giving us, like, an overview labeled "mods", "kernels", "camera", "discussion", "flame" - like, in every other previous XDA Pixel forum?!
Click to expand...
Click to collapse
Sorry for the late response.
FILTER TABS (new way) vs Sub Forums (old way):
Look at it this way:
You're grocery shopping online, and you want to browse the candy bar selection. The store has candy bars in several areas, not just in one place, so now you have to look through pages and pages of all the available product.
Rather than try to scroll through everything in the store to just find the candy bars, you click the CANDY BAR filter tab, and ONLY the candy bars are visible now.
So even though they aren't technically in one single area of the store, you can only see the candy bar selection on your page.
That's how the new forum works. Want to only see Development threads? Click the DEVELOPMENT tab at the top of the device forum.
@Az Biker
could you please make the guide for update factory image with out wiping. and keep root. please please please.
Lw00d said:
@Az Biker
could you please make the guide for update factory image with out wiping. and keep root. please please please.
Click to expand...
Click to collapse
That would be awesome. Just looking around for that as well.
Is it possible to get root without wiping? Currently I only have the bootloader unlocked and I'm on .036
DISCLAIMER* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.PRE REQUIREMENTS:- SDK Platform-tools (Get it here)
-boot.img from Stock Rom
-Patience
LET'S BEGIN!
Extract the SDK Platform tools folder to an easily accessible directory
UNLOCKING THE BOOTLOADERNOTE: THIS WILL ERASE ALL DATA FROM YOUR DEVICE SO MAKE SURE TO TAKE A BACKUP IF NECESSARY
-Extract the SDK Platform tools folder to an easily accessible directory
- Go to Settings > About Tablet > Tap build number 7 times. Go back to main page of Settings > System > Developer
options and enable OEM unlocking and USB Debugging
- Reboot the system to bootloader (Press Vol - and Power key or type "adb reboot bootloader" by opening a command prompt window in Platform tools directory)
- To unlock bootloader type the below code
fastboot flashing unlock
- The device will do a factory reset and restart itself
-After Setting up your device install the magisk app from here
ROOTING [MAGISK]METHOD-1 (FASTBOOT)- Transfer your boot.img to Internal Stroage
- After installing the magisk app Go to Install > Select and Patch a File
- Select the boot.img you transferred to Internal Storage. Magisk will patch your boot.img and display the output folder after the process.
- Transfer the Patched boot.img to SDK Platform tools folder and rename it to boot.img
- Reboot to Bootloader and type the below command:
fastboot flash boot boot.img
-Reboot the device by typing:
fastboot reboot
-Check Magisk manager and the device must be rooted now
METHOD-2 (TWRP)- Install TWRP by following this guide
- Download the magisk apk. Transfer it to SD-Card and flash it from twrp
- Reboot your device
CREDITS@topjohnwu Magisk
@adazem009 For TWRP recovery
Press Thanks button if this guide was useful to you!
@Johannj22
We would appreciate if you provide all help in the open on the thread itself. Please do not post Telegram links and request users to visit you there for help. TG links can only be posted by Devs on Development threads in the OP only. Please read THIS.
PATCHED BOOT IMAGE FROM YT-X705FThis is a magisk patched boot.img from the latest firmware for YT-X705F. Please don't use it for other models (YT-X705L, YT-X705X)
TNSMANI said:
@Johannj22
We would appreciate if you provide all help in the open on the thread itself. Please do not post Telegram links and request users to visit you there for help. TG links can only be posted by Devs on Development threads in the OP only. Please read THIS.
Click to expand...
Click to collapse
Noted sir. It won't happen again
what version of ROM you use .
the last one is not work with magisk
I use this version YT_X705F_S001135_210909_ROW
yes this one is the last one see date from post yet,
but magisk will not work with this version anymore.
i collect from earlier version this "boot.img" does it match with a android roms 10 from lenovo ?
Loserintheend said:
yes this one is the last one see date from post yet,
but magisk will not work with this version anymore.
i collect from earlier version this "boot.img" does it match with a android roms 10 from lenovo ?
Click to expand...
Click to collapse
You just have to make sure you use the boot.img from the exact firmware you are on now. Let me know if it worked.
Johannj22 said:
I use this version YT_X705F_S001135_210909_ROW
Click to expand...
Click to collapse
so S001135 was last Offizial ROM from Lenovo , just was waiting to install this one as root.
because every three month Lenovo release OTA-Update for some Update and get worse.
After rooting tablet and lenovo release update, " boot.img" must be change back to install OTA Update from lenovo .
Now it seams this OS will be stable on Lenovo YT_X705F SMART TAB.
But still probs on running differnt APPS on this doomed crap tablet, for this issue i'm looking on LineageOS
Loserintheend said:
so S001135 was last Offizial ROM from Lenovo , just was waiting to install this one as root.
because every three month Lenovo release Update for some Update and get worse.
After rooting tablet and lenovo release update, " boot.img" must be change back to install update from lenovo .
Now it seams this OS will be stable on Lenovo YT_X705F SMART TAB.
But still probs on running differnt APPS on this doomed crap tablet, for this issue i'm looking on LineageOS
Click to expand...
Click to collapse
If you are on the same firmware S001135 then just use the boot.img I posted above. It should work. Also It would be better to disable system updates. I am creating a seperate post for running GSI of LineageOS and other ROMS.
Johannj22 said:
If you are on the same firmware S001135 then just use the boot.img I posted above. It should work. Also It would be better to disable system updates. I am creating a seperate post for running GSI of LineageOS and other ROMS.
Click to expand...
Click to collapse
No way to disable updates , after every reboot this tablet ask you again. Only mark, i will update rom manuell.
BTW im also switch off all this spying GOOGLE Apps , and a lot of this junk apps from google .
Loserintheend said:
No way to disable updates , after every reboot this tablet ask you again. Only mark, i will update rom manuell.
BTW im also switch off all this spying GOOGLE Apps , and a lot of this junk apps from google .
Click to expand...
Click to collapse
SO you are not able to root the device?. I am on latest update and I rooted it. You can install the latest firmware from Rescue and Smart assistant. Just flash it onto your device. The downloaded ROM should be saved in C:\ProgramData\RSA\Rom files\YT-X705Fxxxx\.......There you should fine boot.img
Johannj22 said:
SO you are not able to root the device?. I am on latest update and I rooted it. You can install the latest firmware from Rescue and Smart assistant. Just flash it onto your device. The downloaded ROM should be saved in C:\ProgramData\RSA\Rom files\YT-X705Fxxxx\.......There you should fine boot.img
Click to expand...
Click to collapse
i told you i do it twice , but by the last ROM i was waiting .. read my issue #9
Loserintheend said:
i told you i do it twice , but by the last ROM i was waiting .. read my issue #9
Click to expand...
Click to collapse
Waiting?. I am sorry I think its the language barrier ..I don't understand certain things you say.
Any help provided for X705X tab,It got A10 update.How can I get stock rom and boot image for the latest update?
Finally I find out RSA mentioned in this threads and able to download stock firmware
vygavedha said:
Finally I find out RSA mentioned in this threads and able to download stock firmware
Click to expand...
Click to collapse
Yes use RSA and flash the stock firmware. This stock firmware you flashed should be saved in your system's C:\ProgramData\RSA\Rom Files folder. Just get the required image files from there/
I did not flashed. I just downloaded the firmware. But it seems it is downloaded with some extension(.bmp Or pac which I did not check well).
How can I extract boot img from this?
I renamed to zip and extracted. But could not find any image files.
Can you help how did you do the extraction?
vygavedha said:
I did not flashed. I just downloaded the firmware. But it seems it is downloaded with some extension(.bmp Or pac which I did not check well).
How can I extract boot img from this?
I renamed to zip and extracted. But could not find any image files.
Can you help how did you do the extraction?
Click to expand...
Click to collapse
Send me a screenshot
Johannj22 said:
Send me a screenshot
Click to expand...
Click to collapse
Sure. I have deleted the downloaded file. I will redownload the same and update the screen shot tomorrow
This is for the CPH2451 Rom, but should also work for other roms.
I have returned my device so I will not be updating this with future updates.
I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or not.
Not my fault if your phone bricks.
Phase 1: Unlocking the bootloader
Spoiler
WARNING: This will erase all data on your phone.
WARNING: Netflix will not work after bootloader unlock. OnePlus's fault.
Step 1: Complete the initial setup. You don't have to waste time signing into anything.
Step 2: Go into Settings and scroll down to About Device.
Step 3: Scroll down and tap on Version.
Step 4: Tap 7 times on Build number.
Step 5: Go back to settings and go to Additional settings.
Step 6: Go into Developer options and tap on OEM unlocking and USB debugging.
Phase 2: Installing drivers
Spoiler
Step 1: Install everything here,except for OPLocalUpdate_For_Android12.apk. Save that for later.
https://www.androidfilehost.com/?w=files&flid=334530
Phase 3: Recognizing the phone and unlocking the bootloader.
Spoiler
Step 1: Connect the phone to the PC and accept the prompt on your phone. Don't worry if it doesn't show.
Step 2: If you installed all the drivers correctly, then from any folder on your computer, hold Shift and right click your mouse and select Open PowerShell window here. Use CMD if you have issues.
Step 3: Type the following code and if you didn't get the prompt earlier, then accept the prompt after entering this code.
Code:
adb devices
You should get something like this:
Code:
List of devices attached
6g73s2t1 device
Step 4: Reboot to bootloader
Code:
adb reboot bootloader
Step 5: Type the following code and you should get something similar like step 3. Skip to Step 7 if you do. Continue to Step 6 if you don't.
Code:
fastboot devices
Step 6: On your computer, right click This PC and select Manage.
Look for a yellow triangle. It probably says Android device.
Right click it and select Update driver.
Select Browse my computer for drivers.
Select Let me pick from a list of available drivers on my computer.
You should have a list of Google or Samsung bootloader drivers or adb drivers or similar.
This just install one and see if the triangle disappears, if not they try another until it disappears.
Retry the code above and it should work.
Step 7: Type the following to unlock the bootloader
Code:
fastboot flashing unlock
WARNING: You might not be able to set your pin, password, fingerprint, and face unlock due to Oneplus incompetence.
Step 8: Let your phone do it's thing, don't worry about the Orange State warning message after it restarts. This is normal.
Step 9: Set up the phone, but don't waste your time logging into anything until you can successfully set up a pin or password. Skip to Step 11 if you can set up a pin or password. Continue to Step 10 if it hangs up on the second entry.
Step 10: Skip everything, enable USB debugging and reboot back into the bootloader.
This is the annoying part. You need to lock and unlock as many times as it takes for the pin or password setup to work. You might need to toggle the OEM unlocking switch in between lock and unlock cycles.
Use the following to lock the bootloader and then repeat all of Phase 1 and 3 as many times as it takes.
Code:
fastboot flashing lock
Step 11: Go ahead and setup your phone or continue to Phase 4.
Phase 4: Rooting
Spoiler
Step 1: Download and install KernelSU.
https://github.com/tiann/KernelSU/releases
Step 2: Open the app to find the Kernel version to download.
Should be something similar to 5.15.41-android...........
NOTE: This number is old and will change with each update so use what your phone says.
Step 3: Take the first 3 sets of numbers and download and save the corresponding boot.img.gz file somewhere convenient.
https://github.com/tiann/KernelSU/releases
Using the example above, you will download this file: ksu-10647-Image-android13-5.15.41_2022-05-boot.img.gz
This file will change with each app update so use the latest available that matches your phone in Step 2.
Step 4: Extract the .img file.
Step 5: Reboot to bootloader.
Code:
adb reboot bootloader
Step 6: BOOT the kernel. DO NOT EVER FLASH THIS PHONE!
Code:
fastboot boot ksu-10647-Image-android13-5.15.41_2022-05-boot.img
You essentially have temp root at this point.
Step 7: Download and install Magisk Canary or Delta. I used Delta. Stable does not work.
https://github.com/topjohnwu/Magisk
Step 8: Open KernelSU and select the middle Superuser tab
Step 9: Scroll down and toggle Magisk
Step 10: Open Magisk and perform a direct install.
Step 11: Install safetynet-fix-v2.4.0-MOD_1.2
https://github.com/displax/safetynet-fix/releases
Step 12: Clear the data from Playstore app and any Google app that has issues.
Step 13: Enjoy!
Netflix:
Spoiler
Netflix does work, but DRM will drop from L1 to L3. However, I'm not prepared to release the fix yet cause I don't want you guys using my Netflix account.
Realistically, since I no longer have this phone, I can't test it anymore so those who don't have a working OP10 or OP10T, you're SOL for now.
For those who do still have a rooted OP10 or OP10T with working Netflix, then download Swift Backup, back up the app settings from your OP10 or OP10T and restore the files on the OP11.
https://play.google.com/store/apps/details?id=org.swiftapps.swiftbackup&hl=en_US&gl=US
WARNING: IF YOU GIVE THE BACKUP FILES TO SOMEONE ELSE, THEN THEY WILL HAVE ACCESS TO YOUR NETFLIX ACCOUNT!
OTA Updates:
Spoiler
I have returned my device so this will be the only post I'm making for updates. Follow the Non-PC Method for future updates.
Color/Oxygen OS android 13 update
CPH2451_11.A.07 NA Update & ROOT
CAUTION!
Not my fault if your phone breaks.
WARNING!!!
Issues I've seen on previous devices:
- A few people have had bootloop issues due to using the wrong rom on the wrong phone. (e.g. Installing the Global ROM on a NA, EU, IN, or CN model)
- If you have "FLASHED" the patched boot vice "BOOT" at anytime prior to this, then you can NOT use OTA unless you want to bootloop or end up in EDL and wipe the phone.
I can't help you if your phone doesn't update properly.
-----------------------------------------------------------------------------------------
NA CPH2451_11.A.07 OTA Incremental update:
Official: https://android.googleapis.com/packages/ota-api/package/11ca82d836bbd2530659d57bca236d2da0caf5dd.zip
Mirror: https://www.androidfilehost.com/?fid=4279422670115720937
SHA-1: 11CA82D836BBD2530659D57BCA236D2DA0CAF5DD
MD5: D0A498CBDC3DABB491FD2EC061CD05C0
OnePlus Local Update Tool (OPLocalUpdate_For_Android12.apk). Works on 13.
Mirror: https://www.androidfilehost.com/?fid=15664248565197176984
SHA-1: 80707A75F7FA9E1864E84C7C7C270175A9FEC129
MD5: ADF932B2FD4C2A2B379C9427197B6B6A
Two methods are available, PC and non-PC. I refer the non-PC method since it's much easier and it hasn't failed me yet so I'm just going to post instructions for that. If you screw up and lose root, then repeat Phase 4 for the PC method.
-----------------------------------------------------------------------------------------
Non-PC Method
See Warning above.
Step 1: You must unroot first. You don't have to completely remove Magisk, just restore images. Open Magisk, click uninstall magisk, and only click restore images. DO NOT REBOOT!
Step 2: Install OTA update using the OPLocalUpdate app or through the stock system update. DO NOT REBOOT!
Note: Skip to the next section if you want to back up the new stock boot.img, init_boot.img, and persist.img files before rooting the update.
Step 3: Open Magisk and install to inactive slot. Reboot.
-----------------------------------------------------------------------------------------
For those who followed other directions to FLASH the patched init_boot, then reflash the stock init_boot using the same directions you previously used to flash the patched file.
Follow Phase 4 to root.
CPH2451_11.A.06 init_boot image:
Stock
init_boot_a.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
SHA-1: 40F29889D68305B87ED8C0936F57F3F18A3A71D0
MD5: BF310CAEE6B1F176CA0A138BC3DB65CC
CPH2451_11.A.07 init_boot image
Stock
init_boot_b.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
SHA-1: 22010F8F186F1438FFFEEC186014515F0C674F54
MD5: 592D48E06F7F4494937445F9910C1CC0
Saving the stock boot, init_boot, and persist images after OTA updates:
Spoiler
Connect your phone to your PC and run the following codes using CMD or Powershell and save the files to your computer.
The new boot files will be either the _a.img or _b.img files, depending on which slot the update is installed to. You can save both and look to see which slot magisk is patching when you install to the inactive slot to know which are the new boot images. There is only one persist img file and it supposedly changes with each update so make sure you save it.
Code:
adb shell
su
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
dd if=/dev/block/by-name/boot_b of=/sdcard/boot_b.img
dd if=/dev/block/by-name/init_boot_a of=/sdcard/init_boot_a.img
dd if=/dev/block/by-name/init_boot_b of=/sdcard/init_boot_b.img
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
GPay no longer works, but Wallet does.
For those who accidentally flashed a patched init_boot over the boot file, here are the stock boot files:
CPH2451_11.A.06 boot image:
Stock boot
boot_a.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
SHA-1: 901EC0F5A2ECAF0F0B5472BA50A2C7B857C6D932
MD5: 96FFEAFC046C3F6B80B706694A46213B
CPH2451_11.A.07 boot image
Stock boot
boot_b.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
SHA-1: FCB9964D9547363AB524C10BA2E15AAE8899DBC1
MD5: DCFED50F37E79C272C954C9F6F1F82E2
Ok testing so i can delete mine,
This will help a lot for future proof the updates.
blasbenoit said:
Ok testing so i can delete mine,
This will help a lot for future proof the updates.
Click to expand...
Click to collapse
Don't delete the whole thread. There's other good info in there from other conversations. Maybe just delete the part about flashing
g96818 said:
This is for the CPH2451 Rom, but should also work for other roms.
I have returned my device so I will not be updating this with future updates.
I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or not.
Not my fault if your phone bricks.
Phase 1: Unlocking the bootloader
Spoiler
WARNING: This will erase all data on your phone.
WARNING: Netflix will not work after bootloader unlock. OnePlus's fault.
Step 1: Complete the initial setup. You don't have to waste time signing into anything.
Step 2: Go into Settings and scroll down to About Device.
Step 3: Scroll down and tap on Version.
Step 4: Tap 7 times on Build number.
Step 5: Go back to settings and go to Additional settings.
Step 6: Go into Developer options and tap on OEM unlocking and USB debugging.
Phase 2: Installing drivers
Spoiler
Step 1: Install everything here,except for OPLocalUpdate_For_Android12.apk. Save that for later.
https://www.androidfilehost.com/?w=files&flid=334530[/CODE]
Phase 3: Recognizing the phone
Spoiler
Step 1: Connect the phone to the PC and accept the prompt on your phone. Don't worry if it doesn't show.
Step 2: If you installed all the drivers correctly, then from any folder on your computer, hold Shift and right click your mouse and select Open PowerShell window here.
Step 3: Type the following code and if you didn't get the prompt earlier, then accept the prompt after entering this code.
Code:
adb devices
You should get something like this:
Code:
List of devices attached
6g73s2t1 device
Step 4: Reboot to bootloader
Code:
adb reboot bootloader
Step 5: Type the following code and you should get something similar like step 3. Skip to Step 7 if you do. Continue to Step 6 if you don't.
Code:
fastboot devices
Step 6: On your computer, right click This PC and select Manage.
Look for a yellow triangle. It probably says Android device.
Right click it and select Update driver.
Select Browse my computer for drivers.
Select Let me pick from a list of available drivers on my computer.
You should have a list of Google or Samsung bootloader drivers or adb drivers or similar.
This just install one and see if the triangle disappears, if not they try another until it disappears.
Retry the code above and it should work.
Step 7: Type the following to unlock the bootloader
Code:
fastboot flashing unlock
WARNING: You might not be able to set your pin, password, fingerprint, and face unlock due to Oneplus incompetence.
Step 8: Let your phone do it's thing, don't worry about the Orange State warning message after it restarts. This is normal.
Step 9: Set up the phone, but don't waste your time logging into anything until you can successfully set up a pin or password. Skip to Step 11 if you can set up a pin or password. Continue to Step 10 if it hangs up on the second entry.
Step 10: Skip everything, enable USB debugging and reboot back into the bootloader.
This is the annoying part. You need to lock and unlock as many times as it takes for the pin or password setup to work. You might need to toggle the OEM unlocking switch in between lock and unlock cycles.
Use the following to lock the bootloader and then repeat all of Phase 1 and 3 as many times as it takes.
Code:
fastboot flashing lock
Step 11: Go ahead and setup your phone or continue to Phase 4.
Phase 4: Rooting
Spoiler
Step 1: Download and install KernelSU.
https://github.com/tiann/KernelSU/releases
Step 2: Open the app to find the Kernel version to download.
Should be something similar to 5.15.41-android...........
Step 3: Take the first 3 sets of numbers and download and save the corresponding boot.img.gz file somewhere convenient.
https://github.com/tiann/KernelSU/releases
Using the example above, you will download this file: ksu-10647-Image-android13-5.15.41_2022-05-boot.img.gz
This file will change with each app update so use the latest available.
Step 4: Extract the .img file.
Step 5: Reboot to bootloader.
Code:
adb reboot bootloader
Step 6: BOOT the kernel. DO NOT EVER FLASH THIS PHONE!
Code:
fastboot boot ksu-10647-Image-android13-5.15.41_2022-05-boot.img
You essentially have temp root at this point.
Step 7: Download and install Magisk Canary or Delta. I used Delta. Stable does not work.
https://github.com/topjohnwu/Magisk
Step 8: Open KernelSU and select the middle Superuser tab
Step 9: Scroll down and toggle Magisk
Step 10: Open Magisk and perform a direct install.
Step 11: Install safetynet-fix-v2.4.0-MOD_1.2
https://github.com/displax/safetynet-fix/releases
Step 12: Clear the data from Playstore app and any Google app that has issues.
Step 13: Enjoy!
Netflix:
Spoiler
Netflix does work, but DRM will drop from L1 to L3. However, I'm not prepared to release the fix yet cause I don't want you guys using my Netflix account.
Realistically, since I no longer have this phone, I can't test it anymore so those who don't have a working OP10 or OP10T, you're SOL for now.
For those who do still have a rooted OP10 or OP10T with working Netflix, then download Swift Backup, back up the app settings from your OP10 or OP10T and restore the files on the OP11.
https://play.google.com/store/apps/details?id=org.swiftapps.swiftbackup&hl=en_US&gl=US
WARNING: IF YOU GIVE THE BACKUP FILES TO SOMEONE ELSE, THEN THEY WILL HAVE ACCESS TO YOUR NETFLIX ACCOUNT!
OTA Updates:
Spoiler
I have returned my device so this will be the only post I'm making for updates. Follow the Non-PC Method for future updates.
Color/Oxygen OS android 13 update
CPH2451_11.A.07 NA Update & ROOT
CAUTION!
Not my fault if your phone breaks.
WARNING!!!
Issues I've seen on previous devices:
- A few people have had bootloop issues due to using the wrong rom on the wrong phone. (e.g. Installing the Global ROM on a NA, EU, IN, or CN model)
- If you have "FLASHED" the patched boot vice "BOOT" at anytime prior to this, then you can NOT use OTA unless you want to bootloop or end up in EDL and wipe the phone.
I can't help you if your phone doesn't update properly.
-----------------------------------------------------------------------------------------
NA CPH2451_11.A.07 OTA Incremental update:
Official: https://android.googleapis.com/packages/ota-api/package/11ca82d836bbd2530659d57bca236d2da0caf5dd.zip
Mirror: https://www.androidfilehost.com/?fid=4279422670115720937
SHA-1: 11CA82D836BBD2530659D57BCA236D2DA0CAF5DD
MD5: D0A498CBDC3DABB491FD2EC061CD05C0
OnePlus Local Update Tool (OPLocalUpdate_For_Android12.apk). Works on 13.
Mirror: https://www.androidfilehost.com/?fid=15664248565197176984
SHA-1: 80707A75F7FA9E1864E84C7C7C270175A9FEC129
MD5: ADF932B2FD4C2A2B379C9427197B6B6A
Two methods are available, PC and non-PC. I refer the non-PC method since it's much easier and it hasn't failed me yet so I'm just going to post instructions for that. If you screw up and lose root, then repeat Phase 4 for the PC method.
-----------------------------------------------------------------------------------------
Non-PC Method
See Warning above.
Step 1: You must unroot first. You don't have to completely remove Magisk, just restore images. Open Magisk, click uninstall magisk, and only click restore images. DO NOT REBOOT!
Step 2: Install OTA update using the OPLocalUpdate app or through the stock system update. DO NOT REBOOT!
Step 3: Open Magisk and install to inactive slot. Reboot.
-----------------------------------------------------------------------------------------
For those who screwed up and followed other directions to FLASH the patched init_boot, then reflash the stock init_boot using the same directions you previously used to flash the patched file.
Follow Phase 4 to root.
CPH2451_11.A.06 init_boot image:
Stock
init_boot_a.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
SHA-1: 40F29889D68305B87ED8C0936F57F3F18A3A71D0
MD5: BF310CAEE6B1F176CA0A138BC3DB65CC
CPH2451_11.A.07 init_boot image
Stock
init_boot_b.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
SHA-1: 22010F8F186F1438FFFEEC186014515F0C674F54
MD5: 592D48E06F7F4494937445F9910C1CC0
GPay no longer works, but Wallet does.
Click to expand...
Click to collapse
Alright so this all makes sense, but one detail I'm unclear on. Past guides has said to FLASH the modified init_boot.img and root works. Your guide said not to, is there a huge risk in flashing init_boot.img?
My understanding was that once you're rooted this way, you can ota update like normal and then just use magisk to flash to inactive slot, and you're fine. Correct me on this, that's what I'm looking for here lol
H4X0R46 said:
Alright so this all makes sense, but one detail I'm unclear on. Past guides has said to FLASH the modified init_boot.img and root works. Your guide said not to, is there a huge risk in flashing init_boot.img?
My understanding was that once you're rooted this way, you can ota update like normal and then just use magisk to flash to inactive slot, and you're fine. Correct me on this, that's what I'm looking for here lol
Click to expand...
Click to collapse
You can't use OTA if you flash. Only my method works for the NA rom. I introduced this method to XDA on the 8T and it is the only way if you want normal OTA updates since full rom updates are few and far.
H4X0R46 said:
Alright so this all makes sense, but one detail I'm unclear on. Past guides has said to FLASH the modified init_boot.img and root works. Your guide said not to, is there a huge risk in flashing init_boot.img?
My understanding was that once you're rooted this way, you can ota update like normal and then just use magisk to flash to inactive slot, and you're fine. Correct me on this, that's what I'm looking for here lol
Click to expand...
Click to collapse
Ok so this is my understanding of the matter:
booting is like using a cap.
but flashing is like using glue with that cap.
g96818 said:
Don't delete the whole thread. There's other good info in there from other conversations. Maybe just delete the part about flashing
Click to expand...
Click to collapse
Upss sorry edited already.
I'll read your entire post and send you suggestions to add them here.
What do you think?
Flashing is also very dangerous post OP9 pro. There is no free MSM available so if you accidentally flash incorrectly, then you're looping.
blasbenoit said:
Upss sorry edited already.
I'll read your entire post and send you suggestions to add them here.
What do you think?
Click to expand...
Click to collapse
That's fines
g96818 said:
You can't use OTA if you flash. Only my method works for the NA rom. I introduced this method to XDA on the 8T and it is the only way if you want normal OTA updates since full rom updates are few and far.
Click to expand...
Click to collapse
Shoot I didn't think of that... Touche! So I'm reading along, and I'm getting to the part where you BOOT kernel su image for temp root. So far so good. What trips me up is when you install magisk app and install magisk, you can't ota update. So as per your guide, you MUST unroot the device and then ota update every time? This device sounds like a pain in the ass, I see why you returned yours tbh
H4X0R46 said:
Shoot I didn't think of that... Touche! So I'm reading along, and I'm getting to the part where you BOOT kernel su image for temp root. So far so good. What trips me up is when you install magisk app and install magisk, you can't ota update. So as per your guide, you MUST unroot the device and then ota update every time? This device sounds like a pain in the ass, I see why you returned yours tbh
Click to expand...
Click to collapse
Essentially, forgetting to unroot before ota is a brick..... ?
H4X0R46 said:
Shoot I didn't think of that... Touche! So I'm reading along, and I'm getting to the part where you BOOT kernel su image for temp root. So far so good. What trips me up is when you install magisk app and install magisk, you can't ota update. So as per your guide, you MUST unroot the device and then ota update every time? This device sounds like a pain in the ass, I see why you returned yours tbh
Click to expand...
Click to collapse
The phone doesn't unroot unless you restart. Just restoring images allows you to take the OTA, but you need to go back to magisk and install in inactive slot before restarting to keep root after restarting.
H4X0R46 said:
Essentially, forgetting to unroot before ota is a brick..... ?
Click to expand...
Click to collapse
No. You just can't update.
I returned the phone cause OP screwed me on the trade in so fcuk em.
g96818 said:
The phone doesn't unroot unless you restart. Just restoring images allows you to take the OTA, but you need to go back to magisk and install in inactive slot before restarting to keep root after restarting.
No. You just can't update.
I returned the phone cause OP screwed me on the trade in so fcuk em.
Click to expand...
Click to collapse
Flashing magisk leaves it a temp root? I figured it would survive reboots after magisk is installed KernelSU root would be gone, but magisk root should persist I thought?
Man they screwed you on the trade in? YIKES! I bought this phone because in the past they were always so easy to root! I'm having second thoughts now...
H4X0R46 said:
Flashing magisk leaves it a temp root? I figured it would survive reboots after magisk is installed KernelSU root would be gone, but magisk root should persist I thought?
Man they screwed you on the trade in? YIKES! I bought this phone because in the past they were always so easy to root! I'm having second thoughts now...
Click to expand...
Click to collapse
No flashing magisk will be permanent root until you un-root to update. KernelSU is only temp as you're only booting it. Also this method can be used to temp boot with root and pull the new un modified images such as boot.img, init_boot, persist, etc each time you update as well just to have a backup in case. I would assume it will be safer to update using the update apk instead of system update though as I've had issues on my 10 pro with unrooting and taking OTA then magisk patching to inactive slot in the past (would just need to capture the update url each update so can manually download it and install using the APK).
jeffsga88 said:
No flashing magisk will be permanent root until you un-root to update. KernelSU is only temp as you're only booting it. Also this method can be used to temp boot with root and pull the new un modified images such as boot.img, init_boot, persist, etc each time you update as well just to have a backup in case. I would assume it will be safer to update using the update apk instead of system update though as I've had issues on my 10 pro with unrooting and taking OTA then magisk patching to inactive slot in the past (would just need to capture the update url each update so can manually download it and install using the APK).
Click to expand...
Click to collapse
Alright this is all making more sense to me. Now you piqued my interest on using kernelSU to take stock backups of my boot and init_boot files, that's INSANELY useful. What tool would I use to take those backups? That alone could be an ass saver lol
jeffsga88 said:
No flashing magisk will be permanent root until you un-root to update. KernelSU is only temp as you're only booting it. Also this method can be used to temp boot with root and pull the new un modified images such as boot.img, init_boot, persist, etc each time you update as well just to have a backup in case. I would assume it will be safer to update using the update apk instead of system update though as I've had issues on my 10 pro with unrooting and taking OTA then magisk patching to inactive slot in the past (would just need to capture the update url each update so can manually download it and install using the APK).
Click to expand...
Click to collapse
You are correct. Using the system update is somewhat safer. You can either get the OTA file from Oxygen updater or let it fail updating while rooted.
The update log is saved here:
/data/misc/oplus_update_engine_log
file name is: update_engine_log
Open it as a text file and you'll see the google download link
H4X0R46 said:
Alright this is all making more sense to me. Now you piqued my interest on using kernelSU to take stock backups of my boot and init_boot files, that's INSANELY useful. What tool would I use to take those backups? That alone could be an ass saver lol
Click to expand...
Click to collapse
Windows PowerShell or cmd.
You need to boot the kernel file and give root access to the app called Shell using KernelSU and then enter the following in PowerShell or cmd:
Spoiler
adb shell
su
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
dd if=/dev/block/by-name/boot_b of=/sdcard/boot_b.img
dd if=/dev/block/by-name/init_boot_a of=/sdcard/init_boot_a.img
dd if=/dev/block/by-name/init_boot_b of=/sdcard/init_boot_b.img
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
It will save the files to your main storage folder and then you can then copy the files over to the computer for safe keeping.
H4X0R46 said:
Alright this is all making more sense to me. Now you piqued my interest on using kernelSU to take stock backups of my boot and init_boot files, that's INSANELY useful. What tool would I use to take those backups? That alone could be an ass saver lol
Click to expand...
Click to collapse
I would just use adb shell using the dd command. On the 10 pro I would always un-root, update using system OTA, then reboot, boot a patched boot.img, run adb shell and then dd my boot.img so I had a stock one then use Magisk app to do direct install.
jeffsga88 said:
I would just use adb shell using the dd command. On the 10 pro I would always un-root, update using system OTA, then reboot, boot a patched boot.img, run adb shell and then dd my boot.img so I had a stock one then use Magisk app to do direct install.
Click to expand...
Click to collapse
You don't have to wait. You can run the dd commands right after the update, but before installing to inactive slot for the boot images. I would wait for the reboot before doing the persist file.
g96818 said:
You don't have to wait. You can run the dd commands right after the update, but before installing to inactive slot for the boot images. I would wait for the reboot before doing the persist file.
Click to expand...
Click to collapse
True, didn't think about that. Was forgetting you're still technically rooted even after restoring images in Magisk as long as you don't reboot. Also if you want to backup without PC from your phone you can just use Termux (or similar terminal emulator) and use dd command from there to back up before installing to inactive slot.