Develop Bugs

QCN Backup andd restore.

Hi,
I searched a lot,but couldn't find a specific answer.
Is it possible to do QCN backup and restore using QPST successfully?Can anyone please confirm it?
or is it just not supported by QPST tool like nexus devices?

none?

Jongla said:
none?
Click to expand...
Click to collapse
You can use this guide here, to get the drivers and the QPST. Then maybe QPST will work, but I am not so sure.
http://www.androidbrick.com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008/
Here some more info

The method above almost works, well at least for me. Unless I'm just doing something wrong. My phone shows in QPST now but it's stuck in a downloading state for some reason.

Sturdymush said:
The method above almost works, well at least for me. Unless I'm just doing something wrong. My phone shows in QPST now but it's stuck in a downloading state for some reason.
Click to expand...
Click to collapse
more drivers here
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
---------- Post added at 10:40 AM ---------- Previous post was at 10:26 AM ----------
Sturdymush said:
The method above almost works, well at least for me. Unless I'm just doing something wrong. My phone shows in QPST now but it's stuck in a downloading state for some reason.
Click to expand...
Click to collapse
Can you try with QXDM instead of QPST ?
I would really appreciate.
cheers.
PS: this is a guide for OP2 (http://forum.xda-developers.com/showpost.php?p=65456106&postcount=16 )
to set it to diag mode dial
*#801# and then select the Engineering mode.
I used QXDM Pro 3.14.594 to get the QCN in xml format (more readable).
Good Luck

Sturdymush said:
The method above almost works, well at least for me. Unless I'm just doing something wrong. My phone shows in QPST now but it's stuck in a downloading state for some reason.
Click to expand...
Click to collapse
you have to find a way to put the phone in diagnostic mode. I think there is a combination of keys,
these are for OP2
http://mobilespecs.net/phone/codes/OnePlus/OnePlus_TWO_64GB.html
*#9090# � Diagnostic configuration
maybe it works
or with adb
setprop sys.usb.config diag,adb
this one for OPO
http://forum.xda-developers.com/oneplus-one/general/guide-unlock-aditional-bands-qualcomm-t2877031

I tried using adb yesterday but after I do it I can't install the drivers

[/COLOR]
Sturdymush said:
I tried using adb yesterday but after I do it I can't install the drivers
Click to expand...
Click to collapse
Ok, found this...
It is from the OP3 forum, here http://forum.xda-developers.com/showpost.php?p=67470602&postcount=2
And it should work
If you switch a device into a hybrid mode like "diag,adb" it will dish out a new custom product id over the usb interface, one that combines both devices into one new one.
There are however no fitting diag drivers that match that product id.
If you want diag to work properly, switch your phone into single-diag mode by executing setprop sys.usb.config diag via a rooted terminal emulator from the phone itself, rather than doing it via an adb shell from a computer.
This will result in the proper diag product id being reported to your computer, allowing you to install the right driver.
As for the driver download, a simple google search will yield you the results.
Just search for "Qualcomm Diag Driver x64".
Edit: Oh one more thing... last time I checked I couldn't find a properly signed Diag driver for 64bit systems...
You will probably have to boot your computer smashing the F8 key repeatedly, and picking "disable driver signature enforcement" from the boot menu to temporarily disable the driver signature check, allowing you to install and use the Diag driver.

LG G4 How to find correct version & model

Hello guys,
I am an unlocked LG G4 user running on Android 5.1 Lollipop.
I cant recieve updates through OTA as it always says "You have latest version of current OS". So I tried updating manually.
Since I am not very good with LG flash tools I was looking at unlocking bootloader and twrp.
The problem is :
My hardware info shows "LG H815"
Adb recognizes it as "LGF500L204da3d4 unauthorized"
A google search told me that F500L is Korean variant and now I am totally confused. Am I missing something here.
I have attached screenshots of device info.
Please guide.

The unauthorized thing comes from enabling ADB in the Developer Options. Once you do that, the very next time you connect the G4 to a computer and then run the "adb devices" command it starts the adb daemon and then tries to connect to the device, upon a connection the phone not the computer will pop up a box asking for permission to allow the connection based on an RSA fingerprint (aka the security aspect) and you have to allow that.
Without allowing that you'll never get ADB to work properly. You can try this process to get things working properly:
- Disconnect the G4 from the computer entirely
- Disconnect it from any charger too just so you're good to go
- Go into the Developer Options, revoke all using the "Revoke USB debugging permissions" and reboot the G4 right then and right there as soon as those permissions are revoked, do NOT do anything else, reboot immediately after you make that change
- Upon the reboot let the G4 boot completely and wait 2 minutes before swiping/unlocking the device back to the Home screen
- Plug in the USB cable and make sure you choose the MTP/file option, not charging
- Fire up the adb devices command on the computer and watch the phone carefully for that popup asking for permission to connect
- Choose OK to enable the connection and check the box to make it permanent for that specific computer
After that it should show you the device serial number and say "authorized." If not then you're missing something or there's some other problem, but that's how I've done this on a few hundred devices over the years and never had an issue. The other thing that could be affecting this are making sure you have the proper ADB drivers, sometimes that can be a complete pooch-screw to get working and I can't help on that front.
Pic below is what you're looking for and without granting this permission ADB will never see the device as authorized.
Good luck...

br0adband said:
The unauthorized thing comes from enabling ADB in the Developer Options. Once you do that, the very next time you connect the G4 to a computer and then run the "adb devices" command it starts the adb daemon and then tries to connect to the device, upon a connection the phone not the computer will pop up a box asking for permission to allow the connection based on an RSA fingerprint (aka the security aspect) and you have to allow that.
Without allowing that you'll never get ADB to work properly. You can try this process to get things working properly:
- Disconnect the G4 from the computer entirely
- Disconnect it from any charger too just so you're good to go
- Go into the Developer Options, revoke all using the "Revoke USB debugging permissions" and reboot the G4 right then and right there as soon as those permissions are revoked, do NOT do anything else, reboot immediately after you make that change
- Upon the reboot let the G4 boot completely and wait 2 minutes before swiping/unlocking the device back to the Home screen
- Plug in the USB cable and make sure you choose the MTP/file option, not charging
- Fire up the adb devices command on the computer and watch the phone carefully for that popup asking for permission to connect
- Choose OK to enable the connection and check the box to make it permanent for that specific computer
After that it should show you the device serial number and say "authorized." If not then you're missing something or there's some other problem, but that's how I've done this on a few hundred devices over the years and never had an issue. The other thing that could be affecting this are making sure you have the proper ADB drivers, sometimes that can be a complete pooch-screw to get working and I can't help on that front.
Pic below is what you're looking for and without granting this permission ADB will never see the device as authorized.
Good luck...
Click to expand...
Click to collapse
Ok..So I tried as per above instructions.
The only change is it's written as "device" in place of "unauthorized". The serial number is the same.
I thought it would be written as LGH815...etc etc for the H815 model. But here it's F500L...
Is this normal?

[email protected] said:
Ok..So I tried as per above instructions.
The only change is it's written as "device" in place of "unauthorized". The serial number is the same.
I thought it would be written as LGH815...etc etc for the H815 model. But here it's F500L...
Is this normal?
Click to expand...
Click to collapse
Update:
Found something interesting as well.
The phone doesn't boot into recovery using hardware keys.
I tried with adb and got into a screen showing "No command" with red exclamation.

It means you don't have a working recovery partition now so something got borked. Best case scenario: do a full factory reinstall of the stock ROM and go from there, maybe, using Odin or whatever tool you prefer, these days I have no idea what software there is to be honest.
I don't own a G4 anymore either, but if I find one in good shape for a good price, like $50 or less, I'll more than likely grab it.

br0adband said:
It means you don't have a working recovery partition now so something got borked. Best case scenario: do a full factory reinstall of the stock ROM and go from there, maybe, using Odin or whatever tool you prefer, these days I have no idea what software there is to be honest.
I don't own a G4 anymore either, but if I find one in good shape for a good price, like $50 or less, I'll more than likely grab it.
Click to expand...
Click to collapse
Maybe I should just keep it as it is coz I don't even know what rom to use and actually which model it is.

[email protected] said:
Maybe I should just keep it as it is coz I don't even know what rom to use and actually which model it is.
Click to expand...
Click to collapse
Used to believe HTC devices are tough nuts to crack but LG just blowed me away.

Windows 10 not recognizing Moto g6 Play

I've found a few posts on other sites with no solutions yet. Hopefully I'm not being a pain and asking an already answered question elsewhere.
I have the amazon version of the Moto G6 Play, and I've been trying to unlock the bootloader. The problem is that motorola's device manager doesn't seem to install the necessary drives for the PC to recognize the phone is connected via usb, and frankly, Motorola's customer service hasn't helped in the slightest.
I'm running Windows 10, fully updated to the latest release, and my G6 is running android 8.0.0.0. I've unlocked the developer options, allowed OEM unlock, USB debugging, and changed the USB connection settings from "charging" to "MTP." I've installed the latest Motorola Device Manager, but I continue to see that the phone is listed as an unknown USB device from my device manager. I've tried manually updating the drivers both by searching the install folder for the MDM, as well as the Windows System 32 folder. I've also tried using the troubleshooter to find drivers online with no luck. When I run abd from the command console, it lists no connected devices and trying to run any commands fails to yield any response on either the phone or the console. I feel like there's something obvious that I must have missed, but for the life of me I can't figure out what.
Any suggestions? Thanks in advance.

:aneburchette said:
I've found a few posts on other sites with no solutions yet. Hopefully I'm not being a pain and asking an already answered question elsewhere.
I have the amazon version of the Moto G6 Play, and I've been trying to unlock the bootloader. The problem is that motorola's device manager doesn't seem to install the necessary drives for the PC to recognize the phone is connected via usb, and frankly, Motorola's customer service hasn't helped in the slightest.
I'm running Windows 10, fully updated to the latest release, and my G6 is running android 8.0.0.0. I've unlocked the developer options, allowed OEM unlock, USB debugging, and changed the USB connection settings from "charging" to "MTP." I've installed the latest Motorola Device Manager, but I continue to see that the phone is listed as an unknown USB device from my device manager. I've tried manually updating the drivers both by searching the install folder for the MDM, as well as the Windows System 32 folder. I've also tried using the troubleshooter to find drivers online with no luck. When I run abd from the command console, it lists no connected devices and trying to run any commands fails to yield any response on either the phone or the console. I feel like there's something obvious that I must have missed, but for the life of me I can't figure out what.
Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
Use this. https://support.motorola.com/us/en/solution/MS88481
Also, make sure to restart your PC after you install them.

my pc did not recognize it in fastboot mode, after trying other cpus ... the solution was to do a factory reset, and go! the adb fastboot already recognized it ... I hope it works for you

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.

Question Device Driver is Unavailable?

Hey guys so nobody kill me if this one seems obvious. At this point I just need help figuring this little issue out and I have kinda hit a dead end on solutions. I've been out of the modding game for quite some time now and have finally got back around to getting into ROMs again.
So I have my OnePlus 9 Pro (North America/ International Version) purchased right from there website. I decided I wanted to start off by unlocking the bootloader and rooting the phone. Basic stuff. I get ADB up and running on my laptop, all of my drivers I can possible install are installed, I check and see if the device lists under adb devices. It does. I boot my device into fastboot. I go to list devices to make sure its still connected aaannndd nothing... No matter what USB sloth I plug it into on the laptop nothing. I heard the device connect sound but nothing happens and the device never lists. So I go to the Device Manager on Windows 10 and I see that it is infact recognizing that an " Android" is connected. After a few seconds of "setting it up" I am met with a lovely reassuring message in the "other devices" list that "Device Driver is Unavailable." Thats it. No options to search online, no options to manually install something. Just no solution its just unavailable.
So at this point I'm not really sure what to do next. Its probably a very simple issue to correct but the driver installation error stuff always confused the hell out of me so If any of you fellow phone loving artists would be willing to help me out I'd greatly appreciate it!

I prefer using Linux because there isn't this problem, but my most recent experience with this on Windows, I had to have phone plugged in, go to Windows settings menu, go to system updates, and check for optional updates. The proper driver was there for me and likely will be for you too

If the device drivers install ok but you have problems detecting device in fastboot, you have to manually update driver:
While device is plugged in and in fastboot, go to device manager > click on your device in the list > update driver > choose from list > oneplus drivers. There should be 3 options
adb interface
Fastboot
Android composite driver (or something like that)
Install the fastboot one. Hope this helps

Guys thank you for the help! I checked under optional updates and all of the drivers i needed were listed as needing an update! Really appreciate the quick responses! Finally I can have some fun with this phone now! Thanks again guys!