Hi there,
I am trying to find MoDaCo's rom with the framework and apps de odexed (that is, not pre odexed for speedup). If someone has it, it will be nice if it can be uploaded on 4shared (please no megaupload or rapidshare). Latest MoDaCo rom is preferable, this is already done for the Nexus one and G1 roms which eases ROM hacking.
Thanks
The latest released version of MCR is available for free over at modaco.com. If you want access to the latest beta (unreleased) versions you'll need to sign up for an account (adfree or premium).
I am not looking for the ROM itself, instead, I am looking for specific files in MoDaCo's ROM. They are the app and framework files but de"odex"ed (that is not pre compiled).
Thanks for your help
Compilation and odexing are 2 separate things.
You have 2 options:
1: PM Paul and ask him nicely, if he can share the files
2: unodex them yourself. It's a matter of minutes, so don't be lazy.
Its not an issue of lazyness, its an issue of Heroless-ness
Anyways, I will try the ask Paul option
i'm in the same boat...dont have a hero but would like a de-dexed version of the stock hero rom
UAE said:
Its not an issue of lazyness, its an issue of Heroless-ness
Anyways, I will try the ask Paul option
Click to expand...
Click to collapse
just for my curiousity: what do you need an unodexed hero rom for if you don't have a hero?
kendong2 said:
just for my curiousity: what do you need an unodexed hero rom for if you don't have a hero?
Click to expand...
Click to collapse
To port the hero sense UI to another device
.odex files are platform specific. From the dexopt documentation:
The output of dexopt is byte-swapped and struct-aligned for the host, and contains indices and offsets that are highly VM-specific (both version-wise and platform-wise)
Click to expand...
Click to collapse
With the de-odexed versions, the apks contain the original classes.dex file which is used to generate platform specific odex files when first booting
bpedman said:
To port the hero sense UI to another device
.odex files are platform specific. From the dexopt documentation:
Click to expand...
Click to collapse
i see. i can help you here, if you give me some starting point. i am a linux sysadmin who has never deodexed anything, so i'll be good if you throw me a script or something...
dsixda's Android Kitchen - Now for Samsung Galaxy S
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of version 0.178, you can now create your own Galaxy S ROMs with the kitchen.
I'd like to thank Perka for testing and providing feedback, and also for giving me some ideas through his tutorial in his Ultimate ROM Cooking Guide.
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S with a ClockworkMod custom recovery. The kitchen supports the GT-I9000, but should also support most of its variants, such as the Captivate, Fascinate, Vibrant and Epic.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
IMPORTANT (DO NOT IGNORE THIS STEP): To verify your variant of the Galaxy S works in the kitchen, read this post.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
factoryfs.rfs (and optionally: cache.rfs, zImage)
PDA.tar.md5 (and optionally: CSC.tar.md5, PHONE.tar.md5)
PDA.tar (and optionally: CSC.tar, PHONE.tar)
TAR/ZIP file containing factoryfs.rfs (optional: cache.rfs, zImage, modem.bin)
TAR/ZIP file containing PDA.tar and others
TAR/ZIP file containing PDA.tar.md5 and others
Custom ROM:
ZIP file originally created by the kitchen from the stock firmware (NOTE: The kitchen does NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a factoryfs.rfs but then didn't include the cache.rfs, then you have the option to add a cache.rfs later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Optional: Add a rooted kernel (zImage) to the base of your working folder
You can create a ROM without a zImage and thus keep the existing kernel on your device, although keep in mind that a newer ROM may not work with a kernel meant for older ROMs!
If you use the stock kernel (zImage), you can always replace it later with the CF-Root kernel or any other custom/rooted kernel. Just replace the stock zImage anytime before you build the ROM.
Optional: Add a modem.bin to the base of your working folder, or remove the existing modem.bin if you don't want it. You can flash the ROM with or without a modem.bin.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers, and to prevent confusion, please only discuss Samsung Galaxy S in this thread!
Most of all, have patience, take your time and enjoy!!
thanks for info mate exactly wat im looking for
cheers
Thx for this. Working very well.
Very nice guide
Just what i was looking for great
Sent from my GT-I9000 using xda premium
Thanks works very well! *5 stalls *
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Gvdn said:
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Click to expand...
Click to collapse
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
dsixda said:
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
Click to expand...
Click to collapse
So no matter what i try it wont work with kitchen? Damn too bad i was starting to know my way around it now
Kitchen made the whole rom without a problem tho. Using the boot.img option and following Perka guide. Just seems its not generating the Meta file correct.
Do u have any idea to what i asked earlier? If there is only 3 different update-binaries , can i get all 3 and test em out and 1 will work for sure or it wont work no matter what?
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
dsixda said:
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
Click to expand...
Click to collapse
Ok thx alot. Sadly no subforum for Gio
CWM issue
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
krazykipa said:
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
Click to expand...
Click to collapse
I'm having the same problem here with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS, I tried to move to DarkCore_4.0_JVS and the device get into reboots (just after activating lagfix).
its 2 days now that im working on stock rom and trying only to root and deOdex... help?
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
bhundven said:
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
Click to expand...
Click to collapse
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
dsixda said:
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
Click to expand...
Click to collapse
Looks like the SGH-T959V file exists. Thanks for helping me figure that out!
I am having an issue with wi-fi not be able to connect after i have flashed my build.. and thats about it. I'm not sure whats causing it any ideas?
EDIT:
Was the updater-script, i swapped it out with another and all is well.
There are problem with kernels. I can't change?
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
xtrem88 said:
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
Click to expand...
Click to collapse
If it's basically the same device then it should support it. Just make sure you have an entry in the kitchen for the ro.product.device value. See the note in the 2nd step in Post #1.
I know nothing much of ROM Development but I do have the basic foundation knowledge and I wish to commence in releasing a modded ROM soon as a start...
As a start can anyone give a pointer of the following :
1. Boot image » what is required to extract / modify ?
Note : Please do not re-quote as I will be making changes as we go along
So let us discuss and explore so that we can learn together....
Sent from my GT-I8150 using xda premium
I was thinking of doing the same andy. Asked cow to see if he would like to point me in the right direction.
I had to abandon my idea as new house i moved into i dont have any internet to work off so had to put my plans on hold. But here is what i was told what is basically needed for cooking roms.
1) Download Kitchen:
http://forum.xda-developers.com/showthread.php?t=633246
2) Download your stock ROM
3) Extract system.img.ext4, cache.img.ext4 and boot.img from stock ROM, put into Kitchen's original_rom folder
4) Do this for SGW: http://forum.xda-developers.com/show...8&postcount=12
- No need to upse KezzaPlane's updater script anymore
5) Run ./menu in kitchen and follow the instructions
On part 3. If you want to use a different kernal( Oc one or simply Cow's oc kernal) please make sure to ask for the use of the kernal first and then use that boot.img and replace it into the rom that you are going to cook.
hi, thank you very much for the information, so far i have downloaded eclipse ee, and the android sdk but had zero idea where to start lol
i was so motivated when arco started and released his ics rom that i wanted to do my share as well, i have experience in coding in java but also wanted to know what else to do, then i bumped on this post, thanks a lot man!
snwman said:
4) Do this for SGW: http://forum.xda-developers.com/show...8&postcount=12
Click to expand...
Click to collapse
um unfortunately that link doesn't seem to work, may i ask for the full link?
this is awesome, i will support this thread. pls someone provide clear informations on how and what needed
Shiny ROM: Android 4.4.4, KTU84P for Galaxy Nexus (Maguro)
Skip right to the downloads (if you dare )
Hello there XDA GNex community! I'll admit this is a pretty spontaneous post; I've been building ROMs from the Android Open Source (Project) for awhile now, but I've never "published" any of them. I myself used to own a Verizon Galaxy Nexus, so I've always built from AOSP to make sure I'm as up to date as possible. Well, that's a little background so let's get going with the overview of the ROM itself:
Overview
This ROM is Android KitKat 4.4.4, build KTU84P. The ROM is built directly from source, that is, the Android source code published by Google available for download to all of us developers. The reason I say the ROM is "OTA-like" is because I make VERY few modifications to it, aside from the things that it takes to get the ROM working. I'll go into detail about those things below, but basically I just want the ROM to make your phone feel stable and shiny and new as if it has just received a new OTA update. That being said, it's clear that the landscape of Nexus devices is changing as new ones are released. Therefore, the other primary goal of this ROM is to keep our Galaxy Nexus as close to the modern Nexus design as possible. This means that I will also add in features that will still be stock, but will also make our phones as close to a current Nexus as possible.
As for how I handle the forum side of things, I'm always open to comments, questions, suggestions, requests, etc. I know that most of those things will often be in the form of criticism, but it's okay, I think I can handle it That being said, I do also have a life and am a college student, so I may not get to come on here ALL the time. I will check back as frequently as possible, and I'm hoping that you guys will help each other out as much as possible! Keep it friendly! So now for the details...
Features
Stock Android 4.4.4, build KTU84P
Source (AOSP) built kernel (boot.img)
Easily rootable (see information below)
G-Apps (GMail, Play Store, etc.) included in build along with Nexus apps
Stock browser replaced with Google Chrome
Shiny restart options - access them by holding down the power button and then long pressing on "Power Off"
All the crazy Google proprietary app stuff has been taken care off
Updated frequently
Everything works!
So what do I mean when I say "Everything works!"?
I'm sure by now you all know that when someone says that, it usually ends up not being true. This ROM is not an exception to that rule, but I can say that I've tested most of the things that would be expected to work in stock Android, such as...
WiFi Tethering (no subscription check)
Bluetooth streaming
Google account sign-in and auto-restore of apps and settings
Google Wallet
Location Services (pretty fast GPS lock in my area also)
Photosphere
Android beam
Photo editing with the new filters
Email
Exchange support
Like I said, the normal stuff (data, voice, hardware acceleration, etc.)
More things that aren't important enough to mention here - check out the changelog for a more comprehensive list
Possible Bugs
It's impossible for me to test for and notice EVERY single possible bug in the operating system, so as of right now I can't say that there are any, although I'm sure you will find some. If you do, report them here!
Other IMPORTANT Information
Root
But wait, nothing in this post said anything about root!!!11!!1!1!!! That's right, my ROM does NOT have root built in! (I don't use any root apps, and it's important to the whole "OTA-like" theme). That being said, the ROM is easily rootable; I made sure of this because I know that many, many of you will use root for many useful purposes. If you want to root the ROM, it's as easy as installing Chainfire's new superuser control app/su with this ZIP file. More detailed information can be found in the "Installation Instructions" section. **NOTE** If you are rooted and upgrading to a new build, you should not have to reflash the rooting flashable ZIP because the ROM will keep root for you.
Updates
Now that the ROM has gotten to this stage, the update policy needs a bit of editing Based on the stats I have access to from the website host and data that I collect myself, it seems like Shiny ROM is currently (as of May 27, 2014) stable for at least 80% of the users who have downloaded it. Based on this, and because the ROM is stock, Nexus-like, it doesn't really make sense to update the ROM as frequently as before. The ROM will still be updated as soon as possible after new versions of Android are released. In between Android versions, I will work on making things 100% stable, although that goal isn't always attainable with older devices and aging hardware support. If we decide to explore other paths for the ROM, you will see many more updates If/when the time comes for me to stop updating Shiny ROM, I will let everyone know in a clear way.
Radios
This ROM will (most likely) work with any maguro radios (so long as you have the appropriate ones for your device/area; however, I of course recommend using the most recent radios doe your device. You can find flashable ZIPs of all radio versions in the download post.
Bootloader
Once again, I'm assuming that this ROM will work with all tuna bootloaders; BUT for optimal experience and performance, use the newest Google-approved bootloader, PRIMEMD04. My ZIP installation package for that bootloader can be downloaded here.
ClockworkMod Recovery
I personally recommend using ClockworkMod Recovery as it has always worked well for me with no quirks. Android 4.2 messed up a few aspects of recoveries because of its multi-user system. ClockworkMod Recovery has been updated to correct some of these issues, and I recommend updating to the most recent version, 6.0.4.7. You can flash either the touch recovery or non-touch recovery image through fastboot OR you can download my flashable recovery update ZIP (touch/non-touch) and flash it in recovery. Check out the installation instructions for more details on this.
Some Other Not-so-important Information
Naming Conventions
All of my ROM ZIP files are automatically generated by my build computer. All builds begin with the prefix ShinyROM_maguro_aosp. That prefix is always followed by the date in mmddyy format (e.g. 112212), a hyphen ("-"), and the time in 24-hour, hhmmss format (e.g. 153945). Finally, all builds end with the "signed" suffix - it just helps me know which packages have finished building and which have not. Hopefully this helps everyone to know which update is newest; I stay away from version numbers because I let Google do all of the version control.
Source
In keeping with the spirit of open-source, all relevant Shiny ROM code can be viewed on Github. I'm not extremely experienced with Github, so bear with me as I learn! Thank you!
File Hosting
I've switched over from using Dev-host to a privately hosted site, graciously and generously given to me by user Goofball. Dev-host is still an amazing service, but it's much more convenient for me to use a privately hosted site, plus I get my own suburl and FTP access! HUGE thanks to Goofball! The private hosting will definitely help me deliver a better experience to you guys as far as downloading goes. You can view all of my uploaded, public files here: http://shinyrom.goofball.org/
Also, if anyone ever wants to mirror for me, please feel free so long as you keep the file name and the file itself intact. As for everyone who downloads from a posted mirror: BE CAREFUL! Always use a virus scanner and be careful with what you are putting on your device!
Installation Instructions (VERY IMPORTANT - Note: You can flash all of these ZIPs in CWM or TWRP*)
*Android 4.4 KitKat builds must be installed using the latest version of your preferred recovery!
ROM
1. Download the latest version of the ROM from the download post. (Also download any other files you will need to install, such as Chainfire's SuperSU Root ZIP, radio installation ZIPs, the bootloader installation ZIP, etc.)
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. If you want to be 100% sure there are no problems, wipe data. If you are coming from another ROM or Android version, wipe data. If you do not wipe data and something goes wrong, repeat this process but wipe data - this step is not necessary if you are simply upgrading.
10. If you are updating your radios, flash the radio ZIP
11. If you are updating your bootloader, flash PRIMEMD04-signed.zip
12. Flash the ROM (ShinyROM_maguro_aosp...signed.zip)
13. If you are rooting, flash Chainfire's SuperSU ZIP file - this step is not necessary if you were rooted on the previous build and are simply upgrading.
14. Reboot your phone, and enjoy!
**Note: If you are simply upgrading to a new version of the ROM and want to keep root, follow the exact instructions above, and do not format /system. It really is not necessary to format /system at any time (unless specifically noted), as the ROM installer has this function built in.
Mods
1. Download the latest version of the mod(s) you wish to install from the download post.
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. Install the mod(s) you downloaded in step 1.
10. Fix permissions (not really necessary)
11. Reboot and enjoy!
**Note: You can remove all mods you've installed by dirty flashing the latest version of the ROM.
ClockworkMod Recovery (Fastboot method - must have an unlocked bootloader and fastboot in your path)
1. Download either the CWM touch recovery image or non-touch recovery image to your computer and rename it to "recovery.img".
2. Power off your phone.
3. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
4. Plug your phone into your computer using the standard USB cable.
5. Open the command prompt/terminal and navigate to the folder where your "recovery.img" is saved.
6. Type "fastboot devices" to make sure your phone is recognized; a serial number should show up on the screen.
7. Type "fastboot flash recovery recovery.img" and wait for the process to complete (should be quick).
8. You're done! Use the volume keys to select "Recovery" and boot into your new recovery!
ClockworkMod Recovery (Flashable ZIP method - easier)
If you are updating your recovery before flashing a ROM, these steps should ALL be completed PRIOR to flashing the ROM.
1. Download either the touch recovery flashable ZIP or the non-touch recovery flashable ZIP.
2. Place the ZIP file downloaded in step 1 on your internal storage/sdcard.
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Choose "Install update from sdcard"
7. Select "Choose file from sdcard"
8. Find the flashable recovery ZIP file you downloaded and install it
9. Back up to the root menu of recovery
10. Select "advanced"
11. Select "reboot recovery"
12. The phone should boot up into your new recovery!
Credits
As with most ROMs, I only did a small part to get everything together. Also, a note that should be made here is that when I am using someone else's file, I ALWAYS host files on the Shiny ROM server to ensure that I don't put any unnecessary stress on their servers. Any file, however, still belongs to and is accredited to its original creator as listed below:
Willyjay - For providing us with lots of amazing and innovative mods for the ROM!
Inmanster - Another great modder who we are fortunate to have here in the thread. He works in collaboration with Willyjay and his mods for many things, but also does some of his own unique mods!
Chainfire - For their SuperSU app and su binary, as well as the convenient ZIP update package, which was previously used and recommended. Check out their website, http://www.chainfire.eu/
Groupers - My new buddy who helped me out with a GPS issue that popped up in 4.2.
Google - Without their amazing staff and willingness to share the source code of their operating system, I wouldn't have been able to build this ROM! Of course, all of the Google apps are theirs, along with the Play Store and system apps. They really are the true owners of all of this.
Samsung - We all may have some mixed feelings about them, but in the end they gave us the amazing, hackable phone that is the Galaxy Nexus.
XDA - By providing such a great Android community, ROMs like this one are able to easily connect with users and get their work out there
Dev-Host - The file-sharing service with virtually no limits on sharing - kudos to them and their hard work. d-h.st
Koush and the ClockworkMod/ROM Manager Team - They make the best recovery that's been around for longest, and their constant updates allow us to keep making ROMs! Also, Koush's recently released open source Superuser control app is the best available and the one linked to in the thread. Thanks Koush! clockworkmod.com
Kevdliu - Huge thanks to this dev and their amazing quick settings mod!
The CyanogenMod Team - For a working implementation of DSPManager on Android which can be ported to any AOSP-based ROM! Without them and Bigwavedave25, the DSP manager mod would not be available! Be sure to thank them and to check out the CyanogenMod website! Also, for their feature-filled version of the stock Messaging app which is available as a mod for my ROM!
bouchigo - a user who has helped to make the CM10 Messaging app available as a mod for my ROM in conjunction with Willyjay for bringing it to my attention.
Schoat333 - A user who helped out Willyjay with the bubble styled MMS mods. The credit for the screenshots to go along with the mods goes to him!
Yarly - The most experienced admin I've ever had the pleasure of talking with, who taught me some new debugging tricks and answered some of my questions.
Razorloves - Another admin who helped me out with a few problems and answered a lot of my questions!
Tiny4579 - A kernel dev who also took the time to talk with me and answer a few of my questions.
Thanks to everyone for their hard work and sharing that work with others!
DISCLAIMER
Come on guys, it's a Galaxy Nexus, to what extent could it really get messed up? Nonetheless, in case someone flashes this then puts their phone in the microwave or something and tries to blame it on me, I am not directly responsible for anything that occurs, either negative or positive, from flashing this ROM to your phone. Despite that, I am posting in the spirit of the Android community, a community that I have embraced and belonged to for several years, and I would never try to hurt any of your innocent, beautiful phones. Also, none of the original source for Android belongs to me, nor do any of Google's apps. All preinstalled applications are property of Google, Inc. and I make no claim of ownership to them.
Okay that's about it! THE ROM DOWNLOAD LINK AND A SUMMARY OF ALL FILE DOWNLOADS CAN BE FOUND BELOW!
ROM Download & Changelog
ShinyROM_maguro_aosp_080914-130930-signed.zip
MD5: c13636212d98b7272a6c8155ce61ac0a
Fixes/Changes Included So Far
(older changes)
6/21/14 CHANGES
Updated to Android 4.4.4, KTU84P
8/9/14 CHANGES
Added system-side support for native screen casting
Added Italian translations for the Shiny restart menu (courtesy of XDA user lparcshinoda)
Mods
Before installing any of the packages below, please be sure to check out the mod installation instructions in the OP!
Key
To make mod installation more convenient, all mod links will now be color-coded based on the files they change. The key shows what each color corresponds with:
Red - SystemUI.apk
Blue - framework-res.apk
Purple - SystemUI.apk & framework-res.apk
Green - Other
If you install mods that are in the same color group, it is likely that they will overwrite each other. It is OK to overwrite a previously installed mod, but please note that the originally installed mod will no longer be there. If you want to completely revert to stock, flash the "Back to Stock ZIP" mod under the baldwinguy77 mod section. This mod replaces your SystemUI.apk and framework-res.apk files with ones from the stock ROM.
Developer-specific Mods
All of these mods have been provided by some really awesome mod developers who take the time to continue to make updated mods for my newest ROM builds. That being said, they have lives and can't always get the mods out right away, so make sure the date next to their name matches the build you're running! They usually are around the thread and are open to doing custom mods if you ask Be sure to thank them and check out the credits section for more info!
Baldwinguy77 (Updated for 8/9/14 build)
Back to Stock ZIP - Returns you to the stock version of the ROM by removing SystemUI and framework-res mods.
Stock kernel flashable ZIP - Overwrites any custom kernel you have installed with the stock kernel normally packaged with the ROM.
Inmanster (Updated for 3/9/14 build)
36 DPI Nav. Bar - Replaces the stock navigation bar with a smaller (height-wise), 36 DPI version.
Black Dash-style Softkeys - Replaces the stock navigation bar buttons with black, dash-style ones.
Blue Stock Softkeys - Replaces the stock navigation bar buttons with blue-colored ones.
Carrier Text Replacement - Replaces the carrier text on the lockscreen and pulldown notification shade with "Galaxy Nexus".
Extended Battery Framework Mods - Improve accuracy of battery level reporting for those using extended batteries.
2100 mAh (with Carrier Text Replacement mod)
3050 mAh
3800 mAh
5900 mAh (with No CRT-off Animation mod)
Grey Battery Percentage - Enables display of the current battery percentage in the status bar with grey-colored font.
InmanMod - A combination of the 2100 mAh battery, no CRT-off animation, carrier text, 36 DPI nav. bar, and white zenyth softkeys mods.
No CRT-off Animation - Removes the stock, default CRT-like screen off animation.
White Zenyth-style Softkeys - Replaces the stock navigation bar buttons with white, zenyth-style ones.
Universal Mods & Downloads
These mods have been compiled by myself, sometimes in conjunction with the modders above, to always work with any version of the ROM (but not necessarily any device). Therefore, you don't have to worry so much about these being up-to-date because they should always work. If that is ever not the case, simply PM me and we'll get it fixed This section also includes some other Verizon Galaxy Nexus related downloads such as the latest radios and bootloader. You can use these according to the installation instructions in the OP.
Universal Mods
AOSP Web Browser (for Android 4.4) - Installs the AOSP web browser with Chrome bookmark syncing for Android 4.4.
DSP Manager (for Android 4.4) - Installs the DSP Manager app along with the audio libs and configs important to running the service, allowing you to customize the audio equalizer of your device. At the moment, certain apps on Android 4.4 do not work with the modular DSP service.
ClockworkMod Images
Touch 6.0.4.7
Non-touch 6.0.4.7
ClockworkMod Recovery Flashable ZIPs
Touch 6.0.4.7
Non-touch 6.0.4.7
Chainfire's SuperSU Root Control App and ROOT Flashable ZIP (Works with 4.3 & 4.4)
Download (Latest version, v2.02)
Maguro Radios
Australia + Oceana - GT-i9250T
DVKK6
DVLE1
DVLF1
DVLH1
International (Europe) - GT-i9250
XXKK1
XXKK6
XXKL1
XXLA2
XXLF1
XXLH1
XXLJ1
International (South America) - GT-i9250
UIKL3
UILE1
UILH1
Japan + Pacific Asia - SC-04D
OMKKD
OMLA1
OMLE3
North America - GT-i9250M
UGKK7
UGKL1
UGLA4
UGLC1
UGLH1
UGLL1
South Korea + East Asia - M420
KRKK7
KRKL1
KRLB1
Tuna Bootloaders
PRIMEMD04 Bootloader Flashable ZIP (Latest)
PRIMELC03 Bootloader Flashable ZIP
Also just want to make it clear that to anyone who tested the 2/8 maguro build for me, the 2/9 one is the same!
The real deal.
Thanks.
Sent from my Galaxy Nexus using Tapatalk
No GApps "Add-on" Zip
Some people don't like the way ShinyROM includes its own GApps. Flash this zip directly after the ROM and it will strip out most of the included GApps so that you may use the preferred GApps of your choosing. This will leave the core GApps (Store, Services, etc.) as well as any others required for basic functionality (Keyboard, Camera, Launcher, Dialer, etc.) since there are none of the AOSP counterparts included.
This is particularly handy for GApps packages that try to measure the free space and may fail to install if it feels there isn't enough room.
Enjoy!
Finally! Boom!
Sent from my Galaxy Nexus using Tapatalk
osm0sis said:
I'll just copy this from the other thread.
No GApps "Add-on" Zip
Some people don't like the way ShinyROM includes its own GApps. Flash this zip directly after the ROM and it will strip out most of the included GApps so that you may use the preferred GApps of your choosing. This will leave the core GApps (Store, Services, etc.) as well any others required for basic functionality (Keyboard, Camera, Launcher, Dialer, etc.) since there are none of the AOSP counterparts included.
cwm-ShinyROM-No.GApps.Addon.zip:
View attachment 2559059
Click to expand...
Click to collapse
Thanks! I'll add this to the OP when I get a chance
baldwinguy77 said:
Thanks! I'll add this to the OP when I get a chance
Click to expand...
Click to collapse
No worries! I actually love having the GApps included, but a lot of people were fussing about it in Sesme's port thread so I thought I'd help out.
Also if you're interested, on xda here we've got a complete maguro radio thread and CWM thread I maintain:
[REF] [RADIO] [GSM] Galaxy Nexus GT-i9250 Baseband Collection & Discussion
[RECOVERY] [GN] [GSM] ClockworkMod Recovery Official + Nightlies [Flashable Zip]
:good:
Is this rom lagging for anyone? Right after I flash it I can't even pass the Setup Wizard ..
Just awesome man! The port was already the best ROM. Pure stock, and I can tell you, it's blazing fast!
osm0sis said:
No worries! I actually love having the GApps included, but a lot of people were fussing about it in Sesme's port thread so I thought I'd help out.
Also if you're interested, on xda here we've got a complete maguro radio thread and CWM thread I maintain:
[REF] [RADIO] [GSM] Galaxy Nexus GT-i9250 Baseband Collection & Discussion
[RECOVERY] [GN] [GSM] ClockworkMod Recovery Official + Nightlies [Flashable Zip]
:good:
Click to expand...
Click to collapse
Thank you! I actually downloaded all of these the other night and uploaded them to my server I just need to update the OP with a list
baldwinguy77 said:
Thank you! I actually downloaded all of these the other night and uploaded them to my server I just need to update the OP with a list
Click to expand...
Click to collapse
Haha cheers! I'll add you as a mirror.
BIG work!!!
Inviato dal mio Nexus 5
Great work man！
Official build both on toro and maguro now,could you make one for toroplus？
We need your awesome rom！
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Awesome! Exactly what we need.
Giving this ROM a go.
Nice to see its official now. But on post #1 there are some reference to rootzwiki as xda and I know its probably a copy+paste thing that's why. Just pointing it out
Sent from my Galaxy Nexus using Tapatalk
JustinXu said:
Great work man！
Official build both on toro and maguro now,could you make one for toroplus？
We need your awesome rom！
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey there! I'd love to push out builds for toroplus as well - I think it's safe to say that's next in the pipeline.
akash3656 said:
Nice to see its official now. But on post #1 there are some reference to rootzwiki as xda and I know its probably a copy+paste thing that's why. Just pointing it out
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Oops! I thought I got all of the necessary edits but I missed the one right at the beginning! *Facepalm* Thank you for pointing that out - it's fixed now
Are those battery Extended Battery Framework zips compatible with maguro? I downloaded them from toro's RootzWiki thread a while ago and they were giving me a bootloop
Also, can I use them with other ROMs?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
I've read that it's not possibile to flash ROM over a stock 4.3 rom.
Someone can confirm this? Also if I wipe /cache partition and Dalvik cache?
Investigating it seems that zip file contains an update script which only overwrites the entire /system mount point.
So, what are the consequences of updating ROM over a stock 4.3 rom?
osm0sis said:
I'll just copy this from the other thread.
No GApps "Add-on" Zip
Some people don't like the way ShinyROM includes its own GApps. Flash this zip directly after the ROM and it will strip out most of the included GApps so that you may use the preferred GApps of your choosing. This will leave the core GApps (Store, Services, etc.) as well any others required for basic functionality (Keyboard, Camera, Launcher, Dialer, etc.) since there are none of the AOSP counterparts included.
cwm-ShinyROM-No.GApps.Addon.zip:
View attachment 2559059
Click to expand...
Click to collapse
@osm0sis
If I simply add to "gapps list" in your zip the apps I do not want to be flashed, will it work?
Something like that:
Code:
/system/app/BasicDreams.apk
/system/app/BasicDreams.odex
/system/app/Books.apk
/system/app/CalendarGoogle.apk
/system/app/Chrome.apk
/system/app/CloudPrint2.apk
/system/app/Drive.apk
/system/app/EmailGoogle.apk
/system/app/EmailGoogle.odex
/system/app/Exchange2Google.apk
/system/app/Exchange2Google.odex
/system/app/FaceLock.apk
/system/app/GenieWidget.apk
/system/app/Gmail2.apk
/system/app/GoogleEars.apk
/system/app/GoogleEarth.apk
/system/app/GoogleTTS.apk
/system/app/Hangouts.apk
/system/app/HPPrintPlugin.apk
/system/app/Keep.apk
/system/app/LiveWallpapersPicker.apk
/system/app/LiveWallpapersPicker.odex
/system/app/Magazines.apk
/system/app/Maps.apk
/system/app/Music2.apk
/system/app/Nfc.apk
/system/app/Nfc.odex
/system/app/PlayGames.apk
/system/app/PlusOne.apk
/system/app/PrintSpooler.apk
/system/app/PrintSpooler.odex
/system/app/QuickOffice.apk
/system/app/Street.apk
/system/app/SunBeam.apk
/system/app/Videos.apk
/system/app/YouTube.apk
/system/priv-app/GoogleFeedback.apk
/system/priv-app/GooglePartnerSetup.apk
/system/priv-app/MusicFX.apk
/system/priv-app/MusicFX.odex
/system/priv-app/TagGoogle.apk
/system/priv-app/TagGoogle.odex
/system/priv-app/talkback.apk
/system/priv-app/Velvet.apk
/system/priv-app/Wallet.apk