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

Honney Villan

I'm using honey villan which has supper user built in. The problem is quick boot and quick boot plus always get denied. I uninstalled booth and reinstalled and get the same problem. It did work, maybe cause super user is bata.. Any ideas

Try running iconiaroot.apk. even though it already rooted, it should replace root access with it's own version.
Sent from my A500 using Tapatalk

hope to try!

I had this same problem with hv, i would reroot, re flash a fresh install, it would be good for awhile then super user would force close and deny everything. I went to taboonay and havent looked back.
Sent from my A500 using XDA Premium App

Never thought of that one, will def give it a try.
After testing for a day, the problem is cwm. On fresh install of rom, su works fine, but do a full backup and then restore your backup and you will have no working superuser.

Been checking out taboonay and will give it a try next.

Euclid's Brother said:
Try running iconiaroot.apk. even though it already rooted, it should replace root access with it's own version.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Just tried it and it worked fine, now I can use my backups. Thanks a million. I thought because su was the problem, but I guess it can't run if you loose root for some strange reason. It still breaks using cwm restore. Later on

Hi! I have a problem with audio on HoneyVillain 1.1 with two last kernels (3.2 и 3.3). When I insert the headphone jack into a tablet, a sound through external speakers does not stop

I believe your problem is not just with your rom. I have read others with different rom's having the same problem. I have hv 105a and it's kernal and not hit the problem yet, but I know it's there cause it did it a few times running stock. Just a software glitch. Just remember its a computer.

Odin'd to stock, trying to root, su broken?

So i just odin'd from miui to stock, went to root, everything went fine. except that it kinda didnt. now, whenever i try to use an app that requires root (rom manager, root explorer, etc) it crashes. Superuser does it too.
is there something i'm missing? i've odind many many times, with no problems whatsoever. this time tho, nothing root related works. i've tried re-odining, rerooting, with different files that i've had on my computer for ages, with new ones just downloaded, with AIO. all to no avail.
any ideas?

I've noticed that Superuser has had some updates lately that could be the issue.
Sent from my SGH-T959 using XDA App

did you reboot the phone right after rooting?

Could you try using my noob guide and my update.zip files.... I prefer B as it is the fastest method. The ROM will give you root access.

Or get old school oneclicklagfix 2.3, I use it every time now. Root zip built in.
Sent from my SGH-T959 using XDA App

I recommend going back and using the noob guide option recommended above. It has also worked perfectly for me.
Sent from my T959 using XDA App

[Q] jwr66y- few apps immediatly crash

Hey, I've done a full wipe as well as return to stock, then proceed to install jwr66y from scratch, after installing i proceeded installing twrp and superuser, everything seems to run fine with root and all. The only thing which has been bothering me is that some apps are displaying force close error immediatly after starting them. Examples are Adaway, Adfree and Yelp.
Anyone knows what's going on there?

Same thing with me, some apps just crash immediately. I'm glad I made a backup before I installed. I installed the ota through a zip to preserve root/custom recovery and also just installing it normally. Same thing happens with crashes.
Sent from my Nexus 4 using Tapatalk 4

CCDillon said:
Same thing with me, some apps just crash immediately. I'm glad I made a backup before I installed. I installed the ota through a zip to preserve root/custom recovery and also just installing it normally. Same thing happens with crashes.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Yeah i also installed though a Zip which was supposed to be vanilla with added busybox and root.
I had my nexus 7 running so i was backing up from there which fixed the problem. However i am really wondering why apps which were downloaded straight from google play messed around.
I hope they won't mess around later.

I was completely stock and the same thing happened to me. I had to erase recovery, data and boot loader through fastboot and then reinstall everything new from the factory image on Google's site.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Oh wow. I had to do that with the initial 4.3 release. Don't think I'll do it for such a minor update unless I have a lot of free time. Though, the software update notification is in the way most of the time.. In surprised this isn't affecting more devices.
Sent from my Nexus 4 using Tapatalk 4

4.3 fails during install

Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk

ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
If I were you I would go back and read a little information about mf3 and what kind of recovery can be used. It sounds to me like you might be very confused. In order to correctly keep from bricking your phone you may want to read up on things. Good luck.

ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Since you are rooted, take a look in the /cache/recovery directory. Read the log file. It will tell you where things messed up.
For example, I had forgotten that I did something with csc and had replaced the feature.xml file. Luckily, I had a back up of the original file. I renamed it, fixed is file permissions to rw-r--r--, advanced my clock one day, and then was able to install MJ9.
Good luck, and remember you won't have root anymore when you install this (for the time being)
Yrs,
dkephart
Sent from my SAMSUNG-SGH-I337 using Tapatalk

ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems

To able to keep your root and upgrade from 4.2.2 to 4.3 you have to change your param file back to the stock. Thats all the information that I have so far so... not completely sure. But I think that is what you're supposed to do.
Because you have a custom param file, when you try to upgrade to 4.3 it's telling you there is an issue with your phone.
I may be wrong.

Is there a copy of the correct feature.xml? Im having the same issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

According to the log its stopping when it can't find the chat on apk. I did remove it using titanium.
Will restore it try again andbipdate the thread. Thanks for pointing out the correct log file to look at.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

I checked again and found my backup feature.xml. Typed this from mj9.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem happen to me on Wednesday night and last night. Today I used Odin to go back to stock MF3, however, then I couldn't get the OTA update. It kept saying my firmware was up to date each of the three times I restored it.
Now I'm finally on MJ9 after copying "update-mf3-mj9.zip" to my SD card, going into recovery mode, and updating from external SD card. Now I can use my Galaxy Gear!

Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk

jball said:
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
I was excited when I rooted the phone, then installed ROM manager premium. It allowed me to install the recovery. You can even boot into the recovery from ROM Manager.
However since the S4 is locked down tight, you can do any thing from there. So i can't flash anything. It even gives me a message saying as much.
However it is partially installed I can boot into it at will.
I will post a video of it. So that you all have an idea of what im talking about.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk

jball said:
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers

ckalantzis said:
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
Click to expand...
Click to collapse
You handled this all very well.

ITNV said:
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
Click to expand...
Click to collapse
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went ahead and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.

erasat said:
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)

ITNV said:
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
Click to expand...
Click to collapse
Yep, that was the reason why I just used the PDA I didn't want to lose my data, and then I did it anyways, my mistake was not doing the Odin Restore just after I realized that it erased everything and I was still at 4.2.2, that's was the perfect time to do it, but now, after I finally put everything back as it was, I simply don't see myself by my own choice, doing all this again.
Thanks.

erasat said:
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went a head and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.

scott14719 said:
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
Click to expand...
Click to collapse
In the thread, there are tons of instances where it explains where to use each file and even pictures, I know because I read every single post, but none of them explains if I could use just the PDA one if I wanted to keep my settings while unrooting the phone, that's why I asked about it, because nobody replied to my question I decided to be the guinea pig, and yes, it works, you keep your settings, and I was glad, but as you can see, what I wanted to accomplish didn't work after all. Without all the files it doesn't fix the issue that causes the error 7 when doing the sideload.

help with mf3 to mj9
Having the same issue and formatted card with backup image.
Update got to 23 % and failed
now phone refuses to flash in odin.....and im missing factory apps preventing me from doing anything to get it back to stock
anyone have a stock restore image I could use in kies?
Would that work properly?