Develop Bugs

why can't I install these 3rd party programs???

Just got the Verizon Touch Pro 2 and am trying to install a few third party programs like:
List Pro
Magic Button
Splash ID
Memaid
I connect my device when trying to install, it says to check my mobile device screen to see if further steps are needed, but nothing is showing and nothing is happening.
Can someone please advise?
Thanks so much!
Cat

CatB said:
Just got the Verizon Touch Pro 2 and am trying to install a few third party programs like:
List Pro
Magic Button
Splash ID
Memaid
I connect my device when trying to install, it says to check my mobile device screen to see if further steps are needed, but nothing is showing and nothing is happening.
Can someone please advise?
Thanks so much!
Cat
Click to expand...
Click to collapse
And you're sure that the apps didn't end up showing up in your programs list?
First, when you plug your phone to the PC, does it show any other signs of conenction? You should first get an option on the device screen to choose between "disk drive" and "active sync"...when you're installing apps from your PC desktop to the phone, you need to be connected via the active "active sync" option. Once you are, you'll see either Active Sync (on XP) or Windows Mobile Device Center (on Vista/7) open on your desktop. You may have already gotten that far, I just wanted to make sure you're connected properly that way.
The next thing to try would be to install the apps straight from the phone, instead of via the PC. To do that, just connect the phone via "disk drive" option, copy the .cab file over to the phone (on to the SD card is best), and just run it from there to install straight to the phone. Running the desktop .exe installer just automates that step for you, but otherwise it's the same process. Running the .cab file from the phone bypasses any possible issues with the active-sync connection.
I've attached the .cab for the memmaid app here, try that one first.

sirphunkee said:
And you're sure that the apps didn't end up showing up in your programs list?
First, when you plug your phone to the PC, does it show any other signs of conenction? You should first get an option on the device screen to choose between "disk drive" and "active sync"...when you're installing apps from your PC desktop to the phone, you need to be connected via the active "active sync" option. Once you are, you'll see either Active Sync (on XP) or Windows Mobile Device Center (on Vista/7) open on your desktop. You may have already gotten that far, I just wanted to make sure you're connected properly that way.
The next thing to try would be to install the apps straight from the phone, instead of via the PC. To do that, just connect the phone via "disk drive" option, copy the .cab file over to the phone (on to the SD card is best), and just run it from there to install straight to the phone. Running the desktop .exe installer just automates that step for you, but otherwise it's the same process. Running the .cab file from the phone bypasses any possible issues with the active-sync connection.
I've attached the .cab for the memmaid app here, try that one first.
Click to expand...
Click to collapse
Thanks so much for the reply! I actually managed to get the programs installed via my ActiveSync connection - finally! Not sure what the problem was before.
I plan on keeping your instructions, though, in case this happens again. Thanks so much for the reply.

CatB said:
Thanks so much for the reply! I actually managed to get the programs installed via my ActiveSync connection - finally! Not sure what the problem was before.
I plan on keeping your instructions, though, in case this happens again. Thanks so much for the reply.
Click to expand...
Click to collapse
No problem, glad to help As long as you got it working, that's what matters! Feel free to come back if you need any more help.

sirphunkee said:
No problem, glad to help As long as you got it working, that's what matters! Feel free to come back if you need any more help.
Click to expand...
Click to collapse
I will, believe me! In fact, I have only had my TP2 for about 3 days but have a few "issues" going on, so I will start a new thread and am looking forward to getting some help.
I love support forums! They rock

Problem with HTC Diag driver, and MSL#... Please help!

So I tried following one of the guides posted here at XDA to retrieve my MSL#.
** EDIT **
XDA FORUMS WILL NOT allow me to post links, because I have a new account, and it hasnt been approved. So I am just going to post the links to the screenshots without the "http" in front. I also had to remove the "." from the first part of the web address. So "google.com" would be "google com". You will have to manually copy and paste the URL, and add the periods to first part of the address.
IF A MOD IS READING THIS CAN YOU PRETTY PLEASE APPROVE MY ACCOUNT? Thanks!
I followed this guide:
forum xda-developers com/showthread.php?t=697487#
I downloaded the pre-requisites, and started to follow the steps.
I am on Windows 7 32bit, and these instructions are for Windows 7 64bit.
Once I cam to the section where I chose my drivers I chose the ones for x86 since I am running 32bit.
It installed the drivers fine. However, it installed the device under the "PORTS" section of the "Device Manager".
The screenshots for the instructions show the device being installed under the "MODEMS" section.
So I thought I did something wrong, and before doing any further research, I decided to delete the device that was installed under the "PORTS" section. I figured by doing this I could start from scratch, and correct whatever it was that I did wrong. Dumb move!!!
I removed the drivers from "C:\windows\system32\drivers" and also from "C:\windows\system32\driversstore\filerepository"
I unplugged my phone, rebooted my machine, dialed "##3424#" to enter diagnostic mode, connected my phone to the computer, and it DID NOT recoginze any new hardware.
I also tried removing any references from regedit for "htcdiag", which is the driver that was installed.
This produced the same result.
I have attached screenshots of the devices currently in my device manager.
Device Manager Screenshot #1:
img46 imageshack us/img46/8923/screenshot1ka.jpg
Device Manager Screenshot #2:
img163 imageshack us/img163/1479/screenshot2m.jpg
Device Manager Screenshot #3:
img202 imageshack us/img202/9158/screenshot3hj.jpg
Please help me get this working!
Thank you!

Have you tried msl reader from the market ?

mendez_v said:
Have you tried msl reader from the market ?
Click to expand...
Click to collapse
No, but at this point I am less worried about the MSL, and more worried about getting the android phone to show up properly under the device manager. When I rooted the phone I installed a modified HTC USB Driver, and then my phone showed up under device manager. As you can see from the screenshots my phone does not show up in device manager AT ALL anymore.

