Just RSD'd the .902 file trying to update my phone finally, and for some reason I'm bootlooping. I've never had a problem with RSD Lite before and now I seem to get the crappy end of the stick. It got through all 15 steps, then to the 'reboot' process where the little android pops up on the phone that comes up when you are updating your firmware, then it booted up and now RSD lite says 'Please manually power up this phone' and its just looping looping looping looping looping...so then I pop the battery out, plug my phone back in and boot to fastboot and RSD Lite says 'PASS'..as in everything worked..... what should I do? re-do this?
nevermind i just went into stock recovery and factory reset and got it fixed. but i'm still on 886, even though RSD Lite said it went to 902
Related
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/
My out of the box Nexus 6 is now stuck looping on and off at the Google boot screen after it tried to install the system update.
I've used the toolkit 1.9.8 to go back to stock. It goes thru the steps appearing to show OKAY and finished at each step. It never reboots the phone at the end. I try to force reboot after waiting for several minutes and it still boot loops. I try again the process again and sometimes it loops and a few times it actually starts up to the welcome screen. However, if I try to root or update recovery (using the toolkit), I get the boot looping again.
Did google bork my phone during a failed update? Is there anything else I can do to completely restore the phone? I've also downloaded the images on google and flashed---same boot loop.
Ultimately, my phone is now booting up to the welcome screen as expected and shows LRX21O. BUT, if I try to do anything (root or recovery), boot loop results again.
(I was able to unlock the phone and know about the usb debug and OEM unlock settings in dev menu, fyi).
Hi
I have an AT&T XT1058 with locked bootloader, on 4.4.4
I tried to rest it to factory, but it got stuck on 'Erasing...' (with the little droid) for more than an hour, so I reset it.
Since then it won't boot, only keep stuck on 'Erasing...'. I've tried reflashing it with ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF both using RSD lite and manually using mfastboot, but no luck - the phone still boots to 'Erasing...' and sometimes after that to the recovery.
I didn't find anything in relevant threads. Does anyone have an idea?
Selecting 'Factory' in the bootloader seemed to fix it.
It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery
mokagi said:
It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery
Click to expand...
Click to collapse
Were you able to get this resolved? I have a xt1095 doing the same thing when I flash a stock recovery. Just shows the android guy and just stuck at erasing... When I flash TWRP it doesn't get stuck at the "erasing..." anymore but just boots straight into TWRP.
Sorry for the late response, I missed the notification on your message.
I wasn't able to fix it, returned it to motorola.
I believe when you update your phone to android 5.0 OTA the boot loader is also upgraded(I did this). I eventually ended up with no OS on my phone messing around with flashing things causing me to not be able to boot up. I was eventually able get stock OS back on but I still get stuck at the Motorola logo. I tried restoring my it in recovery mode and RSD lite. Is this because my boot loader version is to high for stock OS? I really am clueless on how I could fix this problem. Any help would be greatly appreciated.