Develop Bugs

[KITCHEN][ROM] >-=+ [mu] kitchen +=-<

Placeholder for the [mu] kitchen.
DOs and DON'Ts:
DON'T:
1: DON'T ask about vista support. I'm seriously allergic to that expression. Use WinXP SP2/3 and be happy.
2: If it doesn't suit your needs, don't b**** about it and just use another one.
DOs: if you like it, say thanks.
CONSTRUCTIVE criticism/suggestions: more than welcome via PM.
^.^
### Here's the link (lzma)##############
# http://www.mediafire.com/?oufm4oq9t2v #
##############################
### Here's the link (tar+bzip2)#########
# http://www.mediafire.com/?u4tj1jsnuzt #
#############################
1: .net framework 2.0 at least needed.
2: ms vb runtimes recommended.
3: BEST uncompress with 7zip (or any app supporting lzma) / WinRAR/WinZIP to c:\
4; there is no "readme", so place your RUU_signed.nbh (and Part*.raw) into the "source" folder in the kitchen,.
5: although I tried coding it as noob-proof as possible, the kitchen DOES require some minimal knowledge about the cooking/rebuilding process.
I DON'T intend to spoon-feed you, so if you want additional features, you need to seriously catch up on some reading.
This kitchen DOES need further/extended testing, but I decided to release it after several successful tests on 2 different systems.
Nethertheless, I CAN'T possibly account for the heterogeny of every system in the wild...
I could TRY coding the "perfect" kitchen, but that would be utterly pointless, since experienced chefs use their own kitchen/or don't use frontends.
6: last but not least: even though a cooking process might've been completed, give a few seconds till you move to the next step. HDD/IO bottlenecks tend to do strange things.
^.^
The mirror/kitchen link MAY be inaccessible at times. If you REALLY need access to anything hosted, leave me a PM.
I'll provide you with another (temporary) link.
# # #
20090110 edit
Will be uploading an updated version of the kitchen maybe next week.
# # #

Pre-applaud and Pre-thanking
Thank you...................................

Thanks Cyphol.
I will of course give credit where credit is due.
What's taking me so long is that I'm trying to make the batch as easy to read as possible, all the while trying to give as much control as possible over the entire cooking process.
It should RATHER be "noob-proof".
I don't think I will finish it today, because I only have a windows box at work to test it on.
@ home I'm all unix.
^.^

adwinp said:
Thanks Cyphol.
I will of course give credit where credit is due.
What's taking me so long is that I'm trying to make the batch as easy to read as possible, all the while trying to give as much control as possible over the entire cooking process.
It should RATHER be "noob-proof".
I don't think I will finish it today, because I only have a windows box at work to test it on.
@ home I'm all unix.
^.^
Click to expand...
Click to collapse
(pre)Thanks for sharing a probably great and useful tool !

I think it will be a great kitchen because adwinp is a very hardworking man and he reads and searches a lot.

Thanks Cyphol.
I'm honoured. Though I learned a lot from you guys.
I'm nearly done with the batch file. I'll finish and test it tomorrow.
I tried giving the end user as much control as possible, even though using just one batch.
We'll see if it works.
DOS batch coding sux.
Bash rulez.
^.^

.. [reserved] .. for private use.

