Open KikMyaz opened 1 year ago
It is probably also worth noting that I had used internalblue/android
/samsung_s10e_2019-06-04_vendor_firmware.zip. No modifications were made to VSC_Write_RAM. At the moment I can only get InternalBlue to work within 15 seconds after initiating bluetooth scan. I could automate a rescan with while true; do am start -n com.android.settings/com.samsung.android.settings.bluetooth.CheckBluetoothStateActivity; sleep 19; done
but RAM patches seem to be lost after each rescan.
I also tried samsung_s10e_note20-5g_2021-01-21_bcm4375B1_semco.hcd with the VSC_Write_RAM patch in hci.py but this does not appear to be working at all. This might be because I am on Android 10 which is older than this firmware.
First of all thank you so much for creating this project and sharing your research! This has all been incredibly helpful.
Bug Description readMem/writeMem only works for the first 10-15 seconds after Bluetooth is turned on (or when scanning is in operation). readMem fails 10 seconds after scanning is started, and internalblue produces the following error,
Hardware and OS BCM4375B1 (fw_0x1111.py) Samsung S10e (msm), Android 10, Kernel 4.14 (SELinux Permissive)
Logs/To Reproduce When scanning is off,
But as soon as I tap on Scan in Settings -> Connections -> Bluetooth,
Additional Context As Busybox netcat was used, I had to change all references to
nc -l -p
intonetcat -l -p
for everything to work. This was likely a GNU netcat vs. BSD netcat problem in the new Busybox binary.