Database Users

Please Help! USB Debugging related

I am having problems with my N7 not connecting to my desktop. I can get into bootloader and recovery but I can not mount USB to add a rom. I'm SOL as of right now and have no clue what to do...

uitfenc families
makross said:
I am having problems with my N7 not connecting to my desktop. I can get into bootloader and recovery but I can not mount USB to add a rom. I'm SOL as of right now and have no clue what to do...
Click to expand...
Click to collapse
Could it be related to this issue:
http://forum.xda-developers.com/showthread.php?t=1821536
If you have plugged your Nexus 7 on a car charger, the usb might be dead and only be used for charging (and so unable to transfer new ROM data).

charging is fine...is it possible that I did not enable usb debugging before i wiped to factory reset that it would prevent me from connecting???

alright heres alil update i tried using WUGS toolkit and trying to unroot everything was going fine until it cannot find the flashstock.bat...now im back to square one. i cant find the flashstock.bat anywhere

I was having the same problem. It would see the camera mode, but not the mtp. I read in another thread to turn off debugging in settings. What do you know. It worked! Computer sees the tablet now just fine.:victory:

Help required - Bootloader only

Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks

herghost said:
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
Click to expand...
Click to collapse
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers

jombo2323 said:
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
Click to expand...
Click to collapse
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue

herghost said:
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
Click to expand...
Click to collapse
you are 100% positive you did EXACTLY what i said?

I have no idea what went wrong
That's the problem with toolkits though. People don't know what they're doing and when something goes wrong you don't know how to fix it!! I understand where toolkits come from, but they are only useful if you know what happens in the background when you click on a button.

Thread Moved
Thread belongs in Q&A. Not the Dev Forum
Post moved.
MD

I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck

erica_renee said:
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
Click to expand...
Click to collapse
You Star
Put me on the right track, my PC was basically assuming that it was my S3, in the end I removed everything with samsung in it from the registry, uninstalled all the drivers then tried again, correctly showing as a nexus and not a samsung

[Q] Nexus 7 - No Charge, No USB Connection

Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!

DTTD said:
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
Click to expand...
Click to collapse
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!

Fallon9111 said:
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Click to expand...
Click to collapse
Thanks for providing more information on this. I have done a Factory Reset via Settings and also via Recovery, but still not available.
I think I'm making progress with adb via Ubuntu over USB, but USB Debugging still gives the Epic crash and still will not charge while On, which is more just annoying than anything else.
Asus/Google Support are saying it is a physical pin issue, but that doesn't explain why USB Debugging is failing. Does anyone know where the USB files are contained? I'm wondering if I've messed up at the Kernel level. Any thoughts?

About my Nexus - More Info
I forgot that I should provide more information about what I'm running:
Phone: Nexus 7
Android Version: 4.2.2
Kernel version: 3.1.10-g05b777c
Build number: JDQ39
Prior to issue also had:
Recovery: TWRP
ROM: Stock JDQ39
MultiROM: Yes

UPDATE
So after more work on my Ubuntu we have found more information and seem to have narrowed down the issue! :fingers-crossed:
I have been able to flash via Fastboot just fine, which has thus allowed me to get TWRP installed and now I'm back rooted. I still cannot adb via USB though. We've double checked with multiple Nexus 7's of the same type, which allow command: adb devices and their devices will show, while it does not for my device. (Side note: my version of Ubuntu does not "see" the adb command in its pwd so... But tests have been done on other machines and worked...)
So after sifting down to adb issues, we found that in /data/property I'm missing persist.sys.root_access and persist.sys.usb.config ... But creation of persist.sys.usb.config didn't do anything...

Nexus 7 2012 - No Command Error !!

Hy everyone
Few days ago I've tried to update my Nexus 7 2012 model, from 4.2.2 operating system to 4.4. After few minutes, after reboot, on the screen shows the Android sign with an error mesage : No Command
The bigger problem is that in my Device Manager, my computer does not show the tablet, not even as an unknown device. This is how my Device Manger it is looks like:
I have tried all the internet tutorials, SDK Manager Drivers, PdaNet Drivers .. Nexus Toolkit .. and no results. My computer does not recognize the tablet, When i run abd devices .. returns nothing.
As i can't go inside, i'm not sure if the USB Debugging mode is activated or deactivated.
Please help me !!! I really don't know what to do
PS: When i'm trying to install the driver manually it says; Android ADB Interface - This device cannot start. (Code 10)

