Unfortunately I haven't come across a document that correlates the ADB/fastboot versions to a specific API release - that really should happen every time they update the SDK (and independent tools release). At least ADB reports a version number (1.0.36 was the latest one I came across) so you have some idea what's going on. Part of the problem (lousy coding IMO) is that fastboot doesn't report a version number when it's run, so without examining the binary there's no way to tell if you're running an out-of-date version. I'm thinking the safest approach now is to just reset the phone for the trade-in without locking it. S automatically sparse files greaterĪnd this is after I completely removed Android Studio and reinstalled it from scratch. Reboot-bootloader reboot device into bootloader Just the same list of fastboot commands, namely:įlashall flash boot, system, vendor and if found,įlash write a file to a flash partitionįormat] format a flash partition.įlash:raw boot ] create bootimage and
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |