Related
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
the error when booted can be resoled by flashing the latest vendor img, or at least the one relevant to your roms version.
took me about 2 weeks to figure this out because no one would give me the slightest hint when i asked.
the error screen when it first tries to start i havent been able to resolve, and am thinking there may be none.
not sure what your camera issue could be, but i have seen cam issues from the kernel, when the switch to 6.0,1 first began to merge.
maybe test another kernel, other than that i dont know.
Samehere
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
I'm facing exactly the same issue. The camera works fine when I flash a stock based ROM like pure nexus or digitalhigh but as soon as I flash an aosp based ROM or cyanogenmod like chroma,screw'd,benzo. The camera says couldn't connect to camera and nothing seems to work. I've wiped cache, data but still no progress.
I even tried the flashable camera.zip but didn't work.
Problem Solved !!!
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
wrahul31 said:
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
Click to expand...
Click to collapse
Thanks, I have reverted to stock ROM but I might try it soon
Hi,
I have a very big problem.
After I’ve flashed this rom (Unofficial cm13 Mr. Coldbird), the fingerprint sensor disappeared from the settings
How can I fix it?
P.s
It 's my first message , I hope I used the correct section of the forum
Do you flash mm-firmware.zip?
for me it works sometimes and sometimes keep hanging " just vibrating without unlock " .. sometimes it says " hardware is not found "
i entered the recovery and flashed mm-firmware.zip again and the same problem exist ... i'm thinking to back to COS 12.1 it was working perfectly !
I have exactly the same problem, fingerprint option totally disappeared from my lockscreen settings. No idea how to fix it.
Shivver said:
I have exactly the same problem, fingerprint option totally disappeared from my lockscreen settings. No idea how to fix it.
Click to expand...
Click to collapse
when I'm looking for a setting, that I can't find in the settings dialog, I'm using the search function, there. This showed already quite some features.
I'm still on original Cyanogen OS 12.1 (5.1.1), though...
best regards
m
meikelrix said:
when I'm looking for a setting, that I can't find in the settings dialog, I'm using the search function, there. This showed already quite some features.
I'm still on original Cyanogen OS 12.1 (5.1.1), though...
best regards
m
Click to expand...
Click to collapse
Install mm firmware.zip
Sent from Zuk Z1 using Tapatalk
Same Problem here.. In cm13 official and Mr coldbirds Version.. Even with installing mmfirmware.zip
I have the same problem too. It have tested on official CM13 and om Mr.Colbird CM13 versions.
me too
the problem of vibrating that was because of third party app like " screen lock " but if you locked it with power button or double tap the fingerprint sensor will work perfectly :good:
I happen the same. Since I installed unofficial CM 13 (Mr. Coldbird) fingerprint sensor has disappeared.
I have even tried to solve it installing stock COS with qfil, but although the app has appeared again, the sensor doesn't work. I put the finger on it, but no signal arrives to the phone.
I have tried hard reset, install mmfimware, official CM 12 and 13, unofficial 13, but nothing work.
Any idea? Thanks.
Vfc73 said:
I happen the same. Since I installed unofficial CM 13 (Mr. Coldbird) fingerprint sensor has disappeared.
I have even tried to solve it installing stock COS with qfil, but although the app has appeared again, the sensor doesn't work. I put the finger on it, but no signal arrives to the phone.
I have tried hard reset, install mmfimware, official CM 12 and 13, unofficial 13, but nothing work.
Any idea? Thanks.
Click to expand...
Click to collapse
Try this method I have described earlier. It has recovered my Fingerprints already twice. Also because of trying unofficilal cm13. http://forum.xda-developers.com/showpost.php?p=64742948&postcount=2
Planet X said:
Try this method I have described earlier. It has recovered my Fingerprints already twice. Also because of trying unofficilal cm13. http://forum.xda-developers.com/showpost.php?p=64742948&postcount=2
Click to expand...
Click to collapse
I'll try and report. Thanks!!!
I've tries, but it hasn't worked.
Just one question, how do you exit fastboot mode?. I'm a beginner, sorry.
Vfc73 said:
I've tries, but it hasn't worked.
Just one question, how do you exit fastboot mode?. I'm a beginner, sorry.
Click to expand...
Click to collapse
Fastboot reboot or just press the power button until the phone shut down. I don't know went it didn't help you but i have recovered my fingerprint reader already twice with that procedure. You will lose nothing when just flashing the modem and the bootloader. My guess is that the persist.img is the partition you need to restore for the fingerprints. My fingerprint reader has been acted really crazy when i tried the unofficial cm13. Until it stopped working. I restored my backup and did the procedure to recover my fingerprint reader. I'm now on self built odexed cm13 nightly 's with working fingerprint reader.
Stopped working here too. Tried to restore COS but even if the setting is there, fingerprint doesn't get detected (phone keeps vibrating)
simoneser said:
Stopped working here too. Tried to restore COS but even if the setting is there, fingerprint doesn't get detected (phone keeps vibrating)
Click to expand...
Click to collapse
Read my post above. I have recovered two times from this issue. I had it also because of trying unofficial cm13. You will loose nothing but get back your fingerprints.
I have tried but it doesn't work
Inviato dal mio Z1 utilizzando Tapatalk
I have tried too, but it doesn't work.
Vfc73 said:
I have tried too, but it doesn't work.
Click to expand...
Click to collapse
Yesterday my fingerprint stopped again too. So I did the same procedure again and it didn't work anymore for me too. So I tried to flash the official cm13 again. First it didn't work but after a few minutes it started to work again. I really don't know how this is possible but there is one difference. The radio from official cm13 is newer than the one from COS. I'm happy that it works fine again but I'm afraid it will stop again when I try a different rom again.
Hello,
I have posted this on the cyanogenmod forum but everyone seems to be on holiday as I'm getting no replies. I'm hoping someone on here can help.
I recently had CM12.1 running on my S5 SM-G900F for about six months with no problems. I then switched over to CM13 and used that for about a month without any problems.
I decided to go back to CM12.1, I flashed the same CM12.1 Snapshot file that I had been using previously and it installed without error but when I rebooted the phone it would crash and reboot in a loop during start up. I wiped the phone and tried the install again about four or five times having the same problem until on the final attempt it managed to load the OS. Now that I have the OS running I cant connect to WIFI, the 'back' and 'recent apps' buttons on the phone don't respond (the home button does work), the camera app doesn't work (I get the error 'Can connect to Camera') and it keeps crashing and restarting on reboot. Everything else seems to work but the phone seems sluggish and there may be other errors that I haven't come across yet.
I thought that there may be a problem with the zip file I was flashing so I downloaded it again but it did the same thing. I've tried wiping and reinstalling several times but I get the exact same problems. The file I'm flashing is:
cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
If I go back to CM13 everything works fine so the problem is only with CM12.1.
I'm at a lost to explain why this keeps happening as I've had this running fine on my phone previously and wiping the phone and starting again doesn't do anything to solve the problem.
Any ideas please?
Come on people! Have a guess, I'm really stuck here!
I myself have not installed any custom roms on my s5 yet (bc of knox 0x0 lol) but try reverting back to the stock rom and then install cm12.1 again, maybe it could work.
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Can you tell what bothered you to go away from cm13 back to cm 12.1?
caned_monkey said:
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Click to expand...
Click to collapse
ezantera said:
Can you tell what bothered you to go away from cm13 back to cm 12.1?
Click to expand...
Click to collapse
CM13 sucks!!! snapchat and instagram keeps on crashing, now I'm using resurrection remix 5.7.3, that sucks too!!
Hey XDA peeps!
I recently got meself a G4 Plus (32/3 GB, XT1643), and everything has been totally fantastic, except for this: connecting to a Bluetooth device is almost impossible, and using any 7.1 ROM causes SIM errors.
I've been able to connect to my Android Wear watch, but that's about it. I got Motorola's VerveLoop+ headphones too, and it connects to everything but my G4+. I tried multiple things, reflashing the modem file (NON-HLOS.bin), flashing stock ROM, flashing multiple ROMs from the forums (CM, RR, BS, AOKP), none of them fixed the problem.
I'm currently using RR 5.7.4 (MM), and 5.8.0 (N) recently came out. I tried updating but it doesn't read my SIM after the process. I tried flashing the 7.0 "soak" ROM or whatever it is, but nothing, same issue over and over again. I tried a full format and flashing RR alone through TWRP but same thing.
So, what do? Any help on either would be very much appreciated.
themajod said:
Hey XDA peeps!
I recently got meself a G4 Plus (32/3 GB, XT1643), and everything has been totally fantastic, except for this: connecting to a Bluetooth device is almost impossible, and using any 7.1 ROM causes SIM errors.
I've been able to connect to my Android Wear watch, but that's about it. I got Motorola's VerveLoop+ headphones too, and it connects to everything but my G4+. I tried multiple things, reflashing the modem file (NON-HLOS.bin), flashing stock ROM, flashing multiple ROMs from the forums (CM, RR, BS, AOKP), none of them fixed the problem.
I'm currently using RR 5.7.4 (MM), and 5.8.0 (N) recently came out. I tried updating but it doesn't read my SIM after the process. I tried flashing the 7.0 "soak" ROM or whatever it is, but nothing, same issue over and over again. I tried a full format and flashing RR alone through TWRP but same thing.
So, what do? Any help on either would be very much appreciated.
Click to expand...
Click to collapse
I have multiple Bluetooth devices and connections all day long and I'm on RR 5.8.0 atm but no issues like you happened to me ever(XT1642, MM stock modem). Maybe with flashing you messed up the modem so sim detection etc. Is gone? Did you tried to separately flash the M modem?
strongst said:
I have multiple Bluetooth devices and connections all day long and I'm on RR 5.8.0 atm but no issues like you happened to me ever(XT1642, MM stock modem). Maybe with flashing you messed up the modem so sim detection etc. Is gone? Did you tried to separately flash the M modem?
Click to expand...
Click to collapse
Tried it before and tried it just now, and still nothing... Right now I'm more concerned about the Bluetooth thing, its bumming me out. I reverted back to RR 5.7.4 from a backup, but even on 5.8.0, Bluetooth wouldn't work.
Anyone know what to do?
So if I understand correctly Bluetooth has never worked properly for you ever since you bought the phone?
If that's the case and it doesn't work even with stock firmware you should consider hardware fault.
I would put stock back and try to get it serviced.
gabriwinter said:
So if I understand correctly Bluetooth has never worked properly for you ever since you bought the phone?
If that's the case and it doesn't work even with stock firmware you should consider hardware fault.
I would put stock back and try to get it serviced.
Click to expand...
Click to collapse
No what happened is that after flashing RR, the thing stopped working. I tried reverting back and it's the same. It's not that Bluetooth isn't functional, I can connect to my laptop and my Android Wear watch, but it won't connect to my Bluetooth headset (the VerveLoop+ as I mentioned)
themajod said:
No what happened is that after flashing RR, the thing stopped working. I tried reverting back and it's the same. It's not that Bluetooth isn't functional, I can connect to my laptop and my Android Wear watch, but it won't connect to my Bluetooth headset (the VerveLoop+ as I mentioned)
Click to expand...
Click to collapse
If it was working with stock, you should be able to get it back to work.
I would focus in making it work again in stock.
Make sure you flashed the right version for your model and so on.
STOCK
FLASH
gabriwinter said:
If it was working with stock, you should be able to get it back to work.
I would focus in making it work again in stock.
Make sure you flashed the right version for your model and so on.
STOCK
FLASH
Click to expand...
Click to collapse
Well thing is, I tried doing that before, after flashing RR the first time, Bluetooth stopped functioning properly, be it in CM or stock, same thing.
Note: I was able to fix the weird SIM thing with 7.1, but Bluetooth issues still persist.
themajod said:
Well thing is, I tried doing that before, after flashing RR the first time, Bluetooth stopped functioning properly, be it in CM or stock, same thing.
Note: I was able to fix the weird SIM thing with 7.1, but Bluetooth issues still persist.
Click to expand...
Click to collapse
A bit off-topic how did you fix the weird SIM thing with 7.1?
gabriwinter said:
A bit off-topic how did you fix the weird SIM thing with 7.1?
Click to expand...
Click to collapse
I don't really know, I was looking for a workaround and I backed up my RR 5.7.4 ROM, then when I hit restore it wouldn't work, so I flashed RR 5.8.0 just to see what will happen and it got fixed... Really odd how that worked...
Edit: Never mind it, it went back to how it was after restoring my backup properly. I tried updating but it didn't work. For 7.1 issues, I'll just wait until the official update and flash the modem file for it, I really hope it works.
Hello Guys,
pls help me.. after flashing cm13 RR ... when i m installing watsapp .. bootloop occurs.. camera 360 as well, i flashed stock fimware and the flashed cm13 rr ..but no luck
same problem
I have pretty much the same issue but it's not exclusive to whatsapp, other apps send the phone into a bootloop as well, this started a while ago, I installed the cm12 last year or so and it worked great for a long time, then after a while I tried to install the spotify app and things went south, phone went into bootloop so I deleted it from recovery mode and just ignored the issue. Yesterday I installed the cm13 hoping I would get a clean slate, I did everything right, full wipe, flashed the rom, gapps, patch and front cam fix and although everything kept crashing at first ( google launcher and pixel launcher) I eventually got it working, I installed messenger, worked fine, then tried to install whatsapp and it went into a bootloop. Anyone please help us.
DarudeNotSandstorm said:
I have pretty much the same issue but it's not exclusive to whatsapp, other apps send the phone into a bootloop as well, this started a while ago, I installed the cm12 last year or so and it worked great for a long time, then after a while I tried to install the spotify app and things went south, phone went into bootloop so I deleted it from recovery mode and just ignored the issue. Yesterday I installed the cm13 hoping I would get a clean slate, I did everything right, full wipe, flashed the rom, gapps, patch and front cam fix and although everything kept crashing at first ( google launcher and pixel launcher) I eventually got it working, I installed messenger, worked fine, then tried to install whatsapp and it went into a bootloop. Anyone please help us.
Click to expand...
Click to collapse
exactly.. we were on same page .. pls any one help us
I have the same issue on CM12. Phone get stuck in boot-loop after installing whatsapp latest version. I was able to get out of boot-loop after I deleted whatsapp app.
Its very important to use whatsapp. Please any fix for this?
I couldn't find a fix. The best you can do move to nougat ROMs like aicp or crdroid.
I installed crdroid and it's excellent
I too am now stuck on boot loop due to Whatsapp.
I do not need this app and will happily delete it, if this is what is causing the issues, but my problem is, how do I delete it now that I am stuck in a boot loop?
Enter safe mode and delete the app.
It's better to remove cm12 and install new ROM crdriod
GalaxyNote2_ said:
Enter safe mode and delete the app.
It's better to remove cm12 and install new ROM crdriod
Click to expand...
Click to collapse
Thanks for the reply.
This may sound a bit noob, but how do I get it into safe mode?
I have an Xperia Mini Pro SK17i
I managed to get it into recovery mode earlier, but cannot seem to get into safe mode
Yeah!
It happens in 5.1 / 6 custom roms!
Can any body help ??!!!
You need to read this thread. Every CM rom compiled before 2018 will have this problem.
https://forum.xda-developers.com/showpost.php?p=75391884&postcount=18