yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] simms22:
no. you flashing a kernel that allows for decryption, then you formatting your entire storage manually will decrypt your phone, nothing else will.
[Nexus 6  Original Android Development] andreak:
Thanks a lot! Can you please explain what's going on when rebooting to recovery .....I read this message everytime, then if I check in settings, security i ' m still encrypted, so what was decrypted correctly according to that screenshot?
[Nexus 6  Original Android Development] simms22:
"decrypted" so that the recovery can now read it. its not telling you that your phone is decrypted, its telling you that twrp decrypted your data successfully so that it can now be used properly.
[Nexus 6  Original Android Development] andreak:
I' m asking because i was arguing with some guys, they say that if you install twrp you are decrypted then and they say it because of the statement in the screenshot, whatever displayed in settings/security......again, thank you very much!
[Nexus 6  Original Android Development] simms22:
na. it just has to be able to decrypt your data so that it could read it. if you set up a password for your rom, it would ask you for that password so that it could decrypt everything. you can always boot up and go into your options, into security, and itll say if you encrypted or not.
[Nexus 6  Original Android Development] Droidphilev:
Well.... they can flash an old rom as rom/bootloader seem to work together in this "device protection". I had locked myself out before and fixed it by only restoring a lollipop rom.
[Nexus 6  Original Android Development] starcms:
True, but devices that come with Marshmallow (or newer) stock (N6, N6P, N5X, amongst other non Nexus devices) have no option to revert to Lollipop. So things are definitely getting safer.

A modern device that originally came with Android 6.0+ can be encrypted and no user data can be recovered without password. Plus, with Device Protection, even if an encrypted or unencrypted phone (unlocked or locked bootloader), is wiped, it can never be used again without logging in with a Google account previously synced to the phone.

Not to mention the external Google control features such as locating it via GPS, locking phone, changing password, or disabling from use.

I personally find the Device Protection added in Marshmallow in addition to previously existing security measures to be much more than adequate.

The only thing someone who steals an encrypted phone is wipe the data. So if you keep a backup not on your phone, you are perfectly safe and won't lose any data in worst case situation.

And not to mention, criminals know this too. Hence the reason smartphone thefts are dropping significantly since the introduction of Google's Device Protection and Apple's similar security measures. They can no longer take a phone with a bad (stolen) imei and simply sell it for use outside the US on eBay. Now it's just a brick.
[Nexus 6  Original Android Development] EA1DDO_SGS2:
v3.0.0.1 is available to download in the official web site.
[Nexus 6  Original Android Development] Alxoom33:
Thanks, but it has been there since February 11th.:)
[Nexus 6  Original Android Development] bdsullivan:
This is the error message I am getting since updating to the latest version of twerp. Can someone please help.
[Nexus 6  Original Android Development] rrrrrrredbelly:
Sorry if this has been covered, flashing a radio image in twrp, do i choose system or boot? Guessing system, just wanted to make sure.

Thanks
[Nexus 6  Original Android Development] iluvatrix:
have noticed on https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html it says "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." which i take it to mean 3.0.0.1 is a shamu device specific fix for 3.0.0.0. anyone knows what had been fixed?
[Nexus 6  Original Android Development] z31s1g:
Noticeable change was the added ability to backup/restore system and vendor partition.
[Nexus 6  Original Android Development] christianpeso:
This post explains 3.0.0-1.

http://xdaforums.com/showpost.php?p=65393944&postcount=861
[Nexus 6  Original Android Development] z31s1g:
Thanks for reminding me of what I posted [emoji2].
[Nexus 6  Original Android Development] cam30era:
Radio.img is flashed to radio.... If that option isn't available, then use fastboot.
[Nexus 6  Original Android Development] Alxoom33:
I'm on N6 and have been using the N beta OTA. Have been able to fastboot flash TWRP 3.0.0 and 3.0.1 however they don't stick. Any progress in making a recovery for Android N?
[Nexus 6  Original Android Development] Droidphilev:
I flashed N system.img and unencrypted kernel img and have no problems at all (twrp 3001)
[Nexus 6  Original Android Development] Alxoom33:
Yeah, but you killed any chance of future OTA's.
[Nexus 6  Original Android Development] simms22:
ota.. who really needs them? i havent had an ota in 7 years, yet im on each new build number as fast or faster than those taking an ota.
[Nexus 6  Original Android Development] Alxoom33:
That's wonderful! Congratulations! But so did I and very many users who flashed various custom Roms and Android factory images for the last 10 years or so!

