This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
howto:crystalsky [2020/03/14 17:15] digdat0 formatting |
howto:crystalsky [2020/03/16 21:16] knarfboy update |
||
---|---|---|---|
Line 10: | Line 10: | ||
* V02.06.03.00 (12/ | * V02.06.03.00 (12/ | ||
* v02.06.06.00 (12/ | * v02.06.06.00 (12/ | ||
+ | * v03.00.02.00 (12/ | ||
- | It is reported that if you try to downgrade from v3.0.2.0 it bricks the CS. **Do not upgrade past v02.06.06.00** (12/ | + | It is reported that if you try to downgrade from v3.0.2.0 it bricks the CS. |
Rooting v3.0.2.0 is still possible! Source https:// | Rooting v3.0.2.0 is still possible! Source https:// | ||
+ | The only thing I noticed is that adb drivers on Windows are now not compatible | ||
+ | with v3.0.2.0, because the new image reports a different USB VID/PID codes. | ||
+ | So on Win7/Win10 you won't see attached devices on the USB adb bridge. | ||
+ | Use a Linux virtual machine for that (Virtualbox) and the problem is sovled. | ||