I was restoring a nexus S to the factory image and I picked the soju image instead of the sojus image. After flashing the bootloader I lost USB connectivity, so can't see the device with adb or fastboot. I have USB debugging enabled, but USB debugging doesn't start when I plug in the USB cable. The phone is still useable, but this is a development phone, so without ADB it's pretty much useless.
So I'm wondering if anyone knows of a way to reinstall the correct bootloader without USB, i.e. wirelessly? The bootloader is unlocked but doesn't have su or CWM on it.
Thanks in advance!
Related
I have a T-Mobile Nexus S that has a bootloop. Its my friends so I dont know what he did to it. I can get to the bootloader but when I connect it to my computer it won't recognize it. I thought of a driver problem but i can't get past the bootloop to enable usb debugging. It also won't show up in device manager. The phone's usb port works. It will still charge. I just need to get rid of the bootloop. Any help would be greatly appreciated. Thanks!
MAGnum_21 said:
I have a T-Mobile Nexus S that has a bootloop. Its my friends so I dont know what he did to it. I can get to the bootloader but when I connect it to my computer it won't recognize it. I thought of a driver problem but i can't get past the bootloop to enable usb debugging. It also won't show up in device manager. The phone's usb port works. It will still charge. I just need to get rid of the bootloop. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
If it has a custom recovery, boot into it and wipe data/factory reset.
If it does not, flash a custom recovery. These forums are chockful on guides how to root, flash stuff and fix bootloops.
I looked up how to install recoveries but when i plug in my nexus to my computer it is not recognized. At the bottom of the bootloader screen it says "USB Control Init" and then "USB Control Init End". I do have the proper drivers installed. Is there a fix for this?
Are you sure that you have the correct drivers installed, though?
It's known that people who use Windows have a lot of success with the PDAnet drivers (you can search around here for those), rather then with the standard USB drivers the Google SDK provides.
Greetz
Did you try to run "fastboot devices" in command prompt while it's at fastboot mode and plugged into the PC? What do you see as the result? The guides on XDA should help, but you may also head over to nexusshacks_dot_com for more references.
Sent from my Nexus S using XDA App
With pdanet it requires me to plug in my phone with usb debugging turned on to get the drivers with i cant do because of the bootloop. and when i go into command prompt it says "waiting for device" and won't recognize it. Thanks for the help
My USB doesn't connect to a computer because it is broken some how and only charges. But I was wondering if there was a way to root my Nexus S without a USB cable, my bootloader is unlocked.
I was wondering if I could do it wirelessly or idk. Any suggestions/help?
If you're on the lasted stock (4.0.4) and you don't already have a custom recovery you're screwed.
Nearly impossible without a USB connection since you will need adb to flash at least a custom recovery like CWM or TWRP. Have you verified that you have the USB driver installed? Have you tried a different USB cable?
I'm wondering if anyone has run into this problem before?
I'm trying to unlock the bootloader on my friend's Photon Q, I downloaded the SDK and installed the Motorola drivers. But when I put his phone into Fastboot mode, the "fastboot oem get_unlock_data" command does not work and CMD just says waiting for devices.
Yes I'm shift+right clicking on the platform-tools folder in the SDK to run the Command Prompt and I did download the correct Fastboot file. The command "adb devices" shows nothing when his phone is plugged in, but it shows my own phone (A Motorola Droid Bionic) when it's plugged into the USB cable. RSD Lite also recognizes both phones when powered on or in Fastboot mode.
I have no idea what to do at this point, we just need to get that unlock data to plug into the Moto site. Would it be possible to use someone else's unlock key or is each one randomized individually for the device? Or would that even work because my computer can't do the command for the unlock data, so maybe it couldn't push the unlock key onto the phone?
quick thought: did you enable usb debugging on the device?
edit: i guess that wouldn't make any difference in fastboot mode...
anyway, yeah, i'm pretty sure each device has it's own unique code. it's odd that fastboot recognizes the device, but the command isn't working. i bet you will get it somehow tho. a similar thing actually does happen to me sometimes, and in my case, it is because my usb ports are going bad and the computer loses connection with the phone.
Man nobody has anything eh? That's a crying shame. I tried using a different computer and went through the same course and still nothing.
I did try USB debugging on and off on both machines, didn't change a thing.
In order for the drivers (and therefore adb) to pick up the phone, I needed usb debugging *and* the phone not to be in charge only mode. Maybe that will help?
If not, when you reboot to fastboot and connect the cable, look at the devices installing list (if win 7) or device manager, and confirm the pc sees the fastboot device. If not you may need to reinstall the driver. Strange I know, but I needed to after getting my unlock data, holding off on unlocking due to the warranty voiding note, then trying again a couple days later where it wouldn't recognize. Seems to be finicky drivers to match a finicky device. But I do love this keyboard lol...
Sent from my XT897 using Tapatalk 2
We've only ever tried it in MTP mode and USB debugging enabled. This is day three of plugging it in and pulling it out and still no go. This is a royal pain, that is for sure.
Download Motorola Device Manager from the website, install, plug in phone. Place the phone into mass storage mode WITHOUT debugging enabled, then other modes, then back into bootloader mode then into fastboot mode. This will install EVERY driver, I didn't see that as one of the things tried.
Once you are in those modes, Android ADB device driver will install.
Hope that helps...
Sent from my XT897 using xda premium
I lost root after updating the OS. So I want to root the phone. When the phone is in the system, it is OK to connect to my computer, and ADB is also OK. But when I boot into fastboot mode, it just can't connect to the computer no matter the computer is mine or my friend's. I have installed the driver....
USB debugging turned on?
I can help you with that, tell me if you still have the same problem.
Usb debugging makes no difference in fastboot mode. Adb doesn't do anything in fastboot mode. Fastboot works with fastboot mode. If you don't know this simple fact, you will likely screw up your phone trying to root it. I suggest you do some reading.
Just switch to you routed slot and root the update from there. Then switch back.
i was trying to install a custom ROM and wiped all the partitions. I accidentally rebooted my Xiaomi redmi note 8 and now it is stuck in fastboot. i tried to flash TWRP using ADB however it shows that it is waiting for device. (I'm guessing that the USB DEBUGGING turned off). Anyone know how to fix this? Thanks in advance!
I would try possibly checking drivers on your computer, or just try a different cable. USB Debugging is not necessarily a thing in fastboot. Or, better said, there is not a toggle switch for turning on USB access. Plugging in a USB cable gives you full access to fastboot commands on the device that you're using. If that doesn't work, you might want to try checking out the Redmi Note 8 sub-forums since others might have the same issue. Try drivers and/or cable changes and share the results