Related
Hey all!
As you all know, Wileyfox has started rolling out Nougat for their devices, starting with the codenamed marmite family (Swift 2, 2 Plus and 2X models). With this new update, Wileyfox has also included a bunch of BLOATWARE I personally NEVER expected from them. I mean, I didn't request ads in my launcher, and why do I need to forcefully use Truecaller dialer instead of the cleaner, AOSP-based one? That's why I've created this Wileyfox Debloater tool, to keep the system apps as clean and stockish as possible.
App removals included:
- AndroidPay
- BasicDreams
- BookmarkProvider
- Google Books
- Chrome
- CMFileManager
- Drive
- Duo
- Gmail
- GooglePrintRecommendationService
- GoogleTTS
- Hangouts
- Keep
- Maps
- Google Music
- News and Weather
- PhotoTable
- talkback
- Google Videos
- WFChromeCustomization
- Youtube
- Contacts
- FoxHole
- Mms
- SnapdragonGallery
- TrueCaller
- All bundled-apps from /system/vendor/bundled-app
- Possibly more in the future.
(Note: All the moved Google Apps were removed for the sole reason that they can also be downloaded from the Play Store.)
App additons / other features included:
- Google Contacts, in replacement of the half-dummy, prebundled Contacts app (which was missing link with the Dialer).
- Google Dialer, in replacement of TrueCaller.
- Google Messages, in replacement of Wileyfox Mms app.
- AOSP's Launcher3, in replacement of FoxHole (Wileyfox's Launcher).
- Framework and permission files for Google Dialer to work.
- Small tweaks in the build.prop, including drop of min processors to work from 2 to 1, and rise of maximum processors to work from 4 to 8, as well as increasing the Android compiler default amount of processors from 4 to 6.
- Possibly more in the future, too.
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
(To learn how to properly upgrade your device, kindly check post [URL="https://forum.xda-developers.com/swift-2/development/debloat-wileyfox-debloater-quickly-t3587536/post72258926#post72258926"]#25[/URL])
2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Downloads:
- For the latest Wileyfox Swift 2, Swift 2 Plus and Swift 2X firmware: Wileyfox-TOS118C-Debloater--11-05-17.zip
(For version TOS089 check Wileyfox-TOS089-Debloater--10-04-17.zip)
- For more Wileyfox devices, coming soon
Installation instructions:
1. Update your device to Nougat
2. Unlock your bootloader and flash TWRP
3. Download the latest version zip
4. Boot into TWRP, make a backup if you wish (although is highly recommended), choose Install and locate and flash the ZIP.
5. Reboot and enjoy!
6. Are you missing missed calls notifications? Is the caller ID always showed as a number instead of a contact name during phone calls? Check post #16!
Uninstall instructions:
Check post #6
Enjoy, and don't forget to leave a Thanks if you loved it!
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
rivierakid said:
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
Click to expand...
Click to collapse
That is also a possibility but:
1. Launcher3 conflicts with the already installed launcher, so it's impossible to get that out of the way
2. I got latest version working here using the required libraries (extracted from a Pixel), so yeah, probably both possibilities are just fine
And for the third one, just wanted to say there's no need to reactivate them (if you manage to deactivate them, ofc), and, all of the packages the script moves are stored in a safe place (/system/__bloat), so they can be restored from there
I don't remember if I had a problem with a previous OTA update for Wileyfox, but I was not able to install an update without reactivation a disabled app.
I'm not sure...
You could select a default launcher and the phone has really enough RAM, so I think it is not necessary to remove the FoxHole from the system.
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
The final solution for this is LineageOS, if they provide the source
Excellent! Thanks for providing this...such a stupid shame that Wileyfox decided to do this. I'm just hoping that they now release their sources so that we can start working on a proper release of Lineage!
*Edit: Nice! https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937/commits/all*
JT
rivierakid said:
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
Click to expand...
Click to collapse
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Hello,
thanks for your effort to the community.
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
linuxct said:
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Click to expand...
Click to collapse
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
MCPoppa said:
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
Click to expand...
Click to collapse
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
jdtanner said:
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
Click to expand...
Click to collapse
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
linuxct said:
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
Click to expand...
Click to collapse
Everytime i installed twrp i got stuck in a bootloop :/
MCPoppa said:
Everytime i installed twrp i got stuck in a bootloop :/
Click to expand...
Click to collapse
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
linuxct said:
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
Click to expand...
Click to collapse
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
MCPoppa said:
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
Click to expand...
Click to collapse
I explained it last night here, but I also stated it in the OP:
linuxct said:
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
[B]2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.[/B]
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Click to expand...
Click to collapse
linuxct said:
I explained it last night here, but I also stated it in the OP:
Click to expand...
Click to collapse
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
MCPoppa said:
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
Click to expand...
Click to collapse
Try flashing it to your recovery partition, my guess is that now that DM-verity is disabled everything should work fine
Cheers!
Quick update post after two days of usage, yesterday I noticed I didn't receive any notifications on missed calls, and that the caller ID always showed as a number although I had it added as a contact.
I realised that I didn't have any "Phone" app chosen as default in Android settings, so I was missing those notifications until I opened the Google Dialer app.
In case it happens to you, to sort it out go into Settings > Apps, then hit the gear in the top right corner and make sure you've a config similar to this one (Launcher3, Google's "Phone" and Google's "Messages" chosen as default Home, Phone and Messaging apps).
I hope this is clear for everyone, since it's not something I can fix on my side/requires the user to do the change
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Ianharding said:
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Click to expand...
Click to collapse
Firsts things first: After heavily modding the system like you did on Marshmallow, make sure not to update your device through the regular OTA but using a recovery image like the ones posted in this device's forum.
For magisk: are you sure you flashed it correctly? Magisk disables that dmverity message you are mentioning, so maybe you installed an old version or wasn't properly flashed.
My advice is: download everything: the recovery image, the debloater and Magisk. Boot into TWRP, wipe EVERYTHING if possible, including Data cache dalvik cache and system partitions. Once done, flash the recovery image zip, and right after that, without rebooting, flash the debloater and magisk. Reboot and everything should work perfectly
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
digidude512 said:
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
Click to expand...
Click to collapse
As soon as you root any Marshmallow/Nougat phone Android Pay will not work, according to this article
I have never used Android Pay so it doesn't make any difference to me. My phone is much better now that I have debloated it. I also installed Evie Launcher and Halo Browser, both small minimalist apps and everything is really smooth.
Instead of a Debloater, could the Stock ROM not be debloated and rezipped as a custom 'Lite' version?
After much searching I feel defeated for the moment. After unpacking the boot.img on my Chromebook and sifting through as much information as I can take I can only find the recovery.fstab! Where the heck does the main fstab / marlin.fstab live?
They moved them to another partition. To disable dm-verity, you have to recompile the kernel from source with this patch md: disable dm-verity. Or you can use SuperSU, but I'm not 100% sure about SuperSU.
Sent from my Pixel XL using Tapatalk
reddv1 said:
They moved them to another partition. To disable dm-verity, you have to recompile the kernel from source with this patch md: disable dm-verity. Or you can use SuperSU, but I'm not 100% sure about SuperSU.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I got it. I manipulated Magisk's install script to achieve my goal :highfive:
tdct12 said:
I got it. I manipulated Magisk's install script to achieve my goal :highfive:
Click to expand...
Click to collapse
Sorry for bothering you but could you upload a version of the newest Magisk with dm-verity disabled? Also could you explain what values you changed in the Magisk install script to disable dm-verity? I would like to know so I can also mod new Magisk releases for myself.
Edit: I think I've found what value I needed to change but I need a tester as I don't have access to my Pixel right now. Would anyone be willing to test out these 2 zips for me on the Stock Oreo May patch? You can switch your active slots so that if this doesn't work you can swap back to your ROM that does work. Instructions are below.
Instructions Part 1:
1.) Switch your active slot to the one you aren't using with either one of these commands:
fastboot --set-active=a
fastboot --set-active=b
2.) Extract the Bootloader, Radio, image-marlin-opm4.171019.016.b1.zip, and flash-all.bat
3.) Remove system_other.img from image-marlin-opm4.171019.016.b1.zip (this is done to prevent your other slot from being overwritten)
4.) remove the '-w' from flash-all.bat so that your line looks like this: fastboot update image-marlin-opm4.171019.016.b1.zip
5.) Flash all of the images using the flash-all.bat
Instructions Part 2:
boot into TWRP recovery
flash the Magisk-noVerityTest.zip
flash the Hosts-testOreoMay.zip (Note: not sure if this will flash on the Pixel XL due to the update binary, but it is confirmed to flash on the smaller Pixel)
boot into system and go to a site with a lot of ads (Ex. theverge) and see if any ads load up
This is a copy of my question on SO.
I want to remove Google apps and services on a new Fairphone 4 (Android 11, now rooted using Magisk. No TWRP build available yet.).
To this end, I am trying to use microG. In the Prerequisites for its usage, signature spoofing and deleting files in `system/priv-app` are listed. For signature spoofing, I followed the *XPosed solution for Android 11 and 12* listed here, i.e. using Magisk + riru + LSPosed + a FakeGApps fork. Not sure, whether or not this worked. All individual steps reported success, but the Signature Spoofing Checker says it didn't work.
Anyway, I'm definitely stuck at the second step, because I don't seem to be able to delete any files in `system_ext/priv-app`. I tried the solutions proposed here and here.
If I try
Code:
adb shell
su
# then confirm on the phone, then
mount -o rw,remount /
I get '/dev/block/dm-0' is read-only. Similar error (with dm-1) if I try mounting /system_ext.
adb root or adb disable-verity don't work, because it's a user build: adbd cannot run as root in production builds, verity cannot be disabled/enabled - USER build.
I even tried to write a Magisk module to replace the directories in question with empty ones, by putting the following in the customize.sh:
Code:
REPLACE="
/system_ext/priv-app/GoogleFeedback
/system_ext/priv-app/GoogleOneTimeInitializer
/system_ext/priv-app/GoogleServicesFramework
/system_ext/priv-app/SetupWizard
/system/system_ext/priv-app/GoogleFeedback
/system/system_ext/priv-app/GoogleOneTimeInitializer
/system/system_ext/priv-app/GoogleServicesFramework
/system/system_ext/priv-app/SetupWizard
"
I think /system/system_ext and /system_ext are hard linked, but not sure whether that matters. After loading that module and rebooting, the contents of those folders are still the same when checking with adb shell.
Any ideas?
For adb I'm using my desktop with Ubuntu 21.10.
Hello,
It's way easier than you can imagine. I did a tutorial there : https://forum.fairphone.com/t/tutorial-install-microg-on-fairphone-os/80016
But as you are quite advanced, the only thing you have to do is to install NanoDroid-MicroG with Magisk : https://downloads.nanolx.org/NanoDroid/Stable/
Just install the Zip and eventually update MicroG on the official website (version packed in NanoDroid is 17, newest one is 22...). This will erase all old Gapps.
PS :signature check spoofer don't work, the package you mentionned (which is the one I use also) only fake signature for Gapps, which is a good thing...
Thanks a ton! Looks like it worked, and it really wasn't more than installing that one module
Better use an ungoogled OS like LeOS-S. It's Android12L and works great an FP4
See https://leos-gsi.de
I have installed Lineage 18.1 GSI and trying to install gapps. I have rooted and using franko to flash opengapps pico and get an error 70 that there is not enough space on /system. What is the way to get this done? Thanks in advance!
I would like to know that as well.
Tried to flash via stock recovery but that aborted because signature verification failed.
Apps like Flashify, Flash Gordon, Flashfire or Rashr didn't work either.
With MagiskGapps-basic-module from wacko1805 the playservice framework always crashed.
I think the easiest and best way would be to flash opengapps via TWRP.
@ada12 seems to have a TWRP build that still has some bugs, but can be used to flash unsigned zip files.
Maybe he can share this with us.
I feel like this should not be a collasal effort, but it has become one. I have spent the whole day trying to figure it out. I want to use Lineage OS 18.1 with gapps from Andyyan, not any other rom.
psychofaktory said:
I think the easiest and best way would be to flash opengapps via TWRP.
Click to expand...
Click to collapse
I suspect that Magisk should be able to do whatever TWRP is doing (which is just putting some files in certain places, for the most part). Have you tried to find a Magisk module with OpenGapps? Or you can try making your own (but be warned that lzip is not available by default on any Android or Linux).
Edit: nevermind, I see you found a LiteGapps Magisk module.
Thanks @wirespot
The hint with the linked script to create a custom Magisk module on the preferred OpenGapps bundle was worth gold!
Now I have another problem that comes from installing the OpenGapps via Magisk.
For passing SafetyNet I have to add com.google.android.gms and com.google.android.gms.unstable to the deny list.
But when restarting Magisk all modules are reloaded. So also the OpenGapps module.
As a result, the adjustments to the deny list for the Google Play services are discarded again with every restart and the SafetyNet check fails.
How can I prevent that the two entries are no longer removed from the deny list?
Or how can I ensure that the entries are automatically added to the deny list on restart?
Edit:
It seems that this is what Magisk intended and com.google.android.gms and ...gms.unstable are automatically added to the deny list.
But now I have the question, how can I pass the SafetyNet test?
wirespot said:
I suspect that Magisk should be able to do whatever TWRP is doing (which is just putting some files in certain places, for the most part). Have you tried to find a Magisk module with OpenGapps? Or you can try making your own (but be warned that lzip is not available by default on any Android or Linux).
Edit: nevermind, I see you found a LiteGapps Magisk module.
Click to expand...
Click to collapse
Yes, but there is an issue with litegapps, the google contacts sync is broken unfortunately...
psychofaktory said:
It seems that this is what Magisk intended and com.google.android.gms and ...gms.unstable are automatically added to the deny list.
But now I have the question, how can I pass the SafetyNet test?
Click to expand...
Click to collapse
The deny list only lets you pass Basic check. To also pass CTS you need the USNF module (Universal SafetyNet Fix) and possibly other modules too. More details in this thread (check the end of the post), but try with just deny list and USNF first.
Neither the basic integrity check, nor cts profile match are passed.
Besides the denial list, I tried the modules "Shamiko", "Universal SafetyNet Fix" and "MagiskHide Props Config".
With the latter I have also tried various combinations, unfortunately unsuccessful in each case.
It looks like the deny-list does not work.
I suspect here also a connection with the message together that Magisk displays with each call:
Code:
An "su" command that does no belong to Magisk is detected. Please remove the other unsupported su
I have already been able to disable Phh-su with these commands:
Code:
adb shell
phh-su
mount -o remount,rw /
mount -o remount,rw /system
remount
mount -o remount,rw /
mount -o remount,rw /system
/system/bin/phh-securize.sh system.img
But the message in Magisk still appears.
Yeah passing SafetyNet with a custom ROM may be tricky. Didgeridoohan has a few more tips on their website you can try.
OK, I am already a big step closer to the solution.
After installing Magisk regularly, I first installed the Franco Kernel Manager.
Through this I was then able to flash UnSu.zip, which completely removed phh-su.
This also removed the message "An "su" command that does no belong to Magisk is detected" from Magisk.
Magisk had to be set up again afterwards, since it was also cleaned up by the UnSu script.
YASNAC now already showed "Basic integrity -> Pass".
But now I have not found a way to pass the CTS-profile match.
Does anyone here know what settings to set via MagiskHideProps Config?
And could someone send me the fingerprint of the stock rom (62.0.A.9.11)?
Code:
getprop ro.build.fingerprint
After some tests I discovered a big disadvantage with the variant to flash OpenGapps via Magisk.
Push notifications do not seem to work.
I use too many services that rely on Google Push notifications, so I can't do without them.
Compared to the "normal" variant of flashing OpenGapps via recovery before the first boot, the Magisk variant seems to be missing important dependencies and permissions that are only set during the first boot of the rom.
Therefore, the only useful variant is to flash GApps via recovery.
I really hope that we will soon have the possibility to flash unsigned zip files here!
Another approach:
Opengapps-zip files cannot be flashed via the stock recovery because it fails signature verfication.
The GSI roms can be flashed via the stock recovery. So they seem to be signed correctly.
Would it be possible to sign the Opengapps-Zip files with the same signature keys as the GSI-Roms to be able to flash them via the stock recovery?
Aren't GSI ROMs flashed through fastboot? Since they're partition images not zip installers like OpenGapps.
Of course. You are right.
Would it be possible to merge a GAPPS zip file into a GSI image and then flash the image with fastboot?
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.