Database Develop

[Q] New update fails

Hopefully you guys know there is a software fix out from at&t and samsung that fixes gps problems and etc...
goes without saying you can't just straight update if you're rooted. That's where i'm stuck.
Before i touched anything, it would get to 50% and reboot, says the update was not applied.
Then I tried "unrooting" even though it said it was unrooted, and apps requiring SU backed this up saying my phone was unrooted.
Then during the update, it stops even sooner at "preparing".
So... how do we get around this without doing the master clear with odin3???
I DON'T want to lose all my data. I'm too lazy.

Mine said failed at 100%. I def got the jh7 update though. My phone was unable to reboot into recovery using the three button method. Now I can. My phone was rooted with stock rom.

Mine is rooted with the Voodoo fix and it failed during the update (I was at work so don't know at what step during the update).
Will have to do the voodoo-lag unfix - restore back to factory defaults and try it again..
Unless of course someone pops out a tweaked ROM before then!

check out this thread, http://forum.xda-developers.com/showthread.php?t=789546 so we can get everyone with this issue together in one thread

captivate jh7 upgrade

Got the firmware today.. when it loaded it ran the entire progress bar and later said that it failed.. however in the settings it say jh7 and additional attempts to update says no updates available. Also.. after the update the superuser app is still installed and appears that root is still there. Any thoughts?
Sent from my SAMSUNG-SGH-I897 using XDA App

trumsey2005 said:
Got the firmware today.. when it loaded it ran the entire progress bar and later said that it failed.. however in the settings it say jh7 and additional attempts to update says no updates available. Also.. after the update the superuser app is still installed and appears that root is still there. Any thoughts?
Sent from my SAMSUNG-SGH-I897 using XDA App[/QUOTE
I take it back.. after changing clock and checking again the update is available again...
Click to expand...
Click to collapse

You have to unroot before you can do a ota upgrade. Rooting is suppose to block ota upgrades because a ota upgrade would remove superuser.

I read somewhere that people have had to flash back to complete original. I've rooted and removed AT&T crapware. Also, being new to the Android platform I need some guidance on how to go back to factory orig. I've heard of odin.. but base on my limited research I haven't seen if it is available to mac. I am familiar with Unix/Linux.. they are my primary OS'.. but messing with a phone OS is just a different animal altogether.

I had to redo the phone but the update never showed up.. So what I did was just flash the update from samfirmware and it is working even though I have to redo everything...
HTH,
Charlie

evil5826 said:
You have to unroot before you can do a ota upgrade. Rooting is suppose to block ota upgrades because a ota upgrade would remove superuser.
Click to expand...
Click to collapse
My phone is rooted and I updated without issue.

Well i just tred to update mine this morning, i finally got past the communication errors. The download went fine, but when it was installing it went from 0 to 50% percent in about a second and then said update failed and rebooted.
I'm on the stock JF6 rom, however i used odin to get there.
My Sim card and sd were left in, however my sd is blank
And i don't know what any other info i can post to be helpful

2.1 update
just did the update with one click root loaded.went though with no problems phone is faster with less lag.also i can still use as wi fi hot spot. new Quikoffice,Media hub,Mobile Video and you tube. well this may mean no 2.2?

I also did the ota update with root installed, allowed 3rd apps, with wireless tethering, and it went through fine for me but I still have poor gps, did not seem to do anything for the gps except removed the option to enter lbs test mode. Anyone know how to get to the lbs test mode after update?

Samsung Mini-Kies Updater

If anyone is having troubles with Mini Kies (I had the problem where the application crashed, using Win 7 x64), I'd recommend using the regular Samsung Kies application. I was unable to do the JH7 update even after restoring to complete stock with Odin (50% update failed error). This was easy, and now I am fully in JH7, and so far the GPS lock is much, much faster.

Flashing nightmares

So I've been a bit frustrated, struggling with this for 2 days now.
I was running 893 and eclispe 2.0 I wanted to go to 2.1RC but I needed to be on 901. So I decided lets do the RELEASED update thing. Well it did get me back to 886 (with no signal probably because of a radio firmware mismatch) But when it tries do 893 it gets that assert failed thing half way through. So I tried the safepath, same problem trying to get to 893.
I seem to be able to root and and forever root it just fine so I tried doing the updates OTA but they would just reboot half way through the update (probably the same error) and say failed.
Tried to manually load the zip files then use the stock and boostsrapper recovery to install them and I get the same failed assert error
So then I tried RSDlight and this file
targa_cdma_targa-user-2.3.4-5.5.1_84_DBN-55-110814-Verizon-US.tar
But it fails at 1/15 doesn't go anywhere from there.
I'm not sure what else to try or do, I did have a boot loop of that fastboot flashfailed this but the FixCDT seems to take care of that whenever that happens.
So at least I'm able to get root but for the life of me I can't find anyway to get any upgrade to work on this, I've been fallowing tutorials all day trying to find something to get it to work.
If you guys have any ideas I'm open to try them, if you want any specific error messages let me know and i'll go and replicate them (I've tried this tutorials and 2 different computers 2 times)
Thanks for the help

to anyone else having these problems, few days of hardcore trial and error
http://rootzwiki.com/topic/13485-unbrick-your-bionic-here/
downloaded the flash me, ran the xml through rsdlite and bam, got back on the 886 with a working radio, gonna try to root, 4eva root, update to 901 then bootstrap then eclispe 2.1RC this baby

Ok Path Saver worked, no fails, when it told me I had to manually go in and update 893 and without rebooting i ran the 901 update as well, rebooted, installed bootstrapper for bionic (still had root) did a wipe, installed eclipse 2.1RC, booted fine, got 4g in a few seconds.
happy I can get back my GPS Navigation so I can find my way around
If anyone wants the files I used just PM me and I'll find a way to ship them over but there should be mirrors all over the place

5.9.905 - Just got prompted to Download and Install

I was on stock, rooted 5.9.902 and was just prompted to Download and Install 5.9.905 OTA. I backed up root with Voodoo OTA Root Keeper, temp unrooted, downloaded and installed 5.9.905, let the phone reboot, then restored root using Voodoo OTA Root Keeper. All went smooth and am now on the official OTA with root. I noticed the addition of Google+ as a preinstalled app. I am assuming, however, that there is no difference between the 5.9.905 that was pulled from Motorola's servers a few weeks back.

Thanks I was wondering what I should do about the root. Went back to unsafe mode, unrooted with backup thanks to rootkeeper, and now I'm waiting for the update! Cheers.

You will need to remove safestrap and may even have to FXZ or fastboot your preinstall partition before the OTA will succeed.

that's what i was afraid of... can i just download the update and do it myself with safestrap installed? I'm not the complete expert so step by step instructions would be appreciated.

I will wait for the OTA notice. if I have to reroot and reeinstall Safestrap I will.

cellzealot said:
You will need to remove safestrap and may even have to FXZ or fastboot your preinstall partition before the OTA will succeed.
Click to expand...
Click to collapse
OHbenhamean said:
that's what i was afraid of... can i just download the update and do it myself with safestrap installed? I'm not the complete expert so step by step instructions would be appreciated.
Click to expand...
Click to collapse
You don't have to remove Safestrap, or un-root as long as you haven't removed any bloatware apps. They can be frozen in TB and it will install. You will lose root, I used Motofail to re-root, then you will have to rerun the install for safestrap recovery. 15 minutes and your good to go.

Agreed. I just removed safe strap, didn't bother to unroot. Tried to force the update repeatedly with no luck. So i took it from the Phandroid news link. Flashed in stock recovery. Kept root (used for3ver root to root I months and months ago). Reinstalled safe strap, then switched back to my safe side which was DroidTheory's ICS, but now with a better radio now. Radio synced immediately...whereas normally it takes a minute or two. Loving this update.
--Sent from GlaDos baked potato

hey just fyi if you flashed it back to 902 stock and took the update you can use the 902 one click root to reroot, i just tried it

Still rooted
I just let the 5.9.905 ota run this morning on my rooted Bionic. No unroot, no backup, or nuthin. I know, not the wisest thing to do but hey, I was caffeine deficient and spoiling for a fight Anyway after the reboot:
Root check shows it's still rooted.
Opened a shell on the handset with Terminal Explorer and successfully su.
Opened an adb shell and successfully su.
I haven't had a chance to explore what's changed yet, but I did notice that Google+ is no longer un-installable.
I might be the exception, but it appears that the ota doesn't affect root on a previously rooted handset. All seems good in my little piece of the world.

Every time I try to update, it says I need a valid Motorola account. I'm on stock, but have done many customizations to it, along with the webtop. I know how to get back to plain stock, just haven't felt like doing it yet. I suppose at some point I will have to when we finally get ICS.
the funny part is that I never had any issues with my data connection until 905 came around, but I have been having them for the past 2 weeks or so.
Sent from my DROID BIONIC using XDA

Non-rooted Bionic constantly trying to download 5.9.905
The past few days my Bionic has been constantly trying to download an update. I came online to investigate the reason and found that 5.9.905 just got released. The download symbol has been in the notification bar all day for the last few days and the battery is always dead when I wake up.
I have looked online to try to update manually but all the filenames of the 5.9.905 download links are actually labeled Blur_Version.5.9.902.XT875.Verizon.en.US.zip. Link this one here at xda: http://forum.xda-developers.com/showthread.php?t=1297714&page=40. Anyone have any suggestions? Thanks.

The filename is in regards to the version over which it can install.
You just have to download one from may or later, I believe. Pick a page that says it's the 905 update, download the zip file with 902 in the name, put it on your external sd card, and reboot into stock recovery (I use adb reboot recovery), press both volume buttons in, then "install zip from sdcard" use power button to select. go down to the zip file we just put on the sdcard, hit the power button and BING BANG BOOM 905!

Re: Non-rooted Bionic constantly trying to download 5.9.905
Thanks, 5thAgent. I'll give it a try.

January ota update help needed

OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.

My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?

I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.

Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?

If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.

Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img

You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.