Database Info

[Q] [HELP]

Please help me:
After i try to s-off my htc desire like this Tutorial: (http://forum.xda-developers.com/showthread.php?t=805811) my PC is broken after i installed the universal usb installer. Now the PC boot: SYSLINUX 4.07 EDD ...... ERROR: No configuration directive found! boot:
How can i rescue my WIndows??????

Meujki said:
Please help me:
After i try to s-off my htc desire like this Tutorial: (http://forum.xda-developers.com/showthread.php?t=805811) my PC is broken after i installed the universal usb installer. Now the PC boot: SYSLINUX 4.07 EDD ...... ERROR: No configuration directive found! boot:
How can i rescue my WIndows??????
Click to expand...
Click to collapse
1. Insert your Windows CD and boot as if you're going to re-install the OS
2. When it gets to the main screen go to the text that says "Repair your PC".
3. Once clicked on go to the command prompt option and select it
4. Now type DISKPART
5. Type select disk0 then list partitions
6. Select your windows install, usually partition 1 by using the command: select partition 1
7. Now type active and press enter, once finished delete the cmd screen and launch startup repair and once it's finished you should be able to boot back into windows

[Completed] Help Me....Huawei G610-U20 - Unusual things happening

Hi
i am using Huawei G610-U20 since 3 years and it was working fine.
3 weeks before I found that the phone is getting restarted without any reason but with no fixed frequency. sometimes its own, sometimes while connecting to the pc or sometimes when connecting power.
Then I tried to uninstall some apps like bittorrent, whatsapp etc..it shows app uninstalled successfully but after a restart, these apps are back there.
I tried to flash the phone by using MTK Droid Root & Tool and as to begin with ROOT option, when clicking root button, it shows the following error:
--->>> Connect to device <<<---
ERROR file isn't found D:\Tools\Mtk_Droid_Tool_v2.5.3\files\pwn
/system/bin/sh: /data/local/tmp/pwn: not found
ATTENTION! Requests for confirmation on the device screen are possible!
--- ERROR : SU inaccessible
--- Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Then I went through the post and created scatter file. Then start with SP Flash tools, did the following things as mentioned in the thread.
1. Loaded the scatter file
2. Choose path and a ROM file name
3. Determine the ROM_ size by finding out the address after the RECOVERY IN scatter file and provide start address too.
4. Turned off the phone
5. choose Read Back ROM_
then I connect the cable to the pc. after few seconds, it shows the following error
BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL(2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
As they mentioned, I tried to change the USB port and cable but results are same as before.
I notice one thing. Even though I enabled USB debugging, after a restart USB debugging is disabled.
It means whatever things I did before a restart, it reverses after a restart.
Please help me.

raleindia said:
Hi
i am using Huawei G610-U20 since 3 years and it was working fine.
3 weeks before I found that the phone is getting restarted without any reason but with no fixed frequency. sometimes its own, sometimes while connecting to the pc or sometimes when connecting power.
Then I tried to uninstall some apps like bittorrent, whatsapp etc..it shows app uninstalled successfully but after a restart, these apps are back there.
I tried to flash the phone by using MTK Droid Root & Tool and as to begin with ROOT option, when clicking root button, it shows the following error:
--->>> Connect to device <<<---
ERROR file isn't found D:\Tools\Mtk_Droid_Tool_v2.5.3\files\pwn
/system/bin/sh: /data/local/tmp/pwn: not found
ATTENTION! Requests for confirmation on the device screen are possible!
--- ERROR : SU inaccessible
--- Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Then I went through the post and created scatter file. Then start with SP Flash tools, did the following things as mentioned in the thread.
1. Loaded the scatter file
2. Choose path and a ROM file name
3. Determine the ROM_ size by finding out the address after the RECOVERY IN scatter file and provide start address too.
4. Turned off the phone
5. choose Read Back ROM_
then I connect the cable to the pc. after few seconds, it shows the following error
BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL(2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
As they mentioned, I tried to change the USB port and cable but results are same as before.
I notice one thing. Even though I enabled USB debugging, after a restart USB debugging is disabled.
It means whatever things I did before a restart, it reverses after a restart.
Please help me.
Click to expand...
Click to collapse
Hi, Thanks for using XDA assist.
It looks like there is no dedicated forum for your device, however
There is a general forum for android here http://forum.xda-developers.com/android/help where you can try to ask to get expert's help.
Good luck

[FIX] Unknown USB device (Device Descriptor Request Failed) Fastboot Windows 10

First of all, I have a HTC Droid DNA. I was searching for about a year. Finally I got a solution for my problem and I know some of you are still out there with no solution.
The Fail Code is: Unknown USB device (Device Descriptor Request Failed)
Windows has stopped this device because it has reported problems. (Code 43)
So I found a German solution where you have to go to regedit.
Step 1: You need to install the HTC drivers (Google, Samsung etc...) in the normal mode your PC will find your phone, but when you turn into Fastboot you get that error "Unknown USB device (Device Descriptor Request Failed) "
Step 2: Make sure you see that error in your Device Manager under USB - Controller
Step 3: Open "regedit"
Step 4: Navigate to : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags
Step 5: Create a new Key called
0BB40FF00100
Step 6: In that Key you create a Binary Value
Name: SkipBOSDescriptorQuery
Value: 01 00 00 00 (ignore the "0000" at the beginning)
Step 7: Reconnect the Phone and enjoy your FIX
I hope I helped you. I can just tell you that it worked for me. I m not sure if it works on all HTC devices.

tried it with a S7 right now, didnt work. thanks for your post tho!

Had the solution for windows 8.1, from a blog on microsoft MSDN. (Sorry can't link to it. Since I'm new @ xda)
But as it turned out the Datatype for SkipBOSDescriptorQuery has changed from windows 8.1 to 10. Instead of a DWORD Value in Windows 8.1 it should be a Binary Value in Windows 10 .
So thanks :good: Now I can connect via fastboot to my HTC Incredible S.
Ps. Google this:
why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43
And blogpost will show as top result

Thank you very much the regedit method worked for sure..
I spent 5 hours on my computer and laptop different usb cables different ports installing uninstalling drivers and ADB nothing
Thanks BoBo Rich:good:

Thnx!!

Didn't work for HTC Explorer (Pico)

Worked with the HTC Aria on Win10 x64!
Thanks a ton.
edit: Hrm. Seems to have cropped up again. Time to continue the battle *sigh*
edit 2: Got it! Thankfully I had a Win7 laptop that I was able to fire up. The HTC Aria's fastboot hardware ID is "USB\VID_0BB4&PID_0FFF&REV_0100" which means the vvvvpppprrrr is 0BB40FFF0100. So follow the instructions above but using the key of 0BB40FFF0100

Has anyone else gotten this to work?
My Pixel XL isn't recognized at all when plugged in while in system, but it shows up as unrecognized when plugged in while in fastboot. But despite installing the drivers, Windows still refuses to recognize the phone. I tried the various solutions in this thread, but none of them worked. Perhaps it's because my Pixel's fastboot hardware ID is different, but I can't seem to find out what it is.

work perfectly for htc one xl (evita). Thanks !!

Thanks
After 48 Hours of searching!! thanks man! HTC ONE S (Ville)

Thanks! I have this problem with my Shield TV Pro, will try this after work.
Here's some PowerShell code for doing the registry editing, if anyone is interested.
Code:
#Requires -RunAsAdministrator
[string] $Path = 'HKLM:\SYSTEM\CurrentControlSet\Control\usbflags\0BB40FF00100'
[string] $Name = 'SkipBOSDescriptorQuery'
if ($false) {
# Create the path if not exist
if (-not(Test-Path -Path $Path)){New-Item -Path $Path -ItemType 'Directory'}
# Set "SkipBOSDescriptorQuery" to $true
Set-ItemProperty -Path $Path -Name $Name -Value 1 -Type 'DWord'
# Set "SkipBOSDescriptorQuery" to $false
Set-ItemProperty -Path $Path -Name $Name -Value 0 -Type 'DWord'
# Remove item
Remove-ItemProperty -Path $Path -Name $Name
# Remove path and item(s)
Remove-Item -Path $Path -Recurse -Force
}
Edit: This did not work for my Shield TV 2015 Pro unfortunately..

The error changes to "Port Reset failed". Error code remains the same 43. In my case I am trying to connect an LG G3 D858HK. I have tried many different cabels but no solution.

Unknown usb device error Motorola

Doesn't work on lg v20... Haven't been able to fix this issue for a while now..

Thanks for the info mate !
The registry key worked just great in my Windows 10 x64 computer at home and at my work laptop.
I have a Huawei P9 mobile Device.
Had this issue and nothing i tried seemed to work.
Your key did.
Thanks again !!!:good::good:

V20 Method prior to attempt....
@texas### whos still having trouble with a V20 stuck in the firmware screen ( like me) and I have a theory so I'm posting this prior to attempting it but someone please let me know if I have this wrong.
I read this post on the first page of the thread by someone whos name I've forgotten now (sorry) but they wrote....
--------------- edit: Hrm. Seems to have cropped up again. Time to continue the battle *sigh*
edit 2: Got it! Thankfully I had a Win7 laptop that I was able to fire up. The HTC Aria's fastboot hardware ID is "USB\VID_0BB4&PID_0FFF&REV_0100" which means the vvvvpppprrrr is 0BB40FFF0100. So follow the instructions above but using the key of 0BB40FFF0100 -----------------------
and based on this --- my V20 hardware ID reads "USB\VID_0000&PID_0002\5&2BF451F8&0&2" or rather the instance path does and using this I should be able to correct the value of the binary string to fit this corresponding ID for the VVVVPPPPRRRR correct? so value will be "0000000252BF451f02" ????
Im making the key and binary value now and I'll repost results later
I'm so invested in this phone both in time and sheer ignorance of what else I can do to get this damn thing out of the firmware screen.
* I've tried loading the "LG drivers from both LG composite device and VZW versions" to no avail.
*On a side note, tapping the power button brings up a "download mode" sub screen where is searches for wifi connections and after finding mine I went ahead and tried to connect 1- normally 2- removing my wifi password 3- using the WPS button to connect, all of which ended in "connection failed" so can someone explain the actual purpose of this option if there is no way to connect? or am I finding the wrong signal so to speak>?
Thanks
I'll gladly post all of my results or screen shots, (all failed so far) using ADB, uppercut, LGUP, odin, placing TOT files on the SD card, plus a few absolutely embarrassing methods but had to try something.
Please tell me someone knows a way out of this

Otherwise start a *.bat file containing
Code:
REG ADD HKLM\SYSTEM\CurrentControlSet\Control\UsbFlags\0BB40FF00100 /v SkipBOSDescriptorQuery /t REG_BINARY /d 01000000 /f
or use this in the Run window that you can call by pressing the Windows button and R, Win+R.

DEAD
Hi
Hope there's still anyone here that could help. I got the same error {The Fail Code is: Unknown USB device (Device Descriptor Request Failed) Windows has stopped this device because it has reported problems. (Code 43)} that appears on windows when watch is connected and i press the red button. I tried to get the identifier via device manager and microsoft message analyzer but it is not detected. What else can i do?
Thanks!

didnt work for the V40. anyone got any ideas?

SuperMike393 said:
didnt work for the V40. anyone got any ideas?
Click to expand...
Click to collapse
Have you tried going to device manager > universal bus controllers, right click USB Root Hub and unintall. Restart the PPC/Laptop and reconnect the device. It works on both Xiaomi and other brands as well.

[UNLOCK] Tuliptool: unlock, TWRP, and custom boot

First let's get the warnings out of the way:
This is a dangerous tool. It can render your device permanently unusable.
If you use it, your warranty will likely be void.
You accept all responsibility for the consequences.
This is not an official ZTE unlock tool. The official ZTE unlock tool is in another thread.
Acknowledgments
Special thanks to @rombdeta for providing the OEM programmer binary. This would not be possible without his help.
What is tuliptool?
This tool allows you to:
Check status of your boot loader
Unlock your boot loader
Lock your boot loader
Install a custom recovery
Install a custom boot image
NOTE WELL
The first rule of intelligent tinkering is to save all the parts.
Always backup your partitions before writing new contents, so that you can get back to where you started.
Never write both boot and recovery in one session. Always make sure that you can boot into the other partition in case something fails.
Locking and unlocking will erase all user data. Make sure you backup first!
The zip includes:
tuliptool for Linux
tuliptool for Win64
tuliptool for Win32
tuliptool for MacOS
Preparation
1. Extract the package.
You will find the binary files listed above. Note: This is a command line utility, so you must open a command prompt to run it.
2a. Setup for Linux
Create a file named /etc/udev/rules.d/99-qcom.rules with this content exactly as shown:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
Ensure your login user is in the plugdev group.
2b. Setup for Win32/Win64
Download zadig.
Connect your device in EDL mode (see below).
Windows will want to install the Qualcomm USB driver. We won't be using it so you can cancel if you wish, but it won't hurt anything.
Run zadig. Find device 05c6:9008 and install the WinUSB driver for it.
Disconnect the device.
2c. Setup for MacOS
No setup should be necessary.
3. Download boot and/or recovery files to flash.
You will find these in other threads in this section.
Connecting in EDL mode
Via adb
This should work for all models, but you need adb access.
adb reboot edl
Via key combo
If you have a US model device (or the aboot from a US model device) you may use the key combo:
Power off and unplug the device.
Hold both volume buttons.
Plug device into your PC.
Wait about 3 seconds and release the buttons.
Note: There will be no feedback on the device -- no lights, no vibration, nothing. The only way to verify that the device is in EDL mode is that device 05c6:9008 is visible on the PC.
Usage: (un)locking
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, unlocking seems to be completely unnecessary. This section is mostly provided for completeness.
tuliptool lock status
tuliptool lock unlock
tuliptool lock lock
Usage: reading boot/recovery
Note command line options have changed
tuliptool read boot
tuliptool read recovery
Usage: writing boot/recovery
Note command line options have changed
tuliptool write boot <filename>/I]
tuliptool write recovery <filename>
So, for example, to write a TWRP image, run:
tuliptool write recovery tulip-twrp-7.1-r1.img.
Multiple operations
This is a "one shot" tool. After performing an operation, it will reset the device with a 5 second countdown. If you wish do perform multiple operations (eg. backup, unlock, flash), simply hold down the volume buttons while the device resets and it should go back to EDL mode.
Download
tuliptool.zip
md5=58f34850005510b51a832d27a6bce607
Common problems
Device not found: first enter EDL mode, then run the tool.
Device is visible in device manager or lspci but cannot be found by the tool: connect directly to the PC, not through a hub.
Windows says bad file descriptor: the WinUSB driver is not installed.
Linux says permission denied: your login user is not in the plugdev group.
Why call it tuliptool?
Tulip is the device "code name" for the Axon 7 Mini (at least the US version).

first! it's nice to see someone working on the lesser-known devices for once, thanks love!
okay so on that note everything goes perfectly, right up until i try to actually run the tool lol. installing the driver through Zadig does fine, and from everything i can tell, the PC recognizes it. i mean, it's in EDL and everything. what's going wrong? running the tuliptool-win64.exe just opens and closes instantly, and opening a command prompt in the directory just tells me that tuliptool is not a valid command/operation blah blah blah. it's probably something simple but i'm kind of trying to get all over this so :good:

Perhaps try running it as administrator? I'm heading home from work and then I'll be taking a shot at this myself.

I just tried on a Windows 10 virtual machine and it works perfectly.
This is a commandline program so you open a command prompt and type eg:
tuliptool-win64.exe lock status
Meme Queen said:
first! it's nice to see someone working on the lesser-known devices for once, thanks love!
okay so on that note everything goes perfectly, right up until i try to actually run the tool lol. installing the driver through Zadig does fine, and from everything i can tell, the PC recognizes it. i mean, it's in EDL and everything. what's going wrong? running the tuliptool-win64.exe just opens and closes instantly, and opening a command prompt in the directory just tells me that tuliptool is not a valid command/operation blah blah blah. it's probably something simple but i'm kind of trying to get all over this so :good:
Click to expand...
Click to collapse

tdm said:
I just tried on a Windows 10 virtual machine and it works perfectly.
This is a commandline program so you open a command prompt and type eg:
tuliptool-win64.exe lock status
Click to expand...
Click to collapse
so it's gone past that, but now it fails to unlock with an unknown error. checking unlock status after returns "Failed to send programmer: failed to read packet". i have to unplug it and go back into EDL mode, and when i check the lock status, it says unlocked and not tampered. when i try to go ahead with flashing TWRP, it crashes with this:
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
terminate called after throwing an instance of 'std::runtime_error'
what(): No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

I guess im stuck waiting for the update.zip because Zadig is refusing to install drivers. no matter what i do it will not install drivers. it keeps telling me "Remote Source Not Allocated: Driver install Aborted"

Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Meme Queen said:
so it's gone past that, but now it fails to unlock with an unknown error. checking unlock status after returns "Failed to send programmer: failed to read packet". i have to unplug it and go back into EDL mode, and when i check the lock status, it says unlocked and not tampered. when i try to go ahead with flashing TWRP, it crashes with this:
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
terminate called after throwing an instance of 'std::runtime_error'
what(): No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Click to expand...
Click to collapse

tdm said:
Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Click to expand...
Click to collapse
thanks! if there's any information you want me to provide, just let me know.

I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?

pxzei said:
I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?
Click to expand...
Click to collapse
Yeah, try pressing the power button for 10 seconds, until the display turns off, hold down VOL + and enter recovery "power down" and try to enter edl again

Ok. Now ive retraced my steps and found that letting the qualcomm drivers install will not allow the WinUSB drivers to install in Windows 7. Once I told Windows update to not install the qualcomm drivers Zadig was able to install drivers successfully. Now that the drivers are installed, Device is in EDL (im assuming this because screen is black but my computer is recognizing the device), I run the Tuliptool and it keeps telling me "Device Not Detected" . I cant seem to get it to find the device but i can see it in Device Manager just fine. And it shows the WinUSB drivers are installed correctly, any insight on to what I may be doing wrong?

There won't be any lights or other indication that the phone is on when it's in EDL mode. But you should see the device in device manager, as USB id=05c6:9008. I don't normally run windows so I can't give detailed steps to find that.
You may need to have admin privileges to talk to USB devices, I'm not sure.
MrWhite0429 said:
Ok. Now ive retraced my steps and found that letting the qualcomm drivers install will not allow the WinUSB drivers to install in Windows 7. Once I told Windows update to not install the qualcomm drivers Zadig was able to install drivers successfully. Now that the drivers are installed, Device is in EDL (im assuming this because screen is black but my computer is recognizing the device), I run the Tuliptool and it keeps telling me "Device Not Detected" . I cant seem to get it to find the device but i can see it in Device Manager just fine. And it shows the WinUSB drivers are installed correctly, any insight on to what I may be doing wrong?
Click to expand...
Click to collapse

tdm said:
There won't be any lights or other indication that the phone is on when it's in EDL mode. But you should see the device in device manager, as USB id=05c6:9008. I don't normally run windows so I can't give detailed steps to find that.
You may need to have admin privileges to talk to USB devices, I'm not sure.
Click to expand...
Click to collapse
Device Shows connected and drivers installed under device manager.
Command prompt is being run as so:
Start --> type cmd ---> Right click on Command prompt ---> Run as Administrator
cd C:\users\admin\desktop\tuliptool
C:\users\admin\desktop\tuliptool> tuliptool-win64.exe lock status
Device Not Detected
---------- Post added at 03:59 AM ---------- Previous post was at 03:38 AM ----------
UPDATE:
I found that I had to use a USB 3.0 hub in order to get the phone to be detected.
Once detected I ran commands as followed.
tuliptool-win64.exe lock unlock
(The unlocking procedure said it failed, phone bootlooped three times, then it showed as unlocked when I ran the Lock status command)
tuliptool-win64.exe read boot
(This created the backup-boot.bin file in the directory)
Tuliptool-win64.exe read recovery
(This created a backup-recovery file in the directory)
tuliptool-win64.exe write boot
Its at this point here I get a Runtime Error as well. The entire process comes to a halt.

Thsnks, tried that, but no luck. It's still stuck on the splash screen.
Update: The device is running B09 7.1.1, The charger seems to be ZTE authentic. Single sim variant. If you need more info, let me know.
rombdeta said:
Yeah, try pressing the power button for 10 seconds, until the display turns off, hold down VOL + and enter recovery "power down" and try to enter edl again
Click to expand...
Click to collapse

tdm said:
This is not an official ZTE unlock tool. ZTE will likely be providing an official boot loader unlock in the coming few days. You should wait for that if you have any reservations about modifying your device.
[/B][/COLOR]
Click to expand...
Click to collapse
Awesome you got the tool out, I think I am going to wait for the 'Official' tool so if I ever need to send it in for repair in the next 2 years I can say 'well I used your tool' lol
Can't wait to see the roms @tdm, keep it up and I think the mini is going to get a lot more interesting.
I'd like to get a bloat removed(if any) and more lightweight faster rom on mine, maybe try the latest cyanogenmod or w/e they call it now and AOKP, etc.
New roms without MiFavor would be awesome too and ones that improve performance!

ZTE
@tdm, do you think zte will also be giving the official boot loader unlock soon? If not I will use yours that looks solid, but just thought I would ask first.

CRAFTER0302002 said:
@tdm, do you think zte will also be giving the official boot loader unlock soon? If not I will use yours that looks solid, but just thought I would ask first.
Click to expand...
Click to collapse
First post:
"This is not an official ZTE unlock tool. ZTE will likely be providing an official boot loader unlock in the coming few days. You should wait for that if you have any reservations about modifying your device."

Okay I've uploaded a new version of the tool with better error handling and better error messages (particularly for the Win64 version). I successfully wrote TWRP using the Win64 version. Please check the OP for the new link and download it again.
@Meme Queen and @MrWhite0429 please try again. I think the problem was that you didn't copy tulip-twrp-7.1.1.img to recovery.bin.
I can modify the tool to take a filename as a parameter if that helps with the confusion.
Edit: Also fixed a typo in the OP which had the wrong filename in the example. This may have been the source of the confusion.

tdm said:
Okay I've uploaded a new version of the tool with better error handling and better error messages (particularly for the Win64 version). I successfully wrote TWRP using the Win64 version. Please check the OP for the new link and download it again.
@Meme Queen and @MrWhite0429 please try again. I think the problem was that you didn't copy tulip-twrp-7.1.1.img to recovery.bin.
I can modify the tool to take a filename as a parameter if that helps with the confusion.
Edit: Also fixed a typo in the OP which had the wrong filename in the example. This may have been the source of the confusion.
Click to expand...
Click to collapse
as in rename to recovery.bin?

Yes, that.
MrWhite0429 said:
as in rename to recovery.bin?
Click to expand...
Click to collapse

How To Guide [CPH2239] How to Unlock Bootloader and Root the OPPO A54

DISCLAIMER​* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
​IMPORTANT:​This method works only upto c.20 patch.​
PRE REQUIREMENTS:​
Python 3.9 and Git (Please make sure to add Python and Git to PATH. An option to add them to PATH will be available in the installer)
mtk client (Get it from here)
SDK Platform tools (Get it from here)
Patience
USB debugging and OEM unlock should be enabled in developer options
LET'S BEGIN!​
STEPS:​1. Open Command Prompt in any location and type
git clone https://github.com/bkerler/mtkclient
cd mtkclient
pip3 install -r requirements.txt
2. Dump boot and vbmeta partitions by typing the below code
Spoiler: Show Code
python mtk r boot,vbmeta,vbmeta_system,vbmeta_vendor boot.img,vbmeta.img,vbmeta_system.img,vbmeta_vendor.img
Type the above code, then press Enter and insert the USB cable into your device by simultaneously pressing vol up and down buttons. If It doesn't work try again until it does
3. Patch the boot.img in Magisk manager and save the patched boot back to Platform tools folder and rename it to boot.img. Copy vbmeta,vbmeta_system and vbmeta_vendor as well to Platform tools folder
4. Unlock the Bootloader
Execute the below commands:
Spoiler: Show Code
python mtk e metadata,userdata,md_udc
python mtk da seccfg unlock
NOTE THAT AFTER EXECUTING EACH COMMANDS YOU MIGHT HAVE TO RECONNECT YOUR DEVICE. YOU CAN ALSO PERFORM THIS STEP USING THE MTK CLIENT GUI. FOR THAT FOLLOW THE BELOW STEPS
In a command prompt window opened in mtk client folder type
python mtk_gui
Once you are in the GUI connect your device by inserting usb cable and pressing vol up and down buttons simultaneously. Once the device is recognised few tabs will show up. Head over to the erase tab and Erase metadata, userdata and md_udc partitions. Then press the Unlock bootloader button.
Reboot the device now. You should see an orange state warning during start up.
5. Reboot back to fastboot
To do this open a command prompt window in Platform Tools folder and execute
Spoiler: Show code
adb reboot fastboot
6. Flash the patched boot.img and vbmeta
Move the patched boot.img, vbmeta_system and vbmeta_vendor to platform tools folder. Execute the below commands in a command prompt window opened in Platform tools folder
Spoiler: Show code
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
fastboot flash boot boot.img
fastboot reboot
THAT'S IT! NOW YOU SUCCESSFULLY HAVE ROOT IN YOUR OPPO A54​
Press the like button if this guide was useful to you!

Nice

John. P. John said:
Nice
Click to expand...
Click to collapse
Any plans to unlock?

Thank you for the guide, it's not easy but I will try in my A54 5G

Cni said:
Thank you for the guide, it's not easy but I will try in my A54 5G
Click to expand...
Click to collapse
Oppo A54 5G iirc has a Snapdragon. This method is for mediatek devices only.

does this work with the cph2211?
I cant get it to show up in the program.

ZipTies said:
does this work with the cph2211?
I cant get it to show up in the program.
Click to expand...
Click to collapse
What exactly is the issue. Most people miss the part about installing UsbDk driver. It's mentioned in mtkclient page

Johannj22 said:
What exactly is the issue. Most people miss the part about installing UsbDk driver. It's mentioned in mtkclient page
Click to expand...
Click to collapse
yep I got it working, completely missed the driver

ZipTies said:
yep I got it working, completely missed the driver
Click to expand...
Click to collapse
Nice. Also try it at your own risk cause some devices have their fastboot broken after unlocking

Johannj22 said:
Nice. Also try it at your own risk cause some devices have their fastboot broken after unlocking
Click to expand...
Click to collapse
Sir help me please send me tutorial step by step...

Deepjatt7 said:
Sir help me please send me tutorial step by step...
Click to expand...
Click to collapse
This thread itself is a step by step tutorial.

Sir can u send me video tutorial oppo a54 (CPH 2239)

This is the error i get.
C:\Windows\System32\mtkclient>python mtk r boot,vbmeta,vbmeta_system,vbmeta_vendor boot.img,vbmeta.img,vbmeta_system.img,vbmeta_vendor.img
MTK Flash/Exploit Client V1.55 (c) B.Kerler 2018-2022
usb_class
usb_class - [LIB]: ←[31mCouldn't get device configuration.←[0m
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Traceback (most recent call last):
File "C:\Windows\System32\mtkclient\mtk", line 698, in <module>
mtk = Main(args).run()
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_main.py", line 518, in run
mtk = da_handler.configure_da(mtk, preloader)
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_da_cmd.py", line 78, in configure_da
mtk.preloader.init()
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_preloader.py", line 160, in init
self.mtk.port.close()
File "C:\Windows\System32\mtkclient\mtkclient\Library\usblib.py", line 356, in close
time.sleep(2)
KeyboardInterrupt
^C
C:\Windows\System32\mtkclient>

ayyu3m said:
This is the error i get.
C:\Windows\System32\mtkclient>python mtk r boot,vbmeta,vbmeta_system,vbmeta_vendor boot.img,vbmeta.img,vbmeta_system.img,vbmeta_vendor.img
MTK Flash/Exploit Client V1.55 (c) B.Kerler 2018-2022
usb_class
usb_class - [LIB]: ←[31mCouldn't get device configuration.←[0m
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Traceback (most recent call last):
File "C:\Windows\System32\mtkclient\mtk", line 698, in <module>
mtk = Main(args).run()
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_main.py", line 518, in run
mtk = da_handler.configure_da(mtk, preloader)
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_da_cmd.py", line 78, in configure_da
mtk.preloader.init()
File "C:\Windows\System32\mtkclient\mtkclient\Library\mtk_preloader.py", line 160, in init
self.mtk.port.close()
File "C:\Windows\System32\mtkclient\mtkclient\Library\usblib.py", line 356, in close
time.sleep(2)
KeyboardInterrupt
^C
C:\Windows\System32\mtkclient>
Click to expand...
Click to collapse
Restart the device.. Power if off and try again. Make sure the UsbDK driver is installed

Also I recommend performing a downgrade before unlocking. Some users reported that the unlocking was not successful in Android 11

Okay, noob here.
I installed python 3.9.10
And GIT, i entered all commands and EVERYTHING worked until STEP 2.
This point is not really good explained, what does the "spoiler code" mean? Where do i enter this?
What exactly has to be done for STEP 2? "press enter and connect the device" press enter where? what?
If i enter this "phython could not be found bla bla, windows store".
But it worked before, doesnt matter if im in the mtkclient directory or not, same error.

Jayk0b said:
Okay, noob here.
I installed python 3.9.10
And GIT, i entered all commands and EVERYTHING worked until STEP 2.
This point is not really good explained, what does the "spoiler code" mean? Where do i enter this?
What exactly has to be done for STEP 2? "press enter and connect the device" press enter where? what?
If i enter this "phython could not be found bla bla, windows store".
But it worked before, doesnt matter if im in the mtkclient directory or not, same error.
Click to expand...
Click to collapse
In Step 2 you are just dumping boot and vbmeta partitions. If the command prompt says python could not be found.. it means Python wasn't added to PATH while installation. By "Press enter" I meant type the commands and press enter in the command prompt

Johannj22 said:
Also I recommend performing a downgrade before unlocking. Some users reported that the unlocking was not successful in Android 11
Click to expand...
Click to collapse
my oppo is currently in latest version a11 , also successfully done step 4 without any errors . after step 4 theres an warning while booting and it says dm verity corrupted. unsafe etc. i pressed power button once and it booted fine, but when i did step 5-6 it shows bootloader not unlock and wont flash. what do i do now? should i downgrade ? if so should i lockbootloader first then flash stock a10? thanks in advance

Android_0000017 said:
my oppo is currently in latest version a11 , also successfully done step 4 without any errors . after step 4 theres an warning while booting and it says dm verity corrupted. unsafe etc. i pressed power button once and it booted fine, but when i did step 5-6 it shows bootloader not unlock and wont flash. what do i do now? should i downgrade ? if so should i lockbootloader first then flash stock a10? thanks in advance
Click to expand...
Click to collapse
Yes this is the exact issue users had been reporting. You can get stock rom file from here. Use oppo-decrypt (here) and extract the .ofp file of stock firmware to some folder. Use bypass_utility (here) to disable security otherwise we can't flash the rom using sp flash tool. Once security disabled flash the firmware using sp flash tool. While flashing make sure "opporeserve2" is unticked.

Johannj22 said:
Yes this is the exact issue users had been reporting. You can get stock rom file from here. Use oppo-decrypt (here) and extract the .ofp file of stock firmware to some folder. Use bypass_utility (here) to disable security otherwise we can't flash the rom using sp flash tool. Once security disabled flash the firmware using sp flash tool. While flashing make sure "opporeserve2" is unticked.
Click to expand...
Click to collapse
thank you very much for your contribution/help, i successfully unlocked my bootloader and installed magisk with no problems.