Can you boot into recovery or fastboot mode?
Sent from one of my 47 iPads running android C3P0

Captain Sweatpants said:
Can you boot into recovery or fastboot mode?
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
When i'm pressing power button+u up volume+down volume and chose recovery mode, after loading, i'm getting the same error, with the android sign and No Command error message.
When i am in fastboot mode, is the same problem, the device manager doesn't recognize the tablet, neither the adb or fastboot.

Is the tablet going into fastboot mode and not being recognised by the computer or is it not going into fastboot mode. If you can get fastboot mode the next stop would be to try the nexus toolkit http://www.wugfresh.com/nrt/ use the return to stock soft bricked option as far as the problems connecting to the computer did it connect before the boot loop and is it possible the port or the cable are damaged? If it goes into fast boot then it should be recognised.
Edit: I forgot to ask is your warranty still valid you get 2 years with the N7 you could send it to Asus.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:56 PM ---------- Previous post was at 09:23 PM ----------
Also read/try this
http://forum.xda-developers.com/showthread.php?t=2405740&page=4
Sent from my Nexus 7 using xda app-developers app

Captain Sweatpants said:
Is the tablet going into fastboot mode and not being recognised by the computer or is it not going into fastboot mode. If you can get fastboot mode the next stop would be to try the nexus toolkit http://www.wugfresh.com/nrt/ use the return to stock soft bricked option as far as the problems connecting to the computer did it connect before the boot loop and is it possible the port or the cable are damaged? If it goes into fast boot then it should be recognised.
Edit: I forgot to ask is your warranty still valid you get 2 years with the N7 you could send it to Asus.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:56 PM ---------- Previous post was at 09:23 PM ----------
Also read/try this
http://forum.xda-developers.com/showthread.php?t=2405740&page=4
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the reply. I can boot in fastboot but the PC still do not recognize the tablet. Even in fast boot Nexus Toolkit doesn't recognize the tablet .. I've tried to uninstall and reinstall the drivers but no success.

Is RMA an option? Was this an OTA update? Asus may take some responsibility for it then. Did the computer recognise the tablet before the problem we need to work out if its a software or a hardware problem that's stopping it from connecting to the computer.
Sent from one of my 47 iPads running android C3P0

Captain Sweatpants said:
Is RMA an option? Was this an OTA update? Asus may take some responsibility for it then. Did the computer recognise the tablet before the problem we need to work out if its a software or a hardware problem that's stopping it from connecting to the computer.
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
What means RMA ? .. the update was made by wireless connections. Unfortunately I'm in Romania now and the tablet was bought in USA., so I don't think Assus warranty is an option.
The computer was not recognizing the tablet before the update .. it was only charging but not recognizing. Every time I was uploading content on it over Dropbox.
The only time when my PC recognized the tablet was at the beginning, I don't know if I changed something or what I did but after that point the PC didn't recognize the tablet.. Even after that the tablet updates and everything was working perfectly.

RMA is Return Merchandise Authorisation it means Asus agreeing to accept a return. If the tablet was not connecting to the computer before the update then that is where the problem is. No Command bootloop is fixable but not without a USB connection. My advice would be to try a new USB port for the nexus you can get one on eBay UK try to find one that will ship to romania. The other option is to buy a N7 with a broken screen and use parts out of that. Its not much more expensive to buy a broken N7 than to buy the charging port. The advantage to that is you can swap the motherboard as well and you don't need to fix the boot loop.
Sent from one of my 47 iPads running android C3P0

Captain Sweatpants said:
RMA is Return Merchandise Authorisation it means Asus agreeing to accept a return. If the tablet was not connecting to the computer before the update then that is where the problem is. No Command bootloop is fixable but not without a USB connection. My advice would be to try a new USB port for the nexus you can get one on eBay UK try to find one that will ship to romania. The other option is to buy a N7 with a broken screen and use parts out of that. Its not much more expensive to buy a broken N7 than to buy the charging port. The advantage to that is you can swap the motherboard as well and you don't need to fix the boot loop.
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
Thank you for the reply. But is the tablet is charging properly both from the PC and from the wall charger. It is possible to charge properly but the data transfer to be broken because of the micro usb from nexus 7 ?

