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

I can't update my nexus 7.

My nexus 7 is rooted. Is that why it can't accept the 4.1.2 update? What should I do? It keeps reminding me to install the update every 15 minutes. When I try to, it just crashes.
Sent from my Nexus 7 using xda app-developers app

You want to eat from two tables ... ? It's your choice, original or rooted ...
Sent from my Nexus 7 using xda app-developers app

I'm trying to update it while keeping root. I downloaded ota root keeper. But I keep getting the "dead Android with red exclamation mark" screen every time I try to install the OTA update. I even tried its option to temporarily un-root before performing the update, but no luck. Anyone have any ideas?
Edit - Also I tried installing it manually. Used GooManager to install TWRP and tried installing 4.1.2 through it. Still fails every time. I'm disgusted.
Sent from my Nexus 7 using xda app-developers app

I had my Nexus 7 rooted w/ the "Google Nexus 7 Toolkit" and I was able to update to 4.1.2 w/o any problems.
Sent from my Nexus 7 using xda app-developers app

Having the same issue as well..Can't root.
Sent from my GT-I9100 using xda premium
---------- Post added at 02:41 PM ---------- Previous post was at 02:25 PM ----------
Well after trying again I finally successed doing so.
Sent from my GT-I9100 using xda premium

Backup--unroot--relock--update--unlock--reroot--recover? I'm brand new to this stuff (don't even have a N7 yet), but seems like this would work.

The stock update will only install with stock recovery being root has no effect. If you have changed system apps. Like to the 4.2 apps floating around could stop the update as well. Google does not care another root or unlocked. I would say do factory reset then update then root. Or download one of the stock cwm/twelve roms and be done with it.
Sent from my Nexus 7 using Tapatalk 2

Well it happened again. The 4.2.2 update is out and I can't update to it. Every time I try, I get the dead android error icon.

It sure gets old saying this, but...
The error message is recorded in the recovery log at
/cache/recovery/recovery.log
You will find that the problem has nothing to do with root per se - generally the root user (or apps that were granted root privilege) have altered or deleted something in /system needed for the OTA to correctly complete.
In general, OTAs are not meant for customized ROMs - it is unreasonable for anyone to have an expectation that they will work correctly on a customized ROM.

But I didn't install a customized rom. I just rooted/unlocked it.

You can always download the update from Google's servers and flash it through fastboot. No hassle.

