Ive had my phone encrypted for a while now. Last night I decided to decrypt it so I could root it. The problem is its been stuck on the LG Life Is Good logo for the last 8 hours. The red LG logo is doing the little shimmering effect it normally does but its stuck there. I haven't touched or dropped the phone at all so I'm not sure why its stuck.
Any ideas about what I should do? I'm hoping I haven't lost everything.
Edit: It appears that my phone will not decrypt at all!
Just an update. I pulled the battery and restarted my phone. It appears to have had no negative effect. My phone is still encrypted as well. Strange.
I was initially worried just about the phone being stuck when decrypting but now it appears that no matter what the phone will not decrypt at all. It works fine and has no issues when I enter the passcode in to unlock it etc but decryption does not work at all. The phone is ZV8 stock.
Has anyone else had this issue?
Sokesleezy said:
I was initially worried just about the phone being stuck when decrypting but now it appears that no matter what the phone will not decrypt at all. It works fine and has no issues when I enter the passcode in to unlock it etc but decryption does not work at all. The phone is ZV8 stock.
Has anyone else had this issue?
Click to expand...
Click to collapse
I have the same issue. mine is a d852 from Rogers (Canada) and is unlocked. I had 2 different work emails on the phone that each required the encryption and was applied of course. I removed the email accounts before upgrading to lollipop. I did not decrypt the phone prior to the update. I think that may be the cause for this. (need to decrypt first before the update).
I can reboot the phone and still get into it using the passcode. but if I try to decrypt the phone, its stuck on the LG life is good screen.
I dont care about the data/msgs etc... I just want to turn off the encryption as I do not need those work emails on my phone. would be great to hear if anyone else has had this and if so, how you were able to get past this.
Sounds like you and I have the same exact issue.
Yessir and no support or comments/feedback from anyone here is surprising.
I don't recall seeing anything in the upgrade msg about decrypting the phone first, but if so; then it's our oversight...
If anyone has not yet upgraded to lollipop and can proved some info on what the msg/warning is before you upgrade would be super helpful, at least helps us check something off the list of potential causes anyways.... Nothing on LG site or google that I have found on this issue...
I tried adding the same accounts back to the phone then decrypting and a reset but same thing... Stuck on the LG screen till I pull the battery. Even left it overnight and no difference. Phone was pretty warm in the am.
Seems there is no way to remove the decryption AT ALL after upgrading to lollipop if you didn't decrypt first..
mr.vic said:
Yessir and no support or comments/feedback from anyone here is surprising.
I don't recall seeing anything in the upgrade msg about decrypting the phone first, but if so; then it's our oversight...
If anyone has not yet upgraded to lollipop and can proved some info on what the msg/warning is before you upgrade would be super helpful, at least helps us check something off the list of potential causes anyways.... Nothing on LG site or google that I have found on this issue...
I tried adding the same accounts back to the phone then decrypting and a reset but same thing... Stuck on the LG screen till I pull the battery. Even left it overnight and no difference. Phone was pretty warm in the am.
Seems there is no way to remove the decryption AT ALL after upgrading to lollipop if you didn't decrypt first..
Click to expand...
Click to collapse
It appears that after the zva update I'm able to decrypt my phone I did it on a whim after remembering I hadn't tried it after the update.
I'm assuming this is the reason, as nothing else has changed. I did it about 3 days and it went through pretty quickly.
I ended up going through Rogers warranty to get the phone re images. Not sure what caused it to not play nice when I did it. None the less I sold the phone.
Related
Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated
same prob
i've the same problem since the last update. hope it will fixed soon.
ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)
Anybody?
Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
robertlewisca said:
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
Click to expand...
Click to collapse
I was having the same exact problem. I even changed phones thru warranty. The new phone did the same thing. New SIM card didn't help. I had a guy at tech support to push the update to me.
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
IDK, co-worker with a Skyrocket has had the same issue, but he doesn't care about the update, so he hasn't bothered to get it resolved.
If I didn't have a red GS3, I could goof around and tell you that is what the problem is...
Actually, if it were me having the issue, I'd walk into AT&T and have their guys mess around with it. No telling why some have more issues than others.
robertlewisca said:
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
Click to expand...
Click to collapse
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Not really a solution but you could install this http://forum.xda-developers.com/showthread.php?t=1902178 to be fully stock LH9 with Root. Or use the OTA zip from here http://forum.xda-developers.com/showthread.php?t=1896773.
aboveusonlysky said:
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Click to expand...
Click to collapse
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
78c10 said:
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
Click to expand...
Click to collapse
You mention in your signature that your phone is rooted. So, did you update OTA then root, or did you update after rooting through some other method? The challenge some of us are having is that we are not rooted, and cannot update OTA because of the 'server error' it gives us everytime we try.
Problem Solved - for me at least
Well, the problem is solved for me, and I thought I would share what I found out here in hopes it helps someone else.
First, I had the phone replaced under warranty. It appears to be a brand new phone. When I received the new phone, I started it up, went through the normal startup stuff - entered my Google account information, it backed up my info and settings. Before I loaded any apps, I went straight to the update screen, and tried to check for an update. I again got the 'communication failed' error. Bummer.
So, then, I did a factory reset on the new phone, but this time instead of entering the initial Google account info on the startup screens, I skipped through all of the initial screens, got to the home screen, then went straight to the update screen - and this time it worked! So, it must be something to do with the initial screens, and entering Google account information that caused the problem.
Then, I got to thinking - perhaps this might work on my old phone too. Since I just got the warranty phone today, I still had my old phone (which needs to be sent back). So, I did a factory reset on it, skipped all of the initial screens where it asks for Google account information, and it still didn't work on the old phone. So, I'm not sure what the original issue was.
By the way, after the update installed on the new phone, and I went through and entered all of the Google account settings, and then checked for the update again, and there was no error.
So, perhaps this might be helpful for others?
Hello,
I was facing some of the problems everyone is reporting here about random restarts and bootloops even (and mostly) using stock firmwares. As many of you started to have the problems after updates my problem started when I tried to root for the first time when SuperSU was not totally working yet. These problems didn't stop even flashing everything to stock (bootloader, modem, firmware, csc) and other stock firmwares from other countries so I was thinking that my phone was faulty too.
Every reboot my phone asked me for a password that I never set, so there was nothing to put there and I always had to reboot into recovery and flash the "no-verity" script or else I would get stuck in a bootloop or the phone asking me for a decrypt password (that didn't exist).
Sometimes when the phone randomly restarted gave me the "verity encryption" error at the beginning when using the stock recovery, if using TWRP it asked me for a password after semi loading Android (since it didn't found the official recovery to show that error from it), so I always suspected that the Samsung encryption was causing all my problems. Tried everything and even made a post about it (http://forum.xda-developers.com/note-7/help/random-restarts-password-doesnt-exists-t3450678)
So I kept waiting for something that disabled the phone encryption to verify that this was the real cause of this random behaviour before going to Samsung for warranty. Finally @Tkkg1994 came up with the Hydrakernel that disables the encryption so after trying it and formating everything MY PROBLEMS ARE TOTALLY GONE.
My suspects were finally confirmed..... The Samsung encryption was causing all these sh1ty problems (at least in my phone).
So everyone that is flashing stock firmwares even going back to old ones, it seems that doing this doesn't fix anything once you got into this problem for the first time, only disabling the encryption solves it. So my recommendation would be to disable the force encryption from Samsung by using the Hydrakernel and testing again (http://forum.xda-developers.com/note-7/development/kernel-hydrakernel-v1-1-t3452433)
I would like to thank all the devs that are doing their best effort to give us a free Note 7 to enjoy. @Tkkg1994 @dr.ketan @Chainfire it is very admirable that common people like them can solve things that not even Samsung has figured them out yet.
PS: Have you guys flashed this ROM and kernel instead of stock firmwares and continue to have problems with your Note 7??? Give your feedback!!!
Interesting, keep us posted with your phone status...
nice job keeping on testing & we waiting your next result
Hello! I am going to describe my issue with 2 years old nexus 5x which is restarting randomly.
It all started a couple of days ago when my phone started to ask me to enter PIN code. That happened randomly. After entering the code my phone worked completely ok.
But yesterday it started restarting on its own. The restart happened once, than I suddenly got a message before loading screen saying: "Your device is corrupt. It can not be trusted and may not work properly".
Today my Nexus restarted around 10 times. These restarts do not depand on phone usage, since it is restarting randomly (when charging, when not charging, when using it, when screen is off).
I decided to clear cache partition factory reset it and update apps. Unfortunately that did not help, since my phone is restarting even more frequently. Normally it freezes for 5 seconds and than restarts. Sometimes I still get the message: "Your device is corrupt...", but not always.
My Nexus has not been modified (it is not rooted and it is running android 8.1 with november security patch). Also apps have been installed only from play store and not from unknown sources.
I would really need your help. Has anybody experienced any similar issues or does anybody know what could cause the restarting?
Thank you in advance.
@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.
rp158 said:
@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.
Click to expand...
Click to collapse
Thank you for your response. Is installing a custom rom the only possible soultion?
No. It's no solution. It's a vague trial.
tic_tac7 said:
Thank you for your response. Is installing a custom rom the only possible soultion?
Click to expand...
Click to collapse
If you are original owner of phone for up to 30 months, go here and let LG fix (or attempt to) the phone. Mine required two repairs. If you are not in the US, check with LG support in your country.
EDIT: Apparently this was a result of using the wrong setting for enabling hotspot in PropsConfig. Because all that stuff was set during bootup, deleting apps wouldn't change the situation. Setting worked fine on my Pixel XL, but not here. Changed the setting and all is well.
--------------------------
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Might be quicker and easier to back up your required files and just factory reset.
Texan1 said:
Might be quicker and easier to back up your required files and just factory reset.
Click to expand...
Click to collapse
*sigh* I kinda made this post to avoid that step.
somethingsomethingroot said:
*sigh* I kinda made this post to avoid that step.
Click to expand...
Click to collapse
I know, it's just that it sounds like you've already disabled some things that could be causing it, which hasn't helped. If it was me, with something like constant reboots, I'd want to start fresh just to make sure they are eliminated for good
somethingsomethingroot said:
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Click to expand...
Click to collapse
I've seen reports of "random" (=not intentional) reboots after
+ booting up the phone
+ using the FP scanner
+ making videos or shooting photo
+ doing a firmware update (I've seen both reports of ppl that "officially" OTAed & used manual flashing)
+ doing nothing
+ doing something
Some were able to fix their issues by factory resetting, some needed replacement devices. Some reported that even after a factory reset, the issue still persisted, but they were able to fix it by NOT using a backup via cable, some reported that even the Google Drive backup "corrupted" their phone (fix after setting up everything by hand from scratch). Some even reported their issues to get fixed via a software update.
So it seems to be connected to hardware (= replacement device) and/or software simultaneously (=fix via reset).
Strange this is since there are also numerous reports of Samsung owners that upgraded to A12 about random reboots. So it might even be something Android 12 related, or it's just Samsung also implementing similar bugs without it being A12 related (unlikely, since the reports seem to be centered around people using the new A12 update).
I also had the random reboot problem (~ 6 times a day, when doing nothing, it just rebooted when the phone layed on the table in idle). I wasn't able to fix it via a reset, so I got a replacement device.
I also have the "random" reboot problem on my Pixel 3 since upgrading to Android 12 (never had any issues all the years I've been using that phone), so that issue is clearly caused by A12, but I haven't troubleshot it/ tried to solve it, since I don't actively use the phone currently.
Aside from trying a factory reset and minding the backup issue (especially backups that you got from phones that did NOT have Android 12), there is not much more that you can do (ofc you could also use the Pixel repair/android flash tool to do a "clean" install of Android on your phone). Next step would be to contact Google.