Screen mirror not working AFTER ROOT - T-Mobile Samsung Galaxy S6 Edge

Hello,
I was wondering, I rooted my GS6 Edge and it is not letting me screen mirror. It says Unable to screen mirror due to a hardware issue. I then unrooted and tried it again, it mirrored no problems. Why would root cause my screen mirror ability not work?

ohhellochris said:
Hello,
I was wondering, I rooted my GS6 Edge and it is not letting me screen mirror. It says Unable to screen mirror due to a hardware issue. I then unrooted and tried it again, it mirrored no problems. Why would root cause my screen mirror ability not work?
Click to expand...
Click to collapse
I don't know why u r having that problem im rooted and my husband is rooted and we can still do it...how did u root

lrmdaddy said:
I don't know why u r having that problem im rooted and my husband is rooted and we can still do it...how did u root
Click to expand...
Click to collapse
I used the chainfire smg920t file to root using odin3 v3.10.6, I am not sure if the smg925t still bricks the phone or not. Not sure if it matters or not.

I can screen mirror after root.

Nope...not working for me either after root. Coincidentally, I had the same issue with my Galaxy Tab S 10.5.
This is a known issue with Samsung devices after root. Please try the steps in this video. I got it working after that.

Try this zip I made flash in Twrp
https://www.dropbox.com/s/a27nfnzjtaqt68w/tmoedgemirrorfix.zip?dl=0
Works for me now

raw2000j said:
Try this zip I made flash in Twrp
https://www.dropbox.com/s/a27nfnzjtaqt68w/tmoedgemirrorfix.zip?dl=0
Works for me now
Click to expand...
Click to collapse
Can you upload this file again I also have this problem.

bronger said:
Can you upload this file again I also have this problem.
Click to expand...
Click to collapse
https://www.dropbox.com/s/tco2ar2eyj9vutq/ScreenMirrorFix0F8.zip?dl=0
Sent from my SM-G928T using Tapatalk

Using any root explorer go to system/build.prop
-add this line at last
wlan.wfd.hdcp = disable (remove any spaces after that)
- save and reboot.

Kartik Pokar said:
Using any root explorer go to system/build.prop
-add this line at last
wlan.wfd.hdcp = disable (remove any spaces after that)
- save and reboot.
Click to expand...
Click to collapse
Worked on Samsung S7 edge, smart view fails to connect after root, this method solve the issue.
Many thanks!

Latest TWRP is the cause of screen mirror break. If you Odin ROM and root using UniKernel through Odin, everything will work.
For me, the working combination (Gear VR and screen mirror working) is as follows:
TWRP wipe caches, data, internal, system
Odin>
DOJC (latest stock rom before mm. Untested with mm)
reboot
install gear vr (optional)
Odin>
S6_UniKernel_v8-0002-ODIN
reboot
Odin>
uncheck reboot first then
TWRP 2.8.7.1 (3.0.2 breaks screen mirroring)
reboot into recovery do not install SU from TWRP
flash OZOP_ROMless_v2 to debloat (optional)
profit

Kartik Pokar said:
Using any root explorer go to system/build.prop
-add this line at last
wlan.wfd.hdcp = disable (remove any spaces after that)
- save and reboot.
Click to expand...
Click to collapse
This solved the problem. Thanks!!!

Thanks helped me greatly
Sent from my SM-G925T using XDA-Developers mobile app

Kartik Pokar said:
Using any root explorer go to system/build.prop
-add this line at last
wlan.wfd.hdcp = disable (remove any spaces after that)
- save and reboot.
Click to expand...
Click to collapse
thanks for your helping! it's worked on S7 edge 6.0.1 custom rom

Hi I rooted marshmallow rom g925tuvu4EPF1 AND couldn't cast to my TV... what worked for me was updating quick connect from the Galaxy app store so I'm using quick connect v4.1 also I casting to a Samsung 4k tv
Sent from my SM-G925T using Tapatalk

zhelloz said:
thanks for your helping! it's worked on S7 edge 6.0.1 custom rom
Click to expand...
Click to collapse
hi,
i do have that on my S7 edge but it still isn't working...
May i ask if yours is still working, what rom you're using and what version of TWRP (i read this might cause issues)?
Thanks

