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.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
Direct device link
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, 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.
Releases including and past 3.0.2-2 will work on both the L and M bootloader. The screen update issues plaguing unofficial 3.0.0 do not happen on these newer builds either. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
Don't you love the smell of success in the morning? :laugh:
Finally, official status!
Nice! Nice! Nice!
Time for me to get some more roms out I guess
ro.product.device missing?
Not sure if I'm an isolated case for this, but I couldn't flash anything with this recovery because the updater script in ROMs would fail at ro.product.device, basically instead of shieldtablet being there it was blank. Went back to unofficial TWRP and now no problems.
Can anyone care to confirm if this is an issue with the official recovery image?
DaveTheRave said:
Not sure if I'm an isolated case for this, but I couldn't flash anything with this recovery because the updater script in ROMs would fail at ro.product.device, basically instead of shieldtablet being there it was blank. Went back to unofficial TWRP and now no problems.
Can anyone care to confirm if this is an issue with the official recovery image?
Click to expand...
Click to collapse
Yes, It is an issue I am working on.. :good:
Thx for the feedback, I will be posting a working version soon..
Thx Josh
EDIT:
Can I get some feedback on this, seems to be working as expected... :good:
Changelog:
Remove vendor init, cm is able to install now.
TWRP 2.8.7.1 DOWNLOAD LINK !!
Thx Josh
Hi Josh,
I'm trying to use the TWRP build on my new replacement device (received it last Monday). All I've done since unboxing is set a PIN and enable encryption. On booting, the /data partition isn't mounted, with the following error:
Code:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
I tried using the
Code:
adb shell twrp decrypt <pin>
command to decrypt using adb, but get the following response:
Code:
Attempting to decrypt data partition via command line.
E:No crypto support was compiled into this build.
This is with both the 2.8.7.0 official build, and the 2.8.7.1 build you reference above. Is it possible to get crypto support enabled please?
el3ctrik said:
Hi Josh,
I'm trying to use the TWRP build on my new replacement device (received it last Monday). All I've done since unboxing is set a PIN and enable encryption. On booting, the /data partition isn't mounted, with the following error:
Code:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
I tried using the
Code:
adb shell twrp decrypt <pin>
command to decrypt using adb, but get the following response:
Code:
Attempting to decrypt data partition via command line.
E:No crypto support was compiled into this build.
This is with both the 2.8.7.0 official build, and the 2.8.7.1 build you reference above. Is it possible to get crypto support enabled please?
Click to expand...
Click to collapse
Yes, this is a HUGE issue.....
I need to look at making this happen....
Thx Josh
EDIT:
Ok lets give this a go
Changelog:
Added decryption support.
TWRP 2.8.7.2 DOWNLOAD LINK !!
Thx Josh
The recovery does not work with the Nvidia shield k1 tablet. It cant write to the system partition.
philipp21897 said:
The recovery does not work with the Nvidia shield k1 tablet. It cant write to the system partition.
Click to expand...
Click to collapse
I am going to need just a bit more
Please run: adb pull /tmp/recovery.log
Upload or pastebin the output
Thx Josh
I'm a bit confused - how does this version relate (or not) to the version released in this previous thread?:
http://forum.xda-developers.com/showthread.php?t=2877117
Is it that this version has official status compared to the other (and is a newer version as well - 2.8.7.2 vs. 2..8.7.1 as of this post)?
Sent from my SHIELD Tablet using XDA Free mobile app
Correct. This is officially available on the TWRP website. The unofficial one should be almost exactly the same, but I don't think I've ever seen the device tree it was built from, so I can't say for certain.
@lj50036: I'm probably blind, but I can't find the source you're using for newer builds? Is it in a public repo somewhere? I'll want to pull the decryption support into the multirom twrp builds since I assume it's not enabled there either. Haven't tried, though.
An Droid said:
I'm a bit confused - how does this version relate (or not) to the version released in this previous thread?:
http://forum.xda-developers.com/showthread.php?t=2877117
Is it that this version has official status compared to the other (and is a newer version as well - 2.8.7.2 vs. 2..8.7.1 as of this post)?
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
I started with a similar device tree, but did some cleaning up
The device tree is linked in post #2
Thx Josh
Steel01 said:
Correct. This is officially available on the TWRP website. The unofficial one should be almost exactly the same, but I don't think I've ever seen the device tree it was built from, so I can't say for certain.
@lj50036: I'm probably blind, but I can't find the source you're using for newer builds? Is it in a public repo somewhere? I'll want to pull the decryption support into the multirom twrp builds since I assume it's not enabled there either. Haven't tried, though.
Click to expand...
Click to collapse
Dont forget to check gerrit...
http://gerrit.twrp.me/#/c/1115/
Thx Josh
lj50036 said:
Dont forget to check gerrit...
http://gerrit.twrp.me/#/c/1115/
Click to expand...
Click to collapse
Oh duh. Though I'm not certain why I had to register to even look at it? Meh.
*peruses changesets*
*is skeptical that it will work right*
I put the vendor init in to make all the recoveries and roms run across all models. And I think just about every rom uses it now. Without it... I suppose most popular roms will install since they assert as shieldtablet. But if someone has one specifically for wx_na_wf or such, that won't work. Do you know why the vendor init isn't running? It works on my multirom twrp builds built in an omni 5.1.1 tree. But if you really want to revert to a non-unified build, you should add the fingerprints back and probably split to three separate builds, one for each model.
Also, why is selinux being removed? Won't that break labeling on install? Is there a bug/missing rule I'm missing?
The decryption support seems simple enough, one line. I'll pull that in tomorrow and credit you and the review for it. Maybe I can finagle a formatted patch into my repo to keep authorship and all.
Steel01 said:
Oh duh. Though I'm not certain why I had to register to even look at it? Meh.
*peruses changesets*
*is skeptical that it will work right*
I put the vendor init in to make all the recoveries and roms run across all models. And I think just about every rom uses it now. Without it... I suppose most popular roms will install since they assert as shieldtablet. But if someone has one specifically for wx_na_wf or such, that won't work. Do you know why the vendor init isn't running? It works on my multirom twrp builds built in an omni 5.1.1 tree. But if you really want to revert to a non-unified build, you should add the fingerprints back and probably split to three separate builds, one for each model.
Also, why is selinux being removed? Won't that break labeling on install? Is there a bug/missing rule I'm missing?
The decryption support seems simple enough, one line. I'll pull that in tomorrow and credit you and the review for it. Maybe I can finagle a formatted patch into my repo to keep authorship and all.
Click to expand...
Click to collapse
Ok, that is a lot to take in......
I am more then willing to work with anyone that is willing to work with me.....
I am still learning everyday...
If you would like to join us on irc feel free, that is going to be the best for me....
Thx Josh
lj50036 said:
If you would like to join us on irc feel free, that is going to be the best for me...
Click to expand...
Click to collapse
Sure, I can do that. Which channel? I don't know twrp's infrastructure.
Steel01 said:
Sure, I can do that. Which channel? I don't know twrp's infrastructure.
Click to expand...
Click to collapse
TWRP IRC
Network: freenode
Channel: #twrp
Thx Josh
EDIT:
Huge thx to @Steel01 for all his help with this project..... :good:
Changelog:
Reforked kernel source, vendor init is working as expected....
TWRP 2.8.7.3 DOWNLOAD LINK !!
Thx Josh
Hi Josh - just had a chance to test 2.8.7.3 on my encrypted device and working perfectly.
Thanks!
lj50036 said:
TWRP IRC
Network: freenode
Channel: #twrp
Thx Josh
EDIT:
Huge thx to @Steel01 for all his help with this project..... :good:
Changelog:
Reforked kernel source, vendor init is working as expected....
TWRP 2.8.7.3 DOWNLOAD LINK !!
Thx Josh
Click to expand...
Click to collapse
did you already saw this?
http://forum.xda-developers.com/showthread.php?p=64143425
ti fix just define the props correctly via override (i dont know if its shield or shieldtab or anything like that )
Sent from my Xperia T using XDA Free mobile app
Related
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
ReverendJKR posted a great video on TWRP and Goo Manager working together.. Much more to come with this relationship
http://youtu.be/OA0S275XO3U
Oh man. Awesome!
Looks nice...looking forward to trying it out.
This looks very slick!
Sent from space
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Super cool, thanks guys, I am now into Nook Color... HD2, AMAZE 4G...
Jainyankee1993 said:
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
We have a list of supported devices on the main twrp2 page: http://teamw.in/project/twrp2
So I see you got that stuck in recovery bug all worked out ehh? nice work.
eyeballer said:
TeamWin is proud to present TWRP 2.0 for Nook Color!!
Click to expand...
Click to collapse
Congrats TeamWin... this is supercool.
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
hm, anyway to install this on an existing install?
Midnitte said:
hm, anyway to install this on an existing install?
Click to expand...
Click to collapse
Right from their page? Though idk what kernel they are talking about.
Download the above file. Connect your Nook Color to the PC via the USB cable. This assumes you have working ADB.
Execute the following:
adb shell busybox remount / -o rw,remount
adb shell busbbox mkdir /boot
adb shell busybox mount /dev/block/mmcblk0p1 /boot
adb push twrp-encore-2.0.0RC0.ub /boot/uRecRam <--- You can change uRecRam to uAltRam for alternate boot.
adb push kernel /boot/uRecImg
adb shell busybox umount /boot
Click to expand...
Click to collapse
RileyGrant said:
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
Click to expand...
Click to collapse
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
eyeballer said:
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
Click to expand...
Click to collapse
Actually what I thought, thanks for clarifying man .
Oooh, i look forward to trying this.
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
bobtidey said:
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
Click to expand...
Click to collapse
I had to do the same thing. Kept getting an error that "applet not found" for busybox in adb.
Thanks for the alternate method.
This is a much better implementation of our hardware in backup.
Thanks TeamWin.
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
It wasn't there before! I swear! /thanks
Hm, is usb storage working for anyone?
The only thing I don't really care for is... and I know I am doing things in a unique way....
I have SASD with CM7 on it... verygreen's recovery as alt-boot and replaced CWM with TWRP as recovery mode on the uSD... when in TWRP and reboot... it boots stock on eMMC instead of a normal boot... it should do a normal boot (uSD first)
Ok guys, im awful at writing tutorials so i spent the past hour or so looking for the best one, as a few of you have pm'd me asking me to tell you guys how to build recoveries:
First, let's check out the CyanogenMod tree. The CyanogenMod repository contains Clockwork Recovery, which is part of a full Android build.
repo init -u git://github.com/CyanogenMod/android.git -b ics-release
repo sync
make -j4 otatools
Now, use dump_image or dd to dump your recovery or boot image from a running phone and copy it to your computer somewhere.
dump_image boot boot.img
To build Android from source for a new device, you need to set up a board config and its makefiles. This is generally a long and tedious process. Luckily, if you are only building recovery, it is a lot easier. From the root of your Android source directory (assuming you've run envsetup.sh), run the following (substituting names appropriately):
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
You will receive the confirmation "Done!" if everything worked. The mkvendor.sh script will also have created the following directory in your Android source tree:
manufacturer_name/device_name
Now, type the following:
lunch full_device_name-eng
This will set the build system up to build for your new device. Open up the directory in a file explorer or IDE. You should have the following files: AndroidBoard.mk, AndroidProducts.mk, BoardConfig.mk, device_.mk, kernel, system.prop, recovery.fstab, and vendorsetup.sh.
The two files you are interested in are recovery.fstab and kernel. The kernel in that directory is the stock one that was extracted from the boot.img that was provided earlier. For the most part, recovery.fstab will work on most devices that have mtd, emmc, or otherwise named partitions. But if not, recovery.fstab will need to be tweaked to support mounts and their mount points. For example, if your /sdcard mount is /dev/block/mmcblk1p1, you would need the following lines in your BoardConfig.mk:
/sdcard vfat /dev/block/mmcblk1p1
Once the recovery.fstab has been properly setup, you can build the recovery using:
make -j4 recoveryimage
Your recovery can then be found at $OUT/recovery.img. If you are in need of building a fakeflash recovery, you will need to run the following to create the update.zip that hot replaces the recovery:
make -j4 recoveryzip
Once this is done, build, and tested, notify me, "koush", on Github and I can build official releases and add ROM Manager support!
Tip: Run "make clobber" between builds if you change the BoardConfig.mk, or the change will not get picked up.
Credits to Koush and his tutorial here
Hey Lloir was just checking your guide (I'm from the X8 scene). The funniest bit was "Notify...me, "koush"". I guess it's a typo. Anyways good guide.
I think you guys should look into getting Lloir a dev Desire X, he could do a lot more for you guys if he actually had the device
He has done some great work on the One V, including porting both CM9 and CM10, and he could do the same over here for you guys. I'm just dropping by to say that I vouch for Lloir He also has his own ROM in the works
Hopefully you can snag one of these devices soon Lloir, its always nice to get a fun device to play around on and to develop CM for
thanks for that endorsement Rohan, didn't expect that at all..
Lloir said:
thanks for that endorsement Rohan, didn't expect that at all..
Click to expand...
Click to collapse
I tried to compile a CWM based on gingerbread to get the earlier version of nandroid backups, but I just can't get it to work. Props and thanks again for making a CWM 6 for us, without it, we'd be nowhere
Thanks
Hi,
I managed to successfully built CWM using your guide.
It kinda works but i did not adjust recovery.fstab so i get errors saying failed to find cache partition to mount at /cache and some related to recovery.log.
Anyways, have you found the reason for the graphical glitch yet??
Thanks for the guide, it helped me to get started.
Got CWM working (still testing) for my rk3066 based tablet.
One thing I could not figure out - what to does one need to put into recovery.fstab to be able to mount a USB stick from CWM?
hi
Jin^eLD said:
Thanks for the guide, it helped me to get started.
Got CWM working (still testing) for my rk3066 based tablet.
One thing I could not figure out - what to does one need to put into recovery.fstab to be able to mount a USB stick from CWM?
Click to expand...
Click to collapse
On github, find a device tree with similar setup (a similar tab with option for mounting sd card) and use its fstab as reference. You'll also need to add BOARD_LUN_PATH or TARGET_LUN_FILE_PATH or something like that in the BoardConfig.mk of your device to make USB mounting work. Hope it helps.
Regards
Yasir
Yasir Javed Ansari said:
On github, find a device tree with similar setup (a similar tab with option for mounting sd card) and use its fstab as reference. You'll also need to add BOARD_LUN_PATH or TARGET_LUN_FILE_PATH or something like that in the BoardConfig.mk of your device to make USB mounting work. Hope it helps.
Regards
Yasir
Click to expand...
Click to collapse
Yasir, that was one of the things I noticed about the CM9 boardconfig : the paths you just mentioned need fixing
yes, i fixed it, then broke it again.... now figuring out what broke it
any ideea how i can build a touch recovery?
---------- Post added at 03:13 PM ---------- Previous post was at 03:11 PM ----------
neXus PRIME said:
Hi,
I managed to successfully built CWM using your guide.
It kinda works but i did not adjust recovery.fstab so i get errors saying failed to find cache partition to mount at /cache and some related to recovery.log.
Anyways, have you found the reason for the graphical glitch yet??
Click to expand...
Click to collapse
it it cannot find cache partition, the fstab is not correct
for the graphics, what are the bugs?
dany547 said:
any ideea how i can build a touch recovery?
---------- Post added at 03:13 PM ---------- Previous post was at 03:11 PM ----------
it it cannot find cache partition, the fstab is not correct
for the graphics, what are the bugs?
Click to expand...
Click to collapse
The method lloir posted is from koush, it needs some tweaking to work properly. Are you interested in building one yourself?
Compile from a new device
Hello,
I have a BLU Dash 3.5 and would like to build recovery.
I followed the steps in the guide and compilation errors did not return put the recovery did not work. The phone connects but gets the BLU logo on the screen.
The ADB recognizes the device.
The / system / data / cache / sdcard and / sd-ext is mounted correctly.
but the phone's screen does not pass soon.
I noticed that the ROM Manager can make and restore backups normally.
What am I doing wrong?
dump_image
i tried dump_image of boot boot terminal emulator says dump_image not found... i m running jelly bean 4.1.2 Samsung gt-s5282
After a long time of trying to get things right, i finally got things right.
So here it is:
TWRP RECOVERY 3.2.1-0 FOR THE MOTO X FORCE (KINZIE)
This is an actual port and not a recompile of a different version for another device.
It is not yet official but i intend to submit my device tree, so it gets official.
It is probably never going to be official, but i'll try and provide frequent updates.
Everything *should* work, as far as i was able to test.
I am not sure about encryption though, as i have not encrypted my device, nor do i intend to do so atm.
Encryption should be ok now. (TWRP team has put a lot of effort in this).
Encrypted partitions cannot be read atm.
This would probably also work for the Droid 2 Turbo, if someone finds a way to unlock the BL.
I will try to maintain TWRP for this device, fixes may take a while though as i am not having a lot of time to work on this.
Installation:
1. Unlock your device
2. Download the image
3. Power off the phone
4. Boot to fastboot (VOL DN + POWER)
5. plug your usb cable install via fastboot:
Code:
fastboot flash recovery TWRP_3.2.1-0_Kinzie.img
If you want to keep OTA Update ability you can also temporary boot to TWRP. You would have to repeat this step everytime you want to go to TWRP then:
Code:
fastboot boot TWRP_3.2.1-0_Kinzie.img
Download here:
Version 3.2.1-0
http://www.mediafire.com/file/o6gcj4hhjahf936/TWRP_3.2.1-0_Kinzie.img
Version 3.1.1-0
http://www.mediafire.com/file/y2k08c6m5tazhbo/TWRP_3.1.1-0_Kinzie.img
Version 3.1.0-0
https://www.mediafire.com/?7h4u37ddiohwy45
Credits go out to the people of Teamwin Recovery project for creating this nice piece of software!
And credits go to @Arasthel, who is a great dev!
Official Changelog 3.2.1-0
Fixes for kinzie:
- USB OTG now working
- TWRP internal folder should be now accessible via /sdcard symlink
- cm updater is reporting device correctly now as kinzie
Amazing, the most beautiful and wanted TWRP version! Tested and working perfectly! Using it as my recovery, not boot only.
Enviado de meu XT1580 usando Tapatalk
Awesome! It's cool to have an actual port and to know that you will try to maintain it so we can have future updates .
I'm curious, though. What is the difference between this and clark recovery? Did you build it with the latest motorola kernel, which includes msm8994 support or make some BoardConfig changes? I mean, they share the same config and base kernel, at least, the basics that make TWRP work - wifi and other modules are a whole different story, but they are not needed for recovery.
Arasthel said:
Awesome! It's cool to have an actual port and to know that you will try to maintain it so we can have future updates .
I'm curious, though. What is the difference between this and clark recovery? Did you build it with the latest motorola kernel, which includes msm8994 support or make some BoardConfig changes? I mean, they share the same config and base kernel, at least, the basics that make TWRP work - wifi and other modules are a whole different story, but they are not needed for recovery.
Click to expand...
Click to collapse
To be honest, differences are marginal at this point, as of now we've got the fstabs by-name assignments there is almost no way of messing things up with partition assignments (which is kinda the no. 1 thing to do right in recovery). At the moment i am still using a prebuilt kernel and ramdisk i extracted from the device, because when i started building the device tree the kernel sources haven't been available. And when they finally were i decided to first fix the issues i already had, before introducing new ones. The whole graphics sub routines of TWRP (minuitwrp) recently had undergone a pretty big overhaul and so we've lost ability to flip screen on the way. I recently made a patch to fix this for overlay devices (which the kinzie is), and since then, TWRP is running fine on the native kinzie build. The overhaul also made the use of a custom graphics.c obsolete. (I suspect you had to use that?) I made the device tree mostly from scratch, only looking at similiarities at trees from hima and clark. (Hima has msm8994 too, clark has a different chipset as you know, but is a moto device).
You can have a look at it here. Please note that this is not absolute latest configuration (haven't uploaded it yet) and it still needs a little cleanup before submission. After that, i am going to throw in kernel sources from motorola and fetch the prebuilts necessary.
If you are interested in learning more you can contact me via PM.
Just flashed and working 100%. Moto X force BR version.
Thx a lot dude :good: just flashed and working.
no more upside/down issue :silly:
and nice theme btw
Thanks a lot mate! working as expected.
Perfect and beauty one! Thanks!
Xadro, just to let you know that the OTG is not working yet. Tried several things but no good yet. If you need some one to test some workarounds just let me know.
marzliak said:
Xadro, just to let you know that the OTG is not working yet. Tried several things but no good yet. If you need some one to test some workarounds just let me know.
Click to expand...
Click to collapse
I'll look into it as soon as I can. Might also be a general issue in twrp.
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
fubofo said:
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
Click to expand...
Click to collapse
Are you talking of the external sd card (sdcard1)? Or the internal emulated one?
Moderator Edit: @MuyKurioso - it is not necessary or desirable to quote the entire OP. Some users have limited bandwidth or are Mobile - this can affect page load times. Please consider this in the future. Thanks.
Are you currently trying to port CM to Kinzie? Or just waiting to help out someone? Just curious, and thanks for all your hard work in this recovery!
fubofo said:
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
Click to expand...
Click to collapse
You need root to look inside that folder, you need to access through data/media/0/TWRP you probably did not give superuser permissions to your file manager.
Does this work for the turbo 2?
Xadro said:
Are you talking of the external sd card (sdcard1)? Or the internal emulated one?
Click to expand...
Click to collapse
I have backed up to the internal emulated sdcard.
I wanted to sync the folder and backup to my NAS
Sent from my XT1580 using Tapatalk
---------- Post added at 10:16 AM ---------- Previous post was at 10:13 AM ----------
AztekSoul said:
You need root to look inside that folder, you need to access through data/media/0/TWRP you probably did not give superuser permissions to your file manager.
Click to expand...
Click to collapse
It is accessible through TWRP file manager.
I did try with root permissions in ES File Explorer. Although i haven't tried that directory - is it a symlink?
Sent from my XT1580 using Tapatalk
fubofo said:
It is accessible through TWRP file manager.
I did try with root permissions in ES File Explorer. Although i haven't tried that directory - is it a symlink?
Click to expand...
Click to collapse
/sdcard is a symlink to /data/media/0/. The explanation why it isnt accessible in /sdcard is simple. The folder is not owned by media_rw.
To fix this, navigate to /data/media/0 in ES File Explorer. Then highlight TWRP folder by long touching it. Go to properties and change owner and group of the folder to media_rw. This should fix access rights when trying to access the folder via /sdcard symlink.
Xadro said:
/sdcard is a symlink to /data/media/0/. The explanation why it isnt accessible in /sdcard is simple. The folder is not owned by media_rw.
To fix this, navigate to /data/media/0 in ES File Explorer. Then highlight TWRP folder by long touching it. Go to properties and change owner and group of the folder to media_rw. This should fix access rights when trying to access the folder via /sdcard symlink.
Click to expand...
Click to collapse
Thanks, managed to chown the directory in terminal emulator. All works great now, thanks
Sent from my XT1580 using Tapatalk
Hello @Xadro!
I tested new Clark TWRP 3.0.0-1 version (twrp-3.0.0-1-clark.img) in my MOTO X FORCE and everything worked perfect (except MTP in my case). I believe this new version could be a good base for a Kinzie recovery. What do you think?
rodrigoger said:
Hello @Xadro!
I tested new Clark TWRP 3.0.0-1 version (twrp-3.0.0-1-clark.img) in my MOTO X FORCE and everything worked perfect (except MTP in my case). I believe this new version could be a good base for a Kinzie recovery. What do you think?
Click to expand...
Click to collapse
There is something for you in the OP
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.
Note 1/19/18: I fixed OTG in 3.2.1-0. Since the LineageOS kernel for the VS995 is known to have broken OTG, I went back to my good old reliable 10b source. I stripped down the options as much as I could to reduce the file size. It seems to be working well. Unfortunatly the only way to tell them apart is the file size or md5.
Old: 24,637,440 bytes / MD5 - ca8bb67c07a81fe17f463eeaacd7c096
New: 24,653,824 bytes / MD5 - d2b25849241b9524b838a11bb0a39093
Here's the build info from the old builds for those looking for breadcrumbs, etc.
OK, this is the first time I've built TWRP so I'm sure there are some issues. Please use this at your own risk. I've done some very basic testing and it seems to work OK for my purposes. I do not plan to build for anything other than the VS995. For other devices I'll lay out my basic workflow in hopes that those still working on other devices can do the same.
Basically I followed the guide here: https://forum.xda-developers.com/showthread.php?t=1943625
Since I already have the LineageOS repositories (with proprietary files from here) installed on my machine, I started with the code from here: https://github.com/omnirom/android_bootable_recovery
I found out LineageOS doesn't have busybox so I added that to my LineageOS system/external folder from here: https://github.com/omnirom/android_external_busybox
Since it failed to build with encryption, I cherry-picked this commit: https://gerrit.omnirom.org/#/c/22096/
I added the recover.fstab from here to the device folder for the vs995: https://github.com/jcadduono/android_device_lge_vs995/tree/android-6.0/recovery/root
Here are the extra lines and flags I added to my default LineageOS BoardConfig.mk
Code:
RECOVERY_VARIANT := twrp
PRODUCT_COPY_FILES += device/lge/vs995/twrp.fstab:recovery/root/etc/twrp.fstab
TW_THEME := portrait_hdpi
RECOVERY_SDCARD_ON_DATA := true
TW_INCLUDE_CRYPTO := true
That's pretty much everything I've done.
Note to developers: This recovery is a true VS995 build. Please add vs995 to your zips asserts.
Know issues:
- ROMs, kernels, mods, etc. whose zips are built with 'elsa' and/or 'vs996' only asserts will not flash. This is not a bug. If your zip tells you it's for another device and not a vs995, please ask the developer to add this to their asserts.
Download: VS995 TWRP 3.2.1-0
Device tree/kernel source
Old Builds:
VS995 TWRP 3.2.0-0
TWRP 3.2.1-0 Changelog
Code:
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Thank you very much, even though I don't own a VS995 it's always good to see new development. Thanks again OP.
Link gives me "Access Denied"
wally86 said:
Link gives me "Access Denied"
Click to expand...
Click to collapse
I (think I) fixed it. Please try again.
BackCheck said:
I (think I) fixed it. Please try again.
Click to expand...
Click to collapse
Working now!
I just received my vs995. I'm gonna downgrade to 12A from 15A with uppercut, when use dirtysanta. Should I use twrp 3.0.2-1 like in the guide then then update to 3.2.0-0 or just use 3.2.0-0?
Thanks
wally86 said:
Working now!
I just received my vs995. I'm gonna downgrade to 12A from 15A with uppercut, when use dirtysanta. Should I use twrp 3.0.2-1 like in the guide then then update to 3.2.0-0 or just use 3.2.0-0?
Thanks
Click to expand...
Click to collapse
I would 100% use the 3.0.2-1 from the thread. It has been well tested. From there is you're looking to use a custom kernel or flash a custom rom, then you might test 3.2.0-0. Like I said in the OP, this is the first time I've ever messed with compiling TWRP.
BackCheck said:
I would 100% use the 3.0.2-1 from the thread. It has been well tested. From there is you're looking to use a custom kernel or flash a custom rom, then you might test 3.2.0-0. Like I said in the OP, this is the first time I've ever messed with compiling TWRP.
Click to expand...
Click to collapse
Alright sounds good. I'm gonna try resurrection remix & weta with this version and I'll report back in a few days with how it's working.
Awesome, thanks for keeping the development alive!
Awesome thanks so much. Downloading now. You're great!
Any idea if this is available on the H918 (T-mobile)?
jaysonic88 said:
Any idea if this is available on the H918 (T-mobile)?
Click to expand...
Click to collapse
To the best of my knowledge, there is no 3.2.0 TWRP for the H918, 3.1.1 is the most recent build for it.
This works perfectly with VS995. Thank you!
Any idea how to make this for H990DS ?
Zenns said:
Any idea how to make this for H990DS ?
Click to expand...
Click to collapse
Between the links I posted in the OP and this there are enough breadcrumbs for someone to start building it. That someone isn't me but I would gladly offer advice if needed.
BackCheck said:
Between the links I posted in the OP and this there are enough breadcrumbs for someone to start building it. That someone isn't me but I would gladly offer advice if needed.
Click to expand...
Click to collapse
So I followed your guide (thanks btw!) and successfully compiled twrp 3.2 for the h910 (att) variant. There are some issues for me though. First the terminal in twrp constantly says "child process exited" when I try to type anything in. Also when installing stuff there's a red warning saying "error mount -o bind data/media/0 error 2" or something similar. In the file manager I can access that partition and see files there. Backup and restore seems to work and I tested a couple of magisk zips and they all flashed successfully. Was wondering if you had seen anything like that.
toastyp said:
So I followed your guide (thanks btw!) and successfully compiled twrp 3.2 for the h910 (att) variant. There are some issues for me though. First the terminal in twrp constantly says "child process exited" when I try to type anything in. Also when installing stuff there's a red warning saying "error mount -o bind data/media/0 error 2" or something similar. In the file manager I can access that partition and see files there. Backup and restore seems to work and I tested a couple of magisk zips and they all flashed successfully. Was wondering if you had seen anything like that.
Click to expand...
Click to collapse
Good job. And no, my first build had completely different errors. If you want to PM me your fstab and board config I might be able to look over it sometime and see if I can see anything. Those 2 files look like good places to start.
So I've gone and gotten a sorta working us996 build. Definitely took a couple trys, and my first attempt wiped /data (thanks LG, but this is why I keep backups!) Since I didn't have TW_IGNORE_MISC_WIPE_DATA set. It doesn't have USB otg support like the old 3.0.2 build does (neither does Lineage, but the old build and stock does). I plan on looking at cleaning up my fstab or whatever so that the sdcard is labeled nicely (has internal storage and then storage0 - storage4 with the sdcard being one of those). Havnt tried backups/restoring yet, nor any sort of encryption, but flashing a new lineage build, gapps, and magisk worked. Slightly annoyed I can't build lineage and twrp at the same time (using brunch it pukes out an error about not being able to find some library twrp builds in it's applypatch directory, granted paraphrasing errors doesn't help much) but whatever I can toggle back and forth.
Phoenix591 said:
So I've gone and gotten a sorta working us996 build. Definitely took a couple trys, and my first attempt wiped /data (thanks LG, but this is why I keep backups!) Since I didn't have TW_IGNORE_MISC_WIPE_DATA set. It doesn't have USB otg support like the old 3.0.2 build does (neither does Lineage, but the old build and stock does). I plan on looking at cleaning up my fstab or whatever so that the sdcard is labeled nicely (has internal storage and then storage0 - storage4 with the sdcard being one of those). Havnt tried backups/restoring yet, nor any sort of encryption, but flashing a new lineage build, gapps, and magisk worked. Slightly annoyed I can't build lineage and twrp at the same time (using brunch it pukes out an error about not being able to find some library twrp builds in it's applypatch directory, granted paraphrasing errors doesn't help much) but whatever I can toggle back and forth.
Click to expand...
Click to collapse
I share your pain on the errors with brunch, I get that too. What are you using for fstab? If your using the fstab from jcadduono then OTG is in the file, then it's in there. I don't use OTG so I'm not sure it or encryption is working in mine either. I need testers.
BackCheck said:
I share your pain on the errors with brunch, I get that too. What are you using for fstab? If your using the fstab from jcadduono then OTG is in the file, then it's in there. I don't use OTG so I'm not sure it or encryption is working in mine either. I need testers.
Click to expand...
Click to collapse
No it isn't in jc's fstab, looks like USA-RedDragon has it in his, https://github.com/DesolationRom-Devices/device_lge_h910twrp?files=1 . Going to take a closer look in a day or so.
Well, I got USB otg working, just not the way I hoped. I grabbed the prebuilt kernel image from the repo in my last post and that did the trick when using his fstab as well. So it's probably a kernel problem, since it didn't work with his fstab alone. I tried enabling the more obviously named USB otg kernel config options without success.
[RECOVERY] TWRP 3.5.0-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
flame Device Config: https://github.com/bigbiff/android_device_google_coral
DOWNLOAD:
Please go to https://twrp.me to download the device image.
A11 Testing:
https://build.twrp.me/test/flame/twrp-3.6.0-0-test1-flame.img- updated for lineage-18.1 booting
Old info:
Hello, this is a test build for flame users (will work on coral crosshatch/blueline later). The image is pretty safe for backing up now.
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.
Not working: sideload and fastbootd
May FW Date https://build.twrp.me/test/flame/twrp-3.3.1-0-test1-flame.img
June FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test2-flame.img
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test4-flame.img
- fix super partition restore
- fix persist partition restore
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test5-flame.img
- allow repacking of TWRP boot.img
- magisk currently doesn't work
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test6-flame.img
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test7-flame.img
- fix repacking TWRP with magisk
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test8-flame.img
- multiuser decryption support
- fastbootd support
3.5.0-0: Android 11 bringup
https://build.twrp.me/test/flame/twrp-3.5.0-0-test1-flame.img
https://build.twrp.me/test/flame/twrp-3.5.0-0-test2-flame.img
- Titan M Wipe working on Format Data
- Apex fixes for flattened directories
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a Coral/Flame TWRP base
http://twrp.me
What to backup
* super
* data
* persist
* boot
* any other partition desired
What to restore
* super
* data
* boot - depending on ROM support
Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.
Repacking TWRP into Boot partition
To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
1. adb push <latest_boot.img> /sdcard/
2. reboot to bootloader and fastboot latest boot.img of TWRP
3. Go to Install
4. Touch Install Image
5. Select your boot.img from /sdcard
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation
TWRP won't Boot?
Make sure you have a kernel that supports the R DTBO and LZMA ramdisk starting with test5 such as https://forum.xda-developers.com/pi...nel-kirisakuraq-1-0-0-pixel-4-xl-aka-t3992213
Is this just for flame? Or both coral and flame? Reason I ask is because the 2 devices have significant differences, and if it's just for flame, you'll want to throw it in the regular Pixel 4 subforum
This is for flame as described. I will work on coral next.
They share the same device tree btw.
Weird I thought I chose pixel 4 forum. Asking for this thread to be moved.
bigbiff said:
Weird I thought I chose pixel 4 forum. Asking for this thread to be moved.
Click to expand...
Click to collapse
Ah man lol got me all excited!
Thanks long awaited :good:
Will try later..
ok fastboot boot boots fine to TWRP but decryption wont work for me
https://paste.omnirom.org/view/e9536f05
Can confirm this works for flashing. Booted the image and then ADB pushed magisk and kernel and both flashed successfully!
Will try removing lockscreen security next attempt to gain access to internal storage which should likely work.
Great work to see, we are finally not tied to magisk for flashing things now
Mrcactuseater said:
Will try removing lockscreen security next attempt to gain access to internal storage which should likely work.
Click to expand...
Click to collapse
wont work to @my end
2WildFirE said:
Thanks long awaited :good:
Will try later..
ok fastboot boot boots fine to TWRP but decryption wont work for me
https://paste.omnirom.org/view/e9536f05
Click to expand...
Click to collapse
Can you paste logcat output too?
Please guys don't just say it doesn't work. I need recovery.log and logcat so I can debug issues.
2WildFirE said:
wont work to @my end
Click to expand...
Click to collapse
Can you please post recovery.log and logcat?
bigbiff said:
Can you please post recovery.log and logcat?
Click to expand...
Click to collapse
Yep
Is ADB logcat -l the correct one?
2WildFirE said:
Yep
Is ADB logcat -l the correct one?
Click to expand...
Click to collapse
I usually do in adb shell
logcat > /tmp/logcat.txt
Then adb pull /tmp/logcat.txt
OK here logcat https://paste.omnirom.org/view/9caa8b33
And recovery.log https://paste.omnirom.org/view/3c26a706
hope it helps
2WildFirE said:
OK here logcat https://paste.omnirom.org/view/9caa8b33
And recovery.log https://paste.omnirom.org/view/3c26a706
hope it helps
Click to expand...
Click to collapse
Can you tell me your android build version?
bigbiff said:
can you tell me your android build version?
Click to expand...
Click to collapse
qq3a.200605.001
just to thank you a lot bigbiff for putting so much work and efforts on this, you are great. hope you can sort this out, best luck!! (a p3 user) :fingers-crossed::good: sorry for the ot
2WildFirE said:
qq3a.200605.001
Click to expand...
Click to collapse
There was an update to the platform version, please test https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
bigbiff said:
There was an update to the platform version, please test https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
Click to expand...
Click to collapse
Thanks will try :good:
@bigbiff
yeah decryption works fine now
@bigbiff
Sorry for dump questions, but if I want to backup, is it enough to backup super and data partition?