Detect if sitting for too long waiting for twrp
2019-12-16 08:45:21 -0700 - Setup successful: Free-Droid 0.7.12 on windows
2019-12-16 08:57:23 -0700 - Device connection update: android
2019-12-16 08:57:29 -0700 - new device: SM-G900F (codename: klte) (running custom rom)
2019-12-16 09:00:38 -0700 - Starting new flashing procedure.
2019-12-16 09:00:39 -0700 - Call to flash_conductor with device state: android
2019-12-16 09:00:39 -0700 - Progress is: {:unlock=>false, :twrp=>false, :update_twrp=>false, :format_data=>false, :rest=>false, :flashme_pre=>false, :rom=>false, :root=>false, :nanodroid=>false, :patcher=>false, :flashme_post=>false}
2019-12-16 09:00:39 -0700 - Checking progress...
2019-12-16 09:00:39 -0700 - No bootloader unlock needed on Samsung devices.
2019-12-16 09:00:39 -0700 - Detected custom rom. Assuming TWRP already installed.
2019-12-16 09:00:41 -0700 - Progress is: {:unlock=>true, :twrp=>true, :update_twrp=>false, :format_data=>false, :rest=>false, :flashme_pre=>false, :rom=>false, :root=>false, :nanodroid=>false, :patcher=>false, :flashme_post=>false}
2019-12-16 09:00:47 -0700 - Device connection update: disconnected
Then after an hour the user reboots to download mode:
2019-12-16 10:03:51 -0700 - Device connection update: heimdall
This might happen to any user with a buggy twrp version installed before using Free-Droid.
Possible solution: ask the user after a minute (?) of waiting if the screen shows twrp or not. Log the answer for more insightful bug reports. If yes and it was just flashed by Free-Droid, then report buggy twrp to stop using it and tell user to try again in a while. If yes and twrp was assumed to have been flashed by the user, then automatically restart the flashing procedure but force reflash twrp. If no, then something must have gone wrong with flashing twrp. Maybe report a bug.