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.
Related
Acer Predator 8 GT-810 system\etc backup please!
Make a backup folder etc
Do you still need it? I can send it you tomorrow or something like that.
p8tgames said:
Do you still need it? I can send it you tomorrow or something like that.
Click to expand...
Click to collapse
hey man if u able to send me a back up. Will that solve my problem ?
I made mistake to wipe everything in my phone and now i dont have OS ( i cant start my phone) i can only enter TWRP and thats all. i can use pc to transfer files to my phone and then install the files from there , so i wonder if any1 send me back up will that save me ???
i cand find anywhere OS for acer predator gt 810
there is official avolo zip on acers' page. flash that zip and you're safe
Flash archive corrupted
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware.
dvijetrecine said:
there is official avolo zip on acers' page. flash that zip and you're safe
Click to expand...
Click to collapse
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware
Alex_merser54 said:
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware
Click to expand...
Click to collapse
Use fastboot to flash the stock ROM instead of Intel flash tool. (If you know what you're doing, just read the part in blue below.)
fastboot is for Android devices, whether they have Qualcomm or Intel processors. Using Intel Flash tool is more akin to using Qualcomm's QPST for flashing, which is also something that should only be attempted
after trying fastboot. The Intel flash tool expects the .zip file to be in a format such as a Chuwi ROM with Windows is. Intel Flash tool unfortunately doesn't expect the .zip to be in the Android format like Acer's stock
ROM "AV0L0-something.zip" is.
With the tablet off, and plugged into your computer, hold both volume buttons and power it on. (You probably already knew this step, but here just in case )
It will vibrate longer than it usually does when turning on.
The screen should indicate that the device is in download, or "dnx" mode.
Open a command prompt in administrator mode,(the title of the window should say "Administrator: Windows Command Prompt" or "Administrator: <current directory>")
Type:
Code:
fastboot
If command not found, then either copy fastboot.exe into System32, or add the path it is in to your PATH variable, or simply navigate to its directory within the command prompt.
If you're not familiar with the PATH variable, you can just shift+right-click on fastboot.exe, click "Copy Path" and then paste it into the command prompt to use it's full path in place of simply "fastboot".
Once you're able to type "fastboot" or paste the full path and press enter and it returns the fastboot help message, type:
Code:
fastboot devices
this will either return a single line containing your device's serial number, or it will return nothing at all
If you see a serial number, you're in business.
(make sure the tablet is not low on battery before you continue):
Type:
fastboot update <path to ROM .zip>
Click to expand...
Click to collapse
This should initiate a full reflashing of the stock ROM. The tablet will reboot a couple times, you should hear/feel an even longer vibration during the process, do not touch it or unplug it from the computer until it is at the initial Google device setup screen waiting for your input.
Note that this full reflashing will also overwrite TWRP with the stock recovery.
if "fastboot devices" returns nothing at all, and also doesn't say "command not found" then do the following:
open device manager on computer, find the tablet's driver (may be under portable devices, or COM ports. sometimes under USB.)
if you can't find it, look for an "unknown device" with a yellow exclamation mark on it. If you see that, then you may not have had the driver installed in the first place. To verify, unplug the tablet from the computer
and see if the unknown device disappears from device manager.
If you were able to find the tablet in device manager, then right click and "Uninstall Device" and be sure to check the box to uninstall the driver software as well before clicking OK.
Then, unplug the tablet from your computer if you haven't already.
Download the latest driver from the same place on Acer's website that you downloaded the stock ROM from. Install the driver and restart your computer if it says it needs to.
Afterward, ensure the tablet is off and try the steps above again.
biorpg said:
Use fastboot to flash the stock ROM instead of Intel flash tool. (If you know what you're doing, just read the part in blue below.)
fastboot is for Android devices, whether they have Qualcomm or Intel processors. Using Intel Flash tool is more akin to using Qualcomm's QPST for flashing, which is also something that should only be attempted
after trying fastboot. The Intel flash tool expects the .zip file to be in a format such as a Chuwi ROM with Windows is. Intel Flash tool unfortunately doesn't expect the .zip to be in the Android format like Acer's stock
ROM "AV0L0-something.zip" is.
With the tablet off, and plugged into your computer, hold both volume buttons and power it on. (You probably already knew this step, but here just in case )
It will vibrate longer than it usually does when turning on.
The screen should indicate that the device is in download, or "dnx" mode.
Open a command prompt in administrator mode,(the title of the window should say "Administrator: Windows Command Prompt" or "Administrator: <current directory>")
Type:
If command not found, then either copy fastboot.exe into System32, or add the path it is in to your PATH variable, or simply navigate to its directory within the command prompt.
If you're not familiar with the PATH variable, you can just shift+right-click on fastboot.exe, click "Copy Path" and then paste it into the command prompt to use it's full path in place of simply "fastboot".
Once you're able to type "fastboot" or paste the full path and press enter and it returns the fastboot help message, type:
this will either return a single line containing your device's serial number, or it will return nothing at all
If you see a serial number, you're in business.
(make sure the tablet is not low on battery before you continue):
Type:
This should initiate a full reflashing of the stock ROM. The tablet will reboot a couple times, you should hear/feel an even longer vibration during the process, do not touch it or unplug it from the computer until it is at the initial Google device setup screen waiting for your input.
Note that this full reflashing will also overwrite TWRP with the stock recovery.
if "fastboot devices" returns nothing at all, and also doesn't say "command not found" then do the following:
open device manager on computer, find the tablet's driver (may be under portable devices, or COM ports. sometimes under USB.)
if you can't find it, look for an "unknown device" with a yellow exclamation mark on it. If you see that, then you may not have had the driver installed in the first place. To verify, unplug the tablet from the computer
and see if the unknown device disappears from device manager.
If you were able to find the tablet in device manager, then right click and "Uninstall Device" and be sure to check the box to uninstall the driver software as well before clicking OK.
Then, unplug the tablet from your computer if you haven't already.
Download the latest driver from the same place on Acer's website that you downloaded the stock ROM from. Install the driver and restart your computer if it says it needs to.
Afterward, ensure the tablet is off and try the steps above again.
Click to expand...
Click to collapse
Thank you, but I just entered EFI and load android.efi file, also I autorun it and reflash via recovery
Hello friends,
I am following this guide here to try to root my WP7:
http://androidbiits.com/root-oukitel-wp1-wp2-wp7-easily/
Everything works fine, except for the very last step, when I am supposed to flash the patched .img.
I issue the command
fastboot flash boot magisk_patched.img
and all I am getting is "Waiting for device".
The screen remains in "FASTBOOT mode..." and nothing else happens.
What am I doing wrong? I would appreciate some help, please.
Thank you.
Did you use the MTK USB-drivers?
jwoegerbauer said:
Did you use the MTK USB-drivers?
Click to expand...
Click to collapse
Hi, thanks for the reply. I already have the MTK USB_All_v1.0.8 driver installed as my previous phone was also MKT based.
I can see Windows installing different types of drivers when i connect my phone, so I assumed I was alright.
Perhaps you or anyone else can link for me the correct MKT USB drivers to use? Googling I found different links that seem to be different.
I also tried adb from my Mac too, same result: nothing seems to happen.
Thanks!
@fabioganga
For phones with Mediatek MT65xx chips it exists the so-called Mediatek MT65xx USB VCOM driver which claims that fastboot problems no longer occur.
Look inside here.
jwoegerbauer said:
@fabioganga
For phones with Mediatek MT65xx chips it exists the so-called Mediatek MT65xx USB VCOM driver which claims that fastboot problems no longer occur.
Look inside here.
Click to expand...
Click to collapse
Thanks @jwoegerbauer for the quick reply, much appreciated. As far as I ma maware the processor is a 6779, but the page refers to MT65xx drivers. Are they the same drivers?
No joy at all with Windows, not even with the drivers the article mentioned features.
I tried again with my Mac instead, installing adbd and fastboot there.
I am finally getting the phone to respond,
howver, the bootlaoader in my case was unlocked, so I first had to type
fastboot flashing unlock (warning! it deletes all data!) and confirm it with volume UP.
Then, after the device reboots to fastboot, I can finally type
fastboot flash boot magisk_patched.img
and it flashes correctly.
After updating to latest update, now the phone only shows background with either the "LOCKED" or "UNLOCKED" icon on the top and is constantly flickers on/off every second.
No response on the touchscreen either.
Attached video
Am currently downloading a stock rom (https://www.mediafire.com/file/bu4s...21062302340000_%28Mobileguru4.com%29.zip/file).
In the meantime, I installed the drivers for realme and the Realme Flashtool. Plugged in the phone to the PC using the cable however, the device is not recognized by the Realme Flashtool software, or is not "detecting" the phone.
(The driver I installed was this: https://www.mediafire.com/file/d3xf...river_Setup_V2.0.1.1_MobileGuru4.com.zip/file)
I have a guess on what it might be that's causing it (inside the developer settings option, sensors option). Not sure how to turn that **** off without being able to access the phone.
Scorpionish said:
Am currently downloading a stock rom (https://www.mediafire.com/file/bu4sjesfikq74dg/RMX2085_RMX2086export_11_C.07_2021062302340000_%28Mobileguru4.com%29.zip/file).
In the meantime, I installed the drivers for realme and the Realme Flashtool. Plugged in the phone to the PC using the cable however, the device is not recognized by the Realme Flashtool software, or is not "detecting" the phone.
(The driver I installed was this: https://www.mediafire.com/file/d3xf...river_Setup_V2.0.1.1_MobileGuru4.com.zip/file)
Click to expand...
Click to collapse
Download Driver Booster app (free version), run in and find Android drivers option and install. It will clear most of the driver issues.
Realme Flashing tool is not working and no other flashing tool worked forme, only fastboot method is worked good
Llatest stock images not having partitions of System and Vendor, they may be userdata and others.
Install "Minimal ADB Fastboot" and then download latest Stock OFP file.
Erase Data, if possible flash OrngeFox / custom recovery and format the phone.
Download this OFP to Scatter format (Link: https://softwarerom.blogspot.com/2021/03/ofp-file-cmd-converter-ofp-file-extract.html) and unzip it
Copy Latest Stock OFP to this folder and Just push the OFP to Qualcomm... Exe file, it will open a command prompt and create a folder contains some files & folder including Images,
Copy all the image files to Minimal ADB Fastboot folder, open Minimal ADB fastboot command prompt and copy all the images like, recovery, boot, vbmeta, userdata and so on using "Fastboot Flash Name Name.img" commands and reboot.
It worked for me.
The problem has reoccurred, exact same problem issue (browsing playstore, exited, closed phone, a moment later after opening up the phone) same thing happened, screen just flickering on&off.
I dont get how such problem could occur, now am certain its not the (sensor thing) cus this time (after PHONE WIPE) I did not play with any of those settings or (dev settings).
Honestly, if any1 experienced this, or might have a clue whats causing it.
[email protected] said:
Download Driver Booster app (free version), run in and find Android drivers option and install. It will clear most of the driver issues.
Click to expand...
Click to collapse
Its not a drivers issue, was able to plug in phone after having wiped the phone data (a complete reset), but did reinstall just incase, thx.
Also, I dont see how that fixes the issue (its a stock firmware)
Phone was working just fine after hard reset/wipe.. for a few months that is.
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)
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Hi, did you manage to solve this problem?
What have you tried with mtk client?
hi, I still haven't solved the problem. In mtkclent, I tried to flash the "boot.img" file through brom mode
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Tria13 said:
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Click to expand...
Click to collapse
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
I have the same device and I bricked it a while ago by flashing twrp and booting to recovery
From my understanding edl flashing can only be done with an authorized xiaomi account. I don't have one so I had to pay someone on telegram who had one and who could unbrick it. He used a modified version of SP Flash Tool. Although he struggled a bit he got it fixed the next day after I downgraded to windows 10. If you want to avoid bricking this device I recommend you don't use twrp altogether or be very cautious and only use twrp builds from the official telegram group. Compatibility depends on the kernel and android version. For now aosp-based roms have issues with the gpu anyways. (always under 100% load)
Also there is a mtk bootprotect magisk module which might help. (I don't think it will if you flash wrong twrp tho)
I hope these informations are somewhat useful
WolfnHex said:
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Click to expand...
Click to collapse
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
The thing is ---- Auth bypass is not yet available for your chipset type MT6895.
We have to wait until we can bypass auth to flash using SP Flash tool.
Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
im sorry to hear this
mvikrant97 is right. MT6895 is currently unsupported. you just have to wait
mvikrant97 said:
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
Click to expand...
Click to collapse
Hi, sorry I didn't see your post earlier. Can you solve your phone problem with an authorized Xiaomi Server? You can write your telegram or something else by which I can write to you. Thanks for the answer