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
Related
Any Lollipop ROM that i try works fine but after flashing Gapps and rebooting, pretty much everything force closes and nothing can function. I've tried different Gapps packages and ROM's, wiping cache and dalvik but nothing works. Anyone knows what to do?
I can propose a combination that surely work great.
Rastapop Rom
With L minimal gapps
I tried this, but again all the gapps crash and force close. The only android lollipop rom that works for is the one that has gapps built in. Do you think it's related to CWM? My current version is 6.0.3.6
I have been using TWRP for the last 3 years and never had any problems.
You could give it a try.
I've used CWM for a year and a half now. No problems on Kitkat roms.
Ive tried literally all lollipop roms and gapps but none seem to work
steelheart91 said:
I've used CWM for a year and a half now. No problems on Kitkat roms.
Ive tried literally all lollipop roms and gapps but none seem to work
Click to expand...
Click to collapse
Flash twrp 2.8.4.0. Thats your problem. CWM is out of date.
Csacsifiu said:
Flash twrp 2.8.4.0. Thats your problem. CWM is out of date.
Click to expand...
Click to collapse
Thanks Csacsifiu and rastaviper. TWRP fixed my problem.
Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.
trent4071 said:
Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.
Click to expand...
Click to collapse
Same here I tried it, and it did the same for me also...
Sent from my SM-N920F using Tapatalk
These are the Gapps that worked for me
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
Thank you for the help wikked26, but it didn't work. Those Gapps still crash for me. I think it's something incorrect in the way my phone is configured, not a case of downloading the wrong Gapps.
If anyone has any other ideas, please share them! I haven't cracked the case just yet
I know I was having issues with the Slimroms version where I booted into CM and set it up before installing Gapps. Fixed it by reinstalling/wiping the cache and installing Gapps before booting anything. Don't know if that helps, but I'm running fine now.
I'm hoping this is similar to the issue I'm having. Do you get it where you can factory reset in TWRP, then flash CM13, but when you go to flash Slim Gapps? Because I figured out that after factory resetting TWRP will only successfully flash 1 zip file. I also tried to wipe the cacher, dalvik, data, and system, then flash cm13 but Gapps still wouldn't flash. Maybe its a bug with TWRP 3.0.2? I'm going to try to use a different version of TWRP and I'll update with my results
EDIT: TWRP 2.8.5 did not do anything different
Wow, thanks for all the great responses. I made sure to try and install CM13 and Gapps at the same time, before boot, after wiping everything one last time. It worked flawlessly, and I can now use Google Play Services.
I hope this thread helps anyone else who is also a little stuck. I also found that TWRP didn't have any issues flashing multiple zips at the same time, not sure whats going on with you, Orange Officer. Perhaps try removing your battery after CM13 flashes, and then boot into TWRP again and flash Gapps without booting up CM13 at all?
Hey guys,
I have a little problem with my new OP2.
I unlocked the bootloader and rooted etc.
I installed Paranoid Android and I wanst sure which kernel works on it.
So I tried flashing one for CM13 and one for OOS3, but both of them wouldnt work.
Now Im trying to get back to stock or atleast flash the boot.img from the Paranoid ROM.
I can boot, access the recovery and bootloader. I flashed different boot.imgs (Stock and Paranoid) and recoverys. But none of them helped.
The touchscreen wont react at all. If I boot, if I am in the recovery. It just wont work. Hardware button seems to be fine though.
Any ideas how to fix that?
Try wiping system partition and flash the PA ROM again (and Gapps of course) and it will restore system and kernel back to PA default.
If touch still doesn't work, then you'll probably have to wipe userdata partition as something you installed with the kernels not supporting other than official latest CM13 sources is messing with your system.
You need to flash full stock using fastboot from unbrick guide.
Sent from my ONE A2005 using Tapatalk
google megaunbrick guide oneplus2 and follow that!
didn't got your logic behind flashing custom kernel that too on paranoid android, I can understand that for cm13 as the battery life sucks there but pa easily gives 6+ hrs of sot which any other rom or even a custom kernel can't even come closer to it in my personal experience.
meaning you can try to flash the whole rom through fast boot or use unbrick guide to go full stock.
Alright, so I'm thinking my problem was that i initially had supersu installed when attempting to install this kernel, and thus causing that bootloop.
Can anyone provide insight as to whether this is true. I had a nandroid backup of my stock rom and even though I "restored" it, it was still stuck in bootloop regardless :/. I don't want to keep restarting and reinstalling everything over and over without knowing what the problem is.
I currently run Resurrection Remix with xposed. I'm fearing if I make another nandroid backup for this and try to flash the rom again, it won't work and I have to start again.
FYI: I was on RR when I attempted the kernel install.
Try downloading the kernel again and dirty flash it. If that doesn't work try dirty flashing some other kernel. And if that doesn't work dirty flash your rr rom. And if still not working then restore your backup
billamin said:
Try downloading the kernel again and dirty flash it. If that doesn't work try dirty flashing some other kernel. And if that doesn't work dirty flash your rr rom. And if still not working then restore your backup
Click to expand...
Click to collapse
well what i did was following:
round 1. RR rom already installed
wipe cache and delvik, install kernal, bootloop
attempt to restore nandroid., still bootloop,
attempt 2:
wipe everything and install RR, SU, Gapps
did setup
installed franko r25
attempt 3.
wipe and factory reset
restore nandroid
bootloop
attempt 4
DONT install franco and install ak. after everything
works
Franco kernel needs to be installed twice to work. flash kernel, dont restart, just flash again
feis said:
Franco kernel needs to be installed twice to work. flash kernel, dont restart, just flash again
Click to expand...
Click to collapse
omg thanks! that worked perfectly. Now a new problem is specifically when I'm using tugapower, while typing on my swiftkey into the xda forum. I'm noticing a lag. I've made it so then both apps are operating on performance with franco. Not sure what's causing the lag. Is it possibly the theme?
Dunno whats the problem, but im pretty sure if you just flashed franco, didnt change anything and used those apps, they wouldnt lag
didn't figure out what caused the lag but its gone now
In this topic there is CM13 and then a custom kernel for CM. My question is, is that kernel the same one included in CM13? If so, why is it posted? If not, what changes?
I installed CM13, then flashed that kernel and gapps (cleaned cache, data, everything, with TWRP) but for some reason it stuttered a lot. Google play crashed every few moments and the file explrorer couldnt even open. I tried restarting the phone but it didtn change anything.
Then I tried installing exactly the same ROM again and the same gapps but without the custom kernel, and now it doesnt stutter or crash at all.
Could these problems be caused by the custom kernel, if it was different than the stock CM13 one? Or maybe I had just an unlucky flash?
Now that I think this would be an overall question, not just focused in the i8730...