Related
Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?
I totally know that feeling. I started with a tmo op7p, flashed international, unlocked bootloader, try to boot TWRP, and nope. Switch slot, it works. Flash it, great. Make a backup with TWRP of my working system, flash ROMaur, won't do anything but boot to TWRP. Open TWRP file manager and every file on internal storage is a ton of folders with jumbled strings of letters and numbers for names. MSM tool back to intl stock, try lineage... Nope. Keeps telling me to do a factory reset. I did, but I do another and still boot loop. MSM to intl, try other roms, same outcome.
I can unlock my bootloader and root it and run intl stock but that's it.
oxadedzn said:
Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?
Click to expand...
Click to collapse
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.
tech_head said:
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.
Click to expand...
Click to collapse
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)
JhinCuatro said:
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)
Click to expand...
Click to collapse
If you install TWRP on a 7 Pro without installing Magisk you will absolutely boot loop. If you wipe the system in one slot and have a differing ROM from the active slot you can in fact boot loop. Although the systems are different, the settings between the systems are shared.
Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system
Arden144 said:
Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system
Click to expand...
Click to collapse
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
You can also install TWRP if you like.
No computer needed.
This works.
tech_head said:
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
This works.
Click to expand...
Click to collapse
That's completely unnecessary and just avoiding the purpose of the a/b system.
All it would take is:
1. Local install
2. Install magisk to inactive slot
EDIT: After a few reboots, TWRP stopped working.. now if I try to enter recovery, I get into fastboot instead. But I can still boot the system fine and I still have Magisk. Sorry.. looks like TWRP on this version is still a no-go for now..
I leave the guide here to keep the discussion open, though.. and after the steps some more info on what exactly worked for me..
Hi all, the following steps worked for me (not really, see edit above), but as usual please proceed at your own risk, backup everything before, and be prepared to reinstall everything from scratch if something goes wrong. I am not responsible of anything that happens to your devices when following this guide.
Prerequisites:
- OnePlus 6 (might work also for 6t, but it's untested)
- Oxygen OS 9 open beta 25 (Might work also with the stable version, but again, untested)
- Enable the "advanced reboot" option in developer options.
- latest blu_spark TWRP installed (3.3.1 v9.101)
- if you have Magisk, make sure it's version 20.0 or later (previous versions don't support Android 10)
- if you have Magisk modules, it's highly recommended to disable or uninstall them before proceeding, as some of them might not be compatible with Android 10 and eventually cause a bootloop.
- A computer that is able to run fastboot commands and that you can connect your phone to.
Now, the steps:
- Reboot into TWRP, open the "reboot" menu and take a note of your current active slot (can be a or b)
- Go back to Oxygen OS and install Android 10 open beta 1 through system updates. At the end of the installation, DO NOT PRESS "REBOOT".
- Press the power button and from the advanced reboot menu, reboot into bootloader.
- Connect the phone to the pc.
- If your active slot, noted in the first step, was "a", type "fastboot --set-active=a" . If it was "b", use the same command but replace the final letter with "b".
- On the phone, use the volume buttons to select "recovery mode", and press the power button to confirm.
- You should now be into TWRP: install TWRP again using its installation zip file, DO NOT REBOOT.
- Go to the reboot menu, and change the active slot to the other one (depending on your currently active one).
- Still in TWRP, reboot to recovery.. you should land in TWRP again.
- If you had Magisk, or if you want it, flash it.
- Reboot to system.
If everything goes well, you should now be on Oxygen OS 10 open beta 1, with TWRP installed!
Note: the current version of TWRP does not support flashing the new OnePlus open betas, so when a new open beta is released and you want to update, you will have to go through this process again (until a new compatible TWRP is released).
EDIT 2: Just to give some more information in case someone else wants to try, here's what I did AFTER the steps below:
- Rebooted into OOS open beta 1, just to check that it was booting.. worked.
- Rebooted into TWRP and did a complete wipe, including the internal storage (I wanted a clean install of OB1)
- Rebooted into OOS and did the phone setup (Google account, ecc) including setting up a lockscreen pattern, but no figerprints yet.
- Rebooted again into TWRP to install Magisk, and everything worked, TWRP also asked for my pattern and decrypted data correctly
- After that I didn't reboot anymore for a while, and completed the setup with apps, fingerprints, etc.. and also installed a magisk module (quickswitch), but without using recovery.
- The next time I tried to reboot into recovery, I wasn't able anymore.. I was getting into fastboot instead, but the system can still boot just fine.
cc_rock said:
Hi all, the following steps worked for me, but as usual please proceed at your own risk, backup everything before, and be prepared to reinstall everything from scratch if something goes wrong. I am not responsible of anything that happens to your devices when following this guide.
Prerequisites:
- OnePlus 6 (might work also for 6t, but it's untested)
- Oxygen OS 9 open beta 25 (Might work also with the stable version, but again, untested)
- Enable the "advanced reboot" option in developer options.
- latest blu_spark TWRP installed (3.3.1 v9.101)
- if you have Magisk, make sure it's version 20.0 or later (previous versions don't support Android 10)
- if you have Magisk modules, it's highly recommended to disable or uninstall them before proceeding, as some of them might not be compatible with Android 10 and eventually cause a bootloop.
- A computer that is able to run fastboot commands and that you can connect your phone to.
Now, the steps:
- Reboot into TWRP, open the "reboot" menu and take a note of your current active slot (can be a or b)
- Go back to Oxygen OS and install Android 10 open beta 1 through system updates. At the end of the installation, DO NOT PRESS "REBOOT".
- Press the power button and from the advanced reboot menu, reboot into bootloader.
- Connect the phone to the pc.
- If your active slot, noted in the first step, was "a", type "fastboot --set-active=a" . If it was "b", use the same command but replace the final letter with "b".
- On the phone, use the volume buttons to select "recovery mode", and press the power button to confirm.
- You should now be into TWRP: install TWRP again using its installation zip file, DO NOT REBOOT.
- Go to the reboot menu, and change the active slot to the other one (depending on your currently active one).
- Still in TWRP, reboot to recovery.. you should land in TWRP again.
- If you had Magisk, or if you want it, flash it.
- Reboot to system.
If everything goes well, you should now be on Oxygen OS 10 open beta 1, with TWRP installed!
Note: the current version of TWRP does not support flashing the new OnePlus open betas, so when a new open beta is released and you want to update, you will have to go through this process again (until a new compatible TWRP is released).
Click to expand...
Click to collapse
Anyone tried?
This sounds plausible. Nice!
Question though, how much working functionality remains? Can TWRP be used to install zips, clear cache, do factory reset, install magisk stuff, etc..? Are these still compatible with android 10? Have you tried to do something with it?
kyljys said:
This sounds plausible. Nice!
Question though, how much working functionality remains? Can TWRP be used to install zips, clear cache, do factory reset, install magisk stuff, etc..? Are these still compatible with android 10? Have you tried to do something with it?
Click to expand...
Click to collapse
Hi, first of all, see the edit above.. looks like my TWRP stopped working now.. but it was working for a while.
Initially I was able to flash TWRP itself, and then flash Magisk (which still works) .. not sure exactly when TWRP stopped working.
I bet it stopped working after magisk install. It does the same fir the stock recovery also. No recovery, goes to bootloader.
Oh.. So that means we either have twrp and no root... Or root and no recovery... Choose whatever one wants... Hehe.. Thnx op for the efforts though
cc_rock said:
Hi, first of all, see the edit above.. looks like my TWRP stopped working now.. but it was working for a while.
Initially I was able to flash TWRP itself, and then flash Magisk (which still works) .. not sure exactly when TWRP stopped working.
Click to expand...
Click to collapse
One thing to try would be installing magisk 19.4 from twrp. In canary thread there's a discussion on this very problem with other oneplus devices with A10 and magisk 20.1 that the recovery disappears. Magisk 19.4 did have some fixes regarding Android 10, maybe worth a shot?
Though we could wait the next version of magisk as this problem seems to be under investigation.
I'm able to to keep twrp with magisk 19.3
[email protected] said:
I'm able to to keep twrp with magisk 19.3
Click to expand...
Click to collapse
Ive also managed to do this after a fair bit of fiddling. A quick guide below as im off to bed.
1) you need to be rooted
2) Flash twrp installer in magisk manager (twrp-3.3.1-x_blu_spark_v9.101_op6.zip)
3) reboot to bootloader
3) fastboot flash boot boothybridbeta2.img ( https://drive.google.com/open?id=1JCltKatjRUk1XdEibAme8MnDJxMkzhwE ) boot image is from [ROM][PORT][10.0.0] OnePlus7 Open Beta 3 Port for OnePlus 6 [12.10.19]
4) fastboot reboot
5) reboot to recovery via adb
6) run magisk uninstaller.zip
7) flash stock boot.img in twrp
8) flash twrp installer.zip
9) reboot recovery (to see if it works)
10) reboot phone and choose boot to recovery from phone system again to test it works
11) install magisk v19.3 installer zip in twrp
12) reboot
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
kold11 said:
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
Click to expand...
Click to collapse
To force restart I need to use power button and both volume keys..
To keep TWRP you need to flash rom, then without restart flash TWRP again, then restart TWRP, then flash Magisk.
Likely the r reason why your system doesn't boot is because it can't decrypt your data.
Why this happens I don't know, maybe in the upgrade they changed something related to the exception and then by downgrading again it isn't able to read it anymore.
I would suggest to:
Flash the latest rom.
Flash TWRP
Reboot TWRP
If TWRP then doesn't ask for PIN or password, then I'm afraid you have lost your data. I hope you have a backup.
I'm that case format (not just clear) data -> yes
Reboot TWRP
Then flash Magisk.
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
kold11 said:
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
Click to expand...
Click to collapse
I would suggest do restore your device with msm unbrick tool.
1. From recovery, turn off (i noticed, that when tried to turn off from somewhere else, the device would auto reboot later in downlaod mode)
2. In windows, turn off the connection & open device manager: Get this driver http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab
3. Press volume/down + volume/up, after about 5s connect to pc
4. Your device should show up in device manager, open it and install the driver manuell from step 2 (keep device options open... if fail you need to uninstall the driver before trying again)
5. Now wait for about 40s, if your device stays in download mode, you can open & start the msm tool (leave the options in msm as they are)
6. It will take about 280s, then the device will reboot.... (its normal that it stays longer at the oneplus logo at first start)
MSM Thread: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
I've also uploaded the 10.0.5OOS Unbrick tool on mega, because android file hosted downloads are so terrible: https://mega.nz/file/ArZFkYpS#Z_rOIwZeYN27IG6L8rOi-yfw8wXGiwvK-uWVDlsmvTI
Hi all,
Yesterday I was messing around with V4A and following the final installation steps my phone got stuck in fastboot. To fix it I did the following:
1. I extracted the stock boot.img from my current OS version (10.3.12) and flashed it to boot_a and boot_b using fastboot. This restored the phone's ability to boot.
2. I booted the phone and went into the Magisk app to disable/unhide as much as possible and uninstalled the V4A app.
3. Rebooted into fastboot and booted into TWRP to remove Magisk, V4A and Vanced stuff from data/adb with the file manager.
4. Booted and flashed various combinations of TWRP versions (Mauronofrio, Bluspark) and Magisk (from 19.4 to 23.0). TWRP flashes fine and allows system to boot, but as soon as Magisk is flashed and a reboot is tried into system, it gets stuck on bootloader again and I have to repeat step 1.
(5. Tried patching stock boot.img file with the Magisk app. Same results as step 4.)
Does anyone here know what might be wrong? Is there another method I can try to regain Magisk without losing data?
Thanks in advance!
EDIT: really at a loss here. Idk why but as soon as magisk is flashed, the system refuses to boot. Without flashing magisk, system boots fine – am typing from it now. I figured at first that it had to do with remnants of AML, V4A and other Magisk modules not being properly removed, but I've removed those through TWRP file manager.
Really hoping one of you can point out something I've missed or think of something else I can try.
EDIT: solved! See update below.
UPDATE: solved it by forcing a local upgrade of the full OTA through phone settings (same version as mentioned above), causing it to switch slots. On the other slot, the system managed to boot after flashing TWRP and Magisk (latest versions).
I have Android 13 on my Pixel 6a with Magisk, Root and AOSPMod. After the update was downloaded, I followed these steps (https://topjohnwu.github.io/Magisk/ota.html):
Use "restore images" function in Magisk app to have a clean system
Apply the update
Instead of rebooting from the update, use "install to inactive slot" in Magisk app
When finished, press reboot in Magisk app
This lead to the phone displaying a "this phone is corrupt" message on bootup. It did not do this before. Also, it then got stock on colorful Google logo.
I had this happen twice, both times after a couple minutes I held all buttons for some time so the phone would reset.
Finally, the phone would boot again (as I understand it) from the old slot.
Magisk is now not installed anymore (due to step 1). In System / Update dialog I am still offered to reboot into the update (the new slot which didn't boot).
How should I proceed?
My intuition is to download, patch and flash most recent image through Pixelflasher.
ypnos42 said:
I have Android 13 on my Pixel 6a with Magisk, Root and AOSPMod. After the update was downloaded, I followed these steps (https://topjohnwu.github.io/Magisk/ota.html):
Use "restore images" function in Magisk app to have a clean system
Apply the update
Instead of rebooting from the update, use "install to inactive slot" in Magisk app
When finished, press reboot in Magisk app
This lead to the phone displaying a "this phone is corrupt" message on bootup. It did not do this before. Also, it then got stock on colorful Google logo.
I had this happen twice, both times after a couple minutes I held all buttons for some time so the phone would reset.
Finally, the phone would boot again (as I understand it) from the old slot.
Magisk is now not installed anymore (due to step 1). In System / Update dialog I am still offered to reboot into the update (the new slot which didn't boot).
How should I proceed?
My intuition is to download, patch and flash most recent image through Pixelflasher.
Click to expand...
Click to collapse
The "Install to Inactive Slot" method in Magisk doesn't seem to be working for most on the Pixel 6 series at this time. Pixel Flasher or Android Flash Tool are probably your best options at this time. Also, if you haven't already, make sure you have the A13 bootloader on both slots to avoid the new ARB fiasco.