first of all you need root and Lineage os 14 (not sure if must)
then connect your phone to pc and install ADB
open cmd and type
1.cd C://adb
2.adb shell
3.su
4 can be pasted in one line
mount -o rw,remount /system
echo '<?xml version="1.0" encoding="utf-8"?><permissions><feature name="android.hardware.vr.high_performance" /></permissions>' > /system/etc/permissions/android.hardware.vr.high_performance.xml
echo '<?xml version="1.0" encoding="utf-8"?><permissions><feature name="android.software.vr.mode" /></permissions>' > /system/etc/permissions/android.software.vr.mode.xml
chmod 644 /system/etc/permissions/android.hardware.vr.high_performance.xml
chmod 644 /system/etc/permissions/android.software.vr.mode.xml
mount -o ro,remount /system
pm clear com.google.android.gms
pm clear com.android.vending
reboot
install daydream from the playstore after you reboot and launch it ta dam daydream VR is working perfectly
note to self= it works for me only on the lineage os 14.1 custom rom so i prefer you to install that lineageos its great
??
Related
My S2 is on LA2 with the corresponding CF-ROOT. Since I upgraded to LA2, adb is unable to push a file to /system/app. In this case, I need to push Widgetsoid to /system/app or else I lose all widgets after a reboot. Before LA2, I pushed with adb just fine, but now my push command returns the error "failed to copy: no space left on device." I'm able to push to /mnt/sdcard and my device has plenty of room. I assume, then, that adb is failing to mount the directory for writing. But my adb command "mount -o rw,remount /system" returns with no error. Any suggestions how to re-enable push access to /system/app with current CF-ROOT?
My full procedure for pushing is this:
Code:
> adb shell
> su
# mount -o rw,remount /system
# chmod 777 /system
# chmod 777 /system/app
# exit
> exit
> adb push ApkFileName.apk /system/app/
> adb shell
> su
# chmod 755 /system
# chmod 755 /system/app
# exit
> exit
> adb reboot
Emm /system space is different from phone space.
You need to delete some apps in system b4.
Like zinio.apk etc
Red_Vex said:
Emm /system space is different from phone space.
Click to expand...
Click to collapse
I didn't know that. that fixed it
- Root devices
Code:
adb shell
su
mount -o remount,rw /system
rm /system/csc/language.xml
reboot
Or
Code:
adb shell
su
mount -o remount,rw /system
mv /system/csc/language.xml /system/csc/language.xml.bak
reboot
Done
Hey everyone,
I am a new member and I haven't ever developed anything for Android, even though I am a CS major, thus I am not very familiar with kernels , bootloaders and recoveries.
Anyway, I decided that I wanted BlueStacks on my computer. I have been going through a variety of Android emulators and this is the one interface I like the most.
I have downloaded the pre-rooted version of BlueStacks 2.0.0 (from here: http://forum.xda-developers.com/wiki/BlueStacks_App_Player) and I have downloaded some apps to check if it was rooted, in fact. And yes, it is, but it doesn't have SuperSU installed.
I have then tried to install SuperSU. But once I click on SuperSU icon I get an error message "There is no binary SU installed and SuperSU cannot install it .... " and it suggests to install SuperSU manually.
Since then I have been reading a little about how Android boots and I have tried some apps like RecoveryReboot, QuickBoot, etc. None of them work. I have tried to find ways to see if the BootLoader is locked or to discover if the system has or doesn't have a recovery but no luck. I believe there's no recovery mode available.
Instead of going through the kernel and bootloader (which I am not familiar with and would take me ages to figure out) I decided to look for alternative ways.
I have found this apk: http://forum.xda-developers.com/showthread.php?t=2250555 which looked promising because it would allow me to install SuperSU without going through recovery mode. But, unfortunately, after selecting the zip file with SuperSU, I receive an error saying that this package is not a flashable zip.
Anyway, instead of keep looking, I was wondering if anyone has an idea of a way to install SuperSU in this version of BlueStacks.
I know that some previous versions have SuperSU installed by default, but I like BlueStacks 2 interface and some functionalities better.
Thank you!
How to install SuperSU and root BlueStacks 2.0.x.x manually
I'm a total noob when it comes to android but somehow I've managed to root latest 2.0.8.5638 with trial and error method Here is what I've done. I'm not sure if its the right way tho
1. Download SuperSU 2.46 from their site or download this: https://dl.dropboxusercontent.com/s/v5kje7gsb9q3pp8/tmp.7z?dl=1 I've only added necessary files in the zip.
Open cmd and push this files to BlueStacks. If you've downloaded complete supersu package then you'll need "libsupol.so, su, supolicy" from "x86" folder and "Superuser.apk" from "common" folder. You'll also need adb installed and added to your environment variable path or you can use "C:\Program Files (x86)\BlueStacks\HD-Adb.exe" instead of adb...
Code:
adb push xbin\su /data/local/tmp
adb push xbin\supolicy /data/local/tmp
adb push lib\libsupol.so /data/local/tmp
adb push app\Superuser.apk /data/local/tmp
2. Run adb shell in cmd
Code:
adb shell
And type this in shell, it will grant you root permission. They left this and also busybox in latest versions.
Code:
/system/xbin/bstk/su
3. Remount with rw rights. Not sure about first and last though, /dev/sda1 /system is necessary.
Code:
mount -o rw,remount /dev/block/sdb1 /data
mount -o rw,remount /dev/sda1 /system
mount -o rw,remount / /
4. cd to /data/local/tmp and give these permissions below to files.
Code:
cd /data/local/tmp
chmod 0775 su
chmod 0775 supolicy
chmod 0664 libsupol.so
chmod 0664 Superuser.apk
5. Move/copy this files.
Code:
cp su /system/xbin/su
cp su /system/xbin/daemonsu
cp supolicy /system/xbin/supolicy
cp libsupol.so /system/lib/libsupol.so
cp Superuser.apk /system/app/Superuser.apk
6. You have to edit init.sh file. You can do it with vi
Code:
busybox vi /system/etc/init.sh
Scroll down to end of script.
You'll see something like this.
Code:
init|"")
do_init
;;
esac
change it to
Code:
init|"")
do_init
/system/xbin/daemonsu --auto-daemon &
;;
esac
then exit with ":wq!"
or alternatively you can copy that file to bluestacks shared folder and edit it with your text editor then copy it back. Its easier this way.
Code:
cp /system/etc/init.sh /storage/sdcard/windows/BstSharedFolder/init.sh
edit init.sh file in "C:\ProgramData\BlueStacks\UserData\SharedFolder" then copy it back to BlueStacks.
Code:
rm /system/etc/init.sh
cp /storage/sdcard/windows/BstSharedFolder/init.sh /system/etc/init.sh
P.S. if you use "cp -f" you may not need to write "rm" command, haven't tried it myself. Like I said, noob here
Ok, now you should have root access.
You may want to install apps like apex launcher, root explorer etc. Then you can uninstall BlueStacks' bloatware if you want.
::bluestacks things
Code:
rm /mnt/prebundledapps/com.google.android.apps.photos-1.apk
rm /mnt/prebundledapps/downloads/BstFakeGps.apk
rm /mnt/prebundledapps/downloads/MyBluestacks.apk
rm /mnt/prebundledapps/downloads/bluestacksHome.apk
rm /mnt/prebundledapps/downloads/bluestacksServices.apk
rm /mnt/prebundledapps/downloads/newAppFinder.apk
rm /mnt/prebundledapps/downloads/setupWizard.apk
rm /data/downloads/AppGuidance.apk
rm /data/downloads/AppSettings.apk
rm /data/downloads/BstFakeGps.apk
rm /data/downloads/MyBluestacks.apk
rm /data/downloads/S2P.apk
rm /data/downloads/bluestacksHome.apk
rm /data/downloads/bluestacksServices.apk
rm /data/downloads/newAppFinder.apk
rm /data/downloads/setupWizard.apk
7. Remount with readonly again.
Code:
mount -o ro,remount /dev/sda1 /system
mount -o ro,remount / /
8. Don't know what it does but I've seen it on some instructions
Code:
sync
9. Open a cmd with admin rights and kill BS2 completely then open it again.
Code:
taskkill /f /t /im "BlueStacks.exe" /im "HD-Agent.exe" /im "HD-Adb.exe" /im "HD-BlockDevice.exe" /im "HD-FrontEnd.exe" /im "HD-Network.exe" /im "HD-Service.exe" /im "HD-SharedFolder.exe" /im "HD-UpdaterService.exe" /im "HD-LogRotatorService.exe"
10. Open SuperSu app in BS2, it may want you to update su binaries. Update it with normal option and restart it. Use taskkill way to completely kill it again.
11. Run adb shell again. You may need to run "adb kill-server" command first.
12. Run "adb shell" command then type "su". SuperSu will want grant permission approval for shell. Give it and now you should have a rooted BS2
Hi guys,
I am using a Huawei T1-701u. I can consistently get root using iovyroot. I have added all the firmwares I can find and created a pull request.
There seems to be some sort of protection on the system partition however. This manifests in two ways. Firstly changes to the partition are magically reverted on reboot. Secondly, I sometimes get an error when mounting /system as rw saying it is readonly.
I have some scripts up on GitHub: /chrisfraser/HuaweiRoot (Sorry you have to search. This is my first post). This eventually works, but it is indeterminate. Sometimes it works first time. Other times it can take 20 tries. Below is the important remount code.
Code:
install_perm() {
cat $1 > $2
chown 0.0 $2
chmod 755 $2
}
echo '[*] Starting root install'
mount -o rw,remount /system
setenforce 0
install_perm $BIN/su /system/xbin/su
install_perm $BIN/su /system/xbin/daemonsu
install_perm $BIN/install-recovery.sh /system/etc/install-recovery.sh
ln -s /system/etc/install-recovery.sh /system/bin/install-recovery.sh
mount -o ro,remount /system
sync
echo '[*] Root install complete, rebooting'
sleep 5
reboot
Thanks in advance
Hi guys I've installed kali nethunter on my old smartphone and I have a problem with the terminal. When I try to boot kali with command: bootkali, I recive an error message about permission despite I use root terminal. I have a moto g 2gen and I've done a downgrade from marshmellow to lollipo to use kali nethunter's version for nexus 4. I've tryed also the version for nexus 5 mashmellow before downgrade but It gives me an error while installing chroot. Anyone can helpme to solve the problem or simply I can't use kali on my old phone?
Terminal:
[email protected]_umtsds: / # bootkali
tmp-mksh: bootkali: can't execute: Permission denied
Try setting the permissions to 755 as root. Like this:
mount -o rw,remount /system #mount /system rw
cd /system/bin/ #change dir
chmod 755 bootkali #set permission rwxr-xr-x
mount -o ro,remount /system #mount /system ro