Database Users

Fascinate OTA update underway

I just did a check for updates on my Fascinate, and it pulled down a 697KB update, SCH-I500_DH12_to_DI01. Not sure what it changes, etc.

I was able to download it, but I can't get it to install. It keeps failing. Do I have to unroot to install?
Sent from my SCH-I500 using XDA App

Not sure. Some guys in #samsung-fascinate on irc.freenode.net are going to mess around with it.

I got it. I think it installed correctly. Baseband ends in DI01 now.
Sent from my SCH-I500 using XDA App

did you lose root?

got mine really don't notice a difference..anyone else?
Sent from my SCH-I500 using XDA App & yes I'm a chick.

Just tried to trigger the update - got a Server Unavailable message. Guess they took it down??

Mine failed. Says IP previous update failed now.

the is a list of changes in one of the threads in dev section.
you have to have a stock /system to be able to apply so if you removed any bloat must put back or flash with odin
Ota will cause root lose but we have a flashable zip with root if you got clockwork running
Sent from my Clockwork Fascinate using XDA App

orateam said:
Mine failed. Says IP previous update failed now.
Click to expand...
Click to collapse
Same issue here

Mine failed as well with the following error code: "UPDATE FAILED or INCOMPLETE. reason: IP_PREVIOUS_UPDATE_FAILED."
I wasn't rooted, but I do have third party software installed. Any ideas why I can't get the update to stick?

I tried the update on my non rooted phone. I mean i've never even done anything extra to it, and i still got the update failed reason: IP_PREVIOUS_UPDATE_FAILED
I'm thinking there must be something wrong with the update.

I'm having the same issue with "IP_PREVIOUS_UPDATE_FAILED".
I was rooted+lagfixed but went back to stock using the ODin restores, still getting the above. I've tried it with and w/o CWM enabled as well.
*EDIT*: I just want to note that the phone attempts to reboot and install the update, and I can see (VERY briefly) the recovery manager attempting to apply the update. In this, I was able to see 'signature verification failed' amongst the normal messages.

Hmm, if you're running the stock recovery, and stock everything else, and you see a "signature verification failed" error, then the downloaded patch must be corrupt. I'm guessing you might need to delete the downloaded files and force it to redownload the patch, but I have no idea how to do that.
On a side note, I just applied the official patch to my rooted and lag-fixed Fascinate yesterday, by temporarily reverting to stock, and re-rooting afterward. I posted the steps I took to do this over in the development forum, for those that are interested: http://forum.xda-developers.com/showthread.php?t=792652

I called verizon and talked to tech support about the IP_PREVIOUS_UPDATE_FAILED problem, he didn't have a fix. So he said i can take my phone back to the store and have it replaced with a new one.

Anyone know where I can find the bloatware apk files? I got a little trigger happy and deleted them instead of renaming. I can't install the update until I replace them.

Any help with this...
I was rooted with lag fix and OTA installed unannounced. So I lost root as expected. Meanwhile, seems I have the update but each reboot brings the update screen back, over and over again. Baseband and build number are updated. I have rerooted, un-lag fixed. Trying to get this update to stop showing up because its KILLING my battery. Thanks for any help.
BUMPED

Hizenthorn said:
Anyone know where I can find the bloatware apk files? I got a little trigger happy and deleted them instead of renaming. I can't install the update until I replace them.
Click to expand...
Click to collapse
This link has been posted multiple times. Please search. http://forum.xda-developers.com/showthread.php?p=8450686

If your Fascinate (unrooted, cannot speak to rooted phones) will not take the update, AFAIK your only option seems to be the 30 day return policy at Verizon. Last week after over two hours in the store they finally swapped, but even that phone would not take the update. I went in today, got a new phone, and it took the DI01 update. Third times the charm.

Its updated for sure and currently rooted. When the phone reboots it says installation starts in "x" and counts down. I have to defer for 24 hrs to keep from irritating me. I may try the store for an exchange.
Sent from my SCH-I500 using XDA App

