Related
So the A/B structure of the Pixel (I came from Nexus 5X) took some getting used to, not having a recovery partition was a new wrinkle, and the jimmy jammy required to unlock the bootloader (I bought a Verizon Pixel apparently) was a neat trick. So I got the Pixel bootloader unlocked, booted with TWRP, installed Lineage, rebooted to bootloader, fastboot booted to TWRP, installed TWRP and OpenGapps.. Excellent! Setup the phone, booted to TWRP and installed Magisk. eveything works! great phone!
Then, a week later there is an update to Lineage. So I copy the ZIP file to my phone, flash it and OpenGapps and reboot. Boom. all screwed up. no problem, I'll restore from the backup I made in TWRP. nope. bootloop. then I read that you restore BOOT,SYSTEM IMAGE,VENDOR IMAGE, and DATA. NOT all the partitions as I had naively thought. Turns out I boned the backup and didn't backup the DATA partition so the Restore works but all my setup stuff is gone. My fault.
I went through the entire process again. Phone is working fine. All is well. Heres the question: What is the appropriate method to upgrade Lineage when a new one is released? So that I end up with new lineage, updated OpenGapps, TWRP working, and Magisk keeping me rooted? I can just keep trying to figure it out but I dont want to keep starting at zero with my phone.
Thanks in advance. I searched diligently on the forums but it looks like not that many Pixel users use Lineage.
Cheers
d.
130 views and no one knows how you upgrade LineageOS? is anyone using Lineage on their Pixel? Really?
I just discovered Lineage OS for my VZW Pixel. What build did you use? If I can figure out how to install, I'll try playing with updating, too.
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
SkinnyT said:
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
Click to expand...
Click to collapse
Probably here: https://download.lineageos.org/sailfish
post-mortem said:
Probably here: https://download.lineageos.org/sailfish
Click to expand...
Click to collapse
I probably should have looked there. I didn't even realize they supported the pixel. It's been a while since I've messed with things.
I've been using LineageOS and it's great. Super stable compared to most of the other ROMs I've tested. These are the steps I take when upgrading to a newer build.
- reboot to recovery (TWRP)
- install lineage-15.1-xxx-nightly-sailfish-signed.zip (no wipe or anything beforehand)
- install twrp-pixel-installer-sailfish-xxx.zip
- return to TWRP main menu and select reboot, then Recovery (whenever it prompts me to install TWRP app I just hit "Do Not Install")
- once back in TWRP, install MindTheGapps-8.1.0-arm64-xxx.zip
- reboot to system (again, I always decline the TWRP app installation)
- once you've booted to system, reboot to recovery one last time.
- install Magisk-v17.x.zip
- reboot to system and you should be good to go.
I always have a recent backup from TitaniumBackup stored on my computer so if anything goes wrong I can do a clean install and reload all my apps.
awesome. I'll try that. I'm using 15.1 10/23/2018 version and I have backed up so I'll do it. one question, do you reboot between installing lineage zip and twrp installer?
SkinnyT said:
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
Click to expand...
Click to collapse
yeah I got it from lineage website. have you managed to update using Crawdads method?
dcarrco said:
awesome. I'll try that. I'm using 15.1 10/23/2018 version and I have backed up so I'll do it. one question, do you reboot between installing lineage zip and twrp installer?
Click to expand...
Click to collapse
No. Install TWRP immediately after installing the Lineage zip, before rebooting. Otherwise when you reboot to recovery it'll be the Lineage recovery and then you'll need a computer to send any other files you want to flash.
Also, they just started releasing builds every 24 hours. You might want to check the changelog every few days to see if there is anything new that's worthwhile. Some days there may actually not be any changes at all.
@CapriciousCrawdad
well I tried it today, just as you have it written in your post (other than what I assume was a typo where you say "return to lineage" in step 4 where I think you meant TWRP) and what it looks like is my working installation is on partition A and after installing as you specified it tried to boot on B and couldnt get past the Google screen. so I finally got it to reboot into TWRP and switched back to A and got my phone going again with my old October revision. the only difference is that I use OpenGApps and not MindTheApps. so tomorrow I'll try it with those.
CapriciousCrawdad said:
No. Install TWRP immediately after installing the Lineage zip, before rebooting. Otherwise when you reboot to recovery it'll be the Lineage recovery and then you'll need a computer to send any other files you want to flash.
Also, they just started releasing builds every 24 hours. You might want to check the changelog every few days to see if there is anything new that's worthwhile. Some days there may actually not be any changes at all.
Click to expand...
Click to collapse
dcarrco said:
@CapriciousCrawdad
well I tried it today, just as you have it written in your post (other than what I assume was a typo where you say "return to lineage" in step 4 where I think you meant TWRP) and what it looks like is my working installation is on partition A and after installing as you specified it tried to boot on B and couldnt get past the Google screen. so I finally got it to reboot into TWRP and switched back to A and got my phone going again with my old October revision. the only difference is that I use OpenGApps and not MindTheApps. so tomorrow I'll try it with those.
Click to expand...
Click to collapse
Whoops. Indeed, that was a typo in step 4. I edited the post.
Not sure about your problem though... I do remember specifically reading that opengapps can cause some issues but I can't find the source of that info and I don't think that it had anything to do with updating the system. I'm on mobile now but I might have time to check it out tomorrow.
If you haven't already, I suggest you check out the official LineageOS thread for the Pixel and Pixel XL. There might be some helpful info there.
CapriciousCrawdad said:
Whoops. Indeed, that was a typo in step 4. I edited the post.
Not sure about your problem though... I do remember specifically reading that opengapps can cause some issues but I can't find the source of that info and I don't think that it had anything to do with updating the system. I'm on mobile now but I might have time to check it out tomorrow.
If you haven't already, I suggest you check out the official LineageOS thread for the Pixel and Pixel XL. There might be some helpful info there.
Click to expand...
Click to collapse
yes thats where i ended up. tried to update and got bootlooped, my backup didnt work for some reason (do i backup EFS partition also?) so i started again with the instructions in that post. i used the Gapps package from @razorloves and it all worked. setup my phone again and now it upgrades fine using the Lineage updater although i have to reinstall TWRP and reroot (using SuperSU from Lineage) when that happens. razorloves hasnt updated his google FI compatible Gapps package yet so i will see how/if i can update those when the times come. on a side note, im getting really good at setting up my pixel. got to look at the upside.
thanks for your suggestions.
I rooted following Maxwell's tutorial (OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk
).
Now that all is said and done, and my phone is rooted, I noticed that:
1) The wifi does not work. It will not let me enable wifi. Just keeps switching back to off.
2) The speakers don't work.
I need to know how to fix it. What do I do?
I am new to android so I am not sure the steps needed to fix this botched install/operating system/root whatever
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
download
Bradl79 said:
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
Click to expand...
Click to collapse
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
jfny100 said:
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
Click to expand...
Click to collapse
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Bradl79 said:
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
Click to expand...
Click to collapse
Okay. That was it (flashing the wrong boot.img) It's working now - I upgraded to latest OS. Downloaded correct boot.img. Redid the root process with correct files this time, and it worked. Wifi is good. Speakers are good. Everything is good. Thanks for the help. Also, I removed any criticism of the tutorial creators in my post since it turns out I was the idiot. I'm brand new to android though so go easy on me.
djsubterrain said:
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Click to expand...
Click to collapse
I didn't read the post until after I encountered errors. I was going off of the video. One problem I had was that the video assumed I had a basic knowledge of some steps, so they didn't mention them. I did not have this knowledge since I am brand new to android. Anyways. I was able to fix these errors via the steps discussed in earlier comments. Everything is working now. I removed any criticism of the tutorial creators from this post since it turns out I'm the idiot.
Glad you got it working
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
BC that is just an extra step not really needed, I haven't even flashed twrp on my device yet, if I need it I will just boot to it, it's so much easier doing this.
I always thought the same thing u did, until I just flashed the patched boot and updating is so much easier too.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
Because I'm just following along with the tutorial xda put on YouTube and that's what they say to do
Hey guys!
I have a rooted pixel 3. I want to upgrade to Android 10 if they release in the next day or so as reported. I've read they made some progress with magisk...
What is my best bet here?
I would love to keep root, but most importantly I want to keep my data and upgrade to Android 10.
I do really want to keep root too.
Is there a guide?
Thanks!
I had Q beta 6 working with current process. Canary channel still only works by patching your boot.IMG. So with twrp still not working on beta 6. All instructions say image flash not possible upgrade path. So until 10 is stable + twrp stable I don't know either. I will just flash 10 and see also. But I really don't expect data to retain, will try though.
kkjb said:
I had Q beta 6 working with current process. Canary channel still only works by patching your boot.IMG. So with twrp still not working on beta 6. All instructions say image flash not possible upgrade path. So until 10 is stable + twrp stable I don't know either. I will just flash 10 and see also. But I really don't expect data to retain, will try though.
Click to expand...
Click to collapse
This is a build of blueline TWRP-3.3.1 from the crosshatch tree that is supposedly working from a follow-up post.
https://forum.xda-developers.com/pi...pixel-3-xl-t3861623/post79995400#post79995400
So is there no way to root just now?
I upgraded from a rooted Android 9 by downloading the factory image for 10 and removing -w from the bat file. All okay, data retained.
But there is no TWRP that works and I tried to fastboot boot a magisk patched boot image from the factory image zip file and it didn't work.
Audioboxer said:
I tried to fastboot boot a magisk patched boot image from the factory image zip file and it didn't work.
Click to expand...
Click to collapse
That works, did it myself. Make sure you are on the latest canary build of Magisk.
TonikJDK said:
That works, did it myself. Make sure you are on the latest canary build of Magisk.
Click to expand...
Click to collapse
Thanks, I was on beta.
Does edxposed work with android 10?
Bubbler4343 said:
Does edxposed work with android 10?
Click to expand...
Click to collapse
It did not work on Android Q Beta 6... just bootlooped. So I am assuming it still does not work for 10.
It does not work for me, guess I should have removed my magisk modules before updating :crying:
TWRP also seems not to work so I see no way to remove these modules now...
Does anyone have a suggestion besides wiping the device?
stilltli said:
It does not work for me, guess I should have removed my magisk modules before updating :crying:
TWRP also seems not to work so I see no way to remove these modules now...
Does anyone have a suggestion besides wiping the device?
Click to expand...
Click to collapse
Did you try the twrp version in post #3?
Just got a notification for upgrading to android 10 , date Tuesday 10.19 pm.
Since there is no xposed available for Android 10, i' ll stick to android 9
Looks like TWRP won't decrypt. Has anyone ADB sideloaded the Canary version of Magisk through TWRP? That was the old workaround when decryption didn't work.
stilltli said:
It does not work for me, guess I should have removed my magisk modules before updating :crying:
TWRP also seems not to work so I see no way to remove these modules now...
Does anyone have a suggestion besides wiping the device?
Click to expand...
Click to collapse
I was under the impression that fastboot of twrp-3.3.1-0-blueline could be used for certain things in 10 (possibly flashing Magisk uninstaller). Also, be sure you have the canary uninstaller.
jd1639 said:
Did you try the twrp version in post #3?
Click to expand...
Click to collapse
I assumed it was for 3XL only, glad you pointed that out! It does boot, however TWRP is not able to mount anything (system, data etc.), so I guess this is a dead end.
sliding_billy said:
I was under the impression that fastboot of twrp-3.3.1-0-blueline could be used for certain things in 10 (possibly flashing Magisk uninstaller). Also, be sure you have the canary uninstaller.
Click to expand...
Click to collapse
As stated above I am unable to access any partitions, so I guess I'm also unable to run the uninstaller :crying:
Thank you both for your suggestions :good:
jd1639 said:
Did you try the twrp version in post #3?
Click to expand...
Click to collapse
I have tried, and it doesn't decrypt from what I see (booted into TWRP, but no file access)
Uhh,so now, android 10 can root or not!?
My English isn't good....
So hope someone tell me root is work or not
Edemilorhea said:
Uhh,so now, android 10 can root or not!?
My English isn't good....
So hope someone tell me root is work or not
Click to expand...
Click to collapse
I rooted 10 with no issues.
sliding_billy said:
I rooted 10 with no issues.
Click to expand...
Click to collapse
Oh cool！！
So just fellow android 9 root step on android 10?
It's worked?
Edemilorhea said:
Oh cool！！
So just fellow android 9 root step on android 10?
It's worked?
Click to expand...
Click to collapse
No, you have to use a Magisk patched boot with canary magisk. Not even close to the old way. No TWRP. Lot of info on here. You might want to start reading before jumping in.
Manually patching the boot image with the canary build "works" - as in - it shows Magisk installed in Magisk Manager and can grant Superuser to apps --- BUT, you can't write to system, so things like Adaway don't work, also Google Pay doesn't work. I'm not sure what you use root for, but this makes it fairly useless to me for now.
Hello everyone, I have the OP9 china varient,
I've flashed custom ROMs in some devices in the past, specially on a Poco F1 and a Mi 11 Ultra (flashed MIUI.EU in it several times). With the OnePlus 9 the process with unlocking the bootloader was a bit different but I got it to work. But when it comes to custom ROMs installation, the end result is always a bricked device and I had to use MSM from OP9 pro to unbrick and then OP9 MSM to get the device back to normal. I've downgraded everytime to OxygenOS 11 but it didn't work. Can someone help me find out what am I doing wrong?
My procedure besides unlocking the bootloader was:
1. Install boot.img
2. From fastboot to recovery
3. Wipe everything (tried not doing it with the same result)
4. Install ROM via ADB (as an update)
5. Wipe everything (tried not doing it with the same result)
6. Reboot
7. Brick..
I've considered it being an ADB drivers problem, but the device is recognized in the computer as an ADB device so I don't think it is.
As I install through ADB, the CMD window keeps the percentage going up but on the device it never shows anything ROM related as it is being installed, just the final message saying steps 2/2 had been completed.
Thanks in advance, and happy flashing guys!
Change to slot A before flashing. Slot B just doesn't flash right most of the time. Sometimes the device still bricks despite doing everything right though and after the last one, I just went back to stock and stayed there. It's far less likely to brick if you're flashing slot A though in my experience.
You are making sure to use the posted recovery image with each ROM as well, right?
Try StagOS as it was the least problematic for me, both flashing and in terms of bugs. Go to slot A like I recommended and then follow the instructions including flashing the copy partitions zip.
EtherealRemnant said:
Change to slot A before flashing. Slot B just doesn't flash right most of the time. Sometimes the device still bricks despite doing everything right though and after the last one, I just went back to stock and stayed there. It's far less likely to brick if you're flashing slot A though in my experience.
You are making sure to use the posted recovery image with each ROM as well, right?
Try StagOS as it was the least problematic for me, both flashing and in terms of bugs. Go to slot A like I recommended and then follow the instructions including flashing the copy partitions zip.
Click to expand...
Click to collapse
Hey, I've only tried Nameless OS and EvolutionX.
The think I liked about the Poco F1 is that it had no Slot A/B mess (though I've heard A/B slot is better overall).
I'm pretty sure both recoveries went straight to slot A but I might be wrong.
To be fair, stock OOS12 is working fairly good. I just like to help developing custom ROMs and try new stuff. Next time I find time to mess with the phone I'll try StagOS as you suggested. Thank you for your time and opinion.
lleonardocruzz said:
Hey, I've only tried Nameless OS and EvolutionX.
The think I liked about the Poco F1 is that it had no Slot A/B mess (though I've heard A/B slot is better overall).
I'm pretty sure both recoveries went straight to slot A but I might be wrong.
To be fair, stock OOS12 is working fairly good. I just like to help developing custom ROMs and try new stuff. Next time I find time to mess with the phone I'll try StagOS as you suggested. Thank you for your time and opinion.
Click to expand...
Click to collapse
If you use the copy partitions zip before you flash and then you reboot recovery, you end up with both partitions having the same data before you flash and much less likelihood of a brick. Also, don't clear data after you flash, that caused me to reboot to fastboot when I was done flashing and at that point I couldn't recover the OS and had to use the MSM.
I am not a fan of the A/B system but I will say that my Pixel 3 XL didn't have this issue.
EtherealRemnant said:
If you use the copy partitions zip before you flash and then you reboot recovery, you end up with both partitions having the same data before you flash and much less likelihood of a brick. Also, don't clear data after you flash, that caused me to reboot to fastboot when I was done flashing and at that point I couldn't recover the OS and had to use the MSM.
I am not a fan of the A/B system but I will say that my Pixel 3 XL didn't have this issue.
Click to expand...
Click to collapse
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
lleonardocruzz said:
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
Click to expand...
Click to collapse
It's only mentioned in the Stag thread and I think Lineage too but it should work with every ROM since it's only a recovery script that copies the partitions.
lleonardocruzz said:
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
Click to expand...
Click to collapse
Copy partitions is def what you need. Your using msm then trying to flash. If you took an ota or used copy partitions after msm. You will be all good. Oos has to be on both slots. This is your issue
mattie_49 said:
Copy partitions is def what you need. Your using msm then trying to flash. If you took an ota or used copy partitions after msm. You will be all good. Oos has to be on both slots. This is your issue
Click to expand...
Click to collapse
so, basically I need to have OOS11 and ensure it is in both slots (by copying the partitions) right? I'm feeling so dumb right now ahah I was going crazy over this
lleonardocruzz said:
so, basically I need to have OOS11 and ensure it is in both slots (by copying the partitions) right? I'm feeling so dumb right now ahah I was going crazy over this
Click to expand...
Click to collapse
It's easier to take an ota update to get oos on both slots truly. Go into system updates. Make sure it's A 11. Seamless updates . However you can do it get it done. Then flashing will be fine.
Can you tell me what is the easiest way to downgrade from A12 to A11 (latest OOS)? The only way I've found was through MSM. It is impossible to install A11 while already being on A12 through OTA right? You're helping me a lot btw, thank you
lleonardocruzz said:
Can you tell me what is the easiest way to downgrade from A12 to A11 (latest OOS)? The only way I've found was through MSM. It is impossible to install A11 while already being on A12 through OTA right? You're helping me a lot btw, thank you
Click to expand...
Click to collapse
There is a downgrade package posted in the forums here. You install the local upgrade APK and then flash the downgrade package.
[OnePlus 9][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
The link to the APK is in the post.
Haven't flashed required firmware in both slots.To do this,flashing copy partions before installing custom rom and then reboot phone to recovery to install custom rom.
mattie_49 said:
It's easier to take an ota update to get oos on both slots truly. Go into system updates. Make sure it's A 11. Seamless updates . However you can do it get it done. Then flashing will be fine.
Click to expand...
Click to collapse
EtherealRemnant said:
There is a downgrade package posted in the forums here. You install the local upgrade APK and then flash the downgrade package.
[OnePlus 9][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
The link to the APK is in the post.
Click to expand...
Click to collapse
cbrown666 said:
Haven't flashed required firmware in both slots.To do this,flashing copy partions before installing custom rom and then reboot phone to recovery to install custom rom.
Click to expand...
Click to collapse
I'm replying to everyone so that you know that I was successful. It was indeed a partition's problem. Sadly I didn't find the ROM as stable as OOS 12 or OOS 11 so I guess I'll stick with Oneplus software for the time being. Thank you so much for the help
lleonardocruzz said:
I'm replying to everyone so that you know that I was successful. It was indeed a partition's problem. Sadly I didn't find the ROM as stable as OOS 12 or OOS 11 so I guess I'll stick with Oneplus software for the time being. Thank you so much for the help
Click to expand...
Click to collapse
Glad that you got it sorted.
I found the same thing. I'm back on OOS12 C.48 with root. Browsing performance sucks with the CPU throttling they do, and they changed the way they do it so the fixes posted in the 9 Pro forum don't work anymore, but it's otherwise better than all the custom ROMs I tried and I don't have much to complain about.
EtherealRemnant said:
Glad that you got it sorted.
I found the same thing. I'm back on OOS12 C.48 with root. Browsing performance sucks with the CPU throttling they do, and they changed the way they do it so the fixes posted in the 9 Pro forum don't work anymore, but it's otherwise better than all the custom ROMs I tried and I don't have much to complain about.
Click to expand...
Click to collapse
I have to agree with both. I'm also a global unit op9 unlocked on C-48 rooted. Anything that is usually still maintained/updated and not deserted is better than custom. Cherry picking and flashing is overrated. Stock isn't bad at all. You guys enjoy your devices.
I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
a quick search didn't turn up the stock boot image for my existing ROM version (IN2025_11_f.15)
I figure it may be easier to just update and lose root, then re-root with the new boot image, but I've had some issues doing what I thought would be easy, but turned into big issues, so before I start down this path, I wanted to ask what may be the best way to go from where I am...
(rooted with Magisk, but no stock boot.img, running build number IN2025_11_F.15, Baseband version Q_V1_P14)
...to getting onto the latest version my phone is offering (IN2025_11.F.62_2620_202301162204) and get Magisk fixed so that it then has a stock boot image, so I can update later by just uninstalling/restoring images, installing the update, then rebooting to the inactive slot, which worked fine for years.
Thanks in advance for any help/guidance doing so.
JustinChase said:
I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
a quick search didn't turn up the stock boot image for my existing ROM version (IN2025_11_f.15)
I figure it may be easier to just update and lose root, then re-root with the new boot image, but I've had some issues doing what I thought would be easy, but turned into big issues, so before I start down this path, I wanted to ask what may be the best way to go from where I am...
(rooted with Magisk, but no stock boot.img, running build number IN2025_11_F.15, Baseband version Q_V1_P14)
...to getting onto the latest version my phone is offering (IN2025_11.F.62_2620_202301162204) and get Magisk fixed so that it then has a stock boot image, so I can update later by just uninstalling/restoring images, installing the update, then rebooting to the inactive slot, which worked fine for years.
Thanks in advance for any help/guidance doing so.
Click to expand...
Click to collapse
Does it work if you try to update without unrooting?
JustinChase said:
I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
<snip>
Click to expand...
Click to collapse
That happens if you flash a Magisk patched boot image instead of booting it and then using direct install.
TheNewHEROBRINE said:
Does it work if you try to update without unrooting?
Click to expand...
Click to collapse
No. I think the update isn't a full ROM. I believe read somewhere that works when the update is a full ROM
I'm just not sure how to 'start over' to get a stock image saved so Magisk will let me restore again, without having to wipe the phone.
JustinChase said:
No. I think the update isn't a full ROM. I believe read somewhere that works when the update is a full ROM
I'm just not sure how to 'start over' to get a stock image saved so Magisk will let me restore again, without having to wipe the phone.
Click to expand...
Click to collapse
White don't you ask in the 8/8 Pro (I'm assuming that's what you have) forums if someone can provide you with a stock boot image for your current OOS version?
Note that this is an 8T forum so you don't get people here providing you with a copy.
BillGoss said:
White don't you ask in the 8/8 Pro (I'm assuming that's what you have) forums if someone can provide you with a stock boot image for your current OOS version?
Note that this is an 8T forum so you don't get people here providing you with a copy.
Click to expand...
Click to collapse
Oh, sorry.
I did think this was an 8 Pro forum
I'll find that and repost
Thanks