No matter what I tried via kernel modules (mmcfix), I was not able to fix the issues with writing to certain sdcards under 2.6.29 kernel (of our 'vulnerable' recovery that we use to start OpenRecovery).
So I decided to give a try to 2ndboot from 2.6.29 to 2.6.32 kernel under recovery.
Here is a version of OpenRecovery 1.46 that runs under custom 2.6.32 kernel using 2ndboot:
Download: http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OpenRecovery_2ndbootOR_v1_2.zip
Fixes:
- all issues with writing to some sdcards under recovery ("DMA transaction error with device 61" in dmesg)
- missing huge_file feature of ext4 filesystem under recovery
New features:
- battery charging under recovery
Please let me know if you encounter any problems.
The start of OpenRecovery with 2ndboot takes a bit longer, so be patient.
You can see a phone reboot during the start of OR under certain conditions - it's intentional, just wait, the OR will start automatically afterwards.
Kernel source: https://github.com/nadlabak/kernel/tree/recovery
UPDATE 30.01.2013
- prevent watchdog reboot (by automatic reboot of recovery if it was not started via /cache/recovery/command)
- use 10% battd for better compatibility with 3rd party batteries
- modversion set to 2ndbootOR v1.2
UPDATE 03.11.2012
- kernel and 2ndboot files updated (2.6.32.60, L2 cache enabled etc.)
- patches by justcsdr from issue #773 included (power off, mass storage with complete access to all sdcard partitions etc.)
- modversion set to 2ndbootOR v1.1
UPDATE 26.09.2012 (2)
- fixed linker issues - IMPORTANT! please update from the previous version
- modversion set to 2ndbootOR v1.0
UPDATE 26.09.2012
- battery charging and status display added
UPDATE 23.09.2012
- workaround for occasionally non-working adb
- clean kernel build (no change in functionality)
UPDATE 21.09.2012:
- fixed backup of logo, bpsw, lbl and devtree partitions
- added 2ndboot splash screen
Seems to be working for me. No issues
Sorry for the dumb question, but what is the purpose of this OR?
Erovia said:
Sorry for the dumb question, but what is the purpose of this OR?
Click to expand...
Click to collapse
Read the first post...
LuigiC6 said:
Read the first post...
Click to expand...
Click to collapse
Oh god, i really should go to sleep..
By the way, i tried it, works fine, no issues so far. :good:
Works great, slowest but for me without issues
Now my nandroid backups are not hanging on system dump anymore. Great work man. Thanks a lot.
Update:
- fixed backup of logo, bpsw, lbl and devtree partitions
- added 2ndboot splash screen
Download: http://d-h.st/AeS
Kabaldan I have one question.
Is there possibility to run rom on this second kernel? Maybe this is the way to make kernel more complatible for rom
Just a suggestion/question - can't you change version numbers so not to confuse new 1.46 with old 1.46?
DJPatriX said:
Kabaldan I have one question.
Is there possibility to run rom on this second kernel? Maybe this is the way to make kernel more complatible for rom
Click to expand...
Click to collapse
DJ,
As far as I understand, Rom already runs on this "second" kernel. This second kernel is the Motorola Froyo Kernel, recovery was using an older kernel to boot. Both are signed by motorola, so, it is not a custom kernel.
It actually is a custom kernel (2.6.32.59), not signed by Motorola (the last kernel released by Motorola for Milestone is 2.6.32.9 from early 2011).
Check 'cat /proc/version' and see when it was compiled .
You could even use swap with this kernel, if it would make sense under recovery .
But you're right that it's not the main point - this OR release is about recovery to be run under 2.6.32 kernel to achieve reliability in sdcard operations, which was not possible under 2.6.29 kernel of our old recovery.
The problem with 2ndboot (or kexec) method to run custom kernel is that there is no known way to get the Wrigley 3G BP working afterwards (BP = Baseband Processor - the gsm/umts phone features).
This is fine under recovery as the phone functionality is not needed there.
But there's no known way to run a custom kernel on Milestone (or any other Wrigley 3G BP phone such as Defy(+), Milestone 2 etc.) while the device would still be able to function as a phone.
Thanks for the update. Seems to be working fine. Console, nandroid backup/delete (haven't tried restoring yet), scripts...
Btw., indeed very nice 2nd boot splash image
Thank you
Thank you for this update, everything is working just fine!
the dl-link does not work for me. could you reupload it, please?
As dev-host seems to be off-line, I've uploaded new update to issue-tracker site
http://code.google.com/p/cyanogenmo...nRecovery_v1_46_SHOLS_2ndboot_2_6_32_kern.zip
UPDATE 23.09.2012
- added workaround for occasionally non-working adb
- clean kernel build (no change in functionality)
Thanks for the reply. I've seen some issues with radio an other roms who runs on "second kernel". Now everything is clear 4 me.
Cheers
battery charging under recovery added
Link
That is amazing... Thank you.
Btw., you might have forgotten a link http://code.google.com/p/cyanogenmo...1_46_SHOLS_2ndboot_2_6_32_Charge.zip&can=2&q=
New version uploaded:
http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OpenRecovery_2ndbootOR_v1_0.zip
It contains important fix for a nasty bug introduced with the addition of battery charge support. Please update.
Related
data2whatever v0.2
UPDATE: For the new test version of v0.3 and v0.4 look at the end of the post.
Features:
- Supports: Ext2, Ext3, Ext4 (and if kernel supports it: ) btrfs, ReiserFS
- Supports loop device as optional addon (as siberes data2sd)
- Flashable zip for many app2sd ROMs (no long setup required)
- It does a e2fsck (disk check) on every boot and creates a logfile on the sdcard (/sdcard/e2fscklog.txt)
- looks nice if you do a logcat on boot
- no "settings lost on reboot" bug like in my old or siberes script
- changes the scheduler for the sd-card and internal to noop for better performance on sd.
- Nandroid Backup of EXT2/3/4 external with AmonRa 2.0.0.1 or any clockwork recovery.
- Removes the common app2sd scripts on its own
Requirements
- A second partition (same as app2sd - Min 512 mb - 1024mb is highly recommended - max 2048 MB or there will be issues with market) in any format (as long as the kernel supports - ext2/3/4 support is default in most kernels - Ext4 or ReiserFS is recommended).
- An app2sd or non app2sd ROM (data2sd versions wont work) (this SHOULD work with most or at least many ROMs . Roms that are confirmed to work can be found in the post below. Please report to me it it works or not so i can update this thread. If it doesn't work i try to make it compatible asap. )
Installation
1.) Full wipe (at least needed on first installation)
2.) Flash the app2sd Version of the ROM of your choice
3.) DONT REBOOT
4.) If you rebooted then start over at 1.)
5.) flash the attached "data2whatever.zip"
6.) now reboot
ADDITIONAL INFO: Even without "life on the edge" you should watch the first 4 "don't"s of "life on the edge". The normal script use the same disk safety methods as NTFS on Windows or EXT4 on linux. But as you know you shouldnt just switch off the computer because there can still be issues in very rare cases. Reboots with tools like "snqs power menu" is the same as a batterypull (or pulling the ac plug on PC) and this isn't good in general (and this also applies for using it with app2sd). If you want to go to recovery just make a normal shutdown and switch the phone on with "volume down" button pressed.
Optional life-on-the-edge add on
EDIT: Life on the edge causes reboots. Don't use it for now.
This patch has the same effect as sibere's and ownhere's script (loop device - the way ownhere does in v4 doesnt work though). Other than those scripts it this addon doesnt need any repartitioning or other setup (like FAT or a third partition) and can simply be installed or removed with a flashable zip. All you need for this is a normal ext 2/3/4 partition (as above ^^). Ext4 is recommended for this (as above) since it is the fastest of those 3. This patch is more risky than normal ext3/4 considering the possibility of data loss. If you want to use this add-on you should watch the following (this also applys to ownheres and sibere script and is NOT more risky than their scripts):
- DON'T use the reboot of snq's powermenu (or any other reboot app)
- DON'T use anything in the "ROM Manager" that makes it reboot.
- DON'T do adb reboot / abd reboot recovery / adb reboot bootloader
- DON'T pull the battery while the phone is on (this should be obvious)
- DON'T remove the "sync" mount options for the Quadrant "boost" (this is a fake boost anyway)
All of this is like a powerloss for the sd-card and has a high change of data corruption.
From my test with this i give you an estimate what can happen if a powerloss occurs or any of the 5 points above happen:
- 50% general chance of corruption that will be autofixed on boot (not a problem)
- 10% chance of forcecloses after reboot of some apps (this can be fixed by deleting the app data or restoring it with titanium (or other) backup)
- REALLY tiny chance (didnt happen for me in over 40 "simulated" powerlosses) that partition gets corrupted (needs complete repartitioning of the microSD so all data on it will be gone then)
As long as you watch the 5 points above and as long as you don't drop the phone and the battery jumps out this will be safe.
Installation of the addon:
- Flash the "life-on-the-edge.zip" any time after you installed "data2whatever".
Installation of the addon:
- Flash the "life-on-the-edge-UNPATCH.zip" any time after you installed "data2whatever" and the addon. (this will revert back to the normal script)
Personal remark: While this is a improvement over normal ext4 it is not the "holy-grale" of a data2sd lag fix. I'm not using this myself and use a ReiserFS as second partition instead which is more safe and completly feels the same as a "loop" device considering performance.
Further Plans
- Changes for the mount options of the internal YAFFS2 Partition to optimize the speed of the "dalvik-cache" (have to look into YAFFS2 what can be done)
- Make Roms that doesn't work yet compatible to this
Thanks:
- cyanogen who made app2sd+ in the first place.
- sibere and ownhere who started all the data2sd.
- supercurio and Unhelpful of SGS' Voodoolagfix (#Project-Voodoo on freenode) for their helpfull script tipps.
- Coutts99 and Neophyte for their Kernels.
- woti23 for all those test's in this thread.
- All devs of XDA in generall for all this nice stuff that is done here
UPDATE: Test version of v0.3 and v0.4:
BOTH NEED A FULL WIPE BEFORE INSTALLED FOR THE FIRST TIME.
Please make a logcat of the first boot. This can help me to find possible issues.
This version now checks if your second partition is aligned and if not it will ERASE it and recreate it aligned. You will find more info about alignment later here (in the meantime you can google "ssd alignment" to get some info).
WARNING: THIS WILL ERASE THE SD-EXT PARTITION IF IT IS NOT ALIGNED. On top of that there is a little risk that it messes up the partition table. Although i made a lot of test with this and added busybox to assure compatibility there could still issues with it. If something should go wrong in recreating the partition you may have to REPARTITION the COMPLETE Sd-card. So make a BACKUP OF ALL YOUR DATA ON THE SD before you test this .
Additional info: Don't let yourself get confused by the many deleting messages on install. The update script tries to erase:
- busybox (newest version gets installed afterwards)
- 4 different versions of app2sd scripts
- dalvikcache2cache script
- the 3 binaries included (e2fsck, tune2fs, mkfs.ext4)
- 3 possible symlinks for the binaries
- mtab file
Everything that is erased gets either installed afterwards (busybox, etc ...) or isn't needed (app2sd scripts).
Please post the alignment log if you testet this. This log can be found on the sdcard ( /sdcard/sd-ext-alignment-log.txt).
==================================================================================
changelog
0.4d test release
- If the partitions gets aligned it will be formated with ext3 now instead of ext4 so it works with ROMs without ext4 kernel support.
0.4c test release
-fixed a rare issue that could happen on alignment if a partition has set the bootflag.
v0.4b test release
- fixed and Oxygen 2.0 RC4 related issue:
- renamed the "99complete" to "991complete" to prevent similiar issues on other AOSP ROMs that use individual properties.
v0.4 test release
- dalvik cache is now left internal. This should spread i/o and thus speed things up a bit.
- change scheduler to "deadline" if the kernel supports it
- changed logging: One file (data2whateverlog.txt on sdcard) for alignement and fsck with more info (thx moebius83)
- In case there is a swap partition (mmcblck0p3) this will also get aligned.
v0.3 test release
- this version will now recreate your sd-ext partition if it is not aligned (format: ext4)
- fixed the mtab error that could cause issues in some cases
- added busybox v1.17.2 to assure compatibility.
- added support for swap partition (if kernel supports it and partition 3 exists)
- removing more stuff on install (to make sure there are no old symlinks)
0.2e
-fixed an issue caused by the s-off fix.
0.2d
-fixed the cm6 fix
v0.2c
-fixed a bug that made this only work with S-OFF. (i totally forgot that system can't be mounted rw as default )
v0.2b
- fixed a typo of the last fix . This could have caused issues on leedroid. (thanks woti)
- added the patch for CM6 (thanks iinga)
v0.2
- fixed a syntax error making the script not working at all
- fixed a bug that would have occured on leedroid if it would have worked ^^
------------------------------------------
data2whatever v0.1 (dec 23.)
-completly rewrote of the data2ext script
Confirmed to work with:
- LeeDroid 2.3b A2SD (life-on-the-edge may not work)
- MIUI 0.12.18 R3
- Gingerbread Oxygen RC2
- Ginger Villain ROM
- CM6
- MidianUI r2e
- Desire stock (with init.d support enabled through ramdisk - more info)
Don't work yet:
(about HD roms in general. They will be the ones with most issues because they use external space for system stuff because of the size of the HD Rom - ill still try to make my script work with them)
- robocik's Z v06
- ReflexTSenseHD 1.5
nice work man
im using miui currently and it hass 04apps2sd instead
is this the same thing?
Very nice work.... and it kinda confirmed what i've been thinking all the time about it. Ppl thinks it speeds up your phone! Still this is of very good use if u want alot of space for apps
Rastaman-FB said:
nice work man
im using miui currently and it hass 04apps2sd instead
is this the same thing?
Click to expand...
Click to collapse
Check my 2nd post. I just edited it.
I love you.
But still the best way is to integrate it w/ ROM
where is the download link
ghmail2 said:
where is the download link
Click to expand...
Click to collapse
This
10char
Rafa91 said:
This
10char
Click to expand...
Click to collapse
a joke?
ghmail2 said:
where is the download link
Click to expand...
Click to collapse
+1
10char
Go here ->http://forum.xda-developers.com/showpost.php?p=9697369&postcount=7229
but i don't know if it's RCMixHD specific.
+1
Is it a joke or not?
ghmail2 said:
where is the download link
Click to expand...
Click to collapse
D'oh .... sry ... when i finished the post i went eating ... i had the fealing i should have checked it again
just wait omg ...
anko184 said:
Go here ->http://forum.xda-developers.com/showpost.php?p=9697369&postcount=7229
but i don't know if it's RCMixHD specific.
Click to expand...
Click to collapse
This one also works. All 3 Roms i posted use the same script
So generally, it should work on any rom with CM6/AOSP based A2SD script? Mkay...
ghmail2 said:
a joke?
Click to expand...
Click to collapse
It wasn't there before xD
Didn't get to experimenting with btrfs today, will test it tomorrow
Sent from my HTC Desire using XDA App
@melethron great work man, but I will remain to my opinion that data2sd(ext) is bad for so many reasons. But it is good to have choices.
But nevertheless your work is apreciated
Hi, having small issue here, trying to install this on the baadnwz rc2 hd rom, following all the steps, when i finally restart and everything boots up as it should, it freezes on the white htc screen before it asks you to select your network provider and force closes.
Anyone have a solution?
PRIME! v1.6
This is a custom rom for the Asus Eee Pad Transformer TF101
Special thanks to: Hacre | afm | MoDaCo | dc13 | supercurio | Bumble-Bee | RaYmAn | netarchy | Vividboarder | CurtisBeef
This rom is a work in progress and all feedback is appreciated. It has everything that the stock rom has to offer with a few modifications designed to provide a better user experience. As always whenever installing any rom, please ensure that you are fully aware of what you are doing as no one enjoys seeing their pride and joy end up bricked or stuck in a boot-loop (although these are easily fixed if either were to happen so don't panic in the event that something goes wrong).
Instructions:
1. Copy ROM to sdcard
2. Verify the MD5 of the zip on the sdcard, DO NOT FLASH IF THIS DOESN'T MATCH THE MD5 UNDER THE DOWNLOAD LINK!
3. Boot into clockworkmod recovery
4. Take a nandroid backup (optional but highly recommended)
5. Install the ROM
6. Reboot and wait... The first boot may take a while...
7. After a successful restart, you can change one of the power mod or remove it if desired.
Rom Details:
Android 3.1
GPS - V1.3.2
WiFi - V5.1.50
Bluetooth - V6.17
Kernel - 2.6.36.3-g3eb19ec
Build - HMJ37.prime_epad-1.6-20110716
MobileDock - EP101-0209 (Prompts for install after first boot if required)
See the second post of this thread for the changelog
Known Issues:
In Prime 1.6 if you flash a custom kernel you may experience a slight drop in performance due to a change in the way Prime optimises I/O performance.
Install this patch in CWM to resolve the issue. - http://kan.gd/uij - This has been fixed in 1.6r2
Battery History option in Spare Parts triggers F/C
Download Links: - Main Rom (You need this one)
PRIME! v1.6 (HMJ37.prime_epad-1.6-20110716)
Alternate Link
MD5: 574d34b0923cd5ef03762ae5357acc93
Torrent Link - Thanks Aligatro
NVflash version now available: http://kan.gd/up2
Uncompress the image files into a folder and see Androidroot.mobi for details on how to flash.
Kernel - Only required to return from other kernels
Prime_v1.6_Kernel.zip
Alternate Link
MD5: d45a27115e2ac0c22659a131abb075bc
Previous versions:
PRIME! v1.5 (HMJ37.prime_epad-1.5-20110626)
MD5: 13a0923e7ad178de2ae7636cd0f628a3
Power button mods
These mods give you either a reboot or reboot to recovery option when you long press the power button.
REBOOT power button mod
Alternate Link
MD5: fc17f4bbbd37aa6dbf163604484bb3ba
RECOVERY power button mod - (included in rom)
Alternate Link
MD5: bb8b361f024246f0a8f06a06f2ee47ed
REBOOT and RECOVERY power button mod - (there is no shutdown option with this mod but some people dont ever need to)
Alternate Link
MD5: d7d7e2abca184dc59e1b912183539b3a
Changelog:
v1.6r2
Fixed I/O Performance
v1.6
Based on 8.4.4.11-20110711
Wifi enabled for chan's 12 and 13 - see 2nd post for instructions
Power mods translated to most languages thanks to CaNsA
Bash 4.2 binary added
Sqlite3 binary added
Google Maps updated to 5.7.0
Further optimisation of scripts to improve loading times
Power mods updated
sh linked to busybox to enable colour and tab completion
v1.5
Hybrid of 8.4.4.5 and 8.4.4.7 releases
Asus updated apps for the 8.4.4.7 release are inlcuded except for Splastop Remote wich was generating F/C's
Custom kernel compiled from asus source with built in cifs/tun support
Voodoo sound driver v1 kernel mod (Thanks to supercurio)
Added init.d scripts with working cron scheduler
Various performance tweaks via init.d and kernel mods
Added Terminal Emulator
Google Maps updated to 5.6.0
Updated SuperUser and su
New custom busybox 1.19.0
Ad-hoc wifi support via wpa_supplicant
Added InputSetting app to allow disabling of the touchpad tap to click (Thanks to Netarchy and Vividboarder)
Reboot to recovery mod installed by default but this can be changed or removed as desired. See the download section for details
v1.4
Based on 8.4.4.5-20110527
Insecure Boot thanks to Bumble-Bee
The First HC3.1 fully deodexed, optimised and zipaligned rom
CIFS and TUN modules added
Updated boot animation for HC3.1 thanks to Curtisbeef
Google Music updated to 3.0.1
Google Maps updated to 5.5.0
Power button mods available - see download section
v1.3r2 - bugfix release
WW version now based on UK OTA Update 8.2.3.13-20110511
Corrected issue with Google Talk F/C
Corrected issue with Double Tap not producing a full stop
Modified image in MyGazine App - feedback appreciated
v1.3
Based on US OTA Update 8.2.3.13-20110511
Deodexed and Optimised by dc13
Bluetooth and Wifi updated
Asus Keyboard Dock FW included for optional flashing (TF101-EC-0209)
New Boot animation thanks to Curtisbeef
v1.2
US and WW versions now available
The Transformer's first custom kernel with CIFS/TUN/NTFS compiled in - Thanks to afm, RaYmAn and Bumble-Bee for their efforts.
CifsManager
Google Maps updated to 5.4.0
Google Books added from stock US rom
SDCard Speed Fix thanks to brainmaster
v1.1beta2
Added Google Maps 5.3.1
Further optimised system apps, feels much smoother.
Removed DMClient (Asus FOTA Updates)
v1.0
Superuser
Busybox
Spare Parts
Ext4 performance enhancements
About wifi support for channels 12 and 13 in Prime 1.6
When set to US mode the Transformer does not see chans 12 or 13. This is the default behaviour on US and WW roms. In EU mode these channels can be used.
To allow the TF to set EU mode please wait until three minutes pass on the first power up and then restart your transformer. This is after fresh install or factory reset.
US/EU mode can also be toggled by running /system/etc/setwifi.sh from a cli and you can check whether you are in EU or US mode by looking at the flag in /data. If this is removed the TF will set EU mode automatically on next reboot.
Strange codes appearing in Dos windows using ADB
The reason you see are seeing strange stuff in ADB with windows is because the dos prompt cannot interpret the colour codes. You have two solutions.
1- enable colour support using this - http://adoxa.110mb.com/ansicon/index.html
2- disable colour support...
Code:
alias ls='ls --color=never'
Spare Parts, newest OTA - sounds like fun, will try when I get home
Working well so far, installed over the top of dc13s rom with no issues.
Cheers
I installed this fine thanks loads.
Would be nice if the asus update reminder could be taken off. I keep getting prompted to download it. I saw the thread about removing it but would rather a more permanent solution without the use for 3rd party apps.
Will give it some testing tonight
be_vigilant said:
I installed this fine thanks loads.
Would be nice if the asus update reminder could be taken off. I keep getting prompted to download it. I saw the thread about removing it but would rather a more permanent solution without the use for 3rd party apps.
Will give it some testing tonight
Click to expand...
Click to collapse
The Update tool is coming out of my next rom.
Will there be a rom that can be applied over the 20110423 rom update?
NMCBR600 said:
Will there be a rom that can be applied over the 20110423 rom update?
Click to expand...
Click to collapse
Not until there is a way to get custom recovery running, there is an exploit being developed but it was based on the first update. It's currently being tested against the second update (20110423).
Roach2010 said:
Not until there is a way to get custom recovery running, there is an exploit being developed but it was based on the first update. It's currently being tested against the second update (20110423).
Click to expand...
Click to collapse
there's a new root method in the root thread, FYI
New version out...
Also I must ask, does this keep my own apps and settings?
Yes, just flash and reboot and you won't lose your stuff.
For peace of mind though you should take a nandroid backup first, it's good practice to always do this before flashing any rom.
Oh I know, I've been flashing ROMs on my HTC hero since day 1
has this been tested with a US transformer yet?
I have only got a UK device to test my roms on but if you want to flash it and provide feedback then that would be greatly appreciated.
seshmaru said:
Oh I know, I've been flashing ROMs on my HTC hero since day 1
has this been tested with a US transformer yet?
Click to expand...
Click to collapse
Works fine.
corruptz0r said:
Will this work on US TF101's?
Click to expand...
Click to collapse
read the post above yours.
Also testing it myself now.
Just flashed it over stock US version, works fine so far.
Hmm. As soon as I try to start the camera I get a reboot. Using a US Transformer
dictionary said:
Hmm. As soon as I try to start the camera I get a reboot. Using a US Transformer
Click to expand...
Click to collapse
Confirmed here too.. UK
Have removed quite a few apks from system though.
Hmm, my camera sorta works, I get a nice green picture fom the back camera and the front one is ok. I'll do some testing.
[INTRODUCTION]
This ROM is based of the joined effort of a couple of devs (Ejtable, Scanno and Brucelee666) who are working on getting JellyBean working for our device. As soon as JellyBean is getting stable, my goal is also to put everything on github, just like i did with VegaCream. This way other devs can also work on this.
Please remember that I, ejtagle and brucelee666 are *NOT* professionals and do this in our spare time. We all have full time jobs and a family. So be happy that there is an Android ROM based on Android 4.1.1 / JellyBean for a device that was sold with Android 2.2 and never had an update.
We do our best to make this ROM as good as possible. With VegaCream we gave you a ROM that gave a new life to your tablet and unleashed its full potential. But we are not wizzards and there might be problems that we cannot solve or do not have time for.
[SPECIFICATIONS]
This ROM is based on AOSP 4.1.1 and the device config made by Ejtagle, brucelee666 and myself.
- INT2EXT+ (Needs a correctly partitioned SDCard)
- zRAM
- DPI is set at 120dpi
- Default JellyBean Launcher installed
- Apex Launcher installed
- Filemanager installed
- Terminal installed
- Google Apps is installed. This means that the Google base is installed and all the apps that are available in the Play Store are not installed (i.e. GMail, Maps)
- All languages that are available in AOSP are included
- Partition layout is the same as VegaCream / VegaICS beta1 / Modded stock
- /system/app, /system/lib, /system/fonts, /system/framework and /system/usr are Squashfs filesystems.
[INSTALLATION]
There are 2 methods of installation. There is a CWM recovery flashable ZIP and a NVFlash file.
I realy recommend flashing VegaBean the first time with the NVFlash version.
Before installing any version, you have to make sure that you have a SDCard that has the correct partition layout:
- First partition is a primary partition formatted as FAT32
- Second partition is a primary partition formatted as EXT4
EXT4 is a linux filesystem so you will need a program that can handle Linux filesystems when you are using Windows.
Before installing the ZIP file make sure that:
- You have the correct partition layout (if you have VegaCream installed, you have the correct layout, if not then use the NVFlash installer. This will repartition your internal memory))
- Copy the ZIP file to your SD-Card
- Boot into Recovery
- Do a FULL WIPE / FACTORY RESET
- Install the ZIP file from your SDCard
- After installing reboot the tablet.
[WORKING]
- WiFi
- Bluetooth (Tested with a A2DP headset)
- Camera
- HDMI including audio
- 3G (only fro the Huawei internal modem, usb modems may work)
- GPS not tested by me, but some say it kind of works.
[CREDITS]
- Ejtagle
- Brucelee666
- Scanno
- LeoP for his zRAM implementation
- Legionaire (for the VegaBean bootanimation)
[DOWNLOADS]
Please do *NOT* use Link2SD anymore. You do not need it. With the INT2EXT script, your apps will install on SDCard by default. Just make sure you have 2 primary partition. First partition *MUST* be a FAT32 partition. The second partition *SHOULD* be EXT4. When upgrading from a previous version, make sure your EXT partition is empty / reformatted. Also when using the NVflash version !!!
Downloads:
https://www.androidfilehost.com/?w=files&flid=118264
[Changelist]
[Beta 6]
- RIL updated to the latest version (3 october i think)
- updated to AOSP 4.1.2
- Added check to see if there is a second partition on the SDCard. If not INT2EXT is not excecuted (PLEASE TEST !!!)
- Updated GApps
[Beta 5]
Changes compared to Beta 3-1:
- New kernel with the following changes:
- Suspend problem solved. Tablet does not enter LP0 anymore
- Compiled with zRAM support
- zRAM modules added
- zRAM implementation from LeoP included
- RIL from ejtagle updated
[Beta 3-1]
- Included int2ext+
- Included bootanimation for legionnaire
[Beta 3]
- Latest RIL from EJTagle
- CM10 keyboard
- Stock browser with the option to set User Agent
- You can now just wipe cache and dalvik-cache when updating from a previous VegaBean version. Please remember that from other version you will have to do a full wipe / factory reset !!!
[Beta 2.2]
What has changed compared to Beta 2
- AOSP updated to JRO03L
- Latest update to the huaweigeneric RIL (from aug 27) by EJTagle
The stripped version has the following apps removed from /system/app compared to the original version:
- ApexLauncher.apk
- PlayMusic.apk
- Talk.apk
- YouTube.apk
The stripped version should give you around 10 MiB extra on /system. So if you have bad NAND problems and have problems booting (not able to) you can try this.
[Beta 2]
- HDMI audio working
- VegaBean bootanimation added by indigolemon
[Beta 1]
- Rotation really fixed and HW acceleration working
- Disable / Enable GPS would crash, fixed (thanks Eduardo)
Alpha 3:
- Rotation Fixed. Portrait mode is working correctly
- 3G files included... Sadly no 3G because of too old version of Huawei RIL. Need at least version 6 and we have version 4. So if anybody can get his / her hands on a newer version, please let us know.
Hey , very nice to see JellyBean here
I have ViewSonic 10s
I am using at this moment VegaICS , so i am thinking to upgrate it to JB. So my questions :
- kernel with hostdriver ?
- is system rewritable?? its Squashfs so i think its not (like VegaICS, no deletable apps...)
- can I update BusyBOX and Superuser ??? (always after i did it , WIFI was brocken and I lost root (VegaICS))
- is it possible to change DPI to normal 160 ??
............................
One more question about CWM
always after installing any Roms via CWM , it booted , but after first reboot/turnoff my device died... only what help is reflashing via NVflash....
So what should i flash first to use a stable-CWM (without killing device)
any suggestions
If you are still using VegaICS, I suggest you switch to VegaCream RC2. It has an NVFlash installer, so you don't have to use CWM at all. It is by far the most stable and fast ROM ever built for our devices, and is 100% feature complete.
This ROM is a beta, and if you have not experienced VegaCream RC2 yet, you should try that first and wait on this for a later release.
rpmccormick said:
If you are still using VegaICS, I suggest you switch to VegaCream RC2. It has an NVFlash installer, so you don't have to use CWM at all. It is by far the most stable and fast ROM ever built for our devices, and is 100% feature complete.
This ROM is a beta, and if you have not experienced VegaCream RC2 yet, you should try that first and wait on this for a later release.
Click to expand...
Click to collapse
ye but its 120 dpi... its horrible and all is toooo small .. can see pixels
What a great ROM, but I've got a problem where my Viewpad don't boot. Ok, it boots the first time after installing it, but not on 2nd boot. I've tried to install it over both VegaICS and VegaCream RC2. Does anybody have a solution? I really want this ROM. I had the same problem on VegaCream in the past, but it I think it works now, but not in VegaBean. I hope I get any help...
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
2minuutes said:
What a great ROM, but I've got a problem where my Viewpad don't boot. Ok, it boots the first time after installing it, but not on 2nd boot. I've tried to install it over both VegaICS and VegaCream RC2. Does anybody have a solution? I really want this ROM. I had the same problem on VegaCream in the past, but it I think it works now, but not in VegaBean. I hope I get any help...
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
Click to expand...
Click to collapse
ye its the same problem , flashing with CWM kill your Pad at second boot
thats why i am flashing only via NVflash
Vlad87do said:
ye its the same problem , flashing with CWM kill your Pad at second boot
thats why i am flashing only via NVflash
Click to expand...
Click to collapse
VegaCream works now after flashing it through NVFlash. Could the boot problem have something with an uncomplete CWM or something? Like it "destroys" the important partitions?Since both VegaCream and VegaICS use an unofficial build of CWM with Touch-interface? Mabye I'll try to flash an official version and install VegaBean through there! Will report back if it works!
Nice, will test this out!
2minuutes said:
VegaCream works now after flashing it through NVFlash. Could the boot problem have something with an uncomplete CWM or something? Like it "destroys" the important partitions?Since both VegaCream and VegaICS use an unofficial build of CWM with Touch-interface? Mabye I'll try to flash an official version and install VegaBean through there! Will report back if it works!
Click to expand...
Click to collapse
I can now confirm that flashing VegaBean through official CWM works, and it boots and 2nd boot too... Just download the .zip file at the bottom and follow this guide by me: http://forum.xda-developers.com/showthread.php?t=1597556 or this guide by add.thebad: http://forum.xda-developers.com/showthread.php?t=1041036
Don't forget to hit the "Thanks" button if I helped you out
Link: https://dl.dropbox.com/u/85837377/recovery.zip
Thank you , i will do it then today !
Should i do it better via PC-adb and flash 3.0.2.8 with guide from add.thebad or better your method and recovery OR its just the same recovery 3.0.2.8 just deffirend flash method ???
...........................
Permission request to scanno: can I use his rom as base for Remics-Vega??
Vlad87do said:
Thank you , i will do it then today !
Should i do it better via PC-adb and flash 3.0.2.8 with guide from add.thebad or better your method and recovery OR its just the same recovery 3.0.2.8 just deffirend flash method ???
...........................
Permission request to scanno: can I use his rom as base for Remics-Vega??
Click to expand...
Click to collapse
If you want to use this for a new rom go ahead. Just give the credits for the work done (also ejtagle and brucelee666)
Modifications to the standard AOSP source code can be found on my github. Also the kernel sources are there too.
They are not up-to-date yet.
If you find solutions to problems in the ROM, give them back to the community so they can also be used in other ROMS.
scanno said:
If you want to use this for a new rom go ahead. Just give the credits for the work done (also ejtagle and brucelee666)
Modifications to the standard AOSP source code can be found on my github. Also the kernel sources are there too.
They are not up-to-date yet.
If you find solutions to problems in the ROM, give them back to the community so they can also be used in other ROMS.
Click to expand...
Click to collapse
yes ofc i will.
Is there Host-Driver in the kernel included ?
I am searching developers for Advent Vega device : http://remics.bennz.eu
If you have interests to join Remics-Team pm me!
Vlad87do said:
yes ofc i will.
Is there Host-Driver in the kernel included ?
I am searching developers for Advent Vega device : http://remics.bennz.eu
If you have interests to join Remics-Team pm me!
Click to expand...
Click to collapse
If you mean USB host... Yes it is... On my github there are the sources of the 3.1.10 kernel (based on the rel-15r7 version of nvidia) with the patches ejtagle made. But they are not up to date yet.
As soon as i have time i have to clean up the lunch target of beta1 and do a commit on github. Then you can fork from there and build a version for yourself. If you use the manifest file for vegabean you also get the modifications made to the framework, wpa_supplicant etc to make it all work.
See https://github.com/scanno
Again do not use it yet because they are not up to beta 1.
Thanks for the offer, but i do not have time to do a lot of work and join a development team. For the development of roms for the advent vega i would prefer and suggest that you and the Remics team go to the modaco forum and join the kernel development thread and join the efforts.
This way we have more changes of getting a very good base and from there make ROMS. The more roms to choose from, the better for the people using an advent vega.
Thx for answere, but i dont will compile it , i will use the ready zip file and edit it.
I am not a kernel-developer
thats why i asked you about team
Vlad87do said:
Thx for answere, but i dont will compile it , i will use the ready zip file and edit it.
I am not a kernel-developer
thats why i asked you about team
Click to expand...
Click to collapse
Ok... but again all help is welcome, but you know that. Besides kernel development is done by EJtagle and not by me. He reversed engineerd most of the device specific vega stuff.
Also... /system/lib, /system/framework, /system/usr, /system/app are squashfs filesystems. To access the files in there you have to unsquash them.
do you can tell me programm on windows how to unsquash and again to squash after editing ?
Vlad87do said:
do you can tell me programm on windows how to unsquash and again to squash after editing ?
Click to expand...
Click to collapse
Sorry... I am using Linux and it is available in the repository there. On windows I really do not know. You could Google to see if there are any hits on mksquashfs and unsquashfs. That are the tools used on Linux.
You will need to find a version that supports XZ ( LZMA2) compression. That is the compression algorithm used in vegabean.
This is needed because otherwise the ROM does not fit in the /system partition.
very nice!
7zip can do it under windows - unpack
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.
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! 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
* and point my finger right back at you.
*/
Installation Instructions
Make sure you have a second partition on your SD card formatted to ext4 before flashing!!!! This can be created with either CWM recovery or with TWRP. gparted on Linux should also work. If you "SD card not supported" try repartitionning. If you get "Encryption unsuccesful" then you need to format the second partition as ext4 (or f2fs, your choice).
If on a BML rom (stock-based GB)...
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. It will reboot a couple of times, don't be worried.
4. If you want gapps, reboot to recovery, wipe data+cache and install gapps.
5. If you want root, flash SuperSU whenever
If on an MTD rom (CM7 and all ICS+)
1. Reboot to recovery
2. Wipe data, dalvik/art cache, system, and cache partitions
3. Install zip
4. If you want root or Gapps, install them now.
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess.
Bluetooth only enables from the notification pulldown, not when you go directly to settings. It does work just fine afterwards though
If you're coming from either the last Lollipop build or the initial pre-release Marshmallow build, there is a bug in TWRP that will prevent flashing anything but the ROM. To get around this, please flash the Marshmallow zip, then reboot to recovery, and then follow the typical instructions.
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
If you come across a bug, feel free to let me know by posting in this thread. I will not be working non-stop on this project, but will try to fix bugs that affect me as this is still my main phone (out of choice, not necessity).
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Taking pictures
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Video Recording
Automatic Brightness
Encryption
Compass
GPS
Headset Buttons
Semi-Working
Powered-off charging animation - works at first, but then stops working. Seems to be an Omni problem, but it still charges...
What doesn't
SElinux is currently in permissive mode. Will not be going to enforcing, this would require a data wipe as well
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+
Everything else is not tested!!!
XDA:DevDB Information
Unofficial Omnirom 6.0 for Galaxy S 4G, ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99
Source Code: https://github.com/omnirom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: OmniRom
Version Information
Status: Beta
Created 2016-01-11
Last Updated 2016-05-12
Thanks Time!
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to the OMAP4 AOSP team for their work on porting CMA to a 3.0 kernel.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-6.0 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree (create the local_manifests folder if necessary).
After syncing the source, open a terminal and in the directory where you downloaded the source code type "./device/samsung/aries-common/patches/apply_patches.sh" to apply the patches necessary to have a working build. Then run "source ./build/envsetup.sh" and then "brunch galaxys4gmtd". For future builds, only the envsetup and the brunch parts are necessary. Please note that you will have to re-run the apply_patches.sh script after each time that you run repo sync. (Note: the patch script no longer runs automatically)
You should be able to use my trees for other first-gen galaxy S devices. You will need to apply a patch similar to https://github.com/xc-racer99/andro...mmit/fe6bc6b82881a12fc4a5647812f3cf0f52f79c6a to your device tree (if coming from Omni 5.1). I haven't done anything to P1 trees and may have broken the kernel for it...
Changelog
2015-12-20
Initial pre-release - many bugs
2015-12-26
Second pre-release - fewer bugs, but still plenty
2016-01-07
Initial actual release. Quite stable with minimal bugs
2016-01-23
Updated Omni Source code
Fixed Google Play (and other apps) download error (I think...)
New bootanimation - Its the new Omni one - it doesn't fit on our screen the best but it doesn't have one section lit up all the time so the screen doesn't burn in like the old one
Freed a bit more RAM
Improved zRAM performance by using LZ4 instead of LZO
Added T959P build
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
Added download mirror thanks to @FBis251
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Changelog for 2016-02-29
Updated Omni source - plenty of new features
Low-resource spinner from LegacyXperia (means that the loading spinner isn't the only thing using the CPU)
Miscellaneous performance tweaks (see github if interested)
md5sum for T959V: a7aa8cca3259208eafba7c2cccecdbfd
md5sum for T959P: 879256c93a0e58de0fb9c9e1be91e0e9
Changelog for 2016-04-02
Security fixes in the kernel
Freed roughly ~4MB of RAM in kernel
Updated android drivers resulting in better multitasking
OpenDelta updating system removed as we weren't using it (it used ~3MB of RAM)
Recents menu now has less lag when opened
Selinux contexts have changed. It could likely be put to enforcing now but this would require a complete data wipe so its still permissive
Live Wallpapers removed - we're low-ram
Bootanimation now fits the screen better
PowerHAL removed - it was broken and has been for a while...
Misc other changes - if you didn't notice problems, you won't notice the solutions
Known bug - Camera on T959V is broken...
md5sum for T959V: 247a721f4c27c5191a2a460e4c72ba3b
md5sum for T959P: d15339d8aa10f765155bdd8d1bb0c5f5
Changelog for 2016-04-08
Fixed camera on T959V
Security patch level of April 2, 2016 (latest to date)
Headset buttons fixed
T959V md5sum: 2b1560b99402c73275d1f69b3ceb9a22
T959P md5sum: e102cce0d624383fb85a32321c98c645
Changelog for 2016-05-09
Uses CMA kernel by default
Performance Control can now modify voltages
Systemless SuperSU is now supported
WebM playback is now working
EFS backup in TWRP now works
Data on boot should now work - no need to toggle airplane mode anymore
md5sum for T959P - 118789dd68760d9fd18cc961398bf346
md5sum for T959V - f9375a8d9792c3a0d222c113213c014d
Changelog for 2016-06-07
Security patch level of June 1, 2016
Microphone mute now works when in call
Battery now charges to 100% and should read properly after a system crash
Standby times should be improved
Slightly less RAM - but should result in better graphics performance
CMA crashes fixed (at least, I haven't crashed once since I started testing the patch a week or so ago)
PowerHAL is back - CPU is boosted when turning screen on to avoid delay
md5sum for the T959P: eeed77fb84189e84f2264e32d18ce454
md5sum for the T959V: b6457319d248029429183c342514b072
Changelog for 2016-08-02
First unified build (ie it works on both the T959P and T959V)
Screen recording now works in portrait mode
MMS should be able to be sent when data is disabled (will still use data though)
Default Camera app portrait photos are no longer square
SuperSU systemless updated to 2.76
Slightly less audio latency with UI sounds (and some sounds have changed)
Data should also be working on boot
Slight changes to battery and graphics config
Security patch level of August 5, 2016 (I'm a time traveller...)
md5sum: df587e0bd69552e0ece4b4ba3e214f45
Source, Downloads, Misc Notes
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see android-6.0-t959v branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-6.0 branch). The patches folder holds all the necessary patches along with a script to apply the patches.
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-6.0 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-6.0 branch)
Downloads!
All builds are found at https://drive.google.com/folderview?id=0B7vXjzo0Hj-iOGJ4dmdCd09OZmM&usp=sharing. As well, recent builds are mirrored on https://files.fernandob.com/#xc-racer99/Omni6.0
Gapps
Gapps cause the first boot to be very, very laggy. Things do improve after that. The best way to get through the Setup Wizard (IMO) is to skip everything possible (ie connecting to Wifi, settings up a Google Account, etc) and then reboot. You can manually add a Google Account later in Settings. While any (small) Marshmallow gapps should work, I have had success with OpenGapps pico package from www.opengapps.org (untested on recent builds).
SuperSu
SuperSu can be found at http://forum.xda-developers.com/apps/supersu. If on May 2016+ builds, systemless 2.71 works (other systemless versions may work, untested). If you're on an older build, you need to either force system mode (create a file in /system or /data called .supersu with the contents "SYSTEMLESS=false") or use an older version (ie version 2.52 or earlier). August 2016 build updates the systemless to 2.76.
Woooow thanks
As you suggested, Gapps caused lots of problems...made the ROM very slow and laggy, lots of FC's, lots of random reboots, etc. I re-flashed without Gapps. Was able to restore apps with TB and root with SuperSu. The basics...calling, browsing, messaging, camera...are working fine. Haven't taken it for a ride yet, but GPS test picked up 5 satellites and I haven't even taken it outside yet. If I desperately need another app, I guess I can find the .apk somewhere. Since I did a TWRP backup, maybe next week I'll try the pico gapps again and see what happens. At any rate, wonderful work.
Update: Took it out for a spin this afternoon....GPS works fine.
Been running the 1/7 for a few days. loving it so far
New Build Uploaded!
Alright, I've uploaded a new build
Changelog for 2016-01-23
Updated Omni Source code
Fixed Google Play (and other apps) download error (I think...)
New bootanimation - Its the new Omni one - it doesn't fit on our screen the best but it doesn't have one section lit up all the time so the screen doesn't burn in like the old one
Freed a bit more RAM
Improved zRAM performance by using LZ4 instead of LZO
I've also uploaded a T959P build as I had a request for one. Let me know if you guys find any more bugs.
New build flashed fine although I had to re-flash the SuperSU zip...no problem since I already had it on my SD card. I'll let it rest up for a day or two and then I'll try to flash the pico-gapps and see if it
will run smoothly....good job.
DickyG said:
New build flashed fine although I had to re-flash the SuperSU zip...no problem since I already had it on my SD card. I'll let it rest up for a day or two and then I'll try to flash the pico-gapps and see if it
will run smoothly....good job.
Click to expand...
Click to collapse
Sounds good. Do note that when/if you flash gapps, you will need to do a complete data wipe first, otherwise you will get force-closes like crazy.
I've always just reflashed SuperSU manually and never relied on the script to restore it so I can't help you there.
Tried to install over MTD SlimSaber with TWRP 2.7.0.0, kept getting Status: 7 error with updater.sh script.
Any way to fix this?
Thanks in advance.
SuccubusInc said:
Tried to install over MTD SlimSaber with TWRP 2.7.0.0, kept getting Status: 7 error with updater.sh script.
Any way to fix this?
Thanks in advance.
Click to expand...
Click to collapse
Hmm, going back to to stock with a OneClick/Heimdall/Odin will work for sure.
Alternatively, check if there is an omni.cfg file on your SD card. If there is, delete it and try again. Also, if you can get me the exact wording of the error output that would be great, along with the omni_mtd.log file from the SDcard.
xc-racer99 said:
Hmm, going back to to stock with a OneClick/Heimdall/Odin will work for sure.
Alternatively, check if there is an omni.cfg file on your SD card. If there is, delete it and try again. Also, if you can get me the exact wording of the error output that would be great, along with the omni_mtd.log file from the SDcard.
Click to expand...
Click to collapse
I will Heimdall One-Click back to KJ6 and reflash the ROM after checking for the omni.cfg, and will quote the output and the log if I get another error.
I'll be back by 5:00pm PST. I have school to take care of.
UPDATE:
Tried again after a full wipe [not a restore to stock] and got this:
Installing '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: run_program("/tmp/updater.sh") = = 0
E:Error executing updater binary in zip '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'
Error flashing zip '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'
Updating partition details...
Click to expand...
Click to collapse
Is there any kernel/recovery you recommend for flashing after restoring to stock?
I've tried before on AntonX Voodoo Lagfix recovery and got a similar error.
SuccubusInc said:
I will Heimdall One-Click back to KJ6 and reflash the ROM after checking for the omni.cfg, and will quote the output and the log if I get another error.
I'll be back by 5:00pm PST. I have school to take care of.
UPDATE:
Tried again after a full wipe [not a restore to stock] and got this:
Is there any kernel/recovery you recommend for flashing after restoring to stock?
I've tried before on AntonX Voodoo Lagfix recovery and got a similar error.
Click to expand...
Click to collapse
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
xc-racer99 said:
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
Click to expand...
Click to collapse
I'll try out Blastoff if I can find it. But it probably failed because I did not partition my sdcard. I'll see if that helps later.
Thanks a lot.
xc-racer99 said:
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
Click to expand...
Click to collapse
Hey, xc-racer99, after about four assorted blind attempts at installing your work, I flashed back to stock/AntonX kernel with Heimdall and full wiped, then used CWM to create a 4GB partition on my sdcard. The ROM installed through CWM, then TWRP without an error and booted up after fifteen minutes or so of OMNI animation, and is running on my SGS4G without any issues. The only noticeable lag was for the first five minutes after the initial boot. Now my device is gliding smoothly after a few tweaks in the performance settings and turning off background processes. Thank you so very much.
Next time, I'll read the entire post before blundering through the install process with the assumption that I know what I'm doing [as usual].
Sorry for the trouble, if indeed I was any.
xc-racer99 said:
Alright, I've uploaded a new build
Changelog for 2016-01-23
...
Fixed Google Play (and other apps) download error (I think...)
...
Click to expand...
Click to collapse
I tried Pico gapps and the store works perfectly for me now. Thanks!
New Build Uploaded!
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Still the same bugs present - headset buttons broken (have been on all 3.0 kernel-based ROMs for the Galaxy S 4G), laggy 720p recording, broken webM playback, microphone mute in calls, and bluetooth tethering.
Download link is the same as it always is. Also, thanks to @FBis251, we now have a mirror. It is located at https://files.fernandob.com/#xc-racer99//Omni6.0
Wooow...thanks
xc-racer99 said:
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Still the same bugs present - headset buttons broken (have been on all 3.0 kernel-based ROMs for the Galaxy S 4G), laggy 720p recording, broken webM playback, microphone mute in calls, and bluetooth tethering.
Download link is the same as it always is. Also, thanks to @FBis251, we now have a mirror. It is located at https://files.fernandob.com/#xc-racer99//Omni6.0
Click to expand...
Click to collapse
Finally got pico gapps to run...the initial setup took quite a while but now that it's settled in, no problems. It's also interesting to note that Link2SD is running fine while it seems to be a major problem for other Lollipop & Marshmallow ROM's on other devices.