From 6da45530b943f4f2e448f710a0e7a661456caceb Mon Sep 17 00:00:00 2001
From: Luxferre <3335173-suborg@noreply.users.gitlab.com>
Date: Wed, 29 Jul 2020 21:07:00 +0300
Subject: [PATCH] Something

---
 README.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/README.md b/README.md
index 571098a..5550c21 100644
--- a/README.md
+++ b/README.md
@@ -78,6 +78,12 @@ Most probably, no, but you may try.
 
 No. Not in this utility. Flashing MediaTek SoCs via USB is much more complicated than dumping. The process is generally quite fragile, relies on more proprietary, internal and undocumented logic, and in total requires much more research and rigorous testing on different devices with potential risk of bricking them to an unflashable state. When such research is complete, another utility will be published.
 
+### Are there any plans to move to direct USB access instead of relying on the USB-Serial drivers installed in the OS?
+
+Yes, there are some plans to create a PyUSB-based version and then a browser-based JS port (using WebUSB). This would unlock the access to the devices with non-standard BROM ports not seen by the USB-Serial drivers for some reason (including but not limited to MTK-based Nokia S30+ phones).
+
+However, for this to happen, first all known issues (stated in the section below) need to be solved. Second, as this would drastically increase the codebase size, it might be wiser to do this porting as a part of a larger effort, for instance, when creating the universal utility for dumping and flashing after the research on the latter is complete.
+
 ## Known issues
 
 - Reset-after-dump functionality doesn't have stable behavior (so it's not recommended to dump phones with non-removable batteries for now)