Database Develop

[ROM][NANDROID-BACKUP] minusculeShield 1.0

minusculeShield 1.0
So after some time, I decided that the 4.3 update is worth doing slight modifications, even without the native Shield Services and PC Streaming able to be done remotely. I have gotten used to using Limelight anyways, so I decided to update my basic modified stock Shield ROM
First, I updated to the latest OTA 68, then went from there, the features are as follows:
- Two versions of the ROM, one with OTA and one without
- Includes a alternative Calculator (RealCalc), Zeam Launcher, Adblock, Xposed Framework (Along with an Xposed Module for adding a Play Store link to App info, and GravityBox for various system tweaks), MX Player, and ES File Explorer
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.3 Minimal Gapps
- Koush's Superuser/Superuser Binaries pre-installed
Same installation process as 0.5, excluding need to select Advanced Restore, you can restore like a normal Nandroid without specifying partitions
As always, make sure you wipe System, Data, Cache, and Dalvik before installing
If you have problems with the OTA-exempt version trying to OTA, if it prompts you, it will do it once, and once you "apply" the update (which it will never actually apply) the notification will go away
minusculeShield 0.5[Nandroid-Backup]
So, this is not really a ROM, but a Nandroid backup of my system without any partition but "/system."
This is almost as stripped down as the stock Shield ROM you can get. I have removed all but literally the most essential apps, and also removed the OTA functionality.
The idea for making this was that I couldn't stream remotely anymore since OTA 63, which I promptly set out to fix. I soon realized it was a problem with the Android side of things, as using it on 4.1.2 or 4.2.2 with their respective apps for that release seemed to work fine. OTA 63 (and 64, which is basically the same release, just for those who couldn't install 63) made the local streaming much less productive, as I immediately noticed lagspikes and a load of other problems, which I had never encountered before.
So, in a basic sense, this backup after installed, keeps the ability to stream remotely without troubles of performance or re-connection problems, uses a much more lightweight version of Gapps (Slimrom's version to be exact). It is based on agrabren's TweakerROM 1.1.0, which is a 4.2.2 base, and uses the original TegraZone Dashboard. It again removes OTA, so updating is not an option.
So, when you do install this backup, your internal "/sdcard" storage should no longer need the "nvidia" and "shield" folder, and you can delete those. They will most likely be recreated by some Shield services.
So on to installing and basic rundown in-case you past the above message and just want a bulleted list:
Installation:
Assumes the following:
1. Unlocked Bootloader
2. CWM installed
Installation procedure:
1. Download attached ZIP, extract to your internal SD card ("/sdcard") using the folder structure of "/sdcard/clockworkmod/backup/<extract contents of ZIP here>"
2. Boot into CWM and select backup and restore
3. Choose advanced restore
4. Choose minisculeShield, then "system"
5. Factory reset, wipe cache, data, and dalvik
6. Reboot and enjoy
Information on changes to original 4.2.2 ROM and other info:
- Removes OTA system
- Improves performance of streaming using original Dashboard, Shield Services, and Shield PC Streaming applications
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.2.2 Build 8 version
- Koush's Superuser/Superuser Binaries pre-installed
Download:
Version 0.5
Version 1.0 (OTA Enabled)
Version 1.0 (OTA Removed)

This is great. Will give this a shot today or tomorrow. Thanks!

themichael said:
This is great. Will give this a shot today or tomorrow. Thanks!
Click to expand...
Click to collapse
I'm glad, I thought people would be trampling each other to get a hold of some sort of fix to the remote streaming issue. I guess not. I know I was SUPER disappointed by the latest update for that exact reason.
Let me know if you have any problems, questions, or concerns. I am very new here, but I have been working with Android for almost as long as it came into existence. I started with Android 2.1, so I have learned a lot. I'm also a Unix (mainly the Linux variety) guy, so that goes hand in hand with Android.

I still get notification prompts for ota.

themichael said:
I still get notification prompts for ota.
Click to expand...
Click to collapse
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such

jarjarfinks said:
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
Click to expand...
Click to collapse
Seemed to work. I'll let you know if anything changes.

same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can

milk070 said:
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
Click to expand...
Click to collapse
Is it me, or does the new GFE render the PC running it as "Busy" regardless of the version of the Android side? It was working prior to the GFE update 1.7.1.0, I just had to use the version of the PC Streaming, Dashboard, and Nvidia Shield Services apps in this Nandroid. It seems Nvidia has found a way to render it "Busy" the same problem I had before, no matter what ROM you use
Please test, and let me know, as I will have to find another way

Got Semi-Root-- Is Anyone Still Full-Rooted?

Dear forum,
Long time no talk! I have been able to get "root" for our phones on G925VVRU4BOG7, which anyone can downgrade to. The catch is that even with /system mounted as rw, I am unable to write to it directly through most conventional means. (I can write to /data, though, which means i can patch dalvik-cache, which means my mods are coming ) However, I am able to still write to it using another, more complicated way (I can go into more detail for those interested), as a whole. Here's where you come in-- is anyone still full-rooted? If so, please message me as soon as possible! I may be able to have users who are on newer builds downgrade to older builds and get su properly installed, then manually upgrade back up to the later builds again!
If you are rooted still, all i'm going to have you do is perform this command:
Code:
su
dd if=/dev/block/platform/15570000.ufs/by-name/SYSTEM bs=4096 of=/sdcard/system.img
Then send me that system.img file on your sdcard! It'll be pretty big, so you can zip it or .7z (7-zip), whatever you'd like to do.
I will also need what build you are on. You can just send me your Build number within "Settings->About phone".
First one who does it gets credits on the official release thread i'll make, when I get a procedure down that people can follow!
Thanks!
-Trailblazer101

i have an s6 edge on 5.0.2 rooted. Would that be of help?

Did you get the system.img file? I really wish I could help you. I have this phone on 6.0.1 and stuck without root, but the thing is I really need the root because I bought it used, worked fine the first few days, then didn't get any signal (turns out that it was reported as stolen and of course the IMEI got blacklisted; I tried to contact the seller but he was gone, and his ebay account deleted, so basicly I'm stucked with a ' 5.1" tablet' . I got scammed :/ )
I would be very grateful if you could explain how did you get root on G925VVRU4BOG7 . I know that you want the file mentioned for creating some kind of universal root for the phone, but right now I'm kind of desperate and need root as soon as possible to fix my IMEI issue and I would follow your steps if you made a tutorial.
Thank you very much!

trailblazer101 said:
Dear forum,
Long time no talk! I have been able to get "root" for our phones on G925VVRU4BOG7, which anyone can downgrade to. The catch is that even with /system mounted as rw, I am unable to write to it directly through most conventional means. (I can write to /data, though, which means i can patch dalvik-cache, which means my mods are coming ) However, I am able to still write to it using another, more complicated way (I can go into more detail for those interested), as a whole. Here's where you come in-- is anyone still full-rooted? If so, please message me as soon as possible! I may be able to have users who are on newer builds downgrade to older builds and get su properly installed, then manually upgrade back up to the later builds again!
If you are rooted still, all i'm going to have you do is perform this command:
Code:
su
dd if=/dev/block/platform/15570000.ufs/by-name/SYSTEM bs=4096 of=/sdcard/system.img
Then send me that system.img file on your sdcard! It'll be pretty big, so you can zip it or .7z (7-zip), whatever you'd like to do.
I will also need what build you are on. You can just send me your Build number within "Settings->About phone".
First one who does it gets credits on the official release thread i'll make, when I get a procedure down that people can follow!
Thanks!
-Trailblazer101
Click to expand...
Click to collapse
I am currently running on A0E2 using your rooted rom for this phone. It runs great....except I tried flashing xposed framework using Flashfire and it of course failed...due to the fact that xposed only works on 5.1.1 or above...sucks we are in such a catch 22 with our devices...although I'm happy because I am still rooted.. Anyway...I set up ADB and entered that command you posted and it worked...I just don't know where the storage location of the system.img file is for me to transfer to my PC, 7zip, and send to you. Any help would be excellent....as I desperately want to run xposed framework on my device....but am stuck on 5.0.2

r0ckinb0i said:
I am currently running on A0E2 using your rooted rom for this phone. It runs great....except I tried flashing xposed framework using Flashfire and it of course failed...due to the fact that xposed only works on 5.1.1 or above...sucks we are in such a catch 22 with our devices...although I'm happy because I am still rooted.. Anyway...I set up ADB and entered that command you posted and it worked...I just don't know where the storage location of the system.img file is for me to transfer to my PC, 7zip, and send to you. Any help would be excellent....as I desperately want to run xposed framework on my device....but am stuck on 5.0.2
Click to expand...
Click to collapse
Looking at the last part of the command and if it ran successfully, it should be in /sdcard. Did you ever find it?

gabes100 said:
Looking at the last part of the command and if it ran successfully, it should be in /sdcard. Did you ever find it?
Click to expand...
Click to collapse
Thank you I found it...I'm new to command prompt although I am learning quickly. I found it. I just need to load it onto my computer and compress it so I can send it to Trailblazer. I will do that tomorrow night when I get back home.

I have the img on my computer. It is 4.3G. How do I get it to Trailblazer? Google Drive? EDIT: it is 4.58GB. I am uploading now to google drive, it will an hour

Hi Trailblazer,
Here is a link to system.img:
https :// drive google com / open?id=0B-j3XfGrnj9PbUdwaml5eERvbFU
I am too new to post links the correct way.

Are there any updates on this topic? When I first saw this thread last week, It got me thinking about what a Tethered Root (Temporary/Semi - Root) would still be capable of doing for those of us still on Official Firmware in this day and age.
And really it occurred to me at that moment, that if we could just attain a Root Shell even if it was only for 60 seconds to five minutes, that would be sufficient to get enough root information off of the phone and into a PC editable format.
I ask, because I am in the process of forming a method for the G925V 6.0.1 [PI2] Build. The problem I'm pretty sure I'm going to run into sooner or later in my experiments/research, is the fact that I am one of the few who have the 64GB Verizon S6 Edge. Technically speaking, my device refers to itself in Download/ODIN mode as a SM-G925VZKE model. This also means that my Stock .PIT file is going to be very different than most people's, also meaning my FSTAB configuration probably will be different.
Because there shouldn't be a reason I can't at least get a temporary Root Shell very soon.

So whats up with this? My wife has 6.0.1 on Verizon and I have international much better choice. Will we have root on this phone?

If you are currently on 6.0.1 on your Verizon device. It would serve you well for the time being to disable Automatic Security Updates.
Settings > Lock Screen and Security > Other Security Settings > Security Policy Updates
Turn OFF Automatic Updates, and Turn OFF Wi-Fi Only.
If you leave these on, any potential root option will be patched by Samsung/Google before you know it exists. Disable it for now so you can find an exploit for the build the device is on.

UPDATE:
So apparantly, I've had a rooted 6.0.1 PI2 device persistent through factory resets for over a week, but didn't realize just how much was achieved on my device! According to diagnostics.
I'm already started on writing up the combination of methods that the OP was walking into. Turns out it works up to the September patch too.
But lucky me and not you this time. I got my device essentially decommissioned because I ran my code too soon. But in the sweetest possible way after being so pissed when my tech coach said my warranty was void.
By the end of tomorrow night I should have a thread.

Anyone still working on this?

d0lph said:
Anyone still working on this?
Click to expand...
Click to collapse
Yes. Using the dirtycow vulnerability we've managed to get an arm64 version running that will indeed allow a root console on MM builds.
The last thing standing in the way, for at least a tethered root, is for someone to help me convert the script from the flashable zip version of the SuperSu installer into basically a batch script. Because the how-to guide ChainFire wrote in comments inside his installer script is kind of hard to read because it covers all the different versions of android in a tiny block of text and not every device sets up the same SELinux environment.
Not to mention, if I could get SuperSU to try and install itself as a System Application, it would probably work with what I have already. But for some reason I CANNOT find a single guide anywhere on how to perform a "System" Install of SuperSU, everyone wants to use the "Systemless" version, which is NOT going to work I believe.
We can manage booting the device in the event of DM-Verity Failure, when that happens with the 5.1.1 OG ENG Kernel, we can indeed mount "/system" as read/write, and we can indeed change the contents of the System partition that persist through a reboot.
I just need help setting Perms & Contexts. Because at one point in time, I DID actually manage to get SuperSU to give me a root shell instead of a user shell, but only on the ADB Command Line. In that test I could not get an application to start from the launcher and have Root Permissions.

Delgoth said:
Yes. Using the dirtycow vulnerability we've managed to get an arm64 version running that will indeed allow a root console on MM builds.
The last thing standing in the way, for at least a tethered root, is for someone to help me convert the script from the flashable zip version of the SuperSu installer into basically a batch script. Because the how-to guide ChainFire wrote in comments inside his installer script is kind of hard to read because it covers all the different versions of android in a tiny block of text and not every device sets up the same SELinux environment.
Not to mention, if I could get SuperSU to try and install itself as a System Application, it would probably work with what I have already. But for some reason I CANNOT find a single guide anywhere on how to perform a "System" Install of SuperSU, everyone wants to use the "Systemless" version, which is NOT going to work I believe.
We can manage booting the device in the event of DM-Verity Failure, when that happens with the 5.1.1 OG ENG Kernel, we can indeed mount "/system" as read/write, and we can indeed change the contents of the System partition that persist through a reboot.
I just need help setting Perms & Contexts. Because at one point in time, I DID actually manage to get SuperSU to give me a root shell instead of a user shell, but only on the ADB Command Line. In that test I could not get an application to start from the launcher and have Root Permissions.
Click to expand...
Click to collapse
Thank you for taking the time to still work on this. Subscribed. Following this to the T.

