Hello, i run CM13 nightly on my X. At a point in october, updates would not install anymore, recovery showed error 7, so i used this guide
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
to update Bootloader/kernel to OOS3, and istalled the latest nightly update.
All working fine except HDR in every camera app i tried. Normal camera modes work fine.Today i installed the latest CM update, still nothing.
Any help?
you can flash slimroms 6
hdr working my device
Related
Hello XDA-users,
I just installed the CarbonROM for my D802.
Now when I install Viper4AndroidFX I get no effect at all.
I tried to force it, I tried to run in compatible mode, I've tried various drivers.
When I click on Driver-Status, it tells me: Processing : no.
Can someone tell me what I'm doing wrong?
Maybe it's just not compatible with Carbon-ROM? Or with 4.3.1? I don't know....
Need to use SuperSU. Its the same thing on all 4.3 aosp roms.
Flash this in recovery
http://download.chainfire.eu/351/
I just tried it and it still shows me "processing:no".
Hi, I've had my Z2 tablet for a while now. Soon after opening the box, I had the device rooted and cyanogenmod installed, however, this came with a problem that i have now had for ages, whenever i install or update my CM version, it automatically wipes the recovery i have installed, and installs the crappy CM recovery. I have since tried to flash other recoveries, they say they have worked in Command Prompt, but when i boot into recovery, i am greeted by the Cyanogenmod recovery. Help please!
SGP512 Wifi only, 32GB, CM12 Nightly, latest as of 24th Feb 2015
I know this has been mentioned elsewhere for other Xperia Models, typically newer than the Z U, but I am running in to an issue where my two z ultras are trying to use the same mac address.
I wondered if there was a device specific work around for the z ultra and / if this is being addressed.
Running the latest nightly CM12 builds.
Cheers in advance.
http://d-h.st/agR
Download this zip and flash, it is a fix for when the mac address changes after flashing a custom rom.
Regards
Hi,
Thanks for the post, but unfortunately I am getting a package verification error and a footer error when I attempt to flash the package in recovery.
You are using cyanogenmod recovery, right? If so, you have to use TWRP or CWM to flash it, cm recovery have signature check and you can't turn it off, all custom recoveries have it disabled by default.
Regards
Thanks for the heads up teddy. I was using CM recovery. Installed TWRP and flashed the zip/update. However, CM12 goes tits up with TWRP every time I update CM12 and only seems to play nice with CM recovery. Gapps seems to be the issue with none stop force stops. Seems in order for this to work I have to flash TWRP, flash the mac address zip and then flash CM recovery back every time I want to update via nightly.
You can flash TWRP to the FOTAKernel partition if you don't want to flash it everytime you update rom and if you flash it, it should work like CM recovery and it will be booting instead of CM recovery. Just download an app called Rashr and install TWRP from the app I assume the fix is working for you, isn't it?
Regards
I did use rashr to install TWRP and that's when the issues arose.
Unfortunately the nightly update came through after installing TWRP so I did the update for 30th and the phone was in an unusable state via gapps force closes as mentioned. So I flashed back to CMr via the update and haven't installed the update yet.
Until I have a workable solution to the recovery issue I won't be proceeding. It will be too much hassle each time the updates arrive.
I don't think that gapps are force closing because of the recovery installed, that would be weird. Have you tried flashing another gapps? Because I have also used CM12 with TWRP and gapps and I haven't got that sort of problems, even now I am using CyanideL (CM12-based) with TWRP and on my configuration it is OK. I will try using CM12 nightlies with TWRP tomorrow and I will write you back if I found a solution
Regards
Yes, I was using the signed gapps dated late last year, but when I came across the issue I reflashed the whole of CM12 with the more recent ones dated April I think. I still had the same problem, which is when I read up and saw it was attributed to using a non-CM recovery and reset everything back to CM12 nightly + CMr, I did however keep the most recent gapps. Let me know how you get on.
So, I flashed cm 13 nightly from cm 12.
Honestly this rom is excellent, but its not providing root excees even after tapping build number and set none to "apps & adb"
So, I went to download cm 13 feb 10 (Latest update) Its downloaded successfully but when I tap update my phone restarts and goes to recovery and then it says "Installaition aborted"
Please give me a solution about this as I can't connect my phone to odin and root excess is not working either.
I'm just wondering if my pocophone has a problem because the portrait mode on my stock camera app is not working and it only shoots normal pictures rather than having a blurred background. I've tried a multiple times in many situations still not blurring the background. I have a gcam and its working fine thats why im wondering why the stock cam app doesn't. If anyone has the same problem let me know how you fixed it. TYA
Can anyone tell me how can i update from custom rom nitrogen os to stock miui without compromising twrp recovery?
Rehan Sheikh said:
Can anyone tell me how can i update from custom rom nitrogen os to stock miui without compromising twrp recovery?
Click to expand...
Click to collapse
This is OT here. But since you have already posted, after flashing stock ROM, do not boot into system. Reboot into recovery and you should boot into TWRP. Then boot into system. If it doesn't work, flash TWRP again after the ROM and flash Magisk for good measure before booting into system.
Same problem, when shooting the portrait photo it blurs the background but when i open the photo in the gallery it's just a normal pic ?
Did you apply the twrp or magisk fix for gcam? If so, that's probably what's causing it (I noticed it as well when I installed gcam). This issue is fixed on the latest stable version, because you don't need the fixes anymore for gcam.
Me too have the same problem
My poco f1 portrait mode is also not working but in google camera portrait mode is working