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.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: https://www.mediafire.com/folder/dtsa7p6v17436/jem
fastboot -i 0x1949 flash recovery jem_recovery_xxxxxxxx.img
restore old recovery:fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
Thanks so much for this! I'll flash it and let you know how it works.
Sent from my Amazon Jem using XDA Labs
I played with this for a little bit, and I'm amazed by this. (the only aesthetic issue I see is that when I boot directly into recovery, I see the classic blue & white Kindle Fire logo before the TWRP bootscreen; I intend to replace it with a more updated TWRP bootloader logo to help make the boot process more enjoyable. )
Sent from my Amazon Jem using XDA Labs
it works, but show an error message in log during boot.
Running boot script...
/sbin/postrecoveryboot.sh process ended with ERROR: 1
gatalon said:
it works, but show an error message in log during boot.
Running boot script...
/sbin/postrecoveryboot.sh process ended with ERROR: 1
Click to expand...
Click to collapse
found error source, it will fix, not serious for work
Worked on the first try, no problems and IT LOOKS GREAT
I did get the error msg but no problems
LOL, now tell me how to get a rom with play and working 5g, I do like the amazon 8.5.1 as it's real fast and great gaming but I would like it all, yup I'm greedy,,,
much thanks I like flashing as much as gaming
sully
Awesome work as always @transi1. Installed no problems, works great so far.
build 160312: http://www.mediafire.com/download/nrd897fvhz8lnq1/jem_recovery_160312.img
rework f2fs
for test f2fs make backup, in "Wipe" twrp menu need try convert data and test boot rom, after convert cache and test new f2fs
transi1 said:
build 160312: http://www.mediafire.com/download/nrd897fvhz8lnq1/jem_recovery_160312.img
rework f2fs
for test f2fs make backup, in "Wipe" twrp menu need try convert data and test boot rom, after convert cache and test new f2fs
Click to expand...
Click to collapse
Is it safe to use f2fs with /system? I'll definitely try it out with data & cache.
monster1612 said:
Is it safe to use f2fs with /system?
Click to expand...
Click to collapse
No, only for cache and data.
But you have no disadvantage. The main benefit is in writing, and you only write once in your system partition, if you flash it....
build (3.0.1) 160403: http://www.mediafire.com/download/vscd5fu92s025c0/jem_recovery_160403.img
transi1 said:
build (3.0.1) 160403: http://www.mediafire.com/download/vscd5fu92s025c0/jem_recovery_160403.img
Click to expand...
Click to collapse
Thanks so much for building this so quickly after the 3.0.1 release! It works like a charm.
Guys is there a flashable zip?
Sent from my E6533 using XDA-Developers mobile app
bustr85 said:
Guys is there a flashable zip?
Click to expand...
Click to collapse
Not currently; however, recent TWRP releases will let you directly flash .img partitions to boot or recovery.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Not currently; however, recent TWRP releases will let you directly flash .img partitions to boot or recovery.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for this, would it work with 2.8.7.0?
Sent from my E6533 using XDA-Developers mobile app
---------- Post added at 04:41 PM ---------- Previous post was at 04:40 PM ----------
monster1612 said:
Not currently; however, recent TWRP releases will let you directly flash .img partitions to boot or recovery.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks, would 2.8.7.0 work to flash the img directly?
Sent from my E6533 using XDA-Developers mobile app
bustr85 said:
Thanks for this, would it work with 2.8.7.0?
Sent from my E6533 using XDA-Developers mobile app
---------- Post added at 04:41 PM ---------- Previous post was at 04:40 PM ----------
Thanks, would 2.8.7.0 work to flash the img directly?
Click to expand...
Click to collapse
Yep, just make sure to choose "Images" in the Install window in TWRP. It's been a feature since TWRP 2.8.4.0.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Yep, just make sure to choose "Images" in the Install window in TWRP. It's been a feature since TWRP 2.8.4.0.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks I really haven't noticed before in the bottom right corner..lol
Sent from my E6533 using XDA-Developers mobile app
I can't get F2FS on /cache to stick past a reboot. I'll be fine, though. I am enjoying the fruits of others' labor, after all.
manchucka said:
I can't get F2FS on /cache to stick past a reboot. I'll be fine, though. I am enjoying the fruits of others' labor, after all.
Click to expand...
Click to collapse
Odd, as it works for me. What TWRP version and ROM build are you using? Older versions of TWRP or 6.x ROMs likely don't have support for f2fs /cache.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Odd, as it works for me. What TWRP version and ROM build are you using? Older versions of TWRP or 6.x ROMs likely don't have support for f2fs /cache.
Clouds make rain
Click to expand...
Click to collapse
3.0.1-0. I can format /cache as f2fs through TWRP. It will stay that way even when I reboot back into TWRP from TWRP. But when I boot thence normally and then back into TWRP, I find /cache is back to ext4. Odd, huh? Again, I'm not worried. At least about f2fs on the /cache partition of this tablet. About other things, though? Very worried.
Related
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.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!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
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 NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
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.
Note, all images have already been loki'd. Just flash away!
AT&T Downloads
Verizon Downloads Special thanks to rhcp for helping test the update for G2 VZW to fix 4.4 rom install.
T-Mobile USA Downloads
Korean F320K Downloads
Sprint Downloads
Bell Canada Downloads
Rogers Canada Downloads
Be sure to thank @djrbliss for his work on loki for the G2. Without loki, recovery and ROMs would not be possible.
SWEET! Thanks!
EDIT: Guess it's not available yet. Can't find it.
Sent from my LG-D801 using Tapatalk 4
You're the MAN! Thank you for all of the hard work Devs! it only gets better from here
it was there a minute ago....
cslingerland said:
You're the MAN! Thank you for all of the hard work Devs! it only gets better from here
it was there a minute ago....
Click to expand...
Click to collapse
You have it? I can't seem to find it.
Sent from my LG-D801 using Tapatalk 4
Once the links go live again, and we install TWRP, does this mean we can flash ROMS now, or do we need to wait for G2-specific development?
Han Solo 1 said:
Once the links go live again, and we install TWRP, does this mean we can flash ROMS now, or do we need to wait for G2-specific development?
Click to expand...
Click to collapse
Once ROMs are available specifically for the G2, you can flash them.
Right now there are none, and flashing something from a different phone WILL cause issues.
chrisexv6 said:
Once ROMs are available specifically for the G2, you can flash them.
Right now there are none, and flashing something from a different phone WILL cause issues.
Click to expand...
Click to collapse
Oh boy. I just want a stock ROM with wifi-hotspot enabled. That’s it.
---------- Post added at 03:23 PM ---------- Previous post was at 03:07 PM ----------
So is this not working yet? When I hit "install OpenRecoveryScript" in GooManager, it says "no recoveries were found for your device".
It hasn't been put on the servers per say.
Sent from my LG-D800 using Tapatalk 4
whats the status on using goomanager to get recovery other then what we already know
I tried updating thru goo manager but it doesn't work. It downloads the new .IMG file but even though it says recovery installed, when I boot to twrp its still version 2.5.*.* any ideas on why this happens? Or how to fix? BTW I'm on a att galaxy s4 (jflteatt)
Sent from my SGH-I337 using XDA Premium 4 mobile app
SeveNVapoR said:
I tried updating thru goo manager but it doesn't work. It downloads the new .IMG file but even though it says recovery installed, when I boot to twrp its still version 2.5.*.* any ideas on why this happens? Or how to fix? BTW I'm on a att galaxy s4 (jflteatt)
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First, try posting in the correct forum for the correct device, this is the LG G2 section.
Second, change the download directory for GooManager from whatever it currently is to /sdcard/goomanager/ and that will fix it.
Your right...it worked
Sent from my SGH-I337 using XDA Premium 4 mobile app
Amazing work devs can't wait for more!
Sent from my LG-F320S using xda app-developers app
Fantastic work, thank you so much. Flashed, backed up, started removing system apps. Time to start working on a Custom Rom. Guess I ought to learn Aroma Installer, haven't made a rom since the the Bionic so I've never messed with it before.
Han Solo 1 said:
Oh boy. I just want a stock ROM with wifi-hotspot enabled. That’s it.
---------- Post added at 03:23 PM ---------- Previous post was at 03:07 PM ----------
So is this not working yet? When I hit "install OpenRecoveryScript" in GooManager, it says "no recoveries were found for your device".
Click to expand...
Click to collapse
I totaly feel you,
The phone itself feels solid except for all the crap bloatwear thats bugging down the ram and storage.
a clean rom with tethering is all this phone needs.
goomanager can't find any recovery for the F320K10m version,
is it possible?
can i hook my phone to PC and run adb and do fastboot flash recovery openrecovery-twrp-2.6.3.0-g2vzw.img ?
exciting stuff, this is great to see
drmp3z said:
can i hook my phone to PC and run adb and do fastboot flash recovery openrecovery-twrp-2.6.3.0-g2vzw.img ?
Click to expand...
Click to collapse
Considering this uses an exploit, almost 100% sure the answer is no.
Hi,
I managed to build latest TWRP for N5100/N5110.
This a test build you can flash from your existing recovery.
Odin packages and flashable ZIPs are now available for n5100 and N5110.
Download:
http://www.androidfilehost.com/?w=files&flid=15631
What's new since 2.6.3.0?
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
NOTE: This is a test version and does NOT support f2fs, but you can switch to other filesystems
What's new in 2.7.0.0:
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keyboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 AOSP decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Changelog:
Build 1:
-First release
Credits:
@sbrissen for original port and maintenance of CM11 for n5100/n5110/n5120.
@Dees_Troy & TEAMWIN for making TWRP
Reserved
i'm waiting for n5110
Is there any chance for a 5120 version, if you don't mind me asking.
Sent from my GT-N5120 using Tapatalk
Thx for your effort. Great to have a updated Recovery. Can this used for all kind of Roms? 4.1.2, 4.2.2 and 4.4.x?
Thank you for planning on including the 5110. I will patiently waiting for the addition of this device.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Build 2 is released.
Now n5100 and n5110 is supported. You can get tar files to flash via Odin or use zip files if you want to flash from your existing recovery (CWM, PhilZ or older versions of TWRP)
User_99 said:
Thx for your effort. Great to have a updated Recovery. Can this used for all kind of Roms? 4.1.2, 4.2.2 and 4.4.x?
Click to expand...
Click to collapse
I only tested with 4.4.x. But it should work with older ROMs too.
Fobz said:
Is there any chance for a 5120 version, if you don't mind me asking.
Sent from my GT-N5120 using Tapatalk
Click to expand...
Click to collapse
For now, I can't provide 5120 support.
whitemolecule said:
I only tested with 4.4.x. But it should work with older ROMs too.
For now, I can't provide 5120 support.
Click to expand...
Click to collapse
No problems!
Sent from my Nexus 4 using Tapatalk
Thanks much for flashable zips.
Works great. I've been waiting a long time for this release. Thank you. You rule.
Sent from my GT-N5110 using XDA Premium HD app
whitemolecule said:
Build 2 is released.
Now n5100 and n5110 is supported. You can get tar files to flash via Odin or use zip files if you want to flash from your existing recovery (CWM, PhilZ or older versions of TWRP)
Click to expand...
Click to collapse
Hello Sir thanks for your great work updating TWRP I been using Philz CWM recovery with no problems im thinking of trying yours which is better Philz CWM or TWRP hate to change since Philz is working let me know thanks
matthewtech770 said:
Hello Sir thanks for your great work updating TWRP I been using Philz CWM recovery with no problems im thinking of trying yours which is better Philz CWM or TWRP hate to change since Philz is working let me know thanks
Click to expand...
Click to collapse
The "better" is the one you choose.
Wow again. Quickly, I want to say, it's nice to get back to TWRP. Been using Philzs and it does a good job but not as smooth and easy as TWRP. The only rom I can't use this with is CivZ's new 4.4.2. It won't allow me to hit the "next" button when installing the rom. All other roms work perfect. This is donation good. Thank you again.
Sent from my GT-N5110 using XDA Premium HD app
Thanks for this. Seems It has problems with Aroma installers. The screen orientation specifically. The screen stays in landscape and only allows the top half of the screen to show the aroma installation, while the touch sensitivity is still in portrait. In other words you have to touch the screen as if it were in portrait and kind of guess where the buttons would be while the actual pictures on the screen are in landscape on only the top half of the screen and very stretched looking. Thanks again for your work.
kstephens98 said:
Thanks for this. Seems It has problems with Aroma installers. The screen orientation specifically. The screen stays in landscape and only allows the top half of the screen to show the aroma installation, while the touch sensitivity is still in portrait. In other words you have to touch the screen as if it were in portrait and kind of guess where the buttons would be while the actual pictures on the screen are in landscape on only the top half of the screen and very stretched looking. Thanks again for your work.
Click to expand...
Click to collapse
And that's why developers that use Aroma (like @civato) specify using Philz's Touch Recovery, which is a modified CWM, to flash their ROM's and kernels.
ramjet73
Nice observation. That is what I figured as well.. I usually have a flashable version of TWRP and Philz touch at the ready. I do a lot of testing with my tablet, with different roms and how apps work and can be modified with each.
Sent from my GT-N5110 using XDA Premium HD app
glockman4519 said:
Nice observation. That is what I figured as well.. I usually have a flashable version of TWRP and Philz touch at the ready. I do a lot of testing with my tablet, with different roms and how apps work and can be modified with each.
Click to expand...
Click to collapse
Yea, I do the same thing.
The easiest way I've found to switch recoveries is to keep "recovery.img" versions of each one on the SD card, then move the files you want to flash to the SD card, use Flashify to install the recovery needed if it's not already there, then reboot into recovery with the advanced power menu. It's still a good idea to keep the .zip version of each recovery on the SD card in case you're already in recovery before you discover that you have the wrong version installed. It would be nice to have USB OTG mount available in this version of TWRP recovery since I can't seem to get USB storage working as there appears to be some conflict with ADB.
I tend to do all my backups with TWRP though since it supports compression and restores have been more reliable for me than using CWM. The backup formats are different so it doesn't make sense to use both.
If the Samsung devices supported "fastboot boot recovery.img" like Nexus, HTC and most other brands it wouldn't be necessary to actually flash an alternate recovery since it could just be booted as needed when the tablet is connected to a computer.
Edit: I just discovered that the "fixed" 2.6.3.0 version of TWRP from this post works fine with Aroma. It doesn't have the USB storage option in mounts (explained in this post) but I can't get that to work with this 2.7.1.0 version anyway. I'd love to use this updated version of TWRP but it would be nice if the Aroma support could be included from the 2.6.3.0 version and an OTG mount option (as opposed to USB storage) could be added.
ramjet73
I was wondering if there would be a possibility of getting this recovery in portrait mode. I am wanting to use a Holofied theme that has more options that can utilize TWRP even better but it does not work with landscape layout. I have already tried to take the Grouper TWRP and used its res folder and added that to the n5110 twrp and repacked the recovery.img and flashed but recovery is still in landscape but is displaying a portrait layout which is unusable.
pimpmaneaton said:
I was wondering if there would be a possibility of getting this recovery in portrait mode. I am wanting to use a Holofied theme that has more options that can utilize TWRP even better but it does not work with landscape layout. I have already tried to take the Grouper TWRP and used its res folder and added that to the n5110 twrp and repacked the recovery.img and flashed but recovery is still in landscape but is displaying a portrait layout which is unusable.
Click to expand...
Click to collapse
Yes, I will try to build in portrait mode when I have time, I think this will also fix aroma installer issues too.
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.
This thread is only for the Kazam Thunder Q4.5
Other devices look elsewhere.
You should be able to root the Thunder Q4.5 using Framaroot barahir. From there you can install the recovery using the instructions on our website. Download links for current and past versions and instructions for install here.
Kernel source is here.
Wow, never thought official TWRP would make it to this device! Can't wait to try it out.
it's a good news,
specially because it support's external keyboards .
mottlagh said:
it's a good news,
specially because it support's external keyboards .
Click to expand...
Click to collapse
Unfortunately the Q4.5 doesn't support USB host mode so it can't be used with an external keyboard.
Great to hear! Thanx!!
Will test it asap!
It can, it supports bluetooth keyboards.
Sent from my ET Persona 10114-B using XDA Free mobile app
mmonaghan34 said:
It can, it supports bluetooth keyboards.
Sent from my ET Persona 10114-B using XDA Free mobile app
Click to expand...
Click to collapse
Bluetooth isn't available in recovery either.
In other news, I pushed the kernel source to github. Link is in the second post. I trimmed about 1.4GB of logos meant for various other models of MTK phones from the original dropbox link that isn't needed or used in the kernel to reduce the upload size. I believe the logo is actually used in the lk bootloader. If I had the source code for the lk bootloader I could probably patch it to allow fastboot mode with working fastboot boot. I've done that on other MTK devices.
To make TWRP fit, I had to lzma both the kernel and the ramdisk instead of gzip. Fortunately we have kernel source for this device so we were able to make TWRP fit and now we have plenty of room for new features too.
Dees_Troy said:
Bluetooth isn't available in recovery either.
In other news, I pushed the kernel source to github. Link is in the second post. I trimmed about 1.4GB of logos meant for various other models of MTK phones from the original dropbox link that isn't needed or used in the kernel to reduce the upload size. I believe the logo is actually used in the lk bootloader. If I had the source code for the lk bootloader I could probably patch it to allow fastboot mode with working fastboot boot. I've done that on other MTK devices.
To make TWRP fit, I had to lzma both the kernel and the ramdisk instead of gzip. Fortunately we have kernel source for this device so we were able to make TWRP fit and now we have plenty of room for new features too.
Click to expand...
Click to collapse
Well, I have the stock rom if that would help, if yes, pm me and I'll send you a dropbox link.
Also subtle hint for a possible update to TWRP: bluetooth support if at all possible, as this would rectify said issue
Sent from my KAZAM Thunder Q45 using XDA Free mobile app
mmonaghan34 said:
Well, I have the stock rom if that would help, if yes, pm me and I'll send you a dropbox link.
Also subtle hint for a possible update to TWRP: bluetooth support if at all possible, as this would rectify said issue
Sent from my KAZAM Thunder Q45 using XDA Free mobile app
Click to expand...
Click to collapse
Bluetooth probably won't ever happen in recovery. Same for Wi-Fi, phone calls, texting, mobile data, and a whole host of other things that belong in the ROM and not in recovery. These things require proprietary files / binaries to work and a lot of the parts that make them work are in the Java / dalvik / ART side of Android. Java / davlik / ART aren't available in recovery. They would take up way too much space.
Recovery is a mini OS designed to help you get your device back in working order, not a full blown firmware.
Dees_Troy said:
Bluetooth probably won't ever happen in recovery. Same for Wi-Fi, phone calls, texting, mobile data, and a whole host of other things that belong in the ROM and not in recovery. These things require proprietary files / binaries to work and a lot of the parts that make them work are in the Java / dalvik / ART side of Android. Java / davlik / ART aren't available in recovery. They would take up way too much space.
Recovery is a mini OS designed to help you get your device back in working order, not a full blown firmware.
Click to expand...
Click to collapse
Well, that's interesting, as far as I was aware, recovery booted inside dalvik, guess i was wrong :/
Well, you said about fixing fastboot, if that were to happen, would it just be a custom kernel to flash? Or would it be a different method of intallatiion?
Sent from my ET Persona 10114-B using XDA Free mobile app
has anyone had success installing this through the app or the dd command? neither of these worked for me, I had to use MTK droid root & tools which worked
matt4321 said:
has anyone had success installing this through the app or the dd command? neither of these worked for me, I had to use MTK droid root & tools which worked
Click to expand...
Click to collapse
Nope, in the app, the thunder_q45 option wasn't even in the list. Not trued dd yet though
Sent from my KAZAM Thunder Q45 using XDA Free mobile app
What this guy's i need software upgrade i been getting hacked
bpair9 said:
What this guy's i need software upgrade i been getting hacked
Click to expand...
Click to collapse
In what way have you been getting 'hacked', because I think you will find that hacking is the art of writing code/optimizing the performance of anything, while cracking is breaking into/hijacking a digital system usually for malicious purposes (what the stupid media calls hacking).
Also, if someone really did have remote access to your device, then a software update wouldn't help.
Sent from my ET Persona 10114-B using XDA Free mobile app
Anyone had any luck installing 2.8.6.0?
I've tried through MTK droid root & tools, as well as through 2.8.5.0 flashing the img to the recovery partition.
It just hangs at the spalsh screen
@Dees_Troy I think 2.8.6.0 is borked on this phone
Reverting to 2.8.5.0 and it boots
So i heard about how @matt4321 was having issues installing the recovery from the app or root shell, do either of these work yet? Or do i just use mtk flash tools to install? or is there a way to temp boot into twrp then use it to install itself? Thanks
Sent from my KAZAM Thunder Q45 using XDA Free mobile app
mmonaghan34 said:
So i heard about how @matt4321 was having issues installing the recovery from the app or root shell, do either of these work yet? Or do i just use mtk flash tools to install? or is there a way to temp boot into twrp then use it to install itself? Thanks
Sent from my KAZAM Thunder Q45 using XDA Free mobile app
Click to expand...
Click to collapse
I've been using mtk droid root and tools.
2.8.6.0 still doesn't work though
matt4321 said:
I've been using mtk droid root and tools.
2.8.6.0 still doesn't work though
Click to expand...
Click to collapse
So, as I'm new to all this custom recovery installation without fastboot, would anyone be able to give me a guide on how to use mtk droid root and tools to install twrp?
Many thanks
Sent from my KAZAM Thunder Q45 using XDA Free mobile app
Dees_Troy said:
Team Win Recovery Project 2.x, or twrp2 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.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
Any chance of v3.0.0 for Q45 ? @Dees_Troy
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:
-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!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
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.
Xiaomi Redmi Note 3
TWRP Downloads
NOTE: If you are flashing TWRP for the first time then you need to first flash modified boot.img from here and then TWRP
XDA:DevDB Information
Recovery for the Xiaomi Redmi Note 3
Contributors
vibhu0009
Source Code: https://github.com/TeamWin
Device Tree: https://github.com/TeamWin/android_device_xiaomi_kenzo
Version Information
Status: Stable
Created 2016-04-06
Last Updated 2016-04-06
Special thanks to @Santhosh M
Could you add chinese language please? Thank you
Can we get TWRP Manager app from Google Play store to reference this TWRP version (kenzo)? Will make it easier to flash and apply updates in future.
Does it need to flash cracked boot.img with this official version?
vlado05 said:
Does it need to flash cracked boot.img with this official version?
Click to expand...
Click to collapse
yes.. if u flashing it for the first time then u gotta flash the modified boot.img and then TWRP
_ossie_ said:
Can we get TWRP Manager app from Google Play store to reference this TWRP version (kenzo)? Will make it easier to flash and apply updates in future.
Click to expand...
Click to collapse
It will be up very soon in TWRP manager
vlado05 said:
Does it need to flash cracked boot.img with this official version?
Click to expand...
Click to collapse
Yes, you still need the modded boot.img for respective version of the rom.
---------- Post added at 01:08 PM ---------- Previous post was at 01:06 PM ----------
_ossie_ said:
Can we get TWRP Manager app from Google Play store to reference this TWRP version (kenzo)? Will make it easier to flash and apply updates in future.
Click to expand...
Click to collapse
Definitely it would be easier, with a unlocked BL though.
Thanks
feds64 said:
Yes, you still need the modded boot.img for respective version of the rom.
Click to expand...
Click to collapse
Sorry for the noob Qs and a bit off-topic but can you flash the modded boot.img with TWRP itself? The only way I have been flashing a modded boot.img is via Fastboot.
(I imagine you'd need to convert the boot.img to a flashable zip but I don't know how to do that.
Also, isn't the modded boot.img the very LAST thing to flash? Because every time I have done it differently I have ended up in bootloop/stuck at Mi logo.
The other way I've been restoring boot is via a TWRP backup (boot only) but this requires it to be previously flashed and backed up.
_ossie_ said:
Sorry for the noob Qs and a bit off-topic but can you flash the modded boot.img with TWRP itself? The only way I have been flashing a modded boot.img is via Fastboot.
(I imagine you'd need to convert the boot.img to a flashable zip but I don't know how to do that.
Also, isn't the modded boot.img the very LAST thing to flash? Because every time I have done it differently I have ended up in bootloop/stuck at Mi logo.
The other way I've been restoring boot is via a TWRP backup (boot only) but this requires it to be previously flashed and backed up.
Click to expand...
Click to collapse
In twrp select option of flash images, and then it will show the image file, select and flash it.
Hey,
I just tried this Recovery & as of now it is not able to flash MIUI zip files! Earlier Chinese recoveries were able to flash full zips at least! [OTA cant be flashed though]
Edit- Threre is some weird error as - Failed to mount '/factory' (Invalid argument)
TheDj408 said:
Hey,
I just tried this Recovery & as of now it is not able to flash MIUI zip files! Earlier Chinese recoveries were able to flash full zips at least! [OTA cant be flashed though]
Edit- Threre is some weird error as - Failed to mount '/factory' (Invalid argument)
Click to expand...
Click to collapse
Doesn't effect anything.. But new build is coming soon with this error fixed..
vibhu0009 said:
Doesn't effect anything.. But new build is coming soon with this error fixed..
Click to expand...
Click to collapse
thanks @vibhu0009 for all your hard work
really appreciate it
oficial twrp fr my rn3
omg
thnkz @vibhu0009
gona try it right awy
I Think you remove
/factory ext4 /dev/block/bootdevice/by-name/factory
_ossie_ said:
Sorry for the noob Qs and a bit off-topic but can you flash the modded boot.img with TWRP itself? The only way I have been flashing a modded boot.img is via Fastboot.
(I imagine you'd need to convert the boot.img to a flashable zip but I don't know how to do that.
Also, isn't the modded boot.img the very LAST thing to flash? Because every time I have done it differently I have ended up in bootloop/stuck at Mi logo.
The other way I've been restoring boot is via a TWRP backup (boot only) but this requires it to be previously flashed and backed up.
Click to expand...
Click to collapse
Alternatively you can, always keep these two files together in you device as you may need it for OTA or etc.
---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------
Thanks for the quick fix...
When is the new build with /factory mount error fix?
DrWillz said:
When is the new build with /factory mount error fix?
Click to expand...
Click to collapse
i gues u did not see the change of name of thread
it was fixd and released 3-4 hours bak by @vibhu0009
take links from frst page
---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------
feds64 said:
Alternatively you can, always keep these two files together in you device as you may need it for OTA or etc.
---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------
Thanks for the quick fix...
Click to expand...
Click to collapse
+1
thanks for the quick fix...
First of all thank you very much for your hard work on twrp. It's really amazing. I suppose that release 3.0.2-1 is not yet finished! I cannot see any link for this version, just 3.0.2-0.
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-2:
-Fix subpartition restore bug (ex: EFS)
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!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
TWRP 3.0.2-2
Can be updated quickly and easily within TWRP if TWRP is already installed
1) Download the latest version from the above link
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
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.
SOURCE/THANKS:
Device tree: https://github.com/TeamRegular/android_device_zte_ailsa_ii
@DrakenFX for testing and requesting my help
@Unjustified Dev for being....ME of course
Prerequisites:
* Unlocked bootloader Guide Here
Installation:
Code:
adb reboot bootloader
fastboot flash recovery twrp-3.0.2-2-a2017u.img
fastboot reboot
To enter recovery:
* Power + volume up
Code:
adb reboot recovery
Installing Mods:
If you plan on modifying the system, please follow this post here or you'll result in a bootloop.
Reserved
Holy **** that is quick. You are a hero.
I picked up the chinese model though, still waiting for bootloader... They confirmed it but they are taking their time.
Hoping the devices are similar enough that this twrp will also work on mine.
aPexalpha said:
Holy **** that is quick. You are a hero.
I picked up the chinese model though, still waiting for bootloader... They confirmed it but they are taking their time.
Hoping the devices are similar enough that this twrp will also work on mine.
Click to expand...
Click to collapse
The base HW should be the same across the world. The only real difference is the Force Touch feature in the Chinese 6GB model, which might necessitate a different touch screen driver.
The Chinese ROM also calls the device the ailsa_ii, just with a different model number.
that's awsome, very nice work. Now the custom ROMs have open doors
In BoardConfig.mk, wouldn't we want "BOARD_HAS_NO_REAL_SDCARD := false" (just leave it out) and "TW_NO_USB_STORAGE := false" (or leave it out)? I'm pretty sure it has OTG support and it definitely has a real SD card.
Thanks for getting the repo up and running as well.
Very good news! Suprised how fast it all went down, cheers! On a side note, is there any chance this or any other method will ever work for EU models? I really like the phone, but waiting for the manufacturer to do something about the software is kind of hopeless.
MeggaMortY said:
Very good news! Suprised how fast it all went down, cheers! On a side note, is there any chance this or any other method will ever work for EU models? I really like the phone, but waiting for the manufacturer to do something about the software is kind of hopeless.
Click to expand...
Click to collapse
It all depends on ZTE Europe releasing a bootloader unlock for the European (Global) version of the phone.
Thank you! Sharing the device tree helps a ton with additional development. Let's see what we can build with this.
TeutonJon78 said:
In BoardConfig.mk, wouldn't we want "BOARD_HAS_NO_REAL_SDCARD := false" (just leave it out) and "TW_NO_USB_STORAGE := false" (or leave it out)? I'm pretty sure it has OTG support and it definitely has a real SD card.
Thanks for getting the repo up and running as well.
Click to expand...
Click to collapse
1st config as I remember is for internal storage. Something about not allowing you to partition it.
2nd config is to remove mass storage support. TWRP supports mtp.
Sent from my 6045I using Tapatalk
Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?
ScaryBugThing said:
Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?
Click to expand...
Click to collapse
Unfortunately I do not know. ZTE blocked the command fastboot boot so we couldn't backup the stock recovery.img we had no choice but to flash it. You can however backup system image in recovery and restore it later. This is the first thing that should be done before flashing root as well as a normal backup. If you restore your system image you can always OTA update through TWRP since it will be an untouched image. I do doubt that you can return to official OEM locked status unless they say it won't void warranty if you unlock it.
Sent from my 6045I using Tapatalk
ScaryBugThing said:
Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?
Click to expand...
Click to collapse
Nope, as far as I know. ZTE has to release the stock factory images. It's extremely difficult to create from a mere backup because it requires ZTE's signature verification.
Sent from my XT1095 using Tapatalk
---------- Post added at 12:16 PM ---------- Previous post was at 12:13 PM ----------
I'm really happy for the TWRP. Thank you man.
Sent from my XT1095 using Tapatalk
When I flash SuperSU 2.76 the phone just turns off, which is kind of strange. Has anyone else had any luck?
Got the same thing when I flash SuperSU
goalkeepr said:
When I flash SuperSU 2.76 the phone just turns off, which is kind of strange. Has anyone else had any luck?
Click to expand...
Click to collapse
allan1229 said:
Got the same thing when I flash SuperSU
Click to expand...
Click to collapse
After you try to install super su and the phone turns off boot back into recovery and
adb pull /cache/recovery/last_log
first time doing this. let me know if its right
http://www.mediafire.com/download/s988ykn9wws5a63/last_log
Unjustified Dev said:
1st config as I remember is for internal storage. Something about not allowing you to partition it.
2nd config is to remove mass storage support. TWRP supports mtp.
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
Ah, that would make sense. I couldn't tell from the TWRP documentation if either one was general. The SD one is about partition, I just didn't know if applied to an external card (not that most people partition one since Windows doesn't allow it anyway). You definitely wouldn't want people partitioning their internal one.
It makes sense to get rid of UMS, as then TWRP couldn't read it while you're connected to the computer. It's unfortunate they names it USB rather than UMS then. Thanks.
Unjustified Dev said:
Prerequisites:
* Unlocked bootloader Guide Here
Installation:
Code:
fastboot flash recovery twrp-3.0.2-0-a2017u.img
fastboot reboot
To enter recovery:
* Power + volume up
Code:
adb reboot recovery
Click to expand...
Click to collapse
I'm confused I connect my phone and go into command prompt and do the first command fastboot flash recovery twrp-3.0.2-0-a2017u.img enter and all I get is waiting on device am I doing something wrong?