The [mu] ROM is coming next.
(It might take some time for me to release a ROM worth sharing with the community. I may want to wait for the next official ROM update since I'm not really satisfied with the 1.93 base).
PLEASE DON'T ask when it might be available.
^.^
Although I respect bepe's and dutty's (DP) great work, I stick with Wally regarding protecting the ROM against disasm/copying.
Meaning: No copying protections. Feel free to do with it as you please.

I won't say thanks for this kind of Kitchen. WHAT HAVE YOU DONE???
I only want to say MARVELOUS! NICE AND CLEAN! CONGRATULATIONS.

Thanks Cyphol!
The real thanks goes to the authors of the various tools this kitchen serves as a frontend to.
I doubt this is bug-free, but I hope it will be a contribution of some sort to the community I have learned so much from.
Maybe somebody will do a much better job than I did.

Sorry,
but WinRAR says the archive is destroyed.

scorpio16v said:
[...]WinRAR says the archive is destroyed.
Click to expand...
Click to collapse
Re-download and make sure your browser doesn't screw with the file extension, it's .tbz2 (tar+bzip2) otherwise your unpacker might have issues reading it.
The Archive is fine, and adwinp: the kitchen looks extremely sexy. I'm completely new to cooking and just trying it because I want a proper JVM, but I've looked at the other kitchens, and this one is the nicest so far.
If your ROM is as hot as the kitchen, I might have found myself a new base rom

cptsunshine said:
.... otherwise your unpacker might have issues reading it.
The Archive is fine...
Click to expand...
Click to collapse
You're right.
Was my WinRAR version.
Sorry for the rumour.

scorpio16v said:
You're right.
Was my WinRAR version.
Sorry for the rumour.
Click to expand...
Click to collapse
Use 7zip for any of the archive versions.
It's a fast and free archive manager, supporting lzma.
You can still uncompress the .tbz2 archive with 7zip/winrar/winzip.

Hi adwinp,
Great tool !
Thank you very much for sharing this tool !!!
I've tried it to rebuild a .nbh with some dump files associated with a RUU_signed.nbh from a stock HTC ROM.
After the first steps, all is OK (my casserole seems to smell good ) until the Build step...
I got an abort 'BuildOS.exe ....'
any idea ?

Could you post a screenshot?
Gimme a link to the stock ROM (or tell me what version it is) and I'll check it out.

OS conflict ?
Hi adwinp,
And thanks for your reply.
So, here is what I've done :
1. Copy my 4 Part0*.raw files in y=the \source folder
2. Copy the stock RUU_signed.nbh in the same folder
Notes :
> Dump files are the parts of a french ROM from Bouygues provider avalaible here : http://dl.free.fr/rkxdkK3bp
> RUU_signed.nbh file becomes from an official HTC ROM 1.37.406.1 avalaible here : http://www.4shared.com/file/5430812...io_Signed_Diamond_5226a2509_1002503_Ship.html
3. Launch mu.bat
4. select "a" to Accept
5. select "r" to Rebuilt
6. select "d" to leave it Dirty
7. select "z" to extract OS from base (OK, new folder 'casserole' with the OS.nb file)
8. select "g" to extract system files (OK, new folder 'imgfs_e' in the casserole)
9. select "y" to extract core files (OK, new folder 'xip_e' in the casserole)
10. select "p" to concatenate system (it seems good)
11. select "o" to rebuild the base...
And then, the error message :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that, I've tried to use the other method with Diamond Kitchen, and I got exactly the same error when building the OS...
plus another message :
Even if I don't really know how the BuildOS step proceeded, it seems there is an OS incompatibility or conflict, right ?

I'll try to rebuild your ROM later.
A quick question though: do you have NET Framework >= 2.0 installed?

adwinp said:
I'll try to rebuild your ROM later.
A quick question though: do you have NET Framework >= 2.0 installed?
Click to expand...
Click to collapse
A quick answer though: .NET framework 3.5
Cheer,

Hello,
@ MonteCristoffOn, you've installed Microsoft Visual C + + 2008 Redistributable Package Download

Multi-Carrier Kitchen's & Rom's - Diamond /&\ Manila2d Flavors

*...Before Flashing this Rom or Using the Kitchen...*​
You MUST be:
- Unlocked with the 2.31 unlocker,
- Upgraded your RADIO to 3.42.xx by flashing
RUU_Vogue_BM_WWE_3.09.666.1_Radio3.42.50_Ship.exe
and skip customizations!!!
(I've found this to be the best for me...)​
Insert bold colored disclaimer here about how it is not my fault
if you mess up your phone
or
lose sleep
after reading this tutorial...
If you mess it up...Always Remember:
Power, Camera, Hole...Flash FULL Stock Rom Package. Start Over...​
What's in this basekit:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
These is my Custom version of Carrier Roms. Each Stock Rom was taken and customized with the semi-same components to give you a fairly clean Diamondish Rom. This rom is NOT based on the PPCkitchen, it was built using DogGuys kitchen. This Rom is not protected and you may customize it if U wish by using the tutorials in my e-Signature at the end of my post. Steps on installing this kitchen and links to the indivudual tutorials are in post #2.
This Rom is a clean Diamond-Skinned one. WHY??? How many of you want SprintTV, or the Bell or Sprint Music store to work on your rom? How many of you want a clean stock rom base to build off of? This is intended to be a stock base for new/existing chefs to build off of. These are all free components! I do not mind you using my base, and I do not mind you sharing your modifications w/other users, but if I hear ya begging for donations and your using my creation/free stuff.... In my opinion, it's just not right people...
Thanks goes out to DogGuy (his kitchen), mchapman007 (his manila2d skins), PPCkitchen.org, PPCGeeks.com & it's users, and the usual folks!
Diamond Rom ScreenShots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Manila 2D Rom ScreenShots (v2.13+) : (start menu items differ than shown)
Original Roms Used:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
HTC-Touch Product Support Rom Download Page
RUU_Vogue_BM_WWE_3.09.666.1_Radio3.42.50_Ship.exe
RUU_PPST_Vogue_SPRINT_WWE_3.03.651.4_2_Radio_3.42.30_AM_NV_2.04_Ship.exe
RUU_Vogue_4350_TELUS_WWE_3.07.661.1_Radio_4350H_3.41.00_Ship_withPPSTPatch1.20_web.exe
RUU_Vogue_4350_ALLTEL_WWE_3.10.671.1_RS3.42.30_NV2.02_PRL30031_SHIP.exe
Here is what's inside the Custom Carrier Rom Series:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- Comm Manager (6-button) (Diamond) (ppcgeeks_oem.rar)
- Diamond_Keyboard_gullum - (Gullum's w/english only)
- Diamondish_White_Dialerv3_41
- HTC Diamond_MP3_Trimmer
- HTC Home 2.1.1005.722 (ppcgeeks_oem.rar)
- HTC Home Diamond Icons (ppcgeeks_oem.rar)
- Pocket Outlook Inbox, Mark All as Read v1.4+
- QuickMenu
- Spb Calc-w_Diamond Skin
- Skin-KB-BL OSXGraphite (ppcgeeks_oem.rar)
- TodayTheme - Metal
- User Customization
- Windows Media Player Skin - Diamond
- zzz_My_Files_OEM
- zzz_My_Registry_OEM
- zzz_My_Sounds_OEM
- zzz_My_TodayScreen_OEM
- zzz_Start_Menu_OEM
- OEM_Megapack_MyUtils_v1.4.1 (special build for custom_carrier_roms)
.... Total Commander v2.5.b3 w/Tweak for 2 window mode, "\" and "\Storage Card\". And sorted by name.
.... PHM RegEdit
.... KeePass Password Manager
.... Nyx Hex Editor
.... PIMBackup v2.8
.... Pocket RAR v1.8.b3
.... ScreenCapture by Illumsoft
........ Installs to \Windows\Start Menu\Programs\Utilities
Bell ONLY - Bell Music Store (in OEM package, not NBH package)
Sprint ONLY - Sprint Music Store (in OEM package, not NBH package)
Tweaks:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- no2chems 1% battery
- A complete list of registry tweaks can be found in ..\OEM\zzz_My_Registry_OEM's RGU File.
- Cleaned provxml files
- Cleaned today screen
- Moved sample pictures/videos, camera templates, ringers to Carrier_Extras OEM. Delete them if you don't use them, but individually.
The following items were completely removed from the stock roms and replaced by a diamond-skinned counter-part:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- Stock Comm Manager (new in v1.2)
- Stock Dialer
- Stock HTC Keyboards
- Stock HTC Home and icons
- Stock MP3 Trimmer (if included)
All original cabs from your roms were left in. Find them on your device in the \windows directory, or in the OEM's in the ..\OEM\OperatorPKG_PT directory.

Flashable ROM LINKS :
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
The following Carrier rom's will need the RomUpgradeUtility.rar.​
RSTG_Alltel_NBH_v1.45-=-=-=- RSTG_Alltell_M2D_NBH_v2.14​
RSTG_Bell_NBH_v1.4 -=-=-=-=- RSTG_Bell_M2D_NBH_v2.14​
RSTG_Sprint_NBH_v1.4 -=-=-=- RSTG_Sprint_M2D_NBH_v2.14​
RSTG_Telus_NBH_V1.4 -=-=-=- RSTG_Telus_M2D_NBH_v2.14​
RSTG_CellularSouth_NBH_v1.4 -=-=-=- RSTG_CellularSouth_M2D_NBH_v2.14​RSTG_Cricket_NBH_v1.4 -=-=-=-==-=- RSTG_Cricket_M2D_NBH_v2.14
RSTG_Qwest_NBH_v1.4 -=-=-=-=---=- RSTG_Qwest_M2D_NBH_v2.14
RSTG_TelecomNZ_v1.4 -=-=-=-=-=-=- RSTG_TelcomNZ_M2D_NBH_v2.14
................................... -=-=-=-=-=-=- RSTG_USCellular_M2D_NBH_v2.14
RSTG_Verizon_NBH_v1.4 -=-=-=--=-=- RSTG_Verizon_M2D_NBH_v2.14 ​
OEM Package LINKS:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
RSTG_Alltel_OEM_v1.45-=-=-=- RSTG_Alltel_M2D_OEM_v2.14​
RSTG_Bell_OEM_v1.4 -=-=-=-=- RSTG_Bell_M2D_OEM_v2.14​
RSTG_Sprint_OEM_v1.4 -=-=-=- RSTG_Sprint_M2D_OEM_v2.14​
RSTG_Telus_OEM_V1.4 -=--=-=- RSTG_Telus_M2D_OEM_v2.14​
RSTG_Generic_OEM_V1.4 -=--=- RSTG_Generic_M2D_OEM_v2.14
Allows support for the following carriers:
Alltell - Bell - Cellular South - Cricket - IUSA Cell - Quest
Sprint - Telecom NZ - Telus - US Cellular - Verizon​
Note #1: For the Generic OEM Package, I built with the RUU_Vogue_BM_WWE_3.09.666.1_Radio3.42.50_Ship.exe rom...
Note #2: Support for these carriers was borrowed from ppckitchen.org stuff...This is my project, if you have questions ask them here...

Upcoming Enhancements:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- I'm outta ideas. This is as basic as it gets. Any further ideas are welcome...
Change Log :
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
RSTG xxx said:
-- rstg_xxx_m2d_v2.14 ------------- 11/3/2008
- Update M2DConfig to M2DC_v0.19.203...done. (Supports changing text colors)
- Updated TodayTheme to be as pictured...done.
- Removed MusicID OEM. Didn't fit w/clean idea...done.
-- rstg_xxx_v2.13 ------------- 11/2/2008
- Update M2DConfig to M2DC_v0.17.183...done. (Supports softkey)
- Added registry fix for windows alarm....done.
- Update MegaPack_Manilla2d_Skin3_MM_Black_ICE as default Skin...done.
- Update 4 included Today Themes...done.
- Update MusicID_1_3_16_QVGA-by-lepsyfou_eng...done
- Added OEM_MegaPack_Games_v1.3...done. (Gotta have games!)
- Added fexploreext_v2.03 (file explorer enhancements)...done.
- Updated MegaPack_Manilla2d_OEM_V2.19 for compatibility with the 18 other M2D skins found here ....done.
- I included the wrong TodayTheme on this one...If you want the white bar on the bottom (as pictured), download and install the .tsk file I have attached to post #1. (Black isn't bad. )
-- rstg_xxx_m2d_v2.11 ------------- 10/19/2008
- Released Manila 2D for all carriers....done.
Click to expand...
Click to collapse
RSTG xxx_m2d said:
-- RSTG xxx v1.45 ------------- 10/10/2008
- Upgraded Alltel with the latest rom release....done.
-- RSTG xxx v1.4 ------------- 09/28/2008
- Remove duplicate MP3Trimmer and CommManager links in Start Menu...Done.
- Added Pocket Outlook Inbox, Mark All as Read v1.4+...Done.
- Disable Customer Feedback...Done.
- Package up Camera into seperate OEM...Done.
- Package up Album into seperate OEM...Done.
- Package up Zip into seperate OEM...Done.
-- RSTG xxx v1.3 ------------- 09/26/2008
- Customized Start Menu
Note: If you already have a built rom, to upgrade without starting over...
1. Replace ..\Kitchen\OEM\OEM_Lang_0409\initflashfiles.dat
2. Copy the ..\OEM\zzz_My_Start_Menu_OEM from the archive and drop it into ..\Kitchen\OEM\zzz_My_Start_Menu_OEM
3. EASY STUFF RIGHT!
Other carriers will be added as I do them...
-- RSTG xxx v1.2 ------------- 09/13/2008
- Packaged Cube into an OEM
- Replaced CommManager w/ Comm Manager (6-button) (Diamond) from ppcgeeks_oem.rar
- Upgraded RSTG_Bell_NBH_v1.2 to Windows Mobile 6.1
- Changed naming system to regular versions so I can update them individually...
- The train of thought is is you can upgrade/omit individual components if you want...
Click to expand...
Click to collapse
If you want Generic Boot Splash Images
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
If you want generic boot splash images after flashing the Bell Radio, flash this: Vogue Stock Boot Splash.zip
A generic HTC splash from Sprint's Vogue. It will hard reset your device... (thanks old_man_jenkins!)

I have decided to open up my Kitchen and my Rom that I am currently using to the community! Even better, I've already customized a Kitchen specific to your Carrier! Below you will find instructions on how to install the pieces. This is a test to see if you are ready to work with a kitchen!
This Thread is open to questions concerning developing, I will answer any questions I can.
So lets get started!
*Before Using this Kitchen/Rom....*
You MUST be:
- Unlocked with the 2.31 unlocker,
- Upgraded your devices RADIO to at least v3.42.xx
My Tutorials you may want to check out...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
The following are links to tutorials on Customizing Custom Rom's:
Customizing Rom Sounds - Sound Themes Tutorial
Customize your StartMenu for PPCKitchen.org's - BuildOS - Tutorial
Customizing Your Rom: Adding Personal Files & Other Stuff
How to Customize a Custom Rom: Adding/Removing Programs
Customizing your Rom: Adding your E-Mail Accounts <--Pending Tutorial
Tutorial: Adding Registry Entries to your Rom (RGU Method)
Yes, all these are used to almost their full potential in this rom!
Here are the following files you will need.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
1 - Dogguy's Kitchen for the Vogue. (my Kitchen of choice) http://www.sendspace.com/file/44mfsl
2 - Your stock rom. Preferably direct from HTC!
3 - Your carriers OEM directory from the above links to add into the kitchen.
Here are the steps needed to get up and running...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
1. Download and install my kitchen, well, ok, it's DogGuy's Kitchen!
2. Extract and decompile your donor Stock ROM
3. Run Prepit.bat to create kitchen files.
4. Delete the ..\Kitchen\OEM directory
5. Insert my ..\Kitchen\OEM directory
6. Perform some optional modifications in the ..\Kitchen\SYS directory.
7. Start having sleepness nights packed with fun!!!!!
1. Download and install my kitchen, well, ok, it's DogGuy's Kitchen!
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Extract Vogue_Kitchen_Tools.rar to it's own directory. Create a directory, and extract the contents to that directory. It will create the kitchen structure when you extract it. I will refer to this directory as "..\kitchen" throughout this thread.
If you need help...Are you ready for this???
2. Extract and decompile your donor Stock ROM
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Download the above file from this link to this thread. Right click on it and open w/WinRar or WinZip. Inside the archive there should be two different *.nbh files. Copy the larger of the two into the directory where you extracted the kitchen to. Now close your archiver of choice.
3. Run Prepit.bat to create kitchen files.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Click on PrepIt.bat from file explorer to decompile your carrier ROM of choice. This will take a couple of minutes, and when it tells you that it is finished, close the window and now you have your base rom. You can start here, but I have made many of the modifications for you already.
4. Delete the ..\Kitchen\OEM directory
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
That's right. Delete the ..\Kitchen\OEM directory. The one you will insert in Step 5 will have all the components/modifications you will need to get started. This is gonna marry up all the OEM modifications I have done for you into the SYS portion of the stock rom.
5. Insert my ..\Vogue Kitchen\OEM directory
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Extract my OEM from the link into the ..\Kitchen directory.
6. Perform some optional modifications in the ..\Vogue Kitchen\SYS directory.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Here is what I did to the ..\Kitchen\SYS directory on my machine.
I delete the following Directories:
..\Kitchen\SYS\WelcomeCenter
..\Kitchen\SYS\WelcomeCenter_Lang_0409
..\Kitchen\SYS\SampleMusic
In order for the custom Today Theme to work, you MUST DELETE: ..\SYS\Shell\mxipcold_wpc_2.provxml
7. Start having sleepness nights packed with fun!!!!!
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
To start, run ..\Kitchen\BuildOS.exe, and then ..\Kitchen\BuildIt.bat to create your flashable RUU_Signed.nbh in the ..\Kitchen\RUU directory. Now you are ready to flash, check out your new base rom to see the modifications you would like to make!

Notes on using the RSTG_Generic_OEM_V1.09.10 Package
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
A big thanks goes out to ppckitchen.org! I sorta borrowed em to make it all work...
I used the bell mobility rom, it looked more generic than most of the others. If you are using this Generic OEM package, then just select your carrier in BuildOs, that's it! I tested this with Sprint and it works fine. There are some missing items, but your phone will work with these carriers. I will not be uploading NBH packages for these, so you'll have to cook your own! Just don't expect your carrier specific items (gps, sms, music store, etc...) to work "out of the box". It's a kitchen, add some salt from this thread, pepper from that thread, and oregeno from that other site, and work on it until you get it to work! And don't forget to share!
My Notes on my_OEM_Packages....
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
With this rom I have basically used it to further my knowledge of my tutorials.
--- The Rom sounds are modifed to suite me. The files are in ..\OEM\zzz_My_Sounds_OEM. Check out the initflashfiles.txt to see how I move them, and the RGU file to see the registry settings.
--- My regedits that I added are in ..\OEM\zzz_My_Registry_OEM. The regedits are in the RGU file and can be edited with notepad.exe in Windows Vista/XP.
--- My misc files that I added are in ..\OEM\zzz_My_Files_OEM. The files in this OEM include the banners for the initial bootup and an updated audiopara.csv for the 3.xx roms. Thanks to Deegimus!
--- I prepare the device's Today Screen in ..\Kitchen\OEM\zzz_My_TodayScreen_OEM. This contains the registry edits in the RGU file that are necessary to remove the Items from the Today Screen. Thats it!
--- I organized the device's Start Menu in ..\Kitchen\OEM\zzz_My_Start_Menu_OEM. This contains the file movement commands from ..\Kitchen\OEM\OEM_Lang_0409\initflashfiles.dat. I essentially moved them to this OEM's initflashfiles.txt file. You can look in here and get a feeling for how I did it.
DO NOT REMOVE THE FOLLOWING ENTRY THINKING IT IS THE WELCOME CENTER!!!
IT WILL CAUSE YOUR DEVICE NOT TO BOOT!!!
Directory("\Windows\StartUp"):-File("Welcome.lnk","\Windows\welcome.lnk")
My Thoughts on this...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Ok, this wasn't as big of a deal as I thought it was gonna be, 4-5 days for all this? But now everyone has another kitchen they can use to create custom Roms. I have done most of the hard work for you guys, so do enjoy! When I said I would support this, I meant I will help support you with rom building. Since I have Sprint, I can help you more there. My area of expertise is rom building, I can't really help you with your GPS not working, or you can't use it in Tuskalewwago. For that I'm leaning on the users of PPCGeeks to help out with the different carriers. I appreciate conflipper stepping up and helping with the gps and alltel, and I hope he get's back with an answer. But the point of this project was to give everyone a non-generic rom base to build with. Diamond has been popular so I picked it.
...you guys and gals sure don't have many questions...

Ok, there is my first xda release...
reserved for issues/common fixes...

[HOWTO] Android Developer's Theme Thread

Check post #2 for the guides, post #3 for the theme list
-----------------------------------------------------------------------------------
This is a thread dedicated to themes for Android. Help is available by clicking the links at the bottom of this post. This is not just for Kaiser users but since that's what I have, this is where I post.
-----------------------------------------------------------------------------------
**** NOTE ****
I have made my first app, StaySafe that lets you back up proprietary apps and put them into a clean, legal ROM. All of my ROMs will be in accordance with the Google C&D order.
-----------------------------------------------------------------------------------
My Themes:
** Manup456 and JAC you are the best themers! Please donate to them, sorry the credit wasn't here but it is now.**
If you like these themes, it's mostly because of Manup456:
You know if you can, you should show him some love:
Dark Donut 1.0
Themed black, much of Hero's looks and keyboard (without keylogging). Stable
Download: http://www.mediafire.com/?mgcztjwmihn
MD5sum: cc83cc96296bc3599d45634c595a956a
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Dark Donut 2.1
Has a new clock, AdvancedLauncher, blurry animations, ad blocking hosts file, many of Cyanogen's enhancements (thank him) such as locking Home in memory, vibrate ever 45 seconds during call, etc. Compcache setting in Spare Parts is for another kernel so ignore that. I'd recommend turning on animations for the full effect.
Download: http://www.mediafire.com/?wyzy2lnyzny
MD5sum: 3d3944859d6026c427f11b2aeb9fd0a6
Dark Tattoo
Latest Tattoo update. Blacked out, some other features.
Download: http://www.mediafire.com/?dy5y34jmym0
MD5sum: f3785765d9182c8d45c2dab55b584e0c
There's more on the way. Feedback, requests, issues are welcome. Anything from clocks to full themes.
-----------------------------------------------------------------------------------
I'm not really good at development I've just done this for a while. The themes were in large part from Manup456 and JAC's ROMs. The real dev heroes are dzo, vilord, zenulator, mssmison, pmos69, jamezelle, kb7sqi, the Dream and MT3G people and everyone else who helped out. The list goes on. If you're able to donate, they deserve it.
-----------------------------------------------------------------------------------
Helpful links and people who have helped me get where I'm at:
Google Android and Linux for KAISER!!-- Main thread for Android on our phones
Linux and Android for Vogue (Kernel Thread)-- Dzo's thread for kernel development. He got us started and is a legend here.
Zenulator's threads for Vogue (they work for us too). He has dedicated a lot of time to helping us out.
Android with sense UI for the vogue
Vogue Android 1.6 Donut
Android 2.0 Eclair for the Vogue
-----------------------------------------------------------------------------------

Quick reference
Table of Contents
Files to modify
A word on APK files
Convert binary XML into human-readable text
How to deodex files
Closing notes
-------------------------------------------------------------------------
Files to modify:
/system/app/Launcher.apk--
kind of self explanatory
/system/app/Phone.apk--
this does not contain the dialer. only the keypad while in a call.
/system/app/Contacts.apk--
this contains the actual dialer images among other things
/system/framework/framework-res.apk--
main files to edit. minor changes here can crash your system if you fail at it.
/system/framework/framework-res.apk/res/layout/status_bar.xml--
hex edit this to change the notification bar text color
In a hex editor, search for 00 00 1C and replace the next 3 value with HTML color codes (RGB)
Refer to this for more info
/system/framework/services.jar
Changing notification text color, among other things..
Refer to this excellent guide. Worked for me.
-------------------------------------------------------------------------
A word on APK files
APK files are signed (SHA1 sigs) so don't just unzip, paste and zip back or you will wonder why things don't work. The easiest method is to use a GUI ZIP program like 7zip or Ark (Linux) to open the archive without extracting it. Drop your images over the existing ones and call it a day.
There is also apkopt which can optimize APKs (as the name implies) but will create a temporary folder with which you can inject your images to before it is resigned by the script. Some files do not like to be optimized like framework-res.apk which is why I don't use this method.
-------------------------------------------------------------------------
Convert binary XML into human-readable text
I haven't done this yet but feel I should list it here. You should be able to make changes, compile back (see the next section below) and diff the binary result for future reference.
http://forum.xda-developers.com/showthread.php?t=514412
-------------------------------------------------------------------------
How to deodex files
Generally it is not too difficult. There are some APKs that will throw errors and I'm trying to figure them out. It's a tedious but simple process and luckily I made some scripts to more or less automate it. I use Linux so BASH scripts are all you're getting.
I made a script that will take an app folder of APK and ODEX files and dump the dex files into subfolders. You will then need to add the dex file to the APK to finish. Unfortunately, because the process runs on the phone, you can overload it if you just try to run the output script. Many APKs required me to go line by line such as Music.apk because they are large files and for some reason the script will not wait for the first part to run so you must manually enter them and wait for each line to finish. I know, I'd love some help with this.
I've attached Deodex_Step1.sh.txt. Rename it to .sh and execute in the folder with APK and ODEX files and it will create a script RunScript.sh with the commands needed to deodex. As I said, this is very memory intensive and I could not just run this script so I went through and did a few at a time, careful to watch for errors and retry until it was done.
You need to download deodexerant (or take it from the SDK), smali and baksmali from here. I shouldn't have to mention that whatever build you are deodexing, you need to be running that on your phone when you connect.
Now, you will have RunScript.sh in the folder. You must connect to the phone with ADB. Set up the environment:
Code:
adb push deodexerant /data/local
adb shell chmod 755 /data/local/deodexerant
adb forward tcp:1234 tcp:1234
Here's an example for deodexing Browser.apk from the RunScript.sh you will end up making:
Code:
adb shell /data/local/deodexerant /system/app/Browser.odex 1234 &
java -jar baksmali.jar -o output/Browser.odex/out/ -x :1234 Browser.odex
java -Xmx512M -jar smali.jar output/Browser.odex/out/ -o output/Browser.odex/classes.dex
adb shell killall deodexerant && clear && echo Done Processing Browser.odex
Important notes are that smali.jar and baksmali.jar were put in the same folder and that I am actively killing the deodexerant process at the end to help prevent overloads though they can and will occur between the baksmali and smali commands so watch out.
Okay, still with me? Now you have a folder called "output" with a subfolder "Browser.odex/" containing classes.dex. Open the Browser.apk file with Ark (Linux) or 7zip and drop in the classes.dex file.
Repeat for all files and you're done.
-------------------------------------------------------------------------
Closing notes
If you are not using an ext2 system partition then you have more patience than I will ever have. It's easy to test your themes on the system using ADB to push your modified files. I recommend that you, in ADB, run "stop" and kill vold, service-manager and acore then run "start" to return to the Android splash screen. Protip: If you use the terminal on the phone you will freeze it the moment you type "stop" so use ADB.
That's all I can think of. Please share any tips you have to help others

Current list of themed ROMs posted on this thread
---------------------------------------------------------------------------------------------------------
Dark Donut--
Mine, check first post.
Dark Tattoo--
Mine, check first post.
Plemen's Hero Blend Themed Donut--
Themed Donut. Check the link for screenshots, downloads, etc. Very clean looks.
Jamezelle's Red Themed Hero
Very nice red theme. Hero ROM. Link is to the post with screenshots and download
Garynsa's The Dudes Cupcake
Click above for the post with download link. No screenshots yet.

what is your base rom for your theme, I have been working on plain ION and Donut trying to decide which I want to stick with

Taken from HTC's site. It's the Donut OTA update that just came out: http://developer.htc.com/adp.html
Apps are deodexed too

COOL; thank you for making this thread

enatefox this is good man. hope more devs get involved with theming

how do i install this theme?

modmouse78, please refer to the links at the bottom of the first post. I posted just the system.sqsh file but you need the other files to get it to boot. To save you, and anyone else who doesn't know how to boot Android, a search please refer to the following:
Instructions
Vogue Hero files
Vogue-Android files
Follow the guide, use the two other links to get the files you need to boot, refer to the links at the bottom of the first post, get it to boot, learn to theme, post the theme here. Take the latest basefiles zip, Haret.exe, the latest zImage (kernel) and the system.sqsh image I posted. Besides the system.sqsh, available in the first post here, all of those files are on the two links above and generally you should use the newest ones. To figure out what I mean you will need to read the links at the bottom of the post as various bugs are reported, etc. Hope that helps and if not, please search/post on the main threads to get a faster answer on troubleshooting if needed.
If you already know about editing images, the image I posted only had framework-res.apk, services.jar, Launcher.apk (soon to be Advanced Launcher) and Phone and you could just overwrite another Donut with those files on an ext2 partition so long as the image is (of course) writable and you have a de/unodexed build. The link on HTC's site I posted has from 1.1 to 1.6 images all unodexed as in never were to start with and it's a candy store for getting a full ROM readily available to edit. In the interest to get people to contribute themes, I can post about deodexing and working with smali files but there are other sites that can explain that as well already.

I hope you dont mind enate but I think I will try your unodexed build for my base from what i have read today that right there is my problem.

Feel free to use it but let me know or link back if you can so people can stay updated while I bugfix.

Great thread enatefox - here is something to add to your list:
/system/framework/contacts.apk--
this contains the resources for the dialer
Check out my themed Donut here complete with themed dialer:
http://forum.xda-developers.com/showthread.php?p=4850339#post4850339

Thanks, updated the second post howto. Feel free to add your screenshots and link here. It's really for showcasing themed ROMs and the links to threads for them. Now I can update the ROM I posted..

i am running donut on my kaiser. I tried replacing this theme with the one that i had and it would never boot.

any updates in data for donut?

I don't have data so can't work on it.
Updated the first page link with a new system image that has the HTC dialer theme. If you're using the last one I posted you can just replace it and keep your old data.img.

loving the dark donut!

is it just me or is dark donut the most stable donut ive tried??

Good to hear, I'm using it for now and found it's pretty reliable. Hopefully I can finish getting wifi issues resolved in the rootfs.img so I can do a bundle. I fixed a bunch of issues but still can only connect to local IPs..
Added plemen's themed Donut to the list. First page, 3rd post will be the running list of ROMs people post in this thread.

great job on the themes.

[Tut] How to change kernel logo (1st boot srceen) [COMPLETED]

We have 3 major works here... So I gonna to make it seperated
-1st post is HOW TO EXTRACT kernel.img (boot.img)
-2nd post is HOW TO CONVERT PICTURE FILE to BOOT.RLE
-3rd post is HOW TO REPACK THE KERNEL PAKAGE into boot.img
Requiredment
-Window machine
-installed cygwin
-the full boot.img/kernel (some kernel won't work because there is no full pakage/ i mean we can't)
-bootimg.zip (tool for UNPACK and REPACK kernel)
-boot_screen_logo_creation_package.rar
Thank and Credit
i- Credit to DooMLoRD Recognized Developer over most of XPERIA devices for his own tool and tutor that I learned before
ii- Credit to jimbo77 Senior Member for his tutorial that I used and learned and tool for unpack and repack
ii- Don't forget to give them a thanks meter
=============================================================================
Here we go
1-This section I will show u how to unpack and repack the boot.img
just see from original thread by jimbo77 from here and download the UNPACK and REPACK tool by him HERE
this is a fast guide from me:-
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
cd /boot
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5-Now, unpack your boot.img by running the following command:
./extractboot boot.img
Click to expand...
Click to collapse
If your output looks like this, then the extraction has worked correctly! Note that the Command Line string has also been read from the source file, this will be used later when you go to re-pack your file.
Your script folder should now look like this:
boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk.
Important Note!
Remember, when editing files in the ramdisk through Windows, such as init.rc, Windows notepad will not format the files correctly, making them almost impossible to read, wheras Wordpad will LOOK like it is formatting the files correctly, if you save one of these files from the Wordpad application it will BREAK the file and it will no longer be able to be read correctly by Android. To edit these files you MUST use an editor such as Notepad++ which you can download for free.
AGAIN...
Special thanks/credit to jimbo77 for his excellent guide

So.. NEXT step to change a kernel logo is here
Requiredment
1-a picture what are u like to look into the 1st boot screen (kernel logo) (make sure it size/resolution same your device resolution)
2-boot_screen_logo_creation_package.rar
3-some infos and knowledges here
4-window machine like i explained on 1st post
My quick guide
-extract the tool.rar
-move extracted files into new folder (name it 'rle' folder without quote)
-move into cygwin folder (to make it easy to follow my simple guide)
-copy your own logo.png (a picture u want to use on a kernel) into same rle folder
(for 4 steps above it shold look like tis)
-now launch cygwin.bat
cd /rle
Click to expand...
Click to collapse
./convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
Ah...my mistake..don't forget to move/copy/replace new logo.rle into
C/cygwin/boot/out/ramdisk/here
if you done good...follow next step on next post (to repack your moded kernel)

Last step before you flash a new look kernel (boot.img) is
Repack your moded kernel
./packboot
Click to expand...
Click to collapse
One thing to note that people may mention in other guides, is that when packing boot.img files, you will usually have to declare a base address, and a command line to the packaging tool. This set of scripts reads the existing command line and base address from the boot.img file you originally provided at the time of repacking, so always make sure you leave your original source boot.img file in the folder and do not re-name it after extraction, your newly created boot.img file will be named boot_new.img and will NOT overwrite the original.
Done! If your screen looks like the image above, then you should now have a freshly created boot_new.img file, ready to be flashed to Android for testing, you can now go ahead and flash it through FASTBOOT one thing I'll recommend though is to first do

I need this for an extra (extra thanks..)
(may U?)

Thanks a lot man, i'm looking for it.

thanks a lot my friend
now i can make may own kernal boot animation:silly:

Thanks! Subscribed to this thread, will try my best to do this soon.

and how to extract kernel.elf? ^^

jimRnor said:
and how to extract kernel.elf? ^^
Click to expand...
Click to collapse
Actually that's the same question I have lol

I think i can't do it with bootloader locked?

Thanks!
Thank you so much!
Working very talented!

R: [Tut] How to change kernel logo (1st boot srceen) [COMPLETED]
If you are on a linux distro, you can use championswimmer's kitchen
Sent from my LT26i using xda app-developers app

how to change the boot logo of the acro s?
I can't find any boot.img file in the rom.ftf
all I can see is KERNEL.SIN
I can extract it.
but how to repack ?
I just want to change the boot logo in this acro s kernel with the new logo.rle that is attached with,
pleaaaaaseeee
help me

Anyone could help me ??
No reply?

prob here is how can i find boot.img for stock rom

thanks

How can I extract elf kernel....
Sent from my LT26ii using Tapatalk 2

Why it says:
Android Magic not found in ./boot.img ????

phil1405 said:
Why it says:
Android Magic not found in ./boot.img ????
Click to expand...
Click to collapse
are you extracting kernel.elf?
this tut was not working on kernel.elf, or maybe your cygwin got problem

No i tried with a boot.img :/
Currently I'm trying to install the perl and cpio packages...

[ROM+GUIDE][SM-G955x][AQH3] CeX - Flashable Repackaged Stock [29/08/17]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Definition
Let me first define what I mean by Creator's Experience. This ROM is just as good as your stock ROM on KNOX 0x0. I am in no way taking credit for any of the development in this ROM, I'm just repackaging the stock Samsung ROM in Samsung's experience how they created it. But if you flashed stock ROM you may get a ton of KNOX warnings so selling the device or giving your device to someone else would make it more complicated and frustrating due to nagging popups that you have to disable by first setting up the device. I wanted to create something that you can restore your device to when you get bored of a custom ROM, or you just want to use the latest stock firmware again.
This ROM will never contain any tweaks or system addons, it is barebones stock with no KNOX and stubs so people can use it as a rescue/reference firmware.
Purpose
Being the owner of the Korean Samsung Galaxy S8+ 128GB/6GB (SM-G955N), there are only so many stock firmwares available from Updato or Sammobile. All listed firmwares contain all the CSCs located in the /system partition, and the CSC file toggles between them. This means that regardless of what CSC you flash on the device, you will activate all the applications that were disabled by the CSC (KT mobile apps should be disabled on the SKT CSC, and vice versa). So flashing a Canadian CSC will still have every single South Korean carrier bloat on your device, which sucks.
This is a strange situation with 955N users, where ALL THE BLOAT is stored in /system/priv-app, while the csc is just one small file that controls which applications are active/inactive on the device.
Process
So, what does this mean? I wanted the stock international 955F ROM on my device, really badly. But Odin refused to flash it due to a secure write/invalid magic string error. I have tried everything from modifying the PIT tables in the ROMs to flashing custom ROMs. As much as custom ROMs are great, I wanted something I could fall back to when sh*t hits the fan, as well as something that fit the stock lifestyle...since I would really have loved to keep KNOX 0x0 if the Korean firmware was not as bloated as I thought it would be.
So for those who were searching for the stock ROM that was created with stock in mind, I have repackaged the 955F stock using the kitchen by @SuperR., with removed KNOX + KNOX apps (Secure Folder, KNOX Settings 1 & 2, Samsung Pay, Samsung Pass, etc.), removed stub apps (Microsoft apps folder) and removed CSC (I will elaborate more below).
As it takes me from 3-6 minutes to download stock firmware, I will be keeping this up to date for people who will need a rescue zip.
Reproduction
The reason why I'm keeping this as clean as possible is because it functions the same way as the Odin package. The AP will be the ROM zip, while you have to flash your own custom kernel, and flash the CSC package by @Tkkg1994. Finally, to top everything off, Magisk will be flashed.
A flowchart of this process (clean flash) is listed below:
Flash CeX stock (this ROM)
Flash the CSC using the CSC utility tool by @Tkkg1994: https://forum.xda-developers.com/galaxy-s8+/development/utility-flashable-csc-selection-v1-0-0-t3605264
Flash the kernel, I highly recommend @jesec's Jesse Kernel: https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/kernel-jesse-s-kernel-galaxy-s8-exynos-t3603521
Flash Magisk v12+: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
A flowchart of this process (dirty flash) is listed below [dirty flash is supported on CeX, as long as you follow these steps]:
Use TWRP and wipe /system
Flash CeX stock (this ROM)
Flash the CSC using the CSC utility tool by @Tkkg1994: https://forum.xda-developers.com/galaxy-s8+/development/utility-flashable-csc-selection-v1-0-0-t3605264
Flash the kernel, I highly recommend @jesec's Jesse Kernel: https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/kernel-jesse-s-kernel-galaxy-s8-exynos-t3603521
Flash Magisk v12+: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Anomalies
At the current stage, this is just the stock Samsung firmware. So any bugs found in the official bugs list of the current firmware revision would be present in this ROM. See the second bracketed codename in the title of this thread.
Do you use Netflix or Amazon Prime Video?
With their Widevine DRM Module, it bypasses anything Magisk Hide has to offer.
Using TWRP, remove /system/lib/liboemcrypto.so, then reboot to system.
If you ever want to restore stock, this is the AQEB binary: https://www.androidfilehost.com/?fid=961840155545569722
Screenshots
There really doesn't need to be any screenshots, unless you have never turned on your phone on stock ROM before...but here, I'll show you Settings.
SafetyNet?
This is a simple phenomenon solved by having both a custom kernel with KNOX 0x0 simulation, like Jesse's kernel, and Magisk v12 installed with Magisk Hide enabled. It is confirmed that CeX respects SafetyNet.
Programmatically Displayed Debloated Applications/Services/Libraries
Code:
system/app/Facebook_stub*
system/app/MSSkype_stub*
system/app/SecureFolderSetupPage*
system/priv-app/OneDrive_Samsung_v2*
system/priv-app/SecureFolder*
system/priv-app/SamsungPass_1.1*
system/priv-app/Excel_SamsungStub*
system/priv-app/PowerPoint_SamsungStub*
system/priv-app/Word_SamsungStub*
system/container*
system/app/BBCAgent*
system/app/Bridge*
system/app/ContainerAgent*
system/app/ContainerEventsRelayManager*
system/app/kioskdefault*
system/app/KLMSAgent*
system/app/Knox*
system/app/KNOX*
system/app/MyKNOX*
system/app/RCPComponents*
system/app/SecurityLogAgent*
system/app/SwitchKnoxI*
system/app/UniversalMDMClient*
system/container*
system/etc/secure_storage/com.sec.knox*
system/preloadedkiosk*
system/preloadedmdm*
system/preloadedsso*
system/priv-app/KLMSAgent*
Download Links
AndroidFileHost Folder (Autopushed builds): https://www.androidfilehost.com/?w=files&flid=185563
AQH3 builds (August):
FullRebaseOptions from last build:
https://www.androidfilehost.com/?fid=745425885120758691
Normal build:
https://www.androidfilehost.com/?fid=817550096634795846
AQF7 build (June): https://www.androidfilehost.com/?fid=673368273298964156
AQEB build (May): https://www.androidfilehost.com/?fid=817550096634773510
Credits & Thanks
@SuperR. for his kitchen
@jesec for him helping out when I was frustrated something isn't working, and pretty much his experience with his 955N
@fahadali2315 for refreshing my memory of messing with a Samsung device
Anyone I missed, just hit me up in private!
XDA:DevDB Information
CeX, ROM for the Samsung Galaxy S8+
Contributors
nicholaschum, fahadali2315
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Current Stable Version: AQH3
Stable Release Date: 2017-05-31
Created 2017-06-01
Last Updated 2017-08-29

Building with SuperR Kitchen for your own stock region ROM
If you're interested in creating your own flashable ZIP based on a ROM, I will be listing the full instructions on how to get your own stock ROM up and running.
I will be building the latest XXU builds as soon as they drop.
Please do not PM me, instead, post in the thread for people to learn.
Prerequisites:
- Your device MUST be of the Exynos variant, with an available TWRP on the device. If you have a Qualcomm device, close this window now!
- You must have a Linux environment. I know @SuperR.'s kitchen works on Windows using Cygwin, but as an AOSP developer, I work with Linux to build stuff!
- Sudo account
- Collect and utilize as much wits as you can!
- I will be doing all of this from the command line using SSH, no GUI for this!
1) Download the latest SuperR kitchen here: https://forum.xda-developers.com/ap...chen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434
by doing this (press enter after each line in this code block):
Code:
curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | sudo bash
sudo apt-get install git-lfs
git lfs install
git config --global credential.helper cache
cd ~/
git clone https://bitbucket.org/superr/superrs-kitchen.git
cd superrs-kitchen
./superr
The first time running the kitchen, you may need to install dependencies. It should automatically install all dependencies for you, but if it keeps asking you to install the same dependencies, you should install them using
Code:
sudo apt-get packageName
.
After all dependencies are installed, press 1 to create a new project, and name it whatever you want. In this example I will name it STOCK.
Press Q once the project is created (quits SuperR kitchen)
2) Download your Samsung stock firmware. There are two main sites nowadays to get Samsung stock firmwares from, including Updato and Sammobile.
Updato: http://updato.com/firmware-archive-select-model?q=SM-G955F&rpp=15&order=date&dir=desc&exact=1
Sammobile: https://www.sammobile.com/firmwares/galaxy-s8/SM-G955F/
You will need to get the firmware on your Linux box, or from Updato, right click Download (the orange button) and click Copy Link.
If you are planning to download from the SSH box, do:
Code:
cd ~/superr-kitchen/superr_STOCK && wget link_of_updato
3) Your firmware file is now ready to be loaded up into the kitchen. So do:
Code:
./superr
Then click 4 to extract for a new ROM, then click "y"
4) When it asks you whether you want to include cache.img, it doesn't really matter if you do or don't. Click "y" and include it in the ROM.
5) It will then ask you to type a name for your output ZIP
6) If it asks you where to locate the partition info from, pick the entry that is recommended, which takes the partition from system.img and recovery.img (Detect by-name from boot/recovery images (recommended))
So simply click 1.
7) Finally, we must set the perm type/archive type of your images. Click 1 for set_metadata (KitKat+)
NOTE: I have tried using Sparse dat for Korean 955N image - which working at a cost of all Google apps crashing/not responding, but doing so on the 955F ZIP will completely break and cause it to get stuck in TWRP trying to flash. set_metadata is the most stable.
8) You can now fiddle with the ROM! It is highly recommended to replace the stock kernel with @jesec's kernel, but make sure you extract his other folders from his ZIP into your working directory (~/superr-kitchen/superr_STOCK/system/*) or you won't boot! You can either opt for this, or just flash the kernel ZIP to retain support from Jesse (this is what I picked for CeX).
Key configurations (the options I picked for CeX):
->7) Boot/Recovery Tools
- Unpack boot.img
- Type 5 and disable forceencrypt
- Type 1 and pack boot.img
->8) ROM Tools Menu
- Asserts Menu (if you're trying to do 955N ROM)
- Add/Remove Device (dream2lte) <- change from dream2lteks or any other model, since TWRP only recognizes dream2lte.
->6) Debloat Menu
- Custom Debloat
- ~/superr-kitchen/tools/root/bloat_custom must be edited to contain these entries (nano ~/superr-kitchen/tools/root/bloat_custom to edit the file):
Code:
system/app/Facebook_stub*
system/app/MSSkype_stub*
system/app/SecureFolderSetupPage*
system/priv-app/OneDrive_Samsung_v2*
system/priv-app/SecureFolder*
system/priv-app/SamsungPass_1.1*
system/priv-app/Excel_SamsungStub*
system/priv-app/PowerPoint_SamsungStub*
system/priv-app/Word_SamsungStub*
system/container*
- Remove Samsung Knox
9) You can make external edits by placing files in ~/superr-kitchen/superr_STOCK/system, or do whatever you want with the APKs
10) Let's start building!
If you left the window, all you have to do is do:
Code:
./superr
8
7
1
This will get you to the ROM zip building screen.
If the kitchen asks if you would like to convert the updater-script to an updater-binary, do it. Now give it some time to build. Usually my computer takes 2-3 minutes.
11) Finally, you can decide whether you want to sign the ZIP or not. Personally, I do not sign my ZIPs.
If you decide to skip signing, you're done! Just type "n" on your keyboard and click "q" to quit the kitchen. Your new ZIP is located in ~/superr-kitchen/superr_STOCK/STOCK_BASED_ROM.zip
You can either move this to your h5ai server, like I do at http://download.projektsubstratum.com/, or you could use transfer.sh here:
Code:
curl --upload-file ./STOCK_BASED_ROM.zip https://transfer.sh/STOCK_BASED_ROM.zip
You could also move it to AndroidFileHost using FTP, if you have a developer account.
This may take a while for the upload to complete, but once it is done, you are ready to flash the four ZIPs:
The ROM
A custom kernel
The CSC utility flasher
Magisk (for SafetyNet)
12) Congratulations, you're done!

