![]() Thought I should try "full erase", and I think (but can't recall for sure) flashing started failing even earlier. ![]() Flash FW006 with tool v2.2.0, "Normal erase". When I tried to boot, it came to an Android logo and stayed there for like 30 minutes, and I believe LED was blue. I've even had to try flashing back to even earlier versions of the firmware & then OTA it back up again afterwards, or once an earlier version has successfully flashed, it may then also allow a later FW version to manually flash over that again that otherwise just wouldn't work before.ĭon't ask why!! The U22 has been an absolute headache at times with no updates since release to tie down better procedures for flashing or the reasons why it's such a pig to deal with & the consumer is invariably left to figure it out for themselves through a lot of trial & error.Ĭlick to expand.I don't know if the MCU is/was enabled or not. Try different cables, try different USB ports on your PC, try different versions of the USB burning tool, or try another PC entirely if possible. Otherwise, I've had AWFUL issues trying to flash U22s that have simply defied all normal, routine or even rational reasoning. ![]() Click to expand.So are you saying that the MCU was still actually enabled before you attempted the first manual flash? (Possibly bricking the device in the process!!) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |