Related
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
Requirements:
Flashtool 0.9.15.0
Rooted SGP311 (on any Android version up to and including 4.4.2) with custom recovery installed.
If you do not meet these conditions, for example, if you are on an unrooted system, here is a guide to get you on a rooted 4.1.2 with recovery:
http://forum.xda-developers.com/showpost.php?p=53063218&postcount=14
This works on locked or unlocked bootloaders. This also works on any customization.
The procedure should work with any pre-rooted Android version but I started with 10.1.C.0.370 (4.1.2) which was rooted with DooMLoRD_Easy-Rooting-Toolkit_v17, patched with remountrebootfix, and equipped with XZDualRecovery.
Limitations:
This process can delete the files on your internal SDcard so back them up. Also, you will have to reinstall all your apps, as they get erased too.
Download link:
Mega
https://mega.co.nz/#F!UkshjY6A!HIW7xGf1E1oa04e0N3b1OA
You only need the zip and ftf files. The txt file is just the checksum if you want to verify that your download is error-free. I strongly recommend that you do the checksum before flashing.
Instructions:
1- Backup before you start messing with your tablet!
2- Put system.flashable.zip in /sdcard of your tablet.
3- Keep SGP311_10.4.1.B.0.109_R2C_VMo_US_CA_PR_NoSystem.ftf on your PC.
4- Disconnect any USB cable that may be attached to your tablet.
5- Reboot to recovery. Preferably to TWRP, but you can make CWM work too.
6- Do not wipe anything.
7- Once in recovery, flash system.flashable.zip.
8- It is important to NOT REBOOT the tablet after this step.
9- Find and use the Power Off option in the recovery and turn your tablet off. In CWM based PhilZ Touch it is under "Power Options" -> "Power Off". In TWRP it is under "Reboot" -> "Power Off". If you see your tablet rebooting, force it to turn off by pushing the power and volume up keys simultaneously (or however else you can!)
10- Open Flashtool 0.9.15.0 and click on the flash icon. Choose flash mode.
11- Navigate to where you have saved SGP311_10.4.1.B.0.109_R2C_VMo_US_CA_PR_NoSystem.ftf and flash this ftf with your tablet in flash mode. To put your tablet in flash mode, hold the volume down button when it is off and connect with the USB cable to the PC.
12- Reboot and enjoy!
Credits:
I only put the files together. All the credit should go to XDA's [NUT] and DooMLoRD and many others...
I had a few requests from people who upgraded to 4.4 and were not happy with the speed. So I made these file in case you want to downgrade to rooted 4.3.
Enjoy.
Downloading now. Thanks!
hi njajoor
thanks to your guides i was able to flash in quick an easy way all the procedure was smooth.
may i kinow how did you tewk your rooted 4.3 rom or which settings do you recommend to improve the performance of the tab Z?
many thanks again
mame3876 said:
hi njajoor
thanks to your guides i was able to flash in quick an easy way all the procedure was smooth.
may i kinow how did you tewk your rooted 4.3 rom or which settings do you recommend to improve the performance of the tab Z?
many thanks again
Click to expand...
Click to collapse
This is what I do normally, but you may want to change it for you specific needs:
1- In settings:
Wifi, menu, advanced, network notification unchecked; Keep wifi on never; wifi optimization checked
NFC off
Sound, touch sound off; screen lock sound off
Display, sleep after 30 seconds, double tap to wake up checked, brightness set to lowest
Power management, stamina mode on
Keyboard, sounds feedback, sound on key press unchecked
Accounts, email: set sync frequency to 1 hour; Skype: sync off
2- install adaway
3- use titanium backup pro or apps tab in settings to freeze/disable:
Crackle and Netflix (unless you use them)
Anything with the word or logo of Facebook or twitter or social engine in it. You are better off using the browser for these.
If you use both email and Gmail apps, disable Gmail and set it up in email app.
All Google play apps except store and Services
Google plus and hangout
McAfee, reader by Sony, let's start psm, video unlimited, wisepilot
Mobile date, mobile network, sim lock, and sim toolkit (sgp311 doesn't have mobile data)
PO Box touch and Xperia Chinese keyboard (this may significantly reduce your keyboard flickering if not entirely eliminate it)
4- I install greenify, wakelock detector and juice defender on my other Android devices but I've come to believe Sony's stamina does an excellent job and none of that is necessary.
5- Turn gps on only when you use it
6- Remove active widgets from your home screen. I only have the clock and the weather left. If you want to keep the widgets put them on a separate display than the ones you keep your commonly used icons in.
With these settings mine is smooth as butter. I hope yours will be too.
in the subsequent posts below, you will find all the info you need for not only the device but the ROMs I have had my hands in.
each person who I pulled the files from will get a thanks in the posts as necessary
NonSense 1.04
Disclamer: these files are meant specifically for the HTC Desire 510. Use these files at your peril, you assume any responsibility for loss or damage that may result from use of these files or procedures. what has been included in this tutorial is for the HTC Desire 510
You have been warned.
note: from now on CRI signifies cricket, and B-S signifies sprint/boost if those signifiers aren't used, it applies to both type of this phone
now to the goodies.....
List of supplies:
1. Phone (HTC Desire 510)
2. USB cord that syncs with the PC
3. USB drivers installed for the phone
4. the zip files from this location. click here
4.1 there are 2 different versions of the same ROM, but the *1.04-lean.zip is US only (refer to changes to see why).
4.2 CRI for cricket/att, B-S for boost/sprint
5. read these instructions completely before attempting
before we get started make sure you have supersu (which can be downloaded from here), and NonSense1.04.zip copied to the root of your external SD card
NETWORK UNLOCK (I.E. switching services)
as this phone is LTE compatible, it takes a SIM card no matter the service to receive calls and data. so it stands to presume all you need to do is network unlock the device (Sprint calls it UICC unlock, others it's the Network Unlock Code)
the phone needs to be network (SIM) unlocked in order to switch it from cricket to sprint, or from sprint to virgin mobile, etc.
to network unlock the phone:
1. make sure you are on stock ROM (the one that came with the phone, not the one listed in this post nor CM)
2. call the respective original service provider of the phone (i.e. cricket, sprint, etc.) and tell them that you are leaving the country (like to Australia) and you want to unlock the SIM so you can use your device for service down there.
2.1 if you bought the phone second-hand or don't have service on it, you will have to find a reputable unlock service online
2.2 for sprint customers, your account HAS to be at least 6 months old before they will give you the UICC(SIM unlock) code
2.3 for boost customers, your account HAS to be at least a year before they will give you the UICC(SIM unlock) code
3. once you have the SIM unlock code, pull battery from phone, remove the original SIM, put your services respective SIM in (i.e. originally a cricket phone now running a T-Mobile SIM), put in battery, boot phone, and enter the unlock code where it asks.
4. once your back into device, you'll notice you will have no data.
4.1 what needs to be done is to program the APN (google will be your best friend here - for example sprint lte apn settings, or T-Mobile lte apn settings).
5. now that you have the APN settings, you can program them into the phone.
5.1 APNs can be found in the device by going to settings, then mobile data, clicking on access point names. in there in the upper right hand corner should be 3 dots that are verticle. click on that and then on new APN.
5.2 add the respective settings, click save and then make sure it has a green dot next to it.
6. sit back and enjoy the fruits of your labor
APNs for this device can only be written once the phone has been UNLOCKED and the original (cricket) service providers SIM is NOT inserted, and your using another service Provider ( sprint, T-Mobile, etc.) SIM.
UNLOCKING BOOTLOADER
1. for the drivers, use the ones contained here in the HTCDrivers.zip and extract them to the desktop
1. extract and use the file contained in adb.zip to flash unlock token
2. follow this tutorial and choose all other supported devicess when it asks about device.
INSTALLING TWRP AND KERNEL
in the adb file you should notice a file called recovery.img. that is TWRP recovery for the device
there is also a file called boot.img. this will allow read/write permissions at the System level once root is obtained
if you have either the sprint, boost or another service provider's variety of this phone, try flashing their respective kernel after you install the ROM or before you root (no guarantees that flashing the respective kernel will work. as I have the cricket variety of this phone, I am only developing for that one)
1. from home screen, go to settings and scroll down to power and then scroll all the to the bottom of that and uncheck "fast boot"
2. shut down phone completely
3. go back into fastboot (vol down + power)
4. Select fastboot from the menu list and press the power button.
5. open command prompt and use the CD command to get it to the root of the adb folder (CD C:/users/sky/desktop/adb).
6. plug in device and wait for it to say fastboot USB
7. type in command prompt "fastboot flash recovery recovery.img' (should complete within 4 seconds)
8. in the same command window type "fastboot flash boot boot.img" (should complete within 4 seconds)
8.1 step 8 can be skipped if your just flashing *NonSense1.04*.zip
9. pull battery once that is completed and put it back in.
10. power device on (skip this step if rooting)
OBTAINING ROOT (can be skipped if installing NonSense1.04 as it's already rooted)
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the supersu update package.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load
INSTALLING NonSense 1.04
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the NonSense1.04.zip.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
3.1 beware, it may take a bit to install. just be patient, it's working.
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load. be forewarned, it may take about 15 minutes to load
CHANGES
CRI versions
1. DEODEXed the ROM
2. added external SD support into the ROM
3. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
4. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
5. added more stable kernel to flash file.
6. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, and Viper4android (DSP/equalizer)
6.1 all apps that have been listed in 6 can be uninstalled without the need for root
7. root and SU have been added and are up to date in this rom as of 11:45PM MST on 3/1/215
8. added apns-conf.xml from CyanogenMod
9. got native APP2sd support thanks to pattyboi's kernel
B-S versions
1. mostly DEODEXed the ROM
2. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
3. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
4. added more stable kernel to flash file.
5. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, Wifi Tether, and Viper4android (DSP/equalizer)
5.1 all apps that have been listed in 5 can be uninstalled without the need for root
6. root and SU has been added
*1.04-lean
list of removed apps
1. Dropbox (can be found in playstore)
2. Google plus (can be found in playstore)
3. Hangouts (can be found in playstore)
4. HTC Dot View(can be found in playstore)
5. keyboard language packs for Arabic, Chinese, English UK, French, German, Greek, Italian, Portuguese, Russian, and Spanish (not in play store) if needed, flash language.zip found here
6. VPN dialogs (not in play store) if needed, flash missing.zip found here
7. HTC Zoe (can be found in playstore)
BUGS
CRI versions
1.USB internet pass-through not working
2.WiFi direct (miracast) not working
3. want to get rid of annoying volume too loud warning
B-S versions
1. native hotspot says internet when connected to win 7 machine, but will not allow it to go through. Have included wifi tether as a workaround until the issue can be resolved
THANKS
CRI versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing a more stable kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, CraviingCritic for providing the original ROM in which this wouldn't be possible
B-S versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing the current kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, LarryBoyG for providing the original ROM in which this wouldn't be possible
please feel free to let me know if there's any issues with this release and i will fix them as they are found for now as this device is the one i primarily use as of right now.
I will also be keeping the links updated for as long as I own the device (being that my HTC Desire 510(Cricket) is network unlocked, that may be a long time - or until I get a better device).
UPDATES
for those of you who have downloaded the ROM since first release, I will include an CRI_NSupdate.zip or B-S_NSupdate.zip file found here. it will include the changes I have made to the rom since it's initial upload.
the file by the name of NSupdate.szip will include update that pertain to both the CRI and B-S ROMS
to install the updates, just put the update file onto the root of the SD card, reboot into recovery, choose install, pick the update file, swipe the blue button on the bottom, reboot and enjoy.
EDITING THE BOOTUP
location of files mentioned is in /system/customize/resource
to change boot animation
1. find your favorite boot animation
2. rename it to AIO_bootup.zip
3. copy/move and overwrite the original with a root explorer to /system/customize/resource
to change the boot sound
1. find a sound file you like and want to hear every time the phone boots (can be changed at any time)
2. convert it to wav (the file has to be wav in order for the phone to recognize it)
3. rename it to CRICKET_LOGO_24bit28k_STEREO.wav
4. copy/move and overwrite the original with a root explorer to /system/customize/resource
reboot and enjoy...
THINGS NOTICED WHILE CREATING ROMs
1. both (cricket and boost/sprint) phones are exactly the same except for the boost/sprint ones contain a CDMA chipset.
1.1 the only things I had to change from the cricket rom to the boost rom was apns.xml in framework-res, apns-conf.xml, and the preferred network type in build.prop.
2. all kernels work for both (US) versions
3. the same recovery is used on both (US based) devices
so essentially, if we develop for the boost/sprint version of the device, change a few things, it will be ready to roll for the cricket version as well
TO FIX NATIVE TETHER ON B-S VERSIONS
1. Install Script Manager – SManager app from the Play Store.
2. Open the app and grant it root access when prompted.
3. Now, navigate to /system/etc/init.d and tap “tether” script.
4. Click on SU and Boot (Android skull and gear icons, respectively)
5. Click on Run and Save options.
The issue should be fixed now. Reboot and enjoy!
thanks goes to qwerty6532 and LarryBoyG for the fix. now to add that permanently to the ROMs and then they'll be absolutely stable enough for me to be happy and start working on CM11
CM11
I will be building CM11 for the device for both the cricket and boost models. look for the info here as I update it a I need
****edit**** ok so I figured out some of the issue with CM11 not wanting to install apps. I got the internal memory pulling the 1.1 gbs but now I need to symlink the external memory where it goes.
****edit**** so I have figured out what needs to be done...... the kernel for CM11 needs to be built from the ground, up (or one needs to be built that is compatible with it). i'll upload the current one that fixes the memory error (look in downloads).
reserved
so as i have not been actively developing on the phone i will no longer supply updates. all flash files are up to date as of 8 months ago and should be working with out an issue.
again, reserved
same to you...
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Burtrum57 said:
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Click to expand...
Click to collapse
if I had a 64-bit version for this device, I would have it out as soon as I could. and thanks
Great job. Off and running now
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
CSP III said:
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
Click to expand...
Click to collapse
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
qwerty6532 said:
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Click to expand...
Click to collapse
Well it's added to it. It just needs to be activated for now until I can figure out how to add it to automatically start from the first run of the Sprint/boost ROM
schizoidd said:
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
Click to expand...
Click to collapse
Sorry, not following "wipe the system partition" ???
CSP III said:
Sorry, not following "wipe the system partition" ???
Click to expand...
Click to collapse
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
schizoidd said:
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
Click to expand...
Click to collapse
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
CSP III said:
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
Click to expand...
Click to collapse
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
schizoidd said:
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
Click to expand...
Click to collapse
Right on buddy. I'll take you at your word on it. I've never had to do that before so it naturally made me a little nervous. Not that I couldnt have just restored a backup, but still . Many thanks.
Problems
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
schizoidd said:
I
for those of you that build the kernels, do you think u can build one that is AOSP and compatible with the device for android 4.4.4?
Click to expand...
Click to collapse
we cant really do a "aosp" kernel because of htc's modifications to the board and pins,and they have their own dtb issues...im 99% sure mine works with android 4.4.x because of larry using it in gpe,just repack the ramdisk the zimage and it should be okay
Bobby060 said:
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
Click to expand...
Click to collapse
If you're going from bone stock to this, you need to do a factory data reset. Just make ssure you back up your data and use nandroid manager to pull it data back into the new ROM
So, my phone afaik, is relatively slow and mostly trashy.
BEFORE YOU SAY ANYTHING, I have NEVER NOR INTEND TO play games on it.
It has been generally slow since the day I got it. Tried upgrading to 4.3, didn't work, made it slower and hatred the keyboard. Not that the 4.1.2 keyboard is any better stability wise ( if my phone runs out of ram it'll kill the keyboard and take it down mid-typing for about 20 seconds, most often in chrome. Crashed 4 times as of the start of this sentence.).
Tried flashing cyanogen, I remember having something about a locked bootloader and no fastboot so I had to flash a special version for locked bootloaders, and it was CG v12, which I think is 4.4, far beyond the xperias capabilities afaik. It sure ran like it (all apps including launcher and homescreen would crash intermittently).
I remember trying nova launcher and go launcher on stock Rom. Heh. I got 5 fps navigating the home screen.
So time and time again I tried many things, and at last I'm coming to you guys for help. But also, let's start from scratch. Assuming I know nothing.
I have the stock android kernel, 4.1.2, rooted, with a root file explorer.
This post took 15 minutes to write. Halp.
I use 4.1.2 with greenify and SD maid pro and seeder and I unistalled chrome and using opera and it is lag free
Try the above suggestions (you already have root).
I you are still nog satisfied: unlock your bootloader first and install custom recovery like philz and/or twrp. Then install Williams kernel for stock rom.
The Williams kernel says two of the following:
Q: With what ROM can I use this kernel ?
With any ROM based on*Sony*stock 4.3
Q : Can I install this kernel on locked bootloader ?
A : No ! This kernel is only for unlocked bootloader.
I have lbl and 4.1.2. So that's not possible.
I also would prefer keeping it that way as I don't know my fullest about what drm keys are, but something tells me I want to keep them. As for the kernel itself it looks like it's geared towards battery, not app stability or speed. My battery is fine, and even on its off days it has a 14,000 MaH, 2A power bank ready to charge it at any given time.
As for the apps, are they necessary? Seeder and sd maid pro are paid, and I don't even have an sd card so sd maid is kind of pointless.
As for greenifier, if there's any app, including system, that I don't want running 100% of the time, I've uninstalled it (including system apps)
Also it's worth pointing out , when I borrowed it from a friend, allocating a whole 4gb of a class 10 microsd as alternative swap memory for it has seemingly no effect. It uses about 15m, and leaves the onboard ram at nearly 100% anyway.
Is CM 12.1 any good? I've seen people refer to it as the revival of the SP. However, I haven't found an LBL tutorial, but it has to exist, right? I saw an LBL Rom for android version 5.x, so it can't be that hard for a CM 12.1 Rom right? (CM 12.1 is 5.x as well, I think)
If I'm wrong about any of this, let me know.
First change your SD card to a UHS-1 Class 10 SD Card, this may cost quite alot but trust me the benefits it gives is totally worthwile.
Also no need to use Greenify if you remove all the bloatware that comes with your system via Root Explorer or something like that.
Here's a list of safe-to-remove apps found in Root/system/app
AnonymousData
AntHalService
Backup-Restore
BasicDreams
Books
BrowserProviderProxy
Chrome
CityIdPermission
com.sonyericsson.xhs
com.sonymobile.xperialounge.services
cover-widget
CrashMonitor
CrashMonitorSystem
DeviceConfigTool
Drive
DualShockManager
EditorsDocs
EnchantedForest
ExperienceFlow2LiveWallpaper
ExternalKeyboardJP
FaceLock
Galaxy4
gmail-reader-service
Gmail2
GoogleLyricsPlugin
GoogleTTS
Hangouts
HoloSpiralWallpaper
HTMLViewer
IddAgent
IntelligentBacklight
IntelligentRotation
IntelligentSettings
Keep
KeyChain
Lifelog-googlePreloadLive-release-2.4.P.1.4
LiveWallpapers
Maps
Newsstand
NewsWeather
NoiseField
OmaDownload
OmaV1AgentDownloadServices
PartnerBookmarksProvider
PhaseBeam
phone-usage
PhotoSlideshow
PhotoTable
PhotoWidget-release
PlayGames
PlusOne
RecommendationEngineExtension
RemoteControlService
RemoteFileAccess
SelfPortrait
SemcWarrantyTime
sneiaccountmanager
SomcMovieCreatorRmm
SomcPOBox
SomcSketch
SonyEntrance
Street
SyncHub
talkback
Tasks
textinput-chn
TopContactsWidget-release
TouchBlock
TouchFilterPackageSwitchService
UnsupportedHeadsetNotifier
Videos
VisualizationWallpapers
white-balance
WikipediaPlugin
WirelessControllerManagerService
WorldClockWidget-release
YouTube
YouTubeKaraokePlugin
YouTubePlugin
/system/priv-app/
AndroidForWork
BackupRestoreConfirmation
com.bambuser.sociallive
CoverApp
enhancedusbux
EnterpriseService
Exchange2
FBCalendarSync
filecommander
helpapp
InputDevices
IntelligentGesture
livewaremanager
MyXperia
OMAClientProvisioning
OnlineRemoteCamera
retaildemo
SemcEmail
SEMCFacebookProxy
SimlockUnlockApp
SmartcardService
SocialEngineCore
SocialEngineFacebookPlugin
SocialEnginePicasaPlugin
SomcHotspot2Settings
SomcMirrorLinkManualSwitch
SomcMirrorLinkServer
SomcMirrorLinkSystem
SomcPhotoAnalyzer
SomcPodcast
SomcSeamlessTethering
SOMCTwitterAccount
TagGoogle
UpdateCenter
usb-mtp-backup-transport
usb-mtp-factoryreset-wrapper
usb-mtp-marlin-wrapper
usb-mtp-update-wrapper
usb-mtp-vendor-extension-service
Velvet
VpnDialogs
/system/vendor/app/
root/etc/customization/product/applications/
root/etc/customization/applications/
root/etc/product/applications/
/system/etc/customization/product/applications/
/system/etc/customization/applications/
/system/etc/product/applications
After which you can also try using a Custom kernel, this provides you with alot of CPU Governors which you can use depending on need and of course Overclocking which can help boost some fps in games.
Hope this helps
Revontheus said:
First change your SD card to a UHS-1 Class 10 SD Card, this may cost quite alot but trust me the benefits it gives is totally worthwile.
Also no need to use Greenify if you remove all the bloatware that comes with your system via Root Explorer or something like that.
Here's a list of safe-to-remove apps found in Root/system/app
AnonymousData
AntHalService
Backup-Restore
BasicDreams
Books
BrowserProviderProxy
Chrome
CityIdPermission
com.sonyericsson.xhs
com.sonymobile.xperialounge.services
cover-widget
CrashMonitor
CrashMonitorSystem
DeviceConfigTool
Drive
DualShockManager
EditorsDocs
EnchantedForest
ExperienceFlow2LiveWallpaper
ExternalKeyboardJP
FaceLock
Galaxy4
gmail-reader-service
Gmail2
GoogleLyricsPlugin
GoogleTTS
Hangouts
HoloSpiralWallpaper
HTMLViewer
IddAgent
IntelligentBacklight
IntelligentRotation
IntelligentSettings
Keep
KeyChain
Lifelog-googlePreloadLive-release-2.4.P.1.4
LiveWallpapers
Maps
Newsstand
NewsWeather
NoiseField
OmaDownload
OmaV1AgentDownloadServices
PartnerBookmarksProvider
PhaseBeam
phone-usage
PhotoSlideshow
PhotoTable
PhotoWidget-release
PlayGames
PlusOne
RecommendationEngineExtension
RemoteControlService
RemoteFileAccess
SelfPortrait
SemcWarrantyTime
sneiaccountmanager
SomcMovieCreatorRmm
SomcPOBox
SomcSketch
SonyEntrance
Street
SyncHub
talkback
Tasks
textinput-chn
TopContactsWidget-release
TouchBlock
TouchFilterPackageSwitchService
UnsupportedHeadsetNotifier
Videos
VisualizationWallpapers
white-balance
WikipediaPlugin
WirelessControllerManagerService
WorldClockWidget-release
YouTube
YouTubeKaraokePlugin
YouTubePlugin
/system/priv-app/
AndroidForWork
BackupRestoreConfirmation
com.bambuser.sociallive
CoverApp
enhancedusbux
EnterpriseService
Exchange2
FBCalendarSync
filecommander
helpapp
InputDevices
IntelligentGesture
livewaremanager
MyXperia
OMAClientProvisioning
OnlineRemoteCamera
retaildemo
SemcEmail
SEMCFacebookProxy
SimlockUnlockApp
SmartcardService
SocialEngineCore
SocialEngineFacebookPlugin
SocialEnginePicasaPlugin
SomcHotspot2Settings
SomcMirrorLinkManualSwitch
SomcMirrorLinkServer
SomcMirrorLinkSystem
SomcPhotoAnalyzer
SomcPodcast
SomcSeamlessTethering
SOMCTwitterAccount
TagGoogle
UpdateCenter
usb-mtp-backup-transport
usb-mtp-factoryreset-wrapper
usb-mtp-marlin-wrapper
usb-mtp-update-wrapper
usb-mtp-vendor-extension-service
Velvet
VpnDialogs
/system/vendor/app/
root/etc/customization/product/applications/
root/etc/customization/applications/
root/etc/product/applications/
/system/etc/customization/product/applications/
/system/etc/customization/applications/
/system/etc/product/applications
After which you can also try using a Custom kernel, this provides you with alot of CPU Governors which you can use depending on need and of course Overclocking which can help boost some fps in games.
Hope this helps
Click to expand...
Click to collapse
This does help quite a bit, some of these I left out of caution, thanks!
Still looking for more advice if anyone has any
_/~-{Xperia SP | C5303}[Rooted/Stock/4.1.2/12.0.A.2.254/LBL]-~\_
Actually, I tried doing this. My phone restarts anytime I try to mount it as read-write, and dedicated uninstaller apps also restart my phone when I try this.
_/~-{Xperia SP | C5303}[Rooted/Stock/4.1.2/12.0.A.2.254/LBL]-~\_
Zycarite said:
The Williams kernel says two of the following:
Q: With what ROM can I use this kernel ?
With any ROM based on*Sony*stock 4.3
Q : Can I install this kernel on locked bootloader ?
A : No ! This kernel is only for unlocked bootloader.
I have lbl and 4.1.2. So that's not possible.
Also I would like to keep it that way
Click to expand...
Click to collapse
When I said this, I meant keep the LBL. Not 4.1.2. I'd be fine with upgrading, if it HELPED. When I went to update 4.3, the official Sony one, it was slower. Same with CM 11.
_/~-{Xperia SP | C5303}[Rooted/Stock/4.1.2/12.0.A.2.254/LBL]-~\_
Click to expand...
Click to collapse
Bump.
Unless someone can tell me exactly what I lose when I unlock my bootloader, I will likely keep it locked.
_/~-{Xperia SP | C5303}[Rooted/Stock/4.1.2/12.0.A.2.254/LBL]-~\_
Click to expand...
Click to collapse
Some Sony functions, where bravia engine is the most important.
Before you unlock your bootloader do a ta backup. Thats the way tot restore even your drm Keys.
just saying
have you tried flashing ftf 4.3 stock via Flashtool ?!
also i experience no lag using the latest build of cm11 or Omni-X rom
Ahmed_HM said:
just saying
have you tried flashing ftf 4.3 stock via Flashtool ?!
also i experience no lag using the latest build of cm11 or Omni-X rom
Click to expand...
Click to collapse
No, because Windows 8.1 is horrible with adb, and also I remembered my phone has a permanently locked bootloader, as well as a sim lock (Not sure if that helps)
I'll take at omni and attempt to flash via windows 7 this time.
_/~-{Xperia SP | C5303}[Rooted/Stock/4.1.2/12.0.A.2.254/LBL]-~\_
Click to expand...
Click to collapse
Zycarite said:
No, because Windows 8.1 is horrible with adb, and also I remembered my phone has a permanently locked bootloader, as well as a sim lock (Not sure if that helps)
I'll take at omni and attempt to flash via windows 7 this time.
Click to expand...
Click to collapse
You just need to turn off driver signature verification on windows 8.1 before installing adb drivers and etc ...
my phone is also LBL but not sim locked,
anyway if you are on windows 7 now, then it's ok.
Ahmed_HM said:
You just need to turn off driver signature verification on windows 8.1 before installing adb drivers and etc ...
my phone is also LBL but not sim locked,
anyway if you are on windows 7 now, then it's ok.
Click to expand...
Click to collapse
Got it working on 8.1, turns out I was missing just one driver.
Attempting to install the rom but it advised a wipe beforehand, I'm assuming "factory reset" means the same thing.
It's taking a while, and I assume it'll be quite some time more.
Thanks by the way!
Zycarite said:
Got it working on 8.1, turns out I was missing just one driver.
Attempting to install the rom but it advised a wipe beforehand, I'm assuming "factory reset" means the same thing.
It's taking a while, and I assume it'll be quite some time more.
Thanks by the way!
Click to expand...
Click to collapse
Keep me updated if anything goes wrong , best of luck
Ahmed_HM said:
You just need to turn off driver signature verification on windows 8.1 before installing adb drivers and etc ...
my phone is also LBL but not sim locked,
anyway if you are on windows 7 now, then it's ok.
Click to expand...
Click to collapse
Flash tool didn't work, drivers must've been installed correctly because recoveries installed just fine. However in the process of installing omni, it said something along the lines of "meta error" or "cannot write meta" shortly after it was expanding system. It very promptly rebooted after showing an icon of a dead android in the background, and that kids, is how I met your mother.
No wait,
That's how I hard bricked my xperia.
****.
It just cycles through the sony logo. Stays for a bit, then fades out like a gameboy would back in the day if it ran out of battery, then re-appears, repeat.
Only hint of something happening is the glow of red along the lightbar if I attempt to put it into fastboot which doesn't end up working anyway.
Recoveries are gone and inaccessible AFAIK.
Do I have to get a new phone?
Zycarite said:
Flash tool didn't work, drivers must've been installed correctly because recoveries installed just fine. However in the process of installing omni, it said something along the lines of "meta error" or "cannot write meta" shortly after it was expanding system. It very promptly rebooted after showing an icon of a dead android in the background, and that kids, is how I met your mother.
No wait,
That's how I hard bricked my xperia.
****.
It just cycles through the sony logo. Stays for a bit, then fades out like a gameboy would back in the day if it ran out of battery, then re-appears, repeat.
Only hint of something happening is the glow of red along the lightbar if I attempt to put it into fastboot which doesn't end up working anyway.
Recoveries are gone and inaccessible AFAIK.
Do I have to get a new phone?
Click to expand...
Click to collapse
No, Your Phone is just Soft Bricked
on the back of your phone , you will find a button called off
press it until your phone vibrates three times to shut your phone down to conserve battery
you need to get flashtool working to Recover your phone
if you are on Win 8.1, make sure you have disabled driver signature verification and installed the driver pack that comes with flashtool
then you shouldn't have any problem flashing ftf stock rom
Zycarite said:
Flash tool didn't work, drivers must've been installed correctly because recoveries installed just fine. However in the process of installing omni, it said something along the lines of "meta error" or "cannot write meta" shortly after it was expanding system. It very promptly rebooted after showing an icon of a dead android in the background, and that kids, is how I met your mother.
No wait,
That's how I hard bricked my xperia.
****.
It just cycles through the sony logo. Stays for a bit, then fades out like a gameboy would back in the day if it ran out of battery, then re-appears, repeat.
Only hint of something happening is the glow of red along the lightbar if I attempt to put it into fastboot which doesn't end up working anyway.
Recoveries are gone and inaccessible AFAIK.
Do I have to get a new phone?
Click to expand...
Click to collapse
Instead of flashtool you can try emma/flashtool from Sony website. My experience is that the connection with phone is good.
(Power off, volume down, connect usb cable)
If only red light remains, is it possible that your battery is down? -> connect to charger all night (i advice use a charger with more mA in such cases, like ipad charger)
halloarno said:
Instead of flashtool you can try emma/flashtool from Sony website. My experience is that the connection with phone is good.
(Power off, volume down, connect usb cable)
If only red light remains, is it possible that your battery is down? -> connect to charger all night (i advice use a charger with more mA in such cases, like ipad charger)
Click to expand...
Click to collapse
Tried Emma, just informs me when I try to do flash boot that my device is locked, as I always knew. (In terms of the bootloader)
Booting it with fastboot shows nothing.
Zycarite said:
Tried Emma, just informs me when I try to do flash boot that my device is locked, as I always knew. (In terms of the bootloader)
Booting it with fastboot shows nothing.
Click to expand...
Click to collapse
Hmmm, when I start Emma, my phone get automaticly detect, and Emma suggest to install stock 4.3 firmware.....
Hi everyone,
I have a Sony Z3 compact I just received, model D5803 running Android 6.0.1 with Firmware 23.5.A.0.575.
I really dislike Google and want to run a phone with the minimum of proprietary software (I guess blobs to communicate with the hardware are mandatory). I guess AOSP (any version, but a recent one would be better ) with F-Droid is a good solution.
Unfortunately when checking the sony website but it tells my the bootloader is not unlockable. What should I do? I'm running Ubuntu and have adb and fastboot installed.
I found [this topic](https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714) which tells it roots the phone (and has a GNU/Linux script) but how does that help me to install a Rom, for example the AOSP provided by Sony at /open-devices/list-of-devices-and-resources/ if the bootloader is still locked? What are TWRP and busybox, is that supposed to help?
Flaburgan said:
I found [this topic](https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714) which tells it roots the phone (and has a GNU/Linux script) but how does that help me to install a Rom, for example the AOSP provided by Sony at /open-devices/list-of-devices-and-resources/ if the bootloader is still locked? What are TWRP and busybox, is that supposed to help?
Click to expand...
Click to collapse
TWRP is a custom recovery that allows you to flash a ROM and other files, that are stored on the normal internal or external storage.
Busybox is a binary that gives you command line tools that are often included in a Linux install and some of which aren't included on normal Android. These are commands that other things may make use of, or that you can make use of at a terminal app or run from Tasker or similar app.
You want to look at backing up your TA partition, which stores your DRM keys, before unlocking the bootloader to install a custom ROM because some functionality, camera quality and anti-distortion, sound quality, and some other stuff which I don't remember, won't work if you go back to the stock ROM unless you have these keys backed up and then restored later. You need to unlock the bootloader in order to flash a custom ROM and doing this erases, permanently, these DRM keys, so they need to be backed up and then put back later if you relock the bootloader and flash a stock ROM.
If you look in the Original Development section, Jaguar Aries ROM has no Google Apps, had the latest patches up to Febuary, and had the best battery life of any custom ROM I've seen for this phone, right on par with stock. There are some builds of Lineage OS that are probably closer to being up to date as well and may have a better camera than Jaguar. The developer of Jaguar has moved on to another phone. That said, if you aren't experienced and don't know what TWRP is, then installing it is an extra step from other ROMs as well since it requires you to setup a firewall app to permit connections on data or wifi before you can use the wifi or data at all. I doubt Lineage OS has this, but presume that battery life would not be good.
Also, if you install microg apps, you can still use things such as cell and wifi based location, google push services, and ... I don't remember what else, however it hasn't been updated recently and many apps will complain and refuse to run saying that you need to update google play services, especially annoying for anything that uses push especially. Microg essentially sits in the place of where some functionality of Google Apps would and fills in some blanks.
When you don't have Google Apps installed, many paid apps will refuse to run as well, specifically the ones you paid for, because they can't verify the purchase with Google servers. There should be a **** list for any developers that don't cooperate when this is a problem for a user. I've only had one app developer help me on this, ever.
Thanks for your detailed answer!
You need to unlock the bootloader in order to flash a custom ROM and doing this erases, permanently, these DRM keys, so they need to be backed up and then put back later if you relock the bootloader and flash a stock ROM.
Click to expand...
Click to collapse
Does that mean that I can't use the DRM keys with another ROM? So I will never have the full quality of my hardware? Would using the AOSP rom provided by Sony solve that problem?
On which version of Android Jaguar Aries ROM is based? I searched for a lineageOS image but didn't find any for the Z3 Compact.
I had another z3c which died and was running Firefox OS, I'm fine with not having access to the Google Play store, I plan to install F-Droid and use only FOSS apps. In fact I would even prefer to go back to Firefox OS even if it is not maintained anymore, its UX is so much better than Android... That said, thanks for telling me about Microg, I didn't know it and that's true that many apps use Play services especially for push. Even Signal had that as a dependency (fortunately not anymore). Still, I would avoid any data coming out from my phone to by sent to Google servers, so I will probably avoid it.
Flaburgan said:
Thanks for your detailed answer!
Does that mean that I can't use the DRM keys with another ROM? So I will never have the full quality of my hardware? Would using the AOSP rom provided by Sony solve that problem?
On which version of Android Jaguar Aries ROM is based? I searched for a lineageOS image but didn't find any for the Z3 Compact.
I had another z3c which died and was running Firefox OS, I'm fine with not having access to the Google Play store, I plan to install F-Droid and use only FOSS apps. In fact I would even prefer to go back to Firefox OS even if it is not maintained anymore, its UX is so much better than Android... That said, thanks for telling me about Microg, I didn't know it and that's true that many apps use Play services especially for push. Even Signal had that as a dependency (fortunately not anymore). Still, I would avoid any data coming out from my phone to by sent to Google servers, so I will probably avoid it.
Click to expand...
Click to collapse
When you unlock the bootloader the DRM keys get erased permanently, so you'd need to root the phone and back up the partition where they are held before unlocking it. As far as I know, every custom ROM needs to have the bootloader unlocked. If there is an alternative way to install a ROM on a locked bootloader then it would be one of those scenarios where its installed while keeping the stock one, and I don't know if this has been done on the Z3c or not.
I also don't know if Sony's AOSP requires unlocking the bootloader or not.
Jaguar is based on 5.1.1
Its a mix of AOSP, Lineage, and was getting monthly backports of the latest security patches until Febuary when the developer no longer had a Z series phone for his own use. The only criticism it met was that the developer never released the source code for the entire ROM, just the kernel. He never replied to why that was. A lot of the custom ROMs out there are like this, so its still a case of who you choose to trust when it comes to this a lot of times. I liked it because the battery life was really good and assuming the security was what was advertised then that was also a real plus.
Many apps, by the way, were working fine with microg push but then with updates to apps, they complained about needing to update google services framework, which obviously was spoofed and microg hasn't been updated, and it happened to a lot of apps in a short period of time, so I assume there was a change enforced by Google for their requirements in the Play Store. If you just want it for location, for example if you use Osmand maps, then you don't have to enable the feature for push notifications nor have a google account associated with the phone, and it all works as user installed apps, so it can be undone without any real fear of the system getting modified after you try it out. There's a microg repo that can be added to fdroid. The location is based on either databases you download to the phone, which aren't very good, or also you can opt for cell location from Mozilla servers, and if you have to have wifi based location as well then you can hook into the Apple servers but the latter doesn't sound like something you want, if you want to do any of it at all that is.
I think most likely that GPS location would work without any need for microg.
The post you linked to with the Linux script installs TWRP to the /data partition, then you root it, then you back up the DRM keys after its rooted, then unlock the bootloader, install normal TWRP, and go from there. In Linux you'lle want to use the dd command to back up the DRM keys as all that's available on the forum is a Windows script (I think). There is info on it somewhere but it would be hard to find it. If you search my posts the thread will come up somewhere in the history. Anyway, the reason I broght this up is because the script in the thread for installing TWRP and rooting didn't work properly. I don't remember why, but I had to go through it line by line and enter the commands in from a termnial to get it right, I think there was some bad syntax. If you can't figure it out, quote one of my posts and ask, that way I get a notification that I was replied to, I think I have a fixed version of it on my drive somewhere if it causes a problem.
For the DRM keys you want to backup the TA partition bit for bit to a file. I backed up my Fota partition as well as I was unclear what role it plays. You also want to keep a copy of that particular Sony ROM file, and the two kernels involved, to flash with Flashtool in case you relock and restore so you can get root access to restore the partition while the bootloader is locked again.
May I ask why are you going FOSS only? if that's because privacy concerns, then FF OS is not the best solution... Because any Cloud-based OS is a little bit creepy, doesn't matter if it's ChromeOS from Google, or FirefoxOS from Mozilla.
There are plenty of Linux distros dedicated to run on Android phones, but it's not the best UX.
And yes, you can enjoy clean AOSP install (LOS is fine) without flashing G-Apps. But you won't have Google play at all! F-Droid is fine but you won't find there Gmail alternatives, you can't find Gmail even on Amazon AppStore... Sadly if you install Gmail then you'll find out that it installed bunch of google apps and hidden services behind the scenes... So only option is to use Gmail web app.
But then again, F-Droid is fine, there are many FOSS alternatives to youtube and other apps.
And if privacy (and security) is your concern, use LOS privacy guard / Android's builtin Permission Manager, and on Rooted ROMs you can use AFwall firewall which is the best.
Good luck
GadgetAvi said:
Because any Cloud-based OS is a little bit creepy, doesn't matter if it's ChromeOS from Google, or FirefoxOS from Mozilla.
Click to expand...
Click to collapse
Firefox OS is not a Cloud-based OS at all. It runs perfectly without internet connection.
GadgetAvi said:
F-Droid is fine but you won't find there Gmail alternatives, you can't find Gmail even on Amazon AppStore...
Click to expand...
Click to collapse
Be sure that if I don't want Google on my phone, my e-mails are already **not** on GMail...
Ok, if so, then you'll be fine with any AOSP clean rom. LOS is great, and F-Droid as well. Cheers!
PantsDownJedi said:
The post you linked to with the Linux script installs TWRP to the /data partition, then you root it, then you back up the DRM keys after its rooted, then unlock the bootloader, install normal TWRP, and go from there. In Linux you'lle want to use the dd command to back up the DRM keys as all that's available on the forum is a Windows script (I think).
Click to expand...
Click to collapse
I ran the commands and the phone is now booted on TWRP from the /data partition. I did a backup with TWRP of all proposed options (Boot, TrimArea, Recovery, System, Cache and Data). Is that "TrimArea" enough to have a backup of the DRM keys? The other topic talks about Backup-TA but looking at their github https://github.com/DevShaft/Backup-TA/releases it looks very old and unmaintained.
The current TWRP I'm running is 3.1.0-0.
Also, it looks like I'm not root (at least, su is not available). Do I have to install SuperSu by giving this zip https://download.chainfire.eu/696/supersu/ to TWRP?
Flaburgan said:
I ran the commands and the phone is now booted on TWRP from the /data partition. I did a backup with TWRP of all proposed options (Boot, TrimArea, Recovery, System, Cache and Data). Is that "TrimArea" enough to have a backup of the DRM keys? The other topic talks about Backup-TA but looking at their github https://github.com/DevShaft/Backup-TA/releases it looks very old and unmaintained.
The current TWRP I'm running is 3.1.0-0.
Click to expand...
Click to collapse
I don't know. I haven't looked at a TWRP backup to see what format it is. Back when Clockwork Mod was all that was available, it merely made a tar.gz of partitions. Ideally you want a bit for bit image of the TA partitions to make sure it was exactly what it was when you restore it. I don't know if that's necisarry, or if TWRP does this anyway, but using the dd command is still prudent.
You want to either use a terminal emulator app or run 'adb shell' at a linux terminal (much easier), run 'su' once in the phone environment, allow it at the phone supersu app popup, and then do it like this.
https://forum.xda-developers.com/showpost.php?p=61307511&postcount=6
And store a copy of the image file where it won't get lost.
Edit: Sorry, I didn't see the other post. Yes, you need to flash that supersu zip file. When you try to access root from an app or the command line, it will have a popup on the phone screen asking you if you want to allow access or not, so when you run it from a terminal, 'adb shell' to get into the phone OS, there will be a popup for allowing that often times. Then 'su' there's a popup from the supersu app you just flashed. Then 'cd' to the sdcard or external sd. Then the 'dd' command. The dd command in what I linked to is inevitbaly what all those .bat files in the Windows TA Backup thing does after it does a bit of looking around to find the TA partition for a particular phone model.
The md5sum part of what I linked to compares the partitionn itself to the image file you just wrote, you just look at it to see that there are two of them (that it didn't fail) and that they are the same.
The last part pulls the image file to the hard drive, but there are other ways to accomplish this obviously. If you have a cloud storage you can upload it there, or send it as an email attahment, put it on the external sd, etc etc.
Also, in many cases, once you unlock the bootloader to flash something else, you'lle need to install TWRP again from the command line, pushing it straight to a phone partition. You'lle need help with this if you haven't done it before.
Pulling my hair on this one; I have rooted the tab successfully, flashed cAndroid 5.01 and it runs great, but won't accept any of the dozen version of Gapps (GPS stop, AOSP keyboard fail, Play Store Hangs, etc.) I have tried, so I thought, let's just try AOSP or cAndroid Nougat, which I have successfully flashed to my Nexus 7 2012 (note re-purpose addiction). Various sideloaded apks work with no issue on the 5.0 ROM, no google apps or services.
I am running CW Mod for flashing and SR5-SuperSU 2.8 for root and the AOSP Rom exits with Status 0, and the cAndroid exits with Status 7, and I am hesitant to edit the install script. Rootcheck show device rooted successfully.
Any help with either would be appreciated, ultimate goal is getting Onenote to run, again, which I have done for both 5.x and 7.x on nexus, using old APKs
Upate your Recovery to the TWRP Version >= 2.8.7.0..
Do you have a link for the twrp build for the gt-p7310, can't find it listed under twrp supported devices
thanks
Searched with every criteria I can come up with, can't find a .zip for GT-P7310 or p5wifi for >2.7
SOLVED
Found right copy of TWRP, installed and now running Nougat on the tab, thanks for the assist
Spoke to soon , update to 7.1.2 goes fine, but no keyboard works none of them will activate when a text field is tapped
You can actives the keyboard under setting, language and inputs , vituelle keyboards
Thanks for the update ; I have the device working properly now with 7.1.2 AOSP thanks to updating my TWRM ; everything works but anything Google or Microsoft - I have tried every version of GApps Zips, APKs GPS back to 10.0.8, Gmail, Play, Gboard, etc. and everytime I introduce anything Google , it flakes out, get service stopped messages from Play Services, Gboard stops, etc. Oddly enough GHandwriting works which i use alot on m other tabs with Onenote, which also won't run, I am assuming b c of GPS; Onenote installs passively, but errors out 8000400 evertime, which seems to be some kind of sign in error, but TS steps I have found have not worked. OTher than the Google and MS snafus, device runs better than ever and i am resolved to using Evernote and exporting over to one note when i need to, any ideas would be appreciated , I like the size of this device and hate to trash anything useful - Thanks for the reply