I have this Screen View Mirroring problem too....
First some info about my phone, and how I rooted it,
then the question follows below that...
PHONE INFO:
I have a "Samsung Galaxy S7 Exynos (SM-G930F) "
I have NOT updated the phones software (OTA/ODIN)
Android Version 6.0.1
Baseband Version: G930FXXU1BPJG
BuildNumber: MMB29K.G930FXXU1BPJG
(Android Security Patch Level: 01.NOV.2016)
I have rooted it using "ODIN" with "Samsung USB Drivers"
and "Download Mode" to flash the phone with ROOT...
Flashed it with this file "CF-Auto-Root-herolte-heroltexx-smg930f.zip" (Contains ChainFire Root + TWRP)
Seems to be "TWRP-3.0.2.4-herolte.img" thats installed on my phone now... This could probably (maybe) be changed with the use of the app "TWRP Manager", if needed, to another version of TWRP...
Then I restarted the phone, and booted into recovery (TWRP)
did select WIPE + FORMAT DATA in TWRP.
Then I installed the XPOSED FRAMEWORK using TWRP.
I installed "xposed-v86.0-sdk23-arm64-custom-build-by-wanam-20160709.zip"
All of this works! I get ROOT and I get TWRP, and XPOSED with different modules to work... So far so great...
THE QUESTION:
Then there was the Screen Mirroring part (Smart View/QuickConnect)
This is NOT working at all on my phone, after rooting the phone...
I did the EDIT of the "/SYSTEM/build.prop" file, as suggested above, and added the "wlan.wfd.hdcp=disable" line to the end of that file. Saved "build.prop" and rebooted.
This made my "GRUNDIG TV" (not a samsung tv) connect to the phone, asking for the PIN, and upon entering the PIN, a black screen opened on the middle of the tv screen (where content from the phone would normally be) and only a mouse pointer is visible in the black middle part of the screen (the content space).
I then later tested the same phone (with no new changes) at a friends house, connected it to a 55inch Samsung with a curved display, and there it worked as expected...
Both sound and image was transferred... But at home, only a "black box w/mouse pointer" in the middle of the screen - no image transferred...
PS: WHILE HAVING THAT EDITED LINE AT THE END OF THE "build.prop" FILE...
I also noticed that some pages could not be opened in FIREFOX while having this edited line at the bottom of the "build.prop", and apps like SureSpot and Wickr could not be logged into...
It is as if the mobile networking on my phone was partly working, and partly not....
So I edited the line away, using a #hashta, aka: commented it away, then saved it, and restarted the phone, and could now immediately log into SureSpot/Wickr and open the pages in FireFox that could not be opened before.... (with the line of code active in "build.prop")
So my question is... How can I make this work with my GrundigTV ???
I need ROOT for other fine-grained control of apps and the android system, and I need XPOSED too, to get that fine control...
So my question is:
How can I maintain ROOT and XPOSED (using the method explained above, to root the phone)
and still change around "something" to make Screen Mirroring (Smart View) work with any TV? And not having that fix, create strange problems with app connectivity.....?
PS: I've also updated "QuickConnect" to the version
(v 4.1.8980705.0)
using "Samsung Apps" to update it... As it seems to have something to do with this...

I'm having the exact same problem, any success?

The same problem on A3 2017 (SM-A320F) using CMW Recovery and latest SuperSU zip to root. I will try some suggestions above to see if I can fix this.

jnflos said:
The same problem on A3 2017 (SM-A320F) using CMW Recovery and latest SuperSU zip to root. I will try some suggestions above to see if I can fix this.
Click to expand...
Click to collapse
Use a file browser such as Root Browser and go to the root of your device then locate the "System" folder and find build.prop and edit it with any application that can edit it and find the bottom line, right at the edge of the bottom line you need to press enter twice and then paste this:
wlan.wfd.hdcp=disable
And then save it and reboot your device.

Related

[Q] HELP Unfortunately SuperSu has stopped

