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

Search This thread
By:
Advanced…
Poor Grammar

Poor Grammar

Senior Member
Aug 2, 2013
492
78
chattanooga tn
LG Nexus 5X
OnePlus 6T
?...Well guys the bottom part of my screen stopped working couple years ago so I can't swipe in twrp (Known issue). I remember using multirom twrp awhile back but links are dead now anyone know of a twrp without touch that I can use to flash a current ROM... I'm stuck on 5.1 at the moment which keeps freezing up also outdated... Edit:? After flashing twrp 2.3.2.3 the digitizer works and I can swipe now. What's up with that...I haven't tried to install a ROM yet or if it will work
 
Last edited:
nitin.chobhe

nitin.chobhe

Recognized Contributor
Jan 3, 2013
8,298
19,955
India
Google Pixel 2 XL
Google Pixel 7 Pro
WelfareBaby said:
?...Well guys the bottom part of my screen stopped working couple years ago so I can't swipe in twrp (Known issue). I remember using multirom twrp awhile back but links are dead now anyone know of a twrp without touch that I can use to flash a current ROM... I'm stuck on 5.1 at the moment which keeps freezing up also outdated... Edit:? After flashing twrp 2.3.2.3 the digitizer works and I can swipe now. What's up with that...I haven't tried to install a ROM yet or if it will work
Click to expand...
Click to collapse
Well, if it's only the bottom part of your screen, then you can follow these steps to resize the TWRP UI - thanks to @ze7zez

I had the same issue and I was able to flash using TWRP with modified UI.

Nitin
 
  • Like
Reactions: plegdroid
Poor Grammar

Poor Grammar

Senior Member
Aug 2, 2013
492
78
chattanooga tn
LG Nexus 5X
OnePlus 6T
nitin.chobhe said:
Well, if it's only the bottom part of your screen, then you can follow these steps to resize the TWRP UI - thanks to @ze7zez

I had the same issue and I was able to flash using TWRP with modified UI.

Nitin
Click to expand...
Click to collapse
Oh wow that's a awesome trick. Now I got to figure out how to do those steps lol I got lost on 3rd step ...I should know how to do this by now?,....Thanks Nitin I will figure this out tell ya that... Thanks@ ze7zez also:good:
 
Poor Grammar

Poor Grammar

Senior Member
Aug 2, 2013
492
78
chattanooga tn
LG Nexus 5X
OnePlus 6T
ze7zez said:
If you do what I asked Nitin for, I will help you tonight.
Click to expand...
Click to collapse
☺...Thanks for fast and helpful reply right after I posted I flashed a 8.1 ROM using the 2.3.2.3 twrp...(Stupid I know) well I been stuck in a bootloop since,Lol Finally managed to get 5.1,stock rooted today...Hope the screenshot ain't to bad that's the best one I can get since my buttons acting up..Blank area goes all the way up just case you was wondering
 

Attachments

  • Screenshot_2019-11-19-22-19-24.png
    Screenshot_2019-11-19-22-19-24.png
    22.9 KB · Views: 135
Last edited:
Poor Grammar

Poor Grammar

Senior Member
Aug 2, 2013
492
78
chattanooga tn
LG Nexus 5X
OnePlus 6T
ze7zez said:
So you have an inactive area like an inverted letter T.
You can use my setting.
Click to expand...
Click to collapse
Yep pretty much... So do I have to create a directory in twrp /follow the steps you mentioned or is resolution in a newer twrp version? Sorry this over my head a little..By the way I took the easy way out in this community and used tool kits to get me out of jams...I have tried though to get adb but gave up after drivers wasn't installing correctly...Anyway that's my story and I'm sticking to it..:cowboy:....I'll still take the offer when you get time
 
Last edited:
Poor Grammar

Poor Grammar

Senior Member
Aug 2, 2013
492
78
chattanooga tn
LG Nexus 5X
OnePlus 6T
Trying to flash twrp using fastboot/ adb.. After downloading the twrp image website says copy the file into same folder as adb/fastboot binaries and then Rename to twrp.IMG....fastboot flash recovery twrp.IMG. is this the right location? First time doing this unlocked bootloader yesterday...Late Bloomer I know...
 

Attachments

  • IMG_20191130_184238.jpg
    IMG_20191130_184238.jpg
    254 KB · Views: 66
CamoGeko

CamoGeko

Retired Forum Moderator
Dec 10, 2010
15,978
8,371
Establishing Battlefield Control... Standby!
Nexus 7
Essential Phone
Poor Grammar said:
Trying to flash twrp using fastboot/ adb.. After downloading the twrp image website says copy the file into same folder as adb/fastboot binaries and then Rename to twrp.IMG....fastboot flash recovery twrp.IMG. is this the right location? First time doing this unlocked bootloader yesterday...Late Bloomer I know...
Click to expand...
Click to collapse

Yes that is the right place.

If you add ADB/Fastboot to your Windows Environment variables then you can run those commands from any directory. Of course you would have to them define where the IMG is located, whereas its not needed in this case.
 
  • Like
Reactions: TheIntruder
Waldold

Waldold

Member
Aug 22, 2020
29
8
Google Nexus 4
After updating from the old (3.2.x) to the latest TWRP (3.4.) Nexus 4 doesn't reboot nor shut down properly from recovery menu (reboots again to recovery, not to system), you need to hold power button and shut down smartphone. Is it only my problem or anybody else face the same?
 
ze7zez

ze7zez

Recognized Contributor
Aug 24, 2012
5,358
2
3,273
Center of psychoacoustic space
nz.geoview.info
Samsung Galaxy S III I9300
HTC Leo
7

7wells

Senior Member
Oct 9, 2019
212
19
Google Nexus 4
Lenovo Thinkpad Tablet
The previous TWRP version 3.3.1-0 for the Nexus 4 (mako) correctly (re)boots as intended. I confirm that (for me) the problem with not being able to (re)boot into recovery or bootloader (but instead into itself) started with the latest TWRP version 3.4.0-0, so I went back to 3.3.1-0. And yes, the workaround works, too.

How can TWRP be used on an encrypted Nexus 4 for backup? Because of the encryption (and TWRP not being able to decrypt the /Data partition), there is no target to save the backup to. I thought that maybe via adb something is possible, but I have bo clue how. Something like this?
Code: 
adb pull /dev/block/mmcblk0 mmcblk0.img
But how do I know which are which partitions? With adb shell I can see these:
Code: 
brw-------    1 root     root      179,   0 Sep 22 14:18 mmcblk0
brw-------    1 root     root      179,   1 Sep 22 14:18 mmcblk0p1
brw-------    1 root     root      179,  10 Sep 22 14:18 mmcblk0p10
brw-------    1 root     root      179,  11 Sep 22 14:18 mmcblk0p11
brw-------    1 root     root      179,  12 Sep 22 14:18 mmcblk0p12
brw-------    1 root     root      179,  13 Sep 22 14:18 mmcblk0p13
brw-------    1 root     root      179,  14 Sep 22 14:18 mmcblk0p14
brw-------    1 root     root      179,  15 Sep 22 14:18 mmcblk0p15
brw-------    1 root     root      179,  16 Sep 22 14:18 mmcblk0p16
brw-------    1 root     root      179,  17 Sep 22 14:18 mmcblk0p17
brw-------    1 root     root      179,  18 Sep 22 14:18 mmcblk0p18
brw-------    1 root     root      179,  19 Sep 22 14:18 mmcblk0p19
brw-------    1 root     root      179,   2 Sep 22 14:18 mmcblk0p2
brw-------    1 root     root      179,  20 Sep 22 14:18 mmcblk0p20
brw-------    1 root     root      179,  21 Sep 22 14:18 mmcblk0p21
brw-------    1 root     root      179,  22 Sep 22 14:18 mmcblk0p22
brw-------    1 root     root      179,  23 Sep 22 14:18 mmcblk0p23
brw-------    1 root     root      179,  24 Sep 22 14:18 mmcblk0p24
brw-------    1 root     root      179,  25 Sep 22 14:18 mmcblk0p25
brw-------    1 root     root      179,   3 Sep 22 14:18 mmcblk0p3
brw-------    1 root     root      179,   4 Sep 22 14:18 mmcblk0p4
brw-------    1 root     root      179,   5 Sep 22 14:18 mmcblk0p5
brw-------    1 root     root      179,   6 Sep 22 14:18 mmcblk0p6
brw-------    1 root     root      179,   7 Sep 22 14:18 mmcblk0p7
brw-rw----    1 system   system    179,   8 Sep 22 14:18 mmcblk0p8
brw-rw----    1 system   system    179,   9 Sep 22 14:18 mmcblk0p9
Code: 
/dev/block # cat /proc/partitions
major minor  #blocks  name

 179        0   15388672 mmcblk0
 179        1      65536 mmcblk0p1
 179        2        512 mmcblk0p2
 179        3        512 mmcblk0p3
 179        4       2048 mmcblk0p4
 179        5        512 mmcblk0p5
 179        6      22528 mmcblk0p6
 179        7      22528 mmcblk0p7
 179        8        780 mmcblk0p8
 179        9        780 mmcblk0p9
 179       10        780 mmcblk0p10
 179       11        512 mmcblk0p11
 179       12        512 mmcblk0p12
 179       13        512 mmcblk0p13
 179       14       2048 mmcblk0p14
 179       15        512 mmcblk0p15
 179       16        512 mmcblk0p16
 179       17        512 mmcblk0p17
 179       18        512 mmcblk0p18
 179       19      16384 mmcblk0p19
 179       20      16384 mmcblk0p20
 179       21    1406852 mmcblk0p21
 179       22      26747 mmcblk0p22
 179       23   13798400 mmcblk0p23
 179       24        512 mmcblk0p24
 179       25        495 mmcblk0p25
Code: 
/dev/block/platform/msm_sdcc.1 # ls -al by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x    2 root     root           540 Sep 22 14:18 .
drwxr-xr-x    4 root     root           600 Sep 22 14:18 ..
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 DDR -> /dev/block/mmcblk0p24
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 abootb -> /dev/block/mmcblk0p15
lrwxrwxrwx    1 root     root            20 Sep 22 14:18 boot -> /dev/block/mmcblk0p6
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 grow -> /dev/block/mmcblk0p25
lrwxrwxrwx    1 root     root            20 Sep 22 14:18 m9kefs1 -> /dev/block/mmcblk0p8
lrwxrwxrwx    1 root     root            20 Sep 22 14:18 m9kefs2 -> /dev/block/mmcblk0p9
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 metadata -> /dev/block/mmcblk0p18
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx    1 root     root            20 Sep 22 14:18 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 persist -> /dev/block/mmcblk0p20
lrwxrwxrwx    1 root     root            20 Sep 22 14:18 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 rpm -> /dev/block/mmcblk0p11
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 rpmb -> /dev/block/mmcblk0p16
lrwxrwxrwx    1 root     root            20 Sep 22 14:18 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx    1 root     root            20 Sep 22 14:18 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 sbl2b -> /dev/block/mmcblk0p13
lrwxrwxrwx    1 root     root            20 Sep 22 14:18 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 sbl3b -> /dev/block/mmcblk0p14
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 system -> /dev/block/mmcblk0p21
lrwxrwxrwx    1 root     root            20 Sep 22 14:18 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 tzb -> /dev/block/mmcblk0p17
lrwxrwxrwx    1 root     root            21 Sep 22 14:18 userdata -> /dev/block/mmcblk0p23
Code: 
 ~ # ./parted /dev/block/mmcblk0 p
