my motorola zoom has locked it's self in fast boot mode see bellow what it looks like on the screen --> Fastboot Starting Fastboot protocol support.It has been in this point for about 3 hours this morning how do i get it out of this or get it to boot up?
I have a Nexus 5 (Hammerhead) 32gb device, stock with no rooting. I mean, I had never done anything special on it ever.
1. Recently I started getting Google Play Store related problems, first 194 error and then couple of days back 495 (I think). After trying switching on/off, clearing cache and some other similar ways to fix this, I decided to do a factory reset
2. I backed up all my data, and followed the documented steps for factory reset. The phone got stuck on 'erasing'. After waiting for over 24 hours, I finally figured out that this 'erasing' is not going to complete, ever.
3. So I again did some research and figured that I should do a fastboot recovery. Tried that with no difference. Recovery again took me to 'erasing' screen.
4. Some more research and then I decided to flash a factory image using ADB. I was (and still am) a complete newbie, so first I figured out what was ADB and how to get to it. After completing the installation, I found out Nexus 5 factory images. There was no mention of which ones to chose, so I just picked up the latest one.
5. Having learnt my lessons, I read the flashing instructions many times and also watched some videos 3-4 times. Once I was confident that no more information was going to be had, and the phone was unlocked (fastboot oem unlock) I went ahead with the flashing. I did it step by step - bootloader, radio and they recovery image. The last one failed.
6. I did some more research and found a method which told me to unzip the last image and flash the component images one by one. I did. Success! However, the phone did not reboot by itself as the guide said it would. So I tried to boot it manually.
7. I did not get the dead android with red exclamation mark. Instead, I got an alive android with gears whirring on its tummy and back. Pressing power + vol-up button told me that this was the 'formatting /data' screen. I am unable to get past this screen. I am supposed to get to a screen where I can wipe data and cache etc. But I cannot get to it.
8. I have tried to wait it out (16 hours) and tried flashing the images again. Ultimately, I end up here.
9. I am unable to find any answers on what to do if stuck on this screen. So this is the end? Is my phone bricked? Is there anything else I can try? Will trying TWRP way useful or is that just another way to same failure?
Since I installed the ICS update, I have no sound control. The speaker shows a slash through it indicating off, but it will not allow me to turn sound on.
Has anyone else noticed that you can't zoom in on sattalite view as close as you used to be able to..Used to I could see my car in my driveway.Not anymore, checked all my settings and see no option to get as close a view as in the past..
make the zoom function part of the operating system. It should not depend on the application or website. Meaning that every screen should be zoomable regardless of application or website. make the text size function available on the desktop. Drilling down through 3 menus to change it is kind of annoying.
Just got my upgraded XOOM back a few days ago, and I've noticed that the battery life is far, far worse than it was before I sent it away. I mainly use my XOOM for reading ebooks, so I nearly always have airplane mode on. Before the upgrade, I could go several days, sometimes even a week before having to charge the battery, even with occasional excursions outside airplane mode.
However, after the upgrade, I can have the XOOM fully charged, in airplane mode, read for an hour just before going to sleep, shut off the screen, and wake up the next day with 60% battery remaining, as opposed to being in the 90-95% range before the upgrade.
The battery usage app shows 87% screen, 11% idle, 3% drmserver. One strange thing I've noticed is that under Settings > About tablet > Status, I see this:
Network: Searching for service Signal strength: -120dBm 16 asu Mobile network type: Unknown:0 Service state: Radio off Roaming: Not roaming Mobile network state: Disconnected
Why would it be searching for service in airplane mode? Did something break in 3.2.2?
So my questions are:
1. Is anyone else experiencing the same symptoms as above (reduced battery life after upgrade, screen showing most usage)?
2. Is there any way for me to downgrade to 3.2 in order to see if that helps? I don't care if that disables 4G, since I'm not in a 4G coverage region.
After a normal morning of Xoom use the battery was low so I turned the Xoom off and plugged it in to charge. This afternoon I unplugged the charger and tried to turn the Xoom on. I get to the Red Circle M with DUAL CORE TECHNOLOGY on the screen but no further. I am unable to turn the Xoom off. If I press/hold the Power button and the Up volume key the unit shuts off and then turns back on.
So I turned on my xoom this morning, saw an update, updated. Now my wifi xoom will boot go to the home screen for approx 1 minute then go back to the honeycomb loading screen for a while before it locks up.
I've just recently upgraded my Motoactv but since then it won't boot.It gets stuck on the pulsing 'M' bit. as anyone else had this issue since upgrading?I've tried holding down 'Start' 'Music' & the 'Power' button, the screen turned off but when booting it up it gets stuck again.I can't re-do the firmware again because my PC wont recognize it.
I plugged my Motorola Razr into the USB to charge, and it is now stuck on the 'dual core technology' boot screen. The device was already powered on, but when I plugged it in, the screen went black and it started to turn on and paused here. I have tried holding the power button and plugging it in and unplugging it, but nothing happens?
My Bravo got stuck at the Motorola Screen. I tried to VOL/POW button at the same time but that leads me to no where. Every 60 seconds, the Motorola logo flashes.
Since updating my xoom, I have had a long delay from 5 to 10 minutes on the honeycomb powering up. Very frustrating, I avoid shutting off my tablet, just let it shut down after a few minues.
As I was talking on my Razr v3 yesterday, I experienced what I thought was just another typical of many AT&T dropped calls. However, upon further inspection, I noticed my phone had gone into boot loader mode for no apparent reason. It's done this on a couple of occasions. Once after it was accidentally dropped and another when I turned it off (then back on) because I was on a plane trip. I've been able to get it back to normal by just power cycling it until it booted.This time no such luck and the screen says the battery is 'too low to program' so if I wanted to attempt to flash it which is something I have NEVER done, I couldn't even do it due to the low battery. This is the only Razr I have and I don't know anyone that still uses one so I don't have one available to put my battery in to charge.Is this the only way to charge the battery? Is it not possible to charge it with the power off?
Greetings, my phone recently froze on me, and I couldn't even reboot by holding down the power button. Instead I opted to reboot via the Power Button + Volume Down method. This forced it to shut down, but upon rebooting, the phone is now in a loop. It shows the Droid at launch, then makes it to the red eye, but after sitting on the red eye a moment, it freezes, then restarts the cycle again.
Things I have tried:
Forcing another reboot via Power + Volume Down Going into the Boot Mode Selection to use Normal Power Up Going to BMS and trying Recovery (Wiped data/factory reset) Attempted to enter Safe Mode (Didn't seem to work, cycled again at eye) Fastboot Lastly, tried launching to Tools in BMS. Same as above.
At this point I am at a loss as to what to do. I would like to not have to send this out, and to fix it here, but is it comes to that, I guess I'll take it to Verizon and see about getting it shipped out, and getting a replacement.
Oh, also this is a stock phone, the only "modifications" I had was Go Launcher and Go Lockscreen. I was, when this happened, going to check my Google Reader app, and that is when it froze on me. (Never had it happen before this)
We have an airave and whenever I leave the house or come back home I have to turn the phone off and then restart to get it to connect either to the airave or an outside tower so the dc will work again. I got home, turned the phone off and left it off for a couple of minutes. Turned it back on and it's been stuck on the black screen with the red motorola icon for about 8 minutes. Is there a force-shut down?
I did a factory data reset on my phone through the settings menu. The phone rebooted, but will only cycle through the Droid boot up animation. I let it go for about twenty minutes. The phone will not let me use the power button to shut it down. The only way to turn it off is to pull the battery. The phone had no problems before this.
I let my phone's battery run out, after plugging it in the the charger for about two minutes, i turned it back on, and my phone has been stuck on the AT&T Rethink Possible boot screen. I have done a batter pull, and still nothing
i bought this KRZR k1 in may2007 unlocked since i was gonna use it in Europe, it worked great
..used it with tmobile for a while when i got a new phone i stopped using this phone and put it away since i know i can use it in europe with their SIM cards well, getttin ready to go to europe again and planned on using this phone again
Here are my problems i charged phone with wall charger and turned it on all i get is a black screen with this on it....
My Xoom said an update was available last week and every since th update was applied the boot process will not progress past the Motorola logo with "Dual Core Technology" below it. How to make my system functional again?
I received my shiny new 3G Xoom (MZ601) yesterday and decided to root it. I successfully unlocked the bootloader and then flashed the rootboot.img file. Unfortunately on rebooting it hung at the Motorola logo. I tried a couple of other boot images, such as Tiamat 1.3.1 and ocboot but all with the same result. Obviously something is different about the European 3G Xoom which makes these US boot images fail.
I managed to "sort of" recover using one of the stock US boot images (can't remember which one!) but my Wi-Fi and Bluetooth are no longer working. What I would really like to do is revert to a completely stock MZ601 image. I see that the Verizon stock images are available on motodev but no mention of MZ601.
Several flashing attempts failed. Now i'm stuck in the "bootloader usb init" screen.(but thats another problem i'm trying to get help with in another thread.)I started with a fully charged good battery, but after hours of trying to get this thing back into verizon by flashing it with VRZ_E815_01.1E.0R_PRIii09574_MONSTER_01.shx , i believe i'm outa juice, well the battery is.So I plugged it in the charger, it's still in the bootloader mode and on! Now.It's been about 4 hrs, but the phone still turns off after displaying 'hello moto' for 1 second(when charger is unplugged), which make it impossible to try fixing the flashing problem.
QUESTION: How do i know that/if the battery is charging while in the bootloader state?.. or is this phone turning it self off, not a battery problem at all, but has something to do with the failed flashing... a dead phone?
My WiFi Xoom cannot boot due to Error "failed to boot lnx 0x0004". I use the following command to update MZ604 image,after reboot, there is red line "failed to boot lnx 0x0004". PC cannot find the device when I use fastboot command after boot in "Starting Fastboot protocolsupport".
I want to install CyanogenMod on my Ray but all the tutorials I have seen say I need to go into fastboot mode. Now, it says that all I have to do is hold the volume up button and attach a USB cable but nothing happens when I do this! The phone just charges as per usual.
I have never rooted my phone nor have I flashed a custom ROM before. I have a 32 GB HTC One M9 from Verizon on stock Lollipop Android, and it has been working perfectly until this morning. I woke up to my M9 stuck in a bootloop. It would boot to the HTC logo, stay there for about 10 sec, then go black and constantly restart again (even as I type this). I can access the bootloader, but it seems none of the options work for me! I can't boot to recovery mode or even power off my phone. It just constantly boots again by itself.
Like others, I tried the software update, and then my phone constantly got stuck at the four little circles at start up. I followed some instructions I found on AndroidPit:
1. From a powered off state, press the Power button to start your Nexus 5. When you see the Google logo press and hold the Volume Down key and release when the device vibrates. 2. Use the volume keys to highlight Recovery Menu and press the Power button to select. This will bring you to a screen with an Android on its back. 3. Hold the Volume Up key for 5 secs then release and a new menu will appear. 4. First off, you can use the volume keys to select Wipe Cache Partition. This will cause your phone to restart. once this is done, re-do the previous steps to get back to the same screen (the one that Wipe Cache Partition was on). 5. Highlight Wipe Data/Factory Reset and select using the Power key. Scroll down to Yes, Delete All Data and press the Power button again to select. 6. Your Nexus 5 will now wipe your data and reformat. 7. On the next screen hit the Power button to select Reboot System Now.
It has been 40 minutes now and it's stuck on 'Formatting /data'. Is this normal?
I've only had this phone for a couple of months and it was functioning perfectly until now I haven't rooted it or anything.
I wanted to unlock bootloader, and I got stuck at the point where I need to use fastboot (adb works fine), initially I thought that I did something wrong - but I've done some research and found out that the problem is actually with the phone. You are probably thinking that I did indeed something wrong, but bear with me please - here is how I found out:When updating/restoring via PC companion or SEUS it doesn´t matter if I connect the phone with volume UP or DOWN, it works either way (obviously should work only with volume down - Flash mode). Also when I use The Flashtool it always says that the device is in flash mode, doesn´t matter if the LED shines blue or green.I also tried getting fastboot to work in Ubuntu (first time around I was using win7 x32) and while assigning UDEV rules I was using the lsusb command and I found out that it reports the same thing in Fastboot (connecting with volume UP) and in Flash mode (with volume DOWN) - it repported 0fce:adde in both cases (and 0fce:0166 in normal mode and 0fce:5166 in USB debug).There is simply no difference when connecting with volume UP or DOWN (except for the LED color) - in both cases it connects in Flash mode...