I tried rooting to chainfires root process but after doing this 6 times after it boots back i get the message that Unfortunately SuperSu has stopped working and on top of that i keep getting the notification Unauthorized access to a secured area has been blocked. Im not sure if i did something wrong cause i followed his instructions step by step exactly right am i missing something or what is the deal.. please help
update i realize i forgot to say what phone im rooting lol
i have samsung galaxy note 2 with 4.3
I am in the same situation. I was able to root my S4, but I can't get my wife's Note 2 to root. Every issue you have I am having also. Hopefully someone will be able to help us.
critter1332 said:
I tried rooting to chainfires root process but after doing this 6 times after it boots back i get the message that Unfortunately SuperSu has stopped working and on top of that i keep getting the notification Unauthorized access to a secured area has been blocked. Im not sure if i did something wrong cause i followed his instructions step by step exactly right am i missing something or what is the deal.. please help
update i realize i forgot to say what phone im rooting lol
i have samsung galaxy note 2 with 4.3
Click to expand...
Click to collapse
+1.
Frustrated. :banghead:
Any help would be appreciated.
Sent from my SPH-L900 using Tapatalk
chconser said:
+1.
Frustrated. :banghead:
Any help would be appreciated.
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
I finally got mine rooted. Do everything in this post. I was able to remove KNOX and finally get my damn phone rooted! This was used to root my wife's Sprint Note 2 with the OTA 4.3 update. here
is the complete thread if you want to see it all. The link I posted first is the 3rd post from that thread.
Doing those steps WILL FIX your issues with not being able to root your Note 2.
I actually boot looped my wife's Note 2 in the process, so if you do brick/boot loop it, then follow these instructions. That put the phone back to the OTA 4.3 stock version. I had to put my wife's SD card into my phone and add the files to her SD card (provided in the link I just posted) to get it to work. Me being an idiot is how I boot looped her phone. This was the ONLY way I could get it to work... and I tried so many methods I found here, youtube, and online.
Good luck gentleman! Let me know if I can help you anymore!
baseband version
i was wondering if the baseband version could have anything to do with it (im still new to rooting) i have L900VPUBMK4 on my phone but when i looked around in other places i noticed people having L900VPAMK4 is there a difference an could this be why mine wont root
i will try your method above an thanks so much for posting this i will let you know of my outcome
oops miss spelled the baseband version i have LP900VPUBK4 but others have L900VPAMK4
tried
smashedixnay said:
I finally got mine rooted. Do everything in this post. I was able to remove KNOX and finally get my damn phone rooted! This was used to root my wife's Sprint Note 2 with the OTA 4.3 update. here
is the complete thread if you want to see it all. The link I posted first is the 3rd post from that thread.
Doing those steps WILL FIX your issues with not being able to root your Note 2.
I actually boot looped my wife's Note 2 in the process, so if you do brick/boot loop it, then follow these instructions. That put the phone back to the OTA 4.3 stock version. I had to put my wife's SD card into my phone and add the files to her SD card (provided in the link I just posted) to get it to work. Me being an idiot is how I boot looped her phone. This was the ONLY way I could get it to work... and I tried so many methods I found here, youtube, and online.
Good luck gentleman! Let me know if I can help you anymore!
Click to expand...
Click to collapse
I tried this but when i did the kingo software it immediately asked me to grant supersu an had a button on bottom of kingo that said ok so i look at my phone but no supersu so i still kept going thru the process an then noticed in kingo where its suppose to say what phone type is connected it says samsung device an from seeing it on other sites of people connecting there devices it had there device names reconised so not sure if its not doing that correctly for my phone or what but after running the software which frozen for awhile when it came to the part that said checking root an then it said waiting for device for awhile an then stopped an said root failed
i cant even get passed step one
I finally rooted my note 2
i tried cf's method an im not sure what went wrong but something did an it wouldnt root so i then tried kingo but at first i noticed that when connecting my note to kingo it just said samsung device it didnt reconize it fully to it saying samsung sphl900 so i knew something wasnt right an then after trying to root it failed so i then noticed that in download mode it said it was customized so i downloaded USER_L900_SPT_MC2_to_MK4_Update_FWD an used odin an then opened the download again on my phone an it finally said samsung official so i then went back to kingo an it did reconize my phone an it did finally root it ,,, im new to rooting an not sure if this will actually help anyone but its what i went thru to get mine rooted an thanks to everyone that has helped me
I was able to fix the same issue...
chconser said:
+1.
Frustrated. :banghead:
Any help would be appreciated.
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu
kkgiyer said:
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu
Click to expand...
Click to collapse
I tried this to no avail, getting error message 'Application not installed'. The thing is, when I go into the Play Store it says SuperSU IS installed but I only have the option to open it. There is no 'update' option available like I keep reading everyone suggests to do to fix this problem. And when I attempt to open SuperSU, I get the error message 'Unfortunately, SuperSU has stopped' followed by the KNOX security notice 'Unauthorized access to a secured area has been blocked'.
Sent from my SPH-L900 using Tapatalk
Ahh
I am having a similar issue
PhonezDoctor said:
I am having a similar issue
Click to expand...
Click to collapse
Same.
Everyone I figured out a simple solution to this. I got my phone back on the 13 from replacement. On the 16 I tried to root for the first time. And KNOX led me into a panic. Reading all the forums and knox blocked every attempt I made, but I neat that ***** into the ground.
1. Get some kind of file Explorer and find the SuperSU apk.
2. ReInstall that bad boy.
3. Immediately after install a message will appear asking if SuperSU can try to disable KNOX.
4. Click it quickly, if you don't knox will try to block it again.
5. You should now have KNOX out of the way. You should now be free to delete that slut!
I chose system app safe remover and searched for all files with KNOX and deleted it. I feel you could probably kill it with any root explorer and know the files you are looking for.
Sent from my SPH-L900 using xda app-developers app
kkgiyer said:
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu
Click to expand...
Click to collapse
For further clarification, simply clicking on it did not work for me. It gave me an "There is a problem parsing the package."
If you long press on the file then select More from the bottom menu then select Install, it will install properly.
Just wanted to clarify for anybody else who ended up with that issue.
It worked!
kkgiyer said:
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu
Click to expand...
Click to collapse
This worked for me. Once I reinstalled the SuperUser APK, ES asked for access and everything else fell into place. Thanks!
use esfile to solve it
chconser said:
I tried this to no avail, getting error message 'Application not installed'. The thing is, when I go into the Play Store it says SuperSU IS installed but I only have the option to open it. There is no 'update' option available like I keep reading everyone suggests to do to fix this problem. And when I attempt to open SuperSU, I get the error message 'Unfortunately, SuperSU has stopped' followed by the KNOX security notice 'Unauthorized access to a secured area has been blocked'.
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
I got this done by the following:
1. Do exactly as aforementioned instruction, untill you find superuser.apk
2. Hold your finger on that apk icon untill a little squre show up that you can mark it
3. Find "more"(my is at the right lower corner of the screen), choose it and find "install" on your right.
4. Then install.
I dont know why this apk can be installed through es file, basically it still needs to Android to run the installation, yet it works in this way.
have a try and good luck
I keep having to go back into the file explorer and installing it. It will work for a while then out of the blue it pops up and says it has quit. I am very skeptical to try and go through the flash process to install a different ROM. Currently bone stock 4.3 eff bomb. Any suggestions?
JD
Try and use ODIN to flash TWRP then flash @billard412 to get back to MC2 stock, it will remove KNOX and reset flash counters, if any. Then ODIN TWRP again since it will re-install the stock recovery you can then flash the MK4 kernel, WIFI Fix and MK4 ROM of your choice.
flynhawn2002 said:
Try and use ODIN to flash TWRP then flash @billard412 to get back to MC2 stock, it will remove KNOX and reset flash counters, if any. Then ODIN TWRP again since it will re-install the stock recovery you can then flash the MK4 kernel, WIFI Fix and MK4 ROM of your choice.
Click to expand...
Click to collapse
I have warranty bit 1 showing.
JD
jdougs said:
I have warranty bit 1 showing.
JD
Click to expand...
Click to collapse
Ok....since you tripped KNOX you cant get rid of that but its ok if you are not returning your phone (maybe out of warranty?) then just ignore it.
Flash away!
Ya the warranty didn't mean squat...I went ahead and tried the SGS3 JELLYBOMB VER 20.0.0.MD5 and it went with no problems. Haven't got the SuperSU has stopped since flashing. Thanks for the encouragement here. So far so good.
JD

