Flashing A/B partitions - Google Pixel Questions & Answers

Hello, after unsuccesfull flashing elementalx my device went to bootloop, so i did flash-all, but i noticed that i flashed B partition, so i changed to a and did flash-all again. Is it normal to flash both partition with same default Google image?

WhiteBirdER said:
Hello, after unsuccesfull flashing elementalx my device went to bootloop, so i did flash-all, but i noticed that i flashed B partition, so i changed to a and did flash-all again. Is it normal to flash both partition with same default Google image?
Click to expand...
Click to collapse
Its not really necessary, unless you're locking your boatloader. If you're relocking your bootloader then you should just to be sure.

Related

Stuck in Bootloop when installing Magisk

Helloguys and gals,
I just got a Pixel 3 and wanted to root it. I followed this guide: https://www.youtube.com/watch?v=BgV1xxkcBk8
I installed the latest TWRP recovery (didn't keep it read only, maybe this was a mistake?). After that I installed Magisk which was followed by a bootloop.
To fix the bootloop I used TWRPs fix bootloop fix which worked. But that makes Magisk undone.
So my Questions is how to install Magisk? Do I need to flash the stock image on both slots and start again? Is the guide outdated? If so, which guide should I follow?
Edit: My phone is still on the update from November 2018.
On A/B devices there is no dedicated recovery partition anymore, recovery is contained in the boot partition, so if you install Magisk it's advised not to install TWRP on those devices anymore to avoid both modifying the same image, but instead to always fastboot boot when you need to use TWRP.
These are the steps I follow every time I need to factory reset then root my own Pixel 3 :
Boot to bootloader
Flash stock image on current slot
Flash stock image on other slot
Boot the system, enable Developer options and USB debugging
Fastboot boot TWRP image
Backup Boot partition
Flash Magisk
[optional] Flash custom kernel (check flashing order depending on kernel)
Reboot
bafforosso said:
On A/B devices there is no dedicated recovery partition anymore, recovery is contained in the boot partition, so if you install Magisk it's advised not to install TWRP on those devices anymore to avoid both modifying the same image, but instead to always fastboot boot when you need to use TWRP.
These are the steps I follow every time I need to factory reset then root my own Pixel 3 :
Boot to bootloader
Flash stock image on current slot
Flash stock image on other slot
Boot the system, enable Developer options and USB debugging
Fastboot boot TWRP image
Backup Boot partition
Flash Magisk
[optional] Flash custom kernel (check flashing order depending on kernel)
Reboot
Click to expand...
Click to collapse
Allright, thank you for your explanation! I used the stock image and the flash-all.bat to install the stock image. Will it be enough since you are speaking of two different slots? if not, how can i do both slots?
thx in advance
I run twrp as the devices recovery and have magisk. I would follow the twrp and magisk guides for this device. First boot twrp then use the installer, second reboot, third get to recovery and flash magisk. The boot partition needs to be rebooted before root. It is an initialization thing. Get twrp, reboot, magisk.
Having a similar issue here. I was rooted till the latest OTA happened a few days ago. Trying to re-root in several different ways, but all result in boot loop.
Methods I've tried:
Extracted boot.img from factory image, patched with Magisk Manager, flashed with fastboot
Fastboot boot twrp-3.3.0-0-blueline.img, installed Magisk-v19.3.zip
Fastboot boot twrp-3.3.0-0-blueline.img, installed twrp-pixel3-installer-blueline-3.3.0-0.zip, rebooted recovery, installed Magisk-v19.3.zip
Any ideas?
levibuko said:
Allright, thank you for your explanation! I used the stock image and the flash-all.bat to install the stock image. Will it be enough since you are speaking of two different slots? if not, how can i do both slots?
thx in advance
Click to expand...
Click to collapse
I tinker a lot with my phone so I usually want to have both slots clean flashed when I start back from scratch, not sure that is really necessary, but here are the steps I use for flashing both slots :
Code:
fastboot getvar current-slot
./flash-all.sh
fastboot --set-active=x (x being a or b, the other slot than the one you get with the fastboot getvar command)
./flash-all.sh
Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.
---------- Post added at 08:00 PM ---------- Previous post was at 07:52 PM ----------
tenthousandfeet said:
Having a similar issue here. I was rooted till the latest OTA happened a few days ago. Trying to re-root in several different ways, but all result in boot loop.
Methods I've tried:
Extracted boot.img from factory image, patched with Magisk Manager, flashed with fastboot
Fastboot boot twrp-3.3.0-0-blueline.img, installed Magisk-v19.3.zip
Fastboot boot twrp-3.3.0-0-blueline.img, installed twrp-pixel3-installer-blueline-3.3.0-0.zip, rebooted recovery, installed Magisk-v19.3.zip
Any ideas?
Click to expand...
Click to collapse
Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.
Boot twrp and install it, then reboot to system, then reboot recovery and install magisk. You need to boot system before installing magisk.
wangdaning said:
Boot twrp and install it, then reboot to system, then reboot recovery and install magisk. You need to boot system before installing magisk.
Click to expand...
Click to collapse
Tried that. No success.
Only thing I can think is to install an older magisk then let it update. I originally installed 18 something and have just let it update. I do not use google's factory image though, so cannot really help troubleshoot.
wangdaning said:
Only thing I can think is to install an older magisk then let it update. I originally installed 18 something and have just let it update. I do not use google's factory image though, so cannot really help troubleshoot.
Click to expand...
Click to collapse
I had a similar thought, but no dice. Tried installing Magisk 19.2, which boot looped just like the latest 19.3.
I even went back to 16.7, and though that one didn't boot loop it also didn't show up in the system. Magisk Manager didn't recognize it, anyway.
Though I'm loathe to do a full wipe/reset and then reconfigure all my junk, I may be headed in that direction as I'm running out of other ideas. Perhaps I'll save a backup just before that I can return to if the reset is fruitless.
---------- Post added at 07:53 AM ---------- Previous post was at 07:36 AM ----------
Magisk 18.0 does the same as 16.7 - no bootloop, but no root.
Interestingly, I noticed that the 18.0 and 16.7 zip installers say something about the partition being boot_a, whereas the bootlooping 19.2 and 19.3 zip installers say it's boot_b.
Run the Magisk uninstaller. Flash boot.img to both slots. Do a flash-all (minus the -w). With those things done, you should be essentially at reset state for this problem.
sliding_billy said:
Run the Magisk uninstaller. Flash boot.img to both slots. Do a flash-all (minus the -w). With those things done, you should be essentially at reset state for this problem.
Click to expand...
Click to collapse
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
tenthousandfeet said:
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
Click to expand...
Click to collapse
That stinks. Have you tried changing slots in fastboot boot instance of TWRP and then installing Magisk? It sure sounds like your slots are out of sync somehow, and the easiest way to remedy that is to run flash-all with -w in place.
sliding_billy said:
That stinks. Have you tried changing slots in fastboot boot instance of TWRP and then installing Magisk? It sure sounds like your slots are out of sync somehow, and the easiest way to remedy that is to run flash-all with -w in place.
Click to expand...
Click to collapse
I'm not sure if it's related to slots or not, actually. I was thinking that it was, but I've now done a flash-all on both slots (one after the other), then tried my TWRP flash of the Magisk installer again. Results? Bootloop.
I've also tried flashing Magisk Manager's patched_boot.img to both boot_a and boot_b, with the now-familiar outcome.
tenthousandfeet said:
I'm not sure if it's related to slots or not, actually. I was thinking that it was, but I've now done a flash-all on both slots (one after the other), then tried my TWRP flash of the Magisk installer again. Results? Bootloop.
I've also tried flashing Magisk Manager's patched_boot.img to both boot_a and boot_b, with the now-familiar outcome.
Click to expand...
Click to collapse
I hear you about flash-all on both slots, but if you left yourself on the same active slot there could still potentially be an issue. I'll need to think about this some more when I wake. I'd hate to see you do a full reset and end up with the same issue if it is something in the procedural that is causing it. One other thing that shouldn't be a concern, but are you using the proper/current TWRP for the P3 (twrp-3.3.0-0-blueline)? And yet one more thing... try rooting with a patched boot instead of running the installer in TWRP. I can't do the instructions by memory, but they are on here. Check the P3 XL page if they are not readily available on the P3 page.
tenthousandfeet said:
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
Click to expand...
Click to collapse
Please update when/if you find a solution. We are both in the same boat.
I'll let you know if I get anything working.
sliding_billy said:
I hear you about flash-all on both slots, but if you left yourself on the same active slot there could still potentially be an issue. I'll need to think about this some more when I wake. I'd hate to see you do a full reset and end up with the same issue if it is something in the procedural that is causing it. One other thing that shouldn't be a concern, but are you using the proper/current TWRP for the P3 (twrp-3.3.0-0-blueline)? And yet one more thing... try rooting with a patched boot instead of running the installer in TWRP. I can't do the instructions by memory, but they are on here. Check the P3 XL page if they are not readily available on the P3 page.
Click to expand...
Click to collapse
Here's what I did to get both slots:
Code:
fastboot --set-active=_a
flash-all
fastboot reboot-bootloader
fastboot --set-active=_b
flash-all
fastboot reboot
adb reboot bootloader
fastboot boot twrp-3.3.0-0-blueline.img
Note the TWRP image is the latest - 3.3.0.
I've also tried flashing the Magisk-patched boot, using the following:
Code:
fastboot flash boot patched_boot.img
...and...
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Everything reports success while flashing, but won't boot.
One more thing I could try is an updated ADB/Fastboot. Mine is probably a little dated, though I wouldn't expect that would have any ramifications for flashing with TWRP.
tenthousandfeet said:
Here's what I did to get both slots:
Code:
fastboot --set-active=_a
flash-all
fastboot reboot-bootloader
fastboot --set-active=_b
flash-all
fastboot reboot
adb reboot bootloader
fastboot boot twrp-3.3.0-0-blueline.img
Note the TWRP image is the latest - 3.3.0.
I've also tried flashing the Magisk-patched boot, using the following:
Code:
fastboot flash boot patched_boot.img
...and...
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Everything reports success while flashing, but won't boot.
One more thing I could try is an updated ADB/Fastboot. Mine is probably a little dated, though I wouldn't expect that would have any ramifications for flashing with TWRP.
Click to expand...
Click to collapse
It still looks like your boot slot ended up the one you had tried already (b), since you changes to a and ran flash-all, changed back to b and ran flash-all and rebooted. As for the old platform tools, that could definnitly have an impact on running the fastboot of the patched boot. Other than that, I think a flash-all with the -w is the only approach left.
I'm also in the same boat. I've tried all the various install methods, and done the double "flash-all" on both slots, and no matter what, it ends in a bootloop.
Haven't tried the -w yet so I'll be interested if anyone gives that a go. Until then I'm dying with no root

Need stock or patched boot img 10.3.2

I was hoping someone could share the newest patched boot image if not that the stock one. For the international version. I updated to the newest firmware and I forgot to switch slots flash TWRP and magic on the other slot. So I'm hoping I can flash a patch boot image and get back without wiping everything. Thanks
mac796 said:
I was hoping someone could share the newest patched boot image if not that the stock one. For the international version. I updated to the newest firmware and I forgot to switch slots flash TWRP and magic on the other slot. So I'm hoping I can flash a patch boot image and get back without wiping everything. Thanks
Click to expand...
Click to collapse
Is booting to bootloader then fastboot boot twrp. Img that hard to do?
MrSteelX said:
Is booting to bootloader then fastboot boot twrp. Img that hard to do?
Click to expand...
Click to collapse
I think he's trying to revert to stock and forgot to grab the stock image.
Otherwise, yeah, just "fastboot boot the_twrp.img" and move on.
tech_head said:
I think he's trying to revert to stock and forgot to grab the stock image.
Otherwise, yeah, just "fastboot boot the_twrp.img" and move on.
Click to expand...
Click to collapse
I was updating to newest firmware. I forgot to change slots and flash magisk. I run decrypted, but this encrypted me again, I could still boot TWRP but it was encrypted, I was thinking if I had the patched boot IMG I could have brought myself back. I ended up just formatting in TWRP and starting over.
Can someone pls provide OnePlus 7pro 10.3.3 model GM1911
stock boot.img

How do I flash GSI's

I been trying to flash some system images I find on the treble forum and nothing is flashing.
My bootloader is unlocked and I'm rooted with magisk
Whenever I run "fastboot erase system" I get a permission denied error and doing "fastboot format system" I get an error about a raw filesystem
Trying to flash an image without wiping I get an error about resizing the system partition.
Am I doing something wrong? It's been years since I've tinkered with Android so I'm out of the loop on Android's dynamic partitioning etc etc
Edit: Figured it out
https://forum.xda-developers.com/mo...de-how-to-flash-generic-image-moto-g-t4131199
for anyone wondering, i just figured it out, the moto g stylus has 2 fastboot modes? one is the bootloader (adb reboot bootloader) and the other is fastbootd (adb reboot fastboot)
booting into fastbootd solved my flashing and wiping issues
Yes. The Android 10 has a new fastbootd mode.
You can enter it with a command
Code:
adb reboot fastboot
You can try to install the Treble image through it. Because in Android 10 there is a new physical partition super.img, which contains three logical partitions - vendor.img, system.img and product.img.
ilia3367 said:
Yes. The Android 10 has a new fastbootd mode.
You can enter it with a command
You can try to install the Treble image through it. Because in Android 10 there is a new physical partition super.img, which contains three logical partitions - vendor.img, system.img and product.img.
Click to expand...
Click to collapse
Yeah I just figured this out although I'm still having issues flashing any gsi ROM, nothing boots after a factory reset, even if I just flash a boot.img patched by magisk with dm verity and encryption disabled
DMedina559 said:
Yeah I just figured this out although I'm still having issues flashing any gsi ROM, nothing boots after a factory reset, even if I just flash a boot.img patched by magisk with dm verity and encryption disabled
Click to expand...
Click to collapse
Same boat. Bootloop if I try to get it to start unencrypted. Booting at least once into a clean boot, then flashing without formatting first let me patch magisk. Have a suspicion the phone isn't too happy about being unecrypted.

bootloop

i have a few questions, and it's stumping me bad. i got a pixel sailfish on ebay and its in a bootloop. i have tried flashing factory images, ota's, fastbooting twrp and factory resetting and still...loop. sometimes in twrp it will flash the rom, but will freeze and random reboot. i have tried formatting system, vendor and then flashing factory images and to no avail...bootloop. one time i was able to flash nougat factory, and it actually booted. i went ahead and fastbooted twrp...then bam...bootloop again. i need some help. even when i boot into each slot, there is different baseband versions and bootlooder version on each slot. is this normal? should not both slots have same bootloader and baseband version? could this be my bootloop issue?
to reiterate, when i was able to boot the nougat factory, i had fastboot -w, format system and vendor then flashed the nougat fw and it stuck. now i have nothing. can anyone help?
Here are some pics of bl screens. this is result after formatting userdata and flashing latest stock firmware. android 10.
also noted that sometimes when trying to format system, it says no dtbo img. i notice on fw flash that it says no dtbo.img on the flash.
now when i flash nougat, i get "ramdump writing to ext4 file"
it didnt do this when the same nougat fw was successful
Rootmaster906 said:
now when i flash nougat, i get "ramdump writing to ext4 file"
it didnt do this when the same nougat fw was successful
Click to expand...
Click to collapse
You flashed your firmware to both slots and still show different bootloader on each?
Rootmaster906 said:
Here are some pics of bl screens. this is result after formatting userdata and flashing latest stock firmware. android 10.
also noted that sometimes when trying to format system, it says no dtbo img. i notice on fw flash that it says no dtbo.img on the flash.
Click to expand...
Click to collapse
Sailfish doesn't have a dtbo.img. Just system, system_other, boot, and vendor so don't worry about that.

Nexus 5 deleted data partition

Hi there,
So I wanted to resize the system partition so I could install GApps. I accidentally deleted the data partition somehow (deleted not corrupted). I can go into bootloader and recovery, my bootloader is unlocked so I can flash any recovery I need to but I can't boot Android. Any ways to redo the partition table or manually add the userdata partition?
Thanks in advance.
Edit: I was able to fix the partition by creating a partition called "userdata" with parted, but now my phone is constantly rebooting and it cant be the power button because when powered off or in bootloader, it doesnt automatically turn on. Any help?
KevinKraze said:
Hi there,
So I wanted to resize the system partition so I could install GApps. I accidentally deleted the data partition somehow (deleted not corrupted). I can go into bootloader and recovery, my bootloader is unlocked so I can flash any recovery I need to but I can't boot Android. Any ways to redo the partition table or manually add the userdata partition?
Thanks in advance.
Click to expand...
Click to collapse
I would start fresh and flash the last factory image using fastboot
Then follow this guide for repartitioning... https://forum.xda-developers.com/t/recovery-unofficial-twrp-hh-for-nexus-5-hammerhead.4047653/
Lughnasadh said:
I would start fresh and flash the last factory image using fastboot
Then follow this guide for repartitioning... https://forum.xda-developers.com/t/recovery-unofficial-twrp-hh-for-nexus-5-hammerhead.4047653/
Click to expand...
Click to collapse
I have tried to flash the factory image, but as I said, the data partition is deleted so nothing works
I got it to work by manually creating a partition with parted and called it "userdata" After I just flashed the userdata.img file and everything seemed to work!

Categories

Resources