All the same, I solved the issue with the automatic inclusion of Samsung galaxy tab s 8.4 T-705, on the custom firmware based on CM 12.1 - Pak-man 5.1.1. I think on any Samsung with Cyanogen mod will work. Delov for 20 minutes, great knowledge of programming is not required, I will try to explain everything on the shelves.
BEFORE ALL WE DO THE FULL BECAP !!! I had so many failures in the process of experimentation that without a backup it was possible to go crazy with reinstalling the system!
What is required:
On the computer.
1. Android Image Kitchen (found onsavagemessiahzine.com).
2.Notepad ++.
3.Total Comander.
4. 7zip
On phone / tablet
1.Total Comander.
Actions on the computer:
1. Download the custom CM firmware, unpack it using the 7zip archiver. In the unpacked folder we are looking for the boot.img file. Copy it to a separate folder. It is better to rename the folder for example CM Boot.
2. Download the Samsung official firmware, unpack it using the 7zip archiver. In the unpacked folder we are looking for the boot.img file. Copy it to a separate folder. It is better to rename the folder for example Samsung Boot.
3. Copy of Samsung Boot boot.img file folder in the folder with the installed programs you Android Image Kitchen. In the open folder Android Image Kitchen, grab your mouse and drag it boot.img directly on unpackimg.bat icon, click that offers the program. The kernel unpacked, we are interested in appearing ramdisk folder in her file init.universal5420.rc. Open it with notepad ++, and look for the line # LPM. That's this line and all that is under it (referring to it, that is the sign of # the LPM and up to the next character you want to copy # ... In my case, it's such a line.:
# LPM
on property: ro.bootmode = charger
mount ext4 / dev / block / mmcblk0p18 / system wait ro
on property: ro.bootmode = charger
wait /dev/block/platform/dw_mmc.0/by-name/EFS
check_fs /dev/block/platform/dw_mmc.0/by-name/EFS ext4
mount ext4 /dev/block/platform/dw_mmc.0/by-name/EFS / efs nosuid nodev noatime noauto_da_alloc, discard, journal_async_commit
on property: ro.bootmode = charger
class_start sec-charger
service playlpm / system / bin / lpm
class sec-charger
critical
4. After the above lines have been copied to the clipboard, the ramdisk folder and the boot.img file need to be deleted from the folder with the Android Image Kitchen program.
5. Copy the boot.img kernel on which we will do when charging the load, in this case the folder CM Boot boot.img file in the folder with the installed programs you Android Image Kitchen. In the open folder Android Image Kitchen, grab your mouse and drag it boot.img directly on unpackimg.bat icon, click that offers the program. The kernel unpacked, we are interested in appearing ramdisk folder in her file init.universal5420.rc. Open it with notepad ++, and look for the line # LPM. In my case, it was here the following lines:
# LPM
on charger
# EHCI runtime enable for LPA
write / sys / devices / platform / s5p-ehci / power / control auto
mkdir / data / log 0777
chmod 0666 / dev / log / radio
chmod 0666 / dev / log / main
chmod 0666 / dev / log / event
ifup lo
hostname localhost
domainname localdomain
service charger / sbin / healthd -c
class charger
critical
seclabel u: r: healthd: s0
Now, you need to replace all the lines relating to # LPM that we copied from the Samsung kernel. We save.
6. Click on the icon repackimg.bat and see the emergence of a new kernel image-new.img. The kernel is copied to the phone / tablet, we will put it through the recovery. Just in case, you need to copy the normal and not correct kernel boot.img on occasion if the device does not boot.
7. Go to Total Commander on your phone / tablet on the system / bin path. We copy any file from there (preferably not large, otherwise there are such files there that you edit the FIG. Rename the copied file to lpm. We delete everything in it and write the following lines:
#! / system / bin / sh
/ system / bin / reboot
8. Copy the lpm file on the system / bin path, set permissions to 755.
9. Install the new kernel through the recovery. We are checking. From the beginning, just after installation, we reboot, if booted up, then we try to turn off the device and connect the charging. If not, then go to the recovery and put in advance the copied "original" core.
As a result, we get it
https://www.youtube.com/watch?v=dX4hjTyW4iYPS - perhaps not everyone will have exactly the same string and even files. In this case, we search for all files in the ramdisk with the word lpm or playlpm and replace it. I think the meaning is clear.
Post has been editedWhiteTezis - 03.04.16, 23:47