[X]Assistant

[Twaikyont]

пїЅпїЅпїЅпїЅпїЅпїЅ Android пїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ download

... He just had his own ideas about how the world should look, and he was powerful enough to try to implement them.

V. Archer

I wonder if anyone, except me, tried to completely get rid of the android on his device and deploy a normal distribution.
If such people exist, then they may want to discuss the results, share their experiences, or boast achievements.

Surely, someone will ask, "What for? Yes, almost any desktop Linux program already has counterparts for android. But maybe someone just does not like the android. Or maybe someone wants to write highly specialized programs for their device and write them not in Java.

Here you can ask questions (or leave instructions) on the following topics:
- Rebuilding the kernel with the new config or drivers;
- Work with ramdisk;
- HAL libraries and libhybris;
- Set up Wi-Fi, 3g;
- Setup and launch of the X server;
- Choice of window manager, environment, virtual keyboard;
- Sound output;
- Development of programs that replace the functionality of the android: control backlight, processor frequency, volume, lights, calls, messages, hibernation;
- Using cameras, sensors.

Init FAQ.
Easy reading for leisure.

If someone is interested, but do not know where to start, you can look here:
Replacing Android on the desktop distribution (Post Pigg # 48927960)

Post has been editedottiwell - 15.06.18, 23:22

[Twaikyont]

Junior Developer,
Have to edit ramdisk. In it you change default.prop. It is necessary to set the parameters

ro.secure = 0
...
ro.debuggable = 1

[Junior Developer]

What options are there to dig up ramdisk and disable android services other than compiling the kernel from source?
P.s. I can not compile, because the arm drvgen does not start

[Twaikyont]

Junior Developer,
The theory says that there are special programs called kitchens that allow you to unpack and pack ramdisks located in boot.img and recovery.img. One example isBoot & Recovery Repack for Windows, but usually they vary from device to device. There are devices common to devices, a line of devices, SoC, by manufacturer, and so on, you need to start looking from the beginning, and if you don’t find the kitchen on the first item, then go search for the second. With each transition the chances are reduced. You should start in the profile topic of your device.

[Junior Developer]

ottiwell,
Found a tool for MTK kernels, but in order to pack, you need a 64-bit distribution

[Twaikyont]

Junior Developer,
Look for better, should be on a normal system. Here are a couple of links, maybe there you will find tips.
unpacking boot.img system.img
Tool for disassembling / assembling firmware and individual images
Image Processing under Windows

[wladimir_tm]

Junior Developer,
Google: AIK Android Image Kitchen

[Azathtot]

Junior Developer,
not necessary. Attached are perl scripts for working with boot / recovery MTK systems. The result is perfectly sewed through SP Flash or via dd
MTK-repack.zip(6.63 KB)


Post has been editedAzathtot - 20.04.16, 10:25

[Junior Developer]

Azathtot
The same error as before is not packaged.

Exhaust

Repacking boot image ...
Ramdisk size: 4553 blocks
/ usr / bin / mkbootimg: 1: / usr / bin / mkbootimg: ELF: not found
/ usr / bin / mkbootimg: 2: / usr / bin / mkbootimg: Syntax error: "(" unexpected

[Azathtot]

Junior Developer,
and you have utilities like mkbootimg and others installed under your OS?

[Junior Developer]

Azathtot
Yes, it is unpacked without problems, but it does not work. The error gives mkbootimg. User for files and group "root", rights - all checkboxes (rwxrwxrwx), also run from root
https://github.com/bgcngm/mtk-tools

Post has been editedJunior Developer - 21.04.16, 15:42

[Twaikyont]

Junior Developer,
Even better - busybox init.https: //www.busybox.ne...inaries/busybox-armv5lThere is already part of init. It remains to leave in the ramdisk simlink init at the root of this busybox. Run everything else through init.d

Post has been editedottiwell - 24.05.16, 10:29

[Junior Developer]

I shortened init as much as possible and cannot mount partitions. Left only adb and mkdir'y (removed section / data).
adb shell swears that there is no sh file, I decide to load sh into the directory every time after switching on.

Nodes are created, but not mounted. I tried everything with the command mount -t ext4 -o rw, exec, dev $ nod / data

[Twaikyont]

Junior Developer,
ueventd left? In general, I propose to take a normal init.rc and clean it line by line, while checking in parallel whether it’s working.

[Junior Developer]

ottiwell,
Yes, I left it. The system partition is formatted via fastboot. Although I think that there is a ueventd binary in the system which I do not have

Posted 05/25/2016 22:43:

If uevent is in the ramdisk root

[Twaikyont]

Junior Developer,
No, not that. The ueventd binary should be in the ramdisk. In the android ramdisk you have it 100%.

Posted 05/25/2016 at 10:44 PM:

Yes, here it is and run.

Post has been editedottiwell - 25.05.16, 22:44

[Junior Developer]

ottiwell,
It is, but unpacked / sbin / ueventd - simlink on init
In init.rc "start ueventd"

Posted 05/25/2016 at 10:49 PM:

And service / sbin / ueventd is

Post has been editedJunior Developer - 25.05.16, 22:48

[Junior Developer]

If you do this:

on charger
start adbd

Then start adb on usb in the phone off?

[wladimir_tm]

Junior Developer,
In android, access by adb when the device is "on charge" is (almost) a common thing :)

[Junior Developer]

uevent runs fine, they create dev sections of the kernel. Later I will try to pack the system partition for firmware via fastboot

[Olegaslav]

Something turned out! namely, mounted the image, before downloading the android! (for me it was important!)
In general, I disassembled the bootloader, changed the values ​​in: default.prop to:

ro.secure = 0
ro.adb.secure = 0
ro.allow.mock.location = 0
ro.debuggable = 1
persist.sys.usb.config = mtp, adb

To get out of fastboot, you could switch to adb mode.

Found such a script (only edited for yourself):

mount -o remount, rw -t ext4 / dev / block / mmcblk0p8 / system
echo "SETTING VARIABLES"
export bin = / system / bin
export mnt = / data / local / ubuntu
export PATH = $ bin: / usr / bin: / usr / sbin: / bin: $ PATH
export TERM = linux
export HOME = / root
if [! -d / data / local / ubuntu]
then
mkdir / data / local / ubuntu
fi

echo "MOUNTING"
mount -t ext2 -o loop /sdcard/ubuntu/rootfs.ext2 / data / local / ubuntu
mount -t devpts devpts $ mnt / dev / pts
mount -t proc proc $ mnt / proc
mount -t sysfs sysfs $ mnt / sys

echo "SETTING UP NETWORK"
sysctl -w net.ipv4.ip_forward = 1
echo "nameserver 208.67.222.222">$ mnt / etc / resolv.conf
echo "nameserver 208.67.220.220">>$ mnt / etc / resolv.conf
echo "127.0.0.1 localhost">$ mnt / etc / hosts
echo "All credits to original creator !!!!!!!"


chroot $ mnt / bin / bash

The image was mounted, an invitation appeared:
root @ localhost: / #
But what to do next? How to run the GUI?