Related
Well, now that it's up and running it's time to properly set this thread up.
The idea of this thread is to provide a kernel repo that most can use to build their own.
I'll be building and posting the builds from this without modification.
May 29, 2014 Update: I have added the NE2 Kitkat kernel and built but it will remain untested.
I'll try to see if someone can test but it doesn't look like much has changed from MK4.
Project Repositories:
NE2 (4.4) (Initial Setup Only)
https://github.com/garwynn/L900_NE2_Kernel
MK4 (4.3) (WIP):
https://github.com/sleshepic/l900_MK4_Kernel (Thanks to sleshepic for his work on this!)
MC2:
https://github.com/garwynn/L900_MC2_Kernel
Older Versions (Development has stopped)
MA7 | LJC
Project Status:
NE2:
I've used the same as MK4 to make a test kernel. Untested though without a N2.
MK4:
Still trying to get a full boot.img together, stay tuned.
MC2 Status:
Kernel patched to current Linux 3.0.x (.71 at time of update)
Stock governors enabled, 6 additional ones added.
Project Downloads (Built Kernels):
My kernels are currently housed by rwilco12's Android Stock Repo. (All versions)
To compile on your own you need:
1) Linux Box - I'm using Ubuntu 14.04 and all prerequisites for building AOSP.
2) Android SDK with toolchains - I used arm-eabi-4.4.3 all the way through NE2.
3) Cloned repo from above.
Just modify the toolchain location in ./build_n2.sh and execute ./build_n2.sh.
Rest should go on its own.
On some cases I had to also change the toolchain location in main makefile.
Releasing/Posting your Kernels:
Folks are encouraged to try building the kernel and posting it if they want to.
Any posts should refer to using the kernel as their base.
If you modify the code further outside of this you should include a link to your repo for others to see those changes.
Anyone interested in chipping into this is more than welcome!
Thank you in advance for your time!
I've been playing, digging, etc for about a year now. Ive been attempting my first rom build and I think im really close. Its a 4.2 rom, so its been a challenge.
But I would love to participate in this too if its open to everyone.
Sent from my SPH-L900 using Tapatalk 2
cbucz24 said:
I've been playing, digging, etc for about a year now. Ive been attempting my first rom build and I think im really close. Its a 4.2 rom, so its been a challenge.
But I would love to participate in this too if its open to everyone.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
That's the goal! It slowed down on the E4GT but it's hopefully going to heat up again soon.
The more people that get involved, the better the kernel should end up - and the more that fellow XDAers learn and share knowledge!
Talk to sleshepic. He built a kernel for his rom.
Sent from my SPH-L900 using Tapatalk 2
Self-plug below. It should get you started on kernels.
http://forum.xda-developers.com/showthread.php?t=1748297
btbamzao said:
Talk to sleshepic. He built a kernel for his rom.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Agat63 showed him and also is willing to show me but catching him will be tough for the next 3 weeks.
So that's what I'll go with if we can't get something cobbled together before then.
garwynn said:
Agat63 showed him and also is willing to show me but catching him will be tough for the next 3 weeks.
So that's what I'll go with if we can't get something cobbled together before then.
Click to expand...
Click to collapse
Agat was def helpful as always. The way I ended up doing it was slightly dif than the way he does it on the S3, really similar though. im really busy for a couple days but when I get to my comp with some time ill type up what I do.
My git wouldn't be a good source to clone from just cus my first commit had a few changes already, but it def would be helpful to get a working repo together with the Cypress touch drivers already placed in source - did they forget them or what lol. Could try getting that together too.
sleshepic said:
Agat was def helpful as always. The way I ended up doing it was slightly dif than the way he does it on the S3, really similar though. im really busy for a couple days but when I get to my comp with some time ill type up what I do.
My git wouldn't be a good source to clone from just cus my first commit had a few changes already, but it def would be helpful to get a working repo together with the Cypress touch drivers already placed in source - did they forget them or what lol. Could try getting that together too.
Click to expand...
Click to collapse
Thanks for the assist!
I'll try to commit a fresh LJC repo over the weekend then and we can go from there.
Hope I don't mess that up. I'll ask if I have any ??s.
Well, I made a repo here:
https://github.com/garwynn/L900_LJC_Kernel
...and followed the kernel readme instructions. Looks like it's compiling.
*Edit* ...and failed. arm-eabi-nm missing in toolchain I'm using.
(Wait, it's right there!)
Code:
/root/Kernel/L900_LJC_Kernel/scripts/mksysmap: line 44: ~/Kernel/toolchain/prebuilt/arm-eabi-4.4.3/bin/arm-eabi-nm: No such file or directory
make: *** [vmlinux] Error 1
How about a Modem Repo? Like on the Epic Touch
Avatar said:
How about a Modem Repo? Like on the Epic Touch
Click to expand...
Click to collapse
Rwilco12 - when he has time - is going to set up a Kernel/ROM/Modem Repo... at least time I talked to him.
Cool.
garwynn said:
Well, I made a repo here:
https://github.com/garwynn/L900_LJC_Kernel
...and followed the kernel readme instructions. Looks like it's compiling.
*Edit* ...and failed. arm-eabi-nm missing in toolchain I'm using.
(Wait, it's right there!)
Code:
/root/Kernel/L900_LJC_Kernel/scripts/mksysmap: line 44: ~/Kernel/toolchain/prebuilt/arm-eabi-4.4.3/bin/arm-eabi-nm: No such file or directory
make: *** [vmlinux] Error 1
Click to expand...
Click to collapse
Here is what my build looks like, in general. I have my toolchain referenced in the first export (which could also be easily put in the makefile so its not needed each time)
$ export CROSS_COMPILE=/media/Android/Kernel/toolchain/prebuilt/arm-eabi-4.4.3/bin/arm-eabi-
$ make t0spr_04_defconfig
$ make menuconfig (this is not necessary, and possibly not recommended unless you know what your changing etc, or could be manually edited in the file)
$ make modules
$ make -j5 (the -j5 is optional, I have a quad core processor so this just speeds things up, if you believe your comp is capable of faster than standard builds put the number of cores plus 1 for the number after "-j" )
Then that will build the zImage into the /arch/arm/boot directory.
Which we then bundle with the ramdisk to create the boot.img.
On the Epic Touch all we needed was the zImage for the kernel since the initramfs were bundled differently, but it's dif on our Note 2's. you'll need the ramdisk and zimage to make your boot.img. I pulled the ramdisk from the stock kernel.
I use
$ ./unpack-bootimg.pl boot.img
to pull the "ramdisk-contents" from the stock kernel, I renamed that folder "initramfs" and threw it in a folder along with my mkbootimg binary, and my zImage I just compiled. you can put this anywhere, I just put it in my working kernel folder so it's easy to navigate to
I put the newly created modules from zImage build in my initramfs/libs/modules with
$ find -name '*.ko' -exec cp -av {} [path to desired folder] \;
I navigate to the initramfs folder and
$ find .|cpio -o -H newc > ../ramdisk
$ cd ..
$ gzip ramdisk
$ ./mkbootimg --kernel ./zImage --ramdisk ./ramdisk.gz --board smdk4x12 --base 0x10000000 --pagesize 2048 --ramdiskaddr 0x11000000 -o boot.img
That last part is what bundles the zimage and ramdisk into the boot,img. sorry I had to rush it, hope i didn't miss much, can fill in the blanks as needed, just I'd get up whatever I could when I found a moment, open to help in any way I can.
Edit: Also, checked out the repo put up, Nice work so quick! this is the folder I mentioned that needs to be added or else the capacative touch keys won't work, unbelievable that that was missed in the source drop. I mean, isn't it supposed to be a buildable working version for it to meet open source standards? guess not. anyway, this "cypress" folder needs to be added to the source prior to build for the two touch keys to work. first time I finally got mine booting and all I was so psyched only to find out my touch keys didnt work, so frustrating. Just have to pull it from other source, or you can grab it from mine
https://github.com/sleshepic/Note_2_l900/tree/master/drivers/input/keyboard/cypress
Big thanks to agat63 and Andreilux for help along the way
Nice stuff here, will be following this thread. Here is another repo with fresh LJC kernel source with cypress drivers included https://github.com/slickrick/L900_Kernel
thewadegeek said:
Self-plug below. It should get you started on kernels.
http://forum.xda-developers.com/showthread.php?t=1748297
Click to expand...
Click to collapse
Mind if include this in OP revision after Phase 1 is finished?
Also thanks for the quick responses... will try to get to it this weekend but will probably be Monday. Sucks but that's the way it will be a few more weeks.
Sent from my SPH-L900 using Tapatalk 2
garwynn said:
Rwilco12 - when he has time - is going to set up a Kernel/ROM/Modem Repo... at least time I talked to him.
Click to expand...
Click to collapse
Working on it as we speak! I was able to finish the week with only 10 hours of overtime and had some free time to work on some projects.
Got one or two little things to sort out in the PHP but here's a sneak peek of what I've got coming! It's a complete rework of my original Repo for the E4GT with more devices and more goodies!
If there are any PHP gurus (or web design in general) and you're willing to help hit me up and maybe I can get over this last hurdle and make the New Repo public!
{
"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"
}
garwynn said:
Mind if include this in OP revision after Phase 1 is finished?
Also thanks for the quick responses... will try to get to it this weekend but will probably be Monday. Sucks but that's the way it will be a few more weeks.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Nope feel free.
Sent from my SCH-R950 using Tapatalk 2
Well.. work on this may be pushed back a day or two, new source for the E4GT. Gotta look at it first.
Hi everyone.
I'm here by invitation and will try to participate as much as I can.
Hopefully with combined knowledge and power we can make this
project move faster.
agat63 said:
Hi everyone.
I'm here by invitation and will try to participate as much as I can.
Hopefully with combined knowledge and power we can make this
project move faster.
Click to expand...
Click to collapse
Okay... here's where I still stand.
Added Cypress and pushed a commit to Github.
Make still is good up until VMLinux and fails.
Didn't know I can just skip to here so here's the command and output:
Code:
[email protected]:~/Kernel/L900_LJC_Kernel# make vmlinux
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
LD vmlinux
SYSMAP System.map
/root/Kernel/L900_LJC_Kernel/scripts/mksysmap: line 44: ~/Kernel/toolchain/prebuilt/arm-eabi-4.4.3/bin/arm-eabi-nm: No such file or directory
make: *** [vmlinux] Error 1
Where should the vmlinux object be? It's trying to create system.map so I suspect that vmlinux is not being created properly.
I dumped a debug output from this make but it's 115MB.
AOSP-Kernel for Ascent P6 (W.I.P)
Screenshot
{
"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"
}
Source:
Ascend P6 Open Source(P6-U06,JellyBean,kernel-3.0.8)
Click to expand...
Click to collapse
Features:
First Build
Only Added "Optimize for size" (so that the kernel should work without problems)
Click to expand...
Click to collapse
Credits:
m!k3 (for the right download-link ^^)
Huawei (for releasing this source)
CNexus (for his wonderful Boot.img tools)
worstenbrood (for his Huawei Update Extractor)
raolleel (Building the kernels)
jimbo77 for testing B118/CN + The Screenshot
husen4u for the flashable ZIP
Click to expand...
Click to collapse
Warning:
keep in mind : THIS IS A VERY EARLY BUILD
tell me which bugs are there, or if this doesn't work _B118CN is tested, but should wok on every Rom with unlocked BL
Only Works with Unlocked Bootloader, so you must have been on B118CN
Should work with B118CN
Should work with B125 if you were on B118Cn before
Could work with B111 if your Bootloader is not relocked when you flash B111 from B118CN
(only released because everyone said that the kernel is only for B111 [which I can't belive)
I am not responsible for bricking/destroying your phone. Custom kernels comes with no warranty.
Click to expand...
Click to collapse
Installation:
You must be on B118CN or any other Firmware with unlocked BL
simply flash via fastboot
or flash ZIP via TWRP/CWM
Click to expand...
Click to collapse
Download:
Boot.img (included zImage in every boot.img
B111
B118CN
B125
flashable Zip (B118CN)
https://mega.co.nz/#!7AYiVQwb!eThA93t7zRMEOJw57Zqq4mi8pgwwTmAzXNdpztpMcew
Click to expand...
Click to collapse
Source:
https://github.com/damienyong/Kernel-3.0.8
Click to expand...
Click to collapse
Thanks A Lot For Your Work. I Will Test And Give Feedback
Hello !
Good to see here more dev. involved in the development part for P6 !
Please, when you have some free time, push your modified kernel source code on your github ! In this way you will not violate XDA rules , and will also help those who want to contribute / improve this source !
Thank you very much !
surdu_petru said:
Hello !
Good to see here more dev. involved in the development part for P6 !
Please, when you have some free time, push your modified kernel source code on your github ! In this way you will not violate XDA rules , and will also help those who want to contribute / improve this source !
Thank you very much !
Click to expand...
Click to collapse
I am / was about to do so, but some files are bigger than 100mb and github doesn't like this ^^
raolleel said:
I am / was about to do so, but some files are bigger than 100mb and github doesn't like this ^^
Click to expand...
Click to collapse
What ??? 100mb one file ? what do you want to push on github
The whole kernel source code has about 480mb , you can not have just one file 100mb....
surdu_petru said:
What ??? 100mb one file ? what do you want to push on github
The whole kernel source code has about 480mb , you can not have just one file 100mb....
Click to expand...
Click to collapse
I cleaned up a little bit ... start uploading in a few minutes ... hope its clean enough ^^
raolleel said:
I cleaned up a little bit ... start uploading in a few minutes ... hope its clean enough ^^
Click to expand...
Click to collapse
Sure, you cannot push source code after you builded zImage , you need > make mrproper , make clean & make distclean before push on your github !
> make distclean will wipe also .config and all modified files "~" !
surdu_petru said:
Sure, you cannot push source code after you builded zImage , you need > make mrproper , make clean & make distclean before push on your github !
> make distclean will wipe also .config and all modified files "~" !
Click to expand...
Click to collapse
I didn't use make distclean ^^ sry .. but I'm uploading
Github added
Ps ... simply ignore the warnings .. Huawei didn't do a good job ...
Tutorial how to build : https://github.com/damienyong/Kernel-3.0.8/blob/master/README.md
Did anybody test the kernel?
jimbo77 for testing B118/CN
Click to expand...
Click to collapse
Yes it works with B118CN
what is the advantages of this kernel. undervolting??
Until now there isn't much which is better in this kernel, but when I'll get my phone from repair I'll hope to include a few mods
Are you able to add Loop-Device support?
Would be really nice, because i want to run a Linux Distro on my Phone.
_heisenberg said:
Are you able to add Loop-Device support?
Would be really nice, because i want to run a Linux Distro on my Phone.
Click to expand...
Click to collapse
It should be doable, but at first I want to make this kernel stable, enable some mods, if everything is working like it should, I will try my best to enable loop-device-support
raolleel said:
It should be doable, but at first I want to make this kernel stable, enable some mods, if everything is working like it should, I will try my best to enable loop-device-support
Click to expand...
Click to collapse
Of course, take the time you need, don't hurry
.. I'm a little confused, but my kernel has loopback-support,
my next release should have this enabled,too .
What is about the promised flashable zip?
_heisenberg said:
Are you able to add Loop-Device support?
Would be really nice, because i want to run a Linux Distro on my Phone.
Click to expand...
Click to collapse
Hi!
Loop-Device is already enabled in our device !
Please take a look on hisi_k3v2oem1_defconfig , you will see : CONFIG_BLK_DEV_LOOP=y , and also we have : CONFIG_BLK_DEV_CRYPTOLOOP=y
Or you can take alook in your device :
[email protected]:~/xxx/kernel/cm$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ # export
ANDROID_ASSETS
ANDROID_BOOTLOGO
ANDROID_CACHE
ANDROID_DATA
ANDROID_PROPERTY_WORKSPACE
ANDROID_ROOT
ANDROID_SOCKET_adbd
ANDROID_STORAGE
ASEC_MOUNTPOINT
BOOTCLASSPATH
EMULATED_STORAGE_SOURCE
EMULATED_STORAGE_TARGET
EXTERNAL_STORAGE
HOME
HOSTNAME
LD_LIBRARY_PATH
LOOP_MOUNTPOINT
MKSH
PATH
RANDOM
SECONDARY_STORAGE
SHELL
TERM
TERMINFO
USER
Click to expand...
Click to collapse
surdu_petru said:
Hi!
Loop-Device is already enabled in our device !
Please take a look on hisi_k3v2oem1_defconfig , you will see : CONFIG_BLK_DEV_LOOP=y , and also we have : CONFIG_BLK_DEV_CRYPTOLOOP=y
Or you can take alook in your device :
Click to expand...
Click to collapse
Strange...tried to install Ubuntu 13.04 via full Linux Installer and it didn't work...but thanks, i will try again!
Dmitry Budnikov said:
What is about the promised flashable zip?[/QUOTE
My phone is in repair, when I'll get it back I will create a flashable zip
Click to expand...
Click to collapse
Hello,
A few days ago I wrote a new implementation inspired by the work of CyboLabs and Codefire that in harmony contributed for the creation of Open_Bump. Basically I rewrote Open_Bump using POSIX C to run directly on LG G2 or any compatible device with Open_Bump. So now you can bump any kernel or recovery using the target device, validate images to know if they have been bumped and other things.
The source code and binaries for Linux and Android found at: https://github.com/ferreirawax/cbump
FAQ
What is POSIX?
POSIX is an API for Unix-like systems (Linux, Android, etc).
But what are the benefits of this?
Considering the benefits already mentioned above. Other example, if you are a developer, you will probably will get rid of Python or even get rid of everything and create a script to bump the Kernel/Recovery on the flash time.
And why the original developers did not do it?
I do not know.
I do not know how to use it.
See the readme in the link above.
Click to expand...
Click to collapse
Cheers!
It will be useful for developers, thanks for the effort
Nice work, I guess the reason why it remained in Python was because it was just working fine once you installed python on your linux environment. And the only way to bump on android was what was implented in multirom to first unloki the boot.img and then sign it with the LG key.
Just some questions:
so if you use cbump with -f then it will check or it's bumped and then flash it but if it's loki then it will not flash it and it will only say that it's not bumped right?
And with your usage:
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdin]
Is it both stdin or must the last one be stdout?
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdout]
Also could you perhaps explain a bit with how to use it on android, like where to put it and those things a little bit more explaination.
Just asking as I won't check the complete code now and as I am tired and I am still a newb at this level of writing codes etc but it look's :good: but still, I am not sure how much we will use cbump in Android and perhaps also in multirom but I'll check it out perhaps tomorrow or later more. Still thanks for your contribution:good:
wulsic said:
Nice work, I guess the reason why it remained in Python was because it was just working fine once you installed python on your linux environment. And the only way to bump on android was what was implented in multirom to first unloki the boot.img and then sign it with the LG key.
Just some questions:
so if you use cbump with -f then it will check or it's bumped and then flash it but if it's loki then it will not flash it and it will only say that it's not bumped right?
And with your usage:
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdin]
Is it both stdin or must the last one be stdout?
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdout]
Also could you perhaps explain a bit with how to use it on android, like where to put it and those things a little bit more explaination.
Just asking as I won't check the complete code now and as I am tired and I am still a newb at this level of writing codes etc but it look's :good: but still, I am not sure how much we will use cbump in Android and perhaps also in multirom but I'll check it out perhaps tomorrow or later more. Still thanks for your contribution:good:
Click to expand...
Click to collapse
Hello,
I know that Python works well, but Cbump was thought to be portable. I did not even know about MultiROM, I checked now and discover that he used the unrepresentative signature in many standard unicodes which is not an elegant method. About -f, yes. I had not thought about Loki up because I have no reason to use Loki instead of Bump (Without disregarding the Dan's splendid work), Maybe I can add support for Loki verification later. About streams take look here, I'll add more information/instructions in thread soon.
Thanks.
@ferreirawax
Very cool work. Can't wait to expand on this and find more use cases!
how I know if my devices is bump supported? I know it works in G2,G3 on lollipop 5.0.2, right? now I own a G flex 2 on 5.0.1, can this work?????
Sj12345 said:
how I know if my devices is bump supported? I know it works in G2,G3 on lollipop 5.0.2, right? now I own a G flex 2 on 5.0.1, can this work?????
Click to expand...
Click to collapse
{
"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"
}
You're in the WROOOOOONG thread, buddy...
jeebspawnshop said:
You're in the WROOOOOONG thread, buddy...
Click to expand...
Click to collapse
haha,no I dont buddy, LG exploits can be used for all LG devices (we have root on g2,g3,g4,gflex,gflex2 with the SAME EXPLOIT) He understands how the exploit "bump" works... so I need help from HIM to try this in my devices
....... thanks
From Readme.txt
"The flash function uses MSM identifier to detect partition block, Tested only on LG G2, Probably works too with LG G3 and others LG devices powered by Qualcomm."
Sorry its me again
I have a lot of question???? can you help me? @ferreirawax
I have two partitions on my phone (aboot and boot), which should be used???
I will dump the correct partition with
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/data/media/0/boot.img
then use your tool like
Code:
cbump /data/media/0/boot.img /data/media/0/cboot.img
flash partition with
Code:
dd if=/data/media/0/cboot.img of=/dev/block/bootdevice/by-name/boot
and try to booting up....so if this boot up means it works?
and my next step will be make a TWRP recovery???? I will be carefull cause My phone doesnt have kdz or tot for go back to stock... I only have my own backup from dd
@Sj12345 this is a rewritten version of open_bump so if bump didnt worked on your device this won't work either. Lollipop isn't working with bump only jellybean and kitkat as far as I know. Also I suggest before doing these things to learn what the partitions etc are before you will hardbrick yourself. Aboot is the bootloader. Boot is the boot.img so that's the kernel.
It probably will result into an security error.
Sent from my LG-D802 using Tapatalk
One word: COOL
This is awesome, thank you so much. Now we can use .zip to bump and flash, just like loki method. Will make testing things SO much easier. Won't have to re-bump the image every time
You the man!
Now if u can get one for the G4 n get the $10,000 bounty!
Sent from my LG-H811 using Tapatalk
5 Star For You [Excellent]
Testing Cbump to our devices
Awesome Tools! :good:
It should help multirom?
Inviato dal mio LG-D802 utilizzando Tapatalk
Edited
Sorry for the bump (ehehe), but does anyone have a mirror of this? Nvm, solved!
https://github.com/dorimanx/cbump
{
"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"
}
Plasma Mobile aims to become a complete software system for mobile devices. It is designed to give privacy-aware users back the full-control over their information and communication. Plasma Mobile takes a pragmatic approach and is inclusive to 3rd party software, allowing the user to choose which applications and services to use. It provides a seamless experience across multiple devices. Plasma Mobile implements open standards and it is developed in a transparent process that is open for the community to participate in.
Visit Plasma Mobile Website to see all cool features, video intros and more.
Plasma Mobile is very new OS and is still developing everyday. This is an Alpha version build and by no means is usable as daily driver. You can still try it for testing purposes and help me fix the bugs. Don't use it if you intend to complain and disrespect my work.
What's Working
GUI
WiFi
What's Not Working
Most features are unimplemented.
Screenshots
Check screenshots tab. You might need to use desktop site to see that.
Downloads
Hybris-boot | System | Plasma rootfs-caf | Scriptss
Instructions on How To Flash
You are required to have a PC with Linux distro on it to flash. Scripts required to flash are in downloads tab. You might need to use desktop version of XDA to see that.
Check my instructions on how to flash on Github Gist.
Hybris-boot and system image files are based on Halium-7.1. There source can be found on GitHub as well as the Device, Kernel and Vendor Source required to build both image files. The whole documentation to build can be also on the website.
XDA:DevDB Information
Plasma Mobie-CAF, Tool/Utility for the Zenfone 2 Laser
Contributors
TheImpulson
Source Code: https://github.com/blue-systems
Version Information
Status: Alpha
Created 2018-01-07
Last Updated 2018-01-08
Reserved
Reserved
Reserved
..
Can you make a flashable zip for TWRP
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
Can we have some screenshots please
It reminds me of my old HTC Leo. Hahaha Good Job tho. Still confuses me as to what the OS is about, but hey, we have it.
jitu nayak cvrce said:
Can you make a flashable zip for TWRP
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
Can we have some screenshots please
Click to expand...
Click to collapse
It can't be flashed via TWRP. You will require a PC.
Added Flashing Instructions in thread. You can test if you all want. Use latest rootfs while testing. You are required to have a PC to flash running a Linux distro and again this is not usable as daily driver by any means. Most features are incomplete and unimplemented.
eiPeiDweP said:
It reminds me of my old HTC Leo. Hahaha Good Job tho. Still confuses me as to what the OS is about, but hey, we have it.
Click to expand...
Click to collapse
I added website link in thread. Check that to know more.
very cool...was looking forward to seeing this ported for our devices.
I was planning to toy around with this come spring if no one else did. good job.
Are you part of the plasma team ?
Turns my phone into a hacking device huh. Coooool. Watch dogs mode?
All steps are performed without errors, but after entering the root password occurs cyclic reboot! The system will not boot and run a script that ssh is not possible. All manipulations are performed on ubuntu, only in a virtual machine.
kutdenis said:
All steps are performed without errors, but after entering the root password occurs cyclic reboot! The system will not boot and run a script that ssh is not possible. All manipulations are performed on ubuntu, only in a virtual machine.
Click to expand...
Click to collapse
Shouldn't be happening. I had booted it without any such issue. Tell me your mode number and device name. Also grab kmesg and dmesg for me if possible using TWRP. Also check if the images are not corrupted and are getting flash perfectly.
@TheImpulson , thanks for the ROM ... The much waited rom for me ...but finally you have done bro...:good:
Stuck at chroot step
@TheImpulson, I am getting error at this step
~ # chroot /mnt /bin/bash
bash: groups: command not found
bash: lesspipe: command not found
bash: dircolors: command not found
after this it displays - [email protected]:/#
And then it doesn't accept any command.
please help!!
hassan.h said:
@TheImpulson, I am getting error at this step
~ # chroot /mnt /bin/bash
bash: groups: command not found
bash: lesspipe: command not found
bash: dircolors: command not found
after this it displays - [email protected]:/#
And then it doesn't accept any command.
please help!!
Click to expand...
Click to collapse
Try this:
Code:
TERM=linux HOME=/root PATH=/sbin:/bin:/usr/sbin:/usr/bin:$PATH chroot . /bin/bash
doniks said:
Try this:
Code:
TERM=linux HOME=/root PATH=/sbin:/bin:/usr/sbin:/usr/bin:$PATH chroot . /bin/bash
Click to expand...
Click to collapse
I checked with ls command, the /bin directory is not there.
hassan.h said:
I checked with ls command, the /bin directory is not there.
Click to expand...
Click to collapse
did the mount command work? show the output of
mount
doniks said:
did the mount command work? show the output of
mount
Click to expand...
Click to collapse
mount is successful
[email protected]:~/Z00L$ sudo adb shell
~ # mkdik mnt
/sbin/sh: mkdik: not found
~ # mkdir mnt
~ # mount -O loop /data/rootfs.img /mnt
~ # chroot /mnt /bin/bash
bash: groups: command not found
bash: lesspipe: command not found
bash: dircolors: command not found
[email protected]:/#
hassan.h said:
mount is successful
[email protected]:~/Z00L$ sudo adb shell
~ # mkdik mnt
/sbin/sh: mkdik: not found
~ # mkdir mnt
~ # mount -O loop /data/rootfs.img /mnt
~ # chroot /mnt /bin/bash
bash: groups: command not found
bash: lesspipe: command not found
bash: dircolors: command not found
[email protected]:/#
Click to expand...
Click to collapse
Change the password now
Hello Everyone,
I recently bought this device G7 play with on-going offer with MetroPCS. Since last one week, I've been getting my hands dirty on successfully building and booting the kernel from the source code provided by moto here https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PPYS29.105-134-7
I would like to share with you all my progress currently.
Working:
Boots
Touch works
Not Working:
Camera
Baseband (radio)
A lot more
Screenshot :
{
"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"
}
I will update my progress here and release it once I manage get around few major issues and also I'm working on building TWRP for our device from source.
Sorry for my ignorance, but what does this mean for the g7 play development?, Thnx
Hello, is this 32bit or 64bit?
brickhayabusa said:
Sorry for my ignorance, but what does this mean for the g7 play development?, Thnx
Click to expand...
Click to collapse
I will try to build a functional TWRP, custom kernel and maybe even a ROM.
Electimon said:
Hello, is this 32bit or 64bit?
Click to expand...
Click to collapse
It is a 64 bit build
kD said:
I will try to build a functional TWRP, custom kernel and maybe even a ROM.
It is a 64 bit build
Click to expand...
Click to collapse
Do you have telegram?
@kD
You might be able to get LTE working by reflashing the modem and wiping modemst1 & 2. Your kernel might actually get around the security problems we have with installing twrp on stock as well. I'd love to do some testing with it. If you feel like dropping me a link, please send me a pm.
Spaceminer said:
@kD
You might be able to get LTE working by reflashing the modem and wiping modemst1 & 2. Your kernel might actually get around the security problems we have with installing twrp on stock as well. I'd love to do some testing with it. If you feel like dropping me a link, please send me a pm.
Click to expand...
Click to collapse
Sent a PM to you.
Thanks for your work!!!
A custom kernel for this device will be amazing! Go on!!
Using this kernel im going to build halium-boot eta s0n
This is amazing!! Please continue, you are a hope for us and share your progress with us
nothing new?
@kD
I don't know if you saw this but one of the devs from Motorola finally updated the build process. You'd have to adapt some minor things like folder names, and the -j number but it should work. I can't believe how stupidly complicated building the kernel modules are. No body would remember this line for line, and they waited like a year to tell us this crap.
https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-PPYS29.105-134-7.txt
Spaceminer said:
@kD
I don't know if you saw this but one of the devs from Motorola finally updated the build process. You'd have to adapt some minor things like folder names, and the -j number but it should work. I can't believe how stupidly complicated building the kernel modules are. No body would remember this line for line, and they waited like a year to tell us this crap.
https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-PPYS29.105-134-7.txt
Click to expand...
Click to collapse
Seems like great news! When we can get a 64 bit OS running ill make a zip to convert from this 64 bit rom to 64 bit halium 9!
Hey man! Good work! Any news in your 64bit kernel?
@kD
How do you get past this part compiling the kernel?
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", @ARGV) . \"\n\" ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig || ( rm -f ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig && false )
It originally gave me an error because of an extra ' symbol in there. Upon removing it, the command goes through, but... It drops me into some kind of "perl shell" that I can't get out of to enter the next commands. I almost have a script ready to auto build our kernel, but that perl command is holding up progress.
Spaceminer said:
@kD
How do you get past this part compiling the kernel?
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", [user=2467029]@argv[/user]) . \"\n\" ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig || ( rm -f ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig && false )
It originally gave me an error because of an extra ' symbol in there. Upon removing it, the command goes through, but... It drops me into some kind of "perl shell" that I can't get out of to enter the next commands. I almost have a script ready to auto build our kernel, but that perl command is holding up progress.
Click to expand...
Click to collapse
Hi @Spaceminer.
I'm a new XDA Developers Community member. English is not a my first language. I'm a Software Engineer in my country and I'm 23 years old.
Even so, I'm going to try to support you with anything. I don't know a lot of Android, I've done some Android applications and I know a very little about root, recovery and custom kernels.
I don't know perl, but I've seen that you have forgotten to write ' at the end of this part:
join("\n#\t", @argv) . "\n"
PD: I'm from Mexico. Greetings.
ErikAlvarez00 said:
Hi @Spaceminer.
I'm a new XDA Developers Community member. English is not a my first language. I'm a Software Engineer in my country and I'm 23 years old.
Even so, I'm going to try to support you with anything. I don't know a lot of Android, I've done some Android applications and I know a very little about root, recovery and custom kernels.
I don't know perl, but I've seen that you have forgotten to write ' at the end of this part:
join("\n#\t", @argv) . "\n"
PD: I'm from Mexico. Greetings.
Click to expand...
Click to collapse
That explains the problem. I removed one of those, because it caused an error, but it really needed to be moved to the end... Thank you so much!
What's wrong with this command?
I need help with the syntax on this. There's an error somewhere and I can't find it, so I can't finish building a 64bit kernel. I've tried moving the ' symbol to a few places and nothing works. I'm very lost on this part.
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", [user=2467029]@argv[/user]) . \"\n\"' kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > $kernel_out_dir/mapphone_defconfig || ( rm -f $kernel_out_dir/mapphone_defconfig && false )
Edit: I think that I found the solution. It should actually be this according to build instructions for other Motorola devices.
/bin/bash -c "( perl -le 'print "# This file was automatically generated from:\n#\t" . join("\n#\t", @argv) . "\n"'