OK, for starters:
Tablet's current stats:
ROM: CWM-Rooted_Acer_A500_7.006.01_COM_GEN2
Recovery: Stock US 1.141.07_COM_GEN1
Root status: Rooted
Problem at hand: Cannot install OTA updates. I used Acer Recovery Installer to originally install CWM so I could flash ROMs (duh). So I used Acer Recovery Installer to have it install the stock recovery image so I could actually install the OTA updates. I know this likely means I would lose root, and that is OK.
When I installed the stock recovery back, I tried to let it install the update. It would reboot, show the package opening (little box that was open and a progress bar showed up). The bar got about 25% completed, then it changed into a triangle with a "!" inside it, and the little Android dude below it. After a few minutes, it would reboot by itself. Once booted up, I would get a message that simply said "Update Failed".
I brought this up in another thread, and someone suggested I unroot as well. I immediately tried to do that, but IconiaRoot gives me the following:
Removing superuser.apk
Removing /system/xbin/su
Sleeping in 5 seconds...
Something went wrong.. you are still root?!?!
I can confirm I am still rooted by going into terminal emulator and running su and I get a # sign. So I am at a loss now on what else to try. With the stock recovery, if I tell Acer Recovery Installer to reboot into recovery, when it reboots, all I get is the triangle with a "!" in it. I noticed the ROM has GEN2 and my stock recovery has GEN1, and the OTA update ends with GEN2, is that an issue?
EDIT: I also know now there are other rooted ROMs with these OTAs applied. I'd like to unroot and go back to stock, so please do not recommend this.
Ok did you make a backup via CWM ?
In the other thread the recovery i restored was the backup i made of my one via Acer recovery,
If i was you i would reinstall CWM and make sure that recovery is working then wait for someone to come in and tell you the correct stock recovery for your one is.
oh i get u now, u got the gen2rom installed and u want back to your own stock gen1 to get the OTA, correct?
u need a cwm backup of 3.2 gen1 stock, when u restore it, u should receive an OTA notification for the 3.2.1 GEN1 OTA. Before you download it, u need to be rooted, use the backdoor/OTA method of timmyDeans. It will create a backdoor so after you have installed the OTA you can get in to run the installtools command again to root and install cwm again. AND you will still recieve OTA's.
Iconia Root - only works on 3.1, it will not work for 3.2, so it will throw an error.
But i'm sure root wont prevent the install as the OTA overwrites system files and resets the permissions, it also checks all system apps are there, so if you;ve deleted any bloatware or changed build.props the update will fail.
I have spent the last week trying to get back to stock so i can OTA. I have read hundreds of posts and tried all the methods that had been posted. The easiest and quickest and most successful way of achieving this was the backdoor method. Yes you need adb installed but you dont actually use it, it is all done for you. there is a very good walkthrough here http://www.chdcomputers.gr/en/mnu-kb-en/mnu-kb-android-en/mnu-kb-android-devices-en/mnu-kb-android-a500-en/254-art-kb000005-en
Then install the backdoor v3 (link in sig) -have a look and see if that will get u to where u wanna be!
Decideed it was easieeer to just install one of the prerooted roms from the dev forum. Running 7.014.14.com gen 1 now. Thanks guys.
Related
Woke up today and it said there was a system update available. I unrooted with iconia root and started to update. It downloaded the file which only took a min or two (only 14.49MB) and it reboots to install, but then when it starts back up to install it hangs at a screen with the android honeycomb bee and a !.
I can turn it back off and then turn it back on and it boots back up without the update installed. I checked for the system update through About tablet and it allows me to start over and download the update again, but the same thing happens every time. I have the stock rom, was rooted and now unrooted, build 4.010.11_COM_GEN2, kernal 2.6.36.3
Is anyone else having trouble installing this update?
edit...Sorry! I thought the update was so new that no one had posted about it yet. I searched a little more and found other threads. I'll try to figure it out with those posts and the mods can delete this one.
You said you were rooted. Did you use Acer Recovery for any backups? Did you backup the current recovery image when prompted? If you did you might need to go into Acer Recovery and install the stock recovery image. (The top radio button). You don't have to reboot, just unroot and then try the OTA update. Worked for me.
I did unroot when I tried it but I re-rooted and tried another method. I did use Acer Recovery but I didn't use the stock recovery. I booted into the CW recovery and installed the zip file of the update from the other thread. Everything worked fine and now I am at 4.010.13
n1ke5h said:
I did unroot when I tried it but I re-rooted and tried another method. I did use Acer Recovery but I didn't use the stock recovery. I booted into the CW recovery and installed the zip file of the update from the other thread. Everything worked fine and now I am at 4.010.13
Click to expand...
Click to collapse
What are the fixes with this update?
I noticed with my iconia that when a SD card is inserted, my updates downloads but doesn't install properly. I had to remove it to install succsessfully. I'm wondering if anyone has the same problem
Sent from my A500 using Tapatalk
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.
Hello,
I rooted my kindle fire last week using KFU 0.9.5. Everything was going fine until yesterday, when it decides to restart itself and try to install an update, I think it's the 6.3.1 update. It get's about 1/4 of the way through and stops, shows a white triangle with a yellow exclamation point in the middle and andy on the side, and just sits there. I've restarted it about 10 times now, and every time it gets to the home screen, it restarts and goes in the cycle again.
FYI I used the CWM recovery in the KFU, I don't know if it makes a difference.
The 6.3.1 update is causing a lot of problems with rooted devices. It may take a few days to pinpoint the problem. See if you can get into recovery, you may need to flash a different rom.
MoDaCo is a very good "stock" analog if that's what you're into.
Thanks
Thanks, I think I'll just wait a few days to see if the problem gets fixed.
At least in my experience twrp will actually unpack and install the update for you.Also if the fact that your rooted is causing the installation failure and you really want the update install ota root keeper from the market click protect root and temporarily unroot the device. If the update succeeds you will then need to go through the process of rerooting your device.f your simply just tired of what its doing download the latest stock image place it at the root of your SD card and flash it via cwm recovery under install update zip. Then reroot flash fff and the recovery of your choice then your good to go. I prefer twrp recovery plus if you want to flash ics with the new kernel you will need twrp to do this cwm doesn't work.
Thepooch said:
At least in my experience twrp will actually unpack and install the update for you also if the fact that your rooted is causing the installation failure if you really want the update install ota root keeper from the market click protect root and temporarily unroot the device and the update succeeds you will then need to go through the process of rerooting your device if your simply just tired of what its doing download the latest stock image place it at the root of your SD card and flash it via cwm recovery under install update zip then reroot flash fff and the recovery of your choice then your good to go I prefer twrp recovery plus if you want to flash ics with the new kernel you will need twrp to do this cwm doesn't work.
Click to expand...
Click to collapse
punctuation? lol!
Awhh who cares lol I sure dont THERE I PUNCTUATED PURE SYMANTICS! Lol punctuation should cost more I will add a donate button later.
Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.
No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
LORD MJ said:
Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.
Click to expand...
Click to collapse
nyepo said:
No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
Click to expand...
Click to collapse
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.
LORD MJ said:
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.
Click to expand...
Click to collapse
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.
I did a "flash stock+unroot" and relocked my device via the Wug app and it still errors
eksasol said:
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.
Click to expand...
Click to collapse
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.
LORD MJ said:
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.
Click to expand...
Click to collapse
The OTA update can fail for many reasons, it could be due to any changes to the /system partition which is what root does, such as changes to gps.conf file, changes in build.prop, different kernel or radio.
If you're going to make a full backup, what you should do is flash a full factory image (link in my signature, and provided you already backup your data.) Then boot into a custom recovery to make a full backup, (not flash the recovery, but: fastboot boot twrp.img) When you do the backup make sure the boot (kernel) and recovery partition are selected. However, you can't backup the radio partition, but that should be fine unless you intend to use the LTE radio.
I have a similar problem. I have ROOTED device with TWRP recovery and stock 4.3 android (obtained OTA before rooting), and I just got notification that my OTA update to 4.4 is ready to be installed.
So I clicked Restart and Install button and the phone restarts(as it should) but after that it went in TWRP recovery and waited for some instruction I suppose. I didn't know what to click exactly, so I clicked Reboot from TWPR menu and it went in fastboot mode. From fastboot I chose Start and phone turns on. Updating didn't even start..
So, were there something that I could do when I was in TWRP recovery that could initiate updating process, or I never had a chance?
What exactly I should do to get that update on my phone? Sorry for my English and if was unclear.
I used Google's batch file on windows to flash the stock 5.0, having unlocked the bootloader and also installed the chainfire root. Just wondering whether I'll get any fixes, or whether i'll have to always repeat this process, wiping out everything on the device in the process.
You may get prompted to download and install new updates when they arrive, but they will fail upon installation unless you're 100% stock.
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
igeigeige said:
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
Click to expand...
Click to collapse
Does the Google image download page (https://developers.google.com/android/nexus/images) get updated as Lollipop gets updated? Or am I going to have to do OTA updates?
hmm.. im not sure which comes first.. but, if you want to get OTA, you'll have to wait for your device to get its turn for the notification to appear. The effect will still be the same though if you flash that google image to your device.. And flashing that device, will save you time from waiting for your OTA to appear on your device.
Cheers! :good:
igeigeige said:
hmm.. im not sure which comes first.. but, if you want to get OTA, you'll have to wait for your device to get its turn for the notification to appear. The effect will still be the same though if you flash that google image to your device.. And flashing that device, will save you time from waiting for your OTA to appear on your device.
Cheers! :good:
Click to expand...
Click to collapse
Well, I'm a bit confused. I'm on stock, but i need root, so i installed cfar, which I think included super su. when a new version of super su came out (i was alerted via google play), i needed to install the twrp recovery (which I didn't have installed at that point) to update it. So I guess I'm not stock any more, even though I've not actually put a non-stock image on. So even if the OTA update message popped up, I doubt it's safe to install it that way, even if it let me. I'm just not sure whether I need to a factory reset/wipe etc before updating, or if I can do a dirty update (the OTA is effectively a dirty update, isn't it?). And, like i said, i'm not sure whether that page gets updated with new images, or whether you're supposed to just put the initial one down and then do OTA updates (and only then root, change the recovery etc).
You have a stock rom but with a CUSTOM recovery. Yes, ota will prompt you to update, but DON'T. You should convert to stock recovery first. Because if you do, the update will push through, but once it asks you to boot to make the update in effect, you will have a NO COMMAND error - bootloop, and only fastboot and recovery (sort of dysfunctional). Just like most of the people here, including me. So make backup of your files first before doing the update. Cheers :good:
Sent from my Nexus 10 using XDA Premium 4 mobile app
If having a custom recovery is an issue, why could I flash ota zips from custom recoveries ever since buying the tablet?
igeigeige said:
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
Click to expand...
Click to collapse
Should have read this first. In the bootloop. Tried flashing back to stuck with nexus toolkit. No luck. Suggestions?
Rizz67 said:
Should have read this first. In the bootloop. Tried flashing back to stuck with nexus toolkit. No luck. Suggestions?
Click to expand...
Click to collapse
Hi, what i did was flashing the official factory image from google via fastboot/bootloader... Make a nandroid backup first though.. Because you'll need to clean flash (system partition/cache and data) to avoid future problems.
please educate me
A few weeks ago I rooted my N4 with CFAR (& of course had to wipe out everything). My understanding was that now that my bootloader is unlocked, I can sideload new images, thus sparing me a rewipe -- & in my ignorance, was anticipating that ChainFire would make 5.0.1 images in due course.
So, If I want to root subsequent 5.x.x releases, how would this work in real life??
Can i just restore stock recovery and then install the 5.0.1 ota update without losing everything?