I recently just wipe did a factory reset on a encrypted (factory encryption) Galaxy S3, after rebooting it i have found that i am unable to get past the initial password prompt screen. I have tried to flash stock ROM, multiple times, to no avail as after each reboot i get the same password prompt screen. i have tried to flash custom ROM, multiple times, this to to no avail as it will not even go onto the device through push in Samsung toolkit v7 or slideloader. i have wiped the ROM to the point of nothing being on the phone and re-installed the factory ROM again this to with not avail as it still has the password screen. Now before i go back to t-mobile and see if they will help me, i decided to get community input to see if there is anything that can be done outside of the Factory as i have void warranty using Samsung Galaxy S3 Toolkit v7.
******UPDATE******* for those with similar problem, i just fixed this. Issue is as follows with possible fix action:
Issue was that encrypting the Samsung Galaxy S3 with the factory encryption and then wiping the system will cause the password file to be deleted but the encryption to stay on the phone. My fix action was that download original ROM from the provider, delete existing ROM on phone till it is basically a brick with USB debugging on and re install the original providers ROM. After it is re install you have to go in and wipe the phone's data one more time. This resulted in the password prompt screen disappearing and the basic start setup being initiated as if you just bought the phone from the store. Although this is my fix and other fixes for future reference would be much appreciated to. *********UPDATE************
zidale said:
I recently just wipe did a factory reset on a encrypted (factory encryption) Galaxy S3, after rebooting it i have found that i am unable to get past the initial password prompt screen. I have tried to flash stock ROM, multiple times, to no avail as after each reboot i get the same password prompt screen. i have tried to flash custom ROM, multiple times, this to to no avail as it will not even go onto the device through push in Samsung toolkit v7 or slideloader. i have wiped the ROM to the point of nothing being on the phone and re-installed the factory ROM again this to with not avail as it still has the password screen. Now before i go back to t-mobile and see if they will help me, i decided to get community input to see if there is anything that can be done outside of the Factory as i have void warranty using Samsung Galaxy S3 Toolkit v7.
******UPDATE******* for those with similar problem, i just fixed this. Issue is as follows with possible fix action:
Issue was that encrypting the Samsung Galaxy S3 with the factory encryption and then wiping the system will cause the password file to be deleted but the encryption to stay on the phone. My fix action was that download original ROM from the provider, delete existing ROM on phone till it is basically a brick with USB debugging on and re install the original providers ROM. After it is re install you have to go in and wipe the phone's data one more time. This resulted in the password prompt screen disappearing and the basic start setup being initiated as if you just bought the phone from the store. Although this is my fix and other fixes for future reference would be much appreciated to. *********UPDATE************
Click to expand...
Click to collapse
When you say you reinstalled the original provider's ROM, I'm not sure if you mean you used ODIN. I believe ODIN install is the only way to recover from this as it reformats the partitions.
An ODIN flash back to OTA did not help my issue.
My company now requires the encrypt device policy for exchange, so I went ahead encrypted the device while running CM10. The encryption succeeded, but every time the screen timed out, it would turn off the device instead of just turn off the screen (CM10 bug?) - didn't want to have to deal with having to cold boot the device every time I want to do something, not to mention the phone being off :/
So I did a nandroid restore to my last known state and now I get prompted for the unencrypt password. However, the password doesn't work. Probably because the password file was deleted, but the system and data partitions are still encrypted.
I've tried doing a full wipe in TWRP and flashing multiple ROMs. I've also tried ODIN flashing root66 and OTA JB 4.1.1 with no success. It still asks for the unencrypt password. I suspect the only way to fix this is to completely re-create the system and data partitions.
If anyone knows how to accomplish this, I'd be grateful because I have a soft brick right now (i.e. can't get past unencrypt password prompt with any ROM)
OMG THANK YOU SO MUCH FOR THIS. I was in the same exact situation you were in and thank god for this thread. I thought my phone was pretty much done for.
fix
BTT8 said:
OMG THANK YOU SO MUCH FOR THIS. I was in the same exact situation you were in and thank god for this thread. I thought my phone was pretty much done for.
Click to expand...
Click to collapse
flash ur rom. then flash CF-Auto-Root, boot to recovery, factory restore, done
Related
Model: Samsung Galaxy S3 AT&T i747
Hi!
I was forced to encrypt my galaxy s3 in order to receive corporate emails on my phone using the stock email app. However I never imagined that encrypting the phone would literally lock the memory and options to customize the phone.
I tried to root the phone to benefit from more flexibility and also debloat the phone. However during the rooting process, I could not mount /emmc/ when using ClockWorkRecovery in the startup menu. Based on what I found on the web, I figured it was due to the encryption.
I then tried to factory reset the phone to get rid of the encryption but I simply can't hard reset the phone from the OS or the startup menu. When doing the reset from the startup menu, the errors are "Can't mount /sdcard/". The reset continues but when the phone reboots, all my applications and personal data are there and the phone is still encrypted.
I read a lot about flashing a custom recovery via flashboot or ADB but I am reluctant to do it without guidance from the experts (you guys).
I deleted my corporate email account (It is my personal phone, I am not required to install exchange on it).
I tried to use an external sd card but as soon as the phone recoginizes it, I have to encrypt the card as well as a result from the corporate policies. I ejected the card and did not encrypt it.
I am new to android (long time iPhone user) and I would really appreciate your guidance on the methods to factory reset my phone or a different technique to get rid of the encryption because I am really stuck right now.
I have never encrypted an Android phone before. But maybe your response to these questions will serve as a "bump" to this thread.
1) What method did you use to encrypt the phone? Stock or 3rd party encryption?
2) Doesn't that same method also offer you the offer to unencrypt the phone?
3) If you used a stock method of encrypting the phone, then I'd assume your provider (AT&T?) tech support should be able to help you unencrypt it.
Eddie,
Thanks for your response.
1) I used stock method for encryption
2) Decrypt the phone is not possible apparently,only way is to factory restore the phone apparently
3) I went to the AT&T store and they were unable to factory restore (using the standard methods). They offered an exchange but since I purchase over the phone at a discounted price, I have to do the exchange using that method. Before shipping back the phone, I was wondering if I could fix it myself with the help of knowledgeable people.
CZ Eddie said:
I have never encrypted an Android phone before. But maybe your response to these questions will serve as a "bump" to this thread.
1) What method did you use to encrypt the phone? Stock or 3rd party encryption?
2) Doesn't that same method also offer you the offer to unencrypt the phone?
3) If you used a stock method of encrypting the phone, then I'd assume your provider (AT&T?) tech support should be able to help you unencrypt it.
Click to expand...
Click to collapse
I have never used the encryption but if the phone can turn on and is usable, cant you go into the encryption settings and turn encryption off? then you should be able to do anything (may be best to start with a factory restore first just so you have a fresh slate to work with)
1ofAKind said:
Model: Samsung Galaxy S3 AT&T i747
Hi!
I was forced to encrypt my galaxy s3 in order to receive corporate emails on my phone using the stock email app. However I never imagined that encrypting the phone would literally lock the memory and options to customize the phone.
I tried to root the phone to benefit from more flexibility and also debloat the phone. However during the rooting process, I could not mount /emmc/ when using ClockWorkRecovery in the startup menu. Based on what I found on the web, I figured it was due to the encryption.
I then tried to factory reset the phone to get rid of the encryption but I simply can't hard reset the phone from the OS or the startup menu. When doing the reset from the startup menu, the errors are "Can't mount /sdcard/". The reset continues but when the phone reboots, all my applications and personal data are there and the phone is still encrypted.
I read a lot about flashing a custom recovery via flashboot or ADB but I am reluctant to do it without guidance from the experts (you guys).
I deleted my corporate email account (It is my personal phone, I am not required to install exchange on it).
I tried to use an external sd card but as soon as the phone recoginizes it, I have to encrypt the card as well as a result from the corporate policies. I ejected the card and did not encrypt it.
I am new to android (long time iPhone user) and I would really appreciate your guidance on the methods to factory reset my phone or a different technique to get rid of the encryption because I am really stuck right now.
Click to expand...
Click to collapse
1ofaKind,
Had EXACTLY the same thing happen to me. Encrypted my S3 in order to access work exchange server. Tried CWM but cannot mount /emmc/ problem after booting into recovery. Have not tried to factory reset yet as I am wanting to learn more before I go that route. But basically I am in the same boat as you. The only difference is I was not required to encrypt an external SD card when I put it in my phone. Read about flashboot as well...maybe the only way to actually factory reset after encryption??
Sorry I cannot offer any solutions at the moment...but I will keep scouring the forums looking for a way.
If I learn something valuable, I will try to post it here to help ya out.
EDIT: Maybe you have read these threads, but there is some decent info in them. http://forum.xda-developers.com/showthread.php?t=1451655 & http://forum.xda-developers.com/showthread.php?t=1392037
good luck
Look into using Odin to restore a factory image.
Sent from my SAMSUNG-SGH-I747 using xda premium
I'm in the same boat here - had to encrypt my GS3 in order to receive corporate (Exchange Server) emails. Now can't update the OS on the phone which is more important to me than receiving corporate emails on the device.
Can someone tell me how to decrypt (UN-encrypt) the phone? Everything I've read says that a factory reset won't do it.
Please help!
CZ Eddie said:
Look into using Odin to restore a factory image.
Click to expand...
Click to collapse
Has anyone tried this? If so, did it work?
I clicked install rom from sd card in cwm selected f/w which i had copied into internal memory. Did factory reset in recovery.
Odin it back to stock.
This might be too late to help you guys, but here's what worked for me. I odined it back to stock. Then I went into recovery (volume down, power and home button) and selected wipe data/factory reset. This does of course erase all your data, so try to copy whatever you can onto a computer or something before doing this. You should end up with an unencrypted storage.
sid9102 said:
This might be too late to help you guys, but here's what worked for me. I odined it back to stock. Then I went into recovery (volume down, power and home button) and selected wipe data/factory reset. This does of course erase all your data, so try to copy whatever you can onto a computer or something before doing this. You should end up with an unencrypted storage.
Click to expand...
Click to collapse
ODIN will not recognize my phone when it is in download mode ...
tamon77 said:
ODIN will not recognize my phone when it is in download mode ...
Click to expand...
Click to collapse
After you hit start, unplug then replug the usb from the computer. I had some issues with it not recognizing it either to flash stock, but when i messed with the cord, it made the noise that i unplugged and it started working. Same thing with the root injected, only this time i fully unplugged it when the fiddling with it didnt work. Make sure you replace it into the same com port.
so, i seem to be having the same problem as all of you, only i encrypted to protect my data from agents. So, right now, i am *hopefully* :fingers-crossed: installing the root injected JB now. I had many issues. TWRP and CWM were no help, couldnt see phone to add new roms to it. ODIN was the only hope. I booted into recovery after going back to stock, did a new factory reset and am installing the stock with root. When i let it boot, it didnt go to encryption this time, but the first time i flashed the stock, it did. This is a mess to say the least.
EDIT: YEAH! done. No encryption and i got root. i used the image from here: http://forum.xda-developers.com/showthread.php?t=1968625 DLK3 worked for me. Good luck. i hope this helps. Ill be happy to explain more if you want.
tamon77 said:
ODIN will not recognize my phone when it is in download mode ...
Click to expand...
Click to collapse
ODIN (for me at least) wont see anything since im using Windows 8. On Windows 7, however, it works just fine.
Factory reset encrypted phone
hi,
I'm using CM11 as a rom.
I didn't want to reinstall stock rom, just to root it again later.
Installing updated version from external SD didn't work (updated the ROM but no decryption)
Tried to factory reset from recovery - didn't work, as the internal storage is encrypted it can't mount /sdcard/
however, from within settings menu, in backup&restore there's an option to do a factory reset - this is formatting internal memory altogether.
worked like a charm.
oxidase said:
After you hit start, unplug then replug the usb from the computer. I had some issues with it not recognizing it either to flash stock, but when i messed with the cord, it made the noise that i unplugged and it started working. Same thing with the root injected, only this time i fully unplugged it when the fiddling with it didnt work. Make sure you replace it into the same com port.
so, i seem to be having the same problem as all of you, only i encrypted to protect my data from agents. So, right now, i am *hopefully* :fingers-crossed: installing the root injected JB now. I had many issues. TWRP and CWM were no help, couldnt see phone to add new roms to it. ODIN was the only hope. I booted into recovery after going back to stock, did a new factory reset and am installing the stock with root. When i let it boot, it didnt go to encryption this time, but the first time i flashed the stock, it did. This is a mess to say the least.
EDIT: YEAH! done. No encryption and i got root. i used the image from here: http://forum.xda-developers.com/showthread.php?t=1968625 DLK3 worked for me. Good luck. i hope this helps. Ill be happy to explain more if you want.
Click to expand...
Click to collapse
I understand this is very old but I am going to make a note here in case anyone else gets into this problem. When you go back to stock, do the factory reset using the STOCK recovery. Don't install TWRP or anything else until you have cleared the encryption. At least, that's what worked for me.
Disclaimer: I am not responsible for any damage or liability arising out of these steps. I did not invent anything, I just tried something. Only move forward at your risk
If you don't agree ... stop reading and move on...
Background: Our phone has access to so much personal information that its scary if it fell into wrong hands. The only way to fix this is to encrypt phone. I did lot of research and here is a working solution that works for me - try at your risk.
Download Links:
a) Tested with ROM Stock 4.4.4 NH7 Galaxy S4 M919/Jfltetmo by @ShinySide
b) Tested with ROM |ROM|★KANGAKAT★|►KTU84P◄|4.4.4|Xposed|►8◄|6.26.14 by @iB4STiD
c) stock recovery AT&T S4 works with M919
d) Philz/CWM custom recovery
Encrypting with custom rom
1) Assume you are on custom recovery. - Backup everything first. Create a nandroid backup
2) Do a full wipe and install one of the two roms linked above (I have tested with few other roms ... none worked). Start the phone and set it up the way you want. Install all apps etc.
3) ODIN Stock recovery. See #c under download above. Its AT&T stock recovery but works for me. You need to know how to ODIN - find out. Doing this wrong will permanently damage your phone
4) Start your phone and turn on encryption. You will need to set lock type = password and will need to connect to charger and have 80% charge.
- Phone will do blank and stay blank for 20-30 minutes. Do not do anything. Encryption is happening behind the scenes.
- You might have to do this twice or thrice if it did not encrypt first time. For me the phone went blank first time and after 25 minutes it restarted but device was not encrypted. I redid the same steps and worked second time.
- If you interrupt the encryption process (battery pull or power up) you will see error message (encryption failed, reset device)
5) If all goes well you now have a password protected encrypted phone with custom rom!!! Check in Settings -> Security
6) You may install custom recovery ... but I don't see the point because you will need stock recovery to decrypt
To install another ROM
1) Reboot into stock recovery, then wipe data and cache (this removes encryption).
2) install your recovery of choice and install ROM using recovery. Philz/CWM
Credit goes to @Tronicus and his reply Flash a Rom on an Encrypted Android
Tronicus said:
How to Flash a rom on an encrypted Android phone (specifically this one, the I9505 SGH-I337).
The Problem: Once encrypted, you can't decrypt it easily. When encrypting the phone android will tell you you can only decrypt it using a factory reset. Naturally you assume it's talking about the "Factory Data Reset" option found in Settings --> Backup and Reset. But noooo, Android is lying through its ****ing teeth. Then you'll assume you have to wipe everything from your custom recovery mod (CWM, TWRP, or one of those). Wrong again! You'll get beautiful "can't mount /data" messages and more bull****. I read about a workaround that required installing the new rom using ADB, but I had ingeniously disabled USB debugging prior to wiping everything, so I only got so far with that option (plus it's tediously long if you haven't installed all the necessary software already and don't feel like bricking your phone because you made a typo in the command line). So, apparently the only other way to really format that partition free of its encryption is to use a stock recovery. So:
Short Version for Godlike users who know automatically how to do all this **** without any help (mimicking how most help posts are finely detailed on this site): Flash stock recovery, wipe everything, flash your custom recovery and install your new rom.
Long version for us mortals who don't know everything and haven't already downloaded already every single bit of software on earth:
Backup all the stuff you want to save. This process will truly wipe EVERYTHING. You can do it manually, or you can use an app like Titanium Backup Pro to help you (find it on Google Play Store). Here's a nice guide which recommends what to restore and what not to restore: http://forum.xda-developers.com/showthread.php?t=1480343
Flash the stock recovery using Odin. You can download a stock recovery from here: http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3 It's the link called "I337MK2stockrecovery.tar.md5" In case you don't know how to flash it with Odin, this short guide will help: http://forum.xda-developers.com/showthread.php?t=1506697
In step 6 replace "recovery.tar.md5" with the stock recovery you downloaded.
Wipe everything from the Stock recovery console. This little ****er will **** up the encryption all those sissies couldn't touch. You're welcome. You boot into recovery mode from a turned off phone by pressing simultaneously the volume up key + the home key + the power key until you see blue text appearing in the top left corner of your screen.
Reinstall your custom recovery. In my case I had installed the rom BEFORE flashing in the stock recovery (apparently it works, you just can't boot because of the encryption), so I was able to boot into the new rom before I returned to my custom recovery. Weird. Anyways, I recommend CWM. You can pick it up from this link: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte
For some weird reason they call the I337 version the "jflte" version. It's bonkers. Click there, and download the latest version that ends with .tar.md5. This version is upgradable via Odin, which we already used. Use the same instructions used as when you upgraded the stock recovery rom.
Boot into your recovery mod and flash your rom like you usually do.
A word about TWRP: it cost me many hours of work and I don't recommend it. Its website is outdated, and recommends using GooManager (which is no longer mantained) and doesn't work anymore for this. GooManager suggests using a new, different app, which doesn't have the option of installing TWRP. Then I tried using their TWRP Manager app from play store and the image file wouldn't download. Then I tried manually selecting the image file in TWRP manager that I downloaded from their site for use via the ADB method, and it bricked my phone... twice (using two different methods the app sugested). I tried so much because in theory TWRP has the ability to decrypt android's 4.4 encryption, but after looking at their github site I noticed it was filled with people's reports (including people with the S4) on how it wouldn't work decrypting squat. So I gave up, and installed CWM in 30 seconds.
Click to expand...
Click to collapse
Disclaimer: I am not responsible for any damage or liability arising out of these steps. I did not invent anything, I just tried something. Only move forward at your risk
cnewsgrp said:
One of the things I needed was the ability to encrypt my phone (device only not external SD) for security purpose. Our phones today gives access to lot of information that I would rather not fall in wrong hands. I did lot of research and here is a working solution.
Credit goes to @Tronicus and his reply Flash a Rom on an Encrypted Android
The quote looks long however it is really very simple. To install another ROM
- Install and reboot into stock recovery, then wipe data and cache (this removes encryption).
- Then install your recovery of choice and install ROM using recovery. Philz/CWM
This has been tested working on |ROM|★KANGAKAT★|►KTU84P◄|4.4.4|Xposed|►8◄|6.26.14 by @iB4STiD
This did NOT work on a Touchwiz ROM by same developer
I have not tested any other ROM
Click to expand...
Click to collapse
I don't know if it matters too much or not, but the stock recovery you linked to is for the AT&T S4. A good rule of thumb is to never use Odin to flash anything not specifically for your particular device... In this case the M919.
Sent from my SGH-M919 using XDA Premium 4 mobile app
lordcheeto03 said:
I don't know if it matters too much or not, but the stock recovery you linked to is for the AT&T S4. A good rule of thumb is to never use Odin to flash anything not specifically for your particular device... In this case the M919.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have tested stock recovery on M919 .. it works
Honestly im surprised its not talked about more since there is a big push for personal privacy when it comes to data. Encryption really is a pain in the ass to work with on android. Figuring out how to switch or update custom roms while encrypted will drive you insane. The easiest way is to just odin back to stock and start over, but that requires a computer anytime you need to flash anything.
I recently was trying out one of the 4.4.4 GPE roms and turned on encryption. It worked great until i started missing touchwiz and wanted to go back to HyperDrive TW. So the journey began...
First of all, i backed up everything to external storage since i knew everything on the internal storage would have to be wiped. I loaded the phone into recovery mode (using TWRP) and tried wiping, but all i got was a bunch of "Failed to mount" errors. Fine. Got the same error when trying to factory reset or wiping /system, /data, /cache, and anything else. Tried formatting to different file systems and then formatting back to the original but no luck. Fixing permissions didnt help. I just kept trying everything available multiple times.
Eventually it started wiping everything except the /data mount. Well... At least i could install new custom roms. Im not sure exactly what did it because i was just throwing everything at it. Anyways I got it to install, and booted into it. Nope.
Now it was saying I needed the password to decrypt the internal storage. It would detect wrong passwords fine, but as soon as i put the correct password in, it would allow me in, show the green android encryption picture, then blank screen. I thought it was just decrypting and setting up my rom but after a few hours my screen was still black and nothing was happening. Pulled battery and went back to TWRP.
I started wiping everything again and again and tried doing everything i could to wipe everything on the internal storage. Again, not sure what did it, but eventually got it all cleaned up and got a new rom installed and could boot into it.
The whole process probably took about 6-7 hours...
I dont even want to enable encryption on the new rom...
p-hil said:
Honestly im surprised its not talked about more since there is a big push for personal privacy when it comes to data. Encryption really is a pain in the ass to work with on android. Figuring out how to switch or update custom roms while encrypted will drive you insane. The easiest way is to just odin back to stock and start over, but that requires a computer anytime you need to flash anything.
I recently was trying out one of the 4.4.4 GPE roms and turned on encryption. It worked great until i started missing touchwiz and wanted to go back to HyperDrive TW. So the journey began...
First of all, i backed up everything to external storage since i knew everything on the internal storage would have to be wiped. I loaded the phone into recovery mode (using TWRP) and tried wiping, but all i got was a bunch of "Failed to mount" errors. Fine. Got the same error when trying to factory reset or wiping /system, /data, /cache, and anything else. Tried formatting to different file systems and then formatting back to the original but no luck. Fixing permissions didnt help. I just kept trying everything available multiple times.
Eventually it started wiping everything except the /data mount. Well... At least i could install new custom roms. Im not sure exactly what did it because i was just throwing everything at it. Anyways I got it to install, and booted into it. Nope.
Now it was saying I needed the password to decrypt the internal storage. It would detect wrong passwords fine, but as soon as i put the correct password in, it would allow me in, show the green android encryption picture, then blank screen. I thought it was just decrypting and setting up my rom but after a few hours my screen was still black and nothing was happening. Pulled battery and went back to TWRP.
I started wiping everything again and again and tried doing everything i could to wipe everything on the internal storage. Again, not sure what did it, but eventually got it all cleaned up and got a new rom installed and could boot into it.
The whole process probably took about 6-7 hours...
I dont even want to enable encryption on the new rom...
Click to expand...
Click to collapse
Yeah Encryption does not seem to work on TWZ roms. I tried on G Eye without luck.
I have updated op. Please check
Encryption will slow down your phone quite a bit. More battery usage + more CPU usage + slower phone = not worth it unless you've got some very private stuff you don't want being shared. Otherwise, 3rd party apps that lock a lot of files, can encrypt certain files, and hide others will do the trick perfectly well.'
Not trying to bash fully encrypting your phone, but I've tried it before and although I am very pro privacy, I had to eventually take it off due to all the extra hassle it created.
Don't know about slowing down. I am not seeing it. I feel differently about security.
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
EDIT:
I've solved the issue. After re-flashing the RUU, flashing TWRP, and re-rooting over and over, I figured out what seemed to be going on.
In case anyone else has the same problem as me, here was my solution:
Starting from stock, I went ahead and flashed my phone with the latest TWRP compatible with N (3.0.3.0 at this current time). Afterwards I flashed LineageOS and GApps. As usual, upon reboot, the phone needed a password to get in. So, I rebooted to Recovery, which also required a password. I hit cancel, wiped the phone with a factory reset, formatted all data, and restarted. This did the trick, and I've been running LineageOS 7.1 with no problems whatsoever!
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
Click to expand...
Click to collapse
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
5m4r7ph0n36uru said:
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
dladz said:
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
Click to expand...
Click to collapse
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
dreDREb13 said:
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
Could have thought of that myself. Encryption used by Cyanogen/Lineage is different to HTCs encryption used on Sense based ROMs. Thanks for your feedback.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
There is no password and I've had it out in the cm thread, apparently it's common knowledge, which we've both found out its not, there is no password either so you did what was required.
Also, click thanks instead of saying mate [emoji6]
Glad you're back up and running.
thanks had same issue when installing Lineage 14.1 nightly on my HTC 10 today, which already had twrp on it and the stock rom - your solution worked.
i.e.
turn off device
hold volume down while pressing power for few seconds
choose reboot to bootloader from menu
choose boot to recovery mode
hit cancel when prompted for password
choose wipe from twrp, use default options
reboot
no more password prompt.
I have an old Verizon Note 4 that I'd like to give to my wife's bed ridden grandmother. She could really use something to pass the time and talk with friends.
I wiped the phone to remove all my old stuff. I rebooted into recovery mode, wiped the cache partition and did a factory reset. When I rebooted and started to configure the phone it gave the message:
"The phone is locked because of an abnormal factory reset. Sign in to the Samsung account that was previously used on this phone to confirm that it belongs to you."
I never had a Samsung account, and I don't want to start now. I think the best course of action is to install a custom ROM. I dislike all the Samsung bloatware anyhow.
But I can't boot this phone because I can't get past this "abnormal factory reset" screen (presumably it's an anti-theft thing?). How can I install a custom ROM on this phone? Everything I've read says that I already need to have root before installing the ROM, which seems impossible since I can no longer have access to this phone's OS.
How can I proceed?
Dou you have TWRP? If not, make Odin Download Mode, put Rom Stock, and try again... root/unlock bootload/Twrp/customrom, etc
peterNYC said:
I have an old Verizon Note 4 that I'd like to give to my wife's bed ridden grandmother. She could really use something to pass the time and talk with friends.
I wiped the phone to remove all my old stuff. I rebooted into recovery mode, wiped the cache partition and did a factory reset. When I rebooted and started to configure the phone it gave the message:
"The phone is locked because of an abnormal factory reset. Sign in to the Samsung account that was previously used on this phone to confirm that it belongs to you."
I never had a Samsung account, and I don't want to start now. I think the best course of action is to install a custom ROM. I dislike all the Samsung bloatware anyhow.
But I can't boot this phone because I can't get past this "abnormal factory reset" screen (presumably it's an anti-theft thing?). How can I install a custom ROM on this phone? Everything I've read says that I already need to have root before installing the ROM, which seems impossible since I can no longer have access to this phone's OS.
How can I proceed?
Click to expand...
Click to collapse
Got to be in the phone to unlock the bootloader. Ive never seen this screen you speak of . Could you post a pic?
My friend has an AT&T S6 Edge+ that is boot looping. Initially it was just frozen/unresponsive on the home screen. Rebooting just went to a boot loop showing the Samsung splash screen over and over again, although once in a while it does actually seem to do something which appears to be perhaps a failed attempt to apply an update (see attached image)
All I really want to do is to recover contacts from it. For some reason it seems the device was not configured to sync them to Google (or Samsung Cloud afaik), and they are not stored on the SIM, so they must be on the device only. If my best option is to try to fix the boot looping (i.e. get it to boot) in order to recover this data, let me know.
I have done recovery and rooting and custom ROMs on Nexus/Pixel devices for years, but never on a Samsung device. This was running the stock ROM (but I am not sure of which version exactly)
Is it conceivable that I could use ODIN to flash the same (or perhaps a slightly newer) AT&T ROM onto it in order to get it to boot? Does that flashing process have to wipe the user data from the device? (I have already download a fairly recent AT&T ROM) This won't cause a KNOX issue, will it?
Is there another way? Can I install a custom recovery on it and access user data via ADB? Seems like that might require it to have an unlocked bootloader, right? And I bet there is no way to unlock the bootloader without first booting it and enabling "OEM unlock", is there?
Does anyone know where the Samsung Contacts app stores its data? What is the full package name of that app?
Would it be better to post this on the regular "Galaxy S6" non-Edge+ forum? Or on the non-carrier-specific forum?
Do people in AT&T stores have the ability to repair the OS or access data with a device in such a state?
Take it easy on me because I am a noob with Samsungs but otherwise pretty experienced with this sort of stuff.
scootley said:
My friend has an AT&T S6 Edge+ that is boot looping. Initially it was just frozen/unresponsive on the home screen. Rebooting just went to a boot loop showing the Samsung splash screen over and over again, although once in a while it does actually seem to do something which appears to be perhaps a failed attempt to apply an update (see attached image)
All I really want to do is to recover contacts from it. For some reason it seems the device was not configured to sync them to Google (or Samsung Cloud afaik), and they are not stored on the SIM, so they must be on the device only. If my best option is to try to fix the boot looping (i.e. get it to boot) in order to recover this data, let me know.
I have done recovery and rooting and custom ROMs on Nexus/Pixel devices for years, but never on a Samsung device. This was running the stock ROM (but I am not sure of which version exactly)
Is it conceivable that I could use ODIN to flash the same (or perhaps a slightly newer) AT&T ROM onto it in order to get it to boot? Does that flashing process have to wipe the user data from the device? (I have already download a fairly recent AT&T ROM) This won't cause a KNOX issue, will it?
Is there another way? Can I install a custom recovery on it and access user data via ADB? Seems like that might require it to have an unlocked bootloader, right? And I bet there is no way to unlock the bootloader without first booting it and enabling "OEM unlock", is there?
Does anyone know where the Samsung Contacts app stores its data? What is the full package name of that app?
Would it be better to post this on the regular "Galaxy S6" non-Edge+ forum? Or on the non-carrier-specific forum?
Do people in AT&T stores have the ability to repair the OS or access data with a device in such a state?
Take it easy on me because I am a noob with Samsungs but otherwise pretty experienced with this sort of stuff.
Click to expand...
Click to collapse
You can flash the latest firmware via Odin under CSC. Just make sure to untick F. Reset under options and choose HOME CSC as it will keep device data intact, leaving the contacts you are trying to get. Not sure if that will fix the issue on your friend's phone though. Good luck!
Rehvix said:
You can flash the latest firmware via Odin under CSC. Just make sure to untick F. Reset under options and choose HOME CSC as it will keep device data intact, leaving the contacts you are trying to get. Not sure if that will fix the issue on your friend's phone though. Good luck!
Click to expand...
Click to collapse
Thanks for the help @Rehvix. I thought CSC was just for location/carrier features. Do you think that will fix the boot loop? Is that a common situation? I was thinking I might have to flash the Android System which I believe is "AP". Maybe I should try CSC first and then AP. What effect will unticking the "F Reset Time" have? Does that option (if ticked) just reset a flash counter? And in the ROM that I got from another post on XDA (version G928AUCS5ERA2), there is only one CSC_ATT.....tar.md5. There is no separate CSC file with HOME in the name. Maybe I need to read up on Odin some more.
scootley said:
Thanks for the help @Rehvix. I thought CSC was just for location/carrier features. Do you think that will fix the boot loop? Is that a common situation? I was thinking I might have to flash the Android System which I believe is "AP". Maybe I should try CSC first and then AP. What effect will unticking the "F Reset Time" have? Does that option (if ticked) just reset a flash counter? And in the ROM that I got from another post on XDA (version G928AUCS5ERA2), there is only one CSC_ATT.....tar.md5. There is no separate CSC file with HOME in the name. Maybe I need to read up on Odin some more.
Click to expand...
Click to collapse
I apologize for creating confusion. CSC is used on phones starting with the s7 because the firmwares started getting really big so they had to break them up into chunks for flashing. For the s6 edge+ there will only be one AP file, as you mentioned. This one should end in HOME (mine goes G928TUV...EQC6_HOME.tar.md5). Flashing this should upgrade the OS to the latest version without wiping it, unless the SD Card is bad, it may or may not flash at all.
As for F Reset Time, it's not factory reset as I believed it was. It resets the flash counter, so you would want to leave that checked.