[Q] Device Encryption issue - AT&T Samsung Galaxy S6 Edge

When I got my S6 Edge I enabled device encryption so that when I would reboot the phone I would be prompted for a long password. But ever since the OE2 OTA it no longer prompts for the passphrase it just boots straight to the lockscreen. When I go into the security settings it says the device is encrypted. I am wondering if anyone else has seen this behavior or knows why this is happening.
Thanks

Well I tried decrypting and re-encrypting but the decryption process would never really begin, it just hung when trying to restart my phone, so I eventually just did a factory reset and encrypted again from scratch. It is all working again. I hope I don't have to do this every time I get an OTA.

Related

[Q] 4.3 Open Lock and "Custom" on boot up

OK, I have searched for this, but have not found it in this context. I did a flawless OTA and install of 4.3 on my S4 Active. After install I had an image of an open padlock and the word "custom" show up on a boot screen, Used to get this in the early root days, but not for several month after following some tips elsewhere in these forums.
I also had trouble connecting WiFi unless I rebooted. Whether I needed or not, I did a complete factory restore, which seems to have cleaned up the WiFI thus far, but not the lock/custom situation.
Any ideas or suggestions?

[Q] Wifi and Bluetooth not turning on

I'm trying to sell my moto x so I factory reset it but when it tries to make you type something in it didn't give you the option to use a keyboard, it only let you use voice typing. So I tried flashing some factory firmware from here after removing the line in the xml file that prevents them from flashing.
ATT 4.4.2 flashed fine and then now Wifi and bluetooth won't turn on.
ATT 4.2.2 and ATT 4.4 won't flash. Fastboot screen on the phone says "downgraded security version" so it refuses to flash those.
I never had any custom ROM's on here. It was rooted previously but HO LEE S**T it was the most convoluted process ever and I'm never doing that again. What do I do? Has anyone else had this problem?
okay somehow it got fixed.
I tried flashing 4.4 using this guide, the manual way. It kept throwing "FAILED <remote failure>" for half the stuff but i just kept going :silly: and at the end it rebooted and wifi was working. Despite trying to flash 4.4, it still has 4.4.2 on it...
really makes me appreciate how easy everything is with Nexus 5

HELP - "dm-verity verification failed..." recovery message and no cell service

HELP - "dm-verity verification failed..." recovery message and no cell service
Background Info:
Was rooted on OE2 via pingpongroot and supersu and froze some bloatware with Titanium Backup, nothing else done to the phone. Flashfire was on there but never used. Phone has worked fine this way for about 7 months.
This past Friday I suddenly lost all network connectivity and was very sporadic in connecting to the LTE network. Also lost ability to send text messages.
These are the steps I did:
1. Went to the ATT store, verified IMEI was ok, and got a new SIM card - nothing
2. Tried *#*#4636#*#* dialer code to see the network settings - nothing
3. *#0011# diagnostics dialer code - nothing
4. Tried different APN settings as well as APN reset - nothing
5. Factory reset - nothing (could not factory reset from UI, had to do it from recovery - "dm-verity verification failed..." message seen in recovery)
6. Removed pingpongroot app and uninstalled root via supersu, verified with rootchecker - nothing
7. Did another factory reset without root - nothing (could not factory reset from UI, had to do it from recovery - "dm-verity verification failed..." message seen in recovery)
8. Somehow the texting message center digit code was changed, so I did some googling and changed it back to +13123149810 from 313133127 - FIXED TEXT MESSAGING
9. Spent an hour with tech support verifying there were no network restrictions or limitations with my device - nothing
10. Attempted an OTA update on the phone - update failed (dm-verity verification failed.... message in recovery)
I didnt find too much on the dm-verity verification failed... message in recovery. It seems it has something to do with system files being modified, or something with the EFS. I cannot figure out what is going on with no network service, so an option is to either replace the phone under warranty from a service center, or to try and flash stock firmware via ODIN. Phone doesnt have knox tripped and says official under status, so I dont think I would have a problem replacing with them.
Questions:
1. Will "dm-verity verification failed..." cause issues with Odin and going back to stock recovery? Last thing I want is a brick when I could return it.
2. Can anyone think of anything else I could try in terms of trying to get my cell signal back? It connects to LTE in high populated places, but in places where it used to have fine reception (work, home) it gets nothings. This combined with the fact that my message center code was changed makes me think something deep in the network settings was also changed, but I have no idea where to look.
Thanks.
Do you still have frozen bloatware? You might want to try un freezing everything, and seeing if that helps. Perhaps you locked something up that's in need of an update / conflicting now.
AoN
anneoneamouse said:
Do you still have frozen bloatware? You might want to try un freezing everything, and seeing if that helps. Perhaps you locked something up that's in need of an update / conflicting now.
AoN
Click to expand...
Click to collapse
Everything should be unfrozen after I did the factory reset, as I saw all of the ATT bloatware pop up again.
I am receiving reception again!
1. Odin back to stock. In this case it was OE2
2. Factory reset - this removed the "dm-verity verification failed..." message in recovery
3. Took the OTA update to OI2 ROM version
4. Factory Reset
5. Took the OTA update to OJ7 ROM version
6. Now have reception again in areas where it suddenly dropped off.
I do notice that my IMEISV number changed between OTA updates, and there are some extra network options in the secret dialer code menu. Not sure if that had anything to do with it, or the fact that I did not take any OTA updates since receiving the phone 7 months ago.
Anyway, hope this helps some people who may have suddenly lost reception in places they used to have it.
orlandoxpolice said:
I am receiving reception again!
1. Odin back to stock. In this case it was OE2
2. Factory reset - this removed the "dm-verity verification failed..." message in recovery
3. Took the OTA update to OI2 ROM version
4. Factory Reset
5. Took the OTA update to OJ7 ROM version
6. Now have reception again in areas where it suddenly dropped off.
I do notice that my IMEISV number changed between OTA updates, and there are some extra network options in the secret dialer code menu. Not sure if that had anything to do with it, or the fact that I did not take any OTA updates since receiving the phone 7 months ago.
Anyway, hope this helps some people who may have suddenly lost reception in places they used to have it.
Click to expand...
Click to collapse
Sorry bro, as you installed the old program?
I believe it's because you are on Of4 firmware, but restored the oe2 files? To get back you need the flash the files in Odin from the muniz of4 update thread.
Nevermind, I see you updated already.

