[RECOVERY][i9500] TWRP 3.0.0-0 touch recovery [2016-02-06] - Galaxy S 4 i9500 Original Android Development

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.

Device specific page for i9500
Mirror 1
Mirror 2
Special thanks to SamerDiab for helping test.

TWRP Flasher BUILD 1.0 Noob Edition​What Do You Get With TWRP Flasher ?
1. The Most Easiest Way To Flash TWRP Recovery.
2.A Full Guide on HOW To Flash TWRP Recovery.
What Do you Need To DO To USE The TOOL ?
1.Enable USB Debugging.
2.On S4 No Need To Install Drivers.
3.Plug in Your Phone And Sit Down And Realx.{Just Follow The Command Prompt}
Downloads :
TWRP Flasher Build 1 Noob Edition{WINDOWS Edition}
How To USE ?
1.Download And Extract To A Folder.
2.Copy TWRP.tar To Place-Recovey-Here Folder That Comes With The Tool.
3.Run TWRP Flahsher.
And Please Hit The Thanks Button.
KingCobra Rom's Run's Best With TWRP​

It is not working for me.
I have just tried the GooManager method, it downloaded the openscript for the i9500 and installed. I then rebooted through a Restart>Recovery from inside Android OS it rebooted but it was not able to boot to TWRP, instead it rebooted twice and went back to Android OS.
I have not tested booting using 3 button combination yet. Will give it a try and report back.
Update: So if I try to boot with Volume Up + Home + Power then it does boot to TWRP with no problem. Weird. I am on Wanamlite 1.8 if it works.
Update: Disregard after a second reboot it did go to TWRP when rebooted into recovery from within the power menu in the ROM. All is working fine now. Thanks for the great work. I used to work with CWM but TWRP rulez!!!

Great!!! Working well for me...
Sent from my Octa using New Tapatalk 4

Guti1977 said:
It is not working for me.
I have just tried the GooManager method, it downloaded the openscript for the i9500 and installed. I then rebooted through a Restart>Recovery from inside Android OS it rebooted but it was not able to boot to TWRP, instead it rebooted twice and went back to Android OS.
I have not tested booting using 3 button combination yet. Will give it a try and report back.
Update: So if I try to boot with Volume Up + Home + Power then it does boot to TWRP with no problem. Weird. I am on Wanamlite 1.8 if it works.
Update: Disregard after a second reboot it did go to TWRP when rebooted into recovery from within the power menu in the ROM. All is working fine now. Thanks for the great work. I used to work with CWM but TWRP rulez!!!
Click to expand...
Click to collapse
Well wanam apm is working so it should be working

Yay TWRP! Welcome, Deestroy
Sent from my GT-I9500 using Tapatalk 5.0.203 Alpha
1700Mhz A15 and 1500Mhz A7 running together with 640Mhz GPU.

