Hello!
I need to downgrade Android 10 to Android 9 on my Oppo F11 Pro. I've flashed many roms till now on other devices. This one is a bit *cough*
I have the .ozip file of the Android 9 rom, need to flash.
Default recovery mode of ColorOS doesnt work ofc, doesnt support downgrading.
After converting .ozip to .zip and extracting the files, SP Flash Tool or such tools arent able to get the files somehow They dont load it up, even not the scatter files.
So I think I should first unlock the bootloader, which I've been trying to today.
Doing the "adb devices" doesnt list my device, guess I need the drivers.
Downloaded drivers but they are in .inf format, which Ive been unable to install (with my "search the internet and do it" ways.
"The inf file you selected does not support this method of installation". And thru administrator cmd, its Installation failed.
Im so confused with those drivers Idk which ones to install.
One driver I've pasted on hastebin as.. hastebin[dot]com/abopesexej.shell
Couls someone pls help me out? Im hitting the wall atm
Neon111 said:
Doing the "adb devices" doesnt list my device, guess I need the drivers.
Downloaded drivers but they are in .inf format, which Ive been unable to install (with my "search the internet and do it" ways.
"The inf file you selected does not support this method of installation". And thru administrator cmd, its Installation failed.
Im so confused with those drivers Idk which ones to install.
One driver I've pasted on hastebin as.. hastebin[dot]com/abopesexej.shell
Couls someone pls help me out? Im hitting the wall atm
Click to expand...
Click to collapse
Don't mix up USB-driver and ADB-driver and/or Fastboot-driver: totally different drivers.
A USB-driver is a file that allows an USB hardware device to communicate with the operating system of a computer. This driver is implemented in all operating systems by default.
ADB-driver and/or Fastboot-driver is a “bridge” for Android developers / hackers to work out bugs in their Android applications and/or modify existing Android OS. This is done by connecting an Android device that runs the software through a PC, and feeding appropriate commands in its terminal.
Don't use any ADB-driver and/or Fastboot-driver as they are hundreds of times published on the WEB - and even here on XDA. Only make use of those drivers officially offered by your device's OEM/Carrier.
Comment withdrawn by author.
(When "adb devices" shows the device serial)
When i try to do "adb reboot bootloader",
The phone reboots and says
"The serial is not matched
fastboot_unlock_verify fail"
What should I do? :u
And not being able to use fastboot.. I cant find related drivers on the internet for that purpose.. I downloaded and installed what I could (fastboot commands not working.. shows <waiting for device> )
Neon111 said:
(When "adb devices" shows the device serial)
When i try to do "adb reboot bootloader",
The phone reboots and says
"The serial is not matched
fastboot_unlock_verify fail"
What should I do? :u
Click to expand...
Click to collapse
Generally speaking, the serial number as reported by ADB will be different to Fastboot as determined by:
Manufacturer
Make and model of device in question
Android version
Fastboot, on the other hand, since there's no ADB loaded, instead, uses a rudimentary USB protocol tied in with Android's boot-loader, the serial number will be different.
EDIT:
Neon111 said:
And not being able to use fastboot.. I cant find related drivers on the internet for that purpose.. I downloaded and installed what I could (fastboot commands not working.. shows <waiting for device> )
Click to expand...
Click to collapse
Your Oppo F11 Pro is based on Mediatek chipset. IMO you instead of Fastboot driver have to make use of Oppo F11 Pro Mediatek driver - a specialized version of general Fastboot driver - what is compatible with SP Flash Tool, MTK Flash Tool, SP MDT Tool and SN Write Tool.
DL: https://gsmusbdriver.com/oppo-f11-pro
jwoegerbauer said:
Your Oppo F11 Pro is based on Mediatek chipset. IMO you instead of Fastboot driver have to make use of Oppo F11 Pro Mediatek driver - a specialized version of general Fastboot driver - what is compatible with SP Flash Tool, MTK Flash Tool, SP MDT Tool and SN Write Tool.
DL: https://gsmusbdriver.com/oppo-f11-pro
Click to expand...
Click to collapse
But I do not have flash files related to the listed programs..
Everywhere I could find only an .ozip file, which I turned into a .zip from a program I found on here. The zip when extracted gave me all the .img files and scatter.txt, but the scatter.txt doesnt load up in SP Flash Tool and the like.
Neon111 said:
But I do not have flash files related to the listed programs..
Everywhere I could find only an .ozip file, which I turned into a .zip from a program I found on here. The zip when extracted gave me all the .img files and scatter.txt, but the scatter.txt doesnt load up in SP Flash Tool and the like.
Click to expand...
Click to collapse
Were you able to unlock your bootloader? I found various tutorials of extracting boot image from the ozip files. But Veterans are saying oppo doesn't let people unlock bootloader.
So long story short , i flashed a ROM using mtk client and usbdk driver and now my device wont turn on , doesnt display corrupted rom or boot or anything like that , no fastboot no recovery and somehow i get the boot to boot into BROM mode , now problem is when i am injecting payload from mtk client using command " python mtk payload " the payload injection is done succesfully but problem comes when i execute the next command which is " python mtk_gui " it gets stuck on detecting phone 0x200000 and the mtk_gui menu just doesnt open it stays stuck there forever , in the command windows it says no preloader detected amd daxflash error. Any idea if anyone of you could help me with this one ?
Also drivers installed are OPPO mtk vcom 1668 driver and usbdk driver .
No idea how to use sp flash tool as there are no exact instructions for sp flash tools
I tried flashing many roms like govix and other roms but still the phones screen just stays black .
The Phone gets stuck on
Jumping to 0x200000 ok. in MTK GUI
in command console it says : No preloader given . Operation may fail due to no DRAM Setup .
Uploading Stage 2
DAXFlash
Error on sending data: DA hash mismatch
Error on booting to DA
Any help would be appreciated .
You should've flashed the TWRP through fastboot and then flash the ROM from there, I honestly don't know how you flashed it from MTK, but anyway...
Try using the live-distro which is on MTKClient's GitHub page; flash it into an USB and boot from it. Had no issues at all on it (mostly used the GUI version), compared to Windows.
Flash a version's stock firmware partitions (A.20 is overall the best), all of them except seccfg, persist, nvcfg, nvdata, nvram, protect1, protect2, which are device-specific partitions.
Here's Giovix's guide.
Hi guys sadly I completely softbricked my motorola X40 phone i'm a idiot.
I flashed to a wrong firmware file (edge 30 pro) and re-locked bootloader then found it phone doesn't properly boot anymore.
I can boot it in fastboot mode but flashing in normal fastboot mode doesn't work with locked bootloader and lenovo rescue tool can't help me either.
Edit: Weirdly I managed to boot it up and it shows as a "motorola edge 30 pro" and I can control my screen with a USB mouse.
But when I try to enable "OEM unlocking" in developer options the settings app just crashes.
But my problem stays the same, i'm still stuck with a locked bootloader
Is there any chance to trick this phone into EDL mode or any working blankflash?
Any suggestions? i'd appreciate it
jody2k said:
Hi guys sadly I completely softbricked my motorola X40 phone i'm a idiot.
I flashed to a wrong firmware file (edge 30 pro) and re-locked bootloader then found it phone doesn't properly boot anymore.
I can boot it in fastboot mode but flashing in normal fastboot mode doesn't work with locked bootloader and lenovo rescue tool can't help me either.
Edit: Weirdly I managed to boot it up and it shows as a "motorola edge 30 pro" and I can control my screen with a USB mouse.
But when I try to enable "OEM unlocking" in developer options the settings app just crashes.
But my problem stays the same, i'm still stuck with a locked bootloader
Is there any chance to trick this phone into EDL mode or any working blankflash?
Any suggestions? i'd appreciate it
Click to expand...
Click to collapse
It doesn't matter if the oem lock is on to flash the stock firmware.
You can directly flash the right firmware via fastboot. Lenovo rescue tool may not flash...
cascade128 said:
It doesn't matter if the oem lock is on to flash the stock firmware.
You can directly flash the right firmware via fastboot. Lenovo rescue tool may not flash...
Click to expand...
Click to collapse
Hi thanks for the response, how to flash directly stock firmware? which method should I use? This is what I get when I try to flash anything through adb (phone in fastboot mode) I added a screenshot from adb in windows and took a picture from my phone to show in which fastboot mode it shows.
Tried several things flashing directly from adb but it always says permission denied because of the bootloader lock, maybe i'm doing something wrong.
It's not adb, it's fastboot mode.
Where you are is right.
It will be in the mode in the screenshot of the device, that's right.
Use the one in the file i gave you.
Here are the guidelines.
01. Download the latest Firmware from lolinet
02. We extract the firmware.zip, open servicefile.xml and copy the contents into this website
03. Download the mfastboot.rar ADB i gave and put it in the rom folder you extracted.
04. We put the flashfile.bat we created (Step 02. Extract, open servicefile.xml and copy the content to this site) into the rom folder you extracted.
05. Reboot your phone into fastboot (adb reboot fastboot or press and hold Power + Volume Down)
06. Everything is ready, click on the ''flashfile.bat'' file.
07. Don't disconnect the phone until the update has finished.
cascade128 said:
It's not adb, it's fastboot mode.
Where you are is right.
It will be in the mode in the screenshot of the device, that's right.
Use the one in the file i gave you.
Here are the guidelines.
01. Download the latest Firmware from lolinet
02. We extract the firmware.zip, open servicefile.xml and copy the contents into this website
03. Download the mfastboot.rar ADB i gave and put it in the rom folder you extracted.
04. We put the flashfile.bat we created (Step 02. Extract, open servicefile.xml and copy the content to this site) into the rom folder you extracted.
05. Reboot your phone into fastboot (adb reboot fastboot or press and hold Power + Volume Down)
06. Everything is ready, click on the ''flashfile.bat'' file.
07. Don't disconnect the phone until the update has finished.
Click to expand...
Click to collapse
Hi thanks for helping me, I downloaded the right firmware, uploaded the servicefile.xml to the site you gave me and created the flashfile.bat. Pasted the flashfile.bat into the samen folder as the rom and also extracted the mfastboot.rar into the same rom folder.
Then clicked on the flashfile.bat but sadly I get the same error's (Permission Denied)
My phone is still in fastboot mode (right screenshot)
Any idea's?
jody2k said:
Hi thanks for helping me, I downloaded the right firmware, uploaded the servicefile.xml to the site you gave me and created the flashfile.bat. Pasted the flashfile.bat into the samen folder as the rom and also extracted the mfastboot.rar into the same rom folder.
Then clicked on the flashfile.bat but sadly I get the same error's (Permission Denied)
My phone is still in fastboot mode (right screenshot)
Any idea's?
Click to expand...
Click to collapse
Very interesting, it shouldn't give such an error. You are flashing Motorola signed images, you don't need the bootloader unlocked for this Sorry i can't be of more help, i hope you can recover your device...
cascade128 said:
Very interesting, it shouldn't give such an error. You are flashing Motorola signed images, you don't need the bootloader unlocked for this Sorry i can't be of more help, i hope you can recover your device...
Click to expand...
Click to collapse
Yea indeed well thanks anyway, my only hope left is a third party recovery tool that supports this phone in future.
I'll put the X40 in my closet until then and buy another new phone in the meanwhile don't have much of a choice lol.
Hello!
Did you try RSDLite tool to flash firmware?
thunderman75 said:
Hello!
Did you try RSDLite tool to flash firmware?
Click to expand...
Click to collapse
I tried but the issue is there that it doesn't detect the port / device on the RSDlite tool.
Meanwhile I can see in devicemanager in windows the phone is detected in ADB/fastboot mode but RSDlite tool needs some portmode to succeed, the tool says it doesn't detect my device. I can't seem to connect it with that port RSDlite tool needs, also tried general ADB drivers but didn't help either. I also saw in one topic to make it work with RSD tool you need to install the qualcomm drivers, but these drivers don't work with this phone in normal fastboot mode. In other words I can't seem to RSD tool recognise my phone on the needed port. I think this tool only works in EDL mode (+qualcomm driver) but my moto X40 doesn't yet support EDL mode I think.
https://androidmtk.com/use-rsd-lite-tool
=> I followwed this tutorial but @ Step nr.8 there isn't any port or device detected even when my phone is correctly in fastboot mode
I tried Generic ADB drivers and the official motorola USB drivers, both detected in devicemanager in windows but RSDtool lite didn't detect my phone.
jody2k said:
I tried but the issue is there that it doesn't detect the port / device on the RSDlite tool.
Meanwhile I can see in devicemanager in windows the phone is detected in ADB/fastboot mode but RSDlite tool needs some portmode to succeed, the tool says it doesn't detect my device. I can't seem to connect it with that port RSDlite tool needs, also tried general ADB drivers but didn't help either. I also saw in one topic to make it work with RSD tool you need to install the qualcomm drivers, but these drivers don't work fastboot mode. In other words I can't seem to RSD tool recognise my phone on the needed port. I think this tool only works in EDL mode (+qualcomm driver) but my moto X40 doesn't yet support EDL mode I think.
https://androidmtk.com/use-rsd-lite-tool
=> I followwed this tutorial but @ Step nr.8 there isn't any port or device detected even when my phone is correctly in fastboot mode
I tried Generic ADB drivers and the official motorola USB drivers, both detected in devicemanager in windows but RSDtool lite didn't detect my phone.
Click to expand...
Click to collapse
This looks promising:
Motorola Unbrick Tool: Unbrick any Moto Device via EDL Mode
In this comprehensive guide, we will show you the detailed steps to unbrick any Motorola device booted to EDL Mode using the Unbrick Tool.
droidwin.com
thunderman75 said:
This looks promising:
Motorola Unbrick Tool: Unbrick any Moto Device via EDL Mode
In this comprehensive guide, we will show you the detailed steps to unbrick any Motorola device booted to EDL Mode using the Unbrick Tool.
droidwin.com
Click to expand...
Click to collapse
Yeah let's hope my device model (X40) get's support soon
@mark332 Any idea's?
I have the same problem, because I did the same thing hahaha, I tried these methods and nothing was successful, I tried to use Lenovo's RSA, but it only installs the correct firmware and Fastboot, but when it comes to rescuing it just has a "Warning" message.
zequinhaBR said:
I have the same problem, because I did the same thing hahaha, I tried these methods and nothing was successful, I tried to use Lenovo's RSA, but it only installs the correct firmware and Fastboot, but when it comes to rescuing it just has a "Warning" message.View attachment 5872305
Click to expand...
Click to collapse
Guess we are in the same boat loll xp having indeed the exact same message. I think the RSA tool detects the right device but it checks for some sort of keys/verification and sees it isn't the right firmware so it stops flashing.
I have found out you can also enter recovery mode by selecting "recovery" in fastboot mode with the key buttons.
Then you need to press power button + down key for 3 seconds, then short the volume up key.
Youll get a other menu with also fastboot mode and adb sideload etc...
but again sadly neither fastboot or adb sideload did work for me
When I tried to flash the original firmware in sideload mode trough ADB it gives a"verification error"
In fastboot mode it says that it can't flash with locked device
I hope this info will be any useful for people stumble upon this topic in the future and maybe help to unbrick this phone.
jody2k said:
I tried but the issue is there that it doesn't detect the port / device on the RSDlite tool.
Meanwhile I can see in devicemanager in windows the phone is detected in ADB/fastboot mode but RSDlite tool needs some portmode to succeed, the tool says it doesn't detect my device. I can't seem to connect it with that port RSDlite tool needs, also tried general ADB drivers but didn't help either. I also saw in one topic to make it work with RSD tool you need to install the qualcomm drivers, but these drivers don't work with this phone in normal fastboot mode. In other words I can't seem to RSD tool recognise my phone on the needed port. I think this tool only works in EDL mode (+qualcomm driver) but my moto X40 doesn't yet support EDL mode I think.
https://androidmtk.com/use-rsd-lite-tool
=> I followwed this tutorial but @ Step nr.8 there isn't any port or device detected even when my phone is correctly in fastboot mode
I tried Generic ADB drivers and the official motorola USB drivers, both detected in devicemanager in windows but RSDtool lite didn't detect my phone.
Click to expand...
Click to collapse
New hope on horizont for your phone...Machine with Windows10(32-bit) and Moto USB drivers(32-bit).
Phone booted in fastboot mode and connected to PC,recognized instantly.
Screenshot of my Moto Edge 30 ultra connected to above mentioned PC.
Good luck!!!
thunderman75 said:
New hope on horizont for your phone...Machine with Windows10(32-bit) and Moto USB drivers(32-bit).
Phone booted in fastboot mode and connected to PC,recognized instantly.
Screenshot of my Moto Edge 30 ultra connected to above mentioned PC.
Good luck!!!
Click to expand...
Click to collapse
Hey man thanks for your response, sadly i'm on a 64bit windows 11 version. Would it be any different than the 64bit driver vs 32bit you think? Because have tried this several times can't get RSD lite detect my phone . In device manager it's detected first as "fastboot rtwo s" and when the moto 64bit driver is installed it's detected as "motorola ADB interface" so it's correctly detect by the system.
My phone is also in fastboot mode never the less RSD lite tool doesn't detect anything
Guess I could try to install windows 10 32bit i'll keep this updated
jody2k said:
Hey man thanks for your response, sadly i'm on a 64bit windows 11 version. Would it be any different than the 64bit driver from motorola you think? Because have tried this several times can't get RSD lite detect my phone . In device manager it's detected first as "fastboot rtwo s" and when the moto 64bit driver is installed it's detected as "motorola ADB interface" so it's correctly detect by the system.
Never the less RSD lite tool doesn't detect anything
On which mode is your edge 30 phone, fastboot or edl?
Click to expand...
Click to collapse
I also have 64 bit Win11 machine with RSD Lite installed and it can't detect phone.
But when I connect it to my old laptop(Win10-32 bit,RSD Lite) phone is detected instantly.
Try to find someone who has machine with 32 bit Windows and try to rescue your phone.
Tip from professionals: RSD Lite works best with older version of a 32 bit Windows...
thunderman75 said:
I also have 64 bit Win11 machine with RSD Lite installed and it can't detect phone.
But when I connect it to my old laptop(Win10-32 bit,RSD Lite) phone is detected instantly.
Try to find someone who has machine with 32 bit Windows and try to rescue your phone.
Tip from professionals: RSD Lite works best with older version of a 32 bit Windows...
Click to expand...
Click to collapse
Just tried on my older 32bit computer with windows 10 and installed the 32bit driver for motorola. Sadly the issue is the same, RSD lite doesn't detect the moto x40. Where did you download the driver?
Motorola USB Driver for Windows 32-Bit/64-Bit - Driver Market
Download now the latest and official Motorola USB Driver for Windows. We shared the latest Motorola USB Driver for Windows.
www.drivermarket.net
Reinstall driver and restart PC(mandatory),it should work then.
thunderman75 said:
Motorola USB Driver for Windows 32-Bit/64-Bit - Driver Market
Download now the latest and official Motorola USB Driver for Windows. We shared the latest Motorola USB Driver for Windows.
www.drivermarket.net
Reinstall driver and restart PC(mandatory),it should work then.
Click to expand...
Click to collapse
Tried that too several times but thanks for the suggestion anyways.
Took my time also this evening to reinstall a clean windows 32bit version, installed 32bit moto driver again from your link.
Reboot, nope
Same issue, RSD lite doesn't detect anything while the driver and device is recognized in device manager whatever I tried last 2 weeks.
I also opened the phone and searched on the motherboard for EDL test points, no avail too.
I think the RSD tool lite or the usb driver needs a update for this device or someone needs to find out how to get this phone into EDL mode. This can take months maybe years who knows lol
I just gave up and bought myself a new phone (xiaomi 13)