Hello everybody
i downloaded openvpn on my galaxy note
then when i start to install it it opens then on the screen there is Binary not installed
it asks me for things like install or exit
i choose install a screen appeared asking to choose target directory
1: /system/xbin
2: /system/bin
if i choose 1
4 options appears
1: /system/xbin/busybox ifconfig
(recommended)
2: /system/xbin/ifconfig
3: /system/xbin/bb/ifconfig
4: /system/bin/ifconfig
i tried every thing but it insists on not to install
please provide me with any thing that helps me install it
or any program similar to it and doing the same job
if there is any video tutorial please post it
Are u rooted??? openvpn requires root...
If u r rooted and face difficulty installing openvpn try droidvpn from market... it is free and easy to use... go to their official site for getting a free account for logging in....
Sent from my GT-N7000 using XDA App
yes, i rooted it
okay i'll try to download that program
thanks
and waiting for anyone who had installed openvpn on his galaxy note to help
7esain said:
yes, i rooted it
okay i'll try to download that program
thanks
and waiting for anyone who had installed openvpn on his galaxy note to help
Click to expand...
Click to collapse
try this
http://vpnblog.info/android-openvpn-strongvpn.html
worked for me without any prob...
both openvpn and droidvpn are working fine in my note
---------- Post added at 12:45 AM ---------- Previous post was at 12:37 AM ----------
7esain said:
Hello everybody
i downloaded openvpn on my galaxy note
then when i start to install it it opens then on the screen there is Binary not installed
it asks me for things like install or exit
i choose install a screen appeared asking to choose target directory
1: /system/xbin
2: /system/bin
if i choose 1
4 options appears
1: /system/xbin/busybox ifconfig
(recommended)
2: /system/xbin/ifconfig
3: /system/xbin/bb/ifconfig
4: /system/bin/ifconfig
i tried every thing but it insists on not to install
please provide me with any thing that helps me install it
or any program similar to it and doing the same job
if there is any video tutorial please post it
Click to expand...
Click to collapse
i think u forgot to install busybox... try installing it first..
thanks mate for helping
now i did everything except one
i can't install the tap/tun driver
i don't knew where to find?
7esain said:
thanks mate for helping
now i did everything except one
i can't install the tap/tun driver
i don't knew where to find?
Click to expand...
Click to collapse
i dont think ul b needing it... i think its already compiled in stock firmware... if u r having any trouble... try installing abyss kernel from development section... then go to market and install tun.ko app and install tun.ko from there...
P.S. dont forget to check the insmod option in advanced options of openvpn...
hope it will work for u this tym
How to root galaxy note and install openvpn
Dear Sandeep,
Could you please share the steps to root the galaxy note and install openvpn on it?
Model: GT-N7000
Android Version: 2.3.6
Baseband Version: N7000XXLA4
Kernel Version: 2.6.35.7-N7000XXLA6-CL907341
[email protected] #2
Build Number:
GINGERBREAD.XXLA6
solved openvpn installer problem, solved routing issues
I just installed openvpn on my GNote N7105 running stock 4.1.1 but rooted
The problem I solved was that openvpn* installer couldn't find busybox, but I have a good on in /data/local/bin, so I remounted / as read-write and made a link at /system/xbin/busybox to /data/local/bin/busybox
Then the installed couldn't find the "cp" command to copy the binary over, so I made a in in /system/xbin from busybox to cp
And then the openvpn installer ran OK but didn't see my openvpn configs and keys.
Because I moved from non-samsung device I had to move my openvpn files from /storage/extSdCard to the "internal" card.
And then the openvpn installer allowed me to start up openvpn. And I saw a tun0 device. But no traffic flows over the VPN. I checked the routing tables (main, default, local) and tried adding routes but no luck
So I searched xda devs and found this thread.
Any idea please?
--EDIT--
I restarted the openvpn server on the remote linux box and everything started working. I realised there was a problem when I used tcpdump and could see ping requests going over the tunnel to the server and nothing coming back. My laptop could also bring up the tunnel and also not send/receive traffic.
* https://play.google.com/store/apps/details?id=de.schaeuffelhut.android.openvpn
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.
Hello there people so i'm an Huawei phone user and I have always wanted to root my mate 20 lite and the thing is nobody got info how to do it but anyways I My self got an 100 euro hydra tool and therefore I'm trying to unlock the bootloader and I came to one place where I saw data about my phone and it freaking says My phone is rooted but the problem is how did it do it by itself and why can't apps see that my phone is rooted. I'll give you the log:
Starting ADB Server....
Searching Device By ADB
Device Found...
Model : SNE-LX1
Brand : HUAWEI
Android Ver : 10
CPU abi : arm64-v8a
Software Version :
CSC Version :
Bootloader :
Board : SNE
Display ID : SNE-LX1 10.0.0.232(C432E10R1P1)
Security Patch : 2020-07-01
Emmc_size :
Platform : kirin710
Kernel ID : 2020-07-01
Marketname :
OTA Version Name :
SYS USB CONFIG : persist.hisuite,mtp,mass_storage,adb,hdb
FRPPST : /dev/block/bootdevice/by-name/frp
FingerPrint : HUAWEI/SNE-LX1/HWSNE:10/HUAWEISNE-L21/10.0.0.232C432:user/release-keys
Checking Root Status....
Root Status : Rooted
Root Version : /system/bin/sh: su: inaccessible or not found
As you can see Root version is unknown or its lost but it shows its working. Maybe some people got some idea or some clue what I could do.
Thank you!
I don't understand exactly what you did, but the device doesn't appear to been rooted (maybe is just a bug that shows the "rooted" status, but without su is not rooted at all.
There is no way to root without unlock the bootloader - what is not possible in almost any Huawei device.
I'm using a rooted S21 Ultra. I'm on stock android.
It's been rooted for 1.5 years and there were no issues. A couple of months ago the attached popup started to appear. I press ok and it goes away. This can happen between once every 2-3 days to a couple times a day.
There were no significant changes on the device when this started, so I have no idea what caused this to appear.
On my searches I read that it could be the Samsung Health app, so I I installed it, but that didn't help. I guess it's another Samsung app? But which?
Right now I'm running A13, but this started a couple of months back when I was running A12. The upgrade didn't change that.
Any leads on this?
sagybp said:
There were no significant changes on the device when this started, so I have no idea what caused this to appear.
Click to expand...
Click to collapse
Yes there were, you rooted your phone. That's a "significant change".
sagybp said:
On my searches I read that it could be the Samsung Health app, so I I installed it, but that didn't help. I guess it's another Samsung app? But which?
Click to expand...
Click to collapse
A number of Samsung apps will check for root/Knox status, and since Knox is hardware based (i.e. trip it once, and it's tripped forever), even if you return to complete stock, these apps won't work.
It's mainly the apps whose data security heavily depends on the phone's root status (even if it's currently unrooted, it's been 'compromised'), so Samsung Health, Secure Folder, etc. are the main culprits for such a message. However it's possible that Samsung added a system-level check that causes the pop-up.
fonix232 said:
Yes there were, you rooted your phone. That's a "significant change".
Click to expand...
Click to collapse
I will clarify again. My phone was rooted for about 16 months before this message showed up. It's been rooted 1.5 years and the message is here for 2 months. This is what I meant when I said no significant changes before the message appeared.
I have the same problem when I first bought the phone, I rooted it, then I unrooted it, but because knox was triggered, android 12 was not coming out, so it started to appear after I made the CSC change. android 13 e upgrade
Someone had a discussion on this link last month, so I wrote it, but no one answered.
How to fix "Access denied" screen randomly appearing on rooted devices
A couple of days ago my S21 Ultra running G998BXXS5CVIF automatically opened an "Access denied" screen. It was impossible to show which app cause it as it disappeared once you got to the app switcher menu. Access denied Unauthorized changes...
forum.xda-developers.com
For rooted
Delete System/priv-app/DigitalKey + uninstall update
OR
Execute this from terminal
Code:
adb shell
su
pm hide com.samsung.android.dkey
For unrooted
You can try disable appears on top permission for digital key app
The phone is not rooted, is there a non-rooted solution? @dr.ketan ?
Can you explain in more detail what programs should be used to do what you wrote?
musakamis said:
The phone is not rooted, is there a non-rooted solution? @dr.ketan ?
Click to expand...
Click to collapse
Edited above
In case that doesn't work try this with adb shell on PC
Code:
pm uninstall com.samsung.android.dkey
musakamis said:
Can you explain in more detail what programs should be used to do what you wrote?
Click to expand...
Click to collapse
For permission you don't need third party app
Open settings - apps - enable show system app - search Digital Key and disable show on top permission
Settings / apps / private access / show on top / Samsung wallet digital key is it correct? Dear @dr.ketan
B I got results by following this way, I recommend it.
dr.ketan said:
For permission you don't need third party app
Open settings - apps - enable show system app - search Digital Key and disable show on top permission
Click to expand...
Click to collapse
I can't see the digital key app. I'm on android 13 and don't see enable show system app option. thanks your help will be appreciated
musakamis said:
B I got results by following this way, I recommend it.
Click to expand...
Click to collapse
which method did you follow?
Settings/apps/private access/Samsung wallet digital/tap to disable show on top access denied window won't pop up again
musakamis said:
Settings / apps / private access / tap on Samsung wallet digital turn off show on top access denied window won't open again
Click to expand...
Click to collapse
I don't see private access in apps only private share?
senin için video çektim ama yükleyemem özelden atarım tamam
musakamis said:
senin için video çektim ama yükleyemem özelden atarım tamam
Click to expand...
Click to collapse
cheers