{
"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"
}
an AROMA based Touch UI Recovery Installer
As seen on Valhalla Black Edition and Team Acid AOKP
Please tell me if you're going to use this in your ROMs just so I know who is using it . Thank you.
This is for ROM chefs only, not for regular users. Regular users, you will see this in all your ROMs soon .
All the instructions below refer to the files in META-INF/com/google/android
You can change the splash image by replacing aroma/splash.png (make sure it's a PNG though)
As mentioned in the installation instructions, make sure your ROM's zip file matches that of Valhalla Black Final's for best results.
Full touch screen support
Allows for a typical install, using default settings
Allows the user to customize the ROM installation
Allows the chef to customize the user experience
Support for different themes/skins
Installs Busybox
Installs kernel if you desire
Installs modem if you desire
No need to check mounts, the installer properly mounts the partitions for you.
No need to format partitions, the installer can wipe them for you.
Download and extract the installer zip file
Edit aroma/installer.default.prop to set your ROM's information
Rename installer.default.prop to installer.prop
Edit aroma-config and updater-script to your liking
Extract your current ROM's zip
Delete your ROM's META-INF folder
Put the new SGS4G CWM Rom Installer's META-INF and tools folders in your ROM's root
Make sure your ROM's file structure matches that of AOKP Unofficial by TeamAcid, unless you know what you're doing
Create a new zip file
Flash away and test!
If you use this tool you have to link back to this thread and give me credit using the link. Example:
My ROM uses the SGS4G ROM Installer by FBis251
http://forum.xda-developers.com/showthread.php?t=1481228
installer.zip
Installer on GitHub
You can download installer.zip from the link above to get the latest version of the installer files to package into your own rom.
Octoboer 13, 2012
Remove touchscreen calibration fix /data extract bug
-- With aroma 2.55+ touchscreen calibration is no longer necessary
-- /data packages should get extracted properly after a /data restore
Updated to latest AROMA binary (2.56)
-- Much more stable binary in ICS recovery!
---- The newest binary hasn't crashed on me yet during testing unlike the older version (2.50) that was included in the last version of the SGS4G Installer.
Here is the AROMA changelog since the last version included in the SGS4G Installer
EDELWEIS - 2.56 - BUILD 121004-031
Fix capacitive button
Remove calibration tools
EDELWEIS - 2.55 - BUILD 121003-030
Completely new Input/Touchscreen Handler - Thanks to agrabren from TWRP
Remove all calibration need. calibtool(), calibrate() and calibrate_matrix() won't do anything now.
EDELWEIS - 2.51 - BUILD 120810-026
Supported Galaxy Nexus Touch Screen - And maybe other devices now supported
Click to expand...
Click to collapse
July 18, 2012
ICS public release
May 25, 2012
Fixed bug that wouldn't mount partitions
-- Added support for mounting /efs
Added /efs partition info to installer.default.prop
Fixed a bug that would cause redbend_ua to restart the phone while flashing
-- (Thanks to itzik2sh from xda-developers for the fix)
Updated efs-backup
Now only checks whether /efs is empty
-- Will be compatible with devices that don't use an nv_data.bin
May 23, 2012
Updated scripts for easier porting
-- aroma-config and updater-script now uses information from installer.prop
-- porting to new devices will now be a lot easier because of this
Updated efs-backup script
--Backups now only take up ~560kB of space, compared to 6.3mB before!
Added colors to the installation confirmation screen
May 2, 2012
Changed to using installer.prop file for controlling all the variables
-- Chefs no longer need to edit the main AROMA script
-- AROMA checks if the installer.prop file exists to prevent users who flash the zip from messing up their phones
Added an installation option confirmation screen to make sure users know what options were selected
April 15, 2012
Updated to aroma-2.00-120414-A7
Now checking for phone version using a kernel check. Should prevent Froyo users from installing a GB ROM
Fixed a bug that would always do a free space check even when the user didn't try to do a /data backup
Now doing a /data restore before the kernel flash. Some ROMs caused the phone to reboot once the kernel flashed which means the /data restore never happened.
March 11, 2012
Updated AROMA binary to 2.0a4
Changed busybox version back to busybox v1.19.0.git
Now using aroma's TrueType font support
-- Installer uses the rom's default font (DroidSans)
Updated ROM information screen
Reboot prompt moved to the end of the installation
Updated Agreement to add formatting
Added efs-backup script which makes a backup of the efs partition
-- Saved under /sdcard/aroma-backup
Now has UTF-8 and RTL support!
March 3, 2012
Forced installation of busybox
Updated busybox to bonsai's version v1.17.1 (2010-08-12 23:44:34 CDT)
Fixed a bug that wouldn't allow the data backup and restore scripts to run
Moved mke2fs.conf to tools directory
Updated the sdcard free space check for /data backup
-- Will now only warn users when they selected the backup option in customized installs
March 3, 2012
Cleaned up a lot of the aroma-config code for easier reading
Deleted duplicate busybox binary
Deleted changelog.txt since no one used it
Added .gitignore
Updated busybox binary to version 1.19.4
Added monospace font
Now using the latest aroma nightly Version 1.62 build 120303-030
Using the latest themes from the nightly
Added a check to disallow /data backup when there isn't enough free sdcard space
-- Added a warning for the user to know the backup isn't going to happen
Updated touchscreen calibration values
Now displays filesystem and ROM information on the same screen
-- Added sdcard filesystem information
Reboot no longer done in the updater-script
Changed symlinks in updater-script to use busybox for more functions
Feb 12, 2012
Added aroma theme support. Check aroma/themes/
Added three themes, sense, MIUI and ICS (default ICS)
Added MIUI icons
Added filesystem (disk free/total and percentage used) information viewbox
Added ext4 format from bonsai's installer script.
-- Now does a full ext4 format and tuning before the install
Now allows choice of splash animation instead of static splash screen
Removed a lot of whitespace from aroma-config
Removed options to do wipes since the format takes care of this
Added data backup option
Now using bonsai backup. Left compression enabled for minimal sd storage usage.
Backup may take up to 10 minutes to complete!
Removed color.prop (no longer needed due to themes)
Changed checking for SGH-T959V to allow you to continue in case there is no ROM installed.
Feb 5, 2012
Edited updater script to output all installer options to one prop file
Now using variables in aroma-config for easier writing of the final options.prop file
Cleaned up updater-script to only use one .prop file
Fixed a bug that would make the wipe /data dialog come up even when deselected in the customized install
The script will now ask the user if they want to reboot their phones in all instances before the install gets going.
Now using Roboto font
Added color.prop file to control theme colors
Updated the wording on the install type chooser
Click to expand...
Click to collapse
FB
I was just gonna thank you for this over on Black thread. Glad you got this out for folks. Slick very slick. Who needs ROM manager(mangler) when you're around. So thanks to you and everyone else who worked on it.
I just used this a few hours ago I installed the black final rom with touch screen features is cool!
Sent from my SGH-T959V using XDA Premium App
FB, I will be using it for the next edition of AOSP Style coming out soon. I have already built mos of the rom and its installer, but I needed verification.
airfluip1 said:
FB, I will be using it for the next edition of AOSP Style coming out soon. I have already built mos of the rom and its installer, but I needed verification.
Click to expand...
Click to collapse
Sounds good. Just follow the OP if you'd like. I'm sure you already looked through the scripts. You should theme the installer to make it look like your ROM .
airflip if u are using my rom as a base its already in there .... which u asked me to use so.....
FB, I just flashed Raver's final and everything flashed fine then when the installer was done it showed an error having to do with not finding a path for something. I was going to re do it and copy the error down but now the phone is stuck at the T-Mo screen and it won't go into recovery with the button combo. I'm going to Odin it in the morning and re-flash and see if it throws the error again and I'll let you know.
bswann said:
FB, I just flashed Raver's final and everything flashed fine then when the installer was done it showed an error having to do with not finding a path for something. I was going to re do it and copy the error down but now the phone is stuck at the T-Mo screen and it won't go into recovery with the button combo. I'm going to Odin it in the morning and re-flash and see if it throws the error again and I'll let you know.
Click to expand...
Click to collapse
Same error on my sgs4g I think it was a temp file error, didn't affect my rom booting though.
Sent from my Glacier using xda premium
bswann said:
FB, I just flashed Raver's final and everything flashed fine then when the installer was done it showed an error having to do with not finding a path for something. I was going to re do it and copy the error down but now the phone is stuck at the T-Mo screen and it won't go into recovery with the button combo. I'm going to Odin it in the morning and re-flash and see if it throws the error again and I'll let you know.
Click to expand...
Click to collapse
If it happens again, hit save log and send that to me. I'd really like to see it.
Gr8 job FB - thank you very much.
We'll probably also use it in our next version
10x
Thanks Guys!!!(Raver,FB)
FBis251 said:
If it happens again, hit save log and send that to me. I'd really like to see it.
Click to expand...
Click to collapse
FB, awesome work man. Lovin it. I had an error on my install but the ROM installed fine and booted fine. I made a log anyway so I could send it to you. Maybe it can be of some use.
alon2 said:
Gr8 job FB - thank you very much.
We'll probably also use it in our next version
10x
Click to expand...
Click to collapse
Awesome, don't forget to post here if you have any usage questions. I wound up taking out a lot of the comments for space, but I learned the syntax of the AROMA functions pretty well.
putsometrebleinit said:
FB, awesome work man. Lovin it. I had an error on my install but the ROM installed fine and booted fine. I made a log anyway so I could send it to you. Maybe it can be of some use.
Click to expand...
Click to collapse
Yes I'd love to see that.
airfluip1 said:
Thanks Guys!!!(Raver,FB)
Click to expand...
Click to collapse
No problem. I'm guessing it's working fine?
Cool very very neat. Never seen this on a phone before
Sent from my SGH-T959V using xda premium
FBis251 said:
Awesome, don't forget to post here if you have any usage questions. I wound up taking out a lot of the comments for space, but I learned the syntax of the AROMA functions pretty well.
Yes I'd love to see that.
No problem. I'm guessing it's working fine?
Click to expand...
Click to collapse
You are right. I am making this installer so customizable, from kernel to bootanimation.
airfluip1 said:
You are right. I am making this installer so customizable, from kernel to bootanimation.
Click to expand...
Click to collapse
I'm gonna release an update soon. You should look into it once I'm done since I simplified the updater-script portion of it.
What do you mean by "soon" because i may release 4.0 tomorrow. I just need to test my new features.
I'm doing final testing of the installer so in about an hour.
Feb 5, 2012
Edited updater script to output all installer options to one prop file
Now using variables in aroma-config for easier writing of the final options.prop file
Cleaned up updater-script to only use one .prop file
Fixed a bug that would make the wipe /data dialog come up even when deselected in the customized install
The script will now ask the user if they want to reboot their phones in all instances before the install gets going.
Now using Roboto font
Added color.prop file to control theme colors
Updated the wording on the install type chooser
Panicking right now because I can't seem to PM you FB.
I hope I don't come off as a stickler for details, but there's just a single typo in what is the 6th screenshot posted in the OP. It's for the option where you can choose to Wipe Data.
"...another ROM. Don't select if you want to keep your ap"
I'm assuming it was supposed to say "apps."
Just wanted to make note of it as I saw that Raver updated the contents in the aroma folder within the META-INF directory for his Valhalla Black rom. I was just thinking the typo might've been updated or something somehow.
Related
Welcome to my OTPA roms!
Version 1.2.x -> Base build is 1.79.482.3 146733
Version 1.4.x -> Base build is 2.73.405.38
Version 1.5.x -> Base build is a mix of 2.73.405.38 and Sense UI 4 Magic
Version 2.0.x -> Base build is a mix of 2.73.405.38, Sense UI 4 Magic, updated kernel, and etc
Version 3.0.x -> Base build is a mix of 2.73.405.38/3.03.990.6, Sense UI 4 Magic, updated kernel, and etc
Credit/Thanks goes to MLIGN, JAC, CC, Paul @ MoDaCo, Drizzy, QTek, Cyanogen, Haykuro, Twistedumbrella, DWang, bouyark, jabbawalkee, sardoid, others, and of course XDA itself.
The Beta Testers
bouyark
sardoid
jabbawalkee
djlman
Donators:
Bouyark
DJlman
PDL
WebghostDK
tfoteh
Requirements:
Format your sdcard with the following specs.
Fat32
ext2/3
linux-swap - At least 96mb
How to setup sdcards
How To Partition SD Card With Ubuntu
From the recovery mod
Manual partition of sdcard w/parted,goto ext3/4 from adb. no liveCD req'd
==================================
Then use the following command or your own.
Run the following command in the adb shell
# Backup your apps using the following commands.
mkdir /sdcard/backup
mkdir /sdcard/backup/app
mkdir /sdcard/backup/app-private
cp -R /system/sd/app/*.* /sdcard/backup/app
cp -R /system/sd/app-private/*.* /sdcard/backup/app-private
# Remove app_s files from system before starting the flashing process.
rm -r /system/sd/app_s/*.*
reboot recovery
Then a WIPE is required...!
These steps need to be performed before flashing this rom.
My otpi will do the same one you've already flashed this rom.
Disclaimer:
This rom is for "HTC Magic/MyTouch 3G/32B devices only.
Please make sure to make a nandroid backup before flashing this rom.
I am not responsible for bricked devices, dead sdcards, and etc.
Please do some research before trying to flash this rom.
Mods:
Added: Bluetooth fix
Moved to app: BizCardReader
Moved to app: HTC_IME
Moved to app: Maps
Moved to app: Quickoffice 1.0.1
Moved to app: teeter
Settings:
Default with Linux Swap set at 60 swappiness
If for some reason it does not set swappiness to 60, then please use swapper to adjust as needed.
Tips:
Create a folder called backup on your sdcard before flashing this rom.
Then another folder called app within the backup folder.
Copy your currenlty used apps into the app folder.
Once your done flashing this rom, connect your device and within adb shell, type otpr.
This will copy all files within your sdcard/backup/app onto /system/sd/app
Tools:
The following tools will be added to this rom, simply connect your system via adb shell and type names below.
otpi
This simple add-on script will backup your app to sdcard/backup/app, then remove all existing files from app_s and app.
Once completed it will reboot your device into recovery mode so that you can flash another rom.
otpm
This simple add-on script will simply mount your sd card with read + write options.
otpr
This simple add-on script will restore your save files from sd/backup/app to your /system/sd/app folder.
=======================================================================
Still working on fixing the following:
1. FC when searching contacts
2. Full Bluetooth support
============================
Version 1.5
OTPA.v.1.5.5 - Updates
This update will fix the miss call issues when present.
It also includes Java and a few addional apps.
It also fixes the sound issue.
There are two versions one with A2sd as with the current rom and one without A2sd.
Do not perform a wipe when using Updates.
If the swappiness drops from 60 to 10 after a reboot, please download swapper and adjust as needed. I will include swapper in the next update.
==========================================
OTPA.v.2.0 - Sense UI 4 Magic
{
"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"
}
Contents:
Bluetooth muisc still works
Faster
More Stable
Black Dialer -> Thanks to twisted for his help
Transparent Lockscreen -> Got bored waiting for a new phone...lol
Replaced kernel with drizzy's -> with some minor edits to the boot.img by me
Removed all warez
Hard coded swappiness to 60 -> Yes, it will stay at 60 after reboots. Do no use swapper on this version...!
Set cpu to 38400 instead of max to help reduce battery drain.
And other things I forgot about.
Wifi Fix - OTPA.v.2.0 - Magic Users Only and Not MyTouch
Do not perform a wipe when using Updates.
====================================
Version 3.0
New Rosie look
Black out theme
Back with old screen lock since people did not like the clear look..lol
Update apks and framework
Two different versions
One with BT Music (Music streaming only not full BT)
One without BT Music (Much smoother since it has the newer core, people search works...lol)
and etc
All roms moved to 4shared folder.
====================================
App Pack v.1.1
Roms Folder - 4shared
========================================
Enjoy,
Suggestions.
If I may:
- Add Plurk, including the widget.
- Render the notification tray transparent.
- Implement EXT4 support.
- Be sure that the Compcache modules are correct.
- Linux-swap supported AND/OR back_swap supported.
- Add Stocks, including the widget. (It's not that much of a resource hog.)
- Add Spare Parts.
- Keep all standard wallpapers to avoid gallery selection force closes.
- Keep all media to avoid "Ringdroid" or "Rings Extended" force closes.
- Keep the standard lock screen w/ throttle bar. (It's gorgeous.)
- Be sure that the latest kernel is the BFS-222 kernel. (Cyanogen's latest is.)
- (Opt.) Twisted's "black dialer."
- (Opt.) 2.73 based-build number. (Modaco's latest WWE dump.)
If you can make that happen before your release...or keeps your initial release HELD OFF...that's fine, trust me ---> it'll be worth it!
The community would be going nuts if you can make some of that happen!
Seriously, if you make at least half of that happen, I'll flash this ROM to both of my devices, and promote the hell outta' this.
Thanks.
EDIT: The reason for the Modaco dump suggestion is because he has the only build that DOES NOT force close while using the People Search function in the contacts. That's a big deal. IMO.
haha am i following you or the other way around. i Used your rom on my Wing, so i will be sure to check this one out.
TTran!!! Dude!! Your on sapph and dream roms now. You are my hero from herald forum!! I cant wait to see what happens with you toying with android!! Now lets go get Ivan lol!!
Be waiting for your upload
Ttran...
Great you here on andriod LOL. I used your rom for HTC Wing LOL..and i still have it..(too bad you retired from it) look foward in your work...
downloading now. About to install. Will report back shortly
vtecbros said:
downloading now. About to install. Will report back shortly
Click to expand...
Click to collapse
Thank you for the response,
Please remember that this is a full version so it might run a bit slower.
I'm running a strip down version of this rom and its working great so far.
E:Failure at line 3:
copy_dir PACKAGE:system System:
Installation aborted.
Tried twice...and still have this message??
x1tyme said:
E:Failure at line 3:
copy_dir PACKAGE:system System:
Installation aborted.
Tried twice...and still have this message??
Click to expand...
Click to collapse
That's strange, I've test it before uploading, the file must have gotten corrupted or something.
I'm going to download it and try again.
File is not available from megaupload...
nevermind, i guess you're uploading it again
Bro this thing is very fast. And as what you said its a full verison so it might be a bit slow. But i dont think its slow at all. I have a class 2 4gb. Its still fast! Getting my class 6 in 3 days
I did notice one thing, with JACHEROski builds the prediction on QWERTY mode prediction dont work. But that is not a problem to me i can just use better keyboard while this whole thing gets figured out why it wont work on texting mode only.
But hey other than that this ROM is go for.
Thanks.
x1tyme said:
E:Failure at line 3:
copy_dir PACKAGE:system System:
Installation aborted.
Tried twice...and still have this message??
Click to expand...
Click to collapse
I just flahed it again did not have any problem, but I've already started uploading it again so, please hang in there.
schtuka said:
File is not available from megaupload...
nevermind, i guess you're uploading it again
Click to expand...
Click to collapse
The upload has been completed.
Thank you for taking the time to try my rom out.
vtecbros said:
Bro this thing is very fast. And as what you said its a full verison so it might be a bit slow. But i dont think its slow at all. I have a class 2 4gb. Its still fast! Getting my class 6 in 3 days
I did notice one thing, with JACHEROski builds the prediction on QWERTY mode prediction dont work. But that is not a problem to me i can just use better keyboard while this whole thing gets figured out why it wont work on texting mode only.
But hey other than that this ROM is go for.
Thanks.
Click to expand...
Click to collapse
Thank you for your feedback.
Hey ttran001,
I seen that you had to re-upload the file.
The one you just re-upload were there any chance to it? There is 3mb less then the first one you uploaded?
vtecbros said:
Hey ttran001,
I seen that you had to re-upload the file.
The one you just re-upload were there any chance to it? There is 3mb less then the first one you uploaded?
Click to expand...
Click to collapse
Man, I'm starting to hate megaupload.
It should be the same file.
As for changes, I'm going to wait until tomorrow after folks have had time to download it and provide their feedback.
I personally like the other build I have of JaCs, but it looks as if people want MoDaCo rom.
ttran001 said:
Man, I'm starting to hate megaupload.
It should be the same file.
As for changes, I'm going to wait until tomorrow after folks have had time to download it and provide their feedback.
I personally like the other build I have of JaCs, but it looks as if people want MoDaCo rom.
Click to expand...
Click to collapse
Well The MoDaCo is running smooth right now. But maybe you can make a build with JaCs and then just upload for testing.
idk?
ttran001 said:
I just flahed it again did not have any problem, but I've already started uploading it again so, please hang in there.
Click to expand...
Click to collapse
I tried to dl it..(even switch memory card) still have the same message???
ttran001 when will you be releasing the Lite verison?
later today?
In a nutshell, this program is designed to allow the MIUI rom to be built more easily. Since there are updates quite often and the process of updating the rom can be tedious for the developers, I decided to help out where I could and create this application.
Instructions
Download a rom of a similar phone from the http://roms.miui.us/ website. The Fascinate should be a good one, and the Nexus S and Nexus S 4g might also work.
Launch the MIUI Builder
In the "MIUI Source Zip File" section, browse to the freshly downloaded rom
Put in a build version (usually the version of MIUI being built)
In the "Build User" put in some name (could use your xda name)
In the "MIUI Destination Zip File" browse to where you would like the CWM flashable rom to be saved
Optionally, you can choose a kernel to use, if you don't want to use the default kernel
NotesNote1: More kernels can be manually added to the kernels directory (Default C:/Program Files/MIUI Builder/kernels/). You just need to make sure they are CM7 compatible kernels. Also, the base is the miui_port_ns.zip, so you can swap files out in there if you want, but that zip will probably get wiped every time you update this application. (This is currently removed, but I plan to add it back in shortly)
Note 2: Fascinate builds currently boot and have data. NS4g builds are still causing issues. Also, before you flash anything that this creates, please do a CWM backup.
Prerequisites
Windows PC
.net 3.5 or greater
Java Development Kit (JDK)
Change LogVersion 1.0.0 - Initial Release
Basic Functionality
Version 1.0.1
Added splash screen
Fixed permissions issue on windows 7 PCs
Version 1.0.2 - Initial Public Release - 11/25/2011
Added ability to choose a different kernel
Version 1.0.3 - 11/25/2011
Fixed build.prop issue when using the nubernel kernel
Provided a cleaner and more informative error message when there is an issue unzipping (seems to only occur with things zipped on *nix)
Version 1.0.4 - 11/27/2011
Fixed issue with /system/lib/ which was pointed out by xboxfanj
Rom built with default kernel has been tested and proven to boot when using the latest (1.11.25) fascinate build
Version 1.0.5 - 12/3/2011
Fixed issue that would not allow you to use a different kernel than stock
Fixed some attributes in the build.prop - might make some things work a little better, but I dunno what those will be
Made the build version field shorter
Fixed issue with the NFC stuff not being removed
Added optional CM7 kernel from the 11/24 build
Fixed issue when building from Nexus S or Nexus S 4G
Fixed issue with writing over an already existing zip file
Fixed issue with part of the build.prop dissapearing
Version 1.0.6 - 12/9/2011
Fixed build.prop issues (mainly issues with certain kernels)
Fixed carrier name issues
Fixed issue with framework.jar and data not working
Version 1.0.7 - 12/22/2011
Updated GoSMS
MMS fix as long as you use GoSMS
Application will remember the build user name and file system chosen
Ability to choose if you want a startup sound as well as the mp3 file itself
MTD support with ability to choose EXT4 or MTD.
Removed ability to choose a kernel for now, but it might be added back in later
Version 1.0.8 - 12/22/2011
Should now have working 911 (I'm not 100% on this though)
Replaced latest CM7 kernel, which wasn't working, with the Beta 6 MIUI kernel
Version 1.1.0 - 4/7/2012 (Dropbox Mirror)
Updating to MIUI V4
Verified SMS and MMS work when built from a Fascinate Rom
Version 1.1.1 - 4/8/2012 (Dropbox Mirror)
Fixed annoying blank message boxes with just an OK button
Version 1.1.2 - WIP
Add advanced reboot menu
Add phantom VM fix
Any suggestions would be appreciated.
If you managed to come across a bug, which at this point wouldn't surprise me, let me know and I will try to fix it as soon as possible.
Oh and of course, the usual jargon that I am not responsible if you somehow managed to mess up your phone or for that matter your computer. This software has been tested on windows 7 and windows 8 and hasn't caused any issues after instillation.
Future Hopes and Dreams: (may never get accomplished but would be nice)
Multi-thread C# application
Create a java version, so that the program will be cross platform compatible
Thanks
bxfxf - Got the initial instructions from him
xboxfanj - For testing it some and helping keep MIUI on the epic4g alive. Also, providing instructions for MTD.
Nubecoder - For nubernel kernel
ugothakd for providing the default EXT4 kernel
Marcusant for getting MIUI V4 to its current awesomness
CM7 Team for CM7 Kernel
Everyone else who makes this community what it is, including but not limited to ACS, Bonzai and CM7 teams.
Found a bug. Here's the screenshot:
{
"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"
}
Death259 said:
MIUI Builder (Windows Only Application)
In a nutshell, this program is designed to allow the MIUI rom to be built more easily. Since there are updates quite often and the process of updating the rom can be tedious for the developers, I decided to help out where I could and create this application.
Instructions:
Download a rom of a similar phone from the http://roms.miui.us/ website. The Fascinate should be a good one, and the Nexus S and Nexus S 4g might also work.
Launch the MIUI Builder
In the "MIUI Source Zip File" section, browse to the freshly downloaded rom
Put in a build version (usually the version of MIUI being built)
In the "Build User" put in some name (could use your xda name)
In the "MIUI Destination Zip File" browse to where you would like the CWM flashable rom to be saved
Optionally, you can choose a kernel to use, if you don't want to use the default kernel
Note: More kernels can be manually added to the kernels directory (Default C:/Program Files/MIUI Builder/kernels/). You just need to make sure they are CM7 compatible kernels. Also, the base is the miui_port_ns.zip, so you can swap files out in there if you want, but that zip will probably get wiped every time you update this application.
Note 2: I tested one rom that was built with the default kernel, and it flashed just fine, but it wouldn't boot. This could potentially be solved by flashing the RFS to EXT4 or EXT4 to RFS zips. With that in mind, before you flash anything that this creates, please do a CWM backup.
Prerequisites:
Windows PC
.net 3.5 or greater
Java Development Kit (JDK)
Change Log
Version 1.0.0 - Initial Release
Basic Functionality
Version 1.0.1
Added splash screen
Fixed permissions issue on windows 7 PCs
Version 1.0.2 - Initial Public Release - 11/25/2011
Added ability to choose a different kernel
Any suggestions would be appreciated.
If you managed to come across a bug, which at this point wouldn't surprise me, let me know and I will try to fix it as soon as possible.
Oh and of course, the usual jargon that I am not responsible if you somehow managed to mess up your phone or for that matter your computer. This software has been tested on windows 7 and windows 8 and hasn't caused any issues after instillation.
Thanks:
bxfxf - Got the initial instructions from him
xboxfanj - For testing it some and helping keep MIUI on the epic4g alive
Nubecoder - For nubernel kernel which is currently the only included optional kernel (p.s. If you want me to remove your kernel I can)
Everyone else who makes this community what it is, including but not limited to ACS, Bonzai and CM7 teams.
Click to expand...
Click to collapse
Please give credit to ugothakd too. His kernel is the default one.
Sent from my SPH-D700 using Tapatalk
xBTx said:
Found a bug. Here's the screenshot:
Click to expand...
Click to collapse
same thing wit me
ns4g build didn't give any errors.. but the fascinate did.
xBTx said:
Found a bug. Here's the screenshot:
Click to expand...
Click to collapse
Ahh... that issue, have a nicer solution in the next version. For now, extract the zip manually, and then rezip it with the built in windowszipping functionality to rezip it.
xboxfanj said:
Please give credit to ugothakd too. His kernel is the default one.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Whoops! Problem solved!
Death259 said:
MIUI Builder (Windows Only Application)
In a nutshell, this program is designed to allow the MIUI rom to be built more easily. Since there are updates quite often and the process of updating the rom can be tedious for the developers, I decided to help out where I could and create this application.
Instructions:
Download a rom of a similar phone from the http://roms.miui.us/ website. The Fascinate should be a good one, and the Nexus S and Nexus S 4g might also work.
Launch the MIUI Builder
In the "MIUI Source Zip File" section, browse to the freshly downloaded rom
Put in a build version (usually the version of MIUI being built)
In the "Build User" put in some name (could use your xda name)
In the "MIUI Destination Zip File" browse to where you would like the CWM flashable rom to be saved
Optionally, you can choose a kernel to use, if you don't want to use the default kernel
Note: More kernels can be manually added to the kernels directory (Default C:/Program Files/MIUI Builder/kernels/). You just need to make sure they are CM7 compatible kernels. Also, the base is the miui_port_ns.zip, so you can swap files out in there if you want, but that zip will probably get wiped every time you update this application.
Note 2: I tested one rom that was built with the default kernel, and it flashed just fine, but it wouldn't boot. This could potentially be solved by flashing the RFS to EXT4 or EXT4 to RFS zips. With that in mind, before you flash anything that this creates, please do a CWM backup.
Prerequisites:
Windows PC
.net 3.5 or greater
Java Development Kit (JDK)
Change Log
Version 1.0.0 - Initial Release
Basic Functionality
Version 1.0.1
Added splash screen
Fixed permissions issue on windows 7 PCs
Version 1.0.2 - Initial Public Release - 11/25/2011
Added ability to choose a different kernel
Any suggestions would be appreciated.
If you managed to come across a bug, which at this point wouldn't surprise me, let me know and I will try to fix it as soon as possible.
Oh and of course, the usual jargon that I am not responsible if you somehow managed to mess up your phone or for that matter your computer. This software has been tested on windows 7 and windows 8 and hasn't caused any issues after instillation.
Thanks:
bxfxf - Got the initial instructions from him
xboxfanj - For testing it some and helping keep MIUI on the epic4g alive
Nubecoder - For nubernel kernel which is currently the only included optional kernel (p.s. If you want me to remove your kernel I can)
ugothakd for providing the default kernel
Everyone else who makes this community what it is, including but not limited to ACS, Bonzai and CM7 teams.
Click to expand...
Click to collapse
This is pretty damn cool
sent from my, ya know cm7 epic
Uploade version 1.0.3, all changes are listed in the OP.
Jesus, stop quoting the entire op...
Awesome job.
Sent from my SPH-D700 using Tapatalk
marcusant said:
Jesus, stop quoting the entire op...
Awesome job.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Jesus can do whatever He wants,it's almost His birthday.
Seriously, though thanks from all of us non-dev miui lovers. Can't wait to see the results.
I'll stay off now and leave this thread for you developers.
Sent from my SPH-D700 using xda premium
Bug:
Applying fix for cdma data in framework.jar, this shows.
The system cannot find the file specified.
This happens on both the fascinate and the crespo4g files.
btw, for your sig, that says "I'm pretty sure that MIUI is pronounced meeooee and not M.I.U.I," it's actually my-you-eye or me-you-eye.
iwasaperson said:
Bug:
Applying fix for cdma data in framework.jar, this shows.
The system cannot find the file specified.
This happens on both the fascinate and the crespo4g files.
Click to expand...
Click to collapse
What OS are you on? If you are on windows 7 or 8 then you might try running as administrator.
im on windows 7 x64, and i AM administrator (thats the only active account on the computer).
iwasaperson said:
im on windows 7 x64, and i AM administrator (thats the only active account on the computer).
Click to expand...
Click to collapse
Aight, you might be administrator, but due to how permissions are done in windows 7 you might still have to run as administrator. So, try right clicking on the shortcut and selecting run as administrator.
curious
so my builds built perfectly, i tried optional kernel, and stock, i also tried rts and ext4 settings, and my builds wont boot!
they flash just fine, no errors on zipping, but for some silly reason they are stuck on the flash screen?
im an avid flasher, i flash roms daily, and im stumped.
and for all you trollers out there yes i wiped, data, wiped cache, and dalvik.
otherwise the process was flawless, you think its because of the recent 11.25 build?
i havent yet tried to build a 11.17 build.
your thoughts death? thanks again for all the heard work
Running as Administrator didn't help at all. I tried the GSM crespo, the CDMA crespo, and the fascinatemtd build, all 1.11.25.
THIS ROM IS OBSOLETE. PLEASE SEE THE NEW VERSION.
{
"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"
}
(MTD)
IMPORTANT: Please read this thread about MTD if you don't know what it is or means.
For those of us who just want our phones to $%#^@! work.
This is a clean EI22 based ROM with a custom Black theme. While much of the preloaded Sprint bloatware is removed, useful stock software like ThinkFree Office, MyFiles, Memo, Clock, and calculator are left in. Stability is the number one priority in this ROM. Those who are into bleeding edge/ricer ROMs will probably find this ROM boring.
Feature List:
Based on the original leaked EI22 NANDroid dump (noobnl)
Deodexed
Custom EI22 kernel with the following features:
init.d script support
keyboard fixes
overclocking to 1.4Ghz
Voltage control
WIFI stability fixes
CWM5 Support
bootanimation.zip support (None included by default. Place one into '/system/media' and it will play)
Carrier IQ ("CIQ") removed (k0nane)
Yaffs2 file system (MTD partition map)
Stock Gingerbread Launcher with 3D fix (hoffman1984)
GPS Fix (hienkhieu)
Proper Reboot and Reboot to CWM Recovery on the power menu (Thanks to untermensch for the excellent quide)
Hacked Sprint Hotspot (Tortel1210)
1% battery (Icons by Mendozinas)
3G/1x icon fix (SenseiSimple)
CRT Off
CRT On (Thanks to Whitehawkx for the guide)
No battery popup
Screen stays off when unplugged
Volume rocker mod (sound on to vibrate to silent) (mkasick)
Silent Camera (SenseiSimple)
Scrollable Status Toggles - with 4G Button (lidroid, SensieSimple, 4G button mod, other fixes mods by me)
Downloads:
Full Version: CleanGB-MTD 1.0.5 (146MB) (MD5: 9D7E480DF87E63908C750567E7902FDE)
ROM Manager Web Connect Link: CleanGB 1.0.5
Kernel: CleanGB-MTD Kernel b805fd377c (source) (Note: This is the kernel from CleanGB-MTD 1.0.5)
Boot into CWM and flash. Info on CWM
Optional Mods:
TouchWiz30 Launcher
Touchwiz Widgets (only usefull if you use the TouchWiz Launcher
Epic Live Wallpapers
If you like my ROM, buy me a beer!
Screenshots
FAQ:
Q: Why should I move to a MTD based ROM?
A: Cyanogen Mod for the Epic 4G, which is being worked on right now requires the MTD partition layout. Once you flash a MTD based ROM, the only way to go back to a stock ROM which uses Samsung proprietary BML partition layout, is with ODIN. This is a major inconvenience for many as ODIN is notoriously unreliable. You can move between MTD based ROMs without the use of ODIN.
Q: When moving from a BML to an MTD ROM can I use Nandroid backup to backup and restore my data?
A: Yes, but the process is a bit more involved (Thanks to Tortell1210 for this guide):
To restore data from a nandroid backup:
Mount your sdcard as USB storage
Navigate to clockworkmod/backups/<LAST BACKUP>/
Rename system.rfs.tar to system.yaffs2.tar, data.rfs.tar to data.yaffs2.tar
Open the nandroid.md5 file, replace all rfs in the filenames with yaffs2
Save/close, unmount USB, and reboot into recovery
Advanced restore data (And system if you really want). Only advanced restore, or else it will give you a BML kernel and recovery, which wont boot
Reboot!
(If you were on ext4, just replace rfs with ext4)
If you want your previous Rom, advanced restore system too.
Q: Where is the bootanimation.zip and how can I change the boot animation?
A: The stock boot animation is actually contained in the framework-res.apk file. If you want to use a custom boot animation, all you have to do is place your bootanimation.zip in the /system/media directory and it will play instead of the stock one.
Q: What about [insert feature here]?
A: See the todo list below
Bugs/Todo:
Change Log:
CleanGB-MTD 1.0.5
Fixed improper permissions set on su at bootup.
Overhaul of clock frequencies - 600,1100,1300 frequencies fixed. (thanks to dyehya for noticing this and teaching me how the frequencies work)
/sbin/remount script fixed
System app changes:
Updated Books
Updated Google Search
Updated Maps
Updated Thinkfree Office
Updated Market
Updated Street View
Updated Superuser
Updated Voice Search
Removed Talkback
Updated su binary to latest version
Integrated Logsprovider fix by default
CleanGB-MTD 1.0.4
Kernel fixes
Proper support for reboot to recovery (mkasick)
ROM Manager MTD Support (see this)
"Non-Optimal" su permissions fixed Not fixed!
Reboot to recovery from power menu added back
Lockscreen changed to AOSP Lockscreen
CleanGB-MTD 1.0.3
Fixed broken bootanimation.zip support
Kernel now checks for and installs root and busybox at bootup
Reboot to recovery from shell now works (Because of this, ROM Manager support is now possible)
Power menu mod enhancement: Reboot dialog and progress now show "Reboot", "Your phone will reboot", "Rebooting...", instead of "Power Off", "Your phone will shut down.", "Shutting down..." (source)
CleanGB-MTD 1.0.2
Fixed broken GPS (see)
CleanGB-MTD 1.0.1
Forked ROM into BML/MTD versions
Fix for power menu bug (see this)
Fixed init.d script support, which was broken (and no one ever noticed!)
CleanGB 1.0
New kernel with capacitive button light fix
Scrollable Status bar toggles with 4G button
Build 18
Removed broken talkback app from system
Build 17
Improved kernel with stability fixes
Updated stock apps
Books
Gmail
Maps
Talkback
Market
Sprint Voice Mail
Youtube
Silent Camera
CRT On
Removed left over CIQ lib
Build 16
ClockworkMod 5.x /ROM Manager Support
Build 15
Changed theme to account for apps that put black text in dropdown menu items
Put back "MyFiles" app as multiple sprint apps rely on it
Restored ClockPackage that links to MyFiles
Build 14
New Kernel - change to how ext4 partitions are mounted; will give you ext4 users those uber fast quadrant scores (that mean nothing).
Clock app was hard coded to use the "MyFiles" app (which is not in this ROM) to chose alarm tones. Hacked app to remove that feature.
Zipaligned apk files (yes, I forgot to do it)
Build 13
Added Kernel that supports overclocking to 1.4Ghz and voltage changes (source is in first post)
Removed useless buddiesnow package
Fixed voicemail notifications (black text on black background)
Added ext4 version
Build 12
Added 3g/1x icon fix (Screw you Sprint!)
Added all-black wallpaper to launcher's wallpaper picker to match default all black wallpaper
Added /system/etc/init.d directory for init.d script support
Build 0-11
I don't remember
Yay!
10Char
FIRST !!!!!!! ( I've waited several months to be able to say that ..... LOL ! ... even though this is Post #5 , the others were already reserved by toad ... LOL !)
I put BML version on my wife's phone and she really likes it. Thanks for all your work Toad.
Sent from my SPH-D700 using Tapatalk
If this is as good as the bml version I've heard so much about, I may have to try this
sent from my touchwiz 4.5-ed epic
Downloads are up!
*praying I didn't f--- something up*
AWESOME!!! Thanks so much for this!
Toad,
I read the instructions, but I'm a little confused, so I'll just ask.
1) I'm on Clean GB1.0....Can I just flash this? If I loose my data, no biggie, I'll restore from Titanium and redo my device. Are there advantages?
2) Is the Kernel built in or flash it separately?
Thanks!!!!!
sandman512 said:
Toad,
I read the instructions, but I'm a little confused, so I'll just ask.
1) I'm on Clean GB1.0....Can I just flash this? If I loose my data, no biggie, I'll restore from Titanium and redo my device. Are there advantages?
Click to expand...
Click to collapse
If you are on CleanGB 1.0, which is BML, your data partition will be wiped. You will have to restore your stuff via Titanium. nandroid backup can be used also, but you have to edit the backup file names before you restore them.
2) Is the Kernel built in or flash it separately?
Click to expand...
Click to collapse
The kernel is built in.
toadlife said:
If you are on CleanGB 1.0, which is BML, your data partition will be wiped. You will have to restore your stuff via Titanium. nandroid backup can be used also, but you have to edit the backup file names before you restore them.
The kernel is built in.
Click to expand...
Click to collapse
Thanks for the reply. What are the advantages of the ROM as compared to GB1.0.
Also, can I use Titanium without renaming.
THANKS!
sandman512 said:
Thanks for the reply. What are the advantages of the ROM as compared to GB1.0.
Also, can I use Titanium without renaming.
THANKS!
Click to expand...
Click to collapse
1) See the FAQ regarding the advantages of moving to MTD
2) Yes.
Any reason to flash for people running Stock-ish MTD build?
lancelot916 said:
Any reason to flash for people running Stock-ish MTD build?
Click to expand...
Click to collapse
The Stockish ROM will do your laundry; this one will sort the colors first.
toadlife said:
The Stockish ROM will do your laundry; this one will sort the colors first.
Click to expand...
Click to collapse
LOL, nice!
What are the main differences between your kernel and the Stock-ish kernel or zman's MTD kernel? Is this more optimized for speed, stability, performance..?
Wait, so Toad, does your MTD have 4G? I'm lucky enough to live in an area with good 4G and despite what I thought I couldn't live without it and had to Odin back to a regular ROM
Sent from my SPH-D700 using xda premium
Link2SD...
Does Link2SD work on MTD ?
Thanks
bit1 said:
Wait, so Toad, does your MTD have 4G? I'm lucky enough to live in an area with good 4G and despite what I thought I couldn't live without it and had to Odin back to a regular ROM
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yes. 4G works. 4G only doesn't work on Cyanogen Mod and MIUI ROMs because they use open source only kernels. This ROM still has Samsung's Wimax driver which is what you need for 4G.
With MTD TW ROMs, you can go back and forth between TW ROMS and CM7/MIUI without having to use ODIN.
Toadlife, does link2sd work on MTD ? please help...
Thanks
DEODEXED/ODEXED DDMD1
You can use this ROM as base for your ROM, Just PM me with a link to the thread!
This is the "FULL ROM" not just the /app and /framework folder. :highfive:
Click to expand...
Click to collapse
FEATURES:
Latest Busybox (Completely Symlinked).
Latest Indian firmware.
Rooted with latest Superuser.
No scrolling bug (as in DDLK2).
Fully stock, no changes in UI.
Now works with any kernel.
Bugless & Rock Solid Stock Build.
The successor of DDLK2.
INCLUDED KERNEL DETAILS:
Latest DDMD1 Kernel
DOWNLOADS:
Deodexed DDMD1
Odexed DDMD1
Mod Edit: Link removed due to using pay per click's site Mirror - File Repository[/URL]
CREDITS:
Samsung
Evanlocked
SamFirmware
dsixda Kitchen
nolinuxnoparty
d3cka
zalzondabuzz
RiddlerA
SCREENSHOTS:
Lidroid Toggles:
{
"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"
}
Settings Mod:
Evolution X4 Statusbar:
4 Way Boot Menu:
ADDONS & PATCHES:
Swipe To Remove Notifications
All Kernel Fix (Call, IMEI, etc.) (MD5: 1EBAE85470D1ECF388A358241B1096A4)
Evolution X4 StatusUI
4 Way Boot Menu
Lidroid Toggles
Settings with embedded QuickPanel Options
For Deodex:
Rename to Settings.apk
Push to /system/app
Set permissions r w- r-- r--
Reboot!
For Odex:
Rename to Settings.apk
Push to /system/app
Remove Settings.odex from /system/app
Set permissions r w- r-- r--
Reboot!
INSTALLATION:
Newbies:
Flash DDMD1 Stock ROM via Odin.
Reboot in Recovery.
Flash Temporary CWM.
Wipe Data & Cache.
Flash ROM.
Advanced users:
Reboot into CWM.
Format system, cache and data.
Mount all partitions.
Flash ROM.
ADDITIONAL INFORMATION:
Know why you should "even" think of using the odexed version.
WHAT IS AN ODEX FILE?
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
HOW THIS WORKS
For the more geeky amongst us, Android OS uses a Java-based virtual machine for running applications, called the Dalvik Virtual Machine. A deodexed, or .dex file contains the cache used by this virtual machine (referred to as Dalvik-cache) for a program, and it is stored inside the APK. An .odex file, on the other hand, is an optimized version of this same .dex file that is stored next to the APK as opposed to inside it. Android applies this technique by default to all the system applications.
Now, when an Android-based system is booting, the davlik cache for the Davlik VM is built using these .odex files, allowing the OS to learn in advance what applications will be loaded, and thus speeds up the booting process.
By deodexing these APKs, a developer actually puts the .odex files back inside their respective APK packages. Since all code is now contained within the APK itself, it becomes possible to modify any application package without conflicting with the operating system’s execution environment.
ADVANTAGES & DISADVANTAGES
The advantage of deodexing is in modification possibilities. This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first, since that would not only allow him to modify various APKs, but also leave room for post-install theming.
On the other hand, since the .odex files were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times. However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used. Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
For a casual user, the main implication is in theming possibilities. Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.
Prevent this thread from dying.
Rate this thread ★★★★★
Press "Tip us?"
Press thanks
Post in this thread (I am not asking you to spam!)
Click to expand...
Click to collapse
At last.Deodexed version is up!
Please upload it Asap
No longer switching to old Stock ROM's because of GNU Kernel, Hells Fusion Kernel, etc. not working!
NOTE: The problem why DDMD1 was not so commonly used is that if you flash a custom kernel other than the one provided with this, then you can't call anyone and IMEI is not displayed.... That is due to some changes in new libs and it is now fixed by flashing the lib provided in OP.
NOTE: To fix all Call & IMEI Problem, you need to flash the above (posted in OP) fix!
NOTE: According to some reports, that although network problems are fixed with above patch, IMEI does not appear with custom kernels. This error should not have occurred if you have followed EXACT instructions as in OP.
Thread Changelogs:
CURRENT:
18-09-2013 WEDNESDAY
--------------------------------------
Added 4 Way Boot Menu to Addons.
OLD:
05-07-2013 FRIDAY
--------------------------------------
Added ODEXED | DEODEXED DDMD1 (no addons till now)
06-07-2013 SATURDAY
--------------------------------------
Added ADDONS - Lidroid Toggles, QuickPanel Settings, Swipe To Remove
08-07-2013 MONDAY
--------------------------------------
Removed Swipe 2 Remove. (Bootloop)
19-08-2013 MONDAY
--------------------------------------
Added Broadcom Radio Interface Layer fix.
boot.img
Do you guys have kernel of ddmd?
I need it for r&d.
CharsiBabu said:
Do you guys have kernel of ddmd?
I need it for r&d.
Click to expand...
Click to collapse
The above package also contains the DD MD1 kernel.
You may download and extract it.
low on data pack
Yash98 said:
The above package also contains the DD MD1 kernel.
You may download and extract it.
Click to expand...
Click to collapse
If I could, I would've downloaded the entire package.
But since I can't, I simply asked for it.
nvm.
Another thing,
can you provide me link to update 4 source?
Because i can't find it on their official page.
Link:-
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=5360
Its not yet released
(source)
Here is your boot.img
CharsiBabu said:
If I could, I would've downloaded the entire package.
But since I can't, I simply asked for it.
nvm.
Another thing,
can you provide me link to update 4 source?
Because i can't find it on their official page.
Link:-
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=5360
Click to expand...
Click to collapse
Can I ask you a question?
What would you do with the RamDisk?
The ODIN firmware(zip)package you've provided contains only one .tar.md5 file, but not separated PDA/MODEM/CSC files we've seen in earlier packages(DDLA2,DDLC2,DDLK2, and so on) and this cannot be flashed via ODIN. Even after checking a guide on XDA on how to use ODIN( I know how to use ODIN but I was confused when I found this only one file) and it fails to flash via ODIN. Later I flashed DDMD1 using this one. Please check the firmware package you've provided.
l0lh4rd said:
The ODIN firmware(zip)package you've provided contains only one .tar.md5 file, but not separated PDA/MODEM/CSC files we've seen in earlier packages(DDLA2,DDLC2,DDLK2, and so on) and this cannot be flashed via ODIN. Even after checking a guide on XDA on how to use ODIN( I know how to use ODIN but I was confused when I found this only one file) and it fails to flash via ODIN. Later I flashed DDMD1 using this one. Please check the firmware package you've provided.
Click to expand...
Click to collapse
Then how did I flash it?
Bro, that 1 .tar.md5 is to be put in PDA section and then start flashing.
You'll be suprised when it works!
You are right, but that was believed some time back
Like for example when you download ODIN flashable kernel .tar, do you get all the three tar's: PDA/CSC/MODEM ?
Yash98 said:
Then how did I flash it?
Bro, that 1 .tar.md5 is to be put in PDA section and then start flashing.
You'll be suprised when it works!
You are right, but that was believed some time back
Click to expand...
Click to collapse
Doesn't work
EDIT: Anyways I don't want to bother you with my problems( latest one: can't flash any custom kernels; might be due to new ramdisk as mentioned by member: Nitzz). Nice work
[REVERTED BACK TO OLD BASEBAND; FORGOT TO PROVIDE LOGCAT ]
Bro, if you want I can PM you the three PDA/CSC/MODEM .tar.md5 files by splitting this package, what say?.
Yash98 said:
Bro, if you want I can PM you the three PDA/CSC/MODEM .tar.md5 files by splitting this package, what say?.
Click to expand...
Click to collapse
No thanks but I already got from this thread http://forum.xda-developers.com/showthread.php?t=2335690&highlight=ddmd1 (thread closed but links not removed )
Yash98 said:
Bro, if you want I can PM you the three PDA/CSC/MODEM .tar.md5 files by splitting this package, what say?.
Click to expand...
Click to collapse
Nice idea :thumbup:
PM me too!
aniket.lamba said:
Nice idea :thumbup:
PM me too!
Click to expand...
Click to collapse
Here: http://www.mediafire.com/download/023udvzhhrgnb4z/S5360_DDMD1_ODDMD1_DDMD1.zip
Please report me if it is not 3 package!
l0lh4rd said:
Doesn't work
EDIT: Anyways I don't want to bother you with my problems( latest one: can't flash any custom kernels; might be due to new ramdisk as mentioned by member: Nitzz). Nice work
[REVERTED BACK TO OLD BASEBAND; FORGOT TO PROVIDE LOGCAT ]
Click to expand...
Click to collapse
yo yo!
m back..
yeah just read my thread..
latest firmwares support either my kernel or latest stock kernel..
what are the problems u all are facing?
Update Changelog:
Added Mirror
Update Changelog:
Added Swipe 2 Remove
Added Settings mod
Updated Credits
Can anybody provide me the latest stock kernal of ddmd1??
Sent from my room using sgy evo-x4//
I m always there to help.
This is a Windows Batch Script/Tool to make any 4.4 based ROM to full F2FS compatibility !! This tool can convert any existing ROM from ext4 to Full F2FS Compatibility in a few clicks !! All tools necessary for conversion included in the batch file itself !!
Basic Info
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
DISCLAIMER
Code:
*I am Not responsible for any bricked devices,SD cards or thermonuclear attacks.
*Please do some research about what you are doing before you use the tool.
*YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Current Device Compatibility
Code:
1. Nexus 4 ( Mako )
2. Nexus 7 2012 Edition ( Grouper)
Prerequisites
Code:
1. A Mako/Grouper
2. Any 4.4 based ROM with [B][U]busybox [/U][/B]installed
3. Proper F2FS Compatible Recovery and Partition Zip from
[URL="http://forum.xda-developers.com/showthread.php?t=2678140"]http://forum.xda-developers.com/showthread.php?t=2678140[/URL]
4. Any Windows version and my batch script
Features
Code:
1. One Click F2FS Conversion Process
2. All tools included in the Zip file itself
3. Changes only the relevant parts of your updater-script keeping the rest unmodified
4. Compatible boot.img included in the ROM itself
5. Single script for both Nexus 4/ Nexus 7 ( 2012)
6. Error conditions at many places so a noob cant go wrong
***Special note for Stock ROM users***
Code:
The script requires busybox and since stock roms dont have busybox the repacked ROM wont boot up.
In such a case the best option is try out any other AOSP based ROM
Instructions
Code:
1. Unpack the Zip file you downloaded from Link Below
2. Run F2FS Convertor.bat
3. Select your device
4.Place the Zip in the Extract /Input directory when prompted
5. The script will Unpack your ROM
6. Select option 11 for boot.img supplied with the script or option 12 for cm boot.img and 13 for any other F2FS compatible boot.img
7. Repack your ROM
8. Check NEW F2FS ROM directory for the Repacked ROM
9. Flash and Enjoy
10.Cleanup the working directory cleanup.bat
Download Links
1) English
2) German (Thanks to @mikaole)
Changelog
Code:
V1 : Initial Release
Credits
Code:
@legolas93 For bringing F2FS to Nexus and also for providing the boot.img for the script
[user=4439521]@mikaole[/user] For the German Translations and extensive testing
[user=2002216]@jolinnard[/user] For the amazing F2FS kernels he is providing
[user=4544860]@osm0sis[/user] For his amazing Android Image Kitchen.The cleanup.bat script is taken from his tool.
[user=3325155]@fishears[/user] For helping out on the kernel side.
[user=5501864]@USBhost[/user] For being the lone tester for the N7 ( 2012 )
[user=4450732]@CallMeAldy[/user] For the CM trick and his compilation thread
And all other beta testers !! Sorry if I forgot anyone from the list !!
Screenshots in the Next Post
Hit the Thanks button if you Like My Work
Reserved
Lol where were you weeks ago when we needed you most? Thanks for this work, but I wish I had something to flash just to try it. Right now SlimKat is working wonderfully as is.
Thanks for doing this for the community. [emoji106]
Sent from my Nexus 7 using Tapatalk
SkOrPn said:
Lol where were you weeks ago when we needed you most? Thanks for this work, but I wish I had something to flash just to try it. Right now SlimKat is working wonderfully as is.
Thanks for doing this for the community. [emoji106]
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
All the best things, take time to come
SkOrPn said:
Lol where were you weeks ago when we needed you most? Thanks for this work, but I wish I had something to flash just to try it. Right now SlimKat is working wonderfully as is.
Thanks for doing this for the community. [emoji106]
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Its just 3 weeks ago things started to build up for f2fs for mako !! I created this script primararily for my Mako dont own a grouper !! Took me two weeks to polish the script !! Basically wanted to make kernels compatible too but after trying hard had to give it up !!
Do I get this right: I can use this script to convert the latest CM 11 nightly to F2FS compatibility? And what if the kernel changes in the nightly? Has the included kernel the fixes for the recently changed ram disk?
NABENDU1 said:
Its just 3 weeks ago things started to build up for f2fs for mako !! I created this script primararily for my Mako dont own a grouper !! Took me two weeks to polish the script !! Basically wanted to make kernels compatible too but after trying hard had to give it up !!
Click to expand...
Click to collapse
I was just poking fun at ya, nothing rude was intended. I am very happy to see something like this take place. Now we have something to do the next time our favorite ROM gets released.
We just need about 100 more devices to get supported and this may take off with the manufacturers themselves. Then I will consider all smart devices up to that point one large 10 year long beta test. Lmao
Sent from my Nexus 7 using Tapatalk
So this won't work on the Galaxy Note II ...... wish it would lol
master.peterm said:
So this won't work on the Galaxy Note II ...... wish it would lol
Click to expand...
Click to collapse
If you can link me to its thread which can make it fully f2fs compatible I'll be more than glad to help !!
SkOrPn said:
I was just poking fun at ya, nothing rude was intended. I am very happy to see something like this take place. Now we have something to do the next time our favorite ROM gets released.
We just need about 100 more devices to get supported and this may take off with the manufacturers themselves. Then I will consider all smart devices up to that point one large 10 year long beta test. Lmao
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I had no hard feelings or stuff on you or anybody !! Just that wanted to inform you about why my script was released so late !! And ya that's exactly my intention to make flashing Roms easy !! I mean changing manually isnt always gr8 especially when you flash on a daily basis like I do
edisso10018 said:
Do I get this right: I can use this script to convert the latest CM 11 nightly to F2FS compatibility? And what if the kernel changes in the nightly? Has the included kernel the fixes for the recently changed ram disk?
Click to expand...
Click to collapse
No idea I don't own a grouper so I don't test it at all !! @USBhost gave this boot.img to me and I included it in my script !! I think he could explain this better
Hey, I've been trying to troubleshoot for about 30 minutes but I simply cannot get the script to repack the ROM.
Here are the issues I'm running into:
1) When I am instructed to place the original ROM zip in EXTRACT/INPUT there is no INPUT subfolder.
That was easy enough though. I simply made one, placed the zip in, and everything seemed to move forward fine.
However:
2) During repacking, the script runs into a few errors. Rather than describing them here, I will post pictures of them below.
{
"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"
}
The end result:
I can't find a repacked ROM in any of the folders or subfolders.
Any ideas about where I went wrong?
Note this does not convert the kernel to f2fs you have to flash a custom All-F2FS kernel
Oh, I thought it did that? Can we please have that included into this script? Just put your favorite f2fs kernel into a folder and let it include it into your new f2fs rom? That would be nice...
SkOrPn said:
Oh, I thought it did that? Can we please have that included into this script? Just put your favorite f2fs kernel into a folder and let it include it into your new f2fs rom? That would be nice...
Click to expand...
Click to collapse
If I get some time, I may try to put together a bat file to do this. Should be able to just extract both zips, merge the kernel library modules into the system folders in the ROM zip, and replacing the boot image. The whole system folder gets extracted recursively so the kernel files go with it, and zip it back up. This program fixes the updater-script.
Sent from my SCH-I545 using Tapatalk
icarianecho said:
Hey, I've been trying to troubleshoot for about 30 minutes but I simply cannot get the script to repack the ROM.
Here are the issues I'm running into:
1) When I am instructed to place the original ROM zip in EXTRACT/INPUT there is no INPUT subfolder.
That was easy enough though. I simply made one, placed the zip in, and everything seemed to move forward fine.
However:
2) During repacking, the script runs into a few errors. Rather than describing them here, I will post pictures of them below.
The end result:
I can't find a repacked ROM in any of the folders or subfolders.
Any ideas about where I went wrong?
Click to expand...
Click to collapse
Its not that you went wrong it's my script which is calling the wrong directories !! I had faced the same problem with my mako script in its early days but after changing a few things here and there it was gone !! Bdw I'll hook you up to a test script hopefully by today evening and I think you should be good to go
Edit : Others report it as working !! Might be you doing something wrong on your end ! Bdw you should extract all my folders in d F2FSROMCONVERTOR folder !! Name change or anything will effect the script to through errors
And ya the v3 test version is d same as the released version as far as I remember
NABENDU1 said:
Its not that you went wrong it's my script which is calling the wrong directories !! I had faced the same problem with my mako script in its early days but after changing a few things here and there it was gone !! Bdw I'll hook you up to a test script hopefully by today evening and I think you should be good to go
Click to expand...
Click to collapse
I tired a bit different method but was not working for me !! Tried android image kitchen to extract the boot.img made a compatible zImage of my kernel and copied the modied zImage to that of the unpacked boot.img from android image kitchen !! Then changed the fstab and repacked but the same still won't boot !!
If you can help me get this working with kernels I'll be much more happy
NABENDU1 said:
I tired a bit different method but was not working for me !! Tried android image kitchen to extract the boot.img made a compatible zImage of my kernel and copied the modied zImage to that of the unpacked boot.img from android image kitchen !! Then changed the fstab and repacked but the same still won't boot !!
If you can help me get this working with kernels I'll be much more happy
Click to expand...
Click to collapse
That's exactly what I tried
---------- Post added at 01:42 AM ---------- Previous post was at 01:32 AM ----------
I wonder if you just replaced the boot.IMG from the ROM with the kernel's boot.img
Would that boot
---------- Post added at 02:03 AM ---------- Previous post was at 01:42 AM ----------
It works!!! Cheer !!
Amazing tool lml
Enviado desde mi Nexus 7 mediante Tapatalk
Carbon ROM 4/24/2014 with the M-kernel
---------- Post added at 04:01 AM ---------- Previous post was at 03:29 AM ----------
icarianecho said:
Hey, I've been trying to troubleshoot for about 30 minutes but I simply cannot get the script to repack the ROM.
Here are the issues I'm running into:
1) When I am instructed to place the original ROM zip in EXTRACT/INPUT there is no INPUT subfolder.
That was easy enough though. I simply made one, placed the zip in, and everything seemed to move forward fine.
However:
2) During repacking, the script runs into a few errors. Rather than describing them here, I will post pictures of them below.
The end result:
I can't find a repacked ROM in any of the folders or subfolders.
Any ideas about where I went wrong?
Click to expand...
Click to collapse
F2FSROMConvetorV3
this one works for me
I tried using this tool to build a omni verison and a cyanogenmod version, both the latest nightly. On each build I get the message " Type Password to Decrypt ..."
Also the recovery provided does not boot up after flashing it using fastboot. The recovery from http://forum.xda-developers.com/nexus-4/orig-development/recovery-rom-kernel-f2fs-05-04-14-t2706825 is working
joefso said:
I tried using this tool to build a omni verison and a cyanogenmod version, both the latest nightly. On each build I get the message " Type Password to Decrypt ..."
Also the recovery provided does not boot up after flashing it using fastboot. The recovery from http://forum.xda-developers.com/nexus-4/orig-development/recovery-rom-kernel-f2fs-05-04-14-t2706825 is working
Click to expand...
Click to collapse
You flashed a MAKO recovery onto your Grouper? I did not know that would work
EDIT: Never mind me, I see that you have a mako and trying to convert your Omni to it.