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

Search This thread
By:
Advanced…
R

roadmutt

New member
Jun 25, 2014
3
0
broken usb port flashing recovery

so i have been infected with what seems to be a common broken usb port on my nexus aswell and honestly it doesnt bother me that much except i wanted to know how sketchy it was if even possible to flash recovery say via ADB wifi ? if anyone has any experience in attempting this lemme know thanks
 
Black_Hat01

Black_Hat01

Senior Member
May 10, 2017
86
123
roadmutt said:
so i have been infected with what seems to be a common broken usb port on my nexus aswell and honestly it doesnt bother me that much except i wanted to know how sketchy it was if even possible to flash recovery say via ADB wifi ? if anyone has any experience in attempting this lemme know thanks
Click to expand...
Click to collapse
Not sketchy at all really, assuming decent internet connection...plus you do normally flash recovery via fastboot, not even sure how to with ADB. I think your best bet is flashify or flashfire if you are rooted.
 
R

roadmutt

New member
Jun 25, 2014
3
0
Black_Hat01 said:
Not sketchy at all really, assuming decent internet connection...plus you do normally flash recovery via fastboot, not even sure how to with ADB. I think your best bet is flashify or flashfire if you are rooted.
Click to expand...
Click to collapse

depends on the phone i guess i use whatevers convenient ADB, odin, kies, i found some binary write tool aswell cant recall the name of it but its for ubuntu (linux) i dont even recall if its designed to be a flash tool but it most certainly was the most unbiased one ive used ALTHOUGH you have to be super careful with it quadruple check everything cuz if you make a mistake with that there is no coming back your phone doesnt know it has a power button anymore type of stuff
 
G

Gad12

New member
Nov 20, 2017
1
0
:)

---------- Post added at 07:50 AM ---------- Previous post was at 07:43 AM ----------

T_q
I

---------- Post added at 08:03 AM ---------- Previous post was at 07:50 AM ----------

T:highfive:
 
D

Dhalsim43

Senior Member
Dec 14, 2016
302
76
Last edited:
  • Like
Reactions: babykut
D

duttyend

Senior Member
Dec 18, 2012
465
354

Thank you so much for the 3.2.1-0 update ! :good:

It would be great if you could also update the thread title so that more people are aware of it.

Have a great day
 
S

Super_SU01

Senior Member
Jan 14, 2018
431
35
Isn't it funny I had all my files downloaded that I needed to root and unlock my Nexus 6 and they just up and vanished like a fart n the wind..
 
ktmom

ktmom

Retired Forum Moderator
Apr 22, 2015
5,179
3,383
Deep Space Station K7
Super_SU01 said:
Isn't it funny I had all my files downloaded that I needed to root and unlock my Nexus 6 and they just up and vanished like a fart n the wind..
Click to expand...
Click to collapse
Did you unlock the bootloader with the files on your device? If so, that's where they went. Unlocking the bootloader wipes the user data.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
 
II_DiE_4

II_DiE_4

Senior Member
Dec 12, 2007
613
259
yoheidiho said:
Anyone have a working 3.2.1 with f2fs support for the Nexus 6? I've been using 3.1.1-6 without issue but could not enter recovery after I flashed 3.2.1.
Click to expand...
Click to collapse
Well, IMHO, f2fs isn't worth it. Not a single, repeatable evidence that its faster. On the contrary, its a headache, especially if encrypted. Also, our device, and google android in general, are made around ext4. Stick with that.
 
  • Like
Reactions: duttyend
Y

yoheidiho

New member
May 2, 2010
3
1
OnePlus 8T
II_DiE_4 said:
Well, IMHO, f2fs isn't worth it. Not a single, repeatable evidence that its faster. On the contrary, its a headache, especially if encrypted. Also, our device, and google android in general, are made around ext4. Stick with that.
Click to expand...
Click to collapse

Too late for that. I have been using f2fs for the past 6+ months without issue.

I'd rather not wipe my device to upgrade from LOS 14.1 to LOS 15.1. Now that begs me to inquire if TWRP 3.1.1-6 can support LOS 15.1 which is based on Oreo 8.1.

Does anyone have experience with 3.1.1-x, especially 3.1.1.6, with Oreo 8.1.
 
ethanhunt123

ethanhunt123

Senior Member
Aug 6, 2010
199
33
Charleston, SC
yoheidiho said:
Too late for that. I have been using f2fs for the past 6+ months without issue.

I'd rather not wipe my device to upgrade from LOS 14.1 to LOS 15.1. Now that begs me to inquire if TWRP 3.1.1-6 can support LOS 15.1 which is based on Oreo 8.1.

