Developer mode can not be activated after deactivation in 3.0.2.8 [not relevant]

asked 2019-04-03 19:47:48 +0300

chris_bavaria gravatar image

updated 2019-04-03 21:22:08 +0300

After the developer mode has been deactivated, it can not be switched on anymore. I tried fix the SMS problem from https://together.jolla.com/question/202278/sms-does-not-work-after-installing-3028/

Is it possible in the recovery mode with chroot to reactivate the developermode?

Edit and close: In fingerterm it was able to get root. The command "ss s" respond the system with 3.0.1.14. But in GUI of systemupdates the system shows 3.0.2.8. After "ssu release 3.0.2.8", "version --dup" in the terminal and reboot the system the developermode works again :))

edit retag flag offensive reopen delete

The question has been closed for the following reason "question is not relevant or outdated" by chris_bavaria
close date 2019-04-03 21:23:19.589111

Comments

1

If this is true, this is a bug. What do you precisely mean by "can not be switched on anymore"? Is the menu item missing from the settings app? Or is activation ineffective?

Maus ( 2019-04-03 19:55:59 +0300 )edit

After accepting the terms of use for developers the progressbar appears. After 30sec the screen jumps back to the developer-tools menu, but the developer mode is still deactivatet.

chris_bavaria ( 2019-04-03 20:13:04 +0300 )edit

I had the same problem with the developers mode. With Sailfish OS 3.0.2.8 (Oulanka) , try to enable and after a while it was going back unenabled. New phone, never had it enabled before. Also it was impossible to start in recovery, so I was reflashing the phone and after that, everythings fine.

tom ( 2019-04-03 22:55:19 +0300 )edit

why closed? - same issue in 3.1.0.11 e.g. once developer mode has been disabled, one cannot re-enable it....and by the look of it, there's a bunch of threads all over TJC. Accepting the disclaimer only leads to an endless "preparing changes" progress bar...which eventually dies back to the previous menu with the option still disabled.

fpb4 ( 2019-09-15 13:43:16 +0300 )edit