Mate - I was missing TWRP for so much time on I9500. It`s really cool that atleast some developers are brave enough to stay with I9500

Thanks bro...just flashed using SGS4 Flasher app from playstore and it works...yeahhhh....no need pc odin...missed twrp on my note2 and s3.
Sent from my GT-I9500 using xda premium

hazri1974 said:
Thanks bro...just flashed using SGS4 Flasher app from playstore and it works...yeahhhh....no need pc odin...missed twrp on my note2 and s3.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
GooManager can download the correct file and flash it for you automatically as well.

And the tool does to its easy to flash with it
Sent from my GT-I9500 using xda premium

When i install super wipe.zip of mike, to the finish this reboot in recovery, so no enter in recovery and have continue loop in galaxy i9500 logo.
Thank you very much, excelent work.
(i dont have this problem in any other recovery)
-Sorry for my bad english.

kirabyte said:
When i install super wipe.zip of mike, to the finish this reboot in recovery, so no enter in recovery and have continue loop in galaxy i9500 logo.
Thank you very much, excelent work.
(i dont have this problem in any other recovery)
-Sorry for my bad english.
Click to expand...
Click to collapse
You mean super wipe frim mike1986 right ?
I dont see a ARHD Here you must be rong this is Gt_i9500 forum not i9505
Sent from my GT-I9500 using xda premium

I really appreciate having this in my i9500.
I was missing it a LOT!
Thanks for your work.
I have tried and I can reboot into recovery, and boot from power off too.
Working great.
BTW, I'm using wanam's 1,8 and it works.

S.a.M.e.R_d said:
You mean super wipe frim mike1986 right ?
I dont see a ARHD Here you must be rong this is Gt_i9500 forum not i9505
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Of course, but the .zip is in phoenix rom 4.0, and i use for install a lot of roms...
I have I9500..
Thank you.

Awesome
Sent from my GT-I9500

Thanks a lot for bringing TWRP for I9500.. That's a solo thing which was being missed by many since many days! :victory:

Thanks for updating it on i9500. Tried almost all the options except themes and everything is working great. Just for info what is the cpu usage on recovery as I noticed phone getting a little more hot than usual.
Sent from my GT-I9500 using Tapatalk 4 Beta

Question regarding the restore
Hi All,
I haven't used it ever. I was on Philz. So just wanted to know if I can restore Nandroid backup created with Philz(which is CWM basically) using TWRP..
Help would be much appreciated..

sozofriend1234 said:
Hi All,
I haven't used it ever. I was on Philz. So just wanted to know if I can restore Nandroid backup created with Philz(which is CWM basically) using TWRP..
Help would be much appreciated..
Click to expand...
Click to collapse
No you canf restore but i highley request that u use twrp it faster loveleiyer to use full touch and more andriid os like si use it
Sent from my GT-I9500 using xda premium

Related

[RECOVERY] TWRP 2.8.7.0 touch recovery for KFireHD 7" (ZIP) [06-24 v2.8.7.0]

[ THIS POST IS TEAMWIN'S STOCK TWRP POSTING. USE OF THE WORDS "US" AND "OURS" MEANS "DEES_TROY AND TEAMWIN" NOT HASHCODE ]
*** ALL CREDIT FOR TWRP BELONGS TO DEES_TROY AND TEAMWIN. ***
They do a BANG UP job on making a fantastic customizable touch-based recovery.
SEE BOTTOM OF THIS POST FOR DOWNLOAD / INSTALL INSTRUCTIONS
Donate to TeamWin:
http://www.teamw.in/project/twrp2
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2128848
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Tablet look:
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.
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
** THIS IS A FLASHABLE .ZIP FILE FOR INSTALLING IN YOUR CURRENT VERSION OF TWRP **
DOWNLOAD:
[ DO NOT DOWNLOAD ANY FILES FROM TEAMWIN'S WEBSITE.
IN GENERAL, THEY ARE MEANT TO BE FLASHED TO UNLOCKED DEVICES AND WON'T WORK FOR KINDLE FIRE HD'S ]
You can download a flashable recovery zip and place in your SDCARD area on the device:
ON THE FOLLOWING DEV-HOST LINK
USE THE BLUE "DOWNLOAD NOW" BUTTON
-- DO NOT INSTALL AN EXECUTABLE DOWNLOADER TO YOUR SYSTEM! --
I'LL LOOK FOR A BETTER HOST WHEN I GET MORE TIME.
Mirror 1 : Download recovery zip from Dev-Host
INSTALL INSTRUCTIONS:
While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button)
Select "Install"
Navigate to where you placed the file on your device
Select the .zip filename
Swipe to confirm flash
Reboot
KNOWN ISSUES:
[07/08] Disabled the screen blank due to a display issue where screen doesn't come back on well.
BUGS:
First: I'd read through this thread and see if your issue isn't answered.
Second: Try googling for it
Third: If it seems like a Kindle Fire HD issue, then post in the thread.
Lastly: If you have found a bug, please consider posting it to TeamWin's 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 #kindlefire-dev or #twrp on Freenode with your IRC client or just click this link.
error
im ending up with this error when i try to flash
Can you check the md5sum on that file and make sure it matches 4056520ee7b13be01d42d785cca2b15e?
Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.
Hashcode said:
Can you check the md5sum on that file and make sure it matches 4056520ee7b13be01d42d785cca2b15e?
Click to expand...
Click to collapse
the md5 does match
tried it again and this time it worked thanks hashcode
seokhun said:
Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.
Click to expand...
Click to collapse
Yes, I can probably do a .zip update. I'll need a night or 2. Been pretty busy.
Hashcode said:
Yes, I can probably do a .zip update. I'll need a night or 2. Been pretty busy.
Click to expand...
Click to collapse
and how is the kernel goings man?, good job with this
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery for KFireHD 7" [2013-04-02]
seokhun said:
Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.
Click to expand...
Click to collapse
Hey you can install the new version through fireflash also I just did with no problem
Sent from my KFTT using xda premium
As in, plugging in the .img recovery file Hashcode provided, leave everything else blank and just flash? Are you sure? Seems a little risky to me. If someone else can verify that, I'll do it, but I'm willing to wait for Hashcode's .zip, no offense.
seokhun said:
I'm willing to wait for Hashcode's .zip, no offense.
Click to expand...
Click to collapse
+1
Sent from my KFHD using xda premium
I promise u it works will post a video of proof by about 12 tonight if everyone would do this and leave hash code alone about petty crap maybe we would have cm 10.1 and custom kernel by :screwy:
Sent from my LG-E970 using xda premium
Respectfully disagree,
If people start bricking their devices because of unnecessary flashes, the threads will be overwhelmed with people griping and begging for help...
Personally I am waiting for cm10 as well and have not even installed recovery yet on my device due to this..
But I do understand that twrp allows a proper backup and honestly is something all android devices should have installed
Sent from my GT-P3110 using xda app-developers app
mrkhigh said:
Respectfully disagree,
If people start bricking their devices because of unnecessary flashes, the threads will be overwhelmed with people griping and begging for help...
Personally I am waiting for cm10 as well and have not even installed recovery yet on my device due to this..
But I do understand that twrp allows a proper backup and honestly is something all android devices should have installed
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.
Jester6 said:
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.
Click to expand...
Click to collapse
:good:+1
Jester6 said:
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.
Click to expand...
Click to collapse
You got wrong what he said. The user above stated that we're wasting hashcode's time by making him do zip updates for twrp (instead of flashing them), and he (the one you quoted) added that is better to update twrp with ZIPs since its less risky.
Sent from my KFTT using xda app-developers app
jailuis said:
You got wrong what he said. The user above stated that we're wasting hashcode's time by making him do zip updates for twrp (instead of flashing them), and he (the one you quoted) added that is better to update twrp with ZIPs since its less risky.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Either way, it makes little to no sense. I understand that hashcode has a lot on his plate but update zips are a simple enough process and take a small amount of time/work, now I don't know that about twrp as its not officially supported (to my knowledge) but an update zip for a ROM is a very easy process, I'm sure there's a bit involved in making twrp work for the kfhd but I don't imagine its crazy.
Thank You Hashcode for your efforts. An update zip would be sweet. Keep up the great work!
This is a Kinology HD using XDA Premium
video with instructions and proof of concept
seokhun said:
As in, plugging in the .img recovery file Hashcode provided, leave everything else blank and just flash? Are you sure? Seems a little risky to me. If someone else can verify that, I'll do it, but I'm willing to wait for Hashcode's .zip, no offense.
Click to expand...
Click to collapse
yes that's correct i need no one else to verify this but there's a video on my channel here>http://www.youtube.com/user/choppedncut79cutlass/videos <as for the rest of these space wasting comments i reply in the morn nite all work in the morning
So I got brave and decided to work with fastboot, and I can flash with the standard platform-tools procedure. I know I have fastboot using Hashcode's "getvar product" command, and booted into fastboot successfully. However, I don't know how to flash using the "fastboot -i 0x1949" command. Do I first CD to the folder that the file is placed in? A little help for a noob will be greatly appreciated, Hashcode, or anyone else well-versed in fastboot. Thank you!
I'd also like to know if the standard procedure will also work here. In other words, if I place the file in \platform-tools and ran the "fastboot flash <filename>.img", would it work? I'm afraid it would fail because of the Kindle's locked bootloader and how we're working with a 2nd one. Sorry, I'm very new to this whole bootloader thing and willing to learn.
Where ever fastboot is, I think.
This is a Kinology HD using XDA Premium

[RECOVERY][OFFICIAL] TWRP for HTC One Dual SIM (802W, 802D and 802T variants)

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 NEW website!
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log to SD, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
If your issue is determined to be 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 contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Reserved
This is great! Whenever i plugin my charger once my battery drained, unlike before, it doesnt boot to recovery with unresposive touch anymore.. good job @bgcngm!
Sent from mobile
Thanks for the feedback.
By the way, you can use TWRP Materialised theme, to get an even nicer UI.
@bgcngm This is great job! Thank you.
You think it would be possible to solve the /data/preload problem when wiping from TWRP?
EDIT:
MTP seems to be working great! I do see MicroSDcard and SD-Ext plus USB OTG. What would be SD-Ext for?
J_M_V_S said:
You think it would be possible to solve the /data/preload problem when wiping from TWRP?
Click to expand...
Click to collapse
I think so, should be possible to preserve /data/preload during a factory reset. I can't try right now because my phone is *again* at the repair center for camera replacement.
MTP seems to be working great! I do see MicroSDcard and SD-Ext plus USB OTG. What would be SD-Ext for?
Click to expand...
Click to collapse
SD-Ext is if you have your SDcard partitioned with an EXT2/3/4 partition. I think that is not so used anymore.
TWRP v2.8.4.0 is out.
TWRP v2.8.5.0 is out.
Do you have any mirror? I cannot download from homepage. Always stuck at 99.99%
No, I don't. That's the official link to the website. Try again later if server is down / overloaded.
TWRP v2.8.6.0 is out.
Help
bgcngm said:
TWRP v2.8.6.0 is out.
Click to expand...
Click to collapse
Hi, thanks for the TWRP but do you have the stock recovery file for HTC One M7 802dwg? I want to revert back to stock recovery to get the OTA updates which i'm not being able too install by TWRP or CWM. I'm on Hboot 2.49, Bootloader unlocked, Rooted, S-On, M7 802dwg.
Thanks in advance.
If you still have a copy of the last OTA that you applied, you can get the recovery from within that file.
Any help??
angusc said:
If you still have a copy of the last OTA that you applied, you can get the recovery from within that file.
Click to expand...
Click to collapse
Hi, thanks i got the stock kitkat recovery and flashed it and then updates by OTA to 4.4.3 but then again after downloading Lollipop OTA i am not being able to update!!! I tried to extract the recovery file from the Firmware.zip from within the OTA.zip
but it gives me an error. I can't open the firmware.zip. Any idea where can i get the stock lollipop recovery image file for 802dwg??
[email protected] said:
Hi, thanks i got the stock kitkat recovery and flashed it and then updates by OTA to 4.4.3 but then again after downloading Lollipop OTA i am not being able to update!!! I tried to extract the recovery file from the Firmware.zip from within the OTA.zip
but it gives me an error. I can't open the firmware.zip. Any idea where can i get the stock lollipop recovery image file for 802dwg??
Click to expand...
Click to collapse
I have the same problem, plz help, i stuck in bootloop on HTC one 802d
sekilo004 said:
I have the same problem, plz help, i stuck in bootloop on HTC one 802d
Click to expand...
Click to collapse
For now restore from a nandroid or TWRP backup...and update upto 4.4.3 unless there is a copy of the lollipop stock recovery.
Could you guys stop spamming this thread with off-topic? If you didn't yet realize, this thread is related to TWRP only. You have already been told how to get the stock recovery.
sorry for my bad english and still noob,..
I flashed twrp-2.8.7.0-m7cdwg.img for my HTC m7 802d..
after booting on twrp, I'm looking on system/lib/modules, but not found. there is only BIN folder
anyone suggest or modify twrp to make it possible that directory, system/lib/modules are avalible on twrp?
thank in advance
What exactly are you trying to do? Maybe you have to mount system first...

[RECOVERY][OFFICIAL] TWRP 3.0.0-0| 10/2/2016

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:
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 Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP Recovery, Tool/Utility for the Sony Xperia Z3 Compact
Contributors
someone755
Version Information
Status: Stable
Stable Release Date: 2015-08-18
Created 2015-08-18
Last Updated 2016-02-17
Device page on the TWRP website:
Mirror 1
There is no Mirror 2.
Due to the way Sony devices function, you will need to have an unlocked bootloader.
Your options, as far as ROMs go, are the following:
Any ROM with this commit
OR just use the new bootloader (with a proper recovery partition)
All credit goes to the TWRP team. I just annoyed the fools until they built the recovery.
Awesome! Very glad to see this.
After flashing through fastboot, its impossible for me to boot into recovery, my phone stays stuck on the Sony screen with the pink/orange led.
Running resurrection remix and m5 kernel, theme has been updated for 2.8.7, previously was on 2.6.0
Can this be install on LB?
rich2007 said:
Can this be install on LB?
Click to expand...
Click to collapse
it should work with andropluskernel, not with stock
omnomnomkimiiee said:
After flashing through fastboot, its impossible for me to boot into recovery, my phone stays stuck on the Sony screen with the pink/orange led.
Running resurrection remix and m5 kernel, theme has been updated for 2.8.7, previously was on 2.6.0
Click to expand...
Click to collapse
Works fine here. Did you check the md5 before installing? Does it work without the theme?
rich2007 said:
Can this be install on LB?
Click to expand...
Click to collapse
You need a custom boot image to boot into it (since our bootloaders don't really support a separate recovery partition, and we rely on a boot.img script to boot into one), which means you'd have to unlock the bootloader.
funiewski said:
it should work with andropluskernel, not with stock
Click to expand...
Click to collapse
On this note, if anyone can provide me with stock boot images, I'll try and keep them up-to-date with the extract_elf_ramdisk utility, so that users on stock may still boot into TWRP if they don't opt for the AndroPlus kernel.
Hello everyone,
Flashed this with "fastboot flash recovery", still getting the cm12.1 recovery.
BL unlocked, USB debugging enabled, CM 12.1 installed.
Anyone have a solution?
Thanks
Edit:
tried the twrp manager, no Z3C here, aswell the dd method, nothing changed.
pityu100 said:
Hello everyone,
Flashed this with "fastboot flash recovery", still getting the cm12.1 recovery.
BL unlocked, USB debugging enabled, CM 12.1 installed.
Anyone have a solution?
Thanks
Edit:
tried the twrp manager, no Z3C here, aswell the dd method, nothing changed.
Click to expand...
Click to collapse
Same here, there is no Z3C in the list on TWRP Manager, and the 'dd' method leaves an unusable recovery (stuck on orange led). I'm happy with official TWRP support, but do you guys even test your stuff before releasing it.....? The steps with TWRP manager app don't even exist (there is no 'advanced' to tap).
Flashed twrp.img as boot: fastboot flash boot twrp.img. -> TWRP starts every time i power on the phone. Flashed CM12.1 from this state, and TWRP got overwrited again with CM12.1 recovery. /sigh
Is the CM kernel counts as "Any custom kernel" ?
pityu100 said:
text
Click to expand...
Click to collapse
Menubalk said:
Same here, there is no Z3C in the list on TWRP Manager, and the 'dd' method leaves an unusable recovery (stuck on orange led). I'm happy with official TWRP support, but do you guys even test your stuff before releasing it.....? The steps with TWRP manager app don't even exist (there is no 'advanced' to tap).
Click to expand...
Click to collapse
Thanks both of you for reporting your issues. Your reports sparked an investigation, and we were able to identify several issues that have thus far been overlooked (for whatever reason).
The "stuff" was tested before it was released, yes, but we're now facing limitations in the form of unmerged patches to the CM device trees. The issues should have been resolved several years ago, but instead they are now wreaking havoc on Sony msm8974 recovery setups. I've gotten some of the elite TWRP and CM people on this, as well as smaller fellow rhine and shinano developers (though Myself5 and oshomun could hardly be classified as small nowadays).
I personally have already uploaded four changes to the CM gerrit (that should have been applied years ago); One of them got denied (though is now being discussed for the near future (possibly as soon as cm-13.0); the result of that discussion is, among others, that the Cyanogen Recovery is now available for download alongside the ROM zip over at https://download.cyanogenmod.org/?device=z3c ), two are still pending any input whatsoever, and the last one was promised a merge, but the device maintainers have gone quiet, at least on the outside.
(If you wish, you can view the patches and their progress at their links: patch1, patch2, patch3, patch4, patch5.)
However, both teams are also having issues with other matters (such as Z3 not building, or adding new features to TWRP), and there is also the fact that school starts around this time of year (which impacts both the younger developers as well as those who already have children).
To conclude, there really isn't a unified guide I can give you to get to TWRP. It works, and you can use it if you have the correct setup. However achieving that setup is not a simple walkthrough away, and it would differ ever so slightly for every person's preferences, not to mention it would be overwritten with each new ROM update.
Such is the state of affairs at this point in time. This may or may not change, but be assured that everything we can do about this, we will do.
EDIT: A quick note that some ROMs may already include fixes for these issues. I don't know which those ROMs could be, so I won't go into listing them, but the possibility exists.
someone755,
thanks for your quick reply and your investigation.
Hope for the best, but time will tell.
Thanks again
Someone, here is a build that actually works, maybe you guys can base on that?: http://forum.xda-developers.com/z3-compact/development/recovery-twrp-2-8-6-0-fota-recovery-t3093537
I'm on Cyanogen 12.1 nightlies with M5 (=Cyanogen-based) kernel btw.
Menubalk said:
Someone, here is a build that actually works, maybe you guys can base on that?: http://forum.xda-developers.com/z3-compact/development/recovery-twrp-2-8-6-0-fota-recovery-t3093537
I'm on Cyanogen 12.1 nightlies with M5 (=Cyanogen-based) kernel btw.
Click to expand...
Click to collapse
The thing is that if you flash a cm-12.1 boot image (completely stock, without kernel or ramdisk modifications that M5 or Kernel12 perform), it won't work. It works with some setups, but not with others, and is, for some reason, very specific -- to get rid of these errors, CyanogenMod would have to (at the very least) accept my changes.
If you feel like you have to try this for yourself, here's a link to the boot image: https://www.androidfilehost.com/?fid=24052804347797955 Getting out of the mess created once you flash this can be a pickle though, so unless you have a boot image on hand with which you know TWRP works, do not flash the file I linked.
I've had somebody say it started working for him after flashing r_02 of Kernel12, though sadly I'm not very sure that's a permanent solution (it is, however, a working temporary one).
Unfortunately the man who was supposed to review the changes is on leave from development, so waiting is the only option available right now (unless we come up with a zip file to flash after each nightly install, but that would only increase the chaos of this already-confusing situation).
someone755 said:
The thing is that if you flash a cm-12.1 boot image (completely stock, without kernel or ramdisk modifications that M5 or Kernel12 perform), it won't work. It works with some setups, but not with others, and is, for some reason, very specific -- to get rid of these errors, CyanogenMod would have to (at the very least) accept my changes.
If you feel like you have to try this for yourself, here's a link to the boot image: https://www.androidfilehost.com/?fid=24052804347797955 Getting out of the mess created once you flash this can be a pickle though, so unless you have a boot image on hand with which you know TWRP works, do not flash the file I linked.
I've had somebody say it started working for him after flashing r_02 of Kernel12, though sadly I'm not very sure that's a permanent solution (it is, however, a working temporary one).
Unfortunately the man who was supposed to review the changes is on leave from development, so waiting is the only option available right now (unless we come up with a zip file to flash after each nightly install, but that would only increase the chaos of this already-confusing situation).
Click to expand...
Click to collapse
Had no issues with my 2.8.7.0 twrp built into my ROMs boot.img been working with no issues so far
Sent from my Z3 Compact using Tapatalk
jenkins-84 said:
Had no issues with my 2.8.7.0 twrp built into my ROMs boot.img been working with no issues so far
Sent from my Z3 Compact using Tapatalk
Click to expand...
Click to collapse
The goal of FOTA recoveries was to let the user boot into a recovery regardless of what recovery is in the boot image. If you flash a CM nightly over your setup, you won't be able to get to TWRP again unless you perform various modifications to the CM boot image.
Packing recovery inside boot is what's causing all these issues in the first place, so doing what you suggest would be a step forward, but two steps back as well.
someone755 said:
The goal of FOTA recoveries was to let the user boot into a recovery regardless of what recovery is in the boot image. If you flash a CM nightly over your setup, you won't be able to get to TWRP again unless you perform various modifications to the CM boot image.
Packing recovery inside boot is what's causing all these issues in the first place, so doing what you suggest would be a step forward, but two steps back as well.
Click to expand...
Click to collapse
Yeah maybe but I don't care to much for CM based ROMs was for people using slimlp based mainly
Sent from my Z3 Compact using Tapatalk
jenkins-84 said:
Yeah maybe but I don't care to much for CM based ROMs was for people using slimlp based mainly
Sent from my Z3 Compact using Tapatalk
Click to expand...
Click to collapse
That's all fine and dandy until you realize most people are sticking with CM (for some unexplainable reason). Other ROM gerrits are much more likely to have already merged the needed changes (and are much more lenient and open when it comes to accepting new changes in general, and all this is the only reason this waiting game is now on).
someone755 said:
That's all fine and dandy until you realize most people are sticking with CM (for some unexplainable reason). Other ROM gerrits are much more likely to have already merged the needed changes (and are much more lenient and open when it comes to accepting new changes in general, and all this is the only reason this waiting game is now on).
Click to expand...
Click to collapse
Yeah but I don't wait on slim or use its device trees etc I build for my own and use commits I want, I don't really care what people use or do. I build ROMs for myself and a friend. I just happened to share a ROM that I don't care if people use or not. If I'm happy with what I build and use then that's all I care about
Sent from my Z3 Compact using Tapatalk
jenkins-84 said:
Yeah but I don't wait on slim or use its device trees etc I build for my own and use commits I want, I don't really care what people use or do. I build ROMs for myself and a friend. I just happened to share a ROM that I don't care if people use or not. If I'm happy with what I build and use then that's all I care about
Sent from my Z3 Compact using Tapatalk
Click to expand...
Click to collapse
You do realize TWRP is meant to work for everyone, not just for 'me and my bros'?
On topic:
Someone, that FOTA TWRP I linked does (or at the very least did, I've been on M5 Kernel for a few weeks now) work with a stock Cyanogenmod boot image. Before M5 kernel I could already reach TWRP. I really think it worth a closer look to see what that guy did because it works/worked for some reason..
My full sequence (the first time anyway):
Unlock Bootloader
Unpack boot.img from Cyanogenmod nightly zip
Flash boot.img in fastboot
Boot to Cyanogenrecovery
Wipe
Flash Cyanogenmod in recovery
Boot Cyanogenmod, Setup Wizard yadda yadda
Shut down and go to fastboot
Flash FOTA TWRP from said link
Test FOTA TWRP, Be happy
----Few days later----
Flash M5 through FOTA TWRP

[31.12.2015][TWRP 3.0.0-2][OFFICIAL][TEAM REDUX]TWRP For HTC Explorer

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.
XDA:DevDB Information
TWRP 3.0.0-x OFFICIAL Builds, Tool/Utility for the HTC Pico (Explorer)
Contributors
MSF Jarvis, abhi_qwerty, thewisenerd,Dees_Troy
Source Code: https://github.com/TeamWin/android_device_htc_pico
Version Information
Status: Stable
Current Stable Version: 3.0.0-2
Stable Release Date: 2016-03-22
Created 2015-12-31
Last Updated 2016-03-23
Reserved
Features:
- Material UI thanks to @z31s1g
- F2FS compatible
- Supports OpenRecoveryScript commands placed in /cache/recovery -- Was borked in 2.8.0.0 and 2.8.5.0
- Data backups are now functional; backup sd-ext if you're on one of my ROMs
- Issues with bootloops due to dirty flashes solved. For those on aw3som3 or CM 12.1, use respective images from my TWRP Experiments Thread.
Reserved
Bugs(Currently very minor ones, thank god)
- MTP borked on Arch Linux (reported by @abhi_qwerty)
- USB Storage borked on Windows (tested by me)
Useful Links
- Flashing Guide
- NAND Recovery
MSF Jarvis said:
Since this is an alpha build, I'll need all the feedback I can get. I currently require feedback for whether USB Storage and MTP are working or not. @chankya, wanna help?
Click to expand...
Click to collapse
hey MSF yes both MTP and usb storage worked for me i booted up your cyanogen os build with this recovery that worked too. Let you know if i found any bug :good:
chankya said:
hey MSF yes both MTP and usb storage worked for me i booted up your cyanogen os build with this recovery that worked too. Let you know if i found any bug :good:
Click to expand...
Click to collapse
Thanks. @abhi_qwerty has also confirmed his download. He'll also confirm if they work on Linux.
MSF i tried this on ubuntu 15.10 so it is working on linux don't know about windows
chankya said:
MSF i tried this on ubuntu 15.10 so it is working on linux don't know about windows [emoji14]
Click to expand...
Click to collapse
Means it'll probably work on my Wily Werewolf system too. Will check Windows compatibility at night when Dad comes back from office. Sometimes helps to have a non-techie family[emoji6]
MSF Jarvis said:
Means it'll probably work on my Wily Werewolf system too. Will check Windows compatibility at night when Dad comes back from office. Sometimes helps to have a non-techie family[emoji6]
Click to expand...
Click to collapse
True story :good::good:
Mission accomplished.
USB Storage is dead on Windows 8.1, but MTP works almost as fast as USB Storage. Shouldn't be an issue for anyone.:fingers-crossed:
@abhi_qwerty, have a read of this and then tell if the issue persists.
Does this work with older JB and KitKat ROMs that are not aw3some based?
hrkh83 said:
Does this work with older JB and KitKat ROMs that are not aw3some based?
Click to expand...
Click to collapse
Unfortunately not. But I can cook something up if there's people wanting that.
Edit: Though that'll qualify as unofficial, as it'll be a personal build. That'll show up on the Experiments thread, if ever.
MSF Jarvis said:
Unfortunately not. But I can cook something up if there's people wanting that.
Edit: Though that'll qualify as unofficial, as it'll be a personal build. That'll show up on the Experiments thread, if ever.
Click to expand...
Click to collapse
@MSF Jarvis
Yes.
I would be deeply grateful if you could make a non-aw3som3 based updated TWRP available for me and other users who want to install older ROMs.
hrkh83 said:
@MSF Jarvis
Yes.
I would be deeply grateful if you could make a non-aw3som3 based updated TWRP available for me and other users who want to install older ROMs.
Click to expand...
Click to collapse
Available here
MSF Jarvis said:
Available here
Click to expand...
Click to collapse
@MSF Jarvis
Thank you very much. I am deeply grateful. I will try it and report back.
hrkh83 said:
@MSF Jarvis
Thank you very much. I am deeply grateful. I will try it and report back.
Click to expand...
Click to collapse
Good. I haven't got around to trying this out so testers are appreciated.
hrkh83 said:
@MSF Jarvis
Thank you very much. I am deeply grateful. I will try it and report back.
Click to expand...
Click to collapse
But I don't see any download on it. Are you sure you downloaded the right recovery image??
Sent from my HTC Explorer A310e using Tapatalk
!!!!!!!!!! Serious help needed !!!!!!!!!
I flashed 2.8.7.0 using Rashr(Cause my phone usb somehow got fu*ked up and couldnt do fastboot using pc).
Now I am trying to flash new ROM . It's not allowing boot any ROM, i dint get any error while flashing , success msg is coming but it's not booting up(even I aint seeing any ROM bootanimation) and again TWRP recovery menu is coming. Already tried flashing 4 ROMS no luck :'(
And I also tried flashing new recovery(old version) using 'image' toggle but it's giving 255 error.
Please help me I anit using my mobile and I dnt have any other mobile.
ReX-Hell2heAven said:
!!!!!!!!!! Serious help needed !!!!!!!!!
I flashed 2.8.7.0 using Rashr(Cause my phone usb somehow got fu*ked up and couldnt do fastboot using pc).
Now I am trying to flash new ROM . It's not allowing boot any ROM, i dint get any error while flashing , success msg is coming but it's not booting up(even I aint seeing any ROM bootanimation) and again TWRP recovery menu is coming. Already tried flashing 4 ROMS no luck :'(
And I also tried flashing new recovery(old version) using 'image' toggle but it's giving 255 error.
Please help me I anit using my mobile and I dnt have any other mobile.
Click to expand...
Click to collapse
Which ROM were you using before this?
Sent from my pico using XDA Labs

[RECOVERY] [20.11.2016] Unofficial TWRP for Ulefone Metal - 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-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:
Unofficial TWRP 3.0.2-0 for Ulefone Metal
Mirror 1
MD5 - 10286EE1255C8371A2E5F720896D02C2
SHA-1 - E6C0875ADA34EB1CDE5D5A648D3F8B9AC883EFDA
INSTALLATION:
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 above
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" 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
To install from SP Flash Tools:
1) Download scatter file attached to this post
2) Load scatter file into SPFT
3) Plug USB cable into device and computer
4) Press download in SPFT
5) Reboot device
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
XDA:DevDB Information
RECOVERY] Unofficial TWRP for Ulefone Metal, Tool/Utility for the Android General
Contributors
Jonny
Source Code: https://github.com/JonnyXDA/android_device_ulefone_metal/tree/Omni
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-11-20
Created 2016-10-31
Last Updated 2016-11-20
FAQ:
- None yet!
DEVICE-SPECIFIC CHANGELOGS:
3.0.2-0:
-Fully built from source for Ulefone Metal
Current TWRP "bugs" for Ulefone Metal:
NONE
Thanks for your work.
Recovery not mounting sd card.
Here is log:
Internal build from ulefone forum works.
Mounting sd card works.
Thanks.
here is log:
dropbear2 said:
Internal build from ulefone forum works.
Mounting sd card works.
Thanks.
here is log:
Click to expand...
Click to collapse
Internal? You mean the build I posted there this morning?
Jonny said:
Internal? You mean the build I posted there this morning?
Click to expand...
Click to collapse
Yes, build posted this morning.
dropbear2 said:
Yes, build posted this morning.
Click to expand...
Click to collapse
Cool, I'll update this thread with it in a bit.
This build twrp in downloads (2016-11-02 16:29) does not work.
Is not the same as the build in ulefone forum.
This twrp works: http://ota.cm.mkoas.de:8080/job/TWRP Ulefone Metal/ws/recovery.img
dropbear2 said:
This build twrp in downloads (2016-11-02 16:29) does not work.
Is not the same as the build in ulefone forum.
This twrp works: http://ota.cm.mkoas.de:8080/job/TWRP Ulefone Metal/ws/recovery.img
Click to expand...
Click to collapse
I know, I said I would get round to updating this post as well, I haven't been able to yet as I've been busy
Jonny said:
I know, I said I would get round to updating this post as well, I haven't been able to yet as I've been busy
Click to expand...
Click to collapse
sorry,
I thought that you replaced.
Thread updated with the new links (eventually!).
Apologies for the delay
Hey,
i've flashed TWRP and when i boot it, the phone just shows the ulefone logo and then restarts..
I tried to flash with flashtools and via fastboot flash recovery...
Its possible to flash custom rom, which works quite nice, but TWRP won't come up so i can't root phone or do nandroid backups.
Any help? Any idea how to get logs of what happening?
BTW: reflashed offical stock does the same, displays ulefone logo and reboots..
EDIT:
Flashed recover as boot, and boot as recovery:
Normal boot (should start TWRP now) reboots all the time.
Recovery boot (should boot normal boot.img now) works and boots the System..
So there has to be a problem with the downloaded TWRP/Recovery Image not working on my phone..
It's normal Ulefone Metal don't know why it doesn't work.. wpuld like so see some logs or something
Edit2:
Flashed twrp-3-0-2-4es-by-mdsdev from needrom,
which worked.. don't know why any other one didn't...
I can not find the scatter mentioned in the post. I tried to install it with another scatter or another TWRP, but when I try to run the recovery it simply restarts.
Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.
sinrequilorios said:
Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.
Click to expand...
Click to collapse
It is not my fault if existing ROM's don't flash properly, we faced this problem on Elephone P9000, it is because the people who develop the ROM's don't use the proper mount points, if they did, it would flash. Instead, they use the mount points for the ported recoveries which are not correct.
End of story, not my fault and I will not support the people that this happens to.
sinrequilorios said:
Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.
Click to expand...
Click to collapse
Jonny said:
It is not my fault if existing ROM's don't flash properly, we faced this problem on Elephone P9000, it is because the people who develop the ROM's don't use the proper mount points, if they did, it would flash. Instead, they use the mount points for the ported recoveries which are not correct.
End of story, not my fault and I will not support the people that this happens to.
Click to expand...
Click to collapse
I think here's some confusion. As far as I understand it, it's not a problem of neither the recovery, nor wrong mount points.
There's just a newer revision of the model it seems. This newer models only work with recovery, built against stock pre-built kernel (aka ports).
Our rom is built for being flashed by this recovery, because this recovery is the only compiled one. Unfortunately, there's nothing which can be done without ulefone updating the kernel source code.
DerTeufel1980 said:
I think here's some confusion. As far as I understand it, it's not a problem of neither the recovery, nor wrong mount points.
There's just a newer revision of the model it seems. This newer models only work with recovery, built against stock pre-built kernel (aka ports).
Our rom is built for being flashed by this recovery, because this recovery is the only compiled one. Unfortunately, there's nothing which can be done without ulefone updating the kernel source code.
Click to expand...
Click to collapse
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...
Jonny said:
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...
Click to expand...
Click to collapse
Ug..
GPL source code is provided on our Metal thread...
https://github.com/MediatekAndroidDevelopers/android_kernel_ulefone_metal
Cheers
M.A.D. Team
Jonny said:
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...
Click to expand...
Click to collapse
Of course we didn't build upon your kernel. Why should we have done this?
We are using your recovery, or more detailed, we are suggesting to use your recovery.
What's your problem? We did not disrespect you in any way.
Sent from my Thor using Tapatalk
DerTeufel1980 said:
Of course we didn't build upon your kernel. Why should we have done this?
We are using your recovery, or more detailed, we are suggesting to use your recovery.
What's your problem? We did not disrespect you in any way.
Sent from my Thor using Tapatalk
Click to expand...
Click to collapse
^^ THIS

Categories

Resources