always installing is done on inactive slotPhew! Just applied the newest update via OTA. Turns out my slot B was not on C62 so I had the touchscreen not working issue. To compound, switching back to slot A would not boot.
USE THIS INFORMATION AT YOUR OWN RISK. I DON'T KNOW WHAT I'M DOING.
I ended up using the LE2113 firmware flasher from this thread (even though I have LE2115). I modified the .bat file to comment out all the "slot=a" commands and changed all the "slot=all" commands to "slot=b". The reason I did this was twofold:
I then sideloaded the 20220819 crDroid build, reboot to recovery, sideload gapps, reboot to system.
- I wanted to preserve slot A in case there was a way to boot into it since it was the previously working slot
- Slot B booted but it had the touchscreen issue so in my mind only slot B needed to be fixed
Things that I noticed:
- After running the .bat file and rebooting to recovery I was on slot A. I had set this to the active slot before running the .bat file. This was the previously working slot and it was on build 20220813.
- After sideloading build 20220819 and rebooting to recovery, I was on slot B. It seems that sideloading crDroid installs it into the inactive slot and causes a slot change at the next reboot (I DO NOT KNOW FOR SURE IF THIS IS TRUE). If this is true it could be useful information for people having trouble with the install.
All seems to be working again. Hopefully doing things this way hasn't broken things in the background. Also hoping that the next update will work on slot A since it was previously working with the 20220813 build.
Thanks for the clarification. Should I flash the firmware onto slot A to make sure the next update works? Or should I be fine since slot A was running build 20220813 without issue previously?
U don't make a zip for it you use the copy partitions zip before flashing the rom
As far as I know, 2113 is global and 2115 is US unlocked so there could be some similarities between the two models. Even then, flashing different firmware on different models can lead to random bugs or problems so I try to stick to my devices firmware
*** Disclaimer I am not responsible for any damage you made to your device You have been warned
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash boot boot.img
adb sideload crDroid.zip
adb sideload crDroid.zip
fastboot flash --slot=all keymaster keymaster-op9.img