Database Develop

[Toolkit]S5 KoolKit V1.0.1 RC2 06/25/2014[Toolkit] - AT&T Samsung Galaxy S 5

S5 Android KoolKit V1.0.1 RC2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remove Bloatware based on custom text file
Enable init.d support​
Apply several performance build.prop performance enhancements​
Instructions:
Extract the zip file to your PC, Make sure your device is connected via USB and that you have the appropriate USB drivers installed.For Bloatware removal look in the "bloat" folder and customize the nobloat.txt file to your needs (it has a set of default apks and odex files to remove you can modifiy this however you like (the files for knox removal are listed but are commented out in order to enable them just remove "#" from the beginning of the line (However, I have not tested the knox removal completely so use caution, i would suggest start by removing only those apks and odex files that exist in the system/priv-app folder and then go from there). init.d support is built into the code itself and needs no editing. the performance tweaks are a set of midrange enhancements for picture and video quality as well as connectivity and battery enhancement (these are hard coded and in the final release I will make them user customizable. More detailed instructions are displayed in the initial readme file displayed when starting up the application.
Click to expand...
Click to collapse
I recomend installing busybox from the playstore prior to running the tookit some components that are pushed to the device make use of busybox.​
Changelog
V1.0.1 RC2
Removes annoying AT&T Startup sound
Fixed busybox install
tested and confirmed Samsung Knox removal works
enabled knox removal by default (comment out lines in nobloat.txt if you want to keep it)
removed some more bloatware
Can now edit the nobloat.txt from within the toolkit
Can now edit build.prop additions from within the toolkit
Can now edit sysctl.conf settings from within the toolkit
cleaned up more code
V1.0.1 RC1
Added CSC customizations (enable remove default bookmarks) Thanks to [email protected]
Added remote application install
Added busybox install
Cleaned up some more code
Fixed system read/write access
Fixed missing edits in nobloat.txt
Fixed custom bootanimation
Added initial README
Converted build.prop edits to user customizable state
Added proper device detection (displayed under title in application)
Added checks for customizations and allow for updates if already applied
V1.0.0 Beta
init.d support
performance enhancements
bloatware removal
reboot options (reboot, recovery, download)
device model detected on startup
Much more to come as I get a chance.
Bugs
odex file names missing from nobloat.txt defaults - (fixed in beta 1.0.0.1)
custom bootanimation - (fixed in beta 1.0.0.1)
system read/write access ocasionally fails - (fixed in beta 1.0.0.1)
AT&T Startup sound still active with custom bootanimation (Fixed in RC2)
busybox install fails (Fixed in RC2)
DOWNLOAD S5 KoolKit V1.0.1 RC2​
Attached to this post is an excel spreadsheet that shows all of the apps that are safe to disable/delete not all of these are included by default in the nobloat.txt, the file also includes all of the custom USSD Codes and the codes verified to work on our device.
Thanks
@pcidiot for the csc edits for default bookmarks
Google (For Android of course)
Samsung (For the Galaxy S5)
AT&T (For putting us thru a living H$!! for the last two months)
And mostly thanks @geohot for providing us with root, because lets face it without root This app would be meaningless!

Upcoming changes
This is a short list of the upcoming changes to KoolKit
Minor re-write to allow users more control over build.prop edits
fixed custom bootanimation issues
fixed system RW issues
some small changes to hopefully make this Android Version independent (work for any Device any OS Ver. )
!!!DO NOT ENABLE KNOX REMOVAL IN V1.0.1 RC1 IT WILL SOFT BRICK YOUR DEVICE!!!
!!!PLEASE WAIT FOR RC2 TO BE RELEASED BEFORE USING KNOX REMOVAL!!!​
Removes annoying AT&T Startup sound
Fixed busybox install
tested and confirmed Samsung Knox removal works
enabled knox removal by default (comment out lines in nobloat.txt if you want to keep it)
removed some more bloatware
Can now edit the nobloat.txt from within the toolkit
Can now edit build.prop additions from within the toolkit
cleaned up more code
I ran this through on a clean install of the stock firmware after updating to and3 and rooting with towelroot and had no issues whatsoever.
More as i think of them:laugh:

one more just in case

Think this is okay for the At&t Active s5? Thanks

LuckyColdJohnson said:
Think this is okay for the At&t Active s5? Thanks
Click to expand...
Click to collapse
Should work just fine on the S5 Active since the base hardware is identical, make sure to apply the patch from the attachments as well so that you can enable custom bootanimations.

The zip file doesn't contain a Bloat folder, only a .exe and a bin folder with bootanimatoin file with no extension.
EDIT: Figured it out. the Tool is a download in the OP, the patch is what is attached along with the XLSX. Sorry, missed the link in the post.

michaelpule said:
The zip file doesn't contain a Bloat folder, only a .exe and a bin folder with bootanimatoin file with no extension.
EDIT: Figured it out. the Tool is a download in the OP, the patch is what is attached along with the XLSX. Sorry, missed the link in the post.
Click to expand...
Click to collapse
that's the patch file download the main toolkit first (the link is right above the note about the patch)

michaelpule said:
The zip file doesn't contain a Bloat folder, only a .exe and a bin folder with bootanimatoin file with no extension.
EDIT: Figured it out. the Tool is a download in the OP, the patch is what is attached along with the XLSX. Sorry, missed the link in the post.
Click to expand...
Click to collapse
remember this is a beta so i may be throwing patches at it frequently so check back once in a while

This look super kool tool kit Sir.....I managed to installed Safestrap ... I'm away from my Laptop ATM so I've to wait till I can goes to recovery or not just incase....but at least is good start.
☆Swyped From S-Five SS Edition☆

Oh shnit, did he say Safestrap!? That's a move in the right direction. Hope it's working for ya man!
Sent from my "ROOTED" SAMSUNG-SM-G900A using XDA Premium 4 mobile app

ted77usa said:
This look super kool tool kit Sir.....I managed to installed Safestrap ... I'm away from my Laptop ATM so I've to wait till I can goes to recovery or not just incase....but at least is good start.
☆Swyped From S-Five SS Edition☆
Click to expand...
Click to collapse
well if we get safestrap recovery I have a ROM just waiting to be posted :good::good::good:

cstayton said:
S5 Android KoolKit V1.0.0 Beta
Remove Bloatware based on custom text file
Enable init.d support​
Apply several performance build.prop performance enhancements​
Instructions:
I recomend installing busybox from the playstore prior to running the tookit some components that are pushed to the device make use of busybox.​
I know the screenshot shows the ability to enable custom bootanimation which at this moment is not enabled do to some small glitches yet to be fixed.
Changelog
V1.0.0 Beta
init.d support
performance enhancements
bloatware removal
reboot options (reboot, recovery, download)
device model detected on startup
Much more to come as I get a chance.
Bugs
odex file names missing from nobloat.txt defaults - (fixed in beta 1.0.0.1)
custom bootanimation - (fixed in beta 1.0.0.1)
system read/write access ocasionally fails - (fixed in beta 1.0.0.1)
DOWNLOAD S5 KoolKit V1.0.0 Beta​Attached to this post is a patch that will enable the custom bootanimation portion of the KoolKit v1.0.0 beta, just extract into the kooklit folder and overwrite when prompted.​
Attached to this post is an excel spreadsheet that shows all of the apps that are safe to disable/delete not all of these are included by default in the nobloat.txt, the file also includes all of the custom USSD Codes and the codes verified to work on our device.
Thanks
Google (For Android of course)
Samsung (For the Galaxy S5)
AT&T (For putting us thru a living H$!! for the last two months)
And mostly thanks @geohot for providing us with root, because lets face it without root This app would be meaningless!
Click to expand...
Click to collapse
Just to report my experience, I followed the directions in the OP to a T and used the enable custom boot animation option, it asked me to grant SU access on my phone, which I did, then I rebooted, now my device has no boot animation at all, it just stays on the galaxy s5 powered by android screen the whole time, I can hear the AT&T boot sound go off, but it just stays on that screen until it boots up fully, then it kinda freaks out and blinks back and forth between my lockscreen and my homescreen with flat black backgrounds for about a minute, then goes to the normal lockscreen, is there a way to revert back the changes that this tool makes or a revert to stock option? I also ran the performance tweaks too if that makes a difference.

ted77usa said:
This look super kool tool kit Sir.....I managed to installed Safestrap ... I'm away from my Laptop ATM so I've to wait till I can goes to recovery or not just incase....but at least is good start.
☆Swyped From S-Five SS Edition☆
Click to expand...
Click to collapse
I can almost taste custom roms, nice

For some reason it will not detect my phone, I have the USB debug turned on in Dev mode, Samsung drivers are installed and my PC sees the phone and I can access all the files, but I get an error "Couldn't Detect your device, reconnect and try again. then I get .net framework unhanded exception errors when I close the program. What am I missing or is this something on my end?

zacharyt86 said:
Just to report my experience, I followed the directions in the OP to a T and used the enable custom boot animation option, it asked me to grant SU access on my phone, which I did, then I rebooted, now my device has no boot animation at all, it just stays on the galaxy s5 powered by android screen the whole time, I can hear the AT&T boot sound go off, but it just stays on that screen until it boots up fully, then it kinda freaks out and blinks back and forth between my lockscreen and my homescreen with flat black backgrounds for about a minute, then goes to the normal lockscreen, is there a way to revert back the changes that this tool makes or a revert to stock option? I also ran the performance tweaks too if that makes a difference.
Click to expand...
Click to collapse
download the patch file from the attachments to the first post then do the custom boot animation enable again, without the patch the bootanimation wont run

dunlar said:
For some reason it will not detect my phone, I have the USB debug turned on in Dev mode, Samsung drivers are installed and my PC sees the phone and I can access all the files, but I get an error "Couldn't Detect your device, reconnect and try again. then I get .net framework unhanded exception errors when I close the program. What am I missing or is this something on my end?
Click to expand...
Click to collapse
What version of windows are you running on? make sure you have .net 4.5 installed on your PC (that would explain the .net exception, what is the model of your deviceG900A or is it one of the unlocked variants?

I'm on W7& .net 4.5 is installed I'll uninstall and re-install maybe there is a bad file. This is the G900A.
Updating to .NET 4.5.2 did not help

cstayton said:
download the patch file from the attachments to the first post then do the custom boot animation enable again, without the patch the bootanimation wont run
Click to expand...
Click to collapse
I did that before I did anything, I downloaded the patch first thing. I even deleted the toolkit and redownloaded everything just in case I got a bad download, still the same result. I mean ever thing works fine and my device boots up, just no boot animation and it kinda freaks out for the first minute or so when it boots.

zacharyt86 said:
I did that before I did anything, I downloaded the patch first thing. I even deleted the toolkit and redownloaded everything just in case I got a bad download, still the same result. I mean ever thing works fine and my device boots up, just no boot animation and it kinda freaks out for the first minute or so when it boots.
Click to expand...
Click to collapse
just sent you a PM with a test version let me know if it fixes the bootanimation problem

cstayton said:
just sent you a PM with a test version let me know if it fixes the bootanimation problem
Click to expand...
Click to collapse
Ok no problem, just replace the files just like in the patch right?
EDIT: Nevermind, after extracting I realized it was a whole new package with all the files.
---------- Post added at 09:28 AM ---------- Previous post was at 09:18 AM ----------
cstayton said:
just sent you a PM with a test version let me know if it fixes the bootanimation problem
Click to expand...
Click to collapse
That did the trick, I now have the Nexus-ish boot animation, and as an added bonus the AT&T boot sound is gone also now. Thanks for all the help!

Related

Super SU by CF
SuperSU is the Superuser access management tool of the future
Features include:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Trusts ADB connection
- Always runs in ghost mode
- Wake on prompt
The Pro version additionally offers:
- OTA survival mode (no guarantees)
- Full color-coded command content logging (input/output/error)
- Per-app logging configuration
- Per-app user override
- PIN protection
Who, What Why ? - said by CF
As you may know, I make a lot of apps that use or require root. I also release rooted kernels. I run into a lot of issues with existing Superuser tools. More importantly, a lot of my users run into these issues as well and then email me about it. So I decided to do something about this. Doesn't mean these were problems you have ever seen, or will ever see.
And thus, I have written - pretty much from scratch - SuperSU. I have taken the su binary command line parameter parsing from Superuser, to make sure that is compatible. Aside from that, it is completely rewritten, because how I wanted to do a number of things was incompatible with the existing codebase.
This is not a stab at ChainsDD, or his skills. He has done great work and will no doubt continue to do so, however, I felt the need for some of these changes, and thus made them. This is an early release, so I expect there will be some unforseen issues somewhere.
From now on, all CF-Root and Mobile ODIN Pro (EverRoot) releases will be built around SuperSU.
Please note that SuperSU is not hardened-security-tested or reviewed, and may be exploitable (... as may other solutions ...).
Install :
Flashable Zip v0.93
Market :
Lite
Pro
Note : Pro is key only, you need to install lite version first.
If you install from market, you will have two superuser, remove older one with system appl remover, or any other application can perform same job.
Remember, if you remove older first without installing newer one, you will lose Root n newer won't run.
One more thing market version will be regular application, so hard reset can delete it. So better install with flashable zip, to make it system application.
Source : http://forum.xda-developers.com/showthread.php?t=1538053

Thanks a lot doc. Gonna give it a try.
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Sorry to say but this belongs to General Section.

Nice one, Dr.Ketan.
Perhaps your fine installation instruction could also include this:
"Superuser (the old one) is a system app and should be removed from /system/app/ folder using Root Explorer, ES Eplorer with root permissions, or similar explorer app. Titanium Backup does not show Superuser in its app list, and therefore cannot remove it."
Otherwise you'll be swamped with Titanium questions.

This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..

dr.ketan said:
This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..
Click to expand...
Click to collapse
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...

grgsiocl said:
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...
Click to expand...
Click to collapse
CF says he has fixed that bug in v0.74, and that's the one posted here.

I have no issue with USB debugging ON

Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA

kopitalk said:
Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Newbie question here, (sorry) so you don't just download from the market/play store..... open and it will install on it's own?
Sent From my Two Tin Cans & String Device on The Wookie Network

It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market

dr.ketan said:
It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market
Click to expand...
Click to collapse
Another newbie question... Is there enough of a difference between superuser & supersu for a newbie to risk mucking up their phone?
Thanks!
EDIT : are there instructions as to how to flash with CWM? SORRY!!
Sent From my Two Tin Cans & String Device on The Wookie Network

Superuser v0.75 has been released.
Changelog:
10.03.2012 - v0.75
- Adjustment to OTA survival (better!)
- Slight speedup in Settings
- Fixed native settings update after temp-re-root
- Clear data no longer clears PIN code
- Layout: Prompt: Grant and Deny switch positions (ICS style)
- Layout: AppDetail: Save and Cancel switched positions (ICS style)
- Layout: Added xlarge PIN layout
http://forum.xda-developers.com/attachment.php?attachmentid=940641&d=1331395344
P.S. Dr.Ketan, when I try to download CWM flashable zip from your 1st post I get a 404.

Ya b'coz link replaced by CF with new version
updated now

dr.ketan said:
Ya b'coz link replaced by CF with new version
updated now
Click to expand...
Click to collapse
even mobile Odin is updated with 2.25

Very Slow Boot Up Following Switch to SuperSU Pro
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz

krazman325 said:
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz
Click to expand...
Click to collapse
what you said was true...it slows up booting...but what i did was, in supersu app, i selected grant as default and there is no need for prompt...after that, booting as speed up!

I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Sorry for wasting space in this thread!!! Hopefully, anyone else having similar trouble will see this.
kraz

Thanks Doc!flashing now

krazman325 said:
I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Click to expand...
Click to collapse
Yeah, this is what CF has to say about it in his original thread:
Chainfire said:
PROTIP:
For extra performance, disable notifications. Logging does not impact performance much.
Click to expand...
Click to collapse

I think it would have been better to just link to chainfires thread rather than repost what he posted.

I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!!!
STOCK RELOADED v1 fix 1
Kernel base: stock XXUANC3 (kernel 3.4.0-1131235)
Kernel ramdisk: modded
Features: a few...
Security level: low!
Purpose: giving everyone who loves free exploring of Android secrets and who doesn't consider security as an absolute priority and who wants to put some life in this, indeed, awesome device, a possibility of playing with his device without disturbing restrictions, forced by Samsung, at least until fully-custom kernels, compiled from sources, appear (and that may take some time, as source code available atm seems to be broken, causing all the compiled kernels to stuck at boot screen).
Features working out-of-the-box:
- su binary from SuperSU by Chainfire @ /sbin/su (binary only for scripting purposes! Flash cf-root to use SuperSU app!)
- busybox 1.22.1 binary compiled by Stericson @ /sbin/busybox
- init.d support - just put your favorite scripts into /system/etc/init.d using any file manager and chmod 755 (not 777! it's NOT smart to permit write access for "world" to any system file), chown root:root, they will run on every boot. Well, to be honest, above permissions are given to all the scripts automatically during boot, but it has not yet been tested
- SELinux: Permissive - Samsung's most recent policy of forcing SELinux Enforcing mode by pre-compiling it into a kernel binary part, found in latest KitKat builds since at least a few months, HACKED FOR THE FIRST TIME EVER using innovative method of injecting an information directly into kernel memory space and forcing overwriting potentially-persistent kernel symbol value on-line during boot!)
- unsecure adb access (not tested yet)
- ext4 tweak: 20 sec (instead of stock 5 sec) write commit delay for /data partition (significantly increases IO performance!)
- some further, minor modifications
WARNING!!!
- flashing this WILL undoubtly trip KNOX, avoiding your warranty (which atm cannot be reverted! in any way)
- flashing this WILL cause a warning message of avoided warranty to be displayed on every boot (ofc it disappears right after reverting to stock boot.img)
- flashing this WILL disable some of the very important security features provided with stock firmware!!!! For advanced and experienced users only!!! Use at your own risk!
Known issues:
- AllCast Share mirroring not working (typical for all Samsung devices running not-exactly-stock kernels since S3). WORKING FIX AT POST #16!!!
http://forum.xda-developers.com/showpost.php?p=54516532&postcount=16
Please consider solution from post #3 as not-always-working and depreciated!
Installation:
- compatibile with XXUANC3 firmwares but probably also with other (past and hope future too...) KitKat 4.4.2 Samsung branded firmwares;
- rooting by Chainfire's CF-Root first recommended as it will install SuperSU app in Android (this kernel contains su binary only giving su access without any policy settings!);
- enter download mode and plug the tablet via USB...
- ...select provided file in PDA section (and NOT touch anything except that)...
- ...and flash with Odin in a same way as CF-Root or like anything else...
- enjoy.
DOWNLOAD HERE:
Current version - STOCK RELOADED v1 fix 1
http://www63.zippyshare.com/v/87557346/file.html
FIXED: file name changed so it can be flashed directly by Odin without renaming! Sorry for this silly mistake!
=======
Changelog:
v1 fix1:
- fixed permissive mode due to trivial error;
- delayed init.d execution to a moment AFTER init process set cfq scheduler so it is not overriding mmcblk0 tweaks (if put in init.d) anymore;
- minor code cleanups
v1:
- initial release
- init.d support
- SELinux permissive
- unsecure ADB
- ext4 delayed commit for /data
=======
Stock XXUANC3 kernel (to revert changes)
http://www65.zippyshare.com/v/32441894/file.html
Revert using Odin, in the same way you've installed a Reloaded Version....

Awww man,...I wish i could flash this, but I'm on the exynos =(
Sent from my SM-P900 using Tapatalk

rgolnazarian said:
Awww man,...I wish i could flash this, but I'm on the exynos =(
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Sorry pal, Qualcomm only, not even a chance to run this same way as the devices (and mostly important: provided software, ie. system structure) DIFFER A LOT between themselves.
Update 1: uploaded fix #1 which is resolving some trivial issues found in initial version; sorry for that, now we can say that every described feature has been included hope for some feedback... thank you...
Update 2: FIX FOR NOT WORKING SCREEN MIRRORING CAN BE DOWNLOADED HERE:
http://www67.zippyshare.com/v/25492738/file.html
I have personally modified a library that is being used by screen mirroring feature, which forces video encryption using keys from stock kernel, and which prevents to run mirroring at all . This is an issue of any modified kernel, on any Samsung device. Attached library fixes this, by disabling HDCP at all. It has been reported that the library resolves the issue for any Qualcomm based Samsung device running 4.4.2 KitKat and for any custom kernel. It will NOT work for Exynos devices...
Installation:
- download attached libwfdsm.so file
- overwrite genuine one in/system/vendor/lib (important! NOT /system/lib!!!!)
- chmod 644 libwfdsm.so ||| chown 0.0 libwfdsm.so ||| restorecon -R /system/vendor/lib
- mirroring will work again after reboot!!

YAY!
Beautiful, absolutely beautiful. You made ma a very happy man with this. I'll flash this as soon as I get home from work. Can't wait to try it out, the stock kernel is giving me SOD and frozen wifi issues sometimes.

esgie said:
Sorry pal, Qualcomm only, not even a chance to run this same way as the devices (and mostly important: provided software, ie. system structure) DIFFER A LOT between themselves.
Update 1: uploaded fix #1 which is resolving some trivial issues found in initial version; sorry for that, now we can say that every described feature has been included hope for some feedback... thank you...
Update 2: FIX FOR NOT WORKING SCREEN MIRRORING CAN BE DOWNLOADED HERE:
http://www67.zippyshare.com/v/25492738/file.html
I have personally modified a library that is being used by screen mirroring feature, which forces video encryption using keys from stock kernel, and which prevents to run mirroring at all . This is an issue of any modified kernel, on any Samsung device. Attached library fixes this, by disabling HDCP at all. It has been reported that the library resolves the issue for any Qualcomm based Samsung device running 4.4.2 KitKat and for any custom kernel. It will NOT work for Exynos devices...
Installation:
- download attached libwfdsm.so file
- overwrite genuine one in/system/vendor/lib (important! NOT /system/lib!!!!)
- chmod 644 libwfdsm.so ||| chown 0.0 libwfdsm.so ||| restorecon -R /system/vendor/lib
- mirroring will work again after reboot!!
Click to expand...
Click to collapse
I was literally just about to post in the old thread with bad news about the modified "libwfdsm.so" file & screen mirroring with a custom kernel...if u remember i confirmed that the file u altered would work with a custom recovery on the 8.4 lte & i just assumed that it would work with an altered boot.img as well but unfortunately thats not the case after testing the other night (unless something else is wrong with my setup). So...my question is have u changed something else since then to allow it to work again & have u personally tested this yourself?
sorry to hijack the thread...didnt know if i should pm or post in the older thread

THEDEVIOUS1 said:
I was literally just about to post in the old thread with bad news about the modified "libwfdsm.so" file & screen mirroring with a custom kernel...if u remember i confirmed that the file u altered would work with a custom recovery on the 8.4 lte & i just assumed that it would work with an altered boot.img as well but unfortunately thats not the case after testing the other night (unless something else is wrong with my setup). So...my question is have u changed something else since then to allow it to work again & have u personally tested this yourself?
sorry to hijack the thread...didnt know if i should pm or post in the older thread
Click to expand...
Click to collapse
No problem, anyway, thanks for pointing the issue out! This may be an important information for mirroring users!
Since then I didn't change anything, yet. Really, I am also not sure if I have tested it with modified kernel, as the one posted here is the first kernel for P905 at all, and it's not even "fully" customized, as the kernel binary base was left unchanged.
So, I'd like to be sure: you are saying that modded lib:
- fixed the problem for custom recovery, but...
- ...didn't fix it for custom kernel
right?
I was looking for a solution to persistent enforcing mode since some time, so I was flashing test boot.imgs from time to time, then reverting to stock again, meanwhile I created above lib, I can't really be sure about if it is working when both bootimg and kernel are customized (this would also be an opposite to previous Sammy's Android releases, where a single fix was solving all the issues related to customizations of both kernel and recovery!).
We also have to be aware that the issues may not be a result of flashing different kernel at all, but a result of the changes themselves, ie. disabled knox, disabled encryption of i-dont-really-know-what, etc, etc.
And the most important thing! Since I have heard of AllShareCast/Screen Mirroring for the first time (it probably appeared for the first time in S3/Note2/Note10.1), it always required resetting the flash counter - which could be viewed in download mode and which is NOT the same as Knox flag - to ZERO and that requirement AFAIR remained totally independent from the requirement of having stock boot/kernel (or lib patch). Have you checked the counter state? Did you reset it to zero again using Chainfire's Triangle Away after flashing non-stock kernel (which, obviously, TRIPPED the counter)? Can you check if it is working? Note that at least on my P905, Triangle Away still works flawlessly and resets the counter without any problems and even without a need of reboot!
Please check above info and try if the issue is fixed after running Triangle Away. I am leaving for a short business trip soon, so I'll perform my own tests with AllShare cast until next of the week, however, neither today nor tomorrow...

I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.

cavkic said:
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
Click to expand...
Click to collapse
Argh possibly too many dots in filename... will correct it tomorrow.

cavkic said:
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
Click to expand...
Click to collapse
same here...

Hi,
I have a problem with screen mirroring.
Installed the patch and mirroring connects to the dongle, but the TV screen turns just black.
The dongle works perfect with HTC One M8, it must be a softwareproblem?
Thanks for help!!!

Will this work on the P905V (Verizon Variant)? I need to downgrade the permissions in my Security in order to use Towelroot, because they're set to Medium and I believe that prevents Towelroot to work properly. Most of the other Note 12.2 variants have been rooted....except the Verizon version.

Can anyone give me some advice please. When I enter the command in terminal emulator I get an error saying "Unable to open chown. No such file or directory". Am I missing something obvious lol.

Will this work on p907a AT&T version of note pro 12.2?
Sent from my SAMSUNG-SM-P907A using XDA Premium 4 mobile app

cnote74 said:
Will this work on p907a AT&T version of note pro 12.2?
Sent from my SAMSUNG-SM-P907A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On the topic name it says [P905 LTE ONLY], and your device is some different..

tdetroit said:
Will this work on the P905V (Verizon Variant)? I need to downgrade the permissions in my Security in order to use Towelroot, because they're set to Medium and I believe that prevents Towelroot to work properly. Most of the other Note 12.2 variants have been rooted....except the Verizon version.
Click to expand...
Click to collapse
I would like this answered as well. I also have the "v" variant. Maybe saying LTE includes many? See my link I attached, found while investigating this specific question.
http://www.usatoday.com/story/tech/2013/07/07/sprint-att-verizon-phones-network-carriers/2486813/
Ever since I rooted my tablet it goes on random reboot kicks. I want to start over. Also TWRP will not stick when I try to flash it.
I have many issues which I'm currently posing in their appropriate forums. It would be nice to wipe to a rooted stock.

Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!

Thanks. The Galaxy is connecting to theTV, but the screen is only turning black - no Display...
Any idea?
Thank you.
esgie said:
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Click to expand...
Click to collapse

esgie said:
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Click to expand...
Click to collapse
I tried both methods and still get no devices found when I turn on screen mirroring.

ColBill said:
I tried both methods and still get no devices found when I turn on screen mirroring.
Click to expand...
Click to collapse
Hm.
This is weird, as the problems with allshare cast + custom kernels is not that "no devices are found" but that devices ARE found without any problem but the connection process fails after a few secs. This solution may help with the issue i described, but it will surely not solve the problem with no peers detected at all.
No peers detected = problems with wifi direct (are you able to send files between wifi direct between devices?)
Can you tell me what is your exact device config? And are you using allsharecast dongle or other third party hardware?
@fokus
Only one: also reset flash counter with Triangle Away and then try again. And make sure you spell the value in the command as "disable" not "disabled" - it's tricky and one can miss it...
Well, there are two additional things to add.
Guys, make sure you have updated Samsung's ScreenMirroring firmware update app to the latest version. And check out the samsung mirroring fix app in google play, which solves some issues for various devices (dunno which ones exactly as i have never been in need of using it).

The fix half worked for me lol. The tablet now connects fine to the Netgear PTV3000 but all I get is black screen. Step in the right direction though as at least it connects now. Just need to get a picture to show lol.

Welcome to Galaxy Mod Ultimate
Galaxy Mod is the ultimate collection of tweaks and modifications. All tweaks are in 100% working order. All logs have been verified accurate. I turned on the jet engine's. This will work on any device,but is made for galaxy device's. It can still be used on any device 4.4+.
Android 4.4+
Contents:
1.Cleaner script-Cleans junk at boot
2.Entropy generator-Ramps up entropy
3.Ext4 journal tweaks-Disables journalism
4.Fstrim-Free's up space
5.Galaxy_engine-Network speed tweaks and sleepers adjustment
6.Kill_media_server-Kills media server when not in use
7.Ram manager-Minfree's adjustment
8.SQLite optimize-Optimizes SQLite Data Bases
9.Touchscreen tweaks-Adjust touchscreen response
10.Zipalign-Speed up apps by zipalign
11.Frames per Second adjustment
12.Liquid Smooth UI
13.Loopy smoothness
14.V4A Selinux policy work around. V4A will work as system app without getting reset.
15.Build.prop tweaks
**********************************************************************************************************************************************************************
DIRECTIONS/HOW TO SEE IF IT'S WORKING OR REMOVE TWEAKS
1.Install zip in custom recovery- this is really all you need to do.
2.Open terminal type su then type Galaxy this will perform checks to ensure proper install.
3.In terminal type Entropy and navigate through the menu's/Entropy is active and turned on at boot by default.
4.Open terminal and type uninstaller to uninstall Galaxy_Mod
5.qrngd binary is deleted and backed up to system/bin/qrngd_backup/ this is needed for entropy to work properly.
6.Galaxy_Mod logs all activities in data for all tweaks and scripts with working verification.
7.Galaxy_Mod backs up your original init.d folder.
**********************************************************************************************************************************************************************
Credits; Thanks to these xda members for inspiration and base tweaks
zepplinrocks
slaid480
Ryuinferno
rass1
Anyone else who helped me learn this stuff along the way.Whoever you might be.
If I forgot to give you any credit p.m me and I'll fix it.
**********************************************************************************************************************************************************************
Changelog:
7/29/14 Complete rebuild of entire package
Everything much smoother now.
6/28/15 Lollipop compatible test version.
6/30/15: Fixed engine and uninstaller,Added V2 Entropy less zip,Added remover zip for systems that won't mount rw.
7/2/15: Added new ram options.
7/5/15: Added Loopy smoothness,viper for android SeLinux work around,logs now go to system/etc/Galaxy,Touchwiz launcher locked in memory,added new build.prop tweaks package,loads of new tweaks and adjustments.
Download:Ultimate
Standard Mods Pack
Download;Ultimate V2
This is an entropy free mod,for use with seeder.apk or when entropy causes issue's.
Download:Galaxy Remover
Use this if system can't mount as rw in uninstaller.
A lot changed so make sure you uninstall old tweaks with terminal first.Type su then type uninstaller.

Excellent work. Will try as soon as I take a backup

Thanks. veryone just feel free to comment on either thread. Let me know what you would like to see.

Updated with new zip. Much better response and smoother UI interactions. Come and get it.

Going to bake this into my new rom . Thanks

i'm going to try it on eudemony rom v2 superslim
i'll make you know..
edit: no, nothing.. installation aborted..
edit2: well.. su galaxy tells me that everything is installed, so i don't know that final message (error status 7, installation aborted to what referred XD)

erghetto said:
i'm going to try it on eudemony rom v2 superslim
i'll make you know..
edit: no, nothing.. installation aborted..
edit2: well.. su galaxy tells me that everything is installed, so i don't know that final message (error status 7, installation aborted to what referred XD)
Click to expand...
Click to collapse
What recovery are you using? Look in data/Galaxy and see if there are logs.

CWM touch.
well, typing command in terminal seems it says me it is installed, so i think all is fine.
only thing.. i have deleted Kill_media_server from init.d folder because at boot it disables bootanimation's sound

CWM has been throwing error 7 for a long time now. On many different devices. It's a well known issue. No worries thought, maybe I can find a way to trick it. That way no more false errors.

Sorry off topic is dark side of me cohee related?

Weirdly yes and no. I know the song your talking about, and even to top it off. The dark side is a reference, to where in my personality I normally reside. But they have no connection other than, the bazaar coincidence.

Wow. This works great. Had no error installing and this made my phone feel way faster.

I typed su then Galaxy but nothing happen ? So what should i do next ?

I flashed this mod but on reboot not files inside etc/init.d why?
edit: init.d now showed, but build.prop still the same no modifies

No_Fe4r said:
I typed su then Galaxy but nothing happen ? So what should i do next ?
Click to expand...
Click to collapse
Make sure you use a capital G when you type Galaxy.

Thanks. Installed this just now and verified everything installed correctly. Hope it makes a difference. :fingers-crossed:

churchey360 said:
Make sure you use a capital G when you type Galaxy.
Click to expand...
Click to collapse
Great working with Phoenix rom

Will this help my battery life at all?
---------- Post added at 04:39 PM ---------- Previous post was at 04:31 PM ----------
Also if im on an aosp based rom and i dirty flash to a newer nightly do i need to reflash the mod or should it still be working?

5.0
Does this work with 5.0?

Installed and working on my Galaxy Tab 4 10.1 SM-T530NU running stock rooted NK1. Thank you so much

FINALLY Lenovo Yoga Tab 2 Pro 13.3" +Lollipop UPDATE NOV 2015 (for non root device)
This is the first somewhat official release of lollipop for the 1380F ::: Lenovo Yoga Tablet 2 Pro Android with Projector ::: avoid flashing this if your device is rooted
This update (as to my knowledge) was first released to some region and then perhaps pulled off. I'm I Japan and I did not receive this update
The original poster ionioni shared a download link in the lenovo forums
https://storage.rcs-rds.ro/links/9e7a1ddd-8aa9-4a47-a995-89b0a75fc25d
I have uploaded the same file to my rapidgator account
http://rg.to/file/5dfad2ef864bc65ac477139da26aa559
If any dev out there with androidfilehost.com cares to upload it there to would be great.
To install >>>>> if you never rooted <<<<
::: go to settings :: update :: upper right hand corner :: tool kit :: select downloaded zip
== so far so good, perhaps its a beta release but the word is so far that its better ==
**** you 99.999% might not be able to downgrade to KitKat ***
If it is a rooted device
By user ionioni
you should NEVER take an [ota] update AFTER you root. the rooting process modifies your system partition files and this is a problem because an update process will patch or replace files (and since Android 5.0 Google recomends the patch to be made against the whole system partition as a block patch, but it's not the YT2 case as they still use file patches), so if the files are modified by rooting, and they are, your update will fail and some of the files will be patched while others will not be and this will bring unexpected results: from minor ones to a complete hang.
so if you take an update always UNROOT before you take-it and reroot AFTER the update. that's no longer your case because you already screwed the system partition files, and the easiest way is to flash a stock rom (which ofcourse includes your system partition files among others) and this way you will restore the device.
but the problem (in your case) is that the stock rom you flash MUST match the bios version (KitKat rom matches an IA32 bios, while Lollipop matches an x64 one) and YOU HAVE after the Lollipop upgrade a Lollipop bios (x64) and you cannot just try to flash (as you did) a KitKat rom as this will fail (the files from your stock kitkat involved in the flashing process will fail to load because the bios is a x64 one and it wont accept files made for the IA32 architecture)
you have two solutions:
1. flash a stock Lollipop rom (but this is not yet made available by Lenovo, in general takes one or two months since the OTA before they release a complete updated rom)
2. return to KitKat bios and only AFTER you have downgraded the bios try and flash the kitkat (and after ofcourse you can re-take the Lollipop OTA). in this case again be careful, the one solution publicly available for returning to kitkat bios form lollipop is a 830/1050F and NOT a 1380F one (and i think noboy has tried yet a complete kitkat return). also be careful because the bios is not your mmc or sdcard drive, if you wrongly write it (with for wxample an incompatible version) you will HARD BRICK (and you will have no other solution but to send your tab to lenovo for fixing, it will be completely dead, no longer starting no lights nothing!).
MAJOR NOTES :::: IMPORTANT PLEASE READ ::::
by ionioni (original poster of the update)
Remember: if you have NO REGION configured when you do the Lollipop OTA update it will FAIL at the end and your tab will have errand behavior after the update (fails to boot, EFI shell, BIOS screen only, stuff like that) so remember to CHECK that you have a region configured BEFORE updating to Lollipop and if you don't have then set one. you most likely don't have one if you flashed back the stock kitkat rom at some point and didn't configuret one after.
check region: input in contacts the code ####59930# it should show a (your) region, if it shows Unknown you need to set a region
set (or modify) region: input in contacts the code ####6020# then chose your region, it will reboot and update (deleting your user data too so backup if required) after rebootyou can check region again and take the OTA
Little Notes
Your basic bloatware comes with the installation pacakge and that green security hd app is replaced by McFee, good news it is uninstallalbe.
The "downside" if any to this update is :: bottom drag up quick settings menu is gone and still uncertain if multiwindows is available. lenovo scratchpad works even better now.
Screenshots for the unbeliebers
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quick Tutorial to remove bloat **** Requires Root *** by ionioni
you install your rom or your ota and only afterwards you modify your os. from within a shell use pm command to first disable/block unwanted apps for testing first (so you can pm enable/unblock them if you do something wrong) and if ok you can pm uninstall them. be carefule as the tool will allow you to basically disable any app (system ones included) so you should pay attention, start with the more easier ones (for eg among others i disabled com.lenovo.videoplayer as i instaled mxplayer, com.lenovo.email i don't need it i have gmail app etc)
google for "Android package manager pm" for more info on what is and how to use the tool. root required ofcourse.

Are you running this? Is it stable?

grumpyrussian said:
Are you running this? Is it stable?
Click to expand...
Click to collapse
Yes I am. I have been running it for the past two hours. Others in the lenovo forum have been on it for more than a day or two. General feeling it is good.
Projector works fine, it seems like it is a pure android experience with their bloatware, most of it uninstallable.
I installed it as a ota update. It took some time but no errors or anything problematic. None of my installed apps or files were deleted.
With the KitKat version Firefox would crash and auto rotate function had major flaws.
I still have to see if Firefox crashes and if certain addons are available now.
I use rotate app by Fame It to solve my rotating issues. Since it remained after the update I will most likely not uninstall it.
Keyboard is google keyboard which is nicer.
The quick menu from the bottom drawer is no longer there, slightly sad but I don't care.
Everything seems faster too.
I will post updates if I notice anything strange.

ichiai said:
Yes I am. I have been running it for the past two hours. Others in the lenovo forum have been on it for more than a day or two. General feeling it is good.
Projector works fine, it seems like it is a pure android experience with their bloatware, most of it uninstallable.
I installed it as a ota update. It took some time but no errors or anything problematic. None of my installed apps or files were deleted.
With the KitKat version Firefox would crash and auto rotate function had major flaws.
I still have to see if Firefox crashes and if certain addons are available now.
I use rotate app by Fame It to solve my rotating issues. Since it remained after the update I will most likely not uninstall it.
Keyboard is google keyboard which is nicer.
The quick menu from the bottom drawer is no longer there, slightly sad but I don't care.
Everything seems faster too.
I will post updates if I notice anything strange.
Click to expand...
Click to collapse
That's good to hear, I think im going to give it a try.

grumpyrussian said:
That's good to hear, I think im going to give it a try.
Click to expand...
Click to collapse
If you having been wanting the lollipop I think its a must.
Another change is that now you have McFee antivirus app thing instead of the previous one, and this too is uninstallable

ichiai said:
If you having been wanting the lollipop I think its a must.
Another change is that now you have McFee antivirus app thing instead of the previous one, and this too is uninstallable
Click to expand...
Click to collapse
Oh great I just love bloatware.

grumpyrussian said:
Oh great I just love bloatware.
Click to expand...
Click to collapse
Lol
I wish there was Android development for this. I know this would be a killer tablet if it we could flash asop ROMs like cyanogen or dirty unicorns. I would install black Gapps and my world would be close to perfection.

ichiai said:
Lol
I wish there was Android development for this. I know this would be a killer tablet if it we could flash asop ROMs like cyanogen or dirty unicorns. I would install black Gapps and my world would be close to perfection.
Click to expand...
Click to collapse
Yes this, or even something like remix os: http://www.jide.com/en/remixos

That looks pretty sweet

copy/paste from another (mine) post in official lenovo forums
to remember: if you have NO REGION configured when you do the Lollipop OTA update it will FAIL at the end and your tab will have errand behavior after the update (fails to boot, EFI shell, BIOS screen only, stuff like that) so remember to CHECK that you have a region configured BEFORE updating to Lollipop and if you don't have then set one. you most likely don't have one if you flashed back the stock kitkat rom at some point and didn't configuret one after.
check region: input in contacts the code ####59930# it should show a (your) region, if it shows Unknown you need to set a region
set (or modify) region: input in contacts the code ####6020# then chose your region, it will reboot and update (deleting your user data too so backup if required) after rebootyou can check region again and take the OTA

thanks for sharing. ive been banned from lenovo forrums for three days. anyway, have you produced any roms for 1380F?

ichiai said:
thanks for sharing. ive been banned from lenovo forrums for three days. anyway, have you produced any roms for 1380F?
Click to expand...
Click to collapse
i'm happy with my android+linux combo, the extra a custom rom could bring is not worth the effort and i already have that extra plus more in linux. also the ui/bloatware can be easily tweaked to one's needs by removing the unwanted apk
so the short answer is no (at least for now)

ionioni said:
i'm happy with my android+linux combo, the extra a custom rom could bring is not worth the effort and i already have that extra plus more in linux. also the ui/bloatware can be easily tweaked to one's needs by removing the unwanted apk
so the short answer is no (at least for now)
Click to expand...
Click to collapse
Damn that's pro == "that extra plus more in Linux" ==
:: I just unpacked the zip and feel too n00b. Could I hardbrick if I delete an apk that I'm not supposed to delete? I have a feeling the answer is yes.

ichiai said:
Damn that's pro == "that extra plus more in Linux" ==
:: so to confirm, if I unpack the zip and delete the apks and repack it will all be good?
Click to expand...
Click to collapse
you install your rom or your ota and only afterwards you modify your os. from within a shell use pm command to first disable/block unwanted apps for testing first (so you can pm enable/unblock them if you do something wrong) and if ok you can pm uninstall them. be carefule as the tool will allow you to basically disable any app (system ones included) so you should pay attention, start with the more easier ones (for eg among others i disabled com.lenovo.videoplayer as i instaled mxplayer, com.lenovo.email i don't need it i have gmail app etc)
google for "Android package manager pm" for more info on what is and how to use the tool. root required ofcourse.

ionioni said:
you install your rom or your ota and only afterwards you modify your os. from within a shell use pm command to first disable/block unwanted apps for testing first (so you can pm enable/unblock them if you do something wrong) and if ok you can pm uninstall them. be carefule as the tool will allow you to basically disable any app (system ones included) so you should pay attention, start with the more easier ones (for eg among others i disabled com.lenovo.videoplayer as i instaled mxplayer, com.lenovo.email i don't need it i have gmail app etc)
google for "Android package manager pm" for more info on what is and how to use the tool. root required ofcourse.
Click to expand...
Click to collapse
Thanks for the quick tutorial. I'm glad I asked. I was about to just unpack delete apks and the repack and flash.
I don't have root and I feel challenged to follow your advice. Will add this info.

and this is a list of my disabled packages (their names are self-explanatory), of course you can add remove from the list, it's just what i don't use, don't need
com.google.android.apps.books
com.google.android.apps.docs
com.google.android.apps.genie.geniewidget
com.google.android.apps.magazines
com.google.android.apps.messaging
com.google.android.music
com.google.android.play.games
com.google.android.talk
com.google.android.youtube
com.lenovo.anyshare.gps
com.lenovo.deskclock
com.lenovo.email
com.lenovo.fingerpaint
com.lenovo.lenovodaydream
com.lenovo.lps.cloud.sync.row
com.lenovo.paperdisplay
com.lenovo.smartswitch
com.lenovo.videoplayer
com.lenovo.weather.theme.dreamlandPad
you can disable with pm disable package_name
or enable with pm enable _package_name

this is from a pm i had with an 1380F owner. moral of the story ALWAYS UN-ROOT before you take an update
Re: Yoga 2 Pro Update
Originally Posted by USERNAME_DELETED
I asked somebody to borrow me a Micro SD Adapter, so I can format my SD card to fat32 on windows 10 today.
I copied your small update file on the SD Card and flashed it under 5.0.1 recovery and it seemed fine. Unfortunately, my Yoga just would NOT boot up ever after. I thought maybe the problem is I rooted it after upgraded it to 5.0.1
Unfortunately, I spent over 8 hours keep flashing it back to KitKat stock rom after having a problem of booting up right after flashing your small update file and it just didn't work at all.
so, what can I do now ? can I just flash it back to 5.0.1 ? or do I have to do it under KitKat ??
if so, how can I flash it back to KitKat then ? any idea ??
Click to expand...
Click to collapse
yes, as you said, the problem is that you should NEVER take an update AFTER you root. the rooting process modifies your system partition files and this is a problem because an update process will patch or replace files (and since Android 5.0 Google recomends the patch to be made against the whole system partition as a block patch, but it's not the YT2 case as they still use file patches), so if the files are modified by rooting, and they are, your update will fail and some of the files will be patched while others will not be and this will bring unexpected results: from minor ones to a complete hang.
so if you take an update always UNROOT before you take-it and reroot AFTER the update. that's no longer your case because you already screwed the system partition files, and the easiest way is to flash a stock rom (which ofcourse includes your system partition files among others) and this way you will restore the device.
but the problem (in your case) is that the stock rom you flash MUST match the bios version (KitKat rom matches an IA32 bios, while Lollipop matches an x64 one) and YOU HAVE after the Lollipop upgrade a Lollipop bios (x64) and you cannot just try to flash (as you did) a KitKat rom as this will fail (the files from your stock kitkat involved in the flashing process will fail to load because the bios is a x64 one and it wont accept files made for the IA32 architecture)
you have two solutions:
1. flash a stock Lollipop rom (but this is not yet made available by Lenovo, in general takes one or two months since the OTA before they release a complete updated rom)
2. return to KitKat bios and only AFTER you have downgraded the bios try and flash the kitkat (and after ofcourse you can re-take the Lollipop OTA). in this case again be careful, the one solution publicly available for returning to kitkat bios form lollipop is a 830/1050F and NOT a 1380F one (and i think noboy has tried yet a complete kitkat return). also be careful because the bios is not your mmc or sdcard drive, if you wrongly write it (with for wxample an incompatible version) you will HARD BRICK (and you will have no other solution but to send your tab to lenovo for fixing, it will be completely dead, no longer starting no lights nothing!)
sure thing a solution must exist for a 1380f Lollipop bricked, but it takes some time (a few things to test again)...
update: done testing http://forum.xda-developers.com/thinkpad-tablet/general/yoga-tab-2-830-1050-1380-to-kitkat-t3240487

yes lollipop and next..
okiiiii lenovo tab 2 1380f turn with lollipop 5.0.1...
root mmmm ok...
but il i try to install xposed ...bad news blank screen on boot ... and reset bootloader..install K.K. etc etc (soft brick..but easy to reset)
Someone success to install xposed on 5.0.1 for 1380f ?
an idea ? it's sdk21 for x86 i suppose...
thanks a lot
fab

help yoga 1380f
I have a setup error "install failure" how to fix it?

rafal9426 said:
I have a setup error "install failure" how to fix it?
Click to expand...
Click to collapse
I am getting the same error.. Fully unrootedd and changed the language to u.s
Sent from my YOGA Tablet 2 Pro-1380F using Tapatalk

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!