yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] silvers01:
the other day i experience a sudden random reboot. random reboots are always happening. but this time my phone won't proceed as normal after rebooting. phone stucked at samsung logo (where the yellow triangle usually appears). also i cannot proceed pass to recovery logo, i'm using TWRP 3.0.2.1 stucked at twrp logo too and cannot proceed to where the controls are. but download mode seems fine. i tried flashing recovery through odin and heimdall but it fails.

i don't know if download mode is also getting stuck/freeze. but odin seems to recognize the phone but i cannot flash any recovery/kernel.

pls help me. i also want to recover my files. using adb pull doesn't work also as it cannot read my device.

my current rom is resurrection remix m.
[Galaxy S II Q&A, Help & Troubleshooting] MigoMujahid:
Try flashing this one, if it succeeded, make a clean installation.
[Galaxy S II Q&A, Help & Troubleshooting] silvers01:
is it isorec?
[Galaxy S II Q&A, Help & Troubleshooting] MigoMujahid:
No it's cwm kitkat compatible recovery, use it to flash isorec kernel then TWRP 3, and then flash the rom.

Flash that recovery with Odin, and in recovery, flash this kernel, and flash TWRP 3, then reboot recovery and you should find TWRP 3 installed.
[Galaxy S II Q&A, Help & Troubleshooting] silvers01:
flash fails :crying:
[Galaxy S II Q&A, Help & Troubleshooting] MigoMujahid:
Be specific what flash

In odin or recovery?

Edit: i see now it fails in Odin, what version of Odin do you use?

Also try other cables and USB ports, and make sure you installed the drivers correctly
[Samsung Galaxy S7 Edge Questions and Answers] left13:
Hello,

I am about to buy nexus 6p. The main reason is the pure android for app development.

There is also the s7 edge for 50 euros more in my country.

Considering google stops guaranteed updates on September 2017 for nexus devices, does the s7 opens the possibility for continous support by updates and custom roms, so i can keep on latest features and stuff ?

Really need some help here.

