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.
Related
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.
I have seen many people asking about bitpim and the kin phones and many with no solutions or answers to their questions. It IS possible to use bitpim to view the file system with these devices. I haven't seen any tutorials on how to do it so I've decided to post a step by step guide.
The things you will need:
Kin Two or Kin TwoM(I have not been able to test this on a Kin One or OneM)
A micro usb data cable
Bitpim
Drivers for the Kin available below
http://rapidshare.com/files/439206164/KinPixiPreCentroTreo800w_etc_DiagDrivers.zip
Don't worry about fixing the error in the qcser.inf, since I have already done this for you.
I would like to thank jennydevil for reminding us that these drivers are for 32-bit not 64-bit operating systems.
Step 1
On your kin device go to the phone application. Once there dial ##77647266488 and call. It will ask you for your Service Programming Code. The default code is 000000. You will now be in a menu labeled "SETTINGS". Navigate to OTHER and then swipe to the left. Here you will see PPro, USB Pass-Through, and USB VID Stream. All of these options will be off. You will want to turn USB Pass-Through on.
Step 2
Now connect your phone to your Windows PC. Your pc will try to find a driver called "Pink CDMA diagnostics" and will fail. Fear not. Open the start menu and right click on Computer then Manage. On the menu to the far left click device manager. In other devices you will see the Pink CDMA diagnostics. Right click it and press "Update Driver Software". Click "Browse My Computer for Driver Software". Browse for the location of the drivers downloaded earlier and click next. It will show a warning that the drivers are not signed. Continue anyways.
Step 3
Now you are ready to open up bitpim. Set it to the same COM as the phone and make sure in the View menu that View Filesystem is checked. Now feel free to browse through the file system of your kin.
If you run in to any problems feel free to ask questions. If you have any ideas or information to make this tutorial more useful feel free to speak your mind.
Fantastic!!
This is a great start to making our kin experience much better! Thank you, and keep up the solid work! Your friends at Microsoft Kin Forums thank you aswell! Check our sites for updates that could help, and together we can make KIN the phone it truely can be!
social.answers.microsoft.com/Forums/en-US/pmxphone/threads
link to MS kin forums (gotta add http)
Thank you for putting the tutorial together (and posting the pre-fixed drivers)! In case anyone else runs into the same hiccup I did - the drivers are for 32-bit OS, not 64-bit OS. Once I used the right system, the drivers and BitPim worked like a champ.
Thanks again!
I can see filesystem
Hey thanks, I can see the filesystem, I think? It says nothing is detected when I manually set the phone. I cannot "get phone data" but can read the filesystem.
.efs_private
CGPS_ME
CGPS_PE
DMU
...etc
But what does this all mean? Can I access ringtones/sounds to edit the list? Please all I want is to add and delete ringtones! Ugh why is this so difficult. Anybody know how to do this?
sabernat said:
Hey thanks, I can see the filesystem, I think? It says nothing is detected when I manually set the phone. I cannot "get phone data" but can read the filesystem.
.efs_private
CGPS_ME
CGPS_PE
DMU
...etc
But what does this all mean? Can I access ringtones/sounds to edit the list? Please all I want is to add and delete ringtones! Ugh why is this so difficult. Anybody know how to do this?
Click to expand...
Click to collapse
No at the moment you can't do that with BitPim but you can email a ringtone to your phone.
Help in step two
Can not find driver location on Windows Vista. I can get to Windows32 file/ then to driver file but new downloaded drivers as in step two.
Thanks
Ah ok, dang. Problem is...Kin has no function to delete ringtones. So once its on, its on forever. I just can't commit to that.
Moved to KIN two forum and stickied.
Also, fix the rapidshare link, the file seems to be unavailable.
jekikeyes said:
Can not find driver location on Windows Vista. I can get to Windows32 file/ then to driver file but new downloaded drivers as in step two.
Thanks
Click to expand...
Click to collapse
Download the drivers extract them somewhere like a folder on your desktop. Let's call the folder kindrivers. Then when you are browsing to the files you would go to C: (or the drive vista is located on)/Users/Yourusername/desktop/kindrivers
Hope that helps.
Any chance we'll be able to get 64-bit drivers soon?
activesack said:
Any chance we'll be able to get 64-bit drivers soon?
Click to expand...
Click to collapse
Not unless someone wants to take the time to write them.
After trying it myself I am not convinced that "we" are seeing anything. It states no phone is connected. There are no signs that I see anything from the phone. Keep trying and keep posting.
dezgrz said:
Not unless someone wants to take the time to write them.
Click to expand...
Click to collapse
someone please do
Kin_Two 2
I am at a lost, I did all the steps, plus the driver download. Everything went fine. I can see what port the phone is using, and have it set on bitpim. When I go to detect the phone on bitpim, it can not find the phone. Have tried on two different computers and can not get it to work. Bitpim can not find the phone, any thoughts?
Ron
phoneinu said:
I am at a lost, I did all the steps, plus the driver download. Everything went fine. I can see what port the phone is using, and have it set on bitpim. When I go to detect the phone on bitpim, it can not find the phone. Have tried on two different computers and can not get it to work. Bitpim can not find the phone, any thoughts?
Ron
Click to expand...
Click to collapse
Bitpim won't find the phone you have to manually set it to the correct COMM port.
I found the com port in device manager. It has been set, but it says it can not still detect phone. When I do go to settings in bitpim, I go to Verzion Wireless, Motorola, and then Kim? Is that correct, there is no Kin just Kim,so is that the same thing?
Ron Fone
phoneinu said:
I found the com port in device manager. It has been set, but it says it can not still detect phone. When I do go to settings in bitpim, I go to Verzion Wireless, Motorola, and then Kim? Is that correct, there is no Kin just Kim,so is that the same thing?
Ron Fone
Click to expand...
Click to collapse
It won't detect it. Just show the file system. Just set it to other cdma.
Hey, I'm about to be forced to get the Kin TwoM (its the best phone on Verizon without a data plan). Has there been any progress on the ROM dumping front? It seems like you would know. Thanks...
Just wanted to post in here saying that I just got myself a Kin TwoM this weekend without knowing anything about it's limitations or potential. I got it working with BitPim using this tutorial, but... yeah, I have no idea what to do now. I'll certainly be watching this board for anything cool that comes of this, though!
Well I have had my Kin Twom for more then a week. I am probably going to return it, its a shame because it is not a bad little phone. Microsoft and Verizon will be the death of this thing. Know what to do about my cell phone?
Ron
I am completely new to Android and all of this flashing stuff. This is my first tutorial hope it helps some out there. I really couldn't find one tutorial that helped me completely so I put stuff I used from many into one.
MAKE SURE YOUR ESN IS CLEAN AND NOT A STOLEN PHONE. IN MY CASE IT WAS A CLEAN ONE.
What you need:
1. QPST 2.7 Build 323 (Look it up yourself and download it)
2. ADB and DIAG drivers here
3. The 60650.prl from this site http://www.corolada.com/prl/
Here are the steps.
1. Make sure that your Evo's drivers are all installed. By that I mean the ADB and HTC DIAG drivers.
2. Dial ##3424# which will put your phone in Diag mode, and enable usb debugging.
3. You can follow this to install the DIAG and ADB drivers.
http://forum.xda-developers.com/showthread.php?t=697487&highlight=cdma+workshop
4. Once done installing the DIAG driver make sure you're still on device manager.
Make sure you see this below:
Now right click on HTC USB Modem and click properties, and something like this will come up:
take note of the port # on the top, in my case COM4
5. Now open CDMA workshop in Administrator mode. Right click Run as Admin. This will come up:
6. Click on connect on the bottom right, on the bottom left it should say "Connected to (your COM name) port successfully" in my case COM4
7. Click on other and make sure it says NAM1 for the first flash. Click write and browse for the 60650.prl and select it press open. Something like the second image should pop out, just press ok the prl has been flashed.
8. Now where it previously said NAM1 press the arrow down and click NAM2. Click write and browse again for 60650.prl do the same as step 7.
9. You are done. Close CDMA workshop. Reboot your EVO.
10. Go to update your PRL
11. Punch ##3282# hit edit type your MSL pass, go to Data Profile, hit menu and hit RESET.
12. Reboot once more and youre good to reactivate your EVO.
Sources:
http://forum.xda-developers.com/showthread.php?t=937652
http://forum.xda-developers.com/showthread.php?t=898628
http://forum.xda-developers.com/showthread.php?t=737594
http://forum.xda-developers.com/showthread.php?t=697487
http://www.corolada.com/prl/
REMEMBER FLASHING IS AT YOUR OWN RISK AND I AM NOT HELD RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE (IM NOT SAYING THAT ANYTHING BAD IS GOING TO HAPPEN). I JUST SAY THIS TO PROTECT MYSELF. THIS WORKED FOR ME, I HOPE IT WORKS FOR YOU.
My proof:
Today in my room at 11AM with Metro PCS prl (Look at the bars XD)
Today at 7PM in my room with Sprint prl (Look at the bars)
But people need to be reminded, if You bought a *STOLEN* Sprint evo (one that has been reported) it won't work on Sprint.
So make sure you check the ESN with Sprint before hand.
Yes ill edit that into the post thanks bro.
Sent from my PC36100 using XDA App
i posted this in the wrong section is there a way this can be deleted or reposted in the development section?
hey, do you think this will work for the evo shift?
EDIT:
I followed your instructions which are pretty simple to the letter, after rebooting, im still stuck with metro prl. I tried updating it with using wifi, but no luck.
EDIT2: Whats weird i that the "sprint zone" msg comes up, so some kind of progress was made..... to be continued upon further discoveries!!
Edit3: Ok, it finally took after resetting the phone a few times, and it does show the new prl. But now, it takes forever to update the prl. The only other prob is I cannot find my msl code, neither thru msl reader or cdma workshop, they both tell me its 6 zero's. Boy oh boy!!!
Hello pediz123
I have couple questions on your tutorial.
1. Is it possible if I use DEMO-CDMA Workshop with your tutorial? I went to the link they gave me the demo version.
2. In your tutorial, I dont see when you run "QPST 2.7 Build 323". What is it for?
Thanks
inw
Why do I want this?
Some apps do not work properly without an IMEI. The example app that I ran into is the XDA free application. Without an IMEI, the XDA app crashes when logging in. I believe it may also affect Terminal Emulator, causing it to force close on launch. The Kindle Fire, at least when running CM7 (not sure about stock), does not have an IMEI built in. Test yours by typing "*#06#" in the dialer.
Prereq's
Ensure the Kindle Fire ADB drivers are installed. The Kindle Fire Utility installed them for me.
Step 1
Download DizzyDen's IMEI generator.
Edit .ini to modify build.prop to stock Kindle Fire device identification (optional step)
(Use if you have issues with the Market or Amazon Appstore allowing you to download apps)
Settings:
Device_Manufacturer = TI
Manufacturer_Device = blaze
Device_Model = Full Android on Blaze or SDP
{
"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"
}
Step 2
Run the program! For the first option, asking about dev's rom, select "no."
Choose "yes" for in-place upgrade.
It will pop up saying "Failed to read MAC address."
Ensure that your serial number was found and the IMEI is a correct 00-#### (series of numbers) format.
If all is correct, push to device:
You must run it again on every ROM update!
FAQ
Q: Anything else this program can do?
A: Look in the !IMEIme.ini file, there are options for spoofing the device manufacturer, etc.
The following is the relationship from the ini to the build.prop settings:
Device_Manufacturer edits the ro.product.manufacturer
Manufacturer_Device edits the ro.product.device
Device_Model edits the ro.product.model
Q: Does this program support ICS?
A: DizzyDen says that it should.
Q: I've heard messing with IMEIs is illegal.
A: DizzyDen's program generates an IMEI with a 00- in front, indicating that it is a test IMEI. No illegal spoofing of a real phone is going on.
Q: Is there any way to add an IMEI to a ROM before flashing?
A: Yup, just choose "Yes" to "Are you planning to update a dev's ROM zip file?" and choose your ROM.
Q: Ran it, and under system > About Tablet > IMEI it shows as Unknown.
A: Normal, test with *#06# in dialer.
Please consider clicking a "Thanks" to me and to DizzyDen!
The XDA app works fine with stock rooted 6.2.1. CM7 might clear the IMEI.
I'll give a look to see if the I have an IMEI.
I'm in CM7 with no imei but I use the premium version
Sent from my Kindle Fire using xda premium
Thanks for the feedback guys.
I've tried the free version on CM7.. FC QUITE A BIT!!! Will try this when I get off of work. Great work btw
Sent from my SGH-I897 using XDA App
CrimsonSentinel13 said:
The XDA app works fine with stock rooted 6.2.1. CM7 might clear the IMEI.
I'll give a look to see if the I have an IMEI.
Click to expand...
Click to collapse
That's weird... Doesn't for me.... I'm going to try this fix when I get home.
Sent from my myTouch_4G_Slide using XDA App
Nice work, when I was on CM7 (now am back on stock kindle rooted) I was unable to use the XDA Free app at all because it kept force closing, though like others mentioned, the premium app worked fine.
The regular app checks for an IMEI, the premium does not.
Sent from my Galaxy Nexus using xda premium
Good find. Decent guide. xda free app is working well now.
That explains a lot! Thanks! I have had issues nwith the XDA Premium app on the Fiya.
Noobi question guys. Would adding an IMEI allow me to download some market apps that don't otherwise show up? I have a couple of apps that I have on my Evo that I would like to have on my KF. One example is FLCommando. Or is there a different way of doing that?
ibleo02 said:
Noobi question guys. Would adding an IMEI allow me to download some market apps that don't otherwise show up? I have a couple of apps that I have on my Evo that I would like to have on my KF. One example is FLCommando. Or is there a different way of doing that?
Click to expand...
Click to collapse
No... it won't cause apps to show up that don't show up... BUT
With the build.prop edits available by simply editing the !IMEI.ini you can get apps to show up.
You can leave all the information for both devices in the ini file and just place a ; at the beginning of the one you don't want.
You could try the default KF info and if that don't work... make it mimic your Evo
And thank you for the write up on the tutorial Max... glad this is getting more info out to other forums other than the NookColor... should work on just about all devices now.
One thing to be aware of... since the program edits framework.jar for IMEI spoofing... you must run it again on every ROM update.
So I'm not sure if I'm doing something wrong here, but for whatever reason !IMEIme cannot recognize my device's serial number. I have tried re-installing drivers, restarting my computer, restarting the kindle, elevating adb first, and nothing seems to be working.
Every time I run the program it says it cannot detect the serial number, nor the MAC address, then it tells me to input an IMEI manually. Judging by the original instructions, it is important that the tool recognizes my device's S/N before continuing. Any advice?
Thanks,
td
Edit: Just for more info, I'm running stock 6.2.1 with root. I tried a big ordeal just now with my drivers to no avail. It seems like the tool is not properly communicating somehow, though adb is certainly communicating fine.
I'm doing these steps:
1) connect kindle
2) select "Disconnect" when the usb transfer option appears on the kindle
3) run "!IMEIme.exe" from its own folder on.my desktop
4) it runs through several windows, tells me it can't find the serial, then the MAC.
I did try inputting my own code for the IMEI, but it then gave me an error saying it couldn't upload. Any help in this matter is greatly appreciated.
There may be a way to spoof this. I think the nook color does this
Sent from my Galaxy Nexus using XDA App
tduermeier said:
So I'm not sure if I'm doing something wrong here, but for whatever reason !IMEIme cannot recognize my device's serial number. I have tried re-installing drivers, restarting my computer, restarting the kindle, elevating adb first, and nothing seems to be working.
Every time I run the program it says it cannot detect the serial number, nor the MAC address, then it tells me to input an IMEI manually. Judging by the original instructions, it is important that the tool recognizes my device's S/N before continuing. Any advice?
Thanks,
td
Edit: Just for more info, I'm running stock 6.2.1 with root. I tried a big ordeal just now with my drivers to no avail. It seems like the tool is not properly communicating somehow, though adb is certainly communicating fine.
I'm doing these steps:
1) connect kindle
2) select "Disconnect" when the usb transfer option appears on the kindle
3) run "!IMEIme.exe" from its own folder on.my desktop
4) it runs through several windows, tells me it can't find the serial, then the MAC.
I did try inputting my own code for the IMEI, but it then gave me an error saying it couldn't upload. Any help in this matter is greatly appreciated.
Click to expand...
Click to collapse
It shouldn't be necessary to click "disconnect" on the Kindle. Do you have USB Debugging enabled in the Applications -> Development Settings?
A troubleshooting step: If you run the Kindle Fire Utility with your KF plugged in, does the "ADB Status" and "ADB Rooted" report your Kindle?
MaxRabbit said:
It shouldn't be necessary to click "disconnect" on the Kindle. Do you have USB Debugging enabled in the Applications -> Development Settings?
A troubleshooting step: If you run the Kindle Fire Utility with your KF plugged in, does the "ADB Status" and "ADB Rooted" report your Kindle?
Click to expand...
Click to collapse
So there doesn't appear to be a selection for Development Settings under Applications, all I see when I click on Applications (on the stock rom) is a list of the running applications.
When hooked up to KFU, ADB Status is online, but ADB Rooted says No. My device is running Burritoroot and has SU installed, but if I elevate adb with burritoroot through KFU it will revert back as soon as I close the utility, correct?
Is there anyone who has gotten this to work on a stock, rooted setup that could tell me the steps they followed to make this work?
Regards,
td
Edit:
Tried a couple new things, still to no avail.
1) Ran KFU and elevated adb to have root access, confirmed before and after IMEI through KFU outputting "ADB Rooted: Yes" when prompted to Recheck the device status
2) Did not select "Disconnect" before running utility.
After this attempt I got an error reading:
This will circumvent the intent of this program by using a GENERIC IMEI. This program will not allow this. Program will exit now.
Click to expand...
Click to collapse
I got this error after selecting "No" to the first prompt regarding a developer's ROM, and "Yes" to the second prompt about In-Place updates. I never saw the "Obtaining IMEI" or "Obtaining Serial Number" or "Obtaining MAC Address" screens at all, this error popped up before any of those screens had a chance.
Then, just to be stubborn, I ran the utility once more and saw it go through a different set of issues, wherein I see "Testing ADB" (no error after this), then the screen flashes to "Obtaining IMEI," which flashes twice, then "Obtaining serial number," which also flashes twice then tells me it could not obtain my serial number, then "Obtaining MAC address," which also flashes twice and tells me it could not obtain it. I am then given a screen where I can input an IMEI base manually and when I hit cancel it gives me the same quoted error above.
It seems like this should be a very simple thing judging by the instructions in the OP, but nothing I've tried has brought me success.
DizzyDen said:
No... it won't cause apps to show up that don't show up... BUT
With the build.prop edits available by simply editing the !IMEI.ini you can get apps to show up.
You can leave all the information for both devices in the ini file and just place a ; at the beginning of the one you don't want.
You could try the default KF info and if that don't work... make it mimic your Evo
And thank you for the write up on the tutorial Max... glad this is getting more info out to other forums other than the NookColor... should work on just about all devices now.
One thing to be aware of... since the program edits framework.jar for IMEI spoofing... you must run it again on every ROM update.
Click to expand...
Click to collapse
Thank you sir, i will try that.
I'm running Ubuntu, and having no luck with this method. Could someone point me in the right direction? I've been trying to use this tool under wine, and keep getting the error "Failed to mount ROM to read device information". Adb works under Ubuntu, I can edit files, do everything else, but I can't seem to get this working using this tool under wine. Can you provide me with any ideas on how to fix this? It's crazy that I need to use a Windoze box to fix this.... as android is linux, as is Ubuntu. Cheers.
tduermeier said:
So there doesn't appear to be a selection for Development Settings under Applications, all I see when I click on Applications (on the stock rom) is a list of the running applications.
When hooked up to KFU, ADB Status is online, but ADB Rooted says No. My device is running Burritoroot and has SU installed, but if I elevate adb with burritoroot through KFU it will revert back as soon as I close the utility, correct?
Is there anyone who has gotten this to work on a stock, rooted setup that could tell me the steps they followed to make this work?
Regards,
td
Edit:
Tried a couple new things, still to no avail.
1) Ran KFU and elevated adb to have root access, confirmed before and after IMEI through KFU outputting "ADB Rooted: Yes" when prompted to Recheck the device status
2) Did not select "Disconnect" before running utility.
After this attempt I got an error reading:
I got this error after selecting "No" to the first prompt regarding a developer's ROM, and "Yes" to the second prompt about In-Place updates. I never saw the "Obtaining IMEI" or "Obtaining Serial Number" or "Obtaining MAC Address" screens at all, this error popped up before any of those screens had a chance.
Then, just to be stubborn, I ran the utility once more and saw it go through a different set of issues, wherein I see "Testing ADB" (no error after this), then the screen flashes to "Obtaining IMEI," which flashes twice, then "Obtaining serial number," which also flashes twice then tells me it could not obtain my serial number, then "Obtaining MAC address," which also flashes twice and tells me it could not obtain it. I am then given a screen where I can input an IMEI base manually and when I hit cancel it gives me the same quoted error above.
It seems like this should be a very simple thing judging by the instructions in the OP, but nothing I've tried has brought me success.
Click to expand...
Click to collapse
The error regarding circumventing may be due to the method of rooting used causing your device to report one of the "generic" serial numbers (11223344.... or 12345.... etc) several recovery applications use this and without me taking that into account there could be MANY devices obtaining the same IMEI (which defeats the purpose)... a method you could use is
1. edit !IMEI.ini and set Use_ADB = 0
2. select yes to update developer's ROM
4. manually input your device serial number
5. flash the ROM (the one with -IMEI.zip to the device)
Alternatively you could pull your framework.jar from you /system/framework folder and select no to dev's ROM, and no to inplace... it will then let you browse for your framework file to patch.
tillum said:
I'm running Ubuntu, and having no luck with this method. Could someone point me in the right direction? I've been trying to use this tool under wine, and keep getting the error "Failed to mount ROM to read device information". Adb works under Ubuntu, I can edit files, do everything else, but I can't seem to get this working using this tool under wine. Can you provide me with any ideas on how to fix this? It's crazy that I need to use a Windoze box to fix this.... as android is linux, as is Ubuntu. Cheers.
Click to expand...
Click to collapse
the "Failed to mount ROM to read device information" shouldn't effect the use on a KF... since the program was originally intended for use on a NookColor... I have it written to mount the ROM partition to read the device specific files... but I also added the use of the "adb getserialno" to obtain device serial number from other devices.
I'm confused then, as it doesn't appear to be working... I will check the other error messages I'm getting and post back... basically, the program seems to be quitting with something along the lines of "Unable to generate generic IMEI... quitting" etc. Cheers.
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 ?.