After upgrading to OxygenOS 5.3.8 I enabled developer mode by tapping the build number, afterwards I wanted to turn it off by using the switch in the developer mode settings page, when I turn it off and exit the settings app the development mode is re-enabled I have tried rebooting the phone but the issue still persists,
Tested on a oneplus 3 with the latest updates and it his does not occur, tested on the previous OS version and not an issue
Can anyone recreate it? Oneplus' response is to factory reset the phone
Related
I just updated the software from kitkat to marshmallow via samsung kies sofrware. There are many problems iam facing.
1) The keyaboard pops up automatically on the lock screen menu and it doesn't go away neither it lets me enter the pin code. In the end i have to restart my phone.
2) the ultra power saving mode doesn't work. It looks like it is disabled permanently.
3)Many apps like facebook,twitter and Instagram they stuck while working and then they automatically restart. I never faced these issues on kitkat.
4) Battery issue. Battery drops to 80% after a complete charge
Factory Reset it
I was running developer preview 2. it just randomly rebooted and kept going to first google logo and then tuned off and then back again. after 3 or so hours of troubleshooting like complete wipe including userdata installing the same dev preview 2 over and over again i gave up and let it keep boot looping and after an hour it booted back into android. i clicked settings icon and it froze and again reboot.
This is a known dev preview 2 issue and its ongoing currently on the issue tracker.
problem with my device is i cant even flash back to get it to boot since oem unlock switch was off when it random rebooted.
i gave it in service center, they want to change the motherboard for around 16k or 236$ which is just unacceptable and i cant shell out that kinda cash either.
if the oem unlock switch was on i could have flashed back to 7.0 stable.
any suggestions?
Hi All,
I need a help, i am having a coolpad note 3, rooted through kingroot, flashify used to install twrp and upgrade to MM. Phone was working absolutely fine for more than 6 months, post which when i tried to enter recovery mode phone does not allow to enter the mode. Power button and volume up pressed, it shows option of recovery mode below but nothing happens post that.
Tried various methods to root it again while it was booting up (had to restart several time to get to main screen) but all the efforts failed. Now the state is it restarts and stays at coolpad powered by android screen and nothing happens post that. it remains indefinitely at this screen with nor reboot or any change.
Note: USB debugging and OEM options are enabled in developer mode.
Will require your help to suggest how i can get the phone working back to normal.
Thanks for your help.
I've purchased 12 of these Tablets for my company. Out of the box they were android 6.0, as soon as we connected them to WiFi the 7.0 Update option came up so we updated all 12. We then loaded our Comodo MDM enrollment on them. Well Next time they rebooted 9 of them would not come up, they just sit at the samsung screen fading in and out. I went into recovery mode to try factory reset & wipe, I get the message that "mdm does not allow factory reset". So I tried resetting the cache which did nothing as well. So I loaded Odin and booted into odin mode tried to load a stock rom and I get the message that the device is in FRP mode and cannot load a custom image...
I have ALWAYS had droids and I favor Samsungs normally.... I have always rooted and unrooted every device I've ever had, but these have me stumped... I cannot get into USB debugging mode, I cannot get the things to boot at all. Every tutorial requires debugging mode. Samsung Business support is NO help at all. So I turn to the dark side... HELP!!!
cpubugs said:
I've purchased 12 of these Tablets for my company. Out of the box they were android 6.0, as soon as we connected them to WiFi the 7.0 Update option came up so we updated all 12. We then loaded our Comodo MDM enrollment on them. Well Next time they rebooted 9 of them would not come up, they just sit at the samsung screen fading in and out. I went into recovery mode to try factory reset & wipe, I get the message that "mdm does not allow factory reset". So I tried resetting the cache which did nothing as well. So I loaded Odin and booted into odin mode tried to load a stock rom and I get the message that the device is in FRP mode and cannot load a custom image...
I have ALWAYS had droids and I favor Samsungs normally.... I have always rooted and unrooted every device I've ever had, but these have me stumped... I cannot get into USB debugging mode, I cannot get the things to boot at all. Every tutorial requires debugging mode. Samsung Business support is NO help at all. So I turn to the dark side... HELP!!!
Click to expand...
Click to collapse
Sounds to me like the problem isn't with Google's FRP lock but with the Comodo MDM enrollment. First thing I'd do is contact their tech support. The FRP lock doesn't prevent you from flashing a ROM with Odin. The FRP lock would just ask for the Google login and password on the first reboot. And I have seen other security apps blame the FRP lock for not allowing a ROM to flash via Odin.
I've updated my 6T to OxygenOS 10 successfully and factory reset my phone after the update as well. The phone now has a stuck yellow ting everywhere but on the lock screen?
Any have any idea whats gone wrong or how to fix it?
I'm in the same situation but then i tried changing display settings in below location
Display -->Screen calibration
In the Advanced setting you can go for
1.AMOLED Wide gamut
2. Display P3
Where you can avoid that yellow tint
sounds like night mode is on always on night mode did you have any magisk mods installed and if you use xxx rom you needed to uninstall and reinstall after you boot 10