Develop Bugs

Possible solution for issues with MAGLDR, USB Flasher.

Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.

:::Edited:::

Try killing any adb running in the background first

I'm not sure it is somehow connected with Android or ADB since when HD2 is in flasher mode it is not runnung Android. The device is detected like HTC Usb Sync or something like this.

Another option is to use updated flasher attached. I found it on russian forum.

hlvl said:
I'm not sure it is somehow connected with Android or ADB since when HD2 is in flasher mode it is not runnung Android. The device is detected like HTC Usb Sync or something like this.
Click to expand...
Click to collapse
Meh... I can't read. For some reason I read that you were talking about connecting your phone to the PC, i.e. within android, for USB mass storage etc....
Even the topic of the thread says otherwise. I'll go get my eyes tested...

Sometimes it's because ADB still in your PC memery, just force close it and everything will be fine.

As I said I tried to reboot PC but it didn't help. I doubt ADB start with Windows but rather only when you start using it.

hlvl said:
Another option is to use updated flasher attached. I found it on russian forum.
Click to expand...
Click to collapse
Do you mean that this is MAGLDR 1.13!?!?

hlvl said:
Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.
Click to expand...
Click to collapse
Thanks man. I was already freaking out because of this.

I'm going to try this on my desktop, that's why I stopped using it lol
Sent from my HD2 using xda premium

Thanks! It worked very well!!
PG

Really thank you, you saved my phone

Mine has always done that. I just have to wait until the flasher program gets to the Looking for USB step and disconnect/reconnect the USB cable.

Or get a new cable. I had the same issue but even this guide didnt work. My cable needed replacing, luckily I had a spare in my closet. Tried it and bingo all the drivers installed. If it just wont find it, get a new USB cable.

I have the same problem but in bootloader my usb connection works...when i try to flash recovery with usb flasher mode in magdlr doesnt.
Wait for usb............and is stuck like that.So its not the cable..i tried to install new driver..i tried with command prompt....im freaking out!!

Installing WMDC 6.1 worked for me
hlvl said:
Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.
Click to expand...
Click to collapse
Had same problem getting PC to recognize HD2 in order to Task29, etc...
I downloaded/installed WMDC 6.1 (for Vista, but works with W7) and walla... fixed! Link HERE.

ADB not seeing my Swift (retry)

Hi all, posting here because my other thread hasn't been seen.
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Update: I have found that at the least I should be able to see my phone in the Other Devices list in the Device Manager but I've got nothing, just ADB Interface

Alright I see. I am assuming you are using stock COS. So when you enable developer options and enabled android debugging your computer did not want to pick it up. Unplug device and Try revoking USB Authoriztions in developer options. plug swift back in and look at the device. It should ask you for Authroization

Thanks Yasteellutch. Still not seen by adb devices. I think I'll just clear the phone back to factory and try again...
B

Hi everyone,
@finnfather I think I have solved the issue. Today, I decided to manualy install (cm-12.1-YOG7DAS2FI) the latest cyanogen update as my phone didn't recive it as an OTA. I downloaded the zip package here and installed it through the stock recovery. And now, adb works! Also, this has fixed a few problems with themes. Now I can use helium! I hope this helps,
Jev

I cound manage the get a workung adb connection, buy switching adb debugging off and on again on the device while the device was connected to the pc via USB. Then I opened the device manager in windows and klicked on update driver vor the unrecogniced device. After that the device prompted a dialog, I had to accept the connection. Now the device was visible in the adb device list. (@jevtheboss: So you do not have to reinstall the cm to make it work)

Device unrecognized on multiple systems

