RULES1. Read the OP fully.
2. For bug reports, I need a log to assess the issue. Capture a log while replicating the issue.
3. Do not ask ETA's on updates; you will be ignored.
4. Use the "search this thread" feature to make sure your question wasn't already answered by using key words.
5. Only ask a question about this project. Any questions about another ROM or project will be disregarded.
6. If you dont like my ROM then too bad.
7. You want 100% untouched/unmodified AOSP. This isn't the ROM for you.
8. AOKP is open source. so you can always build it yourself.
Instructions:Download ROM .zip file
Download KitKat GApps
Download latest SuperSU flashable (Optional)
Reboot to Recovery
Flash ROM, GApps, SuperSU .zip files
Clear Dalvik/Cache
Reboot and EnjoyIf you want to run art thats fine but use at YOUR OWN RISK as i currently do not support it.
DOWNLOADS
ROM: Mod Edit: Link RemovedGAPPS: HERESuperSU: HERE
Also a quick shoutout to xboxfanj for letting me use his kernel. Thanks bro
XDA:DevDB Information
One M8, ROM for the HTC One (M8)
Contributors
MadTwatter, xboxfanj
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOKP
Version Information
Status: Stable
Current Stable Version: 8.29.2014
Stable Release Date: 2014-08-29
Created 2014-08-31
Last Updated 2014-09-03
Thread closed pending further information and understanding of duplicated thread.
Thread reopened to allow OP to add sources, credits and add more detail regarding the "essence" of this ROM...
It's mostly kernel optimization with a little bit of rom tweaking to make it smoother, when I get time I will sit down and go over the commits that I think are worth telling people about if that makes you feel more comfortable sir.
Sent From The Tardis
MadTwatter said:
It's mostly kernel optimization with a little bit of rom tweaking to make it smoother, when I get time I will sit down and go over the commits that I think are worth telling people about if that makes you feel more comfortable sir.
Sent From The Tardis
Click to expand...
Click to collapse
This thread started out rather poorly and has been cleaned. I'm going to leave the thread open for now so that the OP can update the first post as @LenAsh requested and so that members can help with testing and troubleshooting. I am subscribing to this thread to encourage members to be on their best behavior. Instead of arguing in a thread and posting PMs publicly in a thread, please report the offending posts / PM and let a moderator handle it.
To the OP:
First off, welcome to XDA. We are glad you decided to post a ROM here. A few things:
You are required to post the following. If you do not within the next few days, I will need to close the thread and remove the download links:
1. Kernel source: You mention "kernel optimizations" so you need to upload your source code to Github. If you used a kernel without any changes, then please link to the thread of that kernel.
2. Credits: Link to AOKP at least to give them credit for the base. Also credit for any tweaks you found here that you included.
Suggested things to post. Although these are not required, most threads have them and members expect them so they know what they are flashing (I personally wouldn't flash a ROM without these).:
1. Feature list: what this ROM has that makes it special. You made changes that you liked - what were they?
2. Screenshots
3. Changelog: when you have one since this is the initial release
For more help on what's expected for ROM OPs, please look at these guidelines.
I don't want to close the thread. In fact, I like to encourage people to develop on here. So, please at least post kernel source and credits to keep the thread open. The other stuff is gravy and can be done as you get time or your thread maintainer you mentioned gets to it.
Hope the OP is adjusted according to XDA rules. i'm going to kick things off by flashing and testing this ROM. i'll check for any kind of malware/spyware (crash-test-dummy). Keep your fingers crossed.
Chuckd610 said:
Hope the OP is adjusted according to XDA rules. i'm going to kick things off by flashing and testing this ROM. i'll check for any kind of malware/spyware (crash-test-dummy). Keep your fingers crossed.
Click to expand...
Click to collapse
I wouldn't be holding my breath on the OP providing the info requested by @coal686. I see he's been active around the place, but this mustn't be a priority.
Out of interest, did you flash the ROM, and if you did, how did it go?
OP has stated that he is not going to update the thread to give credits (kernel source is in the download tab), so thread closed and download link removed until he changes his mind.
General informations:
This thread's aim is only to represent a central meeting and discussion point for BCM21553 developers and, in particular, for the open Kernel/ROM sources development for the Samsung Galaxy Pocket GT-S5300 (codenamed Cori).
Information for common users:
As already described in the previous section, if you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Every post that is not strictly respecting these rules will be reported to the forum moderators. Thanks for your understanding.
For any other BCM21553 device related question or information, please, use this thread as a reference point, instead:
[DEVS ONLY][BCM21553 series] CyanogenMod 11 for BCM21553 Development Discussion
As someone already might know, I'm streambinder, from MoltenMotherBoard team.
I have already followed some projects for the GT-S5300, but especially kept in contact
with some of the events related to the porting of ROM and Kernel sources for BCM21553 chipset based devices.
In this precise moment, the sources in my possession allow you to be able to compile
a bugfree CWM 5.0.2.8 (based on CyanogenMod 7 code) with a kernel based on the Samsung stock one.
The only - fundamental - problem was due to the fact that unless I hadn't used the prebuilt INIT binary
token in the Samsung stock firmware boot.img, the phone would not work - or, better, boot up.
This means that until the situation - regarding this issue - doesn't change, our access to the porting of custom ROM
would be barred.
Recently, I decided to give Cori another chance and rework my sources, looking at the wonderful work brought
by the BroadcomCM team on CyanogenMod 9 (in particular, thanks to @bieltv.3 and @Alberto96) and @psyke83 on CyanogenMod 11.
They've not only been able to run these two ROMs in a more or less crude way, but this developer has been able to write
the necessary strings to make the INIT binary of some of these BCM21553 devices opensource.
Strong of this informations, I readjusted some of the sources of BroadcomCM's CyangenMod 9, which includes
all the progress carried out by both the team and psyke83, in order to make them work even on Cori,
and am now next to the first test of the CWM 6.X.X.X, based on IceCreamSandwich code.
At the same time, @akhbh is working on the KitKat code based CWM.
I hope I can give more information about any progress as soon as possible.
The General Discussion thread for non-development issues is here:
*.[DISCUSSION] CyanogenMod 11 For Galaxy Pocket GT-S5300 Discussion Thread
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
streambinder said:
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
Click to expand...
Click to collapse
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
akhbh said:
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
Click to expand...
Click to collapse
Perfect.
Which kernel have you based your build on?
streambinder said:
Perfect.
Which kernel have you based your build on?
Click to expand...
Click to collapse
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
akhbh said:
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
Click to expand...
Click to collapse
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
streambinder said:
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
Click to expand...
Click to collapse
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
akhbh said:
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
Click to expand...
Click to collapse
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
streambinder said:
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori | github.com
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
Click to expand...
Click to collapse
have u tried to build cwm v6 from cm9 source ??
cleverior.ipul said:
have u tried to build cwm v6 from cm9 source ??
Click to expand...
Click to collapse
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
akhbh said:
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
Click to expand...
Click to collapse
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
streambinder said:
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
Click to expand...
Click to collapse
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources coz as said earlier, his kernel is used. Well, we were working together to bring cm11 but weren't successful
akhbh said:
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources.
Click to expand...
Click to collapse
Ok, please send it to me, will compare it with my package.
streambinder said:
Ok, please send it to me, will compare it with my package.
Click to expand...
Click to collapse
Here it is:
http://www.4shared.com/zip/1nKFbOJ2ba/ccccGetux_CM11.html
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
here the link source https://github.com/cleverior/android_kernel_samsung_cori
i've changed the board name. If your device can not boot after using the zImage from this source, then rename init.bcm21553.rc to init.gt-s5300.rc.
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
akhbh said:
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
Click to expand...
Click to collapse
Sincerely don't what are you talking about.
Anyway, have to try to understand where's the problem with the not-booting CWM.
Will try with your sources and let you know.
***Moderator Edit: Thread closed due to GPL Policy violation***
ROM features:
- debloated
- pre-rooted
- with nice wallpaper
Warning: this ROM is still in test process, if there is any bugs please report
Download ROM:
(Pan Baidu) ***Link removed by moderator***
Credits: ROM PLAYGROUND
@(EVIL RYU) Please read the GPL Policy linked in my signature. You are required to post the source your kernel was built from to be GPL compliant. Please correct this immediately.
Also, if you ported this from someone else's work, you MUST give them credit, per Rule 12 of the XDA Forum Rules.
Otherwise, if this is not your own work, you must give credit to the original developer.
If these corrections are not made within 5 days, this thread will be closed and download links will be removed.
V0latyle said:
@(EVIL RYU) Please read the GPL Policy linked in my signature. You are required to post the source your kernel was built from to be GPL compliant. Please correct this immediately.
Also, if you ported this from someone else's work, you MUST give them credit, per Rule 12 of the XDA Forum Rules.
Otherwise, if this is not your own work, you must give credit to the original developer.
If these corrections are not made within 5 days, this thread will be closed and download links will be removed.
Click to expand...
Click to collapse
hello, I have fixed the problems as you mentioned..
(EVIL RYU) said:
hello, I have fixed the problems as you mentioned..
Click to expand...
Click to collapse
Your kernel source link is not correct. Are you using the stock kernel? If this is just a modified stock ROM, you can find the stock kernel source here
Is this an Android 9 rom as you menthioned in the title? Gald to see that on Snapdragon S7e. Thanks for your work.
(EVIL RYU) said:
hello, I have fixed the problems as you mentioned..
Click to expand...
Click to collapse
As you still have not posted the correct kernel source, I have closed this thread and removed the download links.
Please be aware that your kernel source link must point to the source code for the OEM kernel if you're using the stock one, OR if you are using a custom kernel, either the source used to build that kernel or its repository. You cannot use the ROM download link as your source.
When you are ready to correct this issue, please use the Report button on your post to contact us.