GUIDE: ROOT, install XPOSED, and UNROOT/returning to stock a Galaxy S7 or S7 Edge - Verizon Samsung Galaxy S7 Guides, News, & Discussi

NOT WORKING? This method requires Marshmallow (Android 6.0), released with the phone at launch, in order to flash. Apparently this flash method won't work with any OTA update released over the last year or so, which means you cannot use anything in this guide if you're unable to flash these stock images. Sorry, I can't help you with that.
DISCLAIMER: I don't take credit for releasing a root method -- a huge giant thank-you goes out to Chainfire, Wanam, markhaines1985, PrinceComsy, Snoop05, x3demond3x, br3w3r, and everyone else who goes out of their way to make our phone experience better!
PERMANENT ROOT
Prerequisites: Samsung Galaxy S7 or S7 Edge (any carrier) and Microsoft Windows PC
Optional: I highly recommend making a backup of the data on your phone, including pictures and videos from the internal sdcard. If there is a problem at any point or if you need to unroot, there's a high likelihood of losing that data. Make sure you back up to an external sdcard or your computer or laptop.
Optional: Once satisfied with any backup you want to make, use my unroot guide to (a) upgrade to a more recent firmware if you're on an older firmware and (b) start from a fresh state. I have seen too many people have problems that were completely fixed by unrooting and re-rooting, so it's a good idea to just start fresh if you can.
Install Samsung USB device drivers
SAMSUNG_USB_Driver_for_Mobile_Phones.zip (mirror)
Install ADB (system-wide)
adb-setup-1.4.3.exe (MD5 hash 8C9085D4F753A2AAB26082FD2EB46A8E) (credit Snoop05)
On your phone, go into Settings -> Lock screen and security. Make sure that "Secure startup" is off/disabled. This option prevents the su binary from giving root.
Again on your phone, go into Settings -> About phone. Tap on the space that says 'Build number' seven times until it tells you that developer mode/options have been enabled. Tap back and then tap on Developer options. Make sure that developer options are on (general setting at the top of the Developer options screen) and then scroll down to USB debugging. Tap to enable USB debugging.
Connect phone to PC via USB.
At your PC, a Windows command prompt (Win+R and type 'cmd' and press enter or find it under Start -> Accessories). In the command prompt, type adb wait-for-device. Your phone may prompt you to authorize the computer and it is important that you approve the authorization and check on to "Always allow from this computer". If it doesn't prompt you, that's fine (you may have given it authorization some other time), but you should not skip this step or the root process may not work. After the adb command in command prompt returns to a blinking prompt, you may close the command prompt window (or just type exit inside the prompt).
Note: if typing the 'adb' command gives you the message "'adb' is not recognized as an internal or external command, operable program or batch file", then please check the F.A.Q./Help section of this guide.
Download and extract Odin3 v3.12 (try either version)
Odin3_v3.12.zip (MD5 hash F4BAE9E20925DA85854A9C49E8E06F1C)
Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C) (credit PrinceComsy)
Note: most people use the PrinceComsy version, but some AT&T users said the other version will prevent bootloop/stuck AT&T logo.
Download engineer-rooted boot image appropriate for your model of phone:
Samsung_G930x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7) (MD5 hash 948A01ECCF280828DFD13AC366F6FE85) (credit markhaines1985)
Samsung_G935x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7 Edge) (MD5 hash F3B7C5E4E8F6B31235ED0125371EB1F6) (credit markhaines1985)
Note that this download is a .TAR file and while it looks like an archive, you should not extract its contents.
Power off the phone. Turn it back on while holding Home, Volume Down, and Power buttons at the same time to enter download mode. Press Volume Up to confirm that you want to flash data to the phone.
Open Odin. Click 'AP' and select the appropriate AP TAR file:
Samsung_G930x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7)
Samsung_G935x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7 Edge)
Still in Odin, click 'Start' to flash the engineer-rooted boot image and reboot the phone.
When the phone has finished rebooting and while it is still connected to your PC, enter settings and re-enable USB debugging if it has been disabled.
Download and extract SuperSU flash package:
SuperSU-v2.76-S7QC.zip (MD5 hash E6990D0A34B0142C1F35D2EB386D748F) (mirror) (credit Chainfire)
Start the SuperSU flash package by double-clicking 'root.bat' from 'SuperSU-v2.76-S7QC'. Once it finishes, the phone will automatically reboot again. If double-clicking 'root.bat' only briefly shows a command prompt that quickly disappears, then most likely your PC is not recognized/authorized for USB debugging, the USB cable isn't connected, or ADB isn't properly installed. Check the steps above and try again or check the F.A.Q./Help section of this guide for more.
You'll know that the 'root.bat' process has completed successfully when your phone reboots. Once it has finished rebooting, SuperUser may inform you that the 'su' binary is outdated and that you should update. Dismiss this notice for now as Chainfire has indicated that our build is unsupported and that we should not update. As of right now (July 15, 2016), v2.76 is the most recent version for our phone.
Proceed to the recommended next steps to fix some odd quirks and behaviors with the root boot image.
RECOMMENDED NEXT STEPS (after rooting)
Prerequisite: rooted Samsung Galaxy S7 or Samsung Galaxy S7 Edge (any carrier)
Install Xposed (optional, instructions below).
Debloat and fix several issues with the phone (CPU lag issues, poor battery performance, phone becoming too hot, Wi-Fi not saving passwords, hotspot/tethering not working, VoLTE icon appearing, searching for service issues, MMS not working, unauthorized security nag notification, etc.):
On your phone, open the SuperSU app (installed during the root process) and tap on Settings. Half-way down under Security, tap on "Enable su during boot". This option will ensure that startup scripts that are installed during this process get to do their job correctly.
Install FlashFire on your phone:
https://play.google.com/store/apps/details?id=eu.chainfire.flash
Download the fix or fix+debloat script flashable ZIP package appropriate for your model of phone and copy this file to your device:
S7_or_S7Edge_Fixes_V15.zip (MD5 hash F15CD9BDC35382A8F48FFBEDBB1BCDF0) (any Samsung Galaxy S7 or S7 Edge)
S7_or_S7Edge_Fixes_Debloater_V15.zip (MD5 hash 4DED5D7B09BB7672723AAA77F395BC87) (any Samsung Galaxy S7 or S7 Edge)
VZWS7_PE1_Fixes_V15.zip (MD5 hash 7FEE320A9749B7CDFBAEACCBDC8AC45C) (Verizon Samsung Galaxy S7 on *PE1 firmwre)
VZWS7_PE1_Fixes_Debloater_V15.zip (MD5 hash 9146006E9A3C5AB5CAF9EB6123F7DB77) (Verizon Samsung Galaxy S7 on *PE1 firmwre)
VZWS7Edge_PE1_Fixes_V15.zip (MD5 hash 5F7CC8C95D316332B581F982D4ECAAF9) (Verizon Samsung Galaxy S7 Edge on *PE1 firmwre)
VZWS7Edge_PE1_Fixes_Debloater_V15.zip (MD5 hash 00850CA4D879660E74A54CFD3D47D0E5) (Verizon Samsung Galaxy S7 Edge on *PE1 firmwre)
What's special with the Verizon-only files? We flash a patched /system/framework/framework-res.apk that bypasses Verizon's Wi-Fi hotspot tethering provisioning. This is only compatible with the PE1 firmware and only for Verizon.
Full notes on what this flashable update does:
Adds a rotate button to the native gallery app.
Adds a shortcut call button in the call log next to each logged call.
Adjusts several CPU tunables, which fixes phone lag and battery life issues.
Disables "No SIM" popup when no SIM card is present.
Disables roaming data by default.
Disables secure storage support, which fixes Wi-Fi passwords not saving issue.
Disables Verizon provisioning for Wi-Fi tethering/hotspot (will still use your data plan, of course).
Enables ADB to run as root by default.
Enables CPU idling/sleeping, which fixes phone heat issues.
Enables mock GPS locations.
Enables native call recording feature in the dialer.
Enables native Wi-Fi calling feature in the dialer.
Enables RIL power saving features.
Enables scheduled messages in the native messaging app.
Enables the camera during calls.
Enables unlimited contact merging.
Enables using the new 3GPP2 Profile ID (Verizon exclusive).
Fixes various 'searching for service' and other cellular network connectivity issues (SMS/MMS not working, calls not working, etc.)
Knox apps, drivers, and data are removed (fix+debloat version).
Prefers LTE network.
Raises the contact name length limit to 1,280 characters.
Raises the maximum SMS recipient limit from 10 to 90.
Remove nagging 'unauthorized actions' security notification (fix+debloat version).
Removes VoLTE icon.
Removes bloatware and/or apps that can be downloaded from the Play Store and don't need to live in /system (fix+debloat version):
AdvSoundDetector2015
Amazon_Audible
Amazon_IMDB
Amazon_MP3
Amazon_Shopping
Amazon_Shopping_vpl
AmazonInstaller_ATT
AmazonKindle_vpl_ATT
AmazonShopping_vpl_ATT
BBCAgent
Bridge
BriefingPanel
Chrome
ChromeCustomizations
CloudGateway
com.customermobile.preload.vzw
com.govt.nflgamecenter.us.lite
com.samsung.android.securitylogagent
com.sec.knox.store
ContainerAgent
ContainerEventsRelayManager
DigitalLocker_ATT
Directtv_Shade_ATT
Directv_ATT
DriveMode_ATT
Facebook_stub
FamilyUtility_ATT
FBInstagram_stub
FlipboardBriefing
Gmail2
Go90
Hangouts
IgniteVerizon
Kindle
KLMSAgent
KnoxAppsUpdateAgent
KnoxAttestationAgent
KnoxFolderContainer
KnoxSetupWizardClient
KnoxSwitcher
LLKAgent
Lookout_ATT
Lookout_TMO
Maps
MILK_US
MobileLocate_ATT
Music2
MyATT_ATT
MyInfozone
NaverTvCast
Plenti_vpl_ATT
preloadedkiosk
preloadedmdm
preloadedsoo
RCPComponents
RemoteSupport_ATT
Safetyinformation
SDM
SDMViewer
SecHelp
SecurityLogAgent
SimLock_TMO
Slacker
Swype
UniversalMDMClient
Videos
VMS
VzCloud
VZNavigator
WhatsAppDownloader
WhitePagesNameId-release_TMO
withTV
Launch FlashFire on the phone and click the (+) button in the lower right to add a step. Select a 'Flash ZIP or OTA' flash step. Locate the flashable ZIP package and select it. For options, check on 'Mount /system read/write' and leave the rest of the options unchecked.
Scroll all the way down and click the 'Flash' lightning button in the lower left to commit this single step and wait a few moments. You should see the phone flash the package briefly before rebooting twice.
Problems getting this patch to run? Unfortunately, I can't test the universal script on devices I don't have, so if it's not compatible with your flavor of S7 or S7 Edge, you can perform most of the critical stuff manually by following these instructions:
Fix odd lag issues by setting the kernel governor to 'ondemand' or 'interactive' using Kernel Adiutor (ROOT) or Trickster MOD Kernel Settings:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
This is a poor-man's fix as it will not appropriately set CPU settings for both big and little core clusters, only the little core cluster. Also it won't re-enable some sleep states so it will still have battery issues.
Fix an issue with the Wi-Fi not saving passwords after reboots by editing the build.prop and setting 'ro.securestorage.support' to 'false'. I used JRummy's BuildProp editor:
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Remove nagging 'unauthorized actions' security notification by removing or disabling the SecurityLogAgent (com.samsung.android.securitylogagent) app using Package Disabler or Titanium Backup:
https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpro
https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
Hide the VoLTE icons by downloading and pushing a new APK:
imsservice.apk (credit x3demond3x)
Deep debloat: freeze all bloat using my separate guide (includes flashable update).
Also maybe check out my fine-tuning performance guide for the more hardcore.
Want ViPER4Android? There's a version for SELinux-enforcing kernels now that's compatible with our phone! (ViPERAtmos 4.8 Sony Beats Universal Edition.zip at the bottom of the linked thread)
INSTALL XPOSED (after rooting)
Prerequisite: rooted Samsung Galaxy S7 or Samsung Galaxy S7 Edge (any carrier)
Install FlashFire on your phone:
https://play.google.com/store/apps/details?id=eu.chainfire.flash
Download the Xposed flashable ZIP package and copy this file to your device:
xposed-v85.1-sdk23-arm64-custom-build-by-wanam-20160530.zip (MD5 hash F62C21CA8A8B7E015622D116CD8F4B8C) (credit Wanam)
Launch FlashFire on the phone and click the (+) button in the lower right to add a step. Select a 'Flash ZIP or OTA' flash step. Locate the Xposed flashable ZIP package and select it. For options, check on 'Mount /system read/write' and leave the rest of the options unchecked.
Click the (+) button again to add another step. Select Wipe and only choose to wipe the 'Dalvik cache' and the 'Cache partition' (format method not required, but it won't hurt, either).
Scroll all the way down and click the 'Flash' lightning button in the lower left to commit these two steps and wait a few moments. You should see the phone flash the package briefly before rebooting twice.
During the final reboot, you will see the animated boot screen appear for a very long time (three to five minutes or longer) before the screen changes to an 'Android is starting...' green screen with animated gears indicating that it is 'optimizing' apps. It is building a new Dalvik cache which should take several minutes. This is all normal; so no need to panic if it takes longer!
Once the phone finally finishes booting, you can continue.
Download the Xposed Installer APK and install it from internal storage or over ADB:
XposedInstaller_3.0_alpha4.apk (credit Wanam)
RETURN TO STOCK (unroot)
Prerequisites: Samsung Galaxy S7 or S7 Edge and Microsoft Windows PC on one of these carriers: AT&T, Sprint, T-Mobile, US Cellular, or Verizon
Install Samsung USB device drivers
SAMSUNG_USB_Driver_for_Mobile_Phones.zip (mirror)
Connect phone to PC via USB.
Download and extract Odin3 v3.12 (try either version)
Odin3_v3.12.zip (MD5 hash F4BAE9E20925DA85854A9C49E8E06F1C)
Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C) (credit PrinceComsy)
Note: most people use the PrinceComsy version, but some AT&T users said the other version will prevent bootloop/stuck AT&T logo.
Download and extract the Samsung Galaxy S7 or S7 Edge stock firmware image appropriate for your model of phone:
ATT_G930AUCS2APF2.zip (MD5 hash B9314F30E00E541C8700DC9F5E039513) (AT&T Samsung Galaxy S7)
ATT_G935AUCS2APF2.zip (MD5 hash BB4904F9D6E730F23AE0DC727AC87752) (AT&T Samsung Galaxy S7 Edge)
SPT_G930PVPU2APF2.zip (MD5 hash A463543B398CE49FD7F5DE97DF456AB3) (Sprint Samsung Galaxy S7)
SPT_G935PVPU2APE1.zip (MD5 hash C31850FE02C0EDC5588ECAB99A6B5D2F) (Sprint Samsung Galaxy S7 Edge)
TMB_G930TUVU3APG1.zip (MD5 hash 0BD0E1899113643C46916BB597CB7212) (T-Mobile Samsung Galaxy S7)
TMB_G935TUVU3APG1.zip (MD5 hash EB35AB39E178C3EC442632FE6D61B0B5) (T-Mobile Samsung Galaxy S7 Edge)
USC_G930R4TYU2APE2.zip (MD5 hash BC9AFEF1E508D10DA1BC17638C25959B) (US Cellular Samsung Galaxy S7)
USC_G935R4TYU2APE2.zip (MD5 hash F5A361989EADBF65A178F0A2212CC376 ) (US Cellular Samsung Galaxy S7 Edge)
VZW_G930VVRU2APE1.zip (mirror) (MD5 hash 248CAE83530C167F98B2EAF4AA93E79A) (Verizon Samsung Galaxy S7)
VZW_G935VVRU2APE1.zip (mirror) (MD5 hash C01226B362F123945B3E4C1F257A501A) (Verizon Samsung Galaxy S7 Edge)
Power off the phone. Turn it back on while holding Home, Volume Down, and Power buttons at the same time to enter download mode. Press Volume Up to confirm that you want to flash data to the phone.
Open Odin. Click 'AP' and select the appropriate AP TAR file:
AP_G930AUCS2APF2_CL7617530_QB9897892_REV02_user_low_ship_MULTI_CERT.tar.md5 (AT&T Samsung Galaxy S7)
AP_G935AUCS2APF2_CL7617530_QB9897831_REV02_user_low_ship_MULTI_CERT.tar.md5 (AT&T Samsung Galaxy S7 Edge)
AP_G930PVPU2APF2_CL8196840_QB9937218_REV02_user_low_ship_MULTI_CERT.tar.md5 (Sprint Samsung Galaxy S7)
AP_G935PVPU2APE1_CL7925126_QB9447145_REV02_user_low_ship_MULTI_CERT.tar.md5 (Sprint Samsung Galaxy S7 Edge)
AP_G930TUVU3APG1_CL8439036_QB10212948_REV02_user_low_ship_MULTI_CERT.tar.md5 (T-Mobile Samsung Galaxy S7)
AP_G935TUVU3APG1_CL8439036_QB10213096_REV02_user_low_ship_MULTI_CERT.tar.md5 (T-Mobile Samsung Galaxy S7 Edge)
AP_G930R4TYU2APE2_CL7999897_QB9615072_REV02_user_low_ship_MULTI_CERT.tar.md5 (US Cellular Samsung Galaxy S7)
AP_G935R4TYU2APE2_CL7999897_QB9615073_REV02_user_low_ship_MULTI_CERT.tar.md5 (US Cellular Samsung Galaxy S7 Edge)
AP_G930VVRU2APE1_CL7722939_QB9709794_REV02_user_low_ship_MULTI_CERT.tar.md5 (Verizon Samsung Galaxy S7)
AP_G935VVRU2APE1_CL7722939_QB9709803_REV02_user_low_ship_MULTI_CERT.tar.md5 (Verizon Samsung Galaxy S7 Edge)
It will take a few moments to verify the MD5 of this very large file.
Now click 'CP' and select the appropriate CP TAR file:
CP_G930AUCS2APF2_CL7617530_QB9897892_REV02_user_low_ship_MULTI_CERT.tar.md5 (AT&T Samsung Galaxy S7)
CP_G935AUCS2APF2_CL7617530_QB9897831_REV02_user_low_ship_MULTI_CERT.tar.md5 (AT&T Samsung Galaxy S7 Edge)
CP_G930PVPU2APF2_CL8196840_QB9937218_REV02_user_low_ship_MULTI_CERT.tar.md5 (Sprint Samsung Galaxy S7)
CP_G935PVPU2APE1_CL7925126_QB9447145_REV02_user_low_ship_MULTI_CERT.tar.md5 (Sprint Samsung Galaxy S7 Edge)
CP_G930TUVU3APG1_CL8439036_QB10212948_REV02_user_low_ship_MULTI_CERT.tar.md5 (T-Mobile Samsung Galaxy S7)
CP_G935TUVU3APG1_CL8439036_QB10213096_REV02_user_low_ship_MULTI_CERT.tar.md5 (T-Mobile Samsung Galaxy S7 Edge)
CP_G930R4TYU2APE2_CL7999897_QB9615072_REV02_user_low_ship_MULTI_CERT.tar.md5 (US Cellular Samsung Galaxy S7)
CP_G935R4TYU2APE2_CL7999897_QB9615073_REV02_user_low_ship_MULTI_CERT.tar.md5 (US Cellular Samsung Galaxy S7 Edge)
CP_G930VVRU2APE1_CL7722939_QB9709794_REV02_user_low_ship_MULTI_CERT.tar.md5 (Verizon Samsung Galaxy S7)
CP_G935VVRU2APE1_CL7722939_QB9709803_REV02_user_low_ship_MULTI_CERT.tar.md5 (Verizon Samsung Galaxy S7 Edge)
Now click 'CSC' and select the appropriate CSC TAR file:
CSC_ATT_G930AATT2APF2_CL7617530_QB9897892_REV02_user_low_ship_MULTI_CERT.tar.md5 (AT&T Samsung Galaxy S7)
CSC_ATT_G935AATT2APF2_CL7617530_QB9897831_REV02_user_low_ship_MULTI_CERT.tar.md5 (AT&T Samsung Galaxy S7 Edge)
CSC_SPT_G930PSPT2APF2_CL8196840_QB9937218_REV02_user_low_ship_MULTI_CERT.tar.md5 (Sprint Samsung Galaxy S7)
CSC_SPT_G935PSPT2APE1_CL7925126_QB9447145_REV02_user_low_ship_MULTI_CERT.tar.md5 (Sprint Samsung Galaxy S7 Edge)
CSC_TMB_G930TTMB3APG1_CL8439036_QB10212948_REV02_user_low_ship_MULTI_CERT.tar.md5 (T-Mobile Samsung Galaxy S7)
CSC_TMB_G935TTMB3APG1_CL8439036_QB10213096_REV02_user_low_ship_MULTI_CERT.tar.md5 (T-Mobile Samsung Galaxy S7 Edge)
CSC_USC_G930R4USC2APE2_CL7999897_QB9615072_REV02_user_low_ship_MULTI_CERT.tar.md5 (US Cellular Samsung Galaxy S7)
CSC_USC_G935R4USC2APE2_CL7999897_QB9615073_REV02_user_low_ship_MULTI_CERT.tar.md5 (US Cellular Samsung Galaxy S7 Edge)
CSC_VZW_G930VVZW2APE1_CL7722939_QB9709794_REV02_user_low_ship_MULTI_CERT.tar.md5 (Verizon Samsung Galaxy S7)
CSC_VZW_G935VVZW2APE1_CL7722939_QB9709803_REV02_user_low_ship_MULTI_CERT.tar.md5 (Verizon Samsung Galaxy S7 Edge)
Now click 'Start' to flash the stock images and reboot the phone.
F.A.Q. / HELP, I'M STUCK!
Will I lose my data during the root process?
You shouldn't if you're just rooting, however you should always make a backup. Helium from the Play Store is a good choice as is Samsung's built-in cloud backup. If you have to flash the stock image for any reason, it will erase your app data as well as the internal storage (internal sdcard) so be sure you copy any important files to a safe location first. It's always a good idea to have backups and it's generally assumed that users who are looking for root/admin access to their phones know and accept the risks involved.
Does this method trip Knox?
No, it doesn't. And flashing back to stock will allow Knox to work again, as long as you didn't flash files from other sources (there are some that will trip Knox, so be careful).
Does Samsung Pay work?
No, sorry. They can detect the rooted boot environment through a driver, so you can't even hide root from the app using RootCloak.
Does Android Pay work?
It does, but you have to make a change that disables root and then reboot your phone. You can toggle this back/forth without flashing, but you either get root or Android Pay at any one time.
What happens if I brick my phone?
As long as there are stock images to flash back to, it's almost impossible to do this no matter how badly the process goes. Check that we have stock images; if we do, then we can always flash them over the device using the unroot method in this guide. That practically guarantees a return-to-stock experience for a phone as long as it doesn't have any serious physical damage preventing it from powering on.
I installed the ADB system-wide on my Windows computer/laptop, but I see "'adb' is not recognized as an internal or external command, operable program or batch file".
Your user profile path can't contain a space. That means if your Windows user is 'Somebody Nice' and thus your Windows user path is 'C:\Users\Somebody Nice', the install will fail. You can create another user on your computer (if prompted for a Microsoft login, choose to make only a local account) and enter a short, single-word name for your user. Sign into and use that user profile instead. Also, the path where you extract the SuperSU package can't contain a space, so try extracting them to somewhere simple like perhaps C:\S7Root.
I can't get Odin to flash the images.
This typically means you haven't followed the instructions carefully. Read the prerequisites for each section, don't skip or skim anything, and make sure you've downloaded the files for your phone. This guide works for both the S7 and S7 Edge, so only download the correct files relative to your device. There are also two versions of Odin going around that work slightly different from each other. If one is causing issues, try the other.
BusyBox won't install.
Try another BusyBox installer, like JRummy's BusyBox for Android which is known to work.
I am seeing odd blank menus in Settings that causes it to force-close when I click it. Also Quick Settings force-closes when editing.
We suspect that XTouchWiz is causing this and I recommend uninstalling that Xposed module. Then either flash the latest version of my fix+debloater package in the 'Recommended Next Steps' section or manually use a file explorer to delete /system/csc/feature.xml (leave everything else alone). Reboot and the menus and force-closes should be fixed.
Additional Credit:
Thanks @Chainfire for supporting us with a custom SuperSU and su binaries on our devices, for Flashfire, and for so, so much more over the years.
Thanks @wanam for his great work with Xposed.
Thanks @princecomsy for his original guide in the AT&T S7 forum and the many people posting with their early findings and notes as well as his version of Odin.
Thanks @x3demond3x for a new imsservice.apk.
Thanks @jrkruse for the original S7 Edge fixes/debloater script and a patched framework-res.apk for Verizon phones.
Thanks @airos4 for a hint about secure startup preventing the su binary from functioning.
Thanks @cuezaireekaa for several suggestions and a link to working ViPER4 for our SELinux-enforcing phone.
Notes:
I am using the PrinceComsy version of Odin in these instructions. I understand that it's not necessary for all carrier variants, but for consistency it made its way to my notes and is the version that I personally used. Additionally, I have mirrored most of these files on my server since they were originally uploaded to websites with malicious ads and malware.

