Forum Discussion
[Guide] First aid for bug reports
I don't see any way to do this on a real device, except for work profile enrollment (BYOD).
ADB must be enabled in the developer options. However, this cannot be done until the setup wizard has been completed. We once found a flaw that allowed us to break out of the setup wizard. But as long as it wasn't completed, we couldn't enable any developer options.
If the ADB is fully available during enrollment, this may have an impact on security. See, for example CVE-2025-22442
As an admin, I would wish that there was a way, for example via DPCextras, to activate developer options/ADB in order to better investigate problems during enrollment.
I had a call with Samsung yesterday, and they have an option in OneUI to set debug mode to high. This setting is saved during a factory reset and logs everything I need. But as far as I know, only Samsung has this option.
It is indeed a security risk if we would be able to enable it during setup. But yes, it would be very. helpfull to have an easier way to get logging options during enrollment.
I have seen the option again on Samsung devices to exit some MDM's during enrolment to enable debug logging but didn't know if set to High it stayed on after a Factory Reset, is any special configuration required to enable this?
Not them i'm aware of, just go to the dailer and enter *#9900#. In that menu you can set the debug level. Set it, let it reboot and perform a reset after that. It should stay on.
It's good to know that the logs in SysDump survive the factory reset with Debug Level "High". 😃 You probably need to run "run dumpstate/logcat" before performing a factory reset, right?
Yes, you set it to mid or high, perform a reboot and then a reset. Do the enrollment to reproduce the issue and after that you should run dumpstate/logcat
But while writing this I remember that some logs are cleared after reboot, so not sure what sticks and what not. But i'll have to test this soon.
