Database Info

[Q] Download Mode/Odin not working on Nexus S 4g

I can't get Odin to work on my 3 day old NS4G. If I put the phone in download mode (a pain in itself because half the time it boots android), Windows 7 and odin won't recognize it.
However, adb still works if the phone is fully booted or in fastboot, and the fastboot commands work. I guess I can get by with fastboot but I was wondering if anyone has run across this problem.
I'm using the pdanet drivers.
Thx...

no real reason to use odin, take my word on it fastboot is easier overall once you learn the commands and much safer

nexus s boot problem
i updated my samsung nexus s to 2.3.6 officially from phone update. but now it wont start without plugging in charger or usb cable connected to pc. if i start the phone without the charger or usb cable plugged a screen pops up saying 'downloading.. do no turn of target' what should i do to remove this bug. would really appreciate any help

Tried to update to GB Fail

I decided to try to update to GB because my G2X rebooted while on the charger, clock night mode turns off and the screen locks, and wifi is ok but resets sometimes. My phone is stock 2.2 with stock recovery but rooted.
I turned off all programs on my Windows 7 32 bit laptop, turned off anti virus and turned off Windows firewall. The updater ran ok, checked the phone environment and downloaded the update. Then at 4% when the phone is supposed to download into software update mode, it just sat there staying in Android. After the update failed and it told me to remove the cable and remove battery, etc., I just shutdown the phone, did a battery pull and turned the phone back on. I then canceled the update.
My phone booted back into Android no problem. I tried to boot into recovery using Quickboot but that just rebooted the phone back into Android. My questions are as follows:
1. Did the update change anything on the phone or did it fail before attempting to change anything?
2. Why did it fail to boot into software update mode? Do I need to try another USB port or another computer?
3. Should I use the alternate method on a Windows XP machine that people use when their phone is soft bricked?
4. Should I just install CWM recovery and use the pre-rooted zip of GB with the old baseband?
5. Or should I just forego the update for now and see if another update is released?

Try reinstalling everything, and restarting your computer. It worked just fine on Windows 7 Ultimate x86, and x64.

My update went the same way but everytime I retried it got a little further so I just retried it over and over till I hit 100 percent
Sent from my LG-P999 using XDA App

I just tried to run the LG update program on my XP machine but I got a runtime error (see attached). Anybody know what this means and how to fix it?

Does anyone know why it just sits there on 4% and never boots into the software update mode? Can I just run it and then when it fails manually boot into software update mode? Or is that risking a brick?

jboxer said:
I decided to try to update to GB because my G2X rebooted while on the charger, clock night mode turns off and the screen locks, and wifi is ok but resets sometimes. My phone is stock 2.2 with stock recovery but rooted.
I turned off all programs on my Windows 7 32 bit laptop, turned off anti virus and turned off Windows firewall. The updater ran ok, checked the phone environment and downloaded the update. Then at 4% when the phone is supposed to download into software update mode, it just sat there staying in Android. After the update failed and it told me to remove the cable and remove battery, etc., I just shutdown the phone, did a battery pull and turned the phone back on. I then canceled the update.
My phone booted back into Android no problem. I tried to boot into recovery using Quickboot but that just rebooted the phone back into Android. My questions are as follows:
1. Did the update change anything on the phone or did it fail before attempting to change anything?
2. Why did it fail to boot into software update mode? Do I need to try another USB port or another computer?
3. Should I use the alternate method on a Windows XP machine that people use when their phone is soft bricked?
4. Should I just install CWM recovery and use the pre-rooted zip of GB with the old baseband?
5. Or should I just forego the update for now and see if another update is released?
Click to expand...
Click to collapse
Follow your Item 4

Finally got it updated
Used Windows 7 32bit.
The update progressed very scarily.
I downloaded the drivers and reinstalled them directly from the update program. I then used a different USB port then my previous attempt, unplugged all other USB devices, and shutdown everything running on the computer I could including Avast andti-virus and the Windows Firewall. This time when I plugged the G2X into my computer a lot more devices installed than last time (first time only 2 devices were installed, this time about 8 to 10).
During the first download of the firmware I canceled it because I realized I left the micro sd card in the phone and the instructions on the website say to remove the card. Then I also decided to unroot the phone and remove all programs that require root access. Since the phone would be unrooted after an update I decided I didn't want superuser in the system if I couldn't use it, and after the update I would be unable to remove it since the phone would not be rooted.
Then I ran the program again and this time the phone booted into software update mode. It started pushing the update to the phone and at 5% the phone disconnects from the computer and reconnects (does this three times during the update) but the software doesn't see the phone and tells me to unplug the USB cable, remove the battery, reinsert the battery and turn the phone back on. But I heard the computer reconnect to the phone so I decided I would just remove the cable and reinsert it. This worked and the update started over again. This time it went past 5% and then reset the phone connection again at 46%. It then slowly completed the update resetting one more time at 76% and when it reconnected it went back to 75% but then progressed to 100% and rebooted the phone.
It now has an updated baseband and Gingerbread 2.3.3. I am leaving it unrooted for now and just use it stock.