Internet Connection Unstable (WiFi) Since Recent OTA Update

My phone is a T-Mobile branded HTC One M7 with Android 5.0.2. A few days ago, I received an OTA Android update and since then, WiFi has been unusable.
When WiFi is turned on, the phone sees and connects to the WiFi access point, but a error message pops up, "Internet Connection Unstable" with the SSID of the access point displayed below.
I contacted HTC support and was advised to wipe the cache partition. This did not work, and the next bit of advice was to do a factory reset on the phone. I'd like to avoid that if possible... has anyone else encountered this issue?
Thanks.
Earl
UPDATE: this turned out to be not a problem with the phone. I found a rogue DHCP server on the network that was causing the instability.
they might be right, a full reset is quite useful after a ota update (for HTC phones). After upgrading to lollipop I did have a couple of bugs (tho none as major as the one you're describing) and I had to do a factory reset to get everything working flawlessly.
And after trying to upgrade from stock 7.19.401.102 to 7.19.401.121 my m7 stopped working altogether, it got stuck in a bootloop at HTC's logo. I had to flash a nandroid backup I made when I was on KitKat and then upgrade to 7.19.401.102 lollipop, do a full reset, upgrade to 7.19.401.121, and then another reset. That fixed everything for me (maybe the factory resets weren't necessary in that case tho). But I no longer care about htc's stock roms to go through such trouble again.
HTC's ota update seem to have lots of bells and whistle (and annoyances) going about them, which is why I'm on 6.0.1 crdroid ROM.
try clearing the settings app data (from settings>apps) or the WiFi app data. There's no guarantee it'll work but it's better than having to do a full reset.

G925A stuck on welcome screen after factory reset

Its been about 2 months since my phone has been unreachable to everyone that is trying to call me even though my phone is fully working with full tower and data services active almost 24 hrs a day. Everything was working fine instead if someone tried to call me they would have to hear "This phone is unreachable at the moment" operator message. My operator is Airtel btw.
So i googled this issue and some people suggested factory resetting. I thought its just a factory reset and went to recovery and reset the phone (Not my first time, but my first factory reset after i upgraded to Nougat). So after factory reset i rebooted the phone from recovery and was greeted with the welcome screen. I added samsung account, google account. Everything went fine until it asked me for time and date. I selected the time zone and it was showing the correct time so i pressed next, then again it reverts back to the same screen. I tried pressing next a million times but im stuck on that screen.
I did a cache wipe and factory reset again and same problem. Please help.
I think my Android is G925AUCU6EQCF which should be Nougat 7.0. I updated it way back when Nougat came to xda through adb sideload and havent updated the security patches. So the firmware version must be this G925AUCU6EQCF.

Categories

Resources