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/
Related
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.
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
Here's the deal, I have a sprout8 device (the Indonesian Nexian Journey One) running stock 6.0 with some xposed mods installed on it. Suddenly the device shuts down and when I try to boot it up it only goes halfway through the bootanimation when it shuts down again. I wasn't too worried as I thought it was just a conflicting system issue and I also thought it was time to re-flash fresh stock 6.0 to freshen up my phone anyway. So I went ahead and did it.
Here's where the problems start to show up, I had a hard time booting to recovery through the power + volume up combination. The phone suddenly shuts down on its own as it boots up. I tried it a few times and finally got to recovery. After that, as I flashed stock 6.0 the phone shut down again. I thought it was an issue with my recovery so I tried wiping everything through fastboot and re-flashed recovery through fastboot aswell. From there I tried again to flash stock 6.0 through recovery and again, the phone shut down. I tried a different ROM thinking it was a ROM issue but still got the same results.
After hours of trying to flash a ROM through recovery (retrying over and over as it suddenly shut down while flashing), I finally got a ROM installed. Then I rebooted my phone, but again it freezes halfway through the bootanimation (literally freezing the bootanimation) and refused to do anything. I took off the battery and booted up the phone countless tries trying to get it to boot up. When it finally booted up, I filled in all the Google startup credentials and finally got started on a fresh stock 6.0. However, I tried to restore my previous application data through Android's application recovery on startup but everytime the device installs a new application it would freeze up and shut down. This happened countless times. Then the phone, once again, shut down and could not start the ROM. It would freeze up on the bootanimation.
Then things started to get weird, when the phone turns on it should show the "Nexian" logo in all its glory before going to bootanimation. But here the screen gets all distorted and shows these weird horizontal (and sometimes vertical) lines. Nothing's wrong with my phone screen so I assume it is a system error. From here on, the phone refused to boot. It just shows the Nexian logo and restarts over and over. The same thing happens even after I re-flashed both my recovery and ROM. I even tried using SP Flash Tool to re-flash stock but still the same results.
Now, the device wouldn't even turn on. But when I connect it using USB to a Windows computer, it still gets detected through device manager as an ordinary MediaTek device.
I'm assuming now that it may be a problem with the /system parition where we install our ROMs in. The partition may be (partially) corrupt. Seeing as the device could still boot the ROM a few hours ago but freezing upon updates to the stated partition.
If you guys have any other ideas/solutions I'm all ears.
So i've got this old XT1064 that i ended up passing down to my brother, but he managed to brick it a while ago. A few days back my friend's phone got stolen, so i decided to try and fix this old brick that was sitting in my shelf. Its the Canadian version XT1064. It used to have a custom rom when it got bricked (no clue wich one, long ago.)
Anyways, the problem is; Its constantly in the booting animation. Its not rebooting over and over as it usually happens in a bootloop. The animation just never ends. It doesn't restart, doesn't start into system etc. The only way to get out of the booting animation or powering it off is by hard rebooting it (holding power for 10 secs.)
I've tried a number of stock roms of different versions for the XT1064 and absolutely nothing seems to fix it.. When i try flashing a rom with fastboot, everything shows up as "OKAY [ #.###s]", yet when i reboot it gets to the same animation as before..
Here's a youtube video of the booting animation: /watch?v=HoSds0LULH4
My friend has no money to buy a new phone for a few months and i really want to help her out.
Thanks in advance!
I presume you cleared all the caches and user data and tried again.
Just installing ROM's won't clear caches, you need to use the mfastboot erase command to clear them.
I my case, I had a bootloop, which was not fixed by just flashing a stock ROM.
I had to erase all the caches etc as well
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and got all the flashing related fastboot commands working i've
Flashed a stock image using the miflash tool, seems to succeed but then on reb but once it's done i'm still in a boot loop!
I've been able to boot into twrp a few times (though most of the time I can't and am still in a bootloop)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Throughout the last few hours i've also managed to hit the os a couple of times but it seems very easy to accidently put it back in a bootloop.
If anyone has advice of something to try, that would be great.
(was trying stock image version 10.0.9.0, going to try and go back to stock Oreo)
Smtih said:
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and flashed a stock image using the miflash tool which all seems to go swimmingly, but once it's done i'm still in a boot loop!
Throughout the last few hours i've managed to get into the os a couple of times.
I've been able to boot into twrp a few times (though most of the time I can't)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Sometimes it goes to a failed to boot screen, while other times it seems to loop endlessly.
If anyone has advice of something to try, that would be great.
(was trying image version 10.0.9.0, going to try and go back to stock Oreo)
Click to expand...
Click to collapse
Try some custom kernel, or patched boot img
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
Yeah, A2 have A/B partition and if update is faulty and the phone ends in bootloop, after a few failed boots, it will boot from other partition.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Smtih said:
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Click to expand...
Click to collapse
Plss post the link of 10.0.10