so do i..
feature of TWRP is coolbut i don't understand to use it,
please,, any body can help give me some tutorial to use TWRP??
thanks be4...
TWRP touch recovery device list
- Thread starter Dees_Troy
- Start date
so do i..
feature of TWRP is coolbut i don't understand to use it,
please,, any body can help give me some tutorial to use TWRP??
thanks be4...
so do i..
but i don't understand to use it,
please,, any body can help give me some tutorial to use TWRP??
thanks be4...
There are many posts on xda you can search for to see pecularities for a specific device. But you can start by reading http://teamw.in/twrpfaq
Thank you!
I have one question - in TWRP home screen, what is the middle soft button (between the back and the home buttons)? The middle soft button that looks like a small square?
P.S. Just noticed in the FAQ - http://teamw.in/exFAT states that 64GB or larger exFAT partitions aren't supported - but they are, now, right? (I was able to backup using the latest TWRP to my 64GB card. While I didn't flash from the microSD, I was able to browse it in TWRP)
Pls add Motorola Defy in device list
Pls add Motorola Defy in device list..Quarx has sucessfully ported TWRP 2.5.0.0 to Defy/Defy+.
Pls add Motorola Defy in device list..Quarx has sucessfully ported TWRP 2.5.0.0 to Defy/Defy+.
As long as exfat and fuse works on your device. It's a per device compatibility via kernel fuse modules.
Thanks
Can you help with this question too?
That brings up the console.
I hope this has not been answered already. I could not find the real answer to this from a google search. Will Wipe/Advanced ticking all except OTG-USB wipe the kernel to? I am assuming boot.img contains the kernel etc.
Reason I ask is because there is a kernel cleaning utility floating around the XDA forums and I don't understand the need if we can do a full wipe in TWRP unless it does not touch the Kernel?
I am guessing that if you do a lot of rom updates maybe the kernel could use a cleaning after so many times? The new Rom you flash also flashes a new kernel but just not sure if this is considered a clean install of a new kernel or not since it installs the kernel to boot.img correct?
I see system wipe option but not sure if that really wipes the kernel? All other options make no reference to wiping the kernel in TWRP.
Thanks
Reason I ask is because there is a kernel cleaning utility floating around the XDA forums and I don't understand the need if we can do a full wipe in TWRP unless it does not touch the Kernel?
I am guessing that if you do a lot of rom updates maybe the kernel could use a cleaning after so many times? The new Rom you flash also flashes a new kernel but just not sure if this is considered a clean install of a new kernel or not since it installs the kernel to boot.img correct?
I see system wipe option but not sure if that really wipes the kernel? All other options make no reference to wiping the kernel in TWRP.
Thanks
Last edited:
Is there a possible bug in both Chainfire's latest versions of SuperSu v1.60/V1.65 and TWRP version 2.6.2? I am getting messages now that root permissions are broken. Slider to fix or click no to fix. I get the message anytime I boot into TWRP and do nothing at all except reboot.
I don't know if this bug is from both applications or one or the other? Chainfire's threads claim it to be a bug in TWRP?
Anyone?
I don't know if this bug is from both applications or one or the other? Chainfire's threads claim it to be a bug in TWRP?
Anyone?
Could you possibly fix the issue with init.d injector failing to work under TWRP (latest version for T989) Or provide a way around this please
http://xdaforums.com/showthread.php?p=45688859#post45688859
Injector Log:
Starting Injector v.0.2.14
/tmp/aroma-data/injector/injector.sh: line 382: /tmp/busybox: not found
Using /tmp/aroma-data/busybox as the toolbox for this script
Using configuration file global.conf
Extracting the device boot.img
[[: /dev/block/mmcblk0p8: unknown operand
It was not possible to extract the boot.img from the device!
Moving log file to /sdcard/Injector/injector.log
http://xdaforums.com/showthread.php?p=45688859#post45688859
Injector Log:
Starting Injector v.0.2.14
/tmp/aroma-data/injector/injector.sh: line 382: /tmp/busybox: not found
Using /tmp/aroma-data/busybox as the toolbox for this script
Using configuration file global.conf
Extracting the device boot.img
[[: /dev/block/mmcblk0p8: unknown operand
It was not possible to extract the boot.img from the device!
Moving log file to /sdcard/Injector/injector.log
Last edited:
Could you possibly fix the issue with init.d injector failing to work under TWRP (latest version for T989) Or provide a way around this please
http://xdaforums.com/showthread.php?p=45688859#post45688859
Injector Log:
Starting Injector v.0.2.14
/tmp/aroma-data/injector/injector.sh: line 382: /tmp/busybox: not found
Using /tmp/aroma-data/busybox as the toolbox for this script
Using configuration file global.conf
Extracting the device boot.img
[[: /dev/block/mmcblk0p8: unknown operand
It was not possible to extract the boot.img from the device!
Moving log file to /sdcard/Injector/injector.log
We don't maintain external zips. I would suggest asking who created that script why he's not using busybox out of /sbin/.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
46Team 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.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.
DEVICE SPECIFIC THREADS:
Acer Iconia A500
Amazon Kindle Fire
Asus Transformer TF101
Asus Transformer Infinity TF700T
HP TouchPad
HTC Amaze 4G
HTC Butterfly
HTC Desire HD
HTC Droid Incredible
HTC Droid Incredible 2
HTC EVO 4G
HTC EVO Shift 4G
HTC EVO 3D CDMA
HTC EVO 3D GSM (shooteru)
HTC EVO 4G LTE
HTC Hero CDMA
HTC One S (S3 C2 variant)
HTC One X (evita)
HTC One X International (endeavoru)
HTC Sensation
HTC Thunderbolt
HTC Vivid, Raider, Velocity
LG Optimus Black
LG Optimus G Sprint
Motorola Atrix 4G
Motorola Photon 4G
Nexus 4
Nexus 7
Nexus 10
Nexus S
Nexus S 4G
Samsung Fascinate
Samsung Epic 4G
Samsung Epic 4G Touch
Samsung Galaxy Nexus GSM (maguro)
Samsung Galaxy Nexus Verizon (toro)
Samsung Galaxy Nexus Sprint (toroplus)
Samsung Galaxy Note 10.1
Samsung Galaxy S2 T-Mobile USA (hercules)
Samsung Galaxy S2 AT&T USA (skyrocket)
Samsung Galaxy S3 AT&T USA
Samsung Galaxy S3 Sprint USA
Samsung Galaxy S3 T-Mobile USA
Samsung Galaxy S3 Verizon USA
Samsung Galaxy S3 International i9300
Samsung Galaxy S3 LTE 2GB i9305
Samsung Galaxy Tab 7.7
Samsung Galaxy Wonder i8150
Sony Xperia T3
Pretty much all Samsung phones released before the SGS3 that don't have a Qualcomm SoC in them have a recovery-in-boot setup which means that anytime you install a new ROM or kernel, you get whatever recovery the developer includes in the boot image. I know that Talustus makes a kernel for the i9100 that has both TWRP and CWM in the same kernel so you can try his kernel if you want TWRP on your device.
The vast majority of devices have a separate, bootable recovery partition making it much easier for users to install and keep the recovery of their choice. I've also been working with developers here and there to help ensure that devices with recovery-in-boot are set up in a manner that allows users to install an alternate recovery, but TWRP didn't really break onto the scene until later in the i9100's development cycle making it much less likely that TWRP would get sufficient support from ROM and kernel makers.