Rand0lph said:
Thank you for taking the time to still work on this. Subscribed. Following this to the T.
Click to expand...
Click to collapse
If you want to follow the complete story of what I just mentioned please follow and contribute to this thread: Injecting Root & Setting SELinux - End Stages?
This is the thread that contains the Greyhat Root console, first designed for the AT&T Galaxy Note 5. But that device uses the same Exynos7420 Mainboard as the Galaxy S6 Edge, so the project is still compatible.
I haven't kept the OP maintained as I should yes. But it is actually worth it to read that whole thread as @droidvoider went out of his way explaining some of his methods. I have a bit of R&D that isn't posted in that thread as well, if you can read up on the project. I'd be more than happy to share what I know with anyone wanting to help as long as they can catch up with what we have accomplished so far.
Look at some of the other threads I've started as well for the initial methods.

Delgoth said:
If you want to follow the complete story of what I just mentioned please follow and contribute to this thread: Injecting Root & Setting SELinux - End Stages?
This is the thread that contains the Greyhat Root console, first designed for the AT&T Galaxy Note 5. But that device uses the same Exynos7420 Mainboard as the Galaxy S6 Edge, so the project is still compatible.
I haven't kept the OP maintained as I should yes. But it is actually worth it to read that whole thread as @droidvoider went out of his way explaining some of his methods. I have a bit of R&D that isn't posted in that thread as well, if you can read up on the project. I'd be more than happy to share what I know with anyone wanting to help as long as they can catch up with what we have accomplished so far.
Look at some of the other threads I've started as well for the initial methods.
Click to expand...
Click to collapse
Sorry, I didn't even acknowledge this is for the EDGE S6. I have a regular Verizon S6.

Rand0lph said:
Sorry, I didn't even acknowledge this is for the EDGE S6. I have a regular Verizon S6.
Click to expand...
Click to collapse
I don't really think that matters as much for the thread I referred to.
I tested the Greyhat Root Console on my S7 Edge, and it worked as well using the September build.
The S6 Line plus the Note 5, all use the same System on a Chip.
If anything, there may be just a couple tweaks to make when compiling it using the NDK.

[TOOL][ROM] UpdateEngine UI -- Flash Android O beta without wiping data

I highly recommend @JamFlux's work instead. Currently, this has got way more complicated than it should be (in the past 24 hours, only 40% users have managed to accurately follow the procedure, and even less for the latest beta). However, I will continue working on this project in order to make it compatible across more devices. The app is now open-source and you can visit the GitHub repo here. Thanks for using UpdateEngine Interface and I hope to see you folks again soon.
I've created the UpdateEngine Interface, a tool to install OTAs that haven't been assigned to your device. It talks to Android's update_engine binary to flash the block-based updates just the way the original updater does, ensuring that your data is preserved and your system partition's signature doesn't change.
TLDR: It allows you to install Oreo without using someone else's TWRP backup or losing data.
Now has the latest build (20th December)
Installation:
Install Magisk
Install the attached Magisk module (named UpdateEngine_1.2.zip) and reboot
Open the newly installed UpdateEngine app and press start
Wait for the installation to complete and restart your device to boot into Android O
If you wish to update to the latest beta, use Magisk to install UpdateEngine_1.3.zip afterwards
Note: If you're a FlashFire user, please uninstall it and reboot before continuing.
Note #2: You must install Oreo via v1.2 before installing the latest beta (via v1.3).
XDA:DevDB Information
UpdateEngine User Interface, Device Specific App for the Xiaomi Mi A1
Contributors
ur0
Version Information
Status: Stable
Current Stable Version: 1.1
Created 2017-12-19
Last Updated 2017-12-19

Does it need a virgin /system?

I love you! thats what we need.

konradit said:
Does it need a virgin /system?
Click to expand...
Click to collapse
Yeah. It requires that the system hasn't been modified since the December OTA (just like the original updater) since the updates are applied block-by-block.

