I never got the original ICS update OTA, after trying every troubleshooting suggestion ASUS had to offer I finally just said screw it and rooted my TF101 and installed the ROM manually from here. Now, strangely enough, I am getting the latest one OTA with the option to postpone only 3 times, I'm not concerned with losing root or anything, I just don't want to brick my tablet. Is it safe to take the update?
Do you have CWM installed?
It generally is a bad idea to install official OTA's on a rooted device. If you're running a normal Asus Rom modified to keep root you might want to just flash ARHD while you're at it
Thats what I thought, thanks for confirming that for me. What exactly is ARHD? I do have CWM installed.
Sent from my SCH-I510 using XDA
Anyone have any issues trying to update with the stock ROM and recovery (not rooted either)? My wife's will download the update and reboot where it shows the android guy and the progress bar that gets to about 1/3 the way across, then get the Android guy with the Exclamation point in the triangle. Tried it twice.
Anyone else getting this?
Just so I have it straight ...
I have the same issue. I have an updated to ICS and rooted the device (no custom ROM) TF101. I have CWM installed.
I have the option to update the firmware ....
1) should I unroot and install the OTA update? Then re-root?
2) Go ahead and install regardless
3) Then I can install the ARWD?
4) some other option ????
I have looked and I haven't found a clear answer.
toolmanz said:
I have the same issue. I have an updated to ICS and rooted the device (no custom ROM) TF101. I have CWM installed.
I have the option to update the firmware ....
1) should I unroot and install the OTA update? Then re-root?
2) Go ahead and install regardless
3) Then I can install the ARWD?
4) some other option ????
I have looked and I haven't found a clear answer.
Click to expand...
Click to collapse
I'm rooted and I just downloaded and installed the update fine. Stock ota ics and stock recovery. Rooted with vipermod too before the update.
toolmanz said:
I have the same issue. I have an updated to ICS and rooted the device (no custom ROM) TF101. I have CWM installed.
I have the option to update the firmware ....
1) should I unroot and install the OTA update? Then re-root?
2) Go ahead and install regardless
3) Then I can install the ARWD?
4) some other option ????
I have looked and I haven't found a clear answer.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1545965
This is what I did with mine. It updates everything but your recovery since you have a custom one on yours. This was the easiest thing with CWM installed with the stock ICS ROM
Thanks folks! I have my answer.
Hi,
atm, I have an A501 with CWM-based Recovery v5.5.0.x(thor2002ro rev1.7) and Android 3.2 (EMEA CUS7 - Germany).
My Tab tells me that there is an update, which I downloaded and tried to install. However, after a few seconds an Android with a red exclamation mark appears and the installation of the updates aborts.
So, I want to remove CWM Recovery and root and return to a stock rom. However, that seems impossible. I downloaded the Acer Recovery Installer App but this one offers me a USA A500 stock rom - but I need an A501 rom because of 3g.
When I try to install this one (http://forum.xda-developers.com/showthread.php?t=1234039) I decrypted before, CWM tells me
"Installating update...
Installation aborted"
So, this does not work either.
I am really desperate because I have to revert to a stock rom...
Can someone please, please, please help me out?
lamajstro said:
Hi,
My Tab tells me that there is an update, which I downloaded and tried to install. However, after a few seconds an Android with a red exclamation mark appears and the installation of the updates aborts.
Click to expand...
Click to collapse
The update has overwritten yr custom recovery with the Acer stock recovery. It also checks yr system files if it ain't completely stock it will abort. being rooted can also affect the update.
but I need an A501 rom because of 3g.
When I try to install this one (http://forum.xda-developers.com/showthread.php?t=1234039) I decrypted before, CWM tells me
"Installating update...
Installation aborted";
Click to expand...
Click to collapse
Did u install cwm again from Acer recovery installer b4 flashing. the rom?
I'm unfamiliar with the 501 and what stock Roms are available for it
Search xda for vache full ota update packages and see if there's one that thread
So, I want to remove CWM Recovery and root and return to a stock rom.
Click to expand...
Click to collapse
Why not give HC the flick and upgrade to a custom ICS rom?
dibb_nz said:
The update has overwritten yr custom recovery with the Acer stock recovery. It also checks yr system files if it ain't completely stock it will abort. being rooted can also affect the update.
Did u install cwm again from Acer recovery installer b4 flashing. the rom?
I'm unfamiliar with the 501 and what stock Roms are available for it
Search xda for vache full ota update packages and see if there's one that thread
Why not give HC the flick and upgrade to a custom ICS rom?
Click to expand...
Click to collapse
Thank you a lot for your answer!
Yes, I did install cwm again from acer recovery installer, but that did not change anything.
Unfortunately none of the roms offered on xda work, they all abort in cwm and I don't know why.
I would prefer to go back to a stock rom with stock recovery because I want to give the tab to someone else.
lamajstro said:
Thank you a lot for your answer!
Yes, I did install cwm again from acer recovery installer, but that did not change anything.
Unfortunately none of the roms offered on xda work, they all abort in cwm and I don't know why.
I would prefer to go back to a stock rom with stock recovery because I want to give the tab to someone else.
Click to expand...
Click to collapse
Yeah, you may have difficulties flashing full packages via CWM. Especially if you didn't decrypt the rom first.
I've got a few 501 roms you can try. All HC 3.2.
One of them, is an ATT full package update which will probably work for you. Just pull the update.zip out of it. Put it on your Ext SD card, and boot holding PWR and Vol+. This will force it to install update.zip from the SD card.
Any rom you use, you have to decrypt it first. Some try renaming the rom to update.zip, and some have success using this method.
Like I say, it's an AT&T rom, but is probably really a ComGen 1. So it should have decent language support.
If you're interested, I can throw them up on a server tomorrow.
But I tell you this first, before you go messing around with these things. GET YOUR UID Number first, and write it down. You can get instructions on UID in the Development Forum, 1st page usually. It's easy.
MD
lamajstro said:
Thank you a lot for your answer!
Yes, I did install cwm again from acer recovery installer, but that did not change anything.
Unfortunately none of the roms offered on xda work, they all abort in cwm and I don't know why.
I would prefer to go back to a stock rom with stock recovery because I want to give the tab to someone else.
Click to expand...
Click to collapse
Sent from my A500 using Tapatalk 2
No probs!!
U must use a "update.zip" , decrypted first as Moscow said, and booting into recovery via button combo may help too,
also remember to remove the zip file off the ext. sdcard when you are done!!
....good luck
Can you please help me answer how to install OTA updated with CWM installed. I get this error saying the installation aborted .. it boots into CWM
is there any step by step method to get the new update on nexus 4
Thanks
you need stock rom, no modifications made, and stock kernel for it to work
Download and extract the original 4.2 and fastboot flash system system.img and it'll restore all missing apps.. I had to do it earlier to allow the system to install the update
Sent from my Nexus 4 using xda app-developers app
I reflashed stock recovery but now the update isn't available. Any ideas?
billybennett said:
I reflashed stock recovery but now the update isn't available. Any ideas?
Click to expand...
Click to collapse
update manually.
So I got my update but it keeps failing during install. I'm rooted and every time the update starts it kicks over to CWM recovery and stops with a message something like, "do you want to install this untrusted zip file" I say yes but it still fails. I have even tried to manually install the update through CWM but that fails too. My N7 is rooted but otherwise stock, I have not removed any stock apps or flashed roms or kernels so WTF must I do???
Did you not read the posts above yours? CWM recovery is not stock.
Sent from Arkham
zelendel said:
Did you not read the posts above yours? CWM recovery is not stock.
Sent from Arkham
Click to expand...
Click to collapse
I don't know where, but I saw a few posts about working updates to 4.2.1 with CWM recovery.
However, I'm not getting it to work.
How do I get rid of the recovery without loosing the root?
If you are on Windows I find the Nexus 4 Toolkit to be super easy to use. I flashed a stock recovery so I could get the update. Unfortunately, I forgot I had made changes to the stock weather widget so I can't apply the update anymore because of a missing geniewidget.odex file.
You will need to be fully stock to get the update to take as posted earlier in this thread. This is a well known requirement when doing OTA
Sent from Arkham
4.2.1 update getting installation aborted
Hey, can some please post the stock Nexus 4 v4.2 build.prop file? I can't seem to install the v4.2.1 update without it...
Thanks...
zelendel said:
You will need to be fully stock to get the update to take as posted earlier in this thread. This is a well known requirement when doing OTA
Sent from Arkham
Click to expand...
Click to collapse
Successfully installed OTA here while rooted with CWM recovery, though everything else is stock.
billybennett said:
If you are on Windows I find the Nexus 4 Toolkit to be super easy to use. I flashed a stock recovery so I could get the update. Unfortunately, I forgot I had made changes to the stock weather widget so I can't apply the update anymore because of a missing geniewidget.odex file.
Click to expand...
Click to collapse
Hey,
got an Error over here with stock recovery and root.
However, tengen says he made it with CWM and root - maybe it's because I'm using stuff like Busybox or the Pimp my Rom APK?
EDIT: I think its because of the %-BatteryMod I'm using. I'll try to flash the custom rom.
Greetings
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
you probably need stock recovery to complete the update... I would just wait for someone to root the update and then flash it that way
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.
phonic said:
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.
Click to expand...
Click to collapse
is this problem caused by flashed kernel ??
williamlaw said:
is this problem caused by flashed kernel ??
Click to expand...
Click to collapse
Did you not bother to read anything I wrote?
I had the same problem. If you have a TWRP backup from a previous android version that allowed the ota to work just flash that and you'll still receive the ota for 4.2.2
Sent from my Nexus 7 using Tapatalk HD
This happened to me too, though I have the wifi-only version. So it's not just the radio.
I got the same problem with my Wifi version. Is there any fix yet? I only rooted the device but the rest is still stock. How come the update failed?
the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?
rexxxxx said:
the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?
Click to expand...
Click to collapse
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
finally flashed back to stock 4.2.1 then OTA update 4.2.2
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
how ? I indeed have the mount stick installed for the OTG cable !
rexxxxx said:
how ? I indeed have the mount stick installed for the OTG cable !
Click to expand...
Click to collapse
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer
I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
So, is there any way of doing this without doing a wipe ? Or losing any of your data ?
What about putting the update, downloaded from google, on a USB stick and booting into twrp then flashing from there ?
I don't mind losing root, although I have rootkeeper installed, and I don't mind losing custom recovery, all of this can be fixed.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
What I don't want to do is lose my data. I have plenty of full twrp backups done, but then these are 4.2.1 backups. Backing up my apps isn't really feasible at the moment because of their sheer size. Horn, NOVA 3, the GTA games, bards tale, all gigs and gigs of data. Infact, I only have 1 gig left on a 32Gb N7, and I just don't have anywhere left to put a full backup of apps on to. I also don't want to download them all again, NOVA 3, for example, took me 6 hours to download on wi-fi.
I have read a lot of advice and help on here, plenty of googling which simply sends you back here anyway, and most advice centers around losing your data in some way. So, any help without losing data would be most appreciated,
spiou said:
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer
Click to expand...
Click to collapse
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app
After reading many threads and articles, I finally upgraded to 4.2.2 with stock recovery. Your mileage may vary.
Based on the discussions on http://forum.xda-developers.com/showthread.php?t=2148456, the failure may be caused by an app you installed
that corrupted some system files. Therefore, you have to flash 4.2.1 stock system and boot images back. The nice thing is your data and settings remain intact.
Although you lost root, it can be easily re-rooted using nexus root toolkit.
Now you're back to 4.2.1 which is allowed to upgrade, use OTA RootKeeper to keep su and then upgrade thru OTA. If you can not longer get OTA, you can clean data/stop/start Google Framework service, Google play service, and Google play store, and then re-check update. The last tip I read it somewhere but I forgot where I read it. Sorry.
Good luck. :laugh:
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
JohnRM said:
I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
Click to expand...
Click to collapse
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....
rexxxxx said:
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You must clear the data of the Google framework (in the list of apps) and reboot immediately the tablet. Then the update will be proposed again.
One more thing : when you replace the file, check that the permissions are identical.
khaytsus said:
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....
Click to expand...
Click to collapse
Exactly. I don't understand why we need to see posts like that over and over and over again. Hell, the OTA update will even tell the user what failed, and yet people still complain and ask what's wrong.
Also, while in most cases a custom recovery is OK (though the update will overwrite it), with the N73G unit, you need to use the stock recovery, otherwise it will fail without warning ahead of time.
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
Can you elaborate? E.g., where do you get the original debuggerd from, how do you replace it (adb push?), etc.
This OTA-Update will update your french (Retail.en.FR) MotoG from Blur_Version.174.44.9.falcon_umts.Retail.en.FR to Blur_Version.176.44.9.falcon_umts.Retail.en.FR.
Don't get fooled by the filename this is indeed the 176.44.9 update. You might need to change the file name to "Blur_Version.176.44.9.falcon_umts.Retail.en.FR.zip" in order to install via SDCARD (copy renamed update to /sdcard/ on your phone) method
http://www.file-upload.net/download-8643048/Blur_Version.174.44.9.falcon_umts.Retail.en.FR.zip.html
MD5 checksum: 56934274b7985aad92ea4fc08bc29f12
PS: Please ignore the thread title. I've mixed up OTA and OTG . I've reported myself to get it changed.
... or without renaming it can be installed via stock (!) recovery.
Edit: Philz can be used too.
drfr said:
... or without renaming it can be installed via stock (!) recovery.
Edit: Philz can be used too.
Click to expand...
Click to collapse
Hello,
Is that possible to install this firmware update with root ?
When i try to apply with custom recovery, he say errors happen.
Thanks
Math43 said:
Hello,
Is that possible to install this firmware update with root ?
When i try to apply with custom recovery, he say errors happen.
Thanks
Click to expand...
Click to collapse
My experience is that root is not a problem. And when Philz recovery warns you about non-signed file, just ignore it.