Bionic Wont Update to 893 - Motorola Droid Bionic

ok so i have the current version 5.5.886 rooted and all when i try to install the the 5.5.893 update the phone beings the update process but it stops halfway the installation and i get the Triangle ans it stops the attempt

is your bionic fully stock? if so try this. grab the update from here and stick it on your sd-ext, enter stock recovery and install from their. if that doesnt work try the pathsaver method. if that doesnt work their are some threeds with other methods as well. if you have froze or deleeted any apps it will not install. you also cannot be on a custom rom. good luck

Related

I screwed something up.

I was rooted and running CM6. I tried getting back to a stock 2.2 by flashing the stock image from Rom Manager. I downloaded the 2.2 update from google and it wouldn't update. In the system menu or bootloader I got a little format happy with boot/system and so on. Anyway, doing a nandroid now. Is there anyway to get this phone back to the kernel it shipped with?
You have to flash it with the stock recovery.
I've been using that Universal androot.http://www.androidappjudge.com/2010/08/one-click-root-application-universal_10.html I tried flashing stock 2.2 and I didn't read the two options, I just clicked them and kept going not realizing that I flashed the rooted, superuser version. Does this mean that I'm now rooted forever? When I try flashing stock 2.2 with rom manager It stops @ the android and /!\ symbol. Now it's even doing this with CM.
I'm now wondering how to get rid of whatever crap might be floating around on my phone and why it may not be flashing anymore?
there is nothing wrong, rooting allows you the ability to have super administrative rights. Since all you have done is grant yourself admin rights, the recovery should be the same.
Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.
glwinkler said:
Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.
Click to expand...
Click to collapse
Did you wipe? I used 1-click root and I hadn't flashed anything in over a year so I forgot to wipe and I boot looped until I pulled the battery, booted into recovery and wiped. Simple solution but it could be worth mentioning...
So you are saying that, you have the stock recovery now? Triangle with little android? If so, Just download a PASSIMG.zip and flash through bootloader. This will take you to stock.
I have an N1 with locked bootloader and when I wanted to go back to stock(Forgot to get a nandroid of unroot rom). I had to flash a stock recovery. then downloaded the PASSIMG.zip from here http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91+downgrade
This takes me back to ERE76. Then I download an OTA of FRF85B.
I think fix permissions fixed everything. Thanks for the tips!
THIS HELPED TOO:
http://forum.xda-developers.com/showthread.php?t=619153

Unable to get Clockworkmod working

Two days ago I updated my phone to the newest CM7 nightly and all was going well. The next morning I kept getting a bunch of force closes so I decided to reboot and go back to my previous save state. When i tried to restore i keep getting errors of it being unable to mount anything and it ends up ending the operation without doing anything. I was unable to do wipe anything since I kept getting unable to mount errors.
So I decided to wipe my phone and I went to http://androidforums.com/fascinate-support-troubleshooting/322208-fixed-how-get-froyo-if-your-ota-failing.html and followed the instructions. I did all of the Verizon updates until I was running 2.2.2.
After my phone finished installing all of the updates from Verizon I went to http://wiki.cyanogenmod.com/wiki/Samsung_Fascinate:_Rooting and followed those instructions for rooting. After I finished I installed Rom Manager and flashed Clockworkmod. However whenever I reboot I get sent to Samsung's recovery manager and not Clockworkmod.
I posted this question over on reddit http://www.reddit.com/r/AndroidQuestions/comments/m0dcs/unable_to_restore_backup_on_clockworkmod/ and was told to try the guide in http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000/. According to the site my kernel won't allow those types of installations so I need to change my kernel. I went to the site that was linked http://forum.xda-developers.com/showthread.php?t=788108 but I had no idea which kernel to download. I tried downloading one of them but then my phone wouldn't start so I had to start all over again and do the same thing I did here.
I have no idea which kernel to use so I'm hoping someone here will help me out.
Tldr; Running touchwiz but the kernel won't allow me to install Clockworkmod.

