Thanks for the reply. I really want to buy one of the to depending on the call recording availability, its a must for me.
If anybody knows what rom has call recorder please let me know
How To Guide [Chinese and Global Version] Unlock bootloader, updated
- Thread starter myogui
- Start date
If anybody knows what rom has call recorder please let me know
Anyone with European phone try to flash Indian A13 beta, flash rollback indian A12 package and then try to unlock ? In realme forum, I read one user flash by mistake European A13 beta to indian phone successfully.
www.xda-developers.com
Download: Android 13 beta is now available for the Realme GT 2 Pro
Realme has released the Android 13 Beta 1 build for the Realme GT 2 Pro through its Developer Preview program. Read on to know more!
Unfortunately, you can't install Indian A13 beta over EU ROM. I just tried.Anyone with European phone try to flash Indian A13 beta, flash rollback indian A12 package and then try to unlock ? In realme forum, I read one user flash by mistake European A13 beta to indian phone successfully.
Download: Android 13 beta is now available for the Realme GT 2 Pro
Realme has released the Android 13 Beta 1 build for the Realme GT 2 Pro through its Developer Preview program. Read on to know more!
Maybe you can try to upgrade to European A13 beta and then try to use Indian A12 rollback package ?
Already tried. The model numbers are different RMX3301 vs RMX3301EEA, so it won't verify.
D
Deleted member 1755208
Guest
U need lock bootloader.Any banking apps can not used . How to reinstall china rom
Can someone with Global RMX3301 GT2 Pro (not the RMX3300 Chinese to Global flash) run this in Termux or other CLI and report the value?
getprop ro.build.oplus_nv_id
The stock ROM flash contains multiple super.img files dependent on nv_id
3 x super img files are merged into one for specific region and used for flash
Below is an example for A.16 ROM
Myogui Global ROM flash reports 11010 (TW)
getprop ro.build.oplus_nv_id
The stock ROM flash contains multiple super.img files dependent on nv_id
3 x super img files are merged into one for specific region and used for flash
Below is an example for A.16 ROM
Myogui Global ROM flash reports 11010 (TW)
| nv_id | nv_text | super_0_path | super_1_path | super_2_path |
| 11010 | TW | super.0.ad946a19.img | super.1.ba735c68.img | super.2.fbe1edbd.img |
| 11011 | IN | super.0.ad946a19.img | super.1.ba735c68.img | super.2.5300e516.img |
| 110011 | ID | super.0.ad946a19.img | super.1.ba735c68.img | super.2.0b7dcd09.img |
| 110111 | RU | super.0.ad946a19.img | super.1.ba735c68.img | super.2.23bb3f6a.img |
| 111000 | MY | super.0.ad946a19.img | super.1.ba735c68.img | super.2.1d9738ec.img |
| 111001 | TH | super.0.ad946a19.img | super.1.ba735c68.img | super.2.2af0319f.img |
| 111110 | PH | super.0.ad946a19.img | super.1.ba735c68.img | super.2.9e14078e.img |
| 10000011 | SA | super.0.ad946a19.img | super.1.ba735c68.img | super.2.714754e6.img |
| 10011010 | LATAM | super.0.ad946a19.img | super.1.ba735c68.img | super.2.80e6f651.img |
| 10011110 | BR | super.0.ad946a19.img | super.1.ba735c68.img | super.2.6f7e5f51.img |
| 10100110 | MEA | super.0.ad946a19.img | super.1.ba735c68.img | super.2.828ca058.img |
| 0 | MEA | super.0.ad946a19.img | super.1.ba735c68.img | super.2.828ca058.img |
Last edited:
is there anyway to use this info to change region from TW to maybe MEA? I am on converted global rom A17
Just download the latest firmware and flash it with this tool. If it doesn't work you have to merge the three super files corresponding to the MEA region in one using simg2img, and then you can try
fastboot flash super super.img or use lpunpack to extract all the files inside and flash them as you already did for the already prepared ROM in the first post.
I will upload A.16 Global MEA super.img (non-GDPR)
Available here:
https://drive.google.com/drive/folders/1Y5mZtZchLytYqDqs0sOYTqCmaZeURrJ5?usp=sharing
You would need to downgrade from A.17 to A.16. All other flash files apart from super.img are same
It is unclear what exactly are the differences between the regions. It could be just the preloaded apps.
I really need help with dat i dont know what to do i have the APK app and i unlocked the bootloader (i cant even press on it, its unlocked all the time by it self) USB debugging is unlocked too, when i try to run the APK app it says "Run the bootloader lock command in fastboot mode. After the bootloader is locked,you can exit deep testing" can someone please help what to do? i cant run the APK deep test it says all the time the same thing
Last edited:
Have you tried running the bootloader lock command in fastboot mode?
"fastboot flashing lock"
Has anyone been able to unlock their bootloader on the export/IN version of A.17. The depth test approves the application but once in fastboot mode the phone will not communicate with PC. Not an issue with the PC either because all my other phones communicate just not this one. Also the android 13 beta gives a "verification failed" and the rollback gives "not compatible with your system" and the factory reset option in settings also doesn't work. Have tried requesting to exit depth test and reapplying and updating platform-tools and still none of these work anymore.
Edit: nvm for some reason I had to update the adb bootloader interface drivers for the phone even tho it had been working on A.16. Turning off developer options also fixed the factory reset not working. Still won't let me use the Android 13 beta or rollback package tho but the guide says the phone has to be on A.14/latest firmware in order to work so maybe that's why.
Edit: nvm for some reason I had to update the adb bootloader interface drivers for the phone even tho it had been working on A.16. Turning off developer options also fixed the factory reset not working. Still won't let me use the Android 13 beta or rollback package tho but the guide says the phone has to be on A.14/latest firmware in order to work so maybe that's why.
Last edited:
If you're using the OTA package I posted in my guide, it's only for the EU model. You can use the IN rollback package, but you don't need to be on A.14 to unlock the bootloader anyway.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
9I am not responsible for bricked devices, dead SD cards, etc!
I have not tested the global unlock, Global version unlock thread.
Make sure you make backups before unlocking the bootloader, as this operation will wipe all user data and apps.
Make sure your system version is the official and latest one.
Requirements
- 60% charge on the phone
- PC and usb data cable
- Installed fastboot and proper drivers on your PC
1. Install Deep Testing Apk attached in this post.
2. Click on the Apply Now button in order to get approval for bootloader unlock.
3. Check the status after apply using the Query Approval Status.
4. If you get an error, force stop the application, change your device language to Chinese and try again (if someone can post screenshot of what to tap, I would update this post)
5. Once the approval is done, tap Start Testing button, this will reboot your device in the bootloader.
6. Last chance, make backups at this point otherwise your data is gone.
7. Run command8. Done, you can now reboot into system normallyCode:fastboot flashing unlock
If I missed anything, kindly comment and I'll update OP.2
Don't relock the bootloader using the ADB lock command. This will brick your device!1
Same problem. It work for me trying all Chinese languages (simple and another two). It seems stuck for like 30 minutes, then idk why I've exit and re enter the app and it worked.
New posts
-
How to unlock fastboot of Redmi 9AT?- Latest: GamerNameHere