jboxer said:
Does anyone know why it just sits there on 4% and never boots into the software update mode? Can I just run it and then when it fails manually boot into software update mode? Or is that risking a brick?
Click to expand...
Click to collapse
I do! It's installing one of the THREE usb drivers that it installs over the course of the upgrade. Mine got stuck at 4% for just a second (at which point I about **** my pants), but then I saw a Win7 notification pop up that it had just installed a USB driver, and then it proceeded to do the update.
So maybe the failure mode is the LG updater not being able to install a USB driver?

Maris_ said:
Follow your Item 4
Click to expand...
Click to collapse
Is there any significant reason to update to get the newest baseband and then flash CM7? Or is there no benefit from the new baseband?

brdma said:
Is there any significant reason to update to get the newest baseband and then flash CM7? Or is there no benefit from the new baseband?
Click to expand...
Click to collapse
July 15, 2011 baseband has more reliable wifi and much better GPS lock. After the scares of getting mine updated finally, my G2X has had no issues in the 30+ hours since the update. No reboots on charger, no sleep of death and everything is working as it should.

Stuck at activation, can't enter recovery, fastboot not working

Right now my Nexus appears to be pretty much soft bricked and I do not know how to get back to normal. A little background on what happened that led up to this. Was running slimbean 4.3 don't know what slim version but about a month or 2 old(had it when 4.3 was still new) Installed the google hom launcher(launcher, search framework) All went well, Decided to factory reset because phone was running slow(was before installing kit kat launcher) Did so through recovery(latest CWM) when I rebooted I was stuck on the activation screen. Iut can scroll through the various languages, but can not click on any of them to procede. Can open the notification bar and the control panel. Can turn off and on wifi, bluetooth etc. Setting does me no good. When I enter fastboot, I can only reboot booloader, I can not select any of the other options using volume down. I can not use fastboot as it detects nothing(no error, no device on/offline) Device manager gives me generic drivers which aren't installed such as ethernet and pci. No Nexus S driver. Tried installing drivers nothing. I should also note that when I am on the activation screen I can enter usb mode to copy and paste files. ADB and fastboot are working with galaxy nexus. I really want to sell this phone to my cousin but obviously I can not. I really don't think any hardware is currupt but I don't know for sure.

md1008 said:
Right now my Nexus appears to be pretty much soft bricked and I do not know how to get back to normal. A little background on what happened that led up to this. Was running slimbean 4.3 don't know what slim version but about a month or 2 old(had it when 4.3 was still new) Installed the google hom launcher(launcher, search framework) All went well, Decided to factory reset because phone was running slow(was before installing kit kat launcher) Did so through recovery(latest CWM) when I rebooted I was stuck on the activation screen. Iut can scroll through the various languages, but can not click on any of them to procede. Can open the notification bar and the control panel. Can turn off and on wifi, bluetooth etc. Setting does me no good. When I enter fastboot, I can only reboot booloader, I can not select any of the other options using volume down. I can not use fastboot as it detects nothing(no error, no device on/offline) Device manager gives me generic drivers which aren't installed such as ethernet and pci. No Nexus S driver. Tried installing drivers nothing. I should also note that when I am on the activation screen I can enter usb mode to copy and paste files. ADB and fastboot are working with galaxy nexus. I really want to sell this phone to my cousin but obviously I can not. I really don't think any hardware is currupt but I don't know for sure.
Click to expand...
Click to collapse
Don't know how I did it, but somehow I was able to go through recovery via bootloader, still curious as to why I wasn't able to before and why installing drivers to enter fastboot mode failed, I am just glad all is running

Nexus 5 gets stuck trying to write files with fastboot

Hey guys, I've been trying to update to 4.4.3 and managed to sort of get it working with the OTA but it was kind of a dirty mess so I wanted to try and do a clean flash with fastboot. So I downloaded the image from Google and tried to run the flash-all.bat and it errors out after flashing the radio and trying to send a reboot command to fastboot-far as I can tell this is because the bootloader is stuck on "writing..." The same thing happened before when I tried to write the system.img alone while restoring my phone to stock to load the OTA-it would get stuck on "writing..." in the bootloader and even waiting 5 hours didn't get it past "writing..." Does anybody know how to fix this? I'm trying to manually send things over one by one with fastboot instead of using the script but since it gets stuck with every file I'm not sure if it's even fully flashing everything over...very frustrating that it's getting stuck and this is with the latest bootloader on it too (hhz11k).

