Related
Root SM-T707A on Lollipop with SuperSu - Xposed & Debloated - Part II
Where are we right now?
* Part I: Flash Stock Lollipop 5.0.2.
* Part II: Gain Root access for Lollipop with SuperSU. <---- YOU ARE HERE!
* Part III: Flash Xposed Framework thru Flashfire.
* Part IV: Debloat the tablet from both AT&T and most of Samsung stuff.
* Part V: Improve usability and aspect with Xposed Modules.
Once again, some words of our sponsors: NO, I'm NOT resposible for any consequence originated from the use of this guide, being that the death of your tablet, or your smart tv, the Panama Papers or Luis Suarez just playing rough with Filipe Luiz's foot. Whatever happens to your tablet, it's ON YOU.
Introduction (PLEASE READ!):
This guide works as a continuation of Part I, so we assume you flashed KitKat and applied Lollipop updates as described.
If you are already on Lollipop and have several weeks using it, of course you can try this guide, but I STRONGLY SUGGEST to start from zero, backup your files and use the guidelines on Part I of this guide.
Part II: Gain Root access for Lollipop with SuperSU
IMPORTANT - During the first boot on our brand new lollipop, don't try to connect to your WiFi and remove your SimCard if availble before even selecting any option. We don't want any internet at this time.
Our first move in Lollipop is to Reject all the AT&T offers..
Then accept terms of Samsung EULA (and hit No Thanks below)...unless you want to share information with Sammy.
Then you can put your name (I didn't), it' s up to you.
Disable the 3 checkboxes for location services (you can enable this later).
Then skip the Samsung Account creation and hit also Next on my "Find my mobile" screen without doing nothing.
Finally, you'll reach the Android Desktop.
Setting the stage for rooting with KingRoot
Still avoiding any conection to the internet, go to your apps and tap Settings.
Before doing nothin, I strongly suggest you change your language to english in case you use another.
If your first language is English, you're good.
If it's not, you can change it on General TAB, then "Language and Input".
After this, tap the Device tab, choosing then Display option on the left.
Choose Screen timeout and select 10 minutes.
Now select Lock screen on your left and Screen lock on your right. Tap "None".
Now go to "General" tab and tap "Security".
Enable the Unknown sources checkbox and press OK on the popup.
Press home button. Now you can connect to your Wifi.
The moment you got Internet, Samsung will start forcing some updates on your tablet.
At the same time, several Google popups will ask you to "regularly check device for security".
Decline them all the time!
There is a "Games" app that loves to open itself without asking
When that happens, it will introduce you to an agreement that you will REJECT.
If it doesn't show, better. But it will eventually.
Now enter the Play Store and Log in with your credentials.
Accept the playstore conditions when prompted. If you are kicked out of the app just enter again.
Still inside Playstore, now swipe from your left side border to gain access to the menu.
Tap "My Apps" and use the "Update All" button on the right.
Accept all APP Permisions (seven times in my case).
The update process will start. This will take some time so BE PATIENT and do nothing else.
When everything is updated, you'll notice some warning on your status bar.
Swipe down your status bar. It will ask several times to Update Google Play Services.
Tap any of update offers for Play Services. Playstore will open again offering the update.
Hit Update and Accept. When the update of Google Play Services is finished, hit the Open button.
You gain access to Google Settings. Tap Security.
Disable "Remote locate this device" - "Allow remote lock and erase".
Disable also "Scan device for security threats" and "Improve harmfull app detection" (unless is greyed out).
Hit the home button and go back to desktop.
Installing KingRoot
For the next step, you need to download these files on your PC:
* Kingroot V4.90
* RemoveKing
Copy them on your tablet's internal memory. Specifically on the root of your internal memory. If you copy them inside a folder, later commands will fail.
Back to your tablet's desktop, look for the folder icon on the bottom left corner. This will open the Samsung File Manager. Look for "Device Storage" on the left column. If you copied the files correctly, you'll find both on the right pane of the display. Extract the RemoveKing.zip file by tapping it and clicking "OK". A RemoveKing folder will appear on the root of your filesystem.
Now open the Kingroot V4.90 file. Hit Next and then Install.
If a google warning appears citing - "Installation blocked". Hit "Install anyway" (unsafe).
If it doesnt, just hit Open. A blue screen shows up with the legend "ROOT auth".
Swipe upwards twice (assuming you're holding your tablet in portrait).
Now hit the "Try it" button. The app will verify root status in a matter of seconds.
Now tap the "TRY THE ROOT" button at the bottom.
When the root is sucessful, you'll be asked to "Forbid Knox".
Tap Cancel and press the home button. Now you are rooted with Kingroot.
Installing and preparing Terminal Emulator
Now that we are rooted, enter the playstore and install the app "Terminal Emulator for Android". Open it. You'll notice some small font selected so, hit the 3 dots on the right upper corner and go to preferences. On Font Size choose 24 pt. Hit the back physical button of the tablet. Now the "white letters" become readable. And it shows something like:
Code:
klimtlteatt:/ $
Next type the following and hit enter:
Code:
su
A Kingroot popup will ask for root permission. Tap "Allow".
Now the $ symbol will change for #.
Next you hit the HOME button to exit the app briefly (don't close the app in any other way, just hit the HOME button).
Uninstalling KingRoot
After that, go to your apps and enter the KingRoot app.
Now tap the 3 dots on the upper right corner and select "General Setting". Disable "Smart Authorization", then disable "Enable Root Authorization". Finally choose below "Uninstall KingRoot". Hit Continue. Uncheck "Backup Root" when prompted and hit OK. When all is over, you're back to the desktop. Go back again to your apps and uninstall Purify.
Applying the Scripts
Open again Terminal Emulator app (thru the app Icon) . Now we need to hit a couple of scripts by moving first to our extracted folder by entering the following command on the terminal (plus enter):
Code:
cd /sdcard/RemoveKing/
To run the first script type (then press enter):
Code:
./step0.sh
It just takes 3 seconds, then type the following and press enter:
Code:
./step1.sh
This last script will ask for a confirmation during its process.
Type just an "y" and hit enter: (WARNING, the Y won't appear on your display after typing it)
Code:
y
You'll notice a bunch of errors, don't mind them.
Installing SuperSU
Now hit the home button and go to the play store.
Search and Install SuperSU (free version). Open it. Choose Expert.
The app will ask "The SU binary needs to be updated, continue?".
Hit Continue and then choose "Normal" when asked on the next popup.
You'll receive an "Installation Sucess!". Tap the Reboot option.
Congratulations! You are now rooted with SuperSU.
After rebooting, enter the Terminal app once more, and tap the X on the right upper corner and hit OK.
That will finish the current terminal session.
If you're interested in getting Xposed Framework, go to part 3 of this guide.
If you're just interested in debloating the SM-T707A and improve its performance, go to part 4 (Soon).
Part 5 is where I discuss the modules I'm using on Xposed and also some Playstore apps to improve functionality, and remove as much Touchwiz as possible, while also working on better battery life (Soon too).
Final Considerations (suggested reading - not mandatory)
While this guide may seem easy to carryout, it took me almost a month to get SuperSu to work on Lollipop.
I'm no coder (a soon to be Certified Public Accountant), and the real magic to pull this off was to try many combinations of different app versions, different situations with google services and several strategies with the script and superSU. In fact, most of KingRoot versions don't work on this tablet to get root, also tried SuperSume app from the playstore. The same could be said for KingoRoot (don't confuse it with KingRoot), it worked but I couldn't remove it without losing root.
Why I'm telling you this? Because using KingRoot and similar apps to root this tablet, your mileage may vary while doing it. In fact, even while applying my first two guides there's a respectable chance of KingRoot tool failing to root your tablet. If you followed this couple of guides to the last comma, your chances of success are very close to 100%. But I have noticed in similar Galaxy Tab S threads, that the use of KingRoot and KingoRoot to achieve root is just a matter of using the root tool many times until it works, and I wanted to avoid you guys going thru that. To take sucess rate as close as it gets to 100%, we took all of this steps. They were included to avoid many failures. I believe they're are 99% flawless to achieve root on Lollipop with SuperSU.
Also, the second script won't remove many KingRoot files, because it was thought for KingoRoot on KitKat.
I have to give myself more time to develop something that could really clean up the last traces of KingRoot.
Special Thanks
* @chixvicious - For showing how to achieve the same over KitKat and KingoRoot instead.
* @bakageta - For creating these scripts for the Alcatel smartphone over KingoRoot.
* @Kingxteam - For developing KingRoot to allow us to root our device.
Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.
bakageta said:
Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.
Click to expand...
Click to collapse
They were life-savers, thanks a lot for them!!
Broken links?
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!
kainanmaki said:
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!
Click to expand...
Click to collapse
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again
ElCid43 said:
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again
Click to expand...
Click to collapse
I hope to get part IV and V in no more than 10 days...
I'm in the process of testing removing/freezing many services, just a sneak preview:
So far I was able to disable close to 180-190 apps/services from a total 250-260 (can't remember the exact number).
Of course there are some key services removed (for e.g multi windows, but that's just one service).
Still you can easily remove like 165 without losing any stock functionality. That's how much bloated the tablet is.
Removing useless stuff from samsung and 3rd party (eg. VPN, Policy Updates) or more evident like MultiWindow, the gallery app or even the file browser.
Or the weird ones like the phone app that is hidden and you can't use (you can disable it and still keep LTE Data).
More to come.
Need Help - Having Untimely Reboot Issues
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom
Where did you find the alternate method??
zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom
TomandJonna said:
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
I had that problem many times, the uninstall reboots the tablet before you can establish SuperSu.
The most reliable way I found of overcoming this is to follow the exactly in this order and without stopping to much because google wants to run updates behind scenes that mess with our process (that's why sometimes it works and sometime it doesn't). My recommendation is to start over from scracth again (I know it's boring). I'll probably do it again on my tablet just to validate and to try some other things related to the original services).
TomandJonna said:
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
Other thing I forgot to ask, did you started clean from the first part or just started with part 2 of the guide?
Will this method trip Knox?
i need * RemoveKing file now...
POST IS UPDATED REGULARLY.
LINK 1 - Parallel Space: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl&hl=en[/URL][/URL]
LINK 2 - Parallel Space 64-Bit Support: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl.arm64&hl=en[/URL][/URL]
Salutations. (That means 'Hello').
NOTE: For those who are interested, I will include background information about how I came to the solution. All that other jazz too. First and foremost however; the fix!
SOLUTION:
Right at the top of the post, you will find two links. This being a new account and all (don't ask), until I create 10 posts I cannot include any outside links. So once I've done so, I will update the post.
STEP **: So at the top of the post, there are clearly two links. 64-Bit Android devices are becoming increasingly common. This architecture may pose a few problems. give the application framework. Should you own a 64-Bit device, I recommend installing this application too (LINK 2). This will theoretically prevent any obstacles.
Pre-requisite(s): Make sure you have the 'Snapchat' application installed. It is recommended to have installed the latest update from the Google Play Store.
STEP ONE: Download the application appended to LINK 1. This is called Parallel Space. You might recognize the name (its creators are the same who allow you to seamlessly virtualize Windows OS on Mac OS).
STEP TWO: Launch the application.
STEP THREE: You should be prompted with a grid-like interface. Here you will be greeted with a range of familiar icons. In the top right corner of each icon, you will notice a blue check-mark. Make sure that there is one next to the 'Snapchat' icon. This will ensure that the app is 'cloned'.
STEP FOUR: In the 'Parallel Space' app, tap on the 'Snapchat' icon. This will launch the application.
STEP FIVE: From here it is pretty self-explanatory. You are greeted by the standard 'Snapchat' interface. Tap on 'Log In'. Then proceed to do so.
STEP SIX: 'Snapchat' should be functioning as normal.
STEP SEVEN (BONUS): During testing, this worked on and off. --
Remain logged-in to the 'cloned' 'Snapchat' application within the 'Parallel Space' application.
Then proceed to launch the stock 'Snapchat' application.
Next attempt to 'Log-In'.
Should this operation be successful, you are then free to uninstall 'Parallel Space' and any related assets from your device.
HOWEVER, I personally do not recommend this. When logging out or updating the 'Snapchat' application, errors may be re-encountered.
Instead, I recommend that if possible, do use the stock application, but leave 'Parallel Space' installed. Using the stock app will improve efficiency and reduce the load on system resources. But keeping the 'Parallel Space' application on the device, well; you get the point.
Enjoy the fix! If it does not work, please let me know [Device Name and Model No.]. I've tested on various devices, succeeded every-time. Do keep in mind that this is a loop-hole, so may be patched in future or not work at all for some devices.
Background (Because I know someone will ask): The idea came to mind while using a LG G5 as a daily driver. I had tested every custom ROM available for the device. The problem was that with custom ROM's, there was always an issue, Malfunctioning sensors, camera's not working persistently, etc , etc.
The G5's stock ROM left me wanting more. The overbearing interface made it a living hell. Plus, the device just being rooted (NO XPOSED) meant that 'Snapchat' did not work. I looked for fixes for a time, but could not find any.
Development of ROM's for the device is on-going, and I am an active member. But I just couldn't handle not being able to use the camera (one of the device's best features) and no accelerator, screen-rotation, etc. So I went back to stock again. Do keep in mind that I was alternating/dual-booting between custom and stock ROM's just because of the camera; mainly.
This most recent time. instead of flashing stock MM, I flashed stock N for the G5. For 850, it has been officially released in some countries, and a manual flash via TWRP was a peice of cake.
This update is a lot better. I am running Nova Launcher again. So it makes it look a little better. Themes have also been improved. I am using an in-built dark one which makes the device look a lot better aesthetically. Additionally, I'm rocking a white carbon-fibre skin on the exterior; improving grip and overall security. The only issue was again, no 'Snapchat'.
After a few days, I had the idea to attempt this. I tested my theory and it worked! That's it.
Please do keep in mind that I will update this post as often as possible.
P.S This was tested just after updating to the latest version of 'Snapchat' which was a significant update. It included Shazam, Groups, etc. So you know, pretty cool that it worked.
Did not work on Google Nexus 5 running Android 7.1.1. Still gives error message saying that I can't connect to the server.
Same here, not working on freshly reinstalled and rooted 7.1.1 Nexus 5x. No Xposed, no nothing. I get the infuriating "temporarily failed" message in both cloned and regular modes.
It didn't worked. S7 edge exynos (6.0.1)
Holyphe said:
It didn't worked. S7 edge exynos (6.0.1)
Click to expand...
Click to collapse
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
hot_potato said:
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
Click to expand...
Click to collapse
Whats the name of it?
Holyphe said:
Whats the name of it?
Click to expand...
Click to collapse
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
AndroidFL said:
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
Click to expand...
Click to collapse
That's the only solution I've seen working so far. unroot and reroot. Root cloak doesn't work, parallel doesn't work. I should've logged in before rooting and I hate to do it again.
Any work arounds yet? I've seen ppl do it using titanium backup but I'm not sure if that works. Can anybody help?
Samsung s5 G900v Not working
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Dukeboyty said:
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Click to expand...
Click to collapse
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Okay. I will try this on monday and will let youknow how it goes. Right now I decided to unroot to use snapchat, so I didn't loose my streaks. Thanks in advane will let you know how it goes.
immorality said:
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Click to expand...
Click to collapse
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Dukeboyty said:
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Click to expand...
Click to collapse
Snapchat detects xposed framework.
Though at a time they did do root they since moved to blocking xposed due to the security concerns with money and also privacy of the user.
Though with certain phones and ect that could be the case I am using a s5 and have no issues.
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
ahmedsasker said:
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
Click to expand...
Click to collapse
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Fnn.09 said:
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Click to expand...
Click to collapse
make a nandroid backup if u want
1- full unroot by opening supersu and going to settings and press Full unroot and wait till it finishes and restart
2- download xposed uninstaller if u have xposed framework installed and flash it
3- install magisk manager from playstore
4- download and flash last magisk which is (12v) now from : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
5- flash magisk v12.0 which you downloaded now your phone will have systemless root
6- go into magisk manager app and go to settings and toggle "Magisk Hide" (ON) and restart now your root is hidden
7- remove your current xposed app and install this one : https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
8- flash systemless xposed : https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
9- reboot and go to the xposed installer app and toggle the xposed off or on as you want when u restart it won't take time optimizing apps like before so fast now
your root is hidden now but xposed is not but you can disable it and enable it easily
Instead of using Parallel Space (which I believe to be insecure) use Island to clone your apps. It's a little more advanced to setup, but it's a lot more secure. It works for rooted and non-rooted devices. On the 1st page of the thread, it explains how Parallel Space and others repack the apk file locally, which is dangerous. https://forum.xda-developers.com/android/apps-games/closed-beta-test-incoming-companion-app-t3366295
Island never repack apk file locally, which is inherently insecure for users, since all your app data (including password input) are technically in the hand of MoboClean. (The same applies to other similar tools, e.g. LBE Parallel Space)
Instead, Island takes advantage of the underlying mechanism used by "Android for Work". This ensures that all your apps run natively in Android system and their data are securely stored in internal location of Android which is never accessible by Island. It has the same level of security as "Android for Work".
Click to expand...
Click to collapse
Be sure to read the disclaimer!!! The app is still only available in closed beta at the time of writing this, and could possibly cause you're device to bootloop or even possibly brick it, but root, xposed, or other modifications {in my opinion) has a higher chance of bootloops or bricking your device.
You follow the same steps in island to clone snapchat as you would in Parallel Space to login to snapchat. It might be possible to use the play store inside island to download snapchat inside island and login that way. I can't remember exactly how it works. I believe that island is a good way to test apps in a "sandbox environment" to keep the data excluded, safe and secure from the regular apps that you have installed outside of island.
I use Magisk now which bypasses SafetyNet which is what snapchat uses to "block access" to modified/rooted devices.
Probably the easiest method is to download Casper which is an alternative snapchat client that allows you to save snaps, and many other features that the official snapchat client can't do. Find Casper at www.casper.io
FYI Netflix has started to change how they do things as well by hiding the app's play store page from devices that have been modified or rooted, but it's still possible to simply sideload Netflix for now.
Hi everyone,
I have a Sony Z3 compact I just received, model D5803 running Android 6.0.1 with Firmware 23.5.A.0.575.
I really dislike Google and want to run a phone with the minimum of proprietary software (I guess blobs to communicate with the hardware are mandatory). I guess AOSP (any version, but a recent one would be better ) with F-Droid is a good solution.
Unfortunately when checking the sony website but it tells my the bootloader is not unlockable. What should I do? I'm running Ubuntu and have adb and fastboot installed.
I found [this topic](https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714) which tells it roots the phone (and has a GNU/Linux script) but how does that help me to install a Rom, for example the AOSP provided by Sony at /open-devices/list-of-devices-and-resources/ if the bootloader is still locked? What are TWRP and busybox, is that supposed to help?
Flaburgan said:
I found [this topic](https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714) which tells it roots the phone (and has a GNU/Linux script) but how does that help me to install a Rom, for example the AOSP provided by Sony at /open-devices/list-of-devices-and-resources/ if the bootloader is still locked? What are TWRP and busybox, is that supposed to help?
Click to expand...
Click to collapse
TWRP is a custom recovery that allows you to flash a ROM and other files, that are stored on the normal internal or external storage.
Busybox is a binary that gives you command line tools that are often included in a Linux install and some of which aren't included on normal Android. These are commands that other things may make use of, or that you can make use of at a terminal app or run from Tasker or similar app.
You want to look at backing up your TA partition, which stores your DRM keys, before unlocking the bootloader to install a custom ROM because some functionality, camera quality and anti-distortion, sound quality, and some other stuff which I don't remember, won't work if you go back to the stock ROM unless you have these keys backed up and then restored later. You need to unlock the bootloader in order to flash a custom ROM and doing this erases, permanently, these DRM keys, so they need to be backed up and then put back later if you relock the bootloader and flash a stock ROM.
If you look in the Original Development section, Jaguar Aries ROM has no Google Apps, had the latest patches up to Febuary, and had the best battery life of any custom ROM I've seen for this phone, right on par with stock. There are some builds of Lineage OS that are probably closer to being up to date as well and may have a better camera than Jaguar. The developer of Jaguar has moved on to another phone. That said, if you aren't experienced and don't know what TWRP is, then installing it is an extra step from other ROMs as well since it requires you to setup a firewall app to permit connections on data or wifi before you can use the wifi or data at all. I doubt Lineage OS has this, but presume that battery life would not be good.
Also, if you install microg apps, you can still use things such as cell and wifi based location, google push services, and ... I don't remember what else, however it hasn't been updated recently and many apps will complain and refuse to run saying that you need to update google play services, especially annoying for anything that uses push especially. Microg essentially sits in the place of where some functionality of Google Apps would and fills in some blanks.
When you don't have Google Apps installed, many paid apps will refuse to run as well, specifically the ones you paid for, because they can't verify the purchase with Google servers. There should be a **** list for any developers that don't cooperate when this is a problem for a user. I've only had one app developer help me on this, ever.
Thanks for your detailed answer!
You need to unlock the bootloader in order to flash a custom ROM and doing this erases, permanently, these DRM keys, so they need to be backed up and then put back later if you relock the bootloader and flash a stock ROM.
Click to expand...
Click to collapse
Does that mean that I can't use the DRM keys with another ROM? So I will never have the full quality of my hardware? Would using the AOSP rom provided by Sony solve that problem?
On which version of Android Jaguar Aries ROM is based? I searched for a lineageOS image but didn't find any for the Z3 Compact.
I had another z3c which died and was running Firefox OS, I'm fine with not having access to the Google Play store, I plan to install F-Droid and use only FOSS apps. In fact I would even prefer to go back to Firefox OS even if it is not maintained anymore, its UX is so much better than Android... That said, thanks for telling me about Microg, I didn't know it and that's true that many apps use Play services especially for push. Even Signal had that as a dependency (fortunately not anymore). Still, I would avoid any data coming out from my phone to by sent to Google servers, so I will probably avoid it.
Flaburgan said:
Thanks for your detailed answer!
Does that mean that I can't use the DRM keys with another ROM? So I will never have the full quality of my hardware? Would using the AOSP rom provided by Sony solve that problem?
On which version of Android Jaguar Aries ROM is based? I searched for a lineageOS image but didn't find any for the Z3 Compact.
I had another z3c which died and was running Firefox OS, I'm fine with not having access to the Google Play store, I plan to install F-Droid and use only FOSS apps. In fact I would even prefer to go back to Firefox OS even if it is not maintained anymore, its UX is so much better than Android... That said, thanks for telling me about Microg, I didn't know it and that's true that many apps use Play services especially for push. Even Signal had that as a dependency (fortunately not anymore). Still, I would avoid any data coming out from my phone to by sent to Google servers, so I will probably avoid it.
Click to expand...
Click to collapse
When you unlock the bootloader the DRM keys get erased permanently, so you'd need to root the phone and back up the partition where they are held before unlocking it. As far as I know, every custom ROM needs to have the bootloader unlocked. If there is an alternative way to install a ROM on a locked bootloader then it would be one of those scenarios where its installed while keeping the stock one, and I don't know if this has been done on the Z3c or not.
I also don't know if Sony's AOSP requires unlocking the bootloader or not.
Jaguar is based on 5.1.1
Its a mix of AOSP, Lineage, and was getting monthly backports of the latest security patches until Febuary when the developer no longer had a Z series phone for his own use. The only criticism it met was that the developer never released the source code for the entire ROM, just the kernel. He never replied to why that was. A lot of the custom ROMs out there are like this, so its still a case of who you choose to trust when it comes to this a lot of times. I liked it because the battery life was really good and assuming the security was what was advertised then that was also a real plus.
Many apps, by the way, were working fine with microg push but then with updates to apps, they complained about needing to update google services framework, which obviously was spoofed and microg hasn't been updated, and it happened to a lot of apps in a short period of time, so I assume there was a change enforced by Google for their requirements in the Play Store. If you just want it for location, for example if you use Osmand maps, then you don't have to enable the feature for push notifications nor have a google account associated with the phone, and it all works as user installed apps, so it can be undone without any real fear of the system getting modified after you try it out. There's a microg repo that can be added to fdroid. The location is based on either databases you download to the phone, which aren't very good, or also you can opt for cell location from Mozilla servers, and if you have to have wifi based location as well then you can hook into the Apple servers but the latter doesn't sound like something you want, if you want to do any of it at all that is.
I think most likely that GPS location would work without any need for microg.
The post you linked to with the Linux script installs TWRP to the /data partition, then you root it, then you back up the DRM keys after its rooted, then unlock the bootloader, install normal TWRP, and go from there. In Linux you'lle want to use the dd command to back up the DRM keys as all that's available on the forum is a Windows script (I think). There is info on it somewhere but it would be hard to find it. If you search my posts the thread will come up somewhere in the history. Anyway, the reason I broght this up is because the script in the thread for installing TWRP and rooting didn't work properly. I don't remember why, but I had to go through it line by line and enter the commands in from a termnial to get it right, I think there was some bad syntax. If you can't figure it out, quote one of my posts and ask, that way I get a notification that I was replied to, I think I have a fixed version of it on my drive somewhere if it causes a problem.
For the DRM keys you want to backup the TA partition bit for bit to a file. I backed up my Fota partition as well as I was unclear what role it plays. You also want to keep a copy of that particular Sony ROM file, and the two kernels involved, to flash with Flashtool in case you relock and restore so you can get root access to restore the partition while the bootloader is locked again.
May I ask why are you going FOSS only? if that's because privacy concerns, then FF OS is not the best solution... Because any Cloud-based OS is a little bit creepy, doesn't matter if it's ChromeOS from Google, or FirefoxOS from Mozilla.
There are plenty of Linux distros dedicated to run on Android phones, but it's not the best UX.
And yes, you can enjoy clean AOSP install (LOS is fine) without flashing G-Apps. But you won't have Google play at all! F-Droid is fine but you won't find there Gmail alternatives, you can't find Gmail even on Amazon AppStore... Sadly if you install Gmail then you'll find out that it installed bunch of google apps and hidden services behind the scenes... So only option is to use Gmail web app.
But then again, F-Droid is fine, there are many FOSS alternatives to youtube and other apps.
And if privacy (and security) is your concern, use LOS privacy guard / Android's builtin Permission Manager, and on Rooted ROMs you can use AFwall firewall which is the best.
Good luck
GadgetAvi said:
Because any Cloud-based OS is a little bit creepy, doesn't matter if it's ChromeOS from Google, or FirefoxOS from Mozilla.
Click to expand...
Click to collapse
Firefox OS is not a Cloud-based OS at all. It runs perfectly without internet connection.
GadgetAvi said:
F-Droid is fine but you won't find there Gmail alternatives, you can't find Gmail even on Amazon AppStore...
Click to expand...
Click to collapse
Be sure that if I don't want Google on my phone, my e-mails are already **not** on GMail...
Ok, if so, then you'll be fine with any AOSP clean rom. LOS is great, and F-Droid as well. Cheers!
PantsDownJedi said:
The post you linked to with the Linux script installs TWRP to the /data partition, then you root it, then you back up the DRM keys after its rooted, then unlock the bootloader, install normal TWRP, and go from there. In Linux you'lle want to use the dd command to back up the DRM keys as all that's available on the forum is a Windows script (I think).
Click to expand...
Click to collapse
I ran the commands and the phone is now booted on TWRP from the /data partition. I did a backup with TWRP of all proposed options (Boot, TrimArea, Recovery, System, Cache and Data). Is that "TrimArea" enough to have a backup of the DRM keys? The other topic talks about Backup-TA but looking at their github https://github.com/DevShaft/Backup-TA/releases it looks very old and unmaintained.
The current TWRP I'm running is 3.1.0-0.
Also, it looks like I'm not root (at least, su is not available). Do I have to install SuperSu by giving this zip https://download.chainfire.eu/696/supersu/ to TWRP?
Flaburgan said:
I ran the commands and the phone is now booted on TWRP from the /data partition. I did a backup with TWRP of all proposed options (Boot, TrimArea, Recovery, System, Cache and Data). Is that "TrimArea" enough to have a backup of the DRM keys? The other topic talks about Backup-TA but looking at their github https://github.com/DevShaft/Backup-TA/releases it looks very old and unmaintained.
The current TWRP I'm running is 3.1.0-0.
Click to expand...
Click to collapse
I don't know. I haven't looked at a TWRP backup to see what format it is. Back when Clockwork Mod was all that was available, it merely made a tar.gz of partitions. Ideally you want a bit for bit image of the TA partitions to make sure it was exactly what it was when you restore it. I don't know if that's necisarry, or if TWRP does this anyway, but using the dd command is still prudent.
You want to either use a terminal emulator app or run 'adb shell' at a linux terminal (much easier), run 'su' once in the phone environment, allow it at the phone supersu app popup, and then do it like this.
https://forum.xda-developers.com/showpost.php?p=61307511&postcount=6
And store a copy of the image file where it won't get lost.
Edit: Sorry, I didn't see the other post. Yes, you need to flash that supersu zip file. When you try to access root from an app or the command line, it will have a popup on the phone screen asking you if you want to allow access or not, so when you run it from a terminal, 'adb shell' to get into the phone OS, there will be a popup for allowing that often times. Then 'su' there's a popup from the supersu app you just flashed. Then 'cd' to the sdcard or external sd. Then the 'dd' command. The dd command in what I linked to is inevitbaly what all those .bat files in the Windows TA Backup thing does after it does a bit of looking around to find the TA partition for a particular phone model.
The md5sum part of what I linked to compares the partitionn itself to the image file you just wrote, you just look at it to see that there are two of them (that it didn't fail) and that they are the same.
The last part pulls the image file to the hard drive, but there are other ways to accomplish this obviously. If you have a cloud storage you can upload it there, or send it as an email attahment, put it on the external sd, etc etc.
Also, in many cases, once you unlock the bootloader to flash something else, you'lle need to install TWRP again from the command line, pushing it straight to a phone partition. You'lle need help with this if you haven't done it before.
Updated version of this ROM: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]G930TUVU4CRI2
ROM last updated: 10/30/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This ROM is a complete rewrite of my ROM [ROM][TMOBILE][S7_SM-G930T][Oreo Rooted] That ROM doesnt have WifiCalling & I couldn't get it to work for the life of me, so I rewrote it. I started with stock, and slowly stepped back making changes, reinstalling each time, confirming it still worked. About 200 installs later & 1000s of changes, this is the result. Yes, it took a LONG time. Hope you enjoy it! Don't forget to say Thanks so I know it is actually helpful to others, and continue doing this!
Description:
Stock Tmobile Oreo 8.0 modified (G930TUVU4CRF1)
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc. Yes, this means NO Samsung or Android Pay. There could be more apps to debloat but Im out of time for now! (Please provide suggestions if interested)
Everything possible I replace Samsung with Google
Solid ROM. It was actually kind of slow for me, but I'm curious how this works for others.
Xposed is part of the guide, which will give you infinite customization & tweak-ability
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
This will delete all of your data on the phone! (Not external SD card) This is the only way so don't ask. Backup your data!
Features:
Tmobile Wifi Calling works, along with Visual Voicemail & Mobile Hotspot
Many Aroma Installer app options
(Optional) KevinsFavorites option in Aroma. I'm not sure I'd recommend it due to my tastes. If you're looking for some good common apps tho, it includes: Amazon, AmazonMusic, AquaMail, Gmail, GoogleDrive, GoogleKeep, GooglePhoto, Hangouts, IFTTT, Pandora, RootBrowserClassic, TitaniumBackup, Uber, & Wink (If you install these and want to remove them later, use TitaniumBackup (or similiar) to uninstall
Root Features: See Downloads->Recommended Root Zip & say Thanks!
Debloated
De-Knoxed
Decrypted /data/ partition
OTAs disabled
Speed & Build Prop Tweaks
Dual speaker
Ruthless Launcher
Apps
AdAway
AOD Clock Face Themes
CPUSpy
DisableService
Kernel Adiutor
Samsung Video Editor and Trimmer
Xposed
Many more...
Download Links:
Base.7z & Oreo_Kevin71246Modded_v3.#.#.zip
Installation:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Summary (for Pros)
Flash Oreo stock
Root
Flashfire
Oreo_Kevin71246Modded_v3.1.##, Auto-mount, Mount /system read/write Option
Go through Aroma setup. When finished, it should boot to Recovery (if not do this). Do a "Wipe data/factory reset"->Reboot
Detailed Steps
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again. Once in Android, go to Settings->Display->Screen resolution->WQHD->Apply
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM & Xposed
Download & copy Oreo_Kevin71246Modded_v##.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash Zip or OTA->Oreo_Kevin71246Modded_v#, Auto-mount, Mount /system read/write Option->Check mark
Click Lighting bolt at bottom-> OK
Phone will reboot to Aroma. Go through setup. (See above for what's in KevinsFavorites)
When finished, allow Aroma to exit.
It should reboot into Recovery (If not, do this: immediately hold Vol-Up btn+Home btn until you see recovery on screen. If you missed it, try again: hold Vol-Down+Pwr btn ~10sec until phone restarts & immediately hold Vol-Up btn+Home btn until you see recovery on screen.)
In recovery: Factory Reset->Yes->Restart phone
*Wait 5-10min on loading screens
Go thru Android setup. Ignore "Xposed Installer has stopped" error
Followup-Steps:
Set Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Recommendations:
Xposed
Setup Xposed: Xposed Installer app:Install framework option & restart phone
Xposed Installer app: Settings button (3 lines)->Download->Search "GravityBox [O]"->Click it->Versions tab->Download->Install->Back arrow (upper left)->Settings->Modules->Check box next to GravityBox [O]->Restart phone
GravityBox [O] Tweaks: (Open GravityBox app)
Battery indicator: Statusbar tweaks->Battery settings->Turn on Master switch->Battery indicatory style: None->Battery percent text...->Back
Clock: Statusbar tweaks->Clock settings->Turn on Master switch->Center clock...
Firefds Kit [O] Tweaks: (Install same way as Gravity box)
This is a supplement to Gravitybox. Things of note: Advanced power menu, call recording, & disable bluetooth toggle popup, etc
Known Issues:
Visual Voicemail may fail to register, but restart phone and give it a few hours. It works eventually.
RCS (Rich Communication Services/AdvancedMessages/Chat) texts don't show up in Android Messages & Textra, etc apps (This is an issue on stock as well!!)
Fix: (Use Samsung Messages)
How to Install Samsung Messages via ADB (Easiest way though is just reinstall!):
Download Messaging_SEP81.zip, unzip, & manually copy apk to phone via usb/Windows My Computer
adb shell (Get into shell to run beow commands)
su (Run as root)
mount -o rw,remount /system (Mount system read/write since default it read-only)
chmod 755 /system/priv-app/Messaging_SEP81 (Set permissions on folder)
chmod -R 644 /system/priv-app/Messaging_SEP81 (Set permissions on apk file)
ls -l /system/priv-app/Messaging_SEP81 (Check permissions - Should be: -rw-r--r-- 1 root root - not sure what 1 & 2 is)
ls -l /system/priv-app | grep "Messaging" (Check permissions - Should be: drwxr-xr-x 2 root root)
reboot (Reboot device)
Changelog:
Version 3.1.32: First stable build
Ver 3.1.36:
-Disabled encryption on /data/ partition to resolve "Bluetooth paired devices deleted after reboot" issue & so mods play nicer with ROM
-Fixed "Device not supported" error on Google Phone app
Ver 3.1.37:
-Added most of the apps I replaced or added as options in Aroma Installer now
Credits:
- @jrkruse & @klabit87 for Root
- @partcyborg for helping jrkruse
- @jrkruse for his similar ROMs as guides & help
- @Lanc-City for assistance in ROM modding
- @gustco for eng boot.img
- @Raymonf for modified odin
- @amarullz for Aroma Installer
- @Chainfire for FlashFire & SuperSU
- @rovo89 for Xposed
- @JaeKar99 for the cool & colorful boot animation
- @mrRobinson for AdAway ADAway.org
- Brandon Valosek for CPUSpy
- WangQi for DisableService
- Willi Ye for Kernel Adiutor
- @shubby for Ruthless Launcher
- @Craz Basics for Dual Speaker Mod
...
- Please PM me if you were forgotten!
Some screenies:
Saved2
Saved3
Well nice job!
jrkruse said:
Well nice job!
Click to expand...
Click to collapse
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
kevin71246 said:
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
Click to expand...
Click to collapse
Is this Ufirm firmware?
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
I have so many FW packages on my PC at this point, from so many places that I used while trying to get this to work, but I think it might be a package from one of your threads(?) Since I'm not exactly sure what you're asking regarding "Ufirm FW", I'll elaborate hoping that answers your question. (Tho I'm thinking you mean the U variation/unlocked. So based on these stock files below I guess the answer is no.) If you're question is really, "is it possible to get tmobile wifi calling to work on a U model #", then I'd have to really think about that. But at this point I don't have an answer. I can tell you a million dependencies about it tho! (I seriously have hundreds of revisions I made while testing, & notes. The symbolic & meta links in Aroma initially broke it, as I found out after a week or so of testing - wish I knew a bit more about them, and why they're all there, then I'd know what was wrong about them...)
High-level process:
1)Flash Base/Stock/Oreo Rom:
- AP_G930TUVU4CRF1.tar
- BL_G930TUVU4CRF1.tar
- CP_G930TUVU4CRF1.tar
- CSC_TMB_G930TTMB4CRF1.tar
- HEROQLTE_USA_VZW.pit
2)Root with your method
3)Flash Xposed framework & my ROM (it's a "start with stock then remove what we don't want" type of Aroma/Edify script)
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
kevin71246 said:
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
Click to expand...
Click to collapse
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
It works perfectly!!
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
charredchar said:
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
Click to expand...
Click to collapse
I believe I know what the issue is, I'm testing a fix (for THIS ROM) as we speak. Stay tuned. Maybe tomorrow if I have time and it works I'll update the OP. BTW, this ROM and my other ROM are TOTALLY different. Thanks for the feedback!
FranMLG said:
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
Click to expand...
Click to collapse
What do you mean by this? "but if you do not pull them, let me know"
And tell me more about Viper4Android, and if it works solid for you on this ROM...then I'll consider adding it. Thanks!
New version, see change log in OP for details.
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
jrkruse said:
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
Click to expand...
Click to collapse
Hi, why you have to flash this - HEROQLTE_USA_VZW.pit on 930t, is it ROM specified? if I do and don't then what are pro and cons?
---------- Post added at 01:36 PM ---------- Previous post was at 01:26 PM ----------
josh2020glacier said:
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
Click to expand...
Click to collapse
since bootloader is locked you can't use TWRP so you have to use Flashfire to install this ROM, as you know flashfire required root so you have to setup the base per OP and then root the base then install the ROM and then root it again, read the first page I don't think you will get a instructions more detailed then his
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Alkan3 said:
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Click to expand...
Click to collapse
Nauseating rainbow? LOL. Sorry. This is much more of a general question though, that wouldn't exactly pertain to this ROM specifically. And given I don't have an answer, I'd try searching BootAnimation How-Tos to get this customized. The ONLY thing I did regarding this was replaced the existing files with the rainbow ones. That's it. Apologies in advance.
Just discovered an issue: RCS (Rich Communication Services / Chat) texts don't show up in Android Messages app. See "Known Issues" in OP for a solution. BTW I posted a new ROM version a few days back that allows many choices in Aroma Installer. Make sure to pick Samsung Messages (instead of Google), so you get RCS chat text messages!
So, I was going through and removing bloat from my phone and was trying to remove the Samsung Contacts app through `adb`, but apparently I removed the wrong thing and now the Phone, Messages, and Contacts app are crashing every time I try to open them. I removed "package:/system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk=com.samsung.android.providers.contacts" which is apparently a core service. I'm wondering if anyone might know how I could reinstall that APK?
install this apk should solve the problem
If worse comes to worse a factory reset will.
A lot of the bloatware is useful. I prefer to use a package disabler as I can easily toggle them on or off as needed real time.
rtd4 said:
install this apk should solve the problem
Click to expand...
Click to collapse
It sat for a minute trying to install and then came up with, "App not installed" and says that every time I retry.
Trying install via adb I get: "
Performing Streamed Install
adb: failed to install /home/mhicks/Downloads/SamsungContactsProvider.apk: Failure [INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.samsung.android.providers.contacts attempting to redeclare permission android.permission.SEND_CALL_LOG_CHANGE already owned by com.android.providers.contacts]"
Hmmm, perhaps I should remove Google Contacts first...
Okay, that helped, but now I'm getting: "
Performing Streamed Install
adb: failed to install /home/mhicks/Downloads/SamsungContactsProvider.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]"
I thought deleting the "com.samsung.android.providers.contacts" might solve the problem, but trying gave me: "
./adb -d uninstall com.samsung.android.providers.contacts
Failure [DELETE_FAILED_INTERNAL_ERROR]"
darkfrog26 said:
It sat for a minute trying to install and then came up with, "App not installed" and says that every time I retry.
Click to expand...
Click to collapse
try these commands on pc
adb shell cmd package install-existing com.samsung.android.providers.contacts
adb shell pm install -r --user 0 /system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk
The first command returns: "Package com.samsung.android.providers.contacts installed for user: 0", but the second command returns: "Failure [-3001: INSTALL_FAILED_REJECTED_BY_BUILDTYPE]"
If you have deleted the apk with root you just have to paste it again in the folder /system/priv-app/SamsungContactsProvider
@rtd4, unfortunately, this device isn't rooted.
darkfrog26 said:
@rtd4, unfortunately, this device isn't rooted.
Click to expand...
Click to collapse
It is somewhat complicated to recover the device without wipe in the past I had these problems, it was solved with a higher version of the application
@rtd4, I suppose it's time for a wipe... Thanks for trying to help me.
If you had made a copy of all your apps including system apks with ApkExport you could now use that copy to restore it.
Now before you factory reset make a copy of your installed apps and any system updates then save it on the PC or SD card. After the reload you won't need Playstore. It speeds things up a lot...
APK Export (Backup & Share) - Apps on Google Play
Manage and extract your apps.
play.google.com
@blackhawk, thanks for the tip. Right now, I'm trying to set up a Telegram account so I can root my phone (US version) if I'm going to go through the trouble of wiping. Unfortunately, Telegram's SMS verification appears to be broken or at least doesn't like Mint Mobile... Fun day.
darkfrog26 said:
@blackhawk, thanks for the tip. Right now, I'm trying to set up a Telegram account so I can root my phone (US version) if I'm going to go through the trouble of wiping. Unfortunately, Telegram's SMS verification appears to be broken or at least doesn't like Mint Mobile... Fun day.
Click to expand...
Click to collapse
You're welcome.
You really don't need to root.
Consider the possible consequences carefully.
Package Disabler will easily block apks you don't want running.
Well, it would appear it's moot anyway since I'm at Baseband v4 and only v1 can be rooted apparently...
darkfrog26 said:
Well, it would appear it's moot anyway since I'm at Baseband v4 and only v1 can be rooted apparently...
Click to expand...
Click to collapse
This is the one I use:
Home - Package Disabler
The only NON-root solution that let’s you disable any unwanted packages that come pre-installed / installed with your phone / tablet.
www.packagedisabler.com
It has an interactive widget that allows you to toggle selected entries on/off. It runs even in Safe mode so be careful what you disable. I've never had to do a factory reset because of it but the potential is there.
Unfortunately it no longer disables Google play Services but will disable all carrier bloatware including OTA updates.
darkfrog26 said:
@rtd4, unfortunately, this device isn't rooted.
Click to expand...
Click to collapse
Then how come you have removed apk from system?
In case you have used command like
pm disable packageName . Then try pm enable packageName
Or
If you have used
pm hide packageName then try
pm unhide packageName
darkfrog26 said:
So, I was going through and removing bloat from my phone and was trying to remove the Samsung Contacts app through `adb`, but apparently I removed the wrong thing and now the Phone, Messages, and Contacts app are crashing every time I try to open them. I removed "package:/system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk=com.samsung.android.providers.contacts" which is apparently a core service. I'm wondering if anyone might know how I could reinstall that APK?
Click to expand...
Click to collapse
Next time use this, so you don't make mistakes:
[TOOL] ADB AppControl 1.8.0 🚀 Ultimate App Manager & Debloat Tool + Tweaks
ADB AppControl 🚀 Root is not required. Works with any Android device. Can do almost everything you dreamed about with applications. ADB AppControl - the desktop program, that will allow you to easily manage applications on your android device...
forum.xda-developers.com