Hi, I've got a Nexus S 4g. I recently tried to flash it with the stock Jelly Bean image from Google's developer page - developers.google.com/android/nexus/images. While I was running flash-all.sh, the flash appeared to finish, and my terminal just said <waiting for device>. The device does boot up, and is functional, however, I can't get this thing to connect to any of my PCs via USB.
I've plugged it into my 12.10 Ubuntu laptop, and run lsusb. The device isn't listed at all, so adb doesn't work. I've also booted the phone into fastboot, and lsusb still doesn't list it (so fastboot devices doesn't list anything either). I've also plugged it into my Arch box, and tried the same steps with the same results. Before I flashed the phone, I was able to debug just fine on both machines.
Has anyone seen this behavior before? Is there any way to fix it? I've spent a bunch of time searching around for this problem, and haven't seen much. Thanks.
Well, crap. It looks like I flashed the wrong image to my phone. I've got a Nexus S 4G (d720), and it appears I flashed the i9020 image. That's what has probably caused my issue. Does anyone know if there's any way to recover from this?
Rephrase: Do you have unlocked bootloader?
Do you have adb and fastboot drivers installed?
Do you have debugging enabled in devoper settings?
kwibis said:
Rephrase: Do you have unlocked bootloader?
Do you have adb and fastboot drivers installed?
Do you have debugging enabled in devoper settings?
Click to expand...
Click to collapse
no need to have debbuging mode on
kwibis said:
Rephrase: Do you have unlocked bootloader?
Click to expand...
Click to collapse
Yes
kwibis said:
Do you have adb and fastboot drivers installed?
Click to expand...
Click to collapse
Yes
kwibis said:
Do you have debugging enabled in devoper settings?
Click to expand...
Click to collapse
Yes
The problem is that I flashed the wrong image to my device. I'm pretty sure it's hosed. The phone works fine - it boots up, I can get on wifi, but I just can't connect via USB. The image I flashed must have different USB drivers than what my device has. It looks like I'm stuck with it, or I will see if someone can "unbrick" it, and flash the proper image to it.
Well since you have unlocked bootloader I guess you have custom recovery and are rooted as well. You can download a custom rom, safe your app data with titanium backup, factory reset and wipe cache in recovery and flash proper rom. Then the drivers should work again and you can flash the correct image if wanted.
Sent from my Nexus S
Related
PC does not see my Infinity
Always get waiting for devices when i try to flash recovery in fastboot
Can not boot into recovery no matter what i do
Can someone help me
did you run cmd as administrator and is the usb driver installed ?
cmd as administrator-Yes
APX driver is not installed,for some reason i can not do it.Downloaded them but can not update.I'm running out of ideas
enable media app
kpchico said:
PC does not see my Infinity
Always get waiting for devices when i try to flash recovery in fastboot
Can not boot into recovery no matter what i do
Can someone help me
Click to expand...
Click to collapse
You may have the media app disabled it happened to me I disabled it then PC wouldn't detect' enabled then everything was fine.
icecreampaintjob said:
You may have the media app disabled it happened to me I disabled it then PC wouldn't detect' enabled then everything was fine.
Click to expand...
Click to collapse
That doesn't explain while the OP is unable to boot into recovery, though? On what ROM are you (stock or custom, and what type/version)? Have you tried a reflash/update? What recovery do you have installed? We need a bit more info than this.
This is an increasingly common problem after JB update - there's lots of posts on it in the T201 thread. Currently there is no way out unless you ha NVflash installed.
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
brickdummy said:
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
Click to expand...
Click to collapse
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
brickdummy said:
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
Click to expand...
Click to collapse
I just went through some similar stuff. What type of computer are you using? PC/Mac? Are you using the original cable? What troubleshooting steps for connectivity have you done? Different cable? USB port?
Can you access the bootloader screen when you pull the battery and reboot while holding the volume button down and holding the power button? By accident, I found that the phone and PC will communicate with each other when "Fastboot" is selected on the bootloader screen (you should hear a connection chime and it should change to "Fastboot USB") except I could only get fastboot commands to work. The good news is that should be enough to flash a boot or whatever else you need to get back in business.
shadowboxx said:
I just went through some similar stuff. What type of computer are you using? PC/Mac? Are you using the original cable? What troubleshooting steps for connectivity have you done? Different cable? USB port?
Can you access the bootloader screen when you pull the battery and reboot while holding the volume button down and holding the power button? By accident, I found that the phone and PC will communicate with each other when "Fastboot" is selected on the bootloader screen (you should hear a connection chime and it should change to "Fastboot USB") except I could only get fastboot commands to work. The good news is that should be enough to flash a boot or whatever else you need to get back in business.
Click to expand...
Click to collapse
Hi, Thanks for the reply.I am using windows 7. I downloaded the drivers for HTC, and I am using a data cable and the USB port in the back of my computer, nearest the mother board. I do see "Fastboot USB" on the phone but when i type in the command prompt "adb devices" I get nothing.
brickdummy said:
Hi, Thanks for the reply.I am using windows 7. I downloaded the drivers for HTC, and I am using a data cable and the USB port in the back of my computer, nearest the mother board. I do see "Fastboot USB" on the phone but when i type in the command prompt "adb devices" I get nothing.
Click to expand...
Click to collapse
That's great you're getting the fastboot usb message! As long as you're not using a hub or some other usb extender, any functioning usb port on the pc will do. Again, I learned this by accident (ie the hard way) and found that in this mode, only fastboot commands will work, not adb. (on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Great test for connection: fastboot devices (if you get anything else except a serial # with fastboot after it, then close the cmd window, unplug, and pull battery/reboot to bootloader), fastboot reboot-bootloader. Once it reboots back into the bootloader screen, make sure you press the power button while fastboot is selected and you should again hear the chime and see fastboot usb come up. This is your phone saying it's ready to accept your fastboot commands.
Do let us know how it works.
bananagranola said:
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
Click to expand...
Click to collapse
Hi I actually saw your post earlier thank you. I will work on this. I found it in a tutorial when I rooted my phone with HTC dev, ace_recovery_ext_4.img. I'll post where i found it later.
bananagranola said:
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
Click to expand...
Click to collapse
when i flashboot the recovery.img file it goes to the red triangle.
brickdummy said:
Hi I actually saw your post earlier thank you. I will work on this. I found it in a tutorial when I rooted my phone with HTC dev, ace_recovery_ext_4.img. I'll post where i found it later.
Click to expand...
Click to collapse
Hi the program is actually called 4EXT Recovery Touch. I finally was able to open it through fastboot....Now all thats left is to find the right zip file to put my phone back to stock.
shadowboxx said:
That's great you're getting the fastboot usb message! As long as you're not using a hub or some other usb extender, any functioning usb port on the pc will do. Again, I learned this by accident (ie the hard way) and found that in this mode, only fastboot commands will work, not adb. (on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Great test for connection: fastboot devices (if you get anything else except a serial # with fastboot after it, then close the cmd window, unplug, and pull battery/reboot to bootloader), fastboot reboot-bootloader. Once it reboots back into the bootloader screen, make sure you press the power button while fastboot is selected and you should again hear the chime and see fastboot usb come up. This is your phone saying it's ready to accept your fastboot commands.
Do let us know how it works.
Click to expand...
Click to collapse
Hi, this did work, thank you. Would you happen to know how i can load the stock software on my phone? I had it rooted before im not sure if its still rooted. I also managed to get the 4ext recovery on my phone too.
shadowboxx said:
(on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Click to expand...
Click to collapse
As far as I know, fastboot only works when your phone is in fastboot mode. ADB works in recovery or system.
brickdummy said:
Hi, this did work, thank you. Would you happen to know how i can load the stock software on my phone? I had it rooted before im not sure if its still rooted. I also managed to get the 4ext recovery on my phone too.
Click to expand...
Click to collapse
Flash a rooted stock ROM from recovery. Whether you have root is in your system partition. Whether your bootloader is unlocked is in your bootloader. Whether you have a custom recovery is in your recovery partition. Three separate things.
As for your post in your other thread, read my signature.
bananagranola said:
As far as I know, fastboot only works when your phone is in fastboot mode. ADB works in recovery or system.
Flash a rooted stock ROM from recovery. Whether you have root is in your system partition. Whether your bootloader is unlocked is in your bootloader. Whether you have a custom recovery is in your recovery partition. Three separate things.
Click to expand...
Click to collapse
I'm sorry, I have no idea what I am doing. Can you show me the steps? When I try installing a stock rom zip file in my recovery from my sd card it aborts.
brickdummy said:
I'm sorry, I have no idea what I am doing. Can you show me the steps? When I try installing a stock rom zip file in my recovery from my sd card it aborts.
Click to expand...
Click to collapse
I'm guessing that you're trying to flash a PD98IMG.zip or a RUU. You need an actual stock rooted ROM, probably from here on the forum. Or just flash Android Revolution HD, an optimized rooted stock ROM, also from here on the forum in the development section. For more specific steps read the Ace Think Tank linked in my signature.
bananagranola said:
I'm guessing that you're trying to flash a PD98IMG.zip or a RUU. You need an actual stock rooted ROM, probably from here on the forum. Or just flash Android Revolution HD, an optimized rooted stock ROM, also from here on the forum in the development section. For more specific steps read the Ace Think Tank linked in my signature.
Click to expand...
Click to collapse
Ok, one more thing. I have S-ON. does that matter?
----
It did not, lol anyway it worked. Thank you everyone for you help. I really appreciate it.
-----
For those wondering I found the stock rooted rom here http://http://forum.xda-developers.com/showthread.php?t=996368
http://forum.xda-developers.com/showthread.php?p=26617631
Instructions to flash the rom
http://http://forum.xda-developers.com/showthread.php?t=2168500
brickdummy said:
Ok, one more thing. I have S-ON. does that matter?
Click to expand...
Click to collapse
Yes. You need to read the part in my signature about being stuck in the splash screen.
bananagranola said:
Yes. You need to read the part in my signature about being stuck in the splash screen.
Click to expand...
Click to collapse
ok, got it. Thank you again
Dear friends,
I have this problem: I got a brand new TCL S720 and the Google Play did not work, being a known rom issue. So, before doing anything, I've managed to make a backup of it's original rom with MTK Droid tools whichI supose it did it well. Then I've tried to install a CWM recovery to try a custom rom for it. The CWM recovery seemed to install succesfully but I didn't manage to install the new rom. If I remember well, it stucked on boot logo. Then tried to revert at it's original stock recovery, managed to have the phone back as it was in initial state, but doing more tries, It remained stucked on boot logo. The problem is that my computer doesn't recognise it anymore, when I connect it to USB it tries to install MTP usb driver but even before the driver was installed well, now it refuse to install, like the driver is not good or the proper driver doesn't exist. So the only thing I can do is to boot on stock recovery but even I tried to copy the original rom update.zip on external SD and to flash the phone using install update from sd card in recovery mode, It doesn't find the external sd card. So I'm stuck here, the computer doesn't detect the phone to try flashing it with SP flash tool or MTK Droid tool, and I also can't flash it from sd card. Have you any idea how to make it work again?
Thanks in advance.
I tried to install the android revolution hd one 71.1 on my phone and it went out good so far into the installation but after the installation, i rebooted my phone and it went to a boot logo then went to the TWRP recovery mode. i tried deleting the cache and doing a reset but nothing is happening. please help me.
patrickgrantm said:
I tried to install the android revolution hd one 71.1 on my phone and it went out good so far into the installation but after the installation, i rebooted my phone and it went to a boot logo then went to the TWRP recovery mode. i tried deleting the cache and doing a reset but nothing is happening. please help me.
Click to expand...
Click to collapse
Having the same problem. The phone only reboots into twrp recovery mode, yet shows no errors when re-flashing device with most recent version of sense ui.
I'd really like to be able to use my phone.
lurkeratthegate said:
Having the same problem. The phone only reboots into twrp recovery mode, yet shows no errors when re-flashing device with most recent version of sense ui.
I'd really like to be able to use my phone.
Click to expand...
Click to collapse
Flash latest stock RUU. Once phone is fixed you can go for a custom rom again
LS.xD said:
Flash latest stock RUU. Once phone is fixed you can go for a custom rom again
Click to expand...
Click to collapse
I tried that. My computer is no longer recognizing the device at all. I thought I was making progress through the first part of the day, but for some reason, usb recognition seems to fluctuate.
I'm normally pretty alright working with this type of thing, but this phone has me completely baffled.
lurkeratthegate said:
I tried that. My computer is no longer recognizing the device at all. I thought I was making progress through the first part of the day, but for some reason, usb recognition seems to fluctuate.
I'm normally pretty alright working with this type of thing, but this phone has me completely baffled.
Click to expand...
Click to collapse
Really weird. So you have no chance to get into fastboot mode, not even by selection reboot to bootloader in twrp?!
LS.xD said:
Really weird. So you have no chance to get into fastboot mode, not even by selection reboot to bootloader in twrp?!
Click to expand...
Click to collapse
I supposed I should have been more clear. Fastboot will work, but all of the adb commands fail as the "device not found". I have tried restarting everything multiple times, updated all of the drivers, deleted the drivers, re-installed them, and while it makes the chime noise when I plug the phone in, all I can do is look at it in device manager. I'm running windows 8.1 and twrp 2.8.5.0, by the way.
lurkeratthegate said:
I supposed I should have been more clear. Fastboot will work, but all of the adb commands fail as the "device not found". I have tried restarting everything multiple times, updated all of the drivers, deleted the drivers, re-installed them, and while it makes the chime noise when I plug the phone in, all I can do is look at it in device manager. I'm running windows 8.1 and twrp 2.8.5.0, by the way.
Click to expand...
Click to collapse
RUU flashing is fastboot based I suppose. So you won't need adb at all.
LS.xD said:
RUU flashing is fastboot based I suppose. So you won't need adb at all.
Click to expand...
Click to collapse
Wait, what? I can flash images like twrp to my phone via fastboot, but the only ruu's I've found either have executable wizard files, or are self extracting. How can I flash a rom or update utility using fastboot?
lurkeratthegate said:
Wait, what? I can flash images like twrp to my phone via fastboot, but the only ruu's I've found either have executable wizard files, or are self extracting. How can I flash a rom or update utility using fastboot?
Click to expand...
Click to collapse
Connect phone in fastboot mode, run RUU, click next plenty of times, and done
If your phone is S-ON, flash stock recovery first and relock the bootloader before running the RUU
Hello,
I just broke my nexus 5 screen but the device is still working. I'd like to retrieve some files from my phone before buying a new one, like pictures or SMS for example.
Here is what I can do :
- Boot in fastboot mode
- Flash a custom recovery (ex : TWRP)
Here is what is not working :
- Device is not recognized in Windows file folder, then I suppose that MTP is not enabled
- no developer mode enabled
- no USB debugging mode enabled
- Then ADB is not working
By the way, the device is not unlocked and not rooted.
I tried to flash and boot into TWRP mode but I don't know how to "drive" it from my computer as the device screen is not working.
Could somebody help me please ?
pilipe75 said:
Hello,
I just broke my nexus 5 screen but the device is still working. I'd like to retrieve some files from my phone before buying a new one, like pictures or SMS for example.
Here is what I can do :
- Boot in fastboot mode
- Flash a custom recovery (ex : TWRP)
Here is what is not working :
- Device is not recognized in Windows file folder, then I suppose that MTP is not enabled
- no developer mode enabled
- no USB debugging mode enabled
- Then ADB is not working
By the way, the device is not unlocked and not rooted.
I tried to flash and boot into TWRP mode but I don't know how to "drive" it from my computer as the device screen is not working.
Could somebody help me please ?
Click to expand...
Click to collapse
Then i suppose there is nothing you can do if almost nothing works and adb doesn`t recognise your phone, good luck mate
BTW next time enable google foto`s backup.
gee2012 said:
Then i suppose there is nothing you can do if almost nothing works and adb doesn`t recognise your phone, good luck mate
Click to expand...
Click to collapse
Using ADB would have been to easy
There is nothing I can do with a custom recovery ? or a modified boot ?
pilipe75 said:
Using ADB would have been to easy
There is nothing I can do with a custom recovery ? or a modified boot ?
Click to expand...
Click to collapse
You can`t, the bootloader is locked so you can`t flash custom stuff like a recovery. And even then you couldn`t know what buttons you`ld press if you can`t see what you`re doing.
gee2012 said:
You can`t, the bootloader is locked so you can`t flash custom stuff like a recovery.
Click to expand...
Click to collapse
I can unlock and root it, but I guess that it'll erase everything, right ?
pilipe75 said:
I can unlock and root it, but I guess that it'll erase everything, right ?
Click to expand...
Click to collapse
Unlocking the device wipes the device, so this kills the whole purpouse of your question. Might as well do nothing and get the phone repaired or buy a another one.
gee2012 said:
Unlocking the device wipes the device, so this kills the whole purpouse of your question. Might as well do nothing and get the phone repaired or buy a another one.
Click to expand...
Click to collapse
ok thanks for your help I'm still opened to news ideas if somebody is able to do miracles.
It's Christmas after all
pilipe75 said:
Here is what I can do :
- Flash a custom recovery (ex : TWRP)
By the way, the device is not unlocked and not rooted.
Click to expand...
Click to collapse
if bl is not unlocked... you won't be able to flash a custom recovery to use ADB to pull files.. so.. you're done here.
I maybe found a solution but I need a specific apk.
I may use the sideload mode to push and install a ROM or an apk. The best would be to push/install an apk from sideload mode, and this apk would automatically launch itself at device startup and will activate USB debugging mode which will allow me to fully use adb.
What do you think about that ? Would you know an apk which would do that ?
Or secondary option, push a specific ROM with USB debugging enabled by default. But I'm afraid that it could erase all my data.
Have you tried a TV out adapter?
rootSU said:
Have you tried a TV out adapter?
Click to expand...
Click to collapse
Great idea but i don't have any and, above all i'm afraid that the touch screen is not working either, so i'm not sure if it could really help
pilipe75 said:
Great idea but i don't have any and, above all i'm afraid that the touch screen is not working either, so i'm not sure if it could really help
Click to expand...
Click to collapse
Well I guess you're a bit stuck unfortunately.
Can you try ubuntu.
download a live cd version and boot into ubuntu or maybe a smaller version of linux (i know ubuntu works)
once booted into ubuntu plug in the phone.
usually linux can read the file system even when windows can't
You can't flash anything unsigned with stock recovery.
a hammerhead wrote this.
qnc said:
Can you try ubuntu.
download a live cd version and boot into ubuntu or maybe a smaller version of linux (i know ubuntu works)
once booted into ubuntu plug in the phone.
usually linux can read the file system even when windows can't
Click to expand...
Click to collapse
It's not working
pilipe75 said:
It's not working
Click to expand...
Click to collapse
We don't even know if your phone boots up... Does it ring when you call it?
rootSU said:
We don't even know if your phone boots up... Does it ring when you call it?
Click to expand...
Click to collapse
Yes it does. And it's responding in fastboot and sideload mode. So the phone is working, it's just the screen which ia dead.
The only way is to install a custom recovery. There is no other way. However as you said, unlocking the bootloader will erase everything.
pilipe75 said:
Yes it does. And it's responding in fastboot and sideload mode. So the phone is working, it's just the screen which ia dead.
Click to expand...
Click to collapse
... But your bootloader is locked and you think you have stock recovery and MTP mode doesn't work?
pilipe75 said:
Yes it does. And it's responding in fastboot and sideload mode. So the phone is working, it's just the screen which ia dead.
Click to expand...
Click to collapse
sorry that did not work.
when connected to ubuntu and you type "fastboot devices" do you get a response?
If so ubuntu can not browse file system in fastboot mode, you need to reboot back to the OS.
type fastboot reboot and when the phone reboots try to browse the file system.
I was working on rooting my device, and had a working root successfully with Magisk. But then I wanted to remove it and relock my bootloader, that's when the trouble started.
I am able to boot the phone and it is working. I can boot to recovery (stock OEM not TWRP), can boot to bootloader, and can boot and use the Oxygen OS. But I cannot get fastboot to run to lock the bootloader. ADB devices comes up empty. These are the steps that I've tried:
-using it on my chromebook that was working with ADB before the unrooting mess
-installed fastboot and adb along with Oneplus USB drivers on a fresh Windows 8 copy
-2 different red OEM oneplus cables
My goal is to return completely to stock and a locked bootloader. Any help would be appreciated, it really seems to be a phone issue and not a driver issue. Thanks everyone!
Use the unbrick tool. That autolocks bootloader when it flashes stock.
NateDev said:
Use the unbrick tool. That autolocks bootloader when it flashes stock.
Click to expand...
Click to collapse
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
bam099 said:
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
Click to expand...
Click to collapse
Are you sure you have USB debugging checked in developer options?
Absolutely. Just checked again. I would normally say it was a driver issue, but it was working fine until I flashed a boot.img and also I used a windows pc and a Chromebook and chrome os pretty much comes ready to talk to android phones or of the box. I was wondering if adb could have been messed up during the flashing of boot images.
bam099 said:
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
Click to expand...
Click to collapse
No fastboot needed, it's done with the phone off.
NateDev said:
No fastboot needed, it's done with the phone off.
Click to expand...
Click to collapse
Even better! I will definitely try the tool and report back.
NateDev said:
No fastboot needed, it's done with the phone off.
Click to expand...
Click to collapse
This was correct and it worked. Phone is restored back to stock with a locked bootloader and everything is working as it should.