yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Formhault:
So... TWRP prompts for a password only if one is set AND enabled in Android? Or I can have it disabled in Android and enabled in TWRP?

Not something I'd really need, as I don't hand my device to other people for more than a few seconds, but... I'm curious :)
[Nexus 6  Original Android Development] danarama:
If you don't set a password (and you're encrypted) it will use default.. My assumption is your password / pin / pattern must be enabled to be used..I don't encrypt so I don't know for sure not can I test.
[Nexus 6  Original Android Development] appro77:
I know this is a dumb question but I've never used TWRP to flash an image file before, only zips. If I'm flashing a radio.img file do I choose "Boot" or "Recovery" when prompted for a partition? I'm thinking "Boot" but I need to check. :)
[Nexus 6  Original Android Development] Droidphilev:
Hi,

You can't flash radios or bootloaders in .img format with TWRP. Only 2 thinsg are possible: 'boot' which means 'kernel' and 'recovery' which is a.... recovery like TWRP itself.
[Nexus 6  Original Android Development] appro77:
Thanks for clarifying.
[Nexus 6  Original Android Development] Mortify1:
I just switched over from a dead note 4, I've updated all the way up to 6.0and then tried to fastboot the twrp recovery but all I get is a red triangle. I've flashed back to completely stock 6.0 now and would like some help.

Thanks
[Nexus 6  Original Android Development] :
After you fastboot flash recovery, immediately boot to recovery from the bootloader screen on your phone.
[Nexus 6  Original Android Development] Mortify1:
Thanks, I'll try it out. Simple enough×
[Nexus 6  Original Android Development] Enigmafied:
Hello all, I installed Marshmallow Chroma today. I was almost completely set up, and now came time to restoring data of my apps. I found that a bunch of my apps data had not been backed up even tho I had backed them all up before flashing MM Chroma. Sucks, but thought oh well I will make an image of MM, go back to my LP image, redo my app backups, go back to my MM image, and restore the data. Time wasting, but will eventually get the job done. Well, turns out I can no longer restore LP images, I tried the one I made this morning, and the one I made before I flashed the 5th's LP build. Both result in the following error while restoring Data:

E:extractTarFork() process ended with ERROR=255

MM image I made restores fine. Except WiFi no longer works.

I appear to be in a bit of a pickle. Can anyone help me out?

Thanks.
[Nexus 6  Original Android Development] ben_pyett:
Hello there, you don't state which version of twrp you are using, might be an idea to flash another version either earlier or current depending where you are now and then re-attempt the restore.
[Nexus 6  Original Android Development] skidaway:
I had the same problem recently. However mine occurred during a backup. In the backup folder was a recovery.log file. I checked the log and somehow one of my files in my /system/app/ directory had become corrupted.

I'm not sure how to go about dealing with an already made backup, but check for a recovery.log file on your device and the specific error should be in it.
[Nexus 6  Original Android Development] Enigmafied:
Thanks for your response! I am running version 2.8.7.1 of TWRP.

Thank you for your response as well. I have rectified the problem by restoring my MM nandroid, booting up into Android, wifi did not work, rebooted to recovery, dirty flashed bootloader, radio, rom, and gapps. Wiped dalvik and cache after zips were installed. Wifi works again!

I looked at my backups folders, and there are indeed log files in both LP folder as well as the MM folder. Oddly, the MM log is only 1.5MB, while the LP logs are 8 and 6.7 MB each. At the end it says that it was successful on all of them, that it copied the log, and that is it. I wonder if that is just a backup log?

Thanks again to the both of you!

I am feeling fairly sheepish about trying to restore my LP images again after that fiasco...
[Nexus 6  Original Android Development] kwdan:
Backing up in Twrp

I'm using version 2.8.7.1 I would normally back up system, data, boot. Now I see "system image". Do I back that up also? It's pretty large.
[Nexus 6  Original Android Development] adrman:
No. It's meant to be used on a factory image, to enable an easy restore. Since Google has already provided Nexus factory images, it's not really necessary.
[Nexus 6  Original Android Development] DarkRazorr7:
I think worth to add any theme with Material Desing ;)
[Nexus 6  Original Android Development] xratex:
.

Hi guys, i come from an HTC One X and things are quite different now, the thing is im full stock, bootloader unlocked (i flashed factory files of 6.0) the thing is:

Do i need to do anything in special?

Or a "fastboot flash recovery recovery.img" is enough?