:silly:

That's not the point.

However, for N I am trying to preserve my ability to get Google's OTA's while still having a rooted device.

:angel:
[Nexus 6  Original Android Development] HueyT:
Could you share a link to the "unencrypted" boot or kernel img?

EDIT: Found it in the Skydragon thread in "Nexus 6 Android Development" forum:

https://www.androidfilehost.com/?fid=24438995911975928
[Nexus 6  Original Android Development] simms22:
as unrelated to twrp as this seems, its also very related to twrp.. today is [MENTION=244907]AmonRA[/MENTION]'s birthday :)
[Nexus 6  Original Android Development] CRXed:
Does anybody have a way to solve the date / time being wrong for the Auto Generated backup name?

It's always set to 1970 for me.
[Nexus 6  Original Android Development] sansnil:
Even after you set the date and time in settings?
[Nexus 6  Original Android Development] Shamestick:
Recently I have been experiencing a myriad of flashing failures due to "zip verification failed" error. I had gone from official 3.0.0.1 to multirom twrp from app when it started, things failing to flash even with correct md5 and even zips I had flashed before successfully.. so I thought it might be the multirom twrp causing issues so I went back to official 3.0.0.1 and the issues persist. A couple roms flash, but most things don't go through and I have to uncheck zip verification as I know they're okay since I've flashed them before successfully. I can grab a recovery log or other if needed, don't really know what helps in this situation.
[Nexus 6  Original Android Development] rignfool:
Unchecked zip verification?
[Nexus 6  Original Android Development] DSDONE:
I absolutely love the new TWRP! The older one worked fine but, it's looks got dated. This newer look is greatly received and appreciated!
[Nexus 6  Original Android Development] grgana:
Hy, im gonna ulock bootlader and install twrp ad superSu, after a custom rom. Now I'm in comlete stock condition (encrypted).

Will twrp is going to ask me for some password, (i dont have pin or any kind of lockscreen beside slide to unlock,)

What shoud i do if TWRP ask me for password,..

I've read something about default password
[Nexus 6  Original Android Development] HueyT:
You'd stay encrypted if your \data is encrypted once you rooted and install TWRP 3.0.0.1. To become unencrypted, you must back up your data to laptop and/or USB OTG and then format your data. Then use "unencrypted" kernel or boot.img to stay "unencrypted". I recommend using WUG root kit to do all this (google for it, you need to install Google USB drivers and adb drivers for the kit or fastboot to work)
[Nexus 6  Original Android Development] sjgore:
Just flashed 3.0.1.0, and it doesn't work with encryption: just tells me my password is wrong all the time. Back to 3.0.0.1 and password works fine again.
[Nexus 6  Original Android Development] 8zabi:
same problem here
[Nexus 6  Original Android Development] spainter:
Running it fastbooted, not flashed, on a stock Nexus 6 with MM 6.01 with no problems with being encripted.
[Nexus 6  Original Android Development] iluvatrix:
Installed via twrp manager also no problem being encrypted
[Nexus 6  Original Android Development] sjgore:
Interesting. I flashed using Flashify.

Have you got it set to require a PIN on start-up (the question it asks you in Lockscreen settings when you set the PIN)? I wonder if that makes a difference.
[Nexus 6  Original Android Development] spainter:
I have a pin setup but only for the lock screen. I don't get asked for a pin while booting. So it is using the default password for the encryption.
[Nexus 6  Original Android Development] kwdan:
Just googled it.. I knew that i had seen that name. I remember that from the EVO days. First phone i ever rooted. I was so scared back then. Only rooted for the tethering.. Now root means so much more to me..
[Nexus 6  Original Android Development] abalam:
I don't can make a backup. What I see is this.Have make my backup folder clean but stil this error. Ps latest twrp 3.0.0.1
[Nexus 6  Original Android Development] Alxoom33:
I have also been having this problem. It only fails on the System backup, if you uncheck System it will back up everything else, even System Img. I think it dosn't like backing up any modified System partitions. For example, I have layers and NavZ running, which are in the System Partition.

Any help would be appreciated. Thanks,

---------- Post added at 02:48 PM ---------- Previous post was at 02:47 PM ----------

I was able to back up my rooted Nexus 6, when the System Partition was not modified.
[Nexus 6  Original Android Development] abalam:
When I downgrade to 2.8.7.1 I have stil the problem.Wt***
[Nexus 6  Original Android Development] simms22:
you have root, your system partition is modified.