Pulling your own CSC files
So you tried to extract the CSC file (cache.img) from the CP tar for Odin but no luck flashing...but you really wanted an up to date version..
Prerequisites:
- Your device MUST be of the Exynos variant, with an available TWRP on the device. If you have a Qualcomm device, close this window now!
- You must have a Linux environment for simg2img
- Sudo account
- Collect and utilize as much wits as you can!
- I will be doing all of this from the command line using SSH, no GUI for this!
1) Download simg2img to your Linux box and build the project
Code:
cd ~/
git clone https://github.com/anestisb/android-simg2img
cd android-simg2img
make
2) After simg2img has been compiled, we will have to use it.
Place your cache.img.ext4, yanked out of the CP.tar.md5 file (renamed to CP.tar) in the same directory of the git cloned repo
If you need a command to extract the .tar file, run:
Code:
tar xf CP.tar
3) Convert the image
Code:
./simg2img cache.img.ext4 cache.raw.img
4) Mount the image
Code:
sudo mkdir /media/csc
sudo mount -t ext4 -o loop cache.raw.img /media/csc
cd /media/csc
5) Copy the prepared flashable CSC zip out of the image
Code:
cp sec_csc.zip ~/
6) Flash the ZIP
7) Boot into the system. If you flashed a multi-CSC, you may need to configure it to be specific to your country.
This will require root, so get yourself into adb shell, then (credits to @jesec):
Code:
adb shell
su
am start com.sec.android.Preconfig/.Preconfig
A window will pop up giving you all the options selectable in your MultiCSC. Clicking and installing any of them will wipe your device, so watch out!

