I have the Motorola droid hd xt926 with the Android 4.4.2. Update. I suddenly for unknown reasons have been reduced to having little more than an expensive paperweight. Upon startup the phone shows only an infinite glowing red eyeball with spinning lightning bolts. This goes on until the battery dies. I have discovered the recovery and ap fastboot modes. I have performed several cache clears and factory reset/wipe data selections only to get more stuck on red eye. When I press power+volume up and down then scroll down AP fast boot I am encouraged to see the battery ok and connect USB cable options. However I have not found instruction on what to do next specific to my device loaded with Android 4.4.2. So, since I'm stuck on the boot loader what can I do to reflash, refresh, repair, or reinstall the appropriate Android system? I have never rooted it and am unable to switch on USB dubugging because I'm stuck at eternal red eye. I think I am looking for a download of the respective Android image file and the necessary utilities to deliver it from my Windows 7 pc to my droid phone via fast boot mode and rsd6. Does anyone have a solution?
Check your inbox I can't send links yet.
Let me know if you need some help with that.
I am experiencing the same issue. Is there anyone that can help me with this? Thanks
Related
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
yeah:) said:
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
Click to expand...
Click to collapse
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
alroco20 said:
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
Click to expand...
Click to collapse
This thread is old, and OP is ignorant and wants to blame ROM Manager for his own problems. If you can't get into recovery, chances are you are using one built for another phone. Find the one for the G1.
Or ran into the know issue of cm5.0.7 that fash_image sometimes (more than not) fails.. thus applications using it sometimes fail.
But you have danger spl right? So flash the recovery via fastboot.. and if you don't have fastboot/adb and intended to run these custom roms its about time you installed it.
I could only find three references to boot loop in the Moto G troubleshooting area...so here I type.
phone is XT1064
Was trying to side load Lollipop. Got to the boot menu no problem...when I selected Recovery the phone rebooted and got stuck on the Moto logo screen "powered by android."
I'm able via external reset get back to the boot menu, but whatever option I choose I end up looping...
Just spent a couple of hours with Moto tech support...painful, avoid if possible. The script pages were turning so fast I thought there were wind gusts in the tech office!
Any ideas would be greatly appreciated.
Littlalex
littlalex said:
I could only find three references to boot loop in the Moto G troubleshooting area...so here I type.
phone is XT1064
Was trying to side load Lollipop. Got to the boot menu no problem...when I selected Recovery the phone rebooted and got stuck on the Moto logo screen "powered by android."
I'm able via external reset get back to the boot menu, but whatever option I choose I end up looping...
Just spent a couple of hours with Moto tech support...painful, avoid if possible. The script pages were turning so fast I thought there were wind gusts in the tech office!
Any ideas would be greatly appreciated.
Littlalex
Click to expand...
Click to collapse
did you have your xt1064 rooted? i have mine rooted in lollipop, i also have the boot loop when starting sometimes, so far you can uninstall root via super user app and solve the problem or have patience untill some good developer fix this problem, to get out of the boot loop i find that connecting to charger the phone does the trick for me, it take like 3 minutes to start, if i uninstall root it starts very fast, im waiting for a solution.
I have a Note (GT-N7000) which has decided to no longer boot up completely. It is unrooted stock ROM. It manages to get bast the initial boot screen, but gets stuck on the SAMSUNG splash screen.
I can:
Boot into Recovery
Boot into Download Mode
Use ADB
see it in device manager as aMTP Device (although I can't see the actual device contents)
I have data (appdata, and files/documents)on it I need to get off, is there any hope?
It's my wifes phone, so some of you probably know how important this is!
Any help appreciated.
dartho said:
I have a Note (GT-N7000) which has decided to no longer boot up completely. It is unrooted stock ROM. It manages to get bast the initial boot screen, but gets stuck on the SAMSUNG splash screen.
I can:
Boot into Recovery
Boot into Download Mode
Use ADB
see it in device manager as aMTP Device (although I can't see the actual device contents)
I have data (appdata, and files/documents)on it I need to get off, is there any hope?
It's my wifes phone, so some of you probably know how important this is!
Any help appreciated.
Click to expand...
Click to collapse
From what I've read, I guessed I'm screwed, but was hoping there was something I missed. Look slike the phone will be relegated to a drawer in the hope that one day I can get data back. Look out Note 3! (or 4 if the budget can stretch)
Solved!
So, I ended up installing PhilZ-cwm6 - Safe Stock Based Kernel (http://forum.xda-developers.com/showthread.php?t=1901191) and could then boot into a custom recovery, mount USB and copy all the data off.
All good. Now to factory reset and see if phone comes back to us. Already got a new Note 4 to replace the old girl, so not a issue anymore.
my device was working fine after replacing the battery (0onite 2070mah) and screen. i lend the phone to a friend, when he tried to charge the device, it went to boot loop.
so my phone is stuck on boot loop ( it shows the blue motorola ( a google company) logo,on and off)
device wont charge,can only be on when connected to charger or laptop.
when i go to recovery mode,it blacks out in a second, then goes to startup
i dont know what to do. i got some flash tools from youtube.
Motorola drive
Driver Installation 6.4.0
and a firmware restore lock and more (cant post link)
help!
its not a rooted phone......
well,i dont know wich stickies i should read about my situation?
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
utundu said:
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
Click to expand...
Click to collapse
Try sideloading an OTA image. You can do that with a locked bootloader.
Thanks Lughnasadh
I've tried multiple times, and the process fails randomly, at different percentages ...
The phone suddenly reboots and the laptop displays " adb: failed to read command: No error"
The weird thing is it doesn't reboot and can stay up for super long while on the bootloader.
With a locked bootloader the rescue OTA (full OTA image flashed via adb) is all you have. I would try a different data cable (A-to-C) first and then move to a different computer. Make sure the new PC is running the latest adb/fastboot binaries. This is why I unlock the bootloader on every Pixel in my family. Even though they will never root the phone, if the fit hits the shan you have many more options. BTW, I just traded in my son's P4XL and got $285 trade-in on a 6a. Net cost was less than $150. The deal just ended but will likely come back again. Same deal was offered earlier but included a pair of first-gen earbuds. Wish you luck on getting your old phone working. The P4XL is still my primary phone and is still working well.