regardless, ive never had an issue with twrp backing up. it ALWAYS backs up everything, having root, with a heavily modified system partition..
[Nexus 6  Original Android Development] abalam:
And how we can fix this simms22
[Nexus 6  Original Android Development] Alxoom33:
[MENTION=631273]Chainfire[/MENTION] has developed Systemless Root. Keeps System partition completely clean if installed correctly. There is an XDA thread, if you search on Google or in XDA Chainfire Systemless Root you should be able to find it.

---------- Post added at 03:05 PM ---------- Previous post was at 03:02 PM ----------

No. Not necessarily. See my post above regarding Chainfire's Systemless Root.

---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------

Uncheck the box for System, back up the rest, including your data. You can restore and reflash your Rom with the System separately.
[Nexus 6  Original Android Development] abalam:
And still have a full backup of my rom when I Flash the rom after restore?
[Nexus 6  Original Android Development] simms22:
yup, systemless root, i forgot.

---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------

all i ever back up is system, boot, and data. and it never errors out, unless i have no space, then theres an error in the begining.
[Nexus 6  Original Android Development] Alxoom33:
If you modified the system, the above error apparently comes up. I worked around it by unchecking the System box. But you will be missing that partition in the Nandroid.

---------- Post added at 03:23 PM ---------- Previous post was at 03:22 PM ----------

No! It's a workaround. Your Nandroid will not have the full system. You will have to reflash the Rom first and then restore the Nandroid.
[Nexus 6  Original Android Development] abalam:
Problem solved. Have make a backup without system (uncheck it) afther that dirty flash my rom. Reboot is and testing for backup and it's working again. Tnx guys!!![emoji106] [emoji106] [emoji106] [emoji106]
[Nexus 6  Original Android Development] spainter:
Rooted and encrypted Nexus 6, Backed up all 9 available partitions which includes the system and system image with out a problem. Restores with out a problem as well. You may want to look at other things to find your problem.
[Nexus 6  Original Android Development] abalam:
Delete
[Nexus 6  Original Android Development] NLBeev:
I did that the same way. But recently I changed. I.m.o back up of the data partition is enough. Caches can be wiped and system can be reflashed.

I will appreciate your response about the need of backing all partitions, incl. system image.
[Nexus 6  Original Android Development] Alxoom33:
I agree, however if it is stock rather than a custom ROM, it's a little more involved to reflash System.
[Nexus 6  Original Android Development] NLBeev:
Yes, that is true...... More thanking/liking to the dev's making custom Rom's. ?
[Nexus 6  Original Android Development] Alxoom33:
FYI, TWRP 3.0.1 working flawlessly with Nexus 6, Stock, and Rooted versions running latest MMB29V with Cata Mod, Layers, NavZ.
[Nexus 6  Original Android Development] Formhault:
Is cataclysm still alive? :/
[Nexus 6  Original Android Development] Alxoom33:
Yes, as long as you are on MM. Here is a link to the thread. http://xdaforums.com/showthread.php?t=3307703