I've been researching and trying to sort this out on my own for a while now. I've turned up nothing, so I figured I'd ask for some help. I'll try to provide as much information as possible here.
I was attempting to unlock and root my Razer Phone from my Windows PC. I plugged it in and had it recognized over ADB with no issue. I sent "adb reboot bootloader" to start things off. Once it was in download mode, I sent the "fastboot -i 0x1532 devices" command to make sure it was recognized. It wasn't. I checked devices manager, and sure enough, it was not picking up the Google driver that every other device I own works with. I attempted to update the driver manually by pointing it to the inf file. It gave me an error stating that the driver is not designed to work with 64-bit Windows. I found that odd, as this is the exact same driver that I've used with my other devices for this stuff. I plugged in my HTC 10, since that was nearby. It was recognized via fastboot like it always was. Same cable I was using with the Razer and everything.
I booted to Linux Mint on the same machine and tried the same stuff. It would pick up the Razer only in fastboot, but not ADB. In fastboot, I could detect it with "fastboot -i 0x1532 devices", and it showed up just fine. When I attempted to run "fastboot -i 0x1532 flashing unlock" it just gave me the fastboot command reference list. (I don't have a screenshot, but it looked like this, in case you're unsure what I am referring to.) I rebooted back to the system and double checked that I had checked "Enable OEM Unlock", and I had done that already. I double checked everything with my HTC 10, and again, it all works fine on the HTC 10. ADB and fastboot are both recognized correctly on Linux.
So armed with this information, I moved over to my Linux server. I used a different cable this time, and got a similar result. The Razer phone was recognized over ADB and I was able to get into fastboot. Once there, it was detected with the fastboot devices command. I attempted to run the unlock command, and again was presented with the fastboot reference list as before. Double checked with the HTC 10, and all was workign fine with that device.
Does anyone have any ideas, or is it possible that it's the Razer phone that's the problem? I may have access to a Mac laptop later on, and I could attempt this from there, but this is getting nuts. I don't think I've ever had this much trouble getting into a device before.

Yeah I had this as well, basically you may have the latest drivers but are missing the latest adb/Fastboot executables. Apparently they have changed a few commands in the newer one and that way of unlocking isn't in the old version. Just google for the adb/Fastboot package from the Google site, can remember the exact name but it was the first hit on Google. I just extracted the whole zip to a directory and used it right from there. The reason you are getting the help screen from Fastboot is cause for that version at least, your giving it an illegal command.

I got the same problem till I put my usb in a usb 2.0 in the back of the pc in a highlight usb port witch I read after on Asus Website that suppose to charge your phone if you turn off your pc so basically a always on usb. Also I managed to unlock and brick my device only with one cable I tried 4 cables none of them worked .so for you to keep In mind
Try different cables
Try usb 2.0
Try driver from twrp for razer phone thread that worked for me

Seems to be an ongoing issue for me on my main desktop. I grabbed my old development laptop out of the closet, booted it up, and I was able to get everything recognized and working. I tried doing some more work this morning on my desktop and noticed that I'm having driver issues elsewhere, so it seems to be an issue with this machine. I'm still not sure why the Linux installation on the same machine was exhibiting the same issue, though.

OP3 with completly broken screen, any way to access?

Hey Guys!
The screen of my OP3 broke a while back and since then I hadn't got the time to fix it - well until a few days ago - and I can't seem to access it via adb. The phone is rooted so USB-Debugging is enabled but if I try to find it through '''adb devices''' nothing pops up, albeit windows "sees" the phone (the CD-Rom Driver is showing up in the File Explorer). ADB is installed and works with other phones (Tried it with an LG G3 & Huawei Ascend G7)
Stuff I tried:
Reinstalling ADB => Still can't find the device
Unplugged , replugged the battery & start the phone > just gets me into the lock screen (i assume: LED Indicator is green, an Alert slider is working, captive buttons are working, can take a pic with VOLUME DOWN & POWER,...)
Tried Vysor > cannot see device
Installing OP3 Drivers from the phone => Stuck at the end
The Screen is completely black so I can't really see anything But all other buttons are working.
If someone has a fix, please post - thanks. I just wanna get my photos back

TheTitanSmash said:
Hey Guys!
The screen of my OP3 broke a while back and since then I hadn't got the time to fix it - well until a few days ago - and I can't seem to access it via adb. The phone is rooted so USB-Debugging is enabled but if I try to find it through '''adb devices''' nothing pops up, albeit windows "sees" the phone (the CD-Rom Driver is showing up in the File Explorer). ADB is installed and works with other phones (Tried it with an LG G3 & Huawei Ascend G7)
Stuff I tried:
Reinstalling ADB => Still can't find the device
Unplugged , replugged the battery & start the phone > just gets me into the lock screen (i assume: LED Indicator is green, an Alert slider is working, captive buttons are working, can take a pic with VOLUME DOWN & POWER,...)
Tried Vysor > cannot see device
Installing OP3 Drivers from the phone => Stuck at the end
The Screen is completely black so I can't really see anything But all other buttons are working.
If someone has a fix, please post - thanks. I just wanna get my photos back
Click to expand...
Click to collapse
Your drivers seem to be the issue. Delete all the drivers for mobile, Android etc devices and then install OP3 drivers alone. If necessary use USBDview on PC/laptop to view the drivers and to delete. If adb starts working, you can simply use 'adb pull /sdcard' to copy all the photos and files.