Pls help!!! GT-I9192 ROOT

Hi All,
I'm trying very hard to search for the best method/option for rooting my Samsung GT-I9192 Duos(India Version) but not found any as yet.
Not sure if I have knox or not(is there is way to find out?) but I would prefer an option which does not void my warranty. Although if I have to, I don't mind foregoing the warranty. Also, I need only root - custom kernel, etc may not be required, Thanks
Can you please suggest the best and simplest method/option(preferably one click) to root my device having the following specs:
Model: GT-I9192
Android version: 4.2.2
Baseband version: I9192DDU1BML1
Kernel version: 3.4.0-1971249
[email protected] #1
Sat Dec 14 21:59:36 KST 2013
Build number: JDQ39.I9192DDU1BML1
Appreciate any help urgently, Thanks!!!
BS
well if you don't mind sending your info to some server in china [as some ppl claim] kngo root is your safest bet and you do have knox, you can always check it by going in download mode and see it if the word knox is there, which it will be in your case , btw after using kingo root you cannot boot into recovery you have to flash a custom recovery which will also trip your knox . or you might get lucky as me on the same build as you , rooted via kingo on I9192DDU1BML1 , deleted all Knox files [ search this forms for which files to delete] , flashed cwm recovery , flashed custom kernels, and still din't trigger knox only god knows why as i can't figure it out.
there are some other methods like saferoot , just do a search on this forums.
The BML1 has knox and saferoot does not work on BML1. Kingo works fine and I have rooted the BML1 on mine using Kingo
Sent from my GT-I9192
Some how Kingo refuses to work with my device. At first with Kies installed, it would connect to my device and get stuck at 0% on the "Downloading Device Driver Software Screen". I waited hours but it was still stuck at 0%.
After reading up on their support page, I downloaded and installed the drivers manually. But now Kingo wont connect to my device.
It does initiate a connection when I plug the cable/device in USB but after a few seconds, its back to the home screen saying "Device Not Connected".
I have tried the following drivers with/without Kies 3:
SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.24.0.exe
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0.exe
What am I doing wrong? Hope there is another option/method if Kingo doesnt work out, Thanks again.
bs24 said:
Some how Kingo refuses to work with my device. At first with Kies installed, it would connect to my device and get stuck at 0% on the "Downloading Device Driver Software Screen". I waited hours but it was still stuck at 0%.
After reading up on their support page, I downloaded and installed the drivers manually. But now Kingo wont connect to my device.
It does initiate a connection when I plug the cable/device in USB but after a few seconds, its back to the home screen saying "Device Not Connected".
I have tried the following drivers with/without Kies 3:
SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.24.0.exe
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0.exe
What am I doing wrong? Hope there is another option/method if Kingo doesnt work out, Thanks again.
Click to expand...
Click to collapse
Did you turn on USB Debugging mode?
You have to first enable the Developer Options before you can access USB debugging
Setting>About Device>Tap on Build Number 7 times until the screen shows Developer Options is enabled
hobbya said:
Did you turn on USB Debugging mode?
You have to first enable the Developer Options before you can access USB debugging
Setting>About Device>Tap on Build Number 7 times until the screen shows Developer Options is enabled
Click to expand...
Click to collapse
Hi... Yes, developer mode was turned on before starting the procedure.
What else could it be? Thanks
I have no clue. Do you have another Samsung phone to prove the setup on the computer? The Samsung drivers can recognize any Samsung phone if they have been installed properly.
hobbya said:
I have no clue. Do you have another Samsung phone to prove the setup on the computer? The Samsung drivers can recognize any Samsung phone if they have been installed properly.
Click to expand...
Click to collapse
Yes, I did root a Note 2 successfully with the same computer/setup but another/manual method(using Odin) with only Kies installed. I guess all required device drivers get installed when you install kies? This is the first time i'm using Kingo though.
Will this method work for my device? The only concern is I don't see I9192DDU1BML1 mentioned anywhere. Thanks
http://forum.xda-developers.com/showthread.php?t=2494435
^ this method did work for me on the earlier firmware before BML1, but i lost my wifi so had to flash a custom kernel , dunno if it will work for ML1 as for usb try dialing *#0808# from your cell this would take you in usb settings, tick both mtp+adb , reboot , if they art already ticked uncheck them and check them again.
had the same issue with kies and s4 drivers this sorted it out .
dovakinn said:
^ this method did work for me on the earlier firmware before BML1, but i lost my wifi so had to flash a custom kernel , dunno if it will work for ML1 as for usb try dialing *#0808# from your cell this would take you in usb settings, tick both mtp+adb , reboot , if they art already ticked uncheck them and check them again.
had the same issue with kies and s4 drivers this sorted it out .
Click to expand...
Click to collapse
Thanks a lot. Only MTP was checked, I checked the 2nd option MTP+ADB and rebooted the device. Hope this resolves the issue.
Unfortunately, I don't have sufficient privileges on this computer so will have to wait another 2 hours to verify it on my computer
This worked and now I have ROOT!!! Thanks a million everyone, especially dovakinn for that last master stroke!!!!
Is there a way to remove or delete the Supersu icon from the menu? I dont want to uninstall it, just hide the icon without using the native hide/unhide feature. Thanks Again!
bs24 said:
This worked and now I have ROOT!!! Thanks a million everyone, especially dovakinn for that last master stroke!!!!
Is there a way to remove or delete the Supersu icon from the menu? I dont want to uninstall it, just hide the icon without using the native hide/unhide feature. Thanks Again!
Click to expand...
Click to collapse
U have 2 options to hide Supersu icon.
Samsung way: Apps - Menu Button - Hide applications - Check supersu - Done
Supersu way - SuperSu - Settings - Launcher icon - Invisible from launcher
SilviuMik said:
U have 2 options to hide Supersu icon.
Samsung way: Apps - Menu Button - Hide applications - Check supersu - Done
Supersu way - SuperSu - Settings - Launcher icon - Invisible from launcher
Click to expand...
Click to collapse
Thanks SilviuMik. I got the following pop up as soon as I clicked on SuperSu - "Samsung KNOX has been detected. this might limit root capabilities and cause annoying popups. Try to disable KNOX?"
Should I say OK or Cancel?
Srry but Im completely new to this KNOX business. Many Thanks
bs24 said:
Thanks SilviuMik. I got the following pop up as soon as I clicked on SuperSu - "Samsung KNOX has been detected. this might limit root capabilities and cause annoying popups. Try to disable KNOX?"
Should I say OK or Cancel?
Srry but Im completely new to this KNOX business. Many Thanks
Click to expand...
Click to collapse
Press Ok
Otherwise u will get errors while using su apps
SilviuMik said:
Press Ok
Otherwise u will get errors while using su apps
Click to expand...
Click to collapse
Worked like a charm! :good: :victory:
Thanks once again from the bottom of my heart to You, dovakinn, gladson1976 and hobbya!!!
bs24 said:
This worked and now I have ROOT!!! Thanks a million everyone, especially dovakinn for that last master stroke!!!!
Is there a way to remove or delete the Supersu icon from the menu? I dont want to uninstall it, just hide the icon without using the native hide/unhide feature. Thanks Again!
Click to expand...
Click to collapse
I know you are already removed/hide your super su icon . But here is also some option
Just install super user elite and switch to ghost mode .
Install nova launcher latest version and hide app from the menu .
Thank you .
Sent from my GT-S7562 using XDA Premium 4 mobile app
AlfasPeralassery said:
I know you are already removed/hide your super su icon . But here is also some option
Just install super user elite and switch to ghost mode .
Install nova launcher latest version and hide app from the menu .
Thank you .
Sent from my GT-S7562 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I have already hidden the Supersu, thanks though for the alternative approach.
A couple of observations though, which may or may not be significant:
1) While installing SuperSu, there was a pop-up on the device which said something like "SuperSu has tried to make changes to your device and was blocked. It gave only 2 options I think (a) Block now or (b) Inform me again after 30 days. I chose option b.
2) I chose to block KNOX when it asked me as soon as I started SuperSu and It gave me a success message.
Now my question is - Will this 30 day counter give a prompt to block supersu again after 30 days?
If someone chooses Yes, then what will happen? Will the device become unrooted or apps needing root become dysfunctional?
I did block KNOX later so shouldn't all these notifications etc not come up anymore. Thanks!!
bs24 said:
Yes I have already hidden the Supersu, thanks though for the alternative approach.
A couple of observations though, which may or may not be significant:
1) While installing SuperSu, there was a pop-up on the device which said something like "SuperSu has tried to make changes to your device and was blocked. It gave only 2 options I think (a) Block now or (b) Inform me again after 30 days. I chose option b.
2) I chose to block KNOX when it asked me as soon as I started SuperSu and It gave me a success message.
Now my question is - Will this 30 day counter give a prompt to block supersu again after 30 days?
If someone chooses Yes, then what will happen? Will the device become unrooted or apps needing root become dysfunctional?
I did block KNOX later so shouldn't all these notifications etc not come up anymore. Thanks!!
Click to expand...
Click to collapse
I didn't see anything like that . Sorrt no answers ....
Sent from my GT-S7562 using XDA Premium 4 mobile app
bs24 said:
Yes I have already hidden the Supersu, thanks though for the alternative approach.
A couple of observations though, which may or may not be significant:
1) While installing SuperSu, there was a pop-up on the device which said something like "SuperSu has tried to make changes to your device and was blocked. It gave only 2 options I think (a) Block now or (b) Inform me again after 30 days. I chose option b.
2) I chose to block KNOX when it asked me as soon as I started SuperSu and It gave me a success message.
Now my question is - Will this 30 day counter give a prompt to block supersu again after 30 days?
If someone chooses Yes, then what will happen? Will the device become unrooted or apps needing root become dysfunctional?
I did block KNOX later so shouldn't all these notifications etc not come up anymore. Thanks!!
Click to expand...
Click to collapse
you have disable knox or remove all files
1 method if you want just disable knox from terminal run cmd as root but knox will remain
su pm disable com.sec.knox.seandroid
Click to expand...
Click to collapse
better way is delete or freeze all knox related files , i used root explorer you could try any app which lets you delete system files , just delete all these
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
KLMS Agent
KNOX
KNOX Notification Manager
KNOX Store
Click to expand...
Click to collapse

