Develop Bugs

[RECOVERY][crespo4g] TWRP 3.0.0-0 touch recovery [2016-02-06]

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.

Changelog - See our website!

FAQ:
How to install with Fastboot:
1. Download the fastboot binary for your computer from HTC
2. Connect your phone and boot it into fastboot
3. Run fastboot with the command
Code:
Code:
fastboot flash recovery path/to/recovery-twrp-crespo4g-1.0.3.img
Error when flashing some zip files:
twrp only supports the latest and greatest edify script for zip flashing. Please bug the zip developer to update the zip script to edify.
Does this back up the WiMAX partition?
That is an option if you chose, but you'll find it under "efs" and not wimax. Both the NS4G and the GSM Nexus S have an efs partition. The efs partition on the NS4G includes WiMAX along with some other fairly crucial data. It's a good idea to back up your efs separately (e.g. just pick efs and don't choose any other partitions) and keep this backup in a safe place.
Live support:
Click this link or join us in #twrp on Freenode IRC.

Yes. Thanks for this. Works great
So how will flashing our backed up images thru fastboot work since they are backed up as .win?
Uncle Jimmy says hello

snandlal said:
Yes. Thanks for this. Works great
So how will flashing our backed up images thru fastboot work since they are backed up as .win?
Uncle Jimmy says hello
Click to expand...
Click to collapse
What partition?
Most are img files just with a different extension some are .tars. You can try it. If it doesn't work you can just restore.

If i go in TWRP on my storage and look at the backed up images like system.win, data.win, boot.win. how would i use that image in fastboot if for some reason i couldnt get to recovery? Rename it to .img?
Uncle Jimmy says hello

The .win files are either .tar or .tgz files (depending on whether you chose compression or not). The backups themselves are usually done with dd. So long as you're not messing with the recovery partition itself and leaving compression turned off, you should be good to go with fastboot flashing, though I don't have a NS4G myself to check.

snandlal said:
If i go in TWRP on my storage and look at the backed up images like system.win, data.win, boot.win. how would i use that image in fastboot if for some reason i couldnt get to recovery? Rename it to .img?
Uncle Jimmy says hello
Click to expand...
Click to collapse
No, you can not fastboot system/data/cache/sd-ext/.android_secure as those are essentially tgz. You can how ever fastboot or dd the others which are boot/recovery/efs by renaming it to .img

AssassinsLament said:
No, you can not fastboot system/data/cache/sd-ext/.android_secure as those are essentially tgz. You can how ever fastboot or dd the others which are boot/recovery/efs by renaming it to .img
Click to expand...
Click to collapse
What? Ok so all im asking is.....the system.win in TWRP, can i rename that system.img and flash thru fastboot?
Uncle Jimmy says hello

snandlal said:
What? Ok so all im asking is.....the system.win in TWRP, can i rename that system.img and flash thru fastboot?
Uncle Jimmy says hello
Click to expand...
Click to collapse
You can fastboot these backups:
boot/recovery/efs
You cannot fastboot these:
system/data/cache/sd-ext/.android_secure
Hope that clears it up.

Dees_Troy said:
You can fastboot these backups:
boot/recovery/efs
You cannot fastboot these:
system/data/cache/sd-ext/.android_secure
Hope that clears it up.
Click to expand...
Click to collapse
Ok thanks. That did clear it up.
Uncle Jimmy says hello

You guys gonna submit this to koushik so it can be flashed in rom manager under "flash alternate recoveries"?

I would love to use this recovery, but unable to push anything on my laptop right now (needs formation). Any flashable scripts?
Sent from my Nexus S 4G using XDA Premium App

info[]box1 said:
I would love to use this recovery, but unable to push anything on my laptop right now (needs formation). Any flashable scripts?
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Use "flash_image gui" by Joeykrim. Apps & Themes section
http://forum.xda-developers.com/showthread.php?t=1122599

snandlal said:
Use "flash_image gui" by Joeykrim. Apps & Themes section
http://forum.xda-developers.com/showthread.php?t=1122599
Click to expand...
Click to collapse
Thanks for help I'll report back.
Edit: it worked thx
Sent from my Nexus S 4G using XDA Premium App

Loving this recovery. Great job teamwin!
Wish all capacitive buttons worked though.

snandlal said:
Use "flash_image gui" by Joeykrim. Apps & Themes section
http://forum.xda-developers.com/showthread.php?t=1122599
Click to expand...
Click to collapse
Please advise: If your using the app do you just select the recovery image option and hit flash file?

very very well done.
would there be a way to implement the option to perform backup/restore via adb like on RA recovery?
I tried it but i am not sure if i remember the command properly I did
Code:
adb shell
# cd /sbin
# nandroid-mobile.sh -b

TheBurgh said:
Please advise: If your using the app do you just select the recovery image option and hit flash file?
Click to expand...
Click to collapse
yeah the first attempt i selected recovery img and manually selected wipe cache. it prompted successful execute, but recovered cwm recovery (no recovery)lol. just rebooted and the second attempt i didnt check wipe cache. all is GOOD now lol.

[email protected] said:
very very well done.
would there be a way to implement the option to perform backup/restore via adb like on RA recovery?
I tried it but i am not sure if i remember the command properly I did
Code:
adb shell
# cd /sbin
# nandroid-mobile.sh -b
Click to expand...
Click to collapse
We don't use nandroid.sh at all. It's not included in our recovery. All of our backups are done in C, so this isn't possible. Sorry.
We didn't base our recovery on CWM or Amon_RA. While we may have used a few bits of code here and there, for the most part we tried to write our own recovery doing things the best way that we thought was possible.

[RECOVERY][p4noterf] TWRP 3.1.1-0 touch recovery [2017-05-19]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Will this work with N0813?
Also should i install it via goo?
Also THANKS!!!
Edit worked awesome!!!
Thanks again, no more buggy cwm!!!!

Yes, Working on GT-N8013
davidrules7778 said:
Will this work with N0813?
Also should i install it via goo?
Also THANKS!!!
Edit worked awesome!!!
Thanks again, no more buggy cwm!!!!
Click to expand...
Click to collapse
Works and Yes install through GOO is fine. Only issue experienced from the install so far is when in recovery trying to type or select sometimes creates double entries or backs out of the function completely. But aside from that it is working as expected.

hkeyman said:
Works and Yes install through GOO is fine. Only issue experienced from the install so far is when in recovery trying to type or select sometimes creates double entries or backs out of the function completely. But aside from that it is working as expected.
Click to expand...
Click to collapse
so awesome to have this on the note.
just wondering, does installing this through goo fix the problem we had with CWM root method where if you boot into recovery it would auto write a script to reinstall the standard recovery? right now i am rooted but because of this bug with the new firmware my CWM is gone and i haven't used the adb instructions to fix it.
once you use TWRP you'll never go back to CWM imo

knives of ice said:
so awesome to have this on the note.
just wondering, does installing this through goo fix the problem we had with CWM root method where if you boot into recovery it would auto write a script to reinstall the standard recovery?
once you use TWRP you'll never go back to CWM imo
Click to expand...
Click to collapse
Not sure, but i got out of that issue with the original clockwork.
Pretty sure it will though

Still rooted...
davidrules7778 said:
Not sure, but i got out of that issue with the original clockwork.
Pretty sure it will though
Click to expand...
Click to collapse
After installing TWRP and using recovery a few times and then rebooting back into system I am not seeing any root/unroot issues. All is working normally here. Which version of the Tablet are you running? I am on the GT-N8013.

hkeyman said:
After installing TWRP and using recovery a few times and then rebooting back into system I am not seeing any root/unroot issues. All is working normally here. Which version of the Tablet are you running? I am on the GT-N8013.
Click to expand...
Click to collapse
I am not having issues at all
Ask the other guy
Sent from a Baked Black Jelly Belly

What I am referring to is with the latest rooting method 2 and if you are on the latest firmware when you reboot the firmware automatically rewrites the cwm image. The only way to stop this is via adb check the instructions below that are to be used in the current method
0) Copy the SU/superSU zip file to your tablet.1) Boot into ODIN mode by holding volume down and power. Volume down is the one closest to power.2) Open ODIN on your computer, select the CWM tar.md5 file in the PDA slot, uncheck auto reboot.3) Hit start. It should flash recovery successfully4) Now you want to boot directly into CWM, or you'll lose it. So while holding down volume UP (the one farther from power), hold down the power button. When you see the Samsung Galaxy Note 10.1 logo, let go of power, or else you'll keep rebooting, but keep holding volume UP. Or at least that's what I had to do, which was kind of surprising coming from other Samsung devices.5) Once in CWM, flash the superSU zip file. Congratulations, you have root, but if you reboot now the firmware will nuke CWM. We don't want to have to flash it again, so let's remove the shell script that nukes CWM.6) Under mounts and storage in CWM, mount system.7) Back on your computer, run adb shell. If you forget to mount system it'll complain because it can't find sh, silly adb. For a second I thought Samsung didn't include sh out of the box and then I realized that makes no sense.8) Type su to become root9) rm /system/etc/install-recovery.sh
So anyways I personally don't know jack squat about adb so I am rooted but don't have cwm installed because it overwrite.
Flashing twrp with goo it flashes for me successfully it claims but when I reboot to recovery I still have stock recovery. I suspect because I didn't do the adb.instructions above that this is the problem
I was hoping flashing this would automatically remove that script you need to remove in adb

knives of ice said:
What I am referring to is with the latest rooting method 2 and if you are on the latest firmware when you reboot the firmware automatically rewrites the cwm image. The only way to stop this is via adb check the instructions below that are to be used in the current method
0) Copy the SU/superSU zip file to your tablet.1) Boot into ODIN mode by holding volume down and power. Volume down is the one closest to power.2) Open ODIN on your computer, select the CWM tar.md5 file in the PDA slot, uncheck auto reboot.3) Hit start. It should flash recovery successfully4) Now you want to boot directly into CWM, or you'll lose it. So while holding down volume UP (the one farther from power), hold down the power button. When you see the Samsung Galaxy Note 10.1 logo, let go of power, or else you'll keep rebooting, but keep holding volume UP. Or at least that's what I had to do, which was kind of surprising coming from other Samsung devices.5) Once in CWM, flash the superSU zip file. Congratulations, you have root, but if you reboot now the firmware will nuke CWM. We don't want to have to flash it again, so let's remove the shell script that nukes CWM.6) Under mounts and storage in CWM, mount system.7) Back on your computer, run adb shell. If you forget to mount system it'll complain because it can't find sh, silly adb. For a second I thought Samsung didn't include sh out of the box and then I realized that makes no sense.8) Type su to become root9) rm /system/etc/install-recovery.sh
So anyways I personally don't know jack squat about adb so I am rooted but don't have cwm installed because it overwrite.
Flashing twrp with goo it flashes for me successfully it claims but when I reboot to recovery I still have stock recovery. I suspect because I didn't do the adb.instructions above that this is the problem
I was hoping flashing this would automatically remove that script you need to remove in adb
Click to expand...
Click to collapse
Actually, you don't need to use ADB, but that was just the fastest way to do it for me. The script doesn't remove root so you can let it boot up and delete the sript using a root file explorer (these days I'm partial to Solid Explorer Beta). But you'll just have to flash CWM a second time if you let it boot up once.

No recovery found using GooManager
I tried installing TWRP through GooManager, but after several minutes of 'Looking for recoveries...' I guess it gave up
Device: GT-N8000 (EU WiFi+3G).

iofthestorm said:
Actually, you don't need to use ADB, but that was just the fastest way to do it for me. The script doesn't remove root so you can let it boot up and delete the sript using a root file explorer (these days I'm partial to Solid Explorer Beta). But you'll just have to flash CWM a second time if you let it boot up once.
Click to expand...
Click to collapse
Thanks.
Seems like goo is down again so as soon as its up we will see if this works

LayZeeDK said:
I tried installing TWRP through GooManager, but after several minutes of 'Looking for recoveries...' I guess it gave up
Device: GT-N8000 (EU WiFi+3G).
Click to expand...
Click to collapse
Did u go into goos menu and select install open recovery?

davidrules7778 said:
Did u go into goos menu and select install open recovery?
Click to expand...
Click to collapse
Of course. I pressed 'Install OpenRecoveryScript', pressed 'Yes', and a dialog box said 'Looking for recoveries...' for several minutes after which it disappeared. But knives of ice says that something is wrong with GooManager.

LayZeeDK said:
Yes, I pressed 'Install OpenRecoveryScript', pressed 'Yes', and a dialog box said 'Looking for recoveries...' for several minutes after which it disappeared. But knives of ice says that something is wrong with GooManager.
Click to expand...
Click to collapse
Yeah the goo servers seem to be down has happened many times in the past. I can't even login to my goo supporter account

There are download links for a mirror and instructions for a manual install on our website.

Dees_Troy said:
There are download links for a mirror and instructions for a manual install on our website.
Click to expand...
Click to collapse
Awesome I got it working now you definitely must delete the file referenced above if you have recently rooted on the latest firmware.
You can also manually flash with mobile Odin if you don't want to use adb like myself while goo is down. Just rename the file to recovery.img

Wanted to say thanks, Dees_Troy! Just picked up a WiFi GT-8013 and this is the first thing I put on it. If you need any help testing or whatnot, feel free to give me a shout and I will test you stuff

Finally got something to flash on this. Anyways it seems like something is messed up with the touchscreen in twrp recovery. Its either much too sensetive or won't scroll at all. Its near impossible to pick a file to flash right now for me anyways if its in a specific folder like downloads
Anyone else?

Yes, i´ve got the same problem, needed 10 minutes yesterday to pick up all the files for cm10 flash...

Same thing here, although I eventually got it to flash. CitizenX, if you flashed CM10, could you report whether your S Pen still works in the CM10 discussion thread? Mine just stopped working with the same errors I was getting last time the S Pen stopped working for me.

[TOOL] [v3.2] [09NOV] Ubuntu Touch "system-image" Installer // w/o computers

[TOOL] [v3.2] [09NOV] Ubuntu Touch "system-image" Installer // w/o computers
# All credit goes to Ubuntu and contributors
ut-system-installer
I wanted to install Ubuntu Touch system-image (official, ro, OTA-enabled, for-sale-in-the-future) on my Galaxy Nexus, but there were some limitations and disadvantages to do so. It requires Ubuntu on my computer and completely wipes my device. Compared to cdimage-touch, which one can install easily with his/her phone, system-image is hard for some people to try, so I made a simple recovery-flashable zip with shell scripts to install it without computer and losing data. It downloads and installs system-image on your device(officially supported ones only).
What is does:
The same thing as doing
Code:
phablet-flash ubuntu-system --channel devel --no-backup
but without wiping the device, so
-Download files for installing Ubuntu Touch system-image (half-automatically)
-Install it on your device (supported ones by Canonical)
Supported Devices:
-Galaxy Nexus (maguro, toro, toroplus)
-Nexus 7 (grouper, tilapia)
-Nexus 4 (mako)
-Nexus 10 (manta)
Downloads:
http://d-h.st/users/zittoro/ut
Do not use anything in wip folder.
* This will install a CWM-based recovery from Ubuntu, and your device could brick but will not be compensated. *
How-to:
1. Download the zip.
2. Unzip it in /sdcard/Download/ut
3. Move or copy ut-system-dl(read "Arguments for "ut-system-dl"" in second post for options) to /data. Then run the script with root(su). You can just type these in terminal instead of doing this step manually (You need busybox and su installed)
Code:
su
cp -a /storage/emulated/0/Download/ut/ut-system-dl /data
sh /data/ut-system-dl
4. Zip everything in /sdcard/Download/ut
5. Flash it in recovery and reboot recovery (Just use the default install menu at home if you are using special recoveries like MultiROM)
6. Enjoy Ubuntu Touch
Bug reports: post your /sdcard/Download/ut/ut-system.log, /cache/recovery/last_log, and copy of the error if possible

Changelogs:
Code:
[b]09NOV2013[/b]
v3.2
-Added official UT disclaimer link
-Cleaner code
[b]07NOV2013[/b]
v3.1
-Support for "generic customization" channels
[b]03NOV2013[/b]
v3
-Support for "*-customized" channels
-More consistent and easier way of configuring files names to download
v2.2
-Download the recovery image properly as saucy-named doesn't exist in the path anymore. --Thanks to @pildoc for reporting.
[b]21OCT2013[/b]
v2.1
-Log file support to the installation script; still need recovery log because of "system-image-installer"
-Support for trusty-related channels
-Workaround for delta images when device files are the same
-Dropped support for old-channel device images
-Workaround for non-patched recoveries
-Show the actual device names rather than codenames to avoid confusion
[b]19OCT2013[/b]
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files
[b]18OCT2013[/b]
v1.2
-Fix for script error
-Aborts installation if script fails
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad:(
-Added log file: ut-system.log
[b]16OCT2013[/b]
v1
-Initial
Arguments for "ut-system-dl":
-$1: -auto: default for script, automatically detects the device's codename using the value for "ro.build.product"
-DEVICE_NAME: images for DEVICE_NAME devices
-$2: -full: default for script, full images used for initial installation
-delta: delta images used for updates(OTA)
-$3: -CHANNEL: use CHANNEL channel to download images, default "devel"
-$4: -BUILD_NUMBER: build number of image

I dont get it
Sent from my Nexus 4 using xda app-developers app

gazhead said:
I dont get it
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It basically installs the recommended version of ubuntu touch

Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl

hockeyadc said:
Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl
Click to expand...
Click to collapse
Dang I made a mistake

Zittoro said:
Dang I made a mistake
Click to expand...
Click to collapse
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?

hockeyadc said:
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?
Click to expand...
Click to collapse
Can you get a screenshot for me?

Zittoro said:
Can you get a screenshot for me?
Click to expand...
Click to collapse
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?

hockeyadc said:
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?
Click to expand...
Click to collapse
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.

Zittoro said:
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.
Click to expand...
Click to collapse
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?

hockeyadc said:
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?
Click to expand...
Click to collapse
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery

Zittoro said:
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery
Click to expand...
Click to collapse
Awesome!

hockeyadc said:
Awesome!
Click to expand...
Click to collapse
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?

Zittoro said:
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?
Click to expand...
Click to collapse
I haven't tried yet. I realized how many apps I need and use on a daily basis, so I would rather not install it yet. Just gonna wait it out until Ubuntu is more complete.

Changelogs:
18OCT2013
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad
-Added log file: ut-system.log
v1.2
-Fix for script error
-Aborts installation if script fails

Blur
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..

subaash said:
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..
Click to expand...
Click to collapse
1. Download the zip from the link
2. Unzip it to the specified directory on your phone (you can do this with a file explorer app)
3. Download a terminal app and copy and paste the "code" into it.
4. If you get an error, post your /sdcard/Download/ut-system.log. If you don't, zip everything in the specified folder and flash it in recovery
5. Reboot recovery right after the installation

Changelogs:
19OCT2013
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files

Will this work with kulturom(nexus7) AS secondary ROM?
Wysłane z mojego Nexus 7 przy użyciu Tapatalk

[DEV][RECOVERY][callisto] TWRP Recovery 2.7.0.0

TWRP Recovery
For Galaxy 551
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
 @chraso: For Hosting & giving compatible flags.
Me: Compiling work.

CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.

DOWNLOAD:
https://drive.google.com/file/d/0B5c3gpyMBJusRzkzd2FTanVsNmM/edit?usp=sharing .
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!

About the current build:
First build. Test everything, though if it boots, it must be fully stable.

Thanks for your nice work every thing is working well.

(removed)

I had been using CWM 6.0.5.3 with CM11.0 on my Callisto for a while, but since virtually every other phone of mine runs TWRP, I gave it a try.
I installed the recovery.img as suggested, via adb shell.
I was able to boot into TWRP, and backup my whole phone - I had planned to upgrade the ROM. While that failed (fs size too big), I tried to go back, so I restored the whole set and rebooted into system...
... only to see TWRP again. There was no way out - I had to flash CWM again, and reboot into that, then reboot system. Now everything seems to be fine, but I'm hesitant to touch TWRP again.
What may have happened, causing the system boot to immediately (no boot animation) hand over to TWRP? boot.img wasn't affected (fortunately), otherwise flashing CWM over TWRP wouldn't have helped in an instant.
Puzzled... Should I try 2.6 instead?

Bhargav97 said:
DOWNLOAD:
https://drive.google.com/file/d/0B5c3gpyMBJusRzkzd2FTanVsNmM/edit?usp=sharing .
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
Click to expand...
Click to collapse
Where am I supposed to write those commands to install the recovery?? I tried this app but no command works, even 'help' doesn't do anythink... What am I doing wrong??

[TOOL/UTILITY][TWRP][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 5/11

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
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.
DOWNLOAD & HOW-TO INSTALL:
--------- On Device ---------
1) Download the latest recovery.img from Android File Host
2) Use Flashify to flash the recovery.img
(How to use flashify)
1) Grant Root Access
2) Click "Recovery image"
3) Click "Choose a file"
4) Select the img you just downloaded and when prompted to flash, press "Yep"
5) When it offers you to reboot, select "Yep"
------------------------------------------------------------------
--------- Odin (On Windows PC) ---------
1) Download the recovery.tar from Android File Host
2) Open Odin and click the "AP" button and select the .tar file you downloaded
3) Boot your phone into download mode (hold Volume Down + Home + Power)
4) When prompted, press the Volume Up button to continue
5) Connect your device to your PC and press Start
6) Once your device is finished booting, shut it off
7) Once your device is completely off, press and hold Volume up + Home + Power until you get a "recovery is not seenforcing" message in red at the upper left hand of your screen
-----------------------------------------------------------------------------​
XDA:DevDB Information
TeamWin TWRP Recovery for the Sprint Samsung Galaxy S6 (SM-G920P)
Contributors
tvm2487 - TWRP Compiler
1619415 - Thread Maintainer
And TeamWin (duh)
Version Information: 3.0.2-0
Status: Stable
Last Updated May 10th, 2016​
XDA:DevDB Information
[TOOL/UTILITY][TWRP][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 5/10, Tool/Utility for the Sprint Samsung Galaxy S6
Contributors
1619415, tvm2487
Version Information
Status: Stable
Created 2016-05-10
Last Updated 2016-05-10

We love you, man. No homo
Sent from my SM-G920P using Tapatalk

Thank you guys! Keep up the good work!

asafegous said:
We love you, man. No homo
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Lol

Excellent job TeamSpr. Much appreciated. Sadly, not working the Edge yet

iam assuming this will also work for boost mobile,?

nyfl2004 said:
Excellent job TeamSpr. Much appreciated. Sadly, not working the Edge yet
Click to expand...
Click to collapse
If the good folks that built the modified version would share the device tree, I can help unify it with the Edge ( I don't have an edge, but can help @nyfl2004 extract the necessary blobs, et al, to build the Edge in).
Did you start with this by chance? https://github.com/TeamWin/android_device_samsung_zerofltespr

It won't flash for me....it gets most of the way through and then it fails.

Euronymous88 said:
It won't flash for me....it gets most of the way through and then it fails.
Click to expand...
Click to collapse
What version of Odin are you using? I personally use the one linked above which worked fine. Make sure you have enabled OEM Unlocking under Dev options. Also, make sure that you don't bump the cable or anything while flashing I suggest that you just plug it in lay it on a flat surface and just let it run.

1619415 said:
What version of Odin are you using? I personally use the one linked above which worked fine. Make sure you have enabled OEM Unlocking under Dev options. Also, make sure that you don't bump the cable or anything while flashing I suggest that you just plug it in lay it on a flat surface and just let it run.
Click to expand...
Click to collapse
That's what I normally do. I've used Odin many times...I'm using the latest version of Odin. Just seeing if anyone else had the same problem.

tdhite said:
If the good folks that built the modified version would share the device tree, I can help unify it with the Edge ( I don't have an edge, but can help @nyfl2004 extract the necessary blobs, et al, to build the Edge in).
Did you start with this by chance? https://github.com/TeamWin/android_device_samsung_zerofltespr
Click to expand...
Click to collapse
I have already built it for the edge, please pm me on how you rooted!
Sent from my SM-G925P using Tapatalk

Euronymous88 said:
That's what I normally do. I've used Odin many times...I'm using the latest version of Odin. Just seeing if anyone else had the same problem.
Click to expand...
Click to collapse
You can just untar it and that will give you the image. For example, in linux:
Code:
tar xvf New_S6_Spr_TWRP_MM_Bootloader2.tar
That will give you a file called "recovery.img"
Then copy that file to your phone, adb shell in, type "su" at the shell prompt (which will ask you for permission, of course, so grant it); then 'dd' it to the recovery partition as described in the section "dd Install Method (Requires Root)" at https://twrp.me/devices/samsunggalaxys6sprint.html.
You don't need Odin to install TWRP in most cases.

Once you successfully flash TWRP...all you need to do for root is flash SuperSU 2.68.

So soon we will have the TeamSpr v2 rite ?
Sent from my SM-G920P using Tapatalk

TaNuXzx said:
So soon we will have the TeamSpr v2 rite ?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
V3.0.0-1 we just added the "-1" that way you guys know that this is the updated and working version

1619415 said:
V3.0.0-1 we just added the "-1" that way you guys know that this is the updated and working version
Click to expand...
Click to collapse
i mean the rom . sorry ?
Sent from my SM-G920P using Tapatalk

I Installed thru Flashify,only Because the wife was on the computer gaming. It worked made a backup flashed xposed modules turned on now thanks.

Great work TeamSpr. Works great on my s6 phone. Thx
Sent from my SM-G920P using Tapatalk

Not taking, still on default recovery
Hi,
Just checking if others see this:
1) turn on oem unlocking (even off then on again to assure it's on);
2) load up Odin3 v3.10.7 (used this to flash twrp in LL, works fine, also used to return to stock and take OTA);
3) turn off R. Reset Time;
4) Flash New_S6_Spr_TWRP_MM_Bootloader2.tar
It just reboots to stock MM, then if I force to recover, it's still stock recovery.
?? Anyone have a clue on that one? I can get to stock recovery and reboot to system still, but sheesh -- no take of the Odin flash of TWRP? Not enough knowledge in my head around Odin for that one if anyone has some help.

tdhite said:
Hi,
Just checking if others see this:
1) turn on oem unlocking (even off then on again to assure it's on);
2) load up Odin3 v3.10.7 (used this to flash twrp in LL, works fine, also used to return to stock and take OTA);
3) turn off R. Reset Time;
4) Flash New_S6_Spr_TWRP_MM_Bootloader2.tar
It just reboots to stock MM, then if I force to recover, it's still stock recovery.
?? Anyone have a clue on that one? I can get to stock recovery and reboot to system still, but sheesh -- no take of the Odin flash of TWRP? Not enough knowledge in my head around Odin for that one if anyone has some help.
Click to expand...
Click to collapse
Turn on Reset time and try the Odin included in This zip