Not for Android N, however, as of yet. :_{
[Nexus 6  Original Android Development] Nergal di Cuthah:
Is 3.0.1 showing up in TWRP manager for anybody, I finally gave up a manually installed it?
[Nexus 6  Original Android Development] simms22:
yes
[Nexus 6  Original Android Development] Nergal di Cuthah:
ok then i'll attempt a data and cache clear for manager. Thanks for the response.

Edit

Nope same issue, manager says I have 3.0.0.-1 not 3.0.1 and shows 0.0-1 is last available
[Nexus 6  Original Android Development] simms22:
3.0.0-1 is what it shows here as well, my bad, sorry :angel:
[Nexus 6  Original Android Development] Alxoom33:
No, you need to DL directly from TWRP site.
[Nexus 6  Original Android Development] ggfool:
I installed version 3.0.1.0 via adb and it says my password is wrong every time i try to decrypt my data, it is a pin password and i know i am using the right one (still works to boot the phone) going to try installing 3.0.0.1 and see if it works...

edit: works fine on 3.0.0.1
[Nexus 6  Original Android Development] holeindalip:
Same here password always wrong
[Nexus 6  Original Android Development] simms22:
you used fastboot, not adb
[Nexus 6  Original Android Development] iluvatrix:
erm how is it even done via adb?
[Nexus 6  Original Android Development] pittrich:
I used flashify, same issue here. My old pin with 3.0.0 fail on 3.0.1.

Any solution?
[Nexus 6  Original Android Development] Nergal di Cuthah:
now shows correctly, weird[emoji38]
[Nexus 6  Original Android Development] skidaway:
The encryption problem seems to be widespread, I'm sure a fix will come soon.

https://github.com/TeamWin/Team-Win-Recovery-Project/issues
[Nexus 6  Original Android Development] Omar04:
DO NOT INSTALL twrp-3.0.1-0-shamu.img many issues like "can't decrypt device" or in some cases like mine it doesn't even flash via fastboot. ProTip: Stay on twrp-3.0.0-1-shamu.img until a new one comes out.
[Nexus 6  Original Android Development] Aqua1ung:
System software not authorized by AT&T has been found on your phone

Manually flashed the latest TWRP .img file (3.0.1-0) in TWRP 2.8.x.x, and now phone boots into "System software not authorized by AT&T has been found on your phone" triangle screen. Was running CM13 on i337 (AT&T SGS4) with TWRP 2.8.x.x recovery, and everything was fine and dandy. Please help!
[Nexus 6  Original Android Development] holeindalip:
Please tell me your joking right?
[Nexus 6  Original Android Development] ricco333:
That sucks big time, you may want to ask around in the SGS4 i337 thread, since this one is for the Nexus 6 and most folks here have no idea or clue regarding Samsung related recovery problems, my only suggestion is to restore the recovery back to 2.8.x.x.

Good Luck man

Erik
[Nexus 6  Original Android Development] pittrich:
Can I downgrade to 3.0.0-1 from 3.0.1-0 without issues?
[Nexus 6  Original Android Development] simms22:
it isnt
[Nexus 6  Original Android Development] Aqua1ung:
Well, I flashed the i337 recovery, downloaded from TWRP's website. Anyway, thanks, I'll direct my inquiries to the i337 forum.
[Nexus 6  Original Android Development] christianpeso:
Yes you can.
[Nexus 6  Original Android Development] mondohow:
Delete... wrong device thread... but hopefully coming for our N6 as well.

Encrypt/Decrypt bug has been identified and fixed as per: https://plus.google.com/+DeesTroy/posts/jk9dwNrhnQ8
[Nexus 6  Original Android Development] wase4711:
you posted a link to hammerhead, NOT to shamu, our device!!!
[Nexus 6  Original Android Development] mondohow:
Yeah I already fixed it... Too many Nexus devices and following too many Nexus threads

Encryption bug has been found and fixed so we should get a new build soon as well.
[Nexus 6  Original Android Development] wase4711:
i'm gonna wait a few days and let the test monkeys try out 3.02 and see if any issues like 3.01 show up..never want to be the first to try a new recovery..
[Nexus 6  Original Android Development] SamuriHL:
3.0.2.0 is out for us.
[Nexus 6  Original Android Development] pittrich:
3.0.2-0 is online and I've flashed. Perfect! Thanks for your help.
[Nexus 6  Original Android Development] mondohow:
Nice. Updated earlier and no problems so far. Have you tried to make a backup yet? I'll have to wait till I get home to try.
[Nexus 6  Original Android Development] Alxoom33:
Thanks, Samuri. Look at my sig. Finally replaced my Xoom with a Nexus 10.2 that I have been waiting for, AKA Pixel C. :)
[Nexus 6  Original Android Development] SamuriHL:
Not bad, not bad. :) I've been using my NX6 more than anything. And 3.0.2.0 has so far been rock solid in my testing. Then again, I only boot it, I don't flash it.
[Nexus 6  Original Android Development] Alxoom33:
Haven't tried it yet. Been recently using 3.0.1.0 on my N6 without issue. Dl'd 3.0.2.0 for when it is needed. I am on N beta, so I can't flash it right now.
[Nexus 6  Original Android Development] rignfool:
Can't the dd command be run from adb?
[Nexus 6  Original Android Development] :
I Cannot get successful on my backup,twrp 3.0.2, n6, pn 4/5, xposed, ex kernel, it hangs at 4088 of 4033 mb, backup defaults, system, data, and boot..

