Database Develop

QC Diag drivers for Moto X where they at?

I've installed all kinds of motorola drivers including the one that the device manager from motorola website, still I cannot read the qc diag serial port. Does anyone have these drivers?! I'm working on sim unlocking the sprint moto x and I gotta be able to get into the modem and see what I'm dealing with. Get me usb serial access to issue QC commands and hopefully I'll be able to post instructions for simunlock and cricket/metropcs flash (that opens up pretty much every carrier except verizon for the sprint model). I wont know until I can qxdm to it, I wish I had a radiocomm version that supported the msm8960 but the version I have goes up through the 6x00 not even close. I still think I can get done what I need to do with qxdm.
Thanks in advance.

+1,did you find then?

thundercles said:
I've installed all kinds of motorola drivers including the one that the device manager from motorola website, still I cannot read the qc diag serial port. Does anyone have these drivers?! I'm working on sim unlocking the sprint moto x and I gotta be able to get into the modem and see what I'm dealing with. Get me usb serial access to issue QC commands and hopefully I'll be able to post instructions for simunlock and cricket/metropcs flash (that opens up pretty much every carrier except verizon for the sprint model). I wont know until I can qxdm to it, I wish I had a radiocomm version that supported the msm8960 but the version I have goes up through the 6x00 not even close. I still think I can get done what I need to do with qxdm.
Thanks in advance.
Click to expand...
Click to collapse
looks like you're booted into bp tools for those interfaces to be dectected, correct? i'm not sure whether or not the moto device manager has drivers for these interfaces as i always use the standalone drivers. here's a link to the latest available as of this posting:
http://batakang.com/ftp/?dir=devs/mhous33/drivers
whichever driver installer you use, the drivers have to be installed manually. iirc motorola qc diag interface is the only one you need to communicate with qpst/qxdm.
in device manager, right click on motorola qc diag interface > update driver software > browse my computer for driver software > let me pick from a list of device drivers on my computer > ports (com & lpt).
under manufacturer, select motorola.
under model, select motorola qc diag port.
click next, driver should be installed successfully.
looks like you're using windows 8, so you may have to temporarily disable driver signing for it to install.
hope this helps.

Q9Nap said:
looks like you're booted into bp tools for those interfaces to be dectected, correct? i'm not sure whether or not the moto device manager has drivers for these interfaces as i always use the standalone drivers. here's a link to the latest available as of this posting:
http://batakang.com/ftp/?dir=devs/mhous33/drivers
whichever driver installer you use, the drivers have to be installed manually. iirc motorola qc diag interface is the only one you need to communicate with qpst/qxdm.
in device manager, right click on motorola qc diag interface > update driver software > browse my computer for driver software > let me pick from a list of device drivers on my computer > ports (com & lpt).
under manufacturer, select motorola.
under model, select motorola qc diag port.
click next, driver should be installed successfully.
looks like you're using windows 8, so you may have to temporarily disable driver signing for it to install.
hope this helps.
Click to expand...
Click to collapse
Lmao I posted this same rant on facebook and a phone flashing friend did these things with team viewer and went ahead and helped me retrieve my MSL code as well. It is all coming down to the UICC unlock, this is what is holding back our ability to sim unlock the sprint version of this phone (because without the UICC unlock it wont read any other Sim cards anyways) I'm working on that right now but I have a headache so it will be later.

ok,please if you have sucefully unlock gsm i will love to pay you if you give me the way.

MSL code
thundercles said:
Lmao I posted this same rant on facebook and a phone flashing friend did these things with team viewer and went ahead and helped me retrieve my MSL code as well. It is all coming down to the UICC unlock, this is what is holding back our ability to sim unlock the sprint version of this phone (because without the UICC unlock it wont read any other Sim cards anyways) I'm working on that right now but I have a headache so it will be later.
Click to expand...
Click to collapse
Does this mean getting the MSL code is useless in unlocking the device for GSM use?

do you have that moto x drivers? i dont find it anywhere.. will you please reupload it some where.. Thanks.

Help with Bootloader and Root. I'm stuck! XT1063

Hello!
I'm from Puerto Rico, my carrier is Claro PR. I've been trying to root my device but so far I haven't even been able to unlock the Bootloader. I get the annoying and indefinite < waiting for device > message on the Fastboot CMD screen. I have installed ADB drivers from Google and it didn't help since the Motorola drivers did not even recognize my device in Fastboot. It seems that the only time my device is recognized in Fastboot mode is when there are no ADB or Fastboot drivers installed and Device Manager lists it as a Fasboot Titan device. Quite honestly this is very frustrating since I've been searching for days to no avail. I do not wish to update to Lollipop(Until it is available officially in my area), which is what most articles I found are for. I just want root access. I'm beginning to doubt if my device is even supported and its just an extremely well made clone.
I was trying this on Windows 8.1 Pro x64. Some people told me Fastboot drivers had some issues with 8.1 so I did my best to clean out old drivers and plug the phone into different USB ports. At first I was trying on my USB 3.0 ports, people also told me USB 3.0 has issues with FB, so I used my 2.0 ports on the front of my computer case. Again, people told me that I had to use ports directly on the motherboard, so I plugged the phone into my PC's back USB ports. I also tried a different micro USB cable, same result. At that time I figured it was probably Windows causing the problems so I pulled a hard drive from and old PC, hooked it up to my own and installed my old copy of Windows 7 Ultimate x64. I installed all the essentials, from ADB to Motorola Device Manager for the drivers. My phone is still not being recognized, although I did get to have it listed under ADB Devices by using USB Debugging, yet it appears offline, as shown in the image below. I figured it was my particular PC because its custom built with salvaged parts from another PC, so I tried the procedure from my family's Dell Optiplex (running win7 Home Premium x32) only to hit the same dead-end. At this point I'm tearing off hair from my head. I don't want to be bald yet! I'm only just turning 20 at the end of the month!
A few details:
Device: Moto G 2014 16GB XT1063. Android Kitkat 4.4.4 (5.0 has yet to be released for my area)
System Version: 21.11.14.titan_amxpr.amxpr.en.PR amxpr
Build number: KXB21.85-14

Inquisitor956 said:
yet it appears offline
Click to expand...
Click to collapse
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.

doppelhelix said:
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.
Click to expand...
Click to collapse
Thanks solved a problem I had on other laptop that would not show phone

doppelhelix said:
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.
Click to expand...
Click to collapse
Thank you! The RSA Fingerprint popup never appeared on my phone. I kept toggling USB Debugging on and off until it did. I managed to get the keys. Now I hit another wall... (image below)
I also tried it onto the Latin America page. This time no matter how I paste my code whether manually typing it or just copy/pasting, it always returns a popup with "Your input text was not recognized as a valid dataset. Please try again." This happens on Chrome, Firefox and even Internet Explorer and combined with the really slow loading of any official Motorola page I try to enter I'm guessing the forces of life itself are preventing me from unlocking this particular phone's Bootloader.

Inquisitor956 said:
preventing me from unlocking this particular phone's Bootloader.
Click to expand...
Click to collapse
Please have a look here: https://forums.motorola.com/posts/f2061da875

doppelhelix said:
Please have a look here:
Click to expand...
Click to collapse
Thank you once again! My device IS unlockable, I was told to wait for some time before requesting my unique unlock key, since the page has been having a few hiccups. I will report back if I was successful or not.
Edit: I successfully unlocked bootloader, installed TWRP and rooted. Thank you for your assistance!

http://developer.sonymobile.com/ instructions to Unlock Bootloader - problems

I'm having some problems following the instructions from http://developer.sonymobile.com/ regarding setting up Android Studios and the recommended 'fastboot' drivers on Win 10. I have done some vocoder development in the past and have a background in tech development and dedicated microprocessor programming, but i'm in over my head here. I could use a little help.
This is on a Sony Xperia Z Model C6606 4.3 T-Mobile variant Build 10.4.C.0.814. Even though I checked (by *#*#7378423#*#*) and got unlock bootloader allowed: No.; T-Mobile tier 2 technical support indicated that I should try the OEM method anyway. When I checked their site, I plugged in all the info about my phone and it indicated that I could unlock the boot loader. :Big Grin:
Now to the problems. This is where you hear the *blub blub* as I wade into the deep end.
Their instructions read in part, "1. Download and install the Android SDK."; which I did, including loading the Google USB drivers.
2. If you’re running Windows, you also need to download and install an updated Fastboot driver. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony & Sony Ericsson devices. Replace the original android_winusb.inf-file with the downloaded file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. If you can’t find the usb_driver folder, make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. If not, install the Google USB Driver Packager using the Android SDK manager.
Note: Google USB Driver Packager is ver. 11
After a visit to the device manager, following numerous tips from various sources and floundering about, I looked at the two INFs and found some discrepancies. The first is the one from the Sony 'fastboot driver' link above for their version of android_winusb.inf. The error I get here is based on the fact that this download contains NO CABS and the Google USB cabs do not have the installation files the Sony INF needs. On the other hand the Google USB 'extras' loaded by Android Studio do not include specific support for the Sony Xperia Z. :forehead slap:
Short version, I can't connect to fastboot.
I have tried both INFs and in each case with USB debugging enabled on the Z, I powered it down, held the VOL up button as I plugged the cable into the USB port. In all cases I got the blue light but no windows prompt asking for a driver! Even when I open a command window in the directory where the INF resides I DO NOT get a list of adb devices. If I enter 'fastboot devices' from the command prompt, I get the stock windows error that 'fastboot' isn't a recognized command.
If I could get a little direction here as to next steps, I would really appreciate it. Thanks.

Download an install flashtool, you'll find a link here in the forum. Can't search myself right now as I'm on the phone with slow Internet. In the thread is everything explained and it's very simple to use.

Oops
The correct folder is \AppData\Local\Android\sdk\platform-tools. No wonder it wouldn't load fastboot. Ultimately however, fastboot with the OEM unlock code didn't work. "FAILED (remote: Command not allowed)". BUMMER!
Thanks anyway. Now I'm off to flash what I can...

Best mehod is to install 15 second adb install-it installs adb and fastboot and can be open anywhere
give it a try
http://forum.xda-developers.com/showthread.php?p=48915118

ManagementCritic said:
....Even though I checked (by *#*#7378423#*#*) and got unlock bootloader allowed: No.....
Click to expand...
Click to collapse
Your bootloader cannot be unlocked. Blame your operator...

Hey ptmaniac,
Thanks for the response.
Yeah, I get that. I wrote in another thread how I had attempted to negotiate a remedy through both the OEM and the carrier; not that I expected a good result, but probing for what was left unsaid. I wanted to see if I could determine their reasons and motivation and whether they would consider any alternatives. The only admission was that they could, but would not. Best guess? It has to do with existing agreements they are unwilling to revisit.
ptmaniac said:
Your bootloader cannot be unlocked. Blame your operator...
Click to expand...
Click to collapse

@ManagementCritic
No problem,
In my country it's the same endless loop unfortunately... the carrier says i should talk to the oem, the oem says the phone was locked at carrier request and they can't do anything about it so i should talk to the carrier instead
I still blame myself from buying a full priced device locked to the carrier, i thought all of them could be unlocked anyway by submitting imei to the sony developer website... if i had researched a bit more i would have figured out that i should have bought it unlocked directly from the oem... lesson learned i guess.

Alcatel 1S 2019 (5024D) ROOT

Hello XDA Developers
I have been running for two days through Internet (including XDA) and try to find any valuable solution how to root my phone Alcatel 1S 2019 (5024D) on Windows 10.
I did:
- unlock developer mode and activated "OEM unlocking" and "USB debugging"
- installed "Minimal ADB and Fastboot" and when i connect the phone and run "adb devices" i can see my device on the list
- found, that in "Device manager" after connecting the phone i get a lot of: "Spreadtrum Phone" devices under "Other Devices" - those not workin properly, sice there is yellow exclamation mark next to the icon
- tried to install the drivers for the case from above - no luck. Keep getting errors while installing the drivers.
- tried: Framaroot https://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276 without luck.
I found:
- https://forum.xda-developers.com/alcatel-1/development/alcatel-1-root-achieved-t3970713, but there is no clear information how to get to the fastboot, and the PWR and VOL+ wont work as stated in the post
- https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445, but here I need to unlock bootloader, but when I am trying to do that by using "Minimal ADB and Fastboot" tool, i receive error:
FAILED (remote: Not implemet.)
finished. total time: 0.000s
I suspect that i should start from the drivers. But now i cannot find any clear information how to do that.
Obviously I tried to install some drivers, but without luck. I found dozens of step by step solutions how to properly implement drivers, but always get the same error (above) and can see in device manager, that after connecting the phone still not all devices has been installed properly.
Is someone from here have an experience in rooting that exact phone and will help me?

Hi there, have the same issue, is no driver problem. Seems at present this particular phone CANT be rooted Spent days on it too. Hope someone can help. Regards A.

Sorfeus said:
Hi there, have the same issue, is no driver problem. Seems at present this particular phone CANT be rooted Spent days on it too. Hope someone can help. Regards A.
Click to expand...
Click to collapse
Hello @Sorfeus. I am still fighting with that phone, but I am 80% sure, that there is no need anything else than normal Android USB drivers and ADB/fastboot. What I have noticed is when I have used original Alcatel USB cable and install above drivers still all commands you are able to run. I believe, that there is other problem though. Even when you unlock Developer options in Android and then switch on ability to unlock the bootloader actually you are not able to do this from the fastboot sight. The message I receive is that the option not exist. So you cannot even unlock bootloader not mention about running root ROM.
But again. I am not an expert but I think, that you do not need any spreadtrum drivers.

If only I had the boot image for my device Alcatel 1S (2020) 5028D.. then maybe I could have had root with magisk right now. Since no flashable firmware for my device is out there anywhere to be found and backing up boot partition on device requires root or a custom recovery in the first place, I seem unable to root it for now.
I was able to unlock bootloader with simple "fastboot flashing unlock" command though.
If you wanna do that, do the following: (and I assume you know how to type in the commands)
With "OEM unlocking" and "USB debugging" settings activated, connect phone to pc and type in command "adb reboot bootloader".
Next you type "fastboot flashing unlock" and "fastboot flashing unlock_critical".
Press volume up button on phone to confirm.
Now you type in command "fastboot reboot" and thats all.
My device is with Mediatek SoC and I had Mediatek drivers installed by Windows Update but I dunno if it is a driver issue you're having since you at least are able to run "adb devices" and you do see your device being listed there.
If you are able to unlock bootloader however you could proceed to try doing how this article describes on how to do (getdroidtips.com).
I have to also warn about that stock rom getdroidtips links to is for model 5024J not 5024D, flash a boot.img for wrong device model and you'll most certainly brick your device.
I managed to find stock roms 5024D while searching around the web but none that are free download or they require a password to unpack... could be scams, I dont know. Feels sketchy AF...
Anyways here is some of them I found and I guess these are good ones but needs a premium account:
Alcatel 1S 5024D EEA [needrom.com]
Alcatel 1S 5024D TMST [needrom.com]
Alcatel 1S 5024D ALAP [needrom.com]
Alcatel 1S 5024D ALRU [needrom.com]
[Update] found out this rom and is free download so I'll add it in here too:
Alcatel 1S 5024D ALRU
This might also be of interest if you want to know about how to extract and get the boot.img:
https://androidmtk.com/extract-spreadtrum-pac-file

Hello @RavZ75
Thank you for the clear information regarding unlocking. I didn't knew this command until you stated it in the above post.
Unfortunately I cannot check it, since I sold the phone.
Anyway, I believe that it is a good Idea to keep sharing rooting information in this thread since the question has been already asked.
Maybe someone else will use your knowledge to root it's phone.

Here's how I rooted mine: https://forum.hovatek.com/thread-32678.html
It's a long and complicated process, but it works.

FrescoLibra said:
Hi guys,
This is how I unlocked my bootloader and thats all I can do with this phone without Factory Firmware. I can not Root my device in any way. If anyone has a Scatter File for the Alcatel 1s 5024D 2019, please post so we can help each other out with this nasty phone's security
Bootloader Unlock: You need Linux, (eg) Parrot OS or Ubuntu!
Spreadtrum SC9863A - postmarketOS
wiki.postmarketos.org
Click to expand...
Click to collapse
That's only part of the process, but then you need to sign a modified boot/recovery image, edit the vbmeta image and flash both. It's all in the guide I linked above.

Hi all! I'm almost blown it. I don't know English I write through an interpreter. ROOT obtained in Russia.
Alcatel OneTouch 5024D 1S - Обсуждение - 4PDA
Alcatel OneTouch 5024D 1S - Обсуждение, Смартфон, 5.5"
4pda.to
This is a link to the bootloader unlock and firmware instructions with root 01003.
Alcatel OneTouch 5024D 1S - Обсуждение - 4PDA
Alcatel OneTouch 5024D 1S - Обсуждение, Смартфон, 5.5"
4pda.to
This is the forum itself in the header of which there is a lot of useful things. TWRP and Magisk update.
With an automatic translator, everything will be clear.
Good luck with root rights.

Question How to unlock bootloader for Mi 11 Ultra

Hello, I'm trying to figure out how to unlock my phones bootloader. I already went through all the developer settings, linked my phone to mi account. When I go into Fastboot mode and plug in my phone to my computer, to unlock tool doesn't find or read my phone for me to unlock it. After doing some research, I think I have to install drivers? I'm kid of confused on that part or where to download these drivers from.

Search for Xiaomi a
nickxzr said:
Hello, I'm trying to figure out how to unlock my phones bootloader. I already went through all the developer settings, linked my phone to mi account. When I go into Fastboot mode and plug in my phone to my computer, to unlock tool doesn't find or read my phone for me to unlock it. After doing some research, I think I have to install drivers? I'm kid of confused on that part or where to download these drivers from.
Click to expand...
Click to collapse
Install Xiaomi drivers and ADB package

speedtripler said:
Search for Xiaomi a
Install Xiaomi drivers and ADB package
Click to expand...
Click to collapse
How can i do this? any links 0rstep by step please!

Start at mi unlock official site , you will get the prompted from there on the steps required

Could be that you are not making a proper connection between phone and PC, it needs to show up and install properly. I had the same problem on my rather elderly desktop, tried again on my laptop using a USB 3 cable, it worked.

Use my guide for 10 Ultra just for the unlock process. Here's a link to it from my mega page
File on MEGA
mega.nz
Please remember, the rest of the guide is for 10 ultra, not 11.