I've already asked this in another thread about this but can't get my answer. So I'm rooted with an unlocked boot loader. I'm running motleys kernel. I just got notification of the OTA update 4.1.2 Can I let it install this or should I flash the stock kernel first then let it install?
Sent from my Nexus 7 using Tapatalk 2
Bump this. For hours now, I just stare at the notification "System update available" hoping it would say "You're good to go, trust me". Lol. So, Stock rom, stock kernel, binaries updated, rooted and unlocked bootloader. Anyone similar had tried?
Sent from my Nexus 7 using Tapatalk 2
Damn. I give it a go but it didn't even cross my mind that I've modded Maps.apk installed and f*** the update process failed with error:
assert failed: apply_ patch_check("/system/app/Maps.apk", "randomcharacters", "randomcharacters")
Check system still 4.1.1 but when press system updates, says mine is up to date. Uninstall maps, still the same. Download the patch and manual update, upon restart android is updating but check about, still 4.1.1. I've tried a few similar steps, nada. Totally screwed it.
I need some advice here before I waste hours returning this to stock and start all over again. Sigh.
Sent from my Nexus 7 using Tapatalk 2
Related
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
Ya, malaysia pull down 3.2
second that.. malaysia received the OTA update
I received the notificatioj just now, waiting to update it tomorrow using wifi
Anybody know what are the major upgrades for 3.2 other than adjustable widgets
Is this for A500 or A501
Sent from my PG86100 using Tapatalk
It is A500.
I hope we see that in US soon.
do you have any links by any chance?
I think I'd wait for root before updating
Sent from my A500 using XDA Premium App
After update from 3.1 to 3.2 for my A500, My Papago M8 which run smoothly on 3.1 at 1280x800 resolution, now just dont run on 3.2, it complains that the device is on 1280x752 resolution!
Anyone in the US getting the update yet?
Invalid system update
I have unrooted then rebooted, but still constantly getting invalid system update cancelled message. Any suggestions?
tariche said:
I have unrooted then rebooted, but still constantly getting invalid system update cancelled message. Any suggestions?
Click to expand...
Click to collapse
I'm getting the invalid update too. I have never rooted my Iconia A500.
Please rename the thread
Will we loose root if we do the OTA update?
mshnayde said:
Will we loose root if we do the OTA update?
Click to expand...
Click to collapse
Yes
Sent from my PG86100 using Tapatalk
gmfeny said:
Yes
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Is there a way to update to 3.2 without loosing root.
Seems like we don't have a way to root it again afterwards.
Sorry newbie to the Tablet world.
Can someone getting the update please pull the link or give before and after version numbers?
bigmacpaddy said:
I'm getting the invalid update too. I have never rooted my Iconia A500.[/
is this error during download or installing in recovery.do you have cwm installed.
Click to expand...
Click to collapse
erica_renee said:
is this error during download or installing in recovery.do you have cwm installed.
Click to expand...
Click to collapse
This error comes up after the download completes and it says "preparing update" I don't have any extra Recovery installed. Completely stock 3.1 A500
just an idea
Go intto settings, manage apps, all apps - find the system updater and clear it's data, reboot, should reprompt download and may work.
May not. Worth a shot
so is it pull down loh for anybody in Europe/US yet?
Anyway, regarding invalid update I finally managed to pass the invalid system message. BUT, when it rebooted and started updating suddenly it stopped and showed exclamation traffic sign over droidbug in a middle of the updating.
Rebooted and it just reported failed update.
So I guess we have to be patient, eventually it will work.
For those who are on stock rom and never rooted, I recommend to root,then CWR and backup, cause if it happened that I could not boot after unsuccessful update there is backup, so no sweat.
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).
Please help
I have a stock rooted Nexus 10 running 4.2.1. After the system prompt me that an update is available and I clicked yes to update, now it is stuck at infinite boot screen loop with error message. I had to go into CWM to manually shut it down.
What should I do?
I initially rooted the nexus 10 using the method described here with a PC
http://nexus10root.com/nexus-10-root/how-to-root-nexus-10-easiest-method/
blueice228 said:
Please help
I have a stock rooted Nexus 10 running 4.2.1. After the system prompt me that an update is available and I clicked yes to update, now it is stuck at infinite boot screen loop with error message. I had to go into CWM to manually shut it down.
What should I do?
Click to expand...
Click to collapse
You will need to unroot first
Sent from my Amaze 4G using xda app-developers app
i got my nexus 10 with 4.2.0 and rooted.
and i got 4.2.1 upgrade from google pushed.
i didnt unroot and upgraded successfully.
blueice228,
Here is a link to someone who returned their Nexus 10 back to stock and then applied the 4.2.2 OTA update. Warning, I have not done this myself but the information may be usefull.
http://forum.xda-developers.com/showpost.php?p=37895796&postcount=20
Got this phone in a stupid trade after the bootloader opportunity had passed. Been running safestrap for awhile but wanted to play around with whatever stock its up to. Used Matts utility. Flashed 4.1.2. Rooted with chopper. Vooded to protect. Got the OTA. Failed. Tried again and used OTA grabber. Copied to computer. Tried to ADB Sideload. Started OK then bam! At least this way I got reason:
assert failed: apply_patch_check ("EMMC:boot:10485760:6c80d1f837bb3a127bc7aabd0164afd09e51475e:10485760:bbc1976c3cf2987f182a4747934ffb8d0f532fd8")
any suggestions?
Mcowan226 said:
Got this phone in a stupid trade after the bootloader opportunity had passed. Been running safestrap for awhile but wanted to play around with whatever stock its up to. Used Matts utility. Flashed 4.1.2. Rooted with chopper. Vooded to protect. Got the OTA. Failed. Tried again and used OTA grabber. Copied to computer. Tried to ADB Sideload. Started OK then bam! At least this way I got reason:
assert failed: apply_patch_check ("EMMC:boot:10485760:6c80d1f837bb3a127bc7aabd0164afd09e51475e:10485760:bbc1976c3cf2987f182a4747934ffb8d0f532fd8")
any suggestions?
Click to expand...
Click to collapse
Woaaahhh.
Premises are kinda wrong here. If you aren't on the latest version of stock, you *should* still be able to unlock. Have you tried to yet?
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Woaaahhh.
Premises are kinda wrong here. If you aren't on the latest version of stock, you *should* still be able to unlock. Have you tried to yet?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I wish it were that simple. Used the utility when I got the phone a couple months back. Screen shot of current system info attached.
Mcowan226 said:
I wish it were that simple. Used the utility when I got the phone a couple months back. Screen shot of current system info attached.
Click to expand...
Click to collapse
That should be unlockable. What was the exact result when you ran the unlocker?
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
That should be unlockable. What was the exact result when you ran the unlocker?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I apologize for the delay in getting back to this thread Been caught up with other projects I have attempted a few times to unlock the bout loader through the utility however it always fails The inability to update with the ota as bbecome rather annoyin as it keeps asking
What's the date on your fast boot menu... I ask because if it is indeed unlockable I'd hate to say use this and do that and have this and that kill an opportunity for you
Sent from my XT907 using xda app-developers app