Develop Bugs

[Q] Stuck "Kindle Fire" Spash screen after unrooting

Hi,
My rooted KF started behaving, weirdly so I decided to start from scratch and unroot it using the ClockworkMod recovery utility interface that was automatically loaded when I rooted it using Breakdroid. It started life with 6.2.2 but then updated itself to 6.3, so I downloaded the following file to do the unroot, and converted it into a .zip file called update.zip.
//kindle-fire-updates.s3.amazon...1E_4019920.bin
and went into the ClockworkMod recovery utility mounted my KF, did a factory reset, then applies sdcard update.zip which appeared to perform sucessfully, however when I rebooted, it launched the Stock KF screen, no fire fire fire, and has since stayed there. Can anyone please help! Many thanks.

Does KFU recognize it? If it does you are good to go.

Hi,
Nope. I'm using a Mac, so I use Breakdroid, and it's not picking it up.

http://forum.xda-developers.com/showthread.php?t=1644970

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1644970
Click to expand...
Click to collapse
Keep up the good work soupmagnet!

Thanks soupmagnet,
I know it's the same question asked over and over again, I'll give it a shot and let you know if I sort it out. Appreciate your time.

All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!

nickvon said:
All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!
Click to expand...
Click to collapse
Actually a factory cable, while nice to have, doesn't seem necessary in your case. (Hint Read about the different bootmodes.

Hi again Soupmagnet,
So I eventually got hold of my factory cable which I ordered off Ebay from Hong Kong, so I plugged it in and hey presto, nothing happened. I'm still stuck on the Kindle Fire screen. I've been using a Mac and Breakdroid doesn't pick it up at all. I decided to see if a PC could pick it up using KFU, and it's still offline, although in My Computer I do see an external drive and device manager does call it Kindle. I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle. Could it perhaps be the cable not in fact being a factory cable at all? I'm getting pretty desperate with this situation. Can you offer me advise.
Nickvon

Oh and further to my last I was changing boot modes but as it couldn't recognize the device, it was pointless.

nickvon said:
I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle.
Click to expand...
Click to collapse
Take a breath, relax, and rest assured that you are more likely in the upper 90% range.
As I said before, the factory cable, while nice to have isn't usually required to fix most devices. All it does, is puts the device in fastboot mode and provides direct power to the device via usb in case of low or now power
Your problem is simply a matter of fixing your drivers so you can communicate with the device and change the bootmode.
[Edit:] It's been a while since this post was first started so I forgot you were using Mac instead of Windows.
Open your Terminal and enter the following:
Code:
cat ~/.android/adb_usb.ini
Your output should read:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
Anything other than would explain why you aren't able to change the bootmode normally.
Are you using Terminal commands to change the bootmode or are you using Breakdroid?

USB disconnects my rooted kindle fire very fast (details inside)

I rooted my Kindle Fire about a month ago with KFU. Everything was fine until I turned it on one day and I got stuck at the Triangle screen. None of the reboot tricks work. The interesting thing which I think is what is stopping me from being able to successfully use other methods is that when I plug my Kindle Fire into my computer via usb, it connects, and then disconnects (the USB) about 2 seconds later. I've tried different ports, etc. Any help on this issue would be greatly appreciated. I've read over multiple things, but don't see a mention to the kindle being disconnected via usb so quickly, thus stopping me from being able to do anything.

Care to elaborate on what "reboot tricks" you've used?
What version of Windows are you using?

soupmagnet said:
Care to elaborate on what "reboot tricks" you've used?
What version of Windows are you using?
Click to expand...
Click to collapse
I've tried the rebooting the Kindle while trying to reset the kindle to booting "normally" within the KFU. I've tried holding down the power button on a reset, then pushing it again until it is orange, none seem to work. I'm confident I could get it to work again if the kindle did not disconnect from my computer so quickly. By this I mean I hear the "usb chime" when I plug it in, then within seconds the disconnect chime plays. During the brief few seconds it is connected, it shows up on my devices list, but obviously when the usb disconnect chime plays, it disappears off of the device list.
edit: I'm using windows 7 Ultimate.

Can anyone help me? I may add that My Kindle Fire was originally rooted with the KFU and worked perfectly fine. I literally turned it on one day, and it got stuck at the triangle screen. The connection issue of it disconnecting so quickly is what is stopping me from fixing it I believe. Please help.

