i really need help. i have a Motorola droid milestone a855 stuck at the M screen on boot. i can boot the phone and load recovery (i think) because it's always the M screen. the phone has a broken power button, and when you turn it on it actually boots up. you can feel it vibrate once and see the screen dim. and when you tap the volume buttons, like 10 or so seconds later you get a delayed beep.
View attachment 2215474
View attachment 2215475
that's the M screen. notice how the touch buttons are lite up, and the little fuzz at the bottom, and how the M is near the edge of the screen, and is always changing position everytime on boot. I've tried using RSD lite and I've flashed all the VZW files and boot loaders, to no avail. someone help please?
Edit:
I might have figured it out, while I was in that red triangle / exclamation point screen, I pressed power / volume, then when the screen turned black (phone off) I let go of power and kept holding volume, and it finally entered the bootloader and RUU is now running. Will edit the thread again if that goes through. Leaving info in case anyone runs into the same issue in the future.
Edit2:
The RUU failed when the fastboot binary crashed on step 4 @ 96%, so I switched to a USB3 port and reran and it got through 100% without a hitch, now the phone is working perfectly.
-----------------------------------------------------------------------------------------------------------
Hi, my phone is s-off, bootloader unlocked, h7_wls.
I flashed 5.05.651.2_full_firmware.zip (to install the ViperOne rom - it says to update the firmware) through fastboot, running it 2 times as recommended. Then I ran fastboot reboot and the phone was stuck in a boot loop, the white screen with the HTC logo would appear, then the screen would turn black (still on as it has the IPS blue glow) then it turns off (full black) and turns on again to repeat the loop.
I've tried holding down volume + power until the home/back flash then letting go of power and holding volume, but the phone would just reboot without going into the bootloader.
I've also tried shining the LED from my other phone onto the light sensor and holding power for 15 seconds, which turns off the phone. If I turn it back on, it returns the phone into the aforementioned boot loop.
Doing the volume + power thing, and running the RUU_M7_WL_K44_SENSE60_SPCS_MR_Sprint_WWE_5.05.651.2_Radio_1.01.20.0904_2_NV_SPCS_4.38_003_release_393160_signed_2.exe file while the home/back buttons flash gets the phone into a black background with a red triangle / exclamation point but the RUU program exits with Error[170]: USB CONNECTION ERROR.
Typing adb devices while in the black screen with red triangle / exclamation point, it sees the device but says the device is offline, typing fastboot devices returns nothing.
I've tried 3 USB cables.
Not sure what to do next?
Thanks.
kevinlekiller said:
Edit:
I might have figured it out, while I was in that red triangle / exclamation point screen, I pressed power / volume, then when the screen turned black (phone off) I let go of power and kept holding volume, and it finally entered the bootloader and RUU is now running. Will edit the thread again if that goes through. Leaving info in case anyone runs into the same issue in the future.
Edit2:
The RUU failed when the fastboot binary crashed on step 4 @ 96%, so I switched to a USB3 port and reran and it got through 100% without a hitch, now the phone is working perfectly.
-----------------------------------------------------------------------------------------------------------
Hi, my phone is s-off, bootloader unlocked, h7_wls.
I flashed 5.05.651.2_full_firmware.zip (to install the ViperOne rom - it says to update the firmware) through fastboot, running it 2 times as recommended. Then I ran fastboot reboot and the phone was stuck in a boot loop, the white screen with the HTC logo would appear, then the screen would turn black (still on as it has the IPS blue glow) then it turns off (full black) and turns on again to repeat the loop.
I've tried holding down volume + power until the home/back flash then letting go of power and holding volume, but the phone would just reboot without going into the bootloader.
I've also tried shining the LED from my other phone onto the light sensor and holding power for 15 seconds, which turns off the phone. If I turn it back on, it returns the phone into the aforementioned boot loop.
Doing the volume + power thing, and running the RUU_M7_WL_K44_SENSE60_SPCS_MR_Sprint_WWE_5.05.651.2_Radio_1.01.20.0904_2_NV_SPCS_4.38_003_release_393160_signed_2.exe file while the home/back buttons flash gets the phone into a black background with a red triangle / exclamation point but the RUU program exits with Error[170]: USB CONNECTION ERROR.
Typing adb devices while in the black screen with red triangle / exclamation point, it sees the device but says the device is offline, typing fastboot devices returns nothing.
I've tried 3 USB cables.
Not sure what to do next?
Thanks.
Click to expand...
Click to collapse
oh yeah this time happened to me as well
basically all your phone is doing is rebooting
you need to get it to power down somehow. I managed to force shut it down using the hold power thing and then held volume down and power to get to the boot loader
but if anyone is having difficulty another sure fire way to get the phone to shut down is to wait for the battery to die (may take a really long time)
Tab s2 8.
Was using practically fully charged tablet one minute, went to use again and screen black.
Back and task switch buttons still light up when press power or home. Plus volume up/down makes the louder/quieter beeps.
Power and volume down gives me the quickest flash of the samsung and android boot logos and then screen black again. Makes the email received notifications you get when restarting the tablet.
Is basically on but just no screen. But screen still functional enough to briefly show boot logos.
Any thoughts?
Update. After about 30 mins of faffing, magically returns to life. Any thoughts on common issues that might have caused? Indicator of something about to go wrong for good?
Put down gently today and the right side of the screen displaying flickering dark/black stripes. Left side of screen perfectly fine. Touch still works over the whole display. Any ideas? Internal cable come loose? Or something more terminal? How easy to check/fix?
Xdaforumposter said:
Tab s2 8.
Was using practically fully charged tablet one minute, went to use again and screen black.
Back and task switch buttons still light up when press power or home. Plus volume up/down makes the louder/quieter beeps.
Power and volume down gives me the quickest flash of the samsung and android boot logos and then screen black again. Makes the email received notifications you get when restarting the tablet.
Is basically on but just no screen. But screen still functional enough to briefly show boot logos.
Any thoughts?
Update. After about 30 mins of faffing, magically returns to life. Any thoughts on common issues that might have caused? Indicator of something about to go wrong for good?
Click to expand...
Click to collapse
I have an Lg G4 ls991 from sprint. Haven't used it for like 2 years cause of this issue I got. When I power up the device it starts up with the lg logo then after a few seconds the screen goes black. LED lights still visible and pulsing a few senconds later the sprint boot animation can be heard but with black screen still. The phone turns on and completes the boot cycle but if I try to unlock the device it won't come one. If I hold the power button and wait a few seconds the screen will come on with half flickering and the other half normal. The touch does t work when the screen is on but when it's off and I double tap it the device appears to react with an unlock and black screen. Device seems to be running fine in the background like normal. I can still manage the volume, when pressed the beep sound comes up informing me that the volume changed. I have doubts that this can't be an screen issue but a Motherboard issue. Any thoughts on what could be the problem?
Hi, so I got an A2 which has been submerged in water for a while. I was not turning on at all (just showing the white led light blinking), so I bought a new USB part and battery for it, replaced it, and now it seems to react.
However, it keeps switching between the charging logo for a second, then vibrates and shows the Android One logo (this switch goes on and on forever). I have tried the button combo to go into recovery, but as soon as the Android recovery boot logo appears, it'll still timeout into the charging logo.
Does anyone know what may be going on? Or what component to replace? (the phone was only days old when it accidentally got soaked, so everything is new and it's a shame to just throw it away)