Database Info

OnePlus One- Camera not Working After Flashing CyanogenMOD 12.1

(H) need help camera not working
iv got cm12.1 nightlies installed and even before i installed nightlies i had a problem where when wanting to use my camera or when an app wanted to use my camera it wouldn't responded and would say "can't connect to the camera" iv tried wiping the dalvik and cache and that didn't seem to work. if you could help me would mean a lot

hewy148 said:
iv got cm12.1 nightlies installed and even before i installed nightlies i had a problem where when wanting to use my camera or when an app wanted to use my camera it wouldn't responded and would say "can't connect to the camera" iv tried wiping the dalvik and cache and that didn't seem to work. if you could help me would mean a lot
Click to expand...
Click to collapse
Download Stock Google GApps from this link http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Download latest CM12.1 nightly, wipe your system completely (including internal storage) and after successful completion of flashing for ROM.zip, flash those GApps.zip

Mr hOaX said:
Download Stock Google GApps from this link http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Download latest CM12.1 nightly, wipe your system completely (including internal storage) and after successful completion of flashing for ROM.zip, flash those GApps.zip
Click to expand...
Click to collapse
did all of that still says cant connect to camera

Before you went on to the nightlies, were you completely unable to use the camera in all cases?

mharis05 said:
Before you went on to the nightlies, were you completely unable to use the camera in all cases?
Click to expand...
Click to collapse
sometimes i could use it but it was very hit and miss

hewy148 said:
did all of that still says cant connect to camera
Click to expand...
Click to collapse
All I can say now is to flash fastboot images of CMOS12.1
Tutorial is available as a sticky thread in General Section

No Response ,phone freeze on CM 13 ,CM12.1 Slim Bit, Resurrection Remix Help...

Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:

sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try using the base rom as v5.6.11 and try using the old twrp v2.8.7

I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.

Try provide with a logcat, might be more useful in helping you.

No other custom rom is working on my mi4i
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..?

sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
astro49 said:
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you restore your nandroid backup like CM12, Mowkee, Resurection if you from new MIUI ROM.
If you want to restore MIUI7 nandroid backup from CM12 you need to flash MIUI7 patch ROM first.
RIYAN X55TU said:
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you flash to CM13, if not you'll get bootloop. If you use default init.qcom.post_boot.sh and your phone heat up it will lags, so use edited init.qcom.post_boot.sh.

Confirmed
Glembozt said:
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
Click to expand...
Click to collapse
I can confirm that this DID magically works!
No need to use the old TWRP, just flash MIUI V6.6.6(I used the fastboot package[1], not sure if recovery package works) then flash TWRP then flash other custom OSes.
[1] bigota.d.miui.com/V6.6.6.0.LXIMICF/ferrari_global_images_V6.6.6.0.LXIMICF_20150521.0000.3_5.0_global_46b5474265.tgz

Wifi and bluetooth not working in R7 plusf

I run CM 13 and want to back to color os because it is not run so smooth. I format and then flash stock recovery image (then recovery) via twrp and reboot to stock recovery.
In stock recovery i wipe data and cache. That's problem come. Before finish, the screen goes black. I try to power on the device, back to wipe data then the screen goes to black again. I try to boot to recovery and fastboot but it remain the same, back to wipe data and then the screen goes to black..
I try repair it using msm tool but because my comp not recognize the device, i use QFIL. And then i can use the fastboot to boot stock recovery. Suceed. But no os inside. Try and error many times, i can power on the device at the end.
But now the other problem comes. My wifi and bluetooth not work. And message nv backup appear.
Flash project spectrum. Wifi and bluetooth work. I flash back to stock os. Wifi and bluetooth not work again..
May someone help me to solve the problem (make bluetooth and wifi work again)?

To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app

uyab.com said:
I run CM 13 and want to back to color os because it is not run so smooth.
Click to expand...
Click to collapse
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.

kishd said:
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
Click to expand...
Click to collapse
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.

celoxocis said:
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
Click to expand...
Click to collapse
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.

uyab.com said:
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
Click to expand...
Click to collapse
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.

celoxocis said:
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
Click to expand...
Click to collapse
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.

uyab.com said:
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
Click to expand...
Click to collapse
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.

celoxocis said:
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
Click to expand...
Click to collapse
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.

uyab.com said:
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
Click to expand...
Click to collapse
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.

celoxocis said:
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
Click to expand...
Click to collapse
wish me luck. I will try your suggestion.

uyab.com said:
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
Click to expand...
Click to collapse
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0

kishd said:
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
Click to expand...
Click to collapse
Oya.. Let me try it..

Solved. WiFi and Bluetooth work fine. Run smooth in CM.

uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
Which method fixed the issue in the end?

Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.

uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
hi sir im having the same problem with my R7 plus can you help me
i already flash my phone using QFIL with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is only OPPO Logo
flash the phone with Msm8x38 with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is phone will boot normal but the problem is same with your problem with WIFI and Bluetooth also appear something with NV partion but can be manage with *#268# but with wifi and bluetooth i cant solve
please help me.
thank you in advance

I'm so sorry. I just log in after a long time and read your problem. Have you solved the problem?

same problem for me, no wifi and no bluetooth after flashing stock rom.
Any idea?

uyab.com said:
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
Click to expand...
Click to collapse
hello,
please ask me where to find persist.img and the method for flashing it.
thanks in advance

Bootloop upon flashing Open Gapps in CyanogenMod 13

Hello!
I could not find any other threads related to this issue, so my apologies if this is a "duplicate" thread
So I found my old Samsung Galaxy Tab 2 10.1 (Model GT-P5113 in Samsung ROM, identified as Galaxy Tab 2 in CyanogenMod) in a cabinet doing nothing, so I thought I would flash CyanogenMod on it and get some use out of it. And so I did; I flashed the nightly build of CM 13 in the "espresso wifi" image. Now, that worked just fine, but when I tried to flash open gapps (open_gapps-arm-6.0-nano-20161217.zip to be exact), I got some sort of boot loop; the device starts and gets into the App Preparer thing (pardon my ignorance) and begins preparing the google apps, and once it does all 16 apps, it starts preparing some other cyanogen mod apps, or at least I believe they are cyanogen mod apps, and then the app preparer just closes, and the boot animation restarts. If I wait long enough, it will once again get to the app preparer and begin flashing 2 apps, I could not see the first one, and the 2nd was the Google app. It would then begin flashing the cyanogen mod apps and then it would close, and the cycle would restart. I flashed Gapps right after flashing cyanogenmod; I did NOT boot into the rom upon installing open gapps. Does anyone know how to resolve this issue? I will provide more information if it is needed. All help is appreciated.

You should only flash gapps RIGHT AFTER you flash CM13. If you flashed it after Cm13 boots up, you will face some issues. (Like bootloops, force closes, etc)
Sent from my espresso3g using XDA Labs

Lightracer said:
You should only flash gapps RIGHT AFTER you flash CM13. If you flashed it after Cm13 boots up, you will face some issues. (Like bootloops, force closes, etc)
Click to expand...
Click to collapse
Hi, Lightracer, thanks for the reply! I did not boot up the tablet after installing CyanogenMod; however the same result occurs whether I flash it with or without a boot up in between (I needed to reflash CM multiple times)

What recovery are you using? Are you sure you're flashig the right opengapps package? (6.0 nano/pico work just fine)
Sent from my espresso3g using XDA Labs

Lightracer said:
What recovery are you using? Are you sure you're flashig the right opengapps package? (6.0 nano/pico work just fine)
Click to expand...
Click to collapse
Yes, I am using the right package; arm 6.0 nano with TWRP recovery

What happens if you let it complete rebuilding the ART cache (app preparer)? Does it do that everytime? Also, did you do a clean flash? (Wiping System, data, cache, art cache, and then flashing the rom? I never had issues like that with installing gapps :silly:
Sent from my espresso3g using XDA Labs

chompy33 said:
Yes, I am using the right package; arm 6.0 nano with TWRP recovery
Click to expand...
Click to collapse
which version of twrp??

smart-t78 said:
which version of twrp??
Click to expand...
Click to collapse
TWRP version 2.8.5.0 (I apologize, I would have said this in the above post, however, I was not home at the time so I was unsure)

Lightracer said:
What happens if you let it complete rebuilding the ART cache (app preparer)? Does it do that everytime? Also, did you do a clean flash? (Wiping System, data, cache, art cache, and then flashing the rom? I never had issues like that with installing gapps :silly:
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
I think I wiped it, however, I may have not wiped everything that was required. I will try this and post back.

chompy33 said:
TWRP version 2.8.5.0 (I apologize, I would have said this in the above post, however, I was not home at the time so I was unsure)
Click to expand...
Click to collapse
thats the cause of your problem. wrong twrp version. go to andi34.github.io and download the latest common twrp (3.0.2-8). choose the zip. you can install it with your current twrp. then reboot back into recovery and reinstall rom and gapps.

smart-t78 said:
thats the cause of your problem. wrong twrp version. go to andi34.github.io and download the latest common twrp (3.0.2-8). choose the zip. you can install it with your current twrp. then reboot back into recovery and reinstall rom and gapps.
Click to expand...
Click to collapse
That worked, thanks! I was initially following CyanogenMod's guide for the specific Galaxy Tab 2 Models (P5100,P5110/P5113), which included older CM images and the older TWRP, but flashed the espresso wifi image upon realizing that the guide was out of date. Also, the newest version of TWRP I could find for the Galaxy Tab 2 was version 3.0.0.0, but it still worked fine.
Thanks to everyone who participated in this thread!

chompy33 said:
That worked, thanks! I was initially following CyanogenMod's guide for the specific Galaxy Tab 2 Models (P5100,P5110/P5113), which included older CM images and the older TWRP, but flashed the espresso wifi image upon realizing that the guide was out of date. Also, the newest version of TWRP I could find for the Galaxy Tab 2 was version 3.0.0.0, but it still worked fine.
Thanks to everyone who participated in this thread!
Click to expand...
Click to collapse
You could download the common twrp which works for every samsung galaxy tab 2 model. The newest version is 3.0.2-8 which is found on andi34.github.io under recoveries. This could be useful if you want to flash newer roms.
Sent from my espresso3g using XDA Labs

Customs just bootlooping

Had some time custom rom.
Yesterday flashed stock
Everythong was fine. Decided to go back to custom
Unlocked bootloader
Formatted data
Recovery reboot
Factory Reset
Flashed RROS
Step by step with instructions
So it isn't even show a bootanimation
Just stuck with black screen
What to do? I know i can go back to stock with dload, but i want custom

LOL
Just UPD
Installed for fun unstable AOSP 8.0 and it is worked
Strange

Installed RROS above and caught bootloop
All in all animation appeared

Rommco05 said:
maybe you should be before in emui and after again install RROS
Click to expand...
Click to collapse
nothing like this worked
Tried lot of times
Solved this problem by flashing vendor.zip from LOS Rom

lofik said:
nothing like this worked
Tried lot of times
Solved this problem by flashing vendor.zip from LOS Rom
Click to expand...
Click to collapse
The Reason Why You Had The Problem Is Because You Installed RROS 5.8.4 Instead Of 5.8.3. You Needed To Install RROS 5.8.3 First And THAN Flash RROS, 5.8.4.
I Had The Same Issue On RROS By Flashing 5.8.4 First.