Related
nvm I solved it
I have problems " waiting for device",..Need help...
Sent from my LG-P760 using xda premium
de.rach29 said:
I have problems " waiting for device",..Need help...
Sent from my LG-P760 using xda premium
Click to expand...
Click to collapse
You need to install fastboot drivers. When you are in fastboot you need to go 'device manager' or something like that on PC. Find android and use update drivers bottom option (install manualy) and point where your fastboot drivers are.
Fastboot driver
where can i find it?
giviman said:
where can i find it?
Click to expand...
Click to collapse
Where you can find what?
giviman said:
where can i find it?
Click to expand...
Click to collapse
Drivers? here:
developer.android.com/sdk/win-usb.html
This is also my problem, i try everything allready. Its just stuck on waiting for device after i try to flash recovery.
When phone is in fastboot mode it said unkonwn usb device, flash omap and fastboot and adb drivers are installed.
Is there any other method for root and recovery install?
Im not noob, i rooted and played with many Android phones, but for this i cant find any solution.
OS is Win Xp but there is same problem on Win 7 also.
who can give me the fastboot backup that i can flash !? I have flash recovery at fastboot :S
Need it for LG P760
thanks
install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php
hiiiiiiii
hii sir, when i type fastboot flash recovery recovery.img cmd show waiting for device for long time plz hlp
i had many problems trying to run adb commands along with fastboot...most recent was sideloading a rom in CWM.....no device detected...then dl pdanet and that driver fixed the problem...win7 x64....seems every computer is different and process to use adb on this phone...took me a while to find this as well...
help
i installed all the drivers but still it shows waiting for device
maxver0 said:
Where you can find what?
Click to expand...
Click to collapse
Waiting for device problem
maxver0 said:
You need to install fastboot drivers. When you are in fastboot you need to go 'device manager' or something like that on PC. Find android and use update drivers bottom option (install manualy) and point where your fastboot drivers are.
Click to expand...
Click to collapse
Can get the link for the drivers for micromax a58 need a heck of waiting for that to be installed with twrp recovery
Hello XDA,
I just got a v10 and while i'm new to the phone, I'm not new to rooting/ installing custom roms etc. But for the life of me I cant unlock to bootloader of this phone which if im not mistaken, is the only way to get root. I just installed adb on my windows 10 laptop and I'm trying to enter fastboot on my devices by plugging in the power cable and pressing the volume down and I'm greeted with a screen that says"*welcome to fastboot mode for bootloader unlock: *quick Guidance...etc" I cant exit out of this mode so I assume this is fastboot mode? It doesnt look like any fastboot mode Ive ever seen. Anyways when trying to run the fastboot oem unlock command, I am stuck on "waiting for device". I honestly dont know whats wrong with my setup but if someone could help that would be fantastic. I have tried installing the Lg united drivers and samsung drivers but they dont seem to work. Please advise if you could.
http://forum.xda-developers.com/showthread.php?t=3490604
gamin92 said:
http://forum.xda-developers.com/showthread.php?t=3490604
Click to expand...
Click to collapse
So to get it to work I have to install unbuntu software on my computer, boot into it and then install adb? I'm not getting this?
ayo234 said:
So to get it to work I have to install unbuntu software on my computer, boot into it and then install adb? I'm not getting this?
Click to expand...
Click to collapse
I looked online at some forums about this issue and I got it fixed Here what the post said
1. Connect your device while in fastboot mode.
2. open the device manager (ctrl + X on windows 10)
3. find your device "XXX ADB Device"(Mine was "Alcatel ADB Device" but it can be anything)
4. click on the arrow
5. right click on the Android Bootloader Interface
6. Click on "Properties"
7. Go to "Driver" Tab
8. Click "Uninstall"
9. Mark the "Delete the driver software for this device
10. Click OK
11. Disconnect and Reconnect your device from the cable
12. Windows device manager should show an item in the list that simply says Other devices, and will expand to "Android". Do those next steps quickly! (OR: just disconnect from the internet. Some people report it works). You have between 5-10 seconds until Windows changes it to another driver. If device manager changes the driver to "Kedacom USB device" (or something else, start over from step 8).
13. Right click and choose "Update driver software" -> Browse my computer for driver software -> Let me pick from a list...
14. Choose "Kedacom USB device" (or something else that seems logical)
15. Uncheck "Show compatible hardware"
16. Choose "Android bootloader interface version _" that is the latest (should be 28.8.2016).
17. Hopefully it will work for you
Extremely helpful and it solved my problem. Here the original thread, its post number 33
http://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
What's needed:
latest Android Pie firmware for Xperia XZ1 (I used 47.2.A.4.41_R4C UK or any version of the 47.2.A.6.30) from XperiFirm
newflasher_v13 tool here
Minimal ADB and Fastboot
TWRP Recovery here
last Magisk.zip here
first copy Magisk.zip to the sd card and insert it into the device
Install TWRP:
launch flashtool and download the latest firmware 47.2.A.4.41_R4C with XperiFirm ....
follow the path C: users / name / .flashTool / firmwares / Download
locate the unzipped firmware, open the folder and delete all the .ta files; then open the boot and partition folders and do the same thing
search the internet or XDA newflasher_v13 tool and place all 7 files in the C: users / name / .flashTool / firmwares / Download / 47.2.A.4.41_R4C folder
connect the device in flash mode
launch the .exe command
press "n" and again "n"
finished the firmware flash unplug the phone
When the first ignition is finished, open the debug and connect the mobile phone to the PC
open the folder Minimal in the path C: Program / Minimal and paste in the folder the recovery.img, run cmd.exe type the following commands
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery namerecovery.img
fastboot reboot
finished the start of the phone, turn it off and go into recovery mode (volume down + power button)
flash Magisk from the sd
turn on the cell phone and the root is done
Special thanks
oF2pks for the TWRP
munjeni for the newflasher
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
I have pie stock...can i start guide from point 10 ?
lilbrat said:
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
Click to expand...
Click to collapse
look at this thread for backup/restore your DRM keys
lilbrat said:
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
Click to expand...
Click to collapse
In my experience I can tell you that nothing is lost on the camera neither in the sound effects nor the color effects on the photos ...
ilblago81 said:
I have pie stock...can i start guide from point 10 ?
Click to expand...
Click to collapse
Absolutely yes
From the use I note that the recovery doesn't read the internal data, but only the sd card. I still don't understand if it's the firmware that has bugs or the twrp that still isn't calibrated for Adroid Pie.
Edit: I found in the XDA site the recovery for the new firmwre and everything works fine here
Would this work on SOV36 (AU XZ1)?
sinkoo1979 said:
Would this work on SOV36 (AU XZ1)?
Click to expand...
Click to collapse
Honestly I don't know, but if in your device install the firmware that we install in the g8341 means that you can. I'm thinking it's the same thing!
Sorry, but the requirement is always with unlocked bootloader?Thanks
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
dwang040 said:
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
Click to expand...
Click to collapse
Are your drivers properly installed reason I am asking is you're not getting a return when you type in fastboot devices, go back to you developer setting, revoke your debugging , then reinstall your drivers turn on USB debugging and see what happens?
lilbrat said:
Are your drivers properly installed reason I am asking is you're not getting a return when you type in fastboot devices, go back to you developer setting, revoke your debugging , then reinstall your drivers turn on USB debugging and see what happens?
Click to expand...
Click to collapse
Hmm, I think I know why it wasn't working? I got the xperia xz1 drivers off of the sony developer website, and I went to device manager and tried to do the legacy driver install, but I keep getting "This device cannot start (code 10)" Maybe that's the issue? And if so, am I installing it wrong or something?
dwang040 said:
Hmm, I think I know why it wasn't working? I got the xperia xz1 drivers off of the sony developer website, and I went to device manager and tried to do the legacy driver install, but I keep getting "This device cannot start (code 10)" Maybe that's the issue? And if so, am I installing it wrong or something?
Click to expand...
Click to collapse
What OS is on your computer?
lilbrat said:
What OS is on your computer?
Click to expand...
Click to collapse
Windows 10
dwang040 said:
Windows 10
Click to expand...
Click to collapse
Did you disable the driver verification signature?
(https://www.howtogeek.com/167723/ho....1-so-that-you-can-install-unsigned-drivers/) then reinstall min adb fastboot drivers and Sony companion and let it detect your phone..
chiacla said:
Sorry, but the requirement is always with unlocked bootloader?Thanks
Click to expand...
Click to collapse
you have to unlock the bootloader
dwang040 said:
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
Click to expand...
Click to collapse
did you install flashtool? did you install the drivers from the flashtool "drivers" folder? Did you unlocked the bootloader? ther'is no need to work on win10 signature
theflanker said:
did you install flashtool? did you install the drivers from the flashtool "drivers" folder? Did you unlocked the bootloader? ther'is no need to work on win10 signature
Click to expand...
Click to collapse
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
theflanker said:
you have to unlock the bootloader
Click to expand...
Click to collapse
He won't be able to unlock his bl till he figures out the issues with his drivers.. whether he uses the ones in flashtool, installs min adb and fastboot drivers or the android sdk..
---------- Post added at 05:34 PM ---------- Previous post was at 05:29 PM ----------
dwang040 said:
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
Click to expand...
Click to collapse
Once you get your driver's fixed, just follow the directions given by Sony.. Your phone screen will remain black as all info will be done on your computer..
dwang040 said:
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
Click to expand...
Click to collapse
Absolutely no, flashtool doesn't need to unlock the bootloader, rather serves to re-lock it in some xperia devices. To unlock it you have to use cmd commands in adb & fastboot, but you can find it here in the XZ1 section.
The cell screen remains black and a blue led appears if you connect in fastboot mode, if you connect in flash mode the screen remains black, but a green LED appears.
if you have problems with the recognition of the device on your PC I can link my guide, it's in italian but if you use google translator you understand it well here
arslancn said:
look at this thread for backup/restore your DRM keys
Click to expand...
Click to collapse
I've checked out the thread but it appears only a few with the xz1 have tried it and they didn't report the outcome, well except one who somehow managed to turn his device in an expensive paperweight.. But I will check it out this weekend..
i tried to do it my self. follow an instruction from a official website and other
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
https://www.getdroidtips.com/how-to...-plus-i3213-i4213-i4293-i3223/#Pre-Requisites
which i got stuck at, when i boot into bootloader mode . the phone seem to restart and appear only black screen with blue indicator.
then i tried to check if it still connect to adb or not, with {adb devices} its not listed there
PS.
-the drivers work fine
-my Xperia 10 plus model is I4293
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Zaben said:
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Click to expand...
Click to collapse
one thing weird
i using a Xperia Tool (Xperia Companion) and it display the text that my phone need to unlock the screen or allow to use data tranfer
which i already check a USB debugging to be on, and every time i connect it to my PC, it still ask me a permission to be allow or not
maybe this is a problem here ?
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Haxk20 said:
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Click to expand...
Click to collapse
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
ZimpleThing said:
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
Click to expand...
Click to collapse
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Haxk20 said:
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Click to expand...
Click to collapse
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
ZimpleThing said:
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
Click to expand...
Click to collapse
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Haxk20 said:
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Click to expand...
Click to collapse
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
ZimpleThing said:
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
Click to expand...
Click to collapse
There is a thanks button. Hit it instead of saying it.
Haxk20 said:
There is a thanks button. Hit it instead of saying it.
Click to expand...
Click to collapse
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Glad I could help
I know its been a long time but maybe someone can help me.
I can get into the bootloader but when I trie to use the unlock code, mentioned above, and the sony unlock key it always says waiting for device but nothing happens. Any clue?
Edit fixed the Problem
Xperia 10 plus stuck on waiting for device
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
I was using windows 10. From what I can remember, my problem is that I didn't install driver correctly (I'm not sure which one). I am not really sure if this fastboot driver the one I used. I saw my device in Device Manager, but I got waiting on device... just like you. So what I have done was locate my device in Device Manager and install the sony driver over that device. If sony's driver was not the correct one, then it was another driver that I can't remember, but the instruction still the same. Sorry for an unclear message, but I can barely remember anything now.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
Go in Windows Device Manager and check the device . If needed install drivers manually
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)