Original Shield tab 4.1 OTA update - Shield Tablet General

Doesn't seem like there will be a US LTE version again... hoping there will be a RoW version that someone will eventually create a flashable zip...

Hey Guys -
Yeah, just saw this was available for my Original Shield Tablet (rooted) few minutes ago. Aside from wiping and installing OS all over again, what's the best method to upgrade and ensuring I still have root afterwards + retain installed apps & settings?
I use an SD card in Internal mode if that makes a difference. Thanks!

Just got the Notication for the wx-un-do upgrade.
Now looking for the full ota update.
Send from my .I. .I.

Don't worry, it doesn't seem to work. OTA downloads, boots and back into system again. Asks to download ota again, version number unchanged. I've tried it 3 times already.
Whatever Nividia can do wrong, they will do wrong. It's so frequent it's no longer funny.

When you are rooted and have a custom recovery installed you need the full Ota zip file.
The incremental ota update won't work.

Snah001 said:
When you are rooted you need the full Ota zip file.
The incremental ota update won't work.
Click to expand...
Click to collapse
If you're telling me, then my device is unrooted, stock everything. Not just me, got another guy on the Shield forums saying the same thing hehe.....
on a side note, mine is a ROW LTE. Maybe those with wifi sets have better luck. But the other guy I mentioned has a wifi set, and it didn't work for him.

You have a custom recovery installed?

I search the full WiFi EU ROM. Can anybody help me

Snah001 said:
You have a custom recovery installed?
Click to expand...
Click to collapse
Stock EVERYTHING.
Have no intention to root this one because the battery replaced old version is already rooted.
---------- Post added at 03:17 AM ---------- Previous post was at 03:16 AM ----------
clawwulf said:
I search the full WiFi EU ROM. Can anybody help me
Click to expand...
Click to collapse
Be patient. It will come. many still asleep now.

When we have the full OTA zip then the link will be posted here immediately 4sure.

Yea, I saw mine had the 4.1 update and decided to wait to sideload it and not do the OTA update. Waiting for a TWRP version.

C'mon, RoW LTE version... can't wait

JohnK71 said:
Yea, I saw mine had the 4.1 update and decided to wait to sideload it and not do the OTA update. Waiting for a TWRP version.
Click to expand...
Click to collapse
You should be able to do a FULL OTA download, offload it - then TWRP it.

Once they post it on their site, we'll be able to flash it one way or another, just a matter of time. I'm disappointed it's only through the Mar update though...

Release notes here:
https://shield.nvidia.com/support/shield-tablet/release-notes/1

Incremental OTA works just fine on rooted tab + TWRP. Just keep in mind that it will replace your recovery for the stock one and you will loose root.

Worked fine for me. Completely stock.

Didn't work for me on stock row lte rom with multirom. Does go into mr twrp but fails install with an error 7.

Snah001's posting #24 of 2016.05.13.Fr.09:35 PM solved it all.
Before that, I ran into Failure as follows with "Upgrade" on my rooted RoW LTE.
< 1. > Hitting [[ Restart to install ]] made it into Team Win Recovery Project v3.0.0-0, where it logged the following :::
Running OpenRecoveryScript – Installing ZIP :::
Updating partition details » Done.
Full SE Linux support is present.
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file.
Skipping MD5 check : no MD5 file found.
:::
After that, I could reboot from TWRP, get another identical upgrade notification, and loop through as_many times as I'd like.
< 2. > Installing the upgrade manually from TWRP resulted in :::
Source : nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_664.1902:user/release-keys
Target : nvidia/wx_un_do/shieldtablet:6.0.1/MRA58K/40827_700.6895:user/release-keys
Verifying current system...
Package expects build fingerprint of :::
nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_664.1902:user/release-keys
or nvidia/wx_un_do/shieldtablet:6.0.1/MRA58K/40827_700.6895:user/release-keys;
this device has ::
nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_658.5732:user/release-keys
:::
Updater process ended with ERROR : 7
Error installing zip file '/data/data/com.nvidia.ota/app_download/PUBLIC92c9 4d59.zip'
Updating partition details » Done.
» Failed.
< 3. > Skipping all checks in OTA 4.1 LTE's "PUBLIC92c9fefb721b31eb2dc26fb6ac2b4d59.zip\META-INF\com\google\android\updater-script" seems no_good idea either, as I ended up without Notification Drawer and without Android Settings app. }} I had to restore a backup in TWRP to regain normal functionality.

Didn't manage to the OTA URL (somehow it's not showing in my logcat). But, I managed to grab it out and install manually with TWRP. Here it is:
Code:
https://mega.nz/#!XggijAhZ!Depd8u5nwMNt_wNcjbWmbT_6EGJB4OejmTv8eMSte9Y
EDIT: forgot to mention that this is the LTE ROW version.

Related

[REF][How To] Return to STOCK Recovery (IF rooted) and sideload OTA

By now, with all the OTA's, unless you are brand new to the 2013 X, you know you have to have stock recovery on your phone for an OTA Update or Soak Test to install, and your system can't be modified too much or it will fail the pre-flash validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
If you have an unlocked bootloader, and rooted by flashing a 3rd party recovery (like TWRP, CWM, Philz, etc) and installing SuperSU, you likely didn't put stock recovery back on your phone.
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
The steps in this post help you do that, or get ready to do that, in case you are not near your PC when an OTA comes, of if you just don't want to use your PC.
NOTE: If you have changed too much of stock that the OTA fails, please see -> [FAQ] How to prepare for and take an OTA update (All Carriers)
NOTE: the following worked when updating 4.4 to 4.4.2, and 4.4.2 to 4.4.4 on my VZW Dev Edition X. Since Lollipop has not yet been released for my phone, I can't test this yet.
Note: If you have flashed your phone with another carrier's ROM, or have only flashed "parts" of your phone, these steps may not work!! Or they may cause you to brick!
NOTE: If your Bootloader version does NOT match the one for your phone's software version, taking an OTA could brick your phone!
You must have an Unlocked Bootloader and be rooted for these steps to work:
Obtain the STOCK Moto Recovery image, and TWRP image, for your phone:
On you phone, go App Drawer -> Settings... Make note of what is listed under System Version, and Android Version.
Visit one of the sites listed in -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 and obtain the EXACT same ROM/SBF file that is currently on your phone. Download the ZIP to your PC.
Unzip or extract the RECOVERY.IMG file from the SBF ZIP file.
Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading)
the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053
Flashing Recovery
Place your stock recovery.img, the latest TWRP img, and the latest SuperSU.zip in your phone's DOWNLOAD folder.
Install Rashr.
On your phone, launch Rashr.
Scroll down and select other from storage
Browse and select your stock recovery
When it completes, pick the option to reboot to stock recovery.
Your device should reboot and display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. You should be in Stock recovery now.
Reboot your phone as normal.
To reflash TWRP or other custom recovery, as long as you are still rooted, you can repeat the same steps, selecting your custom recovery in step 5.
How to SIDE LOAD an OTA.ZIP via this process
If your carrier has started the push of the OTA ZIP for your phone, but you haven't received it, and you've found the correct OTA ZIP posted online and would like to flash it, the following steps can be used...
Download the OTA ZIP file (usually named as BLUR_XXX.XXX.XXX.zip, where XXX.XXX.XXX is the build number the ZIP will update) to your phone's /SDCard
Perform steps 1-7 under Flashing Recovery above to flash STOCK recovery onto your phone, and reboot into Stock Recovery.
Use the Vol Down key to scroll to Apply Update From SDCard, and press the Power key to select.
Use Vol Down key to scroll to your OTA zip file, and press Power to select.
The install will begin by verifying the update package, then verifying files on your phone match.
If the install fails, it will be reported on the screen, along with why. (usually because you have modified system files, or are not on the correct ROM version). You need to fix these errors and try again.
If verifications are successful, the patching process steps will begin. This may take several minutes.
Your phone should report Script Succeeded and Install from sdcard Complete.
Ensure Reboot System Now is highlighted, and press the Power key to reboot the phone.
The initial reboot may take longer than a regular reboot.
Note: You will see Android Is Upgrading or Optimizing screen during the boot process, that is normal.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
How to Root with unlocked bootloader...
If you unlocked your bootload by getting the code from Moto, after taking the OTA you may root by following ->http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 NOTE: while the thread is titled for 5.1, it works on older Android versions as well.
Good work KidJoe :laugh::good:
I guess this will be more relevant as Soaks start heading out for the 2013 X...
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
ks73417 said:
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
Click to expand...
Click to collapse
Yes, the OTA zip is usually stored in /cache (at least is is on the 2013 X, and my past Moto phones). it is usually named for the rom it is upgrading, not what the upgrade takes you to.
I don't see why this wont work on the 2014 X, as it did on older motos too.
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
In TWRP you can make a nandroid backup. I've never done it. I haven't had need because I run stock. If I need to reflash, I just reflash the same SBF I've been running.
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
ejlmd said:
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
Click to expand...
Click to collapse
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
KidJoe said:
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
Click to expand...
Click to collapse
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
there any way to make a dump the stock recovery in Lollipop, without the need root?
ejlmd said:
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
Click to expand...
Click to collapse
Yeah, OTA Update files are often named including the version the phone must be on, not the version it takes the phone to.
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
It's ABSOLUTELY BEST you avoid the update............but....
If you can't, it is highly recommended that you clean flash it...kind of the only choice. Flash the 4.4.4 Brazilian stock ROM. And install the update from recovery. You can reroot after adding TWRP back.
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Please see the LINK in my signature for sites to download stock SBF files
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
As explained elsewhere... Xposed makes changes to /system which cause OTA updates to fail their pre-flash validation checks.
It is recommended to boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip then uninstall XPosed.
You will also need to undo any changes to /system or other parts the the OTA tries to validate before installing, or else it will fail.
You are correct that a newer version of Xposed is needed.
You may also want to wait on trying the 5.0.2 Leaks because if they are an early limited early test version, rather than a soak which is nearly ready to be pushed to all, you could be stuck on this version until an SBF leaks.
Update
Does anyone know how to return to stock recovery for lollipop? New update came up today but I have TWRP.
upload the stock recovery lollipop please!!!!
Good work, love your detailed explanations always .

[How to] Upgrade to 4.5.5.1 (or other 4.5.x) with root in TWRP:

Update2: Updated for FireOS 4.5.5.1. Note that you can root 4.5.5.1 directly via Kingroot. With root, you could get TWRP to work, and re-install any FireOS 4 or 5 with all the goodies. The instructions to get TWRP working are here (you need to flash 4.5.3 bootloaders if you do not start with FireOS 4.5.3 !!!) : http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Update: I had a couple of knee-jerks, but realized that I can make TWRP say "full_ariel" (I've changed the string), which enables the standard Amazon update files to work !!! I did test the modified TWRP (and the attached zips), everything works fine.
This 4.5.5 update provides no perceptible difference with 4.5.4, and everything has been running smoothly for me for the past few weeks. So out of the general principle I do recommend upgrading!
If you are just joining us, and have a pristine Fire HD, head over here to get your fire rooted and TWRP installed [all steps up to and including 3) ] :
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
With TWRP installed, there is a quicker way to install 4.5.5, without changing the update file (in contrast to my earlier instructions for 4.5.4). This is a dirty flash, and will keep all the prior settings and programs (if you have not had GAPPS yet, see additional instructions below):
0) Turn off wireless (airplane mode)
If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
1) Boot into TWRP, flash the attached 4.5.3_twrp_recovery_full_ariel_string.zip. Reboot to recovery (TWRP)
2) While in TWRP (this modified version self-identifies as full_ariel) :
a) flash the respective Amazon ROM 4.5.x update (the latest one?): http://forum.xda-developers.com/fire-hd/general/fire-hd-rom-links-t3173102 (rename to zip before flashing)
b) Must do this (!!!) - flash attached 4.5.3_twrp_recovery_uboot.zip
c) flash attached make_space_v01_fireos4.zip to remove moffice and weather in order to increase space in /system.
d) flash Pico (Uni) GAPPS for KK http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html [if you did not have GAPPS before, skip this for now, and come back after Step 3) ]
e) wipe cache and dalvik
f) before reboot say yes to root
3) Boot into fireOS (wait for it to upgrade)
a) install SuperSu
b) disable OTA updates [in ES Explorer rename /system/priv-app/DeviceSoftwareOTA.apk to *apk_ ] - The script in make_space*zip already renamed this file automatically, so nothing to do here.
c) install Xposed. Note if you are using 4.5.5.1, you'll need to get the Xposed installer from here in order to address SDK version 19 error :
http://forum.xda-developers.com/showpost.php?p=64063168&postcount=62
d) install Busybox
Optional 4) : if you did not install GAPPS in 2), boot to TWRP, and install GAPPS
That's it! Whatever you had working before, should be working now the exact same way.
If you prefer a manual way where you repackage the 4.5.5 update file (and perhaps remove some apps from /system), see these instructions (the updater-script is the same) :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
This package is for "full_ariel" products: this is a "omni_ariel"
E:Error executing updater binary in zip '/sdcard/Download/update-kindle-20.1.5.5_user_455001420.zip'
Click to expand...
Click to collapse
Sario27 said:
Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
Click to expand...
Click to collapse
Yep, indeed! I wonder if TWRP could be patched such that the device is being identified as "full_ariel" even when rooted. Otherwise repackaging these ROM zips is a chore ...
bibikalka said:
Yep, indeed! I wonder if TWRP could be patched such that the device is being identified as "full_ariel" even when rooted. Otherwise repackaging these ROM zips is a chore ...
Click to expand...
Click to collapse
Having said that... is there a version of 4.5.5 that will work with root? I can repackage myself I suppose, but it is a mess to navigate that script...
Sario27 said:
Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
Click to expand...
Click to collapse
meatwad12 said:
Having said that... is there a version of 4.5.5 that will work with root? I can repackage myself I suppose, but it is a mess to navigate that script...
Click to expand...
Click to collapse
I've updated the instructions. As the first step, you flash the modified recovery (which says "full_ariel"). This modified recovery will accept the standard Amazon update file. After the update is done, I have you flash the standard TWRP back (just in case) together with 4.5.3 bootloaders.
I don't understand new title, "Upgrade to 4.5.5 (or any 4.5.x) with root in TWRP:" Isn't this just for upgrading to 4.5.5? The files are for 4.5.5, so you wouldn't use it to upgrade to 4.5.4, right? (Yes, I'm going to post a pointer to all the guides. The choices are confusing even me, and I practically live here!) Also, if you see fit, could you add [How To] to title so this stands out with other upgrade guides? yr friend, Do consistency-my-middle-name Looper.
DoLooper said:
I don't understand new title, "Upgrade to 4.5.5 (or any 4.5.x) with root in TWRP:" Isn't this just for upgrading to 4.5.5? The files are for 4.5.5, so you wouldn't use it to upgrade to 4.5.4, right? (Yes, I'm going to post a pointer to all the guides. The choices are confusing even me, and I practically live here!) Also, if you see fit, could you add [How To] to title so this stands out with other upgrade guides? yr friend, Do consistency-my-middle-name Looper.
Click to expand...
Click to collapse
Wow, you are a hard man to please I've put a few changes in there, trying to make it more clear.
The procedure works for 4.5.4 as well, so that's why I try to keep things fairly generic.
bibikalka said:
The procedure works for 4.5.4 as well, so that's why I try to keep things fairly generic.
Click to expand...
Click to collapse
So would you say this supercedes http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613? Is this method "better?' thx
DoLooper said:
So would you say this supercedes http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613? Is this method "better?' thx
Click to expand...
Click to collapse
Potentially this will supersede this :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
The difference is mainly not having to mess around with the update file (which has it's uses, if one wants to shrink the size of "system").
bibikalka said:
I've updated the instructions. As the first step, you flash the modified recovery (which says "full_ariel"). This modified recovery will accept the standard Amazon update file. After the update is done, I have you flash the standard TWRP back (just in case) together with 4.5.3 bootloaders.
Click to expand...
Click to collapse
This worked great for me. I have 4.5.5 running with the stock amazon ROM after following these instructions. Great work thank you!
---------- Post added at 03:19 PM ---------- Previous post was at 02:24 PM ----------
One problem...
I'm having a heck of a time trying to block ads in 4.5.5. I've tried the adb command pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.lockscreenupdateS ervice as mentioned in another thread but with no luck. Did Amazon change something in the structure of 4.5.5 that renders this method unworkable? Is there another way?
meatwad12 said:
I'm having a heck of a time trying to block ads in 4.5.5. I've tried the adb command pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.lockscreenupdateS ervice as mentioned in another thread but with no luck. Did Amazon change something in the structure of 4.5.5 that renders this method unworkable? Is there another way?
Click to expand...
Click to collapse
Did you put a space in "S ervice?" There is none, but it may display that way. So if you did, do it with no space and reboot afterwards if ads don't go away immediately. The other way is JMZ fire tool, but that does a chmod on ad folder and displays the "killed ads" message with every boot.
Please let me know if the pm block pm disable works or not. Thanks!
Looks like I'm good! I tried it several different ways (block vs. disable; with space and without) and it appears to have taken hold after a reboot. We can chalk this one up to user error. Thanks for the response.
meatwad12 said:
Looks like I'm good! I tried it several different ways (block vs. disable; with space and without) and it appears to have taken hold after a reboot. We can chalk this one up to user error. Thanks for the response.
Click to expand...
Click to collapse
Or u can upgrade to lollipop. Ads are disabled by default on lollipop. Here is the thread to lollipop with root. http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I followed the instructions and tried flashing gapps before the initial boot into 4.54 and also after booting but I get the same error. "insufficient storage space available in system partition"
I am flashing this version
pa_gapps-modular-pico(uni)-4.4.4-20150308-signed.zip it is 39,105kb.
this is on the 8gb model of the kindle hd 7, not sure if the 16 has a bigger system partition
mehmehmeh said:
I followed the instructions and tried flashing gapps before the initial boot into 4.54 and also after booting but I get the same error. "insufficient storage space available in system partition"
I am flashing this version
pa_gapps-modular-pico(uni)-4.4.4-20150308-signed.zip it is 39,105kb.
this is on the 8gb model of the kindle hd 7, not sure if the 16 has a bigger system partition
Click to expand...
Click to collapse
Did you flash the older 4.5.4 ? Or the newer 4.5.5 ?
Can you check how much free space you have in /system as is? (DiskUsage app in the store)
In any event, and easy quick hit (20Mb) is to remove something like /system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
You can remove more, as per this :
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3
flashed the newer 4.5.5. Will try later tonight, didn't get the amazon update disabled and woke up to a fire os 5 tablet. So I have to downgrade again
mehmehmeh said:
flashed the newer 4.5.5. Will try later tonight, didn't get the amazon update disabled and woke up to a fire os 5 tablet. So I have to downgrade again
Click to expand...
Click to collapse
Well, as they say, practice makes perfect !
I am surprised it managed to install itself with TWRP present instead of the stock recovery ...
Can you please upload the attachments to a file hoster cause the servers from xda are slow 14 kbps and downloads cancels!
bibikalka said:
Did you flash the older 4.5.4 ? Or the newer 4.5.5 ?
Can you check how much free space you have in /system as is? (DiskUsage app in the store)
In any event, and easy quick hit (20Mb) is to remove something like /system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
You can remove more, as per this :
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3
Click to expand...
Click to collapse
Thanks for the tip!
Ran into the same issue while trying to upgrade my rooted 4.5.3 gapps Firehd 7..
Mhm Ok now I'm running into issues when trying to update the google play services, it always fails saying "not enough space available".
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3
I've moved all the odexed system APKs mentioned in this post to /data/apps and I have 1.5gb free on the "sdcard".
:/
*Edit*
Nvm, found the reason...it's because I allready had gapps installed through jmz's tool and it blocked play services updates from being installed, because back then a play services update would break the entire thing again.
So I had to do these additional steps from this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
0) If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
Click to expand...
Click to collapse
@op maybe include it in your updated guide for ppl who allready had gapps and used jmzs handy tool a couple months ago.

COS 13.1 ZNH2KAS1KN - New Update for OPO

Cyanogen recently pused out COS13.1 for our beloved OPO.
Here is the link to OTA :-
http://builds.cyngn.com/incremental/bacon/cm-bacon-64003595ee-to-ced5430fc0-signed.zip 378 MB
"Upgrade your device to Cyanogen OS 13.1. Based on Android™ 6.0.1, Marshmallow, this update provides critical security fixes, improved stability/performance, product upgrades, and new mods for Cortana, OneNote, Microsoft Hyperlapse, Skype, and Twitter."
Changelog :-
Complete changelog currently unknown.
1st June Android Security patch level
Some MOD Addons.
Skype integration in dialer.Removal of NextDialer. Looks like stock dialer.
Hyperlapse mod in camera.
Update Instruction :-
Stock Unrooted Devices
To flash OTA you need stock unrooted phone.
Flash via stock recovery.
Rooted devices
1st unroot the device or flash system image from previous update then flash the OTA from recovery.
Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.
gigatroned said:
Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.
Click to expand...
Click to collapse
try flashing from stock recovery !
gauravsaini964 said:
try flashing from stock recovery !
Click to expand...
Click to collapse
Same for me lol
gigatroned said:
Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.
Click to expand...
Click to collapse
flash the stock system with the correct recovery over, then flash update
stock recovery here. in the middle of the update it gives me an error.
All the page with red fonts, after a few second the message disappear and I have not been fast enough to read.
after reboot everything it is normal, but still COS 13.0
dam76 said:
stock recovery here. in the middle of the update it gives me an error.
All the page with red fonts, after a few second the message disappear and I have not been fast enough to read.
after reboot everything it is normal, but still COS 13.0
Click to expand...
Click to collapse
Try to install the previous update, and then with recovery stock reinstall the last update.
alijoregon said:
Try to install the previous update, and then with recovery stock reinstall the last update.
Click to expand...
Click to collapse
thanks, I tried installing previous update (same file cm-bacon-64003595ee-to-ced5430fc0-signed.zip that gave me Marshmallow in the first place)
but it gave me the same error again!
This time I took a screenshot with an old phone:
http://i.imgur.com/sW5NTyb.jpg
dam76 said:
thanks, I tried installing previous update (same file cm-bacon-64003595ee-to-ced5430fc0-signed.zip that gave me Marshmallow in the first place)
but it gave me the same error again!
This time I took a screenshot with an old phone:
http://i.imgur.com/sW5NTyb.jpg
Click to expand...
Click to collapse
Is your previous update the full OTA? The incremental is not valid. If you did root any time your system is modified. You must reinstall the full zip.
alijoregon said:
Is your previous update the full OTA? The incremental is not valid. If you did root any time your system is modified. You must reinstall the full zip.
Click to expand...
Click to collapse
yes: my system was rooted, so I had to perform a full wipe and install what I think to be the full zip (cm-bacon-64003595ee-to-ced5430fc0-signed.zip 377MB)
where can I download the full zip just to make sure?
does the full zip update wipe apps and data?
thanks in advance for the help
dam76 said:
yes: my system was rooted, so I had to perform a full wipe and install what I think to be the full zip (cm-bacon-64003595ee-to-ced5430fc0-signed.zip 377MB)
where can I download the full zip just to make sure
thanks in advance for the help
Click to expand...
Click to collapse
This time you needn't do full wipe. Only installing the full OTA via TWRP and then you must come back to the original recovery and install the incremental update. By this way you will have the last update.
All the links are in a post on this web, I don't remember the name of the post, but is easy to find.
alijoregon said:
This time you needn't do full wipe. Only installing the full OTA via TWRP and then you must come back to the original recovery and install the incremental update. By this way you will have the last update.
All the links are in a post on this web, I don't remember the name of the post, but is easy to find.
Click to expand...
Click to collapse
thanks! here I found the CM13.0 Signed flashable zip
cm-13.0-ZNH0EAS2JK-bacon-signed.zip 691 MB
rebooting
applying full zip via stock recovery
rebooting - everything apparently the same
applying update via stock recovery
rebooting... optimizing apps...
success! COS 13.1 up and running! (phone very warm though)
thank you very much for the support. (why messing with android must be so complicated?)
Hi, i also have an ERROR while installing the OTA.
1. I had updated to CM13 via OTA.
2. Since I had an issue with stuck lockscreen , installed TWRP and wiped cache ( Stock CM recovery was not helping). Phone worked great since then.
3. TWRP was not longer there, instead CM Recovery.
4. New update has arrived, but i get an "ERROR" word in the middle of screen while installing.
What can I do?
Thank you in advance for your response.
Seems to be fine. Minimal fixes but at least something...
---------- Post added at 11:29 AM ---------- Previous post was at 11:28 AM ----------
leokook said:
Hi, i also have an ERROR while installing the OTA.
1. I had updated to CM13 via OTA.
2. Since I had an issue with stuck lockscreen , installed TWRP and wiped cache ( Stock CM recovery was not helping). Phone worked great since then.
3. TWRP was not longer there, instead CM Recovery.
4. New update has arrived, but i get an "ERROR" word in the middle of screen while installing.
What can I do?
Thank you in advance for your response.
Click to expand...
Click to collapse
thanks! here I found the CM13.0 Signed flashable zip
cm-13.0-ZNH0EAS2JK-bacon-signed.zip 691 MB
rebooting
applying full zip via stock recovery
rebooting - everything apparently the same
applying update via stock recovery
rebooting... optimizing apps...
success! COS 13.1 up and running! (phone very warm though)
thank you very much for the support. (why messing with android must be so complicated?)
USER ABOVE YOU POSTED HOW HE DID IT. FOLLOW HIS GUIDE AND THANK HIM
anyone have problem with titanium backup on latest ota s1kn ? i cannot freeze and restore app , any idea ? su version 2.65
Are there also any changes with the camera?
prototyp01 said:
Are there also any changes with the camera?
Click to expand...
Click to collapse
Hyperlapse got added !
Is overall camera quality better than before? Or is Hyperlaps the only change?
prototyp01 said:
Is overall camera quality better than before? Or is Hyperlaps the only change?
Click to expand...
Click to collapse
I am sure some one else will be able to answer this better
I haven't flashed this update yet neither I am camera enthusiast.
Updated on this one yesterday, and I regret it....my phone now charges very slow, it took 8 hours to fully charge, dont have this issue before, tried everybody else fixes, but did nothing...do anybody has the flashable ZIP on the previous version and can be flashed using stock recovery?
Thanks

How do I update to Android 7.0 on the Axon 7 (USA Model) with TWRP Recovery installed

I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2

LE S3 20 & 21s[official]with OTA updatable[Lock bootloader]

This is totally CLEAN and Typically ENGLISH (OFFICIAL) version that means no chinees APPS no issue.
Donot forget to make a backup before starting.
Steps to Follow: (FOR TWRP installed user)
1. Download 20s OTA file from here.
2. Download 21s OTA file from here. (Donot Download this ZIP file as i got an OTA update of 21S after installing 20s)
3. Goto TWRP recovery.
4. Formate everything. (Cashe, Delvik, Sysytem,Data)
5. Flash the 20s Rom (Provided in STEP 1)
6. After Installing and setting up phone, You are ready to GO BACK to official stock recovery.
Steps to Follow: (FOR already on stock recovery users)
7. Download the 21s recovery (provided in step # 2)
8. change the name to update.zip
9. put it into the root folder.
10. Goto stock updater and slect MANUAL UPDATE from 3dots on top.
11. This is will install the recovery 21s.
12. DONE
Note: you can not install 21s directly on custom recovery as it will give error 7
Can you 1. correct typos 2. move this to https://forum.xda-developers.com/le-2/how-to
Thank you
Thread cleaned up.
If you find some rule violation, please report it.
Also this is not a thread to bring up your personal vendettas. Add the annoying member to your ignore list and move on. No need to use foul language.
Consider this as the first and final warning. If this is repeated any further, there will be action taken against your accounts.
Hope I made myself very clear.
Regards
Vatsal,
Forum Moderator.
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
zogu said:
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
Click to expand...
Click to collapse
26s removed
as the provider stopped me to share it. correction in heading done.
Found link on Google's cache of https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079.
But this file update.zip was for s2_india, not for s2_na
Is newer version for usa market available?
zogu said:
Found link on Google's cache of https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079.
But this file update.zip was for s2_india, not for s2_na
Is newer version for usa market available?
Click to expand...
Click to collapse
As I already mentioned that I have tested these file on my x522(S3) before upload.
Nd x52x series means x520/522/526
Download 20s flash it you will receive 21s automatically
zogu said:
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
Click to expand...
Click to collapse
Original 26s is available in Chinese only. You can flash it via twrp than root nd remove all Chinese app.
Chinese twrp ?
edan lkr said:
Chinese twrp ?
Click to expand...
Click to collapse
Yes.
Sooooo I have a slight problem.
I have TWRP and stock ROM. Sort of. Xtreme Addiction ROM, only one that would work and not give the error"This is an s2 not s2_na_Xxxx" so I Flashed that, and uninstalled root, now in TWRP it doesn't show my internal storage so I can't flash this ROM, and ask for a password. So I tried using the 3dot option from settings and it won't work either, it'll just boot to TWRP and nothing happens. I'm really not looking forward to deleting everything... AGAIN but I will if I have to.
Is there an update for the Le s3 x522 that can be installed though the phone update app? I am still running stock recovery and don't want to change it but it seems the OTA updates not working
Christhepenguin said:
Sooooo I have a slight problem.
I have TWRP and stock ROM. Sort of. Xtreme Addiction ROM, only one that would work and not give the error"This is an s2 not s2_na_Xxxx" so I Flashed that, and uninstalled root, now in TWRP it doesn't show my internal storage so I can't flash this ROM, and ask for a password. So I tried using the 3dot option from settings and it won't work either, it'll just boot to TWRP and nothing happens. I'm really not looking forward to deleting everything... AGAIN but I will if I have to.
Click to expand...
Click to collapse
I think we might be having the same problem...
My X527 came with 16s as the stock ROM.
Upgraded to 19s with TWRP which gives me the system update option as well as OTA (which says I'm running the latest version).
I want to update to 21s and use the system update method..
Phone starts to load the new update (renamed to "update.zip") progress bar at the bottom of the screen while all of this takes place.
Phone reboots into password screen for TWRP, swipe to continue, then select system reboot and once it's back up and running it is still on 19s...?
Did you get your update resolved?
gtd2000 said:
I think we might be having the same problem...
My X527 came with 16s as the stock ROM.
Upgraded to 19s with TWRP which gives me the system update option as well as OTA (which says I'm running the latest version).
I want to update to 21s and use the system update method..
Phone starts to load the new update (renamed to "update.zip") progress bar at the bottom of the screen while all of this takes place.
Phone reboots into password screen for TWRP, swipe to continue, then select system reboot and once it's back up and running it is still on 19s...?
Did you get your update resolved?
Click to expand...
Click to collapse
I did, I used this website. https://www.google.com/amp/s/forum....factory-image-5-8-020s-directly-t3527790/amp/
Downloaded Chinese TWRP from there. As well as that ROM, if you have the 21s update file, I'm sure you can get it working with that TWRP. Hopefully it works for you.
Christhepenguin said:
I did, I used this website. https://www.google.com/amp/s/forum....factory-image-5-8-020s-directly-t3527790/amp/
Downloaded Chinese TWRP from there. As well as that ROM, if you have the 21s update file, I'm sure you can get it working with that TWRP. Hopefully it works for you.
Click to expand...
Click to collapse
What worked for me was replacing TWRP with the factory recovery and I'm good to go.
There was talk of an official update (beyond 21s) in December but so for, no sign of that...
gtd2000 said:
What worked for me was replacing TWRP with the factory recovery and I'm good to go.
There was talk of an official update (beyond 21s) in December but so for, no sign of that...
Click to expand...
Click to collapse
Interesting, replacing stock Recovery didn't work for me when I did it, and yeah. It's most likely not coming soon due to financial issues LeEco has.
Christhepenguin said:
Interesting, replacing stock Recovery didn't work for me when I did it, and yeah. It's most likely not coming soon due to financial issues LeEco has.
Click to expand...
Click to collapse
I note that this says it's the ROM for the S3.
I'm using the X527 which is the S2 with the Snapdragon chip (now listed as X526 after installing 21s), did you perhaps flash the incorrect ROM?
I had continual problems upgrading from 19s with TWRP - it would go through the whole process and then reboot to 19s..
Even after the replacement of the stock recovery, the first ROM I downloaded (21s) was not accepted. Had to download another one for it to finally work.
Could be a bad download?
Contact
How did you contact leeco and get this. I need all future updates. My phone is rooted and I am unable to completely unroot it and get OTAs.
---------- Post added at 02:59 AM ---------- Previous post was at 02:52 AM ----------
rodogg88 said:
Is there an update for the Le s3 x522 that can be installed though the phone update app? I am still running stock recovery and don't want to change it but it seems the OTA updates not working
Click to expand...
Click to collapse
If you don't have TWRP or anything installed, it should work fine if you put the 20s update in the root folder (the folder with the android and download folders). Then just go to system update, press menu, press local update, go through prompts and it should update automatically. Then just repeat the process for the 21s update. If you have twrp installed, I'm pretty sure the chinese ydss version doesn't allow OTA installs. This update requires stock recovery installed because it updates through the recovery. You can find stock recovery images on google (search le s3 stock recovery and click skyneel) or, someone might have posted a recovery image on the le 2 forum. Plz reply if it doesn't work, it worked for me tho.
Is there any bugs? If yes please list. Thank you
does it work for le s3 X626 mtk?
if not, please guide me as I see that this forum support Le S3.
thanks.

Categories

Resources