Related
I'm pleased to present my MoDaCo Custom ROM for the HTC Vision (this is the version based on the Desire Z ROM, featuring HTC Sense)! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know.
Remember that if you use this ROM, you do so entirely at your own risk!!
About MoDaCo Custom ROMs
MoDaCo Custom ROMs are based on official ROMs - either shipping or leaked. A MCR release is designed to feel as far as possible like a stock ROM, with optimisations, tweaks and complimentary additions that enhance the user experience. The aim of a MCR is to be ultra reliable for use on an everyday device.
Requirements
In order to use this ROM on your device, you must have a custom recovery image installed (Clockwork Mod).
THIS ROM SHOULD RUN ON BOTH THE G2 AND THE DESIRE Z!
Features
Repack of the 1.72.405.3 ROM
Pre-rooted with su and Superuser Permissions by ChainsDD
Insecure boot image (ro.secure=0)
[*]Built, tweaked and massaged with the MCR build process which reduces the size and boosts the speed of the ROM
New busybox with Droid Explorer support
MCR version displayed in 'About' screen
terminfo and settings in boot.img to allow nano etc. use
Updated Google Components
Updated Facebook
Updated Flashlight which now becomes 'Torch' for non en-US configuration.
Added MCR Boot Animation (stock and N1 as options)
Added Development Tools option
Added Spare Parts option
Added Titanium Mobile option
Added WiFi Indicator Option
Added WaveSecure option
Slimmed Customize dir, additional locales added
De-odex'ed for the themers out there
Changelog
Please see 2 posts below this one for the changes in each release.
Installation
To install this ROM:
Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card
Restart your device in recovery mode
PERFORM A NANDROID BACKUP FROM THE MENU
Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM (unless you are coming from a non-'Sense' ROM), however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is now available in the online kitchen - see the post below for details! In addition to the kitchen, a prebaked download is available.
DOWNLOAD
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
Future Updates - READ THIS!
By providing this ROM I am not implying in any way that future updates will follow. Due to limits on my time and the fact that I have a large number of devices for short periods of time, it isn't possible for me to continue providing ROM updates indefinitely. Please do not donate / sign up on the assumption that future releases will be available (I don't want you to be disappointed!).
And finally...
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P
Changelog
r3 10/Feb
Reoptimised - smaller, faster!
Updated all outdated components
Fixed su issue
30/Dec r2
Based on 1.72 release
Updated all components (in turn compressed and optimised)
Added init.d support
Updated busybox
Added terminfo
15/Nov r1
Prebake updated to include 'Locations'.
12/Nov r1
Initial Release
A TON of stuff to put in, this is just about 'getting it up there'!
It's still pretty nice tho.
P
I guess Ill be the first to indulge...installing now, thanks for an easy flashable version of Desire Z sense, appreciate all the hard work in making my G2 the ****!
BTW - does the Desire Z OC kernel module floating around here work for this rom?
Came from Evil's ROM.
No wipe was required, kernel not overclocked, needs patience when flashing and firstboot, but overall seems to be working fine.
The location app, which didn't work correctly in the other Rom I tried, seems to be missing.
a) Where is said kitchen?
b) Can the kitchen include the 1.5GHz kernel and the "interactive" governor SetCPU?
quick question... would I be able to push lights.vision.ko to the appropriate location to get the trackpad to light up for notifications? i MUCH prefer that over the speaker light led
The locations option somehow got missed out of the kitchen!
I've updated it, and will update the prebake next time i'm properly online (visiting family for the weekend now!)
P
just flashed with BB and is working perfect so far @ 1.497 ghz
paulobrien said:
The locations option somehow got missed out of the kitchen!
I've updated it, and will update the prebake next time i'm properly online (visiting family for the weekend now!)
P
Click to expand...
Click to collapse
Have fun Paul! Don't let anything from twitter tempt you to start deving away from home lol.
Love the Rom man thnx ques it reboots with no signal like original g2 dp i gotta aply the ota again??
Sent from my HTC Vision using XDA App
Help... when I first loaded up this rom, the first thing i did was check to make sure the .com button worked... and it did.
Now that everything is done installing, my .com key no longer works, what happened?
Wi-Fi Hotspot
I really like the ROM so far, but I can't seem to get the Wi-Fi Hotspot working. I had success with the hotspot on the G2's version of stock android, but no luck with HTC Sense.
Has anyone been able to get this to work?
EDIT: Tried it again and it works fine. You just can't have the USB cable plugged into a computer and have WiFi Hotspot on. Might have something to do with the tethering.
I have used the FM radio successfully and have paired with a bluetooth headset. Everything seems to work great on this.
I downloade your Rom on setup I can't find English ( united states) option just a bunch of other countries is it not available other than that great Rom real smooth and also will Bacon bits kernel work on your Rom thanks in advance
Sent from my Desire HD using XDA App
sonicspeedway said:
I really like the ROM so far, but I can't seem to get the Wi-Fi Hotspot working. I had success with the hotspot on the G2's version of stock android, but no luck with HTC Sense.
Has anyone been able to get this to work?
Click to expand...
Click to collapse
Works fine on eVil's Sense. Does the FM work on this one?
I can't do Bluetooth device pairing. I can turn it on but can't pair it with bluetooth hands free device.
pls advice if someone else has this problem
Paired OK here?
P
thanks for the universal g2/z rom.
I hope all follow your good example and do the same.
And we can get rid of one of these forums either dz or g2.
Question do DZ owners just need a proper kernel to run a g2 ready rom?
Or can the just flash and go?
How do I install visionary its not letting me do it on astro
Sent from my T-Mobile G2 using XDA App
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 built a stock rom from AOSP for my toro. Everything works except spellcheck (figured out I need to include the dictionary file manually). I notice the rom appears to be deodex'd, is this a property of AOSP? I thought phones were odex'd by default.
Yes, deodexed is what you get by following all of the guides I've seen. I think there might be a command to build an odex rom, but I can't remember for sure.
Thanks, just wanted to make sure that's how it is supposed to be! Slowly getting the hang of all of this. Information for new developers seems to be scattered and requires a lot of hunting
Hi guys,
I want to make my own heavily optimized MIUI ROM, that will be sufficient to my requirements. My goal is to optimize ROM to highest speed and lowest RAM-consumption possible, that can be achieved on my Desire HD.
But I cant find any relevant and newest info, how current MIUI ROM works, and how they are build.
My plan is to somehow optimize released ROM for speed, and low memory requirements (ROM is from MIUIandroid.com) and add there some things, like language pack, and gapps.
Is there some guide about MIUI ROM, that has complete description of directories and files in MIUI ROM ZIP file? I have found nothing on google, MIUI forum or XDA. Just some scattered info, that was months or years old and thus outdated.
I was looking for some complete guide, or things like:
- how and where I must placed gapps files in ROM, so they be available right after flashing ROM, and the user not have to flash it separately?
- what files is required to core functions of MIUI ROM
- what apps in system/app can be deleted without compromise other functions of ROM, and is there some description of each apk file in system/app directory?
- is there a way to specificate what apps will be alwais running in the background, and OS will not close them? (I dont want to wait 10s to start facebook or browser, because System close them after some time of not being used)
...and many more questions like this, about various functions of MIUI ROM.
Where I can find this info, and from where have people knowledge about building custom MIUI ROM, or tweaking/optimizing it? There must be somewhere a complete information about how it works, because obtaining information from google, etc. is highly ineffective....
Hello All,
This may be in the wrong place so if it is, I am sorry, anyway to my question I'm trying to build CM for my S4 Mini LTE Serranoltexx everything was going fine until I got this message after running extract-files.sh
Code:
Extracting /system/lib/egl/libGLESv2S3D_adreno200.so ...
remote object '/system/lib/egl/libGLESv2S3D_adreno200.so' does not exist
Now after adding "libGLESv2S3D_adreno200.so" (if you search Google for it it's the top github link) I managed to get it to build the actual .zip and it does flash properly but it doesn't seem to have the correct graphics drivers (I thought this process wouldn't work and I was right), the guide on the how to build it doesn't help with this problem either so any help would be extremely appreciated
I've attached the logcat for reference (if it's needed) as a .docx file as the .txt file was 1.1mb and because I don't have a pro account on pastebin.
The problem with newer Android versions is that if often require new libraries which are not available in stock rom, so the extract method is actually not very useful unless we have a stock rom of the same version we are building for. To bypass this issue we use libraries from other phones that have the matching Android version. I suggest using the blobs that's on TheMuppets github, as those are up to date.
https://github.com/TheMuppets/proprietary_vendor_samsung