[Q] Screen Mirroring Issue On SM-T700

I have a net gear PTV3000 with the latest update. My tablet is rooted with the SkyHigh kernel. I am trying to mirror to the PTV, but it closes the connection and says they are unable to connect due to a hardware issue. How do I fix this?!
I have read of a user reporting same issue in the T700 root thread. Probably root related, but I've never tried it anytime either stock or custom.
Sent from my SM-N9005 using XDA Premium 4 mobile app
UpInTheAir said:
I have read of a user reporting same issue in the T700 root thread. Probably root related, but I've never tried it anytime either stock or custom.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's my issue, I had never tried it stock.
Stupid1337deer said:
That's my issue, I had never tried it stock.
Click to expand...
Click to collapse
I read online that once you root your device you can not use the ptv. so it is because you are rooted you are not able to mirror.
skzunk71 said:
I read online that once you root your device you can not use the ptv. so it is because you are rooted you are not able to mirror.
Click to expand...
Click to collapse
That's pretty apparent, but what can be done about this? We are all pretty smart folks here at xda, any ideas? Anybody willing to tackle this issue.?
Stupid1337deer said:
That's pretty apparent, but what can be done about this? We are all pretty smart folks here at xda, any ideas? Anybody willing to tackle this issue.?
Click to expand...
Click to collapse
The issue has been around for a very long time, including the very popular Note 3 having plenty of development but issue still there. Unlikely to be solved unless by chance. .
Stupid1337deer said:
I have a net gear PTV3000 with the latest update. My tablet is rooted with the SkyHigh kernel. I am trying to mirror to the PTV, but it closes the connection and says they are unable to connect due to a hardware issue. How do I fix this?!
Click to expand...
Click to collapse
U can try the following solution
http://forum.xda-developers.com/showthread.php?p=48166316
If u r planning to apply the fix please inform us if its working
mbushnaq00 said:
U can try the following solution
http://forum.xda-developers.com/showthread.php?p=48166316
If u r planning to apply the fix please inform us if its working
Click to expand...
Click to collapse
I did a little more digging and find it might be possible. Way down on my " to do " list as I don't use it.
UpInTheAir said:
I did a little more digging and find it might be possible. Way down on my " to do " list as I don't use it.
Click to expand...
Click to collapse
Its seems to only happen if your using a non-stock recovery.
Flashing to stock recovery should resolve the issue according to other user's feedback
Hi,
I am having same problems. Running stock rooted ROM with stock recovery.
Anybody found solution?
EDIT:
I tried to find and replace patched library in /system/lib and there is no such library on SM-T700 device :-/
EDIT2:
I found a solution!!!
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:
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
source: http://forum.xda-developers.com/showpost.php?p=54516532&postcount=16
Works on Galaxy Tab S 8.4 but it's little bit laggy (compared to Miracast on BB Q10).
reinstall stock recovery
SM-T705, cf-autoroot, TWRP
After restoring (with Flashify or ADB/dd Methode) stock recovery (still rooted, but of course loosing TWRP) screen mirroring works for me. I even restored TWRP and it still works.
In Odin Mode (Power & Vol- & Home) I see now:
Samsung Official
Custom
Knox 1
But when you boot into TWRP recovery you will loose it again, as status goes to
Custom
Custom
Knox 1
senel said:
Hi,
I am having same problems. Running stock rooted ROM with stock recovery.
Anybody found solution?
EDIT:
I tried to find and replace patched library in /system/lib and there is no such library on SM-T700 device :-/
EDIT2:
I found a solution!!!
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:
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
source: http://forum.xda-developers.com/showpost.php?p=54516532&postcount=16
Works on Galaxy Tab S 8.4 but it's little bit laggy (compared to Miracast on BB Q10).
Click to expand...
Click to collapse
I had the same issue
Many thanks for posting this, it worked a treat for me.
rooted sm-t700 no screen mirroring
senel said:
Hi,
I am having same problems. Running stock rooted ROM with stock recovery.
Anybody found solution?
EDIT:
I tried to find and replace patched library in /system/lib and there is no such library on SM-T700 device :-/
EDIT2:
I found a solution!!!
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:
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
source: http://forum.xda-developers.com/showpost.php?p=54516532&postcount=16
Works on Galaxy Tab S 8.4 but it's little bit laggy (compared to Miracast on BB Q10).
Click to expand...
Click to collapse
I tried this solution but when I select "screen mirroring" tablet doeasn't find the tv, wifi direct connected.. please tell me I have to choose from cwell-cleaned (rooted) tablet and functionality of display!
---------- Post added at 04:16 PM ---------- Previous post was at 04:00 PM ----------
netprospero said:
I tried this solution but when I select "screen mirroring" tablet doeasn't find the tv, wifi direct connected.. please tell me I have to choose from cwell-cleaned (rooted) tablet and functionality of display!
Click to expand...
Click to collapse
I installed Miracast app, in the app you find "wifi connection", activat it, so click now in tablet preferences on "screen mirroring", and now it goes.. without Miracast app active, not. Fortunately my lg smart tv has Miracast in the options, I am not sure it can get on with tv without Miracast.

