Related
CyanogenMod 7 (w/ Gingerbread 2.3.7) for Galaxy SII
The only rule of CyanogenMod: you don't ask for ETAs. You install, your warranty is void.
Warning : Not for new users, flash this build only if you know what you are doing !!!
FAQ (Please Read!!)
What is CyanogenMod (by mad-murdock)?
CyanogenMod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Q: How do I install this?
A:
Latest version: http://download.cyanogenmod.com/?device=galaxys2 (for when nightlies are working normally)
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Galaxy S2 (or coming from another ROM)?
Only for the International version of the Galaxy S2, US versions like the AT&T have their own device specific builds.
Note: sometimes you need to flash twice back to back without a reboot in the middle. The install should take a little time, if it happens very quickly, flash again.
Install via ClockworkMod (do not use ROMManager for initial install):
Make sure you're running a rooted device.
Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/showthread.php?t=1118693)
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
Install the ROM from internal sdcard using ClockworkMod Recovery.
Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
Reboot
Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
- Upgrading from earlier CM7?
ROM Manager method:
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Samsung Galaxy S2.
Choose Download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe cache, dalvik cache.
Let ROMManager finish the installation.
Clockwork Mod method:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for Samsung Galaxy S2, choose Download ROMs, and pick Google Apps. Or download and push the gapps zip for CM7 from http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps to the sdcard and flash it via ClockworkMod recovery.
- Going to another ROM from CM7?
You can go back and forth freely between CM7 and other ROMs via ROM Manager or ClockworkMod recovery as the file systems are the same and nandroid backup/restore works to go between ROMs.
Q: What are the known issues?
A: Issues that I can remember:
- Video playback - some formats are not recognized, use an alternative app for video playback
- Camera - some modes don't work
- TVout, MHL
- FMRadio
- Issues when using the 2G/3G-Switch
- Volume issues (some report too high, others too low)
Q: Where do I see the Changelogs?
A: http://cm-nightlies.appspot.com/?device=galaxys2 - this shows all the
changes that have gone into a nightly, including anything that is device specific to Galaxy S2 and anything that has gone into common code that is also included on Galaxy S2. If you see another device sometimes in the Galaxy S2 changelog, it is because the changes were done to common code and the repository is also included on the Galaxy S2.
Q: Can I flash over a previous version of CM7?
A: If updating from an already CM7 running SGSII phone, just flash the latest update zip file as it contains all the fixes from previous updates.
Q: I just installed and I don't see the Marketplace, cannot see GMail, cannot sync Contacts.
Q: I just installed and I don't see any Google Apps.
A: You need to install the Google apps. They are available in ROMManager. ROMManager also asks you if you want to install the Google Apps addon when you install via ROMManager.
Q: My phone is running too hot, my phone is not going into deep sleep
A: Try to isolate which application is using too much CPU. The first thing to try is to remove your media (video, music etc) files. Files recorded using Samsung camera, but other files as well, can frequently cause the stock Media Scanner to fail and go into an infinite loop. Then try to isolate which files are causing problems, and report them to us. If it isn't media, then it is some other application. Try to remove that application if it is a third-party application (and report a bug to them).
Q: I cannot find my media files that are on my external sd card
A: Look under /mnt/emmc as that is where CM7 mounts the external sd card as opposed to /mnt/sdcard/external_sd that Samsung ROMs use.
Q: Can I run Samsung Applications like Kies, Phone, Email, AllShare?
A: No. Any applications that use special calls into the Samsung TouchWiz framework will not work.
Q: I restored from Titanium Backup but my applications are not working
A: Do not restore system data, only restore application+user data. CM7 uses new system data and if you restore on top of it, things will not work.
Q: Your notification toggles are different than mine, how can I change them?
A: Go into Settings, CyanogenMod Settings, Interface, Notification power widget, Widget buttons
Q: My Notification bar Sound widget does not toggle through the options.
A: Settings > CyanogenMod Settings > Interface > Notification Power Widgets > Widget Buttons > Sound Modes and set the modes you want it to toggle through.
Q: I really miss the accurate battery mods, can I flash these?
A: No, but you can go into Settings, CyanogenMod Settings, Interface, Status bar tweaks, "Battery percentage"
Q: Where can I get themes for this?
A: A quick search for "theme engine" on the market will produce a number of results, but there are some in the general Android Themes section
Q: Can I use the video player/music player/contacts/phone/launcher from a Samsung ROM?
A: No, anything hooking into Samsung's framework will not work on this ROM, there are plenty of alternatives in the market.
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you installed the SDK
Q: How do I go back to a Samsung stock ROM?
A: Just use ClockworkMod or ROM Manager backup/restore facility to go back and forth between stock (or any other ROM) and CM7.
Q: Can I use ROM Manager to install or back up this ROM?
A: Yes.
Q: Why do I not see the nightlies in ROM Manager?
A: Nightly builds are only visible in the premium version of ROM Manager. Nightly builds should up in ROM Manager when the CyanogenMod buildbot builds the nightly successfully. Every new device needs to also get added to the ROM Manager manifest before it is available. But, the same files are also available at http://download.cyanogenmod.com when the buildbot successfully builds a nightly.
Q: Why can't I play .avi or .mkv files? They worked fine with Samsung's ROM.
A: Due to codec licensing issues, this can't be provided out of the box. Several apps from the marketplace should be able to replicate this feature (such as RockPlayer). We will also try to put these enhancements into CM7 ourselves.
Q: I encountered a bug, how do I find out if it's known and where can I report it?
A: Try to get the logcat output and last_kmsg to your report by:
Code:
desktop$ adb logcat > logcat.txt
desktop$ adb shell
# cat /proc/last_kmsg > /sdcard/last_kmsg (only if you had crash/reboot)
# dmesg > /sdcard/dmesg.txt
# exit
desktop$ adb pull /sdcard/last_kmsg .
desktop$ adb pull /sdcard/dmesg.txt .
Attach the logcat.txt and last_kmsg files to the bug report. Of course, you need to have the android SDK installed to do this.
Hi !
Why we don't see Cyanogen Builds in ROM Manager Premium ?
Thanks & sorry for my bad English.
Nice Q&A here. This is a MUST READ before flashing CM7
Q: Why do I not see the nightlies in ROM Manager?
A: Nightly builds are only visible in the premium version of ROM Manager.
Click to expand...
Click to collapse
I have premium rom manager but dont see any cm7 roms in the download section
???
darkevangerion said:
Hi !
Why we don't see Cyanogen Builds in ROM Manager Premium ?
Thanks & sorry for my bad English.
Click to expand...
Click to collapse
They will be there when the CyanogenMod buildbot successfully builds a nightly - hopefully tonight.
Thanks for your fast answer.
And thanks for the rom, obviously
EDIT : Hmmm... "Tonight" = "Tomorrow" for European. :/
They will be there when the CyanogenMod buildbot successfully builds a nightly - hopefully tonight.
Click to expand...
Click to collapse
Thanks.
Why can't i register my device for notification on updates from nightly?
I got rom manager premium
Sent from my GT-I9100 using XDA Premium App
Answered 3 posts above.
Firstly, I love the first release of CM for the S2....very quick.
I have successfully replaced the samsung apps I liked, and i have gapps installed. One question is, now when I go into the market on my PC it says I have no Android devices to send the apps too.
On the S2, the market is fine.
any ideas?
I can see in Rom managet premium only cognition and darks rom. Is it normal? Anyone else witht the same stats?
carda21 said:
Firstly, I love the first release of CM for the S2....very quick.
I have successfully replaced the samsung apps I liked, and i have gapps installed. One question is, now when I go into the market on my PC it says I have no Android devices to send the apps too.
On the S2, the market is fine.
any ideas?
Click to expand...
Click to collapse
It's strange, it's work fine for me.
Hunteres said:
I can see in Rom managet premium only cognition and darks rom. Is it normal? Anyone else witht the same stats?
Click to expand...
Click to collapse
Take a look at the #5 post
No official nightly build has been built yet by the build bot......thats the automated rombuilder witch is used to build the roms.....so if no rom is built no rom in rom manager ......
Sent from my GT-I9100 using Tapatalk
i have just tryed installing an app via the market website to my mobile and its working fine for me....
Hello,
Is there any way I can increase vibration intensity? It is fine when I reboot it but after a minute the vibration becomes very weak to the point where I can barely feel it. (When typing and pressing "menu" or "back button" etc
Sent from my GT-I9100 using XDA App
It's a known issue of this ROM.
There is nothing to do for this time.
Cyanogen #1 !
Issue gonna be FIX, by next build's
i just have one question, someone said they used kg1 modem does that actually stay or would cm7 just overwrite it anyway?
since im too noob to post in development section i want to thank you all at teamhacksung for this
Also...why was the stock camera app replaced with one that is worse? (Camcorder is worse.) Its a great rom. But can someone explain this to me?
Sent from my GT-I9100 using XDA App
CyanogenMod is a free, community built distribution of Android 2.3.7 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Warning : Not for new users, flash this build only if you know what you are doing !!!
What is CyanogenMod (in less terse form - by mad-murdock)?
since i am a bit idle right now, i try to answer this.
cyanogenmod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Installation instructions:
in following post - will move moved to Q&A Forum when that is up.
teamhacksung:
atin - http://gplus.to/atinm
codeworkx - http://gplus.to/codeworkx
coolya - http://gplus.to/coolya
unhelpful - http://twitter.com/unhelpfulone
Changelog:
Generic Changelog CMSRC Twitter
Device specific Changelog by igor.tonky
Modems:
TBD
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
CyanogenMod 7 (w/ Gingerbread 2.3.7) for AT&T Galaxy SII
The only rule of CyanogenMod: you don't ask for ETAs. You install, your warranty is void.
Warning : Not for new users, flash this build only if you know what you are doing !!!
FAQ (Please Read!!)
What is CyanogenMod (by mad-murdock)?
CyanogenMod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Q: How do I install this?
A:
Latest version:
Temporarily while buildbot is down:
You can get it from ROM Manager (look for teamhacksung builds for Galaxy SII AT&T) or
http://www.multiupload.com/RT29P7AOFS (md5: c8115d0a01d0a47b286ff5c9cc504175)
Previous kang: http://www.multiupload.com/A30J9DZN37 (md5: a23d1b99ff73da31e5d0421ec18e15e3)
Normally: http://download.cyanogenmod.com/?type=nightly&device=galaxys2att
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Galaxy S2 (or coming from another ROM)?
Note: You may need to flash twice back to back if the first one goes by too quickly - the actual flash takes a little time and sometimes the first flash doesn't "stick".
Install via ClockworkMod recovery (do not use ROMManager for initial install):
Make sure you're running a rooted device.
Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/showthread.php?t=1118693)
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
Install the ROM from internal sdcard using ClockworkMod Recovery.
Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
Reboot
Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
- Upgrading from earlier CM7?
ROM Manager method:
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Samsung AT&T Galaxy S2.
Choose Download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe cache, dalvik cache.
Let ROMManager finish the installation.
Clockwork Mod method:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for AT&T Samsung Galaxy S2, choose Download ROMs, and pick Google Apps. Or download and push the gapps zip for CM7 from http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps to the sdcard and flash it via ClockworkMod recovery.
- Going to another ROM from CM7?
You can go back and forth freely between CM7 and other ROMs via ClockworkMod recovery as the file systems are the same and nandroid backup/restore works to go between ROMs.
Q: What are the known issues?
A: Issues that I can remember:
- Video playback - some formats are not recognized, use an alternative app for video playback
- Camera - some video and still modes don't work
- TVout, MHL
- Dock
Q: Where do I see the Changelogs?
A: http://cm-nightlies.appspot.com/?device=galaxys2att - this shows all the changes that have gone into a nightly, including anything that is device specific to Galaxy S2 and anything that has gone into common code that is also included on Galaxy S2. If you see another device sometimes in the Galaxy S2 changelog, it is because the changes were done to common code and the repository is also included on the Galaxy S2.
Q: Can I flash over a previous version of CM7?
A: If updating from an already CM7 running SGSII phone, just flash the latest update zip file as it contains all the fixes from previous updates.
Q: I just installed and I don't see the Marketplace, cannot see GMail, cannot sync Contacts.
Q: I just installed and I don't see any Google Apps.
A: You need to install the Google apps. They are available in ROMManager. ROMManager also asks you if you want to install the Google Apps addon when you install via ROMManager.
Q: Can I run Samsung Applications like Kies, Phone, Email, AllShare?
A: No. Any applications that use special calls into the Samsung TouchWiz framework will not work.
Q: I cannot find my media files that are on my external sd card
A: Look under /mnt/emmc as that is where CM7 mounts the external sd card as opposed to /mnt/sdcard/external_sd that Samsung ROMs use.
Q: My phone is running too hot, my phone is not going into deep sleep
A: Try to isolate which application is using too much CPU. The first thing to try is to remove your media (video, music etc) files. Files recorded using Samsung camera, but other files as well, can frequently cause the stock Media Scanner to fail and go into an infinite loop. Then try to isolate which files are causing problems, and report them to us. If it isn't media, then it is some other application. Try to remove that application if it is a third-party application (and report a bug to them).
Q: I restored from Titanium Backup but my applications are not working
A: Do not restore system data, only restore application+user data. CM7 uses new system data and if you restore on top of it, things will not work.
Q: Your notification toggles are different than mine, how can I change them?
A: Go into Settings, CyanogenMod Settings, Interface, Notification power widget, Widget buttons
Q: I really miss the accurate battery mods, can I flash these?
A: No, but you can go into Settings, CyanogenMod Settings, Interface, Status bar tweaks, "Battery percentage"
Q: Where can I get themes for this?
A: A quick search for "theme engine" on the market will produce a number of results, but there are some in the general Android Themes section
Q: My Status bar Sound widget does not toggle through the options.
A: Settings > CyanogenMod Settings > Interface > Notification Power Widgets > Widget Buttons > Sound Modes and set the modes you want it to toggle through.
Q: Can I use the video player/music player/contacts/phone/launcher from a Samsung ROM?
A: No, anything hooking into Samsung's framework will not work on this ROM, there are plenty of alternatives in the market.
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you installed the SDK
Q: How do I go back to a Samsung stock ROM?
A: Just use ClockworkMod or ROM Manager backup/restore facility to go back and forth between stock (or any other ROM) and CM7.
Q: Can I use ROM Manager to install or back up this ROM?
A: Yes.
Q: Why do I not see the nightlies in ROM Manager?
A: Nightly builds are only visible in the premium version of ROM Manager. Nightly builds should up in ROM Manager when the CyanogenMod buildbot builds the nightly successfully. Every new device needs to also get added to the ROM Manager manifest before it is available. But, the same files are also available at http://download.cyanogenmod.com when the buildbot successfully builds a nightly.
Q: Why can't I play .avi or .mkv files? They worked fine with Samsung's ROM.
A: Due to codec licensing issues, this can't be provided out of the box. Several apps from the marketplace should be able to replicate this feature (such as RockPlayer). We will also try to put these enhancements into CM7 ourselves.
Q: I encountered a bug, how do I find out if it's known and where can I report it?
A: Try to get the logcat output and last_kmsg to your report by:
Code:
desktop$ adb logcat > logcat.txt
desktop$ adb shell
# cat /proc/last_kmsg > /sdcard/last_kmsg (only if you had crash/reboot)
# dmesg > /sdcard/dmesg.txt
# exit
desktop$ adb pull /sdcard/last_kmsg .
desktop$ adb pull /sdcard/dmesg.txt .
Attach the logcat.txt and last_kmsg files to the bug report. Of course, you need to have the android SDK installed to do this.
And one more.
Running very smooth on the sgs2 keep up the great work.
AT&T SGS2 running CM7.
Codeworkx just put up a test build (http://codeworkx.de/download/galaxys2att/cm7-galaxys2att-KANG.zip) - it should work, but right now none of us has an AT&T SGS2, so need someone else to try it. Install it via ClockworkMod recovery as explained in the second post.
Let us know if it basically works.
Yea I've been running that for about an hour no issues.
AT&T SGS2 rooted!
Another Phone gets the best Android ROM ever!!! ;-)
jivy26 said:
Yea I've been running that for about an hour no issues.
AT&T SGS2 rooted!
Click to expand...
Click to collapse
Thanks - excellent! Change your signature to say "AT&T SGS2 CyanogenMod 7!"
Lol already did
Phone: AT&T SGS2
Running: CM7
getting signature verification failed. and yes, i am already rooted.
LOL seriously...already cm7 is here?? Can't wait to get home and throw this on here
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
Lol already did
Phone: AT&T SGS2
Running: CM7
Click to expand...
Click to collapse
Are you running the version of CM7 that codeworkx sent to you? No problems with installation?
atinm said:
Are you running the version of CM7 that codeworkx sent to you? No problems with installation?
Click to expand...
Click to collapse
Yea just had to install cm7 let it reboot it won't load passed galaxy s2. Pull battery goo into cwm install again gtg
Sent from my SGH-I777 using xda premium
seattleboi1982 said:
getting signature verification failed. and yes, i am already rooted.
Click to expand...
Click to collapse
Did you follow the instructions in the second post in the thread? As in, did you use the "Harder way" - flash ClockworkMod recovery etc?
I flashed before this thread was started so flashed using Odin and kernel codework released for cwm. Used super one click to root Then flash cm7 in cwm like I posted earlier
Sent from my SGH-I777 using xda premium
jivy26 said:
I flashed before this thread was started so flashed using Odin and kernel codework released for cwm. Then flash cm7 in cwm like I posted earlier
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok, great - the "harder way" (and only way at the moment!). Thanks!
Tried MIUI and CM7...
Obvious bugs are the back button not working.
But the major one is I can't hear anyone on a call and they can't hear me. Complete silence...both MIUI and CM7. Kernel issue? Known issue?
My order is in, should be seeing my Galaxy S II very soon, stoked!
I'll be testing just about everything pushed out once its here, I'll be reporting back as much as possible can't wait!
Drew489 said:
Tried MIUI and CM7...
Obvious bugs are the back button not working.
But the major one is I can't hear anyone on a call and they can't hear me. Complete silence...both MIUI and CM7. Kernel issue? Known issue?
Click to expand...
Click to collapse
I didn't even know there was a MIUI for AT&T Samsung Galaxy SII yet. As far as no sound - we haven't been able to test anything ourselves as we don't have a device to test on yet (maybe in a couple of days). The code itself hasn't changed much, but it is possible you're seeing something valid that we'll have to fix.
jivy26 said:
Running very smooth on the sgs2 keep up the great work.
AT&T SGS2 running CM7.
Click to expand...
Click to collapse
Did you test voice calls? Can you report back?
Have you seen this app? I find it amazing, it will automatically download differentiated files between your current CM build and the latest build.
It's free from Google Play (but you can donate to the devs from the app) and it is only for CyanogenMod roms.
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Description
Tired of download 200 MB everyday to get your latest CM nightly?
CyanDelta lets you update your CyanogenMod ROM by downloading just a small delta file (about 10 MB) instead of a big full zip file each time. With CyanDelta you can finally update your ROM in just some minutes even with a slow and expensive 2G or 3G connection!
CyanDelta is the perfect replacement of “CM Updater”, “ROM Manager” and “BBQLog”. When a ROM update is available it will notify you and show the changelog between the version you have installed and the new one. If you decide to update, it will delta-download the new version and if you want it will automatically install the new zips via recovery.
Main features:
✓ Security: all downloaded data is digitally signed by us to prevent manomissions.
✓ Recovery zip install: it can automatically reboot to recovery, install the ROM zip and other additional zips (kernel, modem...), wipe dalvik cache and reboot (requires root).
✓ Changelog: if you have a NIGHTLY build, when an update is available, CyanDelta will show you the list of changes between the ROM version you have installed and the new one.
✓ Update notification: when a ROM update is available, CyanDelta will notify you.
✓ High efficiency deltas: it uses the RFC3284 VCDIFF algorithm and some magic to produce really small deltas.
✓ Supports TWRP and CWM-based recovery, but NOT the closed-source ClockworkMod (the name is similar to CWM-based, but it’s a different thing!), since it's locked down by its author to only work with ROM Manager. If you have an unsupported recovery you can just manually install the zips generated by CyanDelta.
✓ Supports all official CyanogenMod ROMs and devices listed in http://get.cm
Click to expand...
Click to collapse
FAQs:
How much small are delta updates?
Typically they are about 10 MB, but it depends on how many changes has been made between the old and the new version. Sometimes it may be low as 5 MB, and sometimes a bit bigger, about 30 MB.
Before start downloading the delta update, you can always see the exact size of the data to be downloaded, so you can decide if download it or not.
What kinds of recovery does CyanDelta support?
CyanDelta supports TWRP recovery and CWM-based open-source recoveries (they are the open-source version of ClockworkMod recovery)
CyanDelta failed to install a zip in recovery on my device!
You probably have the official closed-source ClockworkMod recovery. It’s not supported by CyanDelta because his author has locked it to only work with his proprietary app “ROM Manager”, so we are unable to support it.
If you have that recovery you can replace them with the TWRP recovery (download from here: http://teamw.in/project/twrp2 ) or a CWM-based recovery. Otherwise you can just manually install the zip files generated by CyanDelta.
To use CyanDelta with nightly builds, I must update everyday?
No! It’s not necessary to always update to every new build. You can update only when you want, for example when you see something interesting in the changelog. Currently our server makes deltas between the 40 precedent builds, so for example if you use nightlies, you will always get delta updates unless you have a 40 days old version. If your version becomes too to get delta updates, you will need to download the new full zip from get.cm and import it in CyanDelta.
CyanDelta says “Zip not present in our database, ....”, why?
This may be caused by several reasons:
- if some hours or days ago CyanDelta has always worked fine, it’s almost certanly caused by the server that is rebuilding deltas, it’s the sign that a new update is coming. Just wait some minutes (in exceptional cases it may take some hours) and then reopen CyanDelta, it should show you the update.
- if you have just imported in CyanDelta a zip you just downloaded from get.cm, it might not have been imported yet in our database, wait some minutes or hours and then re-open CyanDelta.
- if you have just imported in CyanDelta a zip that you didn’t downloaded from get.cm, it’s almost certanly a unofficial CyanogenMod build that is not supported by CyanDelta.
- if you have a zip that you didn’t update since a lot of time (40 days for nigthly builds, many months for others), it might not be supported anymore by CyanDelta. This means that you must manually download from get.cm the new zip and import them in CyanDelta.
Can you give me step-by-step instructions to use CyanDelta?
- Install CyanDelta from Google Play.
- Download from CyanogenMod website the .zip file of the ROM you are using.
- Launch CyanDelta and select the .zip file you just downloaded from CM website. CyanDelta will import them and will create a new bigger zip in “Cyandelta” directory in the root of sdcard.
- When an update will be available, a notification will appear. Now you can launch CyanDelta and start the download by simply clicking a button!
- The new zip will be placed in “Cyandelta” dir in the root of sdcard. Now you can install it manually from recovery, or you can press “Install zip”. Cyandelta will automatically reboot to recovery, install the zip, wipe cache partition and reboot (this requires root permission).
On what devices and what ROMs does CyanDelta works?
CyanDelta works on all ARM devices running CM7, CM9 or CM10. Note that only official CyanogenMod ROMs available in http://get.cm are supported. For the moment CyanDelta doesn’t work on x86 devices because it uses a native ARM binary of xdelta3.
Does CyanDelta works with my recovery?
CyanDelta can automatically install new zips in CWM-based recoveries and TWRP recoveries. If you have an unsupported recovery, you can simply use CyanDelta to download the new updated zip and then install it manually in recovery, it’s in Cyandelta directory. Otherwise you can install the
The official ClockworkMod recovery it’s not supported because it’s closed-source and it’s locked down by his author to only work with ROM Manager (doesn’t support extendedcommand scripts). The CWM-based recoveries are identical to original ClockworkMod, but they are completely open-source and support extendedcommand scripts, so they work with CyanDelta.
Is CyanDelta secure?
CyanDelta has been designed from the beginning with security and safety in mind. If you are connected through a public untrusted network (a public wifi hotspot) it’s a lot more secure than download zips from CyanogenMod website.
When the CyanDelta app on your phone connect to our server to get updates, it downloads a JSON with update infos signed with our RSA 2048 bit key, that contains SHA1 hashes of the delta files downloaded by our server. In this way we have a HTTPS equivalent security, although we use HTTP for efficiency reasons.
When the app generate a new updated zip, it will always check if his hash match with the one written in the signed JSON, so data will not get corrupted.
What happens if something fails while installing zips in recovery using CyanDelta?
Theorically the recovery will simply not install the new zip, so it will not damage anything. However since is impossible to test that in all existing devices, there may be strange bugs in your device that might theorically corrupt your data and make your device unable to boot. Unfortunately we can’t prevent this, so you always use this feature at your own risk.
Before installing a zip with CyanDelta for the first time, we suggest you to do a nandroid backup manually.
What happens if the new ROM I have just installed doesn’t boot or it’s unusable?
We know that you want to always use the latest cutting-edge most experimental and unstable ROM! And we know that sometimes these updates can suddently leave you with an unusable device.
To prevent this, CyanDelta always keep one zip file of a previous version of the ROM you are installing. So if the new ROM doesn’t work, simply go to the recovery, reinstall the old zip et voilà!
Thanks to this, we think it’s reasonably safe to update your ROM even without making a nandroid backup every time before flashing.
Why the generated zips by CyanDelta have different size and MD5 than the official CyanogenMod zips?
Because zip files generated by CyanDelta are decompressed. Since data is stored uncompressed inside these zip files, they are bigger and obviously they have different MD5 too.
We have to do that because delta files generated between two uncompressed zips, are a lot smaller than between two compressed ones.
I don’t trust you! If the MD5 is different than the official CyanogenMod zips, who assures me that you haven’t tampered zips?
The content of our zip files and official ones are exactly the same. You can verify that by comparing the hash of every file inside the zip.
Zips produced by CyanDelta are identical (have the same MD5) for all our users, so everybody can verify if the files have been tampered, and in this case alert the whole community.
Does CyanDelta supports other ROMs apart from CyanogenMod?
Not for that moment, but we are planning to add support for other ROMs too, provided that they are completely free to redistribute by us. We will not accept anything that is based on non-free ROMs released by device manufacturers.
If you are a ROM developer that comply with these conditions and you are interested to make your ROM supported by CyanDelta, please contact us.
Click to expand...
Click to collapse
Looks like must have app for cm and should be integrated in cm.. My opinion
Sent from my XT910 using Tapatalk 2
ROM Manager by Koush uses another delta update solution, so there's little chance that CyanDelta will prevail.
I'd like security aspect to be more pronounced, so that you could be less paranoid about updates being tampered with.
It looks convenient to get system updated. But it's safe?
Sent from my XT910 using xda app-developers app
zhichao22 said:
It looks convenient to get system updated. But it's safe?
Sent from my XT910 using xda app-developers app
Click to expand...
Click to collapse
Why not?
Sent from my XT910 using xda premium
Jack'O said:
Why not?
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
testing :good:
Be interesting to hear some detailed feedback on this app. I like the idea of incremental updates instead of totally reinstalling each new rom update.
Sent from my GSM XT910 running AOKP V7 using Xda Premium
I have CM10.1 and installed CyanDelta, I found it easy to use, but for some reason its folder is created on the external sdcard and when it tries to automatically install the update, the recovery doesn't find the update because it searches in the internal sdcard. Now I just use it to download the update and then install it manually.
lukaop said:
I have CM10.1 and installed CyanDelta, I found it easy to use, but for some reason its folder is created on the external sdcard and when it tries to automatically install the update, the recovery doesn't find the update because it searches in the internal sdcard. Now I just use it to download the update and then install it manually.
Click to expand...
Click to collapse
same here, but i can access to the external sdcard so i dont have any problem, works perfectly :good:
What do you mean with that? Is there a way to fix this issue and make CyanDelta really automatic?
Just wait for the next nightly, the internal and external SD cars have been swapped just to tackle this particular issue.
Vatazhka said:
Just wait for the next nightly, the internal and external SD cars have been swapped just to tackle this particular issue.
Click to expand...
Click to collapse
Yup flashed 04-06 here and now the folder shows correct, when a new nightly is released I will try it.
Anyone use cyandelta? I have been trying to use it for the last 2 months but it always comes back with this error during the execution of xdelta. Anything I can do?
Tnks!
Testing.
Right now the app says there is not update available, I will wait a few days to see how it works.
Thank you for the app.
iZak17 said:
Testing.
Right now the app says there is not update available, I will wait a few days to see how it works.
Thank you for the app.
Click to expand...
Click to collapse
I was just trying it out, doesn't work for me since I can't tell it to look on my SDCard.
RedBullet said:
I was just trying it out, doesn't work for me since I can't tell it to look on my SDCard.
Click to expand...
Click to collapse
I'm not using this app any more because for some reason, after download and install the small file made by CyanDelta, I just got bootloops, no matter what, always bootloops.
I'm don't know, maybe is because I use BMM not SS.
Now I'm on CM 11 4.4.2, Not sure if this app can be used with this ROM.
I am using it with CM11 nightlys myself. XT912, SS 3.65. Works great.
Sent from my XT912 using XDA Premium 4 mobile app
:good: Luv the ability to add JBX kernel zip and WIFIAP zip, and have all flash smooth!! xt912 SS 3.65, CM11 12/29 JBX 12/09, Cyandelta as updater, successfully flashed 12/27, 12/29 updates with extra zips, worked perfect both times!! :highfive:
Installed last nightly through CyanDelta, and all the process went perfect. CM team has done a very good work.
Thanks!!
Enviado desde mi XT910 mediante Tapatalk
:laugh: Very sweet, 12/30 flash 7mb download, flawless update!! While download size not an issue, it does kinda "auto"mate the flash process, especially if you flash more then one zip regularly, like JBX or WIFIAP!! :highfive::good:
**Update about the future of this project. We will continue to update and support this port until the majority of users are running our new project.** http://forum.xda-developers.com/showthread.php?t=2432621 it is not ready yet at all. But I thought id post a heads up well in advanced so nobody freaks out.
This is a port from the 9505 Google Edition system dump that was posted. It was originally meant as a proof of concept build but no one picked up the project so I am supporting it.
@hlxanthus has been continually working on mods and feature updates within the ROM. I have a shared folder where we can both access current files for the project. Be sure to thank his posts :good:
Current Build: 9/11/13
Google Edition v6.0 Aroma Deodexed
Aroma package with lots of options built and pieced together by @hlxanthus.
--Link--
https://copy.com/BQlJ0
http://www.androidfilehost.com/?fid=23134718111254860
md5:
8755cbf42def51446ff1440ac2105637
Changelog:
Aroma scrolling fixed
All apps updated (I think at least... G+ updated right as I went to upload so I had to kill it and update and re-up)
Aroma permissions changed to hopefully fix all the random FC issues
Big update for xposed framework.
- in the installer it now lists all modules and their versions. I did not update all the modules because of this. Honestly I would only install the framework now and pick the modules separate. I still use theme engine, xblast, and gravity box personally.
I was working on new builds of systemui and framework-res but kept getting FCs so I reverted those changes. So carrier label is still screwy but you cab change it with the xblast module. :good:
Overall this update is minor besides the xposed framework. But the weird FC people were getting MAY BE fixed.
Please report any bugs. With bug reports please include a syslog log or adb log. It is also helpful to include the aroma log. To get this just before the last continue there is a save log button in aroma. Thanks.
Options:
A Lot
Wipe or dirty flash
One aroma for both pure and tweaked now
Browser selection
Gapps selection
Launcher selection
Clock options
Navbar options
Extra useful apps options
Phone_Info(a shortcut for the already built into android hidden menu *#*#4636#*#* this can do no wrong, it is just a link to a universally built in android feature)
Keyboard options
Battery options
Quick reply mms option
Viper4android option
TW camera option
Watchon app
TricksterMod app
Xposed framework and modules to be able to change quick settings, carrier label, colors and placement, and also fully theme using xtheme
Lots of kernels to choose from (I'm using my tweaked audism kernel)
Init should be installing properly with all performance options if so desired.
Instructions:
Download
Reboot to recovery(I prefer and HIGHLY recommend using only TWRP-2.5.0.2... will include flashables in next post)
Backup your current ROM(if you want)
Install and select your options
Reboot
If people want to donate it is appreciated but not expected. My pp Addy is in my profile or click here
Thanks to all who have already. My wife is slightly less irritated by my android obsession lol.
[ROM][G.E.][4.2.2][AROMA][VZW]GoogleEdition.v5.6 8/11/13
Me7 folks:
http://forum.xda-developers.com/showthread.php?t=2441441
[RECOVERY LOCKED/ME7] Safestrap Recovery v3.5x
http://forum.xda-developers.com/showthread.php?t=2428226
[RECOVERY LOCKED/ME7] Safestrap Recovery v3.5x [WIP DISCUSSION]
http://forum.xda-developers.com/showthread.php?t=2448726
Roms that work with safestrap
Like all Roms... Mine installs a kernel at the end... Since this project actively supports MDK... It installs an MDK kernel. Which is covered in the three threads I linked to above(which you should have already read). Hint: flash the provided kernel fix from the SafeStrap O.P.
AndroidSlave said:
Just a tip for ME7 Safestrap users:
Install this ROM in custom mode in aroma with only minimal apps installed, including Google apps etc.
I tried the install many different ways and kept getting issues, hard and soft reboots, etc.
After install with just nova, only Google play store, and just a few other minimal things, everything is amazing and smooth. Then just manually install everything you need.
For some reason safestrap and the me7 combo causes issues with something.
Just my two cents. Thanks a million to @Dubbsy - beautiful ROM - matter of fact, if I didn't have this ROM combined with gravitybox, I would have returned this device (I'm still within the 14 day grace period)...
Click to expand...
Click to collapse
Thanks to
ALL my generous donators. I do this as a hobby for fun. It's always greatly appreciated to get those emails. :good:
@buckmarble for kernel and rom/project discussion
@Treken for help and rom/project discussion. TeamTrek for ChaOS project
@hlxanthus for being a great partner on this project. We are easily twice as far along as I would have been alone.
@MrMuzik for the help on the banner
the 9505 people for being the first to get everything,
Rujelus22 for his AIO and the knowledge I've gained by digging through BluKuban for VZW
Actual Bugs:
**don't mess with the network settings. If you do, use the phone info app choose CDMA/lte auto prl.
**Carrier label is still screwy and shows up a jumbled mess for half the people.
Data Fix for those that went into network settings:
Going into the built in network settings automatically sets your preferred network to WCDMA. Meaning, no service. The only way to get it back without jumping through a bunch of stupid hoops is to use the built in hidden dialer code *#*#4636#*#*... Or just use the app icon called Phone Info(does the same thing)
To fix:
Go into mobile network settings.
Verify that your CDMA subscription is set to RUIM and not NV.
For good measure go into the rest of the options and set it to CDMA/LTE, automatic, and allow data roaming.
Back out to your home screen.
Then go into Phone Info app.
Scroll to bottom and tap radio off.
Open the drop down list and select CDMA/LTE auto (PRL).
Turn the radio back on.
Reboot.
Upon reboot open Phone Info again.
Verify it is set to CDMA/LTE auto (PRL)
** you should have full service now * *
** if not * *
In Phone_Info(*#*#4636#*#*):
Try CDMA auto (PRL)
Then try CDMA/GSM/LTE
If those still don't work then your nv_data needs reset. The only way to do that is in the hidden menu dialer codes in a touchwiz-stocktype rom :good:
If you destroy your nv_data and cannot get data back via the above you need to (stop screwing with your network settings)flash back to a TW ROM, enable hidden menu, and do a NV data reset via dialer code. After doing that make sure your phone is not in modem mode under diag dialer code. Until I update this section Google is your friend. And it is available information, verified. Your lack of searching skills doesn't mean pester my inbox...
"Bug" Fixes:
Reboot when hit volume up or down:
-Open gravitybox and deselect the 2 items that are checked under media tweaks
Carrier Name is a jumbled mess
-Install XBlast xposed module, enable it, open carrier section, edit it to what you want it to say.
WiFi doesn't turn on at all
-user error, check the download's md5 number
-user error, dirty install, do a full wipe prior and see if that was the issue
-kernel error, not likely if the above 2 have been done properly
GPS doesn't work
-user error, check the download's md5 number
-user error, dirty install, do a full wipe prior and see if that was the issue
-AOSP bug in general. TW writes something to a partition that stores your GPS location and area. AOSP roms don't edit it or write it. So you need to get a GPS lock in a touchwiz rom, then flash back to this. You can make a backup of your current AOSP/GE install, flash a TW rom, get a lock, and restore your backup. This has been a continued known issue with all ROMs that aren't fully TW.
Changes/Old versions:
-v1 was to see if I could get any data on the 9505
-v2 was fix reboot issues on v1. It is still the half odex half deodex
-v3 deodexed, s-voice, watchon, tw camera, tw wallpapers, build.prop tweaks, no native superuser preinstalled. https://copy.com/1Ce0m
-v4 was to update the google apps but didn't work out well so I reverted to the old apps and
-4.0.1 removed the tw apps. Added the lte on off app.
https://copy.com/A1Uk3 Deodexed
https://copy.com/xBVJe Odexed
-PureG.v1- deodexed, no tweaks, no native superuser, ktweaker removed, no tw apps
https://copy.com/otV2R
-4.5 deodexed. If prompted to fix su just ignore. The latest su is installed.
https://copy.com/GRQ34
My own build with all my gapps replaced with team blackouts and their updater
https://copy.com/mjLEm
PureG.v2
https://copy.com/8qUi4 & http://www.androidfilehost.com/?fid=13858085825318748450
4.6 deodexed
http://www.androidfilehost.com/?fid=13858085825318748477
GoogleEdition 4.6 Odex
http://www.androidfilehost.com/?fid=13858085825318748480
GoogleEdition 4.6 MyWayhttp://www.androidfilehost.com/?fid=13858085825318748482 & https://www.copy.com/Nc2uM
GoogleEdition 4.6.1 MyWayhttps://copy.com/qElJ9
GoogleEdition 4.6.1 Deodex - tweaked version https://copy.com/zGtWF
PureG.v3 - stock Google no tweaks https://copy.com/DgNvPvFAhcib
Test pure version with No CSC data https://copy.com/CDdtj
GE 4.7
https://copy.com/pKKuZ with KToonsez Kernel
https://copy.com/p6TxM with stock Kernel
GE 4.7.5
https://copy.com/Xv347
Pure.v4
https://copy.com/IATso
Updated all Google apps, fixed permissions, installed new supersu with new dependencies and permissions, signal bars are fixed
Google Edition 4.8.xx deodexed
https://copy.com/x2laA
changelog:
Updated all Google apps, fixed permissions, installed new supersu with new dependencies and permissions, a couple more minor framework changes, fixed signal bars from 4.7.5, included es file in data/app, and it is using the latest(7/24) KT kernel. No SODs that I have been able to see.
Google Edition PureG.v5 - Stock google, full deodex, no performance tweaks, and the only additions to the Google Experience I added was a reboot menu(stock was just power off), and SuperSU
https://copy.com/NMXKF
Md5: 9e845492078d938327176bd7f5bef3c9
5.4.1:
https://copy.com/7a24X
md5: 9eab755335ced6597642b02e5b25296c
Google Edition 4.9 CleanBuild deodexed
https://copy.com/yd3pj
Md5: cca28f4582838b14fa4cae26e72a629c
Google Edition Odex'd 4 me
https://copy.com/EUOGU
Md5: 0bacda0d4fa15bb8f4379a5f249eab3a
Google Edition 5.5
https://copy.com/s2fNI
md5: e914058bd08cc0f129154309c1098a5e
Google Edition 5.6
https://copy.com/CgLCU
md5: eefcfa2e85fe1c2d6d4f5ab6990ed15a
Google Edition v5.7 Aroma Deodexed
Aroma package with lots of options. Built and pieced together by @hlxanthus.
--Link--
https://copy.com/go7aI
--md5--
4b2d6578a621583eaf120549b400a9c5
Changelog:
Added 4 new kernels (agat, abyss, deviant, insecure stock ge, and my "badassery edition-audism kernel v2"), updated 2 others(KT, audism), updated all apps in installer (to cut back on stuff being installed to data using your precious space), added all xposed modules individually selectable with descriptions (you need to select xposed in system mods then it will open up the next sub menu), I added missing data files (potentially HELP with the random data issues), I didn't fix carrier label but I'm 80% sure I know where everything is now
Google Edition v5.8 Aroma Deodexed
https://copy.com/hfwtp ICS themed aroma
https://copy.com/aQDCs MIUI themed aroma
--md5--
54b1a889e5da6668da31eab9ae2967cd ics
dc9088367ba8047873a7b0a5135c4b63 miui
5.9:::
https://copy.com/wduZa
md5:
1f7189a0727d1a32a67457649ff1e485
Sprint proof of concept(for sprint not vzw):
**I would strongly suggest using and supporting the developer who is working actively on the Sprint version. If I find any specific fixes for things I will forward my info to him to continue helping others.** LINK HERE
https://copy.com/pIaix -my p.o.c. build before the one above was made available
[ROM][G.E.][4.2.2][AROMA][VZW]GoogleEdition.v5.6 8/11/13
Dubbsy's Extras, Tools, and Resources:(this will be updated as I make or gather more)
WARNING
Don't change a recovery from within goomanager or rommanager or romtoolbox or any app installed on the phone while on my GE rom.
Download a flashable recovery or manually Loki and push it from your computer.
Recoveries that are pre-loki'd and ready to be flashed in your current recovery are posted below.
I personally only trust and use TWRP 2.5.0.2(2.6 is buggy). I've seen too many "issues" with ROMs totally disappear when people stopped using cwm in favor of twrp. But cwm recoveries are included below regardless.
TWRP 2.5.0.2:
https://copy.com/0lTMs
Dubbsy's MiDarkness Theme for TWRP 2.5-2.6:
Preview: http://db.tt/2zc9uFt2
*Black and Orange TWRP theme based off of the black theme by z31s1g's black theme.
*To install the theme:
1. Rename the zip file to "ui.zip"
2. Make a folder in your TWRP folder called "theme"
3. Paste ui.zip into theme
4. Reboot to recovery
~ Download ~
*https://copy.com/HjJ7a
CWM-Touch-6.0.3.6:
https://copy.com/IgHQf
Phil Z Recovery 5.0.8.5:
https://copy.com/ODkRl
(*Hit the thanks button if you use these tools.*)
Mods included in the aroma package:
TW camera for Google Edition ROMs v1 7/12/13(included in aroma)
https://copy.com/VqkgF
*Note: not all functions work yet. Gallery icon is still linked the SecGallery. No more work will be done on the camera until both my other projects are in a stable condition. This was only done because at least one person posted or messaged me for it every day. I will ignore all requests for more camera work until the other 2 projects are "complete"
I'm going for it.
rustynutzz said:
I'm going for it.
Click to expand...
Click to collapse
yesss!!!! just added to roms list.
Can u add the TW Calendar widgets?
Getting ready to go into recovery and flash this bad boy. Wish me luck!
P.S. Probably shouldn't be flashing my phone on ambien lol
I can try later. Not sure though
sent from my Galaxy S4 using xda premium
rustynutzz said:
Getting ready to go into recovery and flash this bad boy. Wish me luck!
P.S. Probably shouldn't be flashing my phone on ambien lol
Click to expand...
Click to collapse
hahaha... probably not. reminds me of playing socom on ambien.... i was hiding in the bushes waiting for someone to come by.
Good times
theidoctor said:
hahaha... probably not. reminds me of playing socom on ambien.... i was hiding in the bushes waiting for someone to come by.
Good times
Click to expand...
Click to collapse
I remember halo on that ish, crazy times.
I'm in for a flash, already backed up. Anyone know if this requires a kernel flash or if this is V3 of Op's words? nvm I see V3
rustynutzz said:
Getting ready to go into recovery and flash this bad boy. Wish me luck!
P.S. Probably shouldn't be flashing my phone on ambien lol
Click to expand...
Click to collapse
How is it? Are the signal bars fixed?
Man this is awesome! Flashed v2 earlier just saw a v3 release. Thanks man! Does v3 have root?
marc314 said:
Man this is awesome! Flashed v2 earlier just saw a v3 release. Thanks man! Does v3 have root?
Click to expand...
Click to collapse
run root checker.
Installing now. Will report in a few
kpa2727 said:
I remember halo on that ish, crazy times.
I'm in for a flash, already backed up. Anyone know if this requires a kernel flash or if this is V3 of Op's words? nvm I see V3
Click to expand...
Click to collapse
thought a kernel was added to it but dont quote me on that. id flasha kernel just in case. dont want to be on ambien and go through that mess
theidoctor said:
thought a kernel was added to it but dont quote me on that. id flasha kernel just in case. dont want to be on ambien and go through that mess
Click to expand...
Click to collapse
downloads done, transfer time !
Up and running. Seems a little smoother then V2. LTE back on. Not going into mobile networks. Checking MMS right now.
Rnd0209 said:
Up and running. Seems a little smoother then V2. LTE back on. Not going into mobile networks. Checking MMS right now.
Click to expand...
Click to collapse
Nice if you can let me know how well it's working I'll download and flash tomorrow.
GPS not working. MMS seems like its working. LTE is back but did not go into mobile networks.
inseconds99 said:
Nice if you can let me know how well it's working I'll download and flash tomorrow.
Click to expand...
Click to collapse
lik 11 minutes tomorrow? just do iiiiiit
Ok, to clear the air, I am not the original Dev for this particular project. I had been working on a very similar project until I found this. It just needed for me to add support for our device. So I did just that. I made a prominent build and after extreme testing it is ready to be shared with you.
See Continuous Integration Builds at the end of this post for a link to download latest releases. All releases starting from November 5, 2015 and onward will support the Huawei Ascend Mate 2.
It can patch:
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in other ROMs
NOTE: If you want to dualboot a stock EMUI ROM, I highly recommend installing it as your primary ROM first. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created.
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and install.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Secondary: Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of Extsd slots. These install to the external sd partition and eat up space on the external storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny and your data partition is getting full. These slots are named "extsd-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from the custom recovery will literally backup every ROM you have installed so think about this before making a backup.
App and data sharing
DualBootPatcher got support for sharing apps (deprecated) and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply becomes unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
How do I...?
Switch the ROM if something doesn't work properly?
If you have TWRP, you can switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
I installed a new rom and want to switch to it?
Open app, select ROMs, then select the rom you want to switch to. When the switch is successful, reboot.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
WATCH THESE HOW-TO VIDEOS:
Credits to @superbass311 for making these videos.
It will demonstrate how to use this app effectively. If you read the instructions and still can't figure it out then this will be very helpful to you!
How to install Multi Boot Patcher:
How to flash another ROM with Multi Boot Patcher:
How to flash Xposed with Multi Boot Patcher:
How to share apps with Multi Boot Patcher:
Original Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Contributors
chenxiaolong, SHM
Version Information
Status: Testing
Continuous Integration Builds: https://snapshots.noobdev.io/
Created 2015-10-11
Last Updated 2015-11-07
It seems complicated. May try it later.
One question currently: What if I want to update a ROM? e.g. Huawei releases B323 or whatever to fix security issue(s). Or to do delta update for CM or PAC ROM? I know you seemed mentioning this already, but it is still sort of confusing, esp. with OTA update.
MT2-User said:
It seems complicated. May try it later.
One question currently: What if I want to update a ROM? e.g. Huawei releases B323 or whatever to fix security issue(s). Or to do delta update for CM or PAC ROM? I know you seemed mentioning this already, but it is still sort of confusing, esp. with OTA update.
Click to expand...
Click to collapse
When you download the ROM such as CM for example, open the app, then select to patch that ROM the same way you did before. Then just flash. It will flash the update to the proper ROM without affecting any other ROM.
{
"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"
}
As you can see I have three roms. CM is my primary ROM. Then I have PAC ROM and Carbon ROM installed on my external sd. Should I get an update for PAC ROM and download, I would open the app, then click on, Patch Zip File, change partition configuration to PAC ROM as seen in the picture, then choose the OTA ROM to patch. When the patch is done simply flash. Simple enough.
Edit: please try not to quote the entire first post. Can be a pain scrolling through if using an app.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
When you download the ROM such as CM for example, open the app, then select to patch that ROM the same way you did before. Then just flash. It will flash the update to the proper ROM without affecting any other ROM.
As you can see I have three roms. CM is my primary ROM. Then I have PAC ROM and Carbon ROM installed on my external sd. Should I get an update for PAC ROM and download, I would open the app, then click on, Patch Zip File, change partition configuration to PAC ROM as seen in the picture, then choose the OTA ROM to patch. When the patch is done simply flash. Simple enough.
Click to expand...
Click to collapse
So I have to manually flash the OTA update.zip or I could also let CyanDelta to that?
MT2-User said:
So I have to manually flash the OTA update.zip or I could also let CyanDelta to that?
Click to expand...
Click to collapse
If CyanDelta targets the patched ROM then yes, buy pointless to jump back to the cyandelta app. While using the Dual Boot Patcher app you can install from there. After the patch is made you go to, Roms, then click on the icon at the bottom right. It will have a phone with an arrow pointing down. In the same location press another icon with an add sign. Select the patch ROM. Then flash it through the app. Don't even need to go to TWRP at all unless its the primary ROM. This is explained in the OP already
Sent from my Ascend Mate 2 using Tapatalk
Thanks for your patience to explain.
BTW, I cleaned up the quoted images.
MT2-User said:
Thanks for your patience to explain.
BTW, I cleaned up the quoted images.
Click to expand...
Click to collapse
No worries, maybe @superbass311 will make a video for others to help them out. He likes making them videos lol.
Sent from my Ascend Mate 2 using Tapatalk
Oh sh+t! @SHM I did not see these post! He'll ya this will be my reading for tonight and I will try it all out then I'll make a video. Sweet!
Sent from my Ascend Mate 2 using Tapatalk
Interested in App Sharing.
From @chenxiaolong (http://forum.xda-developers.com/attachment.php?attachmentid=3318276&d=1431909206), space would be saved from keeping two/more APKs; however, if I have to install the same App in each ROM, how would that happen? Or actually the 2nd, and other subsequent ROM(s) just redirect the same App other than do real installation OR delete the same App after permission of the same shared App?
Does it matter in which ROM the shared App is enabled first, esp. regarding the App setting/data?
MT2-User said:
Does it matter in which ROM the shared App is enabled first, esp. regarding the App setting/data?
Click to expand...
Click to collapse
If the app is on your primary ROM but not on any other ROM, then you must enable that app to be shared on the primary ROM. Then switch to the other ROM and enable it in that ROM. Then you can use that app and its data from a shared location. If you wish to share all apps from the primary ROM with all other ROMs then boot up the primary ROM and enable, Share applications. Switch to any other ROM and all the apps from your primary should be available with all other ROMs you boot up. It doesn't matter which ROM you do this from. Its just a matter of which ROM has the app you wish to share in general. That specific ROM which holds that specific app that you wish to share is where you must go to enable it. Then jump to the other ROM and enable it again from there for single sharing.
I'm currently sharing all apps with all ROMs just to make it simple on my device. Its totally up to the end user what they do.
SHM said:
If the app is on your primary ROM but not on any other ROM, then you must enable that app to be shared on the primary ROM. Then switch to the other ROM and enable it in that ROM. Then you can use that app and its data from a shared location. If you wish to share all apps from the primary ROM with all other ROMs then boot up the primary ROM and enable, Share applications. Switch to any other ROM and all the apps from your primary should be available with all other ROMs you boot up. It doesn't matter which ROM you do this from. Its just a matter of which ROM has the app you wish to share in general. That specific ROM which holds that specific app that you wish to share is where you must go to enable it. Then jump to the other ROM and enable it again from there for single sharing.
Click to expand...
Click to collapse
+1. Global App Sharing is supported in primary ROM? Do I need patch every Gapps including the one for primary ROM? (There are 700 pages of the thread started by @chenxiaolong. I saw he mentioned the second Gapps needed to to patched. That's more than 2 years ago though.)
---------- Post added at 08:14 PM ---------- Previous post was at 08:12 PM ----------
SHM said:
I'm currently sharing all apps with all ROMs just to make it simple on my device. Its totally up to the end user what they do.
Click to expand...
Click to collapse
DId you install each App 3X? Or just backup/restore using TB?
MT2-User said:
+1. Global App Sharing is supported in primary ROM? Do I need patch every Gapps including the one for primary ROM? (There are 500 pages of the thread started by @chenxiaolong. I saw he mentioned the second Gapps needed to to patched. That's more than 2 years ago though.)
Click to expand...
Click to collapse
For your first question, yes, but the primary ROM needs to be patched first in order for it to work. My recommendation with that is to grab the latest ROM zip for your primary and patch that zip using the app. Then install the patched zip to your primary. It will add needed files and binaries to make things more effective. This also makes sure not to mess with other ROMs as well. As for your second question about gapps, if you wish to install the gapps to a ROM, let's say PAC rom, and PAC rom is installed on your external SD, then you must patch the gapps zip using the configuration for PAC. When the patch is done, simply flash. Doing this insures the gapps is properly installed to that specific ROM. Otherwise it will just install to your primary ROM by default and if your primary ROM already has gapps then this isn't what you want it to do lol. You must patch the gapps zip for each ROM configuration to insure that it installs to that specific ROM. It takes no time to do this. Its easy, and quick. Give it a try
MT2-User said:
DId you install each App 3X? Or just backup/restore using TB?
Click to expand...
Click to collapse
Neither. By enabling shared apps to share all my apps on my primary ROM with all other ROMs it simply gives my ROMs access to them. No need to do multiple installs. One install of that app is all that is required. If you take a look at the first post it explains how app/data sharing works using an analogy. I would recommend you read that closely for a better understanding on how this process works.
SHM said:
Neither. By enabling shared apps to share all my apps on my primary ROM with all other ROMs it simply gives my ROMs access to them. No need to do multiple installs. One install of that app is all that is required. If you take a look at the first post it explains how app/data sharing works using an analogy. I would recommend you read that closely for a better understanding on how this process works.
Click to expand...
Click to collapse
Actually I got confused from the quoted content in OP saying in each ROM to install the App first.
MT2-User said:
Actually I got confused from OP saying in each ROM to install the App first.
Click to expand...
Click to collapse
For single sharing it was saying to enable them in each ROM. Not install in each ROM. To install in each ROM would defeat the purpose of sharing. Here is an example, I have tapatalk installed on my primary ROM. On my second ROM it doesn't exist. I want to use tapatalk on my second ROM so what I do is I enable tapatalk to be shared from within the primary ROM. I then switch to the second ROM. While in the second ROM I enable for the app to be shared as well. This way the second ROM can use it. If I have a third ROM and want to use tapatalk on that third ROM then I simply switch to the third ROM and enable the sharing of the app. No need to go back to my primary since it was already enabled previously. However, if you want to make it simple you can enable for all apps to be available for all roms by a click of a button and be dome with it.
SHM said:
For single sharing it was saying to enable them in each ROM. Not install in each ROM. To install in each ROM would defeat the purpose of sharing. Here is an example, I have tapatalk installed on my primary ROM. On my second ROM it doesn't exist. I want to use tapatalk on my second ROM so what I do is I enable tapatalk to be shared from within the primary ROM. I then switch to the second ROM. While in the second ROM I enable for the app to be shared as well. This way the second ROM can use it. If I have a third ROM and want to use tapatalk on that third ROM then I simply switch to the third ROM and enable the sharing of the app. No need to go back to my primary since it was already enabled previously. However, if you want to make it simple you can enable for all apps to be available for all roms by a click of a button and be dome with it.
Click to expand...
Click to collapse
That's why I asked at the beginning coz I was confused. Understood since your previous reply. If stock ROM set as primary, guess will not enable global app sharing; or you could distinguish between system apps and user apps?
BTW, sorry I wanted to show my appreciation but I guess I reached the 8 thx per day limit.
MT2-User said:
That's why I asked at the beginning coz I was confused. Understood since your previous reply. If stock ROM set as primary, guess will not enable global app sharing; or you could distinguish system apps and user apps?
BTW, sorry I wanted to show my appreciation but I guess I reached the 8 thx per day limit.
Click to expand...
Click to collapse
System apps are not able to be shared betweem roms. Only user apps. This is done like this to prevent system crashes. If you want a specific system app you will have to handle that manually. How you choose to do so is entirely up to you, and no worries on the thanks. Give them when you can but I won't cry if you don't lol. Not really here for credits, but here to learn, grow, and when applicable, share my experiences with others.
To properly patch the stock ROM as primary you will need to make a flashable ROM so that ROM.zip can be patched. Unfortunately, to my knowledge, no one has made a flashable stock zip and shared it publicly. Only stock roms which are shared are either backups from other members or links to the official updates which are not proper flashable zips. Huawei uses an unnatural method by default, ie. UPDATE. APP and (VENDOR_UPDATE.APP)?.. However, one could easily make a backup of the stock ROM without any modifications and turn that system backup into a proper flashable ROM using tools such as archi kitchen or anything else which is similar to that. Then patch it using this app and install as primary.
How much space are you using running three ROMs?
SHM said:
System apps are not able to be shared betweem roms. Only user apps. This is done like this to prevent system crashes. If you want a specific system app you will have to handle that manually. How you choose to do so is entirely up to you, and no worries on the thanks. Give them when you can but I won't cry if you don't lol. Not really here for credits, but here to learn, grow, and when applicable, share my experiences with others.
To properly patch the stock ROM as primary you will need to make a flashable ROM so that ROM.zip can be patched. Unfortunately, to my knowledge, no one has made a flashable stock zip and shared it publicly. Only stock roms which are shared are either backups from other members or links to the official updates which are not proper flashable zips. Huawei uses an unnatural method by default, ie. UPDATE. APP and (VENDOR_UPDATE.APP)?.. However, one could easily make a backup of the stock ROM without any modifications and turn that system backup into a proper flashable ROM using tools such as archi kitchen or anything else which is similar to that. Then patch it using this app and install as primary.
Click to expand...
Click to collapse
:good::good::good: