Hey guys, I have a OP2 running CM13 Official Nightlies. I flashed the OP2 Camera port however it is removed every time I flash a new CM Nightly release. Is there any way to keep this app an other Non-Rom apps from being removed?
Thanks!
Use Cyan Delta for Updating. In the settings you can put the zips you want to flash after the ROM zip. If there is a newer Update just download it -> wait a moment for stitching -> press install. This will flash the whole queue in TWRP.
Thank you just did it and it works. Nice workaround.
You can Dirty flash by just wiping the cache this will keep you apps
Related
I'm currently running an LS980 with a CM10.2 nightly with TWRP and either ZV8 or ZV7–they both have the same baseband? This was all the latest and greatest as of when I updated in December.
Now I'm trying to just to a decent CM11 or Pacman ROM, but I'm getting confused as I wade through disorganized threads with people with questions not related to my setup. There's a whole mess of downgrades and autorec and ioroot and other tools that I don't know if I need.
So I have CM10 and old TWRP, what do I need to do for a stable CM11?
Thanks a ton!
1. Download your rom and Gapps (usually provided on the rom thread)
2. Copy your rom and Gapps to your internal sd card (on your phone)
3. Boot into recovery
4. Wipe Data/Factory, wipe System, wipe dalvik cache
5. Install your rom first, then Gapps
6. Reboot
7. Profit !
As long as you stick with CM or other aosp-based roms, you're good to go. You don't need to do fancy things to have a working kitkat rom with root and recovery.
If you want a Stock KitKat rom, then you're going to need IOroot 2.5 to root your G2 and then use AutoRec (provided by cloudyfa) to get a working recovery.
That's it !
Edit: think about updating your recovery beforehand, it won't hurt and may save you from going back to square one
For whatever reason, team Vanir doesn't maintain an official thread in this forum, even though they have been actively developing ROMs for Z1c ever since KK. @Wind07 started his own thread, with his own builds and links to official builds, but has abandoned it - http://forum.xda-developers.com/sony-xperia-z1-compact/development/rom-vaniraosp-t2874690 I have been a fan of their ROMs since KK, so decided to post some links.
Vanir currently has 2 ROMs in active development for Z1c: Vanir ROM, (http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/amami/), and Commotio ROM, (http://www.emccann.net/dho/3-Vanir-mirror/4-nighties/), and here's their Gapps link - http://www.emccann.net/dho/5-Gapps/
NOTICE **** Latest builds of Vanir ROM do not boot. The last build that booted was 3/10, which runs great, but no camera. I've posted on G+ about it, and dev says looking into it, (https://plus.google.com/111931660643822970788/posts/MV7QYHVZr1r). I can't get the bootloop to show up in adb, so can't get a log. If someone else can, he'd appreciate it. Newest Commotio ROM boots and has camera.
Is this the recommend way to flash it:
Instructions
fastboot boot.img in zip (here is something missing I think)
boot to recovery
format system, data, cache and wipe dalvik
flash zip
reboot
flash gapps(optional)
Marv42 said:
Is this the recommend way to flash it:
Instructions
fastboot boot.img in zip (here is something missing I think)
boot to recovery
format system, data, cache and wipe dalvik
flash zip
reboot
flash gapps(optional)
Click to expand...
Click to collapse
Probably no need for all that. Just do a wipe, then flash ROM, then gapps, and reboot.
4/13 build is good. Still no camera though, (although it's interesting that if you set 'launch camera on button press' in settings, camera app opens, but with 'cannot connect to camera' message). I only tested it without Gapps, but don't think that would make a difference...
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
Hi, If you already have twrp recovery and you can boot into twrp recovery, then you need to download stock oxygen os 2.2.1 ota.
when you download oxygen os 2.2.1 ota, flash it via twrp recovery, after that wipe factory data reset, then you flash your custom roms later. this will bypass the error 7 and you will have to resume enjoying your custom roms.
Here's what happens, when u totally erases the system, data, and formats everything with twrp recovery, custom roms don't run again, i think they kinda need some basic files from the stock rom to enable them to run. i experienced this myself with aicp and this is how i fixed it. so go on, look for the oxygen 2.2.1 ota.zip, download, flash, then wipe data fastory reset, then you can now have your custom roms flashed and working. again.
Right!! but oos 3.0 official is also working
shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
It's there to protect you from flashing a ROM incompatible with your current bootloader (there's two of them, pre oos3 and oos3 bootloader/fastboot).
So if you want to flash a ROM which is Lollipop (or using Lollipop bootloader like easier versions of Graraks and Seraph08s builds) you will have to restore your phone to oos2.x.x first. Same goes the other way around, and also your recovery system must be compatible with respective bootloader.
This info should be force-feeded to every noob checking in on this forum hoping for an easy swapping of ROMs on this phone, which is not gonna happen because of this.
Hello, I've recently installed Temasek's CM 13 nightly marshmallow build to my bootloader unlock note 3. I'm having a difficult time acquiring root after the install. I've flashed SuperSu to no avail. I've even tried the Aramaic tool method with no luck. Is there anything I can do to get root back on this phone or am I screwed?
Look for SuperSU in the settings menu.
Not sure if you need to turn on developer options for it to appear there or not.
[Edit]Did you install CM with a custom recovery, or with flashfire?
Your post doesn't say one way or another, but if you have an unlocked bootloader you can flash a custom recovery using Odin... meaning that you always have root, so long as you preserve the unlocked bootloader.
Having only a single root (locked bootloader and no custom recovery) and using FlashFire to install a ROM puts you at constant risk of root loss.
.
Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.
cblendz said:
Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.
Click to expand...
Click to collapse
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.
bftb0 said:
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.
Click to expand...
Click to collapse
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.
cblendz said:
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.
Click to expand...
Click to collapse
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.
bftb0 said:
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.
Click to expand...
Click to collapse
Thanks a lot that was it. Finally got root. I wish CM would bake root in their Roms but all is good now. Thanks.
My camera is not working since i have flashed the Boeffla Kernel. I tried different camera apps and no one is working. I get a camera connection error everytime, does not matter which app i try.
Because of that i want to flash cm again via dirty flash.
But is it possible to dirty flash a cm.zip over the same cm.zip which is already flashed?
I know that it works if you flash a newer version but will it also works with the same version?
Edit: i have cm13.0-20161013 at the moment.
If there is any cm based rom which is newer and can be dirty flashed over it, it also would be okay. It just should not be Android-N because i just downgraded from it a few days ago (because there is no xposed for N yet)
Edit #2: I just did it and it worked perfectly, thread can be closed, thanks anyway
yes, you can dirty flash the same ROM zip over your current ROM, esp if youre having kernel issues. Thats the main reason why people would dirty flash if youre experimenting with kernels. just wipe the caches a few times (i ususally wipe them 3x just because it seems to work the best), but short answer is yes, youre good to do that