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.
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?
{
"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.
{
"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"
}
This thread will be for my ICS builds which will slowly develop into Kyorarom Serenity (not to be confused with Eternity which will be Gingerbread based).
Basic Features
JIT
Rooted
CM9 built from source code (repository updated extremely often as I use it for my S2)
Kyoratweaks
Kyoralock (coming soon)
Kyoraapp
Hybrid Data2SD and SD card swap
Serenity Kernel
Overclock to 1.2GHz
CWM 5 recovery
Multi-boot
Voodoo Sound v10 (need to add app - coming soon)
What Doesn't Work
Bluetooth
Mobile AP
Camera previews
GPS
USB Mounting (UMS/MTP/PTP)
WiFi signal in the status bar
Still very slow (animations <- due to still immature drivers)
Camera.apk crashes for some
Sound recording
Live streaming of audio
SIM PIN lock (you MUST disable your SIM PIN code before using this ROM)
Sources
android/device/samsung/apollo
android/vendor/samsung/apollo
android/kernel/samsung/apollo
android/vendor/hillbeast
android/bootable/recovery
CM9 repository (Google for it)
Screenshots
Will come when I get time.
Demonstration Video
Might make one at some point.
Kyoraapp Thread (For Guides And Help With It)
Bugs And Questions Thread
Performance
Who really cares?
Credits
Team G3MOD for their kernel
marcellusbe for his work on the Galaxy 3
Kyrillos for all the scripts he's gotten working on this phone
moikop for his assistance with G3MOD Kernel and Kyoraapp
Shree_Jamdar for the Kyorarom Demo video
Rudolf895 for all his guides
RafayelG for helping and pointing me in the right direction
apollo5801 and Arakmar for their work on ICS to date
tom3q for his work on OpenFIMG and helping me with porting kernel 3.x
A big thanks all the respective developers of the included apps
And lastly thanks to Samsung for making a great phone and then screwing it up with weird software
Thanks For Donations
Check the Ascendency thread for the donations.
Planned Features/Requested Features
fs.convert
fs.options (easy peasy)
Do not enable Data2SD while in recovery
Touch recovery
Fix dictionary
/system/sd mount for Titanium (really wish that Titanium would stop being stupid and using a ridiculous location for it's SD-EXT partition...)
Changelog
27-06-2012
Updated OpenFIMG
CM9 RC1
12-06-2012
ROM branded as Kyorarom in modversion
New update.zip naming convention
Updated CM repo
Loads of tweaks all over the place from CM team
This fix didn't happen on the G3, only big phones - Boot animation now has Cid in it, rather than Andy (if you don't understand, you'll know what I mean when you see it) (I will be giving it my own boot animation at some point. I need to make my animation though. It's in my head, I just need to get the time to create it.)
Took MIUI out again seeing CM9 finally fixed the media player
Added 'hold Menu to search' function.
05-06-2012
Lock screen options easier to locate
Lock screen weather
New music player that ****ing works. (called Apollo - coincidence?)
Screen off CRT animation works
28-05-2012
Updated CM repo
Changed default background
21-05-2012
Data2SD
Hybrid Data2SD v2
Added MIUI Music (a lot of features aren't working right in it though, I will look at that when I care enough).
Updated to latest CM repo (nothing too interesting to see there)
init.d is now working
Kyoratweaks are working
08-05-2011
2-stage kernel boot
CWM 5.5 (non touch)
Force boot mode functionality (hold HOME to force normal boot, and hold MENU to force recovery boot - could be useful for people with broken volume buttons)
Faster boot
Removed G3MOD boot logo
Boot logs have moved to /tmp/ (stage1.txt for stage1 log, fsdetect.txt for FS Detection module, fs.current for showing current filesystem structure)
Updated CM to latest repo
Theme Chooser (see Settings -> Interface/Themes)
Lock screen shortcuts (see Settings -> Interface/Settings -> Lock screen)
DSP Manager has better support for WM8994
04-05-2012
Kyoraapp
Kyoratweaks (not working just yet, but the script is all there)
Kyoralock (not automatic yet)
Fixed assert issue in update.zip
Added SamsungServiceMode application. Use *#*#0011#*#* and *#*#4636#*#*. There's probably more but those are the ones I know.
bmlunlock built from source (smaller)
Using kernels busybox when updating rather than using a packaged one (saves space in update.zip)
Fixed adb install/pm command
Added File Manager
03-05-2012
Update.zip format (which will be the format for all future releases. If you cannot flash update.zips, then flash G3MOD kernel first).
G3MOD Inline Kernel Building (latest G3MOD on every release)
Fixed reboot menu (now says Download instead of Bootloader, and it reboots to download mode)
Fixed Superuser
Fixed Camera
Fixed Phone.apk
Fixed sensors
More free space in /system
Test 003
ODIN TAR
Integrated G3MOD Kernel (HB Test 002)
Test 002
First Build
Download Links
Serenity 2012-06-27 (update.zip)
Serenity 2012-06-12 (update.zip)
Test 2012-06-05 (update.zip)
Test 2012-05-28 (update.zip) (Dev-Host)
Test 2012-05-28 (update.zip) (Mediafire)
Test 2012-05-21 (update.zip)
Test 2012-05-08 (update.zip)
Test 2012-05-04 (update.zip)
Test 2012-05-03 (update.zip)
In case people are wondering where the ODIN.tars and system.imgs are, I am not going to release Serenity in those formats as they are not standards compliant, and make the file much bulkier than an update.zip. As well as that, they require more effort to produce. I am only releasing one ODIN version (the foolproof version) for in case people experience issues flashing the update.zip, and these issues should only exist first time.
Extra Downloads
Google Apps Mini <- small Google Apps package that gives you the basics to get running.
ODIN Version (foolproof method) <- For if installing the update.zip doesn't work right for you. This will make sure everything is set up how it should be. This release is outdated now so I suggest downloading this and the latest update.zip and updating after flashing the ODIN version. Includes G3MOD 2.5 OC version.
Non-OC Kernel (G3MOD 2.5)
LatinIME.apk <- full keyboard from SGS2 with all the dictionaries and such if they aren't working for you. This can be installed like any normal APK.
Guides
Installing update.zips
You will need to flash a kernel that includes CWM, or install CWM on a stock ROM. There are guides on how to do this. I recommend installing G3MOD to get CWM.
Copy update.zip to SD Card
Reboot phone into CWM (turn off the phone and turn it back on while holding both volume keys and the home key)
Go to "install zip from sdcard"
Choose to install the update.zip
Reboot phone
Enjoy Kyorarom
Adding Kyorarom support to your kernel
Add all the CM7/9 support functionality (basic stuff like USB and audio)
Make a copy of the defconfig (either .config or apollo_rev_02_defconfig) called cyanogenmod_apollo_defconfig
Edit the config to locate your initramfs (this will depend on where you keep your initramfs). If you use old G3 style (G3MOD, Fugumod) of storing the kernel with initramfs in a directory below the kernel you will want source/../initramfs, whereas if you use Kyorakernel style (initramfs inside kernel directory), you want source/initramfs. If you want 2-stage style, you will want source/usr/initramfs.list. Refer to my kernel to see how I did it as 2-stage is quite tricky and different to what we used to use.
Compile the kernel with the config (make -j2 cyanogenmod_apollo_defconfig) to test it works
Modify scripts/kconfig/Makefile as shown in this commit: https://github.com/dharamg3/G3MOD/commit/c8adf776285365d7fece528e20914d778e2a8d1a#diff-2
Clean the kernel repository (make clean) and (make mrproper)
Full Feature List
In a code box to save space
Coming soon
Bugs And Questions Thread
FAQs
nice going here Mark
I hope you'll be able to fix BT soon
What about Camera.apk?Does it work?
edit: lol...i missed camera app not working in 1st post
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.1
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It may be interesting
Good luck with this version.
Good Luck With This mate......!!!
Looking Forward to it....
Looking forward to Eternity. But all the best of this one too.
Interesting.
I think we can expect good rom because you are the one in cm9 devs.
All the best
Test 003 uploaded to Mediafire
Linky Brinky
I made an ODIN TAR this time not to annoy Linux/Mac users, rather to try to fix the issues people were having of boot looping in 002. If it still doesn't work then wipe your data. If it still doesn't work then take the SD card out. If it still doesn't work then your phone is broken.
Changelog
* ODIN TAR now
* Updated CM9 repo (more translations, and a few fixes that probably won't apply to the G3).
* Compiled with a few tweaks here and there.
great !!! tryin now
EDIT: what do you mean by sensors? all the sensors already work right?
nice work, Mark!
Tried Test build 003. First was stuck at the bootanimation. Factory resetted from the cwm and booted in.
The build seem to be more smoother than the other build.(I maybe wrong cause i havent tested the other ics build for quite a time). Other than that its nothing more special.
@hillbeast waiting for the kyoralock and other tweaks. Also can you try to port the same - kyoralock, kyoraap, and kyoratweaks into CM7. That would really boost the performance.
Thanks!
EDIT
BTW Does hybird data2sd work on ics??
EDIT2
There is a problem in calls. FC's when you call someone.
Good job ! For the next build, can you :
Include the newest GApps ? When I flash, Gplay is missing
Add an File Explorer ?
after flashing gapps, still the setup wizard not shown, not able to sign in to google. also browser fcs and no keyboard
Edit 1: No way to get to the market, no way to get to the SD Card, no way to browse the net or download any app via browser, no way to sign in to google, No setup wizard after flashing Gapps, infact no google app after flashing gapps Wierd problems...
By the way, ROM is blazing fast...
How happy am i to see this thread?
VERY HAPPY!!
Hum, yeah, I too can't seem to install Google Apps... It takes a very long time to start installing from the update.zip, but once I restart the phone, there's no Play or Talk... I can add my account, even though it doesn't work with calendar, etc.
jpaisneto said:
Hum, yeah, I too can't seem to install Google Apps... It takes a very long time to start installing from the update.zip, but once I restart the phone, there's no Play or Talk... I can add my account, even though it doesn't work with calendar, etc.
Click to expand...
Click to collapse
Don't try to install gapps, it will fail as the core ICS system itself take 90-95% of disk space. So gapps will not be completely installed when u try installing it. Only if we remove some core apps/files then only we can able to install it.
If you are interested then try my rom MPICS which has integrated gapps.
Maybe?: Final Note
Hello everybody,
I'm sad to announce that my Galaxy Y has died on me.
Not completely, but the USB port seems to have died on my phone.
Charging through the connector still seems to work, but other then that the device is not recognized by any computer anymore.
I know a lot of you are thinking of drivers right now, but this is not the problem.
Not even the phone detects anymore when it's connected to the phone.
This renders the device rather useless for developing as a USB port is really important in this case certainly when having a bad kernel.
I have three options left right now.
- First option would be to hand over the complete development to another developer owning this device. Of course I will help you get started with my sources so you can get started where I left.
The second and third option is up to the community
- If there is anybody in the community who knows somebody who doesn't use the Galaxy Y anymore or is willing to donate his/her own phone this would help out a lot as then I can continue myself in this development.
- Or if anyone could spare some money you could also donate it to me over PayPal. These donations will only go towards buying a second hand Galaxy Y, and will be evenly divided between all donates all money which is left in this case will be reimbursed evenly to everyone who donated to me.
Whichever everyone chooses, I want to let everybody know I enjoyed developing for this community.
Greetings PsychoGame
Big Update: First alpha release for CM7.2 Samsung Galaxy Y (GT-S5360) Alpha 5
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation instructions are simple:
If you are not working with my kernel:
- Flash my provided boot2.tar file to you're phone using odin (You can download the boot2.tar from here)
If already on my kernel:
- Download the cyanogenmod5.zip file from my dev-host: here (Older releases can be found later in the post!)
- Download the Google Apps from here
- Copy the cyanogenmod.zip and the downloaded gapps file to somewhere on your SD-Card
- Boot in CMW by holding (Volume UP + Select) button while powering up.
- In CWM go to Mounts and Storage first and format /system, /data and /cache.
- Go back to main menu in CWM and choose install zip from sdcard and choose zip from sdcard.
- Apply cyanogenmod.zip
- After installation also apply the gapps-... from here
- Do a wipe data/factory reset from the CWM main menu and reboot the phone
- Be patient while the phone boots for the first time, the phone needs to build up the dalvik cache.
- When fully booted happy testing , and don't forget to report you're findings and bugs.
What works:
- Audio
- Bluetooth (Partially: The device is able to scan for other devices and is also found by other bluetooth devices. Sending files works, receiving does not)
- Camera (Partially: Can take pictures but unable to record film material For more info look at: "known bugs")
- Display "Hardware Accelerated" (Also with some small bugs and glitches, look at "Known bugs")
- GPS
- Input
- Lights
- Network interfaces (Mobile internet)
- Power management
- Radio (Phone "Incoming and Outgoing calls")
- Sensors
- Storage
- Vibrator
- Wifi
What doesn't work:
- Media, media_profiles.xml is included, but the OMX interface still needs to be properly ported which is a WIP.
Known bugs:
- Display: Sometimes there appear to be some glitches. This is known, and due to the usage of a released test binary. I'm currently working myself to reverse engineer the test binary released by BroadCom and the proprietary binary included in the GT-S5360 to come up with a hopefully fixed driver.
- Camera: Still has the white screen bug in the preview of what you're taking a picture of. This is not easily fixable, but will do my best. Movie recording is not yet possible as codecs still need to be included in my build.
Troubleshooting:
Sometimes the Google Apps are giving some troubles with Force Quitting etc., a solution for this is to boot to recovery, clear the cache and dalvik cache and after this do a Fix permissions from the Advanced menu. When rebooting the boot process will take a little longer because the dalvik cache needs to be rebuild.
When anybody has some problems getting it to install through my instructions feel free to ask help in this topic.
Downloads:
- CyanogenMod 7 Alpha 1 Release: http://tinyw.in/VJll
- CyanogenMod 7 Alpha 2 Release: Build Removed (No incoming calls)
- CyanogenMod 7 Alpha 2.1 Release: http://tinyw.in/r4Xs
- CyanogenMod 7 Alpha 2.2 Release: http://tinyw.in/AB92
- CyanogenMod 7 Alpha 3 Release: http://tinyw.in/1G7T
- CyanogenMod 7 Alpha 4 Release: http://tinyw.in/DLUU
- CyanogenMod 7 Alpha 5 Release: http://tinyw.in/dZz0
Changelog for Alpha 2:
Bugs Fixed:
- Not all apps had a ldpi overlay. This has been fixed in the last build I forgot to set the overlay in my full_totoro.mk
- USB Mount didn't work in android. This has also been fixed, I forgot to add the string "file" in the path to the lun file. USB mounting now works as it should work.
- Somebody pointed out that MAC address in the settings wasn't set correct. I researched this problem and it was indeed a bug in my build. This has been fixed now by including the get_macaddrs script in /system/bin. The MAC address wasn't correct because the RIL didn't pass through the MAC address.
Added functionality:
- Compcache has been added to this build. Standard it isn't enabled. To enable this you have to go to: Settings -> CyanogenMod -> Performance -> Compcache. You can choose to allocate 10, 18 or 26 percent. The most recommended value I believe is 18%, but using compcache also has some downfalls. See here for more information: http://en.wikipedia.org/wiki/ZRam
- Wireless Hotspot. This has been tested by me, and I can confirm this function is working perfectly. USB Tethering will be supported hopefully next week.
Changelog for Alpha 2.1:
Bugs Fixed:
- Small fix, I changed the system.prop this week, and in the process forgot to put the ro.telephony.ril_class=samsung option back in the system.prop which results in no incoming calls.
Changelog for Alpha 2.2:
Bugs Fixed:
- Big breakthrough, Headset Support Working. A name in the /system/lib/modules folder of the file brcm_headsetsw.ko had to be bcm_headsetsw.ko. This was why the kernel didn't swich to headset. This was a bug which had slipped my eye as the module name is wrong when compiled from kernel source. This is now completely fixed. And as far as I know this phone doesn't have the Headset Volume Bug. At least not on my phone. Credits go to bluestarfish who pointed this out.
Changelog for Alpha 3:
Bugs Fixed:
- Reverted my system.prop so the tweaks from my first build are included again. Also added some extra tweaks which should reduce the graphics glitches.
- Unsure if GT-S5360L is now able to boot. I haven't got this phone myself, so I can't test it. If it's not working sent me a PM I'll add you on GTalk so we can communicate more easy and fix.
Added functionality:
- Camera: You are able to take pictures, only movie recording is still not possible. This will be a project for later as I'm very busy with bluetooth at the moment.
- Bluetooth: Bluetooth is able to scan for devices and is able to be located by other devices. Pairing or sending from/ to the device is still not possible. Hopefully this will get fixed next week.
Changelog for Alpha 4:
Bugs Fixed:
- The Force Close issues have been resolved. So installing gapps now after CM7 is installed doesn't result in a Force Close error anymore. This is thanks to Gadgetroid.
- Proper apns-conf.xml file has been placed in the /system/etc folder, so this build contains almost all provider APN data now.
- Bluetooth has been made more stable. You can enable bluetooth now without Bluetooth crashing. You're now able to sent files to other devices, only receiving is still not possible. But were getting closer every build .
- Headset: Has been fixed again. My build sources got mixed up a little bit so bcm_headsetsw.so by accident got renamed to brm_headsetsw.so which rendered it unusable.
Added functionality:
- FileManager: The standard filemanager for CyanogenMod has been introduced into this build for everybody who was missing it.
Changelog for Alpha 5:
Bugs fixed:
- The compatibility issue with different basebands and GT-5360L has now been solved.
If you're on alpha 4 you dont need to download the whole alpha 5 again. Only use the boot2.tar provided above to flash the new kernel with Odin.
Credits:
- Myself
- Bluestarfish
- Gadgetroid
- WhiteXP
- Squadzone
- Cyanogen
If you appreciate my work please hit thanks or donate me one beer by clicking the "donate to me" button. I'm investing a great deal of time in this project to make this a very stable product.
Greetings Psycho Game, and have a nice weekend everybody. My sources will be released to my Github next week, so I ask everybody to be patient for that .
Everything below here is old information, you can still read it though to get an idea of the project:
As I already said in another thread about a CWM included kernel I'm also working on a version of CyanogenMod myself with another approach than WhiteXP's build.
The problem is not anymore the availability of the drivers, because BroadCom released their drivers to the public.
In my opinion the next bottleneck is the Kernel. I didn't own a Galaxy Y myself at first (until 2 day's ago), but I recently bought one to make it easier to test different configurations.
My main phone is a Samsung Galaxy S Plus which already has a realy stable CM9 version, but also the kernel is already updated to version 3 from 2.6.35.14.
This is also my goal ultimatly, but the Galaxy Y uses RFS filesystem in combination with FSR. These are closed source modules from Samsung, which make it difficult to update kernels.
There is a known hack that you can alter the version in the makefile of the kernel to 2.6.35.7 while it realy is patched up to 2.6.35.14, but i'm not very fond of such hacks.
I'm a daily linux user already since the year 2000 or so, and build many kernels for Linux computers from source. I can say I have good knowledge of the compilation proces and what's going on in the kernel.
Now back to what i'm doing at the moment:
I already converted the complete galaxy y to EXT4 file system, incl. the EFS partition, and yes I still have my IMEI data etc. so this is considered done [status: Complete]
Next step is getting rid of the RFS & FSR kernel modules, which are proprietary (RFS has been removed, only FSR remains for later. [status: WIP -> stalled]
At the moment I'm busy updating the kernel to version 2.6.35.14 the proper way, so I have a stable base kernel to build CM on [status: Complete]
After this I will add CWM recovery to the updated kernel, and make sure everything works as it should, like ADB in recovery mode, formatting, and all these things. (Only ADBD has to be fixed) [Status: 99% Complete]
When CWM recovery functions as it should work, the proces of building CWM into the Galaxy Y can begin [Status: WIP -> Stalled until kernel stable].
CM already compiles fully without much warnings, but still isn't ready to be released until all predecended steps have been completet.
At the moment I'm also uploading all sources of the kernel into github, so everybody can revieuw the proces i'm doing, and also point out mistakes maybe and give suggestions.
Update 1: Yes already an update. It's more difficult to work you're way around the FSR kernel modules. What I now want to do is convert the BML block layer (which uses the FSR modules) to MTD which is an opensource version of a Flash Transition Layer. I know this is possible, because it's also done on the Samsung Epic 4G. The only downside of this is that I cannot use the promised ext4 anymore on the final product, but I'm forced to use YAFFS2 filesystem (which is luckily also opensource).
Update 2 (1 Feb. 2013): Hello everybody. After almost a week I have another update on the Kernel modifications. I stalled the removal of the fsr module parts for now and started with the inclusion of the ClockWorkMod recovery in the kernel. The way I included the CWM recovery is other than Merruk and WhiteXP did. I left the stock recovery in place, and added the CWM on top of it. Standard it boots in the CWM recovery, but if for some reason you would need the stock recovery you can also call it. Just by leaving a file called .stock_recovery in the root of the /cache partition. So in short it contains 2 recovery's in one image. To make it all fit the InitramFS and kernel have been compressed using the lmza method. This allows for a smaller resulting boot.img file, but comes with a little extra boot time. When android has booted you don't notice any difference. Appart from this it's a stock kernel with ext4 included, and the rfs filesystem modules removed, so it's a ext4 kernel only! The completely changed initramfs can be found on my github over here: https://github.com/PsychoGame/totoro_initramfs_files.git so everybody can study what I've done.
Update 3 (8 Feb. 2013): Hello everybody. Again an update of my kernel, and a weekly build to test in the weekend . There have been some changes in this release, the most major change has been that the kernel has been patched from 2.6.35.7 to 2.6.35.14. Also a little change in the recovery.fstab stopped the nandroid backup from making a useless recovery.img. Also I now know for sure that it's possible to do a full nandroid restore. As long as the FSR modules still function also the boot.img backup will be restored. The only thing still not working is the Android Debugging Bridge in the recovery self. This seems to be a harder to tackle problem then I thought before. It seems that adbd is not working properly so it doesn't see the device. The new kernel can be obtained from here:
boot.tar (08/02/2013)
With this new 2.6.35.14 kernel you also need to have all other updated compiled modules which are available here:
Version14Modules.zip
These files should be placed in /system/lib/modules
This is not a CWM installable package at the moment because I'm a little bit busy at the moment, so this means you have to copy the files manually to the directory.
I recommend using ES File Explorer in which you need to have full read/write acces to the disk.
When anybody needs some extra help please let me know.
There are two small bugs at the moment:
- ADB still not working inside recovery
- Sometimes the touchscreen has a little problem getting out of it's sleep state. I don't know how to describe it, but will look into this problem very soon. It's not a harmfull bug.
Question to other developers: Hopefully there are other kernel developers among us as well. If you think you can contribute to this as well, then please PM me. At the moment I hope everyone together including myself will look into implementing MTD into out device.
The kernel source is uploaded to https://github.com/PsychoGame/android_kernel_samsung_totoro.git Updated
This is a little update on the things I have in mind.
If you like it, please post a comment, that also lifts my spirit in the lots of things that have to be done.
Installation Instructions
It's wise to make a EFS backup first to be sure you're IMEI data etc. is safe at all times. It's not only wise for this project but other projects as well. A good tool for this is Galaxy ToolBox. This tool saves the backup on you're SD card which you should keep safe on you're computer
Here are the installation instructions of the first kernel release:
Known bugs:
- Adb is not working in the CWM at this moment. I'm pretty sure it's a simple problem, but will solve that later on. It's not very annoying as anyting else is in my opinion functioning.
In my walktrough I will cover the steps for installing my kernel on a fresh install of Android.
There are a ton of walkthroughs already on the subject of flashing android to the Galaxy Y (GT-5360) through odin.
I didn't test it yet on a working installation, but I'm pretty sure this should work in there also.
Step 1: First of all, download the needed files
- cwm-madteam-galaxY.zip
- boot.tar (01/02/2013)
- boot.tar (08/02/2013)
- Version14Modules.zip
- Odin 1.85 Used
- update-signed.zip (Su Binary)
Step 2: Make a nandroid backup of you're device using Madteam's ClockWorkMod.
Step 3: Enter download mode (Holding down button + Select) + Power button until the phone seems to boot. In download mode flash my supplied boot.tar by putting it in the PDA field in Odin. No .pit file is required, and just leave anything default and click the (flash button).
Step 4: Enter CWM recovery (holding up + select) + Power button until the phone boots, and go to mounts and storage and one by one do (format /data, format /system and format /cache).
Step 5: Also in the menu Mounts and storage click on mount USB storage while the mobile is connected to the computer with the USB cable, or use a cardreader to open you're miniSD card. On the miniSD card there is a folder which is called clockworkmod which contains the backup you just made in the folder backup. Here you should change as an example (system.rfs.tar to system.ext4.tar), and also do this for the data.rfs.tar. Also inside nandroid.md5 these filenames have to be changed accordingly to resp. system.ext4.tar and data.ext4.tar.
Step 6: Reboot the ClockWorkMod Recovery and in the backup and restore menu click on "advanced restore" and choose you're nandroid backup. Choose only to restore (System and Data.)
Step 7: Just reboot and enjoy you're Galaxy Y with CWM included in kernel. As far as I tested everything is working as it should be, if you come across something that doesn't work please report this.
Step 8: Copy the modules supplied in Version14Modules.zip to /system/lib/modules/
If you flashed a fresh android rom you should Root it again using the update-signed.zip I supplied above this article (Before you install the update-signed.zip you have to mount the /system partition in the "Mounts and storage menu" first the mount is forgotten in the installer script.)
I hope you'll enjoy this little beginning, there's a lot more to come. I'll be gone for the weekend, so after the weekend I will be able to respond to any bugs and problems everyone came across.
Greetings
Psycho Game
gud luck !!!!:good: buddy
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
I smell a new developer here.. Or maybe a reincarnation of maroc
Good luck bro!
Sent from my GT-S5360 using XDA
:good:
:highfive:
keep it up bro..
reserved
great initiative
really appreciate your efforts - good luck and go on !
hell_lock said:
I smell a new developer here.. Or maybe a reincarnation of maroc
Good luck bro!
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
i think reincarnation of maroc....
good luck bro...
carry on ur work..
good luck bro, i can be pray for you
Thanks for the positive comments already, I will try to be as open about the development as I can.
By this I mean that I try to explain every step I do, in my github, but also in the forum so that somebody else could reproduce all the steps I did to create the same thing as me.
So also people beginning with development can try to understand what I'm doing.
Also I will keep this thread as updated as possible.
Greetings PsychoGame
PsychoGame said:
... I will try to be as open about the development as I can.
By this I mean that I try to explain every step I do, in my github, but also in the forum so that somebody else could reproduce all the steps I did to create the same thing as me....
Click to expand...
Click to collapse
I am as excited about that as I am the ROM itself, I will be following this with interest!
Thanks for your efforts so far and for all the work you will put in to realise this project in the future :good:
Stokey
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
Subscribed +2
Awesome work
I expect more from u :thumbup:
jasonxD Leveled to 2
Just wanna ask one question -
Isn't kernel 3 made to make it compatible with ICS/JB ?
If yes, then isn't White's kernel based on kernel 3 ?
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
Ramdisk makes ics/gb/jb boot.. U dont need 3.x kernel for that.. Just make some changes in stock ramdisk and u r good to go.
Sent from my GT-S5360 using XDA
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
I like thread.
I subscribe.
---------------------------------------
Questions? Better go to [Help Thread] Ask ANYTHING! xD
Gamer R said:
Just wanna ask one question -
Isn't kernel 3 made to make it compatible with ICS/JB ?
If yes, then isn't White's kernel based on kernel 3 ?
Click to expand...
Click to collapse
No, ICS for the Samsung Galaxy S Plus was running on the 2.6.35.14 kernel at first.
Only there was a big interest in using kernel 3.0 because this contains many new features and improvements over 2.6.35.14.
So that's why they ported the 3.0 kernel.
White's kernel is also based on the 2.6.35.7 kernel which is used by samsung.
On this moment the Galaxy Y is still limited this kernel serie because the use of RFS and also the FSR (Flash Transition Layer) which are both closed source.
Getting rid of RFS isn't a big deal, that's a matter of converting all the filesystems to EXT4.
The problem is getting rid of FSR, this is a module that's needed to make the NAND accessable for the kernel.
So if you want to break free from the 2.6.35 serie of the kernel you need to use opensourced modules.
As I already found out this isn't very easy to do.
An opensource version of a "Flash Transition Layer" is MTD.
But to use this you have to enable the MTD support in the kernel, and convert the BML to MTD.
That is what I'm currently trying to do.
The problem is that the promised EXT4 support for the /data, /system, /cache, and other phone partitions will not be possible anymore.
In that case I'm forced to use YAFFS2, which is also an opensource filesystem luckily.
Greetings
Psycho Game
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
PsychoGame said:
No, ICS for the Samsung Galaxy S Plus was running on the 2.6.35.14 kernel at first.
Only there was a big interest in using kernel 3.0 because this contains many new features and improvements over 2.6.35.14.
So that's why they ported the 3.0 kernel.
White's kernel is also based on the 2.6.35.7 kernel which is used by samsung.
On this moment the Galaxy Y is still limited this kernel serie because the use of RFS and also the FSR (Flash Transition Layer) which are both closed source.
Getting rid of RFS isn't a big deal, that's a matter of converting all the filesystems to EXT4.
The problem is getting rid of FSR, this is a module that's needed to make the NAND accessable for the kernel.
So if you want to break free from the 2.6.35 serie of the kernel you need to use opensourced modules.
As I already found out this isn't very easy to do.
An opensource version of a "Flash Transition Layer" is MTD.
But to use this you have to enable the MTD support in the kernel, and convert the BML to MTD.
That is what I'm currently trying to do.
The problem is that the promised EXT4 support for the /data, /system, /cache, and other phone partitions will not be possible anymore.
In that case I'm forced to use YAFFS2, which is also an opensource filesystem luckily.
Greetings
Psycho Game
Click to expand...
Click to collapse
Very complicated it is..
Sent from my GT-S5360 using XDA
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
I love u
Phone Slow? go ------>HERE<------
Ubuntu phone OS announced
what do u think share your thoughts --->HERE<---
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
--Sent from the future with a galaxy s4 like a freaking BAWS--
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
PsychoGame said:
No, ICS for the Samsung Galaxy S Plus was running on the 2.6.35.14 kernel at first.
Only there was a big interest in using kernel 3.0 because this contains many new features and improvements over 2.6.35.14.
So that's why they ported the 3.0 kernel.
White's kernel is also based on the 2.6.35.7 kernel which is used by samsung.
On this moment the Galaxy Y is still limited this kernel serie because the use of RFS and also the FSR (Flash Transition Layer) which are both closed source.
Getting rid of RFS isn't a big deal, that's a matter of converting all the filesystems to EXT4.
The problem is getting rid of FSR, this is a module that's needed to make the NAND accessable for the kernel.
So if you want to break free from the 2.6.35 serie of the kernel you need to use opensourced modules.
As I already found out this isn't very easy to do.
An opensource version of a "Flash Transition Layer" is MTD.
But to use this you have to enable the MTD support in the kernel, and convert the BML to MTD.
That is what I'm currently trying to do.
The problem is that the promised EXT4 support for the /data, /system, /cache, and other phone partitions will not be possible anymore.
In that case I'm forced to use YAFFS2, which is also an opensource filesystem luckily.
Greetings
Psycho Game
Click to expand...
Click to collapse
The amount of ur knowledge in this kind of stuff is TO DA*N HIGH
Thanks for ur hard work...
jasonxD Leveled to 2
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
jasonxD said:
The amount of ur knowledge in this kind of stuff is TO DA*N HIGH
Thanks for ur hard work...
jasonxD Leveled to 2
Click to expand...
Click to collapse
Maroc 2.0
Phone Slow? go ------>HERE<------
Ubuntu phone OS announced
what do u think share your thoughts --->HERE<---
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
--Sent from the future with a galaxy s4 like a freaking BAWS--
IMHO most of problem from cm 7 (source) porting come from vendor's proprietary library. i don't think putting effort to porting sgy kernel to 3.x version is worth it. fs and partition only 'small' thing to do. you still have to port gpu, camera, baseband, and other modules which is more difficult.
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.