Jeżeli masz bootloader 4.1.1, instalujesz wersję dla 4.1.1! Jeżeli masz bootloader 4.2, instalujesz wersję dla 4.2! W innym przypadku twój tablet będzie nieodwracalnie uszkodzony!
NIE PONOSZĘ ŻADNEJ ODPOWIEDZIALNOŚCI ZA EWENTUALNE SZKODY, WYRZĄDZONE TYM OPROGRAMOWANIEM! WSZYSTKO ROBISZ NA WŁASNE RYZYKO!
TWRP 2.4.4.0
Team Win Recovery Project (TWRP) jest publikacją recovery dla Asus Transformer TF300T. Instalując je zyskujesz zupełnie nowe funkcje. Najważniejszą z nich jest instalacja Custom Romów, czy też oficjalnego oprogramowania producenta, po odblokowaniu bootloadera.
Instalacja
Oczywiście przed instalacją jakiegokolwiek recovery, musimy odblokować bootloader 😉
Forum po zmianach, link nie działa
TWRP możemy zainstalować tylko za pomocą Fastboot'a i Terminal Emulatora/ADB (goo manager może trawle uszkodzić twój tablet!). Ja pokaże jak się to robi za pomocą fastboota. Zakładam iż macie zainstalowane na komputerze Android SDK i Java SDK, oraz wiecie jak korzystać z ADB oraz Fastboot.
1) Pobierz plik z recovery, i skopiuj go do folderu z fastboot'em (zazwyczaj platform-tools)
2) Sprawdź czy plik jest ściągnięty prawidłowo, i czy nie uległ korupcji, czyli sprawdź Sumę MD5 ( ten krok można pominąć, jednakże jest to mocno zalecane!)
3) Zmień nazwę ściągniętego pliku na twrp.blob
4) Włącz tablet w trybie fastboot, i podepnij do komputera (gdy tablet jest wyłączony wciskamy kombinację klawiszową Vol- i pwr. Wejdziemy wtedy do bootloader menu, przyciskiem vol- nawigujemy na ikonkę USB a operację potwierdzamy przyciskiem Vol+. Należy to zrobić w czasie krótszym niż 5 sekund, bo inaczej tablet uruchomi się ponownie)
5) Mając uruchomiony fastboot na komputerze i podłączony tablet wpisujemu komendę "fastboot -i 0x0B05 flash recovery twrp.blob"
6) Teraz uruchamiamy ponownie nasz tablet wpisując komendę "fastboot reboot"
Jeżeli macie roota, łatwiejsza metoda instalacji TWRP za pomocą terminal emulatora jest przedstawiona na fajnym polskim filmiku: Forum po zmianach, link nie działa
Download
http://www.teamw.in/project/twrp2/97
Jest również opcja instalacji TWRP 2.4.4.0 na TF300TG, tylko trzeba pobrać pliki dla TF300TG.
Changelog w wersji angielskiej:
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
CHANGELOG for 2.3.3.0:
-Fix renaming backups with a space in the name
-Add decrypt button to mount page if you cancel decryption during startup
-Added ignore blkid flag
-Fixed handling of MTD partitions during mount
-Fixed some keyboard mapping issues on 800x1280 layout
CHANGELOG for 2.3.2.0:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Mając na myśli bootloader JB czy ICS, nie chodziło mi o Cyanogenmod, AOKP czy Paranoid! Chodzi mi o wersję oficjalnego bootloadera! Czyli tego, którego zainstalowaliście wraz z oryginalnym oprogramowaniem!