Hi,
today I woke up and my Nexus S was off. I turned it on and it just stucks while showing the google logo..
I tried pulling the battery, turning on.. still stucks!
so I tried do boot in Fastboot, ok.
Installed the SDK, the USB Drivers. The Nexus was recognized as "Android ADB Interface", ok.
Tried to list the device by "adb device", but I only said: list of devices attached. No device!
Then I tried "fastboot device". There it is! Trying "adb device" again, no device. mh.
So I tried to unlock the phone by typing "fastboot oem unlock".
I get the message on my phone, check "YES" and execute by pressing POWER, but no success. The phones stucks again. The cmd just says "...".
I spend 30min by watching on the cmd and the Nexus S, but no result.
What can I do?
Nexus S, locked Bootloader, 2.3.3, 2 days old
*push..*..
Can you get into the bootloader on the device? (Power and Volume Up)
Has it been rooted, and do you have CWM installed?
I can enter the the bootloader. Firmware is stock, unrooted!
I think the main problem is, that usb debug is not enabled in the device. Thats the reason why adb doesnt recognize it. But fastboot does ...
You can only use adb when the phone is booted up. Fastboot is for when the phone is in the bootloader.
Try going into recovery and doing a factory reset?
I don't know which phone you have, I'm on NS4G, got phone unlocked using GSM codes, so erased everything - a mess. When I got to backup using 2 finger method, there was nothing to reboot to
I went to Samsung site - found program called Samsung Simple DL for my phone, downloaded, executed and ran - back to stock. Kept it unlocked, but was back up and running.
I was paniced, so this might help
Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=
If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!
Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!
Yeah, what Mjamocha said...
okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.
okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?
I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?
I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium
Hi,
This is my first post on this forum and I might sound like a total dummy (cos I am when it comes to rooting/flashing android devices).
My Nexus 4 was suffering from poor battery performance and to correct that I thought of trying my hands at rooting it and flashing it with a custom ROM. However, being a noob, little did I realize what I was getting myself in to.
Now, after unlocking the boot loader, when I tried to boot my device from recovery mode, it just wouldn't fire up, but kept showing the rotating dots of lollipop boot screen.
After a lot of fiddling, I managed to mess up even further as now, the rotating dots are also not appearing and I just get Google logo twice and after that the device's screen just keeps blinking with a faded background light on the screen.
I used Nexus4Root to root the device and have ADB installed on my Mac OS X machine.
Is there anything I can do to bring my Nexus 4 back to life?
Any help is appreciated.
Thanks.
ajxkid said:
Seems like unlocking your Boot loader have not been successful , Toolkits are not always dependable. I think you should unlock ur Boot loader manually with adb and fastboot .
You could find guides for that all over the web. Go on and try that..
Good luck
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the response. I think I did manage to unlock the Boot loader, as I can see that in the status when I switch ON the phone in 'recovery mode'. The problem is that I am not able to boot the phone through recovery mode. As I said, it goes in a sort of boot loop. It does not boot from normal mode, same thing happens (boot loop).
Is it possible to flash the factory image in the current state of device? The device is not detected by my Mac when I try to fastboot it.
Any guides/threads I can look at with similar information? Have been looking up quite a lot online, but to no avail.
Thanks again!
Hey guys
So last night my nexus 5 restarted and got stuck on the google logo screen, and won't load past it.
When I go into the bootloader and attempt to enter recovery mode all that happens is a blank screen, with a faint backlight on.
I've tried to use nexus root toolkit and chain fire auto root, but neither of them seem to work.
With the nexus root toolkit, I tried several times using the flash stock/unroot option. It would work fine until the phone prompt titled 'unlock bootloader?' which when I chose yes would then attempt to reboot the device into bootloader mode, but all that happens is my phone will show the charging symbol. There were a few times where the bootloader would flash quickly on screen and show that it was unlocked, but then afterwards the charging symbol would show.
With Chain Fire auto root, after the phone prompt saying 'unlock bootloader' and me selecting yes, it will load the bootloader again and show that it is unlocked, after which the program gets an unknown error.
I'm a complete novice in this area so if anyone has ideas, detailed instructions would be greatly appreciated
I have a feeling its a hardware issue, but am posting just in case.
Thanks heaps for any input!
Dear friends,
I have LG Google Nexus 5 (Hammerhead D821(H) 32GB) model. Some days ago I tried to install Ubuntu Touch OS through UBports Software in my nexus 5 phone. But I forgot to enable USB Debugging first. So when I started the flash process and try to unlock bootloader, one time it show lock state unlocked. But In reality it was not unlocked. Because of this reason Ubuntu Touch OS installation is not completed and it corrupted my phone. Now I am unable to boot in android also. I also tried to re-flash my phone with Google Factory image but it was not completed because of my bootloader is locked. I don't know how i can unlock bootloader now. I used Wipe Data & Factory Reset option in Recovery Mode but it is also vain. Please help me how can I correct my phone.
Assuming you have adb/fastboot drivers correctly installed, you have to reboot to bootloader by pressing volume down + power and keeping them pressed until you see the bootloader screen. Then connect your phone to the PC and issue the following command from a command prompt:
fastboot oem unlock
Keep in mind that unlocking the bootloader will erase all your data, just like a factory reset, so backup everything first!
shivmahar said:
Dear friends,
I have LG Google Nexus 5 (Hammerhead D821(H) 32GB) model. Some days ago I tried to install Ubuntu Touch OS through UBports Software in my nexus 5 phone. But I forgot to enable USB Debugging first. So when I started the flash process and try to unlock bootloader, one time it show lock state unlocked. But In reality it was not unlocked. Because of this reason Ubuntu Touch OS installation is not completed and it corrupted my phone. Now I am unable to boot in android also. I also tried to re-flash my phone with Google Factory image but it was not completed because of my bootloader is locked. I don't know how i can unlock bootloader now. I used Wipe Data & Factory Reset option in Recovery Mode but it is also vain. Please help me how can I correct my phone.
Click to expand...
Click to collapse
perhaps it can help
https://forum.xda-developers.com/go...l-06-03-14-one-click-factory-restore-t2513937
shivmahar said:
Dear friends,
I have LG Google Nexus 5 (Hammerhead D821(H) 32GB) model. Some days ago I tried to install Ubuntu Touch OS through UBports Software in my nexus 5 phone. But I forgot to enable USB Debugging first. So when I started the flash process and try to unlock bootloader, one time it show lock state unlocked. But In reality it was not unlocked. Because of this reason Ubuntu Touch OS installation is not completed and it corrupted my phone. Now I am unable to boot in android also. I also tried to re-flash my phone with Google Factory image but it was not completed because of my bootloader is locked. I don't know how i can unlock bootloader now. I used Wipe Data & Factory Reset option in Recovery Mode but it is also vain. Please help me how can I correct my phone.
Click to expand...
Click to collapse
You can try with this toolkit http://www.wugfresh.com/nrt/
Surf the net in search of tutorial and info,there are also some videos on YouTube.
I already tried it but vain.
ilciumbia said:
Assuming you have adb/fastboot drivers correctly installed, you have to reboot to bootloader by pressing volume down + power and keeping them pressed until you see the bootloader screen. Then connect your phone to the PC and issue the following command from a command prompt:
fastboot oem unlock
Keep in mind that unlocking the bootloader will erase all your data, just like a factory reset, so backup everything first!
Click to expand...
Click to collapse
Dear Sir,
I tried to unlock bootloader with fastboot oem unlock command many times. When I used this command one time it shows unlocked but when I restarted bootloader it again shows locked.
Eh, this is not good. In my experience, this happens when the eMMC has gone bad, either faulty or write protected for some reason. I have investigated the issue and I have not found a solution yet... Even desoldering it and soldering it to a uSD custom PCB does not allow me to write to it... I am afraid you are stuck with a secretly bricked phone...
I don't know if you already tried all possible,just take a look at this thread.
https://forum.xda-developers.com/go...nexus-5-doesnt-boot-access-adb-t2521691/page3
Or even look at this,LG Flashtool.You don't need unlocked bootloader to flash.
https://forum.xda-developers.com/go...orial-how-to-flash-factory-images-lg-t2713833
The thread is quite old,but needed links are working correctly,i've just checked.