Related
i try to flash pixel experience, the developer guide to flash firmware+vender zip after flashing the ROM zip, as per the guide I flash the ROM ZIP and firmware zip, after flashing the firmware, mobile rebooted and nothing to show in display. so i try to force boot in to recovery. the screen nothing to show. so i try to boot on fastboot. still nothing to show in mobile screen even the fastboot logo. i connect my mobile to computer, and i noticed the HS-USB QDLoader 9008 driver was installed. so guess it was in EDL mode, then try to flash the stock ROM using MI flash tool And get the error " cannot receive hello pocket." "object reference not set to an instance of an object " so i try to flash using QFIL , still not get any improvement, so kindly guide any possible to unbrick my phone.
Hey there I'm kinda having the same problem, any progress on your end ? I waited a few days for the battery to die and then connected to MiFlash but it keeps asking for an EDL authorized account, which is apparently a rarity. Exploring other options such as bypassing EDL authorization, long shot but what could be worse eh ...
freeze1994 said:
Exploring other options such as bypassing EDL authorization, long shot but what could be worse eh ...
Click to expand...
Click to collapse
Could you solve the problem? I have the same problem. Did you find information or a method to bypass EDL authentication?
Anandkrish40 said:
i try to flash pixel experience, the developer guide to flash firmware+vender zip after flashing the ROM zip, as per the guide I flash the ROM ZIP and firmware zip, after flashing the firmware, mobile rebooted and nothing to show in display. so i try to force boot in to recovery. the screen nothing to show. so i try to boot on fastboot. still nothing to show in mobile screen even the fastboot logo. i connect my mobile to computer, and i noticed the HS-USB QDLoader 9008 driver was installed. so guess it was in EDL mode, then try to flash the stock ROM using MI flash tool And get the error " cannot receive hello pocket." "object reference not set to an instance of an object " so i try to flash using QFIL , still not get any improvement, so kindly guide any possible to unbrick my phone.
Click to expand...
Click to collapse
got any solution? same thing happened to me too, help please
help I have the same error, any solution?
Syden! said:
help I have the same error, any solution?
Click to expand...
Click to collapse
What version of mi flash are you using? If it is the one from 2017 then it will not work as it isn't compatible with EDL.
Update miflash to latest or at least 2018 version to use EDL mode
My Mi A3 was hard bricked and unbricked it using Mi flash tool , again after a few months in got bricked , I unbricked it again but this time I guess I somehow locked the bootloader , Now my device is bricked again , it's not responding not even charging , I set it in edl mode and tried to flash rom using mi flash tool , but this time the mi flash tool is showing me error "write time out , device may be disconnected"
Have you googled the error message "write time out , device may be disconnected"? There are a few suggestions.
bjlabuk said:
Have you googled the error message "write time out , device may be disconnected"? There are a few suggestions.
Click to expand...
Click to collapse
Yes mate , i tried everything searching on Google , can you please help me mate
I haven't experienced your problem. Could the message relate to the EDL connection? I found this link https://www.droidwin.com/unbrick-xiaomi-fix-device-stuck-in-edl-mode-via-qfil-tool/
So (i) when you used Mi Flash Tool did you use 'clean all' or 'clean all and lock'? - that might explain the locked bootloader. (ii) Did you check in Device Manager as per the link I have given? (iii) have you tried the patched firehose file method, as per https://www.droidwin.com/unbrick-mi-a3-fastboot-commands/ ?
Can't suggest anything else other than a repair shop where someone with more experience might be able to sort it.
bjlabuk said:
I haven't experienced your problem. Could the message relate to the EDL connection? I found this link https://www.droidwin.com/unbrick-xiaomi-fix-device-stuck-in-edl-mode-via-qfil-tool/
So (i) when you used Mi Flash Tool did you use 'clean all' or 'clean all and lock'? - that might explain the locked bootloader. (ii) Did you check in Device Manager as per the link I have given? (iii) have you tried the patched firehose file method, as per https://www.droidwin.com/unbrick-mi-a3-fastboot-commands/ ?
Can't suggest anything else other than a repair shop where someone with more experience might be able to sort it.
Click to expand...
Click to collapse
Thanks mate for your assistance , i guess last time i flash the device i mistakenly use " clean all and lock"
The device is in edl mode as the port is recognised in the device manager and yes i tried the patched firehose , got the same error "write time out may be device was disconnected"
Okay, how about trying to get out of EDL mode? https://www.droidwin.com/how-to-exit-edl-mode-in-android/ Can you do that?
If you can get out of EDL mode then try flashing the STOCK ROM using the platform-tools, not Mi Flash Tool! https://www.thecustomdroid.com/xiao...2a11363abaea7ed177f9037d4693fae#comment-33230
You will get the latest fastboot images here https://xiaomifirmwareupdater.com/miui/laurel/
bjlabuk said:
Okay, how about trying to get out of EDL mode? https://www.droidwin.com/how-to-exit-edl-mode-in-android/ Can you do that?
If you can get out of EDL mode then try flashing the STOCK ROM using the platform-tools, not Mi Flash Tool! https://www.thecustomdroid.com/xiao...2a11363abaea7ed177f9037d4693fae#comment-33230
You will get the latest fastboot images here https://xiaomifirmwareupdater.com/miui/laurel/
Click to expand...
Click to collapse
My Device is hardbrick so I guess doing it using platform tools won't work
Pyro556 said:
My Device is hardbrick so I guess doing it using platform tools won't work
Click to expand...
Click to collapse
Okay, if it is stuck in EDL mode the only think I can think of is to try using QFIL but you will need to search for the stock firmware for your device in 'Flat Build format' - see attached link and instructions https://www.droidwin.com/unbrick-xiaomi-fix-device-stuck-in-edl-mode-via-qfil-tool/
I have successfully unbricked a Wileyfox Swift 2 recently using the QFIL method.
I did try the qflash , it shows
download fail firehose fail fhloader fail process fail
Are you using QFIL from within QPST? https://forum.hovatek.com/thread-30141.html
Also download the Engineering ROM from here. It has the firehose file. https://mifirm.net/downloadfile/66
You're leaving it in edl too long. Hold down the power button for a full 30 seconds. Seriously, count. Now, hold vol up and down for the same. Attach the cable. Release volume buttons. Now, you are freshly in edl. It should work. If you go QFIL, you will need to do this in between each patch.
Check out this link on Sahara: https://www.droidwin.com/fix-sahara-fail-qsaharaserver-fail-process-fail-error-qfil-tool/
Also, you mind posting your patched programmer file? Been having trouble with that.
Eliliyah said:
Also, you mind posting your patched programmer file? Been having trouble with that.
Click to expand...
Click to collapse
Who are you asking? Not sure which file you are referring to?
bjlabuk said:
Are you using QFIL from within QPST? https://forum.hovatek.com/thread-30141.html
Also download the Engineering ROM from here. It has the firehose file. https://mifirm.net/downloadfile/66
Click to expand...
Click to collapse
i will try using this rom let's see
Hello everyone, I have problems after updating Oxygen OS 12, my system stopped starting, more precisely, a cyclic reboot
There were attempts to enter the bootlocker but it does not start
And the Brom mode through mtkclient gives an error - hardshake failed
What other ways are there to restore the device to me very urgently
Sorry for the wrong translation, I used google translate
Have you tried Volume Down + Power button for fastbootd? I suggest you keep trying to connect with mtkclient, check the drivers or as a last resort try to use the bootable livedvd provided on the mtkclient github page.
Coconut_cube said:
Have you tried Volume Down + Power button for fastbootd? I suggest you keep trying to connect with mtkclient, check the drivers or as a last resort try to use the bootable livedvd provided on the mtkclient github page.
Click to expand...
Click to collapse
Tried it doesn't work the same gave out hardshake failed in liunx livedvd
SashaPalamaryuk said:
Tried it doesn't work the same gave out hardshake failed in liunx livedvd
Click to expand...
Click to collapse
Chances are high that your device is truly hardbricked. BROM mode was disabled with the OOS12 preloader and fastboot doesn't work. Did you update through stock recovery with locked bootloader or did you do it differently?
You can try asking in the official TG group @OnePlusNord2GlobalOfficial. Maybe somebody will have an answer.
Coconut_cube said:
Chances are high that your device is truly hardbricked. BROM mode was disabled with the OOS12 preloader and fastboot doesn't work. Did you update through stock recovery with locked bootloader or did you do it differently?
You can try asking in the official TG group @OnePlusNord2GlobalOfficial. Maybe somebody will have an answer.un
Click to expand...
Click to collapse
unlocked bootloader via TWRP
SashaPalamaryuk said:
unlocked bootloader via TWRP
Click to expand...
Click to collapse
Unfortunately, updating through TWRP is known to brick this phone. Your preloader (which is responsible for booting into BROM mode) got corrupted. I've heard that some people have had success with SP Flash Tool instead but use it at your own risk. Servicing the phone would be your best option if possible.
Coconut_cube said:
Unfortunately, updating through TWRP is known to brick this phone. Your preloader (which is responsible for booting into BROM mode) got corrupted. I've heard that some people have had success with SP Flash Tool instead but use it at your own risk. Servicing the phone would be your best option if possible.
Click to expand...
Click to collapse
Maybe somehow through a test point
SashaPalamaryuk said:
Maybe somehow through a test point
Click to expand...
Click to collapse
Unfortunately not, the button combination has the same effect as test point (I discussed it with a dev in another thread). The only way to get BROM mode now is to short the CLK pin on the UFS flash chip (whose location is currently unknown) to ground but that requires expertise otherwise further damage can be done.
I'm on OOS 12 and I can use mtkclient in Brom mode no issues.
It's annoying to use on Windows but on Linux there's no need for specific drivers. On Arch specifically and have to sudo to use it but hey whatever.
That said and I'm sorry if that's gonna sound condescending but have you tried different cables and ports on your computer . It could be just that
SP Flash Tool
Coconut_cube said:
Unfortunately, updating through TWRP is known to brick this phone. Your preloader (which is responsible for booting into BROM mode) got corrupted. I've heard that some people have had success with SP Flash Tool instead but use it at your own risk. Servicing the phone would be your best option if possible.
Click to expand...
Click to collapse
You need to bypass DA authentication with mtk-bypass. It can be found on GitHub. You also need to download the payload exploits collection provided there and extract it into the mtk-bypass folder. Then run mtk-bypass, connect USB to phone while holding button combination and run SP Flash Tool when done. This is a more detailed video, see if it works for you.
Coconut_cube said:
You need to bypass DA authentication with mtk-bypass. It can be found on GitHub. You also need to download the payload exploits collection provided there and extract it into the mtk-bypass folder. Then run mtk-bypass, connect USB to phone while holding button combination and run SP Flash Tool when done. This is a more detailed video, see if it works for you.
Click to expand...
Click to collapse
wait for next update!
Donaldmagee said:
wait for next update!
Click to expand...
Click to collapse
What?
Try using SP Flash Tool after you disable auth with that application. If it doesn't work, CM2 MT2 is the only other tool I've heard which people have had success with by enabling the Force BROM option.
File available for dead repair with imei+baseband remind me on monday
Mr Hassan said:
File available for dead repair with imei+baseband remind me on monday
Click to expand...
Click to collapse
i need that file my nord 2 imei null and fingerprint not work please reply
Coconut_cube said:
You need to bypass DA authentication with mtk-bypass. It can be found on GitHub. You also need to download the payload exploits collection provided there and extract it into the mtk-bypass folder. Then run mtk-bypass, connect USB to phone while holding button combination and run SP Flash Tool when done. This is a more detailed video, see if it works for you.
Click to expand...
Click to collapse
Where to download SP Flash Tool?
Thank you!
roldev said:
Where to download SP Flash Tool?
Thank you!
Click to expand...
Click to collapse
you can get it from here
hi, i recently tried flashing the stock rom for rosemare_redmi note 10s) But after the flash it wont turn on, blank screen, no recovery, no fastboot only brom mode is left, so i was wondering if there is a way to unbrick it.
I am facing the same problem. No fastboot, no recover, only a redmi log and repeat.
I do not know what to do. If you found the solution, please share
NikolaTechGuy said:
hi, i recently tried flashing the stock rom for rosemare_redmi note 10s) But after the flash it wont turn on, blank screen, no recovery, no fastboot only brom mode is left, so i was wondering if there is a way to unbrick it.
Click to expand...
Click to collapse
tutorial to fix your device
Redmi Note 10S - Flashing with SP Flash Tool in BROM mode.
Required Softwares [DOWNLOAD LINK] 1. MTK Drivers 2. LIB USB FILTER 3. MTK Auth Bypass Utility V43 or use Android Utility V109 if MTK Auth Bypass Utility shows expired. 4. SP Flash Tool 5. Stock Firmware STEPS: Install MTK USB Drivers and...
forum.xda-developers.com
NikolaTechGuy said:
hi, i recently tried flashing the stock rom for rosemare_redmi note 10s) But after the flash it wont turn on, blank screen, no recovery, no fastboot only brom mode is left, so i was wondering if there is a way to unbrick it.
Click to expand...
Click to collapse
Redmi Note 10S - Flashing with SP Flash Tool in BROM mode.
Required Softwares [DOWNLOAD LINK] 1. MTK Drivers 2. LIB USB FILTER 3. MTK Auth Bypass Utility V43 or use Android Utility V109 if MTK Auth Bypass Utility shows expired. 4. SP Flash Tool 5. Stock Firmware STEPS: Install MTK USB Drivers and...
forum.xda-developers.com
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)