nice, thanks! the original thread says since this is an engboot, it's unstable and not advised for daily use. does that mean this will be buggy if we root? are there ways to make it more stable?

jayochs said:
nice, thanks! the original thread says since this is an engboot, it's unstable and not advised for daily use. does that mean this will be buggy if we root? are there ways to make it more stable?
Click to expand...
Click to collapse
I think the caution is that the boot image wasn't intended for everyday use so there's the potential for quirky behavior. Except for the WiFi issue (there's a set-it-and-forget-it workaround), I haven't had any issues and have been using it all day setting up all my favorite root stuff.

so i assume this completely wipes the phone, right? so the wifi issue is fixed by a build prop edit too?
Sent from my Samsung Galaxy S7 using Tapatalk

jayochs said:
so i assume this completely wipes the phone, right?
Click to expand...
Click to collapse
Only to unroot, you can otherwise root and install Xposed without clearing data just fine.
jayochs said:
the wifi issue is fixed by a build prop edit too?
Click to expand...
Click to collapse
Yep, can personally confirm.

psouza4 said:
Only to unroot, you can otherwise root and install Xposed without clearing data just fine.
Yep, can personally confirm.
Click to expand...
Click to collapse
Been trying to unlock LTE band 12 on my vzw s7. With root, can i access Diag mode via hidden menu? Has anyone try this yet?
Will hidden menu work by just enable band 12 without qualcomm dp tool?

It's anyone's guess -- try it and report back? We're kind of treading in new waters here.

Thank you for the info, I am rooted, let the debloating begin! Any thoughts on wifi hotspot yet?

Does anyone know if making a bad build.prop change and getting into a bootloop can be resolved by simply re-flashing (dirty) the engineering firmware again? I only ask because I find it dangerous to be messing with root settings if I do not have the ability to do a full backup in TWRP...

xocomaox said:
Does anyone know if making a bad build.prop change and getting into a bootloop can be resolved by simply re-flashing (dirty) the engineering firmware again? I only ask because I find it dangerous to be messing with root settings if I do not have the ability to do a full backup in TWRP...
Click to expand...
Click to collapse
If you bootloop, your best option (since we don't have custom recovery) is to grab the stock Verizon S7 image, flash it, boot your phone and go through the normal setup, then perform the root steps again. I had to do this when I made a mistake trying to get Xposed working and was deodexing files (unnecessary anyway, it turns out).
If you're on an S7 Edge, there aren't any stock files to flash though that I've seen offhand, so that could be dangerous. You'll note that my unroot/restore method has a prerequisite that includes the S7 not an S7 Edge.
TL;DR: on a Verizon S7, you can recover from bootloop, screwing up your /system partition, etc.

psouza4 said:
If you bootloop, your best option (since we don't have custom recovery) is to grab the stock Verizon S7 image, flash it, boot your phone and go through the normal setup, then perform the root steps again. I had to do this when I made a mistake trying to get Xposed working and was deodexing files (unnecessary anyway, it turns out).
If you're on an S7 Edge, there aren't any stock files to flash though that I've seen offhand, so that could be dangerous. You'll note that my unroot/restore method has a prerequisite that includes the S7 not an S7 Edge.
TL;DR: on a Verizon S7, you can recover from bootloop, screwing up your /system partition, etc.
Click to expand...
Click to collapse
Oh, damn! That's no good. I had no idea the S7 Edge had no "return to stock" method.
But if we re-flash that engbuild of the firmware (assuming you can get to a point to actually flash it) then it should revert any build.prop changes made and be okay.
EDIT: What about these? http://forum.xda-developers.com/verizon-s7-edge/how-to/firmware-verizon-s7-edge-t3344092

xocomaox said:
But if we re-flash that engbuild of the firmware (assuming you can get to a point to actually flash it) then it should revert any build.prop changes made and be okay.
Click to expand...
Click to collapse
No, the engboot is just a rooted engineer's boot image and does not affect the system partition that I'm aware of, thus it can't fix issues with the system partition.
xocomaox said:
Oh, damn! That's no good. I had no idea the S7 Edge had no "return to stock" method.
EDIT: What about these? http://forum.xda-developers.com/verizon-s7-edge/how-to/firmware-verizon-s7-edge-t3344092
Click to expand...
Click to collapse
Bingo -- that's exactly what you need to restore a /system partition in case of error or for warranty reasons, etc. Glad you found it! I may have to update my notes.

psouza4 said:
No, the engboot is just a rooted engineer's boot image and does not affect the system partition that I'm aware of, thus it can't fix issues with the system partition.
Click to expand...
Click to collapse
Now I understand, thank you!

Anybody else getting constant Samsung security alert notices after rooting? Mine pop up after I reboot the phone.

sasquatch1 said:
Anybody else getting constant Samsung security alert notices after rooting? Mine pop up after I reboot the phone.
Click to expand...
Click to collapse
Freeze the package SecurityLogAgent (com.samsung.android.securitylogagent) using Package Disabler or Titanium Backup, etc.. I'll add it to my recommended next steps.

psouza4 said:
Freeze the package SecurityLogAgent (com.samsung.android.securitylogagent) using Package Disabler or Titanium Backup, etc.. I'll add it to my recommended next steps.
Click to expand...
Click to collapse
Thank you, that worked. Is there a work around to get the Charging/Photo/File transfer back in the notifications drop down? All I have is Charging listed.

sasquatch1 said:
Thank you, that worked. Is there a work around to get the Charging/Photo/File transfer back in the notifications drop down? All I have is Charging listed.
Click to expand...
Click to collapse
I haven't encountered this issue, but I'm on a fresh data wipe after installing Xposed just because I'm paranoid about random issues (and several have been reported). You may want to check Settings -> About Phone -> tap on the device build a bajillion times until it tells you that you're a developer -> back out -> Developer Options -> USB configuration (about half way down)

I haven't updated since launch. Should I take the security updates prior to this or can I take them after?

sasquatch1 said:
Thank you, that worked. Is there a work around to get the Charging/Photo/File transfer back in the notifications drop down? All I have is Charging listed.
Click to expand...
Click to collapse
I also had the same problem however if you go into settings, developer options, there is an option under the "networking" section called USB configuration and you can change it to MTP or whatever you would like there.
found here by j3ffm1ll, so give him your thanks.
edit... oops, i guess psouza4 also mentioned it, but for some reason i thought it was talking about toggling the debug option. so i guess give him your thanks. lol, sorry

goblygoop said:
I haven't updated since launch. Should I take the security updates prior to this or can I take them after?
Click to expand...
Click to collapse
I did (two weeks ago, finally had given up hope) and it's fine. Even if it weren't, we have stock images we can flash. So all is well!

Related

[Ref] Galaxy Nexus 4.3 tips & tricks with important info to know

Hello everyone, i see here to collect and post some known and maybe unknown tips and tricks with some important information, hoping this will be useful for users.
Any more tips, tricks and suggestions from users are always welcomed. And please feel free to make corrections for any wrong or missed information in this post
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Preface:​
The Galaxy Nexus (GT-I9250) is a touchscreen Android smartphone developed by a partnership between Google and Samsung. The phone and operating system were developed collaboratively by engineers from both companies. It is the third generation successor to Google's previous flagship phones: the Nexus One and Nexus S. The Galaxy Nexus has a high-definition (1280 × 720) Super AMOLED display with curved glass, an improved camera and has an unlockable bootloader to allow further development and end-user modification. Nexus devices are the first Android devices to receive updates to the operating system. The name of this smartphone is the result of co-branding between the Samsung Galaxy and Google Nexus brands of Android smartphones. The device is known as the Galaxy X in Brazil, however, due to a trademark on the "Nexus" brand.
The Galaxy Nexus was unveiled jointly by Google and Samsung on October 19, 2011 in Hong Kong. It was released in Europe on November 17, 2011.
It is one of the few phones recommended by the Android Open Source Project for building Android from source.
The Galaxy Nexus is no longer available for sale on the Google Play Store as of October 29, 2012 with the announcement of its successor, the LG Nexus 4.
Click to expand...
Click to collapse
OTA 4.3 (JWR66Y)​
Google begins to roll Jelly Bean 4.3 on Gnex which have some notable modifications but not at the level that users expect. Not as usual, OTA begun to roll first on yakju build not takju. Users who already got their hands on the latest firmware update have reported what is new:
- More secured ADB. (as 4.2.2)
- Fix the Bluetooth audio bugs.
- Better battery performance noticed.
- Performance enhancements.
-System UI lag also gone.
-Camera rotation lag is reduced.
-Dial pad autocomplete, can be enabled from call settings.
-you will notice more ram freeing.
-Google Hindi Input is added in "Language and imput".
-supporting of App Ops (optional permissions), see here.
** 4.3 supports now "OpenGL ES 3.0" for High-Performance Graphics and "Connectivity with Bluetooth Smart devices and sensors" and "Optimized Location and Sensor Capabilities", but unfortunately, our devices does not support it.
Support for "Restricted Profiles" is only for Nexus tablets
Did you install Android 4.3 on your Nexus device? Have you noticed anything new in Android 4.3? Please post it.
Click to expand...
Click to collapse
Questions & Answers​
Q1) I didn't receive OTA update and i am on unrooted stock firmware?
A Go to Settings > Apps > All > Google Services Framework, clear data, then go to Settings > About phone > System update > Check now. repeat procedure many times.
Q2) Kies program does not recognize my Gnex, i want to update firmware?
A Gnex firmware is not supported by Samsung Kies. it is updated directly from Google.
Q3) Can i make a screen shot on stock firmware?
A Yes you can! user doesn’t need to root the device or employ third-party apps just to take a photo of what's happening on screen. Taking a screenshot is simple, just press the volume down and power buttons together. The device will quickly take a snapshot of the screen and you will find it in your notifications.
Q4) What is Barrel Roll?
A As part of Google's regular antics, it had introduced a "barrel roll" trick for desktop browsers. Type "do a barrel roll" as a search term, and Google would demonstrate the power of modern browsers by flipping everything around on your screen. Your Android device can also do a barrel roll if you speak out the same command. Again, It's great fun to show off.
Q5) How can i uninstall an app. without going to setting?
A Long-pressing on an app within the app drawer pops up a couple of menus along the top of the screen. App Info gives you the boring technical stuff about how much memory it's taking up, or you can fling it off the other way to uninstall it.
Q6) How can i go directly to the quick settings menu?
A expand notification bar by sliding two fingers.
Q7) What is inverted rendering?
A Inverted rendering is a posh way of saying it makes the pages black and turns the text white, so it looks like you're reading the internet from 1997. It also supposedly saves battery, plus is easier on the eyes if you're reading in the dark. It's under the browser's settings tab, within the accessibility area - and there's a contrast slider, too.
Q8) How can i reboot into safe mode?
A Safe mode, the savior of so many Windows PCs! If you are experiencing a problem with your Gnex and you want to determine whether it is being caused by a third-party app, long-press the power button, then long-press the Power off option. Choose OK to reboot in safe mode, which completely disables all third-party apps on your device. If the problem goes away when you’re in safe mode, you should reboot your device and start removing recently installed apps until the problem goes away.
Q9) What does reset app. preferences means?
A Android gives you loads of different options for each installed app, and on the whole this is a very good thing. Sometimes it can be a bad thing, though: you may find your phone playing up because a crucial app has been disabled, or you've changed the notifications for something important like emails. In the apps drawer, you'll find Reset app preferences under the settings. This resets all your apps on a global level, returning actions and data settings to their original levels.
Q10) What is imojis?
A "Emojis" are the Japanese version of emoticons. You can enable emoji support for the default Jelly Bean keyboard by choosing Language & input in the settings app, then going to the settings for the stock Android keyboard. Here, choose Add-on dictionaries and select Emoji for English words. When you next type certain words (there's a complete list here) you'll see its symbol appear in the predictions bar.
Q11) What is the difference between takju and yakju?
A These android builds are almost the same but there are some differences in terms of their android updates. Takju: Mobiles which brought from Google play store in USA and come with a Google wallet pre-installed. In these devices, android update is pushed by Google itself and they are almost first to receive an OTA update. Yakju: Mobiles which brought from Google store but outside of USA, update are also pushed by Google, but this update might delay by some days or weeks. So, do check your android build if your device is running android build other than takju, then change it in takju build to an OTA update first.
Q12) How do i know what is my Gnex android build?
A Download Android System Info application from play store or you can check it from Maps>setting>about.
Q13) I can not see Developer Options in settings?
A Google hide this option, to enable it just go to settings---->about phone, tap 7 times on "build number" and it will be shown in settings.
Q14) how to make apps, data and sdcard backup & restore?
A Refer to post # 286.
Q15) I received 4.3 OTA update, ADB can not recognize my Gnex. What should I do?
A Download and install Android SDK, if you already have it on your PC just update tools and platform-tools. you must have latest ADB version (1.0.31). If you do not want to install Android SDK, download attached file (thx to xaueious).
Q16) How can i make my Gnex feel snappier?
A By speeding up (or disabling) the animated fade-in effects you see when switching between tasks, you’ll see a boost in performance and faster screen transitions. Start by unhiding “Developer options” as described above. Once in “Developer options,” scroll down to the “Window animation scale” and “Transition animation scale” options and set both to .5x. You can even turn each of these off and transitioning between apps and pages will be almost instant. If you ever want to go back, remember the defaults for both of these settings are 1x.
Q17) How can i improve my gaming graphics?
A If you are a hard-core gamer, you probably already know what 4x anti-aliasing is. First, enable Developer Options as described above, then go to Settings and click on Developer Options and enable Force 4x MSAA. Multisample anti-aliasing (MSAA) is a technique used to improve image quality. Since the Gnex has a GPU capable of supporting MSAA, this setting should make your graphics look more detailed when you are playing advanced games. Keep in mind this will also cause your GPU to work harder and your device may get hotter and consume more power than normal. It’s also possible that all games may not support this.
Q18) I want to see Jelly Bean on my screen, can i?
A Yes you can, go to settings---->about phone tap quickly 4-5 times on android version, you will see a big Jelly bean, touch and hold it, you will see small flying Jelly beans.
Q19) How can i customize my LED notifications?
A A free app called Light Flow Lite allows you to take control of the colors of your notification LED. It also makes your Gnex flash one color after another. This app allows you to set the notification color for over 250 applications and system events including missed calls, low battery, no signal, voice mail, calendar reminders, Gmail messages, email messages, SMS messages, MMS messages, Twitter notifications and more.
Q20) How can i put my Gnex in fastboot/recovery mode?
A Turn off your phone, press and hold down Volume Up and Down keys + Power button at the same time until fastboot (bootloader) mode (image of an Android with Start) appears then release the keys. Press volume up or down and select recovery by pressing power button. (For stock recovery, when you see an android logo with exclamation mark, press power + volume up to see the recovery menu).
Q21) How can i put my Gnex in download mode (odin mode)?
A Turn off your phone, press and hold down Volume down + Power button at the same time until odin mode appears then release the keys.
Q22) Why google voice search is crashing when i press on mic when i am on a custom rom?
A Update google search from play store.
Q23) My Gnex screen is turning on by itself, what is happening?
A It is caused by an application, usually by live wallpapers, try to find it and delete it, or install an antivirus app., i recommend Dr.Web Anti-virus, scan, delete, wipe cache and dalvik (optional).
Q24) sometimes i lose packet data (3G) when i turn it off then on, i turn off then turn on my Gnex to enable packet data again?
A There is no need to turn your phone off and on to re-enable packet data, just long press on power button, enable airplane mode for 3-5 seconds then disable it.
Q25) I rooted my Gnex, what to do next?
A It is recommended to make a nandroid backup immediately.
Q26) I rooted my Gnex 4.3, made a nandroid backup, but i can not find my backup folder?
A Use a file manager, enable root option, your backup folder is located in data/media/clockworkmod or mnt/shell/emulated/clockwordmod.
Q27) The kernel does not support PGM, is there a solution?
A change the kernel, or install intellicover application.
Q28) Do i need to wipe cache partition when flashing a new rom?
A No, there is no need to wipe cache, because when you wipe data/factory reset, cache is wiped automatically. Some said to wipe cache and dalvik after flashing a new rom to prevent any potential conflict.
Q29) I rooted my Gnex 4.3, flash custom recovery, but when i reboot into recovery, it shows the stock recovery!?
A Every OTA update places two files on device system (that are not there on a non-update stock ROM) that re-flash the stock recovery on EVERY boot. The two files are /system/recovery-from-boot.p and /system/etc/install-recovery.sh. You need to make sure that these files are either deleted or renamed, or else custom recovery will disappear when you reboot. These files serve no purpose other than re-flashing the stock recovery on every boot. So, by using something like Root Explorer, delete or rename them, and re-flash your custom recovery.
Q30) My Gnex won't start, i can not get into fastboot mode, only i can get into download mode?
A Use odin to flash stock firmware here.
Q31) What is the easiest way to install samsung driver?
A The easiest way is to install Samsung Kies.
Q32) How can i flash stock image on my Gnex?
A See efrant thread.
Q33) What about governors, I/O schedulers.....?
A See droidphile thread.
Q34) How to properly post a kernel bug (LAST_KMSG)?
A See ciprianruse88 thread.
Q35) What is the best kernel for my Gnex?
A There is no something called "best kernel". You must try many kernels and decide what suit your rom and your need.
Click to expand...
Click to collapse
Rooting:​
Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. Rooting is similar to jailbreaking devices running the Apple iOS operating system. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system. Rooting enables all the user-installed applications to run privileged commands that are typically unavailable to the devices in their stock configuration.
Legality: The Free Software Foundation Europe argues that it is legal to root or flash any device. According to the European Directive 1999/44/CE, replacing the original operating system with another does not void the statutory warranty that covers the hardware of the device for two years unless the seller can prove that the modification caused the defect.
On July 26, 2010, the United States announced a new exemption making it officially legal to root a device and run unauthorized third-party applications, as well as the ability to unlock any cell phone for use on multiple carriers.
Safety: I Have always said that the person should learn the Android OS before rooting. It is a good idea to have an idea of what rooting is doing and what it will affect. I would say spend your time really learning the OS which is not a small task. Then, if you still feel like it, go ahead and root. While rooting can help you learn many things about your device, it also can reap very bad consequences, such as:
-Bricking your phone (or in an easier way to explain, making your phone a pretty paper weight).
-Corrupting core files.
-Stopping OTA updates from going to your phone.
-Voiding phone warranty.
-Have your phone open to malicious software and applications that can do serious harm to your phone.
As you can see, it can reap very negative things. I have read/seen people who have literally had to buy brand new phones because they tried the latest and greatest rom. Rooting is essentially something that you must take at your own risk & caution. Generally, if you follow exactly the procedure of rooting made by developers, you will be more likely on the safe side.
Root process: See jabakuba thread.
What to do after rooting?: 1) make a nandroid backup via custom recovery 2) backup efs partition (save your IMEI and NV_DATA):
Install "terminal emulator" from play store, open it and type the following (enter after each line):
Code:
su
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img
Then move efs.img to a safe place on your pc.
Click to expand...
Click to collapse
Problems can happen:​
-Stuck into a Bootloop: Bootloops are mainly caused by system files interfering with each others which cause instability and/or crash at the boot sequence. so what to do??
Pull out battery then reinsert it, boot into recovery, wipe cache and dalvik, reboot. If not, format data, system, cache using recovery and restore stock firmware (supposing that you did a nandroid backup before). if you don't have a backup to restore, flash any custom rom from your sdcard after formatting system & data & cache. If you don't have a custom rom in your sdcard, push one from your pc using adb (supposed that you have adb file or sdk on your pc): boot into recovery, connect your phone to the computer open command prompt and write the following command then hit enter (supposing that your rom is placed on D):
Code:
adb push D:\name of rom.zip /data/media/
Or
Code:
adb push D:\name of rom.zip /sdcard/
Then
Code:
adb reboot recovery
once done, go to your phone and install the rom.zip from recovery, reboot.
If none of above methods works, then flash stock image for your Gnex using fastboot commands here.
-Phone-Triangle-computer: If your phone can not boot, can not boot in fastboot or download modes, maybe after a bad flash, and screen shows phone--triangle--computer pic, so it is sort of download mode, use odin to flash stock firmware using this tutorial.
-Nexus is quietly dead: If your phone did not respond to anything, it won't turn on, can not boot into fastboot or download mode, black screen, try "OMAP FLASH", it can save your Gnex.
For 4.2.2 only:
-AOSP Rom incompatibility: After supplying all needed hardware drivers by AOSP, developers has updated AOSPA. So you absolutely need to be up to date regarding Google Bootloaders and Radios, which are not part of the Rom. Or else your device will be incompatible, unable to make calls perhaps and maybe other issues.
Regarding Bootloader, it still the same build for 4.2.2 (primelc03) but the Radio has changed to xxlj1. So you must flash Radio to the latest build using "Fastboot" or through "Recovery":
Fastboot method:(I prefer this)
Unzip "fastboot-radio-maguro-i9250xxlj1.img.zip" (attached), put unzipped image (in the file) into fastboot folder (attached), enable "usb debugging" option, boot into fastboot mode, connect your device to your PC, open a command prompt into fastboot folder and type:
Code:
fastboot flash radio radio-maguro-i9250xxlj1.img
Hit "enter"
Code:
fastboot reboot-bootloader
Hit "enter"
Code:
fastboot reboot
Hit "enter
Recovery method:
Put "cwm-radio-maguro-i9250xxlj1.zip" (attached) into your sdcard. Boot into recovery and flash the zip file.
Click to expand...
Click to collapse
Battery Conservation Tips:​
-Enable Auto Brightness: Brightness can lure a lot of battery if not changed intelligently with time to match the surroundings, Jellybean in this case brought the “Auto Brightness” function which uses the accelerometer within the device to detect the amount of light in the surroundings and then act upon the brightness level according to it. To enable, go to Settings > Device > Display > Brightness, and tick “Automatic Brightness“. And if you want to save more battery drain, set brightness manually at low level depending on the external amount of light.
-Remove Live Wallpapers: Using a live wallpaper is another battery sucking feature. If you turn out to be truly saving battery, make sure not to use any live wallpaper. A wallpaper with a black background uses less power than a wallpaper with a light-colored background.
-Disable Location and GPS services: Keeping GPS ON at all times, decreases your battery life, so its better to disable it while not in use. To disable, go to Settings > Personal > Location access > and switch it off.
-Disable Wi-Fi or Mobile Data when not in use: Try to avoid situations when you keep your Wifi or Mobile Data ON even when the phone is set in standby.
-Manage Sync carefully: Keeping the Sync ON all the time is another reason for decreased battery life. Enable it anytime you want, manage your emails or services and again turn it off. For those who are on work and want real-time push notifications are advised not to follow this tip.
-Turn OFF Haptic Feedback and screen sounds: To save a little more on battery, its better to switch off the screen touch sounds and vibrations. To do so, go to Settings > Device > Sound and untick Dial pad touch tones, Touch sounds. Screen lock sound and Vibrate on touch.
-Turn OFF bluetooth and NFC: Disabling bluetooth and NFC when you are not using it, is another way to save battery juice.
-Follow the method of full charge and full discharge: Don’t put your phone on charging when there is the battery remaining it for another few hours unless it’s very important. Charge it when your battery is about to get totally discharged and when you put it for charging, let it get charged totally.
-Set sleep time: Check the Sleep setting (under Display) and make sure it is set to 1 minute or less.
Keep calls short: This is obvious, but how many times have you heard people on their mobile phone say, "I think my battery’s dying," and then continue their conversation for several minutes? Sometimes, the dying battery is just an excuse to get off the phone (and a good one, at that), but if you really need to conserve the battery, limit your talk time.
-Turn OFF mobile network when not in range: Its very often that you lose the mobile network when you are travelling, so its advisable to turn OFF the mobile network by switching ON Airplane mode. Go to Settings > Wireless & Networks, tick Airplane Mode.
- After each month remove your battery from mobile phone and let it rest for an hour, it will give battery a breath and it will last longer.
-You should not have to turn off your phone to charge it. Most battery chargers deliver more than enough current to power your phone and charge it at the same time. Doing so will not lengthen the charge time, and leaving a phone on allows the user to be aware of its fuel gauge, so that you can remove it when the battery is full.
-When using a car charger, do not charge the battery when the inside temperature of your car is hot. Wait until the car has cooled before you plug in the phone.
Click to expand...
Click to collapse
Gnex secret codes:​
*#*#4636#*#* Testing menu(Phone, Battery & Wifi Info, Usage Statistics).
*#06# MEID number(Display's your IMEI).
*#*#2432546#*#* Checkin(Manually check for System Updates).
*#*#8255#*#* For Google Talk service monitoring.
*#*#786#*#* Hard Reset(Wipes/Resets Data/Profile & internal storage!) (think before you do it! no warning, no go back).
*#*#1234#*#* or *#*#7873778#*#* Open superuser application.
*#123# then press dial. Shows you if you are in your home network or not (only across networks in USA/Canada).
Click to expand...
Click to collapse
Recommendations:​
-Too loud wallpapers may sometimes disturb the look of your home screen and make the icons quite invisible, simple or a less-colored wallpapers are always suggested as to be the best choice. But your choice is what matters.
- Use only essential widgets on your home screen - each widget consumes memory and processing power which can slow your down your phone.
- Uninstall apps that you don't use - after awhile your phone can get cluttered as some Apps are designed to always run in the background. If you rarely use an App, then uninstall it to free up memory and CPU resource.
- It is best to avoid task killers such as Advanced Task Killer. Android is designed to automatically pre-load certain applications, even if you don't load them yourself. If it starts to run low on memory, it will smartly unload the oldest running apps automatically. Manually killing tasks will only mean they get loaded in memory again. Task killers can make the phone slow, laggy, or drain battery life more quickly.
- Always use latest CWM or latest TWRP recoveries.
- Disable USB debugging when it is not in use. Leaving USB debugging enabled makes your phone vulnerable (e.g. lock pattern can be reset).
- Avoid putting your Gnex in direct sunlight, it may affect touch screen & your battery performance.
- Learn how to use ADB & FASTBOOT commands instead of using toolkits, the last could not function properly.
- Flash stock firmware using fastboot is preferred than using odin.
- Check rom/kernel.zip md5 before flashing if it is convenient.
- Always update applications, if available, for better performance.
- Make a backup of your data, applications, contacts...always ready to restore from your computer.
- Read, read and read before you mess with your Gnex.
- Always be sure that you are flashing the right thing for your Gnex variant.
- If you do not know what you are doing, so don't do it .
Click to expand...
Click to collapse
Did you finish reading? Please press Thanks & Rating buttons
Big thanks to the developers of attached files.
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
Great off topic post in AK thread!!!
Thanx for your love and looking out for others
"powered by AK purity v17 Kernel + purity ROM + C.R.88 Wallpapers for beauty"
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
I love this type of thread ... When my mind goes off here I have all infos
Xda with AK Kernel inside
MOD EDIT: For God's sake, Don't quote the entire OP, post edited.
anarkia1976 said:
I love this type of thread ... When my mind goes off here I have all infos
Xda with AK Kernel inside
Click to expand...
Click to collapse
thx AK. im ready for anything to add from any user :good:
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
samersh72 said:
thx AK. im ready for anything to add from any user :good:
Click to expand...
Click to collapse
If I can help ... You can TOC TOC on my door
Xda with AK Kernel inside
hell yea bro!!!!!:good::good::good::good::good::good::good::good:
great thread bro...will be very helpful to new users :good:
k786 said:
great thread bro...will be very helpful to new users :good:
Click to expand...
Click to collapse
Thx for your post bro:good:
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
I'm impressed the majority of best contributor of ak thread create a new place with his experience for help users .....
Keep up the good work
Xda with AK Kernel inside
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
anarkia1976 said:
I'm impressed the majority of best contributor of ak thread create a new place with him experience for help users .....
Keep up the good work
Xda with AK Kernel inside
Click to expand...
Click to collapse
You are the professor AK
Sent from my Galaxy Nexus using xda premium
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
Hi guy can you add to your guide reference for resolve problem Like sk8 battery .... :thumbup:
Thanks a lot for your great guide ....
I hope every user read this make a thanks to you
Xda with AK Kernel inside
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
anarkia1976 said:
Hi guy can you add to your guide reference for resolve problem Like sk8 battery .... :thumbup:
Thanks a lot for your great guide ....
I hope every user read this make a thanks to you
Xda with AK Kernel inside
Click to expand...
Click to collapse
No problem my friend:thumbup:
Sent from my Galaxy Nexus using xda premium
anarkia1976 said:
Hi guy can you add to your guide reference for resolve problem Like sk8 battery .... :thumbup:
Thanks a lot for your great guide ....
I hope every user read this make a thanks to you
Xda with AK Kernel inside
Click to expand...
Click to collapse
i couldn't figure out properly what is sk8 problem
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with important info to know
jrgilbert79 said:
I have found out how to fix low volume phone wide and give you a reason to buy quality headphones....Guide here. http://forum.xda-developers.com/showthread.php?t=2117648
Click to expand...
Click to collapse
Thx very useful. Testing:thumbup:
Sent from my Galaxy Nexus using xda premium
The code for dialer for manual update checking is nice.
I didn't know that code even exists..
That was really helpful... Thanks!
dmourao said:
That was really helpful... Thanks!
Click to expand...
Click to collapse
you are welcome my friend:good:
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with important info to know
Great topic got a lot useful info :thumbup:
Sent from my smartphone
Amazing
:good:
samersh72 said:
Hello everyone, i see here to collect and post some known and maybe unknown tips and tricks with some important informations, hoping this will be useful for users.
Any more tips, tricks and suggestions from users are always welcomed. And please feel free to make corrections for any wrong or missed information in this post
Questions & Answers​
Q I didn't receive OTA update and i am on stock firmware?
A Go to Settings > Apps > All > Google service framework, clear data and force close it, then go to Settings > About phone > System update > Check now. repeat procedure many times.
Q Can i make a screen shot on stock firmware?
A Yes you can! user doesn’t need to root the device or employ third-party apps just to take a photo of what's happening on screen. Taking a screenshot is simple, just press the volume down and power buttons together. The device will quickly take a snapshot of the screen and you will find it in your notifications.
Q What is Barrel Roll?
A As part of Google's regular antics, it had introduced a "barrel roll" trick for desktop browsers. Type "do a barrel roll" as a search term, and Google would demonstrate the power of modern browsers by flipping everything around on your screen. Your Android device can also do a barrel roll if you speak out the same command. Again, It's great fun to show off.
Q How can i uninstall an app. without going to setting?
A Long-pressing on an app within the app drawer pops up a couple of menus along the top of the screen. App Info gives you the boring technical stuff about how much memory it's taking up, or you can fling it off the other way to uninstall it.
Q How can i go directly to the quick settings menu?
A expand notification bar by sliding two fingers.
Q What is inverted rendering?
A Inverted rendering is a posh way of saying it makes the pages black and turns the text white, so it looks like you're reading the internet from 1997. It also supposedly saves battery, plus is easier on the eyes if you're reading in the dark. It's under the browser's settings tab, within the accessibility area - and there's a contrast slider, too.
Q How can i reboot to safe mode?
A safe mode, the saviour of so many Windows PCs! Long-press the power button, then long-press the Power off option. Choose OK to reboot in safe mode, which completely disables all third-party apps on your device.
Q What does reset app. preferences means?
A Android gives you loads of different options for each installed app, and on the whole this is a very good thing. Sometimes it can be a bad thing, though: you may find your phone playing up because a crucial app has been disabled, or you've changed the notifications for something important like emails. In the apps drawer, you'll find Reset app preferences under the settings. This resets all your apps on a global level, returning actions and data settings to their original levels.
Q What is imojis?
A "Emojis" are the Japanese version of emoticons. You can enable emoji support for the default Jelly Bean keyboard by choosing Language & input in the settings app, then going to the settings for the stock Android keyboard. Here, choose Add-on dictionaries and select Emoji for English words. When you next type certain words (there's a complete list here) you'll see its symbol appear in the predictions bar.
Q I can not see Developer Options in settings?
A Google hide this option on JB 4.2.1, to enable it just go to settings---->about phone, tap 7 times on "build number" and it will be shown in settings.
Q I want to see Jelly Bean on my screen, can i?
A Yes you can, go to settings---->about phone tap quickly 4-5 times on android version, you will see a big Jelly bean, touch and hold it, you will see small flying Jelly beans.
Q How can i put my Gnex in fastboot/recovery mode?
A Turn off your phone, press and hold down Volume Up and Down keys + Power button at the same time until fastboot (bootloader) mode (image of an Android with Start) appears then release the keys. Press volume up or down and select recovery by pressing power button.
Q How can i put my Gnex in download mode (odin mode)?
A Turn off your phone, press and hold down Volume down + Power button at the same time until odin mode appears then release the keys.
Q Why google voice search is crashing when i press on mic when i am on a custom rom?
A Update google search from play store.
Q My Gnex screen is turning on by itself, what is happening?
A It is caused by an application, usually by live wallpapers, try to find it and delete it, or install an antivirus app., i recommend this, scan, delete, wipe cache and dalvik (optional).
Q sometimes i lose packet data (3G) when i turn it off then on, i turn off then turn on my Gnex to enable packet data again?
A There is no need to turn your phone off and on to re-enable packet data, just long press on power button, enable airplane mode for 3-5 seconds then turn it off.
Q I rooted my Gnex, what to do next?
A It is recommended to make a nandroid backup immediately.
Q I rooted my Gnex 4.2.1, made a nandroid backup, but i can not find my backup folder?
A Use a file manager, enable root option, your backup folder is located in data/media/clockworkmod or mnt/shell/emulated/clockwordmod.
Q The kernel does not support PGM, is there a solution?
A change the kernel, or install intellicover application.
Q Do i need to wipe cache partition when flashing a new rom?
A No, there is no need to wipe cache, because when you wipe data/factory reset, cache is wiped automatically. Some said to wipe cache and dalvik after flashing a new rom to prevent any potential conflict.
Q I rooted my Gnex 4.2.1, flash custom recovery, but when i reboot into recovery, it shows the stock recovery!?
A Every OTA update places two files on device system (that are not there on a non-update stock ROM) that re-flash the stock recovery on EVERY boot. The two files are /system/recovery-from-boot.p and /system/etc/install-recovery.sh. You need to make sure that these files are either deleted or renamed, or else custom recovery will disappear when you reboot. These files serve no purpose other than re-flashing the stock recovery on every boot. So, by using something like Root Explorer, delete or rename them, and re-flash your custom recovery.
Q My Gnex won't start, i can not get into fastboot mode, only i can get into download mode?
A Use odin to flash stock firmware here.
Q What is the easiest way to install samsung driver?
A The easiest way is to install Samsung Kies.
Q How can i flash stock image on my Gnex?
A See efrant thread.
Q What about governors, I/O schedulers, TCP congestion?
A See MBQsniper thread.
Q How to properly post a kernel bug (LAST_KMSG)?
A See ciprianruse88 thread.
Q What is the best kernel for my Gnex?
A There is no something called "best kernel". You must try many kernels and decide what suit your rom and your need. But for me AK kernel is the most active kernel in update releases that suit most roms.
Rooting:​
Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. Rooting is similar to jailbreaking devices running the Apple iOS operating system. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system. Rooting enables all the user-installed applications to run privileged commands that are typically unavailable to the devices in their stock configuration.
Legality: The Free Software Foundation Europe argues that it is legal to root or flash any device. According to the European Directive 1999/44/CE, replacing the original operating system with another does not void the statutory warranty that covers the hardware of the device for two years unless the seller can prove that the modification caused the defect.
On July 26, 2010, the United States announced a new exemption making it officially legal to root a device and run unauthorized third-party applications, as well as the ability to unlock any cell phone for use on multiple carriers.
Safety: I Have always said that the person should learn the Android OS before rooting. It is a good idea to have an idea of what rooting is doing and what it will affect. I would say spend your time really learning the OS which is not a small task. Then, if you still feel like it, go ahead and root. While rooting can help you learn many things about your device, it also can reap very bad consequences, such as:
-Bricking your phone (or in an easier way to explain, making your phone a pretty paper weight).
-Corrupting core files.
-Stopping OTA updates from going to your phone.
-Voiding phone warranty.
-Have your phone open to malicious software and applications that can do serious harm to your phone.
As you can see, it can reap very negative things. I have read/seen people who have literally had to buy brand new phones because they tried the latest and greatest rom. Rooting is essentially something that you must take at your own risk & caution. Generally, if you follow exactly the procedure of rooting made by developers, you will be more likely on the safe side.
Problems can happen:​
-Stuck into a Bootloop: Bootloops are mainly caused by system files interfering with each others which cause instability and/or crash at the boot sequence. so what to do? pull out battery then reinsert it, boot into recovery, wipe cache and dalvik, reboot. If not, format data, system, cache using recovery and restore stock firmware (supposing that you did a nandroid backup before). if you don't have a backup to restore, flash any custom rom from your sdcard after formatting system & data & cache. If you don't have a custom rom in your sdcard, push one from your pc using adb (supposed that you have adb file or sdk on your pc): boot into recovery, connect your phone to the computer open command prompt and write the following command then hit enter (supposing that your rom is placed on D):
Code:
adb push D:\name of rom.zip /data/media
once done, go to your phone and install the rom.zip from recovery, reboot.
If none of above methods works, then flash stock image for your Gnex using fastboot commands here.
-Nexus is quietly dead: If your phone did not respond to anything, it won't turn on, can not boot into fastboot or download mode, black screen, try "OMAP flash", it can save your Gnex OMAP FLASH.
Battery Conservation Tips:​
-Enable Auto Brightness: Brightness can lure a lot of battery if not changed intelligently with time to match the surroundings, Jellybean in this case brought the “Auto Brightness” function which uses the accelerometer within the device to detect the amount of light in the surroundings and then act upon the brightness level according to it. To enable, go to Settings > Device > Display > Brightness, and tick “Automatic Brightness“.
-Remove Live Wallpapers: Using a live wallpaper is another battery sucking feature. If you turn out to be truly saving battery, make sure not to use any live wallpaper.
-Disable Location and GPS services: Keeping GPS ON at all times, decreases your battery life, so its better to disable it while not in use. To disable, go to Settings > Personal > Location access > and switch it off.
-Disable Wi-Fi or Mobile Data when not in use: Try to avoid situations when you keep your Wifi or Mobile Data ON even when the phone is set in standby.
-Manage Sync carefully: Keeping the Sync ON all the time is another reason for decreased battery life. Enable it anytime you want, manage your emails or services and again turn it off. For those who are on work and want real-time push notifications are advised not to follow this tip.
-Turn OFF Haptic Feedback and screen sounds: To save a little more on battery, its better to switch off the screen touch sounds and vibrations. To do so, go to Settings > Device > Sound and untick Dial pad touch tones, Touch sounds. Screen lock sound and Vibrate on touch.
-Turn OFF bluetooth: Disabling bluetooth when you are not using it, is another way to save battery juice.
-Turn OFF mobile network when not in range: Its very often that you lose the mobile network when you are travelling, so its advisable to turn OFF the mobile network by switching ON Airplane mode. Go to Settings > Wireless & Networks, tick Airplane Mode.
Gnex secret codes:​
*#*#4636#*#* Testing menu(Phone, Battery & Wifi Info, Usage Statistics).
*#06# MEID number(Display's your IMEI).
*#*#2432546#*#* Checkin(Manually check for System Updates).
*#*#8255#*#* For Google Talk service monitoring.
*#*#786#*#* Hard Reset(Wipes/Resets Data/Profile & internal storage!) (think before you do it! no warning, no go back).
*#*#1234#*#* or *#*#7873778#*#* Open superuser application.
Recommendations:​
-Too loud wallpapers may sometimes disturb the look of your home screen and make the icons quite invisible, simple or a less-colored wallpapers are always suggested as to be the best choice. But your choice is what matters.
- Always use latest CWM or latest TWRP recoveries.
- Disable USB debugging when it is not in use. Leaving USB debugging enabled makes your phone vulnerable (e.g. lock pattern can be reset).
- Avoid putting your Gnex in direct sunlight, it may affect touch screen & your battery performance.
- Learn how to use ADB & FASTBOOT commands instead of using toolkits, the last could not function properly.
- Flash stock firmware using fastboot is preferred than using odin.
- Check rom/kernel.zip md5 before flashing if it is convenient.
- Always be sure that you are flashing the right thing for your Gnex variant.
- If you do not know what you are doing, so don't do it .
Did you finish reading? Don't forget to press Thanks & Rating buttons ​
Click to expand...
Click to collapse
Its Amazing post .. Thanx buddy .. Good luck for the future ..
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with important info to know
Subscribed! Awesomeeee OP! this is soo worth a sticky!
Sent from my Nexus Prime

Rooting the LG Exalt LTE from Verizon (LG VN220) - Request for Advice

TL.DR; Trying to root new Verizon Android flip-phone with Marshmallow 6.0.1, ARMv7. Firmware version: VN22010B. Seems to to be locked down.
Click to expand...
Click to collapse
I'm trying to root the LG Exalt LTE, or LG VN220, from Verizon. Initially, I've attempted the common rooting kits, such as KingoRoot as well as the tools described around XDA. However all failed. I suspect the cause to be the restrictive permissions of /data/local/tmp, which prevents execution of binaries. I believe any kit using this location will likely fail to achieve anything.
As such, I've been looking to achieve the same using manual techniques. The first step, as in most rooting activity is to put the device into USB debugging mode. To do this on the VN220, first compose ##7764726220. When asked for a service code, use 000000 to access a special menu. Select the Developer Options > USB Debugging and select On. There is an additional menu below named Select USB configuration, from which you can select Media Transfer Protocol or RNDIS among other options.
With that done, you can verify that you can now communicate with the device via ADB. To do so, download the Minimal ADB and Fastboot bundle. While I was successful in querying the device with ADB with
Code:
adb devices
Trying to use fastboot simply outputs "< waiting for device >" indefinitively. It is also possible to open a shell using ADB, however attempting ADB with root will fail. I don't think this is caused by having wrong drivers, as all the other tools could detect the phone (see below), but rather a permission issue.
From there, I've try to boot in different modes, which are accessible by turning off the phone, and then powering up the device while holding the Volume Down button. This will boot into a white screen with some options, including the "Safe Mode" option which I attempted. The second mode is the "Firmware Upgrade" mode which is accessible by again, powering down the phone and powering it up again, but this time holding the Volume Up for 3 seconds.
Attempting to run the following fails:
Code:
fastboot oem unlock
That being said, I later found out that LG does provides a legitimate way to unlock the bootloader via their LG developer portal. Unfortunately the VN220 is not in the list of supported devices, nor does the procedure given applies to this phone. Additionally, it requires the device ID which fails also since it requires fastboot:
Code:
fastboot oem device-id
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Trying to run apps from the internal storage such as su or even using the chmod command only results in "Operation not permitted" messages. So even temporary root seems rather difficult.
At this point, I'd like to know if anyone has any advice on additional things I could try to root the phone, or even have temporary root.
Thanks in advance
@cyberrecce
Why?
First of all thank you, I've been looking for that service code to enable developer settings / adb since I discovered the phone secretly runs Android. But I don't see why we would need root, I've been using adb to side load apps since I can't get to a menu that allows it
jfn0802 said:
First of all thank you, I've been looking for that service code to enable developer settings / adb since I discovered the phone secretly runs Android. But I don't see why we would need root, I've been using adb to side load apps since I can't get to a menu that allows it
Click to expand...
Click to collapse
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Same problem
InfectedPackets said:
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Click to expand...
Click to collapse
i get the same error. did you find a solution? i would really appreciate it
InfectedPackets said:
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Click to expand...
Click to collapse
MendilR said:
i get the same error. did you find a solution? i would really appreciate it
Click to expand...
Click to collapse
re: the certificate error for side loading apps...
Code:
adb shell settings put secure install_non_market_apps 1
turns off the unknown source block, but I'm still getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
Could the apk itself I'm trying to use have a bad certificate? Or is there another solution?
InfectedPackets said:
I'm trying to root the LG Exalt LTE, or LG VN220, from Verizon. Initially, I've attempted the common rooting kits, such as KingoRoot as well as the tools described around XDA. However all failed. I suspect the cause to be the restrictive permissions of /data/local/tmp, which prevents execution of binaries. I believe any kit using this location will likely fail to achieve anything.
As such, I've been looking to achieve the same using manual techniques. The first step, as in most rooting activity is to put the device into USB debugging mode. To do this on the VN220, first compose ##7764726220. When asked for a service code, use 000000 to access a special menu. Select the Developer Options > USB Debugging and select On. There is an additional menu below named Select USB configuration, from which you can select Media Transfer Protocol or RNDIS among other options.
With that done, you can verify that you can now communicate with the device via ADB. To do so, download the Minimal ADB and Fastboot bundle. While I was successful in querying the device with ADB with
Code:
adb devices
Trying to use fastboot simply outputs "< waiting for device >" indefinitively. It is also possible to open a shell using ADB, however attempting ADB with root will fail. I don't think this is caused by having wrong drivers, as all the other tools could detect the phone (see below), but rather a permission issue.
From there, I've try to boot in different modes, which are accessible by turning off the phone, and then powering up the device while holding the Volume Down button. This will boot into a white screen with some options, including the "Safe Mode" option which I attempted. The second mode is the "Firmware Upgrade" mode which is accessible by again, powering down the phone and powering it up again, but this time holding the Volume Up for 3 seconds.
Attempting to run the following fails:
Code:
fastboot oem unlock
That being said, I later found out that LG does provides a legitimate way to unlock the bootloader via their LG developer portal. Unfortunately the VN220 is not in the list of supported devices, nor does the procedure given applies to this phone. Additionally, it requires the device ID which fails also since it requires fastboot:
Code:
fastboot oem device-id
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Trying to run apps from the internal storage such as su or even using the chmod command only results in "Operation not permitted" messages. So even temporary root seems rather difficult.
At this point, I'd like to know if anyone has any advice on additional things I could try to root the phone, or even have temporary root.
Thanks in advance
@cyberrecce
Click to expand...
Click to collapse
Just curious - any success or updates. I can't seem to get past " INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from here.
effulgent.unicorn said:
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from here.
Click to expand...
Click to collapse
Any ideas on how to get past - "INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"?
PAULC91316 said:
Any ideas on how to get past - "INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"?
Click to expand...
Click to collapse
I'm still at the same place I was the other day when I posted this.
effulgent.unicorn said:
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from
here.
Click to expand...
Click to collapse
InfectedPackets said:
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Click to expand...
Click to collapse
Can you please share with us the KDZ file?
Thanks!
anyone?
You will need to:
- unlock it’s Bootloader. If the “fastboot oem unlock” command will not work (and I’m quite sure it will not, since we’re talking about a USA LG device), you can stop here and throw the phone out the window.
- if by some any miracle you will be able to unlock the bootloader, you have two ways of rooting it:
1. Using TWRP and a superuser zip file (magisk or the now Chinese owned supersu). The main problem with this is that you will need to compile TWRP yourself, since I doubt anyone will bother for such an obscure device.
2. Using a prerooted boot image. You will need the stock boot image, install the latest magisk manager, let it root it and then flash it via fastboot. This is particularly difficult because you will need to decrypt the kdz file (if any available) in order to get the boot.img
Even if by a greater miracle you will be able to get 1 or 2 working, there still is a huge chance that the fastboot flash command will be disabled.
Forget about solutions like king/kingoroot. Best case scenario they will fail. Worst case scenario they will softbrick the phone by gaining temporary root and then modifying /system. That will in turn trigger dm-verity which will cause the soft brick.
Forget about the scams like oneclickroot. Their so called techs will try the aforementioned and fail and you will waste your $40.
Sorry To deliver the bad news, but there’s no way out of it.
Thanks for taking your time, to help me.
I will check if I can unlock the bootloader.
Thanks alot
r3w1NNNd said:
You will need to:
- unlock it’s Bootloader. If the “fastboot oem unlock” command will not work (and I’m quite sure it will not, since we’re talking about a USA LG device), you can stop here and throw the phone out the window.
- if by some any miracle you will be able to unlock the bootloader, you have two ways of rooting it:
1. Using TWRP and a superuser zip file (magisk or the now Chinese owned supersu). The main problem with this is that you will need to compile TWRP yourself, since I doubt anyone will bother for such an obscure device.
2. Using a prerooted boot image. You will need the stock boot image, install the latest magisk manager, let it root it and then flash it via fastboot. This is particularly difficult because you will need to decrypt the kdz file (if any available) in order to get the boot.img
Even if by a greater miracle you will be able to get 1 or 2 working, there still is a huge chance that the fastboot flash command will be disabled.
Forget about solutions like king/kingoroot. Best case scenario they will fail. Worst case scenario they will softbrick the phone by gaining temporary root and then modifying /system. That will in turn trigger dm-verity which will cause the soft brick.
Forget about the scams like oneclickroot. Their so called techs will try the aforementioned and fail and you will waste your $40.
Sorry To deliver the bad news, but there’s no way out of it.
Click to expand...
Click to collapse
Any sage advice on the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] issue when sideloading apps?
 @jfn0802 said they had success with sideloading, but haven't been online in ages, and none of the rest of us seem to have had the same success. Minimum, that's what I would like to accomplish.