Does anyone have experience with 3.1.1-x, especially 3.1.1.6, with Oreo 8.1.
Click to expand...
Click to collapse

Yea I was able to install it using 3.1.1. You have to modify the install zip script so the that script doesn't asset the device name. Otherwise you'll get a Error 7 when installing via twrp. Google videos on linage os and getting around Error 7
 
ethanhunt123

ethanhunt123

Senior Member
Aug 6, 2010
199
33
Charleston, SC
yoheidiho said:
Too late for that. I have been using f2fs for the past 6+ months without issue.

I'd rather not wipe my device to upgrade from LOS 14.1 to LOS 15.1. Now that begs me to inquire if TWRP 3.1.1-6 can support LOS 15.1 which is based on Oreo 8.1.

Does anyone have experience with 3.1.1-x, especially 3.1.1.6, with Oreo 8.1.
Click to expand...
Click to collapse

Also I ended up converting back to ext4 with a process similar to this one: https://forum.xda-developers.com/oneplus-one/general/guide-formatting-ext4-to-f2fs-losing-t3352116

and just caved in and flashed the official 3.2.1 twrp.
 
  • Like
Reactions: duttyend
You must log in or register to reply here.

Similar threads

Jubakuba
  • Locked
[Shamu][2015/NOV/12] SlimLP 5.1.1 beta 0.12 / [2016/MAY/15] Slim6 alpha 0.1
Replies
4K
Views
512K
Yank555
Yank555
spaceman860
  • Locked
[ROM][Official][6.0.1][Shamu] Dirty Unicorns v10.6 [DU TBO GAPPS]
Replies
3K
Views
444K
Joseph
Joseph
razorloves
[ROM][OFFICIAL] LineageOS 14.1 for Nexus 6 (shamu)
Replies
2K
Views
337K
R
runekock
Elektroschmock
[ROM][(Un)OFFICIAL] LineageOS 15.1 for Nexus 6 (shamu)
Replies
3K
Views
298K
shabang3773
shabang3773
rascarlo
  • Locked
[ROM] RASTAPOP[Android 5.1.0_r1 LMY47D] [PRODUCT_DEVICE := shamu]
Replies
1K
Views
201K
matt4321
matt4321

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 191
    Dees_Troy
    Dees_Troy
    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.




    CHANGELOG for 3.0.2-0:

    -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.
    View
    50
    Dees_Troy
    Dees_Troy
    At least running the stock ROM from Google, the Nexus 6 is *ALWAYS* encrypted even if you did not set up encryption. It uses "default_password" as the default password. TWRP can decrypt this and will do so automatically if the default_password is in use.

    If you have not unlocked your bootloader, you will need to do so. Hold volume up and down while turning the device on. You will be in the bootloader. Do a "fastboot oem unlock" followed by a "fastboot reboot" from your computer to unlock. This will wipe all of your data including internal storage so back up anything you might want first. If you do not fastboot reboot before installing TWRP, you will probably have to perform a "Format Data" from within TWRP. It is highly recommended that you let the device boot normally immediately after doing the fastboot oem unlock and wait to install TWRP after the first successful boot after the unlock.

    Device specific page on our website.

    Download link for current and past versions.
    View
    24
    z31s1g
    z31s1g
    2.8.7.1 Bugfix update

    2.8.7.1 Update is ready for download.

    It fixes the decryption issue, some vendor files where missing in the .0 build.

    https://dl.twrp.me/shamu/

    PresidentMcCain said:
    Looks like TWRP 2.8.7.0 does not decrypt data correctly. It fails to decrypt after trying to enter my pattern. Flashed back to TWRP 2.8.6.0 and it worked immediately.
    Click to expand...
    Click to collapse
    Thunderbolt69 said:
    I also had the same issue when trying TWRP 2.8.7.0 and had to flash back to the previous version.
    Click to expand...
    Click to collapse
    ironjon said:
    Yes exactly same here
    Click to expand...
    Click to collapse
    View
    23
    z31s1g
    z31s1g
    TWRP 3.0.0-1 Unofficial with system image support

    So I built a version for Shamu that includes the ability to backup and restore system images. One can also flash system images from factory image sets.

    https://www.androidfilehost.com/?fid=24407100847294345

    I've tested this version on an encrypted device.
    The screenshot shows the console output of the test:

    1. created a backup of system, data and boot
    2. created a backup of system image
    3. wiped system
    4. restored system image
    I'll go ahead and try do the same for hammerhead, flo and manta.



    starcms said:
    ...
    Click to expand...
    Click to collapse
    View
    19
    Elting
    Elting
    New Version!
    https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img.html
    View

New posts