I have an old Verizon Droid A855 that will not boot. All I get is the Motorola M logo and the softbuttons at the bottom of the screen lit and active (when I use a soft button I can feel the phone vibrate). I have tried various Droid sbf files like VZW_A855_FRG01B_QSC6085BP_C_01.43.01P_SW_UPDATE_01 .sbf or VZW_A855_FRG83G_QSC6085BP_C_01.43.01P_SW_UPDATE.sb f and while they seem to flash correctly using sbf_flash in Linux I get the same result when I the phone boots, M logo and active softkeys at the bottom of the screen.
I have tried following various directions available on the internet regarding booting into recovery where I am supposed to hold down the X key on the keypad when powering on the device but this does not work. When I try this all I get is the M logo just sits there forever and the softkeys are not lit. If I eventually release the X key it will after a while change the M logo screen slightly to where again the softbuttons at the bottom of the screen are lit and active (phone vibs slightly when pressing a softbutton).
I have tried flashing various SPRecovery files such as MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b.sbf and they do seem to flash OK but same result when I try to boot the phone into recovery. I am never able to see anything on the screen except for the Motorola M logo.
I have also tried this command as well:
sbf_flash -f -r --recovery /tmp/recovery-clockwork-2.5.0.1-sholes.img /tmp/VZW_A855_FRG01B_QSC6085BP_C_01.43.01P_SW_UPDATE_01 _newer.sbf
but once again I cannot get anything on the screen other that the M logo.
Also when running "adb devices" or "adb devices -l" from Linux command line as root, no devices are listed. I do however see the phone when I run lsusb.
Any help or suggestions would be most appreciated.
Related
Hello Everyone.
My friend bought this G1 which was locked and according to his account was working fine. He got it unlocked and installed another carrier sim. It worked fine for 1 day then it started hanging. He did a battery pull and now it gets to the home screen and then just hangs there.So now when i got this set the condition was If you press "Menu" key the display show T-Mobile Locked Screen which should be unlocked by pressing twice, but it doesnt.If you open the keyboard the screen shifts to landscape mode. Pressing home + power was not putting the phone to recovery and instead it was showing a blank screen(LCD On). There was no Fastboot. The phone was on stock SPL. When i tried to upgrade the Hboot it gave the infamous RUUNBH error. Which took a day to solve through the Gold card method. finally got fastboot by orange***nbh which has fastboot. After that I have updated the Radio 2.22.23.02 with Danger SPL. and Amon RA recovery. but still the condition is same. and now if you press Home + Power for recovery the set goes to recovery but no menu is shown on the screen just " Build:" on the bottom left corner of the screen. If you connect using adb shell at this point it shows " recovery" also i have checked for root using the "su" command through adb which in turns gives another # line which means the phone is rooted. After searching for three days for no avail , Please anyone who has a clue to this.
I did a nand backup of my own G1 and then used fastboot to flash system.img, boot.img to my friend's g1. So now i do have a custom rom on it (Super E). Slight progress is that now it is going beyond the lock screen. But it is very very very slow. even i tap on the screen take atleast 2 minutes to register. And same thing with recovery still. When pressed Home + power the screen goes blank after the g1 logo and then only "Build :" is the visible text at the bottom left of the screen, whole remaining screen is blank.
I have also noticed that this set is unsealed and now i have a suspicion that this is not just a software fault. What do you guys think ???
Also misc.img, data.img ,were not flashed by fastboot. It gave an error that the partition is not available or something...
need help with my nexus one.
basically i can boot into the bootloader but it i try to go to recovery it just shows the nexus X logo indefinitely, if i power on the device without holding volume down or trackball it shows X logo indefinitely. If i pull the battery out while at X logo I cannot boot at all untill i remove the battery for 15 minutes then try again.
I tried getting an official ROM and flashing it with bootloader by naming it passimg.zip and it keeps saying that the file is incorrect and doesnt load it.
ADB doesnt seem to work and the phone doesnt seem to connect to the computer anymore ie to say no dadum sound on windows when i plug usb in on fastboot or boot loader.
its a friend's phone and he asked me to fix it after trying some weird stuff on it. seems usb bricked and seems all the flashes are blank or corrupted..
raheeljessa said:
need help with my nexus one.
basically i can boot into the bootloader but it i try to go to recovery it just shows the nexus X logo indefinitely, if i power on the device without holding volume down or trackball it shows X logo indefinitely. If i pull the battery out while at X logo I cannot boot at all untill i remove the battery for 15 minutes then try again.
I tried getting an official ROM and flashing it with bootloader by naming it passimg.zip and it keeps saying that the file is incorrect and doesnt load it.
ADB doesnt seem to work and the phone doesnt seem to connect to the computer anymore ie to say no dadum sound on windows when i plug usb in on fastboot or boot loader.
its a friend's phone and he asked me to fix it after trying some weird stuff on it. seems usb bricked and seems all the flashes are blank or corrupted..
Click to expand...
Click to collapse
Genral section
ruu 2.3.4 download
Boot in bootloader
Run ruu program
ANd you have gingerbread again
when on the bootloader you have to use fastboot, not adb.
try fastboot flashing a recovery, then try to boot to it
or flash blackrose and check for bad blocks. If there's too many, then your NAND might have gone bad
I have a Motorola milestone (second hand) and tried to load a update for it then i noticed the following problems:
- boot looping at the android logo
-when i tried going into bootloader i get a blank black screen
-when i go into recovery and try to update using "update.zip" i get a EOCD error and another time i get a authorization error
WHAT TO DO????
Come on dude,
Just search EOCD error, I think you will find at least 15 topics.
You lost root, Nedd to flash vulnerable recovery sbf. You will find latest instructions on nadalbak site.
You can find site inside his cm7 topic. Milestone android development.
Sent from my Milestone using xda premium
i'm fairly new to the milestone side, the version that is on the phone is 2.2
Everybody's instruction is to put the phone in bootloader mode and connect to the pc but i only get a black screen and then the phone restarts hence rsd lite not picking it up
Put it in recovery and try to flash another sbf, it should work.
Trough rsd lite.
try that just now and still no response on the pc, and i know the usb port is working because i charged the phone
Are you sure your drivers for phone are correctly installed?
Explain correctly installed?
yeah so what about when i try going into boot loader and get a blank screen?
In the early development of moto driver's phone wasn't recognised by rsd lite.
I didn't hear of that problem anymore though. The solution was to reinstall / install drivers again or try on another pc.
Cable could also be a problem.
Are you trying to enter bootloader with the cable connected to phone? If yes try without and after connect it.
The cable isnt the problem, im sure of that and i tried on two other laptops but they are 64 bit windows 7 but anyways why when i press "power+vol up + camera" i only get a black screen and not black screen with other milestones?
I'm thinking thats the problem or reason why rsd lite not picking up the phone cuz its not in bootloader mode
Ahhh
It took some time since last used bootloader.
But I think is power + x for bootloader.
==== update ====
my bad that's for recovery
oky just tested:
it's power + up key from keyboard
now when i first pressed the power i got a black screen, so i pressed the power again while holding the up key .. and voila:
bootloader 90.78
battery ok
....
good luck ..
when this happened to me i was shocked so much , but then i got it fixed so yay
sigh was trying that from lastnight but no luck
Does anybody have a video to how this done because i'm wondering if i'm doing it right cuz i'm still getting black screen when trying to go into bootloader, i pressed "power + up button on DPAD" and then pressed the power button again but still black screen
While the phone is off, hold the up button on the D-pad and press the power button. Do not let go of the up button until the bootloader screen comes up.
while the phone is off? i can't turn off the phone because its just looping so i take out the battery then put it in and press up and power button so is that the right way?
Yes,
If it doesn't work, for pre 90.78 bootloader I think it was another combination of keys.
Google it
Got it all wrong, the problem was that a app was installed and then the phone was restarted then the looping start at the android sign
no luck, the ways i see is the same as urs
reesieBennett said:
Got it all wrong, the problem was that a app was installed and then the phone was restarted then the looping start at the android sign
no luck, the ways i see is the same as urs
Click to expand...
Click to collapse
about the video:
found this on youtube:
bootloader:
http://www.youtube.com/watch?v=xjQcvg3Eplc
recovery:
http://www.youtube.com/watch?v=H3Vl9NbU6Ag&feature=related
if you enter recovery try wiping everything / factory reset and see if it get into android.
other than this i haven't got any other idea,
it is possible to reboot it with adb if you got a rom that supports adb at boot. ex CM7. cm6 and froyo rom not sure but this is a long shot.
Hopefully you guys can help me with my problem. Recently, I downloaded the new Marshmallow app drawer from Android Pit's "Here's how to get Android Marshmallow's new app drawer on Lollipop". It was successfully installed and seemed to be working fine. However, Google Now gave me a message saying that it was not connected to the microphone and that I should reboot my device. Thinking that the actual reboot key combo was power and volume down, I did this and this brought me to the fastboot page. I selected and entered the power up normally option on the top, which the booted my phone to a completely black screen, from which only the "power off" option would show if I held the power button down. I was confused and concluded that the app drawer somehow soft bricked my phone. After reading up on the web, I went into recovery in the fastboot screen, then selected clear cache. Two lines of orange text appeared at the bottom saying that the cache clear was starting and that it was finishing. I hit the power button, tried to boot my phone up, then, recieving another black screen, brought back up the fastboot menu and tried to enter the recovery screen again so that I could factory reset my device. The recovery screen gave me messages about how it could not load the cache, and since then has been flashing on a set interval on my screen (going black, showing the broken Android with "no command" then going black again).
Any ideas on what I can do to fix this problem?
note: (I have not rooted my phone)
cole_15 said:
Hopefully you guys can help me with my problem. Recently, I downloaded the new Marshmallow app drawer from Android Pit's "Here's how to get Android Marshmallow's new app drawer on Lollipop". It was successfully installed and seemed to be working fine. However, Google Now gave me a message saying that it was not connected to the microphone and that I should reboot my device. Thinking that the actual reboot key combo was power and volume down, I did this and this brought me to the fastboot page. I selected and entered the power up normally option on the top, which the booted my phone to a completely black screen, from which only the "power off" option would show if I held the power button down. I was confused and concluded that the app drawer somehow soft bricked my phone. After reading up on the web, I went into recovery in the fastboot screen, then selected clear cache. Two lines of orange text appeared at the bottom saying that the cache clear was starting and that it was finishing. I hit the power button, tried to boot my phone up, then, recieving another black screen, brought back up the fastboot menu and tried to enter the recovery screen again so that I could factory reset my device. The recovery screen gave me messages about how it could not load the cache, and since then has been flashing on a set interval on my screen (going black, showing the broken Android with "no command" then going black again).
Any ideas on what I can do to fix this problem?
note: (I have not rooted my phone)
Click to expand...
Click to collapse
What is the actual model of your phone. Did you have an unlocked bootloader with TWRP?
The black screen problem can only be fixed by doing a factory reset. After you get into the screen with the dead android and an exclamation mark. You need to press power and volume buttons to make a menu appear. Then choose factory reset. Unfortunately you will lose your data, but this will fix it.
Sent from my XT1095 using Tapatalk
AGISCI said:
The black screen problem can only be fixed by doing a factory reset. After you get into the screen with the dead android and an exclamation mark. You need to press power and volume buttons to make a menu appear. Then choose factory reset. Unfortunately you will lose your data, but this will fix it.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I have solved the issue... I believe it was stuck in some sort of loop with the revovery mode, because that was flashing periodically on the screen. I was eventually able to get the recovery screen to actually stay on the screen and then reset it. Thanks for the quick reply!
d33dvb said:
What is the actual model of your phone. Did you have an unlocked bootloader with TWRP?
Click to expand...
Click to collapse
I have solved the issue but the actual model is the Moto X 2nd Generation Pure Editon without the bootloader unlocked for anyone with similar issues. Thanks for helping out!
I'm having the same issue today with a Moto X Gen 1 after accepting Verizon's OTA upgrade to Lollipop. Only I can't boot to recovery.
cole_15 said:
I have solved the issue... I believe it was stuck in some sort of loop with the revovery mode, because that was flashing periodically on the screen. I was eventually able to get the recovery screen to actually stay on the screen and then reset it. Thanks for the quick reply!
Click to expand...
Click to collapse
I'm still having the problem that you were facing and cannot get out of that loop sequence. I've booted over and over, tried to launch recovery and nothing... I see some yellow text at the bottom only briefly staying that something couldn't load, then back to the dead-droid/red triangle (no command) for a split second, over and over... I am stuck.
Pfister07 said:
I'm still having the problem that you were facing and cannot get out of that loop sequence. I've booted over and over, tried to launch recovery and nothing... I see some yellow text at the bottom only briefly staying that something couldn't load, then back to the dead-droid/red triangle (no command) for a split second, over and over... I am stuck.
Click to expand...
Click to collapse
I'm having this exact same problem too! The 'dead droid' just constantly flashes over and over, so I am unable to do anything. There was one time when I held power and the low battery icon showed up with a yellow exclamation mark triangle, but I haven't been able to get that screen again. I contacted Motorola and they told me to try and go to settings and do a factory reset... I just told you I can't turn on my phone! What the hell man. I have tried so many things online and none of them worked. From what I'm reading the only was to fix this is to flash a blank bootloader, but those files haven't been released yet.
The worst part is that I have only been using this phone for ONE DAY!:crying:
cole_15 said:
I have solved the issue... I believe it was stuck in some sort of loop with the revovery mode, because that was flashing periodically on the screen. I was eventually able to get the recovery screen to actually stay on the screen and then reset it. Thanks for the quick reply!
Click to expand...
Click to collapse
How did you get the screen to eventually stay on?
mistervino said:
How did you get the screen to eventually stay on?
Click to expand...
Click to collapse
okay so after several guides and steps, i finally got my Moto X (1st Gen) working again using the tutorial here https://www.youtube.com/watch?v=EWDwyqUF6k4
Essentially i flashed a custom recovery like the PhilZ Touch recovery here http://www17.zippyshare.com/v/40132571/file.html by renaming the "philz_touch_6.58.7-ghost.img" file to "boot.img" in fastboot mode and rebooted after that.
And that was it, phone rebooted and is working fine.
I have been trying to root my phone and now my Fastboot screens black. No longer shows the options to boot into recovery, power off and etc with the volume button toggles and power button as select. How do I get that option back? Or is there another way to boot into recovery? Thanks.
I am having the same issue, it seems.
Rooted my phone when I got it a year ago, but messed up with the DRM-keys.
Was running some Lollipop stock-ROM until recently, but decided it was time to update.
Flashed the stock 6.0.1 ROM and, from what I can tell, also successfully flashed TWRP 3.0.2. But I've not been able to get into recovery (tried "fastboot boot recovery.img" but I get a completely black screen at that point, although "backlit").
Fastboot has never shown anything (the LED just turned blue, but the screen is completely black, but not "backlight").
Didn't mean to hijack the thread, but it seems we have the same problem.
PS. The phone boots fine, and works as it should.
Wait shouldn't the fastboot screen always be black? I have never unlocked the bootloader,but my fastboot screen always showed the blue LED and a black screen