[Q] Anyone else with the DI18?

Hey everyone.
I was waiting for the update, but I did not think it was going to happen today. Anyway, I got it while I was at the mall, so I clicked yes for the system update. My epic restarted and everything and did the whole downloading phase. Then when it was about to finish, it says "An error occurred while trying to update your firmware. Please try again later." I was a little disappointed by this. so I waited....and waited...then I checked my about phone settings and it says that I have the DI18 in the baseband ver. but it says update 1 in the firmware. Could anyone else tell me what I should do?

ya you should update manually

I tried to update from the system update menu, but it still came up with the error. Any idea how I can update manually unrooted?

I manually updated and under Firmware version it still says 2.1-update1
But if you got an error message of some kind I don't think it would hurt to manually reinstall the update.

akei1 said:
I manually updated and under Firmware version it still says 2.1-update1
But if you got an error message of some kind I don't think it would hurt to manually reinstall the update.
Click to expand...
Click to collapse
Since it already says DI18 in baseband version and build number,
Would placing the update manually into the root of my SD card have any negative effects?

garreto said:
Since it already says DI18 in baseband version and build number,
Would placing the update manually into the root of my SD card have any negative effects?
Click to expand...
Click to collapse
It's the same update so it should be ok. Just dive right in and we'll work out any problems lol

ah wait. Never mind, I'm not rooted.

I've read someone got the update without having to root. They downloaded the update file, copied to sdcard root, renamed the file to update.zip, booted into samsung recovery, and applied update.zip
The thread name is DI18 update for Stock Roms Only in the Epic 4G Android Development section
http://forum.xda-developers.com/showthread.php?t=796885&page=14

Yeah this can be done with the signed file that was floating around from one of Firon's threads. You don't need to be rooted to flash that one
Sent from my SPH-D700 using XDA App

Was pushed to me OTA at around 9PM yesterday.

So after update installed and reboot, I get "checking for software update" and it's just staying there with the circling ring. Is this normal?

garreto said:
So after update installed and reboot, I get "checking for software update" and it's just staying there with the circling ring. Is this normal?
Click to expand...
Click to collapse
It should do so for about 30 seconds or less to confirm that the update is installed (really just tell you that there are no new updates.) If it still hangs, reboot.
Sent from my SPH-D700 using XDA App

So after I finished updating, once it finished booting up the phone said "there are no current updates, your software is up to date". Is this what's supposed to happen?
Sent from my SPH-D700 using XDA App

Firmware will show 2.1 update1
Build number will show sph-d700 Eclair D18
This is where the updates show, look there on About Phone

You need to boot in recovery mode and have the file named update.zip on ur sd, clear cache in recovery and then update while still in recovery. The rest does itself.
Different steps for rooted users.
Setting->about phone...to see if the update is there
Sent from my SPD700 using XDA App

ROM Manager Fix Permissions Blank Screen [solved]

Running ROM Manager Premium v4.7.0.5 with ClockworkMod 3.0.0.8 (newer versions did not flash ROMs properly) on Cyanogenmod 7.1 with SuperUser 3.0.6 (su binary 3.0.2).
When I try to run Fix Permissions from ROM Manager, it asks me to confirm as normal. When I confirm, it just sits there in the Fix Permissions window where the log output would usually appear. I've let it go for several minutes and nothing ever seems to show up. It should be noted that ROM Manager never requests root permissions for this either.
Am I not waiting long enough, or has anyone seen this issue before?
Edit: I also posted this to reddit under Android (can't link because I don't have enough posts).

Are you running the latest su? I had an issue with the latest version and had to uninstall updates to get it to work, once I did that it let me flash the latest CWM and fix permissions
Sent from my ADR6300 using XDA App