Yes it is possible to damage the data circuit while leaving the charging circuit intact unfortunately unless you know much about micro electronics I can't tell you exactly where that damage is but it definetly sounds like a hardware failure. My best guess would be the USB port. On the Nexus the USB port is separate from the motherboard and is connected by a ribbon cable. The other possibility is that the motherboard is at fault. As the motherboard is where the bootloop is happening from changing it would also make the tablet work. Either way the only way to get your nexus working again is to fix the USB connection and it sounds like that's going to mean new parts.
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

Captain Sweatpants said:
Yes it is possible to damage the data circuit while leaving the charging circuit intact unfortunately unless you know much about micro electronics I can't tell you exactly where that damage is but it definetly sounds like a hardware failure. My best guess would be the USB port. On the Nexus the USB port is separate from the motherboard and is connected by a ribbon cable. The other possibility is that the motherboard is at fault. As the motherboard is where the bootloop is happening from changing it would also make the tablet work. Either way the only way to get your nexus working again is to fix the USB connection and it sounds like that's going to mean new parts.
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Click to expand...
Click to collapse
Anybody know how I can test it the USB is broken ? As long is charging well both from the PC and from the wall charger too, but is the PC is not recognizing the tablet.
Thank you for the reply. But is the tablet is charging properly both from the PC and from the wall charger. It is possible to charge properly but the data transfer to be broken because of the micro usb from nexus 7 ?
Click to expand...
Click to collapse

alpinia said:
Anybody know how I can test it the USB is broken ? As long is charging well both from the PC and from the wall charger too, but is the PC is not recognizing the tablet.
Click to expand...
Click to collapse
OK, so I've changed the micro USB from my tablet, I've putted on another tablet and it works perfectly. I've tried with the other micro usb and the same problem, the PC doesn't see the tablet.
The PC saw the other tablet .. but it can't see mine.
SO the problem is not with the USB port, is with something else. Is possible to erase everything from my tablet .. so the pc cant see the tablet in fast boot mode ?
Is any option to install the operating system on my tablet without PC ? I don;t know .. with an usb stick or something ..

alpinia said:
OK, so I've changed the micro USB from my tablet, I've putted on another tablet and it works perfectly. I've tried with the other micro usb and the same problem, the PC doesn't see the tablet.
The PC saw the other tablet .. but it can't see mine.
SO the problem is not with the USB port, is with something else. Is possible to erase everything from my tablet .. so the pc cant see the tablet in fast boot mode ?
Is any option to install the operating system on my tablet without PC ? I don;t know .. with an usb stick or something ..
Click to expand...
Click to collapse
Any solutions ?

