Upgrade Android 5.1.1 To 8

[Pablo Tatts]

Toget a 5.0 ROM someone has to have written one for that device to utilise the hardware and setup of the machine. You cant take any 5.0 ROM tweak it and make it available for a device. You need a starting point. No-one has done one for the Tab3 so unfortunately you are stuck at 4.4.2 tops. The plus side is that similar 5.0 devices are now so cheap its almost not worth the effort required to try and make it go up to 5.0 so if you did decide to root it and play, you will have lost the monetary equivalent of less than a tank of fuel to replace it with a similar 5.0 android device. I am buying android 7.0 devices sub 100 now.

The Samsung Galaxy Tab 3, much like its predecessors, comes in three sizes, 7", 8" and 10". The 7" is powered by an Exonys 1.2GHz dual core processor, the 8" is powered by the Samsung Exonys 1.5GHz dual core processor and the 10.1" powered by a...

Look for Lineage based roms if you can, Lineage is the successor to Cyanogen, and runs much smoother in my experience. You can even find Lineage builds for older versions that work much better than equivalent cyanogen builds.

I have a Android HP slate 17". I have had difficulty with google , play store app it comes up "unfortunity play store not working" or to that effect. I have to keep clearing the cache but this give me auto updates in which that apps update and stop working.

Hi not a HP worker just someone in the same position as you exactly the problem and I can see that HP have give you no answer to our problem. The problem arises from google/android because as of Oct 17 they have stopped support so basically forcing us to buy another updated product. In light of this I am considering legal action towards HP as they can't make people buy there expensive products and within 3 years they become paperweights because the O/S stops support surely the end user has a right to enjoy their product until it stops working naturally ! HP really need to respond to this there must be thousands of us in the same boat.

hello Iam having the same problem with my 17 slate google stops . After finally (2 hours -13 different depts)I finally got to the slate dept,only to be told that this was Googles problem. I contacted Google they try to troubleshoot it and said it was HP problem.After another call to hp (again same hassle trying to get someone who knew anything about the tablet,they told me to use an SD card download kit-kat-from thier web site and follow the steps to reinstall it..............Well I have done all this and it wont install any of what is on the SD card.thier advise really sucks ,and the tablet still doesnt work. I own litterally thousands of dollars worth of HP equipment and most works well but this is stupid for the support we are not getting,I will keep trying to resolve this issue as I dont want a door stop made out of this Tablet.I will post a fix if I find one.

I've been working on this on and off for a year now, and my main thrust has been to find somewhere to download the Android kitkat or jellybean OS. Did HP tell you where it could be downloaded, or do you have a copy that you could send to me, since HP doesn't provide support anymore? I'll keep watching and if you get this, I'll send you my email. Thanks, hope you still check back, because we will solve this problem---dennyr2

Android 13 presents some unique challenges for organizations planning to migrate their Zebra SDM660-platform devices from earlier Android versions. Updating such devices to Android 13 generally requires conversion from Full-Disk Encryption to File-Based Encryption, resulting in loss of applications, data and settings when the partition is rebuilt using the new encryption. However, Zebra has developed a unique migration process to help reduce data loss by backing up and restoring up to 3GB (after compression)* of apps, data and settings locally on devices during the upgrade.

This migration process allows for the preservation of select apps, data and settings on the device through data backup and restore. To simplify this migration process, Zebra developed Zebra File Guardian, a utility that administrators must use to select the apps, data and settings to be preserved.

The File Guardian is a Zebra utility contained within the Zebra Conversion Package (ZCP)* that allows administrators to choose which non-system apps, data and settings to back up and restore during the migration process. By creating a single "Golden Configuration" for use on all the devices in a device-persona group, administrators have a means to preserve the MOST important apps, data and settings, allowing the migration process to proceed even if some of the devices in a group contain data in excess of the maximum size that can be preserved.

ATTENTION!!

Please read the following section CAREFULLY before proceeding with migration, and follow all provided guidelines. Failure to do so could lead to data loss and/or failure that requires manual device recovery. Any device that started but did not fully complete the migration process should be considered unsuitable for production use until it is successfully recovered as described in the Failure Recovery section.

IF NECESSARY, relax any restrictions applied to the Golden Device that might prevent the use of adb on the PC to push and pull files to and from the Golden Device. Such restrictions might include one or more of the following:

RECOMMENDED: Determine the type of encryption in use on the Golden Device to determine whether data preservation is required and would therefore need to be applied to Target devices in the same group.

ZCP presents a screen on the Golden Device from which the File Guardian utility can be launched.

If the icon seen in the image below is visible on the Golden Device, proceed to Step 12.Click image to enlarge; ESC to exit.

If the EMM has been enrolled and configured to disable system apps," the File Guardian utility might be disabled.

If the Golden Device displays a screen like the image below, use the EMM to enable the File Guardian utility (package name: com.zebra.fileutility) on the Golden Device and reboot the Golden Device. The screen shown in Step 10 (allowing the File Guardian utility) should appear on the Golden Device after it reboots. Click image to enlarge; ESC to exit.

Tap to select apps and files to preserve.

If the size limit is reached, it might be necessary to de-select some items or move them lower in the priority (see next step). Click image to enlarge; ESC to exit.

After selecting files to be preserved, drag the most important files toward the top.

When finished, tap "Proceed" and then "Save XML" to store the Golden Config:Click image to enlarge; ESC to exit.

SKIP THIS STEP ONLY IF ALL TARGET DEVICES ARE IDENTICAL.

The options on this screen allow for the testing of devices similar to the Golden Device to help determine whether those devices will migrate successfully using the Golden Configuration (GC) being created now. Learn more about these optional assessment tests.

Zebra recommends selecting BOTH the Storage Size Check and Precondition Check.

Tap "Proceed" to continue. Click image to enlarge; ESC to exit.

24. Test the Golden Device to ensure that: * It has been updated properly and is in an acceptable production state * The preserved apps, data and settings are present and accounted for * If either of these conditions is not met, it is not advisable to move on to the next part of the migration process. To proceed, make any necessary corrections to the manual process and apply the revised process to a new Golden Device selected from the same group until the Golden Device finishes the process in an acceptable state.

The migration process might proceed fully unattended, automatically rebooting multiple times until the device is in the final state on Android 13. Otherwise, depending on the starting state of the device and depending on whether any configurations are changed during preparation, the process might not proceed fully unattended and manual interventions (e.g. enter a PIN/passcode) might be required for a device to reach the final state on Android 13.

Optional assessment tests are RECOMMENDED ONLY IF ALL TARGET DEVICES IN THE SELECTED PERSONA ARE NOT IDENTICAL, or if the precondition state or storage capacity of some devices in a given persona are not fully known. Assessment tests allow the Golden Configuration (GC) file created previously to be used to test devices similar to the Golden Device to help determine whether those devices will migrate successfully using that GC, or if further actions would be required for migration.

After successfully verifying a small chosen subset of Target devices in a group, the migration process can be applied to ALL remaining Target devices in the group. These remaining devices might be broken down into subsets for logistical reasons. Follow the same steps described in Part 3 for the remainder of the Target devices in the group or subsets of devices until the migration process is complete for the group.

If the Android Migration process fails to complete on a Golden Device or on a Target device, it could leave the device running the Zebra Conversion Package (ZCP). Since devices running ZCP are NOT suitable for production use, some manual intervention is generally required in this situation. If any of the following symptoms of failure is detected on any device, take the recommended actions to recover that device.

3a8082e126