I was running the latest version of Superuser and su. I uninstalled updates to Superuser, but that only brings it down to 3.0.4, and the same problem results.
Edit: It would appear this is deeper than just ROM manager, and that SuperUser is the culprit. I just tried updating the su binary, and it's stuck at "Gaining root access." Always exciting when Superuser can't give itself root rights...
This is affecting everything requiring root permissions. The programs just hang because the root prompt never shows up. Not really sure what would've caused this. Must be an su/Superuser update. I can't flash from ROM manager because Superuser is broken. Is there any place to install an older Superuser APK?

Did you downgrade in the market? That just put me back to version 2.3.6.3 which shouldn't give you problems, and I'm pretty sure there's a way to install it with adb but I'm not sure how, you could always install a new ROM with CWM.
Sent from my ADR6300 using XDA App

I also just noticed your binary is outdated... Try updating that and c if it fixes anything, the latest version of su with the latest binary are actually working for me but, the previous version didn't .
Sent from my ADR6300 using XDA App

The SuperUser update screwed me.
I had to reflash the older 2.3.5.3 version.
If you look at his website there's a way to download the older versions. Flash it like you would a rom. Solved my problems. I'm not upgrading until I know it works for Incredible phones.
I can't seem to find where I got mine from but here's a link to another place that has it.
http://rootzwiki.com/topic/194-superuser-2363-17-june-2011/

gadzooks64 said:
The SuperUser update screwed me.
I had to reflash the older 2.3.5.3 version.
If you look at his website there's a way to download the older versions. Flash it like you would a rom. Solved my problems. I'm not upgrading until I know it works for Incredible phones.
I can't seem to find where I got mine from but here's a link to another place that has it.
Click to expand...
Click to collapse
That fixed it, thanks. Now running Superuser 3.0.6/su 2.3.5.3 and things requiring root permission are actually asking for them again.

Why not just "Fix Permissions" straight through the recovery?

I'm not rooted and I keep getting Custom Status...why?

I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!

