Hi,
On my storm i have installed cm13. Everything was fine, but now phone reboots when turning on wifi. Dpo you have that issue? im on the 20160415 build. Im restoring stock, and i willpost if it works
What is error 255 in TWRP?
OK, COS 12.1.1 backup is broken I,m very sad. If i can fix it somehow, please post a solution
Regarding to problem, seems to be partially foxed. Like i rebooted the phone 3 times, clean flashed cm13 and resotred cm13 data. It was working. I will post if it wont work again
Nevermind. Still not working
Related
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!!
Greetings fellows! Today I have flashed CM 13.0 on my Redmi 3S Prime (land). After flashing, the device worked like a charm. However, after 1 or 2 reboots, the Wi-Fi stopped working. I can't turn it on. The button is also grayed out. I reflashed /persist and tried everything. The MAC-address has become 02:00:00... etc. Did anyone have the same issue? Could anyone help me? Thank you in advance! (I also tried reflashing stock Stable global MIUI, same issue. I don't think it would be a hardware issue, since the problem persist since the ROM flashing).
Edit: Solved it somehow. After I flashed MIUI, a few reboots later the wireless worked. No idea why.
coda00 said:
Greetings fellows! Today I have flashed CM 13.0 on my Redmi 3S Prime (land). After flashing, the device worked like a charm. However, after 1 or 2 reboots, the Wi-Fi stopped working. I can't turn it on. The button is also grayed out. I reflashed /persist and tried everything. The MAC-address has become 02:00:00... etc. Did anyone have the same issue? Could anyone help me? Thank you in advance! (I also tried reflashing stock Stable global MIUI, same issue. I don't think it would be a hardware issue, since the problem persist since the ROM flashing).
Edit: Solved it somehow. After I flashed MIUI, a few reboots later the wireless worked. No idea why.
Click to expand...
Click to collapse
I'm also facing the same problem . . Plz help out
Created myself a mess and I am at a loss on how to fix it. I was trying to run down the BT issue in AOSP and I remembered that BT works fine on the 915F. So I flashed the TWRP file for the 915F and flashed Mickey's RR ROM. The Bluetooth worked but the touch screen input was of the mark by a considerable margin. I reflashed the TWRP for our 910F, but the touchscreen is still messed up in TWRP. Tried flashing our RR thinking it might have been a kernel issue, still messed up. Tried a TW ROM, no dice. Odined a stock ROM, still messed up. Any suggestions?
May have found the solution...
https://forum.xda-developers.com/note-4/general/expanded-fix-touch-calibration-screen-t3617013
Yesterday my Wi-Fi broke; it doesn't connect anymore. It sees the connection, and saves it, but doesn't connect. This happened on the latest version of RR for the vs995. It worked fine on RR for several hours but then I turned it off and it would not connect again. I tried a clean flash of RR, tried restoring my backup of Weta, and tried a clean flash of Weta. Nothing works.
I'm hoping there is a fix for this without having to return to stock. Thanks for any help.
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