[ROM][Lollipop][Z3C] Cyanogenmod 12 - Nightly - Xperia Z3 Compact General

Xperia Z3 Compact, CyanogenMod 12 - official nightly
Since 2015-01-21 CM12 nightly available.
Working:
- calls
- sms
- 2G, 3G, LTE DATA
- sound (2 speakers are ok)
- bluetooth
- camera + video recording are ok
- wi-fi
- GPS
- Compass
- NFC
- OTA update
Reported bugs:
- Audio calls work over loudspeaker, it's usable, but uncomfortable.
- Calling app somebody is a bit laggy - Try turning off "Phone number lookup" in dialer settings
- built in Audio Fx seems to be buggy on BT
- USB OTG
Solved bugs:
- auto brightness is buggy - SOLVED 2015-01-27
- the recovery is _EXTREMELY_ hard to read. It looks like a black screen but if you look closer the brightness is set to minimum or something. - SOLVED 2015-01-27
Download Links:
CyanogenMod 12:
Nightly: link
Changelog:
http://www.cmxlog.com/12/z3c/
Instalation:
- backup current ROM
- download and put cm12 ROM on external SD
- extract kernel from this cm12 zip (boot.img) and flash in fastboot / fastboot flash boot boot.img
- power up phone, go to recovery mode
- do a full wipe
- select Aplly Update -> chose from sdcard1 -> select cm12 nightly zip
- after finish reboot phone
Google Apps i got from here: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900 I pick "micro version of gapps"
Click to expand...
Click to collapse
Thanks to veimus for instalation help

crimpy1 said:
Since 2015-01-21 CM12 nightly available.
Download Links:
CyanogenMod 12:
Nightly: link
Click to expand...
Click to collapse
Great, is there a rls log? Or gerrit which shows wants not working?
Sent from my D5803 using XDA Free mobile app

shafiq01 said:
Great, is there a rls log? Or gerrit which shows wants not working?
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
Changelog:
http://www.cmxlog.com/12/z3c/

Should this thread be posted ?

Does cyanogenmod installer work with z3c

Is it possible to flash it through twrp?
I have kitkat rom now with 23.0.1.A.5.77
Does it require lollipop as base OS before I can flash this *.zip
Sent from my D5803 using XDA Free mobile app

No, you have to flash kernel first from CM12 zip to have a recovery that can handle Android 5
My Easy way is:
- backup current ROM
- download and put cm12 ROM on external SD
- extract kernel from this cm12 zip (boot.img) and flash in fastboot
- power up phone, go to recovery mode
- do a full wipe
- select Aplly Update -> chose from sdcard1 -> select cm12 nightly zip
- after finish reboot phone
Google Apps i got from here: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900 I pick "micro version of gapps"

shafiq01 said:
Is it possible to flash it through twrp?
I have kitkat rom now with 23.0.1.A.5.77
Does it require lollipop as base OS before I can flash this *.zip
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
You have TWRP? Where'd you get that?

I have androplus kernel v19c on top of rEctiFy ROM which has the DRM fix baked into the ROM. Awesomeness.
But androplus kernel supports multiROM. Whether it can take the app https://play.google.com/store/apps/details?id=com.tassadar.multirommgr i don't know. But if it could then it would perhaps be possible to have both my current ROM (Kitkat) and the CM12 ROM. In that manner I would have a daily driver and CM12 to boot between. But first I will try the instructions given with the kernel from CM12, I guess it's inside this nightly build?
Sent from my D5803 using XDA Free mobile app

@op, a bunch more info would be cool, what does work, what does not, known bugs and so on...
tapatalked from lollipopped i9300

flashing fails in cyanogen recovery, and i can't use the adb shell to un dim the recovery screen.
im pretty sure i had adb enabled in dev mode before i started.
is there a fix for that?

I saw this on xperiablog, already downloaded the latest build but didn't try and install it yet. It would be great if someone who tried it posted here what works and what doesn't.

I had it for day, and what works:
- calls
- sms
- 2G, 3G, LTE DATA
- sound (2 speakers are ok)
- bluetooth
- camera + video recording are ok
- wi-fi
- and almost all was fine for me..
And now problems:
- auto brightness is buggy
- high battery consumption when my phone was paired to bluetooth car speaker
- from power menu option Reboot = power off
- LED notification are working but you can`t force to different colours (i.e. if i want setup blue color for SMS its always ~amber), charging/battery LED are OK red/orange/green

Anyone able to confirm that the magnetic charger works?

veimus said:
I had it for day, and what works:
- calls
- sms
- 2G, 3G, LTE DATA
- sound (2 speakers are ok)
- bluetooth
- camera + video recording are ok
- wi-fi
- and almost all was fine for me..
And now problems:
- auto brightness is buggy
- high battery consumption when my phone was paired to bluetooth car speaker
- from power menu option Reboot = power off
- LED notification are working but you can`t force to different colours (i.e. if i want setup blue color for SMS its always ~amber), charging/battery LED are OK red/orange/green
Click to expand...
Click to collapse
wow, sounds nice, i would indeed like to have it as well
but i'm failing on flasing part through cyanogen recovery twice now
first i did the way as mentioned in the thread, then i tried the jerpelea thread method by adding the aries in the script
no success, maybe it could be that my external sd card is formated as exFat32, so i could get larger files than 4GB.
meaning cyanogen recovery can't read, perhaps?
now i i've restored my kitkat nandroid backup twice through twrp(nut) after fastbooting androplus kernel.

I've installed it as well now, so far everything seems to work. Auto brightness is indeed buggy.
To get it installed I had to do a few things:
- Extract boot.img from the cm12 zip and flash it with fastboot
- boot into recovery (power up) , the recovery is _EXTREMELY_ hard to read. It looks like a black screen but if you look closer the brightness is set to minimum or something. Turn off all lights (LOL) and flash cm12 followed by gapps.
- unlock developer options to enable root

shafiq01 said:
I have androplus kernel v19c on top of rEctiFy ROM which has the DRM fix baked into the ROM. Awesomeness.
But androplus kernel supports multiROM. Whether it can take the app https://play.google.com/store/apps/details?id=com.tassadar.multirommgr i don't know. But if it could then it would perhaps be possible to have both my current ROM (Kitkat) and the CM12 ROM. In that manner I would have a daily driver and CM12 to boot between. But first I will try the instructions given with the kernel from CM12, I guess it's inside this nightly build?
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
MultiROM support requires some work to make the z3c a compatible device - androplus kernel (v19c) has the required kexec-hardboot support for multirom, but multirom manager doesn't support the z3c and no multirom custom TWRP... I would have a go at porting Multirom, but I don't know coding with C very well.... If anybody can code in C, there is a porting guide by the dev here: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
---------- Post added at 10:39 AM ---------- Previous post was at 10:28 AM ----------
shafiq01 said:
wow, sounds nice, i would indeed like to have it as well
but i'm failing on flasing part through cyanogen recovery twice now
first i did the way as mentioned in the thread, then i tried the jerpelea thread method by adding the aries in the script
no success, maybe it could be that my external sd card is formated as exFat32, so i could get larger files than 4GB.
meaning cyanogen recovery can't read, perhaps?
now i i've restored my kitkat nandroid backup twice through twrp(nut) after fastbooting androplus kernel.
Click to expand...
Click to collapse
I had the same problem, tried three times (even shut myself in a really dark room to see if i could read the recovery logs!) - I started thinking the issues must be with accessing my external sd card (mount issues?), so I moved the cm rom zip to internal/sdcard0 and flashed again, it worked perfectly! Done the same thing with Gaaps, worked!
We really need TWRP (or CWM) as the cm recovery is a bit pants (no offence intended to CM), no nandroid backup/restore, mount tools etc).
I have spent about six hours playing with and "customising" the rom - I'll post my experiences/issues soon...

Translate
Thanks
A lot of big update on next nightly , I
I would like to know how translate CM12 ?
I find this for CM11 : https://crowdin.com/project/cyanogenmod
but nothing for CM12 and no files strings.xml here : https://github.com/CyanogenMod/android_device_sony_z3c
Thanks

mick711 said:
Thanks
A lot of big update on next nightly , I
I would like to know how translate CM12 ?
I find this for CM11 : https://crowdin.com/project/cyanogenmod
but nothing for CM12 and no files strings.xml here : https://github.com/CyanogenMod/android_device_sony_z3c
Thanks
Click to expand...
Click to collapse
Looking forward to all those changes. I'm tempted to try this as a daily driver for a few days, but the brightness is driving me a bit nuts having to set it manually. Don't see any fixes listed for it in the next nightly.

I installed and seens all fine. Couldn´t install using TWRP from AndroPlus Kernel. Needed to flash the CM boot.img and than try to read the recovery menu lo/
But all seens fine, so far
For next, nights, all i need is wipe cache/dal and apply update like now?

Related

[Telus T959D Fascinate] - Install MIUI, CM7 and More!!

Follow Steps at own Risk
MIUI or CM7 Installation:
1.) Depending on what you want to install, download either the I9000 Miui 1.11.11 Rom or the CM 7.1 Stable Rom.
2.) Download the Glitch-V13-DEV-TelusFascinate+ kernel. I chose the Medium Leakage Kernel.
3.) Move both ZIP (ROM and Kernel) files over to the Root of your Internal SD Card (USB, Bluetooth, etc)
4.) Make sure you DISABLE all Lagfixs if you have it enabled.
IMPORTANT:
Froyo 2.2.x (Not Tested):
We need to be able to boot into CWM. Easiest way to do this if you are on Froyo is to Flash the SpeedMod kernel or the Voodoo Kernel. I suggest following all steps which includes installing Darky 9.2 just to be sure. I haven't tried flashing Miui or CM7 from right from the SpeedMod CWM.
Gingerbread 2.3.x (Tested):
If you running a custom ROM that is based off Gingerbread you will be required to flash the Darky Resurrection Edition 9.2 (Froyo) via Odin. This is to insure that the proper boot loaders updated before installing MIUI or CM7. Download the Darky 9.2 package from the above URL, the ONLY files that we need from here are: Odin3 v1.3.exe, darky_odin.tar.md5 & s1_odin_20100512.pit​
Follow Ficeto's Instructions below to flash Darky 9.2 and remember to backup all your stuff before starting.
-------------------------------------
5.) Next step is to get your phone into Download Mode. If you are unsure please search the forums here.
6.) Now, open ODIN and connect the phone to the computer. ODIN will say 'Added'.
7.) Tick the 'Repartition' option, and then select the following files in ODIN (from the folder you extracted the base package in):
[*]PDA: darky_odin.tar.md5
[*]PIT: s1_odin_20100512.pit
8.) Press the Start button and wait for it to finish. Once it finishes, disconnect the phone from the computer after the phone reboots.
9.) After ODIN completes procedure and the phone reboots, a screen will come on the phone with 'Android system recovery <2e>' written at the top, and the following text will be written at the bottom:
"E:Invalid command argument
--Install from package--
Finding update package...
Opening update package...
Installing update...
#MANUAL MODE#
-- Appling Muti CSC...
Installing Muti CSC"
Don't worry about this.
10.) From here the next step is to reboot your phone, your POWER / SELECT button will not work so you will have to pull the battery out. Once you put the battery back in and start up the phone, it should automatically boot into CWM Recovery.
-------------------------------------
11.) Next we want to do a COMPLETE WIPE (Factory), also deleting Partition Cache and the Delvik Cache.
12.) Once the phone has been cleansed, you want to make your way to the option "Select ZIP from SD Card" and select the ROM zip file located on the SD Card. Start the Installation.
NOTE: Once you start the installation, your phone will reboot part way through, then will continue the rest of the installation. The total time for this installation could take up to 10 minutes, so please be patient and do not touch the phone!
13.) DONE!! You have now successfully Flashed either Miui or CM7 on your Fascinate!.
14.) Actually, one more Step which I have ONLY tested with Miui 1.11.11:
Once you have checked a few things out, we are going to want to Flash the Glitch-V13-DEV-TelusFascinate+ kernel. So boot back into CWM Recovery and Flash it the same way you flashed the ROM.
Optional:
BASEBAND UPDATE:
I would also suggest Flashing the I9000UGJK3 Baseband or another of your liking because I had crappy cell signal with the Stock Miui Baseband. Just download it as you normally would, move the ZIP to the internal SD Card, boot into CMW recovery and flash it. Click on the Link Here and find the modem that you would like to flash.
4WAYREBOOT MOD:
I think this Mod is a MUST for anyone running Miui, it completes it!! It basically adds the additional reboot options like Recovery, Hotboot, etc. to the 'reboot' list when going to reboot the phone. Install the ZIP the same way as usual, through CWM recovery. Download the 4-Way Reboot Mod Here.
ENJOY!!!!
I will add to this post with some additional and helpful information.
Other helpful information:
- With Miui or CM7, you will want to install the ROM Manager Application. It contains a bunch of additional downloads and is a must when using Miui or CM7.
- Please do NOT USE 'ROM manager' Backup option to create a nandroid. To create a backup, boot into CWM recovery normally via ROM manager or if you have the 4-Way Reboot mod installed. Just don't use the 'Backup option' in ROM Manager
- I haven't tried Launcher Pro yet, I've actually stuck with the Stock Launcher that Miui comes with, Launcher2.apk
thanks so much! save me tinkering time
Thanks! On my to do!
EDIT - thinking about this on the way into work. Should we include a step (if the complete wipe doesn't do it) to wipe the battery stats? Could be done in CWM after flashing the ROM, or through an app like battery calibration on boot up. Also, we should note on the coming from froyo that you only need speed kernel if you do not have an option to get CWM. When I ran froyo I had a voodoo kernel so could get to CWM that way.
Also, is miui EXT4 out of the box (no need for a lagfix)? Given its next to latest GB I'm assuming it is
Just some thoughts - hoping to do this tonight, but one quick question for the group - flashing - so do you all make sure you have a full battery before you flash? I've not always done that in the past, but believe its a best practice.
NEW EDIT - almost forgot, great work as always Adam!
jpmccarthy said:
Thanks! On my to do!
EDIT - thinking about this on the way into work. Should we include a step (if the complete wipe doesn't do it) to wipe the battery stats? Could be done in CWM after flashing the ROM, or through an app like battery calibration on boot up. Also, we should note on the coming from froyo that you only need speed kernel if you do not have an option to get CWM. When I ran froyo I had a voodoo kernel so could get to CWM that way.
Click to expand...
Click to collapse
Thanks Jeff, the Voodoo kernel should also work as well. In regards to wiping the battery, I never did but it might be a good idea just in case. I haven't run into any issues as of yet. (knock on wood)
jpmccarthy said:
Also, is miui EXT4 out of the box (no need for a lagfix)? Given its next to latest GB I'm assuming it is
Click to expand...
Click to collapse
Not 100% sure on this at the moment, but I do know that there is no need for Lagfix with Miui or CM7.
jpmccarthy said:
Just some thoughts - hoping to do this tonight, but one quick question for the group - flashing - so do you all make sure you have a full battery before you flash? I've not always done that in the past, but believe its a best practice.
Click to expand...
Click to collapse
It definitely is good practice to Flash a new ROM when the battery is almost 100% full. Now saying that, I have flashed ROMS when my battery has been as low as 40% - 45% and never had any issues.
I think that's the best comment Adam - why apply a lagfix if one is not needed!
Cannot wait to give this a run - hoping tonight assuming my little ones all go to bed, and my wife does not get too annoyed with me
[MIUI Themes and Lock Screens]
The Miui Rom is very customizable when it comes to themes and lock screens.
The Miui 'Themes' application allows you to download, install, customize and apply all different types of themes. Which I would have to say that there are at least a good 100 + or more themes out there at the moment.
I think the best feature that the 'Themes' app has to offer is that you have the option to apply different theme components to the current base theme that you have it set to!
As an example, I currently have one of the 'Honeycomb' themes applied as my base theme, my Lockscreen is based off the 'Slide Slip' theme, my Icon Set is based off the 'Seemless Dark Blue' theme and my Dialer is also based off the 'Seemless Dark Blue' theme. It feels like the possibilities are endless now when it comes to customization.
To see the different components the way the themes are broken down, choose 'Edit Theme' from within the 'Themes' app. Within here you can then assign other theme components as long as you with have the full theme installed or just that one component.
Installation of .mtz files, (Full Themes / Theme components)
Once you have downloaded a compatible Miui theme (.mtz format), copy that file to the following directory on your phone:
/sdcard/MIUI/theme
(You can also import themes from the themes application itself, all that does it move it to that directory for you)
Then open up the 'Themes' app and your new theme will be in the list.
NOTE:
If its a theme component only (Still .mtz format) , eg. Lock Screen component, it WILL NOT show up in your main Theme list. Just click on 'Edit Theme' and it should show up under the drop down for 'Lockscreen Style'. Get what i mean?
For Miui Lockscreens, check out the link below!
http://forum.xda-developers.com/showthread.php?t=1288096
For full Miui themes, check out the link below:
http://forum.xda-developers.com/showthread.php?t=1249352
Also, the Theme app has an Online library that you can search through as well
Cheers!
<drool> awesomeness <\drool>
EDIT flashing in process - factory reset at the moment
Awesome! Thanks for creating this. Just gotta wait until the weekend to take the plunge. It's not the flashing taking too long that I worry about, but the time I spend restoring apps and settings and just playing around in general. Not to mention having time to start over if I feel something went wrong. Two more days to go!
guessing it shouldn't boot loop - I'm stuck in a boot loop
looks like it cannot find the SD card - so keep restarting looking for the miui zip - the CWM error is quick before it restarts (can't see it)
EDIT : re-downloaded the zip but same effect. Anyone hit this before with cm7 or miui? trying a few things before I attempt a restore.
I get to 'checking bml' before it reboots, and then it boot loops continuously - I tried flashing and not flashing the glitch kernel first, but nothing sticks.
EDIT : giving up, attempting a restore of my nandroid I made before I started. Any tips let me know - disappointed.
EDIT : still up, backup didn't go so well - likely cause I have odd kernels - one last ditch - went right back to froyo stock, tried speedmod (bootloop), now put on 9.2, rebooting - may give it one more shot before giving up for the night.
EDIT - SON OF A ***** - that did it!!!!!!!!!!!!!!! I might have to provide some troubleshooting tips on that one!!!!!!!!
EDIT AGAIN - knock on wood here - I'm farther than the bootloop and I'm at a MIUI splash screen - that might be as far as I go tonight ... LOL
FINAL EDIT - so not much playing tonight. Ate into that with all this trouble shooting.
SO IF YOU ARE COMING FROM A GB ROM AND GET STUCK IN A BOOTLOOP - I would go to STOCK FROYO and then flash 9.2 and then follow the instructions. Bang on job Adam! I think I just had something odd on my phone.
I'm now up - gltich on + miui.
Wow, sorry you had such a hard time man. Only time I hit a hard bootloop was when trying to install CM7 using gingerbread bootloaders. Did you eventually get it going??
Sent from my Telus T959D
iwebsource said:
Wow, sorry you had such a hard time man. Only time I hit a hard bootloop was when trying to install CM7 using gingerbread bootloaders. Did you eventually get it going??
Sent from my Telus T959D
Click to expand...
Click to collapse
yeah, see my last edits - putting on 9.2 I'm guessing didn't completely adjust the bootloaders - when I put on stock telus 2.1, THEN 9.2 - I was golden.
Didn't play much (that was after 12) but restored a few apps - but man, it is really fast. Will report some thoughts over the weekend likely.
Questions on MIUI
OK a few questions.
- downloaded google maps (navigation, etc). Start it up, but it fails miserably - bombs out and goes into a constant vibration. ANyone having similar issues with that? Suggestions?
- There's a 6 digit number in the left corner of my screen - no meaning to me - anyone know what that is or seeing something similar?
- also, pinch and zoom with the camera. Those don't seem to work - any issues you folks having with that?
- Adam you suggest a different base band - where are you getting zip - I'm only finding large tars on that link (but I"m over tired)
- The OTA updater looks great BUT is in chinese - any one have a work around for that?
Again, sorry about all the issues you had with installing and such. My very first time
jpmccarthy said:
OK a few questions.
- downloaded google maps (navigation, etc). Start it up, but it fails miserably - bombs out and goes into a constant vibration. ANyone having similar issues with that? Suggestions?
Click to expand...
Click to collapse
Weird man, I actually installed google maps a few days ago. First time I used it (Navigation) was yesterday to test out the GPS. Had no problems at all with the apps yet.
jpmccarthy said:
- There's a 6 digit number in the left corner of my screen - no meaning to me - anyone know what that is or seeing something similar?
Click to expand...
Click to collapse
That is your Service Provider. With CM7 and Miui, I noticed it doesn't resolve the provider. Its no harm unless you don't like looking at numbers there. I did find a work around though, just install the Miui Extended Menu Mod and you can change it to what ever you want:
http://forums.miuiandroid.com/showthread.php?7738-MOD-Extended-Settings-Menu-Options
jpmccarthy said:
- also, pinch and zoom with the camera. Those don't seem to work - any issues you folks having with that?
Click to expand...
Click to collapse
Pinch and Zoom? Unsure what you mean, is that just the touch-point focus? If not I haven't tested that yet.
jpmccarthy said:
- Adam you suggest a different base band - where are you getting zip - I'm only finding large tars on that link (but I"m over tired)
Click to expand...
Click to collapse
Guess I better check my links more better. Stupid site.
For now use this one. I know your in the same geo area as me, I haven't had any issues with this one, use the one attached.
Oh, don't use the OTA updater, just use ROM Manager. Or download the Miui updater app from the market.
I'm guessing MIUI originally was developed in China, lol
iwebsource said:
Oh, don't use the OTA updater, just use ROM Manager. Or download the Miui updater app from the market.
I'm guessing MIUI originally was developed in China, lol
Click to expand...
Click to collapse
OK - maybe I should reflash. I actually have ROM Mgr premium - but its telling me I need CWM installed to work (which I obviously have).
And no apologies needed - we're all guinea pigs here
EDIT - Also, on the camera - used to be able to pinch like a website on Darky's to zoom in and out. Maybe that was a custom camera but I think it was generally samsung stock.
EDIT - Reflashed (1.11.18 actually - am I the first ) and GPS issue solved - might have been tied to the modem as I flashed yours Adam (THANK YOU!!!!!!) Keeping moving forward
jpmccarthy said:
OK - maybe I should reflash. I actually have ROM Mgr premium - but its telling me I need CWM installed to work (which I obviously have).
And no apologies needed - we're all guinea pigs here
EDIT - Also, on the camera - used to be able to pinch like a website on Darky's to zoom in and out. Maybe that was a custom camera but I think it was generally samsung stock.
Click to expand...
Click to collapse
Might be the best thing to do. I've read that some people prefer to >> Flash the ROM first >> Flash Kernel >> Boot into Kernel CWM >> Re-Flash ROM again.
Yeah, if you do there is no need for the Darky steps anymore.
Just boot into CWM, do factory wipe, partition and dalvik cache, fix permissions, then flash miui again.
Oh, in regards to ROM Manager and CWM, just select 'Flash ClockWorkMod Recovery' >> Select I9000 (MTA) and choose version 3.
Then reboot into recovery to test.
It actually still uses the Glitch CWM from the Kernel. This is just so that ROM Manager will recognize that you have a selected CWM
Looks like Miui 1.11.18 is now out. I'm going to Flash and test it out shortly.
iwebsource said:
Looks like Miui 1.11.18 is now out. I'm going to Flash and test it out shortly.
Click to expand...
Click to collapse
Already on it - best you for the FIRST time!
jpmccarthy said:
Already on it - best you for the FIRST time!
Click to expand...
Click to collapse
I'm loving Miui and the glitch kernel man. There are a few other Kernels out there that we can try as well. I maybe testing the platypus kernel out soon, it is also built for our phone too
From what I've read so far though, Glitch is one of the best so far.
iwebsource said:
I'm loving Miui and the glitch kernel man. There are a few other Kernels out there that we can try as well. I maybe testing the platypus kernel out soon, it is also built for our phone too
From what I've read so far though, Glitch is one of the best so far.
Click to expand...
Click to collapse
when you get 1.11.18, go to ROM manager and select update ROM - does nothing happen? I have it registered now with a CWM which is fine, it shows my current version (which is latest) so when I click check for udpates nothing happens (no - 'no update available' or anything like that). Just wanted to see if it was working correctly.

[ROM] [CM7] AceOSP

AceOSP is the only FULLY-WORKING AOSP ROM based upon CM7. It's the pure Google experience. Nothing added. Nothing taken away. And it's free to download!
Wait a minute. If this is based upon CM7, then how can it be AOSP?
Allow me to explain. All CyanogenMod tweaks are removed. If you can find any UI remains of CyanogenMod, I will pay you. [not literally, just tell me via PM and I'll fix the issue]
Why base it on CM7 when you could compile from AOSP?
In AOSP ROMs, there are recurring issues, such as the brightness/sounds issues and some hardware issues. CM7 works fully, so I based it upon that and removed CM7 traces.
Now, there IS an issue. This ROM is based on CyanogenMod. The notification power widget was enabled by default. So what I did was turn all tweaks off before I removed CMParts.apk. The data that controls if that appears or not is in the userdata. And I can't figure out how to make an update.zip restore to some userdata. So I've packaged the ROM into a ClockworkMod Nandroid backup. So for now, you'll have to restore to a Nandroid backup.
(Download the zip, extract it, and then find the nandroid_AceOSP folder that is made - copy that to /sdcard/clockworkmod/backup, reboot into recovery, choose backup and restore -> restore, and then find nandroid_AceOSP, select it, when done, reboot)
Bugs
- Factory resetting in any means will restore the Notification power widget and CyanogenMod's 'Ring' lockscreen. To do a factory reset, restore from the backup again.
- Changing volume, brightness or accessing battery use causes settings to FC. Changing the former two using other methods, like volume buttons and power control seems to work fine.
Download Link
Click here to download AceOSP 1.0
Update AceOSP
You must update to the version NEXT to yours.
For example, if you are running 1.0, and you want to go to 1.0.2, you must install 1.0.1 first
1.0 -> 1.0.1
1.0.1 changes the bootanimation from CM7's to Android's default. Get it here!
I can help you to create a CWM package
Sent from my GT-S5830 using Tapatalk
Thanks - do you know how to flash a full userdata.img via CWM as well?
Lets discuss this through PMs
Sent from my GT-S5830 using Tapatalk
epic118 said:
Thanks - do you know how to flash a full userdata.img via CWM as well?
Click to expand...
Click to collapse
instal rom on phone
use android commander on pc
copy system
then copy boot img find a good meta inf and it wil work
Sent from my GT-S5830 using xda premium
It is not aosp.
I'm sure it is - CyanogenMod is AOSP with tweaks. This ROM is based upon S5830's CyanogenMod, but with the tweaks removed. Thus doesn't that make this AOSP?
Userdata.img = same as data.img , can be used with dsixda's Android Kitchen .
The people who don't compile.....I feel so.....alone and isolated .
Herpderp Adreno + Tegra.
Then it'll be a non functioning cyanogenmod, not aosp rom.
Unlock delay still there. Battery percentage still jumpy. A really clean aosp will not be like that, in fact it'll be similar in function to all cyanogenmod roms.
consegregate said:
Then it'll be a non functioning cyanogenmod, not aosp rom.
Unlock delay still there. Battery percentage still jumpy. A really clean aosp will not be like that, in fact it'll be similar in function to all cyanogenmod roms.
Click to expand...
Click to collapse
Well , the thing is that I even have the unlock delay in my R , Backflip and Defy.....so it's definitely something else .
Herpderp Defy.
EmoBoiix3 said:
Well , the thing is that I even have the unlock delay in my R , Backflip and Defy.....so it's definitely something else .
Herpderp Defy.
Click to expand...
Click to collapse
You don't have it on the nexus phones

[ROM] [WIP] [DEV] Ubuntu Touch 13.10

Warning:
This is very alpha version of Ubuntu Touch. IT'S NOT READY FOR DAILY DRIVER. This is mainly for those curious souls like me that simply can't wait to try it on the find 5. There are and will be bugs. When that is said, lets get started.
Requirements before doing anything:
You will need to read the full guide before starting to do it. Just so you know what to do.
Downloads:
1. ubuntu image
2. saucy-preinstalled-touch-armhf.zip
3. extra zip
How to flash:
1. Reboot to recovery, i tested with twrp but any should do.
2. Make a full backup so you can restore after playing with ubuntu touch
3. Wipe System, Data, Dalvik-cache and Cache
4. Flash Ubuntu image....
5. Flash saucy-preinstalled.zip
6. Flash extra zip.
7. Reboot to System.
-------------------------------------
A few notes:
If you starts camera, you can shoot images but sometimes images files are corrupted, but back and front camera are working, also does flash.
If you enter video recording and starts that, camera app will freeze, you can then just exit it by swyping to the side and then long press camera under Recent apps and hit the X.
then camera can be tested again.
if you want to test music player, it can be done this way :
Code:
adb push testsong.mp3 /home/phablet/Music
adb chown phablet:phablet /home/phablet/Music/testsong.mp3
adb chmod 777 /home/phablet/Music/testsong.mp3
Then if you enter music player it should show a song that can be played. It failed for me the first time so I needed to reboot to recovery, with adb reboot recovery , then did "how to flash" again and after that when trying to boot it failed, and i needed to go back to recovery and do it all over with "how to flash but no wipe". When phone booted i started up the music app and can now play the song with or without wired headset
If you dont start music player before you push the song to the phone and all that, its possible that it can see the song without all the reflashing thing.
The reason for the reflash thing is that if you just reboots ubuntu, it will fail to bootup.
starting apps and switching between those is also working, sometimes phone gets a bit slow and not all apps is working, like soduku will not startup, but alot others is workiing fine.
Working:
Speaker
Camera
Sim card signal with 3g | sim card pin code needs to be disabled on phone before flashing ubuntu.
WiFi
Sms
Bootup.
A few important notes:
1. You cant reboot ubuntu in curret state, it will end up in bootloop.
2. To reboot to recovery use :
Code:
adb reboot recovery
This is a wip (work in progress) and need alot of work and i will do whatever i can to get it good.
Some images can be found here and a review here
Im hoping we can work together on this one so we can get it usefully as a dayli driver. So if you want to help, just pm me.
Sources:
Device tree
Vendors
Kernel
XDA:DevDB Information
[ROM] [WIP] [DEV] Ubuntu Touch 13.10, a ROM for the Oppo Find 5
Contributors
anders3408
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2013-09-19
Last Updated 2013-09-20
Reserved
Cool. Alpha indeed but awesome work nonetheless. Can't wait to see this progress. With roughly the same internals as mako and n4 hopefully the port goes smoothly. Cheers!
Sent from my Find 5 using Tapatalk 4
killerskincanoe said:
Cool. Alpha indeed but awesome work nonetheless. Can't wait to see this progress. With roughly the same internals as mako and n4 hopefully the port goes smoothly. Cheers!
Sent from my Find 5 using Tapatalk 4
Click to expand...
Click to collapse
Just as you think a device is about to "die" and be replaced by a newer version, a developer comes up with this stunning ROM to breath fresh life into it.
I don't want to get rid of my device now!
robifis said:
Just as you think a device is about to "die" and be replaced by a newer version, a developer comes up with this stunning ROM to breath fresh life into it.
I don't want to get rid of my device now!
Click to expand...
Click to collapse
I don't really see the Oppo find5 on it's way to the pasture just yet.
killerskincanoe said:
I don't really see the Oppo find5 on it's way to the pasture just yet.
Click to expand...
Click to collapse
Me neither. I'm sure this device will be running great for a long time.
Sent from my Find 5 using XDA Premium HD app
Thanks for this! Going to try this in the weekend
Sent from my Find 5 using xda app-developers app

CyanogenMod experimental official for honami!

I've noticed that on official CyanogenMod download page there are two experimental builds for honami!
Let the party begin!
http://download.cyanogenmod.org/?device=honami
orzech.miron said:
I've noticed that on official CyanogenMod download page there are two experimental builds for honami!
Let the party begin!
http://download.cyanogenmod.org/?device=honami
Click to expand...
Click to collapse
Would you give us some feedback how this rom perfoms?
Cpt.Schaaf said:
Would you give us some feedback how this rom perfoms?
Click to expand...
Click to collapse
I don't have my bootloader unlocked so I can't flash it :/ But I think that there will be a lot of people who will check this out
Look at the thread in the dev section dude
Kali- said:
know issue are:
* camcorder (fixed but not released)
* data (data must be disabled to make call)
* gps
Click to expand...
Click to collapse
orzech.miron said:
I don't have my bootloader unlocked so I can't flash it :/ But I think that there will be a lot of people who will check this out
Click to expand...
Click to collapse
I am new here but I thought we could flash CWM even with a locked bootloader and thus install any ROMs :-S
Sent from my C6903 using XDA Premium 4 mobile app
eightace said:
I am new here but I thought we could flash CWM even with a locked bootloader and thus install any ROMs :-S
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Bootloader has to be unlocked to flash a new kernel. And the recovery doesn't have permissions to overwrite the kernel so you have to boot into flash mode (or fastboot???) which requires an unlocked bootloader.
I am tempted to flash this though but I'm not exactly ready to unlock my bootloader yet
Woo! Now all we need is a non-convoluted way to root 4.3 and we're set.
kantk20111 said:
Woo! Now all we need is a non-convoluted way to root 4.3 and we're set.
Click to expand...
Click to collapse
Convoluted?
Just unlock bootloader -> flash any kernel with recovery -> flash CM
RyokoN said:
Convoluted?
Just unlock bootloader -> flash any kernel with recovery -> flash CM
Click to expand...
Click to collapse
Maybe he means backup TA direct from 4.3?
TheCraig said:
Bootloader has to be unlocked to flash a new kernel. And the recovery doesn't have permissions to overwrite the kernel so you have to boot into flash mode (or fastboot???) which requires an unlocked bootloader.
I am tempted to flash this though but I'm not exactly ready to unlock my bootloader yet
Click to expand...
Click to collapse
Oh it can overwrite the kernel alright, but a locked bootloader will only boot kernels signed with Sonys private key, which we can't get.
Rom is very fast
Camera work lag 3 sec on start
Bt work
RyokoN said:
Convoluted?
Just unlock bootloader -> flash any kernel with recovery -> flash CM
Click to expand...
Click to collapse
Hmm is there an easy way to root 4.3 yet? I mightve missed it.
kantk20111 said:
Hmm is there an easy way to root 4.3 yet? I mightve missed it.
Click to expand...
Click to collapse
No.
My first Test
Tested just a few minutes now ...
Hardware: C6903 with unlocked BL
wiped everything, flashed Cm11 Experimental and it flashed the full system AND a new kernel "3.4.0cyanogenmod-g8402fcb"
flashed no gapps for now, as this is just a quick test ...
First boot without problems, camera works (little bit unstable but works), wifi works, modem works (tmobile de at full signal)
UI themes to be very fast and stable
RAM-Usage / -free : 754MB / 0,92GB
Internal Storage usage / free : 192MB / 12GB
NFC is on but doesnt seem to work, but not enough tested -> need to have a look on it
Mobile Data (3G AND E) is keeping the modem to reset (signal -> 0 (think it's turned off) and then starts up again with full signal, as 3G or E is displayed it turns off again) if i turn wifi on and no mobile data is active, the signal stays constant (taken a call allready, works fine)
So far ... if mobile data is working, this may be a nice build for "nearly daily test usage" ...
Hello, I just unlocked my Z1 3 days ago and Im testing the new experimental ROM.
I would like to support you by letting you know the problems I realized this ROM has:
1.- data traffic doesnt work and also, if activated, makes you cannot send or receive any calls or sms because it makes the network fail. (I think this is the most important bug).
2.- Locator or GPS doesnt work at all.
3.- Camera works but it takes over 3-4 seconds to start working. Also the video cam make it crashes. Video cam doesnt work at all.
4.- Torch doesnt work nor the app neither when making pictures.
5.- I cannot volume down the music when headphones are connected.
6.- The buzz or sound when you push any icon, app, main manu button, etc, crashed once to me and it sounds so horrible, I had to shut the system down and boot it again to sort it out.
7.- There is no option to make our network works as 2G; there is only option to run as 3G.
8.- I got some problems while trying to restore all my contact I had by copying them from the SIM card and from the SD card; I finally achieved it going to the file explorer and running manually the file which contents the backup of my contacts.
9.- There's no options menu into the screen where are shown all the app's in order to sort them as most used, alphabetically, etc.
NEW ADDED: 10.- It doesnt unmount the SD card or seems like it doesnt.
NEW ADDED (2): 11.- There is no option to save the pictures and videos made with the camera directly in the SD Card. Also no option to move the pictures and videos in the internal storage to the SD Card.
I think the 5 first points are the most important, but the most one is the first one. That's my opinion about preferences.
Anyway, thanks for this new great job.
Im just waiting for an update impaciently.
Regards.
Hey,
I unlocked my boot loader recently and have begun testing the experimental roms. After the previous post I waited until the latest one was released to test it out. I can confirm that the data problems have been resolved and have been using this rom for the past few days.
The main problems I have encountered are:
- Videos within apps such as Facebook or trailers on IMDB play however the picture is corrupted.
- Occasionally apps will randomly close most of the time its the internet browser (no error, it just closes)
- The camera still lags and isn't fluid at all however takes pictures fine.
I think overall there is definitely room for improvement however I have been using it fine for the last few days and it seems quite stable overall.
One problem I did have and I don't know if anyone can help me with it was that I flashed the rom with TWRP however upon rebooting into the new version of CM my recovery was CWM.
Rostitute said:
Hey,
I unlocked my boot loader recently and have begun testing the experimental roms. After the previous post I waited until the latest one was released to test it out. I can confirm that the data problems have been resolved and have been using this rom for the past few days.
The main problems I have encountered are:
- Videos within apps such as Facebook or trailers on IMDB play however the picture is corrupted.
- Occasionally apps will randomly close most of the time its the internet browser (no error, it just closes)
- The camera still lags and isn't fluid at all however takes pictures fine.
I think overall there is definitely room for improvement however I have been using it fine for the last few days and it seems quite stable overall.
One problem I did have and I don't know if anyone can help me with it was that I flashed the rom with TWRP however upon rebooting into the new version of CM my recovery was CWM.
Click to expand...
Click to collapse
CM auto installs CWM as this is what it uses instead of TWRP
I have just moved from a HTC One (which I modded and flashed a lot of ROM's) to Xperia Z1 C6903 but unrooted etc atm
I will be checking things out in the next few weeks or so and see whats out there for my Z1
Just a test build, pre-nightly. Do not install. Early in Feb or March we will have update for KitKat from Sony. Just wait and calm down.

[Guide] A guide to KitKat

Hello, recently there have been a lot of posts requesting help with KitKat on our device. This is why I have created a guide going through the installation, setup, issues and many other aspects of KitKat on our phone.
1. List of KitKat ROMs:
OmniROM
CyanogenMod
ParanoidAndroid
SlimKat
Illusion Roms
C-RoM
SlimSaber
CarbonRom
Dirty Unicorns
MoKee OpenSource
Resurrection Remix
Asylum Omni
2. Installation
If you are on the stock Jelly Bean/ICS Samsung firmware:
-Download Philz kernel and copy it to your SD card
-Download a KitKat ROM and copy it to either your internal or external memory
-Download PA-Google Apps and copy it to either your internal or external memory
-Download Raw Kernel r5 and copy it to either your internal or external memory
-Reboot to recovery by holding down volume up, power and home button at once until you are in recovery mode
-Flash Philz kernel
-Go to "Mounts and Storage" and format /system, /data, /preload
-Reboot to recovery again by going to "advanced", "reboot to recovery" or by holding down volume up, power and home button at once until you are back in recovery mode
-Flash Raw Kernel
-Reboot to recovery again
-Flash your ROM
-Flash PA-Google Apps
-Reboot
If you are on any AOSP based firmware or on any custom TouchWiz ROM:
-Download a KitKat ROM and copy it to either your internal or external memory
-Download PA-Google Apps and copy it to either your internal or external memory
-Download Raw Kernel r5 and copy it to either your internal or external memory
-Reboot to recovery by holding down volume up, power and home button at once until you are in recovery mode
-Flash Raw Kernel
-Go to "Mounts and Storage" and format /system, /data, /preload (formatting /preload may fail, skip if it does)
-Reboot to recovery again by going to "advanced", "reboot to recovery" or by holding down volume up, power and home button at once until you are back in recovery mode
-Flash your ROM
-Flash PA-Google Apps
-Reboot
3. Updating your firmware
Updating your system is very easy, some ROMs (ex. OmniROM) have a built-in updater. Simply go to Settings, About phone and "Update". After that just follow the instructions on screen.
If your ROM doesn't support that option or you want to go old-school:
-Download the updated ROM to your internal/external memory
-Reboot to recovery
-Flash the ROM
-Reboot
4. Bugs, issues
When flashing any KitKat ROM I get a "Status 7 error".
You didn't follow the installation procedure carefully enough. You most probably forgot to flash Raw Kernel or you forgot to reboot to recovery after flashing Philz or Raw Kernel.
Sometimes whilst listening to music, the track freezes and I can no longer access it.
KitKat for our device has a bug in it where this happens. There is NO fix for this. Only a reboot will allow you to access the file again.
Refer to this thread for more information.
UPDATE:
The bug has been fixed however not all ROMs have merged the fix yet. If you are still having this issue then try flashing a kernel with the fixes merged (for example Forest Kernel or Raw Kernel).
Sometimes whilst copying files from my computer, the copying process stops.
This is the same issue as the above one with the music bug. One way to copy files without a problem is to reboot to recovery, go to mounts and storage and go for "mount USB storage". Copying through recovery is stable.
UPDATE:
The bug has been fixed however not all ROMs have merged the fix yet. If you are still having this issue then try flashing a kernel with the fixes merged (for example Forest Kernel or Raw Kernel).
I have battery issues.
This can be caused by many reasons, mainly your apps. Here are a few quick fixes though:
1. If your battery is at least a year old then it may be time to replace it with a new original one
2. Go to Settings, Wi-Fi, menu button, advanced and unmark "Scanning always available"
3. Install Greenify
4. If your ROM supports it, go to App Ops (On CarbonROM: Settings, Privacy, Privacy Guard, menu button, advanced) and disable the permission "keep awake" from as many apps as possible. Do not disable this permission from alarm clocks, email clients etc.
You can also disable other permissions, such as location which will also save your battery life
5. Install Titanium Backup and freeze/uninstall as many un-used apps as possible
6. Install Wakelock Detector to find out what is keeping your device awake
7. If you still have problems, refer to this thread
I haven't got ROOT access.
This usually affects OmniROM users. Download SuperSU zip and flash through recovery mode
I want access to Developer options.
Go to Settings, About phone and tap 7 times "Build number"
I want to change the runtime to ART.
Go To Settings, Developer options and find "Select runtime". Don't forget that the ART runtime is still in development by Google and bug reports shouldn't be filed against ROMs if you experience problems on ART
Every single time I change to the ART runtime, it doesn't change and stays on the current Dalvik runtime.
You have Xposed installed which is stopping you from changing it as Xposed is incompatible with ART. Uninstall Xposed to fix this.
I hope you have found this mini guide useful. If you still have any doubts, please don't hesitate to request more help in this thread.
If you have any suggestions as to what else should be included in this guide, don't forget to drop a line or two.
Nicely done.
Wow u really did a great one there. Hopefully this will be a great help to all "lost sheeps" out there. Well done!
Sent from my GT-N7000 using XDA Free mobile app
Thanks guys
This should be a sticky!
Nice job! Thread stuck.
XxPixX said:
3. Updating your firmware
-Wipe cache
-Go to Advanced, wipe dalvik cache
Click to expand...
Click to collapse
There's no need to wipe anything when dirty flashing updates.
Towle said:
Nice job! Thread stuck.
Click to expand...
Click to collapse
Thank you
chasmodo said:
There's no need to wipe anything when dirty flashing updates.
Click to expand...
Click to collapse
Updated, thanks
Very nice, but I'm sticking with 4.1.2 for several reasons.
One, Samsung hasn't officially (and seriously doubt they will, device is almost 3 years old) released
4.4 to the Note N7000. I usually stick with stock roms (different kernel obviously).
Two, to get kk, you have to jump through some hoops to get it on your device. I'm not above doing it,
it's just too much of a pain, to have to load all the apps, settings etc. Should be a "drag & drop" or
just click, to install.
Three, pretty much every KK rom I've seen, for the N7000, has a glitch here, bug there, battery problem,
BT problem etc. I've heard people flash the same rom to two different N7000's and one works perfect, the
other doesn't.
Four, I've had 4.1.2 on mine, since the day it came out, and, without a doubt, it's been for my usage, pretty
much the most stable rom I've used. When I was younger, back in the 386/486 computer days, it was nothing
for me to spend an evening, tweaking front side buss settings, memory timings, config.sys & autoexec.bat files
to tweak 1-2 seconds of performance from a PC. Today, I'm just after decent performance, and STABILITY.
This device, sadly IS my lifeblood for work. I don't have time for rebooting, lock ups, glitches etc.
I'm shopping around for device...the Note3 was on the list, but the price (I don't do contracts anymore) is a bit
steep, along with getting one to work properly in the USA, means you almost always have to get a LOCKED
down at&t device, with features removed, bloat etc. Got a few on the radar, but I'll just keep going with the N7000.
I'll hate to put her out to pasture, she's been a good ride.
p51d007 said:
Very nice, but I'm sticking with 4.1.2 for several reasons.
One, Samsung hasn't officially (and seriously doubt they will, device is almost 3 years old) released
4.4 to the Note N7000. I usually stick with stock roms (different kernel obviously).
Two, to get kk, you have to jump through some hoops to get it on your device. I'm not above doing it,
it's just too much of a pain, to have to load all the apps, settings etc. Should be a "drag & drop" or
just click, to install.
Three, pretty much every KK rom I've seen, for the N7000, has a glitch here, bug there, battery problem,
BT problem etc. I've heard people flash the same rom to two different N7000's and one works perfect, the
other doesn't.
Four, I've had 4.1.2 on mine, since the day it came out, and, without a doubt, it's been for my usage, pretty
much the most stable rom I've used. When I was younger, back in the 386/486 computer days, it was nothing
for me to spend an evening, tweaking front side buss settings, memory timings, config.sys & autoexec.bat files
to tweak 1-2 seconds of performance from a PC. Today, I'm just after decent performance, and STABILITY.
This device, sadly IS my lifeblood for work. I don't have time for rebooting, lock ups, glitches etc.
I'm shopping around for device...the Note3 was on the list, but the price (I don't do contracts anymore) is a bit
steep, along with getting one to work properly in the USA, means you almost always have to get a LOCKED
down at&t device, with features removed, bloat etc. Got a few on the radar, but I'll just keep going with the N7000.
I'll hate to put her out to pasture, she's been a good ride.
Click to expand...
Click to collapse
Even though it's really off topic, but I will say I do share your sentiments.
Sent from my GT-N7000
I stuck on flashing r5 kernel, after installation complete, I reboot to recovery...my phone was dead, I need connect odin, go Download mode flash back my kernel,only can make my phone alive back..please help
Running 4.0.4 stock rom with rooted kernel
andyshim1989 said:
I stuck on flashing r5 kernel, after installation complete, I reboot to recovery...my phone was dead, I need connect odin, go Download mode flash back my kernel,only can make my phone alive back..please help
Running 4.0.4 stock rom with rooted kernel
Click to expand...
Click to collapse
This is the wrong place to ask your question. Should've gone to troubleshooting section. Your situation might have been caused by ICS kernel. You should've flashed compatible CWM + franco's safe kernel or philz safe kernel n recovery first before flashing anything else in ICS 4.0.4
Sent from my GT-N7000
andyshim1989 said:
I stuck on flashing r5 kernel, after installation complete, I reboot to recovery...my phone was dead, I need connect odin, go Download mode flash back my kernel,only can make my phone alive back..please help
Running 4.0.4 stock rom with rooted kernel
Click to expand...
Click to collapse
After flashing Raw Kernel r5 then you won't be able to boot into your old ROM, only recovery mode and download mode. I'm guessing you chose the wrong reboot option or you didn't follow the instructions properly (rebooting at the proper times for example).
Nice guide mate. Many thanks for your time giving.
Great
Sent from my GT-N7000 using Tapatalk
@XxPixX
Excellent guide, many thanks for taking time to compile this to help others.
Shalom and best wishes, john
Thanks for your guide..!
In the Omni wiki I read.
TWRP is the only recovery officially supported by Omni.
Is this included in the step by step manual?
Thank you
Now with Dirty Unicorns v7.5 !
Nice guide thanks.
Is it possible to flash after cm11, cm10.2 ? Or I have to change kernel or recovery things ?
Thanks
Envoyé de mon GT-N5110 en utilisant Tapatalk
PdroidAndroid said:
Nice guide thanks.
Is it possible to flash after cm11, cm10.2 ? Or I have to change kernel or recovery things ?
Thanks
Envoyé de mon GT-N5110 en utilisant Tapatalk
Click to expand...
Click to collapse
You already will have a superior recovery. So no need.

Categories

Resources