polish_pat said:
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
Click to expand...
Click to collapse
It's really not as big of a deal as you are making it. The way I see it you have 2 choices.
1. Exchange the phone for another (that might do the same thing)
2. Ignore it.
Just like every other Galaxy phone out there (you remember the skyrockets, right?) not all of them react the same way. Some get custom, some do not. Others switch back and forth.
I've noticed you have made many posts about this same thing. If someone hasn't provided a concrete answer that has worked for you by now it just doesn't exist yet. No matter how frustrated you are over it, making new posts about it are not going to change anything.
Its up to you if you keep wanting to post about it (I'm not complaining about it), I just don't think it's going to get you any more information at this point than what already has been said. Maybe I am wrong and someone will tell you exactly what to do to make it "official", but I haven't seen anything yet.
Good luck and try not to let it get to you so much.

euhhh no, they are not about the same thing, one was about retaining officiel while rooted, and now that i've given up on that, i still have a custom status, the reson why i dont report there is becuase poeple have seen the thread and will not go back, so in order to attract new poster i create a new thread. And no, i dont want to ignore anything because i want OTAs. If you have a problem with that, dont answer

You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2

peoples_flip said:
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...

I went through what you have, I completed a full stock restore via Odin and these two files I mentioned were still there. Use a file explorer and go to the path I suggested and you'll see them there
Sent from my SGH-I337M using Tapatalk 2

polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
I don't believe the current Odin contains a pit...or whatever it is that formats the phone...
So all Odin is going to do is reinstall everything...so replace missing or corrupted files - it will not delete your new files
Formating from the phone itself won't delete everything...its just going to delete your apps, app data, and cache
Therefore doing multiple factory resets and odins likely will not remove all traces of root...someone correct me if I'm wrong but that's what I believe is the case...
Sent from my HTC PH39100 using Tapatalk 2

Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium

XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
AT&T software update push or download will not work for your phone if it is showing custom. People like to be getting these stock updates as soon as they are published by the provider, not when some good heart packages a new ROM using them.

polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Thanks.

TheAxman said:
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Click to expand...
Click to collapse
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.

CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Same here

CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Correct. the one from the playstore updates the binaries. then uninstall.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Good answer, why does it matter if it says custom? whats the big deal here. If you are wanting the update, why not just wait until a dev does what they need to do to it, and flash it later. I updated 1 time in a year on my GS3, and never did it again. When a new rom is developed, it usually is a base from the update...so....

Had a posting. Could not delete
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
Mr. Q said:
Well, you do not have to install the ZIP, but instead, do the following:
- Install SuperSU from the market
- Grant SuperSU root access
- When asked to update su-binary, please do
- Remove SuperUser from your device
- Reboot (I read two reboots are needed to make the icon disappear again.)
Click to expand...
Click to collapse
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.

CAG-man said:
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
Click to expand...
Click to collapse
I was able to get official and root, the problem is it comes back after 2-3 days, please report back on sturday and tell me if its still official, also this logo you are talking about, i never see it because im in canada and my bootloader is unlocked already
EDIT: Ok, so once i was rooted and installed SuperSU and got superuser out, i deleted busybox, i then rebooted ONCE and got official just like that. I also took out SD card because i know this screwed me up last time. I'm happy because i'm rooted and official, but i'm not convinced this will last very long because it has never lasted more than 2 days. I will report back in a few days. Thanks Cagman, you've been very helpful and what you told me to do did the best results for me, i just hope they last

so far so good!!!:fingers-crossed:

polish_pat said:
so far so good!!!:fingers-crossed:
Click to expand...
Click to collapse
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...

joeybear23 said:
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
Click to expand...
Click to collapse
Hahaha, i did it!! earlier this afternoon i sort of challenged my phone by rebooting it constantly, ive rebboted probbaly 20-30 times and its still official, i guess deleting busybox sealed the deal!!

Polish_pat I am glad I was able to help. You are welcome. Congratulations.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Stopping the update on vzw note 3

Is there an app I can freeze or remove that will stop the device from trying to automatically doing the update?
Sent from my SM-N900V using xda app-developers app

Unless you're rooted, no. If you are, then use Titanium backup to freeze the SDM app. That'll stop the update and get rid of the notification at the top.
Sent from my SM-N900V using XDA Premium 4 mobile app

Thanks for the tip, app frozen.
Sent from my SM-N900V using xda app-developers app

Too late to root?
I've got the OTA update and have not applied it. I keep dismissing the notice to apply the update.
I'm not rooted. I haven't rebooted since the OTA downloaded. I'm not sure it it will apply once I reboot.
Is it too late to root?
This is N900V.07 with JSS15J.N900VRUBMJE.

To Late To Root?
tward800 said:
I've got the OTA update and have not applied it. I keep dismissing the notice to apply the update.
I'm not rooted. I haven't rebooted since the OTA downloaded. I'm not sure it it will apply once I reboot.
Is it too late to root?
This is N900V.07 with JSS15J.N900VRUBMJE.
Click to expand...
Click to collapse
I went through the same thing on the Verizon Note 3. I wasn't planning on rooting this phone for awhile. When I first got the
update notice I hit cancel and it told me that I wouldn't be asked again and I would have to go to About Phone and hit
Check For Software Update. Figured I was ok with that until the next morning when it seemed to have already downloaded
and was asking to install. I would hit cancel and a clock which I could set a time to install showed up.
I just hit the back button and it would go back to my home screen. Only problem was the install notice kept popping up every
45 secs or so. Knew then it was time to root. I was sure I would hit that software install button by mistake because it's
right over the back button.
Tried rooting with Kingo but couldn't get it to work so went with Vroot and it rooted in a couple of minutes. Got rid of the Superuser
app Vroot installed and installed SuperSU then installed Safestrap. TB was the next app and I froze SDM 1.0 Haven't seen that damn update notification since. Hope this all helps. I was feeling pretty lost for awhile and almost gave up and hit update. SURE GLAD I DIDN'T
Looking to update to KK firmware and rock the KK Hyperdrive Rom pretty soon. No hurry though. I'm rooted and no update
trying to shove itself down my throat. Good Luck!