How to boot into an encrypted phone - Android General

Hi, desperately in need for your guys help. Thanks.
I have a Samsung S3 running Hyperdrive. I've used company email so the memory was encrypted per company security policy. I decided to flash to a newer version of Hyperdrive yesterday and after flash with TWRP, I found that when turning on it displayed the initial logo and ask for password to boot into the system. The problem is that it does not recognize the password I put in as correct one. I am positive I used the right password. Tried to wipe, format and reinstall 4 times with the same results.
Really frustrated. And please help!

Related

[Q] TWRP and Device Encryption on Skyrocket

I am running Stock ATT ICS rooted on my Skyrocket. I have TWRP installed for recovery. My company changed its policy to require device encryption. I can boot into TWRP 2.2.2.0 and it prompt me for a password but when I enter my password, I get a message that the password is invalid. Everything I read says that TWRP should work. Is there something else I need to do? Thanks!
slipsibm said:
I am running Stock ATT ICS rooted on my Skyrocket. I have TWRP installed for recovery. My company changed its policy to require device encryption. I can boot into TWRP 2.2.2.0 and it prompt me for a password but when I enter my password, I get a message that the password is invalid. Everything I read says that TWRP should work. Is there something else I need to do? Thanks!
Click to expand...
Click to collapse
Were you able to figure this out? I'm getting the same issue on my Hercules (T989).
Splaktar said:
Were you able to figure this out? I'm getting the same issue on my Hercules (T989).
Click to expand...
Click to collapse
I was told that the samsung encryption isn't supported by twrp, There is a package on the play store called Online Nandroid Backup that you can use while running that gets around the backup problem, I have no idea how you would use this to recover but I assume if you wiped and restored from this backup, you would have an un-encrypted device that would then need to be re-encrypted. In the mean time, I turned encryption off.....
slipsibm said:
I was told that the samsung encryption isn't supported by twrp, There is a package on the play store called Online Nandroid Backup that you can use while running that gets around the backup problem, I have no idea how you would use this to recover but I assume if you wiped and restored from this backup, you would have an un-encrypted device that would then need to be re-encrypted. In the mean time, I turned encryption off.....
Click to expand...
Click to collapse
Bummer. It looks like the T989 is in the same situation as well, not supported. Looks like the Galaxy Nexus and only a few other devices support encryption of the /data partition in TWRP.
I guess that I'll see if I can turn off encryption and then do my backup, upgrade to a new ROM, and then turn encryption back on.
Thanks.

[Q] Encryption password not working can't get in