tnsmani said:
Your drivers seem to be the issue. Delete all the drivers for mobile, Android etc devices and then install OP3 drivers alone. If necessary use USBDview on PC/laptop to view the drivers and to delete. If adb starts working, you can simply use 'adb pull /sdcard' to copy all the photos and files.
Click to expand...
Click to collapse
So I tried to uninstall everything related to my phone and tried to reinstall the oneplus drivers (i tried the ones on the phone and the ones online). Long story short: The install was unsuccessful & the install stayed stuck (Execute the commands...) in that state.
Weirdly, my OP3 seems to show up as an MTP USB device in the Device Manager......
I think the OP drivers are just broken.... I'll try them on a 32bit computer if i find one.
Any other ideas? ADB is up to date & Android studio too.
Cheers

TheTitanSmash said:
So I tried to uninstall everything related to my phone and tried to reinstall the oneplus drivers (i tried the ones on the phone and the ones online). Long story short: The install was unsuccessful & the install stayed stuck (Execute the commands...) in that state.
Weirdly, my OP3 seems to show up as an MTP USB device in the Device Manager......
I think the OP drivers are just broken.... I'll try them on a 32bit computer if i find one.
Any other ideas? ADB is up to date & Android studio too.
Cheers
Click to expand...
Click to collapse
Well, if it shows up as MTP, open your phone's contents on a browser and copy/paste files.
Otherwise, I think that it is Windows that is having an issue. Try reinstalling Windows or try on another PC/laptop, if possible. Not every driver file on the phone/internet can be corrupt. For what it is worth, I am attaching my OP3 drivers. You can try them if you want to.

Obtained Sprint Nexus S 4G, Stuck on ICS

So my buddy gave me this Nexus S 4G, since I like to collect phones. Unfortunately, it appears to be stuck on 4.0 ICS. I tried to check for an update to 4.1 ICS, but for some reason, it reports that my phone is up to date??? Wtf. So I tried doing it manually, I can't flash this random OTA which may or may not (probably is) Jelly Bean in stock recovery, but it fails. I tried doing it even more manually using fastboot, but for some reason, I can't get the USB drivers to work. My next step is to use a Macintosh, as they seem to work better with Android, but I don't have access to it yet. In the mean time, is there any other way to get this phone updated or, at the very least, rooted and ROM'd?

@Dr. Hax
I'm assuming you are using windows? If so burn a Linux iso, Mint or Ubuntu are both great. You can make a bootable iso using a thumb drive or CD. Then set up your pc for dual boot. You'll never have a driver issue on Linux.
I'm sure you probably know this but how I have gotten windows to work and see my device is install the fastboot and adb 15 second installer from here: https://forum.xda-developers.com/showthread.php?t=2588979
Then reboot of course. And when I plug my device in have developer options enabled and usb debugging enabled and be watching phone for the little box pop up that you just checkmark really quick so your pc can communicate with the device... Also if you scroll down on the phone in developer options to "default usb configuration" and change that to "file transfer", that will usually bring the little box up on my devices to check mark so they can communicate..It only shows for a second then it's gone. But if it hasn't popped up yet then open terminal and type sudo adb devices (hit enter) and again be watching your phone because that little box should then come up that you must quickly check mark on phone so pc and phone can communicate.
I always uninstall and reinstall drivers on windows and reboot afterwards. Also make sure check device manager and see what's there. But that 15 second fastboot adb installer for windows is a life saver and makes it all super easy!! On Linux none of this happens. Ever! ? You just plug in your phone and the model of your device shows up on the computer screen. IDK if this makes sense much but I tried to word it where it did best I could. Hopefully this helps or you already got it going.