Related
Hi,
I have screwed with my smartphone (a Lenovo A760)...
I want to install a new rom and decided to erase everything.
I goes into clockworkmod / storage and format each point like /system, /boot...something, etc.
Of course, my phone won't boot anymore.
Is there a way to re-install a bootloader and a rom?
Thank you so much for helping me and sorry for my english, I speak french.
Cheers
Go here and read the whole thread.
adb devices
iZLeeP said:
Go here and read the whole thread.
Click to expand...
Click to collapse
Hi,
I've just read the 27 pages of this post, but there's no answer to my question.
ADB can't find any devices.
When I connect the phone with USB, Windows detects an unknown device, I try to install QC_Dload_driver.zip found in The lenove a706 thread.
Now Windows detects a "Lenovo HS-USB QDLoader 9008 (COM16)"
ADB can't attached my device.
My gsm is turned off and no manip like volume+ + on/off works, it stays off
What can I do?
Thank you
zzztetsuozzz said:
Hi,
I've just read the 27 pages of this post, but there's no answer to my question.
ADB can't find any devices.
When I connect the phone with USB, Windows detects an unknown device, I try to install QC_Dload_driver.zip found in The lenove a706 thread.
Now Windows detects a "Lenovo HS-USB QDLoader 9008 (COM16)"
ADB can't attached my device.
My gsm is turned off and no manip like volume+ + on/off works, it stays off
What can I do?
Thank you
Click to expand...
Click to collapse
You need to have an insecure boot image. Unpack your boot image with either of these tools: michfood (for windows) or bgcngm (for linux/cygwin). Add the following lines in the default.prop of ramdisk folder
Code:
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
Then repack your boot image.
iZLeeP said:
You need to have an insecure boot image. Unpack your boot image with either of these tools: michfood (for windows) or bgcngm (for linux/cygwin). Add the following lines in the default.prop of ramdisk folder
Code:
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
Then repack your boot image.
Click to expand...
Click to collapse
Thank you for helping me.
Do you know how can I inject the new boot.img?
ADB won't detect my device.
When I run adb devices, I receive an empty list
When I run adb usb or anything it says : error device not found
My Windows 7 detect my GSM as a COM port (Lenovo HS-USB QDLoader 9008 (COM17)) after install QC_Dload_driver.
One more, thank you
zzztetsuozzz said:
Thank you for helping me.
Do you know how can I inject the new boot.img?
ADB won't detect my device.
When I run adb devices, I receive an empty list
When I run adb usb or anything it says : error device not found
My Windows 7 detect my GSM as a COM port (Lenovo HS-USB QDLoader 9008 (COM17)) after install QC_Dload_driver.
One more, thank you
Click to expand...
Click to collapse
You need to flash it via SPFT, download links are here and on how to use that tool. It's the most important tool for any MTK devices.
But you need to find the correct scatter.txt file for your device to be able to use SPFT and flash the modded boot.img, otherwise, SPFT won't work properly.
EDIT: Why not just look for a flashable stock rom for your phone? Since you already have CWM/custom recovery, you can just flash that rom and your phone will be up and running.
iZLeeP said:
You need to flash it via SPFT, download links are here and on how to use that tool. It's the most important tool for any MTK devices.
But you need to find the correct scatter.txt file for your device to be able to use SPFT and flash the modded boot.img, otherwise, SPFT won't work properly.
EDIT: Why not just look for a flashable stock rom for your phone? Since you already have CWM/custom recovery, you can just flash that rom and your phone will be up and running.
Click to expand...
Click to collapse
My phone is not a Mediatek device.
It's an Qualcomm MSM8225Q Quad Core 1.2GHz
Do you know if I can use SPFT for those Qualcomm CPU?
Thank you for the time you spend to answer
zzztetsuozzz said:
My phone is not a Mediatek device.
It's an Qualcomm MSM8225Q Quad Core 1.2GHz
Do you know if I can use SPFT for those Qualcomm CPU?
Thank you for the time you spend to answer
Click to expand...
Click to collapse
I see, nope, you can't use SPFT. It's only for MTK devices.
have the same
anyone came up with a solution?
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
Excuse me for my bad English. I am new on this Forum. Please help me, I have a big problem!
I can’t use Fastboot command, because ewery time I got the „Waiting for devices” error message
1) I have a Motorola Moto G4 phone (XT 1622, athene)
2) This mobile are not rooted.
3) I want to unlock my bootloader, after this I want to install TWRP, and after this I van root my mobile, for install the custom Lineage OS.
4) On my phone I activated at the Developper Otions the USB debugging, and OEM Unlocking.
5) I connected my phone to my PC, I used first time Windows 10. On this system my Moto G4 are identified: Motorola ADB interface. No problem with identification, no any yelow exclamation matrk, no unidentified device!
6) I have installed the correct ADB and Fastboot driver v.1.4.3 (link is made from this site)
7) I have installed the Motorola driver from the official Motorola site.
8) All ADB command work fine, for example adb devices, adb reboot bootloader, etc.
9) But no fastboot command work, when I tested the fastboot devices, I got the „Waiting for devices”. Of corse befor this, I rebooted my phone in fastboot mode! If I use any fastboot command, I got this error message.
10) I try to use the excellent tools (thank you for this): Universal Fastboot & ADB tool, latest version, but the situation in this case is the same, „Waiting for devices”.
11) Of corse I rebooted the PC after instalation of the drivers, the fastboot.exe is in the right paths, etc.
12) I have installed the Universal USB Driver with the Universal Fastboot & ADB tool, Install drivers button, PC rebooted after this.
13) I used Windows 10, Windows XP, and Ubuntu, and in all cases I got the „Waiting for devices”
14) Under Ubuntu I got this message, despite that on Ubuntu the ADB and Fastboot driver installations are cleare.
15) I tested all on many other PC.
16) Every time I connected my phone to the PC only on USB 2.0 port, I changed the USB port, and I changed the USB cable too.
17) I read hundred ot tutorilas on youtube, on differant Forums, but none of them helped.
18) I uninstalled or reinstalled a many timet he ADB and fastboot drivers (I tested a lot of drives from the net), and I installet a many times the official Motorola driver, and the Google universal USB driver, but nothing
Please tell me what can I do for solve this devil situation, Please help me! Thank you again!
Wrong section mate, this is the section for Leeco Le Max 2 and not Moto G4. You're better off posting there in the correct section.
Excuse me
GethPrime said:
Wrong section mate, this is the section for Leeco Le Max 2 and not Moto G4. You're better off posting there in the correct section.
Click to expand...
Click to collapse
Excuse me, I can't see where can I post this! Please help me, where is a link, where I can repost this, or please move this , to a right place. Thank you!
tuzo1960 said:
Excuse me, I can't see where can I post this! Please help me, where is a link, where I can repost this, or please move this , to a right place. Thank you!
Click to expand...
Click to collapse
Not hard to find:
https://forum.xda-developers.com/moto-g4
Thank you
popoyaya said:
Not hard to find:
https://forum.xda-developers.com/moto-g4
Click to expand...
Click to collapse
Thank you popoyaya.
Please somebody delete this wrong placed thread! Thank you!
Closed per OP request
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.
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)