ErikV55 said:
Can anyone help me? I may add that My Kindle Fire was originally rooted with the KFU and worked perfectly fine. I literally turned it on one day, and it got stuck at the triangle screen. The connection issue of it disconnecting so quickly is what is stopping me from fixing it I believe. Please help.
Click to expand...
Click to collapse
Read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Figure out what device drivers are getting loaded when the connect "chimes" sound in Windows. If you confirm that they are correct based on the contents above, you must stop the temporary fastboot, set the bootmode to normal using fastboot, and restart the device.
I suspect you've got more issues than just getting stuck on the bootloader though... If you are getting disconnect tones in the bootloader, that means it's attempting to boot into something, but obviously unable to do so.

kinfauns said:
Read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Figure out what device drivers are getting loaded when the connect "chimes" sound in Windows. If you confirm that they are correct based on the contents above, you must stop the temporary fastboot, set the bootmode to normal using fastboot, and restart the device.
I suspect you've got more issues than just getting stuck on the bootloader though... If you are getting disconnect tones in the bootloader, that means it's attempting to boot into something, but obviously unable to do so.
Click to expand...
Click to collapse
The disconnect tones are from my computer, the same tone when you unplug a usb (since the kindle is plugged in via usb) I can't change the bootmode because the usb disconnect chime happens literally 2 seconds later, and the kindle is disconnected, all the while the kindle is still on and showing the triangle screen.

ErikV55 said:
The disconnect tones are from my computer, the same tone when you unplug a usb (since the kindle is plugged in via usb) I can't change the bootmode because the usb disconnect chime happens literally 2 seconds later, and the kindle is disconnected, all the while the kindle is still on and showing the triangle screen.
Click to expand...
Click to collapse
Have you checked to see what drivers are getting loaded? Do you know what device should appear in the device manager? Have you tried to stop the temporary fastboot countdown? Do you know how to stop the temporary fastboot countdown?
If you aren't willing to try out my suggestions, there's not much else I can do.

kinfauns said:
Have you checked to see what drivers are getting loaded? Do you know what device should appear in the device manager? Have you tried to stop the temporary fastboot countdown? Do you know how to stop the temporary fastboot countdown?
If you aren't willing to try out my suggestions, there's not much else I can do.
Click to expand...
Click to collapse
Yes to all those things. The device does indeed pop up in the device manager but only for the brief 2 second window before it disconnects. I've tried multiple usb ports on my pc with the same result. The kindle does not power off in any way when the it disconnects from the pc.

ErikV55 said:
Yes to all those things. The device does indeed pop up in the device manager but only for the brief 2 second window before it disconnects. I've tried multiple usb ports on my pc with the same result. The kindle does not power off in any way when the it disconnects from the pc.
Click to expand...
Click to collapse
What is the device name that comes up?
What command did you send to stop the countdown?
What did it output as a result of the command?
What makes you think that it should power off when you disconnect from the PC?

kinfauns said:
What is the device name that comes up?
What command did you send to stop the countdown?
What did it output as a result of the command?
What makes you think that it should power off when you disconnect from the PC?
Click to expand...
Click to collapse
I've tried to reset the bootmode via the KFU method recommended in the guide posted here (normal, 4000 and trying to reset when it says waiting for device) The device pops up in the device manager as an "unknown device" which may be a problem with the version of the drivers im DLing. I'm using KFU version 0.9.6
When I first DLed them it seemed as if the drivers were installing correctly, when I plugged in the Kindle is said drivers were being installed but it failed because the device disconnected after the 2 seconds.

Rapid disconnects are nothing unique, they're simply driver or USB problems. Any malfunctioning USB device will give you that same sequence. Anyways, it's difficult to get out of a boot-loop without ADB so let's try to get that USB working again.
First, do you have a bootloader (like FFF) or a recovery (like TWRP) loaded? I'm not sure the USB driver will work during boot without at least one of those installed.
Second, boot into TWRP, then try to fix the USB from the computer end. Uninstall the drivers, download a fresh batch, reinstall drivers, reboot. Use explorer to check %userprofile%\.android\adb_usb.ini and make sure 0x1949 is there. Also check Kindle Fire Utility\drivers\kindle\android_winusb.inf and make sure whatever hardware ID is showing up in device manager is in there.
BTW, what device IS showing in Device Manager after the disconnect? Use right click, scan for hardware changes.
Third, the USB cable or ports themselves may be at fault. Try a different cable, and try a different computer. Also, reboot often.

hunterhk said:
Rapid disconnects are nothing unique, they're simply driver or USB problems. Any malfunctioning USB device will give you that same sequence. Anyways, it's difficult to get out of a boot-loop without ADB so let's try to get that USB working again.
First, do you have a bootloader (like FFF) or a recovery (like TWRP) loaded? I'm not sure the USB driver will work during boot without at least one of those installed.
Second, boot into TWRP, then try to fix the USB from the computer end. Uninstall the drivers, download a fresh batch, reinstall drivers, reboot. Use explorer to check %userprofile%\.android\adb_usb.ini and make sure 0x1949 is there. Also check Kindle Fire Utility\drivers\kindle\android_winusb.inf and make sure whatever hardware ID is showing up in device manager is in there.
BTW, what device IS showing in Device Manager after the disconnect? Use right click, scan for hardware changes.
Third, the USB cable or ports themselves may be at fault. Try a different cable, and try a different computer. Also, reboot often.
Click to expand...
Click to collapse
Thanks for your response, I will go through these and report back when I get back home from class.

ok, now I have my kindle being recognized by my computer as "android phone" with the sub of "android adb interface." If I have read the guide correctly that means it is in fastboot mode. However when I open kfu it says the kindle is offline.
If someone would be willing to help me out through Skype I would gladly appreciate it. I'm really at a lose as to what to do at this point.
and no stupidly I do not have FFF or TWRP loaded, since I first rooted it when I was a super noob. The usb driver seems like it should be able to work according the the Kindle fire beginners guide, but KFU does not recognize the kindle even though my computer does.

Normal Factory Cable Process Does Not Work

I have searched and read a bunch and have not stumbled upon my situation.
Hopefully someone can shed some light on my use of a factory cable.
Bought a cable from SkOrPn - great guy and very helpful. We thought maybe the problem was the cable so he sent out another. TO BE CLEAR, ISSUE IS NOT WITH SkOrPn's CABLE. Both cables yield the same results.
So, here's the deal:
I have 2 KFs that where bone stock. I used KFU to root, install TWRP and FFF 1.5 Bootloader. All worked fine and I subsequently installed CM11. So all is good.
Now when I try to use the Factory Cable as instructed
Factory cable - Using a factory cable is the most straightforward method of enabling fastboot mode on the Kindle Fire and it will work with any bootloader. With the device off, plug the cable into the Kindle Fire, then the computer and the device will boot up directly into fastboot mode. No other user intervention is required.
Click to expand...
Click to collapse
But when I plug the Fcable into the fire it immediately powers on and boots normally, skipping fastboot mode. This happens with or without plugging the other end into the PC.
So SkOrPn suggested I try plugging into the PC 1st and then the fire. This does boot to fastboot mode. So now I unplug the Fcable and using a "normal" cable plug the fire back into my PC. Now I get an error message saying that the USB device cannot be installed and of course KFU/ADB/fastboot does not recognize my device. So I am (or appear to be) in fastboot mode, but can't communicate with my fire. Keep in mind I have KFU working, so I know drivers are installed.
Any thoughts?
And the above is the same for BOTH fires.
Luckly I am fully rooted with FFF 1.5 and CM11, so I really dont need to use the factory cable. But I would like to figure this out BEFORE I need it!

micl9 said:
...So SkOrPn suggested I try plugging into the PC 1st and then the fire. This does boot to fastboot mode. So now I unplug the Fcable and using a "normal" cable plug the fire back into my PC. Now I get an error message saying that the USB device cannot be installed and of course KFU/ADB/fastboot does not recognize my device. So I am (or appear to be) in fastboot mode, but can't communicate with my fire. Keep in mind I have KFU working, so I know drivers are installed.
Any thoughts?
And the above is the same for BOTH fires...
Click to expand...
Click to collapse
Just because you can run kfu, and you got your kindles rooted, that doesn't necessarily mean your drivers are installed properly.
I would uninstall and reinstall your drivers just to check.
Also, when you plug in your kindle in fastboot mode, does you're computer list it as a fastboot device? (Command Prompt, cd to folder with KFU tools are and adb.exe and fastboot.exe are, then type fastboot devices; a string of characters is good, while nothing is bad)
If that doesn't work, can you use kfu to reboot your kindles into fastboot?
Sent from my Nexus 7 using Tapatalk

I tried uninstalling and re-installing drivers - might try a fresh computer
When connected in fastboot mode devices command comes back with nothing.
I will try using KFU to put the kindle into fastboot when I get home tonight.
Update:
OK so KFU can put it into fastboot - witch matches behavior using cable, so now I know that works.
And my PC does not recognize the kindle in fastboot mode. Tried UN-installing and re-installing drivers with no luck. As this has been my "hackers" laptop for quite a while there is no telling what driver ghosts remain.
Will give it a shot on another PC.
Still kinda odd that my Kindles require a different factory cable procedure to get into fastboot mode.

