Hi there, I understand your situation and I'm kind of in the same boat. Though I've figured out to fix the wifi and system ui crashing. I guess need some help from you though because we also have that stupid govt tax system. I'll send you a Private message and we can try to figure it out. Text me asap. ThanksFirst "oh no did I brick my device?" post of the year!
I was on Android 11 with an unlocked bootloader, magisk root on the stock rom, and tried doing a clean install, without the "Magisk Restore Images" step, because Magisk hadn't backed them up, and found myself with a device that doesn't have WIFI or mobile. Luckily, I had a backup of my persist.img, but my phone doesn't appear to like that persist.img anymore.
Note: I had modified my modemst1 because my device is from US and the Turkish government wanted me to pay ~$300 to not block it, so I changed my IMEI for the Turkish line to the IMEI of an old phone that belonged to a relative, and kept my US line with the original IMEI.
Here is what I tried:
- Right when Android 12 booted for the first time, mobile was gone, but WIFI was just flaky. It listed the networks and even started downloading my backup. That was followed by a boot loop, which may have been because of a button issue. I followed the instructions for flashing boot.img with --slot all. Again, WIFI was only flaky but after a few reboots it was gone entirely.
- Reflashed the stock 12 several times, didn't help.
- Reflashed the stock 11 version I was on, didn't help.
- fastboot erase/flash persist consistently fails with "Not allowed to flash" and "Not allowed to persist" even when I have root. This is very strange.
- dd if=<persist.img path> of=/dev/block/sda2 - seems to work but doesn't fix anything. Attempting to turn on the WIFI makes the UI unresponsive.
- Installed TWERP hoping it would provide a way to flash the persist.img but didn't really help. But it showed the persist partition size to be 0 bytes, which was a very interesting finding, confirming the persist partition corruption.
- Am I not flashing my persist.img correctly? If so, why not? I had backed it up with dd.
- I am guessing I might have to start looking for a Pixel 4XL persist.img, but where do I look for that? I am guessing all Pixel 4XLs have the same but the stock image downloads don't come with the persist.img for some reason.
- Is there anything else I should do?
The option to install via inactive slot was re-introduced into Magisk with version 24.0. You should have that option again on the latest Canary, Beta and Stable versions.
In addition to what others have said....It sounds like you are rooting this phone for the 1st time? But in case you are not, make sure that any Magisk modules you may have installed that need updating are disabled.Hi guys, my phone is bootlooping when I am trying to root through the latest Magisk Canary app, (tried the stable magisk version and it didn't work either). If I flash the stock boot image, the phone loops into the system just fine.
I am using the latest platform tools(33.0.1) and my active boot slot is 'b'. I am on (SP2A.220405.004, Apr 2022) build.
Could someone post a video or detailed instructions on rooting through OTA? I have no clue how to do it?
If there is any other method also, I'd be willing to try. Please help me!
you need to unzip it, OP has instructions on what to do with it.
That did download. It seems like stable is working though. Like you said I'm rooted. Should I unhide Magisk before updating in the future? I appreciate your help, and the guide. Even GPay is working. It's always a struggle but I guess that's what makes it fun. At least a challenge.
I think it is sensible to unhide Magisk before updating it in the future.That did download. It seems like stable is working though. Like you said I'm rooted. Should I unhide Magisk before updating in the future? I appreciate your help, and the guide. Even GPay is working. It's always a struggle but I guess that's what makes it fun. At least a challenge.
fastboot devicesto verify communication with phone. It should return your phone's serial number.
fastboot flashing unlockand press enter.
fastboot rebootat the Command Prompt and press enter.
fastboot flashing lock
flash-allat the Command Prompt and press enter.
flash-allat the Command Prompt and press enter.
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash boot --slot all boot.img
fastboot flash boot "name of patched boot".imgwithout the quote marks at the Prompt and press enter.
fastboot rebootat the Prompt and press enter.
fastboot flash boot boot.img --slot all
Yes, it's fine. I've been using Stable version 23.0 since the first beta was released and am currently using it on yesterdays official release of Android 12 stable. Everything is fine for me.