Linux – Bluetooth virker ikke

Asus x75v

Installer rtbth-dkms (AUR)

$ sudo systemctl start bluetooth
$ sudo rmmod rtbth
$ sudo modprobe rtbth
$ sudo bluetoothctl

blacklist module

$ sudo echo 'blacklist rtbth' > /etc/modprobe.d/ralink-bt.conf

opret script indlæsning og start af rtbth modul

$ sudo touch /usr/local/sbin/rtbth
$ sudo vi /usr/local/sbin/rtbth
#!/bin/bash
sleep 5
/sbin/modprobe --ignore-install rtbth;
/usr/bin/mknod /dev/rtbth c 192 0;
/usr/bin/rtbt &

opret system service

$ sudo touch /etc/systemd/system/rtbth.service
$ sudo vi /etc/systemd/system/rtbth.service
[Unit]
Description=Fix rtbth bluetooth after gmd start
After=display-manager.service
[Service]
Type=oneshot
ExecStart=/usr/local/sbin/rtbth
TimeoutSec=0
RemainAfterExit=true

[Install]
WantedBy=multi-user.target

aktiver service

$ sudo systemctl enable rtbth

Linux – WiFi hardware virker ikke

Laptop hacks

Der kan være forskellige årsager til blokeringen af wifi og/eller bluetooth.
Det første der prøves er Fn+icon made by FreePik. Hvis dette ikke aktiverer WiFi bruges rfkill for at vise status – eksempel output

rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
    Soft blocked: no
    Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
    Soft blocked: yes
    Hard blocked: no
2: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
3: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

Hvis wireless status er “Hard blocked: yes”

rfkill unblock all

Asus x75v hacks

Er modulet for funktionstaster (Fn+F2) asus_nb_wmi indlæst? Check:

lsmod | grep asus

Hvis det er – prøv med driver parameter:

sudo -i
echo "options asus_nb_wmi wapf=0" > /etc/modprobe.d/asus.conf
exit

Genstart og kontroller om Fn+F2 det fungerer.

Hvis ovenstående ikke havde nogen effekt gentag ovenstående på denne måde

echo "options asus_nb_wmi wapf=1" > /etc/modprobe.d/asus.conf

Prøv med denne hvis det stadig ikke virker

echo "options asus_nb_wmi wapf=4" > /etc/modprobe.d/asus.conf

ASUS – rooting MeMO Pad 7 (ME572C)

Rooting device ASUS MeMO Pad 7

http://forum.xda-developers.com/memo-pad-7/help/how-to-root-asus-memo-pad-7-me572c-2014-t2915779

Some information [MeMOPad] ME572C of

Talk about the boring part:

Intel Z3560 / Z3580’s CPU, boot.img / fastboot.img / recovery.img of HEAD_PADDING back UNKNOWN_SIZE is 728 bytes, but BOOTSTUBSTACK_SIZE is 8192 bytes.
RootZenFone change it to use, and then release a small update late.
Inside sideload recovery is bad, adb port can not open, when to get there to do a software update or not repaired, guess should not want people to use it? fastboot there SD Download, it seems the future of factory image will be .raw format.
The more interesting part:

fastboot there is a small back door, can be used to do the root of the application:

fastboot oem mount
The first instruction is to mount partitions on the phone, will be mounted at / mnt / data folder, so I’m going to mount the system is ext4 fastboot oem Mount system , that is, you want to mount userdata fastboot oem mount data ext4 can.

fastboot flash The second instruction is to update the information on the phone route, originally only update existing files , but here I do not know why is modified to replace the existing file or upload , it is very interesting, root application ready. Because it is 4.4 and there is open SELinux, so the best way to modify the existing shell file will be executed, when it related to root after the brush into the program to reboot automatically go into.

The idea is simple:

fastboot oem Mount system ext4
fastboot Flash / mnt / system / xbin / su su
Flash /mnt/system/etc/install-recovery.sh install-recovery.sh fastboot
fastboot Flash /mnt/system/Superuser.apk Superuser.apk
Then find a .sh file can be used to modify the plug plug back in the boot judgment if no /system/etc/.installed_su_daemon run the installation program, produced /system/bin/.ext/ , / system / bin /. ext / su , / system / xbin / sugote , / system / xbin / sugote-mksh , / system / xbin / daemonsu …