Hi, i recently installed the Resurrection REMIX rom for the shield k1, and it's impossible to connect to wi-fi as the activate-deactivate button is locked (gray) and it does not work even after a reboot, i can bring the wi-fi list in the notifications bar but if i try to deactivate it, it activates again.
is anyone facing a similar issue? how can i fix it? this wasn't a thing when i had the stock ROM with android 6.0.1 and i'm truly annoyed by this.
update: tried reinstalling the custom rom, now i can't complete the setup, and using power + volume down will not bring recovery mode to restore the stock ROM, now i'm left with an unusable device, what a nice day.
Related
Ive had a long running problem with my tf101, where it sometimes dies with its asleep. Simply, i tap the power button to put it to sleep when im not using it, and when i come back to use it, i tap the power button to bring it back, and nothing. I have to hold the power button for 10 or so seconds to get it to reset. Seems like its freezing before it goes to sleep. Its done it on any rom i flash, so i dont think its a rom issue.
I'm running CM10 nightlies. Im wondering if this is a kernel problem, so i tried flashing the KAT kernel found here:
http://forum.xda-developers.com/showthread.php?t=1841851
It booted, but killed my wifi. I tried a few things to resolve the wifi issue. Cleared cache/dalvik, wiped all data, nothing helped. Restored my cwm backup from before the kernel install, and wifi came back.
Im having trouble determining what kernels are ok to use with CM10. Does it matter? Did i maybe run into some other issue with KAT that wasnt specifically a kernel problem?
Thanks!
I am having issues when unlocking my phone
Whenever i click the unlock key it will unlock my phone, however randomly it will shut the screen off, turn it on again, shut it off etc. WIthout even touching the button this is happeneing. It will also occasionally bring up the power menu (cm10) for the phone. I dont think it is a hardware thing because my button feels fine and isnt broken. However i am wondering if it is cm10, i recently changed from stock cm10 to liquidsmooth and it still does it. Any advice would be great.
Did u data wipe/factory reset before u flashed the new ROM?
UNL◎CKED & L◎ADED GS|||
Yes i did at least through clock work mods factory reset
Have you been using the same kernel through all this?Also is it the correct kernel?
UNL◎CKED & L◎ADED GS|||
I have been using the same kernel i should probably check to ensure it is correct
Hi everyone. I have a problem and i hope i can get the solution from you guys.
My oneplus one screen won't turn on manually, either double tap or power button. sometimes i try it randomly and repeatedly with tapping the screen and power button and suddenly turn on. but when the screen turn off (manually or automatic turn off), it won't turn on again.
My phone can still receive call, notification, etc but when trying to turn it on, futile. I try to trigger it with charging it and it's work. but when it turn off, it won't turn on again. i can plug/unplug the usb to turn it on, but i won't do that because you know why.
This is happened when this morning i want to try to install colorOS (http://forum.xda-developers.com/oneplus-one/general/rom-4-4-2-coloros-2-0-36beta-t2955853) and calkulins cm11s rom (http://forum.xda-developers.com/oneplus-one/development/rom-calkulins-oneplus-one-v1-0-t2810365) in multirom using this guide (https://forums.oneplus.net/threads/...ere-are-my-samples.176376/page-3#post-8703604).
My rom at that time are already on calkulins cm11s. but the bad thing is i forgot that my kernel are franco kernel r34 while multirom need kernel with kexec hardboot.
this is my step by step how can i get this:
- nand backup the current rom (calkulins cm11s)
- wipe, flash colorOS
- install multirom manager, download multirom and the recovery without cm11 kernel. reboot recovery
- add rom using my last backup, reboot to colorOS
- install cm11 kernel from multirom manager, reboot.
- try booting to cm11s but won't boot. hard reset and try booting again. it work. play it quite a while. try to turn it on manually but failed. REALIZED that i'm still using franco kernel. reboot recovery. (the problem start from this step)
- wipe 2nd rom, add rom without using backup, same problem (cannot turn on manually).
- wipe 2nd rom again, wipe colorOS, restore backup without add another rom, same problem.
- uninstall multirom, install twrp, restore backup, same problem.
- install new rom without backup, for 15 minutes is working and then same problem.
- Now i'm charging my phone because it's out of battery.
Can someone help me?? and i'm sorry for the long post and maybe for my bad english.
Currently I try flashing colorOS and everything work normally. Can I assume that maybe some colorOS setting stuck on the phone and made the cm11s rom behave like that? and if it is, how can i remove it?
Same Issue
I've found a solution that worked for me with the same issue.
i've disabled 'prevent accidental wake up' ind dsiplay settings
g.tscharf said:
I've found a solution that worked for me with the same issue.
i've disabled 'prevent accidental wake up' ind dsiplay settings
Click to expand...
Click to collapse
worked for me too
flash color os 1.2 (Android 4.3) and flash CM11S
So I ve had this problem for quite some time and I haven't been able to fix it for ages.
I have a dual boot setup with a 4.4.2 ROM and 5.1 Temasek build on my OPO and whenever I call someone on the 5.1 ROM the screen never lights up again when the call ends. My only option is to hard reboot my phone. This doesn't happen on 4.4.2 though.
I tried flashing the latest firmware quite a few times but nothing fixed it and I really don't wanna erase all my setup.
Any ideas? Would be much appreciated.
-Regards
MetalmanIX said:
So I ve had this problem for quite some time and I haven't been able to fix it for ages.
I have a dual boot setup with a 4.4.2 ROM and 5.1 Temasek build on my OPO and whenever I call someone on the 5.1 ROM the screen never lights up again when the call ends. My only option is to hard reboot my phone. This doesn't happen on 4.4.2 though.
I tried flashing the latest firmware quite a few times but nothing fixed it and I really don't wanna erase all my setup.
Any ideas? Would be much appreciated.
-Regards
Click to expand...
Click to collapse
Hit the option so the power button hangs up the call, enable double tap to wake. See if either of those things work.
bootloader unlocked
MIUI 9.5.19 global ROM installed
Magisk 16.4
Have been using the phone for 2 weeks now it's the second time that the phone shut down because of battery to low. OK so far but it then only is booting into TWRP. Also deleting DALVIK and CACHE i can see it booting and then the black screen with the navigation arrows are visible for a second. It's seems that there is something preventing the system to come up properly. After 5 short attempts with black screen and navigationbar visible it boots into TWRP.
Also re-flashing Magisk is not solving it.
OK I could now re-flash the Global ROM again but it won't fix the general issue why the phone get's stuck once it shuts off because of empty battery and again I would loose all my data.
Anyone with ideas how to fix it or what could be the root cause?
EDIT: It seems that there is really a problem with the system itself. If I instantly hold the power button once booted until the black screen I could keep it running and I see the restart, shutdown, airplane buttons but nothing more.
In Windows I would say it's not starting the explorer.exe
anyone who had something similar?
Have you tried re-flashing with MiFlash?
Bootloop after weeks of normal use is pretty misleading considering that you are using a custom recovery that isn't even official plus Magisk and possibly other mods. You should flash the official stable ROM with the MI Flash Tool and then run the phone without any mods to see if you still experience the same problem. And if you decide to use TWRP again you are better off using it through fastboot so the stock recovery remains installed on the phone.
THx for your replies... I think I've figured it out:
It seems that the alternative launcher is the root cause. I've been using Microsoft Launcher since moths across all my devices (light+fast+sexy). Without it (replaced by Nova now) it seems that the problems are fixed