Which beta does it have currently? THE first one or newer?

jazzthe#1 said:
Which beta does it have currently? THE first one or newer?
Click to expand...
Click to collapse
I only have the first build, since that's the only one that people captured (I'm not in the beta, so I can't get the newer ones myself).

Okay

@ur0 wow, thats awesome, thank you bro)

This looks interesting, although I'm waiting for Xposed Oreo. A question though, I've heard the leaked Oreo build is rooted, does this method install untouched boot.img?

@Filip013 yes, this installs the untouched boot.img.
@rostifaner and @TerQQ, You're welcome!

so this tool can install android O ota beta without twrp ? and without losing data ? and how to install this tool ? sorry for many question .

is possible to add feature "choose ota file from device" or something similar ?

TerQQ said:
is possible to add feature "choose ota file from device" or something similar ?
Click to expand...
Click to collapse
I'm looking into adding this -- the only problem is that it also requires a bit of metadata (which is inconvenient to type manually). I'll look into defining a format which the app can read directly.

It doesn't seem to be working for me. When I press Start, it opens FlashFire app & nothing happens. Even if I come back to this app, there will two buttons Pause & Stop, but nothing will be happening. Also can you please make it open source?

ghpranav said:
It doesn't seem to be working for me. When I press Start, it opens FlashFire app & nothing happens. Even if I come back to this app, there will two buttons Pause & Stop, but nothing will be happening. Also can you please make it open source?
Click to expand...
Click to collapse
That's weird -- can you please post the logcat outputs after this happens (maybe after restarting and trying again)?
I'm sure that it's something with flashfire since the app doesn't use it or depend on it.
I'm definitely going to open-source this after I fix a few hacks I made to get the initial version working.

Any chance of posting your work to github? would be interesting to see the source if possible

How to install?
How to install magisk and update engine. Will we have to root and flash these file from TWRP? Please give the tutorial in detail.

for me its working great.

I don't understand what purpose this tool serves. You're saying that using this we can install the oreo update without someone's twrp bakup?

I keep getting a crash when i press start, then the app won't open again until I reboot and even then no download... am i missing something?
I have magisk 15.6 and i disabled all my other modules just in case...
EDIT:
12-19 11:32:16.564 3121-3267/? E/DatabaseUtils: Writing exception to parcel
java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/fs_id from pid=9022, uid=10111 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission()
at android.content.ContentProvider.enforceReadPermissionInner(ContentProvider.java:608)
at android.content.ContentProvider$Transport.enforceReadPermission(ContentProvider.java:483)
at android.content.ContentProvider$Transport.query(ContentProvider.java:212)
at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112)
at android.os.Binder.execTransact(Binder.java:565)
I think you need to add the read/write premission to your app. not sure how its working for others
EDIT 2: Selinux is denying your app.. had to use a selinux disabler app to get it not to crash... might want to look into that..
EDIT 3: Not working... Nothing happens when i click start...

[GUIDE][GLOBAL]Flyme 7 update,Disable system apps,Enable night mode,Weather fix

