SliTaz Forum
You are not logged in.
Ciao a tutti, voglio condividere con voi questa mia esperienza con slitaz arm.
In pratica l'ho fatto girare così com'è su di un tablet android.
Non so se la cosa possa essere replicabile su altri, ma visto che parecchie distro concorrenti hanno un suo sviluppo su android, che credo la cosa possa suscitare interesse all'esperimento.
Come per le concorrenti serve android roottato, come farlo non starò qui a spiegarlo, la rete offre guide a non finire perciò non perderò altro tempo a riscrivere quello che c'è già fatto.
Oltre al root su android serve un emulatore di terminale, più il pacchetto x sdl server installato.
Preparatevi una micro sd formattata in ext3... sì ext3... non so se sia importante ma così ho fatto.
Sul pc scaricatevi il tarball di slitaz-rpi-desktop-20140329 e scompattatelo in una cartella temporanea.
Cercate nel suo contenuto la cartella rootfs, entrateci dentro e tramite terminale copiate tutto il contenuto nella root della vostra sd.
Ora modificate leggermente il contenuto della sd creando due cartelle in /root
.config e .config/slitaz (in pratica la cartella slitaz dentro .config). poi copiateci dentro il file dalla cartella etc/slitaz/applications.conf
chiudete tutto e trasferite la micro sd nel tablet.
Avviate android e collegatevi in wireless al router (o qualunque altra rete disponibile)
aprite il terminale e date questi comandi
su
mkdir /data/linux
mount -t ext3 -rw /dev/block/mmcblk0p1 /data/linux
mount -o bind /proc /data/linux/proc
mount -o bind /sys /data/linux/sys
export USER=root
export HOME=/root
busybox chroot /data/linux /bin/sh –login
se avete fortuna come me siete in chroot in slitaz
così
[attachment=40202,2100]
ora aprite dal tablet xsdl server. Una volta avviato avrete l'indirizzo utile per dirottare xorg.
Tornate nel terminale e date
export DISPLAY=192.168.0.132:0 (chiaramente questo è il mio caso)
startx
e tornate su xsdl server e godetevi lo spettacolo.
[attachment=40202,2101]
[attachment=40202,2102]
[attachment=40202,2103]
[attachment=40202,2104]
Una volta che tutto funziona per semplificare basta crearsi uno script che ripeta tutti questi comandi
mount -o bind /proc /data/linux/proc
mount -o bind /sys /data/linux/sys
export USER=root
export HOME=/root
busybox chroot /data/linux /bin/sh –login
ve lo salvate in una cartella comoda su android e dopo aver preso i diritti di root lo lanciate dal terminale.
Provo a ripetere le stesse cose con il mio inglese maccaronico....
Hi at all, it is my first experience to try run slitaz-arm on android tablet.
Requisite: Android s.o. Rooted, x server sdl, terminal emulator, and micro sd formatted on ext3... yes at ext3, but not so is very important....
From my pc have downloaded the tarball slitaz-arm (slitaz-rpi-desktop-20140329)
create folder temporary and inside have extracted the tarball
put microsd on usb adaptor, and format on ext3
mount sd (on my case /dev/sdb1 on /media/disk-1)
entry on temporary folder and search subfolder root. Open terminal on this folder and then this command
su > root
mkdir root/.config
mkdir root/.config/slitaz
cp etc/slitaz/applications.conf
cp -ar * /media/disk-1 (note this is my mount point on sdb1)
close terminal and umount microsd
put sd on Android tablet and press poweron
connect tablet to wifi network
open terminal emulator and then
su
mkdir /data/linux
mount -t ext3 -rw /dev/block/mmcblk0p1 /data/linux
mount -o bind /proc /data/linux/proc
mount -o bind /sys /data/linux/sys
export USER=root
export HOME=/root
busybox chroot /data/linux /bin/sh –login
open x sdl server and copy the ipaddress suggested
return on terminal and then
export DISPLAY=192.168.0.132:0 (this is on my case)
startx
return on x sdl server
enjoy
Offline
Bel lavoro gibor! Figurati che io non sono mai riuscito a far partire slitaz arm su Raspberry Pi..
Offline
Ti ringrazio degli apprezzamenti...
io non sono mai riuscito a far partire slitaz arm su Raspberry Pi..
...e se ne hai tempo e voglia di fare un riscontro, magari qui stavolta ti potrebbe andar meglio.
Offline
Very cool!! I am thinking about all the possibilities it opens.
Thank you for this post
Offline
@gibor
Great.
Android Debug Bridge (adb)
AArch64 Processor (aarch64)
1.
tux@slitaz:~ $ uname -a
Linux slitaz 3.2.71-slitaz64 #2 SMP Sat Oct 10 15:35:50 CEST 2015 x86_64 GNU/Linux
2.
tux@slitaz:~ $ adb version
Android Debug Bridge version 1.0.31
3.
tux@slitaz:~ $ lsusb | grep ASUS
Bus 001 Device 003: ID 0b05:5f03 ASUSTek Computer, Inc.
tux@slitaz:~ $ lsusb -v | grep -A 15 0b05:5f03
Bus 001 Device 003: ID 0b05:5f03 ASUSTek Computer, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0b05 ASUSTek Computer, Inc.
idProduct 0x5f03
bcdDevice ff.ff
iManufacturer 1 Android
iProduct 2 Android
iSerial 3 F9AXXXXXX714
bNumConfigurations 1
4.
tux@slitaz:~ $ adb shell
shell@ASUS_Z00E_2:/ $ uname -a
Linux localhost 3.10.49-perf-gd1c5ee8 #1 SMP PREEMPT Mon Oct 26 16:13:26 CST 2015 aarch64 GNU/Linux
5.
shell@ASUS_Z00E_2:/ $ cat /proc/cpuinfo
Processor : AArch64 Processor rev 0 (aarch64)
processor : 0
processor : 1
processor : 2
processor : 3
Features : fp asimd crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 0
Hardware : Qualcomm Technologies, Inc MSM8916
shell@ASUS_Z00E_2:/ $
[attachment=40383,2139]
Offline
ZE500KL / Z00E
Platform OS Android OS, v5.0 (Lollipop), planned upgrade to v6.0 (Marshmallow)
Chipset Qualcomm MSM8916 Snapdragon 410
CPU Quad-core 1.2 GHz Cortex-A53
GPU Adreno 306
Linux localhost 3.10.49-perf-gd1c5ee8 #1 SMP PREEMPT Mon Oct 26 16:13:26 CST 2015 aarch64 GNU/Linux
Processor : AArch64 Processor rev 0 (aarch64)
CPU architecture: 8
Hardware : Qualcomm Technologies, Inc MSM8916
1.
tux@slitaz:~ $ adb devices
List of devices attached
F9AXXXXXX714 device
2.
tux@slitaz:~ $ adb shell
shell@ASUS_Z00E_2:/ $ su
3.
root@ASUS_Z00E_2:/ # grep -Ei '500kl|z00e|abi|8916' /system/build.prop
ro.product.model=ASUS_Z00ED
ro.product.device=ASUS_Z00E_2
ro.product.board=msm8916
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.board.platform=msm8916
ro.build.product=ZE500KL
ro.build.fingerprint=asus/WW_Phone/ASUS_Z00E_2:5.0.2/LRX22G/12.8.5.156-20151026:user/release-keys
ro.build.csc.version=WW_ZE500KL-12.8.5.156-20151026
# from device/qcom/msm8916_64/system.prop
# system.prop for msm8916
# [ASUS BSP] Jacob Kung - ZE500KL support golve mode property
# [ASUS BSP] Jacob Kung - ZE500KL support double tap mode property
# [ASUS BSP] Jacob Kung - ZE500KL support gesture mode property
# [ASUS BSP] Jacob Kung - ZE500KL support flipcover mode property
# [ASUS BSP] Jacob Kung - ZE500KL default enable touch check proximity before gesture wake up
#Set for msm8916
ro.asus.browser.uap=ASUS-ZE500KL
root@ASUS_Z00E_2:/ #
[attachment=40485,2143]
Offline
Hi alanyih thank for your effort, but sorry, on linux i'm simply noob, and this code cannot clear for me.
I have tried at installer of lxde, but from packages manager “spk” more dependency are missed 
first at all libmenu-cache.
Anyway even searching to compile new packages on arm, but not have success. I have read your post on this forum http://forum.slitaz.org/topic/slitaz-arm but they cannot understand mode to cross compile arm packages....
Both having a difficult to speak on english, if you to want get me contribute at clear this question, please put the complete shell output of terminal on http://pastebin.com/ on this mode view all step of the preparation the one system slitaz (x86 32bit) ready to make cross/compile new source of packages on arm.
Thank at you, and at all posting on this queston 
Offline
slitaz-on-armel
http://forum.slitaz.org/topic/slitaz-on-armel#post-28097
Offline
What is the iter to cross compile pakages arm on system i386?
Chroot at suggested at link over fakeroot arm?
over qtemu-arm?
or direct run compile from device arm?
This is the output terminal of command suggested
tazdev gen-chroot --arch=arm
Generating new chroot in : /home/slitaz/--arch=arm/chroot
================================================================================
Creating /home/slitaz/--arch=arm/chroot/var/cache/tazpkg... [ OK ]
Creating /home/slitaz/--arch=arm/chroot/var/lib/tazpkg/installe......................................
.
.
.
.............................Creating resolv.conf... [ OK ]
================================================================================
Ready to chroot. Use 'tazdev chroot [version|path]'
Example: tazdev chroot /home/slitaz/--arch=arm/chroot
root@slitaz:/home# tazdev chroot --arch=arm
Mounting virtual filesystems... [ OK ]
Chrooting to: /home/slitaz/--arch=arm/chroot
root@slitaz:/# root@slitaz:/# wget http://mirror.slitaz.org/packages/cross/
Connecting to mirror.slitaz.org (188.165.229.172:80)
root@slitaz:/# root@slitaz:/# tar xjf slitaz-cross-arm-toolchain*.tar.bz2
tar: can't open 'slitaz-cross-arm-toolchain*.tar.bz2': No such file or directory
root@slitaz:/#
first problem cannot find tar.bz2....
what is wrong?
Offline
Cross compilation
Last modified: 2011/05/26 19:23 by linea
http://doc.slitaz.org/en:cookbook:cross
chroot
http://forum.slitaz.org/topic/chroot
cross-compile VS. native compile
http://forum.slitaz.org/topic/slitaz-on-armel#post-27862
root@slitaz:/# root@slitaz:/# wget http://mirror.slitaz.org/packages/cross/
tar: can't open 'slitaz-cross-arm-toolchain*.tar.bz2': No such file or directory
/# wget http://mirror1.slitaz.org/packages/cross/slitaz-arm-toolchain-20140304.tar.bz2
Offline
Thank for the link, but I have on my head more more confusion.
From my distro have put on /usr/local the slitaz-armhf-cross-toolchain.
And test command obtain
tux@slitaz:~$ arm-slitaz-linux-gnueabi-gcc -v
Using built-in specs.
COLLECT_GCC=arm-slitaz-linux-gnueabi-gcc
COLLECT_LTO_WRAPPER=/usr/local/bin/../lib/gcc/arm-slitaz-linux-gnueabi/4.6.3/lto-wrapper
Target: arm-slitaz-linux-gnueabi
Configured with: ../gcc-4.6.3/configure --prefix=/cross/arm/tools --libexec=/cross/arm/tools/lib --target=arm-slitaz-linux-gnueabi --enable-shared --enable-c99 --enable-long-long --enable-__cxa_atexit --with-system-zlib --enable-plugin --disable-multilib --disable-libssp --disable-checking --disable-werror --with-pkgversion=SliTaz --with-bugurl=https://bugs.slitaz.org/ --with-sysroot=/cross/arm/sysroot --enable-languages=c,c++
Thread model: posix
gcc version 4.6.3 (SliTaz)
first test to compile packages:
downloaded source of nano-2.5.0 and have extracted the tarball
open terminal on this folder and then
./configure
make CC=arm-slitaz-linux-gnueabi-gcc
and obtain this error
/usr/local/bin/../lib/gcc/arm-slitaz-linux-gnueabi/4.6.3/include-fixed/limits.h:169:61: fatal error: limits.h: No such file or directory
compilation terminated
…. totally wrong or where is the problem?
Thank in advance.
Offline
Hi,
Maybe the configure script is confused by the coexistence of your regular distro and the arm tools. That's why you should work in a chroot, as shown by alanyih.
You can download the package directly from the chroot, or from your standard system then copy it into the chroot. (The chroot contents can be seen from the standard system, but the standard system contents cannot be seen from the chroot.)
Offline
Hi llev, but this tool is for cross compilation, or to chroot compilation... anyway
Ok have removed from my standard system the local folder of tool slitaz-armhf-cross-toolchain.
Have tried at so far, but no to done...
New repeat this command
tazdev gen-chroot –arch=arm
wget http://mirror1.slitaz.org/packages/cross/slitaz-arm-toolchain-20140304.tar.bz2
tar -xvf slitaz-arm-toolchain-20140304.tar.bz2
at least on /home have this folder
slitaz (created by tazdev to chroot arm)
slitaz-arm-toolchain-20140304 (uncompressed tool arm)
tux (my regular home)
on folder slitaz/--arch-arm/chroot have one sysroot (alias root of chroot, or fakeroot for my Android device)
on folder slitaz-arm-toolchain-20140304 have a tool and another sysroot
on this tool where folder to move on chroot folder? Important specified whats folder to move (please)
after this if is good then tazdev chroot –arch=arm and chroot on slitaz/--arch-arm/chroot and tried to compile from source nano for armel.
Offline
From my distro have put on /usr/local the slitaz-armhf-cross-toolchain.
Don't change the PATH /cross.
2.
root@slitaz:/# cat /cross/README
http://forum.slitaz.org/topic/chroot/page/2#post-25013
SliTaz Prebuilt arm cross toolchain
================================================================================
Move this arm cross compilation toolchain to /cross then add tools
to your PATH environment and test the toolchain:
# mv arm /cross
# export PATH=$PATH:/cross/arm/tools/bin
# echo 'int main() { return 0; }' > test.c
# arm-slitaz-linux-gnueabi-gcc -v -o test.out test.c
# readelf -h test.out
================================================================================
Offline
Yes, on the final step compile arm binary work!!! Thank you Alanyih
Summarizing preparation of standard system (slitaz x86) for the gnu cross compile
create on standard root (/) the folder cross (/cross)
download the tool (http://mirror1.slitaz.org/packages/cross/slitaz-arm-toolchain-20140304.tar.bz2) and extract. From this tool extracted move the folder arm on folder /cross
create a temporary directory of source packages (on my case on /home/slitaz/arm-compiled)
on this folder download and extract the source of packages you want compile (ex. Nano-2.5.0)
at same folder make a new folder to make a binary compiled (ex. nano/fs)
cd on to folder of source packages and then these command
export PATH=$PATH:/cross/arm/tools/bin
./configure --host=arm-slitaz-linux-gnueabi –prefix=/usr
make CC=arm-slitaz-linux-gnueabi-gcc
and the final make binary on temporary folder
make install DESTDIR=/home/slitaz/arm-compiled/nano/fs
copy the content of folder fs on root system of sd mentioned on this topic.
Umount and transfer sd on android and test if binary compiled work.
enjoy
Offline
Root for ZE500KL / Z00E
Hi at all, it is my first experience to try run slitaz-arm on android tablet.
Requisite: Android s.o. Rooted, x server sdl, terminal emulator,
Rooting (Android OS)
https://en.wikipedia.org/wiki/Rooting_%28Android_OS%29
Rooting is the process of allowing users of smartphones, tablets and other devices running the Android mobile operating system to attain privileged control (known as root access) over various Android subsystems. As Android uses the Linux kernel, rooting an Android device gives similar access to administrative (superuser) permissions as on Linux or any other Unix-like operating system such as FreeBSD or OS X.
Root for ZE500KL and ZE500KG
http://forum.xda-developers.com/zenfone-2-laser/general/wip-finding-to-root-ze500kl-t3223797
THIS GUIDE COULD BRICK YOUR PHONE, FOLLOW IT AT YOUR OWN RISK!
[attachment=40711,2169]
Offline
> Asus Official Firmware and Kernel Source
> Original boot.img
> Decompressed original boot.img (with unpackbootimg)
> Official recovery (linked by @miau9202, credits to @shakalaca )
> Original dt.img (extracted from official recovery)
> Device Tree
> Rooted boot.img
Asus Official Firmware and Kernel Source
Firmware (7)
Version WW_12.8.5.156
Description ASUS ZenFone 2 Laser(Z00E/Z00ED/Z00EDA/Z00EDB)software Image:
V12.8.5.156 for WW SKU only*Version WW_12.8.5.118
Description ASUS ZenFone 2 Laser(Z00E/Z00ED/Z00EDA/Z00EDB)software Image:
V12.8.5.118 for WW SKU only*Version WW_12.8.5.106
Description ASUS ZenFone 2 Laser(Z00E/Z00ED/Z00EDA/Z00EDB)software Image:
V12.8.5.106 for WW SKU only*Source Code (5)
Version V12.8.5.156
Description ASUS ZenFone 2 Laser (ZE500KL) Kernel Source Code for Android OSVersion V12.8.5.118
Description ASUS ZenFone 2 Laser (ZE500KL) Kernel Source Code for Android OSVersion V12.8.5.106
Description ASUS ZenFone 2 Laser (ZE500KL) Kernel Source Code for Android OS
Offline
ASUS Zenfone 2 Basic Device Information
http://forum.xda-developers.com/showpost.php?p=61687936&postcount=2
There are many variants of the Asus Zenfone 2, and it is important to use the files for the corresponding device or you may damage your device permanently. They are:
Device -- Model -- RAM/CPU
[*]Z00AD -- ZE551ML -- 4GB/2.3GHz or 4GB/1.8GHz or 2GB/1.8GHz (5.5 in 1080p FHD Screen)[*]Z008D -- ZE550ML -- 2GB/1.8GHz (5.5 in 720p HD Screen)
[*]Z00D -- ZE500CL -- 2GB/1.6GHz
[*]ZE500KL -- 2GB/1.2 GHz (5.0 in 720p HD Screen)*
[*]ZE500KG -- 2GB/1.2 GHz (5.0 in 720p HD Screen)*
[*]ZD551KL -- 2GB/1.7GHz (5.5 in 1080p FHD Screen)
All of these devices share this subforum, but most of the development is targeted towards the Z00A and the Z008.
[attachment=40866,2185]
Offline
Su slitaz non mi pare ci sia l'utility adb per android. Se a qualcuno può servire qui c'è un pacchetto pronto da installare.
Testato sulla versione 4.0 e 5-rc3.
I seem on slitaz repository dont have adb shell. This is a my adb utility repacked
tested on slitaz 4.0 and 5-rc3
enjoy
https://yadi.sk/d/QjMNI4k_mPsKf
[attachment=40876,2186]
Offline
sh: /usr/bin/adb: No such file or directory
1.
tux@slitaz:~ $ adb --help
sh: /usr/bin/adb: No such file or directory
tux@slitaz:~ $ which adb
tux@slitaz:~ $ ls -l /usr/bin/adb
ls: /usr/bin/adb: No such file or directory
2.
tux@slitaz:~ $ tazpkg info android-platform-tools
TazPKG information
================================================================================
Package : android-platform-tools
Version : r19.0.1
Category : development
Short desc : Platform-Tools for Google Android SDK (adb and fastboot).
Maintainer : pankso@slitaz.org
License : custom
Depends : android-sdk
Web site : http://developer.android.com
Size : 820k/4.8M
================================================================================
3.
tux@slitaz:~ $ tazpkg -lf android-platform-tools
Installed files by: android-platform-tools
==========================================================================================
/opt/android-sdk/platform-tools/adb
/opt/android-sdk/platform-tools/api/api-versions.xml
/opt/android-sdk/platform-tools/fastboot
/opt/android-sdk/platform-tools/NOTICE.txt
/opt/android-sdk/platform-tools/source.properties
/opt/android-sdk/platform-tools/systrace/AUTHORS
/opt/android-sdk/platform-tools/systrace/LICENSE
/opt/android-sdk/platform-tools/systrace/NOTICE
/opt/android-sdk/platform-tools/systrace/prefix.html
/opt/android-sdk/platform-tools/systrace/script.js
/opt/android-sdk/platform-tools/systrace/style.css
/opt/android-sdk/platform-tools/systrace/suffix.html
/opt/android-sdk/platform-tools/systrace/systrace-legacy.py
/opt/android-sdk/platform-tools/systrace/systrace.py
/opt/android-sdk/platform-tools/systrace/UPSTREAM_REVISION
==========================================================================================
15 files installed with android-platform-tools
4.
tux@slitaz:~ $ /opt/android-sdk/platform-tools/adb version
Android Debug Bridge version 1.0.31
tux@slitaz:~ $
Offline
Hi alanyih, run live of slitaz-5.rc3 or slitaz-4.0 and download install adb-4.2.2.tazpkg
then adb on terminal and view image over....
there is list of packages
----------------------------------------------
files.list
/usr/bin/adb
/usr/bin/fastboot
nb. at least is repacked then new tazpkg, but this nouvelle the new upgraded/changing are break my patience...
Offline
tux@slitaz:~ $ tazpkg info android-platform-tools
TazPKG information..................
tux@slitaz:~$ tazpkg info android-platform-tools
Unable to find the receipt: /var/lib/tazpkg/installed/android-platform-tools/receipt
tux@slitaz:~$
______________________________________________________________________________________________
tux@slitaz:~$ tazpkg search android-platform-tools
Search result for: android-platform-tools
Installed packages
================================================================================
0 installed packages found for : android-platform-tools
Available packages name-version
================================================================================
0 available packages found for : android-platform-tools
______________________________________________________________________________________________
tux@slitaz:~$ tazpkg search-pkgname adb
Search result for file adb
================================================================================
abiword-dev
abiword-plugins
assaultcube-data
bind-dev
claws-mail-dev
deadbeef
deadbeef-dev
deadbeef-plugins
dia
dolibarr
e2fsprogs
fail2ban
firefox-dev
fpc
fpc-src
liferea
lincity-ng
linux-api-headers
linux-libre-api-headers
linux-libre-module-headers
linux-module-headers
metasploit
midori
mtools
netsurf
nomad
pingus
ruby-enterprise
slitaz-icon
t2
twisted
uclibc-cross-compiler-armv4eb
uclibc-cross-compiler-armv4l
uclibc-cross-compiler-armv4tl
uclibc-cross-compiler-armv5l
uclibc-cross-compiler-armv6l
uclibc-cross-compiler-i486
uclibc-cross-compiler-mips
uclibc-cross-compiler-mips64
uclibc-cross-compiler-mipsel
uclibc-cross-compiler-powerpc
uclibc-cross-compiler-sh4
uclibc-cross-compiler-sparc
uclibc-cross-compiler-x86_64
wesnoth
wxWidgets-dev
wxpython-dev
zsh
================================================================================
48 pkg(s) found with file: adb
tux@slitaz:~$
Offline
Hi gibor,
tux@slitaz:~$ tazpkg search-pkgname adb
Search result for file adb
Please, also try out our online packages search: http://pkgs.slitaz.org/
In case if your search query is just "adb" you'll find many packages as you stated above.
In case if you use regular expression "/adb$" as your search query you'll find package with file name exactly matched file "adb":
http://pkgs.slitaz.org/?file=/adb$
To install the package "android-platform-tools" you need to execute this command as root user:
[c]tazpkg -gi android-platform-tools[/c]
Offline
In case if you use regular expression "/adb$" as your search query you'll find package with file name exactly matched file "adb":
Thanks for the tips.
To install the package "android-platform-tools" you need to execute this command as root user:
tazpkg -gi android-platform-tools
Im on stable version, the packages are on cooking.
Best wishes for the holidays
Offline
Resources (for Asus ZE551ML / ZE550ML)
Asus Zenfone 2 | Resources all in one thread
1. Drivers | ADB installer
2. Recovery Related Stuff (Entering Recovery|Stock Recovery | Custom Recovery)
3. Rooting | Flashing | Applying OTA
4. Changing from CN to WW version
5. Unlocking Bootloader (UNOFFICIAL METHOD)
6. Xposed Framework Installer
7. Viper4Android Related Stuff
8. Adjusting DPI without root
9. NTFS support for OTG devices
o Manufacturer's Device Home Page
o Basic Device Information
o Official Stock Firmware
o Device Tools, Root/Un-root/Un-brick methods
o Custom ROMs
o Kernels & Radios
o MODS, GUIDES, and Misc
Offline
[ Generated in 0.021 seconds, 7 queries executed - Memory usage: 1.62 MiB (Peak: 1.77 MiB) ]