Quote:
Originally Posted by lenlux
... safer/more "wholesome" than flashing partial updates...
|
True, but in this case it was a full update.
Now that Onyx is trying to switch to incremental updates we're seeing people run into trouble.
The minimal pro-active thing people can do is to hold on to the last full update.
You can see from the updater-script what the important things are:
- xbl
- abl
- rpm
- pmic
- boot
- system
- vendor
- persist
Note that (at least on my Poke3) there are lots of empty partitions:
Code:
# Name Size
-- ----------- ------------
7 fsg 2097152
21 dip 1048576
23 apdp 262144
24 msadp 262144
25 dpo 1024
26 splash 34226176
27 limits 4096
28 toolsfv 1048576
29 logfs 8388608
31 sec 16384
33 fsc 1024
36 modemst2 2097152
39 keystore 524288
42 logdump 67108864
43 sti 2097152
45 rawdump 134217728
46 vbmeta 65536
The stock recovery isn't all that useful. It has no ADB and without ADB it's not easy to get to EDL. For me, all I need out of a recovery is rooted, permissive ADB. The flash drive option is still a work-in-progress. I'm trying to work out some minor bugs. Right now I'd like to work with people who are trying it.
The regular Python EDL utility from bkerler works just fine. Still, it makes you download a bunch of Python stuff and all 100 Megs of loaders just to find what you are looking for. For those who want to use a native Windows utility there's one on my website that weighs in at under 0.25 Megs (including loader). Another feature is that you can just load the boot image, not the extra 53,813,248 bytes of zeroes.
Code:
C:\>edl /pboot boot.img /t
...
Requesting header... Ok, receiving... Ok
Android: 25968 / 131072 = 19.8%
Requesting read boot.img... Ok, receiving 100% Ok
C:\>dir boot.img
13,295,616 boot.img
C:\>edl /pboot boot.img
...
C:\>dir boot.img
67,108,864 boot.img