First of all i highly recommend you update your phone to latest version of Flyme as of day i write this guide newest stable version is 7.0.0.0G. It brings various bug fixes as well as security update and new functions. It fixed the weather problem too when it would not appear on secondary screen. This is my experience based on the standard model with Helio P25 chip.
JUST IN CASE BACKUP ALL OF YOUR DATA FIRST
Grab it at http://www.flymeos.com/firmwarelist?modelId=88&type=1
Installation is pretty straightforward:
-switch off your phone
-now press volume up button and power button at same time, then release power button when meizu logo appears
-phone now will enter update mode, connect it to pc and it should show up as removable drive named recovery, copy the update.zip over it
-once copied tap the start button to begin. the process itself and first boot will take a while
-when done and phone boots up just log in to your accounts and set up everything as normal or whatever
ta-dah ! you should be running latest software now.
Next problem i've encountered was big number of unwanted apps and you will need working ADB for that. I've always used custom roms which did not contain bloatware. Now im giving you one of the way of disabling them (not permanent removal).
For this to be done you need to activate developer mode and usb debugging, simply go to settings->about phone->and now tap on your build number several times
After you activate it it will be available in accessibility options under developer settings. just check the usb debugging and you're good to go
DISCLAIMER: dont ask me about adb drivers for your phone, since i had issues installing them under win 10 x64 build 1803 i thought "aw f*ck it" and just did it on linux where everything worked out of the box.
The application you will need is called Ice Box (you will find it here https://play.google.com/store/apps/details?id=com.catchingnow.icebox&hl=en_US) and install it.
After you install the app its necessary that you remove ALL of your accounts including your Google account. We will need to grant the app device owner permission. Also if multi-user or guest mode has been set on your device, it need to be closed or deleted.
When you have that done just type in your command line , terminal or whatever "adb shell dpm set-device-owner com.catchingnow.icebox/.receiver.DPMReceiver "
Now reboot and add your accounts back, and disable/freeze uwanted apps.
Last - the night mode. As its no longer availble in Flyme 7 if you want to use it you need to manually bring it back by installing Flyme Lab and enabling it trough quickshortcutmanager. Install both apps, then open quickshortcutmanager and search for Flyme Lab. expand it and choose the activity named com.meizu.flymelab/com.meizu.flymelab.component.nightmode.NightModeSettingsActivity .Create shortcut and open it. You should be able to enter the night mode.

Nice guides, thanks.
It's also nice that Flyme 7 still supports rooting, therefore I'm using Titanium Backup to freeze unwanted apps. I bought it when I was using another phone so, for me, it's still worth it. Altough, for uninstalling system apps I'm using separate ADB commands for each app.

cris2d2 said:
Nice guides, thanks.
It's also nice that Flyme 7 still supports rooting, therefore I'm using Titanium Backup to freeze unwanted apps. I bought it when I was using another phone so, for me, it's still worth it. Altough, for uninstalling system apps I'm using separate ADB commands for each app.
Click to expand...
Click to collapse
Its first time for me writing a guide so good word is always appreciated. What im trying to show here is the no root way of getting rid of apps for ppl like me who dont want to root their phone. As i bought it literally two days ago and i dont want to mess with it too much and loose warranty or/and OTA updates.
I also been considering posting a root guide once i tried it myself to confirm it working.

non.verbal said:
Its first time for me writing a guide so good word is always appreciated. What im trying to show here is the no root way of getting rid of apps for ppl like me who dont want to root their phone. As i bought it literally two days ago and i dont want to mess with it too much and loose warranty or/and OTA updates.
I also been considering posting a root guide once i tried it myself to confirm it working.
Click to expand...
Click to collapse
Well, before I discovered a rooting method for Flyme 7, I used to uninstall apps by using ADB commands. So, yes, it is possible to remove unwanted system apps without root. But now, after rooting Flyme 7, I'm only using Titanium Backup to freeze unwanted system apps, not removing them.
As far as I know, rooting Meizu phones by the official method (from Settings) does not lead to losing warranty. Only OTA updates are lost, but this is not important, at least to me, because I can always check Flyme website for new updates and, if I want to update, I just download the file and flash it through standard Flyme recovery. There is no need, for me, to maintain OTA capability. Anyhow, Flyme updates are slow to non-existent, so we can't really complain about losing an update.

Thank you all. I'm happy with this phone at all, but software has few shortcomings and design flaws, in my opinion. Especially related to the integration with "flyme login" and Touchpal. This last one is very annoying because although I try to stop it, at each software update it comes back, more annoying than ever. So, I have some questions: which is the adb command to stop and freeze bloatware without rooting? Which is the official way to root the phone? Once rooted, is it possible to revert to the unrooted state? Some apps, actually, do not work on rooted phones. Thanks

pask876 said:
Thank you all. I'm happy with this phone at all, but software has few shortcomings and design flaws, in my opinion. Especially related to the integration with "flyme login" and Touchpal. This last one is very annoying because although I try to stop it, at each software update it comes back, more annoying than ever. So, I have some questions: which is the adb command to stop and freeze bloatware without rooting? Which is the official way to root the phone? Once rooted, is it possible to revert to the unrooted state? Some apps, actually, do not work on rooted phones. Thanks
Click to expand...
Click to collapse
I can't freeze (or disable) apps with ADB commands, only uninstall.
You need [email protected], App Inspector or similar (to find exact name of package for an app) and these commands:
adb devices
adb shell
pm uninstall -k --user 0 name_of_package
Example, for gmail:
pm uninstall -k --user 0 com.google.android.gm
Regarding rooting, as far as I know, the only method that works on Pro 7 / Pro 7 Plus is also supported by Meizu (but it breaks OTA updates).
The method is described in this video (in russian) but it's quite easy.
If you want to remove root (or if root breaks functionality) you have to reflash the same ROM from Recovery (without wipe).

Any air update coming soon? Or manually installation single option?

[ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]

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!