Related
Hi guys,
Just found out Jetstream phone no sound because some missing commands in framework. Can someone recommend a willing framework engineer?
Sent from my GT-P1000 using xda app-developers app
cx5 said:
Just found out Jetstream phone no sound because some missing commands in framework. Can someone recommend a willing framework engineer?
Click to expand...
Click to collapse
You can try copying some of the system/framework/*.jar files from a ROM with a fully working phone? I suggest starting with LeeDrOiD HC Flyer ROM -- link below.
http://forum.xda-developers.com/showthread.php?t=1406851
It should be noted that LeeDrOiD did some pretty significant kernel work as well. You might want to figure out if his kernel was partly or wholly responsible for the phone functionality.
Thanks, will get to it. From observing GT-P1000, it seems kernel is fine, just lacking something in framework, but I haven't managed to ask deep enough. Like which JAR files?
finniest said:
You can try copying some of the system/framework/*.jar files from a ROM with a fully working phone? I suggest starting with LeeDrOiD HC Flyer ROM -- link below.
http://forum.xda-developers.com/showthread.php?t=1406851
It should be noted that LeeDrOiD did some pretty significant kernel work as well. You might want to figure out if his kernel was partly or wholly responsible for the phone functionality.
Click to expand...
Click to collapse
cx5 said:
Thanks, will get to it. From observing GT-P1000, it seems kernel is fine, just lacking something in framework, but I haven't managed to ask deep enough. Like which JAR files?
Click to expand...
Click to collapse
I don't know much about the framework directory. It looks like it contains functionality that is stagnant for a given Android version and flavor -- i.e. Android x and HTC Sense y.
Java .JAR files are linked at runtime which makes them pretty easy to upgrade without problems. I don't know the anatomy of Android .JAR files, however. They are .ZIP compatible so open one up and see.
Often when swapping out software pieces that are dependent on other pieces you have to rely on a lot of trial and error. If you try doing this then expect to run into a lot of boot loops.
Hi,
first of all, i know that it is prohibited to do that for public roms, but i want to do it for my own builds.
Until CM11 it was pretty easy to integrate. But how can i do that during build time with CM12?
Any advices, how to integrate the package?
Cheers and Thanks
Saint.
With CM plan to separate its self from Google completely they have made it just about impossible. Not to mention you would have to rewrite the whole built script
zelendel said:
With CM plan to separate its self from Google completely they have made it just about impossible. Not to mention you would have to rewrite the whole built script
Click to expand...
Click to collapse
Hi,
thnx for the answer at first, hmmmm it thing it should not be that hard, the updater script of the tools would need to be attached to the updater-script of the rom and all the stuff would have to be put into the source itself, the question is where to put it to?
Based on the first 5.1.1 sources, version OI5
Modifications:
SELinux unlocked
Disabled protection does not allow to boot the OS(disabled at the level of Linux kernel)
Permissive mode is set automatically at boot (without the possibility to switch back to enforce)
Before(you can do it after flash,but recommended before) installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
SecurityLogAgent has to be removed or frozen.
Flash kernel in odin.
v2 - SELinux fix.
Download: Google Drive
Sources: Google Drive
Blue cat said:
Based on the first 5.1.1 sources, version OI5
Modifications:
SELinux unlocked
Disabled protection does not allow to boot the OS(disabled at the level of Linux kernel)
Permissive mode is set automatically at boot (without the possibility to switch back to enforce)
Before installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
Flash kernel in odin.
This is my first kernel which I create on Linux. I hope everything will be working stable.
Download: Google Drive
Click to expand...
Click to collapse
Thank you - I flashed it as per your instructions. Seems to have worked fine and it's showing it as running as permissive!
Hi,
I made mine for my rom, but yours is good too.
Thank you for the comunity
Re...
Oops problems !! security notification
Alan-B said:
Hi,
I made mine for my rom, but yours is good too.
Thank you for the comunity
Re...
Oops problems !! security notification
Click to expand...
Click to collapse
I think you should remove ALL knox apk,because i never not seen security notifications on my device.
This kernel have only 2 changes.
security/selinux/Makefile and security/selinux/selinuxfs.c
Blue cat said:
I think you should remove ALL knox apk,because i never not seen security notifications on my device.
This kernel have only 2 changes.
security/selinux/Makefile and security/selinux/selinuxfs.c
Click to expand...
Click to collapse
Hi,
With my boot.img I have no this message! It is when I made out a will your that and come this message!
NB:
Your Boot and all the eliminated knoks!! (Rom deodex 5.1.1)
Alan-B said:
Your Boot and all the eliminated knoks!! (Rom deodex 5.1.1)
Click to expand...
Click to collapse
Ok,I found a solution.
You need to remove SecurityLogAgent
Bluecat, thanks for this! I wonder if you know what differences exist between the P605 and the P607T. Also, did you use the EUR_LL source from Samsung's opensource portal? Its strange that they already have the source out for the P605, but nothing yet for the P607T which received the update first. Makes me think maybe the code base is the same and its only the bloatware bundled by the carrier that differs?
I am also curious to just learn and get my hands dirty with this. Can you share the Makefile for this kernel, or just point towards the guide you used (assuming you used one) to compile this?
karthikrr said:
Bluecat, thanks for this! I wonder if you know what differences exist between the P605 and the P607T. Also, did you use the EUR_LL source from Samsung's opensource portal? Its strange that they already have the source out for the P605, but nothing yet for the P607T which received the update first. Makes me think maybe the code base is the same and its only the bloatware bundled by the carrier that differs?
I am also curious to just learn and get my hands dirty with this. Can you share the Makefile for this kernel, or just point towards the guide you used (assuming you used one) to compile this?
Click to expand...
Click to collapse
Sorry,but i dont know differences between the P605 and P607T.
Yes,sources SM-P605_EUR_LL_Opensource.zip and version OI5.
If you want check have code 607 and 605 differences or not you should check checksum both original zImage(linux kernel). Extract them from both boot.img and compare.
Version 2 use standart selinux permissive way used by mostly kernel developers,it's have many changes in code now and it's will be very long to explain how to change to permissive,just use my sources available now in first post and compare them with original sources.
If you talk about how to compile kernel...was use many guides and other forums...hard part was only create .config file
Blue cat said:
Sorry,but i dont know differences between the P605 and P607T.
Yes,sources SM-P605_EUR_LL_Opensource.zip and version OI5.
If you want check have code 607 and 605 differences or not you should check checksum both original zImage(linux kernel). Extract them from both boot.img and compare.
Version 2 use standart selinux permissive way used by mostly kernel developers,it's have many changes in code now and it's will be very long to explain how to change to permissive,just use my sources available now in first post and compare them with original sources.
If you talk about how to compile kernel...was use many guides and other forums...hard part was only create .config file
Click to expand...
Click to collapse
Will try to extract the zImage from the P607T boot.img. I do not have the P605 though, do you know if the stock boot.img is downloadable anywhere?
Thanks for uploading the source. I just finished downloading the original source from the opensource site, will compare the two and try to understand.
I do know how to complile a linux kernel, I meant can you share the .config file (not the makefile, as I wrongly stated earlier), so I can see what has changed across the entire kernel. Rather than just change one line directly in the config file to disable SELinux, I wanted to use make menuconfig and go through the whole process, just to learn more about android kernels. But since I do not know much about the hardware and driver requirements, wanted to see a stock .config as well as your changed .config to understand.
karthikrr said:
Will try to extract the zImage from the P607T boot.img. I do not have the P605 though, do you know if the stock boot.img is downloadable anywhere?
Thanks for uploading the source. I just finished downloading the original source from the opensource site, will compare the two and try to understand.
I do know how to complile a linux kernel, I meant can you share the .config file (not the makefile, as I wrongly stated earlier), so I can see what has changed across the entire kernel. Rather than just change one line directly in the config file to disable SELinux, I wanted to use make menuconfig and go through the whole process, just to learn more about android kernels. But since I do not know much about the hardware and driver requirements, wanted to see a stock .config as well as your changed .config to understand.
Click to expand...
Click to collapse
My config https://drive.google.com/file/d/0BxQroXyaGzZOSmdieTNVaFY3VjA/view?usp=sharing
Boot https://drive.google.com/file/d/0BxQroXyaGzZOVFZGZGs3YmloX2s/view?usp=sharing
I dont have original config,you can create your own on linux.
Blue cat said:
My config https://drive.google.com/file/d/0BxQroXyaGzZOSmdieTNVaFY3VjA/view?usp=sharing
Boot https://drive.google.com/file/d/0BxQroXyaGzZOVFZGZGs3YmloX2s/view?usp=sharing
I dont have original config,you can create your own on linux.
Click to expand...
Click to collapse
Brilliant! Thanks for sharing ... As and when I learn anything relevant to the issue of P605 vs. P607T, will update here.
Why does the wifi password get forgotten on every boot?
Any fix for that matter?
valexi said:
Why does the wifi password get forgotten on every boot?
Any fix for that matter?
Click to expand...
Click to collapse
Blue cat said:
Based on the first 5.1.1 sources, version OI5
Before installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
SecurityLogAgent has to be removed or frozen.
Flash kernel in odin.
Click to expand...
Click to collapse
Maybe you missed the update to the original post, the fix is as above, set securestorage to false. Since you have already flashed, you can still go to build.prop, make this change, reboot, and you should be fine.
karthikrr said:
Maybe you missed the update to the original post, the fix is as above, set securestorage to false. Since you have already flashed, you can still go to build.prop, make this change, reboot, and you should be fine.
Click to expand...
Click to collapse
I tried this. With ro.securestorage.support false. Still no WiFi passwords saved after reboot.
Other than that, this works great!
Xposed (for Samsung by wanam) works great!
valexi, the only thing Ive seen suggested in your case is to reflash the firmware. I do not know of any other solutions for this, because pretty much everybody with this problem seems to have solved it when they changed the securestorage thing.
BlueCat, I went ahead and compared checksums for the stock p607t and p605 kernels, they do NOT match. I also extracted the kernels themselves and the zimage files are of different sizes. I then compared the default config files of the P605_LL_EUR source with the only available source for the P607T, which is KK ... They are considerably different. I am of course going with the assumption that the core config for the kernel between KK and LL should not be TOO different, but of course, this is NOT a reliable test. Lastly, I should also say, the P607T source contained an insane number of config files in the Arch/Arm/configs folder, while the P605 source only had three files! I only compared the three that were common ... It seemed like the 607T has the config files for every possible version of the device, while the 605 one had very specific configs for that device only ... This I am speculating based on the fact that the 607T folder even had a msm8894_sec_l03ltmo_defconfig file in addition to the msm8894_sec_l03leur_defconfig file in the 605.
Will do more comparisons over the next few days, but it does seem like there are more changes under the hood between the 605 and the 607T than one would expect. I really wish samsung would release the source for the 607t, but if you check that page, there is just one single KK code there and nothing else, so it does not seem likely anytime soon
Blue cat said:
Ok,I found a solution.
You need to remove SecurityLogAgent
Click to expand...
Click to collapse
Re,
Ok remove SecurityLogAgent and folder Container it is ok...
But delete all other knox and Klm gives a problem with the playstor. (Certain protections cannot be erased)
Hey guys,
Great news around, especially with roms like Alan-B's. Thanks for sharing :good:.
Running 4.4, planning to update 5.x as soon as I'm sure I can run Linux Deploy (meaning the need of permissive kernel), though I can't find any intel about VTS (Virtual Terminal Support) enabled kernel. I've been looking for months a way to run framebuffered distros and looks like this is the solution.
I could try to make it myself but I have no experience in kernels, would someone mind give me a hand to get to this goal? At least give me a hint to "quickly" develop and try one, to see if it works and how well...
Don't even know if I'm looking the right way anymore, so thanks by advance for any help and again for the sharing :highfive:.
karthikrr said:
valexi, the only thing Ive seen suggested in your case is to reflash the firmware. I do not know of any other solutions for this, because pretty much everybody with this problem seems to have solved it when they changed the securestorage thing.
Click to expand...
Click to collapse
But when I reflash the firmware how can I set securestorage BEFORE installing permissive kernel as I don't have root to change build.prop?
valexi said:
But when I reflash the firmware how can I set securestorage BEFORE installing permissive kernel as I don't have root to change build.prop?
Click to expand...
Click to collapse
You can't. Reflash, root, edit build.prop, reboot, set wifi password once again, reboot, it SHOULD be fine. If its not after this sequence, Im not sure what else may work. Every case of this particular problem that I've seen was resolved with this solution.
Luckily I didn't reflash yet. I checked again build.prop and securestorage was true. For some reason it didn't stick first time.
I edited it again and now WiFi works as intended. So I can say that this solution works. Great kernel.
Sent from my ONE A2003 using Tapatalk
This rom is built directly from the stock MRA58R Google image.
PSA
For pin to work you will need a permissive kernel, Rom is currently running enforcing so flash a permissive kernel if you want pin. No issues if your using cataclysm. I'm working on figuring out the fix thanks.
It is basically just the system folder extracted from the MRA58R Google update and repackaged as a flashable zip with a stock kernel with added features by @gerar_f.
I packaged this together for people that want a Stock Bloated Google experience. Or a fully stock rom to customize to the users liking.
Any mod made for the stock google rom should work 100% here.
Cataclysm mod is recommended if your looking for a more custom rom experience and I fully support flashing it over this rom.
http://forum.xda-developers.com/nexus-6/orig-development/rom-cataclysm-nexus-6-t3219121
Cataclysm flashes a kernel so if you like the added features of gerar_f's kernel then you will want to flash it after cataclysm. Link below
Rom Features
Odexed
None really. This is as stock Google as it gets, you will find all the gapps that will possibly fit in the system partition just like a stock google image.
Root is not included. Flash SuperSu 2.5.2 if you want. You can run this rom un-rooted with cataclysm mod flashed over top and have a custom unrooted rom with working android pay.
(Theoretically) I haven't been able to test pay around me
Busybox is also not installed so grab that from the playstore if you want/need it.
Included Kernel by @gerar_f
Included kernel is Custom "Stock" v4 created by @gerar_f big thanks to him and go over to his thread and drop a like.
http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958
Kernel is stock in behavior with a few features. First it is without forced encryption, It is Seandroid Enforcing and includes several features, Root with rw if rooted, Disabled boot verification warning, Color control, Headphone and mic gain control, Vibration control, Wake gestures, Multirom support.
TIPS
There is only 33mb free in the system partition due to google including so many gapps. In my testing ive found that this is enough for installing 1 layers theme and Cataclysm Mod.
Some gapps may need removed to install things like Xposed modules, and other apps to the system(TBO apps, better battery stats etc) or anything that takes up more than a few megs going into the system.
I personally remove Fit, Sheets, and Slides which gives you around 100mb free in system which is enough for my use. I recommend this app for removing system apps you dont want. Root Required.
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
Thanks
@gerar_f for great custom stock kernel. (I couldn't even begin to figure out how to customize a kernel)
@tupac4u for the updater-binary and update-script to flash the zip properly. (my attempts at making the script were futile)
@atl4ntis for making Cataclysm and inspiring me to create a stock rom for said mod to be flashed over.
Google
@magnamentis @dhruvmalik for testing. @Chainfire for ROOTS!
Download
Rom
https://www.androidfilehost.com/?fid=24269982087001131
MD5
52526f45a3ffafd6d9b6bdd0b7f8836c
Install instructions
In TWRP, factory rest, wipe cache, dalvik, data, and system.
Flash Rom
If wanted flash additional stuff (supersu, cataclysm, and/or kernel)
Profit
Reserved for possibly more
Hi,
Thank you for this as this is very useful!
Droidphilev said:
Hi,
Thank you for this as this is very useful!
Click to expand...
Click to collapse
Thanks!
I was surprised that there was not a unmodified flashable Google rom out so I put one together.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Thanks!
I was surprised that there was not a unmodified flashable Google rom out so I put one together.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I tried myself too but gave up
I wonder: this is a one time project? I mean if there's a new factory image can i just extract the system.img and put it into your zip and never ever bother you again?
(I'm not able to download today hence the question)
EDIT: please don't mind the kernel in this question
Droidphilev said:
I tried myself too but gave up
I wonder: this is a one time project? I mean if there's a new factory image can i just extract the system.img and put it into your zip and never ever bother you again?
(I'm not able to download today hence the question)
EDIT: please don't mind the kernel in this question
Click to expand...
Click to collapse
I'm planning on releasing more versions as Google releases it's monthly updates.
To answer your other question it's not as simple as just extracting the system.img but isnt too hard. Basically you extract the actual system.img from the Google update. Then use ext4 unpacker to unpack it into an ext4 file. Then you use ext2 explore to unpack the ext4 file which gives you the system folder with all the files within. Then just take the system folder a compatible boot.img and a working meta-inf folder and zip them up. Then you have your Rom.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
I'm planning on releasing more versions as Google releases it's monthly updates.
To answer your other question it's not as simple as just extracting the system.img but isnt too hard. Basically you extract the actual system.img from the Google update. Then use ext4 unpacker to unpack it into an ext4 file. Then you use ext2 explore to unpack the ext4 file which gives you the system folder with all the files within. Then just take the system folder a compatible boot.img and a working meta-inf folder and zip them up. Then you have your Rom.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thank you for this info and explanation but after reading this i think i will just download your releases if you don't mind
Droidphilev said:
Thank you for this info and explanation but after reading this i think i will just download your releases if you don't mind
Click to expand...
Click to collapse
Lol that's fine with me.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Lol that's fine with me.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah, thanks for the explanation, its nice to learn about stuff that has bewildered you for ages.
arifqur said:
Yeah, thanks for the explanation, its nice to learn about stuff that has bewildered you for ages.
Click to expand...
Click to collapse
Feel free to ask any other questions.
Yea that's very simple way to make a Rom. I wouldn't call myself a dev or anything. The other custom roms require a lot more work like modifying system apks to add the extra features. This is just full unmodified stock with a kernel. I figured it would be a great base to flash cataclysm over. Seeing how it's recommended to flash cataclysm over a full stock Rom this is as close as it gets right now. People have had luck flashing cataclysm over other stock modified roms but I worry that those modifications may cause issues with the modifications of cataclysm. With that said I'm personally running it without cataclysm. I just removed a few gapps I'll never use flashed and installed around 10 team blackout apps, and applied magpie midnight theme for a almost fully blacked out experience.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Feel free to ask any other questions.
Yea that's very simple way to make a Rom. I wouldn't call myself a dev or anything. The other custom roms require a lot more work like modifying system apks to add the extra features. This is just full unmodified stock with a kernel. I figured it would be a great base to flash cataclysm over. Seeing how it's recommended to flash cataclysm over a full stock Rom this is as close as it gets right now. People have had luck flashing cataclysm over other stock modified roms but I worry that those modifications may cause issues with the modifications of cataclysm. With that said I'm personally running it without cataclysm. I just removed a few gapps I'll never use flashed and installed around 10 team blackout apps, and applied magpie midnight theme for a almost fully blacked out experience.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
As stated above by others, I was also surprised that there wasn't a flashable stock ROM available, primarily for those who wish to be stock, use xposed and or mods like Cataclysm.
This is working awesome; thanks @GavinMazey
Great idea, I'll probably be checking it out soon with CatMod. Any chance you could debloat it? It's not hard for me to just use Tibu to do it, but one less thing to do is always nice. No worries if you can't.
Thanks for the rom!
Thank you for this!
GeekMcLeod said:
Great idea, I'll probably be checking it out soon with CatMod. Any chance you could debloat it? It's not hard for me to just use Tibu to do it, but one less thing to do is always nice. No worries if you can't.
Thanks for the rom!
Click to expand...
Click to collapse
I'm not really planning on debloating, there is a plethora debloated roms for the n6. But if enough end up wanting it I might. But if I do it would be my personal debloat instead of removing as much as possible. Keeping it stock let's me update faster when google drops new images.
flashback7 said:
Thank you for this!
Click to expand...
Click to collapse
Thanks for checking it out.
Sent from my Nexus 6 using Tapatalk
+ 1 on NOT debloating. Every one could do it how they like it by themselves.
Thanks.. It's good to know I have an option to flash the zip. I might load up cataclysm tonight
This is great for those who want fresh out of box stock experience with working ANDROID PAY. Once you root it, trim it, customize it, then ANDROID PAY won't work.
cink40 said:
+ 1 on NOT debloating. Every one could do it how they like it by themselves.
Click to expand...
Click to collapse
Noted. That was my thought too stock bloated base for users to do what they want with it. I personally use most of the gapps included, I personally only delete sheets, slides, and fit (I may be a fatty lol). I've found most debloated roms remove too much so instead of having the gapps taking up system space I have to install them to internal storage taking up space where they don't need to be.
Too much free system space is wasted space imo.
Phrodini said:
Thanks.. It's good to know I have an option to flash the zip. I might load up cataclysm tonight
Click to expand...
Click to collapse
If your already on android m you should be good to flash this then cataclysm. Report back how it went if you do. Haven't had too much feedback on users actually flashing it. Hopefully because all works great [emoji12]
HueyT said:
This is great for those who want fresh out of box stock experience with working ANDROID PAY. Once you root it, trim it, customize it, then ANDROID PAY won't work.
Click to expand...
Click to collapse
That's exactly why I kept it unrooted. In theory someone could flash this Rom and then cataclysm without root and have a custom Rom with working Pay just no root. No where that I've been around me accepts pay so I am unable to test. But in theory it should work.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Noted. That was my thought too stock bloated base for users to do what they want with it. I personally use most of the gapps included, I personally only delete sheets, slides, and fit (I may be a fatty lol). I've found most debloated roms remove too much so instead of having the gapps taking up system space I have to install them to internal storage taking up space where they don't need to be.
Too much free system space is wasted space imo.
If your already on android m you should be good to flash this then cataclysm. Report back how it went if you do. Haven't had too much feedback on users actually flashing it. Hopefully because all works great [emoji12]
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I am thinking about using multirom with this zip, cataclysm, and a lollipop rom.. Maybe kitkat too for one game that only works on kitkat lol
Phrodini said:
I am thinking about using multirom with this zip, cataclysm, and a lollipop rom.. Maybe kitkat too for one game that only works on kitkat lol
Click to expand...
Click to collapse
Flashing cataclysm will replace the included kernel with cataclysm kernel which you'll need to check supports multirom, I'm not sure off the top of my head. But if not re flashing the included kernel by gerar_f after cataclysm will give you multirom support. Also I'm not entirely sure you can run kitkat and marshmallow in multirom at the same time. I haven't used it myself but I think (I may be wrong) that multirom uses your main kernel for all other roms. So a different android version may not work properly. Again I might be wrong.
Sent from my Nexus 6 using Tapatalk
I have a custom ROM which I am building from source. I would like to modify the source code so that an app comes pre-installed with it. As far as I am aware, the app should end up in /system/app on the built ROM.
But where do I put the apk in the source, so it gets put in the correct place in the system image?
cameron-martin said:
I have a custom ROM which I am building from source. I would like to modify the source code so that an app comes pre-installed with it. As far as I am aware, the app should end up in /system/app on the built ROM.
But where do I put the apk in the source, so it gets put in the correct place in the system image?
Click to expand...
Click to collapse
I would recommend taking a look at this guide here http://stackoverflow.com/questions/33622299/add-prebuilt-apk-to-aosp-build. If you have any questions please let me know I'll be happy to answer them !