Bryon15 said:
But I didn't install a customized rom. I just rooted/unlocked it.
Click to expand...
Click to collapse
the proof is in the pudding...
...and the pudding is at /cache/recovery/recovery.log
bftb0 said:
generally the root user (or apps that were granted root privilege) have altered or deleted something in /system needed for the OTA to correctly complete.
Click to expand...
Click to collapse
Note that the recovery.log file gets overwritten every time you boot the recovery, so the thing you are trying to retrieve (let's say with the booted OS) will be from the immediately prior use of the recovery. So, attempt the OTA (let it fail), then boot into the OS and capture that file (using something which is root-privileged).

To update... Or not to update... That is the question.

A few days back, my wife got me a shiny new nexus 10. This thing is cool for sure. However the one I'm using now isn't the one from a few days back. It is in fact, a replacement because after I hooked into my WiFi and loaded up the apps I have on my GNex off of Google backup, I got a notification for an android update. So I said "SHURE... I need that stuff" so I pushed the item in the notification and it said "push OK to restart...", so I did.... And it did restart to a DEAD ANDY ICON AND A "NO COMMAND" under him! I did a factory reset three times and never got further than the boot animation. The dude at google play support was a bit flummoxed but beyond a reset... Well... He pronounced it mostly dead. So rather than screw up the warranty, I took it back to where we bought it and got a new one.
So here I am again... I'm at JVP15P... And I've got a pending update downloaded and ready to fry my second N10! I've heard 4.2 has some kind of update issue just like this on the N10.... Is that true? What should I do? If this is true how do I get past this... I sure as s**t don't want to return anther one! Any suggestions are most appreciated.
Sent from my Nexus 10 using xda app-developers app

A short time ago, I was unable to update to 4.2.1 from 4.2, either from the automatic update, or from adb sideload. This was because I was using some older factory image (not sure what was wrong with it), but after downloading the latest factory image from Google and flashing it, I was then able to update without any issue

I finally did my updates.
Thankfully all went smooth. Although, my N10 ran as cool as ice before the updates. I could play games for a long time and it would barely get warm. Now it seems to run extremely warm. I wouldn't say hot, but it is noticeably a lot warmer and that is doing nothing but surfing the web.
Not sure what was in that first update, but it changed the way it runs. No other issues though.

What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app

I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.

alias_neo said:
I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.
Click to expand...
Click to collapse
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app

Doctor Dedroid said:
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It's a boot-loop, technically, but now I'm just being a pedant
I'm not too sure about the toolkits because I don't use them, but yes, you have to unlock to flash stock images.
Easiest way it do download the zip from the dev site, unlock manually, then just double click the flash-all script, that will take care of the rest, then just relock after and happy days.
I know it's a bit nerve racking when it won't boot, but that will get you out of most sticky situations, in the case of boot loops, a wipe/factory reset from recovery should normally solve the issue, if it doesn't just flash the images again as above.
Pesonally, if I'm messing i'll make sure my device is up to date and working, then fastboot boot TWRP (without unlocking or modifying my device) and backup to a USB drive, then, you can restore your system as is at any stage later if things mess up.
fastboot boot is fantastic because it lets you temp boot a custom recovery, and do all your usual stuff (including rooting etc) without replacing the stock recovery, and without unlocking, soon as you reboot, it's gone, cause it just boot the reovery into RAM.

Doctor Dedroid said:
What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
If you are talking to me, mine is stock and used regular updates that were DL and ready.

I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app

Doctor Dedroid said:
I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.

alias_neo said:
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.
Click to expand...
Click to collapse
Got it! To be sure when I tried to update I was around 60% on the battery level... Hopefully my issue was a fluke or due to a low battery.
Update: all updated and good to go. Thanks one and all!
Sent from my Nexus 10 using xda app-developers 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

Kindke fire hd 7" not recognised in windows or Linux

Well.... no effing clue whats happened.... it must've updated recently as no longer rooted or using golauncher... getting rather annoyed at the inability to access the internal storage via usb...
Windows brings up a massive message that when i googled it the fix was to apparently unplug the pc.... which resolved a few issues but still get the same issues with the kindle... which sucks.... managed to connect briefly with Linux but now it just seem to not acknowledge it at all....
I had what i thought were the latest drivers as i only installed them a couple of days ago.. (rediscovered scummvm!!!)
Any ideas what I can do? I want to re root and flash a totally new rom as the amazon one is truely awful
And which is the best root method for 7.4.6? If there is one....
Thanks again peeps!
Sent from my KFTT using Tapatalk now Free

shugs81 said:
Well.... no effing clue whats happened.... it must've updated recently as no longer rooted or using golauncher... getting rather annoyed at the inability to access the internal storage via usb...
Windows brings up a massive message that when i googled it the fix was to apparently unplug the pc.... which resolved a few issues but still get the same issues with the kindle... which sucks.... managed to connect briefly with Linux but now it just seem to not acknowledge it at all....
I had what i thought were the latest drivers as i only installed them a couple of days ago.. (rediscovered scummvm!!!)
Any ideas what I can do? I want to re root and flash a totally new rom as the amazon one is truely awful
And which is the best root method for 7.4.6? If there is one....
Thanks again peeps!
Sent from my KFTT using Tapatalk now Free
Click to expand...
Click to collapse
You would probably benefit most by using KFFA to return to 7.2.3 then root, remove OTA updates and install GApps. This way when you go to install a custom ROM, you have a matching boot loader. In order to put a custom ROM on, you need to flash a 2nd boot loader and TWRP. All this is covered in great detail on here. If you have questions do ask.
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app

I recommend Paranoid Android indeed!