Back in November 2013, my rooted Nexus 7 took the OTA update to Kit Kat and had been in the No Command loop ever since.
I tried repeatedly to get my PC (4 of the each with multiple OS's XP, Win7, Win8.1) to recognize the N7 in connection with the Wugfresh kit. I followed the instructions step by step, still nothing. Finally yesterday after wiping an XP machine and replacing it with an up to date image (as of Oct 2013). I again started the process. 1. Downloaded and fired up Newest Wugfresh kit, allowed it to update; 2. Turned on the N7, put it into recovery mode; 3, Plug the N7 in and removed in Device Mgr whatever drivers XP opened (It found it as an Android device), looked in USBD for but found no other device matching the description in in Wugfresh. 3. Rebooted PC and plugged the N7. Loaded Wugfresh, since the N7 was essentially "dead" I skipped Step 2 and proceeded to Step 3 and loaded the recommended drivers 1 (Universal Drivers); went to step 4 and did the FULL DRIVER TEST. As per usual the klt could not find the ADB device. I was ready to pack it in, but earlier I had noticed the "safely remove device Icon" pop on the lower right hand corner of my screen when I ist plugged in the N7. It seems that XP had again recognized the device when I plugged it in. I clicked out of the driver install dialogue and went back to the Wugfresh tool kit main page and under "Back to Stock" clicked "soft-Bricked/Bootloop" and low and behold it started to work. It took a while, but unlike the numerous times I tried before, data was finally moving to the N7. I left it even after I saw "XXX not found" and then another "XXX2 file not found". It finally finished and I again had life on my N7. I Ieft Wugfresh running (even after I thought it was done, wait until it says...Done) l and followed the suggestions the Wugfresh kit made and it finally works again. It has kit kat installed and I'm leaving it unrooted......for now anyway.
Kit Kat update: longest damn update ever.

odd
alpinia said:
Hy everyone
Few days ago I've tried to update my Nexus 7 2012 model, from 4.2.2 operating system to 4.4. After few minutes, after reboot, on the screen shows the Android sign with an error mesage : No Command
The bigger problem is that in my Device Manager, my computer does not show the tablet, not even as an unknown device. This is how my Device Manger it is looks like:
I have tried all the internet tutorials, SDK Manager Drivers, PdaNet Drivers .. Nexus Toolkit .. and no results. My computer does not recognize the tablet, When i run abd devices .. returns nothing.
As i can't go inside, i'm not sure if the USB Debugging mode is activated or deactivated.
Please help me !!! I really don't know what to do
PS: When i'm trying to install the driver manually it says; Android ADB Interface - This device cannot start. (Code 10)
Click to expand...
Click to collapse
try restoring or using a custom rom!

My husbands pad is stuck in the same state, nothing irretrievable on it, so if I could get it back to factory settings, would be fine. Tried the toolkit, followed it, but not recognising it on the pc.
Can get it to display the Recovery mode, but if I try to select any of the options, it just switches off. Just keeps switching on and off if I leave it connected to pc, charges with either pc or cable.
Totally drained the battery to see if it helped, well getting to the stage to try anything.
Display when into Recovery screen
Fastboot Mode
Product Name - Flo
Variant flo 32g
HW Version - rev_e
Bootloader version - FLO-04.08
Carrier Info - None
Serial Number
Signing - Yes
Secure Boot - enabled
Lock state - locked

[Q] HELP with recovery, no usb access to nexus 7, not detecting with official cable.

Ok so long story short, i have a nexus 7 2012 which a rooted and installed cyanogen mod.
I was using it as a car install and works perfect, i'm using an otg cable to mount usb sticks, triggering soft shutdown and powering the nexus etc. So usb seems to be working fine.
Basically i removed the tablet it to modify the bootloader to turn on automatically with ac power applied, if the battery runs out i have to manually power on with button, but now i'm running into a problem.
Ever since taking the tablet out and trying to connect over usb, none of my computers detect the tablet.
I've tried different operating systems, drivers, cables etc etc.
Also changed from mtp to ptp in storage and also turned on usb debugging mode. If i connect an otg cable the nexus see's the otg and i can mount usb's etc.
So i thought i might try recover the nexus back to factory, maybe there was an issue with the rom corrupted etc, I've downloaded the original 4.2.2 firmware which is currently installed.
Booted into recovery and tried re-installing the 4.2.2 zip, it keeps aborting. A guy in work tried to use sideloader and connect via adb. no luck.
I'm not very familiar with the android platform so i've no other ideas what to do and other idea's how to recover now.
The guy i work with mentioned using a usb jig, would that be the way to go or can anyone else suggest some else that might help.
Thanks

Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.

Does adb see the device

jadesse said:
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Click to expand...
Click to collapse
I last connected the nexus to the laptop a few monts back to load some music onto it, didn't have a problem. It's only been connected to a computer maybe 3 times. once to root/rom it then another few times to load music etc.
I can't see why the usb board maybe faulty as i can read data from a usb key when the otg cable is connected.
It's a strange one. You could be right, i might try pick up a broken nexus and swap some parts. Usb board etc.

crusrod said:
Does adb see the device
Click to expand...
Click to collapse
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc

foster182 said:
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
Click to expand...
Click to collapse
I am having this same problem on my (unrooted) HTC One after attempting to "convert" it from an AT&T to a Google Play Edition device with the procedure described here.
As part of the procedure, I attempted to flash the stock Google Play Edition ROM using fastboot commands, but I got an error message. The instructions say to just try the flash again, but the phone no longer connects properly via USB (error 10) while in bootloader mode. While in bootloader mode, the phone indicates there is some sort of problem (a line showing the OS version is highlighted in red), and attempting to enter recovery mode does nothing but display a phone with a big red X in it. The phone seems to operate fine and responds to ADB commands when the phone is fully booted, albeit with the old OS (not Google Play Edition) still in place.
Any Android device could theoretically get in this state. We're sort of "paralyzed", because everything we want to do to regain control of the bootloader and fix the situation seems to require issuing fastboot commands from a computer connected to the phone while it's in bootloader mode. Yet entering recovery mode or getting a computer to connect to it via USB no longer seems possible.
I wonder if there's another way to issue fastboot commands without relying on the USB connection to a computer?