Related
Hey all, long time lurker and first(ish) time poster. I have a Nexus 7 (2013) that is great, except for a problem I've been having upgrading from 4.4 to 4.4.2. I am unlocked and rooted, and have the latest version of TWRP installed for the device (flo).
The problem originally started with the OTA. When the OTA would come down and I would click it, it would boot into TWRP and then just restart without installing anything. I attempted this five or six times before trying something else. From there, I downloaded and attempted to install manual update zips for the Nexus to take it from 4.4 to 4.4.2. When I would try and install these, it would say "error executing updater binary in ...". I have tried downloading the updating zip from multiple websites, and I've checked the MD5's, which always match up.
I'm sorry if this is a stupid question, but where can I go from here? I've exhausted my knowledge of what other possibilities are out there, or what could be causing the update to fail.
Thanks!
If the stock finds that any system files have been altered and the md5 check is different from what it should be, a OTA stock update will not go through.
In my personal opinion, flashing a stock root / unrooted image found in the development section of these forums is one of the easier ways of applying an update.
For example if you want a rooted one here's one: http://forum.xda-developers.com/showthread.php?t=2563017
photonate said:
Hey all, long time lurker and first(ish) time poster. I have a Nexus 7 (2013) that is great, except for a problem I've been having upgrading from 4.4 to 4.4.2. I am unlocked and rooted, and have the latest version of TWRP installed for the device (flo).
The problem originally started with the OTA. When the OTA would come down and I would click it, it would boot into TWRP and then just restart without installing anything. I attempted this five or six times before trying something else. From there, I downloaded and attempted to install manual update zips for the Nexus to take it from 4.4 to 4.4.2. When I would try and install these, it would say "error executing updater binary in ...". I have tried downloading the updating zip from multiple websites, and I've checked the MD5's, which always match up.
I'm sorry if this is a stupid question, but where can I go from here? I've exhausted my knowledge of what other possibilities are out there, or what could be causing the update to fail.
Thanks!
Click to expand...
Click to collapse
TheAltruistic is right, that is probably the easiest way to get updated. Another option would be to download the 4.4 factory image and pull the system.img from there and flash that with fastboot then the OTA would work. But really if you go through that you might as well flash the 4.4.2 factory image. I'm not a huge fan of doing the OTA and would rather flash factory images while skipping the userdata image which wipes the device.
wantabe said:
TheAltruistic is right, that is probably the easiest way to get updated. Another option would be to download the 4.4 factory image and pull the system.img from there and flash that with fastboot then the OTA would work. But really if you go through that you might as well flash the 4.4.2 factory image. I'm not a huge fan of doing the OTA and would rather flash factory images while skipping the userdata image which wipes the device.
Click to expand...
Click to collapse
/agreed
from the factory image:
Open flash-all.sh (linux) or flash-all.bat (windows) in a proper text editor (for windows users edit++ is a proper editor- linux people can use their editor of choice):
Find this line:
Code:
fastboot -w update image-razor-kot49h.zip
change it to
Code:
fastboot update image-razor-kot49h.zip
and it will leave your user data intact
oldsoldier2003 said:
/agreed
from the factory image:
Open flash-all.sh (linux) or flash-all.bat (windows) in a proper text editor (for windows users edit++ is a proper editor- linux people can use their editor of choice):
Find this line:
Code:
fastboot -w update image-razor-kot49h.zip
change it to
Code:
fastboot update image-razor-kot49h.zip
and it will leave your user data intact
Click to expand...
Click to collapse
You're right, thanks for pointing that out! I've done that before but I'm so used to flashing the images separately I forgot about it for a minute!
I'm sure I'm not the only one that has had this problem. I've never been able to do the update to 4.2 from 4.1.1. After the download and reboot, the phone gives me an error message. AT&T was no help. I rooted my phone last year but I can't remember how I rooted it. Anyway, I want to update to a new stable ROM. My questions are, do I need to update from 4.1 to 4.2, then 4.3 and then 4.4? Or can I go from 4.1 to 4.4? And if someone could direct me to an easy problem-free stable ROM, I would be most grateful!
Jennifer
southernblonde said:
I'm sure I'm not the only one that has had this problem. I've never been able to do the update to 4.2 from 4.1.1. After the download and reboot, the phone gives me an error message. AT&T was no help. I rooted my phone last year but I can't remember how I rooted it. Anyway, I want to update to a new stable ROM. My questions are, do I need to update from 4.1 to 4.2, then 4.3 and then 4.4? Or can I go from 4.1 to 4.4? And if someone could direct me to an easy problem-free stable ROM, I would be most grateful!
Jennifer
Click to expand...
Click to collapse
If your phone is rooted, you could have difficulties getting an OTA update. You could either unroot your phone from the SuperSU app or you could manually do a 2-step update to 4.1.2 and then 4.3. Unrooting should allow your phone take an OTA update if you are currently on a stock ROM. For manual update process, please follow the instructions below ....
1) Go to the first page in the thread below ...
http://forum.xda-developers.com/show....php?t=2387423
2) Download the 2 zip files under update412.zip and update43.zip respectively to your computer
3) Copy the zip files to a good quality (micro) SD card
4) Place the card in your phone and boot to recovery mode by simultaneously holding down the Volume Up, Home and Power buttons
5) Hold the buttons until you see a blue message flash across the screen. Then release the Power button but continue to hold the Volume Up and Home button until you see the Android image appear. Then release the buttons
6) Use the volume up/down key to scroll to <mount from external storage> and the power button to select
7) Navigate to the first zip file (update412.zip) and install. Wait for installation to finish and your phone to reboot.
8) Complete set up. Check your phone settings. Then power off and reboot to recovery again.
9) Repeat the process for the second update file.
The latest (official) Android version available for the i747 is 4.3 Jelly Bean. Android 4.4 (Kit-Kat) has not been rolled out yet for this phone so if you want the latest stock (official) system, that would be 4.3. If you are looking at a custom ROM, there are quite a few Kit-Kat based ROMs out there.
Larry2999 said:
If your phone is rooted, you could have difficulties getting an OTA update. You could either unroot your phone from the SuperSU app or you could manually do a 2-step update to 4.1.2 and then 4.3. Unrooting should allow your phone take an OTA update if you are currently on a stock ROM. For manual update process, please follow the instructions below ....
1) Go to the first page in the thread below ...
http://forum.xda-developers.com/show....php?t=2387423
2) Download the 2 zip files under update412.zip and update43.zip respectively to your computer
3) Copy the zip files to a good quality (micro) SD card
4) Place the card in your phone and boot to recovery mode by simultaneously holding down the Volume Up, Home and Power buttons
5) Hold the buttons until you see a blue message flash across the screen. Then release the Power button but continue to hold the Volume Up and Home button until you see the Android image appear. Then release the buttons
6) Use the volume up/down key to scroll to <mount from external storage> and the power button to select
7) Navigate to the first zip file (update412.zip) and install. Wait for installation to finish and your phone to reboot.
8) Complete set up. Check your phone settings. Then power off and reboot to recovery again.
9) Repeat the process for the second update file.
The latest (official) Android version available for the i747 is 4.3 Jelly Bean. Android 4.4 (Kit-Kat) has not been rolled out yet for this phone so if you want the latest stock (official) system, that would be 4.3. If you are looking at a custom ROM, there are quite a few Kit-Kat based ROMs out there.
Click to expand...
Click to collapse
Thanks for replying so quickly. When installing 412.zip, I get the following error message after Verifying Current System:
E:Error in tmp/sideload/package.zip (Status 7)
southernblonde said:
Thanks for replying so quickly. When installing 412.zip, I get the following error message after Verifying Current System:
E:Error in tmp/sideload/package.zip (Status 7)
Click to expand...
Click to collapse
Usually, you get a status 7 error message when your recovery mode is out of date. Are you using stock recovery or custom recovery? If custom, would you know what version it is?
Larry2999 said:
Usually, you get a status 7 error message when your recovery mode is out of date. Are you using stock recovery or custom recovery? If custom, would you know what version it is?
Click to expand...
Click to collapse
It looked to be stock recovery. It said Android System Recovery
southernblonde said:
It looked to be stock recovery. It said Android System Recovery
Click to expand...
Click to collapse
You shouldn't have any difficulties flashing the zip if you are on stock recovery. Did you verify the MD5 of the zip you downloaded to be sure it downloaded correctly?
Larry2999 said:
You shouldn't have any difficulties flashing the zip if you are on stock recovery. Did you verify the MD5 of the zip you downloaded to be sure it downloaded correctly?
Click to expand...
Click to collapse
What does MD5 stand for?
Earlier today I tried unrooting and downloading OTA but same problem as before....it cuts out early during installation, reboots and I'm left with 4.1.1
southernblonde said:
What does MD5 stand for?
Earlier today I tried unrooting and downloading OTA but same problem as before....it cuts out early during installation, reboots and I'm left with 4.1.1
Click to expand...
Click to collapse
The MD5 (or checksum verifier) is an algorithm used to verify the authenticity and integrity of digital files. It is statistically improbable for 2 separately created files to have the same MD5 so verifying the MD5 ascertains that the file downloaded correctly and/or has not altered in any way from the original prior to your download. The download source for the files shows the MD5 of the original files so you can use the MD5 checker tool to verify the ones you downloaded. If the MD5 matches, then the file is OK. Otherwise, it didn't download correctly or may have been altered in some way.
http://winmd5.com/
However, the fact that you are unable to get the OTA update after unrooting suggests there may be a different problem with your device. Possible some security encryptions are preventing updates to the system. I'll suggest you back up your files and try doing a factory reset to return the phone to original settings then try the upgrade process again. Prior to upgrading your firmware, however, I would suggest you take the opportunity to free unlock your phone (if not already done). This can only be done on 4.1.1
Larry2999 said:
The MD5 (or checksum verifier) is an algorithm used to verify the authenticity and integrity of digital files. It is statistically improbable for 2 separately created files to have the same MD5 so verifying the MD5 ascertains that the file downloaded correctly and/or has not altered in any way from the original prior to your download. The download source for the files shows the MD5 of the original files so you can use the MD5 checker tool to verify the ones you downloaded. If the MD5 matches, then the file is OK. Otherwise, it didn't download correctly or may have been altered in some way.
http://winmd5.com/
However, the fact that you are unable to get the OTA update after unrooting suggests there may be a different problem with your device. Possible some security encryptions are preventing updates to the system. I'll suggest you back up your files and try doing a factory reset to return the phone to original settings then try the upgrade process again. Prior to upgrading your firmware, however, I would suggest you take the opportunity to free unlock your phone (if not already done). This can only be done on 4.1.1
Click to expand...
Click to collapse
Thanks for all your help, I really appreciate it. I've been working on this phone all day. I'm still having issues with the phone after doing a factory reset and a hard reset. I unlocked it also. The MD5s matched. It downloads the update, then when it goes to install, it gets to 25% then bypasses the rest. The phone still says its 4.1.1. After I did the factory reset only, when I went to update, it was saying there were no updates available...thats what led me to do the hard reset. I'm ready to throw this thing in the ocean. I thought the hard reset would put it back to just out of the box fresh but I still see old apps in there like SuperSU and Mobile Odin Pro. Perhaps those apps are messing it up? This really has me stumped. When I USB it to my laptop and boot up Kies, it says there are no updates available.
I just wiped the cache partition and did a hard reset again. This time I downloaded the update412.zip from the sdcard and I got the same original error: E:Error in tmp/sideload/package.zip (Status 7)
southernblonde said:
Thanks for all your help, I really appreciate it. I've been working on this phone all day. I'm still having issues with the phone after doing a factory reset and a hard reset. I unlocked it also. The MD5s matched. It downloads the update, then when it goes to install, it gets to 25% then bypasses the rest. The phone still says its 4.1.1. After I did the factory reset only, when I went to update, it was saying there were no updates available...thats what led me to do the hard reset. I'm ready to throw this thing in the ocean. I thought the hard reset would put it back to just out of the box fresh but I still see old apps in there like SuperSU and Mobile Odin Pro. Perhaps those apps are messing it up? This really has me stumped. When I USB it to my laptop and boot up Kies, it says there are no updates available.
I just wiped the cache partition and did a hard reset again. This time I downloaded the update412.zip from the sdcard and I got the same original error: E:Error in tmp/sideload/package.zip (Status 7)
Click to expand...
Click to collapse
Please don't give up on your phone yet. It isn't that bad yet. The dreaded error message you are getting means that your recovery system is compromised. Also, once rooted, your phone stays that until specifically unrooted. Even a factory reset will not remove SuperSU and Mobile Odin and the definitive solution to un-rooting is to flash a complete stock image. However, you may be able to fix the recovery issue and get updates in a number of ways. First, you could reflash a complete stock 4.1.1 image via Odin. This will update all system partitions including recovery and should deliver a new and working recovery partition. It will also remove root and make it possible to get an OTA update to 4.3JB. You can download the Odin flashable file from Sammobile.com or from the following link ... http://www.4shared.com/get/zAmWJ54J/I747UCDLK3_I747ATTDLK3_ATT.html
Unzip and extract the *.tar file and flash via Odin.
The second solution would be to use Mobile Odin or Desktop Odin v3.09 to flash a new recovery partition. You'll need the same *.tar file for UCDLK3 but you'd only need to load the recovery partition. If this is successful, you can try the manual update process again.
The final solution would be to flash custom recovery via Odin and then flash the 4.3JB stock restore image via (custom) recovery. You could do the same 2-step manual update via custom recovery. However, a complete stock restore image is available for 4.3 which can be flashed via custom recovery. Please see the first page of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2658486
You can find the TWRP custom recovery Odin flashable file for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
Hope this finally solves it.
Larry2999 said:
Please don't give up on your phone yet. It isn't that bad yet. The dreaded error message you are getting means that your recovery system is compromised. Also, once rooted, your phone stays that until specifically unrooted. Even a factory reset will not remove SuperSU and Mobile Odin and the definitive solution to un-rooting is to flash a complete stock image. However, you may be able to fix the recovery issue and get updates in a number of ways. First, you could reflash a complete stock 4.1.1 image via Odin. This will update all system partitions including recovery and should deliver a new and working recovery partition. It will also remove root and make it possible to get an OTA update to 4.3JB. You can download the Odin flashable file from Sammobile.com or from the following link ... http://www.4shared.com/get/zAmWJ54J/I747UCDLK3_I747ATTDLK3_ATT.html
Unzip and extract the *.tar file and flash via Odin.
The second solution would be to use Mobile Odin or Desktop Odin v3.09 to flash a new recovery partition. You'll need the same *.tar file for UCDLK3 but you'd only need to load the recovery partition. If this is successful, you can try the manual update process again.
The final solution would be to flash custom recovery via Odin and then flash the 4.3JB stock restore image via (custom) recovery. You could do the same 2-step manual update via custom recovery. However, a complete stock restore image is available for 4.3 which can be flashed via custom recovery. Please see the first page of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2658486
You can find the TWRP custom recovery Odin flashable file for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
Hope this finally solves it.
Click to expand...
Click to collapse
I finally did get it fixed last night, actually by one of your solutions there. I had googled the error message (status 7) and I found a thread here on XDA where someone said that because I had used Titanium to delete bloatware when I got the phone, I wouldn't be able to update until it looked right out of the box so I downloaded Odin and flashed 4.1.1. again. Thank God I didn't brick the phone with everything I did to it yesterday. LOL It was finally able to flash 4.1.2 then 4.3. Its disturbing all the threads I see going back to 4.1.1 from 4.3. Is there a huge issue? I'm going to try to find a stable KitKat to flash to. Thanks again for your help!
southernblonde said:
I finally did get it fixed last night, actually by one of your solutions there. I had googled the error message (status 7) and I found a thread here on XDA where someone said that because I had used Titanium to delete bloatware when I got the phone, I wouldn't be able to update until it looked right out of the box so I downloaded Odin and flashed 4.1.1. again. Thank God I didn't brick the phone with everything I did to it yesterday. LOL It was finally able to flash 4.1.2 then 4.3. Its disturbing all the threads I see going back to 4.1.1 from 4.3. Is there a huge issue? I'm going to try to find a stable KitKat to flash to. Thanks again for your help!
Click to expand...
Click to collapse
Glad to know it's now working. I think there's more fuss than fact to the 4.3 question. As far as performance and functionality goes, Touchwiz 4.3 is a major improvement on the older Jelly Bean versions. The main problem, of course, is that the bootloader can not be safely downgraded once you are on 4.3. This is only a problem if you need to free unlock your phone which is only possible on 4.1.1. Otherwise, you can safely flash a KitKat based custom ROM. I would only advise you stick with a stable like you've said and be sure it's one that won't try to mess with your bootloader. Most custom ROMs don't but it wouldn't hurt to make sure.
Larry2999 said:
Glad to know it's now working. I think there's more fuss than fact to the 4.3 question. As far as performance and functionality goes, Touchwiz 4.3 is a major improvement on the older Jelly Bean versions. The main problem, of course, is that the bootloader can not be safely downgraded once you are on 4.3. This is only a problem if you need to free unlock your phone which is only possible on 4.1.1. Otherwise, you can safely flash a KitKat based custom ROM. I would only advise you stick with a stable like you've said and be sure it's one that won't try to mess with your bootloader. Most custom ROMs don't but it wouldn't hurt to make sure.
Click to expand...
Click to collapse
Do you have a recommendation for a stable Kit Kat rom?
I am trying to upgrade to 4.3 on an unlocked, rooted SGH-I747 that I am using internationally (in New Zealand now); however, when I tried to flash a clean 4.1.1 so I could update to 4.3, doing a factory reset and cache wipe, I successfully load the firmware with Odin but then it won't boot past the blue pulsing samsung logo I think I need to flash a new recovery partition, as you suggest below, but I don't know how to do that.
Can anyone help?
Larry2999 said:
Please don't give up on your phone yet. It isn't that bad yet. The dreaded error message you are getting means that your recovery system is compromised. Also, once rooted, your phone stays that until specifically unrooted. Even a factory reset will not remove SuperSU and Mobile Odin and the definitive solution to un-rooting is to flash a complete stock image. However, you may be able to fix the recovery issue and get updates in a number of ways. First, you could reflash a complete stock 4.1.1 image via Odin. This will update all system partitions including recovery and should deliver a new and working recovery partition. It will also remove root and make it possible to get an OTA update to 4.3JB. You can download the Odin flashable file from Sammobile.com or from the following link ... http://www.4shared.com/get/zAmWJ54J/I747UCDLK3_I747ATTDLK3_ATT.html
Unzip and extract the *.tar file and flash via Odin.
The second solution would be to use Mobile Odin or Desktop Odin v3.09 to flash a new recovery partition. You'll need the same *.tar file for UCDLK3 but you'd only need to load the recovery partition. If this is successful, you can try the manual update process again.
The final solution would be to flash custom recovery via Odin and then flash the 4.3JB stock restore image via (custom) recovery. You could do the same 2-step manual update via custom recovery. However, a complete stock restore image is available for 4.3 which can be flashed via custom recovery. Please see the first page of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2658486
You can find the TWRP custom recovery Odin flashable file for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
Hope this finally solves it.
Click to expand...
Click to collapse
southernblonde said:
Do you have a recommendation for a stable Kit Kat rom?
Click to expand...
Click to collapse
I'm not too much into customs. You could, however, take a loot at the new AOSP ROMS or CM 10x...
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
Pfhyde said:
I am trying to upgrade to 4.3 on an unlocked, rooted SGH-I747 that I am using internationally (in New Zealand now); however, when I tried to flash a clean 4.1.1 so I could update to 4.3, doing a factory reset and cache wipe, I successfully load the firmware with Odin but then it won't boot past the blue pulsing samsung logo I think I need to flash a new recovery partition, as you suggest below, but I don't know how to do that.
Can anyone help?
Click to expand...
Click to collapse
You could have installed directly from recovery without first trying to flash a fresh 4.1.1. This would have only been necessary if your 4.1.1 wasn't working right in some way. Try booting into recovery and then doing a wipe/reset. If your phone boots successfully after this, then try the 2-step update -first to 4.1.2 and then to 4.3 via the instructions posted earlier in this thread. Please let me know if this works.
Larry2999 said:
I'm not too much into customs. You could, however, take a loot at the new AOSP ROMS or CM 10x...
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
You could have installed directly from recovery without first trying to flash a fresh 4.1.1. This would have only been necessary if your 4.1.1 wasn't working right in some way. Try booting into recovery and then doing a wipe/reset. If your phone boots successfully after this, then try the 2-step update -first to 4.1.2 and then to 4.3 via the instructions posted earlier in this thread. Please let me know if this works.
Click to expand...
Click to collapse
Thanks for the suggestion. I've tried wiping again from recovery but I get errors (see this thread I started for the details).
-pf
Pfhyde said:
Thanks for the suggestion. I've tried wiping again from recovery but I get errors (see this thread I started for the details).
-pf
Click to expand...
Click to collapse
Since you are apparently successful with Odin, can you try flashing an original stock image rather than the modified (pre-rooted) version you are using. You may download the original version from sammobile.com or do an internet search for it. The zip should be close to 1Gb in size but please make sure to verify the MD5 prior to flashing.
Larry2999 said:
I'm not too much into customs. You could, however, take a loot at the new AOSP ROMS or CM 10x...
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
You could have installed directly from recovery without first trying to flash a fresh 4.1.1. This would have only been necessary if your 4.1.1 wasn't working right in some way. Try booting into recovery and then doing a wipe/reset. If your phone boots successfully after this, then try the 2-step update -first to 4.1.2 and then to 4.3 via the instructions posted earlier in this thread. Please let me know if this works.
Click to expand...
Click to collapse
Larry2999 said:
Since you are apparently successful with Odin, can you try flashing an original stock image rather than the modified (pre-rooted) version you are using. You may download the original version from sammobile.com or do an internet search for it. The zip should be close to 1Gb in size but please make sure to verify the MD5 prior to flashing.
Click to expand...
Click to collapse
I did try an original stock, originally. I only tried the rooted stock after the original didn't work (got stuck with pulsing blue samsung logo). I'll try the one from sammobile.com (but I think that's where I got it the first time) and report back after I get off work late tonight.
-p
I just got a message that I have an update for 4.4.4 on my nexus 7 2013 but when I updated and installed, i'm still 4.4.3.
I rooted by using Nexus Root Toolkit by WugFresh.
This happened for 4.4.3 as well from 4.4.2.
omgsy said:
I just got a message that I have an update for 4.4.4 on my nexus 7 2013 but when I updated and installed, i'm still 4.4.3.
I rooted by using Nexus Root Toolkit by WugFresh.
This happened for 4.4.3 as well from 4.4.2.
Click to expand...
Click to collapse
What does the error say? Unexpected contents somewhere in the system? Basically, being rooted has nothing to do with whether the OTA fails or not. It usually is due to the system being modified (having Xposed Installed, system apps deleted, etc.). When it's trying to update, it will tell you why it failed.
charesa39 said:
What does the error say? Unexpected contents somewhere in the system? Basically, being rooted has nothing to do with whether the OTA fails or not. It usually is due to the system being modified (having Xposed Installed, system apps deleted, etc.). When it's trying to update, it will tell you why it failed.
Click to expand...
Click to collapse
when it rebooted, it just took me to TWRP recovery mode screen and i just rebooted and nothing came up. Just 4.4.3 still.
I did delete system apps such as google plus and stuff like those and have Xposed installed.
Do i have to use factory images and flash it that way?
I did it that way for 4.4.3 from 4.4.2
omgsy said:
when it rebooted, it just took me to TWRP recovery mode screen and i just rebooted and nothing came up. Just 4.4.3 still.
I did delete system apps such as google plus and stuff like those and have Xposed installed.
Do i have to use factory images and flash it that way?
I did it that way for 4.4.3 from 4.4.2
Click to expand...
Click to collapse
Well, even if you were stock/rooted with TWRP recovery, it would fail if you try to update the normal way within Android because it is expecting to boot into stock recovery. Since you have a custom recovery, it doesn't do anything more than boot into recovery. You could flash the OTA zip using TWRP, but it would fail as you have deleted system apps and have Xposed installed. Xposed isn't that big of a deal, as you can just uninstall it from with the Xposed Framework installer, then update, then re-install Xposed without losing any settings. Since you deleted system apps, you could reinstall them individually. HOWEVER, it looks like the easiest thing to do is to flash the factory image like you did going from 4.4.2 to 4.4.3 (I assume you didn't flash userdata). Another thing to do would be to just flash the system image from the 4.4.3 factory image, then flash the OTA zip in TWRP. It's really just a matter of your preference. But any of those ways would work.
Hi All,
My Nexus 7 LTE is rooted with TWRP.
I've downloaded the OTA for 4.4.3 from one of the posts in the forums. It updates my razorg from KOT49H to KTU84L.
After using adb sideload, the update zip file is transferred successfully to my device, but it fails with the error message
Code:
"/system/bin/surfaceflinger" has unexpected contents.
error excuting updater binary in zip '/data/media/0/sideload.zip
Does anyone have any idea what could be causing the update to fail?
I've already restored to a stock kernel (from franco kernel) as well as uninstalled xposed framework.
Thanks!
Install stock recovery and take ota as normal. Then reinstall twrp and reroot.
If you fail update I have a backup I made with twrp you can use. Just need to extract it to your twrp backup folder and restore. It's 100% stock and was made after wiping data. Can't post a link to my Dropbox right now because of my post count but if you need it I an send it to you by other means.
Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.
endlesstrail said:
Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.
Click to expand...
Click to collapse
To get the OTA to work with either a stock or custom recovery the unexpected contents error will have to be fixed first. Somehow the surfaceflinger file was changed, that's a new one for me so I have no idea what could have changed it. I could upload a copy of mine if you want to try it but I do have the wifi version and don't know if they are the same. Otherwise you will need to fastboot flash the system image for the version you are running now for the update to work. Instead of doing that I would download the 4.4.3 factory image and extract the radio, system, and boot images and fastboot flash those. The bootloader did not change so that does not need to be flashed. Before flashing the images I would download the newest supersu zip and put it in your device storage, then flash the images, once that is done do not reboot, boot into recovery instead and flash the supersu zip then wipe cache and dalvik then reboot. Should take less than 15 minutes. ; )
You could also flash the factory image but that will install the stock recovery, lose root and completely wipe your device. If you are using windows you can open the flash-all.bat with a text editor like notepad and remove the -w from the text, that will prevent the userdata image from being flashed which wipes your device.
Thanks for your reply, wantabe.
I guessed as much, that if I couldn't figure out what changed the surfaceflinger, I might as well do a complete flash back to stock, which was what I did. Now it's just a matter of flashing back TWRP, restoring all the apps and waiting for 4.4.4 :good:
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Installing '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: Package expects build fingerprint of google/razor/flo:5.0/LRX21P/1570855:user/release-keys or google/razor/flo:5.0.1/LRX22C/1602158:user/release-keys; this device has Android/omni_flo/flo:5.0/LRX21V/dees_troy11241447:eng/test-keys.
Package expects build fingerprint of google/razor/flo:5.0/LRX21P/1570855:user/release-keys or google/razor/flo:5.0.1/LRX22C/1602158:user/release-keys; this device has Android/omni_flo/flo:5.0/LRX21V/dees_troy11241447:eng/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'
Error flashing zip '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'
Click to expand...
Click to collapse
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
indiecognition said:
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
Click to expand...
Click to collapse
Same issue for me, with this strange fingerprint.
I tried to flash it by side load and TWRP 2.8.2.2 with th esame result!:crying:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom from Scrosler found here http://forum.xda-developers.com/nexu...rx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed (no wipes) the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything. Seriously easy, guys!
FWIW the Factory Images are a super easy way as well.
I went from 4.4.4 to 5.0 with Factory Images and the -w flag in the batch file removed (to prevent wiping data), then rooted with Chainfire Auto Root (CFAR). Whole process took about 10 minutes (less download time).
I then went from 5.0 to 5.0.1 in the same fashion. I tried to sideload the OTA but it failed verification (/recovery and /system (root, I'm guessing)) so rather than mess with flashing both then doing the OTA, I just downloaded the 5.0.1 factory Factory Image, removed the -w flag again, and took the same steps as above. Ran the batch, ran CFAR and I was done.
Edit: for clarifiaction, I did these like two weeks apart, not back to back. I also did an upgrade for a friend on his N7 and went from 4.4.4 to 5.0.1 with Factory Images exactly as above. Although I didn't remove the -w flag for him because his bootloader was locked, so it was already wiping for that. Flashed Factory Images, ran CFAR, done.
indiecognition said:
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
Click to expand...
Click to collapse
You can flash the 5.0.1 factory image without wipe (did the same and it works well till now). Just extract system and boot.img, flash them via fastboot, wipe cache and reboot, thats it.
I may have a fix
I was having the same issue on my Nexus 5...(valentine edition ) I recieved the OTA 5.0.1 update and tried to install it automatically. (Not manually) It failed, so once it did i went into Recovery Mode and I cleared my data partition cache and wiped my dalvik cache and once i rebooted i got the "Android is upgrading" screen. I'm assuming this should fix it but I havent finished upgrading to check. Try this and let me know!
Clutchisback said:
I was having the same issue on my Nexus 5...(valentine edition ) I recieved the OTA 5.0.1 update and tried to install it automatically. (Not manually) It failed, so once it did i went into Recovery Mode and I cleared my data partition cache and wiped my dalvik cache and once i rebooted i got the "Android is upgrading" screen. I'm assuming this should fix it but I havent finished upgrading to check. Try this and let me know!
Click to expand...
Click to collapse
"Android is upgrading" after clearing the dalvik cache is normal. It is just optimizing the apps for the runtime.
Well since you have recovery installed, you can try a lot of installations. just don't forget to backup.
fury683 said:
"Android is upgrading" after clearing the dalvik cache is normal. It is just optimizing the apps for the runtime.
Click to expand...
Click to collapse
Yea you were right, it ended up doing nothing... :crying:
Nexus 5 manual download solution
indiecognition said:
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
Click to expand...
Click to collapse
I finally got the install done manually...I took the liberty of writing up some tips to and solutions to all the problems i encountered, check out my thread here: http://forum.xda-developers.com/goo...al-install-t2978147/post57615642#post57615642
I think you should just be able to just tick "Force Flash" in Wug's NRT and this should fixed the mismatch issue when you flash the images. I think he said in another thread that Google hosed something in their Flash-all.bat file which is causing the issue.