yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] 92slammer:
not using OTG...however i went back to 2.8.5 and it recovers just fine...only a matter of minutes.
[Nexus 6  Original Android Development] galaara98:
I had similar issue trying to encrypt backup..2.8.6 took like 55minutes Went back to 2.8.5... Took like 8 mins

Aaron
[Nexus 6  Original Android Development] wvcadle:
So does anyone else use the TWRP app? I mean, it rarely gets updated anytime soon after a new version release, so unless one uses it for one of its other functions, it's useless, no?
[Nexus 6  Original Android Development] cam30era:
That is the best job I have ever seen of asking a question, and answering it, in two sentences!

:good:
[Nexus 6  Original Android Development] kpierce2014:
I been on the latest twrp 2.8.6 and every time I try to do a back up it shows failed but the back up shows in the twrp folder. Anyone else see this happen?

Edit: Ok that is wierd it only fails if its encrypted
[Nexus 6  Original Android Development] :
I've been using 2.8.5.0 and never any issues. Works like a charm. [emoji106]
[Nexus 6  Original Android Development] bill3508:
Same 2.8.5.0 works great.
[Nexus 6  Original Android Development] casonswag:
I don't have any issues with 2.8.6
[Nexus 6  Original Android Development] galaara98:
Have you tried making or restoring an encrypted backup/nandroid... Because if you do, I believe you will notice problems..

Aaron
[Nexus 6  Original Android Development] adrman:
I've done both several times without issues.
[Nexus 6  Original Android Development] purian23:
Same here, no issues.
[Nexus 6  Original Android Development] Maximinus I:
It's working perfectly fine for me as well.
[Nexus 6  Original Android Development] kpierce2014:
I am sorry but the people claiming they are not having the issues obviously are not doing a nano back up with encrpytion. Its a known issue with twrp for the nexus 6. You are either not encrypting it or ur still on 2.8.5.
[Nexus 6  Original Android Development] russlowe73:
Is this issue with making the backup encrypted, or just doing a backup on an N6 that is itself encrypted?
[Nexus 6  Original Android Development] kpierce2014:
its making the back up encrypted when it doesnt work. That last known time it works doing that is 2.8.5
[Nexus 6  Original Android Development] adrman:
My comment about it working refers to the latter.
[Nexus 6  Original Android Development] casonswag:
I dont even mess with the backup ecryption never did and backups works good regular on 2.8.6 my phone is unencrypted tho
[Nexus 6  Original Android Development] russlowe73:
That's why I asked, it sounds as if everyone who says its working is the latter also.
[Nexus 6  Original Android Development] galaara98:
I have an encrypted DATA partition. But the statement I made is about making an Encrypted Backup, nothing to do with the encryption state of your /data partition.

When I backup or restore using the latest TWRP while doing a Non Encrypted Backup, it works fine.

My statement (quoted here) is about doing Encrypted TWRP backup, or a restore of a TWRP encrypted backup. That is not working, or at least not working well, on the latest TWRP but works fine on previous ones.

Aaron
[Nexus 6  Original Android Development] :
+1! Been using it since it came out. Flawless!! :sly:
[Nexus 6  Original Android Development] elkay:
Any word on F2FS support baked in?
[Nexus 6  Original Android Development] rfec:
When I try to flash a ROM I got the following error.:

"unmount of /system failed, no such volume"

Latest TWRP.

Is there a way to fix this problem somehow?:confused:
[Nexus 6  Original Android Development] rignfool:
No...

Its an error that occurs because shamu would not unmount system in the early goings and everyone just added that line to updater scripts....

Doesn't appear necessary anymore... But don't worry... Everything is fine
[Nexus 6  Original Android Development] psychomaniac189:
why is it that when you use cmupdater you cant flash the same file manually again?
[Nexus 6  Original Android Development] liquidDroid:
Nandroid?

OK back when the Nexus6 was scarcely available I got two via eBay.

After I've setup one of my phones, rooted and custom ROM, been my daily driver for months on VZW. I finally decided to put one of my nandroid backups on the other phones. Only problem is the second phone doesn't see the nandroid on my OTG stick with same ROM.

My ? is why won't the second phone recognize the nandroid backup? I know one is the T-Mobile variant but I'm not sure about the second phone.

Thnx
[Nexus 6  Original Android Development] demlv:
I don't think the otg is the issue. Possibly because of different serial numbers? TWRP looks for nandroids under the folder with the phone's serial number .... Like this data/media/TWRP/(phone_serial)/nandroid_folders