I know this was a rookie move, but someone must have done this before, or at the VERY least must have some suggestions on how to get the drivers reinstalled on my machine for my phone.
Anyone.... Bueller? Bueller?

** ONE MORE BUMP **
Perhaps all the useful contributors were on an extended Labor Day vacation.

guht said:
No, but at this point I am less worried about the MSL, and more worried about getting the android phone to show up properly under the device manager. When I rooted the phone I installed a modified HTC USB Driver, and then my phone showed up under device manager. As you can see from the screenshots my phone does not show up in device manager AT ALL anymore.
Click to expand...
Click to collapse
Have you plugged the phone in and tried "scan for hardware changes"?
Still no luck.....The HTC website has a support section with drivers you can download.
OR-
Do you have the android sdk installed on your computer? There is a usb driver package you can use in the sdk.
If you still cannot get it to connect, then flash a rooted stock rom and see if your computer can connect then.
As far as your MSL, just call Sprint and ask them. The rep will ask why you need it. Just tell them your phone has been acting odd and that you are going to do a reset, which you have done before in the past ; ). They will then transfer you to a tech which will ask you again why you need it. Just respond the same about doing a reset, which you have done many times before.....you will then have your MSL - takes only a couple of minutes.

[HOWTO] Change PRL on Virgin Mobile LG Optimus V (5/06/2011)

I saw this information posted elsewhere in pieces and thought I'd bring it together. I didn't make this procedure, but I can confirm that it works (and so can many others now). This is absolutely for the LG Optimus V and no other phone. Do not do this unless you understand what a PRL is and why you are doing it. There is some risk in doing this. I'm sure Virgin and Sprint would not be happy to know of this mod. It might even be blocked in the future by changing the way Sprint's towers filters Virgin users. Do this at your own risk! I take no responsibility!
1. Requirements:
Windows
LG Optimus V USB Serial Drivers (updated 3/22/2011)
Read the first few pages of this thread if you have driver issues. You can also try this. Thank you rjones1981.
You don't need to have a rooted phone to do this.
2. Get Your MSL Code:
New Technique (thanks to mmarz)
Log into your Virgin Mobile account.
Click this link
Although you get a 404 error page, search the page for "msl:"
The six numbers after msl: are your MSL code. Write them down.
Old Technique
Download CDMA Workshop 3.6.0 Demo
Turn on USB Debugging, and connect your phone to your PC.
Open Device Manager.
Ports > LGE Android Platform USB Serial Port > Properties > Port Settings > Advanced > COM port number
Change the value to a port number below 10. (demo restriction of CDMA Workshop)
Run CDMA Workshop
Select the proper port from step 4. Hit "Connect."
Under the "Security" tab, find "SPC/User Lock."
Change the drop down menu to "LG method," and click "Read."
Write down the number that appears in the box. This is your MSL code. Now close CDMA Workshop, we won't need it anymore.
3. Update Your PRL:
Connect your phone to your computer using a USB cable.
Open Device Manager.
Ports > LGE Android Platform USB Serial Port > Properties > Port Settings > Advanced > COM port number
Make a note of your COM port number.
Download and install QPST v2.7.
Open "QPST Configuration".
In the "Ports" tab, if your com port isn't listed, select "Add New Port" and write in your com port as "COM#" (# being the number you noted in step 4). Verify that your com port is listed.
Make sure your phone appears in the the "Active Phones" tab.
Click "Start Clients." Choose "SERVICE PROGRAMMING." Select your phone.
Click "Read from Phone."
Enter your MSL code when promoted. (It will not finish reading from your phone. It will stop near the end and report an error. This is normal.)
Hit "Save to File" to backup your phone's settings and PRL to a .qcn file. (Optional but recommended)
Select the "Roaming" tab.
Under "Preferred Roaming Enable" choose "Browse..." and select the 01115.prl or 61677.prl file. (attached below, also see update 6)
Under the "System" tab change "Roam Preference" to "Home only". (Optional but recommended)
Click "Write to Phone," and your phone should immediately reboot. Do not disconnect your phone until it has booted back up.
To confirm that this worked, go into settings > about phone > status. You should have the new PRL and all that it entails. To reverse the process, follow the same steps but use the Virgin 61007 PRL or use your .qcn backup by selecting "Load from File" in the QPST SERVICE PROGRAMMING.
If you try different PRL's and get better service, please post your results here.
Update 1: Even though you can enable roaming using the QPST System tab under Roam Preferences, and you can actually connect to the Verizon towers, your calls will prompt you for a credit card, and your data will not work while roaming. I recommend leaving roaming on "Home Only." Even though you can't roam, an updated PRL will give you better coverage on Sprint's network. There are already reports that this fixes the 3G connectivity issue.
Update 2: I have created a hybrid PRL numbered 61676. I manually picked that number, and it may conflict with the PRL # of one released in the distant future, just fyi. I created the PRL by taking 60676 and removing a few roaming entries to make room. I then compared the entries in 61007 to it, and added all the non-roaming entries that 60676 lacked. It will almost be impossible to figure out if these additional entries help at all, but they can't hurt. I'm attaching 61676 below if you guys want to test it out. I promise nothing, but so far my phone has not complained about using it. Let me know how it works out if you do try it.
Update 3: Added new 60677 and a new hybrid 61677
Update 4: Proof that it is worthwhile to do!
Update 5: Added 01115 PRL. It is the latest from Sprint. Don't know why it is numbered like it is. I'm not going to make another hybrid prl for it because it is too time consuming, and I see no benefits from it.
Update 6: I'll no longer keep this updated for new PRL's. You can find new ones as they are posted here: http://cid-eabe29f3770d8d15.skydriv...Public/PRLs?ppud=4&wa=wsignin1.0&sa=636785150
Update 7: Newest PRL posted here: http://forum.xda-developers.com/showpost.php?p=17690691&postcount=201
Roaming does not work on Virgin Mobile! If you do roam, you will not receive your phone calls or texts, and you won't be able to make calls or send texts! Your data will also not work if roaming. Set your "Roam Preference" to "Home only", and you don't have to worry about roaming.

