yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] skidaway:
When I reboot into recovery, I get the standard TWRP splash screen, then it displays a page that says "Please Enter Your Password" with a keyboard at the bottom.

After entering the correct pass, it displays:

Data successfully decrypted, new block device: '/dev/block/dm-0'

I'm no expert on encryption, nor recovery, but my best guess is a ROM issue. Hopefully someone else is using encryption on their Mahdi install and can give some advice. I've noticed in general, there are very few people using android encryption.
[Nexus 4 Original Android Development] azrash:
The TWRP recovery has been updated to version 2.8.0.1:

http://techerrata.com/browse/twrp2/mako

As usual, update by flashing the img 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.
[Nexus 4 Original Android Development] sordna:
Please add option to avoid space check on compressed backup

Hi, thank you for this!

I have a suggestion, that came up because I'm running into this all the time:

My phone has 3.5GB free space left, and when I try to take a backup, TWRP (including the latest 2.8.0.0 version) fails because the size of the data to be backed up is determined to be 3.8GB.

However, I am using compression. If I delete some photos to make up the data to be backed up just fit, the backup succeeds, and because I am using compression, I have over 1GB free after the backup !

As you understand, it is very annoying when a backup refuses to start, when I know very well it would succeed because of the compression.

So can you please add an option in the settings to avoid doing the space check for compressed backups ?

Thanks!
[Nexus 4 Original Android Development] Marsou77:
I think before compressing, TWRP have to do the full backup, then it compress. I'm not sure..
[Nexus 4 Original Android Development] pawan1993:
I must say that this is huge! MTP support within recovery is amazing. Great job TeamWin. You guys are amazing!
[Nexus 4 Original Android Development] Vlad Paul:
Flashed it successfully. Thank you nice! ;)
[Nexus 4 Original Android Development] CamoGeko:
This is correct, and thus they will never remove the free space check.

Bit overdue to be honest since CWM has had this support for ages, still my preferred recovery is TWRP so awesome job guys!
[Nexus 4 Original Android Development] sordna:
I don't think so. It would be silly and I would never be able to take backups if that were the case :) I would need 6 or 7 gigs of free space that I don't have.

When you say "it is correct", did you read the code, or are you guessing?

Ok, let's assume you have an old tar command that doesn't do compression, here is how you would do a compressed tarfile, compressing it on the fly without wasting disk space to save the uncompressed tarfile on disk:

tar cvf - blah | gzip > file.tar.gz

I am pretty sure both compression and encryption are happening on the fly, because that's the only sensible way to go.

Also I am not asking to remove the space check, I am asking for a option in the settings, to allow a user that knows what they are doing, to optionally disable the check.

EDIT: Here is how to simulate compression and encryption on the fly on a computer, without saving any intermediate files. The first command creates a backup, the second asks for the password and then extracts the data:

tar cvf - *.pdf | gzip | oaes enc --key password > file.tar.gz.enc
oaes dec --in file.tar.gz.enc | gzip -dc | tar xvf -

oaes does the same encryption that twrp uses, I had posted some info on this here.
[Nexus 4 Original Android Development] ma678:
For some reason, the latest 2.8 didn't save my back even if I saw it back up successfully.

Anyone has the same issue?
[Nexus 4 Original Android Development] icu64:
Sooooo is anyone ever going to fix the rest for the recovery? Its actually pretty far off
[Nexus 4 Original Android Development] ruicc:
How to use MTP? I can enable or disable MTP, but i can't connect my PC to my Nexus in recovery mode...using ubuntu 14.04
[Nexus 4 Original Android Development] Dryblow:
I tried mtp with windows 8 but it ask new drivers and not work mtp session.
[Nexus 4 Original Android Development] Simoneale73:
Tried flashing twice with the TWRP Manager, each time it say's 'Installed OK', and I'm still on 2.7.10 :confused:
[Nexus 4 Original Android Development] krxz:
I have a problem installing version 2.8.0.0 on my oneplus one. Tried with flashify and it sais that flashing was successfull. But when I try to boot into recovery my bacon gets stuck on 1+ logo.

Also tried with twrp manager. Same problem.

Anyone else facing this issue?

Send from my 1+ powered by DroidKang, franco and VomerTweaks
[Nexus 4 Original Android Development] icu64:
Sooooo everyone's just going to ignore this?
[Nexus 4 Original Android Development] Almayce:
Well for one this is mako-Nexus 4 thread for twrp. I hope u didn't flash this one. You should report it on your forum.
[Nexus 4 Original Android Development] CamoGeko:
Did you flash the correct img file?