So maybe copy the nandroid to that subfolder on internal storage? Really just guessing. Report back if you figure it out.
[Nexus 6  Original Android Development] liquidDroid:
I finally figured it out. It was user error of course. When I originally copied the backup file I copied the folder with the serial number too. .So of course it didn't see it.
[Nexus 6  Original Android Development] biglil1:
I've tried to pull the ui.xml using adb but it only pulls the battery images. Does anyone have a stock ui.xml?
[Nexus 6  Original Android Development] rub1k:
I'm having a really strange issue and I've tried searching but couldn't find anything so figured I'd try posting here.

I can't seem to be able to boot into recovery after flashing to 2.8.6.x (tried both .0 and .1, MD5 matched).

After rebooting into the bootloader and choosing to boot into recovery, the white 'Google' logo flashes quickly in the center of the screen and then it kicks me right back to the main bootloader screen.

I've never seen this before and I must have flashed TWRP hundreds of times on 5-6 different phones over the years.

My Nexus 6 is running stock ROM (5.1, build LMY47D), rooted and encrypted.

Does this have something to do with being encrypted?

FWIW, flashing back to TWRP 2.8.5.0 (what I was trying to update from) allows booting into recovery again. So it seems like it just refuses to boot into recovery using 2.86.x (actually just flashed 2.8.5.2 and that doesn't work either).

Any help with this would be greatly appreciated. Thanks in advance.
[Nexus 6  Original Android Development] micmars:
What minor, iterative versions of TWRP are you finding, and from what site did you download same (2.8.5.2 and 2.8.6.1 seem unavailable to me...I'd like to know how to obtain them).
[Nexus 6  Original Android Development] rub1k:
OMG, sooo sorry about that (and thank you for figuring out exactly what I was doing wrong!), it turns out my brain was on auto-pilot and thinking that I was still on my Nexus 4, so I was downloading and flashing 'mako' builds, which DO have those extra few versions. No wonder the bootloader didn't load up the recovery mode (and my old 2.8.5.0 image that I had as backup was the correct 'shamu' one).

I feel like such an idiot... ugh.

You're 100% correct, though. Your screenshot shows the correct (and only ones AFAIK) builds for 'shamu', so I'll go head and flash 2.8.6.0 and stop embarrassing myself in here.

Thanks again for your help!
[Nexus 6  Original Android Development] maddoggin:
ok i know this is a noob question but with update nearing i was wondering if ota will update without messing things up on my phone while using twrp recovery? im on stock lmy47m with twrp! thanks
[Nexus 6  Original Android Development] micmars:
You'll more than likely be fine. Best to keep a watch on the forums, and if you're the least bit reticent to flash a rom update, avoid the temptation to be one of the first, and wait for the dev community to deliver (bootloader, modem if necessary, otherwise just go for the latest rom that incorporates the new features).

In a word, exercise patience and you'll be fine.
[Nexus 6  Original Android Development] SamuriHL:
If you've made any changes at all to system, the ota will not install. They use block checksum checking rather than checksumming individual files. So if you've rooted, it won't install until you restore the entire stock system partition. I know what wasn't your question but those with twrp tend to mess with system so I wanted you to understand that the ota will fail if that's the case.
[Nexus 6  Original Android Development] maddoggin:
yeah unfortunatly i just found that out. i got a message that said installation aborted because system partition has unexpected contents or files or whatever. so will a factory data reset from settings erase everything? i have already flashed back stock recovery but im still rooted and have a backup which when creating a bcakup twrp does something to the poartiton right? so what do i need to do to erase everything?

---------- Post added at 04:50 PM ---------- Previous post was at 04:31 PM ----------

well i went ahead and tried a factory reset and now i bben stuck on and android guy with the word erasing underneath for like 10 minutes

---------- Post added at 04:58 PM ---------- Previous post was at 04:50 PM ----------

factory data reset didnt work

---------- Post added at 05:07 PM ---------- Previous post was at 04:58 PM ----------

i think i figured out what the problem is. when trying to sideload the connection is lost and i had to reconnect the divice. i believe this is what is causing he error. moving along to different thread to find out a fix. thanks!
[Nexus 6  Original Android Development] russlowe73:
Everything has to be stock. Recovery, image, no root. Easiest way would be to use the toolkit and flash the stock 5.0 build, then ota the other 2 builds to get to current.

---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------

http://xdaforums.com/showthread.php?p=60927946
[Nexus 6  Original Android Development] maddoggin:
i dont have windows.
[Nexus 6  Original Android Development] danarama:
Don't use toolkits anyway.

All you need is fast boot. This can be installed on windows, Linux and mac.

Go to general > sticky roll-up > adb and fastboot.

Everything will be explained there
[Nexus 6  Original Android Development] SamuriHL:
If you get completely stuck, my house of nexus works on Windows, Linux, and Mac. It takes the factory image and generates a script for you to flash the different partitions. It even allows you to flash twrp in place of stock recovery. Pm me if you need it.
[Nexus 6  Original Android Development] natezire71:
Has anyone had any issues with the locking mechanic? If I have my phone backing up via TWRP--and the screen dims then "locks", I can never get the device screen back on to the GUI. The screen turns on, but is solid black. I can even take screenshots while this is happening. Only way for me to fix it is to hard reboot via long-pressing the volume rocker and power button.

Only way I've been able to stop this from happening is disabling the locking option. I never had issues with this until 2.8.6.0. Also, not sure if it matters, but I've been using this theme for TWRP as well--I've always used it.
[Nexus 6  Original Android Development] z31s1g:
So just to clarify: the problem isn't with unlocking, but with the ui being shown again after the screen timeout has kicked in.

I always have this option disabled, but I. Did enable it to test. Turning the screen on after timeout works for me.

Just to rule out the theme as a possible cause for the problem, have you tried if it persists if you remove the theme?

In my experience the theme can't cause this kind of issue, but just to be sure...
[Nexus 6  Original Android Development] natezire71:
I'll give it a go without the theme.

But yes, you described it exactly. Try making a backup, and let it timeout. Then after a few minutes, try to wake it.
[Nexus 6  Original Android Development] z31s1g:
Wait, I tested by setting timeout to 15 seconds and waited for the screen to turn off.

Where you making an encrypted or compressed backup? Because I believe one of both is currently broken the backup process just doesn't finish. Might be it also has an impact on other functions..
[Nexus 6  Original Android Development] natezire71:
It is a compressed backup, yes. I've only noticed having this issue when making backups.
[Nexus 6  Original Android Development] z31s1g:
So I just tested making compressed backups with timeout enabled. No problem here, with or without theme.

But I'm using my home-built version of twrp 2860. If you want to give it a try:

https://www.dropbox.com/s/6tfr1b9n1f48i49/recovery0524.img?dl=0
[Nexus 6  Original Android Development] russlowe73:
Set the screen to not turn off when doing a backup.
[Nexus 6  Original Android Development] natezire71:
That's not really a solution. It isn't working properly.
[Nexus 6  Original Android Development] joderme:
Anyone tested with Android M yet? I might have to if no one else has.
[Nexus 6  Original Android Development] SamuriHL:
Not yet. I clean installed M on my NX6 (minus the bootloader) but I've yet to boot up TWRP. I can do so in the morning if no one has but I need to head to bed.
[Nexus 6  Original Android Development] joderme:
Just tried to root and it exploded. I will have to reflash and I will install TWRP as a part of this.
[Nexus 6  Original Android Development] z31s1g:
https://plus.google.com/+DeesTroy/posts/MrEXCHJWZ7M
[Nexus 6  Original Android Development] joderme:
Now ya tell me :)

I did it again w/o SuperSU and it works. I get the "android failed verification... And then for help go-to g.co/AndroidBootHelp" when it boots, however, it eventually boots.
[Nexus 6  Original Android Development] SamuriHL:
Yea don't try to root it. Chainfire said he's going to look at root today. If you can set selinux to permissive it'll boot. Otherwise just wait for a new solution.
[Nexus 6  Original Android Development] DesignGrits:
How do you set selinux to permissive if you can't boot the device?
[Nexus 6  Original Android Development] SamuriHL:
You get a modified kernel and flash it, which is not something I know how to make. Someone in the supersu beta thread made one for the NX9 and is saying he'll do it for the NX5 later, as well.
[Nexus 6  Original Android Development] DesignGrits:
Cool, thanks.

Yeah I flashed SS and was running into that error boot message so I decided to re-flash the System and Boot images and start fresh, which worked and I am able to get into my device, but that message still pops up. At this point would it be wise to just wait for ChainFire to upload a new version?
[Nexus 6  Original Android Development] SamuriHL:
Very likely. The joys of being on the bleeding edge (flashing an M developer preview release) is that sometimes we'll bleed. ;)
[Nexus 6  Original Android Development] jm77:
Same issue. Tried to root via SuperSU, but then the system wouldn't boot. Re-flashed boot and system and it came up after a few seconds.

I'll just wait for a fix.
[Nexus 6  Original Android Development] sn0warmy:
Guys, if you want to eliminate the "verification failed" error message at boot, just flash the stock recovery and then perform a factory reset within the stock recovery and reboot. It eliminates the verification failed message. I can confirm that this is the solution, for now.

The only downside is that if you re-install TWRP afterwards, the message comes back. I imagine that TWRP will be updated shortly to correct this. But I'll remain on the stock recovery until TWRP is updated.
[Nexus 6  Original Android Development] jm77:
I was trying to avoid doing a factory reset and having to start over from scratch again.
[Nexus 6  Original Android Development] sn0warmy:
Unfortunately, you have to do the factory reset and go back to stock recovery if you want the message gone now. Otherwise, hold out until TWRP gets updated to correct this. No idea when that will be though.
[Nexus 6  Original Android Development] fitz420:
Yeah. All good.
[Nexus 6  Original Android Development] iStayHigh:
Yup that's what I had to do to get rid of that message, factory reset in stock recovery and booted up fine with no message

Sent from my Nexus 6
[Nexus 6  Original Android Development] GuyInDogSuit:
Well, that's great. I was wondering why I was getting a black screen when flashing SuperSU....
[Nexus 6  Original Android Development] Aqua1ung:
Hi guys, what is the deal with that "Writeable SD" message? Is it safe to say "yes"? Note that I am rooted on a T-Mobile Galaxy S6, and I am in the process of installing a custom recovery using TWRP Manager.

Thank you!
[Nexus 6  Original Android Development] danarama:
Not sure, we're on the Nexus 6 here
[Nexus 6  Original Android Development] z31s1g:
Note that you posted in the Nexus 6 thread, not sure anybody here can help you much with your question...[emoji6]
[Nexus 6  Original Android Development] GuyInDogSuit:
You might want to ask that in the T-Mobile Galaxy S6 forums. This is for the Nexus 6.
[Nexus 6  Original Android Development] HumpDdumpD:
ElementalX's latest kernel is booting up without the error message. It's permissive by default.
[Nexus 6  Original Android Development] rebretz000:
Happened to me also. I fastbooted stock recovery back in
[Nexus 6  Original Android Development] artpena2323:
Flash Back To Stock

Whats the easiest way to flash back to stock?
[Nexus 6  Original Android Development] Acrono:
Here you go. Nexus 6 isn't an option.
[Nexus 6  Original Android Development] linuxares:
Thank you Team TWRP :D
[Nexus 6  Original Android Development] Cy_n_ic:
Wugs toolkit that was recently posted in android development

via Glade PlugIns
[Nexus 6  Original Android Development] artpena2323:
Sweet. Exactly what iwas looking for. Thanks
[Nexus 6  Original Android Development] tonyfiore75:
I tried using this. I got to the point where I'm supposed to Navigate to "'.sdcard/!ReadyToFlash/Root_Files'... but within recovery it tells me that my Internal Storage (0 MB). How is that possible? It doesn't see my internal storage. Any clues?
[Nexus 6  Original Android Development] Cy_n_ic:
Do you have the option to mount internal storage from settings in recovery. Sounds like its not mounted

via Glade PlugIns
[Nexus 6  Original Android Development] rebretz000:
Is there a way to turn off vibration?
[Nexus 6  Original Android Development] RandoTheKing:
Isn't it annoying as **** on this phone? Wish I could lower it
[Nexus 6  Original Android Development] Dees_Troy:
Settings -> Vibration and slide the sliders all the way to the left.
[Nexus 6  Original Android Development] rebretz000:
I did that but mine still vibrates. I only have two slider options.

Is there a third one? Perhaps I got a bad download.
[Nexus 6  Original Android Development] thrillerbee:
TWRP isn't sticking for me after a reboot. If I 'fastboot flash recovery openrecovery-twrp-2.8.2.0-shamu.img" from bootloader and navigate to and select "recovery", I can see TWRP one time. After any subsequent reboot, I get the "no command" sad Android like I'm back to stock recovery. Any thoughts or suggestions?
[Nexus 6  Original Android Development] allen099:
After running ChainFire's Autoroot, it appears to be sticking now. I don't know if that had anything to do with it or not, but somehow I can now get to it. Also, you may want to try WugFresh's Nexus Root Toolkit that he put out yesterday.
[Nexus 6  Original Android Development] thrillerbee:
I don't have a Windoze machine to use to try the toolkit. I'm flashing the 2.27 BETA SuperSU now to see what it does...
[Nexus 6  Original Android Development] allen099:
Definitely. You can do it on Mac and Linux as well. Assuming that your bootloader is already unlocked...

1) Download and unzip the file to your computer desktop from here: download.chainfire.eu/628/CF-Root/CF-Auto-Root/CF-Auto-Root-shamu-shamu-nexus6.zip

