TWRP 3.2.1-0 recovery for Motorola Razr I (SMI/XT890)
I am not resposible for anything that happens, make sure u always have a backup on the external sd and on your pc!
Download links are in the Download section above.
Download the zip file, extract and flash through fastboot or what ever way u like.
Changelog:
Code:
TWRP 3.2.1-0-f2fs
[LIST]
[*] Updated TWRP with upstream changes
[*] Added F2FS support to the kernel
[/LIST]
TWRP 3.2.1-0
[LIST]
[*] Updated TWRP to 3.2.1-0
[/LIST]
TWRP 3.1.1-0
[LIST]
[*] Updated TWRP to 3.1.1-0
[*] Not build with Intel compiler. The UI is fast enough by itself + size reduction.
[/LIST]
TWRP 3.0.2-0
[LIST]
[*] Updated TWRP to 3.0.2-0
[*] Flashable zip available
[/LIST]
TWRP 3.0.1-0
[LIST]
[*] Updated TWRP to 3.0.1-0
[/LIST]
TWRP 3.0.0.0
[LIST]
[*] Updated to 3.0.0.0
[*] OMNI rom 6.0 base
[/LIST]
TWRP 2.8.6.0
[LIST]
[*] Updated to 2.8.6.0
[*] CM12 as Base
[*] Removed "Increased overal performance" update, recoveryimage to big. But most likely u won't notice a thing!
[/LIST]
TWRP 2.8.5.0
[LIST]
[*] Updated to 2.8.5.0
[/LIST]
TWRP 2.8.4.1
[LIST]
[*] Increased overal performance
[/LIST]
TWRP 2.8.4.0
[LIST]
[*] Fixed MTP support
[*] All changes from TeamWin!
[/LIST]
TWRP 2.8.1.0
[LIST]
[*] Fixed partition wipe problem (using 'discard' now instead of 'secdiscard')
[*] All changes from TeamWin!
TWRP 2.8.0.1
[/LIST]
[LIST]
[*] Updated for Android 4.4+
[*] Remove PDS partition backup
[*] Full SELinux support added
[*] UI feels snappier
[*] All changes from TeamWin!
[/LIST]
TWRP 2.6.3
[LIST]
[*]Maybe fixed system format
[*]Proper backup and restore of SELinux contexts (thanks to Tassadar)
[*]Pull in some ROM information for backup name generation
[*]Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
[*]Add 1200x1920 theme (thanks to Tassadar)
[*]A few other fixes and tweaks
[/LIST]
TWRP 2.6.1.1
[LIST]
[*]Fixed the error: 'Assert Failed' problem
[/LIST]
TWRP 2.6.1
[LIST]
[*]Initial SELinux support (not for SMI)
[*]Initial support for f2fs file system formatting (Moto X)
[*]Update SuperSU install for 4.3 ROMs
[*]Fixed a permissions bug on files created during backup
[*]Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
[*]Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
[*]Ignore lost+found folder during backup and size calculations
[*]Various other minor bug fixes and tweaks
[*][B]Fixed slowness of recovery. Fast as hell compared to the old one :D[/B]
[/LIST]
TWRP 2.6
[LIST]
[*]Can encrypt a backup to prevent theft of private data from your backup files
[*]Updated graphics / icon courtesy of shift
[*]Updated exFAT to latest commits
[*]Fixed a problem with Samsung TouchWiz decryption
[*]Update SuperSU binary
[*]Fixed saving of backup partitions list
[*]Fixed saving of last used zip install folder
[*]Fixed backup of datadata on devices that use a separate partition for datadata
[*]Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
[*]Fixed some problems with partitioning a SD card
[*]Various other bug fixes and tweaks
[*]Battery percentage can now be seen and is working correctly for XT890
[/LIST]
Boot problems? U most likely still have the ICS bootloader on the device. But I and @tablord already tackled this issue some time ago:
Download this: https://github.com/HazouPH/smi_patch...e/motoboot.zip
Now:
-reboot in bootloader
- "fastboot oem fb_mode_set"
- "fastboot flash motoboot motoboot"
- "fastboot reboot-bootloader"
- "fastboot oem fb_mode_clear"
Click to expand...
Click to collapse
Credits:
TeamWin
Turl1
Hazou
XDA:DevDB Information
[RECOVERY][SMI] Unofficial TWRP 3.2.1-0, ROM for the Motorola RAZR i
Contributors
Hazou
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 3.2.1-0-f2fs
Stable Release Date: 2018-03-23
Created 2015-07-27
Last Updated 2018-03-23
Nice, i'll give it an try after work.
Edit: Works flawless here. Just flashed Omars Rom over Retail GB JB. Finally the ability to flash multiple Zips in one Process > I missed it.
Thanks for your Work!
Gesendet von meinem XT890 mit Tapatalk 2
Ty so much, im gonna try it in a couple hours
Intel device - Razr i Owner
Hit thanks if i help you or you like my style
Thank you Hazou,
It works on my phone too. :good: I agree, like it more than CWM. Just did a full backup. Backup files look good.
Nice one agreed much better than cwm
Great stuff thanks
Sent from my XT890 using xda premium
Fantastic. Thanks, much prefer team win, been using it on my nexus 7 and it has its advantages
outstanding work, flawless, thanks for sharing
Excellent work (said in the voice of ingress )!
External SDCard = 0 MB with TWRP
I just installed it and I cannot make a backup to my EXTERNAL SDCard. TWRP say that my external SDCard size is 0MB.
If I try to backup with CWM to the same SDCard, it works fine...
Can someone confirm there is a bug about it ?
-----
I solved my issue : i re-downloaded and re-flashed and now it works fine !
Nope, works fine here. Already tried all the important stuff (backup > flash > restore) and got no problems. External SD is recognized.
Gesendet von meinem XT890 mit Tapatalk 2
lebobo said:
I just installed it and I cannot make a backup to my EXTERNAL SDCard. TWRP say that my external SDCard size is 0MB.
If I try to backup with CWM to the same SDCard, it works fine...
Can someone confirm there is a bug about it ?
Click to expand...
Click to collapse
hmm, cant think of anything that can fix your problem at the moment. Sry, maybe a reflash/redownload?
Windows installer to flash TWRP recovery
I made a simple Windows installer to flash TWRP recovery (and to restore stock recovery or CWM Recovery).
This installer is adapted from @mattlgroff CWM installer (thanks for his work : all credits for him !)
I only cleaned the code and adapted it to be used with TWRP.
You can download it here : http://forum.xda-developers.com/showthread.php?p=41479852#post41479852
Thanks a lot for this recovery. I like it way more than CWM.
I packaged it in a flashable ZIP and flashed it through CWM. If anyone is interested in the ZIP, just tell me, I could post it if there is a demand.
Any idea why both recoveries are so sluggish on our otherwise so quickly reacting RAZR i?
Nope, I don't know yet why both Recovery's GUI work slow. I am looking into it, but this far I don't know. The strange thing is that the stock recovery works fast and when I put the graphic file from there in our recovery it is still slow. But maybe we can find something.
Sent from my XT890 using xda app-developers app
Hazou said:
Nope, I don't know yet why both Recovery's GUI work slow. I am looking into it, but this far I don't know. The strange thing is that the stock recovery works fast and when I put the graphic file from there in our recovery it is still slow. But maybe we can find something.
Sent from my XT890 using xda app-developers app
Click to expand...
Click to collapse
If you check with top you can see kworker threads eating a lot of cpu cycles while in recovery (30%). I even tried a different Kernel on the recovery thinking it was a Kernel bug but it is showing the same slow performance. I was unable to find the source of the issue but I would guess it is not the graphics.c / framebuffer configuration ;/
Omar-Avelar said:
If you check with top you can see kworker threads eating a lot of cpu cycles while in recovery (30%). I even tried a different Kernel on the recovery thinking it was a Kernel bug but it is showing the same slow performance. I was unable to find the source of the issue but I would guess it is not the graphics.c / framebuffer configuration ;/
Click to expand...
Click to collapse
Ah oke, I already thought that it couldn't be it. Because that file is just a loader for the driver. Ty for the confirmation. I did read in another post to lock the CPU in high frequency. Could that help?
Sent from my XT890 using xda app-developers app
Hazou said:
Ah oke, I already thought that it couldn't be it. Because that file is just a loader for the driver. Ty for the confirmation. I did read in another post to lock the CPU in high frequency. Could that help?
Sent from my XT890 using xda app-developers app
Click to expand...
Click to collapse
Will not help, it will only make the phone get hotter. In fact the Kernel's CPU governor still exists in recovery so it is better to let it scale down at 600 MHz when CPU usage is low -- and ramp up when needed. Problem is someone/somewhere is still taxing the CPU and making kworker use a lot of cycles -- it could be a bad module or a device causing a bunch of interrumpts, no idea at this point.
But definetly making the CPU processor be stuck at max is not the solution (IMO)
New version online, TWRP 2.6!
Hazou
Hazou said:
New version online, TWRP 2.6!
Hazou
Click to expand...
Click to collapse
Work fine, thank you very much :good:
backup and installation of zip's correctly :highfive:
does the installation of the Rom by Omar Avelar :victory:
Is there a way to make it multi-boot? I'd like to try ubuntu for example
Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
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!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Reserved.
Dees_Troy said:
This has been available for a little while, but now I'm adding an official thread for it here on XDA.
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
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.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
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 30 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!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
Would it work with V28C ?
Thx.
Sent from my LG-P970 using xda premium
florin250 said:
Would it work with V28C ?
Thx.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
i dont think so......
but....we better wait answer from the expert
@OP
wow.....i just dream about this last night and today you give this.....thank you so much....
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Ilko said:
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Click to expand...
Click to collapse
download stuck at 99,99%, why???
edit : downloading without download manager, now it's okay
In ClockworkMod, on Nandroid Backup...(there is no option to save the name as we wish), it defaultly gives a name with date for backup..
So, here in TWRP, is there possibility for giving name for Nandroid Backup ?
And what are the bugs remaining after 2.3.1.0 update ?
Had anyone brick phone or bootloop history with this ?
sekhar13515 said:
In ClockworkMod, on Nandroid Backup...(there is no option to save the name as we wish), it defaultly gives a name with date for backup..
So, here in TWRP, is there possibility for giving name for Nandroid Backup ?
And what are the bugs remaining after 2.3.1.0 update ?
Had anyone brick phone or bootloop history with this ?
Click to expand...
Click to collapse
The old TWRP recoveries never completely worked for OB.Sometimes it was the SD mounting, sometimes you couldn't restore the backup done with the same TWRP version and so on.I will try this because I like TWRP more than CWM but it's the last time if it won't work.
---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------
Ilko said:
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Click to expand...
Click to collapse
No, it's not but it's 2.3.20(not yet for OB of course).
USB storage not mounting.
Back to the "bomb proof" cwm 5.8.1.3 touch.
great share!Very good job, thank you.
there is a new version 2.3.1.1
timvdhoorn said:
there is a new version 2.3.1.1
Click to expand...
Click to collapse
ilko already said it here http://forum.xda-developers.com/showpost.php?p=34469364&postcount=6 and there is a newer version but it haven't been built to our device yet.
Updated!
Dees_Troy said:
Updated!
Click to expand...
Click to collapse
SDcard mounting as mass storage still not working, please check.
I was writing the same report : )
well, too bad. I like it but it's useless to me since I transfer files very often through recovery. I can't compile a flasher with that
Indeed I prefer twrp rather than cwm.
Dees, what you need to solve the SD card?
Enviado desde mi LG-P970 usando Tapatalk
Every new version always the same problem.
re4lsk said:
Indeed I prefer twrp rather than cwm.
Dees, what you need to solve the SD card?
Enviado desde mi LG-P970 usando Tapatalk
Click to expand...
Click to collapse
I need to know the proper path for the lun file. By default it's in /sys/devices/platform/usb_mass_storage/lun0/file
You'll have to look for it in TWRP, not in Android though if you find it in Android then I can try switching kernels... I'd need a copy of your current kernel or boot image to switch.
A lot of newer devices don't support USB storage mode anymore at all, so bear that in mind when you're getting ready to upgrade to a new device. You'll have to get used to using ADB to push files or use ADB sideload mode.
Dees_Troy said:
I need to know the proper path for the lun file. By default it's in /sys/devices/platform/usb_mass_storage/lun0/file
You'll have to look for it in TWRP, not in Android though if you find it in Android then I can try switching kernels... I'd need a copy of your current kernel or boot image to switch.
A lot of newer devices don't support USB storage mode anymore at all, so bear that in mind when you're getting ready to upgrade to a new device. You'll have to get used to using ADB to push files or use ADB sideload mode.
Click to expand...
Click to collapse
well the black is an old device(2011) so usb storage still works, you need zImage or boot.img to get the kernel? i can point you to the CM kernel source, i'll see if my old linux VM still works to get you the zImage. but in the mean time i'll upload you the boot.img from cm10 from 20-12-2012 nightly.
CM kernel source
re4lsk said:
well the black is an old device(2011) so usb storage still works, you need zImage or boot.img to get the kernel? i can point you to the CM kernel source, i'll see if my old linux VM still works to get you the zImage. but in the mean time i'll upload you the boot.img from cm10 from 20-12-2012 nightly.
CM kernel source
Click to expand...
Click to collapse
It's not that I need a kernel as much as I need the proper path to the lun file for whatever kernel I happen to be using. Since I don't have an Optimus Black I can't boot it up and look for it myself.
- - - - - -
TWRP
- Team Win Recovery Project -
Attention:
You can find the updated TWRP recoveries by @DJNoXD in his thread here!
Remember that you can donate to TWRP here: http://www.teamw.in/project/twrp2
This thread is deprecated.
Old content:
I have been asked to create an own thread for the TWRP recovery I compiled for the new bootloader, so here you go.
Personally I prefer TWRP over CWM, but that's for everybody to choose on their own.
We got official TWRP support for the Optimus 2x - but only for the old bootloader. You can use the GooManager app to flash the recovery (see below).
I adapted and compiled TWRP for the new bootloader and tested it for quite a while without a single problem.
Additionally I added a flashable zip recovery installer for the old bootloader if someone prefers that over the use of GooManager.
TWRP is NOT my work, but the work from TeamWin under the lead of Dees_Troy.
If you like TWRP you can donate to TeamWin here: http://www.teamw.in/project/twrp2
Bugs?:
If you have any issues grab a log, it's really easy: Advanced -> Copy Log to SD. It will copy the log to your external sdcard.
You can post it in here, then I'll review it and forward it to Dees_Troy if it contains an error.
Or contact TWRP directly via their contact form: http://www.teamw.in/contact
I'm not interested in any complaints or bug reports that do not contain a log! Seriously, just don't.
Remember: I'm compiling this for my personal use and am sharing it with you. I don't care if you use it or not, you're free to use CWM or whatever other recovery is out there.
Download:
http://tonyp.basketbuild.com/index.php?dir=main/P990-stuff/TWRP/
mirror: http://goo.im/devs/tonyp/P990-stuff/TWRP
http://tonyp.hopto.org/?dir=P990/TWRP (I'm only updating this if there's a goo.im outage)
Installation:
These files are flashable zips, just flash them with your current recovery.
If you want to flash the recovery manually, extract the img files from the zips, push it to the SDCard, open the Terminal Emularot and type:
old bootloader:
Code:
su
dd if=/sdcard/openrecovery-twrp-oldbl-p990.img of=/dev/block/mmcblk0p7
new bootloader:
Code:
su
dd if=/sdcard/recovery-TWRP-newbl.img of=/dev/block/mmcblk0p8
Dees_Troy said:
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
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!
DOWNLOAD:
The fastest and easiest way to install TWRP [tonyp note: for the old bootloader version!] is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
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!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
TWRP does support a great theme engine, see here: http://www.teamw.in/project/twrp2themers
If you know of nice themes for our HDPI (480x800) device or created your own please post them here
Personally I'd love to get the Holo Theme by thecoby xdhpi theme to get ported to our hdpi device:
http://forum.xda-developers.com/showthread.php?t=1942309
I don't have time to do that at the moment, so I'm posting it here if someone is interested in doing it.
If not I'll do it once I find the time.
Thanks to aldyu we do have the Holo Dark Theme now fully functional for our device!
Check out his post here and don't forget to press thanks!
Installation:
Download the theme, rename it to ui.zip, create the folder /TWRP/theme at the internal SDCard and put the zip into it.
Preview:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
reserved
Great! i tried twrp when you posted in thread cm10 pa, has more options than cwm, but has bugs in other roms???
[480x800] TWRP Holo Theme - Light / Dark
Thanks for the awesome recovery port!
The button between home and back broke the recovery (or was it the theme?). After I pressed the button and pulled the battery the TWRP screen kept on flashing and never entered the recovery (or let me boot the phone). I had to NVFlash to get my device back. Flashed it again same problem. Deleted TWRP folder, now it works flawlessly.
TWRP Theme - Holo Light
kukharski said:
[480x800] TWRP Holo Theme - Light / Dark
Click to expand...
Click to collapse
Thanks, didn't see it. Although it's not finished yet according to the posts in the thread it does look nice
C0D3N1N3R said:
Thanks for the awesome recovery port!
The button between home and back broke the recovery (or was it the theme?). After I pressed the button and pulled the battery the TWRP screen kept on flashing and never entered the recovery (or let me boot the phone). I had to NVFlash to get my device back. Flashed it again same problem. Deleted TWRP folder, now it works flawlessly.
TWRP Theme - Holo Light
Click to expand...
Click to collapse
Eh, certainly not TWRP's fault. Maybe the themes. Or no idea what you did
The button is for displaying the recovery log, pressing it again will remove the log again.
I've been using this quite often when I was testing every aspect of the recovery to ensure it's safe.
I tried pressing it again but the log didn't disappear. Flashed it again and not it works!
Oh and the time is not correct
you have to set the time manually in settings?!
btw tony thanks a lot - really appreciate your work! i waited so long for TWRP on new bootloader! everything works great so far! you are such a huge WIN for all p990 owners!
THANKS
oh wow, this is very nice, better as CWM Touch recovery 6x.x.x i think.
AW: [RECOVERY] [new|old bl] TWRP 2.3.3.0 touch recovery [2013-01-19]
Why can' t I see the batterystatus?
Gesendet von meinem LGP990 mit CM10.
Thanks tonyp
Re: [RECOVERY] [new|old bl] TWRP 2.3.3.0 touch recovery [2013-01-19]
Unbeliveable! Thx Tonyp!!!
I updated my TWRP to 2.4, please update it!
http://goo.im/devs/tonyp/P990-stuff/TWRP
More details later, gtg now.
Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]
I'm sorry for the noob questions but i have lots of backups from CWM, does those backups work on TWRP?
Really interested in using this recovery (no more button mashing) and the possibility to rename the backups is awesome.
Thank you very much Tony!!
Sent from my LG-P990 using xda app-developers app
I.m.Tuga said:
I'm sorry for the noob questions but i have lots of backups from CWM, does those backups work on TWRP?
Really interested in using this recovery (no more button mashing) and the possibility to rename the backups is awesome.
Thank you very much Tony!!
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
No, you can not use it.
The best option was i missed in CWM is flash in Batch-Mode. But the clock and the battery status are a funny gimmick. Nice but not important.
Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]
Okay, as promised another post about the new twrp version.
The v3.3.0.0 version for the new bootloader has unfortunately been compiled exactly at the time pengus kernel source had the rare ext4 race bug.
So I'd recommend everyone on the new bootloader to update to the new version asap.
If you think you got errors then just do a backup, format /system, /data and /cache, then restore. Most people, including me, shouldn't be affected though.
The new kernel should be absolutely stable, it's based on Kowalski kernel 011p4 (which is like p3 but with the shutdown bug fuxed). This one is completely stable again. (remember, even cwm is using the cm kenel which I'd consider less stable than pengus one).
I had planned to update TWRP during this weekend anyways as twrp 2.4.0.0 got released.
Now cm10.1 users can safely use twrp as well!
Lol, while heading to the twrp website I noticed it got a new update today.
So expect a twrp 2.4.1.0 release tomorrow
What's new in 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
Sent from my LG-P990 using xda app-developers app
Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]
Did try twrp, made a backup with it and tried to restore from that backup but the backup folder was empty, am i missing something...
Sent from my LG-P990 using xda app-developers app
Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]
I.m.Tuga said:
Did try twrp, made a backup with it and tried to restore from that backup but the backup folder was empty, am i missing something...
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I did plenty of backups with twrp, always worked like a charm.
In twrp you can choose the backups location (internal or external sdcard).
So check if it's on the other partition.
Speaking about TWRP.
Please read my update in the twrp thread.
You can wait till tomorrow with updating twrp though, I will push version 2.4.1.0 tomorrow.
Sent from my LG-P990 using xda app-developers app
Okay, about version 2.4.1.0:
My self-built newbl build had already been at version 2.4.1.0
I was in a little hurry and confused myself with the 2.4.0.0 version for the oldbl lol :cyclops:
Now the official build reached 2.4.1.0 as well: http://teamw.in/project/twrp2/65
I downloaded it and zipped it into a flashable zip again, download at the OP.
To avoid confusion I uploaded "recovery-TWRP-2.4.1.0-newbl-20130201.zip" file as well - but it's exactly the same recovery as the previous one.
If you downloaded the "recovery-TWRP-2.4-newbl-20130201.zip" file you already got the newest version and don't have to reflash it it.
2.4.0.0 and 2.4.1.0 changelog:
What's new in 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)
What's new in 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
Click to expand...
Click to collapse
2.4.0.0 is a big update. If you want to read more details about the meaning of the above lines in the changelog I'd suggest to read the following post which explains them in more details:
http://rootzwiki.com/news/_/article...dated-to-240-big-changes-under-the-hood-r1360
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
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!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
More information:
What is the FOTAKernel partition?
The FOTAKernel partition is used by Sony to do FOTA updates. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Very nice and great to see more ot this on our devices.
I will link to the all in one thread when i get home.
Re: [RECOVERY] TWRP 2.3.3.0 touch recovery [2012-01-24]
Awesome news! Official support
Sent from my LT30p using xda premium
Updated!
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]
Looks Awesome,I will check it with my Phone
Sent from my Micromax Canvas 3
No recovery found for my Xperia T
question?
Hy works that too on [ROM 4.1.2 - 4.2.1] JELLYBAM - v4.1.0 [17/01] [Mint] [PA.AOKP.CM10] ?
deltomi said:
No recovery found for my Xperia T
Click to expand...
Click to collapse
Same for me
No recovery for my Xperia TX. Please, Dees_Troy, do it for TX community! Thanks!
AW: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]
you got to have a rom and kernel with external recovery support. I have pa installed and it works flawlessly
Sent from my Paranoid Nexus T using xda premium
can you give me a link with this kernel.or is this the fota kernel?
AW: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]
Dante187 said:
can you give me a link with this kernel.or is this the fota kernel?
Click to expand...
Click to collapse
I'm running the fxp kernel that came with paranoid android. They added external recovery support with fxp204 so when you are running a rom that is based on a older release or on stock it won't work at all
Sent from my Paranoid Nexus T using xda premium
dtekkt said:
I'm running the fxp kernel that came with paranoid android. They added external recovery support with fxp204 so when you are running a rom that is based on a older release or on stock it won't work at all
Sent from my Paranoid Nexus T using xda premium
Click to expand...
Click to collapse
First thx.i have now many cm kernels flash who support open recovery then at works fine but the prob is on all other kernels work my wifi not more.i think at exist not open recovery kernel for [ROM 4.1.2 - 4.2.1] JELLYBAM - v4.1.0 [17/01] [Mint] [PA.AOKP.CM10].the original boot.img for this rom support no open recovery.
AW: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]
Dante187 said:
First thx.i have now many cm kernels flash who support open recovery then at works fine but the prob is on all other kernels work my wifi not more.i think at exist not open recovery kernel for [ROM 4.1.2 - 4.2.1] JELLYBAM - v4.1.0 [17/01] [Mint] [PA.AOKP.CM10].the original boot.img for this rom support no open recovery.
Click to expand...
Click to collapse
yes I think the rom needs to be updated. I heard of that before, you could try to wipe system and so on (maybe full wipe) after you installed the kernel, maybe that works for your wifi problem. However I prefer paranoid android
Sent from my Paranoid Nexus T using xda premium
Dees_Troy said:
More information:
What is the FOTAKernel partition?
The FOTAKernel partition is used by Sony to do FOTA updates. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Click to expand...
Click to collapse
I hava make it to works on TX.BTW,how to use the FOTAkernel partition?
petalex99 said:
No recovery for my Xperia TX. Please, Dees_Troy, do it for TX community! Thanks!
Click to expand...
Click to collapse
I don't have a TX so someone with a TX would have to stop by our IRC channel and offer to test.
dtekkt said:
yes I think the rom needs to be updated. I heard of that before, you could try to wipe system and so on (maybe full wipe) after you installed the kernel, maybe that works for your wifi problem. However I prefer paranoid android
Sent from my Paranoid Nexus T using xda premium
Click to expand...
Click to collapse
Oftentimes the wifi drivers are stored in /system so swapping kernels around without updating the wifi drivers can cause problems with wifi.
sj8023ld said:
I hava make it to works on TX.BTW,how to use the FOTAkernel partition?
Click to expand...
Click to collapse
There's instructions on our website for flashing the FOTAKernel partition or just use GooManager app to install it automatically. There's also a stock kernel that's been repacked with TWRP that will use the FOTAKernel partition available on our website. Kernel devs can use that as a template for packing the ramdisk in a way that will use the FOTAKernel partition so that they can enable the same functionality as seen in CM and PA, etc.
Deleted.
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]
And how would one go about updating WiFi drivers to make sure it works after swapping kernels?
Sent from my Xperia T using xda app-developers app
billysimon99 said:
And how would one go about updating WiFi drivers to make sure it works after swapping kernels?
Sent from my Xperia T using xda app-developers app
Click to expand...
Click to collapse
Best solution is to use the zip that installs the kernel again as the zips usually contain the drivers. Other than that, backup and restore system with the kernel.
Hey there! It has been a while..
You may have noticed Team Win Recovery Project (short: TWRP) is available, but still not for our device,
and it seems I am the only one who spends time on making TWRP fully compatible
for our device which includes some bug fixes and modifications.
Both, TWRP and the kernel were compiled on my pc, using OS X Yosemite (10.10) as host system
from CM sources.
Use at your own risk.
I am not responsible for any damages on your device.
Click to expand...
Click to collapse
What is TWRP?
A fully touch driven custom recovery developed by TeamWin with a nice and easy to use user interface.
You can install your ROM's, backup it or restore it from/on your internal or external storage.
Backups can be compressed which saves alot of storage space and backups can have an individual,
user chosen name. Some unique features are an integrated filemanager, shell access,
rooting and the option to set a display timeout and display brightness.
TWRP includes alot of more features that I listed.. just explore yourself.
Download (also check the #Download page):
recovery263.img => TWRP 2.6.3.0 (STABLE)
recovery283_1.img => TWRP 2.8.3.0 (BETA)
For developers and for GPL reasons:
gkernel_x3_defconfig.zip => Used kernel defconfig (no kernel sourcecode changes have been made except mac os x specific kernel building fixes)
Sources (using cm10.2 sourcecode with cm p880 kernel):
p880_device: https://bitbucket.org/supergordon/device_lge_p880
p880_recovery_twrp: https://bitbucket.org/supergordon/twrp_lge_p880
p880_kernel: https://github.com/CyanogenMod/lge-kernel-p880
How do I install TWRP on my unlocked device?
Option 1: Fastboot
Code:
adb reboot oem-unlock
fastboot flash recovery recovery263.img
fastboot reboot
Option 2: ADB (put first the recovery image to the root directory of your internal storage)
Code:
adb shell
su
cat /sdcard/recovery263.img > /dev/block/mmcblk0p1
What device specific changes have been made?
Reboot options now properly working
Use CM's device specific fix to blank the display
Add missing external storage display name
Add missing screen brightness path
Modified display dimming delay
Fix rendering bugs that caused high battery consumption and device heat-ups
Add proper handling of the quadcore. Reduces backup time by about 10%.
UMS support (external storage only)
Since 2.6.3.0:
Using cm10.2 source
Using cm kernel
Exclude wiping sd-ext (bugfix for 2.6.1.0)
Since 2.8.3.0:
Now using twrp.fstab
Remove UMS support (TWRP has now MTP support. both internal and external storage are shown on the PC)
Add data/media[/0] button in Advanced page. Pressing the button toggles between /data/media and /data/media/0
Added missing option to (not) backup/restore recovery partition.
SD-Ext support (secondary partition of your microsd has to be ext4 formatted)
Using twrp sources from 30 december 2014
Click to expand...
Click to collapse
For changelogs on TWRP itself visit http://www.teamw.in/project/twrp2
My submitted patches on TeamWin's gerrit:
http://review.teamw.in/606
http://review.teamw.in/607
[July 1st] --> Both patches have been now reviewed and merged into the official TWRP sources.
Please report any bugs to help improving TWRP on our device.
Bug reports can be submitted here.
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the LG Optimus 4X HD
Contributors
gordon0001
Version Information
Status: No Longer Updated
Current Stable Version: 2.6.3.0
Stable Release Date: 2013-09-12
Current Beta Version: 2.8.3.0
Beta Release Date: 2014-12-31
Created 2013-09-17
Last Updated 2015-01-16
Reserved
Finally!!!...Thanks..Thanks..Thanks..
I follow you and your work and i hope that soon you release a gbootmenu 0.2 with twrp 2.5...
Or via terminale put the recovery.img in your sdcard and write:
1) su and agree superuser request
2) flash_image recovery /sdcard/recovery.img
Sent from my Wildfire S using xda app-developers app
gave thanks as appreciation =)
Sent from my LG-P880 using Tapatalk 4 Beta
Thanks awesome! i really like twrp much more than cwm.
Is it possible that Fix Permissions is not working? it takes about a second to finish, with cwm it was 5 to 10 minutes.
Thanks!
Fastboot mode :
cannot load 'recovery.img': No error
Why?
Thx
saenta said:
Thanks awesome! i really like twrp much more than cwm.
Is it possible that Fix Permissions is not working? it takes about a second to finish, with cwm it was 5 to 10 minutes.
Thanks!
Click to expand...
Click to collapse
no, thats fine. twrp uses its own way to fix permissions.
Gesendet von meinem LG-P880 mit Tapatalk 2
@tiflao
Recovery.img is not in your fastboot directory. I'm 100 percent sure
Sent from my LG-P880 using xda app-developers app
tiflao said:
Fastboot mode :
cannot load 'recovery.img': No error
Why?
Thx
Click to expand...
Click to collapse
be sure you change to the directory where you stored recovery.img at your terminal(linux, osx)/command prompt(windows) with the "cd" command.
Thx guys
@gordon0001:
How is the development of the next version of GBootmenu going on? I am really looking forward to see TWRP 2.5.0.0 and CWM 6.0.3.1 in just one menu.
Thanks for TWRP 2.5.0.0! Good work!
Thanks gordon0001. Will make flashing and everything else a lot easier. Installed using the All in one P880 kit.
Have a good weekend!
tool_king said:
@gordon0001:
How is the development of the next version of GBootmenu going on? I am really looking forward to see TWRP 2.5.0.0 and CWM 6.0.3.1 in just one menu.
Thanks for TWRP 2.5.0.0! Good work!
Click to expand...
Click to collapse
Hey!
Nice to see you like my work, but this thread is about TWRP and not GBootMenu. Post your questions about my other work in the correspondending release thread.
gordonbennet said:
Thanks gordon0001. Will make flashing and everything else a lot easier. Installed using the All in one P880 kit.
Have a good weekend!
Click to expand...
Click to collapse
Thank you!
The all in one kit installs an outdated, dangerous to use, version of TWRP.
Please install the new, updated version of TWRP or your hardware could be damaged.
Instructions can be found in the first post #1.
gordon0001 said:
Thank you!
The all in one kit installs an outdated, dangerous to use, version of TWRP.
Please install the new, updated version of TWRP or your hardware could be damaged.
Instructions can be found in the first post #1.
Click to expand...
Click to collapse
I forgot to add that I replaced the old one with your one in the toolkit's data files (just renamed the v2.5 to whatever the toolkit was using and deleted the old one).
Thanks for the concern though. Currently loving archived backups
TWRP is damn good! more functions, faster backup/restore etc., thanks!
Thanks for your work .. I love the recovery so much .. Thumbs up
Loving the touch,everything works as it should
updated to 2.6.0.0. see first post
the patches i submitted were reviewed, verified and merged into the official twrp sources. meaning with twrp 2.6.0.0 every device profit from it
http://review.teamw.in/606
http://review.teamw.in/607
Click to expand...
Click to collapse
gordon0001 said:
updated to 2.6.0.0. see first post
the patches i submitted were reviewed, verified and merged into the official twrp sources. meaning with twrp 2.6.0.0 every device profit from it
Click to expand...
Click to collapse
works perfect here
Sent from my LG-P880 using xda app-developers app
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
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!
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
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!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY] TWRP 2.6.0.0 [2013-07-08], a Tool/Utility for the Sony Xperia Tablet Z
Contributors
Dees_Troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.6.0.0
Stable Release Date: 2013-07-08
Created 2013-08-20
Last Updated 2013-08-20
Reserved
The images are built using pollux_windy compatible kernels, but if you're using the FOTAKernel setup, it will work with either model. If someone wants to come by #twrp and test builds for regular pollux I'll be happy to try to add support for that model as well.
pls add the information that its for pollux_windy only!
Followed the instruction but " no recoveries were found "
And if you put "for pollux ONLY" on the title that would be great
Sent from my SGP311 using xda app-developers app
I'm at a loss right now. I get up to the point where it's time to connect my tablet to the computer and when I press the volume up button it just flashes this blank screen until I give up. Also my computer doesn't recognize the device being plugged in when I reach this step. Both my mac and Windows computers. I'm at the point where I wanna either return it or pay someone to get twrp on it. I can't stand this Sony skin... I NEED CM 10!
XDA Moderation is contacting OP to clarify the TWRP is for a specific device version.
Thank You.
MD
Moscow Desire said:
XDA Moderation is contacting OP to clarify the TWRP is for a specific device version.
Thank You.
MD
Click to expand...
Click to collapse
AFAIK recovery is bundled within the boot image for Pollux* so we need to know also which kernel is bundled or if they support a multi loader (little kernel or whatever)
Inviato dal mio SGP311 usando Tapatalk 4
I'm just as lost. I'm trying to find a custom recovery for the "POLLUX" and not the "WINDY"
If it's of any use, I'll repeat here what I've already posted in a duplicate TWRP thread in this forum:
If you go to the Team Win website (use the link in the OP), then click on "get TWRP for my device" only the Pollux_windy (wifi only) version is shown.
Again, on the Team Win website, looking at the install instructions for TWRP on the Tablet Z Pollux_Windy, it's not straight forward which makes me think it can't be done using goo. Have a look here : http://www.teamw.in/project/twrp2/185
Very confusing.
is anyone using this recovery? feedback please. thanks
----------------
This was mentioned in the TWRP page
Code:
If you happen to be using lk, then boot your device into lk's fastboot mode and flash using this command:
fastboot flash recovery fotakernel.img
how do I know I'm using "lk"? thanks again
mrjayviper said:
how do I know I'm using "lk"? thanks again
Click to expand...
Click to collapse
If you don't know then you probably aren't using it. LK is a 3rd party bootloader ported to the TabZ
.........
can we fastboot flash this image file ?
golfinggino said:
can we fastboot flash this image file ?
Click to expand...
Click to collapse
No - Sony use a combined kernel/recovery so just flashing the TWRP imgage will not work.
You first have to go through the process of installing the "LK kernel". This effectively splits-out the kernel and recovery.
You can then "fastboot flash boot" the boot.img for whichever custom ROM you have, and then also "fastboot flash recovery" the TWRP recovery image.
See this thread : http://forum.xda-developers.com/showthread.php?t=2333826 , specifically posts #1,2,3,20,39,60,61.
I've done it and I've now got TWRP with my PAC ROM. The process was quite easy - but just watch the timings of when you press the volume buttons. Also, when the tablet goes into LK fastboot mode the LED is red. Bit of a bad choice of colour as it has caused some people to think their tablet has died.
to install TWRP on my stock and unlocked bootloader, I just used the adb commands mentioned in the TWRP site.
mrjayviper said:
to install TWRP on my stock and unlocked bootloader, I just used the adb commands mentioned in the TWRP site.
Click to expand...
Click to collapse
Maybe you have a link to the commands. I cant find it
egosapienz said:
Maybe you have a link to the commands. I cant find it
Click to expand...
Click to collapse
Half way down this page : http://www.teamw.in/project/twrp2/185
Try it out. Maybe I did something wrong but it didn't work for me - maybe it only works on stock ROM.
I had to install LK kernel to get TWRP with PAC ROM - see my post above
GretaLewd said:
Half way down this page : http://www.teamw.in/project/twrp2/185
Try it out. Maybe I did something wrong but it didn't work for me - maybe it only works on stock ROM.
I had to install LK kernel to get TWRP with PAC ROM - see my post above
Click to expand...
Click to collapse
Not shure if I should do it. Its for the WIFI-only Tab. My bootloader is locked too. But anyway thanx for the link
egosapienz said:
Not shure if I should do it. Its for the WIFI-only Tab. My bootloader is locked too. But anyway thanx for the link
Click to expand...
Click to collapse
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
------
I wouldn't do it if yours is the polux. it clearly says wifi only and there seems to be no TWRP for the LTE version.
mrjayviper said:
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
------
I wouldn't do it if yours is the polux. it clearly says wifi only and there seems to be no TWRP for the LTE version.
Click to expand...
Click to collapse
You´re right. I´ll wait. Thanx