[side note, has anyone switched from Verizon with this phone? I'm looking to, but I'm wondering a couple of things like, does verizon have the mobile hotspot function restricted from use on other carriers? & etc & just wondering how it's doing off-verizon for anyone.]
effulgent.unicorn said:
Any sage advice on the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] issue when sideloading apps?
@jfn0802 said they had success with sideloading, but haven't been online in ages, and none of the rest of us seem to have had the same success. Minimum, that's what I would like to accomplish.
[side note, has anyone switched from Verizon with this phone? I'm looking to, but I'm wondering a couple of things like, does verizon have the mobile hotspot function restricted from use on other carriers? & etc & just wondering how it's doing off-verizon for anyone.]
Click to expand...
Click to collapse
my freinds are using it in Canada with videotron and everything works, without unlocking
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
GenTech Solution said:
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
Click to expand...
Click to collapse
Yes right, but how can I go around it?
Ps. I was able to uninstall apps (I removed my Verizon)
With adb shell, as the user 0, but with adb normal uninstall didn't work, but when I try to install with adb shell, it gave the same certificate erorr
GenTech Solution said:
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
Click to expand...
Click to collapse
Isn't that what turning on the "install from unknown sources" option should do? I still get the Install Parse Failed after switching it on with ADB.
@98jbsz I've tried to uninstall without success. What way did you do it? And does it just leave a blank space in the menu screen?
[Less on topic, sorry again, but has anyone seen the LG Wine LTE? http://www.lg.com/us/cell-phones/lg-UN220-lg-wine
It's strikingly similar to our friend the Exalt LTE here, but it seems less carrier branded/available at US Cellular, so I'm wondering if that would make a difference?
Major differences Wine LTE has more 4G bands (2/4/5/12/25) versus Exalt (4/5/13), which kind of has me kicking myself, because travel and 4G was one of the reasons I bought the Exalt. Both have quadband GSM and WCDMA, but interestingly the Wine also has CDMA.
Beyond that, there are some more smaller differences I scavenged from their LG pages, Exalt has more bluetooth profiles, supports more music formats, has more GPS capabilities, wifi calling, and 1 more ringtone. Wine has more supported video formats, and an FM radio.
I'm curious about what/if the Wine would have for sms messaging (I doubt it'd have Verizon's message+) and instead of my Verizon app...]
98jbsz said:
Yes right, but how can I go around it?
Ps. I was able to uninstall apps (I removed my Verizon)
With adb shell, as the user 0, but with adb normal uninstall didn't work, but when I try to install with adb shell, it gave the same certificate erorr
Click to expand...
Click to collapse
Alright, I also managed to uninstall my verizon and verizon's cloud app using
Code:
adb shell and the pm uninstall -k --user 0
But the Verizon apps folder on the menu screen remains, although it's empty. Any ideas on how to remove it?
Then I tried to install an apk using
Code:
pm install
and it came back with [INSTALL_FAILED_INVALID_URI] which...is a different than [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES], but not better.
right, but when you first copy the APK to the phone, and then you install it, you will see the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] error. still not a solution

ATT Note 5 Native Tether/hotspot (NO Root) 6.0.1 MM

I am using an at&t note 5 (sm-920A) i downgraded from Nougat EQC6, 7.0.1 to 6.0.1. MM CPK1 with Binary 4 bootloader. This phone has never been rooted.
I now have access to hotspot in my notifications drop down menu, and USB tethering along with Bluetooth tethering work by just going to the option and switching them on.
My Goal was initially to downgrade to 5.1.1 to get root so i could make use of the Native Tether/Hotspot and other root apps on my ATT Note 5.
I am using this phone on the Straight Talk network.
This is my first how-to and first post. I apologize if i post in the wrong section or am unable to give more help to those in need.
I've searched/googled and although i have found workarounds i have not found any how-to's to get to this end result.
Ive been using my note 5 this way for a few days now with no problems. disabled att bloatware, knox, and system updates with package disabler pro.
With not having any issues, I flashed back to the 6.01 firmware to check my steps and write this how-to. Will update if anything changes.
WARNING!!
Some things i did may be unnessary but were in my process at the time of writing/doing this so are included
I haven't tested everything on this phone.
I don't know if there are any bugs.
I don't know what will happen when updated.
I do not garuntee this will work for you.
I take NO responsibility if your decision to try/do this fails.
The Search button and google were my biggest helpers.
Here is my process as laid out and straight forward as i could think to write it.
Things you will need:
1. N920AUCS4CPK1 posted by droidvoider (https://forum.xda-developers.com/at...lution-samsung-note-5-sm-n920a-error-t3545600 using odin) by droidvoider
2. Odin3 v3.12.10 posted by anycallmongolia (https://forum.xda-developers.com/showthread.php?t=2711451) by anycallmongolia,
3. COMBINATION_FA51_N920AUCU4APL1_CL6053901_QB11816686_REV00_user_mid_noship posted by BE8ST (https://androidfilehost.com/?w=files&flid=124797)
4. N920AUCE2APB2.tar posted by TechNyne66 (https://forum.xda-developers.com/att-galaxy-note5/general/att-note-5-n920a-teather-root-t3356666)
Big Thank you to these guys for posting this stuff, and everything else they post.
I am assuming you know how to put your phone into download mode and use odin in the following instructions. I left my phone connected to my pc with sim card in the entire process.
1. Unzip N920AUCS4CPK1, then Flash using odin. Use all 4 files in their respected spots. nothing else has to be changed hit start.
After reboot I setup up the phone enough to get to settings and enable developer options. making sure to turn on adb debugging and oem unlock. then rebooted to download mode
2. In Odin, Flash N920AUCE2APB2.tar in the BL slot and COMBINATION_FA51_N920AUCU4APL1_CL6053901_QB11816686_REV00_user_mid_noship.tar in the AP slot. (I flashed these two at the same time)
Phone will reboot to binary splash screen then start regularly. For me the phone Played boot music and (vibrated then vibrate twice) repeatedly. Bootloop
If this happens to you as well,
2a. Shut phone off by holding volume down key and power button.
(If you are brought to a screen that says power key long press in yellow with other information below[well call this the info screen, not sure on its proper name],
then power off by holding volume down key and power key again, releasing both when screen goes blank.
2b. When the phone is completly off reboot to recovery by holding volume up key and power key.
Do a factory reset and wipe cache. Then reboot. (If it freezes at cache complete, power off with volume down key and power key).
Holding power button for 10 seconds or more will boot you to info screen again.
3. Your phone should load to a home screen with what looks like a debugging menu as the background.
4. Turn phone off and boot to download mode.
5. In Odin, load BL, AP, and CP from N920AUCS4CPK1. Leave CSC blank. No other options should be changed in Odin.
6. You will reboot to recovery. Use reboot option. dm verity check will start then phone should reboot to normal setup initialization.
7. If for some reason your phone shows the wrong storage size, go to back-up and resert in settings and o a factory data reset mine was showing up as 16gb where as it is 64gb
That was everything i did.
If with straight talk send a text to 611611 with the mesage being apn.
afrter a few minutes they will send a configuration message for browser and mms.
Install both. They should say installed when complete.
For others you will have to input your apn settings manually.
My phone showed H+ for the first few minutes, has been showing 4g ever since.
Just a few thoughts before i post, but are in no way tested or confirmed...
I'm thinking coming from cpk1 full firmware you could just flash the combination file in the AP slot.
Then after reboot to Download mode flash the cpk1 firmware without the CSC file and hve the same result,
but I havnt had a chance to test that yet as i need my phone running, and will soon have to go to work.
The main reason the N920AUCE2APB2.tar file was used was because i was playing around flashing different files it may or may not be needed. further testing is needed. but it was there during this process so i included it. Again I apologize if this could be simplified or if i left anything out. any comments are appreciated positive or negative. Thanks
So i did a little testing. Flash cpk1 all files. Then flash the custom binary and rebooting to download mode. Then flash the cpk1 files again minus the csc file. Leave that slot(csc) empty in odin and it will give you native hotspot and tethering. You get hotspot from notification drop down menu and No more contact att. It will take away the calls over wifi option though.
I will edit this walkthrough (if you canveven call it that) soon to reflect the changes. Thank you for reading.
Badbrane said:
So i did a little testing. Flash cpk1 all files. Then flash the custom binary and rebooting to download mode. Then flash the cpk1 files again minus the csc file. Leave that slot(csc) empty in odin and it will give you native hotspot and tethering. You get hotspot from notification drop down menu and No more contact att. It will take away the calls over wifi option though.
I will edit this walkthrough (if you canveven call it that) soon to reflect the changes. Thank you for reading.
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-galaxy-note5/general/update-t3738023 N920A_N920AUCS4EQL1_ATT_USA_7.0.zip post #2
by huynhlam thank you
[ATT Note 5. on straight talk]
This process also works using this firmware. i updated from cpk1 using my process in post #2. i left out the (csc) and pit file in the N920A_N920AUCS4EQL1_ATT_USA_7.0.zip huynhlam posted in the link above. I am now on 7.0 with native hotspot and mobile hotspot icon in the notification drop down menu working . i can upload pictures but atm im not familiar with the best free file hosting sites so any suggestions would be greatly appreciated. i will keep trying different firmwares and update with results.
Badbrane said:
I am using an at&t note 5 (sm-920A) i downgraded from Nougat EQC6, 7.0.1 to 6.0.1. MM CPK1 with Binary 4 bootloader. This phone has never been rooted.
I now have access to hotspot in my notifications drop down menu, and USB tethering along with Bluetooth tethering work by just going to the option and switching them on.
My Goal was initially to downgrade to 5.1.1 to get root so i could make use of the Native Tether/Hotspot and other root apps on my ATT Note 5.
I am using this phone on the Straight Talk network.
This is my first how-to and first post. I apologize if i post in the wrong section or am unable to give more help to those in need.
I've searched/googled and although i have found workarounds i have not found any how-to's to get to this end result.
Ive been using my note 5 this way for a few days now with no problems. disabled att bloatware, knox, and system updates with package disabler pro.
With not having any issues, I flashed back to the 6.01 firmware to check my steps and write this how-to. Will update if anything changes.
WARNING!!
Some things i did may be unnessary but were in my process at the time of writing/doing this so are included
I haven't tested everything on this phone.
I don't know if there are any bugs.
I don't know what will happen when updated.
I do not garuntee this will work for you.
I take NO responsibility if your decision to try/do this fails.
The Search button and google were my biggest helpers.
Here is my process as laid out and straight forward as i could think to write it.
Things you will need:
1. N920AUCS4CPK1 posted by droidvoider (https://forum.xda-developers.com/at...lution-samsung-note-5-sm-n920a-error-t3545600 using odin) by droidvoider
2. Odin3 v3.12.10 posted by anycallmongolia (https://forum.xda-developers.com/showthread.php?t=2711451) by anycallmongolia,
3. COMBINATION_FA51_N920AUCU4APL1_CL6053901_QB11816686_REV00_user_mid_noship posted by BE8ST (https://androidfilehost.com/?w=files&flid=124797)
4. N920AUCE2APB2.tar posted by TechNyne66 (https://forum.xda-developers.com/att-galaxy-note5/general/att-note-5-n920a-teather-root-t3356666)
Big Thank you to these guys for posting this stuff, and everything else they post.
I am assuming you know how to put your phone into download mode and use odin in the following instructions. I left my phone connected to my pc with sim card in the entire process.
1. Unzip N920AUCS4CPK1, then Flash using odin. Use all 4 files in their respected spots. nothing else has to be changed hit start.
After reboot I setup up the phone enough to get to settings and enable developer options. making sure to turn on adb debugging and oem unlock. then rebooted to download mode
2. In Odin, Flash N920AUCE2APB2.tar in the BL slot and COMBINATION_FA51_N920AUCU4APL1_CL6053901_QB11816686_REV00_user_mid_noship.tar in the AP slot. (I flashed these two at the same time)
Phone will reboot to binary splash screen then start regularly. For me the phone Played boot music and (vibrated then vibrate twice) repeatedly. Bootloop
If this happens to you as well,
2a. Shut phone off by holding volume down key and power button.
(If you are brought to a screen that says power key long press in yellow with other information below[well call this the info screen, not sure on its proper name],
then power off by holding volume down key and power key again, releasing both when screen goes blank.
2b. When the phone is completly off reboot to recovery by holding volume up key and power key.
Do a factory reset and wipe cache. Then reboot. (If it freezes at cache complete, power off with volume down key and power key).
Holding power button for 10 seconds or more will boot you to info screen again.
3. Your phone should load to a home screen with what looks like a debugging menu as the background.
4. Turn phone off and boot to download mode.
5. In Odin, load BL, AP, and CP from N920AUCS4CPK1. Leave CSC blank. No other options should be changed in Odin.
6. You will reboot to recovery. Use reboot option. dm verity check will start then phone should reboot to normal setup initialization.
7. If for some reason your phone shows the wrong storage size, go to back-up and resert in settings and o a factory data reset mine was showing up as 16gb where as it is 64gb
That was everything i did.
If with straight talk send a text to 611611 with the mesage being apn.
afrter a few minutes they will send a configuration message for browser and mms.
Install both. They should say installed when complete.
For others you will have to input your apn settings manually.
My phone showed H+ for the first few minutes, has been showing 4g ever since.
Just a few thoughts before i post, but are in no way tested or confirmed...
I'm thinking coming from cpk1 full firmware you could just flash the combination file in the AP slot.
Then after reboot to Download mode flash the cpk1 firmware without the CSC file and hve the same result,
but I havnt had a chance to test that yet as i need my phone running, and will soon have to go to work.
The main reason the N920AUCE2APB2.tar file was used was because i was playing around flashing different files it may or may not be needed. further testing is needed. but it was there during this process so i included it. Again I apologize if this could be simplified or if i left anything out. any comments are appreciated positive or negative. Thanks
Click to expand...
Click to collapse
If anyone could link me to the original poster of the combination file, it would be much apreciated. the user name i got was off android filehost site annd i would like to give them thanks if they are on the xda site. i searched their user name on xda and could not find. thanks again
Badbrane said:
https://forum.xda-developers.com/att-galaxy-note5/general/update-t3738023 N920A_N920AUCS4EQL1_ATT_USA_7.0.zip post #2
by huynhlam thank you
[ATT Note 5. on straight talk]
This process also works using this firmware. i updated from cpk1 using my process in post #2. i left out the (csc) and pit file in the N920A_N920AUCS4EQL1_ATT_USA_7.0.zip huynhlam posted in the link above. I am now on 7.0 with native hotspot and mobile hotspot icon in the notification drop down menu working . i can upload pictures but atm im not familiar with the best free file hosting sites so any suggestions would be greatly appreciated. i will keep trying different firmwares and update with results.
Click to expand...
Click to collapse
Hello Badbrane, I followed your instructions and I succeeded
Thanks a lot!
EDIT: After some testing I found out a bluetooth issue.
The first time I turn the device on, the bluetooth works fine. Then, after a reboot, I can't turn bluetooth on any more.
If I go through a Factory reset I will get the bluetooth working again, till next reboot
I need some help. I'm stuck in 2b (yellow information screen). when i hold [volume down] + [power button] it restarts instead of turning off. What should I do?
The combination file is no longer on Android file host. Any chance you have another link?
Im blind
https://1drv.ms/f/s!AhYiTPM1C3QkbQJswYeC0PtRMEY
not sure how long this link will be live but here's N920AUCS4CPK1.rar and COMBINATION_FA51_N920AUCU4APL1_CL6053901_QB11816686_REV00_user_mid_noship.rar. sorry it took so long to reply.
crazydoria said:
I need some help. I'm stuck in 2b (yellow information screen). when i hold [volume down] + [power button] it restarts instead of turning off. What should I do?
Click to expand...
Click to collapse
hold vol down and power till screen goes black immediatly change to 3 finger salute for dl or recovery. have to do it fast, that or wait for the battery to die and resume from there.
gmlai said:
Hello Badbrane, I followed your instructions and I succeeded
Thanks a lot!
EDIT: After some testing I found out a bluetooth issue.
The first time I turn the device on, the bluetooth works fine. Then, after a reboot, I can't turn bluetooth on any more.
If I go through a Factory reset I will get the bluetooth working again, till next reboot
Click to expand...
Click to collapse
I havnt really messed with the bluetooth much on my note 5 since i did this process. there are definetly a few bugs but my only concern was being able to use hotspot and tether. found out later that the system will try to auto update but it crashes every time so i no worring about hitting binary 5, as far as i know that is

Just tweak it [Tab S4] - debloat, root, plugins, battery...

Tab S4 stock cleanup actions
phablet guide fest continues V30->Note9->6T->Mi9->S10->7T->Tab S6->Tab S4, time to provide some thoughts, easy to click links and guides. Goal is to have a clean device after each update, and have a helper script running at boot or on demand. This is a tablet, we want to achieve flat battery graphs when it is unused (picture attached), hopefully charge once a week with slight usage.
Debloat
What the script does:
* choose 8 categories of app removal, in the beginning of the file
for each say 0=skip 1=remove 2=revert back
* use more switch to disable some questionable/helpful stuff
* disable up to 80 apps with possibility to revert back
* remove usage access for google (do manually)
* remove device admin backdoor "Find My Mobile", you won't recover stolen device this way lol, it doesn't work with Secure Startup! it's useful for Govt.
* remove proca (which was slowing down tablet after rooting), if it doesn't work from your shell, edit the file as below
Tested ok on March stock Pie firmware. Samsung has too much bloatware installed, and requires shocking permissions to run some basic services. We will further need to reclaim privacy. As for debloat list, i've cooked the list based on knowledge of each process, its current presence in the Pie firmware, and what would fit the tablet usage. In this case, i'm leaving Samsung account, Galaxy shop and few pen apps and we assume XPrivacy is sending these snitch services bogus personal details.
Download: (file attached)
Installation:
- run in su terminal once or add to any startup script (3C\Device mgr\Scheduler can assign scripts from /storage/emulated/0/Android/data/ccc71.at/scripts), or to magisk
Rooting
We want encryption. There are no ROMs, and TWRP can be used for many other tasks without access to your files.
OEM unlock in dev settings
when turned off and rather plugged it to your PC with drivers installed, hold Power & Vol+ & Vol- til you see download screen, confirm with Vol+
in ODIN, slap TWRP into AP while "Auto reboot" is unchecked
hold Power & Vol- to exit download mode, then Power & Vol+ to enter recovery
in TWRP, slap kernel and Magisk into tablet from SD card or USB (can be usb flash, can be other mobile, can be adb)
in TWRP, say boot to system and wait 5min
check Magisk app status, enable USB debugging in dev settings
kernel: WETA recovery: TWRP 3.3.1 for PIE SM-T83x
watch kernel log for 20sec
Code:
dmesg -Tw|grep proca
if proca messages appear open /vendor/etc/init/pa_daemon_qsee.rc and comment the lines
You should enable "Secure startup" in "Biometrics and security" settings. Recovery should fail reading encrypted drive sda27 because of its crypto flags and logical mapping.
Which plugins to use
Similarly to Mi9, collecting what i think is useful to keep on stock rooted firmware.
Magisk plugins:
* Riru - Core, Riru - Ed Exposed -- brings XPosed to Pie. Need also installer. Make a choice SandHook/Yahfa bipolar release, i never found out which one is better.
* libsecure_storage companion -- helps us keep the bluetooth pairings
* (optional) YouTube Vanced black themed -- brings usable YouTube experience. Unfortunately it's now a horror to install (v15), but v14 from Magisk still works.
* (optional) Move certificates -- perhaps
* (impossible) QuickSwitch -- there's no pill but Samsung custom recents... oh how glad i am for it now! Android10 cancelled this fantastic Pie pill already and you can scroll apps in OneUI!
XPosed plugins:
* Xposed Edge Pro -- a must have and best plugin
* XPrivacy -- Screw the big brother. Must have of the century. Disabling analytics, tracking, telephony, network, identification for all visible apps and all Google and Samsung apps with some exceptions.
* Firefds kit -- so this is our main customization app irrelevant here: ..and enables the very important call recording, which is beutifully integrated into call history. Bye bye external apps. Also for Samsungs it forces Restart "recovery"
* (optional) Xposed Dex -- some tweaks
* (optional) afWall -- Problems with this firewall and some VPN clients for years. Using AdGuard now and happy. It can even control DNS, no need one of those paid lausy apps. This plugin should by disabled in Xposed.
* (optional) Exi for Swiftkey -- you can make Swiftkey great again, GBoard is still the best, Samsung keyboard is very good, but too tall and leaves gap in fullscreen mode
Root apps:
* TitaniumBackup -- a must since Android was born
* Adaway -- a must but with AdGuard not so.. but i use both
* AdGuard -- can filter more and can amend requests.. that's a game changer. You can have a efficient proxy when rooted.
* 3C toolbox -- too helpful not to pay for the biggest package
* (optional) Root Essentials -- a multitool, have a look
* (optional) MiXplorer -- best file manager, replaces spyware ES File explorer you had before. Edits root files comfortably even when other editors don't
* (optional) FolderSync -- best sync tool
Battery
Battery saving:
- tablet should not be neccessarily always connected, receive notifications, so why not keep it dead when the screen is off
- the key is to disable background network activity:
disable it overall by Medium Power Saving mode
disable background network for individual apps (there's "Allow background data usage" and also nice "Allow background activity" checkbox)
force it with 3C (Device Mgr\Profiler) or Adguard (App Management)
- can't see wifi switch.. to turn wifi off when screen off. no wifi scanning drainer or other "intelligent" bs functions there either. just "Hotspot 2" - turn off.
- nearby scanning should be off, what a useless function of finding unknown devices - once you pair the known, what's the sense? or you keep connection 10 new bt devices each week? just a drain and endless beacon
- location can be off, and again it can be scripted by turning on only when screen is on by 3C
- not installing {LSpeed, Naptime, Servicely, FDE, LKT, Universal GMS Doze, Sysconfig patcher} here
- no signifficant doze functions here {AOD, fp icon, dt2wake, raise2wake} to speak off
- we want battery to remain flat when screen off, last tablet i had could do -1% per week! let's do it here
Other
- i like tender boot screen indicating knox off status, no need to flash boot logos
- no boot keys needed like on Tab s6
- not using multidisabler as i'm on stock and i do want encryption on every device ever
- how to launch camera quickly?? still dind't find out
- don't be afraid to use another device (mobile) as USB drive.. this way you can restore your apps directly via TitaniumBackup without copying it first! also Smart Switch can be used from non-Samsung phones, but it is as weak as Google backup ever was - no data restore
What do you do to run this exactly?
copy the file to storage. open su terminal. Get any root terminal app (ConnectBot, 3C Toolbox, or adb shell) and run as root. I run this script as autostart on each of my devices.
wifi_standby_test: first battery standby test: 37 hours to 91%, i've 'charging protection' so approx 93% that give us 0.19%/hr drain with wifi and bluetooth on. 10x less then a mobile (S10). Good start, nice 3 weeks of standby potential, but let's try medium power saving mode to squeeze it to over month of standby.
Will i loose my data while rooting? Im on Build number PPR1.180610.011.T835DDS4BSL2
doggydog2 said:
Tab S4 stock cleanup actions
phablet guide fest continues V30->Note9->6T->Mi9->S10->7T->Tab S6->Tab S4, time to provide some thoughts, easy to click links and guides. Goal is to have a clean device after each update, and have a helper script running at boot or on demand. This is a tablet, we want to achieve flat battery graphs when it is unused (picture attached), hopefully charge once a week with slight usage.
Debloat
What the script does:
* choose 8 categories of app removal, in the beginning of the file
for each say 0=skip 1=remove 2=revert back
* use more switch to disable some questionable/helpful stuff
* disable up to 80 apps with possibility to revert back
* remove usage access for google (do manually)
* remove device admin backdoor "Find My Mobile", you won't recover stolen device this way lol, it doesn't work with Secure Startup! it's useful for Govt.
* remove proca (which was slowing down tablet after rooting), if it doesn't work from your shell, edit the file as below
Tested ok on March stock Pie firmware. Samsung has too much bloatware installed, and requires shocking permissions to run some basic services. We will further need to reclaim privacy. As for debloat list, i've cooked the list based on knowledge of each process, its current presence in the Pie firmware, and what would fit the tablet usage. In this case, i'm leaving Samsung account, Galaxy shop and few pen apps and we assume XPrivacy is sending these snitch services bogus personal details.
Download: (file attached)
Installation:
- run in su terminal once or add to any startup script (3C\Device mgr\Scheduler can assign scripts from /storage/emulated/0/Android/data/ccc71.at/scripts), or to magisk
Rooting
We want encryption. There are no ROMs, and TWRP can be used for many other tasks without access to your files.
OEM unlock in dev settings
when turned off and rather plugged it to your PC with drivers installed, hold Power & Vol+ & Vol- til you see download screen, confirm with Vol+
in ODIN, slap TWRP into AP while "Auto reboot" is unchecked
hold Power & Vol- to exit download mode, then Power & Vol+ to enter recovery
in TWRP, slap kernel and Magisk into tablet from SD card or USB (can be usb flash, can be other mobile, can be adb)
in TWRP, say boot to system and wait 5min
check Magisk app status, enable USB debugging in dev settings
kernel: WETA recovery: TWRP 3.3.1 for PIE SM-T83x
watch kernel log for 20sec
Code:
dmesg -Tw|grep proca
if proca messages appear open /vendor/etc/init/pa_daemon_qsee.rc and comment the lines
You should enable "Secure startup" in "Biometrics and security" settings. Recovery should fail reading encrypted drive sda27 because of its crypto flags and logical mapping.
Which plugins to use
Similarly to Mi9, collecting what i think is useful to keep on stock rooted firmware.
Magisk plugins:
* Riru - Core, Riru - Ed Exposed -- brings XPosed to Pie. Need also installer. Make a choice SandHook/Yahfa bipolar release, i never found out which one is better.
* libsecure_storage companion -- helps us keep the bluetooth pairings
* (optional) YouTube Vanced black themed -- brings usable YouTube experience. Unfortunately it's now a horror to install (v15), but v14 from Magisk still works.
* (optional) Move certificates -- perhaps
* (impossible) QuickSwitch -- there's no pill but Samsung custom recents... oh how glad i am for it now! Android10 cancelled this fantastic Pie pill already and you can scroll apps in OneUI!
XPosed plugins:
* Xposed Edge Pro -- a must have and best plugin
* XPrivacy -- Screw the big brother. Must have of the century. Disabling analytics, tracking, telephony, network, identification for all visible apps and all Google and Samsung apps with some exceptions.
* Firefds kit -- so this is our main customization app irrelevant here: ..and enables the very important call recording, which is beutifully integrated into call history. Bye bye external apps. Also for Samsungs it forces Restart "recovery"
* (optional) Xposed Dex -- some tweaks
* (optional) afWall -- Problems with this firewall and some VPN clients for years. Using AdGuard now and happy. It can even control DNS, no need one of those paid lausy apps. This plugin should by disabled in Xposed.
* (optional) Exi for Swiftkey -- you can make Swiftkey great again, GBoard is still the best, Samsung keyboard is very good, but too tall and leaves gap in fullscreen mode
Root apps:
* TitaniumBackup -- a must since Android was born
* Adaway -- a must but with AdGuard not so.. but i use both
* AdGuard -- can filter more and can amend requests.. that's a game changer. You can have a efficient proxy when rooted.
* 3C toolbox -- too helpful not to pay for the biggest package
* (optional) Root Essentials -- a multitool, have a look
* (optional) MiXplorer -- best file manager, replaces spyware ES File explorer you had before. Edits root files comfortably even when other editors don't
* (optional) FolderSync -- best sync tool
Battery
Battery saving:
- tablet should not be neccessarily always connected, receive notifications, so why not keep it dead when the screen is off
- the key is to disable background network activity:
disable it overall by Medium Power Saving mode
disable background network for individual apps (there's "Allow background data usage" and also nice "Allow background activity" checkbox)
force it with 3C (Device Mgr\Profiler) or Adguard (App Management)
- can't see wifi switch.. to turn wifi off when screen off. no wifi scanning drainer or other "intelligent" bs functions there either. just "Hotspot 2" - turn off.
- nearby scanning should be off, what a useless function of finding unknown devices - once you pair the known, what's the sense? or you keep connection 10 new bt devices each week? just a drain and endless beacon
- location can be off, and again it can be scripted by turning on only when screen is on by 3C
- not installing {LSpeed, Naptime, Servicely, FDE, LKT, Universal GMS Doze, Sysconfig patcher} here
- no signifficant doze functions here {AOD, fp icon, dt2wake, raise2wake} to speak off
- we want battery to remain flat when screen off, last tablet i had could do -1% per week! let's do it here
Other
- i like tender boot screen indicating knox off status, no need to flash boot logos
- no boot keys needed like on Tab s6
- not using multidisabler as i'm on stock and i do want encryption on every device ever
- how to launch camera quickly?? still dind't find out
- don't be afraid to use another device (mobile) as USB drive.. this way you can restore your apps directly via TitaniumBackup without copying it first! also Smart Switch can be used from non-Samsung phones, but it is as weak as Google backup ever was - no data restore
Click to expand...
Click to collapse
Bro. Is it possible to do this without losing data?
mayank_nigam said:
Will i loose my data while rooting? Im on Build number PPR1.180610.011.T835DDS4BSL2
Click to expand...
Click to collapse
backup, try and let us know the reason why usual root methods wipe data is to remove encryption, we don't need that.
doggydog2 said:
backup, try and let us know the reason why usual root methods wipe data is to remove encryption, we don't need that.
Click to expand...
Click to collapse
So if we do it without turning oem unlock, will it work?
---------- Post added at 04:41 PM ---------- Previous post was at 04:26 PM ----------
doggydog2 said:
backup, try and let us know the reason why usual root methods wipe data is to remove encryption, we don't need that.
Click to expand...
Click to collapse
Any suggestions on backup method?
mayank_nigam said:
So if we do it without turning oem unlock, will it work?
Click to expand...
Click to collapse
ah i see... you need this checkbox unlocked to flash. this device will wipe itself if you just toggle the checkbox. so in the end, data will be wiped in transition from unrooted state.
and regarding backup, just conventional methods like google backup or deeper cable backup by Helium which can partially substitute TitaniumBackup on unrooted device.
How did you get Weta running on the March firmware when it isn't supported?
NM, I see you just used the kernel part.
Running this script did very little for me - no options were given, just a few packages disabled before it errored out
Thank you for the script! It made a great difference on my tab s4, I was able to enable back Chrome and Google.
My device was lagging before... Thanks again for the write up...
Any suggestions on installing apps to sd card? The option under dev options, to force install apps to sd card is not really good.
I just purchased a refurb Tab S4, it should be arriving over the weekend. The seller notes that the S4 is on Oreo.
I noticed references to Pie here. Should boot and I let the tablet update to the latest release from Samsung, and then root / debloat as described in this thread after the Pie update?
¿GotJazz? said:
I just purchased a refurb Tab S4, it should be arriving over the weekend. The seller notes that the S4 is on Oreo.
I noticed references to Pie here. Should boot and I let the tablet update to the latest release from Samsung, and then root / debloat as described in this thread after the Pie update?
Click to expand...
Click to collapse
My Tab S4 arrived today. Should I allow any updates from Samsung be installed before I run through the rooting process described here, or should I do the rooting before getting the Samsung updates?
¿GotJazz? said:
My Tab S4 arrived today. Should I allow any updates from Samsung be installed before I run through the rooting process described here, or should I do the rooting before getting the Samsung updates?
Click to expand...
Click to collapse
yes..why rooting an old version.. no OTAs later so you'd have to update manually again.
doggydog2 said:
yes..why rooting an old version.. no OTAs later so you'd have to update manually again.
Click to expand...
Click to collapse
Thanks!
But, as it turns out ... I won't be able to root or debloat anyways. I purchased a refurb Tab S4 that appears to be in excellent like-new shape, but it was also mislabeled on Amazon.
Instead of getting a SM-T830, I received a SM-T837T (T-Mobile version). I plan on getting it unlocked so that I can use it on AT&T, but from what I understand, it's unrootable.
Thanks, tho!
¿GJ?
doggydog2 said:
yes..why rooting an old version.. no OTAs later so you'd have to update manually again.
Click to expand...
Click to collapse
I was wondering about this. So there is no way to update once rooted, other than a full clean flash and start again?
ghoulie said:
I was wondering about this. So there is no way to update once rooted, other than a full clean flash and start again?
Click to expand...
Click to collapse
later use Frija to get new firmware and update. cleaning is only on first root as we can't avoid it when switching the OEM lock.
This thread is really one of the best thread for tab S4
Thanks for that
Sent from my SM-T830 using Tapatalk
Question, now that 10 is out will you update the OP, some things change.
I am not sure things like exposed can be update? Tried and get some reboot.
Proca not present and other things.
Thank you for your work
Sent from my SM-T830 using Tapatalk
Looks like it is not working anymore on Android 10:
https://forum.xda-developers.com/galaxy-tab-s4/development/rom-t4137013

How To Guide [GSI] [A13] Pixel Experience Plus for Galaxy S21 FE 5G (Snapdragon/Exynos)

* Your warranty is now void.
* I'm not responsible for bricked devices, dead SD cards,
* Please do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, i will laugh at you.
Click to expand...
Click to collapse
Pixel Experience Plus for Galaxy S21 FE (Snapdragon/Exynos) based on Android 13​Unlock bootloader first:
Go to your phone → Settings → About Phone → Software information → Press Build number 6 times until you see the notice “You’re now a developer”
Go in Settings → Developer options → enable OEM unlocking
Power off your phone first. Then, connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone.
When you arrived at Download Mode, long press volume up until you see the black screen. Confirm to unlock the bootloader and you will erase your device.
Click to expand...
Click to collapse
Guide for flashing system image:
Flash recovery for snapdragon version, i'm using: OrangeFox Recovery is also provided for exynos soc
Please do everything that is written for flashing recovery (Installation), u need to disable encryption and wipe data
reboot when you sure recovery is permanent and check if phone is on "hello screen"
How to boot on recovery first time BEFORE "hello screen":
Uncheck reboot after flash AP recovery in Odin, unplug cable and then push vol - and power -> immiedietly after turn off download mode hold vol + and power and plug in cable -> now should work
Flash GSI image:​First you need to download image from here: here or find thread here: click. This images have Google Apps allready included.
Remember to use arm64 with b !
Reboot to recovery
Now u should see on PC when u connect via cable internal memory - copy image to folder, probably should be "Fox" or create new
Touch files, find image
Now select to flash System image
Reboot
And thats it you should boot to system.
Post install settings​On Phh Treble Settings set:
Samsung features:
Use alternate audio policy
Enable stereo audio mode
Enable extended brightness range
Enable double tap to wake (if u want)
Enable reversed wireless charging (if u want to reverse charge other device)
Enable access to all cameras
Enable extra sensors
Misc features:
Force FPS to [email protected] if you want 120Hz refresh rate display
On camera set expose aux cameras and force enable camera2api
Select Use System Wide BT HAL if u use bluetooth headphones and don't have audio (tested on galaxy buds 2)
Qualcomm features:
select use alternate camera profile if u have trouble with ultrawide photos
Root access on Pixel Experience Plus:​
You should first patch boot img from your stock samsung rom what you allready using
U need to select ap tar.img file in Magisk and wait to be patched
Extract boot.img from it after patch
Flash boot img in recovery on boot image
Root stays even if you reflash system on other GSI
Works:
WiFi 2.4GHz and 5GHz
RIL (phone and mobile data)
Bluetooth with bluetooth audio
fingerprint sensor
Google Pay with NFC (you need to pass safynet check if you have magisk)
120Hz display
Camera front and back (you need other camera app for using ultrawide photo)
Fastcharge
Stereo speakers
Galaxy accessories (Watch 4 and Buds 2 tested)
MHL mode
Probably other functions too
Not work/problems:
Netflix have videwine L1 but no HDR content support
Movies only record max on 30FPS on 4K
On the go don't work any of galaxy wearable devices, you need to patch via magisk some files
Clear View cases (phone don't response for open or close case) even on AOD
Some problems with updates for Chrome and web framework (need to install manual newer version)
Device is showing as Huawei Nexus 6P need to be changed somehow to our model
Workaund for Galaxy Wearable and Google Pay:​
Magisk need to be in zygisk mode
Flash Universal SafetyNet Fix, here: github download
Install FoxMMM for magisk modules finder here: here, find and install MagiskHide Props Config
Flash this for workaund of wearables: gdrive module download
Now download Galaxy wearables from store, and plugins for your proper device form apkpure or other website.
You need to allow all permisions for apps first
Try to find your watch and pair it, you need to be fast to accept all pop ups - u dont need to login to samsung account , for me got it after 2-3 try, you should see "prepairing device" etc.
For galaxy buds should be easier just find it and pair.
Google Pay works out of the box after installing this modules
Get better sound and equalizer:
If you want to have better audio - you need to flash magisk module ViperFX
Download here: click here on github
Flash via magisk
Uncheck legacy mode for work
@hunter3000
Greetings. Since this appears to be a "guide," I have changed the thread designation accordingly.
-Regards: Badger50
@hunter3000 i think you can change the model number in the build.prop if im not mistaking
Hi, can i flash it like the offical pixel experience? Because the offical one is a zip file and this one not
this is GSI style rom, not specific ROM for specific model, so you must flash it by twrp or by fastboot command. Like universal rom for all phones than have project treble.
Thanks for support
Im looking to xda everyday for a stable pixel rom
MemurBey said:
Thanks for support
Im looking to xda everyday for a stable pixel rom
Click to expand...
Click to collapse
Majority of GSI are stable but you will have bugs tho. Like either bad battery life or camera isnt working
On this build all functions is working, for camera ultrawide support you need 3rd party app like OpenCamera.
hunter3000 said:
On this build all functions is working, for camera ultrawide support you need 3rd party app like OpenCamera.
Click to expand...
Click to collapse
Does Gcam Works on any Gsi on the SnapDragon variant? No freezing viewfinder?
no gcam working on snapdragon, or i dont find any working for our model.
hunter3000 said:
Please do everything that is written for flashing recovery (Installation), u need to disable encryption and wipe data
Click to expand...
Click to collapse
When disable encryption how safe is the Data stored on the Device?
OptixWolf said:
When disable encryption how safe is the Data stored on the Device?
Click to expand...
Click to collapse
you must disable encryption to boot to non official rom, so you got answer for your question
Master, any solution to this ? "Device is showing as Huawei Nexus 6P need to be changed somehow to our model ", and Call Recording is working on this version ? many thanks for your hard work to G990B version.
This device showing is related to magisk safenet fix for working root with NFC and banking apps but probably also because of GSI rom as is. No call recording as is stock Pixel Experience ROM u need to root and use some magisk module.
Works great on my Samsung s21fe just charging.. sometimes works then other times says it's charging and then does down. Doesn't really go up unless phone is off.
May I know if VoWifi / VoLTE works?

Categories

Resources