[GUIDE] [HOWTO] Ulefone Note 9P unlock & root - Android General

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Ulefone Note 9P​
There are a number of "easy" tutorials on how to root the rather new Ulefone Note 9P, but none of them works as inteded, as of today.
After I've found (by my own research) how to unlock the phone, I'm sharing the easy procedure here in hope someone can go a step further and actually root it.
Ulefone Note 9P unlock procedure
- become a developer by tapping 7 times the build number in Phone settings;
- from the Developer Menu, enable OEM unlock and USB Debug
- Install Android platform_tools on your PC (I'm personally on Linux/Ubuntu, so for me it's just a matter of unpacking the archive and fixing some missing libraries)
- Connect the phone to the PC via an USB DATA cable
- Give consensus for USB debug, and allow the PC to access
- "./adb devices" should list the connected phone as "device" (it it's "unauthorized", go to Developer Menu and delete past authorizations for USB Debug)
- "./adb reboot fastboot"
- "./fastboot devices" (check the phone is still there)
- "./fastboot flashing unlock_critical" (OEM unlock and USER DATA WIPEOUT!)
Now my Ulefone Note 9P is actually unlocked (check: from the Developer Menu, you can't re-enable OEM Lock, since it is grayed and reports the bootloader is unlocked already).
Ulefone Note 9P root procedure (help is needed here!)
- Download MagiskManager-v7.5.1.apk
- "./adb install MagiskManager-v7.5.1.apk"
- MagiskManager icon is now on the phone screen
- Download Ulefone Note 9P stock Android 10 image (GQ3092SH1_HC_M629_Ulefone_EEA_20200701_V12.tar.gz)
- Unpack the archive and extract "boot.img"
- Copy the boot.img to the phone via standard file transfer, putting e.g. in the "Download" folder on the phone
- Open MagiskManager on the phone, it says Magisk is not installed
- Click Install, then Install (again), then "Select and update a file"
- Browse and search the boot.img you just downloaded to the phone
- Magisk starts to patch it, then saves the result as "magisk_patched.img" in the same folder
- Transfer the "magisk_patched.img" from the phone back to the PC via standard file transfer
- Download "Smart Phone Flash Tool" (SP_Flash_Tool-5.1916_Linux.zip)
- Open it: a "scatter file" is required for any operation, and it can be found in the same directory where you unpacked the stock ROM (filename: "MT6765_Android_scatter.txt")
- In the Download tab, unselect all partitions, then only select the "boot" partition;
- click on the left, where the filename is, and browse where "magisk_patched.img" is, the select it)
- Now click "Download" in the SP Flash Tool: it waits for the kernel to find the "Product: MT65xx Preloader // Manufacturer: MediaTek"
- reboot the phone while still leaving it connected to the PC
- during reboot, the SP Flash Tool activates and writes the boot partition to the phone.
- Then, currently, the Ulefone Note 9P enters a reboot loop, as soon as you detach it from the PC (it won't even boot until then).
Ulefone Note 9P unbrick procedure
- So the Ulefone Note 9P is in a bootloop now!
- Luckily, even that short boot time is enough to access the "MT65xx Preloader" device in the phone.
- So start the SP Falsh Tool, load scatterfile as before, unselect all partitions then select only boot;
- In the "boot" row, all left, there's the filename: browse and select the original "boot.img" from the stock ROM
- Click Download, and wait for the Preloader to apper...
- Ulefone Note 9P is now able to boot normally, it's still unlocked, but also unrooted...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device

[email protected] said:
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Ulefone Note 9P​
.......
Please keep discussion focused, on questions pertaining to this Device
Click to expand...
Click to collapse
With newer devices you also need to disable verification, in order to boot other unsigned images. Not just bootloader unlock.
This device has three verification partitions that need disabled.
vbmeta
vbmeta_system
vbmeta_vendor
All are found in same stock firmware archive you have mentioned in guide.
flash them in fastboot like this
Code:
fastboot --disable-verity --disable-verification flash vbmeta /some-directorty-on-your-pc/vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system /some-directorty-on-your-pc/vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor /some-directorty-on-your-pc/vbmeta_vendor.img
now you can either flash the magisk-modified-boot.img to boot in fastboot or back to spflash tool.
it will not bootloop. but sorry, root was still not working.
Can confirm flashing GSI roms works also. even the new android 11 GSI.
if interested I have been using tags on my posts, when for devices that do not have there own forum section.
https://forum.xda-developers.com/tags.php?tag=ulefone+note+9p

Related

[ROOT] Install Magisk on ZC551KL Guide "FINALLY"

This is a messy post, do as you please with it. I am not responisble for ang damage to your device. Additionally, I dont take any credits for any of this, I just put everything together here.
Tags zc551kl Asus Zenfone 3 Laser z01bdc
Tools Needed:
Asus Bootloacker Unlock Tool - http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZC551KL/UnlockTool_Android_M_0706_signed1.apk
You current boot.img version which can be downloaded from here [Its packaged in the update file]- https://www.asus.com/us/Phone/ZenFone-3-Laser-ZC551KL/HelpDesk_BIOS/
ADB and Fastboot from here [Credits to Snoop05] - https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
Magisk Manager - https://tiny.cc/latestmanager
Prep:
Install the Asus Unlocker on your phone and unlock it.
Install Magisk Manager on your phone but dont run it yet.
Enable USB Degugging on your phone.
Install ABD and Fastboot on your PC. It will be installed to c:/adb/
Download the update that matches your phone version to your pc. [Mine was version "WW-32.40.106.41"]
Open the update file on your pc with your favorite zip manager and extract the boot.img .
Put the boot.img onto your phones internal storage.
Follow this guide [Credits to Dhananjay @ thecustomandroid.com]
» Non-rooted devices
Magisk 14.0 introduces a new and neat method to install on non-rooted Android devices. This new process doesn’t require your device to be rooted, nor does it require a custom recovery like TWRP. But for this method to work, your device must have the stock boot.
But for this method to work, your device must have the stock boot.img dump placed in the internal storage.
Make sure that you enable USB debugging and setup ADB access first, you will need it later in the guide.
Download Magisk Manager 5.3.0: Link
When the APK has been downloaded, use a file manager to install it. Now run the app from the app drawer.
Go to the app settings and tap on “Patched Boot Output Format”. You can select “.img.tar” if you will be using ODIN to flash the file or else simply select “.img” for the rest of the devices.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go back to the app main screen and tap on the “Install” button. Go to INSTALL > PATCH BOOT IMAGE FILE.
Navigate through the storage and select the stock boot.img file. As soon as you select the stock boot.img file, the app will download the installer to patch the image.
Once the process is complete, you can tap on the “CLOSE” button.
Your new and patched boot image now include root and support for modules. So the last step is to grab this boot file and flash it your device via fastboot or ODIN (Depending on the output format you chose in step #4).
Connect your device to the PC via USB cable and navigate to the Magisk Manager folder inside the storage. Your “patched_boot.img” file will be present right there. So copy it to your PC.
Move the “patched_boot.img” file to C:/adb folder. And type in the following command to boot your phone into bootloader/fastboot mode:
adb reboot bootloader
Once your phone enters the bootloader/fastboot mode, enter the command to flash the file:
fastboot flash boot patched_boot.img
Finally, reboot your device:
fastboot reboot
That’s all, you have just installed one of the most trending mod out there and especially on your non-rooted device without any need of a custom recovery. Isn’t it great? Tinker around with the app and see what all things you could do.
I can confirm this is working! Thank you!
Reporting working on Android O (8.0), I download update from Asus and patch boot image. Thanks
kamo84 said:
Reporting working on Android O (8.0), I download update from Asus and patch boot image. Thanks
Click to expand...
Click to collapse
I know it's been some time since this was discussed, but I am trying to go through this process. Can you confirm that you unlocked the bootloader on 8.0 with the Asus tool? Or did you install magisk without unlocking the bootloader (if that's possible)?
thanks
I don't think the unlocker tool works anymore.

[Official][Recovery]TWRP for the Huawei Y3 2017 CRO-U00

TeamWin Recovery Project 3.2.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING #1: Unlocking BL and flashing a custom recovery voids your warranty. Please make sure to contact your carrier/seller if your phone is still under warranty after unlocking the bootloader.
WARNING #2: Make sure you have enabled OEM unlock and unlocked bootloader before trying to flash this. How you can successful root and install TWRP will be described below.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
HOW-TO UNLOCK BOOTLOADER
1. Get bootloader Unlock code here
2. Install minimal adb and fastboot
3. Plug in your phone and make sure all huawei drivers got installed
4. Enable developer options in settings as described above.
5. Enable OEM unlock, enable USB debugging (both in developer options)
6. Open the adb tool you installed recently
7. Type fastboot devices (now a device number should show up)
8. Type fastboot reboot-bootloader (your phone will now boot into bootloader, if not, you haven't set up drivers or adb/fastboot correctly)
9. This step will wipe all your data! Type:
Code:
Code:
fastboot oem unlock xxxxxxxxxxxxxxxx
(xx is for your unlock code)
10. Ones it's done type:
Code:
Code:
fastboot reboot
Your phone will reboot and you have an unlocked bootloader!
11. You can now go on installing TWRP on your device
HOW-TO INSTALL
Make sure you enabled OEM unlock in settings, if you haven't please do that now by tipping 10 times on build number (to activate developer options), than open developer options and go to OEM unlock, enable it
Have an unlocked bootloader is required! (In my case, I login the unlocker website at provide necessary information and get the unlock code so try yourself !!!)
Download the TWRP recovery from the download section below
Make sure you got fastboot drivers installed (I will describe this below in how to unlock your bootloader)
Open the adb/fastboot application on your pc and go to the directory where your TWRP img file is downloaded
Boot your phone into download mode (First method: fastboot reboot-bootloader while connected to pc. Second method: power off your phone, hit power on and volume down until it boots to download mode)
Check again if there is written: unlocked phone!
If yes type now into your adb/fastboot terminal:
Code:
fastboot flash recovery twrp-3.2.3-0-CRO_U00.img
Click to expand...
Click to collapse
Type:
Code:
Code:
fastboot reboot
Now boot into recovery by pressing: power+volume up+volume down at the same time
Enjoy twrp
HOW-TO ROOT
Backup, just in case
Have an unlocked bootloader and TWRP installed from above (take one from december)
We will use this root method: Phh's superuser
Download latest official phh superuser zip here.
Put the zip on your external sd card of your phone (since we can't access /data in twrp)
Boot into twrp and flash the downloaded file
Install latest Material phh apk: Release post
Now you are rooted, congrats!
SUPPORTED DEVICES
CRO-U00
HWCRO-U6580M
(Test your Device, if you want to take the risk )
Official Release Link : https://twrp.me/huawei/huaweiy32017.html
DOWNLOAD
Updated Link Shared In Next Post.
Contributors
Omni 5.1.1 Minimal Twrp Source
Ubuntu 16.04
Google
HWDEV
****
More Information Given Later
[Reserved Post]
Thank you !
Thank you buddy. Though the link you mentioned for DOWNLOAD is no longer available, but I found one in the Official Release Link. :good:
key

[TWRP 3.4.0-0] [OFFICIAL] BQ Aquaris M8 (aquaris_m8) (MT8163)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP FOR BQ AQUARIS M8​Reliable root and recovery method for bq m8. Thanks to @diplomatic for compiling TWRP for this tablet and thanks to the TWRP team. I have tested this recovery and it has no errors.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION
- Go to developer settings and turn on OEM unlock
- Power off the tablet and boot to fastboot mode (power and volume -)
- Open a comand prompt and type:
Code:
fastboot oem-unlock
All the data will be loss
- Confirm the oem unlock by pressing the volume + button
- And now type:
Code:
fastboot continue
- When the tablet is turned on, and you complete the setup wizard, type:
Code:
adb reboot bootloader
- When fastboot mode appears in a corner of the tablet, type the following command:
Code:
fastboot boot twrp-3.X.X-X_aquaris_m8.img
- Now the TeamWin logo will appear. Go to install and select install image. Search for the twrp img in the internal memory and select it.
- When ask where you want to install it, choose recovery and slide to install
- And now reboot system
ROOTING WITH SUPERSU OR MAGISK
- Download this boot.img
- Copy the boot.img to the internal storage
- Reboot to recovery
- Go to install and select install image
- Select the boot.img, select boot partition and swipe to install
- Now you can install the magisk or supersu zip
DOWNLOADS:
- TWRP 3.3.1-0 IMG: https://github.com/R0rt1z2/android_device_bq_aquaris_m8/releases/tag/twrp
- TWRP 3.2.3-0 IMG: https://www.androidfilehost.com/?fid=11410963190603877900
- SUPERSU ZIP: https://www.androidfilehost.com/?fid=11410963190603867786
- MAGISK ZIP: https://github.com/topjohnwu/Magisk/releases/download/v18.0/Magisk-v18.0.zip
- XPOSED ZIP: http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v89-sdk23-arm64.zip
- XPOSED APK: https://forum.xda-developers.com/attachment.php?attachmentid=4393082&d=1516301692
SOURCE CODE:
Download
THANKS TO:
@diplomatic for compile TWRP.
Rortiz2 said:
Once the exploit finishes, flash the seccfg unlocked partition:
Code:
dd if=/sdcard/seccfg of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/seccfg
Click to expand...
Click to collapse
How can this work? The data in that file is encrypted with a device-specific key. It will not unlock any other device but the one it came from. If that does what you say it does, I will eat my sock.
diplomatic said:
How can this work? The data in that file is encrypted with a device-specific key. It will not unlock any other device but the one it came from. If that does what you say it does, I will eat my sock.
Click to expand...
Click to collapse
I pulled that file of my BQ when it had the unlocked BL. I pm'ed some people in a Spanish forum for test if it works, and it worked...
@Rortiz2, are you sure it actually unlocked their BL, and it wasn't just placebo? What I mean is did it show "Orange State" or did it end up in a bootable "Red State" in which the seccfg step did not make any difference? Because I've tried to decrypt the seccfg data from my own Zenpad on another unit, same model, and it failed. That confirms that the embedded keys are different. If it was all the same key, then unlocking a BL would be as simple as flashing some data with SP Flash Tool.
diplomatic said:
@Rortiz2, are you sure it actually unlocked their BL, and it wasn't just placebo? What I mean is did it show "Orange State" or did it end up in a bootable "Red State" in which the seccfg step did not make any difference? Because I've tried to decrypt the seccfg data from my own Zenpad on another unit, same model, and it failed. That confirms that the embedded keys are different. If it was all the same key, then unlocking a BL would be as simple as flashing some data with SP Flash Tool.
Click to expand...
Click to collapse
I've misunderstood you. You're right, it seems that this partition contains device specific codes. It casues red state.
Sorry!
OK, that makes more sense. There won't be any sock-eating yet. But either way, if you can boot it with Red (or yellow) State, it means you don't have to unlock and can still keep your data....
Released 3.3.1-0.
Official support is up!
https://twrp.me/bq/bqaquarism8.html

Zeblaze Thor 6 TWRP

Zeblaze Thor 6 TWRP 3.4.0.0 (unofficial)
99% complete
>Settings >About watch >Build number
>Click on the build number
>Developer options enabled
>Back
>System >Developer options
>OEM unlocking
>USB debugging
Open Minimal ADB and Fastboot folder
Paste the recovery.img file inside the Minimal ADB and Fastboot folder
Open Minimal ADB and Fastboot
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery recovery.img
fastboot reboot
Note: TWRP can read but not modify the contents of dynamic partitions. You cannot modify an apk file. But you can modify a super.img partition. I'm thinking of converting dynamic partitions in the future. So we can get the full benefit of TWRP. I hope it will be successful.
if you want to delete/add an apk file edit the super.img section using crb_v3b10. Flash the super.img partition using TWRP and don't forget to run the following command using the Bootloader.
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
recovery.img
drive.google.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
friend would it be possible to make a version for Kospet Optimus 2?
I am neither a programmer nor an editor. I'm just an enthusiast. I don't have any information. I just analyze and modify it. It actually belonged to TWRP Lemfo lem12 pro. I analyzed it and adapted it for Zeblaze Thor 6. Then I analyzed the UI. I tried to save the user interface from its boring appearance and turn it into a beautiful and useful interface. This job took 2 months. I have not yet received a positive response feedback. Maybe nobody liked this new UI.
I don't have Kospet prime 2 to do an adequate analysis. All I can do is replace its core. They have similar hardware. So there is a chance it will work. Now it's up to you to try it. Please give feedback if it works or not.
Follow the above procedures for installation.
Good luck amigo.
recovery_KP2_TWRP.img
drive.google.com
AYALTUN said:
Zeblaze Thor 6 TWRP 3.4.0.0 (unofficial)
99% complete
>Settings >About watch >Build number
>Click on the build number
>Developer options enabled
>Back
>System >Developer options
>OEM unlocking
>USB debugging
Open Minimal ADB and Fastboot folder
Paste the recovery.img file inside the Minimal ADB and Fastboot folder
Open Minimal ADB and Fastboot
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery recovery.img
fastboot reboot
Note: TWRP can read but not modify the contents of dynamic partitions. You cannot modify an apk file. But you can modify a super.img partition. I'm thinking of converting dynamic partitions in the future. So we can get the full benefit of TWRP. I hope it will be successful.
if you want to delete/add an apk file edit the super.img section using crb_v3b10. Flash the super.img partition using TWRP and don't forget to run the following command using the Bootloader.
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
recovery.img
drive.google.com
View attachment 5475289View attachment 5475293
View attachment 5475285View attachment 5475283View attachment 5475287View attachment 5475295
View attachment 5475279View attachment 5475277
Click to expand...
Click to collapse
can you please send me link to crb_v3b10 i cant not find it anywhere and beta12 and 14 do not work for me
blaze2051 said:
can you please send me link to crb_v3b10 i cant not find it anywhere and beta12 and 14 do not work for me
Click to expand...
Click to collapse
I deleted crb_v3b10. Even if you reinstall crb_v3b10, it still won't work. Even if you reinstall crb_v3b10, it still won't work. The problem is not the versions. The problem is that you did the installation incorrectly. Delete all versions. Download the latest version. Run crb.exe. Select the Unregister distro option. Select the Import distro option. Select the test distro option. Close the window. Crb will open automatically. Tried on the latest version for windows 10. I don't know if it works on older windows 10 versions. It also works on Windows 11.
AYALTUN said:
I deleted crb_v3b10. Even if you reinstall crb_v3b10, it still won't work. Even if you reinstall crb_v3b10, it still won't work. The problem is not the versions. The problem is that you did the installation incorrectly. Delete all versions. Download the latest version. Run crb.exe. Select the Unregister distro option. Select the Import distro option. Select the test distro option. Close the window. Crb will open automatically. Tried on the latest version for windows 10. I don't know if it works on older windows 10 versions. It also works on Windows 11.
Click to expand...
Click to collapse
ill try that but all the options are blacked out and the only one i can select is enable wsl before it will let me choice anything else which would be import distro after a reboot of windows
@AYALTUN How did you unlock bootloader? When I type fastboot flashing unlock I have info on my watch screen about pressing vol button but non of them works. I have Thor 5 smartwatch and only power and back buttons. When I press them nothing happens. Pls help me i am confused.
ktl20 said:
@AYALTUN How did you unlock bootloader? When I type fastboot flashing unlock I have info on my watch screen about pressing vol button but non of them works. I have Thor 5 smartwatch and only power and back buttons. When I press them nothing happens. Pls help me i am confused.
Click to expand...
Click to collapse
I'm sorry. If you get a warning saying press the volume button, there is nothing you can do. You will not be able to unlock bootloader.

[UNBRICK][REALME][MTK] Free Unbrick guide for all Realme Mediatek devices [NO-AUTH]

Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for Realme Mediatek devices only . DON'T DO ANY OF THESE IF YOU HAVE SOMETHING ELSE!
ALWAYS USE DOWNLOAD ONLY MODE OF SP FLASH TOOL.
DON'T TOUCH ANYTHING RELATED TO FORMAT ON SP FLASH TOOL! (IT'S WRITTEN EVERYWHERE, YOU WILL LOSE YOUR IMEIS IF YOU USE FORMAT ALL + DOWNLOAD. YOU ARE SAFE IF YOU USE DOWNLOAD ONLY.)
Windows Method
Requirements:
Device Firmware (Download as per your device model)
Bypass Tools Pack
SP Flash Tool
Install Python from Windows Store
libusb-win32 - Having Issues? Use this.
Get usbdk installer (.msi) from here and install it
MAKING YOUR FIRMWARE READY:
1) Clone this repository : oppo_decrypt
Code:
git clone https://github.com/bkerler/oppo_decrypt
or download the repo zip and extract it
2) Extract the downloaded firmware and move the ofp file to the oppo_decrypt folder
3) In the oppo_decrypt folder open cmd and type these:
Code:
pip3 install -r requirements.txt
(Make sure you have python and pip installed)
4) All the requirements are installed, now it's time to decrypt the ofp:
Code:
python3 ofp_mtk_decrypt.py name_of_file.ofp out
(Replace the ofp name with your actual ofp name)
5) After the decryption now its time to merge superimages (THIS IS ONLY FOR DEVICES WITH DYNAMIC PARTITIONS, IGNORE THIS STEP FOR NON-DYNAMIC DEVICES)
- Install ubuntu from wsl : Guide for that
- Run ubuntu and install simg2img
Code:
sudo apt install simg2img
- Go to the path of your extracted ofp
e.g.
Code:
cd /mnt/d/oppo_decrypt/out
(go to the path of your out folder)
- Check the supermap.csv file
Code:
nano supermap.csv
- check your region and note the superimages names
- Now to merge them :
Code:
simg2img super.0.xxxx.img super.1.xxxx.img super.2.xxxx.img super.img
(Replace the xxxx with the super images' names from your region.)
- After this you will get a Super.img in that out folder
- Now go to scatter file in out folder and edit it (Search Super.img in that and change is_download=false to true)
FLASHING THE FIRMWARE:
1) Extract the bypass zip
2) Go to driver folder, find the .inf file right click and press install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3)Download this file and install it, after installing power off phone and connect to pc while holding Vol+- (don't leave the buttons after connecting) . You might need this driver as well if it's not detected.
Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off, and don't leave the buttons) and you will see the mtkdriver down below. Install it.
Choose MediaTek USB Port and install it.
4)Then run the brom.bat under Bypass folder.
5) Now power off the phone and connect the phone while holding volume + and - (Don't leave the buttons until the bypass is done)
6)After the above step Go into Flash Tool folder and open the SPFlash tool go to Options>Option
Click on Connections and select UART and set Baud Rate to 921600
7) after that choose scatter file and also if not set, set your download-agent. You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
8) Uncheck oplusreserve2 first. Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone and use it like before now! All your userdata will (inevitably) be cleared!
After flashing it should look like this. Download has been complete. Enjoy!
Notes :
After this phone might not boot due to encryption, you can do any of the below procedures to format your data and boot your phone
1. In case you can access recovery by holding volume and power button - Wipe all data from recovery and reboot
2. In case you cannot access recovery, power off phone then enter this command in mtkclient :
Code:
python mtk e metadata,userdata,md_udc
and connect phone while holding both volume buttons. After this just reboot phone
Also note that first boot takes some time, so don't panic leave it for few minutes it'll boot
Credits :
https://github.com/bkerler/ for decryptor and for creating the tool.
Good morning, @pritish1998. Thanks for the effort in producing this well-illustrated and in-depth writeup. Please note, however, that I am removing the reference to Telegram that was previously in your post.
Regarding social networking links, please observe that, as an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we only grant developers the privilege to share references to their social networks in their own development threads, and if thorough support is also provided in that thread. These conditions don't apply to this thread. Additional information is also available here:
Telegram Chat Channels - Way Forward​
Thanks for your cooperation.

Categories

Resources