{
"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"
}
Welcome to the unofficial CyanogenMod 10.2 nightlies
The releases will co-inside and the build start time is at 03:01 UTC every night and should be uploaded soon after. If at anytime the builds are not there, then there was a problem building the ROM, and we will have a look at it ASAP.
These builds are compiled from the latest CyanogenMod repos and device repos on device, kernel and vendor.
These are NativeSD builds Repartitioning may be required
With aging nand storage filled with BBs, a crappy filesystem (namely yaffs2) and high speed sdcards these days it really makes sense to mount /system and /data on the sdcard. prerequisite is a fast sdcard (class 6, class 10 - they're really cheap these days). transfer rates are ~2.5x-3x nand speed with a decent sdcard and we can benefit from ext4. of course, one needs a compatible recovery (built with this change included) and a partitioned sdcard. e.g. minitool with win and fdisk with *nix.
Partition layout
Device partitions (cLK):
* boot: 10
* recovery: 10
* cache: 5
* misc: 1
Click to expand...
Click to collapse
You need to create two primary ext4 partitions in addtition to the regular fat32 partition on your sdcard.
SDcard partitions:
* 1st primary sdcard partition: fat32 storage (should already be there)
* 2nd primary sdcard partition: ext4 (at least 500MB)
* 3rd primary sdcard partition: ext4 (e.g. 2000MB)
The first partition will be your regular sd storage.
The second partition will be /system.
The third partition will be /data.
You can use MiniTool Partition Wizard with Windows and fdisk with Linux
Click to expand...
Click to collapse
Click to expand...
Click to collapse
NativeSD recovery required to properly support these builds
Download
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Download builds here
Click to expand...
Click to collapse
Download Google Apps
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changes
Upstream changes
Devicetree commits
Kernel commits
Click to expand...
Click to collapse
Click to expand...
Click to collapse
And as always: I take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, dead kittens, etc.
IRC channel
Visit us in #cmhtcleo on freenode
Click to expand...
Click to collapse
Click to expand...
Click to collapse
---------- cmhtcleo team ----------
arif-ali | milaq | Rick_1995
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thanks/Credits
Click to expand...
Click to collapse
Marc Alexander (marc1706) - for his awesome work on the HD2 kernels
Sportsstar89 - for carrying on open development - all your build trees are in an open git. Way to go mate. Thats the spirit of FOSS
Securecrt, Rick_1995 - for their awesome work on a full HWA kernel and other great contibutions to the Leo codebase
Evervolv - for the now mandatory legacy repos
arif-ali - for his huge contribution to the cmhtcleo project and beeing a indispensable part of the Android community
copenhagen, warrenb213 - for keeping on devloping for the hd2
charnsingh_online - For starting this great project for porting to CM
tytung - for of his work on the HD2
texasice - For creating the first HD2 compitable ICS through passion/bravo
ankuch - thanks for the HW accel, codecs and Camera
Xylograph - for carrying on development
zivan56 - your input for the headphone fix
Bexton - The fix for USB Mass Storage
michie - Your work on ICS for the HD2
Steve Kondik (cyanogen) - for starting this great project
Google - for an awesome OS
Let me know if i omitted you and i will add you here asap
Preferred and yet more advised is cLK.
If you REALLY need to use MAGLDR then keep on reading.
MAGLDR instructions
We are using boot.img style kernel/ramdisk (as everyone else should be).
For MAGLDR users that means that you need to specify your boot partition as rboot.
The following flash.cfg is recommended (system and data size doesnt matter as we're using NativeSD)
Code:
misc ya 1M
recovery rrecov|ro 10M
boot rboot|ro 10M
system ya 300M
cache ya 5M
userdata ya|asize|hr allsize
Thank you for your awesome work.
HWA??
Does This Rom Support The HwaSettings App, Does this rom have the hwui edit for the hwasettings to work in the Android Source?
thank's man happy to see a dev in this forum .:laugh:
wow a rom by Dev ... Downloading.. plz work on kitkat for hd2 too.. n wish hd2 gets 3.0 kernel... thanks for the great rom.. :good::good::good:
hirencj said:
wow a rom by Dev ... Downloading.. plz work on kitkat for hd2 too.. n wish hd2 gets 3.0 kernel... thanks for the great rom.. :good::good::good:
Click to expand...
Click to collapse
Here's a sneak peak
I from the HD24EVR team is now working for a Kitkat rom that will be uisng ION with the 3.0 kernel
Also a Shoutout to @marc1706 for making the 3.0 kernel
aazzam16661 said:
Here's a sneak peak
I from the HD24EVR team is now working for a Kitkat rom that will be uisng ION with the 3.0 kernel
Also a Shoutout to @marc1706 for making the 3.0 kernel
Click to expand...
Click to collapse
Thank you for your dev on Kernel 3.0 on LEO
I hope we can use new kernel with ION soon..
:good:
fengsam said:
Thank you for your awesome work.
Click to expand...
Click to collapse
Dear Sir,
Can we use this on NativeSD or DirectSD as i am using windows mobile 6.5 and nativesd for android
aazzam16661 said:
Here's a sneak peak
I from the HD24EVR team is now working for a Kitkat rom that will be uisng ION with the 3.0 kernel
Also a Shoutout to @marc1706 for making the 3.0 kernel
Click to expand...
Click to collapse
Wow Thats going to be awesome... HD24EVE Best Wishes for the team... Plz keep up good work.. :good::good::good::good::highfive:
as installed, this ROM?. Lapsus, forgotten concepts. I had my HD2 in a drawer, and I see that this becomes animate. If developers continue to give life to this superphone, put for sale my HTC One Thanks
I think it will be a great build.
Is a problem with GPS fix a known problem or maybe only I am experiencing it?
Can I install this using one ext4 partition on sdcard? Or I need to make another?
vlado3399 said:
Can I install this using one ext4 partition on sdcard? Or I need to make another?
Click to expand...
Click to collapse
Hi vlado3399, I am almost certain you need 2 ext partitions, as it says in OP (so it is not NativeSD)
I tried installing it to one partition, and there is no /data on the ext partition. Also, the install process has formatted the ext partition, so if you have any NativeSD roms or anything in dataonext, be sure to back them up first.
I will try adding another partition. Am trying to boot from magldr, but I think clk is the way to go
Edit; Thank you milaq and team, exciting to see nightlies back on our hd2. I hope there will be enough ongoing interest in testing etc from the hd2 community:fingers-crossed:
OP says that build is NativeSD, that's why i asked my question. Give us feedback when you add another partition and install rom
Robbie P said:
Hi vlado3399, I am almost certain you need 2 ext partitions, as it says in OP (so it is not NativeSD)
Click to expand...
Click to collapse
mounting partitions on sdcard partitions is exactly what nativeSD is.
nativeSD is just a term used for the general principle and is not limited to a specific partition layout. it makes sense to use 2 partitions instead of fuse mounting hackery with only one sdcard partition. e.g. formatting /data and /system separately, etc.
Ok, have added 2nd partition using minitool.
installed 20131227, magldr, using the recommended cwm recovery
It reboots during bootanim, have attached dmesg.
will try with clk a bit later.
Edit; same on clk, reboots during bootanim
Edit2; same with 20131228 on clk. I also tried putting tytung's r2 into boot.img (using this, and adding system files to rom.zip) but the same thing happens, so i don't think it is kernel related.
I can try and get a dmesg, but not sure how to with clk, will have to search a bit
I did notice that minitool sees the first (system) partition as ext3 after installation, looking at updater script, it is formatted as ext4...
format("ext4", "EMMC", "/dev/block/mmcblk0p2", "0", "/system");
Click to expand...
Click to collapse
So not sure why minitool would see it as ext3
goglum said:
Is a problem with GPS fix a known problem or maybe only I am experiencing it?
Click to expand...
Click to collapse
Is anyone else experiencing problems with GPS? Cause I don't know if I should look for the source of the problem on my side. I tried digging through device and kernel commits, but I don't get much of it
I already tried replacing /system/etc/gps.conf with something suitable for my region (Europe/Poland), but it didn't help.
Pls answer someone. ;]
goglum said:
Is a problem with GPS fix a known problem or maybe only I am experiencing it?
Click to expand...
Click to collapse
I cannot get GPS working either.
My phone was previously running CM7 (HyperDroid-CM7-Licking-Lobster-v5.7.0) and it was working fine, so I tried using gps.conf from this version, but it did not work.
Related
{
"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"
}
Welcome to the unofficial CyanogenMod 9 nightlies
The releases will co-inside and the build start time is at 00:01 UTC, and by 01:00 the builds should be uploaded. If at anytime the builds are not there, then there was a problem building the ROM, and we will have a look at it ASAP
These builds are compiled from the latest CyanogenMod repos and device repos on device and vendor files.
Furthermore these builds are multiDPI, i.e. you can run the rom at any dpi between 160 and 240 while having hi-res assets. Also Phone.apk won't crash anymore if a DPI < 190 is set.
kernel/ramdisk packaged boot.img style
if you are on magldr see second post for instructions
System partition size currently required:
Without Gapps 155MB
With Gapps light 190MB
With Gapps standard 195MB
Click to expand...
Click to collapse
Download nightly builds here
or via GooManager
Click to expand...
Click to collapse
Google apps
Latest Gapps LIGHT (2012-03-17) for ICS
(picoTTS folder removed to save some diskspace - can be downloaded to SD later if needed)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changelogs
Upstream changes
Device changes
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Tip: If you want to have your softbuttons and/or density settings persist over updates and don't want to edit build.prop with every update, use local.prop.
create a file named local.prop in your /data root (i.e. /data/local.prop) with the following contents (for example):
Code:
qemu.sf.lcd_density=160 # overrides ro.sf.lcd_density in build.prop
qemu.hw.mainkeys=0 # activates the softbuttons
Click to expand...
Click to collapse
Thanks/Credits
Click to expand...
Click to collapse
arif-ali - for his huge contribution to the cmhtcleo project and beeing a indispensable part of the Android community
securecrt and Rick1995 - for their awesome work on a full HWA kernel and other great contibutions to the Leo codebase
copenhagen - for support with CM7 and now with ICS/CM9
warrenb213 - for support with CM7 and now with ICS/CM9
charnsingh_online - For starting this great project for porting to CM
tytung - Continued dedication of his work to the HD2 Thanks for you kernels
texasice - For creating the first HD2 compitable ICS through passion/bravo
ankuch - thanks for the HW accel, codecs and Camera
zivan56 - your input for the headphone fix
Bexton - The fix for USB Mass Storage
michie - Your work on ICS for the HD2
cyanogen - For starting this great project
Google - This wouldn't have happened without the releases of Android from you
IRC channel
Click to expand...
Click to collapse
Visit us in #cmhtcleo on freenode
Webchat
---------- brought to you by the cmhtcleo team ----------
arif-ali | milaq | zeusk
Click to expand...
Click to collapse
Click to expand...
Click to collapse
MAGLDR instructions
Although we have an unified updater-script for both cLK and MAGLDR you need to take care that your MAGLDR partitioning is correct.
We are using boot.img style kernel/ramdisk (as everyone else should be).
For MAGLDR users that means that you need to specify your boot partition as rboot.
The following flash.cfg is recommended (system size can vary)
Code:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
[COLOR="Green"]boot rboot|ro 5M[/COLOR]
system ya 190M
cache ya 2M
userdata ya|asize|hr allsize
Instead, you can also download this package:
http://milaq.exnet.me/downloads/android/leo/magldr_part_cm9.zip
Extract and run DAF to flash the layout above
Building from source
I thought it would be a good idea that I just give a quick run through on how this is compiled.
First we need a Linux environment, preferably Ubuntu >= 12.04 or a recent Debian
Follow the simple Howto here, to just get an idea of the pre-requisites
To initialize the common cyanogenmod repos, run the following command
Code:
repo init -u git://github.com/CyanogenMod/android.git -b ics
then to get device specific repos for the HD2 you need to pull in a local manifest.
you can use this one
Code:
curl https://raw.github.com/milaq/android/ics/local_manifest_htc_leo.xml > .repo/local_manifest.xml
(you can of course tailor your own too)
then you need to sync the repositories
Code:
repo sync
You can also run repo sync -j 4, say if you had 4 cores to speed things up, you may also need to add a -f, to make sure that it continues to the end even if you get any error messages. You may need to repeat this process 2 or 3 times to make sure everything is synced. This will take a long time to synchronise, so be patient.
next run the following command to gets some prebuilt apks (doesn't need to be done with every build)
Code:
vendor/cm/get-prebuilts
so after this, you need to run the following commands
Code:
. build/envsetup
lunch cm_leo-userdebug
make -j4 bacon
This has changed from lunch cyanogen_leo-eng to lunch cm_leo-userdebug, this is the new method from CyanogenMod team for CM9
In the end you will get a zip file in out/target/product/leo/full_leo-ota-eng.root.zip.
4th Post if required
headphone jack is fixed...you can find solution on tytung ics thread...and hw acceleration is being worked on by dan1j3l....
Hey all,
The link is up.
At the moment, this CWM size supported with cLK, unless you know how to get it working with MAGLDR, then you're free to convert it, and pass it back.
The GAPPS as mentioned on the Nexus One thread is also in the first post
This is still alpha in my opinion at the moment, so some things may still not work as other ICS ROMs
CM code, apps etc... are still not there, and will come, when they add it, and once some the stuff in the "Not Working" are working, will start doing a nightly release
Any suggestions, additions etc.. etc.. aare all welcome. Thanks for the whole community for making this possible
Good luck testing
damn this is so nice! im about to backup now and then flash it. ill report later what kind of bugs i can found and what is working.
THX FOR THE HARD WORK! LOVE THE HOLE XDA, CYANOGEN, ANDROID COMMUNITY!
---------- Post added at 11:03 AM ---------- Previous post was at 10:51 AM ----------
well, got it flashed and jsut started. First thing that come up was an error massage:
unfortunatly, Nfc Service has stopped.
Can only press OK
After i pressed OK, the same massage in an outher languegae pop up and i cant get it away...
No way get around that now...
Ah and my screen just went black and i only can reactivate it with the BACK button.
My System is: HTC HD2 EU, CLK, 200/44, Fresh wipe, Fresh SD Format, Fresh install
gmbhneo said:
damn this is so nice! im about to backup now and then flash it. ill report later what kind of bugs i can found and what is working.
THX FOR THE HARD WORK! LOVE THE HOLE XDA, CYANOGEN, ANDROID COMMUNITY!
---------- Post added at 11:03 AM ---------- Previous post was at 10:51 AM ----------
well, got it flashed and jsut started. First thing that come up was an error massage:
unfortunatly, Nfc Service has stopped.
Can only press OK
After i pressed OK, the same massage in an outher languegae pop up and i cant get it away...
No way get around that now...
Ah and my screen just went black and i only can reactivate it with the BACK button.
My System is: HTC HD2 EU, CLK, 200/44, Fresh wipe, Fresh SD Format, Fresh install
Click to expand...
Click to collapse
To fix that open the gapps zip with 7zip and go to app folder and double tap the nfc.google.apk and go in the lib folder and take the nfc_jni.so and put it in the lib folder than reflash. when flashing addon to system app files has to have a lib file in the lib folder or there will be fcs.
Hi,how can i port this on MAGLDR?
this is post about headphone fix...
Headphones working
diff from http://gitorious.org/~tytung/linux-o...x_on_wince_htc
Still needs work to display icon, but works fine at least in terms of basic playback functionality.
I grabbed the config file from /proc/config.gz from beta 2.
EDIT: if anybody wants to try it (no responbility if it breaks your phone and I have done ZERO testing apart from headphones): http://www.fileserve.com/file/V2tN9E...adphonefix.zip
Install over beta 2 using CWM for Magldr (install zip option).
ofcourse credits to zivan56
cmhtcleo said:
Hey all,
The link is up.
At the moment, this CWM size supported with cLK, unless you know how to get it working with MAGLDR, then you're free to convert it, and pass it back.
The GAPPS as mentioned on the Nexus One thread is also in the first post
This is still alpha in my opinion at the moment, so some things may still not work as other ICS ROMs
CM code, apps etc... are still not there, and will come, when they add it, and once some the stuff in the "Not Working" are working, will start doing a nightly release
Any suggestions, additions etc.. etc.. aare all welcome. Thanks for the whole community for making this possible
Good luck testing
Click to expand...
Click to collapse
mmmm is it possable to add the long push back to "close" app in ICS?
this function is why I use CM7 and the cpu tweak
uio88 said:
Hi,how can i port this on MAGLDR?
Click to expand...
Click to collapse
run through android kitchen and convert boot.img to folder.
kane159 said:
mmmm is it possable to add the long push back to "close" app in ICS?
this function is why I use CM7 and the cpu tweak
Click to expand...
Click to collapse
This is an early alpha version. It barely even boots. Even ultra-basic basics like wireless data transfers are still not working.
Of course it will be possible to add features like the one you asked for later, but
a) This is not the place to ask, as this is only the port of CM9 to the HD2. Join the CyanogenMod forums for upstream (that means non-HD2 specific) feature requests.
b) Features most likely will only be added after basics are taken care of.
cmhtcleo said:
CM code, apps, and anything CM specific etc... are still not there, and will come eventually, when CyanogenMod add it (so don't ask me to add it). It will come when it added
Click to expand...
Click to collapse
Anything that is/was CM specific will not come yet, you have to wait for those to be ported by the CyanogenMod team. I am not part of that team. I work independent of them to get you guys the best out of CM, as we don't and will never get official status by them
comments & feedback blah
sup Arif,
do u think u can post a rom manager downloadable cwr with the 200mb system partition?
will be following the cm9 development intentitively. if u need any feedback from testing dont hesitate to ask.. i dont work.... just mod android stuff all day so got alot of free time -=] oh and if you dont want to test something on your HD2 send it my way ill risk a brick i have some bad motherboards that only work in the freezer or out the window in the winter lol so not a loss if they complete there slow death
thanks
-Marcio @
WinDroidz inc
lots of HD2 parts for sale pm if looking for something... have everything
blahshed said:
sup Arif,
do u think u can post a rom manager downloadable cwr with the 200mb system partition?
will be following the cm9 development intentitively. if u need any feedback from testing dont hesitate to ask.. i dont work.... just mod android stuff all day so got alot of free time -=] oh and if you dont want to test something on your HD2 send it my way ill risk a brick i have some bad motherboards that only work in the freezer or out the window in the winter lol so not a loss if they complete there slow death
thanks
-Marcio @
WinDroidz inc
lots of HD2 parts for sale pm if looking for something... have everything
Click to expand...
Click to collapse
@blahshed, all
The replacement of my HD2 to SGS2 has been enforced on me at work after 2 years contract, so it could be that I may not be able to keep it; so for the time being my development for ICS will cease, as I cannot test anything at all.
I will find out in a week or 2. Nevertheless I may invest in one HD2 for devving purposes, when I find out.
I will however keep monitoring the progress that the HD2 colleagues are making, so that I can quickly fire in any of the updates to the code when and if I come back.
arif-ali said:
I will however keep monitoring the progress that the HD2 colleagues are making, so that I can quickly fire in any of the updates to the code when and if I come back.
Click to expand...
Click to collapse
Hi! What is correct way to build ICS? I am building CM7 without problems. Can you help me with first steps only? ;-)
Thanks in advance!
seanyuan62 said:
How is the SGS2?
Click to expand...
Click to collapse
It's fast, just compiled a cm7 nightly, so it seems all good, at least I have 16GB rather than the 512M of the leo
fhasovic said:
Hi! What is correct way to build ICS? I am building CM7 without problems. Can you help me with first steps only? ;-)
Thanks in advance!
Click to expand...
Click to collapse
Check Post #3, my instructions are there.
arif-ali said:
Check Post #3, my instructions are there.
Click to expand...
Click to collapse
Thanks, that's more than enough ;-) syncing repo for some time now
ICS progress
Just bought a HD2 from ebay, so hopefully development will continue sometime this week. I can see that tytung has managed to get quite a bit working.
I know that still not all CM stuff is not there yet, so that again will take time even if we have everything working from the ICS point of view; so at least a month or 2 yet I think; but we'll see
Code:
/*
* @brief: Standard Disclaimer
*
* Your 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.
*/
What is the difference between this and the nightly ?
All libraries and native code is compiled in ARM mode (except for libwebkit which is still in thumb mode due to it's excessive size) and compiler side optimization is turned on (again, exception being libwebkit using -Os and sqllite using -fno-fast-math).
Important function calls and syscalls are aligned for faster response time.
I re-implemented some of the cpu atomic functions based on what I've learned so far, swp is used for atomic swap instead of ldrex/strex, register swapping of old value is done at success so if a context switch does occur, the loop will be aligned at the same boundary as the function. On best case, there shouldn't be any difference but can improve execution time for worst case of context switches.
Java libraries and bionic libc are compiled with NDEBUG, and the debug variable for java is also set to false.
Most crap (stuff that "I" do not use, has been removed ie. VPN, live wallpaper support etc..)
Fixed a few memory leaks in bionic, dalvik and ppp (also tether).
I've removed most locales except en_US and en_GB, though android still seems to be compiling strings from other languages in the build, so they might work but i can't guarantee anything with locales other than en_(US|GB).
Reverted the patch which auto closed notification bar when all notifications are canceled/removed. It was irritating me..
more stuff i don't remember, if you care pm me and I'll send you a diff of my repo.
Bugs
USB tether (Use another kernel to fix this)
Wierd bootup logo
Auto brightness might get stuck, switch screen on and off to fix it
Poweramp crashes, Though confirmed, the cause itself is not known
Installation
Change partition sizes to as described above the rom link
Boot to recovery
Flash the magldr rom/zip/cwm
Flash clk zip if you're on clk
Reboot
Reboot to recovery and flash data2sd if needed. Must have 5M extra on /system
Tips
Use Quickpic for gallery
Replace ADW with one of your favourite launchers (ADW EX, LP, Zeam etc..). ADW is slow and buggy, I prefer FTL and fast drawer.
DON'T USE SUPERCHARGER V6.
SD Port
NativeSD Port
v2b
Partition Size
misc 1M
recovery 5M
boot 4M
system 68M
cache 2M
Changelog
Update Adreno libraries from latest desire RUU
Switch to release build, less logs and more compile time checks
Hosts included in the rom
Fix data for magldr (left old rmnet module, silly me) thanks Xylograph
Magldr Rom
Magldr to LK
Click to expand...
Click to collapse
v2
Partition Size
misc 1M
recovery 5M
boot 4M
system 67M
cache 2M
Changelog
Old market and trimmed fonts, thanks Xylograph
Updated Software 2D drawing code from jellybean.
Fixes Music creating bogus video app in app drawer
New memcpy routine from apple
Fixes a bug in atomic routines
Suppress/Remove verbose and debug logging.
Remove unnecessary strings from a few hardware libraries
Well if you cared to reach this point, send me a pm for the repo diff.
Magldr Rom
Magldr to LK
Click to expand...
Click to collapse
First release
Partition Size
misc 1M
recovery 5M
boot 4M
system 79M
cache 2M
Magldr Rom
Magldr to LK
Click to expand...
Click to collapse
data2sd (needs 5M extra in system)
Notes:
I compiled this rom for myself but figured sharing won't hurt, and hence I don't plan to provide much support though I'll see what i can if you find a bug. I've run the rom for quite some time now and the results were as expected. Good battery life, large amount of ram upon boot (though I can still notice some memory leaks, will have to look deeper). For now the kernel is tytungs-r1 ics kernel patched for gingerbread, though I will be patching/updating and working on the cmhtcleo kernel once i have the build known to be bug free after some time. Due to switch from arm+thumb mixed to pure ARM mode, i was expecting higher ram usage (alongside with better performance), however looks like I was wrong, this build eats less ram than a arm+thumb interworking build, now i am not really sure why but from what i know it could be because compiler doesn't have to generate arm->thumb and back jumpers for interworking between arm and thumb code.
{
"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"
}
Credits
cyanogenmod
cmhtcleo team (arif-ali, milaq, charansingh and all other cm developers) for device tree
tytung
Xylograph
devhost
This is my first and probably the last rom, thank you for your time.
pretty impressive trying in 3 2 1...
this seems to be nice!! ... downloading!!
another thing you might want to know,
I've removed logo.rle from ramdisk, both to save time and space. I don't fancy bootup logos, Currently it will show wierd patterns on boot if you switch off and power on or the last screen you had if you reboot. This requires a small fix in the kernel which I will release with my next version with the new kernel.
Rick_1995 said:
another thing you might want to know,
I've removed logo.rle from ramdisk, both to save time and space. I don't fancy bootup logos, Currently it will show wierd patterns on boot if you switch off and power on or the last screen you had if you reboot. This requires a small fix in the kernel which I will release with my next version with the new kernel.
Click to expand...
Click to collapse
can you also update the mmc part from my git, as I want to install your rom to my sdcard
Sent from my NexusHD2 using xda premium
Rick_1995 said:
Code:
This is my first and probably the last rom, thank you for your time.[/QUOTE]
no way to say that u just start and u will never stop tell u give up from us hahahahha ...i will test it but i have one qus. why cm7 ?? what about cm9 or jelly bean:p
Click to expand...
Click to collapse
seaman2k said:
no way to say that u just start and u will never stop tell u give up from us hahahahha ...i will test it but i have one qus. why cm7 ?? what about cm9 or jelly bean
Click to expand...
Click to collapse
I don't fancy compiling android, I'm more interested in the lower level work of bootloader and kernel. cm7 because it has most stuff working and is smooth, stable. This is the build i use whenever i go out like a man on a mission.
securecrt said:
can you also update the mmc part from my git, as I want to install your rom to my sdcard
Click to expand...
Click to collapse
Sorry, but i didn't get you what mmc part from your git should be updated ? or Do you want me to update the initrd for phoenix's method of system on sd-ext ?
Rick_1995 said:
I don't fancy compiling android, I'm more interested in the lower level work of bootloader and kernel. cm7 because it has most stuff working and is smooth, stable. This is the build i use whenever i go out like a man on a mission.
Sorry, but i didn't get you what mmc part from your git should be updated ? or Do you want me to update the initrd for phoenix's method of system on sd-ext ?
Click to expand...
Click to collapse
I mean, the mmc driver in the kernel,
I made the following changes from CAF.
81d9816
29e0f0d
08802ee
4eade39
2145485
I install your ROM with my own script to my SDCARD, it is different with DATA on SD-ext
Rick_1995 said:
This is my first and probably the last rom, thank you for your time.
Click to expand...
Click to collapse
Impressive stuff and as I can see a must have !
Going to try this asap m8 thanks for sharing
Arabic_support
here we go for arabic support u can flash this zip file i made it for this woundrfull light cm7 for rick (i hope he give us more)
http://www.multiupload.nl/5K1KOHWWOV
looking very impressive, system partition size is just 79mb awesome.
I have just ported this to SD using super Ram method This is very fast
i have download it , but i never flash this one becase we need ICS or JB
wis1152 said:
I have just ported this to SD using super Ram method This is very fast
Click to expand...
Click to collapse
pls post this link......this rom will always be the fallback....hv been keeping typhoon...now thats changed.
thanks rick...way to go man!
jully3881 said:
i have download it , but i never flash this one becase we need ICS or JB
Click to expand...
Click to collapse
Strange way of saying 'thank you' you have there...
good very lite rom, i like it
will report any bug i found
planing to buy a new phone so hd2 is just a toy for me now
and hope to not plug in sd card this rom is pretty good thanks a lot
gdsbalaji said:
pls post this link......this rom will always be the fallback....hv been keeping typhoon...now thats changed.
thanks rick...way to go man!
Click to expand...
Click to collapse
Uploading now, I will pm rick the link or is it better for me to post the port in SD thread. What's your thoughts rick?
Sent from my GT-I9100 using Tapatalk 2
wis1152 said:
Uploading now, I will pm rick the link or is it better for me to post the port in SD thread. What's your thoughts rick?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
As you wish, It's a work of community.
Thanks for this rick. Installed this in my eu and performance is amazing that's why I downloaded it! I drink San Miguel Lights, I smoke Marlboro Lights and my HD is light. :victory:
Rick_1995 said:
As you wish, It's a work of community.
Click to expand...
Click to collapse
Thanks for your work, can i use fikret kernel on your rom?if so how ?,would you help me
{
"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"
}
proudly presents
Dualboot for Nexus 10
I DO NOT OWN THIS DEVICE
thanks to @add12364 for testing
This is a Mod which allows you to switching between any Rom and any AOSP based rom.
Code:
System.out.println("
Your 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
Submitting bug reports on nightly builds is the leading
cause of male impotence.
");
Before you install this, please read the whole post!
Your first rom can be any Rom and second rom is any AOSP rom.
The second rom is installed on the /cache partition.
/data and /cache folder are in /data/media/.secondrom
This Mod switchs between two kernels.
The App will grab the kernel from your first rom, AOSP will use my ramdisk modified Kernel.
The RomSwitcher App will download the all needed files for you.
They will be in /sdcard/romswitcher
Sources:
https://github.com/RomSwitchers/RomSwitcher-manta
https://github.com/RomSwitchers/RomSwitcher
How to install?
You can use every AOSP rom as second rom
Download any AOSP rom. Extract it and open META-INF/com/google/android/updater-script
Look for this line (some roms have two of them)
Code:
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc.0/by-name/system", "/system");
and replace it with
Code:
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc.0/by-name/[B]cache[/B]", "/system");
then delete these lines
Code:
format("ext4", "EMMC", "/dev/block/platform/dw_mmc.0/by-name/system", "0", "/system");
and
Code:
package_extract_file("boot.img", "/dev/block/platform/dw_mmc.0/by-name/boot");
You will need Gapps
Get it here http://goo.im/gapps/
Extract it and open updater-script
and replace
Code:
run_program("/sbin/busybox", "mount", "/system");
with
Code:
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc.0/by-name/cache", "/system");
Zip your rom and gapps.
If you have troubles with editing the updater script, you can use my modified Paranoid Android Rom
http://d-h.st/qjO
Flash both in recovery. (first rom then gapps)
DO NOT WIPE ANYTHING
Reboot your phone and if you did all correct. You should boot into your current rom.
Now download and install my app
https://github.com/RomSwitchers/Downloadlinks/raw/master/RomSwitcher/RomSwitcher.apk
Open RomSwitcher and follow the instructions. (You need Root and BusyBox to use the App)
XDA:DevDB Information
RomSwitcher Manta, a Kernel for the Google Nexus 10
Contributors
Grarak
Kernel Special Features:
Version Information
Status: Testing
Created 2013-09-14
Last Updated 2013-10-05
Wipe data/cache on AOSP rom
Wipe data:
Delete /data/media/.secondrom/data
Wipe cache:
Delete /data/media/.secondrom/cache
Install new AOSP rom
Wipe cache in recovery and delete /data/media/.secondrom
then flash your new rom
Remove AOSP rom
Wipe cache in recovery and delete /data/media/.secondrom
Do you want support me?
You can buy me a beer via PayPal
Press Thanks
Press "Tip us?" above the OP
Rate this Thread with 5 Stars
Report bugs
FAQ
I forget my password for RomSwitcher! help?!!
delete /sdcard/romswitcher-tmp/pass
I can't switch back to firstrom! why?
Check root access, check busybox, use SuperSu
Why the app keeps force closing?
Not my problem. I've written the app that this shouldn't happen
I want to remove 2nd rom. How???!!
Wipe options in the app
Error in recovery when I install 2nd rom!
don't use editor, wordpad, .. (all windows programms)
Credits
CyanogenMod (for kernel)
Jijonhyuni (using the same dualboot method as he does on Galaxy Nexus)
Gokhanmoral (using some scripts of his Siyah Kernel)
add12364 (for testing and support)
[email protected] (GraSwitcher Banner)
Paul O'Brian (for concept)
Changelog
05 Oct
RomSwitcher App:
Rework on the App:
new features:
Setup Menu
enable App/Data Sharing
Wipe options for 2nd rom
OTA updates
Password
RomSwitcher Kernel:
use /data/media/.secondrom as folder for data and cache for 2nd rom
new scripts for App/Data Sharing
15 Sept
RomSwitcher Kernel:
Enable App/Data Sharing (Experimental)
29 Aug
Inital Release
Awesome I'd like to try this but I'll wait till I know more about my nexus 10
Sent from my Nexus 10 using xda app-developers app
This is awesome. Congrats on your hard work, and look forward to trying this out soon!
-------------------------------------------------------------------------------------
Sent from my Nexus 10
Devices:
Nexus 10 - Paranoid Android 3.98 - Der Kernel 3X
Nook Tablet - CM 10.2 - NOF Showtime Kernel
Nice Post! Is there a way I could do this on Windows cause I need to get GAPPs and I want to try CM dual boot. Thanks!
add12364
add12364 said:
Nice Post! Is there a way I could do this on Windows cause I need to get GAPPs and I want to try CM dual boot. Thanks!
add12364
Click to expand...
Click to collapse
Another guy will take over thread because he will maintain this
So be patient he will provide you the gapps
Sent from my GT-I9500 using xda app-developers app
Good news for Xperia Z users
Mithun successful ported it
App sharing is on the way. Nexus devices will get it first
Grarak said:
Good news for Xperia Z users
Mithun successful ported it
App sharing is on the way. Nexus devices will get it first
Click to expand...
Click to collapse
There's a bit of instability. I was wondering how I could uninstall the second ROM for now. I will come back to dual booting but my tablet is running out of space and I want to wipe the second ROM to get space.
add12364 said:
There's a bit of instability. I was wondering how I could uninstall the second ROM for now. I will come back to dual booting but my tablet is running out of space and I want to wipe the second ROM to get space.
Click to expand...
Click to collapse
Second post
Sent from my GT-I9500 using xda app-developers app
Grarak said:
Second post
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
If you ever need N10 testing just send me a message! This MOD is my favorite.
When you go through the process of modifying the updater scripts and then flashing the modified zips, will that become the 2nd rom and NOT overwrite the rom you already have installed? Just making sure I known what's happening before I do this. Thanks!
-------------------------------------------------------------------------------------
Sent from my Nexus 10
Devices:
Nexus 10 - Paranoid Android 3.98 - Der Kernel 3X
Nook Tablet - CM 10.2 - NOF Showtime Kernel
So could this be used to dual boot CM and Ubuntu touch?
That to me would be the biggest reason to use this mod.
tb01110100 said:
When you go through the process of modifying the updater scripts and then flashing the modified zips, will that become the 2nd rom and NOT overwrite the rom you already have installed? Just making sure I known what's happening before I do this. Thanks!
-------------------------------------------------------------------------------------
Sent from my Nexus 10
Devices:
Nexus 10 - Paranoid Android 3.98 - Der Kernel 3X
Nook Tablet - CM 10.2 - NOF Showtime Kernel
Click to expand...
Click to collapse
why should I give you instructions which override your current rom?
DroidZombie said:
So could this be used to dual boot CM and Ubuntu touch?
That to me would be the biggest reason to use this mod.
Click to expand...
Click to collapse
Do you think an android app will run on ubuntu touch?
Sent from my GT-I9500 using xda app-developers app
Grarak said:
Do you think an android app will run on ubuntu touch?
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Of course not, that's not what I was asking.
Ubuntu touch is based on cm so in theory your mod might allow it to boot as the secondary rom.
Sent from my SC-06D using XDA Premium HD app
Grarak said:
why should I give you instructions which override your current rom?
Do you think an android app will run on ubuntu touch?
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Please, cut the guy a break, the instructions in the OP aren't exactly what I'd call 'clear.' The instructions clearly state that the "default kernel for the first ROM is CM kernel." Sure sounds to me like this erases/alters the current ROM, or else how would the CM kernel get on my device, currently running Trinity? It also says that we can use any kernel we want, well the kernel I want is already installed, again, does it alter the current ROM or not? If not, where does the CM kernel come into play on the random AOSP ROM that I elect to flash as the second ROM? Then in the second post there is no indication of which AOSP ROM is being changed. If I just follow those instructions I wipe both ROMs, unless we redo the script edit before the flash, which is not stated there. Finally, how would I change just the first ROM? I can't wipe cache, as that would blow away the second ROM. Do I have to reinstall both?
As for Ubuntu, I was even unaware that UT lacks the Dalvik VM. A simple explanation would have sufficed.
I immensely respect both you and what you are doing, for both the device and the community as a whole, and I am not trying to be hostile or to be an ass, so please don't take offense to this. Just please don't go jumping down people throats, especially over a procedure that is deeply removed from the realm of everyday protocol, even for people on XDA.
Koopa777 said:
As for Ubuntu, I was even unaware that UT lacks the Dalvik VM. A simple explanation would have sufficed.
I immensely respect both you and what you are doing, for both the device and the community as a whole, and I am not trying to be hostile or to be an ass, so please don't take offense to this. Just please don't go jumping down people throats, especially over a procedure that is deeply removed from the realm of everyday protocol, even for people on XDA.
Click to expand...
Click to collapse
Thank you for the support Koopa.
Grarak said:
angry reply
Click to expand...
Click to collapse
To the OP below is the reason I was CURIOUS about the possibility of Ubuntu touch working with this method. I never demanded that it work with android apps. I know that it would not.
Canonical on Ubuntu wiki said:
How is Ubuntu Touch connected to Android?
The independent open source project CyanogenMod which is based on Android and tries to improve and extend the existing Android Basis has been taken by the developers as a kind of underlaying basis for Ubuntu Touch. The kernel and a few low level drivers for network, video, audio and some other hardware features are taken, all the higher level parts have been taken out. On top of this the whole Ubuntu is started in an chroot environment.
Click to expand...
Click to collapse
This is what does work on UT.
Canonical on Ubuntu wiki said:
Which applications do run on Ubuntu Touch?
Ubuntu Touch is primarily designed to support web apps, and native apps programmed in qml and javascript or C++. As it is a real linux, of course all non graphical applications run equally as on any other linux system. You can ssh to Ubuntu Touch and run any console based application.
X11 is not supported (so far) so all GUI standard applications will not run.
Click to expand...
Click to collapse
and...
Canonical on Ubuntu wiki said:
Can I develop programs directly on Ubuntu Touch?
Ubuntu Touch is a real linux, of course you can install a c compiler and all the rest of the essential-build system and can develop on the mobile devices like on any other linux.
Click to expand...
Click to collapse
Maybe now you will understand why I was so interested in your project. The development possibilities are enormous.
Next time think before you tear into people.
Ubuntu touch works with that method on my gnexus. But have to modify the whole ramdisk to make switching working and I am really too lazy to do it for a device which I don't own. Be happy that I am supporting this device. I really didn't want to support the nexus 10.
Sent from my GT-I9500 using xda app-developers app
Grarak said:
Ubuntu touch works with that method on my gnexus. But have to modify the whole ramdisk to make switching working and I am really too lazy to do it for a device which I don't own. Be happy that I am supporting this device. I really didn't want to support the nexus 10.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Right then. Are you willing to help someone else learn how to do it? I assume from your signature that you are trying to build a "team". I volunteer.
DroidZombie said:
Right then. Are you willing to help someone else learn how to do it? I assume from your signature that you are trying to build a "team". I volunteer.
Click to expand...
Click to collapse
I can give you a tip
Study dualboot methods from other devs. I cannot help you
Sent from my GT-I9500 using xda app-developers app
{
"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"
}
Hello everyone!
Together with @h0rn3t we bring you Dual Boot Support for the Samsung Galaxy Wonder (Ancora)
Let's get started
Requirements:
Root
Busybox
CM or other AOSP like ROM based on 4.0+
Minimum ~350MB internal storage free space
External SD (min 4GB, the higher class, the better)
Description:
The process is fairly simple. The application will format your external-sd (we recommend to back up your personal data), then create 3 partitions as follows:
/dev/block/mmcblk1p1 -> storage (formatted VFAT)
/dev/block/mmcblk1p2 -> /system (formatted EXT4)
/dev/block/mmcblk1p3 -> /data (formatted EXT4)
After that you'll be given the possibility to flash a secondary ROM on your EXT-SD (currently only 4.1.2+ ROM's are supported as secondary and 4.0+ as primary).
At last, you'll be able to switch between ROM's within the app.
Process:
WARNING: Partitioning and flashing operations could take up to 5 minutes to complete, please be patient !
Download the app and kernel pack from the Downloads section
If you want the app to be automatically installed on the secondary ROM, push the app to /system/app and give proper permissions (rw-r-r or 644). Otherwise, just install it normally.
Backup your personal data from the external sd card.
Run the app and partition your external-sd.
In app, choose flashing then choose your preferred secondary ROM from your internal SD card (must be 4.1.2 or higher).
Your phone will reboot into recovery and automatically flash the secondary ROM. (in CWM, if you get "Signature Verification Failed", continue flashing, it is normal)
After the flashing process is done, you'll be redirected to your primary ROM.
On your internal SD-Card, you'll have a folder called DualBootSplus, open it up.
Copy the kernels from the kernels pack into their appropriate subfolder. (eg CM-10 kernel (boot2.img) goes into 4.1.2 subfolder -> you'll have to create the subfolder if it doesn't exit)
Now you can switch between ROM's or flash secondary gapps within the app.
Additional details:
You must put only 1 boot2.img in each DualBootSplus subfolders.
The kernel will determinate which ROM will be booted. So, if you have a primary and secondary ROM, you can quickly switch between them within the app (make sure you have the kernels in the SD-Card subfolders), or manually by flashing the correspondent kernel.
The boot2.img can be flashed separately in ADB.
Special thanks goes to @arsradu for his kernels and @Madridii for testing.
XDA:DevDB Information
[GT-I8150] Dual Boot [ANCORA], Tool/Utility for the Samsung Galaxy W I8150
Contributors
educk, h0rn3t
Version Information
Status: Stable
Current Stable Version: 1.5.1
Stable Release Date: 2013-10-27
Created 2013-10-04
Last Updated 2014-05-20
For Kernel Developers
For Kernel Developers
How to make a kernel suitable for dual-booting (mounting ext-sd partition)
We know that a kernel (for Galaxy W, S Plus and many others) has 2 major components. The RAMDISK and the zImage.
The RAMDISK is responsible for mounting and other init processes so to successfully boot up a secondary ROM (from the external SD-Card) we need a kernel with a modified RAMDISK, so that it recognizes these external partitions.
As stated in the OP, the app partitions the ext-sd like this:
/dev/block/mmcblk1p1 -> storage (formatted VFAT)
/dev/block/mmcblk1p2 -> /system (formatted EXT4)
/dev/block/mmcblk1p3 -> /data (formatted EXT4)
So these are the exact instructions we should pass to the fstab. (this particular file from the RAMDISK is responsible for disk mounting).
I pasted here a modified fstab.qcom which should explain pretty much everything I did to make a proper dual boot kernel:
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
[B]/dev/block/mmcblk1p2[/B] /system ext4 ro,barrier=1 wait
/dev/block/mmcblk0p16 /cache ext4 nosuid,nodev,barrier=0 wait,check
[B]/dev/block/mmcblk1p3[/B] /data ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=1 wait,check,encryptable=footer
Please note that fstabs might vary with Android version.
Currently, only 3.0 kernels are able to mount ext-sd partitions, the 3.4 one has some bugs/differences in the emmc driver which were not fixed/adapted until now.
For decompiling the boot image there are several tools out there. My personal favorite is bootimgtools, there are several toolkits which use this little binary like dsixda's Android Kitchen.
Good luck!
educk said:
Hello everyone!
Together with @h0rn3t we bring you Dual Boot Support for the Samsung Galaxy Wonder (Ancora)
Let's get started
Requirements:
Root
Busybox
CM or other AOSP like ROM based on 4.0+
Minimum ~350MB internal storage free space
External SD (min 4GB, the higher class, the better)
Click to expand...
Click to collapse
awesome job:thumbup:
Sent from my GT-I8150
finally, thanks mr educk :good::good:
---------- Post added at 12:33 AM ---------- Previous post was at 12:24 AM ----------
hi mr educk, it's that ok if i swap the mmc to sd when dual boot ? sorry bad english
Good job mate... thanks :thumbup:
Awesome
Thanks sir educk:thumbup::thumbup:
I have to think about it because i already formatted and configured my ext-sd to be used as app swap with link2sd.
Thanks a lot nevertheless!
tycoo said:
I have to think about it because i already formatted and configured my ext-sd to be used as app swap with link2sd.
Thanks a lot nevertheless!
Click to expand...
Click to collapse
haha sure, i'm just test it, my second rom is swap mmc to sd and i forgot to change it, it's run very laggy on second rom
GOOD!!
thank you very much educk .
now we are able to use stock rom and cm together on the one phone :good::good::good::good:
you are awesome man thanx again
sir mordred said:
thank you very much educk .
now we are able to use stock rom and cm together on the one phone :good::good::good::good:
you are awesome man thanx again
Click to expand...
Click to collapse
i think no, the primary rom is 4.0.+ and secondary is 4.1.2+
sir mordred said:
thank youcan't use sy much educk .
now we are able to use stock rom and cm together on the one phone :good::good::good::good:
you are awesome man thanx again
Click to expand...
Click to collapse
First big thanks to Mr Erik..
No you cant use stock rom as primary read carefully ..
We hope it will support cm9 and 2.3.6
fsl7th said:
i think no, the primary rom is 4.0.+ and secondary is 4.1.2+
Click to expand...
Click to collapse
no first rom is cm10.1 second rom is stock
if there is a cwm flashable stock rom for galaxy w like that XXLB4.zip ı think we can do it
sir mordred said:
no first rom is cm10.1 second rom is stock
if there is a cwm flashable stock rom for galaxy w like that XXLB4.zip ı think we can do it
Click to expand...
Click to collapse
but the rule is that the second rom must be 4.1.2+, that's why mr educk append the cm 10 and cm 10.1 kernel on his post,
correct me if im wrong
fsl7th said:
but the rule is that the second rom must be 4.1.2+, that's why mr educk append the cm 10 and cm 10.1 kernel on his post,
correct me if im wrong
Click to expand...
Click to collapse
You are right.
As stated in the OP, the primary ROM can be any either ICS or JB (4.1.2 & 4.2.2).
The secondary can be only JB (4.1.2 & 4.2.2). Make sure you have the appropriate dual boot kernel (boot2.img) in the correspondent sub folder from /sdcard/DualBoot.
I'm working on ICS as secondary. After that, we'll see about GB.
educk said:
You are right.
As stated in the OP, the primary ROM can be any either ICS or JB (4.1.2 & 4.2.2).
The secondary can be only JB (4.1.2 & 4.2.2). Make sure you have the appropriate dual boot kernel (boot2.img) in the correspondent sub folder from /sdcard/DualBootAncora.
I'm working on ICS as secondary. After that, we'll see about GB.
Click to expand...
Click to collapse
Is cm 10.2 not possible ?
Guys, I made a mistake in the application. Please wait few minutes until I fixed... Sorry for inconvenient !
---------- Post added at 11:02 PM ---------- Previous post was at 10:53 PM ----------
OK. Problem solved. Please update your application. You must put boot2.img files in DualBoot folder. If you already have DualBootSplus folder rename it DualBoot.
The correct folder is /sdcard/DualBoot. You must have something like this /sdcard/DualBoot/4.2.2/boot2.img
Well, thanks guys! I've been waiting for you to do that for ancora.
Sent from my GT-I8150 using Tapatalk 4
This is really new for galaxy w, Amazing work educk.... :thumbup:
Sent from my LT29i using Tapatalk 4
does it support cm9 as secondary ?
Dwama said:
does it support cm9 as secondary ?
Click to expand...
Click to collapse
Not yet !
Hello There!
I am here with a good news and a bad news!
The good news is that I have sucessfully compiled TWRP recovery for our beloved Xperia M!
The bad news is that It is unstable, and I am not able to make it stable. I need help from some developers in order to make it stable.
Please note that this kernel bringup is only for CM11 FXP310.So, dont try it on other ROMs, as your may get into a serious problem after that.
Please bear with me, as I am a noob and will need a lot of help in making this stable for use!
Sources :
The TWRP sources can be found here : https://github.com/omnirom/android_bootable_recovery
The device tree of rebelos(contains commits for TWRP bringup, thanks to him for letting me use the tree) : https://github.com/rebelos/android_device_sony_nicki
The Kernel sources used : https://github.com/freexperia/android_Kernel_sony_msm8x27
Working /Not working
Working :
Normal Touch
Navigation
And Basic operations
Not - Working
Some glitches (sometimes) [that is, the half screen problem]
Screenshots(again, thanks to Bonoboo)
{
"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"
}
Downloads
New flashable zip(thanks to Bonoboo) : https://www.mediafire.com/?gg84xysk8w64fwc
OLD[not recommended for use] :
boot.img
recovery.img ( I am having problems installing this, via fastboot. Use boot.img)
Changelogs
16-03-2014
Initial Release
17-03-2014
fixed up the bugs in main ROM. i.e, the wifi and RIL bugs.
Credits :
PecanCM - For sources
FXP, for supporting this device officially
rebelos for allowing me to use his updated commits in device tree. His device tree can be found on his github.
Bonoboo for giving the idea of packing the ramdisk(the partition with recovery and the boot.img) and for packing it up for me!
A note : I need help from you all to achieve this task Please help me up.
XDA:DevDB Information
[RECOVERY] TWRP, a Tool/Utility for the Sony Xperia M
Contributors
PixCM
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2014-03-17
Created 2014-03-16
Last Updated 2014-03-18
lol twrp.. just got real ..
see these commits
https://github.com/freexperia/android_device_sony_nicki/pull/1
these will fix all your issues
rebelos said:
lol twrp.. just got real ..
see these commits
https://github.com/freexperia/android_device_sony_nicki/pull/1
these will fix all your issues
Click to expand...
Click to collapse
Thank You soo much Will compile and post in an hour or so! Got to do something else at the moment
Tried.. But they didnt help :/ Same bugs!
Finally, TWRP! Thanks!
About problems with Wi-Fi and RIL – yes, it's really due compiling kernel on your side.
I extracted from your boot.img ramdisk-recovery.cpio and replaced it in kernel from latest FXP310 build – all fine.
So maybe you do the same in future for avoiding problems?
Recovery bundled in boot.img so recovery.img can't be flashed with saving current kernel.
I think better to post ramdisk-recovery.cpio so users can combine it with needed in their case kernel: stock, modded or whatever.
Here easy tutorial and tool for do these on Windows. Almost same for Linux.
Bugs:
– no mount of any partitions
– screen most time halved
– at screen timeout it don't off
Best Recovery Shown up!
TWRP just the best recovery ever... my fav.
hope this can be fixed soon... thanks for the good job
Good work bro...
Sent from my C1905 using XDA Premium 4 mobile app
Thanks mate for TWRP recovery! Always used this on my GT-I9100
Wating for an update
Sent from my C1905 using Tapatalk
Bonoboo said:
Finally, TWRP! Thanks!
About problems with Wi-Fi and RIL – yes, it's really due compiling kernel on your side.
I extracted from your boot.img ramdisk-recovery.cpio and replaced it in kernel from latest FXP310 build – all fine.
So maybe you do the same in future for avoiding problems?
Recovery bundled in boot.img so recovery.img can't be flashed with saving current kernel.
I think better to post ramdisk-recovery.cpio so users can combine it with needed in their case kernel: stock, modded or whatever.
Here easy tutorial and tool for do these on Windows. Almost same for Linux.
Bugs:
– no mount of any partitions
– screen most time halved
– at screen timeout it don't off
About screenshots.
Please hide them under spoiler – thread very lagre with them now.
Here flashable ZIP with original FXP310 kernel and this recovery.
Click to expand...
Click to collapse
Thanks dude! I will give you another build, check if the mount is working in this one!
Check your PM.
SUM ONE SAY TWRPDDDDDD goddamn, i want try it, but after the bug like wifi-RIL etc fixed
PixCM said:
Thanks dude! I will give you another build, check if the mount is working in this one! .
Click to expand...
Click to collapse
– Now all partitions mounts, switching internal/external storage ok too. Thanks!
– ADB works
– But there no option for USB Mass storage connection
– Screen still halved, affect touch too
– Screen timeout still broken
Here directly captured screenshots.
Please replace screens in first post and hide them under spoiler.
Richardsentosa said:
i want try it, but after the bug like wifi-RIL etc fixed
Click to expand...
Click to collapse
Use this flashable ZIP with original FXP310 kernel and this new version recovery. No bugs in main ROM (CM11).
Bonoboo said:
– Now all partitions mounts, switching internal/external storage ok too. Thanks!
– ADB works
– But there no option for USB Mass storage connection
– Screen still halved, affect touch too
– Screen timeout still broken
Here directly captured screenshots.
Please replace screens in first post and hide them under spoiler.
Use this flashable ZIP with original FXP310 kernel and this new version recovery. No bugs in main ROM (CM11).
Click to expand...
Click to collapse
but now i using HellKat .-.
Updated
Updated OP with new build.
Download : https://www.mediafire.com/?gg84xysk8w64fwc
Special thanks to @Bonoboo for this
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Bonoboo said:
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Click to expand...
Click to collapse
If I will be compiling again, then it would be in any form. You say. Which one is better? I think for people's use, its better to release in boot.img form. Or else, I will do one thing..
I will release it in both the forms.
P.S I will be updating the OP soon. In an hour or so.
And, will you become my tester? I will send you links to build through PM. I am trying to compile omni at the moment.
PixCM said:
I will release it in both the forms.
Click to expand...
Click to collapse
Yes, this will be nice and more flexible: someone can manually add recovery in beloved kernel and CM11 users can directly flash it.
PixCM said:
And, will you become my tester?
Click to expand...
Click to collapse
Recovery – yes, but not ROM, sorry.
PixCM said:
If I will be compiling again, then it would be in any form. You say. Which one is better? I think for people's use, its better to release in boot.img form. Or else, I will do one thing..
I will release it in both the forms.
P.S I will be updating the OP soon. In an hour or so.
And, will you become my tester? I will send you links to build through PM. I am trying to compile omni at the moment.
Click to expand...
Click to collapse
OmniROM with TWRP recovery is brilliant mate! Hope you will release it
Sent from my C1905 using Tapatalk
a new build? i will try it (if i flashed the FXP CM11)
Richardsentosa said:
a new build?
Click to expand...
Click to collapse
Yep, CM11 FXP311 released.
Here flashable zip with kernel from there with integrated this TWRP recovery.
Bonoboo said:
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Click to expand...
Click to collapse
+1 lol... you just wrote what i want to...
now it's being clear...
coz i need to replace the whole cwm from every Roms i've downloaded... yeah... keep it rolling dude :good:
CM11 FXP312 released.
Here flashable zip with kernel from there with integrated this TWRP recovery.