Also, why didint you use fastboot??
[Nexus 4 Original Android Development] worm9110:
Got same thing as you, but after flashing with fastboot it worked.
[Nexus 4 Original Android Development] tatnai:
I flashed the twrp zip using twrp, rebooted into recovery, and it worked fine.
[Nexus 4 Original Android Development] nickslg:
Installed first time on my nexus 4... its working great
[Nexus 4 Original Android Development] thebrainkafka:
Is there a ZIP for 2801?

Thx
[Nexus 4 Original Android Development] phyl65:
DELETE
[Nexus 4 Original Android Development] CamoGeko:
Pretty sure he was asking for a flashable zip, not an image file.

[MENTION=3946376]thebrainkafka[/MENTION] Look a few pages back, there was a zip posted before. You can just put the 2.8.0.1 img into it and flash as normal.
[Nexus 4 Original Android Development] Jack'O:
Here you go:

TWRP-2.8.1-Mako.zip (Mega)
[Nexus 4 Original Android Development] thebrainkafka:
Cant download from mega. May i ask for a mirror. Thx
[Nexus 4 Original Android Development] M1K3E:
If using mobile.. Select request desktop site

Or mirror here

https://copy.com/sDnBKe4JHcwL9Ks9
[Nexus 4 Original Android Development] Jack'O:
TWRP-2.8.1-Mako.zip (Ge.tt)

TWRP-2.8.1-Mako.zip (G-Drive)

TWRP-2.8.1-Mako.zip (Mediafire)

TWRP-2.8.1-Mako.zip (Mega)
[Nexus 4 Original Android Development] icu64:
mount mtp option