Model: MMC 016G92 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name      Flags
 1      524kB   67.6MB  67.1MB  fat16        modem
 2      67.6MB  68.2MB  524kB                sbl1
 3      68.2MB  68.7MB  524kB                sbl2
 4      68.7MB  70.8MB  2097kB               sbl3
 5      70.8MB  71.3MB  524kB                tz
 6      71.3MB  94.4MB  23.1MB               boot
 7      94.4MB  117MB   23.1MB               recovery
 8      117MB   118MB   799kB                m9kefs1
 9      118MB   119MB   799kB                m9kefs2
10      119MB   120MB   799kB                m9kefs3
11      120MB   121MB   524kB                rpm
12      121MB   121MB   524kB                aboot
13      121MB   122MB   524kB                sbl2b
14      122MB   124MB   2097kB               sbl3b
15      124MB   124MB   524kB                abootb
16      124MB   125MB   524kB                rpmb
17      125MB   125MB   524kB                tzb
18      125MB   126MB   524kB                metadata
19      126MB   143MB   16.8MB               misc
20      143MB   159MB   16.8MB  ext4         persist
21      159MB   1600MB  1441MB  ext2         system
22      1600MB  1627MB  27.4MB  ext4         cache
23      1627MB  15.8GB  14.1GB               userdata
24      15.8GB  15.8GB  524kB                DDR
25      15.8GB  15.8GB  507kB                grow
Now I wonder which other partitions should I backup (if I knew how ;)) in order to be able to revert back to the "original" LOS 17.1 (incl. OpenGApps + my settings) if needed?


PS: I managed to backup to /sdcard. See there:
https://xdaforums.com/showpost.php?p=83556127&postcount=332
 
Last edited:
ze7zez

ze7zez

Recognized Contributor
Aug 24, 2012
5,358
2
3,273
Center of psychoacoustic space
nz.geoview.info
Samsung Galaxy S III I9300
HTC Leo
You must log in or register to reply here.

Similar threads

franciscofranco
[KERNEL][GPL][N4] franco.Kernel - r217
Replies
58K
Views
11M
D
Draketech
C
[ROM][Official][4.2.2] CyanogenMod 10.1 Nightlies for the Nexus 4 (mako)
Replies
14K
Views
3M
VinceCZ
VinceCZ
faux123
[Kernel] (ver 041) Mako KK 4.4 (UV/OTG/CPU/GPU OC/Hybrid Linux 3.4+) [08-02-14]
Replies
17K
Views
3M
B
bubbleguuum
mskip
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - NEXUS 4 - Drivers, Root, Recovery + MORE
Replies
2K
Views
1M
mskip
mskip
DariosF
  • Locked
[ROM][GPL] [KK 4.4.4] ♦ PURITY ROM ♦ (Mako) 15/10
Replies
12K
Views
2M
Woody
Woody

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 336
    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
    79
    OhDae-su
    OhDae-su
    TWRP 2.6.3.2 flashable .zip!

    Just made a flashable .zip...enjoy!
    View
    52
    azrash
    azrash
    The TWRP recovery has been updated to version 2.7.0.0:
    http://techerrata.com/browse/twrp2/mako
    As usual, update by flashing it in fastboot mode

    or flash in any custom recovery using the flashable zips below

    j.mp/n4twrp for TWRP

    j.mp/n4cwm for CWM Touch and normal

    Flash it in recovery and you are all done. You can revert back to either recoveries by flashing the version you want to.

    all zips have been tested on my N4. recovery img files are sourced from clockworkmod.com for CWM and goo.im or techerrata.com for TWRP.

    Sent from my Nexus 4 using Tapatalk 4
    View
    48
    Dees_Troy
    Dees_Troy
    [RECOVERY] TWRP 2.6.0.0 touch recovery [2013-07-08]
    View
    46
    xanthrax
    xanthrax
    ok , because @azrash looks busy atm , i`ve replaced the new twrp image in his zip and made a flashable 2.7.1.0

    don`t thank me please , anyone can do it :cowboy:
    View

New posts