Closed 0oERASERo0 closed 1 year ago
Give it a git pull
to grab the latest version.
It looks like you're using 0.0.3
, but I think i fixed the issue you're seeing with 0.0.4
I git pulled, restored the stock env and follow the steps again.
However, it didn't work. I think the problem is that --enable_burn_mode
didn't work for me.
Because it didn't enable USB Burn Mode at every boot.
When I plug it in, the Car thing show the logo for a sec and GX-Chip appeared.
After a few sec, it reboots itself and boot normally instead of stuck at the booting logo.
Failure to gain ADB access on normal boot
https://github.com/frederic/superbird-bulkcmd/issues/14
Maybe it's due to an update changing some memory addresses?
Hmm, I haven't personally tried it with WSL + usbipd yet, maybe there's something odd I need to account for WRT USB device population. Let me set this up tomorrow and I'll see what's going on
Ok thanks!
Here's are the resources in case you need it.
WSL & usbipd
https://learn.microsoft.com/en-us/windows/wsl/connect-usb
It would be valuable to see if you get the same result if you do it natively from windows, instead of using WSL. You will need to install python of course, and the needed package from pip.
Well, I used a ubuntu live USB and do the work on it. And, it works perfectly now! I think is the usbipd is the problem, because it has to reconnect the devices every time if the carthing reboots. Thanks for the scripts!
Happy to help!
Hi, I used the "--boot_adb_kernel" option and it fails. And I couldn't get the Logo stuck to let me flash the kernel Does using wsl with usbipd matters?