so did anyone figure out how to enable mtp yet? really need it to fix my phone:(
[Nexus 4 Original Android Development] pro.aggro:
it doesn`t work on my device. i tried to boot into the recovery with the cable plugged in and enabled/disabled the mtp option in the recovery. but nothing happens
[Nexus 4 Original Android Development] icu64:
The closest I got was turning on adb sideload and turning it off. The computer would at least pick it up
[Nexus 4 Original Android Development] fr3quency:
No f2fs support? o_O 2.7 had it if I recall correctly.
[Nexus 4 Original Android Development] Shooting Star Max:
At least the MultiROM version supports F2FS. (Though I cannot boot any secondary ROM, but that must be because of my CM kernel...)
[Nexus 4 Original Android Development] jlmntl:
These are img files, not flashable zips

Sent from my Nexus 4
[Nexus 4 Original Android Development] alleyezondisromo:
F2fs?
[Nexus 4 Original Android Development] Jack'O:
Not yet, but you can give MultiROM a try, it have and is based on TWRP (2.8.0 atm).
[Nexus 4 Original Android Development] Calinho:
USB cable not work on TWRP 2.8.0.1, no charging, no adb push...
[Nexus 4 Original Android Development] CamoGeko:
Working fine for me here.

Did you do fastboot erase cache after flashing the img?

Sent using N⁴ with Android L
[Nexus 4 Original Android Development] Calinho:
no

I try to erase cache now, but not solve my problem. I am rollback to 2.7.1.0
[Nexus 4 Original Android Development] jtwebfusion:
The only issue I have is that I have to restart recovery in order to wipe internal storage after clean flashing a rom.
[Nexus 4 Original Android Development] ezio84:
It works fine here, also adb sideload.
[Nexus 4 Original Android Development] nickslg:
i have a problem deleting a backup i ve tried and when i swipe to delete its still there any solutions ?
[Nexus 4 Original Android Development] johnb380:
Just use root explorer or root browser navigate to the folder and manually delete it! Maybe you updated your version and the backup became corrupt or something idk... Just an idea!
[Nexus 4 Original Android Development] nickslg:
Thanks it worked:thumbup:
[Nexus 4 Original Android Development] AO4EVER:
LG G2 (vs980) compatible?

Greetings,

Is LG G2 supported?

Didn't see it on the list of compatible devices, only G3 (vs985).

Thank you!
[Nexus 4 Original Android Development] xanthrax:
Check d802

http://www.teamw.in/project/twrp2/197

Or the dedicated thread on LG G2 forum

Sent from my Darkside of LG G2
[Nexus 4 Original Android Development] AO4EVER:
Got it, it was miscategorized just like d802.

Thank you!
[Nexus 4 Original Android Development] buru898:
​

Those aren't zips. Learn to read.
[Nexus 4 Original Android Development] shobuddy:
1. Does TWRP have to already be installed before installing TWRP Manager? Or can TWRP be installed using TWRP Manager?

2. If TWRP is already installed before installing TWRP Manager, can TWRP Manager be used to update TWRP recovery to the latest version?

3. With the Lollipop update right around the corner, can we download the OTA zip to the phone and install the update using TWRP Manager? Are there any "wipe" settings we should use when doing this update?
[Nexus 4 Original Android Development] fr3quency:
Is it really that hard to boot into fastboot every time a new TWRP update is available and type "fastboot flash recovery TWRP.img"? :/
[Nexus 4 Original Android Development] arffrhn:
1. No. Yes, twrp can be installed using twrp manager though it is not really a reliable tool (at least it was not on my device).

2. Same as the above, not reliable. If you already havr twrp installed, just download the flashable zip and flash it using twrp installed on your device. Easier. Faster. 100% success.

3. As it is a major update, I would suggest a full clean install and by that I mean flash the factory images (if any, from Google). If you are talking about custom rom, you can use twrp but make all wipes (system, data, dalvik, cache) prior to flashing.

To me it seems like you are new here so for number 3, better to start clean like I suggested above rather than doing something you are not sure of, resulting in you facing a lot of problems. Worst case, bricking your device.

Always wipe before updating rom/android version. Good day. :)
[Nexus 4 Original Android Development] bombadier:
New TWRP 2.8.1.0 is up

All credit for the flashable zip to [MENTION=2966468]azrash[/MENTION] I just replaced the image with the latest one and bumped the version number in the updater-script

TWRP Flashable zip

Changelog is in the first post:

CHANGELOG for 2.8.1.0:

-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that

-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar

-Temperature support - thanks to bigbiff

-Various other bugfixes and tweaks
[Nexus 4 Original Android Development] Vlad Paul:
Thank you! Changelog, please?

Sent from mako via tapatalk
[Nexus 4 Original Android Development] fr3quency:
Does MTP work for any of you guys? It still doesn't work for me.(both 2.8.0.1 and 2.8.1.0)

Windows reads the device but it's not shown in explorer(like it is when it's powered on)
[Nexus 4 Original Android Development] bombadier:
I cant get it working either :(
[Nexus 4 Original Android Development] fr3quency:
Does it even work on other devices or have they just added some code and prayed to God it works? :p
[Nexus 4 Original Android Development] bombadier:
Just updated my Nexus 7 (2012) to twrp 2.8.1.0, windows installed new drivers and MTP works ! so the code works....just not on a nexus 4
[Nexus 4 Original Android Development] fr3quency:
This is preposterous! :P How can it work on Nvidia and not on Qualcomm?

Edit: Doing a "twrp set tw_mtp_enabled 1" might fix it?
[Nexus 4 Original Android Development] bombadier:
I can't get adb to recognise my phone in recovery so dont think it would,also believe mtp is enabled by default,guess its not meant to be

just tested rebooting my nexus 7 into recovery and you guessed it adb recognises it

Thinking a driver issue with the nexus 4?

Any of you boffins had any luck?
[Nexus 4 Original Android Development] fr3quency:
When I disable USB Debugging Windows (8.1) doesn't show any MTP connection but it does recognize the device. Maybe it has something to do with debugging and recovery? Is there any IRC channel for TWRP so we ask them directly?
[Nexus 4 Original Android Development] z31s1g:
Last paragraph of the OP holds the channel link.
[Nexus 4 Original Android Development] fr3quency:
[MENTION=2714876]bombadier[/MENTION] Dees_Troy will look into it when he gets a chance. From what they told me in the channel "the maintainer might not be setting the right vendor id for usb".
[Nexus 4 Original Android Development] jtwebfusion:
Still can't wipe internal storage after flashing a rom on 2.8.1.0 (mako).
[Nexus 4 Original Android Development] E.L.E.C.T.R.O.N.I.C:
please any .zip download link for this recovery

i can't find it :(
[Nexus 4 Original Android Development] ilyadan:
Two pages back.
[Nexus 4 Original Android Development] fr3quency:
No .zip. You simply download the .img file from here http://techerrata.com/browse/twrp2/mako and boot into fastboot mode. Then you simply type "fastboot flash recovery name_of_the_recovery.img"

Protip: the .img file must be in the same folder as fastboot.
[Nexus 4 Original Android Development] pincher65:
there is zip http://xdaforums.com/showpost.php?p=56359636&postcount=2339
[Nexus 4 Original Android Development] underskyzx:
You can use Flashify too

--

adb sideload working for anyone?
[Nexus 4 Original Android Development] benbugohit:
A little rude. Not very convenient when you have no computer (with fastboot installed) beside you...
[Nexus 4 Original Android Development] steviemch:
I honestly fail to see what you considered rude about that post?

Anyway if you're not near a computer/don't have fastboot drivers installed, simply download flashify from the play store and flash img files with that.

Sent by Borg neural subspace transceiver node.
[Nexus 4 Original Android Development] fr3quency:
No, it's not rude. You just get offended easily. There's a difference.

If you don't have a PC, simply don't install the new recovery. It's not like you're in the recovery 24/7. Plus TWRP installs everything, so I doubt that's the reason one would want to install the new recovery.

Also, what [MENTION=5364757]steviemch[/MENTION] said.
[Nexus 4 Original Android Development] playya:
Actually so many people make a big deal about finding a zip file for all updated recoveries. People instead of asking just make your own. If you have the zip file from a previous version its nothing more than replacing one img file for another as well as renaming the file to recovery.img. Updates script info can be updated as well if you like

Now as far as flashing a recovery there is more than one way to skin a cat as they say. So I agree with some of the other posts as I see nothing rude in offering alternatives method and I am a firm believer in trying to do things on your own as long as it is possible.
[Nexus 4 Original Android Development] bart.found:
he probably means rudimental.. not rude.. XD XD
[Nexus 4 Original Android Development] KreAch3R:
2.8.1.0 TWRP MTP Fix for the Nexus 4

Hello,

I was annoyed by the fact that the newly announced MTP feature wasn't working on our devices, and I managed to find a way to fix it. The necessary changes are due to the init.rc file.

This is the changed code:

# Always start adbd on userdebug and eng builds
# In recovery, always run adbd as root.
on property:ro.debuggable=1
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18D1
[B]write /sys/class/android_usb/android0/idProduct 4EE2[/B]
[B]write /sys/class/android_usb/android0/functions mtp,adb[/B]
#write /sys/class/android_usb/android0/enable 1
write /sys/class/android_usb/android0/iManufacturer $ro.product.manufacturer
write /sys/class/android_usb/android0/iProduct $ro.product.model
write /sys/class/android_usb/android0/iSerial $ro.serialno
[B]write /sys/module/rmnet_usb/parameters/rmnet_data_init 1[/B]
#start adbd
setprop service.adb.root 1

Now MTP and adb are working correctly (YMMV). Tested on both Windows Pro 8.1. x64 and Xubuntu 14.04.

I have attached two modified files, a plain 2.8.10 twrp and a multirom one. I zipped them because of XDA upload restrictions. Please test them and report back if it works for you.

DISCLAIMER! As always, it is not my fault if you obliterate your device! /DISCLAIMER!

I will try to contact the TWRP devs to find out how and where to do a proper pull request.
[Nexus 4 Original Android Development] fr3quency:
[MENTION=3190122]KreAch3R[/MENTION] thessalonikie, you nailed it! I'll test it and report back.
[Nexus 4 Original Android Development] bombadier:
[MENTION=3190122]KreAch3R[/MENTION]

You are the man it works :good::good:

Made your changes to the init.rc file and bang mtp works, today is a good day thanks to you :good::good:

[MENTION=1225126]fr3quency[/MENTION] I have already updated my curtain repacks with the changes so go ahead and update :D
[Nexus 4 Original Android Development] fr3quency:
[MENTION=2714876]bombadier[/MENTION] hahah will you believe me that the first thing I thought when I saw the fix is that I'll lose the Play curtain? xD You're fast!
[Nexus 4 Original Android Development] Vlad Paul:
Please upload TWRP with MTP fix flashable zip from recovery. Thank you!

Sent from mako via tapatalk
[Nexus 4 Original Android Development] bombadier:
Have done the fix and heres a flashable zip (Also changed the splash screen,I think it looks better)
[Nexus 4 Original Android Development] Vlad Paul:
Sorry, i don't understand because of my poor english. I was sent you a private message.

Sent from mako via tapatalk
[Nexus 4 Original Android Development] KreAch3R:
Thanks guys! I am glad it is working. Currently, I am trying to contact the developers, to get it upstream.

(Καλησπέρα πατρίδα)
[Nexus 4 Original Android Development] Vlad Paul:
Thank you much [MENTION=720170]bombardier[/MENTION] for your efforts .

Ohhh, i have troubles with drivers, please my friend [MENTION=3946657]xanthrax[/MENTION], when you have little time free, help me to fix N4 drivers. My computer recognise Nexus 4 only as PTP. MTP doesn't working.

Sent from mako via tapatalk
[Nexus 4 Original Android Development] KreAch3R:
You can use Nexus Root Toolkit to uninstall and re-install the correct drivers. In my tests, it helped me a lot.
[Nexus 4 Original Android Development] fr3quency:
A question which came out of the blue. What is "rm -rf" command supposed to do in TWRP recovery? rm surely deletes files. But why would someone use it instead of simply wiping the partitions(/system, /data etc)?
[Nexus 4 Original Android Development] LeoPosas:
NAME

rm - remove files or directories

SYNOPSIS

rm [OPTION]... FILE...

DESCRIPTION

This manual page documents the GNU version of rm. rm removes each specified file. By default, it does not remove directories. If a file is unwritable, the standard input is a tty, and the -f or --force option is not given, rm prompts the user for whether to remove the file. If the response does not begin with `y' or `Y', the file is skipped.

OPTIONS

Remove (unlink) the FILE(s).

-d, --directory
unlink FILE, even if it is a non-empty directory (super-user only)

-f, --force
ignore nonexistent files, never prompt

-i, --interactive
prompt before any removal

-r, -R, --recursive
remove the contents of directories recursively

-v, --verbose
explain what is being done

--help
display this help and exit

--version
output version information and exit
To remove a file whose name starts with a `-', for example `-foo', use one of these commands:

rm -- -foo
rm ./-foo

Note that if you use rm to remove a file, it is usually possible to recover the contents of that file. If you want more assurance that the contents are truly unrecoverable, consider using shred.
[Nexus 4 Original Android Development] fr3quency:
So it forces removal of the files in the entire directory. Because there might be locked files or files with read only permissions. Can the simple format we do under advanced settings do this?
[Nexus 4 Original Android Development] LeoPosas:
Sure, but remember that the rm command it's for an specific file or folder, format WIPE the WHOLE partition (Everything inside it).
[Nexus 4 Original Android Development] KreAch3R:
[MENTION=912474]Dees_Troy[/MENTION]

I did as you said, and tried to find out if the mentioned changes are necessary. In my tests, all of them were needed for MTP to work on Windows 8.1.

After that, I used your guide to build TWRP from source, and managed to do it, using the CM tree. I built using my init.recovery.rc though, because I couldn't find the original init.rc I had modified anywhere(I am talking about the one found inside the mako-twrp.img). I am new to building from source, but as I understand, the building script takes the "general", "common" files and overlays the "device specific" files on top, and that's how you get a customized product. So, I thought that I could find that specific mako init.rc somewhere in the omni's source, but I couldn't. The only thing close to that is this android_bootable_recovery / etc / init.rc, which is very different from the one in mako image. Also, the compiled twrp version files were not exactly the same as the files produced by the Android Image Kitchen (the one I used in the first time). I don't know if any of this is affected by AIK.

So, because I couldn't replicate exactly the mako-twrp.img (maybe you use another source tree? ), I didn't continue further in trying to find a way to incorporate the necessary changes into init.recovery.$ro.hardware.rc (that you thought is the best way to go on). Also, I tried to sign in to http://review.teamw.in/ to submit my modified lge/mako/Boardconfig, lge/mako/init.recovery.rc, lge/mako/twrp.fstab but the page is down.

I fear that my skills go so far. I will attach the modified files, and the necessary code changes. Let me repeat that I used these files to build a mako-twrp.img using CM11's source code. I hope you find a way to incorporate it graciously. :)

TL;DR: I didn't manage to improve the code & submit to TWRP gerrit for review and merging. It's up to the TWRP developers.

These are the TWRP settings I used, taken and modified from omnirom/android_device_lge_mako :

#TWRP config
DEVICE_RESOLUTION := 720x1280
RECOVERY_SDCARD_ON_DATA := true
RECOVERY_GRAPHICS_USE_LINELENGTH := true
BOARD_HAS_NO_REAL_SDCARD := true
PRODUCT_BUILD_PROP_OVERRIDES += BUILD_UTC_DATE=0
[B]TARGET_RECOVERY_INITRC := device/lge/mako/init.recovery.rc[/B]
[B]PRODUCT_COPY_FILES += device/lge/mako/twrp.fstab:recovery/root/etc/twrp.fstab[/B]
#TW_INCLUDE_CRYPTO := true
TW_INCLUDE_JB_CRYPTO := true
TW_FLASH_FROM_STORAGE := true
TW_NO_USB_STORAGE := true

TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/usb-otg"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "usb-otg"
[Nexus 4 Original Android Development] HiM@L:
Has anyone noticed this while flashing L....look closely. Just pointing out.
[Nexus 4 Original Android Development] p2pjack:
Can you do the same for the new multirom that came out today please

:)
[Nexus 4 Original Android Development] bombadier:
[MENTION=3418206]p2pjack[/MENTION]

Can you test this please

TWRP_multirom_mako_20141115_MTP_Fix_Black_kk.img

I have also replaced the curtain with kitkat black

It should work if not just flash your old version