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.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.
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.
Device specific page on our website with manual install instructions.
Download links for all current and past versions.
There's no lg g watch r (lenox) available in twrp app. I have latest version of the app. What's wrong?
Sent from HTC One M8 running Viper One
Vi553r said:
There's no lg g watch r (lenox) available in twrp app. I have latest version of the app. What's wrong?
Sent from HTC One M8 running Viper One
Click to expand...
Click to collapse
You will not be able to use the app to flash this because of the way fast boot works. Unless they make a custom watch app to dd flash it.
Sent from my A0001 using XDA Free mobile app
first things first, kudos to tonu42 for posting the unofficial twrp back in december.
sadly, the 2.8.3.0 build somehow screwed up adb for me - but now with the official 2.8.4.0 and that "powerbutton to go back" functionality...just swell
eeermm....I just flashed the twrp recovery and now when I restart, it always goes into recovery. I can't seem to get to boot.
is this normal?
b0gd4n said:
eeermm....I just flashed the twrp recovery and now when I restart, it always goes into recovery. I can't seem to get to boot.
is this normal?
Click to expand...
Click to collapse
No it isn't normal. I flashed yesterday and haven't experienced this problem, you did flash recovery right? How are you trying to reboot btw?
TimmyUK said:
No it isn't normal. I flashed yesterday and haven't experienced this problem, you did flash recovery right? How are you trying to reboot btw?
Click to expand...
Click to collapse
yeah, so I booted in fastboot and did fastboot flash recovery open....zip
twrp works nice, but when I choose reboot system it starts recovery again.
I am also getting mounting errors (unable to mount data and storage).
EDIT: also, in twrp the Internal Storage is appearing as 0MB
b0gd4n said:
yeah, so I booted in fastboot and did fastboot flash recovery open....zip
twrp works nice, but when I choose reboot system it starts recovery again.
I am also getting mounting errors (unable to mount data and storage).
EDIT: also, in twrp the Internal Storage is appearing as 0MB
Click to expand...
Click to collapse
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?
TimmyUK said:
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?
Click to expand...
Click to collapse
yeah, I'm gonna try following this thread http://forum.xda-developers.com/g-watch-r/development/emergency-guide-how-to-blank-regenerate-t2984678
I'll try another twrp now.
TimmyUK said:
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?
Click to expand...
Click to collapse
ok...so flashing previous version of twrp did not work, same problem with unable to mount.
now, this is weird. I flashed stock recovery, and the watch started straight away...
b0gd4n said:
ok...so flashing previous version of twrp did not work, same problem with unable to mount.
now, this is weird. I flashed stock recovery, and the watch started straight away...
Click to expand...
Click to collapse
That is weird, you running 5.0.1?
TimmyUK said:
That is weird, you running 5.0.1?
Click to expand...
Click to collapse
yeah, 5.0.1.
ok, so after I flashed the stock recovery, and restarted the device normally, I adb sideloaded the 5.0.1 update mentioned in the thread posted earlier.
I then flashed the latest twrp again, and it now seems to be all nice and fine. I can boot to twrp, and the stuff gets mounted and I can reboot the system as well.
dunno what, but smth went wrong the first time I flashed.
all fine now.
Really strange, glad you got it sorted.
@b0gd4n
I've had the same problem at first TWRP Flash.
That's why i've posted this guide
Schmurtz1968 said:
@b0gd4n
I've had the same problem at first TWRP Flash.
That's why i've posted this guide
Click to expand...
Click to collapse
erm, which guide?
b0gd4n said:
erm, which guide?
Click to expand...
Click to collapse
The one you've pointed in this Thread
I did bootloader unlock for my watch using fastboot oem unlock
did fastboot flash recovery twrp.img
fastboot reboot.
I do have TWRP but when i press reboot->System it keeps booting to twrp.
I know to properly flash things on my devices but something here is wrong.
anyone got twrp working after flashing wear 5.02 ?
2.8.5.0 works for me on 5.0.2, Supersu FC's after rebooting and attempting installation. I think this is already a known problem. Just need to do a little more digging.
<edit> Updating to the latest (v2.46) has seemed to have resolved my issue
[RECOVERY] [F2FS/exFAT/NTFS] [UNOFFICIAL] TWRP 3.1.0-0 [tomato] [20170311]
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.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 (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
DOWNLOADS: twrp-3.1.0-0-20170311-UNOFFICIAL-tomato.img
HOW TO FLASH:
Fastboot Method :
Code:
fastboot -i 0x1ebf flash recovery twrp-3.1.0-0-20170311-UNOFFICIAL-tomato.img
Boot to OLD TWRP > INSTALL > Select Image > Navigate to twrp-3.1.0-0-20170311-UNOFFICIAL-tomato.img > Select it & Swipe to Flash
CREDITS:
TeamWin
CyanogenMod
@h2o64 [for base twrp tree]
@HridayHS [for instant help]
ashishrocks, anupamdmoran, Vams, Abhiram Shibu, vjs pranav & Mr. Wolverine [for testing all older builds].
XDA:DevDB Information
[RECOVERY] [F2FS/exFAT/NTFS] [UNOFFICIAL] TWRP 3.1.0-0 [tomato] [20170311], Tool/Utility for the YU Yureka
Contributors
darshan1205
Source Code: http://github.com/omnirom
Version Information
Status: Stable
Current Stable Version: twrp-3.1.0-0-2017031
Stable Release Date: 2017-03-11
Created 2016-06-15
Last Updated 2017-03-11
SOURCES:
Device Tree
Kernel Source
SCREENSHOTS:
reserved
whats the difference between unofficial and official?????
gourabpa said:
whats the difference between unofficial and official?????
Click to expand...
Click to collapse
I built it before official but didn't posted on XDA ...
Sent from my Mi 4i using Tapatalk
darshan1205 said:
I built it before official but didn't posted on XDA ...
Sent from my Mi 4i using Tapatalk
Click to expand...
Click to collapse
ok thanks for ur hard work......
but bro don't feel me wrong.......if the official TWRP is released then everyone known all will download the official build only......
but if u add some new/extra features....in this UnOfficial build.......then almost everyone will download.....ur build....u can understand what i am telling....
gourabpa said:
ok thanks for ur hard work......
but bro don't feel me wrong.......if the official TWRP is released then everyone known all will download the official build only......
but if u add some new/extra features....in this UnOfficial build.......then almost everyone will download.....ur build....u can understand what i am telling....
Click to expand...
Click to collapse
Official one doesn't detects SD card which is formatted as internal but this recovery detects it ....[a user said this on YU Forums]
Sent from my Mi 4i using Tapatalk
darshan1205 said:
Official one doesn't detects SD card which is formatted as internal but this recovery detects it ....[a user said this on YU Forums]
Sent from my Mi 4i using Tapatalk
Click to expand...
Click to collapse
Using Official build in my Yureka plus model it shows the SD Card when its formated properly as Internal.....i think that user properly not formated his SD Card thats why the problem appears......
gourabpa said:
Using Official build in my Yureka plus model it shows the SD Card when its formated properly as Internal.....i think that user properly not formated his SD Card thats why the problem appears......
Click to expand...
Click to collapse
Keep using it [emoji106]
Sent from my Mi 4i using Tapatalk
darshan1205 said:
Keep using it [emoji106]
Sent from my Mi 4i using Tapatalk
Click to expand...
Click to collapse
by the way thanks for ur hard work..........
Dear Darshan Can you try to get OmniRom on yuyureka
TWRP Updated to v3.0.3-0
Download Link: https://www.androidfilehost.com/?fid=529152257862692928
any bugs so far?
darshan1205 said:
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.
DOWNLOADS: twrp-3.0.3-0-20160604-UNOFFICIAL-tomato.img
HOW TO FLASH:
Fastboot Method :
Code:
fastboot -i 0x1ebf flash recovery twrp-3.0.3-0-20170104-UNOFFICIAL-tomato.img
Boot to OLD TWRP > INSTALL > Select Image > Navigate to twrp-3.0.3-0-20170104-UNOFFICIAL-tomato.img > Select it & Swipe to Flash
CREDITS:
TeamWin
CyanogenMod
@h2o64 [for base twrp tree]
@HridayHS [for instant help]
ashishrocks, anupamdmoran, Vams, Abhiram Shibu, vjs pranav & Mr. Wolverine [for testing all older builds].
XDA:DevDB Information
[RECOVERY][F2FS][UNOFFICIAL] TWRP 3.0.3-0 for YUREKA/YUREKA PLUS [tomato] [20170104], Tool/Utility for the YU Yureka
Contributors
darshan1205
Source Code: http://github.com/omnirom
Version Information
Status: Stable
Current Stable Version: twrp-3.0.3.0-2017060
Stable Release Date: 2017-01-04
Created 2016-06-15
Last Updated 2017-01-04
Click to expand...
Click to collapse
@darshan1205 TWRP is not detecting my internal memory. And while taking backup, it says "failed to mount /data (invalid argument)". What should I do to make my both internal & external memory to work?
BuntyS5 said:
@darshan1205 TWRP is not detecting my internal memory. And while taking backup, it says "failed to mount /data (invalid argument)". What should I do to make my both internal & external memory to work?
Click to expand...
Click to collapse
Take a backup on OTG drive or PC & wipe everything once
Sent from my YU5010 using Tapatalk
Again same error while formatting everything.
darshan1205 said:
Take a backup on OTG drive or PC & wipe everything once
Sent from my YU5010 using Tapatalk
Click to expand...
Click to collapse
Bro, Again I'm getting the same error while wiping data. It is showing mounting error in TWRP. What to do? Plz help. :crying:
New Build is up!
TWRP 3.1.0-0 for YUREKA/YUREKA PLUS
Device Specific Changelog:
Added EFS backup option (requested by [email protected])
Added NTFS support [not tested] (requested by @nitesh9)
Added exFAT support [not tested] (requested by Abhiram Shibu)
TWRP Changelog:
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 (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
Thanks to wolfie616 & [email protected] for testing.
Download Link: https://www.androidfilehost.com/?fid=529152257862709397
There will be an update based on twrp changes twrp changes & kernel changes
Earlier was using the latest official recovery for my Yureka and was facing Error 7 issue. Now installed the latest 3.1.0.0 version from here and I am able to install the custom 7.1 Lineage RoM. @darshan1205 please update the TWRP here to the latest version if possible. Thanks for the work!!
Team Win Recovery Project
This is a unified build for both the Redmi Note 3 (kenzo) and the Redmi Note 3 SE (kate)
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
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.
FEATURES:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
f2fs file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup (fstab)
ADB root
Full SELinux support
Built with android 7.1 tree
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
CONTRIBUTIONS:
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
TWRP for Redmi Note 3, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
TheStrix
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2017-03-04
Last Updated 2017-03-21
FAQ:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
Is this TWRP able to flash official ROM and incremental OTA also without any workaround, like TWRP zcx does?
i did a few benchmark on f2fs, but didnt notice a major difference on kenzo, is it really the case? or is F2Fs really worth it
fardeenah said:
i did a few benchmark on f2fs, but didnt notice a major difference on kenzo, is it really the case? or is F2Fs really worth it
Click to expand...
Click to collapse
With latest lineage os and Radeon kernel I get 89500 with Antutu. Changing to f2fs gets me 91500. 1 would say a 2000 Antutu increase is pretty impressive.
Antutu don't test disk-speed! So your 2000 extra points have another reason, maybe media-indexing at phone-start etc...ext4 is best filesystem for your phones because it is fast in ALL cases and rock solid!
D4xel said:
Is this TWRP able to flash official ROM and incremental OTA also without any workaround, like TWRP zcx does?
Click to expand...
Click to collapse
I'd like to know this as well, as i'm expecting a Kate device soon.
Thanks! It also prompt you to install the twrp app. Working well for now (Only flashed and wiped stuff)
Hey guys I converted data & cache from ext4 to f2fs (backup data>wipe dalvik+format cache f2fs+format data f2fs>restore data backup with rm-rf) and internal storage was wiped in the process. I don't remember wiping internal storage and can anyone help me check whether I was careless or it is a bug.
With the latest version, I'm not able to install kenzo custom roms to my kate phone.
Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/Nitrogen-OS-kenzo-20170304.zip'
when i did clean wipe & give reboot to recovery phone start on system not going to recovery.
I have to press vol+ & power for 10 sec to go to recovery.
Please fix it.
Note: Its only happen while clean wipe.
So using f2fs is better than ext4?
gaurav1902 said:
So using f2fs is better than ext4?
Click to expand...
Click to collapse
Lot's of devs say no. I can't feel the difference overall but opening Settings>Apps in f2fs is a whole lot faster than in ext4 for me.
Btw ext4 is compatible with more stuff as you might face issues flashing zips to f2fs partition (which I haven't faced yet).
jianwen03 said:
Lot's of devs say no. I can't feel the difference overall but opening Settings>Apps in f2fs is a whole lot faster than in ext4 for me.
Click to expand...
Click to collapse
Same
Awesome thanks for sharing
Draygon said:
With the latest version, I'm not able to install kenzo custom roms to my kate phone.
Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
'
Click to expand...
Click to collapse
The error probably arose due to this being a unified TWRP for Kenzo and Kate . Apparently, this TWRP is able to differentiate between Kenzo and Kate devices, and has assigned a specific flag to each identification. Thus , Kenzo is ID'd as a Kenzo , and Kate is ID'd as a Kate.
This is actually very bad news for Kate users. If you look around Note 3's ROM scene, every single custom ROM is named as a Kenzo release and is keyed for Kenzo. The only reason kate users were able to install these Roms was because they were using Kenzo TWRPs. Despite being Kate, the TWRP fooled the ROM into thinking it is Kenzo and then allowed the installation.
In every ROM and in some other zip installs, there's a file called updater.script. This file, actually the first lines of the file, is where the ROM performs its only device check.
So how does a Kate user bypass this ERROR 7? Well, there are many ways:
1. Change the two mentions of "Kenzo" on the first lines of the ROM 's updater.script to "Kate", then flash like before,
2. Or, urge the op to make a Kenzo-only TWRP, and flash.that,
3. Or beg the op to modify the TWRP to forgo this updater.sfript check.
Personally, I'd just stay away from Kate or Kenzo/Kate unified TWRPs. Changing update.script on every ROM you want to flash can become very tedious.
It's a lot easier being a fake Kenzo, then a real Kate.
gaurav1902 said:
So using f2fs is better than ext4?
Click to expand...
Click to collapse
I am using f2fs for 2 days now and it is definitely snappier when it comes to multitasking. On ext4, the recents button was a bit slow for me, pressing and showing up the recents sometimes took a good half second, was unsure if I even pressed it but then oh look it appeared. No such issue for f2fs, everything is happening as I'm pressing buttons.
Draygon said:
With the latest version, I'm not able to install kenzo custom roms to my kate phone.
Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/Nitrogen-OS-kenzo-20170304.zip'
Click to expand...
Click to collapse
Did you install Kate's TWRP or Kenzo's one?
@TheStrix
System won't boot after changing from M4 recovery to this one..
but this time, I'm even unable to revert back to M4 -> system not booting, just mi logo > reboot
m4 recovery also wouldn't boot
so now I'm completely stuck (given my limited capabilities).
btw: I actually wasn't able to change to another recovery since I changed to f2fs on M4 (tried zcx, dad1, ... )
logs are here: https://drive.google.com/open?id=0B9NuN8yWvpeZQzFDVGF4UTREWnc
edit: found out that it might be a problem with latest AGNI kernel: I unbricked and reinstalled (CM13), and my problem seems to be reproducable with latest releases - radon works however..
schmanto said:
@TheStrix
System won't boot after changing from M4 recovery to this one..
but this time, I'm even unable to revert back to M4 -> system not booting, just mi logo > reboot
m4 recovery also wouldn't boot
so now I'm completely stuck (given my limited capabilities).
btw: I actually wasn't able to change to another recovery since I changed to f2fs on M4 (tried zcx, dad1, ... )
logs are here: https://drive.google.com/open?id=0B9NuN8yWvpeZQzFDVGF4UTREWnc
Click to expand...
Click to collapse
If you are able to boot into recovery, format partitions as ext4 and flash recovery of your choice.
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.2.1-0:
minui fixes (cryptomilk)
Better android-8.0 compatibility in ROM trees (Dees_Troy)
Fix missing library in android-8.0 (nkk71)
Fix inconsistent SDCard naming (DevUt)
Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
CHANGELOG for 3.1.1-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)Updated TWRP source code to AOSP 7.1.2
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 (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
DOWNLOADS: twrp-3.2.1-0-rolex.img
HOW TO FLASH:
Fastboot Method :
Code:
fastboot flash recovery twrp-3.2.1-0-rolex.img
Boot to OLD TWRP > INSTALL > Select Image > Navigate to twrp-3.2.1-0-rolex.img > Select it & Swipe to Flash
CREDITS:
TeamWin
CyanogenMod/Lineage Android
Hyper
XDA:DevDB Information
[RECOVERY] [OFFICIAL] TWRP 3.2.1-0 for Xiaomi Redmi 4A [rolex] [20171210], Tool/Utility for the Android General
Contributors
darshan1205
Source Code: http://github.com/omnirom
Version Information
Status: Stable
Created 2017-03-20
Last Updated 2017-12-10
Device Source: https://github.com/TeamWin/android_device_xiaomi_rolex
Flash lazyflasher to disable dm-verity & forced encryption on MIUI
I've been waiting a long time for this good news.
Thank you sir.
darshan1205 said:
Kernel Source: rolex_global_images_V8.2.1.0.MCCMIDL_20170306.0000.00_6.0_global_801a10c894
Click to expand...
Click to collapse
Kernel source or global rom ?
Thanks for this. Added it to the main thread for the Redmi 4A: https://forum.xda-developers.com/general/general/xiaomi-redmi-4a-chat-root-sd-425-2gb-t3511933
darshan1205 said:
Kernel Source: rolex_global_images_V8.2.1.0.MCCMIDL_20170306.0000.00_6.0_global_801a10c894
Click to expand...
Click to collapse
This is no kernel source. It's just the fastboot images as far as I can tell...
I think kernel sources have not been released yet. But someone please correct me if I'm wrong...
This build of TWRP uses prebuilt kernel from latest global stable rom so that is mentioned as kernel source
Ah ok, I see. And thanks for the recovery! :good:
EDIT: Oh well, after flashing this one, system doesn't boot anymore in my case. I came from cofface-recovery (3.0.2-0), which worked fine.
Now, booting system just hangs on the screen with the 3 moving dots and apparently never finishes. Hmmm, any idea?
EDIT2: To fix it, I had to re-install 8.2.1.0 global rom. Also, I had downgraded TWRP to 3.0.2-0 again, but maybe this wouldn't have been necessary.
void23 said:
Ah ok, I see. And thanks for the recovery! :good:
EDIT: Oh well, after flashing this one, system doesn't boot anymore in my case. I came from cofface-recovery (3.0.2-0), which worked fine.
Now, booting system just hangs on the screen with the 3 moving dots and apparently never finishes. Hmmm, any idea?
EDIT2: To fix it, I had to re-install 8.2.1.0 global rom. Also, I had downgraded TWRP to 3.0.2-0 again, but maybe this wouldn't have been necessary.
Click to expand...
Click to collapse
Flash LazyFlasher zip to disable forced encryption after flashing recovery if you are using MIUI
Thanks man ! But a line is missing for TWRP intall : after you enter this line :
- fastboot flash recovery twrp-3.1.0-0-20170318-UNOFFICIAL-rolex.img
you need to enter this : fastboot boot twrp-3.1.0-0-20170318-UNOFFICIAL-rolex.img
Guys if isn't asking too much when Xiaomi release the source of Rolex (our device) anyone can quote me or send a pm? I plan to do a custom kernel for it. Thanks advanced!
Sent from my Xiaomi Redmi 4A using XDA Labs
Hello, will i used to flash the recovery every time i needed? I am not able to boot to recovery. Only Mi Logo appears at cold boot. By using the extended power button menu it works flawless
Gesendet von meinem Redmi 4A mit Tapatalk
How to unlock bootloader of Redmi 4A
---------- Post added at 02:44 PM ---------- Previous post was at 02:41 PM ----------
Edl mode is not working and when I tried to flash recovery from it shown me
It is not allowed to flash unofficial from
There will be an update based on twrp changes twrp changes & kernel changes from latest STOCK ROM
Can u tell me how to fix that I have compiled a tarp for 4A working fine, but only showing decrypted data, but your recovery working fine
Source: https://github.com/AndroiableDroid/android_device_xiaomi_rolex
Please checkout this repository and tell me mistake
i'm using cofface's version and it doesn't support USB-OTG. Does your version support it?
Mohd.faraz.abc said:
Can u tell me how to fix that I have compiled a tarp for 4A working fine, but only showing decrypted data, but your recovery working fine
Source: https://github.com/AndroiableDroid/android_device_xiaomi_rolex
Please checkout this repository and tell me mistake
Click to expand...
Click to collapse
Add drm blobs
mybabysexy said:
i'm using cofface's version and it doesn't support USB-OTG. Does your version support it?
Click to expand...
Click to collapse
Yup
Sent from my Redmi 3S using Tapatalk
darshan1205 said:
Add drm blobs
Yup
Click to expand...
Click to collapse
How and what should I add
---------- Post added at 11:01 AM ---------- Previous post was at 10:56 AM ----------
Mohd.faraz.abc said:
How and what should I add
Click to expand...
Click to collapse
Can u tell me what files I need to add in which folders plz
mybabysexy said:
i'm using cofface's version and it doesn't support USB-OTG. Does your version support it?
Click to expand...
Click to collapse
I had to format the USB key as exFAT, and it worked in cofface's version without any problem.
---------- Post added at 01:43 PM ---------- Previous post was at 01:30 PM ----------
MIUI seems to overwrite TWRP and flash its own recovery again. I recall that I had the same issue at first with my Note 4X (mido), but I don't remember how I made TWRP persistent. For now, I don't want to flash a custom ROM on my dad's rolex, but I'd like TWRP to remain on the device. Any help would be appreciated.