Related
{
"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"
}
Hi to all of you, Yuga owners.
Let me introduce CarbonRom, Unofficial: since our device is not officially supported by Carbon team. Obviously this is for UNLOCKED BOOTLOADER
This is only my compilation, all the real work has been done by Team Carbon
Andros11
BigShotRob
Bionic Beast
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
vishal_androidfreak
The original thread is here: http://forum.xda-developers.com/showthread.php?t=2137013
Team carbon's Google+ : https://plus.google.com/communities...2/stream/f82fcffc-02a6-470e-a254-e200b9f78ee5
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
Android 4.4.4
As of today:
This is all very much a work in progress. Carbon Fibers are still in the process of being merged with 4.4.3, but I'm sure it'll be ready soon...
(all features will have to be verifed)
Halo project have been abandonned by Carbon Team because its no more supported by PA Team due to bugs caused by this feature with others including Pie, Omni Switch feature is here to replace it
Bugs:
None for now!
U tell me...
And please, report with logcat or no bugs!...
* By flashing this, you automatically void your warranty!
* If your phone breaks, blows up or runs away from you, do not cry to us!
* Do not ask for ETAs!!
Instructions
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Optional- Flash GApps.
8. Reboot and Enjoy Carbon!
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our goo.im page linked above. It's new, but expanding fast. Just like us!
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our G+ Community: http://community.carbon-rom.com This is where we spend the bulk of our time and the best way to reach us and other community members. We update and frequent this community far more than XDA, simply due to time constraints and the convenience of G+.
5) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Downloads
Here my AFH download folder for Yuga
From now builds will be available for download from server here and or OTA
Yuga builds here, take build according to your device
PA Gapps 4.4.2 thread
Banks Gapps thread
OFFICIAL Carbon's CHANGELOG
Here is my changelog, up here u have Carbon's official changelog to see what's happening at sources...
Code:
For other changes,
simply check my posts when i say
a new build is available
[U]Build 29:[/U]
Carbon sources updated
took off linaro toolchain since its not bringing up nothing better...
back to regular cm11 branch
[U]Build 28:[/U]
Carbon sources updated
Test build with new .230 merges...wi-fi don't work, auto rotation, camera etc...
[COLOR="Red"]don't use[/COLOR]
[U]Build 25 to 27:[/U]
Carbon and repos sources updated
minor fixes
[U]Build 19 to 24:[/U]
Carbon sources updated.../ugraded to 4.4.4
repos updated
build24 starts with linaro
[U]Build18:[/U]
Carbon sources updated to 4.4.3
Repos updated
[U]Build18:[/U]
Completely removed sources; and start from scratch with all new fresh ones
Theme engine fully fixed
Repos updated
[U]Build16/17:[/U]
broken builds
[U]Build15:[/U]
power menu fixed
carbon sources updated
[U]Build11 to 14:[/U]
Repositories updates
Carbon updates
[U]Build 10:[/U]
Carbon sources synced
[U]Build9:[/U]
display and media caf sources merged
carbon sources synced
[U]Build8:[/U]
Yuga device repo updated
Fusion3 common repo updated
Carbon sources synced
theme engine still broken
[U]Build7:[/U]
Carbon sources synced
And led manager is back
[U]Build6:[/U]
Carbon sources synced
[U]Build5:[/U]
device repos updated and carbon sources synced
[U]Build4:[/U]
fusion3 common fix cherry picked with additional commit
from CM (Emilio López) for mp decision also
[U]Build 3:[/U]
fusion3 common repos updated with
new commits from CM (Giulio Cervera)
for mp decision fixes
[U]Build 1 and 2:[/U]
original, no changes...see carbon's gerrit
Here my github
Credits
(in no particular order)
As i already mentionned, indeed Team Carbon
you maybe can show some support to this team by donate'em
Special thanks to these guys who teached me everything =)
@percy_g2
@x10forevers
Obviously CyanogenMod,Sony and Google for sources, repos ...
#include<iforgotyou.h>
Here is a Carbon 4.4.4 review from @panorama click his thanks button!
http://youtu.be/2P8hDDC3lXw
Downloading...........
Sent from my Xperia Z using XDA Premium 4 mobile app
acutraaq said:
Downloading...........
Sent from my Xperia Z using XDA Premium 4 mobile app
Click to expand...
Click to collapse
...and? ...u have it now? loll
Tapatalked with my Yuga
@Alx31TLse thanks very much bro, can't wait to try it, i will give it a try tonight when i get home.
Hi, does this use the latest .101 and .569 blobs and stuff from sony?
Hellscythe said:
Hi, does this use the latest .101 and .569 blobs and stuff from sony?
Click to expand...
Click to collapse
nope, as OP states its built from source.
@Alx31TLse
you can get your missing md5sum running "md5sum filename" from linux bash.
hutilicious said:
nope, as OP states its built from source.
@Alx31TLse
you can get your missing md5sum running "md5sum filename" from linux bash.
Click to expand...
Click to collapse
yeah.....im pretty sure blobs from stock firmware are still used when built from source?..
EDIT: Your G drive quota exceeded, i can't download :/
Hellscythe said:
yeah.....im pretty sure blobs from stock firmware are still used when built from source?..
EDIT: Your G drive quota exceeded, i can't download :/
Click to expand...
Click to collapse
Let me come back home after my workday, because yesterday i wasn't able to upload on dev host, i sent a build for Tsubusa then it was stucked...
@hutilicious
here is the one generated from my zip on sd with ES Explorer...
d5b4b2ea33909f100a4e7a58ab98586b
Tapatalked with my Yuga
Which is your kernel source bro..??..And is it boot with infected new kernel?
Sent from my C6603 using Tapatalk
I don't know man i flashed it yesterday morning before work, i have a life beside xda and compiling u know! lollll
Didn't had time yet...
Why don't u test it and report back?
Kernel's sources are from CM, see my github repos...
Tapatalked with my Yuga
Alx31TLse said:
I don't know man i flashed it yesterday morning before work, i have a life beside xda and compiling u know! lollll
Didn't had time yet...
Why don't u test it and report back?
Kernel's sources are from CM, see my github repos...
Tapatalked with my Yuga
Click to expand...
Click to collapse
Of course ....now download in progress that's why..
EDIT: download was broken..now i cant download gdrive shows download limit was exceeded and wait for 24 hours..F****...
Sent from my C6603 using Tapatalk
Removed.
Just flashed :good: ...only the annoying thing i met was the mp-decision error..i think its cm kernel source issue.. Now am going to test infected kernel..
@shamal
Im uploading on dev host too i m just back home, could u please remove link? i would like to keep a track of downloads...thank you
Tapatalked with my Yuga
First post updated with this AFH download folder so please do not mirror my links, thank you.
anshad666 said:
Just flashed :good: ...only the annoying thing i met was the mp-decision error..i think its cm kernel source issue.. Now am going to test infected kernel..
Click to expand...
Click to collapse
Try this, when my backup is done i will also try it out today:
infected_ said:
confirmed... mpdecision is working with thomas commits. a simple script in init.d solves the issue.
https://www.dropbox.com/s/ho6z0uf8fx24qrj/91mpdecision
just place it in /system/etc/init.d and set: owner - root | group - shell | and permissions = rwxr-xr-x
mpdecision errors are gone, check logcat in attachment.
Click to expand...
Click to collapse
If the build of Alx31TLse is realy made with the new changes of cm which merged the official 569/.101 Sony Kernel and Blob's from thomas1991_12 then this should help and work!
ZeRoWaR said:
Try this, when my backup is done i will also try it out today:
If the build of Alx31TLse is realy made with the new changes of cm which merged the official 569/.101 Sony Kernel and Blob's from thomas1991_12 then this should help and work!
Click to expand...
Click to collapse
mpdecision breaks on official cm kernel too, this build doenst have latest blobs
hutilicious said:
mpdecision breaks on official cm kernel too, this build doenst have latest blobs
Click to expand...
Click to collapse
mp-decision is working on official builds, without the need of the script on init.d...
use trickster mod or similar, to see the cores being disabled. logcat still shows errors, but its working.
I love Carbon Rom
thank you very much for your work
Please remove as this now resolved.
I know that this source is not Lineage but I would think the basic principles for building for an supported device under Lineage would also be applicable to any other source repository.
All of the guides I have found only tell you how to build for a supported device and not any help for an unsupported one. I figured out how to sync a suitable device tree and kernel etc but since the rom source repository does not support my device I can't go any further. I can't get it to build from my sync'd local sources it keeps trying to pull stuff from the original source repository so builds fail at the start.
I have setup a local manifest for this project that sync's the device tree and a kernel and the proprietary blobs and this sync completes without error. next I ran - source build/envsetup.sh and then brunch hlte (not a supported device I know) but that throws up this error -
build/core/product_config.mk:248: * Can not locate config makefile for product "gzosp_hlte". Stop.
Device hlte not found. Attempting to retrieve device repository from GZOSP-Devices Github (http://github.com/GZOSP-Devices).
Repository for hlte not found in the GZOSP-Devices Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/gzosp_manifest.xml
build/core/product_config.mk:248: * Can not locate config makefile for product "gzosp_hlte". Stop.
So I think that the error basically means that github.com/GZOSP-Devices does not have the hlte device listed so can anyone tell me how to make the build point to my local repository after I have sync'd so that it at least starts to build ?
I am a newbie to rom building and have much to learn but I would really appreciate any help you guys could give.
Thanks in advance for any an all help offered.
Purposes of this guideThis guide want to be a how-to use Gerrit, allowing everyone to contribute on AOSP like projects.
Divided in 3 parts:
Now few important stuff needs to be setup before proceeding- -> Minimal setup to use Gerrit.
How to setup & submit for recurent contributes
How to submit patches one time
Here we will setup clones, outside of the build tree. See faq for commit testing.
This mean you do not need build environement to contribute
Important: for projects using Gerrit, Github pull request will never be merged! This also mean you do not need to create a Github fork for every changed projects :victory:
So firstly, I'll explain few terms that are important for you to learn before going towards a bit tricky side.
Git - To be precise, git is a code-sharing website/software that allows you to share your project resources you can 'Make Software, better, together'(That's what the tag line says )!
Now, before I go to gerrit, read this: Major Open Source Projects, like, CyanogenMod, AOKP, OmniROM etc. don't directly accept pull requests and in case you want to make a change in their source for a fix/feature or anything, you need to send them patches over gerrit which are then reviewed by the trusted members of the community and if they find it valuable enough, gets merged into the git repository!
Gerrit(Copying the definition from Wiki) - Gerrit is a free, web-based team software code review tool. Software developers in a team can review each other's modifications on their source code using a Web browser and approve or reject those changes. It integrates closely with Git, a distributed version control system.
So, now, git and gerrit are so closely related, that a patch verified over gerrit can directly be merged on git without much hassel, also please note that your gerrit and git username must be same.
Pull Requests - Pull requests are sent over Git after you fork a repository, make some changes into it and then want the owner to merge those changes into his repository, and that's how community development and Open Source works.
Patches - In simple terms, any changes you make to repos of Open Source Projects like LineageOS, OmniRom or AOKP and send them over gerrit for code review are called Patches.
You can find the Gerrit URL of the project you are working on, on the contribute webpage of the project. Example: OmniRom gerrit is https://gerrit.omnirom.org/ , LineageOS is https://review.lineageos.org/
How GERRIT works?! Now, Gerrit is deployed in place of this central repository and adds an additional concept, a store of pending changes. Everyone still fetches from the authoritative repository but instead of pushing back to it, they push to this pending changes location. A change can only be submitted into the authoritative repository and become an accepted part of the project once the change has been reviewed and approved.
I found a nice diagram explaining this over the internet that will clear your doubts(if any ) -
{
"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"
}
There is two different way to use gerrit:
With git , on your computer (useful for recurrent contribute)
Using the Gerrit WebUI (useful for punctual contribute)
Now few important stuff needs to be setup before proceeding-
Install up Git:
Debian/Ubuntu:
Code:
sudo apt-get install git
Fedora:
Code:
yum install git
ArchLinux:
Code:
pacman -S git
openSUSE:
Code:
zypper install git
Configuring git:
This step is very very important as those ID will be the one which identify you and you cannot change them later!
WARNING: You need to setup the same email as on github.com !
WARNING: email is case sensitive!
(For username I highly recommend to use the same as on your computer, but you could use any username you want)
Code:
git config --global user.email "[email protected]"
Code:
git config --global user.name "your-username"
Setting up SSH Keys(Skip this if you have already set them up) -
Code:
ssh-keygen -t rsa -C "[email protected]"
Now this will create 2 files in ~/.ssh directory as follows:
Adding SSH Keys to your Account :
Code:
cat /home/username_on_pc/.ssh/id_rsa.pub
This will show up few lines over terminal, copy those and add them into your Gerrit profile (Will not be detailed, there is a lot of guides on internet for this part)
Important: you need to setup your username into gerrit UI, otherwise you will never be able to push changes (on the screenshot there is no option to modify username as it is already setup but you should see one):
Test ssh is correctly working :
Code:
ssh -p 29418 <username>@<gerrit address>
If you see this message, then everything is setup and ready to propose changes :
If you get any errors, reread the howto to ensure you are not missing something.
You can also contact your team (there is probably an IRC channel for this) and ask for help.
Setting up the hook Change-ID :
WARNING: this need to be done in every repository or upload will fail!
Code:
gitdir=$(git rev-parse --git-dir); scp -p -P 29418 <username>@<gerrit address>:hooks/commit-msg ${gitdir}/hooks/
Making Changes and Submitting Patches -Way 1. (for recurrent contribute) :
If you have a full build environment setup, the best practice say to not use your build trees for change & submit patches. If you do not have build environment setup, just don't care about this warning
Create a folder (like ~/clones/) where your clones with your changes will reside:
Code:
mkdir ~/clones
cd ~/clones
Go to git where you would make the change and copy the Clone link:
Code:
https://github.com/omnirom/android_device_sony_shinano-common.git
Go back into your terminal and clone the repo (optional: you can specify the branch name with -b <branch name>), then get into clone folder:
Now you can make the change using your favorite text editor (<escape> then ':q<enter>' to exit vim ):
Code:
git status
It tells you what files you modified(In Red color ) and shows on which branch you're currently on.
Now, the committing part,
Run:
Code:
git add -A
Run git status again, and it'll show the files in green color, telling you that the changes have been added.
Now:
Code:
git commit -s
This will commit the changes and open up a Text Editor called NANO. Here you need to edit the commit message that appears at the side of the gerrit window to describe what the patch does.
After writing the commit message, press Ctrl+O and then Enter key to save the commit message and then Ctrl+X to exit the editor. This is the committing part done. :good:
Optional (but better ): you can control what your commit changed, then rework if necessary (see last part of the guide):
Code:
git diff HEAD^
Now submitting the patch -
You need to catch the project path from the Gerrit interface. Go into project, list, and find the repository you changed:
Here the path is android_device_sony_shinano-common. It could include a 'sub-folder' like LineageOS do. For example, same repo on Lineage will be LineageOS/android_device_sony_shinano-common.
WARNING: path is case sensitive.
Go back to your shell and type:
Code:
git push ssh://<username>@<gerrit address>:29418/<repo path> HEAD:refs/for/<branch name>
Way 2. (for punctual contribute) :
Log-in into the Gerrit instance you want to commit into. Go into 'Projects', list, then choose the repo you want to make the change in:
Hit the 'Create Change' button:
This open a popup asking for some information:
Select branch for new change: the branch you want to commit in,
Enter topic for new change: leave empty
Description: Enter commit message
Finally hit Create
Now your change page is open, you can start editing files with the Edit button on the right:
then Add the file you want change:
The file open in an editor, make the needed changes and save with Save button, then Close:
(Redo the step if you need to change multiples files.)
When all your changes are present, hit the Done Editing button to validate your changes.
Your changes are pending and you can display it while clicking on file name:
The changed section is highlighted. If you made a mistake you can use the
icon:
Use the
button to get back on the summary page.
WARNING: your change is only a draft for now, you need to publish it:
Ask for review :
Once your commit is on Gerrit you need to setup a reviewer. This person will comment, reject or submit your patch.
Hardest part is to find the reviewer. You can ask in the dedicated IRC chan of your rom, or use some tricks like check who merged the commits into the repo.
Once you find who will be the reviewer, add it on the dedicated gerrit field:
Once your commit is ok and you want the reviewer take care of it, set-it 'Code-Review +1' and add a comment (will stay on gerrit) about why this change should be merged:
Guess what?! Done!
Congratulations, you just learned gerrit and know how you use it. I hope you'll send some nice patches and respect the Open Source. :victory:
Credits -
v_superuser said:
> Original kanged thread
Click to expand...
Click to collapse
FAQ
Ensure your clone is up to date
Before picking and before writing patch you need to ensure your clone is up-to-date with the remote repository.
Go into the needed folder, then check the remote name:
Here the remote is named 'origin'.
We need to fetch the remote, on the right branch, then switch to that branch:
Code:
git fetch <remote name> <branch>
Code:
git checkout <remote name>/<branch>
(You can notice in my right prompt the current HEAD changed for remote/<remote name>/<branch name> . It is now up to date. )
Warning: Only the checkout command switch your local tree
Warning: git fetch use space between remote name & branch name but git checkout use slash (/) !
How to test pending changes
To test a change pending on Gerrit you need a working build environment for your rom. This guide will not explain how to set it up.
Once you have located the change you want to test,
go into the corresponding folder. Use the project path for hints:
here folder will be device/sony/msm8974-common.
Next use the download button into Gerrit interface
and copy paste the command in your terminal:
If you have merge conflict you will need to solve (with git mergetool, internet search and brain).
Now you can do this step again to merge other commits, or trigger the build for testing.
Update a pending change
You made a commit but notice some problem and it need to be reworked, without creating another one.
You need to follow the Ensure your clone is up to date then How to test pending changes with the commit who need reworking.
Once the commit is fetched locally you can make your changes:
Trigger the amend of the commit:
Code:
git commit [B]--amend[/B]
The git editor open and allow you to change the existing commit message:
Once your change is done, upload it:
The commit is updated (new Patch Set) on Gerrit (no new one was created):
Setup Gerrit as remote for easy reuse
Typing the push command each times could be painful if you upload patches often.
You can add Gerrit as a remote for easy reuse:
git remote add <local name> ssh://<username>@<gerrit url>:29418/<repo name>
Now you can simply use git push command:
Warning: need to be done in each repos!
Warning: This tip do not prevent typing HEAD:refs/for/<branch> each time !
reserved
This is absolutely wonderful guide , thank you for your contribution
git init
Click to expand...
Click to collapse
command should be passed before the below command! otherwise it willl show some error!
gitdir=$(git rev-parse --git-dir); scp -p -P 29418 <username>@<gerrit address>:hooks/commit-msg ${gitdir}/hooks/
Click to expand...
Click to collapse
Thanks for your guide, however, on the 3.4 or more version has a little change, can you update the article?
In addition, your article has a defective attachment (in "Adding SSH Keys to Your Account"), please fix it!
I was looking for it from so long
Thanks man
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working :
Boots
USB OTG
Rotation
Key backlights
Video/Audio playback on mxplayer/vlc for now
What's NOT working :
Everything Else
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Build : https://drive.google.com/open?id=1kHXl7YKIt8qq6Mk3R8FojVz5LZYlokDO
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Donations :
You don't have to but if you want so...
[email protected]
Contributors
Ather
Source Code:
android_vendor_samsung_gts28wifi
android_vendor_samsung_gts2-common
android_device_samsung_gts28wifi
android_device_samsung_gts2-common
android_kernel_samsung_exynos5433
local_manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Testing
Created 2018-04-05
Last Updated 2018-04-05
Congratulations
congratulations
So MTP works as long as usb debugging is disabled, also source resync'd for April 5th patches, will update link in OP later
What is the benefit of this new lineage over PoseidonROM 1.1?
Can you please share your source repos so that others may build? https://github.com/LineageOS is not specific to gts28wifi.
raysucks said:
What is the benefit of this new lineage over PoseidonROM 1.1?
Click to expand...
Click to collapse
This is pure Android from Google as opposed to Samsung's modifications, this is the latest android version (8.1.x) where as Samsung stopped at 7.0 for our t710 model, this has the latest security patch as of yesterday April 5th,whilst our TouchWiz rom has from January
Sure this Rom will have bugs but hopefully we'll fix them
ripee said:
Can you please share your source repos so that others may build? https://github.com/LineageOS is not specific to gts28wifi.
Click to expand...
Click to collapse
I'll do that later when they're all synced up, have to add few fixes
Ather said:
This is pure Android from Google as opposed to Samsung's modifications, this is the latest android version (8.1.x) where as Samsung stopped at 7.0 for our t710 model, this has the latest security patch as of yesterday April 5th,whilst our TouchWiz rom has from January
Sure this Rom will have bugs but hopefully we'll fix them
Click to expand...
Click to collapse
Thanks for the explanation. Does this new lineage support the finger print scanner? Your PoseidonROM from what I've read is the only ROM that supports it, it's a must have for me.
Thx again for your hard work.
raysucks said:
Thanks for the explanation. Does this new lineage support the finger print scanner? Your PoseidonROM from what I've read is the only ROM that supports it, it's a must have for me.
Thx again for your hard work.
Click to expand...
Click to collapse
Sadly no fingerprint yet, you're welcome to continue using PoseidonROM until the bugs are fixed in this
Will do. Off topic, super weird anomaly with my Chase bank application. As a security feature, devices have to be registered. This requires an access code be sent to your email address, this confirms your identity. Once confirmed, you're set. Recently, the Chase application continues to interpret that my device is not registered. Is the device ID a moving target with PoseidonROM 1.1? Never had this occur with 1.0. Thx
Thank you very much for being with us.
complete sources are added to OP
Ather said:
complete sources are added to OP
Click to expand...
Click to collapse
What the difference between your code and mine, which you successfully forked some days ago?
I hope you don't mind if I report to you.
I forked your repos if you decide to delete them.
Anyway, tell us, please, your wonderful oreo development story here in public. What Were you doing during 2 weeks of hard work?
I can prove each string of code there. Where was the problem, how I fixed it etc.. But I never have any thoughts to upload almost useless rom to public, but I had this opportunity since february...
Wanted to be famous? You are famous now as kanger and thief.
ps: i'm very loyal when someone uses my code even without any credits. And I even ignored your uploaded rom until you reuploaded sources yesterday night without any mentions at least... So, you are the thief now and you have to live with it. Good luck.
bonuzzz said:
I forked your repos if you decide to delete them.
Anyway, tell us, please, your wonderful oreo development story here in public. What Were you doing during 2 weeks of hard work?
I can prove each string of code there. Where was the problem, how I fixed it etc.. But I never have any thoughts to upload almost useless rom to public, but I had this opportunity since february...
Wanted to be famous? You are famous now as kanger and thief.
ps: i'm very loyal when someone uses my code even without any credits. And I even ignored your uploaded rom until you reuploaded sources yesterday night without any mentions at least... So, you are the thief now and you have to live with it. Good luck.
Click to expand...
Click to collapse
Hello, I helped him to bring oreo to this tab, this is a work in progress, who told it was not useless to flash it and ready for daily use ?
You are right, he used your sources, might you would like to be added on credit right. A quick pm would have been better.. I do not know you that much, might you started to do lineage 15.1 too, in this case you can create a git project and work together, I would be glad to see this project growing up ! I think working together is the best way to learn from each others !
Ps: useless to call him a thief, this is just a mistake .. useless to create a new drama about this story, hope to see you working together
McFy said:
Hello, I helped him to bring oreo to this tab, this is a work in progress, who told it was not useless to flash it and ready for daily use ?
Are you jealous ?
You are right, we used your sources, might you would like to be added on credit right. But why doesn't send a quick pm instead of writing a post that will be deleted by xda mods or hated by people having interest in news rom for this tab, I do not know you that much, might you started to do linege 15.1 too, in this case you can create a git project and work together, I would be glad to see this project growing up !
Rethink life
Click to expand...
Click to collapse
He was writing me also when he tried to compile...
Do you think the rom without wifi is very useful for users? I dont think so..
Answer me one question: what the difference between my code and his code?
I said I ignored this situation until he reuploaded my sources without leaving any history and mention. But he had my forked sources on his git until yesterday.. I dont know why he decided to assign all work to himself. And I really wonder why the xda stuff, retired in particular allows himself to just steal other work.
I dont need any credits of something, but I spent my time to bring up oreo here and it is very unrespectful to just kang all work, publish with other credits and wrote he spent 2 weeks for that..
Just curious, why you answer to me instead of him?
bonuzzz said:
He was writing me also when he tried to compile...
Do you think the rom without wifi is very useful for users? I dont think so..
Answer me one question: what the difference between my code and his code?
I said I ignored this situation until he reuploaded my sources without leaving any history and mention. But he had my forked sources on his git until yesterday.. I dont know why he decided to assign all work to himself. And I really wonder why the xda stuff, retired in particular allows himself to just steal other work.
I dont need any credits of something, but I spent my time to bring up oreo here and it is very unrespectful to just kang all work, publish with other credits and wrote he spent 2 weeks for that..
Just curious, why you answer to me instead of him?
Click to expand...
Click to collapse
I don't think so too,
He did some edit's to boot,
I think this is a mistake,
This doesn't mean anything here
As I said work together, just let him add you to credit and push the commit history, I am pretty sure it's a mistake
For your 2 last question: He wanted to taste oreo on his tab so he tried to build, I told him some edit's to do on nougat tree to build then boot as your sources wasn't fully fixed about this, he shared it for free here to let people know he work on, I just want you know real reason of what you call a kang, I think it's a simple mistake whith a simple solution that you have to found together, might xda is not place for this and it doesn't have to create a drama.
First of all, i'm no thief or a kanger, the only thing i used from you was your kernel modified for oreo , the rest of the sources were initiated by raymanfx BUT they wouldnt compile, and anan is witness to that because i sent him the files to test aswell, the kernel by lineageOS had sepolicy errors which i tried very hard to fix but they woudnt boot with it, FYI before you initiated Oreo commits to your kernel, i already had added my fixes to it, like the missin zimage type, min/max errors, you can ask matt about that, then when i finally got to bootloop it was ueventd error which remi told me about, after that i was missing manifest which by help of matt i generated for gts2 by looking at his. the sources that were upped had problems which i fixed so i pushed them with them included minus the orignal author thats my bad i agree, but please dont call me a kanger atleast i deserve that much respect. this is not a competition to become famous, you withheld souces and the rom from others before aswell and when i always asked you for help you simply gave meaningless answers, rayman never replied, the lineage irc channel is full of dickheads so i did all of it on my own with help from Matt and remy.
i'll add your forked kernel in OP, and also releasing the bare minimum version was because so others could help me fix it not for becoming famous, i've been on xda since windows mobile days and have made my share of custom roms,apps so i dont need to be famous
Ather said:
the lineage irc channel is full of dickheads
Click to expand...
Click to collapse
I laughed so hard when I read this part! :laugh:
{
"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"
}
ALYNX Nethunter Kernel for Pixel 3/3xl - [Stock][Android 12] and [Android 12L PixelDust/ CAF]
What is Nethunter ?
Kali NetHunter is a free & Open-source Mobile Penetration Testing Platform for Android devices, based on Kali Linux.
Click to expand...
Click to collapse
Code:
I'm not responsible for bricked devices, dead SD cards.
Do some research if you have any concerns about features included in this Kernel.
About the kernel :
The Kernel is based on Kirisakura sources for bluecross
Features:
Internal Wifi Monitor Mode Support (packet injection doesn't works as it is based on qcacld-3.0 which is not capable of packet injection yet)
HID gadget keyboard/mouse
USB WiFi, mac80211 (Monitor mode, packet capture, packet injection) [Compatibility List]
RTL88XXAU USB WIFI Support
RTL8188EUS USB WIFI Support
ATH9K_HTC USB WIFI Support
Ethernet Support
Bluetooth USB Support
SDR Support
BadUSB
for more kernel features look into Kirisakura Kernel thread as it is based entirely on Kirisakura sources
warning: please do not update magisk after flashing the kernel, you can update the magisk before flashing the kernel.
Installation:
Boot the device into Twrp recovery .
Backup your current kernel inside Twrp
Download Alynx-12L.zip if you're using Android 12L PixelDust or CAF rom else download Alynx-12-nethunter-bluecross.zip for [STOCK/ PIXELDUST CAF ANDROID 12 ]
Flash the zip (Flashing the kernel/zip will keep root)
Install Busybox
Download Wireless_firmware.zip open Magisk and install the zip as Magisk module
Install Nethunter store
Install Nethunter app & Nethunter terminal from Nethunter store
Open Nethunter app & Download the full chroot kalifs within the app and let the app setup everything. After it finishes it'll start the chroot automatically.
Update the sources with apt-get update && apt-get upgrade in the chroot using nethunter terminal
Reboot the device
Note: if nethunter app crashes open any android terminal in su environment and paste the following.
Code:
pm grant com.offsec.nethunter android.permission.ACCESS_FINE_LOCATION
pm grant com.offsec.nethunter android.permission.ACCESS_COARSE_LOCATION
pm grant com.offsec.nethunter android.permission.READ_EXTERNAL_STORAGE
pm grant com.offsec.nethunter android.permission.WRITE_EXTERNAL_STORAGE
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_SU
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_NH
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_NH_LOGIN
Screenshots:
Tested on pixel 3 with tplink wn722n v1 and v3 both working perfectly well : )
View attachment 5636393 View attachment 5636395 View attachment 5636397 View attachment 5636399
Extra:
if you want to replace nethunter terminal with termux (not completely nethunter main app will still launch nethunter terminal everytime for any operation but you can access kali chroot environment from termux.
(i know nethunter terminal sucks)
Follow these steps to access the environment from termux:
Install termux from f-droid or from nethunter store
Open termux and install root repo using pkg update && pkg install root-repo tsu wget
Download the script from termux wget https://raw.githubusercontent.com/name-is-cipher/boot-nethunter/main/install_boot-kali.sh
chmod +x install_boot-kali,sh && ./install_boot-kali.sh
let it setup everything.
restart termux and type boot-kali to access the nethunter chroot environment
Spoiler: Changelog: [2022/10/29]
- Alynx [NE]
- Bluetooth Support (Added MIssing Drivers)
- Ethernet Support
- Fix RTL 8XXX SL (Replaced)
- All the goodies from KIrisakura Kernel
Thanks to @freak07 for his amazing work.
Downloads & Links :
- Flashable Zip: https://mega.nz/file/nIQTlZYT#GOzWmxygnQa-HX41EtLfJCybZvOdXPMUu3Yx64xYTgg
Spoiler: Changelog: [2022/10/02]
Alynx [End of Life] PixelDust Android 13 CAF
- Upstream Kirisakura
- all the goodies from kirisakura kernel + some modifications from @spezi77
Thanks to @freak07 for his amazing work.
Links: https://mega.nz/file/iRBSWDzZ#0gqZgWYmWLCanRkIjts-4VagW5lsPAm7i7zxfYqUj6M
Credits:
Freak07 For KIrisakura Kernel
Team Kali For Nethunter
Kimocoder For wifi patches
Darkar25 For fixing wifi bugs
Special Thanks to Matthias for helping with the toolchain
XDA:DevDB Information
Alynx Nethunter Kernel For Pixel 3/3xl
Contributors: V3rB0se
Source Code: https://github.com/V3rB0se/Alynx-Nethunter
Version Information
Status: Stable
Stable Release Date: 12/06/2022
Created 13/06/2022
Last Updated 13/06/2022
Thank for this build . But i have problem when install TL722v1 on nethunter to use it . Wish you support soon
chiinh9h said:
Thank for this build . But i have problem when install TL722v1 on nethunter to use it . Wish you support soon View attachment 5685105
Click to expand...
Click to collapse
it should be working already. no need to insert anything. just flash the kernel install the firmware module, run wifite and see if it detects your wifi adapter.
Hi, could you provide a Guide for building this kernel? I tried to build, and the build was successful, but the touchscreen is not working. Am I missing something?
I face this same problem when I compile the sources from the stock kernel after modifying the defconfig for nethunter. Could you help?
Toolchain Used: Google toolchain from the Kernel repo tree.
Thanks.
MShivaG said:
Hi, could you provide a Guide for building this kernel? I tried to build, and the build was successful, but the touchscreen is not working. Am I missing something?
I face this same problem when I compile the sources from the stock kernel after modifying the defconfig for nethunter. Could you help?
Toolchain Used: Google toolchain from the Kernel repo tree.
Thanks.
Click to expand...
Click to collapse
you are missing some extra modules
I fixed the touchscreen issue.
Now the kernel panics and reboots whenever I tried to run wifi commands like iwconfig, wifite, airmon-ng. I used b1c1_defconfig and updated it with nethunter kernel configs.
ended up with kernel panic!
which defconfig you have used to build? Could you please update in the kernel sources?
Thanks
MShivaG said:
I fixed the touchscreen issue.
Now the kernel panics and reboots whenever I tried to run wifi commands like iwconfig, wifite, airmon-ng. I used b1c1_defconfig and updated it with nethunter kernel configs.
ended up with kernel panic!
which defconfig you have used to build? Could you please update in the kernel sources?
Thanks
Click to expand...
Click to collapse
try to build it from this source
V3rB0se said:
try to build it from this source
Click to expand...
Click to collapse
With b1c1_defconfig? b1c1_defconfig is with Kirisakura configs.
V3rB0se said:
try to build it from this source
Click to expand...
Click to collapse
I traced back the issue. It seems to be from the ioctl. Have you faced this issue?
MShivaG said:
I traced back the issue. It seems to be from the ioctl. Have you faced this issue?
Click to expand...
Click to collapse
it was a headache fixing these compile time errors i don't even remember them correctly but they're fixed now you should compile the kernel from the link i posted earlier i fixed all these errors in it.
V3rB0se said:
it was a headache fixing these compile time errors i don't even remember them correctly but they're fixed now you should compile the kernel from the link i posted earlier i fixed all these errors in it.
Click to expand...
Click to collapse
After a full research on the kernel hardening I found that this is because CFI conflicts. The kernel freaks out and panic in response to the cfi_failure. After disabling the CFI and LTO the kernel runs smoothly and all the attacks are working fine.
Could you tell me if your kernel had been compiled with CFI disabled?
The kernel source is missing some modules(So far I found files for wiregaurd is missing). Could you please check and update the kernel sources?
MShivaG said:
After a full research on the kernel hardening I found that this is because CFI conflicts. The kernel freaks out and panic in response to the cfi_failure. After disabling the CFI and LTO the kernel runs smoothly and all the attacks are working fine.
Could you tell me if your kernel had been compiled with CFI disabled?
The kernel source is missing some modules(So far I found files for wiregaurd is missing). Could you please check and update the kernel sources?
Click to expand...
Click to collapse
you can check the defconfig cfi is disabled in it. and what do you mean it is missing some modules? it's just another fork of kirisakura kernel with some minor changes. it is clearly mentioned in the post that the kernel uses sources from kirisakura kernel.
MShivaG said:
After a full research on the kernel hardening I found that this is because CFI conflicts. The kernel freaks out and panic in response to the cfi_failure. After disabling the CFI and LTO the kernel runs smoothly and all the attacks are working fine.
Could you tell me if your kernel had been compiled with CFI disabled?
The kernel source is missing some modules(So far I found files for wiregaurd is missing). Could you please check and update the kernel sources?
Click to expand...
Click to collapse
I can't help you if you're not using the source i provided, CFI and LTO were disabled in the source, you shouldn't be complaining about it when you're using the source from i don't know where?
V3rB0se said:
you can check the defconfig cfi is disabled in it.
Click to expand...
Click to collapse
Which defconfig? I already asked it. I don't find any of the defconfig match nethunter configurations. I don't find any defconfig with local version "Alnyx Nethunter".
V3rB0se said:
it is clearly mentioned in the post that the kernel uses sources from kirisakura kernel.
Click to expand...
Click to collapse
I know the source is from Kirisakura.
V3rB0se said:
I can't help you if you're not using the source i provided, CFI and LTO were disabled in the source, you shouldn't be complaining about it when you're using the source from i don't know where?
Click to expand...
Click to collapse
I tried to compile with your source( see the error, missing wiregaurd). I have attached the screenshot. You should have mentioned that the security feature CFI and LTO are disabled in the first place in your post. It is one of the important security features of Kirisakura kernels. We need to fix the CFI conflicts not disable them.
V3rB0se said:
I can't help you if you're not using the source i provided
Click to expand...
Click to collapse
I am not crazy to ask this forum if I am not using the source described here. As your source is throwing errors I used Kirisakura sources and it's working fine. See the screenshot if you don't believe it.
Why are you too confident? By mistake, you should have forgotten to push the code from your machine.
Don't you check once before replying?
Please don't take anything wrong. We are here to help each other.
MShivaG said:
Which defconfig? I already asked it. I don't find any of the defconfig match nethunter configurations. I don't find any defconfig with local version "Alnyx Nethunter".
I know the source is from Kirisakura.
I tried to compile with your source( see the error, missing wiregaurd). I have attached the screenshot. You should have mentioned that the security feature CFI and LTO are disabled in the first place in your post. It is one of the important security features of Kirisakura kernels. We need to fix the CFI conflicts not disable them.
I am not crazy to ask this forum if I am not using the source described here. As your source is throwing errors I used Kirisakura sources and it's working fine. See the screenshot if you don't believe it.
Why are you too confident? By mistake, you should have forgotten to push the code from your machine.
Don't you check once before replying?
Please don't take anything wrong. We are here to help each other.
Click to expand...
Click to collapse
what makes you so confident that it's missing the wireguard ? use the build script from kirisakura that's not how it works, and for the defconfig it doesn't contain alynx nethunter (my bad) but the default b1c1_defconfig doesn't contain LTO and CFI flags and the main reason for disabling them in the first place is my potato system which doesn't have enough ram to compile the sources with lto and cfi enabled. if it doesn't contain some modules regarding nethunter do inform me I'll push them in the upcoming builds.
and if you're looking for a post on "how to compile a kernel" you're in the wrong place my friend. im not here to teach you. you can visit nathan chance guide on compiling a kernel.
if you care about security you shouldn't install nethunter. see this
V3rB0se said:
what makes you so confident that it's missing the wireguard ? use the build script from kirisakura that's not how it works, and for the defconfig
Click to expand...
Click to collapse
I have attached the screenshot in the previous reply. The same issue occurs even when using Kirisakura build script. I don't know why you removed the script 12 days before. try yourself the fresh clone of your source and try to build. I'm tired of explaining.
V3rB0se said:
and if you're looking for a post on "how to compile a kernel" you're in the wrong place my friend.
Click to expand...
Click to collapse
When did I ask you this my dear friend?
V3rB0se said:
if you care about security you shouldn't install nethunter.
Click to expand...
Click to collapse
I do agree and I have already read this before installing chroot.
MShivaG said:
I have attached the screenshot in the previous reply. The same issue occurs even when using Kirisakura build script.
Click to expand...
Click to collapse
why bother asking if you feel "tired of explaining"
for the removal of build script it was the wrong one. i accidentally put it there.
check if your cloud is blocking the connection as the kernel fetches latest wireguard
Alynx-Nethunter/fetch-latest-wireguard.sh at backup · V3rB0se/Alynx-Nethunter
Alynx nethunter kirasakura sources for pixel 3 and pixel 3xl - Alynx-Nethunter/fetch-latest-wireguard.sh at backup · V3rB0se/Alynx-Nethunter
github.com
V3rB0se said:
why bother asking if you feel "tired of explaining"
for the removal of build script it was the wrong one. i accidentally put it there.
check if your cloud is blocking the connection as the kernel fetches latest wireguard
Alynx-Nethunter/fetch-latest-wireguard.sh at backup · V3rB0se/Alynx-Nethunter
Alynx nethunter kirasakura sources for pixel 3 and pixel 3xl - Alynx-Nethunter/fetch-latest-wireguard.sh at backup · V3rB0se/Alynx-Nethunter
github.com
Click to expand...
Click to collapse
OMG! Finally. Thank you for clarifying. This is what I am looking for.