[APP][ROOT]MultiWindowMod

This is a MultiWindow Mod that allows you to select any apps you want for use with MultiWindow mode. I did not create this, I'm simply sharing it because I can't be the only one who wanted more MultiWindow apps and this is the first place VZW users will check for such a thing, henceforth simplifying the search process. It also doesn't say that it works for G4 but I can personally verify this has worked on my VZW G4 flawlessly. Use at your own risk, as with any root thing, problems can always occur even though 99% unlikely.
Instructions are pretty much unnecessary but I'll state them anyway.
1. Download the APK onto your phone and install it.
2. Open the app and allow root.
3. Select the applications you want for MultiWindowed mode then press Apply.
4. Reboot the phone via the same button where Apply was located.
Originally found this HERE. I'm not sure if he created it, but if someone can verify or tell me who did I will credit them below. - thread by @XabdullahX
Download link: http://www.ayg.dk/FlexMultiWindowMod.apk
Donation Version: https://play.google.com/store/apps/details?id=com.abdulg.flexmultiwindowmod
works perfectly!
Thanks!
Love the app thanks got the donation version thanks!
If you don't want another app, you can just edit the build.prop file (that's what I did):
persist.splitwindow.support_all=false change to true
found here: http://forum.xda-developers.com/show....php?t=3165354
coolgare said:
If you don't want another app, you can just edit the build.prop file (that's what I did):
persist.splitwindow.support_all=false change to true
found here: http://forum.xda-developers.com/show....php?t=3165354
Click to expand...
Click to collapse
I did this and now I'm in a bootloop. Any idea how to correct this?
Worked perfectly(the app did anyway)....to the guy who tried build prop edit. Have u tried a factory reset from your stock recovery? ....a kdz may be in order... Good luck
joeyz400 said:
I did this and now I'm in a bootloop. Any idea how to correct this?
Click to expand...
Click to collapse
You can push files via adb from stock recovery (hold power+voldown). Just push a stock build.prop from a verizon g4 over.
Or factory reset
Deleted
The paid version didn't work for me. I got a file not found error. The free version is no longer on the server.
Sent from my VS986 using Tapatalk
Undue This?
is there anyway to undo this modification? I uninstalled the app but the modification stayed in place. I have previously installed Xposed and it is messing up another Xposed module I am trying to utilize. any help is greatly appreciated. Thanks!
joeyz400 said:
I did this and now I'm in a bootloop. Any idea how to correct this?
Click to expand...
Click to collapse
I tried the unpaid version and would always get a force closed error,
I then modified the build.prop file as above after which it would no long successfully boot (stuck on Verizon splash)
Tried all options:
Safe mode
USB debug mode
Factory data reset
Wipe cache
nothing worked.
Tried to access the build.prop file via ADB but not available in Stock Recovery mode.
Eventually had to KDZ, reroot, and restore from backup via Fireflash
If you are going to try this make sure you have good backup!
Thanks a lot! Just tried the free apk and its working
Sent from my VS986 using Tapatalk