Also kinda offtopic but do i need to flash boot.img as i did on my htc?
[Nexus 6  Original Android Development] hlxanthus:
Yes, all you need to get recovery is

fastboot flash recovery recovery.img

But if you don't root it as well, stock Android will write stock recovery back in place on its own. Now that currently takes a custom kernel (which you can flash in recovery) and SuperSU beta v2.52.
[Nexus 6  Original Android Development] Shilalygawd:
Personally I handle going from stock to custom via the Universal Android Toolkit my first time and then on the device itself from ROM to ROM. So much easier that way because you can do everything you need with a couple of presses of a button.
[Nexus 6  Original Android Development] xratex:
thanks guys! i'm used to ADB and Fastboot, in HOX is a must! so i did flashed the recovery via fastboot, and later flashed a custom rom, everything went fine and smooth.
[Nexus 6  Original Android Development] mcorrie1121:
Hey guys, I'm having the same "E:extractTarFork() process ended with ERROR=255" issue on my backups. This just appeared in the last couple days because I know I did a backup earlier this week. I've attached the full recovery.log, but this seems to be the relevant portion:

Does anyone have a tip on how to fix this? I've already reflashed the 2.8.7.1 img from within TWRP but that did nothing. Thank you!
[Nexus 6  Original Android Development] CrashTestDroid:
If addon.d isn't a directory then it is prob either a file or a symlink. Delete it.
[Nexus 6  Original Android Development] mcorrie1121:
Thanks. I tried deleting it, rebooting into recovery, and running the backup but it just fails again. Then when I reboot the phone I find that the file has returned.

I'm going to cross post this in the ROM thread. Thanks!

EDIT: I wiped everything but internal storage and reinstalled the ROM. That seems to have fixed it. Side note, Marshmallow's settings and apps backup process is pretty great.
[Nexus 6  Original Android Development] NOSTALGIA:
just one dumb question

if i dont want to go with the fastboot method, can i do it through flashify ?

no need to answer..

searched the thread and it says its fine for some..
[Nexus 6  Original Android Development] Formhault:
I flashed a recovery on my Nexus 7 2012 with Flashify and it was fine...

