Skocz do zawartości
Forum Android | CyanMod

[Nexus 6][Shamu] TWRP 2.8.7.0


PeliKan

Rekomendowane odpowiedzi

Uwaga

Ja, jak i forum nie odpowiadamy za ewentualne uceglenia urządzenia, robisz to na własną odpowiedzialność

 

post-1-0-13059600-1430486584.png

Jest to Custom recovery a dokładniej TWRP recovery, pozawala na instalację nieoficjalnego oprogramowania

 

Lista zmian(Pełna lista zmian dostępna w linku źródłowym):

CHANGELOG for 2.8.7.0:

-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)

Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

 

Bugi:

BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

 

Wsparcie techniczne:

SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

post-1-0-63742800-1430486586.png

post-1-0-93295400-1430486585.png

post-16996-0-67606600-1439136206.png

Tryb tabletu:

post-16996-0-88965900-1439136212.png

post-16996-0-12381900-1439136218.png

 

post-1-0-91240000-1430486584.png

TWRP MANAGER

 

post-1-0-22155400-1430486583.png

  1. Zainstaluj aplikację TWRP MANAGER
  2. Uruchom ją, oraz następnie wybierz Advanced->Install Recovery
  3. Wybierz dokładny model Twojego urządzenia z listy
  4. Flashuj
  5. Gotowe, masz już sflashowane TWRP

 

 

Źródło: http://forum.xda-developers.com/nexus-6/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2946534

Odnośnik do komentarza
Udostępnij na innych stronach

Dołącz do dyskusji

Możesz dodać zawartość już teraz a zarejestrować się później. Jeśli posiadasz już konto, zaloguj się aby dodać zawartość za jego pomocą.

Gość
Dodaj odpowiedź do tematu...

×   Wklejono zawartość z formatowaniem.   Przywróć formatowanie

  Dozwolonych jest tylko 75 emoji.

×   Odnośnik został automatycznie osadzony.   Przywróć wyświetlanie jako odnośnik

×   Przywrócono poprzednią zawartość.   Wyczyść edytor

×   Nie możesz bezpośrednio wkleić grafiki. Dodaj lub załącz grafiki z adresu URL.

×
×
  • Dodaj nową pozycję...

Powiadomienie o plikach cookie

Korzystając ze strony akceptujesz - Warunki użytkowania, Polityka prywatności