Post once you try it on a fresh PC.
Sent from my Nexus 7 using Tapatalk

Ok most issues are resolved
KFU
Apparently while in fastboot mode KFU will report status unknown, but using bootmode menu to change back to Normal works.
Also using adb devices in fastboot mode returns nothing, using fastboot getvar product returns kindle!
For these 2 I should have read more - sorry
USB reporting device cannot be installed after having device in fastboot mode via factory cable.
OK this one I got some bad info that said the factory cable is not used for flashing - only for getting device into fastboot mode.
What I was doing wrong - using Fcable to get into fastboot and then swapping the Fcable out for a std USB cable - this results in the device cannot be installed error and kindle not being seen by fastboot commands.
What I should do - using Fcable to get into fastboot mode AND using it for the data communication as well (ie DONT unplug the Fcable!).
Last (and still open) issue
Why my devices don't use the normal factory cable process (plug into Kindle and then PC) - but only works by plugging PC end 1st and then Kindle.
but I am not sure this matters anymore.
jma9454 thanks for chiming in!

[Q] Unrecoverable/bricked FireTV

So, I think in my haste to remove root and go back to stock, I have bricked my firetv. I can no longer connect via ADB. I have tried using a usb-a male to male x-fer cable to connect via computer, to no avail.
My firetv just sits at the white amazon logo. I have connected a keyboard and tried the alt-i-print screen (numerous times) as well as hitting the home button. It appears as if it is just completely unresponsive. I have even tried loading a rom onto a FAT 32 thumb drive, renamed it update.zip and hoped that it would pick up the file upon reboot (I got this idea from another thread here)....also to no avail.
I think the thing is beyond hosed and may have to swap one out at the local big-box store.
Does anyone have any other ideas, because I'm all out.
Thanks!

When you connect an A-to-A USB cable, does it show up listed when you type "fastboot devices"? (Note that you should connect the cable while the Fire TV is powered off, then plug in the power with it already connected to your PC.)

AFTVnews.com said:
When you connect an A-to-A USB cable, does it show up listed when you type "fastboot devices"? (Note that you should connect the cable while the Fire TV is powered off, then plug in the power with it already connected to your PC.)
Click to expand...
Click to collapse
It does not. I've tried several times to reboot while connected to the computer. I believe the transfer cable to be good because it is brand new and the software/drivers run/get installed when the cord was plugged in. The firetv box, the best I can tell, is just completely unresponsive. Beyond 'booting' to the amazon white logo, it does nothing and responds to nothing.

Rex_Kramer said:
It does not. I've tried several times to reboot while connected to the computer. I believe the transfer cable to be good because it is brand new and the software/drivers run/get installed when the cord was plugged in. The firetv box, the best I can tell, is just completely unresponsive. Beyond 'booting' to the amazon white logo, it does nothing and responds to nothing.
Click to expand...
Click to collapse
what does device manager show the device as? also maybe try uninstalling the driver and reinstalling it as a generic fastboot/adb driver

thoughtlesskyle said:
what does device manager show the device as? also maybe try uninstalling the driver and reinstalling it as a generic fastboot/adb driver
Click to expand...
Click to collapse
It doesn't show anything (I have also included the adb devices call, too)

Rex_Kramer said:
It doesn't show anything (I have also included the adb devices call, too)
Click to expand...
Click to collapse
So device manager shows nothing
Sent from my ASUS_Z00AD using Tapatalk

thoughtlesskyle said:
So device manager shows nothing
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Nothing obvious. I've expanded every node and see nothing other than some generic USB hubs and controllers, but nothing different when the devices is attached to the transfer cable than when it's not.

Device recognized in ADB but not in fastboot

Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?

I seem to remember the same thing happening when I got mine a couple days ago and unlocked the BL within a few hours of unboxing. I ended up doing the standard unlock followed by unlock critical commands anyway. Worked fine for me.

morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
Try just turning the phone off and then entering fastboot via volume down and power button. THEN, plus in your phone. Do a 'fastboot devices' and see if it shows up now. In my experience, I got my phone...checked oem unlock and all that...booted into fastboot mode via hard method. And my phone is detected instantly. I did not install any drivers, update platform tools (mine is from like 2012), and even used a third-party USB-C cable. It works every time. Also, I am using the adb and fastboot executables from an older adb minimal set. Probably from like a year or so ago. I don't ever use the SDK ones really anymore.

morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
I'd check and make sure your adb/fastboot is up to date, or do a reinstall just in case.

There are so many options for adb/fastboot and drivers. Where does one find "the latest," that everyone is speaking of?

Thanks for the suggestions but still not working. Even tried disabling driver signature verification at startup. I'm going to uninstall everything, factory reset the device and start over. Might also try a usb-c to usb-a cable. Any other thoughts?
Update: Nothing worked until I used a usb-c to usb-a cable, then it worked like a charm. Must be a Lenovo thing.

morrowa2 said:
Thanks for the suggestions but still not working. Even tried disabling driver signature verification at startup. I'm going to uninstall everything, factory reset the device and start over. Might also try a usb-c to usb-a cable. Any other thoughts?
Update: Nothing worked until I used a usb-c to usb-a cable, then it worked like a charm. Must be a Lenovo thing.
Click to expand...
Click to collapse
I can't even get adb to recognize my device ....I have used multiple cables I'm about to return this phone

canemaxx said:
I can't even get adb to recognize my device ....I have used multiple cables I'm about to return this phone
Click to expand...
Click to collapse
have you tried a usb-c to usb-a cable. that worked for me.

morrowa2 said:
There are so many options for adb/fastboot and drivers. Where does one find "the latest," that everyone is speaking of?
Click to expand...
Click to collapse
Latest ADB/fastboot: https://developer.android.com/studio/releases/platform-tools.html
Latest USB driver: https://developer.android.com/studio/run/win-usb.html

I had no luck except about once in 20 it'd work. Then swapped to a different USB-C port on my laptop, then it worked. FWIW, I tried USB-C to USB-C and USB-C --> USB-A (adapter) to USB-C and it didn't make a difference.

js042507 said:
Try just turning the phone off and then entering fastboot via volume down and power button. THEN, plus in your phone. Do a 'fastboot devices' and see if it shows up now. In my experience, I got my phone...checked oem unlock and all that...booted into fastboot mode via hard method. And my phone is detected instantly. I did not install any drivers, update platform tools (mine is from like 2012), and even used a third-party USB-C cable. It works every time. Also, I am using the adb and fastboot executables from an older adb minimal set. Probably from like a year or so ago. I don't ever use the SDK ones really anymore.
Click to expand...
Click to collapse
I did this and when in the bootloader screen, I am able to display fastboot devices, but when I go into recovery mode and try and flash something via ADB (the November patch since I am not pulling it OTA), it seems to start but it just sits at "Verifying update package" on the phone and "loading: 'taimen-ota-******.zip'" and never progresses. Almost like the PC and the phone are not talking properly?

tluley51 said:
I did this and when in the bootloader screen, I am able to display fastboot devices, but when I go into recovery mode and try and flash something via ADB (the November patch since I am not pulling it OTA), it seems to start but it just sits at "Verifying update package" on the phone and "loading: 'taimen-ota-******.zip'" and never progresses. Almost like the PC and the phone are not talking properly?
Click to expand...
Click to collapse
Like others have stated, maybe try a USB-C to regular USB-A cable. I have only used that type of cable, but didn't realize that the actual cable that comes with the phone might be a problem. I never used it to test that theory though.

js042507 said:
Like others have stated, maybe try a USB-C to regular USB-A cable. I have only used that type of cable, but didn't realize that the actual cable that comes with the phone might be a problem. I never used it to test that theory though.
Click to expand...
Click to collapse
Yeah that is all I have ever used. I use a USB A to C Cable Matters cable.

tluley51 said:
Yeah that is all I have ever used. I use a USB A to C Cable Matters cable.
Click to expand...
Click to collapse
I don't know then. I haven't attempted the update yet to provide any feedback. However, others have reported this issue in the 'November OTA' thread. I would look there.

morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
For anyone in the future, ensure the that Device Manager is showing the 'Android Composite ADB Interface' driver installed.
Then, just download the latest Platform Tools (from https://developer.android.com/studio/releases/platform-tools), and from inside that folder, open a Powershell prompt, and then 'adb reboot bootloader'. Once you are in the 'fastboot' mode, the 'fastboot devices' command works.

I had the same problem. I fixed it by plugging in my UBS-C to USB-A cable into a USB 3 port instead of a USB 2 port.

I am facing the same issue, its been almost 20 days. Tried everything but couldn't get it worked. So dropped the idea of rooting my px2L

My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com

cooltime said:
My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com
Click to expand...
Click to collapse
worked for me thanks.

cooltime said:
My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com
Click to expand...
Click to collapse
This works... Get the Google Driver.