Thanks a lot
[Samsung Galaxy S7 Edge Questions and Answers] Micheal86:
If you want original android and Google`s guaranteed Update then you should go for Pixel devices (obviously if money doesn`t matter). Though nexus 6P is an excellent device,and the Nexus 6P is the best Nexus ever made, but it`s bit old(2015),though it has also excellent XDA support.

But my vote goes to S7 Edge.It`s an awesome device with faster processors, a better camera and a bigger battery to boot and full of features and excellent XDA support.google may stops guaranteed updates for Nexus Devices in future, but I think it`s impossible for Samsung to do the same for S7/S7 edge.But you`ve to spend some extra (as you`ve already mentioned).

Go for S7 Edge and hope you`ll not be regretted.

Now it`s your choice.
[Samsung Galaxy S7 Edge Questions and Answers] fedef12evo:
Had 6p sold because poor performance and Zero battery, buy s7 edge it is better phone
[Samsung Galaxy S7 Edge Questions and Answers] thedarkmunk:
I've had both! I prefer the S7 Edge, and it's what I'd recommend simply because it's much newer, the camera is better and well, even though you don't get the speedy updates from Google via the Nexus 6P, Samsung are pulling their fingers out of their butts and they're improving it!
[Samsung Galaxy S7 Edge Questions and Answers] Shipoftheline:
The S7 Edge will have longer support, be faster, better battery life, batter camera, better screen, more ram................hmm which one to get
[Samsung Galaxy S7 Edge Questions and Answers] andiling:
Supportwise wait for the S8 since once that is released the S7 will be in second row.
[Samsung Galaxy S7 Edge Questions and Answers] left13:
yeah, I would love a pixel one, when it gets lower in price, maybe later.
[Samsung Galaxy S7 Edge Questions and Answers] B3311:
I really don't see why you're "so confused". The very first thing that you say you want is "pure android", which isn't and never will be Samsung's goal or target market. And since that is your #1 priority, why would you consider a device that's 2+ years old?

I like my S7e. But you need a Pixel.?
[Samsung Galaxy S7 Edge Questions and Answers] left13:
Thanks for your response,

As I said in my first post 'is about google stopping updates' after september that's trouble me.

Sure, pure android is the way to go for me but i'm not gonna spend so much for a pixel atm.

As long s7 takes the nougat update or maybe even the next version that's ok with me.

Is there a chart or something for s7-s8 upcoming android versions/updates?
[Samsung Galaxy S7 Edge Questions and Answers] ClaudioJuniorBR:
Go on Galaxy s7 edge.

is nice device and have alot custon rons and aplication.
[Samsung Galaxy S7 Edge Questions and Answers] andiling:
Not worth the money in my idea, too.

Nougat is already on the way and the S7 will get Android O as well; just a question of time.

No and if it would not be reliable at this time.

However, for Galaxy flagships you can always count on release version plus two more (S7 was released with M and will get N and O, S8 will be N with O and P).

Google itself says two years for its devices which is usually release plus one and probably one more for its devices.
[Samsung Galaxy S7 Edge Questions and Answers] Shipoftheline:
From what we know the S8 has the same camera and battery, smaller on the 8+ so it makes more sense to get the cheaper S7 Edge
[Samsung Galaxy S7 Edge Questions and Answers] andiling:
But the S8 will have one year longer support and will be in the front row regarding updates once released.
[Samsung Galaxy S7 Edge Questions and Answers] Shipoftheline:
And, I've got the S7 Edge (G9350) now and still waiting for Android 7!
[Samsung Galaxy S7 Edge Questions and Answers] left13:
I'm sure it will.

But what about its cost ?

range of 700-800 euros ?

Because i'm talking about 500 euros here, for the s7 edge exynos
[AT&T Samsung Galaxy S7 Edge Questions & Answers] Inferati:
Hello,

I've read a ton of the forum threads as to how to flash the T-Mobile firmware to an ATT S7 Edge. I feel like I've followed all instructions; however, I keep getting and SHA256 error or odin invalid depending on different versions. With Android 7.0 recently coming out, I'm not sure if it has anything to do with it. Can anyone help me out?
[OnePlus 3T Guides, News, & Discussion] rahulrs0029:
Disclaimer: I have done these steps multiple times and haven't come across any issues

Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.

If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.

Follow these steps:

1. Download the OxygenOS full zip file (tested on 4.0.1 & above)

2. Open TWRP.

3. When It asks for password, cancel it.

4. Click "Read Only" button.

5. Install the OxygenOS zip file.

6. Reboot.

7. The OS may misbehave.

8. Open TWRP again. & Boom! No encryption password.:cool:

9. Connect to PC and copy the Important data.

10. Flash Any ROM now.​
[OnePlus 3T Guides, News, & Discussion] svandasek:
Thanks!

Recently I had to type in the password but I didn't know that it is possible to bypass it with this... :)
[OnePlus 3T Guides, News, & Discussion] rahulrs0029:
Glad it helped you :)
[OnePlus 3T Guides, News, & Discussion] derbestimmer:
ah.... if i only knew :crying:
[OnePlus 3T Guides, News, & Discussion] maddler:
That's good from a data recovery point of view... but it just sucks from a security point of view.

Not sure if I should be happy or concerned ;)
[OnePlus 3T Guides, News, & Discussion] tk8lm6:
TWRP Encryption ByPass

Agree .... that seems like a gaping security vulnerability. :-/
[OnePlus 3T Guides, News, & Discussion] smaeul:
There's no need to be concerned (about this, specifically).

Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.

On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.

What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
[OnePlus 3T Guides, News, & Discussion] maddler:
No arguing that previous versions were less secure. But, still, as long as there's a way to bypass encryption that's a security failure.

Encrypted data shouldn't be made available unless proper key(s) or passwords have been provided.

If that's the way that's meant to work, then that's flawed by design.
[OnePlus 3T Guides, News, & Discussion] rahulrs0029:
I've tried many times. OOS replaces TWRP only on CLEAN Instal for me.
[OnePlus 3T Guides, News, & Discussion] manchitro:
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
[OnePlus 3T Guides, News, & Discussion] crian:
Just flash it.
[OnePlus 3T Guides, News, & Discussion] GoJo ^^:
Wait, are you saying by just installing a zip, the encrypion hardware pass is gone? WTF.. Is such "hack" available on other devices? Xiaomi redmi(s) for example?
[OnePlus 3T Guides, News, & Discussion] SourPower:
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?

i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?

im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
[OnePlus 3T Guides, News, & Discussion] Sis42:
Yeah same issue here, as soon as I go in twrp and can't type the password, I can't access my files which is expected behavior, so I don't understand how you can access the file to flash from twrp.

Can someone detail please?

---------- Post added at 07:06 PM ---------- Previous post was at 06:40 PM ----------

Actually I just found a way out to get to previous twrp version, and all is back to normal :)

From your running ROM, you can download the application twrp (root needed oc)

Then you can use it to flash recovery.

I always keep former version file so I could revert to bluspark twrp that was working before. All worked as expected!

Still not solving the encryption password issue when flashing new recent twrp..
[OnePlus 3T Guides, News, & Discussion] monicaONxda:
Android 10 Encryption / Security Issue - ADB Encryption Bypass?

Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?

I have discovered another security issue however on a rooted device:

On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!

This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!

Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?

Is this issue related to Magisk? And can it be fixed?
[OnePlus 3T Guides, News, & Discussion] monicaONxda:
Anyone with thoughts on this...?
[OnePlus 3T Guides, News, & Discussion] BillGoss:
There are two, separate passwords. One for the encryption and one for the lock screen. And they don't have to be the same.

If you remove the encryption by formatting /data and then boot up on stock OOS, it will encrypt /data with a default password. TWRP can decrypt /data because it knows the default password that's used.

When you set the lock screen password you have the option to set the encryption password to be the same or not.

So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.

ADB can only access /data after it has been decrypted, ie the phone has booted up. But only if: 1. ADB is enabled, 2. You have given permission on your phone to trust the PC connecting to the phone.

So, there's no back doors here. If you have set an encryption password, you can't access the data without having entered the password. And you can't access the phone data without entering the lock screen password. And you can't access the data via ADB unless you have given the specific PC permission from your phone.

Of course, if you use the default encryption password and have TWRP installed, you might just as well not have a password at all. But that's up too you.
[OnePlus 3T Guides, News, & Discussion] Deleted member 4405529:
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".

The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:

https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post80390263#post80390263
[OnePlus 3T Guides, News, & Discussion] BillGoss:
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
[OnePlus 3T Guides, News, & Discussion] Deleted member 4405529:
I'm pretty sure this behavior is rom dependent and not device dependent. E.g.: in los14 and early los15 builds the user was able to set lockscreen passphrase and boot passphrase seperately from rom's settings. This has been removed from aosp (officially because of "security concerns"; but I guess these "concerns" has been too many users with too less knowledge have locked up the boot process).

For me the cryptfs cli is perfectly ok, for the average user the behaviour you've expirienced may feel more comfortable. But the longer I think about, the more I like the seperate setting... YMMV.
[OnePlus 3T Guides, News, & Discussion] monicaONxda:
I thought Android 10 encryption (file based encryption, FBE) works like this: Android encrypts (if FBE is enabled) automatically the internal storage (userdata partition, /data) on first boot (or after erasing /data via a factory reset etc.) with a randomly (by the KeyMaster) generated aes-256-cts key (key blob, masterkey), stored in the processor-TEE (Trustzone) which will be encrypted itself with another 128 bit AES key, derived from a user-supplied password/PIN. This Device Encryption Key is stored at the end (last 16kb) of the encrypted partition (/data).

That means there is only one password involved, i.e. the screen lock password. There is no option in Android 10 to set another (second password as you mentioned!)

The security issue I was referring is the fact ( you can test it yourself!), that after you have unlocked the phone with your password and accessed it via ADB from a computer (and of course gave the permissions), then, unless you didn't reboot the phone (which you sometimes don't do for a longer time period...), it can be accessed with that PC and ADB (maybe with another PC, too, I haven't checked it!), even when the phone is locked (with the password)! That's a big security hole I think - The phone should automatically encrypt /data on every screen lock and not just on reboot...
[OnePlus 3T Guides, News, & Discussion] BillGoss:
I can't comment about FBE (file based encryption), because our phone doesn't support it. It uses FDE (full data encryption).

With FDE there are two passwords. One associated with the encryption and one associated with the lock screen. You can check this by deleting the lock screen password in TWRP which won't remove the encryption password.

rm -f /data/system/gatekeeper.* /data/system/locksettings.*

Decrypting /data takes a while and starts after you've applied the decryption password and finishes before the lock screen is presented.

If you've granted ADB access to a PC, that's as good as giving that PC the lock screen password to your phone. It will be able to access /data after the phone boots up (data has been decrypted) even if you don't unlock your phone.

If you don't want that to happen then you should not allow the PC to always have access (don't tick the box). You will then need to unlock your phone to grant ADB permission every time.

And don't forget to revoke ADB access from all PCs.
[OnePlus 3T Guides, News, & Discussion] :
The option for seperate boot passphrase has been removed by some security patch in the android 8 lifetime. You can still set it via cli: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post80390263#post80390263

BTW: FDE = full disk encryption.
[OnePlus 3T Guides, News, & Discussion] monicaONxda:
OK, I understand it now almost and have seen now the RSA key message when switching on USB debugging. When the RSA keys are passed to the PC/Windows permanently (until revoke), do you know, where these keys are stored In Windows exactly? Then I could just (auto)delete them when the ADB connection closes and /or PC reboots. I guess that has the same effect as to NOT enabling "always allow from this computer" in developer settings? I think it should be fixed by Android (or not implemented in the first place) to permanently allow a device access to your phone (if you accidentally click it or forgot (like me) that you have enabled it some time ago...)

B.t.w. do you know how to remove the encryption password without TWRP which I don't have unfortunately.. Just curious in case I need to remove it one day.
[OnePlus 3T Guides, News, & Discussion] BillGoss:
As far as I know, the PC never stores the phone's key. It's the other way around: the phone remembers the PC's key. Which is why it's up to you to decide if your phone will trust the PC. So there's nothing, to my knowledge, stored on your PC that identifies your phone.

I think I've only ever used TWRP to remove encryption, but you can use 'fastboot erase userdata' - see https://xdaforums.com/oneplus-3/one...ial-twrp-touch-recovery-t3742894/post80978485
[OnePlus 3T Guides, News, & Discussion] :
That depends on the rom you are using, as already discussed on the last page.

Basically you can't have encrypted data without passphrase, but you can have "default_password" as encryption password. Since "default_password" is probed by the rom, it feels like no passphrase.
[OnePlus 3T Guides, News, & Discussion] monicaONxda:
My Windows 10 it stores the RSA key for the ADB connection in "C:\Users\<my profile>\.android\adbkey.pub" and there is another ADB key on the phone in "/data/misc/adb/adb_keys", but both don't match!?

The lockscreen password I found out is stored on the phone on "/data/system/password.key" and "/data/system/locksettings.key" (salt) - If deleted on a running / decrypted phone, the lockscreen password should be removed and the device unencrypted on the next boot I think?

Regarding the fastboot commands, I can't execute them on a Samsung phone, there is only an "Odin" downloadmode availbale ,where I can flash new partitions (and erase them). My question yesterday "how to remove the encryption/lockscreen password" makes no sense I have to admit: removal the password means erasing /data partition. On Andoid 10 (or above Android 8 I think) it can't be bypassed/resetted etc.
[OnePlus 3T Guides, News, & Discussion] BillGoss:
The RSA key on the PC you found is the signature of the PC. It has nothing to do with the phone. My PC RSA key is more than 5 years old and I've had many phones during that time.

Let me say it again: the lock screen password has nothing to do with encryption, though it may be the same password being used by the encryption and the lock screen. However, a specific rom may choose to change/modify the encryption password when setting the lock screen password.

Finally, this is a OnePlus 3/3T thread so you need to take any Samsung specific issues to the relevant forum.
[OnePlus 3T Guides, News, & Discussion] monicaONxda:
But the lockscreen password encrypts the (in Android 10 with FBE, randomly generated) masterkey and stores it as a "device encryption key" (DEK) I thought, so its PART of the encryption, and without the lockscreen password you cant bypass the encryption, don't you think?

As i understood it now, the DEK unlocks the Android file system that can be accessed via ADB and keeps it unlocked until the next reboot of the device - and not until the next screenlock which one might assume - which is a security hole in my opinion ... An encryption after each screenlock would probably prevent some apps from running while the screen is locked / device in sleep mode... For security reasons I would wish to have an option to encrypt after each screenlock...
[OnePlus 3T Guides, News, & Discussion] :
op3/t doesn't have fbe but fde - no matter if android 6, 7, 8 or 9 (oos 3, 4, 5, 9). Since we don't have sources for the bootloader and firmware that support fbe android 10 and android 11 custom roms have fde, too.

The encryption passphrase (aka boot passphrase) and the lockscreen passphrase are two completely seperate and unrelated passphrases. It's just the settings app that make you think it's related - but that's a misconcept: you can easily set a seperate passphrase for fde. P.ease read the last pages, I've explained that more then one time.

Having adb enabled is a security issue. That's why adb is disabled by default on oos 3 - 9.

Encryption is done when a file is written to disk (and initially by forved encryption (oos) or user action (custom roms)), it's not possible to unencrypt an encrypted partition (you can only format), that's why it's not possible to "to have an option to encrypt after each screenlock". To read and use an encrypted partition, it needs to be decrypted (that's why you need to give the encryption passphrase on boot). If you throw away the decryption on screenlock until you give tne encryption passphrase again on screenunlock, no app or service can run while the scteen is locked, bevaise all app/service config and data is stored on the encrypted partition. Basically it's the same for fbe (of course with fbe it would be possible to exclude all app/service config and data from tje encrypted files, but then again encryption doesn't make sense and it would be readable with adb, too).