Related
I have flashed stock from googles web site and I have tried everything I can to get a custom rom back on this device. I have tried everything. every thing I do just boots to regular google. But I can flash twrp, and magisk on stock and it works. OEM is unlocked but as soon as I flash a rom then twrp and sign it, it says its successful for everything but when I boot to system it just reboots a couple times then boots but up to stock. Any one have any ideas?
KingAroan said:
I have flashed stock from googles web site and I have tried everything I can to get a custom rom back on this device. I have tried everything. every thing I do just boots to regular google. But I can flash twrp, and magisk on stock and it works. OEM is unlocked but as soon as I flash a rom then twrp and sign it, it says its successful for everything but when I boot to system it just reboots a couple times then boots but up to stock. Any one have any ideas?
Click to expand...
Click to collapse
This is normal. Your custom ROM is flashing to the opposite slot your on. When your done u need to reboot to bootloader and boot twrp then install TWRP again and install verified boot signer zip. If not just going to loop once and boot to the slot that works
mac796 said:
This is normal. Your custom ROM is flashing to the opposite slot your on. When your done u need to reboot to bootloader and boot twrp then install TWRP again and install verified boot signer zip. If not just going to loop once and boot to the slot that works
Click to expand...
Click to collapse
I will try that's next time. I just went through hell trying get back on the RR ROM and rooted with magisk. But I finally got it haha. Took about 20 stock flash's to get it finally working
KingAroan said:
I will try that's next time. I just went through hell trying get back on the RR ROM and rooted with magisk. But I finally got it haha. Took about 20 stock flash's to get it finally working
Click to expand...
Click to collapse
Yea once you do it a couple of times you will have it down. Just remember from May bootloader's on, you have to use that VBS zip. Also keep track of what slot your on when your flashing
mac796 said:
Yea once you do it a couple of times you will have it down. Just remember from May bootloader's on, you have to use that VBS zip. Also keep track of what slot your on when your flashing
Click to expand...
Click to collapse
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
KingAroan said:
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
Click to expand...
Click to collapse
No there the same. You can put whatever on either one. There for normal use. seamless updates they call it I believe.
KingAroan said:
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
Click to expand...
Click to collapse
The different slots are for seamless updates. If you're using the stock rom and taking OTA's, the OTA gets flashed to whatever slot is currently inactive. It used to be when you did an OTA, the OTA got downloaded and then you'd be prompted to reboot to install the update. When you rebooted, the update would get installed but you had to sit and wait for it to install before you could use your phone again. With the two slots, it now downloads the update and installs it to the inactive slot while you continue to use your phone. Eventually you get prompted to reboot but instead of having to wait for it to install, it just reboots like any other time you reboot the phone and there is no wait for the update to install. It's already installed. When it reboots, it switches to the slot that was previously inactive because that's where the update is installed to. So, if you're on slot A when the update is downloaded and installed, you'll be using slot B after you reboot. The next month when the update comes out, it will get installed to the other slot again and you'll once again be using slot A and so on and so on for every month after that.
For a custom rom, they can be installed on either slot. It just depends on which slot is currently active. If slot A is the slot that's currently active, TWRP will flash the rom to slot B. If B is active, the rom will get flashed to A. Anything else gets flashed to the slot that is currently active (SuperSU, Vendor files or what have you). That's why after flash the rom, you have to reboot the phone (either reboot to recovery or the OS) before flashing the rest of whatever it is you want to flash. If you don't reboot before flashing SuperSU or whatever, it won't get flashed to the same slot the rom got flashed to and obviously, this causes issues. Bottom line is, slot A or B, it has nothing to do with whether it's a stock or custom rom. Whichever slot is inactive when you flash a rom is the slot the rom will end up on.
robocuff said:
The different slots are for seamless updates. If you're using the stock rom and taking OTA's, the OTA gets flashed to whatever slot is currently inactive. It used to be when you did an OTA, the OTA got downloaded and then you'd be prompted to reboot to install the update. When you rebooted, the update would get installed but you had to sit and wait for it to install before you could use your phone again. With the two slots, it now downloads the update and installs it to the inactive slot while you continue to use your phone. Eventually you get prompted to reboot but instead of having to wait for it to install, it just reboots like any other time you reboot the phone and there is no wait for the update to install. It's already installed. When it reboots, it switches to the slot that was previously inactive because that's where the update is installed to. So, if you're on slot A when the update is downloaded and installed, you'll be using slot B after you reboot. The next month when the update comes out, it will get installed to the other slot again and you'll once again be using slot A and so on and so on for every month after that.
For a custom rom, they can be installed on either slot. It just depends on which slot is currently active. If slot A is the slot that's currently active, TWRP will flash the rom to slot B. If B is active, the rom will get flashed to A. Anything else gets flashed to the slot that is currently active (SuperSU, Vendor files or what have you). That's why after flash the rom, you have to reboot the phone (either reboot to recovery or the OS) before flashing the rest of whatever it is you want to flash. If you don't reboot before flashing SuperSU or whatever, it won't get flashed to the same slot the rom got flashed to and obviously, this causes issues. Bottom line is, slot A or B, it has nothing to do with whether it's a stock or custom rom. Whichever slot is inactive when you flash a rom is the slot the rom will end up on.
Click to expand...
Click to collapse
Holy ****, i didnt know that part, i just thought it flashed it to your current slot and when you rebooted into system, the slot didnt change.....brb but first a quick titanium backup
How would i install Android p/9/pie on my pixel since the bootloader is unlocked and rooted? Is there a guide i can follow? Would i use the factory image or the OTA file? Any help would be appreciated. Thank you in advance.
subvapor said:
How would i install Android p/9/pie on my pixel since the bootloader is unlocked and rooted? Is there a guide i can follow? Would i use the factory image or the OTA file? Any help would be appreciated. Thank you in advance.
Click to expand...
Click to collapse
Flash like every other factory image and all should be good.
phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
Is it do able without a computer my laptop quit on me? If its not I'll have to wait till I'm around my moms house to do it. Ive only ever flash custom roms before so im not sure if it can be done with TWRP. Thanks for the help.
You need to use the fastboot tools, so you need your PC.
phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
phaino00 said:
You need to use the fastboot tools, so you need your PC.
Click to expand...
Click to collapse
Okay thanks for the help.
Whats the difference between the files?
9.0.0 (PPR1.180610.009, Aug 2018)
9.0.0 (PPR1.180610.010, Aug 2018, Telus)
The Telus one is for people who have Telus for cell service. If you don't have Telus use the 009 if you have telus use 010. Google tends to do this from time to time.
phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
Does this apply if you have custom recovery (TWRP) and modified boot.img (Magisk)?
I fastboot flashed the 9.0 files on top of the July 8.1 version without a data wipe. I had to reinstall TWRP and Magisk using the same install procedure I used on 8.1. Even though root was successfully working on Magisk 16 I had to install beta version 16.7 for the SafetyNet check to work properly.
Sent from my SHT-AL09 using Tapatalk
Butch1326 said:
I fastboot flashed the 9.0 files on top of the July 8.1 version without a data wipe. I had to reinstall TWRP and Magisk using the same install procedure I used on 8.1. Even though root was successfully working on Magisk 16 I had to install beta version 16.7 for the SafetyNet check to work properly.
Click to expand...
Click to collapse
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.
SkinnyT said:
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.
Click to expand...
Click to collapse
Not the exact same problem as yours, but I found that I wasn't able to boot into the OS after flashing Magisk 16.7. It would get to the animated "G" loading screen, but then reboot automatically and go into TWRP. Currently reflashing the stock (without wipe) and trying again.
Try installing the Magisk Uninstaller, then rebooting into system. If that doesn't work, you can use fastboot to install the boot.img file taken from the full factory image. If you already have it ready to go, it's faster than a full reinstall of the OS.
SkinnyT said:
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.
Click to expand...
Click to collapse
For me it did not take long for the Pixel to start after boot. Maybe a minute or two. It did take 5-10 minutes to run the Pie update.
Maybe it was because I originally installed Magisk 16 before going to version 16.7.
I agree with post-mortem's suggestion. It will be easier for you to reinstall Magisk before reinstalling the OS.
I've been starting out by flashing the factory image with adb. Then once it boots I can fastboot the twrp.img and get twrp into the recovery slot with no issues. I didn't get a chance today, but tomorrow I'll try with Magisk again.
post-mortem said:
Try installing the Magisk Uninstaller, then rebooting into system. If that doesn't work, you can use fastboot to install the boot.img file taken from the full factory image. If you already have it ready to go, it's faster than a full reinstall of the OS.
Click to expand...
Click to collapse
I did end up doing that, though I don't know if this itself solved my problem. I'll explain more below
daver68 said:
Not the exact same problem as yours, but I found that I wasn't able to boot into the OS after flashing Magisk 16.7. It would get to the animated "G" loading screen, but then reboot automatically and go into TWRP. Currently reflashing the stock (without wipe) and trying again.
Click to expand...
Click to collapse
I ended up fixing my problem. After posting this, I repeated my exact steps a few more times to make sure I wasn't doing something wrong.
1. boot into bootloader
2. fastboot factory image (without -w)
3. boot into stock Pie
4. fastboot boot twrp 3.2.2.0 image
5. install twrp 3.2.2.0 zip
6. reboot into recovery
7. flash Magisk 16.7
8. reboot into Pie
These steps didn't work, and I would always get into a bootloop that takes me straight to recovery
What I ended up doing that fixed my problem was the following
1. boot into bootloader
2. fastboot factory image (without -w)
3. boot into stock Pie
4. fastboot boot twrp 3.2.2.0 image
5. install twrp 3.2.2.0 zip
6. reboot into recovery
7. flash Magisk uninstaller
8. reboot recovery
9. flash Magisk 16.6
10. set boot partition to B
11. reboot into rooted Pie
Specifically, I used the Magisk Uninstaller, used an "older" version of Magisk (16.6, not the later 16.7), and I also changed my boot partition from A to B after flashing Magisk. This worked for me, and until I know specifically why, I'm going to just re-use this procedure on the next factory image update.
Hopefully this can help someone else having the same problem!
Hello guys!
The story began, when I accidently installed a stock OTS update by OP onto my already rooted OP6 with Magsik and TWRP, running a NoLimits ROM...
I just noticed, that the phone said "restart to finish OTS upgrade" or some kind of thing..... I always had the notification on my screen that an update would be available....what surely was ignored because running NoLimits ROM.... but because of some unknown reason, the stock update installed itself magically...
So I ended up finding my phone in complete stock condition, just the unlocked bootloader remained..... F*CK!
I tried to go back to root by trying to install TWRP via fastboot...and that was the beginnig of the end...
By fastboot boot twrp.img, the phone just remained in fastboot mode..... no twrp screen showed up... repeated this a few times, nothing changed....
Somewhere here I read to look up the current slot.... so I did fastboot getvar current-slot.... and after slot b was shown, I flashed twrp into slot b by fastboot flash boot_b twrp.img..... which had the phone stuck in screen "the bootloader is unlocked.....".... so i think that's what is called a BRICK...?
Please guys, help me out...as I don't know how to go on.... I also tried to flash stock boot img from here via fastboot, what didn't work either....
Would be glad for any suggestions...
Thanks!
Alex
dr.zikzak said:
Hello guys!
The story began, when I accidently installed a stock OTS update by OP onto my already rooted OP6 with Magsik and TWRP, running a NoLimits ROM...
I just noticed, that the phone said "restart to finish OTS upgrade" or some kind of thing..... I always had the notification on my screen that an update would be available....what surely was ignored because running NoLimits ROM.... but because of some unknown reason, the stock update installed itself magically...
So I ended up finding my phone in complete stock condition, just the unlocked bootloader remained..... F*CK!
I tried to go back to root by trying to install TWRP via fastboot...and that was the beginnig of the end...
By fastboot boot twrp.img, the phone just remained in fastboot mode..... no twrp screen showed up... repeated this a few times, nothing changed....
Somewhere here I read to look up the current slot.... so I did fastboot getvar current-slot.... and after slot b was shown, I flashed twrp into slot b by fastboot flash boot_b twrp.img..... which had the phone stuck in screen "the bootloader is unlocked.....".... so i think that's what is called a BRICK...?
Please guys, help me out...as I don't know how to go on.... I also tried to flash stock boot img from here via fastboot, what didn't work either....
Would be glad for any suggestions...
Thanks!
Alex
Click to expand...
Click to collapse
i remember that NoLIMIT rom mustbe uninstall before update the oos.In your case i think it was bootloop,softbrick.You boot into fastboob mood and use fastboot rom. and you can root and instant TWRP again.
soihuvuontrang said:
i remember that NoLIMIT rom mustbe uninstall before update the oos.In your case i think it was bootloop,softbrick.You boot into fastboob mood and use fastboot rom. and you can root and instant TWRP again.
Click to expand...
Click to collapse
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex
dr.zikzak said:
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex
Click to expand...
Click to collapse
If you can access fastboot mode you can try follow procedure in next thread:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I could recover my system with this @mauronofrio tool a couple of times. In fact, i never have used MSM tool.
dr.zikzak said:
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex
Click to expand...
Click to collapse
boot in to fastboot mode and your fone is not brick,so msm tool isn't used .
you can download newest driver for oneplus on google.
and you can find on forum. hope you will be successful
Kurtinaitis said:
If you can access fastboot mode you can try follow procedure in next thread:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I could recover my system with this @mauronofrio tool a couple of times. In fact, i never have used MSM tool.
Click to expand...
Click to collapse
I'll have a try..,.thanks for that!
Regards,
Alex
The method of @mauronofrio worked!!! Thanks a lot!
But I still can't boot twrp on the phone....if I do so, the phone boots into fastboot mode again and freezes at "1+ logo" with "Fastboot Mode" below it..... same like before? The device is fully wiped now...
So how can I get TWRP working again...??
I also tried fastboot flash recovery twrp.img -> no such partition..... don't know why it worked the first time I did it, root and custom ROM without any issues...
Thanks,
Alex
dr.zikzak said:
The method of @mauronofrio worked!!! Thanks a lot!
But I still can't boot twrp on the phone....if I do so, the phone boots into fastboot mode again and freezes at "1+ logo" with "Fastboot Mode" below it..... same like before? The device is fully wiped now...
So how can I get TWRP working again...??
Thanks,
Alex
Click to expand...
Click to collapse
It seems a problem with TWRP version or Fastboot command.
Please, describe your method to flash TWRP and which version do you want to flash
Kurtinaitis said:
It seems a problem with TWRP version or Fastboot command.
Please, describe your method to flash TWRP and which version do you want to flash
Click to expand...
Click to collapse
I downloaded latest twrp-3-3-1.2 (I think) for my OP6, copied the belonging .zip file to my phone... started cmd as admin, typed fastboot devices....the device showed up, then fastboot boot twrp...........img.....enter, and afterwards the "1+" logo showed up, below it read Fastboot Mode...and nothing ever happened... till i switched the phone off again after 10 minutes...
Wrong version you think?
Thanks,
Alex
If you are on Android 10 try to download last version from Mauronofrio or last from Blu-Spark (V9.109). I use blu_spark with OOS 10.3.3
Sometimes the command for being able to boot in recovery from Fastboot is:
Fastboot flash boot "nameofTWRPimage".img
Flash a patched boot image of your rom via fastboot and than flash twrp installer through magisk manager. Done.
Kurtinaitis said:
If you are on Android 10 try to download last version from Mauronofrio or last from Blu-Spark (V9.109). I use blu_spark with OOS 10.3.3
Sometimes the command for being able to boot in recovery from Fastboot is:
Fastboot flash boot "nameofTWRPimage".img
Click to expand...
Click to collapse
Yes that worked for me last time I attempted root.
TWRP update - no boot into system
Hello guys....it's me again!
After getting everything working again because of the tremendous help of this forum, i tried to update my twrp recovery via twrp by installing the twrp zip-file...
Afterwards, i tried to upgrade my rom from NoLimits 11.2 to 11.5 - but the phone didn't boot afterwards....i've always ended up in the recovery menue....
I then changed slots (from b to a) in the recovery, and then, the phone booted again....but into the stock ROM...
I can't change slots again now and have stock rom in slot a as it seams.... how can i change that again? how can i flash the custom rom in the right slot again?
Thanks in advance!
Regards,
Alex
dr.zikzak said:
Hello guys....it's me again!
After getting everything working again because of the tremendous help of this forum, i tried to update my twrp recovery via twrp by installing the twrp zip-file...
Afterwards, i tried to upgrade my rom from NoLimits 11.2 to 11.5 - but the phone didn't boot afterwards....i've always ended up in the recovery menue....
I then changed slots (from b to a) in the recovery, and then, the phone booted again....but into the stock ROM...
I can't change slots again now and have stock rom in slot a as it seams.... how can i change that again? how can i flash the custom rom in the right slot again?
Thanks in advance!
Regards,
Alex
Click to expand...
Click to collapse
It's OK. That's the point of having 2 slots system. Be able to recover the other partition if something goes wrong.
So now... Do you have TWRP or stock recovery?
You can dirty flash stock on the inactive Slot.
I would install stock rom in inactive slot through Local Update un System updater, don't reboot, install TWRP retention script in Magisk Manager (of course only if you have a proper TWRP running, if not avoid this step), don't reboot, install magisk to inactive Slot (through Magisk Manager), reboot.
After that you Will have stock on both partitions. You can try again the XXX Update.
Kurtinaitis said:
It's OK. That's the point of having 2 slots system. Be able to recover the other partition if something goes wrong.
So now... Do you have TWRP or stock recovery?
You can dirty flash stock on the inactive Slot.
I would install stock rom in inactive slot through Local Update un System updater, don't reboot, install TWRP retention script in Magisk Manager (of course only if you have a proper TWRP running, if not avoid this step), don't reboot, install magisk to inactive Slot (through Magisk Manager), reboot.
After that you Will have stock on both partitions. You can try again the XXX Update.
Click to expand...
Click to collapse
Thanks for the fast answer!
I think TWRP is working, nur on slot B - the question is: how come that i Installed TWRP Update via TWRP Recovery, was able to reboot Ingo recovery, and after Flash of the ROM via TWRP, only TWRP Recovery was left... No bootable ROM, so i tried Slot A and that was Stock Rom...
How can i install stock ROM into Slot B if Slot A is currently 'running'?
Regards,
Alex
dr.zikzak said:
Thanks for the fast answer!
I think TWRP is working, nur on slot B - the question is: how come that i Installed TWRP Update via TWRP Recovery, was able to reboot Ingo recovery, and after Flash of the ROM via TWRP, only TWRP Recovery was left... No bootable ROM, so i tried Slot A and that was Stock Rom...
How can i install stock ROM into Slot B if Slot A is currently 'running'?
Regards,
Alex
Click to expand...
Click to collapse
Since Oxygen Os Updater > Local Upgrade.
Download 10.3.4 OOS and put in your internal Storage. Then follow procedure i wrote before
Kurtinaitis said:
Since Oxygen Os Updater > Local Upgrade.
Download 10.3.4 OOS and put in your internal Storage. Then follow procedure i wrote before
Click to expand...
Click to collapse
NOTE: don't reboot until you install Magisk to inactive Slot, and of course, as you're rooted must download Full Zip (not incremental)
Kurtinaitis said:
NOTE: don't reboot until you install Magisk to inactive Slot, and of course, as you're rooted must download Full Zip (not incremental)
Click to expand...
Click to collapse
I downloaded Oxygen Updater, also OOS 10.3.4, but in my system stettings, update button is greyed out.... with the nolimits ROM before, I once had issues that the OEM update got installed...so that led to my problem which made me open up this thread in the first place.... so i disabled system update via titanium backup when I had root access...
So now it's greyed out...but as it is the stock rom, it shouldn't be greyed out as titanium backup doesn't work at the moment, without root...
Should i flash via @mauronofrio's method and fully wipe the device?... would be a pain in the a.. as everything gets erased again, setting up from scratch 2 times within 3 weeks
Regards,
Alex
Would it be possible to install magisk without twrp, and then flash the NoLimits ROM via Magisk?
TWRP recovery must be there....only in slot B - i tried to change slot by fastboot --set-active=..... but it didn't work, unknown command
Regards,
Alex
dr.zikzak said:
I downloaded Oxygen Updater, also OOS 10.3.4, but in my system stettings, update button is greyed out.... with the nolimits ROM before, I once had issues that the OEM update got installed...so that led to my problem which made me open up this thread in the first place.... so i disabled system update via titanium backup when I had root access...
So now it's greyed out...but as it is the stock rom, it shouldn't be greyed out as titanium backup doesn't work at the moment, without root...
Should i flash via @mauronofrio's method and fully wipe the device?... would be a pain in the a.. as everything gets erased again, setting up from scratch 2 times within 3 weeks
Regards,
Alex
Click to expand...
Click to collapse
Did you try to install the Update since the app Oxygen Updater?
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
dr.zikzak said:
Would it be possible to install magisk without twrp, and then flash the NoLimits ROM via Magisk?
TWRP recovery must be there....only in slot B - i tried to change slot by fastboot --set-active=..... but it didn't work, unknown command
Regards,
Alex
Click to expand...
Click to collapse
I think there's some thread in Guides and News in which OP uploads some patched boot.img le something like that to have root but i never tried.
I just screwed up when attempting an update. I had the update downloaded but did not install it.
Then I continued to install the A/B retention script and Magisk to the inactive slot and rebooted.
Now my phone fails to boot, and gets stuck continuously loading.
Is there something I can do in TWRP to resolve this?
You can try to flash the Magisk uninstaller in TWRP and see if it fixes your issue. Maybe you lost root on one partition and some Magisk modules that are still installed are putting your phone into a bootloop.
I'm unable to mount any partitions to get the uninstaller zip on my device. I was able to sideload the zip however the Magisk Installer was also unable to mount partitions.
Edit: I changed the slot from B -> A in TWRP then rebooted and it resolved this!
Mgssidley said:
I'm unable to mount any partitions to get the uninstaller zip on my device. I was able to sideload the zip however the Magisk Installer was also unable to mount partitions.
Edit: I changed the slot from B -> A in TWRP then rebooted and it resolved this!
Click to expand...
Click to collapse
Was just about to suggest that, glad you resolved it but you still have a broken slot, you should be able to fix it by flashing the rom, flashing TWRP and magisk, change slot and repeat. You might need a usb drive attached as changing the slot will usually made the data partition not visible so you won't see your files if they're on the phone.
To be honest, I thought flashing the stock rom will flash it to both slots (it shows this during flash) so I'm not sure what you did that broke it.
djsubterrain said:
Was just about to suggest that, glad you resolved it but you still have a broken slot, you should be able to fix it by flashing the rom, flashing TWRP and magisk, change slot and repeat. You might need a usb drive attached as changing the slot will usually made the data partition not visible so you won't see your files if they're on the phone.
To be honest, I thought flashing the stock rom will flash it to both slots (it shows this during flash) so I'm not sure what you did that broke it.
Click to expand...
Click to collapse
I'm actually on stock and doing an OTA update. After it booted up I was able to install the update, A/B retention script, and Magisk (to inactive slot). It rebooted successfully after that, should I still be concerned about a broken slot?
Edit: On closer look, Magisk did not install properly and I'm unable to access internal storage from TWRP to reinstall it.
Mgssidley said:
I just screwed up when attempting an update. I had the update downloaded but did not install it.
Then I continued to install the A/B retention script and Magisk to the inactive slot and rebooted.
Now my phone fails to boot, and gets stuck continuously loading.
Is there something I can do in TWRP to resolve this?
Click to expand...
Click to collapse
You didn't install the ota but you installed magisk to inactive slot?
So I've got a US unlocked device running firmware version KB2005_15_200918. I've rooted it with magisk.
Few days ago I got an update notification, to update to 11.0.1.2.KB05AA. So, thinking I could do it like a pixel, I unrooted, installed the update and re rooted installing to the inactive slot (per @topjohnwu's instructions). On reboot I got stuck on the qualcomm kernel crash screen, leaving my slot_A install hosed.
After some tinkering, I was able to get up and running on slot B. However, slot A is hosed up with the update. (system update says failed, reboot to try again, when i do, hoses back up. Probably because it's setting the active slot to A again).
I've tried re-flashing the KB05AA stock boot image someone dd' and shared on here with no luck. And I don't want to use the unbrick tool, and ending up having to backup/restore all my data.
What are my options at this point to fix slot A, and take the update again? I'm coming from a pixel 3, and know nothing about flashing the factory images on this device or the best way to recover from this. Any advice would be appreciated.
-Michael_ said:
So I've got a US unlocked device running firmware version KB2005_15_200918. I've rooted it with magisk.
Few days ago I got an update notification, to update to 11.0.1.2.KB05AA. So, thinking I could do it like a pixel, I unrooted, installed the update and re rooted installing to the inactive slot (per @topjohnwu's instructions). On reboot I got stuck on the qualcomm kernel crash screen, leaving my slot_A install hosed.
After some tinkering, I was able to get up and running on slot B. However, slot A is hosed up with the update. (system update says failed, reboot to try again, when i do, hoses back up. Probably because it's setting the active slot to A again).
I've tried re-flashing the KB05AA stock boot image someone dd' and shared on here with no luck. And I don't want to use the unbrick tool, and ending up having to backup/restore all my data.
What are my options at this point to fix slot A, and take the update again? I'm coming from a pixel 3, and know nothing about flashing the factory images on this device or the best way to recover from this. Any advice would be appreciated.
Click to expand...
Click to collapse
Use msm tool or reflash stock via fastboot. Either way you gotta wipe one way or another.
Or maybe..
Try fastboot erase boot_a
Then fastboot flash boot_a boot.img. With the kernel you had on slot_a. Hopefully you backed it up prior to this. If not, see my first recommendation.
Thanks, I'll give my kernel backup a shot.