Database Info

OPPO A3s - user password removal

I have OPPO A3s need to remove user password somehow, even in recovery mode phone asking for locks creen password to factory reset or flash, phone goes in Emergency Download Mode (EDL) if open recovery, connect USB cable to PC and click on Build number 3 times.
So far i can think of two solutions:
1. Mount Filesystem (this guide) with Qualcomm Flash Image Loader (QFIL), phone is detected in QFIL as HS-USB QDLoader 9008 once in EDL mode, but then what, i dont have MBN file required to mount filesystem can someone help?
2. Flash stock firmware, i can download two, from official website in CPH1853_11_A.31.qzip which i can extract, but then what?
Other firmware is unofficial in Oppo_A3S_CPH1853_11_A.21.ofp format this cannot be flashed by any tool i know of, there is info online that OFP file can be converted to proper format for QFIL (with scatter file and xml) by software+usb dongle (Miracle Box, UFI Box), but they are not free.
P.S. I am noob please help.

Hello

hello , does anyone have oppo a3s download certificate, that the only thing standing between me and unlocking it

oppo with new security needs to open the phone made jtag or isp connection direct to cpu to erase pattern

touji said:
oppo with new security needs to open the phone made jtag or isp connection direct to cpu to erase pattern
Click to expand...
Click to collapse
why here is no loader for oppo A3s Like other QUALCOMM devices

OnePlus 7 Pro not detected by PC at all (only in EDL/MSM mode)

Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
Edit 2: I'm able to use USB OTG to connect to a flash drive. It's so weird that it won't establish a connection with my PC...
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez

This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse

Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
try cleaning out the port on the phone.

MrSteelX said:
try cleaning out the port on the phone.
Click to expand...
Click to collapse
Gave the port a good couple of blasts with compressed air, but still no luck. What's weird is that it gets picked up by my computer perfectly fine while in EDL mode. Thank you for the suggestion.

amirage said:
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Click to expand...
Click to collapse
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck

Terkitoez said:
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Click to expand...
Click to collapse
I have to wait for something in the usb to time out, then it will load. Often more than a minute.

Im having a similar issue, it seems like Win 10 is having issues with the drivers or something cuz I can see my phone on the PC but cant access the storage at all.

It's working now!
Apologies for the silence, but I was able to miraculously get the phone to finally show up in ADB and Fastboot. I'm not exactly sure what triggered the fix or the order of things I did to get it to show up, but I did multiple flashes of Android 9 through the MSMTool and reinstallations of the OnePlus Drivers and ADB drivers in different orders until it eventually showed up on my computer. I flashed latest OOS 10 after that, successfully unlocked the phone, installed TWRP, flashed persist.img (for OP7Pro) to be safe, and installed Havoc OS A10. Sensors and Warp Charging are back and working as they should be. Thank you all for the replies.

Oneplus 7 pro stuck in fastboot mode

I have a rooted Oneplus 7 pro with android 11, but it has been lagging a lot lately, so I thought I might just unroot it and see if it helps. But, I don't have any access to a windows pc, I have a Mac.. So, I went searching the internet for a tutorial but I couldn't find any for Mac, but many guys mentioned that it could be done via Magisk by just uninstalling it. After doing so, my phone is now booting into fastboot mode only, showing the following :
Fastboot Mode
Product_Name - msmnile
Variant - SDM UFS
Bootloader Version -
Basband Version -
Serial Number - ********
Secure Boot - yes
Device State - unlocked
I have downloaded a stock android 11 version for 7 pro on my Mac, so all I need is to flash it if it is possible.
It is the only phone that I have, so any help would be appreciated.

[YOU ARE AWESOME IF CAN DO THIS] bootloader/fastboot issue

I've just got Realme GT2 PRO (RMX3300) (China ROM) and I need to flash the global ROM on it. but with all of my knowledge and hours and days wasted trying to flash the global ROM I am still unable to.
my main problem is that the phone doesn't have fastboot or bootloader !!!, I honestly never seen a phone that doesn't have a bootloader, and accessing it is necessary to flash a ROM or Unlocking the bootloader
here are some of the things i tried:
1- turning off the phone then holding the VOLUME DOWN and POWER BUTTON (AS SHOWN IN THE PICTURE) only puts me in recovery mode
2- using commands such adb reboot bootloader just restart the phone and shows a weird Chinese text for a split second (AS SHOWN IN THE VIDEO)
3- tried installing DEEP TESTING app but it gives me this error (AS SHOWN IN THE PICTURE)
I am honestly very desperate at this point and I am willing to pay anyone who manages to fix this issue
Tl;dr : can't go into bootloader/fastboot

Mr.pizza said:
my main problem is that the phone doesn't have fastboot or bootloader !!!, I honestly never seen a phone that doesn't have a bootloader, and accessing it is necessary to flash a ROM or Unlocking the bootloader
Click to expand...
Click to collapse
Each computer so also every Android phone ( regardless of brand / model ) has a bootloader. Whether Google's Fastboot tool is supported or not on Android phone depends on brand / model: e.g. Samsung does NOT support it whereas Realme does.

See also here:
How to Unlock Bootloader of Realme GT2 Pro? – (Easy Method)
Do you want to Unlock the Bootloader of Realme GT2 Pro? We have shared the Easiest Method.
androidcatch.com

[SOLVED][Cubot kingkong mini 3] Boot looping, no recovery, can't power off

Hi folks,
I bought a Cubot kingkong mini 3. It device has the new A/B partition system.
I tried to root and install TWRP, running these commands:
Bash:
fastboot flashing unlock
fastboot.exe flash recovery .\331 king kong mini\recovery_TWRP.img
fastboot.exe flash vbmeta .\vbmeta.img
fastboot.exe boot .\331 king kong mini\recovery_TWRP.img
After it, the smartphone started to reboot looping, it show the cubot logo and restart and show the cubot logo again and restart, repetitively.
My hope is a factory reset, but I have a lot of problems to be able to run the SP Flash Tool (mediatek), because the restart loop does not offer time to usb stay connected enough time.
There is other factors:
- The power+vol down command (recovery screen) not worked (appear as I pressed nothing).
- Hold the power by 8 segs to force restart not work (the phone restarts automatically before that time)
- I empty the battery and started the phone with usb connected and pressing power+volume down (not work too, the phone keeping restarting)
- I ask for some local android technicians, no one could help me (because they don't know the manufacturer)
I'm calling the cubot by assistance (no hope that they will solve my problem)
Any one of you already pass through some similar problem? There is some way to be able to reinstall all and save the phone yet? I'm opened to suggestions here.
best regards
UPDATE: It is the same case that happened with the Realme 7 in this thread. No one could solve the problem there too...

To anyone that are finding a way to solve this problem, follow this thread.

I would reccommend to wait for some days and use the flashtool (without format!!!), which is linked to your mini3 (beforehand I would recommend the linked driver from the cubot page) along with the most recent adb from
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com

barenko said:
and started the phone with usb connected
Click to expand...
Click to collapse
1. start sp-flashtool
2. plug-in usb (mobile switched off!)

you must first deactivate encryption
from
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
after that you can flash TWRP.... but this is not help, because you can not flash a nother rom, because all new Androids Systems have a SUPER.IMG not a system.img
you can rescue your phone with the offical Cubot Firmware and Flashtool!
CUBOT FILE DOWNLOAD
Cubot Offical Website for Smartphones and Wearables. Simple and Trust, Cubot aims to be a credit worthy high-tech corporation in the world.
www.cubot.net