Android q beta 2

Anyone running Android Q beta 2 ? Can you make a comparison to Pie in terms of speed or apps that crash or hang? TIA
I have no apps crashing and no apps unable to start. Performance and battery are identical to Pie.
The Android Q is definitely a daily driver for me.
EDIT: The only single issue I have is that double-tap or lift to wake are not working.
Guys how to root? Android Q?
hfmls said:
Guys how to root? Android Q?
Click to expand...
Click to collapse
Install TWRP. Flash Magisk (canary). Reboot into system. Instal Magisk Manager. Reboot and done.
Will this work on beta 2 ??
spleenandcigars said:
Install TWRP. Flash Magisk (canary). Reboot into system. Instal Magisk Manager. Reboot and done.
Click to expand...
Click to collapse
not work on Beta 2, bro
How best to backout of the AndroidQ beta2?
Installed but Android Auto is playing up so want to go back to v8
Can't mount system partition R/W on Marlin using TWRP 3.2.3-1 once updated to AQB2 (although I did a dirty update by removing the -w erase flag from the bat file before executing.) Guess I'll try nuking everything and rebuilding from scratch to see if the partitions will mount R/W to install Magisk...
Is anyone able to set his own mp3 ringtone on this?
hfmls said:
Guys how to root? Android Q?
Click to expand...
Click to collapse
I'm using this.
https://forum.xda-developers.com/showpost.php?p=79271368&postcount=1282
George_Bushels said:
I'm using this.
https://forum.xda-developers.com/showpost.php?p=79271368&postcount=1282
Click to expand...
Click to collapse
Good Information:
Does it work with Android Q beta DP2 patch (marlin-qpp2.190228.023-factory-c262576d.zip)?
Homeboy76 said:
Good Information:
Does it work with Android Q beta DP2 patch (marlin-qpp2.190228.023-factory-c262576d.zip)?
Click to expand...
Click to collapse
Yes.
sonpro10x said:
not work on Beta 2, bro
Click to expand...
Click to collapse
As you can see in this screenshot, it's working just fine. You have to install the latest Magisk canary build. TWRP won't work to do some backups, but you can flash it fine.
Been running Q2 for a few days and is a great daily driver. As soon as Nova paid was installed I have no complaints
and battery life has been excellent. Coming from the Essential phone rooted this has been a pleasant surprise. For 180.00 new
unlocked on Sprint this is a good deal. I also prefer the 16x9 screen and camera.
So, I have some weirdness going on…
I screwed up and tried to install the last P build after getting the ota beta Q update….i had issues (possibly of my own making).
Realized that trying to go back wasn’t going to work so I thought I would just reinstall the Q beta version 2, I downloaded it…all seemed well until I wanted to get to “settings”
I can pull the “curtain’ down and see a few quick access icons (wifi, Bluetooth, airplane mode…) but it won’t pull farther down (second swipe) to see other options and the “settings” gear at the top. I also don’t seem to be getting notifications, I hear them but don’t see an icon.
I also can’t get to the setting that allow me to transfer files.
Any ideas?
Edit: also can't get to my app drawer...
Edit 2: home button doesn't work either...
I got it, it must have been a bad "dirty flash", did a clean install, and all is working as expected...except,
I've got root but can't see my internal storage with ES file explorer (I can see it when using my PC) (or any other root explorer) and can't edit my build.prop (can't save it)
tufyuma said:
So, I have some weirdness going on…
I screwed up and tried to install the last P build after getting the ota beta Q update….i had issues (possibly of my own making).
Realized that trying to go back wasn’t going to work so I thought I would just reinstall the Q beta version 2, I downloaded it…all seemed well until I wanted to get to “settings”
I can pull the “curtain’ down and see a few quick access icons (wifi, Bluetooth, airplane mode…) but it won’t pull farther down (second swipe) to see other options and the “settings” gear at the top. I also don’t seem to be getting notifications, I hear them but don’t see an icon.
I also can’t get to the setting that allow me to transfer files.
Any ideas?
Edit: also can't get to my app drawer...
Edit 2: home button doesn't work either...
I got it, it must have been a bad "dirty flash", did a clean install, and all is working as expected...except,
I've got root but can't see my internal storage with ES file explorer (I can see it when using my PC) (or any other root explorer) and can't edit my build.prop (can't save it)
Click to expand...
Click to collapse
I did a clean flash, and had the same issue with the internal storage. It was weird though because chrome couldnt see it either, and kept failing to get permission to store files. Doing another Wipe now to try and resolve it...
bonfire62 said:
I did a clean flash, and had the same issue with the internal storage. It was weird though because chrome couldnt see it either, and kept failing to get permission to store files. Doing another Wipe now to try and resolve it...
Click to expand...
Click to collapse
Please let us know if it works....I hardly ever use my hot spot, but it's nice to know I have it for emergencies!
tufyuma said:
Please let us know if it works....I hardly ever use my hot spot, but it's nice to know I have it for emergencies!
Click to expand...
Click to collapse
Wasn't talking about hotspot specifically.... The issue with Chrome is still there, still not able to download anything, as it pops up that it needs permission, I hit continue...and nothing. It normally gives the permission request notification here, but it does not.
bonfire62 said:
Wasn't talking about hotspot specifically.... The issue with Chrome is still there, still not able to download anything, as it pops up that it needs permission, I hit continue...and nothing. It normally gives the permission request notification here, but it does not.
Click to expand...
Click to collapse
Right, I don't think I've tried to download anything with chrome, I want the permissions so I can edit the buildprop file.
Having just checked, I also cannot download anything using chrome, Opera doesn't seem to have a problem, though. I didn't check any other browsers
tufyuma said:
Right, I don't think I've tried to download anything with chrome, I want the permissions so I can edit the buildprop file.
Having just checked, I also cannot download anything using chrome, Opera doesn't seem to have a problem, though. I didn't check any other browsers
Click to expand...
Click to collapse
After clean flash, still having the same issue with the downloads. Going to Solidexplorer shows that the sdcard partition never created a Download folder. Chrome also is completely not working now, so definitely rolling back until it's resolved.

Categories

Resources