[Q] Bricked Moto D4 won't boot into Recovery - Motorola Droid 4

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

Related

[Q] Note won't boot on XXLSA

I was using my note to control my Google TV when it restarted. It stuck at the first splash screen, the black and white one before the Samsung boot animation. Restarting the phone either by holding the power button or pulling the battery has no effect. I booted to stock recovery and wiped the cache to see if that helped, but it didn't. And now I can't boot to recovery, it just restarts when it gets to the recovery screen now. I can still boot to download, and seeing as the symptoms looked similar to this thread http://forum.xda-developers.com/showthread.php?t=2034859 I copied what he did and used Odin to flash the stock rooted gingerbread rom from the toolbox by dr.ketan http://forum.xda-developers.com/showthread.php?t=1801341. The flash succeeded, but it still won't boot, and now I can't even get to the recovery screen, but download mode still works.
I'm not sure what to do, should I try and flash an unrooted GB rom?
BTW, I was using a rooted stock JB rom XXLSA before this went wrong, and I hadn't installed anything that day. Also, I hadn't noticed until today but although there is no yellow triangle the download mode has a count of 1, is there a way to fix this if I need to send it back?
Ekreed said:
I was using my note to control my Google TV when it restarted. It stuck at the first splash screen, the black and white one before the Samsung boot animation. Restarting the phone either by holding the power button or pulling the battery has no effect. I booted to stock recovery and wiped the cache to see if that helped, but it didn't. And now I can't boot to recovery, it just restarts when it gets to the recovery screen now. I can still boot to download, and seeing as the symptoms looked similar to this thread http://forum.xda-developers.com/showthread.php?t=2034859 I copied what he did and used Odin to flash the stock rooted gingerbread rom from the toolbox by dr.ketan http://forum.xda-developers.com/showthread.php?t=1801341. The flash succeeded, but it still won't boot, and now I can't even get to the recovery screen, but download mode still works.
I'm not sure what to do, should I try and flash an unrooted GB rom?
BTW, I was using a rooted stock JB rom XXLSA before this went wrong, and I hadn't installed anything that day. Also, I hadn't noticed until today but although there is no yellow triangle the download mode has a count of 1, is there a way to fix this if I need to send it back?
Click to expand...
Click to collapse
Flash a gb rom with odin.. And Triangle away app will reset the flash counter in download mode
Sent from my GT-N7000 using xda app-developers app
Its worth trying a GB rom which has WIPE written next to it from Dr Ketans thread. install using odin a see what happens
Not sure what fixed it, but it's working now.
I just left it plugged in to the mains on the boot screen and it eventually booted up into the stock GB rom, and now the recovery mode works. If I try flashing the XXLSA again it locks up still, not sure why, but it won't boot. I've gone back to using CM10.1 nightlies as I was before trying the stock JB, and that is working as well as can be expected.

[Q] Possibly hard brick situation - help me run down some loose ends

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/

[Q] Weird problem with fastboot when going back to stock.

So I'm using myth tools to flash back to stock and when my device is in fastboot it begins flashing the firmware as usual, however when its like around 30% - 40% the screen flashes off and on for an instant, it then finishes flashing the firmware. However when I reboot the phone it boot loops. This happens with every version of stock firmware. Any one have any clues?

tried installing rom but now bootlooped

Hi guys,
So I had a stock T-Mobile LG G4 H811 that I had unlocked and booted into twrp version 3.1.1-1-g4. I wasn't able to actually flash recovery of this .img becuase of a write failure. So I booted into it instead and then installed it from within twrp into the recovery partition. The actual stock software was the ORIGINAL original, which I think was android 5.1.1
From there, I cleared the cache and delvik cache and installed the G4-H811-10N-xTreme-2.0 Rom. Now, I can't boot into recovery mode anymore, and all I get is the bootloop.. but it's not dead yet because it's a software issue on my part and not a hardware failure.
Any advice on how to get it to recovery mode or at least so I can boot into twrp somehow to try and get this fixed? I tried Power+Volume Down and then let go a sec and Power+Vol Down again and it won't work at all. Just goes straight to bootloop.
Thanks in advance.. I know I screwed up somewhere.. just so many loopholes, it's easy to miss.
Best,
Johnnie
Got somewhere, still broke
Well, somehow I managed to boot into recovery mode only 1 time and installed the stock Tmobile rom. It installed, but now I get a white T-Mobile screen on boot up and it stays there. I tried using the LG Flash Tool 2014 and the stock T-Mobile H811 10N firmware for T-Mobile, but all I get is connection to server errors and the software won't install to the phone over download mode. Anyone else have this problem? I've been trying to figure this stupid thing out for 6 hours. Also, I'm wondering if installing the stock firmware caused the original recovery partition to go back to stock too which is the reason I'm no longer able to boot into recovery mode? It just doesn't recognize it. Power+vol down and then vol down doesn't do anything.
When using the LG Flash Tool 2014, all I get is Connection to Server Failed, Try again. So I do, and nothing. It fails at 9%
Thanks.
jtlefebvre said:
Well, somehow I managed to boot into recovery mode only 1 time and installed the stock Tmobile rom. It installed, but now I get a white T-Mobile screen on boot up and it stays there. I tried using the LG Flash Tool 2014 and the stock T-Mobile H811 10N firmware for T-Mobile, but all I get is connection to server errors and the software won't install to the phone over download mode. Anyone else have this problem? I've been trying to figure this stupid thing out for 6 hours. Also, I'm wondering if installing the stock firmware caused the original recovery partition to go back to stock too which is the reason I'm no longer able to boot into recovery mode? It just doesn't recognize it. Power+vol down and then vol down doesn't do anything.
When using the LG Flash Tool 2014, all I get is Connection to Server Failed, Try again. So I do, and nothing. It fails at 9%
Thanks.
Click to expand...
Click to collapse
try using LGUP

Not able to boot into recovery

I was trying to flash a new rom couple days ago and I feel I did a mistake somewhere which led to an issue and I can't manually boot into recovery (I have tried reflashing recovery) when ever I try to boot into recovery or rom does it for Android updates it gets stuck in fastboot from here I can't turn on the phone, when ever I try to turn it on, it boots back into fastboot, the only way for me to actually get back into my device is by using a pc with fastboot boot recovery.img. It usually updates the rom and I can get back to my device from here. I've tried a couple of things but I'm not able to go to recovery without my pc. Suggest me some fixes that could possibly fix the phone
Thanks in advance

Categories

Resources