I have found a pretty old device Huawei Ascend Y210. This mobile officially has Android 2.3.3 (API level 10). I found an online custom lollipop ROM for the specific mobile. The device has CWM as custom recovery. The zip file (the rom file) was installed successfully. The environment feels like android Lollipop should look like. Going to the mobile's settings > About phone > Android version, the version is 5.0.1 as expected. Using the command
adb shell getprop ro.build.version.release the result is 5.0.1 indeed. However, I tried running
adb shell getprop ro.build.version.sdk the result is 10 which is the API level of the stock android of the phone (Android 2.3.3). Apps made from API level 23 will fail to install as the API level is getting recognized as 10. Changing the apps' Minimum API level to 10 using APK Editor Studio, allows the app to get installed but it crashes once I try to open it.
Is that a bug? I mean can I somewhere change the API level of the device? Or is the ROM a scam and the android is never really getting updated to 5.0.1 and the ROM just changes the graphic interface? How is it even possible to trick the adb that the android version is 5.0.1 but keep the API level to 10?
P.S.: If someone has any ROM for Huawei Ascend Y210 with android 5.0.1 or higher handy, I would appreciate a download link.
Thanks in advance!
adb backupwas introduced with ICS (Android 4.0). If it's indeed only "surface polishing" of a Gingerbread OS,
adb backupwon't work. If it does work, it's a clear indicator of at least Android 4.0 (or higher) being present, and the ROM dev maybe just forgot to update
adb backupthe result was
adb backup -apk -shared -all -f mybackup.ab
WARNING: adb backup is deprecated and may be removed in a future release
adb: unable to connect for backup: closedThe device is getting recognized when I use
adbexecutable on your computer (unfortunately, it looks like
adb backupshall be dropped, leaving non-root users in the dark again). The second one is the interesting one here: it indeed seems the ADB daemon on the device doesn't know about the
backupcommand; as you're unlikely to be on Android 11+, this must mean you're on < 4 then – and the "5.0.1" is fake.