Related
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.
I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..
"Real ota(?)" Is pushed by google and installs automatically, IMO.
Sent from my Nexus S using xda app-developers app
albundy2010 said:
I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..
Click to expand...
Click to collapse
1. Spot on, reading the update script it doesn't look for additional files. I said otherwise previously, my bad.
2. Also true. Updater script does no hash check on the two recovery files either, so even if you deleted /system/etc/install-recovery.sh it will still be fine. My bad also.
3. Spot on.
Thanks for this writeup albundy :good:
So I was running ics roms well before they came to my ns4g... I didn't bother with ota since there was already a port available almost immediately... that fixed most of the bugs we experienced with pre-ota ports...
My question is, I'm running RemICS UX v1.3... what would I need to do to get PTA when its available for our phones?
I'm sure they'll have a flashable rom almost immediately so this question might be null anyways... but it is good to know these things...
Sent from my Nexus S 4G using Tapatalk 2
ioplkj13 said:
"Real ota(?)" Is pushed by google and installs automatically, IMO.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Yes, but the question is when that will happen. Google pushes updates in waves, it could take weeks before it gets pushed to your phone.
And all those people already getting anxious now how to prepare their phone for ota-push don't strike me as the waiting kind... in fact, it's really silly making all that fuzz now, still another 2 weeks before 4.1 gets released.
the1dynasty said:
My question is, I'm running RemICS UX v1.3... what would I need to do to get PTA when its available for our phones?
I'm sure they'll have a flashable rom almost immediately so this question might be null anyways... but it is good to know these things...
Click to expand...
Click to collapse
So far the NS4G always had to wait to get an official update, Sprint taking it's time. The first OTA's will probably be for 9020T/9023 again, different radio. So unless you are willing to wait, you need a custom-zip anyway, don't use the dl-link from Google that will be floating around in 2 weeks.
But to answer your question:
First OTA's have always been incremental updates, so one needed to be on prior stock-rom to apply it. (In this case: 4.0.4 stock -> 4.1 update)
Of course they could change it this time and release everything at once (full rom, factory images, all models), but I heavily doubt it.
I'm on stock 4.0.4 rooted with no custom recovery. The way i see it i have 2 options:
1. Make an OTA update. I will not lose any app or data, but what about the root? It will be lost?
2. Flash CWM and the flash the update zip. In this case the root is surely gonna be in the zip file, but what about the apps and data. Will i lose them?
grigri444 said:
I'm on stock 4.0.4 rooted with no custom recovery. The way i see it i have 2 options:
1. Make an OTA update. I will not lose any app or data, but what about the root? It will be lost?
2. Flash CWM and the flash the update zip. In this case the root is surely gonna be in the zip file, but what about the apps and data. Will i lose them?
Click to expand...
Click to collapse
Re #1: Yep, root will be lost. You shouldn't loose and app / data.
RE #2: You only loose data when you do 'wipe data' in CWM, which you should do when installing a new ROM.
If you install 'Titanuim Backup' you can back up and then later restore all your APPs. After you back up APPs, you will need to transfer these to a PC, and wipe the phone, install new ROM, and then transfer APP backups back to SD Card on phone, install them using Titanium Backup. The PRO version allows you to do this in batch mode (much quicker).
ac17 said:
Re #1: Yep, root will be lost. You shouldn't loose and app / data.
RE #2: You only loose data when you do 'wipe data' in CWM, which you should do when installing a new ROM.
If you install 'Titanuim Backup' you can back up and then later restore all your APPs. After you back up APPs, you will need to transfer these to a PC, and wipe the phone, install new ROM, and then transfer APP backups back to SD Card on phone, install them using Titanium Backup. The PRO version allows you to do this in batch mode (much quicker).
Click to expand...
Click to collapse
I have Titanium backup pro. But which method is the wiser?
OTA and reroot or update zip and re-install all apps?
@ re #2: why the transfer of backups to PC?! They're saved on sdcard, it never gets wiped automatically (except when unlocking boot loader). And there's no need to do it manually.
caliban2 said:
@ re #2: why the transfer of backups to PC?! They're saved on sdcard, it never gets wiped automatically (except when unlocking boot loader). And there's no need to do it manually.
Click to expand...
Click to collapse
Because, i will make a wipe data in order to get a clean install of the new ROM. In our case the 4.1 stock.
you don't have to wipe sdcard to get a clean install... but go ahead, it won't do any harm.
will I get the OTA?
So I've got cyanogen mod 9 on my nexus s with Clockwork mod bootloader will I get the OTA update? if not what changes do I have change back? ps I would rather not format the Internal USB drive.
Ah you people complicated it for me, this is what I was thinking of doing
I'm on CyanogenMod 9 RC1, when Jelly Bean starts going OTA, there should be a flashable ZIP available, right? I know when I was on GB, and waiting for OTA for my country is never gonna happen, I just downloaded update.zip and flashed it.
1. Download ZIP, put it on SD Card, along with full stock 4.0.4 flashable ZIP, and Superuser.zip
2. Make Titanium Backup of apps
3. Go to CWM
4. Wipe data
5. Flash stock 4.0.4
6. Flash update to make it Jelly Bean
7. Flash Superuser
8. Boot to Jelly Bean
9. Explore around, download ROM Manager, install CWM again through it, because it will probably be gone once I boot into JB for the first time
10. Done
Correct me if I'm wrong.
JavaJunkay said:
Ah you people complicated it for me, this is what I was thinking of doing
I'm on CyanogenMod 9 RC1, when Jelly Bean starts going OTA, there should be a flashable ZIP available, right? I know when I was on GB, and waiting for OTA for my country is never gonna happen, I just downloaded update.zip and flashed it.
1. Download ZIP, put it on SD Card, along with full stock 4.0.4 flashable ZIP, and Superuser.zip
2. Make Titanium Backup of apps
3. Go to CWM
4. Wipe data
5. Flash stock 4.0.4
6. Flash update to make it Jelly Bean
7. Flash Superuser
8. Boot to Jelly Bean
9. Explore around, download ROM Manager, install CWM again through it, because it will probably be gone once I boot into JB for the first time
10. Done
Correct me if I'm wrong.
Click to expand...
Click to collapse
Too many steps. From what i have learned, download the JB flashable zip (probably it will be available the same day when ota is pushed) put to sdcard, make a wipe data and flash through cwm. The ics zip was releashed the same day, was root, busybox and superuser.
On stock 4.0.4 official with custom recovery...
Download ota zip
Boot to custom recovery
Flash ota zip
Directly after ota zip finishes, flash latest Superuser.zip (In same recovery session)
Wipe cache
Reboot----> Now you have latest ota JellyBean with Root.
Change permissions of recovery-from-boot & install-recovery.sh to 000 (so you will keep custom recovery upon reboot)
Re-flash custom recovery with JoeyKrim's Flash_Image GUI
Hungry Hungry Hippo Time
Can you have a custom kernel ??
Sent from my Nexus S using xda app-developers app
snandlal said:
On stock 4.0.4 official with custom recovery...
Download ota zip
Boot to custom recovery
Flash ota zip
Directly after ota zip finishes, flash latest Superuser.zip (In same recovery session)
Wipe cache
Reboot----> Now you have latest ota JellyBean with Root.
Change permissions of recovery-from-boot & install-recovery.sh to 000 (so you will keep custom recovery upon reboot)
Re-flash custom recovery with JoeyKrim's Flash_Image GUI
Hungry Hungry Hippo Time
Click to expand...
Click to collapse
Every stock zip contains a directory called "recovery". Delete it before flashing and you don't have to care about cwm getting overwritten.
btw are really needed only stock rom and stock kernel???
what about the 'ota survival' option present in superuser?
albundy2010 said:
I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..
Click to expand...
Click to collapse
I suspect in some of the "misinformation" you have missed the distinction between preparing the phone for automatically receiving and automatically installing properly an actual Over the Air update from Google, vs. preparing for you actually installing an OTA file, or some form of new Jelly Bean. You don't explicitly make this distinction or don't really clearly say which you are discussing. The title of your post points one direction, but the contents the other. Or maybe the "rant" style of writing just confuses people more, including me.
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 got the 4.4.3 update notification and downloaded it. When it rebooted for the install, it went into TWRP recovery. Not sure what to do with that, I rebooted. Now I am still on 4.4.2 and getting the "up to date" when I check for updates.
I am rooted running stock ROM. Does being unlocked and rooted with custom recovery prevent an OTA install of updates?
I vevs
Sent from my Nexus 7 using XDA Premium 4 mobile app
I'm also looking for help updating to 4.4.3. I uninstalled Xposed and tried to flash the update zip with TWRP but the install failed. Does the update need to be installed via adb sideload?
Sent from my Nexus 7 using Tapatalk
When my n7 was on 4.3.1 stock rooted with unlock bootloader i updated via ota and twrp can handle it. I dont know about 4.4.3. There is a thread discussing this matter but i dont remmember where, i think is in the general. I never used side load but im using nrt nexus root toolkit for udpating to 4.4.3 and it work fine.
vs980
Same problem!!
Exactly same has happened to me. I got the notification for update than i downloaded it, it was about 70 mb , then rebooted my device, goes to TWRP recovery than what ?? I just restarted my device and in settings its still on 4.4.2 what to do Now ????
Hey all
What does TWRP stand for please?
I also got the notification to update to 4.3.3 but after downloading, when the installation began I got an error screen with the android dude lying on his back. I switched my nexus off and on again and I'm still on 4.2.2.
Now I get the same message when I check for updates.
How can I get my tablet to update again please?
My nexus is a regular unrooted tablet with the stock ROM that was installed via the previous ota update.
Many thanks
Sent from my Nexus 7 using XDA Free mobile app
hmmmm, sounds odd. same thing happened to me.
maybe TWRP(Team Win Recovery Project) cant handle it, or we should have updated it first. Or maybe we should have used CWM or Stock Recovery.
but the strange thing is that the tablet cannot find the update again!!
i'll try to update NRT (Nexus Root Toolkit) and see if i can update using that.
Don't install it, until there's an answer in http://forum.xda-developers.com/showthread.php?t=2786758 - a couple of us did install it, and we've lost root, but more importantly, recovery has been wiped, and I've been unable to reflash CWM with fastboot.
My wife and son got the 4.4.3 update notification on each of their 2012 Nexus 7 this morning. I told them not to install the update; I'll handle it when I get home this afternoon. My 2013 Wifi-only Nexus 7 needed to be on stock recovery in order to install the 4.4.3 OTA, so I assume the same is true for the 2012 Wifi-only Nexus 7. I'll do the same that I did for the 2013 N7:
1) restore stock recovery, 2) adb sideload the OTA or just install it from the tablet, then 3) re-install custom recovery and re-root.
Update: I installed stock recovery, then tried to download and install the update on the device, and got an "Error" message with Android on its back and an exclamation point in a red triangle. I long-pressed the power button to reboot and it's still on 4.4.2 and says it's up to date.
So, I downloaded the update to my computer and tried an adb sideload. When I did that and watched the update fail I saw the detailed error message that "/system/bin/debuggerd has unexpected contents". Probably something from an app requiring root. So, I downloaded the 4.4.2 factory image from the google developer's site, used 7zip to extract the system image file and flashed it to the device. After that I was able to adb sideload the update, then reinstalled TWRP. When I tried re-rooting using NRT, there was no SuperSU on the device, so I installed it from the Play Store and when I opened it I chose to install binaries through TWRP. When it booted into TWRP it immediately began flashing an old Titanium Backup file named "update.zip", which I did not want to happen. That screwed up a couple of apps, but nothing that couldn't easily be fixed. My lesson is to not leave any files named "update.zip" in the root directory.
GrillMouster said:
My wife and son got the 4.4.3 update notification on each of their 2012 Nexus 7 this morning. I told them not to install the update; I'll handle it when I get home this afternoon. My 2013 Wifi-only Nexus 7 needed to be on stock recovery in order to install the 4.4.3 OTA, so I assume the same is true for the 2012 Wifi-only Nexus 7. I'll do the same that I did for the 2013 N7:
1) restore stock recovery, 2) adb sideload the OTA or just install it from the tablet, then 3) re-install custom recovery and re-root.
Update: I installed stock recovery, then tried to download and install the update on the device, and got an "Error" message with Android on its back and an exclamation point in a red triangle. I long-pressed the power button to reboot and it's still on 4.4.2 and says it's up to date.
So, I downloaded the update to my computer and tried an adb sideload. When I did that and watched the update fail I saw the detailed error message that "/system/bin/debuggerd has unexpected contents". Probably something from an app requiring root. So, I downloaded the 4.4.2 factory image from the google developer's site, used 7zip to extract the system image file and flashed it to the device. After that I was able to adb sideload the update, then reinstalled TWRP. When I tried re-rooting using NRT, there was no SuperSU on the device, so I installed it from the Play Store and when I opened it I chose to install binaries through TWRP. When it booted into TWRP it immediately began flashing an old Titanium Backup file named "update.zip", which I did not want to happen. That screwed up a couple of apps, but nothing that couldn't easily be fixed. My lesson is to not leave any files named "update.zip" in the root directory.
Click to expand...
Click to collapse
good jub. But if we flash stock rom again, all our data will be lost. And backing up 32gb of data and restoring them each time is a pain in the a*s. I'm tired and sick of it. So this time, i'd rather not install the update, than having to reinstall all my apps and reconfigure them and copy files back and ....
So... To hell with 4.4.3 this time if it wont work properly.
But there is something in my mind.
Guys, how many of you have stickmount installed?
I remember an error coused by it. Maybe it is the reason the update failed...
hamid_valad said:
good jub. But if we flash stock rom again, all our data will be lost. And backing up 32gb of data and restoring them each time is a pain in the a*s. I'm tired and sick of it. So this time, i'd rather not install the update, than having to reinstall all my apps and reconfigure them and copy files back and ....
So... To hell with 4.4.3 this time if it wont work properly.
But there is something in my mind.
Guys, how many of you have stickmount installed?
I remember an error coused by it. Maybe it is the reason the update failed...
Click to expand...
Click to collapse
Flashing stock recovery.img and stock system.img does not wipe all my data. Everything was still there: all my media, files, apps, and app data.
I think you're right about the Stickmount app. I did have it on my son's tablet, and I had to flash system. Last night I updated my wife's tablet. She did not have Stickmount, so the OTA installed without me having to flash system. Just to be safe I did flash stock recovery first. I put TWRP back on and re-rooted after the OTA.
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
EDIT: Link to the zip
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
I don't believe so.
In the past you either had to go back to stock or wait on someone to create a compatible update for rooted devices.
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Can you add what variant and build you are using before the update? Also the build afterwards?
KapilFaujdar said:
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Click to expand...
Click to collapse
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
gghose said:
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
Click to expand...
Click to collapse
Yeah I can't find anything in that folder either.
I received the update and applied it. I am not rooted.
I have the XT1687 model.
My current build number is NPN25.137-35
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
bvsbutthd101 said:
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
Click to expand...
Click to collapse
If you have systemless supersu, you should just be able to apply the update after reverting to stock recovery.
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
glight0 said:
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
Click to expand...
Click to collapse
OK, so I tried flashing recovery.img from stock firmware build 33. But the OTA update will not install, instead I get an error after downloading and rebooting (red triangle at recovery mode).
So I tried fully reverting to stock firmware but I decided to skip over erasing userdata. Afterward the OTA downloaded and installed successfully. Keeping userdata does not seem to have caused an issue.
My problem now though is how to get root back without having to wipe userdata after re-flashing TWRP.
Or is this not possible and if I want to root I must first wipe userdata so that TWRP can read internal memory?
bvsbutthd101 said:
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
If your using a custom recovery flash the stock recovery, then go to the stock recovery and using your computer flash using adb sideboard command. I assume you already know how to do this. Hope that helps.
gghose said:
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
Click to expand...
Click to collapse
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone
There's a workaround to disable the "advanced LTE" or whatever it was called, so I did that. But in the meantime until a more "user friendly" means of updating is available, is there a way I can get rid of this nag screen? Way back on an earlier device (Samsung Charge?) I remember manually editing a "build.prop" file or something to match the latest version so I wouldn't keep getting the software update nag. Is there something that will do the same here, or is there a system app I can freeze in TiB?
My best guess is freezing "Moto Actions 03.022.1.4-N" because it's showing "(updated)" on the side.
rellim113 said:
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone .
Click to expand...
Click to collapse
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
glight0 said:
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
Click to expand...
Click to collapse
Strange, reflashed the stock recovery and adb can't see it (adb devices returns nothing). And when trying to install it via the normal OTA way, the stock recovery tries to install but ends with an error.
That's what happened to me when I tried reverting to stock recovery and then trying to install update from phone Settings app.
I ended up having to revert to stock rom to get ota to apply with settings app. But now I am trying to root again but after installing TWRP data is encrypted again. So looks like I will have to wipe data before re-rooting.