[Q] Update to .894 failed, flash back to .893 failed

I went back to stock and tried to update to 894 and it said update failed. I also tried to flash back to 893 via stock recovery and it fails now. What happend?
The flash back to stock should also have failed if you were already on 5.7.893, b/c the kernel is updated in that build and you cannot revert the kernel yet.
antonioj78 said:
I went back to stock and tried to update to 894 and it said update failed. I also tried to flash back to 893 via stock recovery and it fails now. What happend?
Click to expand...
Click to collapse
Once you have a leaked update installed and flash back to stock you then have a mismatched situation. You still have the updated kernel and baseband with the stock .886 system. That is why updates now fail. You will stay that way until the official 5.8.894 is pushed to everyone's phone. That will happen right before the ICS push (well, that's what I've been reading lately anyway, but who knows??).
Good luck.
thanks for the info. i thought it could be that but i wasnt sure.

Issues with Safestrap - How to get phone booting properly?

So I just got this phone, and I've been trying to get it up to ICS. I've gone through and was able to complete the ICS update the first time completely, installed Safestrap, etc. Now this is where the issues came in. I did a backup, and then I started restoring some apps from titanium, from an old phone. This is where I started getting constant force closes. Tried fix permissions, went through again, same issue. So I wiped the phone, and went to restore with safestrap - it failed. Now on bootup, it refuses to even boot into safestrap anymore. All I can get is either a blank screen, or motorola recovery menu. By the fact that I can get into the motorola recovery menu, I presume it's not fully bricked, but I know there can be issues with installing on top of Safestrap.
Long story short, my question: In this condition, will flashing the same file I did during the ICS leak installation through Moto Recovery allow the phone to boot? Or will that cause a brick like downgrading from ICS does?
So, just to be sure, you installed one of the ICS leaks correct? Then you installed safestrap 2.0?
Sent from my Droid 4
Yes, that's exactly what I did. Was able to boot up into Safestrap (2.0) and restore through Safestrap, but after wiping /data I got errors with restoring a backup, and after rebooting to attempt it again, Safestrap splash screen no longer appears for me. It has the initial splash, and where the Safestrap splash should be, it just stays blank screen.
Not sure what would have caused this. I don't think you'll be able to flash the zip again since it looks for a .219 system build. Might be worth a shot though. You could also try booting into recovery and doing a factory reset. If neither of those work, try following the instructions for upgrading from one leak build to another.
Sent from my Droid 4
Tried Factory reset already, and attempted just flashing the update anyways - got an error saying build.prop file was invalid/missing?
Now I'm going through the tool steps to swap between ICS builds. At least I'll hopefully get something working.
Though I did do a step I forgot to mention, if that explains why it happened. After the Safestrap restore failed, I tried to do a partial restore of /system and /data. /system restored fine, when I went to do /data it said it was restoring /system in the log - could that have been an issue? A possible mistake in safestrap that overwrote the wrong folder? Or just an issue with the menu?
Doing the ICS switch got it working for me. Now to attempt round 2 and see if I can get into CM9, and Safestrap works right.
More research, root cause : Forgot to install busy box when doing the initial root.
Glad you got it working!
Sent from my Droid 4

Bootlooping

I tried to update my brothers phone to 4.4 from 12B because he kept saying that it would try to update but would fail which I didn't understand why because he only had root but that's not the problem. I installed TWRP and made a backup right away. I then installed the boot stack from this thread http://forum.xda-developers.com/showthread.php?t=2715408 then rebooted and was bootlooping. So, I put it in recovery mode and think I probably messed something up so I'll just restore the backup I made. I restore it and everything is looking good no errors or anything until I go to reboot it and it's still bootlooping. I'm stuck here because everything I've tried has failed.
I recommend following the restore to stock instructions (the tot method going to 11a then OTA to 12b) in the general section. Then use Cloudy's Malidus 2.0.2 files to update to 4.4.2.
Sent from my VS980 4G using Tapatalk

Categories

Resources