This was never in pieces, why don't you give proper thanks to the original poster from android central?
http://forum.androidcentral.com/opt...irgin-mobile-prl-61007-needed-enter-help.html

xtravbx said:
This was never in pieces, why don't you give proper thanks to the original poster from android central?
http://forum.androidcentral.com/opt...irgin-mobile-prl-61007-needed-enter-help.html
Click to expand...
Click to collapse
Haha, you should be asking why he doesn't give proper thanks to me. I wrote this, and he copied it. Before I wrote it, it was spread out over a bunch of posts. I don't really care either way. I didn't invent the phone, the programs, or the procedure. I'm just glad the info is out there.
http://forum.androidcentral.com/opt...prl-61007-needed-enter-help-5.html#post715849
I guess he did reference me.

I've installed all of the proper drivers but my phone is not showing up in device manager. i have a rooted V on sublimewulf's stock rom.
my cpu is running 64bit win7. after a little research i believe the sprint prl will help me quite a bit in my hometown.
is there anything thing i can do to set com for my phone?
UPDATE found my phone its not using the lg drivers, its using adb sooner driver but i cant figure out how to get it ti show in ports tab

i shot jfk said:
I've installed all of the proper drivers but my phone is not showing up in device manager. i have a rooted V on sublimewulf's stock rom.
my cpu is running 64bit win7. after a little research i believe the sprint prl will help me quite a bit in my hometown.
is there anything thing i can do to set com for my phone?
UPDATE found my phone its not using the lg drivers, its using adb sooner driver but i cant figure out how to get it ti show in ports tab
Click to expand...
Click to collapse
Uninstall the other drivers and install the correct ones.

Does anyone know how to fix the "Failed..phone does not answer" response I get from CDMA when I try to read the spc using the lg method?
This is something I'd really like to try.
Thank you for taking the time to write the guide!

overthinkingme said:
Does anyone know how to fix the "Failed..phone does not answer" response I get from CDMA when I try to read the spc using the lg method?
This is something I'd really like to try.
Thank you for taking the time to write the guide!
Click to expand...
Click to collapse
Which version of CDMA Workshop are you using? It works fine using the demo linked above. You may want to also try reinstalling the drivers. After you click connect, does pressing the read button next to it return an error?

Yeah, i must be missing something here, I installed what should be the right drivers I'd thought but when I plug the phone in there's nothing in device manager under ports... There's an "ADB Interface" now with "Android Sooner Single ADB" under it. There's a Google mass Storage USB Device under Disk Drives, and a new USB Mass storage device under Universal Serial Bus...
So what am I doing wrong and how do I fix it?
Thanks for any help!