Additionally on my s5 twrp 3.0.2-1, i cannot flash anything. On both devices I had to revert to twrp 3.0.0.
[Nexus 6  Original Android Development] ECrispy:
Is there a dark themed version of TWRP 3.0.2 ? One that doesn't need a ui themes folder on the phone?
[Nexus 6  Original Android Development] smclaughlin3:
How do i decrypt with twrp recovery? Thanks
[Nexus 6  Original Android Development] hlxanthus:
You need to format data. Go to the wipe menu, select format data. This will completely wipe everything including internal storage, so create a nandroid of your current setup then back up your internal storage including your nandroid. Make sure you are on a kernel that doesn't force encryption. Boot android. This will build the proper structure of the data partition for multi user. Then copy back at least your nandroid to the storage, boot to recovery and restore the nandroid.
[Nexus 6  Original Android Development] electricpete1:
What is the navbar icon on the right side of the navbar ? (I know about back and home but not that third one)

It looks like 4 horizontal lines, with the middle two shorter and everything left-justified

I pressed it and got some kind of decrypting message.

When should this button be used?

(sorry for noob question and thanks in advance... searching hasn't shown any clues to me.)
[Nexus 6  Original Android Development] donjuro:
Anyone else get "invalid boot image" when trying to flash twrp?
[Nexus 6  Original Android Development] simms22:
are you trying to flaah twrp with twrp? it doesnt work that way, unless you pick recovery.img, not boot.img
[Nexus 6  Original Android Development] donjuro:
I just realized twrp hadn't downloaded correctly. All good now.
[Nexus 6  Original Android Development] Alxoom33:
I have been getting an error 255 which has stopped me from making System backups. If uncheck System then backs up everything else. I have gotten this error on 3.0.1 and 3.0.2. I have reverted back to 3.0.0.1 which does not appear to have this issue.

I am using a Nexus 6 and the errors are in backing up MM 6.01 29V and Android N Preview stock based Roms.
[Nexus 6  Original Android Development] abalam:
Flash rom again. Wich rom and kernel you use. Has the same problem here. Solve it with dirty flash rom. Problems with some kernels. On ElementalX NO problems with nandroid. Pleace feedback, rom and kernel...
[Nexus 6  Original Android Development] SamuriHL:
https://developers.google.com/android/nexus/images

Grab the factory image there. The recovery img is in the download.
[Nexus 6  Original Android Development] mr pnut:
Appreciate the fast reply bro thx.......:)
[Nexus 6  Original Android Development] azn6929:
Crashed while flashing ?

Hi guys,

I tried to install it via TWRP Manager, however it crashed all the time.

Please help :(
[Nexus 6  Original Android Development] papi92:
Any news on the open sourcing your device tree edits?
[Nexus 6  Original Android Development] njd.sina:
Any idea if Flash Image GUI can be used to push the recovery file?
[Nexus 6  Original Android Development] :
Someone had posted that flashify works so my guess is yes, probably.
[Nexus 6  Original Android Development] hsj1906:
Same issue. :(
[Nexus 6  Original Android Development] rebretz000:
Wondering if the option to wipe dalvik cache could/should be removed since 5.0 only has ART

Sent from my Nexus 7
[Nexus 6  Original Android Development] paychex:
I don't think it's completely gone
[Nexus 6  Original Android Development] zeiroe:
TWRP Prompts for Password Even Though I Didn't Set One

Hey guys,

Wanted to give everyone here a heads up. I flashed TWRP and everything works great ... then I decided to play with some lollipop security features. I messed around and enabled the "Require Pattern Before Boot" feature and it seems to work fine. I just found out that having this enabled causes TWRP to boot and ask for a password if you boot into recovery. I never set a password so I wasn't able to mount or do anything to the partitions. Like in the past, a factory reset should correct the issue but for this instance the data wipe isn't necessary. Just disable this feature and TWRP boots and partitions are mountable again. I don't think this problem applies to those who are unencrypted but I wanted to share this finding in case someone who is encrypted can't access their partitions in TWRP.
[Nexus 6  Original Android Development] brizey:
You just do your pattern on the keypad.
[Nexus 6  Original Android Development] zeiroe:
There's no place to put a pattern in on TWRP
[Nexus 6  Original Android Development] Cheater912:
The pattern maps to 0-9. So the top-left dot is 0, and the bottom-right dot is 9.
[Nexus 6  Original Android Development] zeiroe:
Oh snap!! Thanks for this info. The pattern was 1-9 instead of 0-9, but this did it. Thanks!!
[Nexus 6  Original Android Development] akellar:
It's in the op...
[Nexus 6  Original Android Development] Cheater912:
You're welcome! Thanks for the correction. Derp