Yes, they broke it again. I'm tempted to add a check and a warning to the script (in order to save people further frustration), but it's not clear if this affects everybody, or only some phone models. What is the exact firmware version of your phone (`adb shell getprop ro.build.version.ota`)?
How To Guide [How To Guide] Unlocking using DeepTest (GDPR)
- Thread starter melontini
- Start date
Yes, they broke it again. I'm tempted to add a check and a warning to the script (in order to save people further frustration), but it's not clear if this affects everybody, or only some phone models. What is the exact firmware version of your phone (`adb shell getprop ro.build.version.ota`)?
I haven't tested it, but it does mention oppo/realme and "bootloader unlock".
If anyone wants to try it, go ahead, but I'm not responsible for anything going wrong.
VirusTotal 8 detects:
Last edited:
My phone is Narzo 50 5G
RMX3572_11.C.05_1050_202305151653
the error message is "This model does not support applications"
Using android with rootless system for me like kinda useless and not really like my other Xiaomi devices that can usually be done easily even on MTK chipset.
Does anybody know how to solve this with another best trick.
Does the trick is safe to unlock the bootloader with the different Realme model, should it be fine?
You can try putting `RMX3572` into both rpmodel and model fields, but they started appending your model (the one you send to the server) to the end of the key. I'm not sure if they append the region to the key.
If that fails, Narzo 50 5G has an MTK chipset, mtkclient method might work (Although I have no idea how that works. And if something goes wrong, you can get a hardbrick)
If both methods fail, welcome aboard!
I'm thinking of making a `manufacturer bootloader unlock wall of shame`.
This explains why the deeptesting isn't working at all on the X2 Pro for the last 3 days, cursed timing indeed.
This was posted on May 26th. It's been more than 2 weeks now
realme Community
Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!
Plus, the author of the script confirmed that now it only works on some models https://github.com/turistu/rmx3474-rooting
According to recent comments, it's not working yet.This was posted on May 26th. It's been more than 2 weeks now
realme Community
Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!c.realme.com
Plus, the author of the script confirmed that now it only works on some models https://github.com/turistu/rmx3474-rooting
realme Community
Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!
Something tells me they "temporarily" permanently shut it down.According to recent comments, it's not working yet.
realme Community
Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!
On this realme model I can't get into brom mode, mtk client isn't working on this phoneYou can try putting `RMX3572` into both rpmodel and model fields, but they started appending your model (the one you send to the server) to the end of the key. I'm not sure if they append the region to the key.
If that fails, Narzo 50 5G has an MTK chipset, mtkclient method might work (Although I have no idea how that works. And if something goes wrong, you can get a hardbrick)
If both methods fail, welcome aboard!
I'm thinking of making a `manufacturer bootloader unlock wall of shame`.
I've made the first draft, feel free to correct me on anything/give info on other devices/manufacturers. https://github.com/melontini/bootloader-unlock-wall-of-shame
That's because you have edited the script and changed the model from the supported
RMX3471 or RMX3461 to some other, unsupported model. You were not supposed to do that ;-)
If your serial number is a 8-digit hex number (like deadbeef or 3abf7f5c), then please try
again, with the unedited script from https://github.com/turistu/rmx3474-rooting, overriding
only the serial number and imei (as explained there).
If that doesn't work, I would appreciate if you opened an issue, including the info mentioned in the README.md file.
Last edited:
Is that something they changed with the "security update"? Because before the update, Klajnor here sent almost everything from their device except the model https://forum.xda-developers.com/t/how-to-guide-unlocking-using-deeptest-gdpr.4585829/post-88563821
Not really. Before they starting messing with server, they were NOT accepting a otaVersion not matching the model in the applyLkUnlock request. I know because I had tried it.
Since they had started messing the server, they have gone through 6 or 7 iterations, one sillier than the other, and God knows where they're at now ;-)
Klajnor probably had a phone model also sold in the Indian market (unlike my RMX3474, whose Indian equivalent is totally different device: RMX3388).
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3UPDATE:DO NOT WASTE YOUR TIME. The bypass method has been fixed!!!It's truly joever, done, ended and there's no going barack.Not even if you try with different models, serials, IMEIs, OTAs, etc.It won't work unless you own a phone supported by deep testing without the script!!!If you bought your phone in hopes of unlocking - send it back and buy a Google Pixel, or literally anything that can be unlocked fully offline!!!
Hello there!
If you'd like to submit an application to Deeptest successfully, here's a step-by-step guide:
prereqs:
- Install https://strawberryperl.com/ on Windows. If you're using a Debian-esque system, you can use the command `apt-get install libwww-perl libcrypt-rijndael-perl`.
- Download deeptesting-junk.pl [from here https://github.com/turistu/rmx3474-rooting/blob/main/deeptesting-junk.pl]
- Obtain shell access (e.g., ADB shell, Termux failsafe, an app from the Play Store, etc.).
- On Windows, run `chcp 65001` in your command prompt. This sets the console to UTF-8 encoding, allowing you to see Chinese text correctly in case of errors.
Now, execute the command getprop in your chosen shell and look for the following information:
- ro.build.version.oplusrom [V13.0.0 on a13 RUI4]
- ro.build.version.sdk [your Android version, in SDK format, e.g., 13 → 33]
Code:perl deeptesting-junk.pl pcb 0xSSSSSSSS imei IIIIIIIIIIIIIII cmd applyLkUnlock otaVersion ro.build.version.ota os_version ro.build.version.oplusrom android_version ro.build.version.sdk
where SSSSSSSS is your Serial number (prefixed with 0x), IIIIIIIIIIIIII is the first IMEI. replace ro.* placeholders with actual values.
or alternatively
Open deeptesting-junk.pl in a text editor and locate %cfg.
- put ro.build.version.oplusrom in os_version
- put ro.build.version.sdk in android_version
runwhere S is your Serial prefixed with 0x and I is the first IMEICode:perl deeptesting-junk.pl pcb 0xSSSSSSSS imei IIIIIIIIIIIIIII cmd applyLkUnlock
Note regarding the model, rpmodel and oatVersion fields:
It's fine to leave them as is, but if that doesn't work, try putting RMX3081 in both model and rpmodel and the result of getprop ro.build.version.ota in otaVersion.
Before reapplying with different values, don't forget to close your application by running the same command from before, but with applyLkUnlock replaced by closeApply
Either way, the console should return {"resultCode":0,"msg":"SUCCESS"}
Now, open Deeptest and submit your application. You may need to wait for approval. After that, you can unlock your device as usual.
If you're not sure which Deeptest apk to install, try this one: https://forum.xda-developers.com/t/unlock-bootloader-help.4425415/post-86777721
Reminder:
Code:* Unlocking your bootloader voids your warranty!!! * I am not responsible for any damages that may occur to your phone!!!
All credit to https://github.com/turistu/rmx3474-rooting !
Please let me know if this method works for you.3Seems you don't need to change model in the PL file. In this cese i've got error like "this device not support deeptest" (it was chinese so I used google translator for it)
Any way it ssems working!
Simplest way I think is change config part in the PL script
For example my config part:
Perl:my %cfg = ( cmd => 'acquireClientStatus', url => 'https://lkf.realmemobile.com/realme/v1/', # lkf. if oppo.version.exp feature, lk. otherwise # these are used to build the json POST data model => 'RMX3461', # ro.product.name [RMX3474EEA] pcb => '0xSSSSSSSS', # the serial number with 0x prepended [0x????????] # ro.vold.serialno # /proc/oppoVersion/serialID # /proc/oplusVersion/serialID ** imei => '868853052000000', # the first IMEI otaVersion => 'RMX3081_11.F.03_3030_202304132230', # ro.build.version.ota [RMX3474_11.?.??_????_202?????????] clientStatus => 'i:0', adbDvice => '', # ro.oppo.operator [] # these are used to build the O_NETON: ... HTTP header client_id => '000000000000000', sso_id => 0, rpmodel => 'RMX3461', # ro.product.model [RMX3474] os_version => 'V13.0.0', # ro.build_bak.version.opporom rom_version => '', # ro.build_bak.display.id android_version => 33, # Build.VERSION_SDK_INT [31] key_version => '1.0.3', network_type => 'WIFI', version_name => '1.0.1', );
My serial and imei hidden so fill you data here
And after it just run
Code:perl deeptesting-junk.pl cmd applyLkUnlock
Wait few minutes and check deeptest app or run:
Code:perl deeptesting-junk.pl cmd checkApproveResult
You should see something like:
Code:{"resultCode":0,"msg":"SUCCESS","data":{"unlockCode":"a82ae20(... long-long code was here....)534"}}
PS I can't loose all my data. I have to prepare backups and etc
So I didn't confirm unlock but I hope it should work
PS This script (or oppo/realme servers) returns error on chinese so use google translator and run once command below in console (should work on win 10/11). It will change code page to utf-8
Code:chcp 650011
@melontini Welcome to XDA! I hope you've always an enjoyable time here.
I've removed the link to 4pda from your post! 4pda is not only another phone related website (and not at all affiliated with xda-developers) but also well known for the distribution of malware and warez. Links or references to 4pda are not accepted on XDA at all.
XDA Forum Rules (excerpt):
Please refrain from sharing of such links or references in future! Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator1
Have you tried resubmitting? Turistu says that the script's working again.1
It's rather 256 (the sig or whatever) + 8 (the serial no) = 264 which hex-encoded should have a length of 528 not 522.
