Open ReverendGates opened 1 year ago
@DysasterGates @aisivan36
Could you guys give it a try again?
if you still keep getting a -1006 answer, then first run the script with cmd closeApply
and then apply again with cmd applyLkUnlock
.
@turistu I don't know how... but after i installed oscar.apk from https://c.realme.com/in/post-details/1591008567903752192 and pressed the "green button"(i don't remember the naming on it) it said that my application is approved after 30 seconds without your script. It looks like that servers are working back, but after i tried to unlock bootloader with instruction from 4pda(russian tech forum) and wrote in cmd "fastboot flashing unlock" and pressed start deep-testing on phone, cmd gives back only < waiting for any device > but on phone appears a winking face, writes something on chinese and word fastboot and 6-10 and then instantly restarts.
Captured this moment on the video and it says(google translator)
it said that my application is approved after 30 seconds without your script.
That's because you have submitted the application in the past, and they have finally approved it. Unfortunately, they haven't started supporting the phone model (neither RMX3474RU
, RMX3474EEA
or RMX3474
).
But the phone did not accept the unlock code it got from the server, and did not enter fastboot mode (it should've shown a screeen like this if it had really entered fastboot mode). That's because, since the end of May, they have started including the model number in the unlock code. The people who applied with cmd applyLkUnlock
before the end of May get a working unlock code, those who applied after get a garbage unlock code.
tl;dr; All this pretty much means that my script is pretty much useless with this model too ;-(
So there is still no way to unlock bootloader?
Not now and not with this trick, sorry.
I suggest you exit the deeptesting mode, since it only prevents you from applying for a new code with cmd applyLkUnlock
(should they ever revert that change to the server; it's pretty useless to try that now).
We got a downgrade solution form A13 to A12. What chance, that your deeptestjunk trick will work on it?
I don't think it will work.
I haven't yet got the time to reverse engineer the bootloader, but it seems to do the same checks about the "new struct" and "model name".
adb shell pm has-feature oppo.version.exp - true adb shell getprop ro.product.name - RMX3474RU adb shell getprop ro.product.model - RMX3474 adb shell getprop ro.build.version.ota - RMX3474_11.C.14_1140_202304031900
Still waiting for 2 days already...