I set an encryption password 3 weeks ago and have been using it ever since. Today, I decided to root my device using chainfire's CF-root method through odin. Everything went fine, but after the reboot, it kept saying my password was incorrect. I tried 10x but no luck. I booted into CWM and did a factory reset but following reboot, I'm back to the encryption password request. I tried again and I exceeded the limit and it wiped all my user data. I still can't get passed the encryption request, the tablet just reboots and asks me to try again. Can anyone help? I can't get into my tablet and there is no option that I know of to reset the password. Please help. thank you.
rekil goth said:
I set an encryption password 3 weeks ago and have been using it ever since. Today, I decided to root my device using chainfire's CF-root method through odin. Everything went fine, but after the reboot, it kept saying my password was incorrect. I tried 10x but no luck. I booted into CWM and did a factory reset but following reboot, I'm back to the encryption password request. I tried again and I exceeded the limit and it wiped all my user data. I still can't get passed the encryption request, the tablet just reboots and asks me to try again. Can anyone help? I can't get into my tablet and there is no option that I know of to reset the password. Please help. thank you.
Click to expand...
Click to collapse
Not really funny but I just did this on my wifes note 10 minutes ago. You find a solution yet. I'm digging away for a solution.:crying:
Update: Went into recovery and did a factory reset. Everything seems fine. Of course I did lose my wifes data.
I accepted my defeat. I flashed stock recovery and booted into it. From there I did a factory/Dalvik/cache wipe and rebooted. Once it rebooted, I was back to a brand new tablet. I lost everything.
rekil goth said:
I accepted my defeat. I flashed stock recovery and booted into it. From there I did a factory/Dalvik/cache wipe and rebooted. Once it rebooted, I was back to a brand new tablet. I lost everything.
Click to expand...
Click to collapse
Could have been worse I guess.
Yep, could've kept asking for password after the stock flash.... Now that would be a bummer...
rekil goth said:
I set an encryption password 3 weeks ago and have been using it ever since. Today, I decided to root my device using chainfire's CF-root method through odin. Everything went fine, but after the reboot, it kept saying my password was incorrect. I tried 10x but no luck. I booted into CWM and did a factory reset but following reboot, I'm back to the encryption password request. I tried again and I exceeded the limit and it wiped all my user data. I still can't get passed the encryption request, the tablet just reboots and asks me to try again. Can anyone help? I can't get into my tablet and there is no option that I know of to reset the password. Please help. thank you.
Click to expand...
Click to collapse
Another data point, totally stock Note just tried to encrypt it (lost the encryption after the upgrade to 4.1) and seemed to do its thing fine but wont accept my password which I KNOW is correct. Frak! Going to have to wipe it I guess, pissed to say the least. Wonder if the recent update (don't even know what it was for but it was small) created a problem?
Did you guys managed to find a way to fix this without factory reset.
Try this password: un!ockm3!

OTA update Fail, Save my data

Hi ~
- Be kind with me, it's my first post! -
I'm facing a very bad problem with my Galaxy S6. A week ago I received an OTA from Samsung and I installed it. My phone rebooted and showed the bugdroid, meaning that the update was progressing. After that, the device keep rebooting over and over just after I entered my encryption password. I said to myself that I can try to wipe the cache because maybe an application was causing this problem. But now, the device is only showing the Samsung logo then just shut himself off.
Now I need your help to get my data. The hard part is that my device is encrypted. After many hour of search I see two solutions:
Flash the rom via ODIN
Install TWRP which can read encrypted volumes
The first solution seems easy and I keep the warranty. The problem is that I'm not 100% sure that flashing the rom again will not touch the /data and /sdext partitions (and the header/footer where master key are to decrypt the volume).
The second solution seems safer and should not touch any other partitions. But knox counter will be incremented and I will loose my warranty.
So, does anyone could test if flashing the rom via ODIN do not absolutely touch encrypted volumes and certificate that I will be able to get my data again?
Thank you a lot
Have a leap of faith. Go ahead and flash. Otherwise bring it to Samsung for warranty repair. They may be able to recover your data for you.
roydok said:
Have a leap of faith. Go ahead and flash. Otherwise bring it to Samsung for warranty repair. They may be able to recover your data for you.
Click to expand...
Click to collapse
I want to be sure and I don't want to loose any photos if possible, so no
I already tried to go in a Samsung repair store (Allo PSM), but they just don't care about my data, their job is just to make the phone working again.
So Anyone is able to confirm to me that flashing stock Galaxy S6 ROM (AP Via Odin) doesn't touch the /data and /sdext partition that are encrypted?
After many hours of search, I was able to make my phone working again!
For anyone concerned by the problem in the future, here's some informations:
You can flash a stock rom, your encrypted /data will not be erased and you will be prompt to enter your password on the next boot
In my case flashing a newer rom didn't solve my problem (bootloop after entering the password of the encrypted partition). I had to flash the rom that was in the phone before the OTA.
Now everything seems to working again. No data were lost, all my configuration was saved. Android showed a message that a problem occurred during the upgrade process and I sent logs to Samsung, hoping that it will help them!

I Need your help please..

Hello ppl..
Yesterday i decided to flash latest "back to n0t3" Note 5 port rom by @arter97.Installed latest modem and bootloader (oj5) installed latest Philz recovery wiped and formated everything,and i flashed the rom and layest arter kernel (7.2). Wiped cache / dalvik cache x3 and rebooted the device.Strangelly the device took only 15 sec to boot up to "Select language" menu.. So there i selected my native language,puted my wifi passwors,and here we go.
Normally the next step isbto sign in with your google account.For me it asks me to sign in with an account that allready synced with that device.offcourse it didnt accept my Google account and i couldnt move farward....I cant understand what is going wrong with my phone since i see i an the only one who deal with that problem.
I will provide you all the things i tryed allready but didnt work .
Reflahed the rom
Download the zip file again
Flashed again stock firmware and reroot my device from the beggining
Trying and flashed successfully with latest TWRP and Philz recoverys with no luck
The even stranger think is i decided to try Ditto's Note 5/S6edge+ port rom and i had the same results...It asked me again to sign in with an account that allready synced with that device...
What is going on guys anyone have any idea what is the problem in my phone?
My device is 920f
Sounds like Google Factory Reset Protection. Not sure how rooting and flashing will interact with the FRP. Did you have more than one Google account on the phone? If so, you might try another account.
FYI, from what I understand, if you change (reset) your Google password, it will not work on the phone for 72 hours.

I messed up and now I'm stuck on FRP lock

Ok so admittedly I made a noob mistake and inadvertently unchecked OEM unlock and rebooted. So I'm stuck on FRP lock. From what I see, my only option is to flash the original firmware on the phone.
My question is simple: I don't have TWRP and can't do a NAND backup. Will my internal SD card get wiped as well? If so, is there ANY way I can back it up before hand??
Thanks...
Ok so I managed to save my arse after all, but I figured I would leave a reply here for archival purposes.
I used Odin to flash the stock Bootloader and PDA. Not only it didn't touch my SD, but it really didn't wipe anything and I only lost my root.
Two things happened I didn't see documented anywhere I looked: I got a weird crash on boot update and ended up in Stock recovery after auto reboot and got a slew of error messages, but a simple phone reboot worked.
Then I was asked for a password to restart, which turned out to be "default_password"...
Hope this will help someone down the road!
Sent from my SM-G930W8 using XDA-Developers mobile app
Cleaned & wiped all stuff, flashed stock 6.0.1 with Odin AP,BL,CP,CSC and same FRP google login shows up. Mind sharing those two files?
For sure, I just used the latest firmware on Sammobile: this is the generic one for Canada, but I'm on Rogers so I used this one.
I only used the BL and PDA, but I also made sure I wasn't locked out on my Samsung Account. FRP can be because of the custom binaries, but it can also be a system lock out and I've read that in some cases it's because the phone has soft locked itself out. Not sure how accurate that is, but wouldn't hurt to check I guess...
now all ok or still facing same?

Categories

Resources