danwil77 said:
Yeah, i must be missing something here, I installed what should be the right drivers I'd thought but when I plug the phone in there's nothing in device manager under ports... There's an "ADB Interface" now with "Android Sooner Single ADB" under it. There's a Google mass Storage USB Device under Disk Drives, and a new USB Mass storage device under Universal Serial Bus...
So what am I doing wrong and how do I fix it?
Thanks for any help!
Click to expand...
Click to collapse
Same issue here. If I install the phone's USB drivers from the LG website (http://www.lg.com/us/mobile-phones/LG-VM670.jsp, under "Resources" tab) I get an "ADB Interface" section in the device manager with "Android Sooner Single ADB" under it, exactly as the previous poster described.
If I uninstall those and install the drivers linked to in the OP, I then get told that no driver was found for my device when I plug in my phone. It should be noted that the page linked to by the original poster identifies the drivers there as being for the LG-LS670, which would be the Optimus S... The Sprint version of the phone. The Optimus V is technically the LG-VM670. (See http://en.wikipedia.org/wiki/LG_Optimus_One#LG_Optimus_S_-_LS670_-_Sprint).
Could this be why my system is refusing to use those drivers?
Are those of you who've connected to your Optimus V with the drivers linked to in the OP all running hacked ROMs?

Kate6 said:
Same issue here. If I install the phone's USB drivers from the LG website (http://www.lg.com/us/mobile-phones/LG-VM670.jsp, under "Resources" tab) I get an "ADB Interface" section in the device manager with "Android Sooner Single ADB" under it, exactly as the previous poster described.
If I uninstall those and install the drivers linked to in the OP, I then get told that no driver was found for my device when I plug in my phone. It should be noted that the page linked to by the original poster identifies the drivers there as being for the LG-LS670, which would be the Optimus S... The Sprint version of the phone. The Optimus V is technically the LG-VM670. (See http://en.wikipedia.org/wiki/LG_Optimus_One#LG_Optimus_S_-_LS670_-_Sprint).
Could this be why my system is refusing to use those drivers?
Are those of you who've connected to your Optimus V with the drivers linked to in the OP all running hacked ROMs?
Click to expand...
Click to collapse
I uploaded the drivers myself and fixed the link in the original post. Uninstall and delete (using device manager) the "Android Sooner Single ADB" driver and try unplugging and reinserting the USB cable.. If the device shows up as unrecognized, Right click on it in the device manager window> Update Driver Software> Browse my Computer> Let me pick from a list> All> (wait for the list to be populated)> LG Electronics> LGE Android Platform USB Serial.

freddysam said:
Which version of CDMA Workshop are you using? It works fine using the demo linked above. You may want to also try reinstalling the drivers. After you click connect, does pressing the read button next to it return an error?
Click to expand...
Click to collapse
CDMA 2.7, I am going to try the demo and see if that helps.
Read also returns the same error. It connects fine though.
EDIT:
Figured it out!
Don't connect to the modem port.
I should have read the directions more slowly.

freddysam said:
I uploaded the drivers myself and fixed the link in the original post. Uninstall the other drivers you are using and install these. If the device shows up as unrecognized, Right click on it in the device manager window> Update Driver Software> Browse my Computer> Let me pick from a list> All> (wait for the list to be populated)> LG Electronics> LGE Android Platform USB Serial
Click to expand...
Click to collapse
Okay... I've uninstalled any LG drivers I previously had installed, installed the drivers you uploaded.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Turned on USB Debugging on my phone and plugged it in. Device Manager shows this:
I right click, "Update Driver Software" => "Browse my computer for driver software" => "Let me pick from a list of device drivers on my computer"... This brings me here:
Unchecking "Show compatible hardware" gives me a lot more options, including a couple of references to the "HTC Dream" (which I believe is another name for the T-Mobile G1, the first widely available Android phone)... But nothing about USB Serial.
The only thing I have showing up under ports is a "Printer Port (LPT1)." What am I doing wrong? Any clue?

Same exact results here as above, can't get the USB Serial drivers to show up anywhere after uninstalling and installing the new drivers that were uploaded...
I've tried it on Windows 7 Home 32bit and also Windows 7 Ultimate 64bit with the same results (of course i'd already tried the install with the other drivers on both machines... Should I dig out an XP machine to try this on?
Has anyone with an un-rooted Optimus V gotten this to work?
I hope after all this trouble (assuming i get it to work) it actually does help with all the 3g data outages like i've been promised

Kate6 said:
Okay... I've uninstalled any LG drivers I previously had installed, installed the drivers you uploaded.
http://www.kate6.org/Screen0.png
Turned on USB Debugging on my phone and plugged it in. Device Manager shows this:
http://www.kate6.org/Screen1.png
I right click, "Update Driver Software" => "Browse my computer for driver software" => "Let me pick from a list of device drivers on my computer"... This brings me here:
http://www.kate6.org/Screen2.png
Unchecking "Show compatible hardware" gives me a lot more options, including a couple of references to the "HTC Dream" (which I believe is another name for the T-Mobile G1, the first widely available Android phone)... But nothing about USB Serial.
http://www.kate6.org/Screen3.png
The only thing I have showing up under ports is a "Printer Port (LPT1)." What am I doing wrong? Any clue?
Click to expand...
Click to collapse
You didn't uninstall the Android Sooner Single ADB Interface Driver. Right click on it and select Uninstall. When it asks you to confirm, check the box to delete the drivers. Then follow the directions I posted to manually add the correct driver.

freddysam said:
Haha, you should be asking why he doesn't give proper thanks to me. I wrote this, and he copied it. Before I wrote it, it was spread out over a bunch of posts. I don't really care either way. I didn't invent the phone, the programs, or the procedure. I'm just glad the info is out there.
http://forum.androidcentral.com/opt...prl-61007-needed-enter-help-5.html#post715849
I guess he did reference me.
Click to expand...
Click to collapse
Hmmmm, really? OK... Yes, it was spread out (in one thread, not multiple). But you gave no mention where you obtained the info from. But thanks for cleaning it up, cause it did help a few people get going.

freddysam said:
You didn't uninstall the Android Sooner Single ADB Interface Driver. Right click on it and select Uninstall. When it asks you to confirm, check the box to delete the drivers. Then follow the directions I posted to manually add the correct driver.
Click to expand...
Click to collapse
God, I hate Windows. There's no Mac-native or Linux-native programs that can do this, are there?
At this point there was nothing to right click on, which I assume means that when I uninstalled the drivers through the "Uninstall Programs" control panel it left some files behind that were mucking up the process. So I went ahead and reinstalled the driver's from LG's, website, reconnected my phone to get the "Sooner Single" to show up, then right clicked on it, chose uninstall and make sure Delete was selected.
Then I went in the Uninstall control panel to make sure everything was deleted. Then I deleted anything that looked like it was owned by LG under C:\Program Files, C:\ProgramData and C:\Windows\System32\Drivers.
Then I installed your drivers, as linked in the first post and plugged my phone back in. And it showed back up as the "Sooner Single" interface, but had a "Device Cannot Start" error on it... Which I'm guessing means that driver was actually in your package. Right clicked, uninstall, make sure I check Delete... Unplug and replug my phone back in. This time I get an "Android USB Device" that the system was unable to find a driver for.
So I followed your directions.... Update Driver, Search my computer, etc. There appears to be both an "LG Electronics, Inc" entry and an "LG Electronics Inc" (without the comma) entry. One of them has two Serial Port drivers, and two NMEA GPS Port drivers, the other has three of each. I've at this point tried all five of the Serial Port drivers.
The ones from the group of three (I can't remember if that's the one with the comma or without) required me to reboot my computer when I installed them and then, after the reboot, had a "Device cannot start" on them. The other two managed to start, but when I hit the "Connect" button in the CDMA Workshop it says "Failed to open COMx"... I tried switching around between COM1, COM3, COM5 (making sure to always have the same port selected in both the device manager and the CDMA Workshop)... I tried messing with the baud rate setting, again matching them in both locations.
No go.
I'm doing all of this on two machines, btw... An installation of Windows 7 64 bit running under Parallels Desktop on my Mac, and an install of Windows 7 32 bit running on a friend's computer with no virtualization. Getting identical results on both. Well, I did discover that my friend's computer freezes up mid-POST if my phone is plugged into its USB port while it's rebooting, which was just a little bit of extra frustration to deal with.
Any more hints?
I'd really like to get this working... I've had data outages of several hours almost every day for 2-3 weeks now, usually during prime time usage hours (i.e. around noon, and around 4pm to 7-8pm.) Would love anything that would make the stop or even lessen it.

Wow Kate, ok. Install one of the drivers that is labeled "LGE Android Platform USB Serial Port", I don't think it matters which one. Then make sure no other com ports conflict with the com port you choose. To make sure, restart your computer after changing the port and verify it didn't change. You obviously have debugging enabled on your phone, otherwise the driver wouldn't even appear....Hmmm. I agree that windows makes all of this so much harder than it has to be. The problem with the drivers is a perfect example of how something so simple requires a full days worth of trial and error to fix.
Takenover83 said:
Hmmmm, really? OK... Yes, it was spread out (in one thread, not multiple). But you gave no mention where you obtained the info from. But thanks for cleaning it up, cause it did help a few people get going.
Click to expand...
Click to collapse
Actually, the only part I got from your thread was the procedure to use the Demo version of CDMA workshop to get the MSL code. The rest a pieced together from XDA posts and forums:
http://forum.xda-developers.com/showthread.php?t=940612
http://mark.cdmaforums.com/QPSTSetup.htm
http://www.evanvaughan.com/default.aspx?pageid=56EED25AA49D4B1C
I also didn't use pirated software to get the VM PRL. When you read from the phone using QPST, even though it gives an error, it does download the phone's PRL. You can then save that to a QCN file with the rest of the phone settings. You can then extract the PRL using QPST's Roaming List editor. You should know that the pirated copy of CDMA workshop that is floating around online has been flagged as containing a virus multiple times.
Again, you copied and pasted my entire post and gave no reference to me. I did not complain because this isn't anything besides a walk through.
I'm going to be posting a new PRL soon just for VM users that has all of the roaming features of 60676 removed and adds in the difference from 61007. Feel free to post it in your thread too.

Again, you copied and pasted my entire post and gave no reference to me. I did not complain because this isn't anything besides a walk through.
Click to expand...
Click to collapse
I didn't? Maybe you should go read your post #3 again. You admit to me referencing you. I did mention it and went as far to call it "nice". That is more then you did for me.

Takenover83 said:
I didn't? Maybe you should go read your post #3 again. You admit to me referencing you. I did mention it and went as far to call it "nice". That is more then you did for me.
Click to expand...
Click to collapse
Haha, I'm really not looking for a pissing match, and we both have links to each others threads. So I'm just going to leave it at that.
I posted the new PRL if you want to try it out.

followed your steps and got the same results as kate.
getting extremely frusterated with the process.

Found why adb not recognizing some 6.2.2 kindle's

My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized

Th3-Chronikk said:
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Click to expand...
Click to collapse
Look here for hardwareid http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
I think this is an attempt to prevent root from amazon. However, if you know the procedure, the game is not over.

THANHVO31 said:
Look here for hardwareid http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
I think this is an attempt to prevent root from amazon. However, if you know the procedure, the game is not over.
Click to expand...
Click to collapse
That link you posted doesn't use my same ids

Th3-Chronikk said:
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Click to expand...
Click to collapse
Once you find the solution can you please let me know as well?
I am really interested in this!
btw, I have another Kindle that is working and gets recognized by computer in seconds and the other that has been bricked for over 2 months :'(
EDIT: and I made a huge mistake and i had not put in the bootloader (FIREFIREFIRE) on my bricked kindle, however, I took extra precaution and put it on my working kindle and to prevent it even further I am not using any roms and only using GoLauncher EX, googleframework, Superuser(root), and Market
as some roms are unstable and ALWAYS have a problem that something is not working correctly!

umarsl said:
Once you find the solution can you please let me know as well?
I am really interested in this!
btw, I have another Kindle that is working and gets recognized by computer in seconds and the other that has been bricked for over 2 months :'(
Click to expand...
Click to collapse
I will post it on a new thread so you will know and I cant find anyone to help me with these ids

Th3-Chronikk said:
I will post it on a new thread so you will know and I cant find anyone to help me with these ids
Click to expand...
Click to collapse
I just give you the fishing rod, not fish
Once your KF stuck at Kindle Fire, you can get your HardwareID
You should know the file call "android_winusb.inf" that you'll point to that to install driver for your bricked KF.
put the following
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\Vid_1949&Pid_0006&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0100
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006
Click to expand...
Click to collapse
And try again.
Goodluck

THANHVO31 said:
I just give you the fishing rod, not fish
Once your KF stuck at Kindle Fire, you can get your HardwareID
You should know the file call "android_winusb.inf" that you'll point to that to install driver for your bricked KF.
put the following
And try again.
Goodluck
Click to expand...
Click to collapse
Didn't work

Th3-Chronikk said:
That link you posted doesn't use my same ids
Click to expand...
Click to collapse
The hardware IDs in that link look identical to yours, and I think every other Kindle Fire I've seen. Yours don't look unusual.

I'm having the same damn issue, my 6.2.2 kindle is not recognized by adb. The weird thing is that sometimes it does see the device and then it disappears? The driver ID's that are posted are identical to the ones that are included with KFU.
If anyone figures this out please let me know!
Troy.

This post is ridiculously long and is kind of a rant... but Ive had it with all these "cant find adb in KF" posts and yes its a problem, and yes amazon devs are prob laughing at us but the answer is not on XDA forums or anywhere its not in Vashypooh's Teamviewer, its in your computer its in your Fire and you need to make it happen. Im probably going to regret posting this, but whatever, its a crap answer for a crap question.
Look - Ive messed around with just about everything from the kindle to the computer to using different computers to performing downgrades from Win8 to Win7 and trying to figure out why my Fire sometimes can be seen by adb and why sometimes it cannot...
I cant explain everything in one post its too much information but you need to mess around.
Without explaining these are the steps I took and I cant tell you which ones work because its like a very messy environment on a computer and everyones got different flavors and different variables...
try these (in no particular order) try them all at once or try them in pieces, but you need to reboot after each instance (think about your science teacher explaining why scientific experiments need to be controlled and clean and precise so as to eliminate any variables which may interfere with the end result!)
Do you have admin rights over your computer? If you dont... get it.
delete the .android file (this will have adb_usb file in it) try again. Watch for your driver action you need to know whats going on... you need to make your computer verbose so its reporting all its activity
Uninstall and delete (FULLY DELETE!) the Kindle Fire Utility if you have it.
Uninstall and delete (FULLY DELETE) the Android SDK if you have it. All of them if you have more than one.
Uninstall and delete (FULLY DELETE) any such programs you have that are dedicated to using adb.exe such as say AndroidCommander Droid Explorer or any of that stuff they are gone!
If you want to know if theres any other stuff on your computer, and dont really know how to use anything other than Windows Explorer, (shame on you) then install the greatest file finder I know - Everything.exe http://www.voidtools.com/download.php install that crap and then fix the options to "show hidden files and system files and hide nothing) and then when its set up, type in the search "adb" and "android" and "winusb" instances, then go to their parent folder and delete the whole thing, clear out your trash, uninstall all drivers, delete them, and UNPLUG all connected android devices so they dont throw stuff back into system and reboot the computer. You want a nice virgin promiscuous machine when it reboots, so you can pop its cherry with one Kindle Fire that needs to get its adb on.
install a verbose driver program (i am fond of USBDeview http://www.nirsoft.net/utils/usb_devices_view.html) make sure whatever program you use is VERBOSE and reports every activity, like in the options make everyhting so that it reports, displays and hides nothing. UNINSTALL AND DELETE EVERYTHING that indicates it could be connected to 1. ADB 2. Device 3. anything freaking android. Actually, I have been so frustrated in the past that I actually uninstalled every single driver on the computer....I highlighted all my drivers and Uninstalled... and they all uninstalled.. my mouse stopped working my keyboard stopped working but screw that, shut down the computer (irrelevant to whatever winblows geeks tell you it is NOT harmful to crash-power down your windoze machine) and then upon rebooting it will install all its relevant inner drivers) which may be bad for some of you if you have a complicated setup but whatever all I wanted was to get adb working at the expense of other drivers. Everything will reinstall when its connected, thats how drivers work -- you connect it and it starts talking to windows and **** happens right there.
So, delete everything! Reboot! you need to reboot your machine after each major change, because its just to eliominate the chances of not being able to communicate if winblows needs to reboot to be fresh.
If you have deleted uninstalled all of these android-related drivers... and if you have made your machine verbose, so that its not hiding information or thinking you are not interested in whats going on in system, and then you reboot, chances are when you first plug that KF in to your system, **** will happen. You just need to make it work.
you cant just sit around for two months waiting for someone to give you the fix -- the answer is right there in your hands... you just have to make it stick. Its there. Just gotta tweak the hell out of your computer to make it happen. If it doesnt work... keep trying... try again. if that doesnt work, change something. keep on tweaking, keep on shaking the nest and itll pop in.
HOWEVER I checked out the Jayceooi website and he/she has a good case to make there -- and if "it dont work" then thats because you are not trying hard enough.
Now.. all I can say is Ive lost adb.. and Ive found it again.. and I still have it because I have not installed ANY other android related or SDK ADB related programs after I found it.... everytime I do... everytime I attach my other HTC devices, it messes up everything and I repeat the above all over again

Mine are
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
And I can't seem to get recognized although the "Composite" piece of it is working...I cannot get ADB to see it. What do I need to add to my file?
The obvious thing to do is make the entries match this, but that's obviously not it. I do need help, it's not a crap question, and I have done everything to get this going.

p-niiice said:
Mine are
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
And I can't seem to get recognized although the "Composite" piece of it is working...I cannot get ADB to see it. What do I need to add to my file?
The obvious thing to do is make the entries match this, but that's obviously not it. I do need help, it's not a crap question, and I have done everything to get this going.
Click to expand...
Click to collapse
android update adb
add 0x1949 on its own line to adb_usb.ini in C:\users\<username>\.android\adb_usb.ini
save the file
adb kill-server
adb start-server
adb devices

I had all these problems, but what fixed mine was manually typing in the "0x1949". I initially was copying and pasting, but I seen somewhere else that it was causing problems. Its the only text/line in the file.
I have absolutely no clue as to why this fixed it, but it did for me.

jcc2z said:
I had all these problems, but what fixed mine was manually typing in the "0x1949". I initially was copying and pasting, but I seen somewhere else that it was causing problems. Its the only text/line in the file.
I have absolutely no clue as to why this fixed it, but it did for me.
Click to expand...
Click to collapse
Thanks - doing this plus the hardware ID lines earlier in the thread got me further, but adb still isn't picking up the composite device.

androidcues said:
This post is ridiculously long and is kind of a rant... but Ive had it with all these "cant find adb in KF" posts and yes its a problem, and yes amazon devs are prob laughing at us but the answer is not on XDA forums or anywhere its not in Vashypooh's Teamviewer, its in your computer its in your Fire and you need to make it happen. Im probably going to regret posting this, but whatever, its a crap answer for a crap question.
Look - Ive messed around with just about everything from the kindle to the computer to using different computers to performing downgrades from Win8 to Win7 and trying to figure out why my Fire sometimes can be seen by adb and why sometimes it cannot...
I cant explain everything in one post its too much information but you need to mess around.
Without explaining these are the steps I took and I cant tell you which ones work because its like a very messy environment on a computer and everyones got different flavors and different variables...
try these (in no particular order) try them all at once or try them in pieces, but you need to reboot after each instance (think about your science teacher explaining why scientific experiments need to be controlled and clean and precise so as to eliminate any variables which may interfere with the end result!)
Do you have admin rights over your computer? If you dont... get it.
delete the .android file (this will have adb_usb file in it) try again. Watch for your driver action you need to know whats going on... you need to make your computer verbose so its reporting all its activity
Uninstall and delete (FULLY DELETE!) the Kindle Fire Utility if you have it.
Uninstall and delete (FULLY DELETE) the Android SDK if you have it. All of them if you have more than one.
Uninstall and delete (FULLY DELETE) any such programs you have that are dedicated to using adb.exe such as say AndroidCommander Droid Explorer or any of that stuff they are gone!
If you want to know if theres any other stuff on your computer, and dont really know how to use anything other than Windows Explorer, (shame on you) then install the greatest file finder I know - Everything.exe http://www.voidtools.com/download.php install that crap and then fix the options to "show hidden files and system files and hide nothing) and then when its set up, type in the search "adb" and "android" and "winusb" instances, then go to their parent folder and delete the whole thing, clear out your trash, uninstall all drivers, delete them, and UNPLUG all connected android devices so they dont throw stuff back into system and reboot the computer. You want a nice virgin promiscuous machine when it reboots, so you can pop its cherry with one Kindle Fire that needs to get its adb on.
install a verbose driver program (i am fond of USBDeview http://www.nirsoft.net/utils/usb_devices_view.html) make sure whatever program you use is VERBOSE and reports every activity, like in the options make everyhting so that it reports, displays and hides nothing. UNINSTALL AND DELETE EVERYTHING that indicates it could be connected to 1. ADB 2. Device 3. anything freaking android. Actually, I have been so frustrated in the past that I actually uninstalled every single driver on the computer....I highlighted all my drivers and Uninstalled... and they all uninstalled.. my mouse stopped working my keyboard stopped working but screw that, shut down the computer (irrelevant to whatever winblows geeks tell you it is NOT harmful to crash-power down your windoze machine) and then upon rebooting it will install all its relevant inner drivers) which may be bad for some of you if you have a complicated setup but whatever all I wanted was to get adb working at the expense of other drivers. Everything will reinstall when its connected, thats how drivers work -- you connect it and it starts talking to windows and **** happens right there.
So, delete everything! Reboot! you need to reboot your machine after each major change, because its just to eliominate the chances of not being able to communicate if winblows needs to reboot to be fresh.
If you have deleted uninstalled all of these android-related drivers... and if you have made your machine verbose, so that its not hiding information or thinking you are not interested in whats going on in system, and then you reboot, chances are when you first plug that KF in to your system, **** will happen. You just need to make it work.
you cant just sit around for two months waiting for someone to give you the fix -- the answer is right there in your hands... you just have to make it stick. Its there. Just gotta tweak the hell out of your computer to make it happen. If it doesnt work... keep trying... try again. if that doesnt work, change something. keep on tweaking, keep on shaking the nest and itll pop in.
HOWEVER I checked out the Jayceooi website and he/she has a good case to make there -- and if "it dont work" then thats because you are not trying hard enough.
Now.. all I can say is Ive lost adb.. and Ive found it again.. and I still have it because I have not installed ANY other android related or SDK ADB related programs after I found it.... everytime I do... everytime I attach my other HTC devices, it messes up everything and I repeat the above all over again
Click to expand...
Click to collapse
This is why i use linux.. i just have way to many android devices i plug into my pc to have to be deleting and reinstalling drivers and android sdk everytime.
Ive rooted three kindle fires already, one on windows and two with linux. rooting with windows took me a whole day to get to work while it took me an under an hour with linux.
if you like to plug in android devices a lot and want to use adb on all of them, do yourself a favor and trash windows and install linux. I have 2 PCs so its not a problem for me. one house computer running windows, and my pc running linux..
windows hates android!

K3nDroid said:
This is why i use linux.. i just have way to many android devices i plug into my pc to have to be deleting and reinstalling drivers and android sdk everytime.
Ive rooted three kindle fires already, one on windows and two with linux. rooting with windows took me a whole day to get to work while it took me an under an hour with linux.
if you like to plug in android devices a lot and want to use adb on all of them, do yourself a favor and trash windows and install linux. I have 2 PCs so its not a problem for me. one house computer running windows, and my pc running linux..
windows hates android!
Click to expand...
Click to collapse
Interesting that you had such an issue with getting windows to work. I have rooted 2 Kindles(took an hour total to get them set up, rooted, recovery and Gapps installed), Samsung Epic 4g, Multiple Evo 4gs, Optimus M, Hauwei Ascend, and HTC Hero and never had an issue with drivers or having to uninstall them. I am running Windows 7 and each one I plug in it recognizes.

TP-LINK Android Phone / ADB Device

Ok so i'm pulling whats left of my hair out as I cannot seem to be able to remove this pest of a driver , windows 8.1 Pro is insisting my Nexus 5X is a TP-Link Android Phone and keeps over writing my google adb drivers so my fastboot / adb no longer works , has / is anybody having this problem? wugfresh install wont overwrite the TP-Link either all universal adb installers wont work either

MKD73 said:
Ok so i'm pulling whats left of my hair out as I cannot seem to be able to remove this pest of a driver , windows 8.1 Pro is insisting my Nexus 5X is a TP-Link Android Phone and keeps over writing my google adb drivers so my fastboot / adb no longer works , has / is anybody having this problem? wugfresh install wont overwrite the TP-Link either all universal adb installers wont work either
Click to expand...
Click to collapse
Kind of surprised you're still running Windows 8.1. Windows 10 is free for you and better in just about every way, regardless of the UI changes. Just a recommendation, though I doubt it'd fix your issue.
There's an easy way to tackle this but it depends on how the driver is being installed. If you're connecting your phone to your computer and Windows is insisting on downloading and installing this "TP-Link" driver from Windows Update, there is a way to disable this in a few easy steps. If you're connecting your phone to your computer and Windows just assumes that it's a "TP-Link Android Phone" and applies the wrong pre-loaded driver (usually gives you a notification near the clock) then we're gonna have to get a bit crafty.
EDIT: Silly question. You don't have USB tethering or any wacky app that would be causing this issue, right?

Alcolawl said:
Kind of surprised you're still running Windows 8.1. Windows 10 is free for you and better in just about every way, regardless of the UI changes. Just a recommendation, though I doubt it'd fix your issue.
There's an easy way to tackle this but it depends on how the driver is being installed. If you're connecting your phone to your computer and Windows is insisting on downloading and installing this "TP-Link" driver from Windows Update, there is a way to disable this in a few easy steps. If you're connecting your phone to your computer and Windows just assumes that it's a "TP-Link Android Phone" and applies the wrong pre-loaded driver (usually gives you a notification near the clock) then we're gonna have to get a bit crafty.
EDIT: Silly question. You don't have USB tethering or any wacky app that would be causing this issue, right?
Click to expand...
Click to collapse
Yeah we will have to get a bit crafty, i hid the TP-Link update in windows update god knows how it got installed but its in and i removed it but its still insisting its a TP-Link Android Phone , man its bugging me out . No tether app or other apps no, thats why im lost as to why its started this BS , windows i know can be tricky WIN10 was not for me plus the free upgrade has past now (29July) anyway.

MKD73 said:
Yeah we will have to get a bit crafty, i hid the TP-Link update in windows update god knows how it got installed but its in and i removed it but its still insisting its a TP-Link Android Phone , man its bugging me out . No tether app or other apps no, thats why im lost as to why its started this BS , windows i know can be tricky WIN10 was not for me plus the free upgrade has past now (29July) anyway.
Click to expand...
Click to collapse
Would you mind doing something for me before performing the steps I'm going to list below? Go into Device Manager with the phone plugged in and installed as the stupid "TP-Link" BS and find it in the list of devices. Should probably be under Portable Devices or something. Right click it and click Properties, go to the Driver tab and click "Driver Details". All of the drivers should be located in the 'system32/DRIVERS' folder. Mind giving me the names of those drivers listed? Naming convention is typically driverName.sys.
Additionally, we're going to try a Group Policy change. Hit Windows Key + R and type 'gpedit.msc' and hit enter. A window labeled "Local Group Policy Editor" should come up. Then do the following:
Expand Computer Configuration (Left hand side, the navigation panel)
Expand Administrative Templates
Expand System
Expand Device Installation
Click Device Installation Restrictions
On the right hand side, now, there should be a list of restrictions. Somewhere in that list there should be an item "Prevent installation of devices not described by other policy settings". Double-click that and another window named the same thing should pop up. In the top left, set it to enabled and click Apply, then OK.
Unplug your phone and get rid of that ****ty driver if you haven't already and then restart and try connecting the phone again to see if the same incorrect driver install occurs.

@MKD73 You ever get this sorted out?

Sorry been away on holiday for the weekend , I'll be taking a look in the morning :victory:

Please give update
Have you resolved this issue? My laptop is acting the same. Device manager sees my phone as "TP-Link Android Phone" with sub category of "Android Bootloader Interface." I can't use ADB with it, not recognized.
I tried doing what Alcolawl said but nothing happens. When I right click the "TP Link--- it just says general properties, no 'drivers' etc. I saw the 'driver' option in the "Andoid bootloader Interface" . It says the driver is: winusb.sys, wdfCoInstaller01009.dll and WinUSBInstaller2.dll. When I tried to edit the group, it says "Windows can not find gpedit.msc
Hope you can help me. My phone is stuck in fastboost mode- LG D838

kalikotpepot said:
Have you resolved this issue? My laptop is acting the same. Device manager sees my phone as "TP-Link Android Phone" with sub category of "Android Bootloader Interface." I can't use ADB with it, not recognized.
I tried doing what Alcolawl said but nothing happens. When I right click the "TP Link--- it just says general properties, no 'drivers' etc. I saw the 'driver' option in the "Andoid bootloader Interface" . It says the driver is: winusb.sys, wdfCoInstaller01009.dll and WinUSBInstaller2.dll. When I tried to edit the group, it says "Windows can not find gpedit.msc
Hope you can help me. My phone is stuck in fastboost mode- LG D838
Click to expand...
Click to collapse
Hi Kalikotpepot,
Got the same issue here., Nexus 5x keeps on rebooting, no way to get to recovery and shows as TP Link on my computer. Did you manage to sort it out somehow?

loeage said:
Hi Kalikotpepot,
Got the same issue here., Nexus 5x keeps on rebooting, no way to get to recovery and shows as TP Link on my computer. Did you manage to sort it out somehow?
Click to expand...
Click to collapse
I did it. Execute :
Code:
rundll32.exe newdev.dll,DeviceInternetSettingUi 2
and prevent driver from being installed.

Help me please!
Did you guys manage to fix it? I tried everything you people said but it didn't work. I have a Blu Vivo Xi+ and my PC only recognizes it as TP-LINK Android Phone. I dumbly deleted it's OS and all it's data when trying to update it. I only have access to TWRP and fastboot, is there a way to fix it? I would love if someone could assist me ?.