Something that helped me in a similar situation. Is putting your boot img and Rom in your platform tools folder. That way you just do fastboot flash --slot all boot boot.img and do not have to provide the path to the file for some reason when I had my files in any place besides in the platform tools it would cause an error and I'd end up bootloopingOkay, I got my pixel 4a back to stock by using android flash tool and flashing back to public at this website: https://developers.google.com/android/images
I think it worked that time because it performs a complete wipe first. Anyway, I still want to install this rom on my Pixel 4a. Any advice on what I may have done wrong the first time would be helpful. To be clear, I had made sure that my Pixel 4a was running Android 10 (QD4A.200805.003) and had unlocked the bootloader and made sure to allow USB Debugging in Developer Options. Then, after flashing the boot.img file in platform-tools_r30.0.5-windows (latest version) using your fastboot flash --slot all boot path/to/boot.img method, which did flash the image, I became stuck in a fastboot loop (Not Fastbootd), and was unable to get into recovery after power off (power and volume up), and was unable to boot up as phone stated no valid slot to boot, while it was stuck in fastboot. Please help me. How should I Reboot to Recovery, and then Factory Reset?
I don't think that's possible, especially on different android versions. Would be pretty cool though.So, here's a bit of a noob question... I'm new to the android 11 accessibility options and see something called a DSU list, and was wondering if there was a way to basically dual boot RR android 10, and stock android 11 using it??? I would love the ability to somehow be able to dual boot, if for no other reason, to test out this great rom... Used it back when android 6 was a thing, and would definitely use it again on a device if I had one that supported it that wasn't my main device, but since it is my main device, then something akin to dual booting even if a little slower, would be great, to try the ROM out until I can get hardware, like a 2-in-1 tablet or something that's compatible...
That's because you can't flash recovery. You need to temp boot twrp with the command fastboot boot boot.img. Then you can permanently install twrp by installing it as recovery ramdisk. Before you do that though, you need to flash a kernel that supports installing twrp via recovery ramdisk. The reason for that is because a kernel will compress it because there is not enough room to install twrp otherwise on this phone.I would like to try the Custom Roms like this one...but I'm not really able to flash the TWRP in my phone. It alway says:
FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: command failed
I tried flashing on android 10 but still same error with android 11
Thanks TheSayaMan for the answer...I'm still lost how to get a kernel that supports twrp via recovery ramdisk.That's because you can't flash recovery. You need to temp boot twrp with the command fastboot boot boot.img. Then you can permanently install twrp by installing it as recovery ramdisk. Before you do that though, you need to flash a kernel that supports installing twrp via recovery ramdisk. The reason for that is because a kernel will compress it because there is not enough room to install twrp otherwise on this phone.
Go here: https://forum.xda-developers.com/t/twrp-3-5-2-11-for-sunfish-testing.4179101/page-9
I can't get to the no Gapps build. Is there another way? (google can't be trusted).
[SIZE="4"]/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */[/SIZE]
If your using Dirty Unicorns why are you here? Mentioning another devs rom in another devs thread is considered disrespectful. These people put in a lot of time and effort to bring this to us and they don't have to. They have other full time jobs and can't focus on rom development full time. I appreciate what we have and I'm sure it will only get better. Patience is key.