Related
The reason I post my ROM here is because I'm soon starting with a new rom, broodROM KitKat which will also be available for the Note 3, So I figured why not test it on my current AOSP ROM (to see if there is any trouble on compiling, but no!). This AOSP is based on the real Google AOSP, no real further modifications (only thing is that it includes DeviceSettings from the S4 currently), and AppOps is exposed. that's all.
It includes the stock CM11 kernel (which is kinda crappy). but I don't have the device so cannot make decent kernel myself without testing. Also the ROM is 100% untested. but it compiled without any error with my sources (www.github.com/AOSP-S4-KK) so I think it's alright.
Working List
- You tell me I have no idea :silly:
Download Alpha 1
www.broodplank.net/files/AOSP-442-N9005-Alpha-1.zip
on alpha 01 you need to flash a custom kernel
SEND ME LOGCAT! BECAUSE CURRENTLY IT SEEM TO BOOTLOOP
The device name is listed as hlte in settings / build.prop, don't worry this is actually hltexx
Download Gapps Lite + SuperSU (yes it's not rooted by default, I recommend installing this package)
http://broodplank.net/files/gapps-4.4.2-lite-with-supersu-1.86.zip
Sources
- https://github.com/aosp-s4-kk
Download:
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u git://github.com/AOSP-S4-KK/platform_manifest -b kk-4.4
repo sync
Building:
Code:
. build/envsetup.sh
lunch
make otapackage
reserved1
Sweet man!! Thanks always looking for something new to flash lol downloading now
Sent from my iPad using Tapatalk
Downloading!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thankyou OP
anybody that has tried this, can you let me know if the temp/humidity sensors are still working after a few hours? as with other cm roms they stop working for me
Awesome Broodplank! Just switched from the Galaxy S Plus to the Note 3, always enjoyed your roms on there. Will try out this one! Keep up the good work
Sent from my SM-N9005 using xda app-developers app
Flashed and it went straight into Odin mode and said "Could not do normal boot" - I'm on the new Kitkat bootloader.
radicalisto said:
Flashed and it went straight into Odin mode and said "Could not do normal boot" - I'm on the new Kitkat bootloader.
Click to expand...
Click to collapse
Lol what the hell, that's almost impossible that my rom triggered download mode XD.
But it could be true, I have no clue since I do not have the device. what you could try is using the boot.img & /system/lib/modules from CM11 nightly.
btw, just downloaded CM11 and noticed there are NO modules in the kernel of hltexx. this means the kernel I added will not boot most likely.
So please install this zip after installing the rom:
www.broodplank.net/files/aosp-442-hltexx-kernel.zip
broodplank1337 said:
Lol what the hell, that's almost impossible that my rom triggered download mode XD.
But it could be true, I have no clue since I do not have the device. what you could try is using the boot.img & /system/lib/modules from CM11 nightly.
btw, just downloaded CM11 and noticed there are NO modules in the kernel of hltexx. this means the kernel I added will not boot most likely.
So please install this zip after installing the rom:
www.broodplank.net/files/aosp-442-hltexx-kernel.zip
Click to expand...
Click to collapse
OK - will try again now and let you know :good:
and new bootloader ?
Just bootloops with that .zip you added.
I did however change your kernel zip after the bootloop and used - temasek's HLTE custom kernel - I am now on the Android start up screen you have added but it is stuck on there.
radicalisto said:
Just bootloops with that .zip you added.
I did however change your kernel zip after the bootloop and used - temasek's HLTE custom kernel - I am now on the Android start up screen you have added but it is stuck on there.
Click to expand...
Click to collapse
ok good, could you open up adb shell, and send me the logcat, since I have no idea what actually could be the cause atm.
Yup will do it shortly, just heading home now
Sent from my CM11 Kitkat powered N9005
radicalisto said:
Yup will do it shortly, just heading home now
Sent from my CM11 Kitkat powered N9005
Click to expand...
Click to collapse
Ok thank you very much, without some proper logcat I cannot fix anything since I don't have the device :silly:
Anyways, I think the problem won't be a serious one, since the rom has msm8974 support
www.broodplank.net/logcat for uploading logcats pls
broodplank1337 said:
Ok thank you very much, without some proper logcat I cannot fix anything since I don't have the device :silly:
Anyways, I think the problem won't be a serious one, since the rom has msm8974 support
www.broodplank.net/logcat for uploading logcats pls
Click to expand...
Click to collapse
Sorry I couldn't manage to get a logcat via ADB due to some kernel issues with connecting to the PC - I'll try again today. - Is It possible you are using the old CM sources rather than the unified build sources? - device changed from HLTEXX to HLTE
radicalisto said:
Sorry I couldn't manage to get a logcat via ADB due to some kernel issues with connecting to the PC - I'll try again today. - Is It possible you are using the old CM sources rather than the unified build sources? - device changed from HLTEXX to HLTE
Click to expand...
Click to collapse
This ROM is built from pure AOSP sources not CM.
Hope a working build comes up soon, really like pure AOSP ROMs!
gianton said:
This ROM is built from pure AOSP sources not CM.
Hope a working build comes up soon, really like pure AOSP ROMs!
Click to expand...
Click to collapse
Ah I dropped the herp a derp then hahah, Nah reason I thought that was because of the CM kernel used to boot it up. Thanks for correcting :good:
---------- Post added at 08:56 AM ---------- Previous post was at 08:55 AM ----------
@gianton it'll boot into splash screen with temasek's kernel, if you wanna try and grab an ADB Logcat? - I'm having issues getting one :crying:
Sorry for not providing a good kernel, the thing is I cannot compile it decently with the ROM. it says I have to add module support and recontinue, thing is, the note 3 does not use it. but my build forces it.. Anyone have experience on CM with compiling the kernel? (the kernel is from CM after all)
You could try temasek or Yank555 or wootever for help with kernels as they're pretty decent at them - civato knows his stuff also, however I believe he has only worked with Stock samsung kernels and not CM stuff.
Still cannot get ADB logcat, phone won't recognise in PC
Hi folks,
I just started to port UbuntuTouch for the Sony Xperia Z Ultra and I think I should have a *.zip ready for testing in 2 weeks.
Until then, I will use this thread as a scrap book to document all the troubles I run into, all the things that needed my special attention and fixes that are not that obvious. I hope there will be some fellas brave enough to test everything and report back or even to join me with the development.
Best regards,
Kalle
First Update:
I found that the Ubuntu Touch version that ist based on CyanogenMod was not updated to a more recent version. This means that I have to either look into AOSP or backport everything to CM-10.1. I think backporting is kinda stupid because newer we are writing new software to improve things. Sadly I don't have much experiance with AOSP so I will have to find out how everything works and what the differences to CyanogenMod are.
The good news is, that I'm catching up with the mailing list, which means I'll have a place to call for help.
Also I'm in the progress to start a git repo, but I'm unsure what I will need to add, maybe some common stuff from sony does not need to be changed.
So long,
Kalle
Update!
There is a new porting guide! See here
I already freed some space for it and ordered a bit more ram so after my exam next week, I'll pick this up/Start all over.
Hope you are as excited as I am,
Kalle
XDA:DevDB Information
Ubuntu Touch for Sony Xperia Z Ultra, ROM for the Sony Xperia Z Ultra
Contributors
KalleEatingBrain, Kohelet
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Testing
Created 2014-05-14
Last Updated 2015-02-24
freaking awesome!
freaking awesome!
i would like to test. maybe i can help with developing/porting
Thank you for your efforts. I will test if needed.
Sent from my C6806 using XDA Premium 4 mobile app
Great this would be awesome if you can make it happen. I'm here for testing if required.
Sent from my C6833 using XDA Premium 4 mobile app
In also here for testing... Ubuntu Touch has intruiged me, I would love to try it out.
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
iBuzman said:
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
+1
Nice.ill be watching out everyday
Sent from my C6833 using XDA Premium 4 mobile app
blueether said:
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
Click to expand...
Click to collapse
Cool, thanks can you give me a hint on how to deal with new targets in Aosp? I mean setting up the files in a way "lunch" is able to find the right target.
Sent from my C6833 using XDA Free mobile app
vendersetup.sh file in vender/ might be what you are looking for?
have a gander at this http://www.kandroid.org/online-pdk/guide/build_new_device.html
How are you doing on this? I've just started working on this as well and am curious to know how far along you've gotten/what issues you've run into.
Sent from my Nexus 7 using XDA Free mobile app
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Kohelet said:
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Click to expand...
Click to collapse
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
KalleEatingBrain said:
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
Click to expand...
Click to collapse
I actually got past the libhybris issue. The problem was that the porting guide is out of date. It's based on using cm-10.1 whereas the current source for Ubuntu is based on cm-11.0. So if you use 4.4.2 instead instead of 4.2.2 then it works. But there are so many other issues and the documentation for fixing them is so poor. I've kept a running list of problems I've come across and the solutions for them (it's below).
Also they dropped the whole UCM thing so you should be able to get sound working once you actually get a working build, but I couldn't get it to build. The error that is currently in my way has to do with "No rule to make target signapk.jar needed by com.qualcomm.location" or something or other. And I found nothing on how to solve that online.
At this point I've decided to take a short break from the whole thing because it's so frustrating.
Once I get motivated to work on it again, I'll probably start from scratch.
Issues List (I apologize for not being specific about the errors, I didn't write them down verbatim):
If you get an error about libelf you need to add CyanogenMod/android_external_elfutils to your local_manifests/roomservice.xml and also add external/elfutils under subdirs in build/core/main.mk
Don't forget to also add device/sony and vendor/sony to build/core/main.mk as well.
The build will complain about not having a rule to make android-boot.img. To fix you have to go to device/sony/fusion3-common/custombookimg.mk and change boot.img to android-boot.img. You need to make the same change in device/sony/rhine-common/custombootimg.mk
I got an error about android.hardware.bluetooth_le.xml. If you just restart the build it doesn't complain, but I didn't find a proper solution to that.
If you get the libhybris error you have the wrong version of the Ubuntu source. Make sure you're using 4.4.2 when you phablet-dev-botstrap. It should be phablet-dev-bootstrap --sources aosp --repo-branch phablet-4.4.2_r1 [target_directory]
You might get an error about a product_config.mk and how it's missing a makefile for togari. You have to make sure that in device/sony/togari Android.mk, cm.mk, full_togari.mk, and vendorsetup.sh PRODUCT_NAME is the same. I solved this by changing PRODUCT_NAME to cm_togari in all of them and then renamed full_togari.mk to cm_togari.mk
You might get an error like MODULE.TARGET.SHARED_LIBRARIES.libOmxCore already defined in hardware/qcom/media. You should have CyanogenMod/android_hardware_qcom_media-caf-new in your repo manifest with a path of android/qcom/media-caf-new so you can safely rm -rf the hardware/qcom/media directory to get past this error.
If you get an error about dtbToolCM, add /device/qcom/common/dtbtool to your subdirs in build/core/main.mk
You may get an error about mkbootimg, that's because Sony uses a different version of mkbootimg. The only option I found was to download it from the internet (Thanks DooMLorD!). Once you get that version edit device/sony/rhine-common/custombootimg.mk and replace $(MKBOOTIMG) with the path to your downloaded mkbootimg binary.
You might get an error about no rule to make target something/something/signapk.jar needed by something/something/com.qualcomm.location. I didn't find a solution to this error.
Click to expand...
Click to collapse
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
blueether said:
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
Click to expand...
Click to collapse
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Kohelet said:
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Click to expand...
Click to collapse
Yeh carbon and slim were easy to build, and simple fixes. AOSP on the other hand I wish I had kept a build log
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch. I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
KalleEatingBrain said:
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch.
Click to expand...
Click to collapse
That could potentially be a major source of my problems. i wasn't aware of that.
I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
All I have at the moment is a fork of the CM repos. Feel free to add me to your repo. My username on Github is Kohelet as well. I can start to look into removing java dependencies as well.
As for the sound, the mailing list made it appear as if it was a simple matter of running
Code:
$ sudo apt-add-repository ppa:ci-train-ppa-service/landing-018
$ sudo apt-get update
$ sudo apt-get dist-upgrade
$ sudo apt-get install pulseaudio-module-droid
I could be wrong though.
This thread is NOT for general Q & A about using the kernel or configuring a specific version.
This thread IS for sharing source code or attempting to apply debugging to code changes.
In English: This is what a development thread really looks like. No downloads, No user manual.
Note to Mods: OT is welcome, so long as it is relevant to the kernel developer experience
Building the kernel 101:
A clean branch with only the build tools, ramdisks, and MacOS updates is at:
https://github.com/StarKissed/starkissed-kernel-trlte/tree/master
The stockish branch adds Linux patches, mainline updates, and SELinux mods
The deported branch is the customized version described in the OP feature list
You are going to need a few things, especially if building this kernel for MacOS.
GCC 4.7 (This is the version Samsung's documentation listed)
An updated mkbootimg (Must have DTS support)
A dtbtool (Included in the source, but only for Linux)
Insomnia (Not a requirement, but it will help you in the long run)
For MacOS, the tools are available from the following repositories:
https://github.com/StarKissed/android-toolchain-eabi-4.7
https://github.com/StarKissed/starkissed-build-tools
Let's jump ahead a moment for those of you who have built kernels and notice your boot.img is only around 11 MB while the versions you see listed here are all roughly 14 MB. This is where the new mkbootimg and dtbtool are necessary.
Attempting to retrieve the commandline arguments from the boot.img will not tell you one important piece:
Code:
./dtbtool -o dt.img -s 4096 -p ../scripts/dtc/ ../arch/arm/boot/dts/
chmod a+r dt.img
mkbootfs (ramdisk creation)
mkbootimg (mkbootimg params) --dt dt.img
This takes the DTSI that was built into a dtb as one of the first steps in the compile process and turns it into an image that is appended to the end of the boot.img. The dt.img just happens to be about 3 MB. (11 MB + 3 MB = 14 MB)
If you grabbed the original Samsung kernel source, you may notice that their default compile script directs the build to an "out" folder in the root of the kernel directory.
The obvious advantage to this is that their clean command runs into some errors, so the clean process is simply deleting the "out" folder and making a new one.
This doesn't work for a lot of the custom components you may want to add to your kernel, though. Some modifications, such as intelli-thermal, rely on a subdirectory that is referenced in the Makefile.
Building to this out folder will result in an error because it cannot find the output of that component, but building in the tree, or actual source, will also result in an error. The lesser of two evils is to fix in-tree builds.
Code:
Instructions for TRACE_INCLUDE_FILE in include/trace/define_trace.h say
"the path is relative to define_trace.h, not the file including it".
Fix in-tree compilation by making the path relative to define_trace.h.
What this means is that when you have a line that refers to the TRACE_INCLUDE_PATH or an include reference to a file that uses a relative location instead of a global, these need to be updated
The only two files that currently require updates in the stock source code are
Code:
drivers/scsi/ufs/ufs_test.c
#include -> #include "../sd.h"
and
Code:
drivers/video/msm/mdss/mdss_mdp_trace.h
#define TRACE_INCLUDE_PATH . -> #define TRACE_INCLUDE_PATH ../../drivers/video/msm/mdss/
If you want to be able to debug your kernel, you will need to enable last_kmsg.
Open up the arch/arm/configs/apq8084_sec_defconfig and add
Code:
CONFIG_SEC_DEBUG_NOCACHE_LOG_IN_LEVEL_LOW=y
CONFIG_PRINTK_PROCESS=y
CONFIG_SEC_DEBUG_LOW_LOG=y
More to come soon...
This is a great idea!
Looking fwd to seeing this thread take off...it will be very interesting for sure.
Sent from my SM-N910W8 using Tapatalk 2
@ktoonsez im back ready to play my man
@twistedumbrella my man i hope i dont become a ball buster on this thread but i have the 1st 2 questions on this thread:
1. How do you patch your kernels? (i use the p1 command.. is there another way?)
2. How did you manage to make the OC values show?
Disclaimer: I may have a lot of follow up questions
friedrich420 said:
@ktoonsez im back ready to play my man
@twistedumbrella my man i hope i dont become a ball buster on this thread but i have the 1st 2 questions on this thread:
1. How do you patch your kernels? (i use the p1 command.. is there another way?)
2. How did you manage to make the OC values show?
Disclaimer: I may have a lot of follow up questions
Click to expand...
Click to collapse
I use git am -3 so that any issue defaults to a merge then git mergetool to resolve it.
Switching the index in the dtsi that was modified was the only change to show it that I remember needing.
https://github.com/StarKissed/stark...mmit/695abe187620acf513b33237042925d60a99f0c1
friedrich420 said:
@ktoonsez im back ready to play my man
@twistedumbrella my man i hope i dont become a ball buster on this thread but i have the 1st 2 questions on this thread:
1. How do you patch your kernels? (i use the p1 command.. is there another way?)
2. How did you manage to make the OC values show?
Disclaimer: I may have a lot of follow up questions
Click to expand...
Click to collapse
Im back too.
ktoonsez said:
Im back too.
Click to expand...
Click to collapse
right on
any thoughts my man?
friedrich420 said:
right on
any thoughts my man?
Click to expand...
Click to collapse
Im in the process of just starting over from the "F" source and looking for testers on INTL thread. I wish I didnt have to start over but looks like Im going to have to
ktoonsez said:
Im in the process of just starting over from the "F" source and looking for testers on INTL thread. I wish I didnt have to start over but looks like Im going to have to
Click to expand...
Click to collapse
we know for sure that your source without bfq works fine... now its a matter of figuring out what of all the additions from yesterday's source to today's source caused the bootloop..
friedrich420 said:
we know for sure that your source without bfq works fine... now its a matter of figuring out what of all the additions from yesterday's source to today's source caused the bootloop..
Click to expand...
Click to collapse
I wonder if its any of the top 4 commits from here:
https://github.com/ktoonsez/KTNOTE4/commits/tw4.4?page=2
ktoonsez said:
I wonder if its any of the top 4 commits from here:
https://github.com/ktoonsez/KTNOTE4/commits/tw4.4?page=2
Click to expand...
Click to collapse
give me a little bit of time and ill revert it manually and compile again the one i compiled in the afternoon (your morning)
I got lost in Freedom Wars for a bit. I need to figure out an issue with thermal then I'll be back
friedrich420 said:
give me a little bit of time and ill revert it manually and compile again the one i compiled in the afternoon (your morning)
Click to expand...
Click to collapse
Here is a test one starting all over again, just has OC and Voltage control:
http://ktoonsez.jonathanjsimon.com/note4/TW/KT-NOTE4-KK4.4-TW-N910-11.13.2014D.zip
ktoonsez said:
Here is a test one starting all over again, just has OC and Voltage control:
http://ktoonsez.jonathanjsimon.com/note4/TW/KT-NOTE4-KK4.4-TW-N910-11.13.2014D.zip
Click to expand...
Click to collapse
Unfortunately same bahavior my man..
friedrich420 said:
Unfortunately same bahavior my man..
Click to expand...
Click to collapse
LOL, really? I just had 3 people boot up successfully, finally. You have the "F" or the "G"?
EDIT:
The guy I am testing with has the "G".
ktoonsez said:
LOL, really? I just had 3 people boot up successfully, finally. You have the "F" or the "G"?
Click to expand...
Click to collapse
the F...
friedrich420 said:
the F...
Click to expand...
Click to collapse
Just edited my post above, the guy that is answering me quick has the "G". Now Im really getting PISSED!!!!!!!!!! WTH!!
ktoonsez said:
Just edited my post above, the guy that is answering me quick has the "G". Now Im really getting PISSED!!!!!!!!!! WTH!!
Click to expand...
Click to collapse
Did anyone diff the ramdisk? If not, I can throw the two in git and see if anything lights up. I have the visual editor for Mac for exactly that.
ktoonsez said:
Just edited my post above, the guy that is answering me quick has the "G". Now Im really getting PISSED!!!!!!!!!! WTH!!
Click to expand...
Click to collapse
this may or may not confuse you more...
i made a test git repository : https://github.com/friedrich420/Note4-AEL-Kernel2
all i did was cherry pick your oc and voltage control commits..
It booted im running it @2.99ghz right now and its fine...
Could it be that you need the F source my man?
twistedumbrella said:
Did anyone diff the ramdisk? If not, I can throw the two in git and see if anything lights up. I have the visual editor for Mac for exactly that.
Click to expand...
Click to collapse
I started with stock N910F ramdisk in version "C", version "D" went back to my original universal ramdisk you can try the "C" and see if anything changes:
http://ktoonsez.jonathanjsimon.com/note4/TW/KT-NOTE4-KK4.4-TW-N910-11.13.2014C.zip
friedrich420 said:
this may or may not confuse you more...
i made a test git repository : https://github.com/friedrich420/Note4-AEL-Kernel2
all i did was cherry pick your oc and voltage control commits..
It booted im running it @2.99ghz right now and its fine...
Could it be that you need the F source my man?
Click to expand...
Click to collapse
That is exactly what I just merged in so the "D" that wont boot for you is pretty much the same thing, lol. See what happens on the "C" version which is stock N910F ramdisk.
Is anyone trying to work on the Honor 7? I've got the the point now where I can't continue.
Things I know:
Kernel source compiles with no issues
Boot image has secure boot for first 4095 bytes
Kernel and ramdisk can be extracted easily
Bootloader is crap! Doesn't allow fastboot boot
Things I can't do:
Repack a stock boot image! Tried countless ideas. Various unmkbootimg give differing offset values for kernel and ramdisk, tried all those, tried zeroing off the secureboot section. I either get hang on Honor or bootloader error
Superr's kitchen doesn't even recognise it as a valid boot.img, I thought that was my lifeline..
Can't create flashable zip, various update-binary's have been tried - including Huawei's own pulled from the 140 OTA, can't get any edify zip to run (I know shell scripts will work, that's how SU installs.)
It's either something I'm doing wrong (very likely), or this handset is so non-standard, we as a community are screwed! (less likely but possible)
Just to note - I'm not a dev, I'm a Linux admin by day...
Any sensible ideas welcomed :silly:
Hey there,
for differing Offset u tried this:
http://forum.xda-developers.com/showpost.php?p=61956115&postcount=54
For a flashable zip-file u should have a look at anykernel2 ... maybe u can find a solution here!
The secure boot shouldn't be a problem as ur bootloader is unlocked
Sent from my PLK-L01 using XDA Premium HD app
thanks @c0llal0 , some interesting things to look at there that I haven't tried :good:
Ur welcome! We all benefit from ur efforts.
In case i find some free time in the next days, i will try to help more...
Sent from my PLK-L01 using XDA Premium HD app
AnyKernel2 seems to be working :victory: - don't understand, as it's using still using umkbootimg and mkbootimg (arm) - need to put some debug in there to get the values it's using!
...but i've had to use use some force. I've had to disable the device check, which I'm not happy about (you know, some people may flash another device by "mistake")
Can u tell me where u disabled it? Maybe u could link to some code? Will have a look at those lines.
Sent from my PLK-L01 using XDA Premium HD app
in anykernel.sh
Code:
do.devicecheck=1
using
Code:
device.name1=HWPLK
device.name2=hi3635
as that's what is in build.prop
this is used in META-INF/com/google/android/update-binary
Code:
if [ "$(file_getprop /tmp/anykernel/anykernel.sh do.devicecheck)" == 1 ]; then
ui_print "Checking device...";
for i in 1 2 3 4 5; do
testname="$(file_getprop /tmp/anykernel/anykernel.sh device.name$i)";
if [ "$(getprop ro.product.device)" == "$testname" -o "$(getprop ro.build.product)" == "$testname" ]; then
ui_print "$testname";
match=1;
fi;
done;
ui_print " ";
if [ "$match" != 1 ]; then
abort "Unsupported device. Aborting...";
fi;
fi;
Always get unsupported device
I am on B170! Rooted.
My build.prop only shows HWPLK
No second device id here!
Sent from my PLK-L01 using XDA Premium HD app
added some extra ui_print - it's getting the value "HWGRA" ! that's not in build.prop :silly:
I had a look via TWRP and things get a little revealing
Code:
adb shell
~ # getprop
[ro.build.product]: [HWGRA]
[ro.product.device]: [HWGRA]
so, it looks as though this recovery is for the Huawei P8 / GRACE !
So now we have another job to do!
here's what Anykernel2 returns from unpackbootimg (also posting here for my own reference )
values here are yet again different from other unpackbootimg builds!
Code:
BOARD_KERNEL_CMDLINE mem=3072M mmcparts=mmcblk0:p1(vrl),p2(vrl_backup),p6(modemnvm_factory),p9(splash),p10(modemnvm_backup),p11(modemnvm_img),p12(modemnvm_system),p14(3rdmodemnvm),p15(3rdmodemnvmback),p17(modem_om),p20(modemnvm_update),p30(modem),p31(modem_dsp),p32(dfx),p33(3rdmodem) androidboot.selinux=enforcing
BOARD_KERNEL_BASE 00678000
BOARD_NAME
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 07588000
BOARD_TAGS_OFFSET ffb88000
something else to try...
EDIT:
YESSSS! :victory: :victory: :victory:
that's the one!
Code:
mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline \
'mem=3072M mcparts=mmcblk0:p1(vrl),p2(vrl_backup),p6(modemnvm_factory),p9(splash),p10(modemnvm_backup),p11(modemnvm_img),p12(modemnvm_system),p14(3rdmodemnvm),p15(3rdmodemnvmback),p17(modem_om),p20(modemnvm_update),p30(modem),p31(modem_dsp),p32(dfx),p33(3rdmodem) androidboot.selinux=enforcing' \
--base 0x678000 --pagesize 2048 --ramdisk_offset 0x7588000 \
-o new_boot.img
Yep! There u go
Now we have a good base to start, at least, kernel development!
Great work!!!
Sent from my PLK-L01 using XDA Premium HD app
c0llal0 said:
Yep! There u go
Now we have a good base to start, at least, kernel development!
Great work!!!
Click to expand...
Click to collapse
thanks can you do one thing for me, as you're on 170
can you tell me what the kernel version is?
cheers :highfive:
Here we go
Sent from my PLK-L01 using XDA Premium HD app
c0llal0 said:
Here we go
Click to expand...
Click to collapse
3.10.61, cool thanks!
As u have a bootin' kernel, what comes out of those logfiles? U looked after drivers for sensors and stuff?
Is the phone behaviour like it should be?
Sent from my PLK-L01 using XDA Premium HD app
c0llal0 said:
As u have a bootin' kernel, what comes out of those logfiles? U looked after drivers for sensors and stuff?
Is the phone behaviour like it should be?
Sent from my PLK-L01 using XDA Premium HD app
Click to expand...
Click to collapse
phone is working fine, as it's the same kernel version, the module for sensors etc. are all loading and working normally
Hi guys,
I've been following these posts for a few weeks now als also the kernel development. Massive shout out to Sminki and the ON-OR kernel!!
But I'm really new to the development of kernels and ROMs and new to xda so I have some questions if you don't mind.
I guess you guys are working on the kernel, how long should this take since it's kind of safe to use? And can I help testing (pls keep in mind I'm not an expert, just used to flash roms and kernels on nexus 4, that's all my knowlege.)?
When you get the kernel up and running, does it take much to make roms? Like making them from scratch or just a few changes to existing roms?
And again, can I help testing those ROMs?
My buildnr is PLK-L01c432B121, as far as I understand, L01 means I have the European version and B121 stands for the firmware version (an old one i guess). What does C432 mean?
You're working on an L01 kernel, is this compatible for other versions? In other words, when there are other kernels available, should I keep in mind that I can use only L01 based kernels?
Thank you to all the people that are spending their free time and all your hard work!!!!
Sorry this is a long reply, i got carried away, but you did ask a lot!
Anderjax said:
Hi guys,
Massive shout out to Sminki and the ON-OR kernel!!
Click to expand...
Click to collapse
thanks
But I'm really new to the development of kernels and ROMs
Click to expand...
Click to collapse
Me too, although I have been using linux for about 13 years so I do have some understanding of the underlying system, compiling, kernel modules, etc.. However some bits of this post may be incorrect!
I guess you guys are working on the kernel, how long should this take since it's kind of safe to use?
Click to expand...
Click to collapse
It is safe, i added the experimental tag as mine went into un-wakeable sleep with bluactiv cpu governor, but it's current uptime is 85hrs using ondemand instead. i built it because i wanted to see if it would actually compile, i posted it because it worked (and no one else had, haha!)
When you get the kernel up and running, does it take much to make roms? Like making them from scratch or just a few changes to existing roms?
Click to expand...
Click to collapse
this is where it gets difficult. right now there is nothing, no AOSP, no CM, etc.. to port to
So to start from scratch you need a device tree, which is essentially a collection of files that give the rom the bits of info it needs to build for your device, roms are a little easier to build if you have a "sibling" or "ancestor" (similar/older) device with a custom ROM, one that is similar enough to use some of the device tree that custom ROM was built from.
As the CPU is Huawei's own HiSilicon Kirin, there really is nothing similar with the exception of codeworkx CM for the Honor 6, the P8 is a "sibling" (but no custom roms) and the mediapad x2, which is Kirin, but not a phone, but someone may be able to do something with the custom roms available (?)
I'm currently playing around with this when i have spare time
What does C432 mean?
Click to expand...
Click to collapse
no idea!
You're working on an L01 kernel, is this compatible for other versions? In other words, when there are other kernels available, should I keep in mind that I can use only L01 based kernels?
Click to expand...
Click to collapse
the Chinese PLK-AL10 is the PLK-L01 with more RAM - with the MarshMallow beta "blackbox" partitions flashed i was able to run the AL10 kernel and system (android 5.1.1) on the L01
The PLK-(UL/TL/CL) are all essentially the same (rom) in a smaller system partition (as I tried that too!) I've not looked into the Indian variant yet..
"blackbox" are things like "radio" that you can flash directly from fastboot on a nexus, but not on this device, this is where the problems would lie. So yes, kernel per device, unless the dev has considered the above, but there is only one kernel right now :silly:
sminki said:
Sorry this is a long reply, i got carried away, but you did ask a lot!
Nice one,
Thank you, this explaines a lot really. Have you ever made a tree like that?
Is there someway to help you by installing the kernel en sending you feedback errors and stuff?
Click to expand...
Click to collapse
Anderjax said:
Nice one,
Thank you, this explaines a lot really. Have you ever made a tree like that?
Is there someway to help you by installing the kernel en sending you feedback errors and stuff?
Click to expand...
Click to collapse
Never made a tree before, but I have something which might work, will find out soon
As for the kernel, you can try and install it but it may not work because:
a) your're on B121
b) you may have the chinese twrp
c) other
I'll post the B121 boot.img later (at work now) on the main kernel post should you need to go back to it.
However - I don't know how much I'll be able to debug as i'm not a dev, or that good at C, also the huawei source seems to be really non-standard! :silly:
G'day guys and girls
I haven't seen PN source code updated for a while on the r33 side, seems they are focusing on the kernel a little bit
So I merged the tags myself and add some features to the ROM
I'LL TRY TO KEEP THE THREAD UPDATED, BUT THERES NO GUARANTEE ON THAT, THE REPO WILL PROBABLY BE UPDATED, IF YOU WANT TO BUILD YOURSELF, GO TO THE REPOSITORY DOWN BELOW
PLEASE NOTICE
This version was NOT signed by the PureNexus's certificates, please do a FULL FACTORY RESET if you are from the offical build.
I'm sorry for the inconvenience, but this is compulsory
Features
Built in GAPPS (no gmail, Google News and weather and play magazines, don't find them useful since I've got outlook and other replacement)
Built in Greenify
Android 7.1.2_r33 August security level
VoLTE tested
Lineage Terminal
ElementalX 1.15 Kernel (NTFS rw, exFAT, High Brightness Mode, Digital Gain control)
USB Patch for using the phone as a USB HID keyboard/mouse see here
All PureNexus Features
Untested
Since I am in Australia, there's no actual way to test whether Wi-Fi calling works, but it should work considering Project Fi was prebuilted. Please tell me if I need to add anything.
Magisk
https://forum.xda-developers.com/apps/magisk/unofficial-google-pixel-family-support-t3639262
Goodwin_c's magisk seems to work very well, thanks @goodwin_c
Known Bugs
OK Google detection is known to be not working in some languages (eg. Japanese)
MusicFX don't seems to open
Screenshots
https://ibb.co/m9XXz5
https://ibb.co/fL0Ke5
Downloads
https://drive.google.com/file/d/0B5ns3qw5ULWhTkZMQ2dVN0Z3LUU/view?usp=sharing
Flashing - How to
Please unzip the zip file, flash using fastboot commands
fastboot flash system_a /path/to/system.img
fastboot flash system_b /path/to/system.img
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
GitHub Source
manifest
patched kernel
Credits
the PureNexus Project https://github.com/purenexusproject
LineageOS https://github.com/lineageos
Pelya https://github.com/pelya/android-keyboard-gadget
flar2 (aka. Aaron Segaert) https://github.com/flar2
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Sent from my Pixel XL using Tapatalk
It's asking me to flash NZH54D Vendor image but i'm on T-Mobile shouldn't my Vendor image be NKG47S...?
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Ok Google works fine for me but I still haven't updated the vendor image. I'm worried I'm gonna screw up the rom. I'm gonna test it now after flashing the correct vendor image.
Ok vendor has been updated and everything is working fine.
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Delete.
TheUndertaker21 said:
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Click to expand...
Click to collapse
If the official PN doesn't have a feature that a user wants, they are within their rights to build a version that incorporates that feature.
And in most cases, if the builder marks it as Unofficial (as is the case here), they are welcome to share it others, on the understanding that no support will likely be given from the official builder.
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Hey, there, actually I'm also having this problem. What language are you using? I am using Japanese and this problem presents, I thought it was Google's problem so I didn't care, I'll try figure it out.
EDIT: fixes typo
TheUndertaker21 said:
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Click to expand...
Click to collapse
No, they aren't dead. they seems to focusing on other things especially the kernel and they are preparing for O since all the repos are being moved to the PureNexus-Legacy repo now. So I just built myself also add things for my own use.:fingers-crossed:
Pøîñtßlåñk said:
It's asking me to flash NZH54D Vendor image but i'm on T-Mobile shouldn't my Vendor image be NKG47S...?
Click to expand...
Click to collapse
I think it's probably fine. Since I'm using the international version so I'm just flashing the NZH54D vendor
cydia2020 said:
I think it's probably fine. Since I'm using the international version so I'm just flashing the NZH54D vendor
Click to expand...
Click to collapse
Worked fine thx.
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Do you see the same thing here
Pøîñtßlåñk said:
Worked fine thx.
Click to expand...
Click to collapse
Can you get OK Google to work? What language are you on. Cheers.
cydia2020 said:
Can you get OK Google to work? What language are you on. Cheers.
Click to expand...
Click to collapse
Works fine here English.
I was using English...
Sent from my Pixel XL using Tapatalk
BHermes211 said:
I was using English...
Click to expand...
Click to collapse
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
cydia2020 said:
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
Click to expand...
Click to collapse
Thank you. I'll be more than happy to give it a try again
Sent from my Pixel XL using Tapatalk
MusicFX don't seems to open in case you're concerned.
cydia2020 said:
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
Click to expand...
Click to collapse
Question... Is there a way to remove system apps on this rom? I've tried to remove the YouTube app even with magisk installed it gives apps that are able to remove system apps root permission but in the app remover app itself it says that I'm not rooted