But you can also flash .img files via TWRP - provided you already have it, and just want to flash an update. In the "Install" section, check out the lower right corner, where it says "Images...".
[Nexus 6  Original Android Development] Hazzo31:
Please someone help me. I cant mount anything because TWRP keeps asking for password. I want to flash a ROM and updated to 2.8.7.0 through TWRP and now asks for password. I already format data but each time I reboot the phone to download the zip to my Storage and reboot into TWRP asks for password. I have already tried setting a unlock password but it not seems to be the same. Only after formating data and rebooting to TWRP password is not required but I have nothing in my Storage to flash. Tried to adb sideload de zip but does not recognize device. Plsss help!!! It's really annoying. Thank youuu!!!!
[Nexus 6  Original Android Development] v12xke:
Factory reset and run decrypted until a compatible version is available.
[Nexus 6  Original Android Development] Hazzo31:
Oh okey and sorry for my ignorance but how I avoid encryption? Or how I decrypt my phone?
[Nexus 6  Original Android Development] v12xke:
http://xdaforums.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
[Nexus 6  Original Android Development] Hazzo31:
Solved with an USB/OTG and after formatting data y flashes a Cataclysm ROM that is decrypted.
[Nexus 6  Original Android Development] frozenpandaman:
Hey all– so this is still happening. Haven't been able to solve it since my initial post. The only way I'm able to update my ROM (to new nightlies) at the moment is to back everything up via Titanium Backup and store it on Dropbox (because no SD card), then wipe my internal storage. At this point TWRP is able to recognize my internal storage is not 0MB (i.e. functionality is restored – hence why I think it's some specific data on my device causing this issue of TWRP being unable to mount /data or backup/restore), and I can transfer new .zip files to the device and flash them via TWRP. But… that's a hassle, and the issue still exists.

Would anyone recommend posting this issue to the GitHub issues log, as suggested/linked in the original post? EDIT: Posted.

Also, another short question: Why is this thread not updated to TWRP 2.8.7.1, and why is the changelog for 2.8.7.1 not yet posted to twrp.me (teamw.in)? It is, however, listed on the shamu downloads page. (Note that regarding my issue above, I've tried downgrading to 2.8.7.0 with no luck.)

Thanks!
[Nexus 6  Original Android Development] garyhigh:
Hello Guys, I am still running version 2.8.3.1 and it has been working OK for flashing Chroma until the latest update. I think I may need to update to a newer version. However, the TWRP app in the play store says it's incompatible with 6.0. What is the easiest way to flash a newer version? Thanks !
[Nexus 6  Original Android Development] haibane:
Use fastboot.

Fastboot flash recovery recovery.img

Not sure how the latest twrp shows up as when it is downloaded so just change the recovery.img to that.

Place it somewhere easy to access if you are on windows. For example the c:\recovery.img
[Nexus 6  Original Android Development] :
Download twrp image from the site and flash in twrp. Go to install then hit image in bottom right corner and select twrp img that you downloaded. Works great! ;)
[Nexus 6  Original Android Development] AlkaliV2:
Disregard. Turns out fstrim can be passed from the command line in TWRP as long as busybox and fstrim is installed to /system/bin which is awesome!
[Nexus 6  Original Android Development] xt926:
Any way to make an external sd partition so I can clean flash everything without needing a USB adapter??
[Nexus 6  Original Android Development] CCJ22:
Is version 2.8.7.1 the latest TWRP for our Nexus 6? Is there a newer one?
[Nexus 6  Original Android Development] cujo6801:
1. Yes

2. No

Sent from the "DOG" pound...
[Nexus 6  Original Android Development] znel52:
Are the TWRP guys still active? Haven't seen an update in a long time. I guess it's not really necessary because it's solid as is.
[Nexus 6  Original Android Development] hlxanthus:
Yes they are. They are currently working on updating the default theme to material design and new devices.
[Nexus 6  Original Android Development] pkgnex:
I would expect an update might be forthcoming that eliminates the perpetual "install superuser" prompt for users who are utilizing the new "systemless root" method(s).

If not, consider this a request! I think all root methods are now going this way, so it would be good to clean this up in the recovery.

In the meantime, thanks to the Dev's for this very solid custom recovery!
[Nexus 6  Original Android Development] z31s1g:
This topic is being discussed: https://gerrit.omnirom.org/#/c/15721/
[Nexus 6  Original Android Development] Droidphilev:
For now you can create the file /system/etc/.installed_su_daemon
[Nexus 6  Original Android Development] pkgnex:
Thank you both!
[Nexus 6  Original Android Development] Tubes6al4v:
I am having a weird issue:

I backed up everything but my internal storage. When I restore, it acts like a fresh install. I have tested it on 6.0 and 6.1. The correct system installs, but none of the data is restored. No apps (other than system apps), no messages, call logs, etc. I have selected everything to restore and do a full wipe before restoring the backup. Still no avail.

Any suggestions? I could not find a changelog for TWRP to see if this is an issue that is ongoing or has been corrected in some way.

Thanks!
[Nexus 6  Original Android Development] :
Did you backup and restore /data? If so, what's the size of data in your twrp backup folder?

Also, you can't backup your internal storage unless you're backing up to usb-otg.

I've never seen or heard of this issue before.
[Nexus 6  Original Android Development] Tubes6al4v:
Yes, I backed up a number of times

1. Backup from 6.0 after using it for a few months. Backup size: 1.8Gb I see a number of files labeled recovery, system, etc, but no "Data" should that be in there?

2. Backup after upgrade to 6.0.1 to test backups Size: 1.2Gb This includes additional backup files called "mdm1m...". This backup should have contained the system setup and SMS messages, but restoring it does not restore these either.

That make sense about the internal storage and OTG. I may do that anyway since I have a couple OTG cables and usb drives.

Thanks for your help!
[Nexus 6  Original Android Development] :
Yeah, there's supposed to be one called data. Your mdm1m... files I believe are your EFS/Modem backups.

Where did you get the TWRP image that you're using from? Was it directly from TWRP.me? or a third party installer/image?

I would personally try to re-flash the latest official TWRP.

It shouldn't really matter, but what carrier N6 is it? I don't think they're different, but you never know.

Also, what version of TWRP are you currently using that's causing these issues?

You could also use the option in the advanced settings to export the recovery log to SD after trying to backup to see if it gives you any errors.
[Nexus 6  Original Android Development] Meowdib:
http://xdaforums.com/showpost.php?p=64475913&postcount=692

Some changes to TWRP, looks nicer. Not sure if there are any other changes.
[Nexus 6  Original Android Development] Alxoom33:
Nice cosmetic changes! However, it's an older version of TWRP 2.8.7.0. The current version is 2.8.7.1.
[Nexus 6  Original Android Development] hlxanthus:
"1" of the official twrp signifies a bug fix. The omni build is more current as far as twrp source code but doesn't follow official version naming and numbering.
[Nexus 6  Original Android Development] Alxoom33:
Thanks [MENTION=4129069]hlxanthus[/MENTION]! Appreciate your and the Oct team's fine work. I will reflash[emoji2] [emoji106]
[Nexus 6  Original Android Development] rahuliyer95:
OTA Issue

Can I flash OTA after restoring from NANDROID backup that was taken after clean flashing sytem.img from factory image?

When I tried sideloading the OTA zip it shows

Please help!!
[Nexus 6  Original Android Development] MikeCriggs:
Go back to stock and take the OTA from there.
[Nexus 6  Original Android Development] sansnil:
This workaround doesn't work for me, does it work for others?

I created the file /system/etc/.installed_su_daemon and chmod'ed to 755 but still get prompted to install su in TWRP.
[Nexus 6  Original Android Development] Alxoom33:
I've been using your new version. Really enjoying the updated graphics and functions. Not getting the "your device is not rooted" message for Systemless Root is nice, as well!

Thanks. Any further updates?
[Nexus 6  Original Android Development] elkay:
Anyone had a problem where they suddenly couldn't get TWRP past the splash screen no matter what you do? I've tried 2.8.5.0, 2.8.7.0 and 2.8.7.1 (what I had installed last time it worked), and none get past the splash. My phone boots completely fine to normal system. I'm on (mostly) stock 6.0.1 MMB29S. I've tried flashing from fastboot and from Flashify. No errors. Really confused as to what happened.
[Nexus 6  Original Android Development] Droidphilev:
Delete (hidden) .twrps in TWRP folder on storage.
[Nexus 6  Original Android Development] elkay:
Nope. :( I tried deleting my whole TWRP folder even (after backing it up to my computer).
[Nexus 6  Original Android Development] :
When you boot twrp take an active log while it's booting. I think it's

adb shell cat /tmp/recovery.log

But if have to double check the path. This should work even though it's not clearing the splash... Its likely that the recovery binary or post boot script is hanging.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6  Original Android Development] elkay:
The good news: It could pull a log. via adb pull /tmp/recovery.log.

The bad news: I thought it had hung, so I stopped it at about 30 seconds and the log was already almost 500MB. (no, not KB!!)

I'm seeing a tonnnnnn of stuff like (in fact, I think it's looping):

E:error: Too many open files

E:error opening '/data/data/com.google.android.apps.docs.editors.sheets/files/appmetadata/3b8637d9d2f33fbe641ee1b7e1cc3558/files/fonts/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

And just to add, I checked and there are 178 files in that folder. And I rechecked the log. It infinitely loops that exact line.
[Nexus 6  Original Android Development] :
Yeah, it's stuck in an infinite loop ten probably...

I'm going to go ahead and assume that you've probably got a backup of whatever is in your google docs.

I'd personally probably try to delete that path (assuming it's the only one that you had in the log) with:

adb shell rm -rf /data/data/com.google.android.apps.docs.editors.sheets/

if you can deal with losing the stuff in there.
[Nexus 6  Original Android Development] elkay:
I was thinking the same thing.

I don't even use google docs, so I'm fine nuking it. The whole folder is nothing but TTF font files. The phone boots fine, so I can kill them from Root Explorer without needing to use ADB.

Giving it a shot. And thanks for the log file advice. Never would have tracked this down and format would have been the only option (still may end up there).

---------- Post added at 08:17 PM ---------- Previous post was at 08:11 PM ----------

Success!

Actually, I went the "cleanest" way I could about it. Having "sheets" in the path, I figured it was probably the "Sheets" app and not Google Docs. I went into Apps in Settings and did "clear data" on that app. Browsed back to the offending folder in Root Explorer, it was now empty except a "lib" folder.

Rebooted into recovery, worked fine first shot!

Thank you!!
[Nexus 6  Original Android Development] :
No worries, glad it got you fixed up. You'd think TWRP would be smart enough to recover from that (or at least finish booting and prompt your or something)... but sometimes it can't recover from errors very well. Same way that people end up with the 'tar process' when doing backups. It's because of some file being corrupted. It's easy enough to pull the log, find the corrupt file and delete... but most people just end up wiping.
[Nexus 6  Original Android Development] Droidphilev:
I would wipe :(

Bookmarked your help! Thanks!!!
[Nexus 6  Original Android Development] :
...and yet... no thanks?
[Nexus 6  Original Android Development] Droidphilev:
hmm, language problem i think.

I mean in such case i would be such a user that would just wipe. I mean that your post is very usefull and i wanted to thank you for that.
[Nexus 6  Original Android Development] miladmaz12:
Hey, is TWRP v3.0.0-0 released on this device?
[Nexus 6  Original Android Development] Jiggs82:
+1
[Nexus 6  Original Android Development] nathanchance:
Well you can see that here.
[Nexus 6  Original Android Development] wase4711:
its not up on their download site yet, so I doubt it
[Nexus 6  Original Android Development] Meowdib:
~Around 4 more hours

(pending—Waiting for next available executor)
[Nexus 6  Original Android Development] nazfalas:
If I'm reading it correctly on Jenkins almost all Nexus devices have failed builds so currently no 3.0.0, right?
[Nexus 6  Original Android Development] akellar:
recovery.img should be the actual name of the file
[Nexus 6  Original Android Development] :
Yep, twrp recovery image was renamed as 'recovery.img'. I placed the img file in the platform-tools folder with fastboot and adb, correct?
[Nexus 6  Original Android Development] remag6383:
just to be sure, in windows just rename to recovery. leave the .img off
[Nexus 6  Original Android Development] :
Just to be sure, I renamed the file just 'recovery', retried and still same message :confused:
[Nexus 6  Original Android Development] akellar:
Bad download?
[Nexus 6  Original Android Development] remag6383:
could be bad download. have you tried wugfresh toolkit, it will dl for you. very simple way to do it.
[Nexus 6  Original Android Development] :
Heard of the toolkit, but never used it until now. Wow, what a handy toolkit! Thanks for the suggestion, it did it flawlessly. I'll have to donate to this guy:victory:
[Nexus 6  Original Android Development] SamuriHL:
Check the md5 hash on your download. Could be corrupt.
[Nexus 6  Original Android Development] tyea:
in /system rename the file recovery-from-boot.p to something else. This will allow the recovery to stick. I flashed twrp. Within TWRP I used twrp options to: mount the system then used twrps file manager to rename the file.
[Nexus 6  Original Android Development] remag6383:
glad you got it going
[Nexus 6  Original Android Development] aSquard:
I had the same issue as another user - clashed TWRP and can't get into android. My Nexus 6 loops at the TWRP recovery screen. I flashed the stock recovery in order to remedy the situation in the meantime though... any fix for this?
[Nexus 6  Original Android Development] blastagator:
When will these changes be pushed to the git so we can build for other devices? Thanks for all the hard work!
[Nexus 6  Original Android Development] ericerk:
I have this issue as well.
[Nexus 6  Original Android Development] thrillerbee:
I had this issue when I didn't follow instructions and flashed TWRP immediately after unlocking (instead of letting it boot once before flashing TWRP).
[Nexus 6  Original Android Development] ericerk:
I had a fully set up system.
[Nexus 6  Original Android Development] mhsbrian:
Working beautifully for me, thanks to all the devs!!!

Very excited for the future of this device...
[Nexus 6  Original Android Development] Moostafa29:
I just used flashify for the sake of experimentation and it worked just fine.
[Nexus 6  Original Android Development] pappy97:
I just did the same, works like a charm.
[Nexus 6  Original Android Development] mr pnut:
Does anyone has the stock recovery.IMG?
[Nexus 6  Original Android Development] starcms:
No 3.0.0 today.
[Nexus 6  Original Android Development] Skripka:
For those waiting, there are unofficial 3.0.0 builds floating around on AFH and elsewhere...They are slick.
[Nexus 6  Original Android Development] ANDR01DN00B:
I'm not sure I can find them. Do you mind sharing a link?

Thanks
[Nexus 6  Original Android Development] starcms:
Link please?
[Nexus 6  Original Android Development] ieatacid:
It just finished building and updating the download index: https://dl.twrp.me/shamu/
[Nexus 6  Original Android Development] starcms:
It's live!! Go go go
[Nexus 6  Original Android Development] wase4711:
please report back on if it works properly...supposedly there might be issues if you are encrypted...