I had a similar problem does fastboot on your computer crash and say out of memory
Sent from my Nexus 5 using Tapatalk

No oddly on the computer everything looks ok, it sends the file over and it says the write is successful. But fastboot on the phone then locks up basically and gets stuck on the "writing..." portion so then the next command will fail when the computer tries to send any commands. Very weird and reflashing the bootloader didn't fix anything either.

Try restarting the computer and unplugging nexus 5
Sent from my Nexus 5 using Tapatalk

[Q] Nexus 5 Mysterious Stuck on boot animation

Hi Everyone!
Really new to xda so I'm not sure if this is the right place to post this at (sorry). I have a nexus 5 that after I (purposely) rebooted, is now just stuck on the boot animation, (it was not updating to 5.1.0 or 5.0.1). I tried leaving it on but it just kept spinning until the phone died. I can access fastboot, and recovery, have tried wiping cache, and factory resetting multiple times. Nothing has happened. I have gotten adb and fastboot on my mac, and downloaded a factory image from google to try and reflash, but ./adb devices doesn't show anything, even though the phone is connected in fastboot mode. (On the google website it says drivers shouldn't be an issue?). My nexus 5 is running stock, was unlocked before but now still unrooted, its the US version and I have tried connecting to the computer with multiple micro-usb cables (including the one included in the box). What should I do? Or how do I get my nexus 5 to show in ./adb devices?
I'm stumped, any help would be greatly appreciated , thanks!

hanssw said:
Hi Everyone!
Really new to xda so I'm not sure if this is the right place to post this at (sorry). I have a nexus 5 that after I (purposely) rebooted, is now just stuck on the boot animation, (it was not updating to 5.1.0 or 5.0.1). I tried leaving it on but it just kept spinning until the phone died. I can access fastboot, and recovery, have tried wiping cache, and factory resetting multiple times. Nothing has happened. I have gotten adb and fastboot on my mac, and downloaded a factory image from google to try and reflash, but ./adb devices doesn't show anything, even though the phone is connected in fastboot mode. (On the google website it says drivers shouldn't be an issue?). My nexus 5 is running stock, was unlocked before but now still unrooted, its the US version and I have tried connecting to the computer with multiple micro-usb cables (including the one included in the box). What should I do? Or how do I get my nexus 5 to show in ./adb devices?
I'm stumped, any help would be greatly appreciated , thanks!
Click to expand...
Click to collapse
As long as you're able to charge the phone still while it's off you'll have some options.
When you do factory reset, does it complete the process and reboot on its own??
Just saw this thread. You might want to try it out.
http://forum.xda-developers.com/showthread.php?t=2957801
Sent from my 1+1

Mojar7070 said:
As long as you're able to charge the phone still while it's off you'll have some options.
When you do factory reset, does it complete the process and reboot on its own??
Just saw this thread. You might want to try it out.
http://forum.xda-developers.com/showthread.php?t=2957801
Sent from my 1+1
Click to expand...
Click to collapse
Yes it does does complete it, I reset it from recovery, so it completes and when it restarts its still stuck on the loop again for another hour. I'm downloading the file, hopefully it works
EDIT: Already completed the flash using the tool, but the first boot didn't work, reformatting again after the flash.
EDIT 2: Reboot doesn't work after the reformat after the flash.

hanssw said:
Yes it does does complete it, I reset it from recovery, so it completes and when it restarts its still stuck on the loop again for another hour. I'm downloading the file, hopefully it works
EDIT: Already completed the flash using the tool, but the first boot didn't work, reformatting again after the flash.
EDIT 2: Reboot doesn't work after the reformat after the flash.
Click to expand...
Click to collapse
Have you tried flashing through fastboot?? I'll be honest I'm not to knowledgeable on fastboot, maybe someone else would like to chime in for that.
I've used wug fresh nexus tools but you'll need the phone to boot up properly to get into developer settings to turn on USB debugging.
Sorry if I can't help any further.
Sent from my 1+1

Nexus 5 boot stuck
Bro just try to write the following Command in cmd in the platform devices folder
'fastboot devices' instead adb devices. copy the stock image to the Platform-tools folder and just flash it via fastboot commands. mine was stuck in boot animation and did the same