Why is there the instructions to enable USB debugging and approve the connection when upgrading from Android 11?
1 Like
Probably so that if thereâs a problem, you can actually gather and pass along logs so that if itâs a fixable issue rather than something intrinsic in the data, they can actually try to patch it out for future builds?
1 Like
What about canada? Most i can get is android 11 from updater.
1 Like
Youâll need to manually download and install the update as it is not available OTA for Android 11 and earlier due to a possible data migration bug causing a reset:
1 Like
I ran into the same corruption issue:
âCanât load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.â
I followed all the steps with enabling usb debugging and adb devices prior to the upgrade process, and confirmed that my computer connected sucessfully to my phone via adb.
Unfortunately, once my phone was at that âCanât load Android systemâ screen, it was no longer connected, and following the instructions in the OP to choose âTry Againâ and do adb logcat > logs.txt doesnât do anything. adb just sits there saying - waiting for device - with no further output. Note that I first did those two steps in the order listed (first selecting âTry Againâ, and then starting adb logcat > logs.txt), and when that did nothing I tried the other way around, leaving the - waiting for device - message sitting and waiting while I selected âTry Againâ on my phone. In both cases, the phone just ends up back at the corruption screen and never connects to adb (and thus no logs are output).
More on this SN:2020 upgrade bug
We are not able to reproduce it in our testing. We did ask users to help us by providing logs, but we have yet to receive any.
My above experience makes me think that the reason you arenât receiving any logs from people is because the instructions provided arenât working to get the logs. Are the listed steps perhaps incomplete?
Were you able to see the bootanimation after âTry againâ?