lies and silent very good compact adb-driver purely for GN. maybe, in his hat, so that people wouldnвЂ™t cradle all the packs of all-in-one drivers in vain?Naked_Samsung_1.7.zip
On the topic of updating: it was unlocked, received a root, tried to provoke a PTA update for a long time, but did not wait. threw my hands into / caСЃhe fileyakju-icl53f-factory-89fccaac.tgz
however, the recovery only noticed it after renaming toupdate.zip
however, this is obvious, of course.
but failed to update:signature verification failed
- Install / cache ...
Finding update package ...
I: Update location: /tmp/sideload/package.zip
Opening update package ...
I: 2 key (s) loaded from / res / keys
Verifying update package ...
I: verify_file returned 1
E: signature verification failed
in the end, I installed the custom recovery cwm, again stupidly renamed the update in update.zip, but even then a failure hit me: an errorCan't open /sdcard/update.zip (bad)
I stumbled on something. I'll go google.update:
I did not have to go far. here is the manual
- everything worked out. I was for this instruction with xda
started acting but the team adb devices
did not issue the serial number of the device ( list of devices attached
), and this method with fastboot turned out to be on top. to all:
How to understand the tireless reminders of an advanced guy with Google Groups about the need to lock the boot? What kind of danger are we talking about and why leave the "bad idea" open? "Don't forget that after flashing back to a factory state, your
bootloader is still unlocked. Don't forget to lock it back in order to
secure your device ("fastboot oem lock"). " from here
"-However, if you keep your bootloader unlocked at all times
(which is a bad idea) "from herePost has been editedkrasnoff - 22.12.11, 20:02