{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.DOWNLOAD: Below attachments!
DEVICE-SPECIFIC TREE:
GitHub - TeamWin/android_device_samsung_j7elte: For building TWRP for Samsung J700M ONLY
For building TWRP for Samsung J700M ONLY. Contribute to TeamWin/android_device_samsung_j7elte development by creating an account on GitHub.
github.com
Installation: Flash the .img in TWRP like this: Install Image > Locate the .img > Flash it in recovery section
CREDITS:
OmniROM
TeamWin
CM/LineageOS
Thank you for this recovery
Can you give me the commands for building this? I've read the official guide by Dees_Troy but couldn't quite get it.
This is what I'm doing:
Bash:
$ repo init --depth=1 -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git
$ cores=$( printf '%.0f' $(bc -l "scale=0; $(nproc --all) * 1.5") )
$ repo sync -j$cores
$ git clone https://github.com/TeamWin/android_device_samsung_j7elte.git --depth=1 --single-branch device/samsung/j7elte
$ git clone https://github.com/TeamWin/android_device_samsung_exynos7580-common --depth=1 --single-branch device/samsung/exynos7580-common
$ git clone https://github.com/Exynos7580/Android_kernel_samsung_exynos7580-common --depth=1 --single-branch kernel/samsung/exynos7580-common
$ git clone https://github.com/LineageOS/android_hardware_samsung -b lineage-15.1 --depth=1 --single-branch hardware/samsung/common # for dtbhtoolExynos
$ export ALLOW_MISSING_DEPENDENCIES=true
$ lunch omni_j7elte-eng
$ mka recoveryimage -j$cores
The build doesn't show me any errors (except the warnings about finding telephony thingies), and the recovery.img builds fine, but flashing it within TWRP (official) to Recovery and booting it fails. I can't take adb logcat because apparently adbd isn't started yet (it gets stuck at the manufacturer logo).
This stuff has really been a journey. All my learning is from incomplete guides and some guessing game (lol).
I dearly appreciate your support!
shrihankp said:
Can you give me the commands for building this? I've read the official guide by Dees_Troy but couldn't quite get it.
This is what I'm doing:
Bash:
$ repo init --depth=1 -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git
$ cores=$( printf '%.0f' $(bc -l "scale=0; $(nproc --all) * 1.5") )
$ repo sync -j$cores
$ git clone https://github.com/TeamWin/android_device_samsung_j7elte.git --depth=1 --single-branch device/samsung/j7elte
$ git clone https://github.com/TeamWin/android_device_samsung_exynos7580-common --depth=1 --single-branch device/samsung/exynos7580-common
$ git clone https://github.com/Exynos7580/Android_kernel_samsung_exynos7580-common --depth=1 --single-branch kernel/samsung/exynos7580-common
$ git clone https://github.com/LineageOS/android_hardware_samsung -b lineage-15.1 --depth=1 --single-branch hardware/samsung/common # for dtbhtoolExynos
$ export ALLOW_MISSING_DEPENDENCIES=true
$ lunch omni_j7elte-eng
$ mka recoveryimage -j$cores
The build doesn't show me any errors (except the warnings about finding telephony thingies), and the recovery.img builds fine, but flashing it within TWRP (official) to Recovery and booting it fails. I can't take adb logcat because apparently adbd isn't started yet (it gets stuck at the manufacturer logo).
This stuff has really been a journey. All my learning is from incomplete guides and some guessing game (lol).
I dearly appreciate your support!
Click to expand...
Click to collapse
I built TWRP for this device quite long time ago, so nope, can't help... sorry
notnoelchannel said:
I built TWRP for this device quite long time ago, so nope, can't help... sorry
Click to expand...
Click to collapse
No problem. I'll figure this out (I hope). Thanks.
official version is already available with no bugs?
i see no point
https://dl.twrp.me/j7elte/
NullCode said:
official version is already available with no bugs?
i see no point
https://dl.twrp.me/j7elte/
Click to expand...
Click to collapse
i built this because i was new at twrp building at that moment
Related
This is my first topic on english speaking forum and second on forums in general. Sorry for my english in advance.
Attension! May be you can just use this tool instead:
Pimp my Rom XDA Thread
Pimp my Rom (beta) on Google Play
I made this mod after reading this brunojcm's tutorial.
Link to my russian forum post with this Mod and link to translated to russian and adapted for Xperia P brunojcm's tutorial "Doing simple mods on framework-res.apk when apktool doesn't work properly".
Very long time ago, yet before I bought my Sony Xperia P, I hoped that I can enable on-screen navigation bar when ICS will have come to my device. But, I haven't found complete solution. However, 2 days ago I found this brunojcm's Mod on Xperia S Android Development thread and link to his tutorial at the end of his topic.
With the help of his Tutorial I made mine Mod for Xperia P and a little simplified tutorial (only in russian yet, it's hard to translate it because of it's length and links to auxiliary materials from the russian forum, but I will try to do it later).
Make backup of your device with Sony PC Companion and/or CWM.
Probably you will need Android SDK (or just adb from another sourse)
Your device must be rooted.
If something goes wrong (particularly endless reboot loop) you can force shutdown your phone by holding "VOLLUME UP
+ POWER" for about 10 seconds until triple vibration have occured and then flash your System partition from Stock ROM (without loosing any data, applications or configurations) via the Flashtool (suit's for most Sony's).
Attach your phone to PC
Download this archive and extract it somewhere:
[optional] download your framework-res.apk for backup reason.
Code:
adb pull /system/framework/framework-res.apk framework-res.apk.bkp
Push framework-res.apk from archive to your phone via executing these commands (Ubuntu sample by brunojcm, but works in Windows too)
Code:
[email protected]:~/Android/LT26i$ adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o remount,rw /system
[email protected]:/ # mkdir /system/tmp
[email protected]:/ # ^D
[email protected]:/ $ ^D
[email protected]:~/Android/LT26i$ adb push framework-res.apk /system/tmp/framework-res.apk
4765 KB/s (15874684 bytes in 3.253s)
[email protected]:~/Android/LT26i$ adb shell
[email protected]:/ $ su
[email protected]:/ $ mv /system/tmp/framework-res.apk /system/framework/framework-res.apk
[email protected]:/ # ls -l /system/framework/framework-res.apk
-rw-rw-rw- shell shell 15874684 2012-06-28 03:58 framework-res.apk
[email protected]:/ # rmdir /system/tmp
[email protected]:/ # mount -o remount,ro /system
[email protected]:/ # ^D
[email protected]:/ $ ^D
[email protected]:~/Android/LT26i$ adb reboot
Wait for your device reboot.
Enjoy your ICS Navigation Bar)
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
P.S. Don't be surprised much smaller size of my framework-res.apk - it caused by Normal Compession Strength of WinRAR, but I couldn't notice any lags increase. Nevertheless, If you don't like this, you can simply extract resources.arsc from my framework-res.apk, put it in yours framework-res.apk via some archiver (without compression) and push it to your phone.
P.P.S. May be I (or moderators) can move this topic to Xperia Mod's thread with time (when I jump over my 10 posts barrier).
Does this work for custom roms like cm9?
R: [MOD] Enable Xperia P on-screen buttons (navigation bar) (for Stock ICS)
Old thread
can yhu please post tutorial on how to get dis navigation button?
CM9 Support
No, it doesn't support any custom roms, only Stock, and it probably won't work with 6.1.1.B.1.75.
This caused by differences in framework-res.apk files in these roms.
igenid said:
No, it doesn't support any custom roms, only Stock, and it probably won't work with 6.1.1.B.1.75.
This caused by differences in framework-res.apk files in these roms.
Click to expand...
Click to collapse
i know it wont work on .75 FW dats why i was asking for A tutorial so dat one can do it himself!
thanks.
Will this work on .75 rom?
HAPPINESS is here?
With this tool may be there will be no need for my method any more and it's cool !
Tell me if it works for you. I can't see result, may be because I already have enabled buttons with my metod.
Pimp my Rom XDA Thread
Pimp my Rom (beta) on Google Play
I own a Xolo q1000/cherry mobile OHD
Specs :-
1.2 ghz quadcore mt6589
powervr gpu
4gb internal( rest not worth metioning here )
There is another device called BQ AQUARIS 5 HD
It has the same specs as the above device
even the same gpu and all the placement of the hard keys is the same as my device ( BUILD AND SPECS ARE TOTALLY SAME, EVEN THE SCREEN )
But it has 16gb internal ( only one difference )
Xolo :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Aquaris 5 HD :
Hope you can see the similarity
Now my problem here is that the source of aquaris 5 HD is available and my friend has used it to make a custom kernel for my xolo, but it doesnt boot up..
Can someone pls help me with this ??
I want to change the files corresponding to the internal memory..
Help will be appreciated
Make sure you're getting the mount points right,if the only difference between the phones were storage then, ADB would start when kernel initialises if you added it in the ramdisk. Get a dmesg or a logcat to understand the problem.
An easier do to check if the kernel works is, build a recovery with the kernel and check if it works.
Well I have been been trying to make the kernel... I got an idea.. Will changing the recovery.fstab in the source be helpful ?? And also can I copy some files in the source parts of which are having similar specs?? Like touch etc...??
protox 109 said:
Well I have been been trying to make the kernel... I got an idea.. Will changing the recovery.fstab in the source be helpful ?? And also can I copy some files in the source parts of which are having similar specs?? Like touch etc...??
Click to expand...
Click to collapse
However similar your device maybe, the calibrations may vary
"some calibrations settings are on the device itself.
Search with an root explorer under /sys/devices/platform and check under the MT-IC's (eg MT-i2C.0)
Under those IC's you'll find most of the devices (sensors,, etc), that are being used.
Example
/sys/devices/platform
MT-I2C.0
0-0039 - s3202 ---> s3202 is the TouchPanel
MT-I2C.1
1-0018 - FM50AF ---> Camera Lens
MT-I2C.2
2-0018- BMA222 ---> Accelerometer
etc, etc.
Some sensors special configs, can be found on those IC's, others are under /proc."
whenever i use the MAKE command this happens.. how to fix it ?
Code:
Command 'make' is available in '/usr/bin/make'
The command could not be located because '/usr/bin' is not included in the PATH environment variable.
make: command not found
protox 109 said:
whenever i use the MAKE command this happens.. how to fix it ?
Code:
Command 'make' is available in '/usr/bin/make'
The command could not be located because '/usr/bin' is not included in the PATH environment variable.
make: command not found
Click to expand...
Click to collapse
If you exported your path dynamically via terminal for that instance, you need to do
export PATH = path_to_dir:$PATH
this will include the existing environment paths also.
New problem at hand
Getting these errors when i am following your thread about making mediatek kernels
Code:
[email protected]:/q1100/aquaris-5HD-aquaris-5HD/kernel# cp mediatek/config/lcsh_we_jb2/autoconfig/kconfig/platform .config
cp: cannot stat `mediatek/config/lcsh_we_jb2/autoconfig/kconfig/platform': No such file or directory
protox 109 said:
New problem at hand
Getting these errors when i am following your thread about making mediatek kernels
Code:
[email protected]:/q1100/aquaris-5HD-aquaris-5HD/kernel# cp mediatek/config/lcsh_we_jb2/autoconfig/kconfig/platform .config
cp: cannot stat `mediatek/config/lcsh_we_jb2/autoconfig/kconfig/platform': No such file or directory
Click to expand...
Click to collapse
Instead of doing that try "make mediatek-configs"
MasterAwesome said:
Instead of doing that try "make mediatek-configs"
Click to expand...
Click to collapse
giving me this error .. D:
Code:
[email protected]:/q1100/aquaris-5HD-aquaris-5HD/kernel# make mediatek-configs
/q1100/aquaris-5HD-aquaris-5HD/kernel/arch/arm/Makefile:237: /q1100/aquaris-5HD-aquaris-5HD/kernel/mediatek/Makefile: No such file or directory
make: arm-linux-androideabi-gcc: Command not found
make: *** No rule to make target `/q1100/aquaris-5HD-aquaris-5HD/kernel/mediatek/Makefile'. Stop.
gcc compiler
Do you have the GCC toolchain?
If you do, try typing:
export CROSS_COMPILE=~/dir/where/gcc/is/installed/bin/arm-eabi-
if you downloaded the entire google source it will look sth like:
export CROSS_COMPILE=~/google/source/dir//prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-
protox 109 said:
giving me this error .. D:
Code:
[email protected]:/q1100/aquaris-5HD-aquaris-5HD/kernel# make mediatek-configs
/q1100/aquaris-5HD-aquaris-5HD/kernel/arch/arm/Makefile:237: /q1100/aquaris-5HD-aquaris-5HD/kernel/mediatek/Makefile: No such file or directory
make: arm-linux-androideabi-gcc: Command not found
make: *** No rule to make target `/q1100/aquaris-5HD-aquaris-5HD/kernel/mediatek/Makefile'. Stop.
Click to expand...
Click to collapse
jin03002 said:
Do you have the GCC toolchain?
If you do, try typing:
export CROSS_COMPILE=~/dir/where/gcc/is/installed/bin/arm-eabi-
if you downloaded the entire google source it will look sth like:
export CROSS_COMPILE=~/google/source/dir//prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-
Click to expand...
Click to collapse
Thanks, it works
But now i have got the zImage and modules.. How to to append mediatek headers to it and how to flash it to my device ???
Thanks
[Q&A] [DEV][TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/
Q&A for [DEV][TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV][TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I don't know what I am doing wrong. I have an 1+1.
Now newest twrp and mobile aik 1.8, I follow the steps end up with standard curtain picture. Same thing happened to me with 1.7.
I would post a link to custom_splash_twrp.img but, not enough postings. :silly:
With aik 2.2 everthing works as expected.
TIA
Fried Locust said:
I don't know what I am doing wrong. I have an 1+1.
Now newest twrp and mobile aik 1.8, I follow the steps end up with standard curtain picture. Same thing happened to me with 1.7.
I would post a link to custom_splash_twrp.img but, not enough postings. :silly:
With aik 2.2 everthing works as expected.
TIA
Click to expand...
Click to collapse
I can tell by your resulting image name that you are using the TWRP Holofied or Materialised theme as a frontend for AIK-mobile, so that's likely where you need to direct your question, since as you can see in my main thread, it's all been working just fine. :good:
I have a Asus Zenfone Max 2016 and I want to port my nougat base rr rom using a aosp oreo rom build for a similar specification device yu yureka. I'm using android kitchen. Is it possible? how do I port one and what shoud use.
I dont see the folder systeem in the Android 8 roms.
I do see system.dat is there a different wat tot port a oreo ROM with kitchen ?
Please im looking for a oreo ROM what i can port tot my leeco le 2 s3 mtk 6797 chipset.
Android Kitchen can't detect Java.exe during ROM (.zip) packaging
Hey guys
Till a few days back, I was a complete noob at making android roms and porting, but in these past few days, I've learnt a lot, thanks to wonderful tutorials on XDA. I'm trying to port LG Power X 's rom for my Micromax MEGA 4G Q417 device, and everything is all well and done and configured, but I'm getting struck here at this screen in Android Kitchen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says that I probably do not have JAVA JDK installed, but, I DO HAVE IT. I don't know what I'm doing wrong.
Here is my .bash_profile if it helps...
Code:
# To the extent possible under law, the author(s) have dedicated all
# copyright and related and neighboring rights to this software to the
# public domain worldwide. This software is distributed without any warranty.
# You should have received a copy of the CC0 Public Domain Dedication along
# with this software.
# If not, see <http://creativecommons.org/publicdomain/zero/1.0/>.
# base-files version 4.2-4
# ~/.bash_profile: executed by bash(1) for login shells.
# The latest version as installed by the Cygwin Setup program can
# always be found at /etc/defaults/etc/skel/.bash_profile
# Modifying /etc/skel/.bash_profile directly will prevent
# setup from updating it.
# The copy in your home directory (~/.bash_profile) is yours, please
# feel free to customise it to create a shell
# environment to your liking. If you feel a change
# would be benifitial to all, please feel free to send
# a patch to the cygwin mailing list.
# User dependent .bash_profile file
# source the users bashrc if it exists
if [ -f "${HOME}/.bashrc" ] ; then
source "${HOME}/.bashrc"
fi
# Set PATH so it includes user's private bin if it exists
if [ -d "${HOME}/bin" ] ; then
#PATH="${HOME}/bin:${PATH}"
export PATH=$PATH:"/cygdrive/C/Program Files/Java/jdk-10.0.2/bin/"
fi
# Set MANPATH so it includes users' private man if it exists
# if [ -d "${HOME}/man" ]; then
# MANPATH="${HOME}/man:${MANPATH}"
# fi
# Set INFOPATH so it includes users' private info if it exists
# if [ -d "${HOME}/info" ]; then
# INFOPATH="${HOME}/info:${INFOPATH}"
# fi
PATH=/cygdrive/c/Program\ Files/Java/jdk-10.0.2/bin:${PATH}
What am I doing wrong? I'm trying since yesterday to fix this, but, even after countless frustrating attempts, the error persists. I now have no other option than to ask the help of you guys here. Please help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GNU/Linux for Android devices
I am NOT responsible for bricked devices
Installing
Make sure you backup your device, I am not responsible for any data loss!
Install git and Android platform tools
Download these files and put them somewhere:
hybris-boot.img
system.img
pm-rootfs-(date)-(time).tar.gz (Plasma Mobile rootfs)
Clone halium-scripts to the directory you put the other files in
Code:
$ git clone https://github.com/Halium/halium-scripts
Put your device in fastboot mode, I assume you have backed up your device by now, if not, do it now, and run these commands:
Code:
$ fastboot flash boot hybris-boot.img
$ halium-scripts/halium-install pm-rootfs-(date)-(time).tar.gz system.img
# replace (date) and (time) with the date and time you downloaded, for example: pm-rootfs-20180524-110808.tar.gz
Reboot your device, it should now boot into Plasma Mobile.
Downloads
Downloads can be found here, If my download server goes down feel free to poke me.
Please report anything broken and/or working!
XDA:DevDB Information
Halium for Xperia Z3, ROM for the Sony Xperia Z3
Contributors
noud02
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Version Information
Status: Testing
Created 2018-07-14
Last Updated 2018-07-14
noud02 said:
GNU/Linux for Android devices
I am NOT responsible for bricked devices
NOTE
I have not yet tested this on my own device as I'm on vacation and don't have a backup device.
Installing
Make sure you backup your device, I am not responsible for any data loss!
Install git and Android platform tools
Download these files and put them somewhere:
hybris-boot.img
system.img
pm-rootfs-(date)-(time).tar.gz (Plasma Mobile rootfs)
Clone halium-scripts to the directory you put the other files in
Code:
$ git clone https://github.com/Halium/halium-scripts
Put your device in fastboot mode, I assume you have backed up your device by now, if not, do it now, and run these commands:
Code:
$ fastboot flash boot hybris-boot.img
$ halium-scripts/halium-install pm-rootfs-(date)-(time).tar.gz system.img
# replace (date) and (time) with the date and time you downloaded, for example: pm-rootfs-20180524-110808.tar.gz
Reboot your device, it should now boot into Plasma Mobile.
Downloads
Downloads can be found here, If my download server goes down feel free to poke me.
Please report anything broken and/or working!
XDA:DevDB Information
Halium for Xperia Z3, ROM for the Sony Xperia Z3
Contributors
noud02
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Version Information
Status: Testing
Created 2018-07-14
Last Updated 2018-07-14
Click to expand...
Click to collapse
thanks for your develoment but unforturnately i have to say that the install progress is corrupted due to error.....
more infor i had posted here: https://github.com/Halium/halium-scripts/issues/10
kaotd99 said:
thanks for your develoment but unforturnately i have to say that the install progress is corrupted due to error.....
Click to expand...
Click to collapse
Could you maybe try JBB's tool to write the rootfs and system image to your device? (JBBgameich/halium-install on gitlab, XDA won't let me post replies with URLs )
Could be interesting to try, but im worried if this can brick my phone...
Tux111 said:
Could be interesting to try, but im worried if this can brick my phone...
Click to expand...
Click to collapse
It does not brick your phone (source: I tried myself )
Also, I kinda gave up on this project, maybe I'll continue it later if I have some more time.
If anyone is interested in working on this feel free to poke me on discord (noud02#0080).
EDIT: forgot to say, it does not boot successfully :<
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
every time i post it at reddit it gets removed, so was getting difficult sharing it
What works
audio
video
wifi
keyboard
trackpoint
touch
android apps
linux
What doesn't work yet
acpi (needs linux people help to make a kernel to chrome os)
bluetooth (easy fix)
battery level
What do you need
one 16gb pendrive
one 8gb pendrive or higher
one gpd pocket (duh)
a lots of patience and free time
First step
Go to CrOS page and download pyro
Download EmydeOS
Download SWTPM.tar and chromefy script
Second step
use a linux or mac pc and dd EmedyOS image to a 16gb pendrive
List all disks:
Code:
in linux: lsblk
in mac : diskutil list
sudo dd if=/path to emedy os/ of=/dev/sdx (where x is your pendrive disk nummber)
Third Step
Boot the flashed pendrive in dev mode
enter in shell pressing press ctrl + alt+fn + f2
type in chronos
in shell follow this:
Code:
sudo su
lsblk (find your drive , usually its mmcblk0)
sudo /usr/sbin/chromeos-install --dst YOURDRIVE (Ex: /dev/mmcblk0)
wait and check if boots
fourth step
download mate ubuntu
flash it into 8gb usb using the mentioned dd command
boot in live usb
open gparted
delete mmcblk0p5
extend mmcblk0p3 to 4gb
fifth step
format ubuntu mate pendrive to extfat
extract pyro image and copy the bin file to pendrive
copy chromefy sh and swtpm to pendrive
boot emedyos pendrive
press ctrl fn alt f2
enter chronos
Code:
sudo su
sudo mkdir /home/chronos/tempfolder
lsblk ( find the 8gb with pyro files, mine was sdb)
sudo mount /dev/YOURDRIVEHERE /home/chronos/tempfolder
cd /home/chronos/tempfolder
sudo bash /home/chronos/temfolder/chromefy.sh /dev/mmcblk0p3 /home/chronos/tempfolderNAMEOFpyro.bin /home/chronos/tempfolderswtpm.tar
sudo mkfs.ext4 /dev/mmcblk0p1
Sixth step
boot into chrome os and boot into shell again
Code:
sudo su
cd /usr/share/vboot/bin/ ./make_dev_ssd.sh --remove_rootfs_verification --f --partitions 2 reboot
Upon reboot go back into shell
Code:
sudo su -
mount -o remount,rw /
mount -o remount,exec /mnt/stateful_partition
download [URL="https://fedorapeople.org/~jwrdegoede/brcmfmac4356-pcie.txt"]this[/URL] file and copy to 8gb pendrive
mount the pendrive
sudo su
sudo mkdir /home/chronos/tempfolder
lsblk ( find the 8gb with file, mine was sda)
sudo mount /dev/YOURDRIVEHERE /home/chronos/tempfolder
cd /home/chronos/tempfolder
cp /home/chronos/tempfolder/brcmfmac4356-pcie.txt /lib/firmware/brcm
reboot into dev mode and complete steup
seventh step
to get sound working
press ctrl alt t into chrome
Code:
type shell
sudo su
mkdir /usr/share/alsa/ucm/chtrt5645 directory and copy the 2 .conf files from here into that dir.
What needs to be done
with the help of linux fans we need to patch the kernel
Kernel patches needed:
MAX17047 Fuel Gauge
BATTERY_MAX17042
BQ24190 Charger
CHARGER_BQ24190
GPIO for Fan Control
GPD_POCKET_FAN
Intel Graphics
CONFIG_DRM_I915
UEFI Framebuffer
CONFIG_FB_EFI
ALSA Sound Card Support
CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_ACPI
eMMC Block Device (ACPI SDIO)
CONFIG_MMC_SDHCI
CONFIG_MMC_SDHCI_ACPI
Wireless
CONFIG_B43
CONFIG_BRCMFMAC
CONFIG_BRCMFMAC_SDIO
CONFIG_BRCMFMAC_PCIE[/INDENT]
References
https://hansdegoede.livejournal.com/17445.html
https://forum.xda-developers.com/ha...talling-official-chrome-os-pc-t3865697/page92
https://github.com/imperador/chromefy
https://wiki.gentoo.org/wiki/GPD_Pocket
thank you so much for taking the time to write a tutorial!
I'm going to try it on my gpd pocket as soon as possible that at the moment is running this build https://kmyers.me/blog/computers/public-preview-chromiumos-for-the-gpd-pocket-1/ .
By chance, in the meanwhile, are there any news about a new kernel with working acpi/bluetooth/battery meter?
Thanks again for the great work you did!