I got a Droid Bionic which was not able to boot and actually it was stacked into “DROID screen” which is coming up after the red Motorola Logo.
The phone was able to enter into recovery mode but although I wiped data and cache it was still not able to boot.
I flashed through RSD Lite (5.7) the 6.7.246 XML zip and everything went OK. The procedure end up with no errors and then the green droid came up as expected … after the flashing procedure completed the phone rebooted BUT again end up stacked into the DROID screen.
I entered again into recovery and wiped just in case, but still the same problem. The phone boots until the DROID screen and then remains there …
I tried to flash the 6.7.246 a few more times but every time the same problem.
At the end as I was desperate I flashed the flashable 6.7.246 zip through the stock recovery and again everything went ok with no errors. BUT again the same problem … The phone remains stack into DROID Screen and cannot boot ...
I am starting believing the phone has hardware problem … Any ideas?
Hardware problem. Nothing else really left to try. Are you sure flashing .246 is working or are you perhaps missing an error message somewhere along the way?
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD
Same Problem
Hi Guys,
I have the same problem with my Bionic. I've been working on this thing for about a week straight and still stuck at droid screen. Of course now we have JB but its not making a difference for me. I got no errors when flashing Jelly Bean and Droid Screen Persists. Here are a few things i've tried.
Used JB cdt.bin, boot.img, system.img with the rest of the files being ICS. After booting i get blank screen after moto insignia.
So i used the update.zip for JB and it passes. Everything patched well and correctly but no boot animation just the droid screen again.
Flashing strictly JB files with RSDlite and HOB got no errors but still no boot past that droid screen.
Are we sure this could be a hardware problem and if so is there a way to fix it?
Hello,
in my case proved to be a Hardware issue. Fortunately the device was still under warranty and was replaced by Motorola.
Related
It's been randomly crashing and and shutting off a lot lately. Today, whilst on a call, it shut off and wouldn't boot back up.
ClockworkMod still works and I have wiped boot, system, data and cache and then re-installed CM7 (the rom it was on when it died) but it hangs at the boot ani. Tried a rooted 2.3.4 and it hangs/reboots on the X.
It's had the mobo replaced a while back - could this one be dead now too? Or is there something else I can try?
TIA
managed to get it to boot again with updated hboot (spl) from here:
http://forum.xda-developers.com/showthread.php?t=744605
Hello,
I have a Droid 4 that recently black-screened and wouldn't respond to any input, and upon rebooting won't get past the Motorola Logo boot screen.
It was previously rooted, but I had not flashed anything onto it, and I believe it was on Android 2.3.6 still.
The current state of affairs:
A normal boot shows the Motorola Dual Core Technology screen, as well as a thin multi-colored line along the bottom of the screen.
Boot Mode Selection Menu works fine, but booting into Recovery shows the Motorola screen indefinitely (without the thin line at the bottom)
AP Fastboot and BP SBF flash modes appear to work normally, and I am able to see the device in RSD Lite 6.0.
Steps I have taken:
I tried to fix the problem by flashing 9.8.2O-72_VZW-18 Blur_Version.98.72.18.XT894.Verizon.en.US from sbf.droid-developers.org/cdma_maserati/list.php The flash was successful, apart from not rebooting successfully. When I manually restarted into AP Fastboot, RSD said the flash passed successfully.
There has been no change in startup behavior since I flashed the new version. I still can't boot into normal phone operation or recovery.
Please help!
Regards,
RS
RestroomSounds said:
Hello,
I have a Droid 4 that recently black-screened and wouldn't respond to any input, and upon rebooting won't get past the Motorola Logo boot screen.
It was previously rooted, but I had not flashed anything onto it, and I believe it was on Android 2.3.6 still.
The current state of affairs:
A normal boot shows the Motorola Dual Core Technology screen, as well as a thin multi-colored line along the bottom of the screen.
Boot Mode Selection Menu works fine, but booting into Recovery shows the Motorola screen indefinitely (without the thin line at the bottom)
AP Fastboot and BP SBF flash modes appear to work normally, and I am able to see the device in RSD Lite 6.0.
Steps I have taken:
I tried to fix the problem by flashing 9.8.2O-72_VZW-18 Blur_Version.98.72.18.XT894.Verizon.en.US from sbf.droid-developers.org/cdma_maserati/list.php The flash was successful, apart from not rebooting successfully. When I manually restarted into AP Fastboot, RSD said the flash passed successfully.
There has been no change in startup behavior since I flashed the new version. I still can't boot into normal phone operation or recovery.
Please help!
Regards,
RS
Click to expand...
Click to collapse
It looks like you tried to flash the JB fastboot files. If you were on GB that may be your problem. I'm not for sure on this but I think the fastboot files will only flash over itself or the previous software version. Maybe try flashing the GB or ICS fastboot files and see what happens. Doesn't sound like it could make it worse.
kwyrt said:
It looks like you tried to flash the JB fastboot files. If you were on GB that may be your problem. I'm not for sure on this but I think the fastboot files will only flash over itself or the previous software version. Maybe try flashing the GB or ICS fastboot files and see what happens. Doesn't sound like it could make it worse.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried the 6.5.1_167_DR4-1_M1-219, which didn't have any effect. I'll try the 6.5.1_167_DR4-1_M1-215 and see what happens.
You can flash same or higher than what your phone/device was....ie....if you were on GB you can flash the GB, ICS or JB fastboot files to stay at GB, update to ICS or update to JB. If you were on ICS you can fastboot the ICS or JB fastboot files to stay the same at ICS or update to JB.
If you are on JB or have flashed the JB fastboot files....you can only RSDlite the JB fastboot files.
I would reflash the JB fastboot files and then attempt to let the phone boot normally. If it boots normally, then reboot and try to enter Recovery.
Try booting into a Linux OS and connect the phone. Then use the Droid 4 ICS or JB utility. Boot the phone into fastboot ap mode,connect the phone to linux, and run ICS or JB Utility. It should work right away, I was getting the same thing a few days ago and the JB utility worked for me with Linux and not Windows.
Sent from my DROID4 using xda premium
Hi all
Pertinent details:
Rooted / safestrapped Bionic with Stock ROM (I honestly can't remember, but I believe it was the ICS leak - may have been JB, whatever it was, it was NOT OTA. I flashed it manually, I believe via recovery) and ROM slot 1 running the Bionic CM11 nightly
Safestrap was updated, as was CM
About a month ago, I dropped the phone, broke the LCD, ordered a new one, and long story short, the phone was disassembled, and sat disassembled for about a month (had other things come up). Battery wasn't completely dead when I put it back together, but the battery wasn't in it either for that month.
Got around to putting it back together, the phone boots to the M logo, and will sit there indefinitely, doing nothing. Strange right? Worked fine even when the LCD was broken - I was able to make a phone call while the LCD was black by memory
I can access AP Fastboot and RSD Lite can see the phone. Recovery mode hangs at the M logo screen, does not proceed beyond it
What I have tried so far:
RSD Lite the JB 9.8.2O-72 official build - result: hangs at M logo, briefly turns off then back on after 4-5 minutes, but will hang at the M logo for the next 30+ minutes, recovery does the same thing
RSD Lite the 246 official build - result: will not flash, MBM fails, MBM loader fails, CDT fails, I stopped removing command lines after that
Moto-fastboot the preinstall.img and system.img from 246 in an attempt to get to recovery and install JB from there - result: hangs at M logo indefinitely, briefly turns off and on as with the JB build when trying to access recovery but just sits at the M logo after that for 30+ minutes
Right now I'm extracting the JB official build and will moto-fastboot system.img/preinstall.img/recovery.img in an attempt to at least get to recovery
Does this sound like a hard brick situation? Any possible solutions? I've done a ton of googling, a ton of reading, and tried a lot of different things, with no progress whatsoever.
thanks!
If you tried flashing the jb fxz first that was the problem. There are two files within that fxz file you have to remove, I any remember off hand which ones but should be easy enough to Google. Good luck
Sent from my XT875 using Tapatalk 2
Here ya go
http://www.droidrzr.com/index.php/topic/1107-fix-unknown-fastboot-command-oem-phone-connected/
Last night I started messing with the S5, I used Odin to restore to stock, then took all the OTA updates all the way to the 4.4.4 one that came out recently and after that I debloated it and removed the att apps and such, everything was fine. I tried changing the boot animation but messed up somewhere along the way and it wouldn't show a boot animation at all but still booted and got to the main screen and functioned perfectly. I decided to start over and tried to use Odin to restore to stock 4.4.2 but after flashing the first screen comes on and says that it's custom and has the open lock symbol then shows a slow and laggy samsung boot animation before freezing at some point on the animation and the screen goes completely black but the blue LED light stays on and it does nothing after that. I have tried using Odin repeatedly and erasing everything through recovery and nothing works. Please, any help would be appreciated.
It has been fixed I believe, I flashed the G900A_OA1_Stock_Kernel.tar.md5 and it works again.
Where did you get the .tar.md5 file? I think I just bricked myself out of recovery mode
Using my Moto Maker XT1060 (Verizon variant). I had unlocked bootloader some time ago using Sunshine and was previously using the most up-to-date VZW 4.4.4 firmware.
I got sick of waiting for VZW to release the Lollipop update so I figured I would try CM 12.1. Here's what I did:
Download the latest Dev Edition recovery firmware from Motorola (VZW_212.55.26.ghost_verizon.Verizon.en.US.tgz)
Flashed it to the device using fastboot successfully for a stable and clean base
Booted up and used the phone no problem
Downloaded the CM12.1 Nightly .zip file
Downloaded the latest TWRP and flashed it
Booted into recovery no problem
Used TWRP to do a factory reset
Installed CM .zip
Restart the phone normally
The phone was able to load CM and get to the Startup Wizard, but was caught in a soft bootloop (no rebooting from bootloader and buzzing, but the system would crash and the CM boot animation would come up, then repeat). I noticed this was happening at about the same time that the "Location" icon was appearing in the notification tray, so I figured it was an issue with GPS. I rebooted and cleared modemst1 and modemst2 using fastboot, but this yielded no results.
At that point I figured "to hell with it" and flashed the Motorola recovery firmware back onto it using fastboot. Now the damn thing is stuck in a soft bootloop and won't get past "Preparing device..."
No idea what happened, I have never experienced anything like this before (fully flashed 6 other devices at this point). Any help is appreciated as of all the devices I have worked with, this one is actually my personal phone. Figures it would be the one to get screwed up somehow...
Did you format/wipe /data or perform a factory reset before booting into CM?
Sent from my Nexus 6