![]() It would not detect it on its own, or even use the SONY driver without me telling it to specifically. opened windows device manager found my "discovered device" and forced it to use the SONY driver downloaded from sonys website.everything worked following these instructions here.device manager> "andorid" > properties > update driver > browse computer for driver > installed sony driver ![]() FAILED (remote: unknown command) finished. opened windows device manager found my "discovered device" and forced it to use the SONY driver downloaded from sonys website. When I connect with fastbot, I get this: Code: C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices WGMBMRMNQW6TMNNN fastboot C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info."adb reboot bootloader" used from windows PC.I downloaded and used platform tools version 33.0.3 NOT version 34.The windows drivers behave differently between the two. There is definitely a difference between going into fastboot through the phone itself and through adb commands on PC.įastboot through the phone shows the drop down menu and no blue light illuminated on phone.įastboot through adb phone is black screen with a blue light on right corner on the phone. I'm on day 3 of trying to get the phone to bootload.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |