Hi,
I encrypted my 4.3 stock rdlv rooted 9005 with the stock encryption. It did not take 1 hour like i read a lot, it basically instantly reboot and asked for my passcode. My problem is now everytime i dont use my phone it wants to be unlocked by passcode. I thought it only asks for it on booting up. Its really annoying. Now i disabled passlock on lockscreen and it disabled it aswell on booting, which is weird since i read u cannot disable encryption only by factory reset.
Where did i make a mistake?
Sent from my rooted 0x0 SM-N9005 using xda-developers supreme free app
I have had this problem ever since i installed lollipop roms on my i9505, whenever i go to security, it always says swipe and none option are deactivated by device administrator, credentials etc. Also PIN lock and password lock dont work, i set them but i would still have the swipe lock when i go ahead and lock my phones screen. Also pattern works. I have cleared credentials and deactivated all device administrators but the problem persists, is there anything i can do to solve this? I updated my modems through mobile odin as my computer is unable to read my phone die to faulty usb ports.
Here i attached the screenshot to my lock screen options.
Oh yea i forgot to mention this problem only appears on touchwiz roms that i have installed, cyanogen mod roms and other aosp roms i have installed like the 7.0 nougat rom by jdc dont have this problem for me
Is the device encrypted? Are you using VPN?
Sent from my ASUS_Z00AD using XDA Labs
No its not encrypted nor is it on vpn.
Hi all!
I searched the entire forum for a question similar to mine, but didnt find any thread about it.
I rooted my S7 Edge G935FD using odin, and the startup screen where i get to input my pattern generates me an "incorrect" pattern!!
Once I reflash my firmare back to stock...everything works back as normal, and im able to input my pattern successfully and log in to the phone.
Am I missing something? ?
ahmedmohsin said:
I rooted my S7 Edge G935FD using odin, and the startup screen where i get to input my pattern generates me an "incorrect" pattern!!
Once I reflash my firmare back to stock...everything works back as normal, and im able to input my pattern successfully and log in to the phone.
Click to expand...
Click to collapse
Does disabling the pattern lock and then rooting it work?
Not sure what seems to be the issue, but this https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 works if you want to root ur phone. May as well flash a ROM (which will come with disable DM-Verity and root) while ur at it rather than root the phone using this method though (that's what I did anyways). I recommend Superman ROM.
Hope this helped
ahmedmohsin said:
Hi all!
I searched the entire forum for a question similar to mine, but didnt find any thread about it.
I rooted my S7 Edge G935FD using odin, and the startup screen where i get to input my pattern generates me an "incorrect" pattern!!
Once I reflash my firmare back to stock...everything works back as normal, and im able to input my pattern successfully and log in to the phone.
Am I missing something? ?
Click to expand...
Click to collapse
yes rooting or any major change to the operating system requires pin to be enable after the phone successful reboot and you get main, you can reset the pin to a pattern.
This is my understanding of what is need with any modifications to boot loader or kernal which rooting does.
I tried everything, from disabling fingerprint and pattern lock entirely to clearing the cache from the stock recovery menu, but still rooting or flashing TWRP cripples the phone into a Samsung logo stuck screen. The only way out is to re-flash back to complete stock.
Am I missing something? I recall rooting the S7 edge was much easier...whats going on?
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
jaszfalvi.tamas said:
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
Click to expand...
Click to collapse
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
shah22 said:
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I set a password when I enabled Secure Startup.
jaszfalvi.tamas said:
I set a password when I enabled Secure Startup.
Click to expand...
Click to collapse
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to confuse them. If it still happens, then I guess there's got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
shah22 said:
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to remember them. If it still happens, then I guess there got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I entered the password correctly, as it stated "Starting Android..." then the rotating padlock took forever. More than 10 hours even. But in the end, a factory reset helped me. But rip my photos and memories...
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Right, but i use encryption and i could update without any problem, don't know what caused this issue with him. But one should backup all data BEFORE updating, as i did to save yourself from such hassle.
Sent from my S7 Edge using XDA Labs
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Yeah, it's a sure thing I won't turn on Secure Stratup anymore. I don't know what OEM unlock does or does not, but right now, I don't have dev options enabled. If I had a microSD then I couldn't care less about resetting my phone, but since I don't have, because I have two SIM cards and a memory card has no place left, I feel bad.
Still, I don't know caused this issue. I had OTA updates before with full device encryption enabled and I had no issues before. I kinda used the same disk space at every OTA, so it should have took the same time... And I have to mention, that I did not tamper with the software. No root, no custom rom, and software only from the play store.
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
benjamen50 said:
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
Click to expand...
Click to collapse
Never had OEM unlock enabled, because I didn't know what is does, so thanks for the info. I reflashed the correct stock firmware, but that didn't help either, so I had to resort to wiping the data... Regarding this, do you know by any chance a good software for recovering data without root?
I don't know of any unfortunately, if anyone has any good paid ones that actually work please post here.
Hi,
I tried to change the pattern of my device, it seems that I didn't set what I thought and now that I restarted my system, the device (Android 7) is asking my for a pattern to let me turn it on, that I don't know.
Of course I'm the owner from this device, with my Google account and everything but I made a misstake and I don't know how to fix it.
What are my options now?, Should I restart the device with recovery options, wiping data user and that or what do I need to do?
Regards in advance.
Do you by any chance have TWRP installed? If so, there are certain files you can delete to remove the pattern.
Try it enough times and it should offer to unlock another way, then use your Google account.
And don't use pattern unlock... PIN an fingerprint are fine.