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!!
Related
Hi. I'm having wifi issues with my Nexus. It started after flashing MIUI. I was using TWRP to flash, it took a while for the google logo to disappear and to get to the Xiaomi bootlogo. After it finally booted, the wifi was stuck to "turning on", but never ultimately firing up(couldn't get it to turn on nor off, even having turning it off). I've also noticed that I have the same EXACT issue with CyanogenMod. I completely returned to stock, i've relocked the bootloader and everything. I tried CM installer today and i'm rooted again with CM, but still I have the same exact issues as before. I don't have these issues with some other roms such as stock, official Omnirom and such, i wouldn't think it would be exactly a hardware issue, since it works just fine with certain roms. Would anyone have an idea why my phone is having this issue? It wasn't always this way. Specifically, I haven't been having issues with 4.4 roms. Does anyone think it could be something related to bootloader, or something?
Juanito216 said:
Hi. I'm having wifi issues with my Nexus. It started after flashing MIUI. I was using TWRP to flash, it took a while for the google logo to disappear and to get to the Xiaomi bootlogo. After it finally booted, the wifi was stuck to "turning on", but never ultimately firing up(couldn't get it to turn on nor off, even having turning it off). I've also noticed that I have the same EXACT issue with CyanogenMod. I completely returned to stock, i've relocked the bootloader and everything. I tried CM installer today and i'm rooted again with CM, but still I have the same exact issues as before. I don't have these issues with some other roms such as stock, official Omnirom and such, i wouldn't think it would be exactly a hardware issue, since it works just fine with certain roms. Would anyone have an idea why my phone is having this issue? It wasn't always this way. Specifically, I haven't been having issues with 4.4 roms. Does anyone think it could be something related to bootloader, or something?
Click to expand...
Click to collapse
i have a similar problem... i rooted my nexus and flashed a custom rom (PACman) when it boots wifi is disabled, also bluetooth doesnt work neither any sounds, no music, no speaker, nothing, so i flashed Paranoid android (both based on 4.3) and i had the same problem
so then i flashed stock, everything ok, then CrDroid (based en 4.4) everything ok, then OmniRom (Based on 4.4) everything ok too...
i posted it here and got no replies, hope someone could help
Yes, right now I'm running an unofficial CM 11, and no issues. I wonder if something needs to be downgraded, in order for things to be okay again. I would still like the option to be able to run 4.2/4.3 based roms. Maybe I could try flashing to stock 4.2 or 4.3, then reroot, and test my results
Sent from my Nexus 4 using Tapatalk
What radio/baseband version are you using?
Hi, I'm using AOKP last nightly builds and since 2013-10-18 Wi-Fi started to stuck, settings ui errors and other problems. So I just tried franko kernel with official AOKP releases and Wi-Fi now is working fine. But i've faced skype problems). After 4 minutes it hangs and i need to restart my phone.
Ok, I was running PA 4 Beta3 but was having problems with the screen delay so thought I would completly wipe my phone, fresh install PA and install the mini Gapps (I had prev installed the stock but didnt want all the apps)
Here is where it started to go wrong, Phone would not start ptopery, would get past animation screen but that was it, would then just crash with small date in corner.
Wiped and flashed just the Rom and this also failed.
Wiped and installed 3.99 and this seem to work but then the wizard crashed and I had to power down.
Booted back up into recovery and dirty flashed Beta 3 again and this seemed ok. Flashed Stock Gapps and rebooted.
All apps have installed again, titanium back has been run but I still have no network what so ever.,
If i go into settings, more, vpn, mobile networks I get 'unfortunately settings has stopped'.
I have dirty flashed again but still have same problem.
I cant do a complete wipe and install again as need to get out of the office, however with the prev problems I had I am weary about doing so.
Can anyone shed any light on any of the issues i had at all?
foxguard said:
Ok, I was running PA 4 Beta3 but was having problems with the screen delay so thought I would completly wipe my phone, fresh install PA and install the mini Gapps (I had prev installed the stock but didnt want all the apps)
Here is where it started to go wrong, Phone would not start ptopery, would get past animation screen but that was it, would then just crash with small date in corner.
Wiped and flashed just the Rom and this also failed.
Wiped and installed 3.99 and this seem to work but then the wizard crashed and I had to power down.
Booted back up into recovery and dirty flashed Beta 3 again and this seemed ok. Flashed Stock Gapps and rebooted.
All apps have installed again, titanium back has been run but I still have no network what so ever.,
If i go into settings, more, vpn, mobile networks I get 'unfortunately settings has stopped'.
I have dirty flashed again but still have same problem.
I cant do a complete wipe and install again as need to get out of the office, however with the prev problems I had I am weary about doing so.
Can anyone shed any light on any of the issues i had at all?
Click to expand...
Click to collapse
Sounds like a radio issue. If you are running 3.99, you need the radio for 4.3 which I do believe 3.99 is based on. You need the radio for KitKat when running the new betas.
Sent with my Nexus® 10 minus 3
This is the easiest way to flash a new radio http://forum.xda-developers.com/showthread.php?t=2607221
If you went up to a 4.4 based rom and it changed your radio to .97 or .98 then you'll need to flash back to a .84 or before.
to go back to 4.3.
I think I basically said that. Sometimes I believe in not holding hands and let the guy/gal do some of the, legwork.
Sent with my Nexus® 10 minus 3
Thank you every one. I have reverted back to my recovery and all is well but I don't understand why when I flash the ROM ad gapps it happens. My recovery is the same ROM and gapps. No idea.
Oh well stuck with the screen delay for now!
Sent from my Nexus 4 using Tapatalk
mrhiab said:
This is the easiest way to flash a new radio http://forum.xda-developers.com/showthread.php?t=2607221
If you went up to a 4.4 based rom and it changed your radio to .97 or .98 then you'll need to flash back to a .84 or before.
to go back to 4.3.
Click to expand...
Click to collapse
Hi mate, thanks for this. I have reflashed my phone again and still have the same problem. My baseband is showing as 84 though s that is correct?
EDIT, dont worry a reboot has fixed this issue. Odd.
Thanks again though.
foxguard said:
Hi mate, thanks for this. I have reflashed my phone again and still have the same problem. My baseband is showing as 84 though s that is correct?
EDIT, dont worry a reboot has fixed this issue. Odd.
Thanks again though.
Click to expand...
Click to collapse
Ohh you are having issues with ur network !! Seen people completely losing their Imei during flashing !! Not to scare you but its better to get the imei files backed up !!
Check my post on the below mentioned link
http://forum.xda-developers.com/showpost.php?p=49753344&postcount=11
Hit the thanks button if you find my post useful
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.
Hey guys. I just recently updated to Android 7 via the resurrection ROM. I have flashed 2 different rooms and this problem still persists. I have done absolute full wipes in between and I have also tried flashing other kernels. This only started as a problem when I went from 6 to 7. Any ideas?
SiqMawsh said:
Hey guys. I just recently updated to Android 7 via the resurrection ROM. I have flashed 2 different rooms and this problem still persists. I have done absolute full wipes in between and I have also tried flashing other kernels. This only started as a problem when I went from 6 to 7. Any ideas?
Click to expand...
Click to collapse
Try different GApps packages.
Gapps solution didn't work. I tried all the way back to Feb gapps packages. I can't get any 7.0 Roms to work without crashing when location is requested. I am back to 6.0 and working fine. What could the issue be? I might try to go fully back to stock then back again.
I'm also having the same problem. I've tried both Resurrection and Lineage.
OP - did you find any solution?
I was having problems with Google Play Services, related to location, and I did type this command on the terminal:
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
See if it works.
Sorry bad english
I've tried Lineage, AOKP, AICP, AOSCP, RR; Delta Gapps, Open Gapps. This problem won't go away.
As far as I can tell there aren't any MM ROMs still being updated? At least the threads are all dead. Really at this point I'm debating going back to stock and waiting for Moto to give me something. Maybe the same bug is what's tripping them up.
purplegreendave said:
I've tried Lineage, AOKP, AICP, AOSCP, RR; Delta Gapps, Open Gapps. This problem won't go away.
As far as I can tell there aren't any MM ROMs still being updated? At least the threads are all dead. Really at this point I'm debating going back to stock and waiting for Moto to give me something. Maybe the same bug is what's tripping them up.
Click to expand...
Click to collapse
Did you try the command, mate? I don't know if someone did try it, and I want to know if it works, because it did work for me
smsporto said:
Did you try the command, mate? I don't know if someone did try it, and I want to know if it works, because it did work for me
Click to expand...
Click to collapse
Just got several messages telling me the action wasn't allowed, even with root
purplegreendave said:
Just got several messages telling me the action wasn't allowed, even with root
Click to expand...
Click to collapse
I tried the command it didn't work for me. The command itself went ok without errors, but it did not fix the rebooting issue. The only solution for me is to put GPS onto battery saver mode, which is not ideal.
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