2) Boot your phone into the Bootloader and connect it to your machine

3) Run a fastboot devices command to make sure your serial number is visible. After that, run the command within that Auto Root folder that pertains to your OS. The command line will walk you through what to do.
[Nexus 6  Original Android Development] Acrono:
Same issue here in 2.8.2.1.

There's no slider for "Button Vibration". It's set to 80 and you can't change it.

The other two, "Keyboard Vibration" and "Action Vibration", I have both sliders set to 0. Still getting vibrations.
[Nexus 6  Original Android Development] popfan:
Try in Sounds & notification - other sounds

There is a vibrate on touch there
[Nexus 6  Original Android Development] Acrono:
We're talking about TWRP, not in Android. It's a minor annoyance, and obviously, in the grand scheme of things, inconsequential.
[Nexus 6  Original Android Development] :
Problem flashing

Just sitting down to do the fun stuff to the nexus 6 but ran into a problem flash twrp. Boot loader is unlocked, and rebooted into android.

When I go to fastboot flash recovery recovery.img, I get this message

"

targetreported max download size of 536870912 bytes

sending 'recovery' <4KB>...

OKAY [ 0.16s]

writing 'recovery'...

<bootloader> Invalid boot image

FAILED <remote failure>

finished. total time: 0.016s

"

Any ideas? Other than unlocking bootloader, device is stock. Any help would be greatly appreciated!
[Nexus 6  Original Android Development] mkeller96:
Has anyone else had a problem with the clock time being incorrect and not being able to change it?
[Nexus 6  Original Android Development] JRJ442:
You should be able to go into settings and adjust the clock for whatever time zone you're in. Mine got off by an hour once.
[Nexus 6  Original Android Development] mkeller96:
I tried but changing time zone has no effect on time...
[Nexus 6  Original Android Development] JRJ442:
I'm assuming you did tap the Set Time Zone button after you selected the time zone you're in right? It's working fine for me. Are you using a theme?
[Nexus 6  Original Android Development] AlxMAX:
Is your phone content encrypted?
[Nexus 6  Original Android Development] mkeller96:
No, I was finally able to get the right hour but can't get the minutes right even when using offset. Also note that my time zone was completely wrong. I had to use one I've never heard of to get the correct hour.
[Nexus 6  Original Android Development] PresidentMcCain:
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.
[Nexus 6  Original Android Development] Thunderbolt69:
I also had the same issue when trying TWRP 2.8.7.0 and had to flash back to the previous version.
[Nexus 6  Original Android Development] brizey:
Yep. I've learned over the years that the .0 release of TWRP usually has a bug.
[Nexus 6  Original Android Development] ironjon:
Yes exactly same here

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6  Original Android Development] eng.stk:
Before anyone asks, no there isn't f2fs support yet on 2.8.7.0
[Nexus 6  Original Android Development] sansnil:
Just upgraded to 2.8.7.0 and definitely started having this issue on my Nexus 6. I never had issues with this previously - I think it's calculating the time change in reverse order incorrectly.

I'm also having the pattern lock / password decryption error others have reported. Back to 2.8.6.0 for now.
[Nexus 6  Original Android Development] 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/
[Nexus 6  Original Android Development] casonswag:
7.1 is woeking fine for me but i dont understand what the new system image backup is for?
[Nexus 6  Original Android Development] c@p:
Anyone a hint what this new backup option does?
[Nexus 6  Original Android Development] dany20mh:
I haven't tried it yet, but there is this one here:

http://files.oceighty.co/recovery/twrp-2.8.7.1-f2fs-xanaxdroid.img
[Nexus 6  Original Android Development] brizey:
It allows you to backup a pristine system image that your can restore and take an ota. Previously, if you have ever mounted system r/w the stock otas can fail.

For myself, I've never understood the obsession with otas around here... The whole point of XDA is to enhance the stock experience. Flashable zips are usually available within a day or two, and you can always just flash the image that Google posts.