a buddy of mine bought a nexus s off of craigslist that is constantly force closing when you boot it. it will force close everything then reboot itself. im attempting to unlock the bootloader but adb devices doesnt show the serial number like it does for my nexus s. when i hold down volume up+down and plug in the usb it goes to the unlock bootloader screen but it doesnt give you the option of yes or no. iv posted a picture to show what it looks like. i cant get the phone into download to try to fix it with odin either. any help would be appreciated.
edit: i finally got my pc to recognize it and we now have an unlocked bootloader, but now iv encountered another problem. i downloaded a recovery image and moved it to the tools folder of sdk when i type in the fastboot flash recovery command it responds with error: cannot load recovery.img.
To unlock bootloader, you have to use fastboot, not adb. So the correct command would be fastboot devices
To boot into the bootloader, you have to press volume up + power, not volume up+down and plug in the usb -- that would bring you into the Download Mode instead
suksit said:
To unlock bootloader, you have to use fastboot, not adb. So the correct command would be fastboot devices
To boot into the bootloader, you have to press volume up + power, not volume up+down and plug in the usb -- that would bring you into the Download Mode instead
Click to expand...
Click to collapse
i know, i used adb devices to see if my computer would even recognize the phone. i i can get into fastboot mode by pressing volume up and power but cant send a fastboot command to the phone because it doesnt recognize the phone. when i hold down volume up and down to get into download mode it sends me to the screen i showed in the pic. its the unlock bootloader screen except there is no option to click yes to unlock the bootloader. i would love to get into download mode and use odin hence why i pressed vol up and down and plugged in usb, but like i said it sends me to the unlock bootloader screen.
fosdos4790 said:
a buddy of mine bought a nexus s off of craigslist that is constantly force closing when you boot it. it will force close everything then reboot itself. im attempting to unlock the bootloader but adb devices doesnt show the serial number like it does for my nexus s. when i hold down volume up+down and plug in the usb it goes to the unlock bootloader screen but it doesnt give you the option of yes or no. iv posted a picture to show what it looks like. i cant get the phone into download to try to fix it with odin either. any help would be appreciated.
edit: i finally got my pc to recognize it and we now have an unlocked bootloader, but now iv encountered another problem. i downloaded a recovery image and moved it to the tools folder of sdk when i type in the fastboot flash recovery command it responds with error: cannot load recovery.img.
Click to expand...
Click to collapse
Before you try to unlock the bootloader I would flash the latest stock rom and see if it boots properly.
Sent from my PC36100 using XDA Premium App
fosdos4790 said:
edit: i finally got my pc to recognize it and we now have an unlocked bootloader, but now iv encountered another problem. i downloaded a recovery image and moved it to the tools folder of sdk when i type in the fastboot flash recovery command it responds with error: cannot load recovery.img.
Click to expand...
Click to collapse
Try one of these recovery images:
http://forum.xda-developers.com/showthread.php?t=988686
The full command is
fastboot flash recovery recovery.img
(make sure your recovery image file is actually named recovery.img)
If 'fastboot devices' returns your phone's id you can flash a custom recovery. Otherwise get a full _signed_ stock rom and flash from stock recovery.
Did you install all drivers? Deinstall existing and use either pdanet or sdk build in program to get them. You need like 3 different ones.
Try locking unlocking bootloader again.
There's always the chance you got a defective usb connector.
Sent from my Nexus S using XDA App
Related
I updated my i9023 to ICS using the stock recovery. Now I dont have a recovery since the ics update bugged it and my bootloader is locked. How am I supposed to unlock/install cmw/root?
Thx in advance.
andrei.voinea93 said:
I updated my i9023 to ICS using the stock recovery. Now I dont have a recovery since the ics update bugged it and my bootloader is locked. How am I supposed to unlock/install cmw/root?
Thx in advance.
Click to expand...
Click to collapse
Try here: http://forum.xda-developers.com/showthread.php?t=1396913
I cannot boot in stock recovery to install the zip as described in that post
Sent from my Nexus S using XDA App
andrei.voinea93 said:
I cannot boot in stock recovery to install the zip as described in that post
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Try fastboot & try to flash clockwork.img recovery!
unlock bootloader doesnot work
We all know the standard commands to unlock the bootloader but for some reason on my Nexus S device, the bootloader unlock is not working. Here is what I did,
1. Connect the device and type 'fastboot oem unlock'
2. It brings up a menu to select "No" or "YES" to unlock options...I navigated through volume up key to select "YES" to unlock boot loader.
3. Now I have to restart the device by pressing power button, the POWER BUTTON doesn't respond there by bootloader unlock doesn't complete.
4. It just hangs in bootloader unlock screen forever.
Does anyone faced this issue? why this happens??
please help me out.
Thanks and regards,
-Lakshman
Fastboot oem unlock wont see my nexus. It says its waiting for a device even if i installed the needed deivers
Sent from my Nexus S using XDA App
andrei.voinea93 said:
Fastboot oem unlock wont see my nexus. It says its waiting for a device even if i installed the needed deivers
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You need to be in the boot loader for that to work.
I am
Sent from my Nexus S using XDA App
I've the same Problem. I'm in the bootloader and it says Fastboot Mode but the device is not recognized via USB.
Therefore fastboot is just waiting for devices.
Any suggestions? When my nexus is booted i can connect it als USB-Storage and so on.
I fixed it using the sdk drivers and the fastboot and adb files from the sdk (path/android/platform-tools).
Didn't work for me. I'm always using SDK.
My Bootloader is unlocked. (the little lock ist opened )
I just tried it on a completly different computer. just setted up a new SDK on my laptop.
Am I doing something wrong?
I've USB-Debug Mode enabled.
I boot holding VOL up + Power Button to enter the bootloader
Plug in the USB cable
and then i try ~android-sdk/platform-tools/fastboot flash recovery myrecovery.img
Here my Fastboot says wating for device.
If i'm booted up on my rom i can connect via adb and get a my device via adb devices.
Probably something wrong with my fastboot.exe?
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
Firstly, the power button has gone faulty on my Nexus S and I am due to send it back to Samsung for repairs, so I want to get it back to factory image 4.0.4 IMM76D using the Google image and to relock the bootloader. However, when I reboot into fastboot all the keys stop working and I presume it has stopped responding and the only way to reboot is to do a battery pull. Just wondering if anyone has had this experience before and knows a solution.
By keys you mean volume and power right?
Does a computer recognize it with fastboot. Example . Fastboot devices / fastboot reboot etc?
albundy2010 said:
By keys you mean volume and power right?
Does a computer recognize it with fastboot. Example . Fastboot devices / fastboot reboot etc?
Click to expand...
Click to collapse
Volume and power keys don't work while in fastboot and it isn't recognised by that. And when it powers on regularly it say No boot or recovery img. Nope, doesn't get recognised by PC and just says No devices found...
Did it work before in the same system?
Only other thing I could think of to try is download mode/Odin
It was working fine that day. I even flashed CWM on it after trying TWRP. But then suddenly the power button broke, and when I used the key combo to get into fastboot mode using the plug in to charger method it loaded fastboot and just wouldn't respond
My phone is bootlooping and the power button has been broken for a while. I've tried various things posted in other threads, just wondering if anyone has any solutions or ideas.
I can't seem to get it to connect with usb in the bootloader but it does connect while bootlooping. Can I fix it while connected in the bootloop?
edit: Actually, now that I've researched more, I'm pretty sure the problem is that my bootloader is frozen. That's why neither my functioning volume keys or adb works in the bootloader.
ekovv said:
My phone is bootlooping and the power button has been broken for a while. I've tried various things posted in other threads, just wondering if anyone has any solutions or ideas.
I can't seem to get it to connect with usb in the bootloader but it does connect while bootlooping. Can I fix it while connected in the bootloop?
Click to expand...
Click to collapse
Try Nexus root toolkit to boot custom recovery temporarily (or another option like that), while looping, ?may? work??
Setting.Out said:
Try Nexus root toolkit to boot custom recovery temporarily (or another option like that), while looping, ?may? work??
Click to expand...
Click to collapse
I can't seem to get anything in the Nexus Root Toolkit to work while it's bootlooping or while it's in the bootloader even though it comes up in my device manager as Google Nexus S ADB Interface while in the bootloop.
Is there a way to fix it in the command line, or is that just the same thing as using the root toolkit?
ekovv said:
I can't seem to get anything in the Nexus Root Toolkit to work while it's bootlooping or while it's in the bootloader even though it comes up in my device manager as Google Nexus S ADB Interface while in the bootloop.
Is there a way to fix it in the command line, or is that just the same thing as using the root toolkit?
Click to expand...
Click to collapse
Can you get into recovery?
No I can't get into recovery because my volume buttons won't let me navigate the bootloader options. They aren't broken, they just don't work in the bootloader for some reason. My power button is physically broken though so I don't know how to get to recovery or if I can even use recovery without the power button...
I think fastboot will work without a power button?
This command...
adb reboot bootloader
Click to expand...
Click to collapse
ekovv said:
My phone is bootlooping and the power button has been broken for a while. I've tried various things posted in other threads, just wondering if anyone has any solutions or ideas.
I can't seem to get it to connect with usb in the bootloader but it does connect while bootlooping. Can I fix it while connected in the bootloop?
Click to expand...
Click to collapse
1) Download latest CWM Touch.
2) Follow steps from here to install CWM.
3) Boot in recovery using the command in the above link.
4) Download a flashable touch recovery from here.
5) Mount USB in the recovery and copy this zip and flash it. This will make your custom recovery permanent. Reboot to recovery again just to verify.
Now, you have a touch recovery accessible through fastboot and can install custom ROMs
smit.sanghavi said:
1) Download latest CWM Touch.
2) Follow steps from here to install CWM.
3) Boot in recovery using the command in the above link.
4) Download a flashable touch recovery from here.
5) Mount USB in the recovery and copy this zip and flash it. This will make your custom recovery permanent. Reboot to recovery again just to verify.
Now, you have a touch recovery accessible through fastboot and can install custom ROMs
Click to expand...
Click to collapse
Thanks for the step by step! The problem is I still can't get the adb working in the bootloader to install CWM Touch. When I type adb reboot bootloader it says "no device connected." If I type the same command while the phone is bootlooping it says "device unauthorized."
edit: Actually, now that I've researched more, I'm pretty sure the problem is that my bootloader is frozen. That's why neither my functioning volume keys or adb works in the bootloader.
ekovv said:
Thanks for the step by step! The problem is I still can't get the adb working in the bootloader to install CWM Touch. When I type adb reboot bootloader it says "no device connected." If I type the same command while the phone is bootlooping it says "device unauthorized."
edit: Actually, now that I've researched more, I'm pretty sure the problem is that my bootloader is frozen. That's why neither my functioning volume keys or adb works in the bootloader.
Click to expand...
Click to collapse
You can't use adb in fastboot. There are fastboot commands for that.
Step 2 has fastboot commands to install custom recovery.
Very similar problem on Nexus 4
https://forum.xda-developers.com/nexus-4/general/nexus-4-bootloop-adb-unauthorized-t3540874
ekovv said:
My phone is bootlooping and the power button has been broken for a while. I've tried various things posted in other threads, just wondering if anyone has any solutions or ideas.
I can't seem to get it to connect with usb in the bootloader but it does connect while bootlooping. Can I fix it while connected in the bootloop?
edit: Actually, now that I've researched more, I'm pretty sure the problem is that my bootloader is frozen. That's why neither my functioning volume keys or adb works in the bootloader.
Click to expand...
Click to collapse
You can wait till the battery drain and then connect your phone to PC holding the volume button to enter bootloader and then using Nexus Root Toolkit flash your stock rom.
Kiranarul2000 said:
You can wait till the battery drain and then connect your phone to PC holding the volume button to enter bootloader and then using Nexus Root Toolkit flash your stock rom.
Click to expand...
Click to collapse
it doesnt work because if the phone gets charged up it goes into the loop again
Hi all. So my stock opo somehow got bricked overnight while charging. It's completely stock and I have no idea why.
Status of my problem:
-Stuck on Android boot screen.
-Able to access fastboot.
-Can't access recovery mode
-No TRWP
-it's still locked
-Tried unlocking with fastboot oem unlock cmd / toolbox but it just reboots back to android stuck screen after its done but its still locked after checking with fastboot oem device-info cmd.
*USB debugging not enabled (cant enable it cuz i cant go in my phone duh)
-Cm11 33r I think...
-Installed android adb on device manager
But couldn't detect it on the list ("adb devices" cmd)
-Able to detect serial using fastboot device cmd tho.
-Tried universal adp, adb bootloader driver, Samsung adb driver, composite driver and it still won't detect it on list.
-Tried using another usb port.
-computer doesn't detect phone unless I go on fastboot or hold power+up volume for 10 sec (this shows QHUSB_BULK)
-Tried using msm9874downloadtool.exe with cm 11, doesn't do anything even tho it's completed and it's green.
-Tried using msm9874downloadtool.exe with color os but it doesnt work as well, in fact, it made my screen have multiple grey lines vertically across my screen and no fastboot display or android display.
-Tried just flashing Cm11 33r images but it won't work cuz I'm locked.
-Tried unlocking but goes back to my other problem of device not being on the list and not having usb debugging enabled.
Tldr;
Phone stuck on Android boot screen
USB debugging not enabled
Phone is not unlocked so I can't flash anything
Thanks for your time and effort. I really need help.
I still need help guys plzzz. Thankss
Have you tried getting into download mode? I think you power it off. Connect to USB and hold vol down? Or vol down + power. Something like that. Once in DL mode, flash it. There's a tutorial somewhere.
Sent from my A0001 using Tapatalk
ackliph said:
Have you tried getting into download mode? I think you power it off. Connect to USB and hold vol down? Or vol down + power. Something like that. Once in DL mode, flash it. There's a tutorial somewhere.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
download mode? you mean fast boot? power + down doesnt load anything. Power + up goes into fastboot mode.
And i cant flash anything because you have to unlock the phone first. But mine is not unlocked. And i cant unlock it with fastboot oem unlock cmd because all it does it reboots my phone. Yes i checked if im unlocked after that with fastboot oem device-info.
First try to go to recovery by pressing volume down+ power button at the same time and then clear data and factory reset. This will wipe out ur data on phone but u can revive ur device by flashing stock rom using flashing tolls available... Check youtube videos for flashing tools.
Once you clear the data and factory reset from recovery mlde then ur device will be at the state where there is no OS in it n just a stock kernel. Give it a try and let me know
I can't get into recovery. Power + down only stays at android boot screen.
Have the exact same issue. Did you find a fix???
Even if your bootloader is not unlocked you can flash stock rom. Use oneplus one flashtool and flash cm11s. There are plenty of videos available on net for these problem, just go through them or try the hard bricked video to solve your problem. I hope it helps you. I lost my one device because of a silly mistake so i know the pain.
I've tried flashing stock rom. Cm11 33r. But it keeps telling me I'm locked.
put it on fastboot mode, download the stock rom from this:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Choose carefully between 16gb or 64
unzip the file and click on the flashall.bat or something like that , it's a script and it will flash everything
and you should be good
you will loose all your data, i don't know if you dont flash userdata and you remove it from the file and remove it's line from the script, maybe you wont loose your data, but try it
if you want i can help you through teamviewer