I have tried holding down the volume buttons and power button several times the past three days and nothing. The device vibrates and nothing happens. If I continue to hold the buttons then it vibrates every 6-7 seconds. I also tried to get into fastboot using a toolkit in our development section with no luck. The toolkit says I'm in fastboot when connected, but nothing is on my screen.
At this point I am at a complete loss. If I can't get it to work is that a valid reason for replacement by Google?
I went through all the settings and could not find a way to configure the phone to speak the SMS, the caller id, etc....when I am driving.
On my other phone, a samsung galaxy s3 from verizon with android 4.3, there is a "driving mode". I thought it was a true android capability, but could it be a samsung feature instead ?In any case how do I get the Nexus 5 with Android 4.4 to do the same ? can I get it to do it using an NFC tag...
I tried flashing a stock Android 4.2 JB ROM that seems legit. After flashing, I rebooted my device and saw the standard Nexus boot animation. So far, I though all was well. It's not. My phone has been stuck in this constant booting state for hours. I pulled the battery after an appropriate amount of waiting and held down the power and volume down+up button. Instead of booting into Fastboot mode, it went straight to Odin Mode. All I can do with my device is boot to Odin Mode or watch the Nexus boot animation over and over again.
Friends of Jupiter Huawei g525-u00and have been asked Ram Kastvm able but Alanmshkl. Already green screen after power ... not that fast boot mode will not go into recovery mode and not the original ROM using loam bottom half Vbala White gets going
My Problem: Was using the HTC Desire bought in India. I rooted with Unrevoked 3.21, S-OFF with Alpharev.
I was thinking of taking my phone to HTC to show an LED burnin problem, and tried to unroot by flashing the RUU for Asia_India: RUU_Bravo_hTC_Asia_India_1.21.720.4_Radio_32.36.00 .28U_4.06.00.02_2_release_127705_signed. I thought that was the correct RUU.
I booted my phone in Fastboot, applied the RUU, and it rebooted my phone into RUU. Then it flashed an error message saying the RUU version was incorrect. Being the idiot that I am, I rebooted the phone..And got stuck!
The phone does not boot. On pressing Vol- and Power button, it vibrates, and then nothing. Screen is blank. It wont boot into Fastboot, Recovery or the ROM. If I connect it to USB and do the Vol- and Poweron, it detects my device as an Android 1.0 device.
I have tried the following: 1. Went to Android SDK, tried flashing Clockworkmod recovery image with the command: Code:........
I want to install ClockWorkMod Recovery on my Karbonn A18, i tried doing it using SP Flash Tool, but it gives various Errors, I want to know how can i get into FastBoot Mode in A18 so that i can install it through their ?
My mom's LGC800 is stuck in LG boot screen, is there any possible way to enter fastboot mode in the LGC800? I tried the adb command "adb reboot bootloader" it reboots and gets stuck again in LG boot screen..
I have a motorola motostart (xt390) and wish to unlock bootloader, root, etc. Nevertless, I just can't get into fastboot mode. Powering up with VOL Down it access the recovery mode. The same for VOL UP+DOWN. When i try powering up with VOL UP pressed the device simply don't power up.
Is it a malfunctioning device or some roms for this hardware simply have mysteriuos ways to enter fastboot?
The ROM is a brazilian retail, Gingerbread (2.3.6) version MAUI.11AMD.W11.37.SP.V9.F4.P1, build: ARGONM_W_07.15.04R_D.
my nexus 5 is stuck in boot loop ( turning on and off by itself and can't get past the Google icon) and i can't access the boot loader for a reset. all system reset/ factory image guides require me to access the boot loader but the problem is that the phone won't stay in the boot loader because of the boot loop, it turns off as soon as i get into the boot loader.
I have a Nexus S running 4.0.4. I did the update manually when it was released.
The bootloader is unlocked from previous ROM experiments but this ICS is stock/unrooted.
A few weeks later, the power button now doesn't work. This is a VERY common issue, but no one knows for sure if it is Hardware or Software. I was going to lock my bootloader and send it in to get a fix or replacement device from my carrier. Alternatively, I was going to attempt to flash a ROM onto it and see if the button comes back.
The bizarre thing is that when I go into fastboot, the device freezes and I cannot use any of the buttons. Furthermore, below the device information, nothing else shows up. The device shows up to ADB when booted, but Device Manager doesn't even find an unknown device when in Fastboot.
I deleted /system folder on my nexian cosmic journey. And now my nexian is stuck...
I try to using fastboot mode to flash recovery image, but my device seems not detected. I already installed the android composite driver, but when i use "fastboot devices" command, it shows (?) So how the heck to get my nexian back to normal?..
Or perhaps, if i just be able to put back the /system folder to its place again, it would be more easy to recover it... But how access the root when phone is like that?
New to Android here after a long hiatus and with a Moto X. I am enjoying it. But certain apps (for example Hangouts) are stuck on downloading. I tried clearing cache etc etc, restarted but to no avail.
I should have just left it as it was out of the box..So after attempting to install a custom rom (4.4.2 Play edition)my s4 is stuck at the Samsung I9505 boot screen. I wiped the 'Dalvik cache' 'System' and 'cache' partitions in TWRP as I was following along with a Youtube video (that didn't work). When I tried to flash the custom ROM it automatically said failed. After giving up and turning on the phone I found that I'm stuck at this screen.
Have I bricked the phone? $550 could have gone down the drain just like that. I don't want to touch it without any advice and make everything worse. My only hope now is that I've managed to wipe the original software and it has nothing to boot from.
Why did the ROM install fail in the first place? I had it copied on the SD card. It was zip file.I can still access TWRP just fine and my SD shows up with the custom ROM still there, it's just whenever I hit install it fails in under a second.
in iOS, I can set a DND mode for a specific time automatically so the phone will not ring or alert me during that specified time. This is particularly useful for a recurring event (meeting or sleeping time).
Is there a way to do that in 4.4.2 without downloading a new app in Google Play? It would be nice to be able to do that automatically so i do not have to silent the phone every single time for that recurring event.