@machapman Hi, can you retry once and see if the problem persists? This should not happen. I wonder if the server sent an invalid solution. I will recommend that you delete the UID file and then restart the unlock process.
@movrs Hi, as mentioned on the OTP page, it is only 15 devices a day. We stop the further generation of OTPs after that limit is hit. I know the limit is too small for a global audience, but to ensure that it can stay available for longer time, I had to take such a decision.
The resets happen around 00:00 New York time. You can try close to that :)
Hi @aguery, there are only 15 devices (globally) that we can support in a day. The limit resets at 00:00 in New York time. So, if possible, please try close to that time and you'll be able to get an OTP.
Hi, I'll consider doing that. The complication is that such videos usually attract dislikes because users expect to see a tutorial rather than an advertisement for a paid tool. And for one-off downgrades to unlock, the end users won't be greatly interested in buying a tool themselves and then learning to use it.
I'll still probably try to record my next downgrade session and put it up as a video as a proof of concept. Let's see if the buyer allows for such screen recording :)
I believe what you are doing is right and Magisk is working. When you boot the Magisk patched boot image, you'll be booted to the Android system only. Magisk is a root utility for Android, which means you get root/superuser access when you have Magisk installed/loaded. So, if you want root access within your Android, you can follow the remaining instructions in the guide to complete the full installation.
If you are looking to install a ROM, then you do not need root/Magisk. What you need is TWRP (or fastboot directly if the ROM is an img file that you can flash via fastboot). So, something like:
Flash TWRP (fastboot flash boot twrp.img) to your boot partition (since there is no recovery partition in Android anymore)
Reboot to TWRP
Flash the ROM within TWRP
Change the active boot slot
Erase userdata (factory reset)
Adding to that, please do follow any device-specific instructions. For example for the Nokia 7.2, you will also need to flash vbmeta with disabling flags included. Please follow the XDA threads about the steps to install.
Hi, this is a likely hardware issue with the touchscreen itself and can be improved slightly if the OEM does an OTA update to improve it. But it is largely a hardware issue (usually due to grounding) and cannot be fully gotten rid of by the user.