I have a Pixel 2XL. It is rooted w/ Magisk and running RR Oreo ROM.
My Slot A does not work. I have tried to to install a ROM from TWRP and boot, but it goes into a boot loop. Slot B works fine. In TWRP, there is a re-partition or fix partitions button. Will that fix the problem? I've been rooting my phones for years, but I really only understand the basics. Is re-partitioning for Slot A/B, of for recovery/boot/vendor etc partitions?
Any other way to fix Slot A? Is there any problem other than OTA updates with not having 2 slots?
Any help would be greatly appreciated! I would really like it work.
TWRP won't fix this, and using the fix partitions option may do more harm than good. Flash a stock ROM (NOT an OTA image) using Fastboot and it should fix your A/B slot issue. From there you can go about setting up your device to use your chosen custom ROM.
Related
Hello guys,
I tried some stuff from the twrp thread and now I am curious how I can reflash the stock recovery?
Another question is the a/b slot system. I am currently on slot b with flashed stock image and root. If I use the OTA feature now, will the system set up on the slot a and after the next boot I am on slot a?
Best regards,
smoo62
Hello guys.
I'm having trouble here with a friend's device.
the device simply reboots the twrp.
I already realized the flash of several rons, I also tried with the stock.
installs everything correctly, but at the time of doing the reenicialization in the system returns to twrp again.
I have already tested several versions of twrp and also did not succeed.
Has anyone ever had this problem? I'm finding it very strange, because I've been with rom for a long time and I've never had any problems like this.
What do you think it could be? and how can I resolve and re-restart correctly again?
Thank you in advance.
You flashed the stock ROM and you still have TWRP? Then something is wrong. Usually when that happens you did something wrong. So this is a good thing you are stuck in TWRP. Usually a factory reset will make it boot again. You can pull data off from TWRP before doing this (like pictures and such).
What exactly have you tried to flash (order too), and what version of TWRP are you using. The factory ROM may not have worked as well if you tried to flash the latest, without having the treble partition setup, or did not have a version of TWRP that keeps the vendor partition mounted.
We really need a few more details on what you tried to help.
If you just want to get it booting, I would try wiping everything in BluSpark's TWRP, and flash 5.1.5 OOS.
My device forum doesn't have instructions how to do it, i've posted asking there but better to ask here also. I found this post for the Mi A2 that isn't my device mines the Mi A3 https://forum.xda-developers.com/mi-a2/how-to/guide-discussion-aio-gsi-thread-mi-a2-t3933356
The device is A/B arm64 has slots a and b i dunno how that effects flashing here, flashing custom roms will install into the inactive slot then you gotta change your active slot to be the the slot it installed into, then install rest of files there, does this apply with gsi .img files also?
When i tried using flashing the .img file i used orangefox recovery wiped all partitions flashed to system, just says no os installed i will probably try doing that again and flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip however who noes if that will help.
If someone can list the correct steps to flash using both fastboot method and twrp/orangefox recovery methods i would appreciate it. If it matters i was trying to flash android 10 gsi. I've seen many different methods listed depending on the device, so i guess that makes it harder to work out.
Thanks.
I've flashed it twice via TWRP with flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip. Plus TWRP.
1st time it was into A slot. After 1st flashing I've restarted TWRP and booted into B slot. And then flashed slot B.
After rebooting and seeing Logo in 15 minutes - I've got Android.10
xVM said:
I've flashed it twice via TWRP with flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip. Plus TWRP.
1st time it was into A slot. After 1st flashing I've restarted TWRP and booted into B slot. And then flashed slot B.
After rebooting and seeing Logo in 15 minutes - I've got Android.10
Click to expand...
Click to collapse
Thanks for the feedback, are you able to tell me the exact steps? like lets just say twrp is already installed and you factory reset, cleared all data.
Do you flash DM-Verity before you flash the rom? or after you flash the rom and what you just flash Forceencrypt Disabler and permissiver_v2.zip after installing the rom?
What i see with regular roms not gsi when you flash the rom if your on slot a it's actually installing it into slot b when you reboot that's where it is so you need to restart before flashing Magisk and other stuff. So i assume with the gsi maybe you need to reboot after installing as system image before flashing the other files?
Alister. said:
Thanks for the feedback, are you able to tell me the exact steps? like lets just say twrp is already installed and you factory reset, cleared all data.
Do you flash DM-Verity before you flash the rom? or after you flash the rom and what you just flash Forceencrypt Disabler and permissiver_v2.zip after installing the rom?
What i see with regular roms not gsi when you flash the rom if your on slot a it's actually installing it into slot b when you reboot that's where it is so you need to restart before flashing Magisk and other stuff. So i assume with the gsi maybe you need to reboot after installing as system image before flashing the other files?
Click to expand...
Click to collapse
Your better of using fastboot if flashing a gsi .img you dont need twrp really unless the rom is in a .zip format, or your wanting to add extras like magisk and such, or take a backup
Android 11
Did anyone tried Android 11 gsi??
I hope that someone here can help me rescue to rescue my data.
I was on the AOSiP build from september and than decided to encrypt my device. That worked perfectly. Now I wanted to install the latest update. The internal updater didn't work (just booted into TWRP recovery without further action, so I moved the update file to microsd and than updated manually by flashing the zip file via TWRP). Prior to the whole action, I updated TWRP through the app to the latest version.
Now my phone doesn't boot anymore, it is stuck in the AOSiP boot animation. Reverting to a previous TWRP version (3.2.3.2) didn't help, also flashing the september build again didn't help.
In TWRP I was unable to decrypt data, because TWRP keeps asking me for a password (but I don't remember putting a password in the first place). Therefor I switched from TWRP to OrangeFox recovery. Here decryption worked, put still after flashing the phone doesn't boot.
Anyone that has further ideas how to fix this without loosing all my data? Any help appreciated!
Have you tried installing another kernel?
kotobodj said:
Have you tried installing another kernel?
Click to expand...
Click to collapse
No, but as my system was running before without problems I don't expect the kernel to be the problem .. Or why would that make sense?
SOLVED: I noticed that flashing the update manually didn't automatically flash Gapps right afterwards. So flashing the Gapps helped and the phone now boots normally!
Hey you!
So I am back using my Pixel 2 XL and I want to root it, but I am having a lot of trouble doing so... Things I have tried:
First time I just tried installing the zip from magisk, after that my phone was stuck in an endless boot loop, nothing to do there...
I have done as this guide says:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
So this is where I am right now:
Flashed the newest factory image "10.0.0 (QQ3A.200605.001, Jun 2020)" by running the "flash-all.bat", booted it up and everything was working.
Downloaded the newest twrp "twrp-3.3.0-0-taimen.img" and loaded it using fastboot.
Installed "twrp-pixel2-installer-taimen-3.3.0-0.zip" and rebooted into recovery.
Wiped userdata, installed AOSiP 10, rebooted into recovery and installed opengapps.
Booted up the rom and checked that everything was working.
Installed Magisk manager and copied over the boot.img file from the factory zip and did the "patch img" thing.
Rebooted into fastboot and did "fastboot flash boot patched_boot.img"
Now I can boot up the rom but... My touchscreen isnt working? power and volume buttons works just fine, twrp has the same problem after I install it with the zip (it works fine when booting it up from fastboot)
I tried installing the stock boot.img but that didnt change anything.
Another thing is that on slot B is the stock rom and on slot A is the AOSiP rom, is this normal? I don't know how the slot thingy works is it just like partitions?? The stock rom on slot B is working just fine.
-Hapse
Update:
I ran the "flash-all.bat" on both slots and booted up twrp using fastboot and installed the magisk zip (not the img) before installing the manager, I then installed the manager once I booted up the rom. So I guess it's stock with root for now...
hapse said:
Hey you!
So I am back using my Pixel 2 XL and I want to root it, but I am having a lot of trouble doing so... Things I have tried:
First time I just tried installing the zip from magisk, after that my phone was stuck in an endless boot loop, nothing to do there...
I have done as this guide says:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
So this is where I am right now:
Flashed the newest factory image "10.0.0 (QQ3A.200605.001, Jun 2020)" by running the "flash-all.bat", booted it up and everything was working.
Downloaded the newest twrp "twrp-3.3.0-0-taimen.img" and loaded it using fastboot.
Installed "twrp-pixel2-installer-taimen-3.3.0-0.zip" and rebooted into recovery.
Wiped userdata, installed AOSiP 10, rebooted into recovery and installed opengapps.
Booted up the rom and checked that everything was working.
Installed Magisk manager and copied over the boot.img file from the factory zip and did the "patch img" thing.
Rebooted into fastboot and did "fastboot flash boot patched_boot.img"
Now I can boot up the rom but... My touchscreen isnt working? power and volume buttons works just fine, twrp has the same problem after I install it with the zip (it works fine when booting it up from fastboot)
I tried installing the stock boot.img but that didnt change anything.
Another thing is that on slot B is the stock rom and on slot A is the AOSiP rom, is this normal? I don't know how the slot thingy works is it just like partitions?? The stock rom on slot B is working just fine.
-Hapse
Click to expand...
Click to collapse
When you are on stock and you flash a custom rom, the custom rom will be flashed to the opposite slot of the stock rom. So yes, it is normal to have stock rom on 1 slot and the custom rom on the other.
Lughnasadh said:
When you are on stock and you flash a custom rom, the custom rom will be flashed to the opposite slot of the stock rom. So yes, it is normal to have stock rom on 1 slot and the custom rom on the other.
Click to expand...
Click to collapse
Ah I see, thank you