one last reserve post

locking my thread till the upload is finished....

@OP
Great idea bro, thanks a lot.

Nice work! @nicholaschum

Very Good! Thanks!

Sorry, my english is to bad...
Thats mean, if i Flash this Rom and later, when i go back to stock, my knox will be 0x0?

No, KNOX still tripped but with fake 0x0

Good work !! @nicholaschum

Th3PorTuGa said:
No, KNOX still tripped but with fake 0x0
Click to expand...
Click to collapse
Thanks

@nicholaschum
Can I ask possibly a dumb question
Is flashing CSC required?
I mean what happens if you don't flash CSC.
I am currently in AU on Vodafone CSC. I would change it to XSA but if I decided not to or forgot to do it. Would the CSC activate based on what is currently set as my CSC there or is this required so the rom can then load the apps based on location?

Perfect Build Perfect ROM. Installed as per instructions and works like a charm. Thanks for the work.

davjak said:
@nicholaschum
Can I ask possibly a dumb question
Is flashing CSC required?
I mean what happens if you don't flash CSC.
I am currently in AU on Vodafone CSC. I would change it to XSA but if I decided not to or forgot to do it. Would the CSC activate based on what is currently set as my CSC there or is this required so the rom can then load the apps based on location?
Click to expand...
Click to collapse
The CSC is required or else Samsung stock ROMs will not know how to configure your phone. This also I closed LTE-A capabilities, wifi calling and VoLTE functionality. Since this ROM does not contain any CSC you could flash the DBT CSC from the flashing utility which is the default CSC on most ROMs that is Germany debranded.

@nicholaschum - thanks for sharing this ROM. i'm using as a daily driver for my "work device" in combination with the ATT CSC flashed via TK's CSC package. if/when Substratum is available for TW based S8 ROMs, can i assume your ROM will support it? thanks for taking time to read/respond to my question.

Just installed. Silky smooth! Great work op

cortez.i said:
@nicholaschum - thanks for sharing this ROM. i'm using as a daily driver for my "work device" in combination with the ATT CSC flashed via TK's CSC package. if/when Substratum is available for TW based S8 ROMs, can i assume your ROM will support it? thanks for taking time to read/respond to my question.
Click to expand...
Click to collapse
Yes. That is the whole point behind it , keeping it stockish with subs support when it arrives.

I want install it, but i dont what do..
I want sale my phone later and get Note 7.
Is complicate if we cant use Samsung pay when we back to stock.

@nicholaschum Thanks heaps for this, took the leap and followed the instructions. Very simple task! now running XSA CSC with AQEB