Stuck with "unsuccessful encryption" dialog, have not activated phone encryption!
Received my OPT about 3 weeks ago.
Today, I cannot get past the SIM unlock dialog. With a successful PIN code, I see a dialog "encryption unsuccessful", some more text and at the bottom a button with "reset phone". However, nothing happens when I hit that button.
I did perform a factory reset in the recovery mode, but I still see the "encryption unsuccessful" dialog.
I never activated encryption of the phone in the first place.
The phone is un-rooted, no attempt was made to change that.
What is the best appoach now ?
I have the identical issue. Have raised a ticket but not heard back yet. Has yours been resolved?
But mine was rooted
I had the same result encrypting my phone.
I was rooted and lost everything.
I had the luxury of atill being able to boot into twrp to recover.
So the recovery was not effected by the screw up.
You maybe able to simply run through the root process to gain access to a recovery like twrp that is worth somehting to format the space back tp something you can use and reflash the Rom
ahgillett said:
I have the identical issue. Have raised a ticket but not heard back yet. Has yours been resolved?
Click to expand...
Click to collapse
Mine was addressed, I had my device replaced.
Related
Nexus 7 (2012)
4.4.4 Stock
KTU84P
HW Version - ER3
Bootloader Version - 4.23
Locked Bootloader
Not Rooted
I have a Nexus 7 sitting in front of me that was dropped off by my aunt in hopes that I could repair it for her. It doesn't look too promising, but I thought I'd consult the mighty fine people here on XDA before I give her the bad news. Here's what she says happened. Yesterday, while preforming day to day activities on it (browsing internet, Skyping, Facebook, etc), the device completely froze. After holding down the Power Button and forcing it to shutdown, she booted it back up. Everything seemed to functioned properly for about 30s - 1min when, at that time, the device turned off and rebooted on its own. After booting back up, it started to repeat this cycle. Basically getting stuck in a bootloop. I personally have never witnessed a bootloop like this before, where the device successfully boots up completely into the OS before turning off and repeating. I'm more used to dealing with ones where it might go as far as the manufacturer logo and then repeats. So anway, as I stated, I only have a 30s - 1min window where I can make changes in order to troubleshoot. The first thing I figured I should do was to go into "About Device", turn Developer Mode on and get USB Debugging enabled. I was able to do this and used "adb devices" to confirm its connection to my computer before it looped again. After its next bootloop I headed back into settings because I wanted to take note of the Android version she was running. As I was navigating there, I noticed that the Developer Options were no longer active. Basically as if I hadn't enabled them yet. This made me start thinking that changes being made on the device weren't sticking. I decided to make a few visual changes to the home screen and see if they were still there after the next bootloop. I uninstalled an app, rearranged icon placement, and changed the wallpaper. Once it shutdown and booted back up again, everything was back to the way it was before the changes had been made. The app I had uninstalled was still there, the wallpaper reverted back, and the icons were back in their original location. At this point I decided to see if I could reboot into Safe Mode. Unfortunately, this doesn't work. I am able to get the reboot to Safe Mode confirmation box and tap "Ok" but it remains in Normal mode when it boots back up. I eventually tried to boot into recovery and preform a Factory Reset. I was able to get into recovery and reset the Nexus. Or so I thought. Instead of seeing a Device Setup screen after it wiped, like I assumed I would, it booted up and still had all the data on it. There were no errors during the wipe and it was confirmed with "Data wipe complete." afterwards.
I am absolutely lost. I've never dealt with such an unusual issue before. Especially with it not even reacting to a complete data wipe. So, just to recap . . . I only have 30s - 1min available to interact with the OS before it reboots itself, any changes made during that time don't stick, Device is successful booting into Stock Recovery, and I can successfully get a Fastboot connection when booting to the Bootloader.
Luckily she has come to terms that this might not get fixed and has decided to go a head an order a newer 2013 model. I'd still like to try any solutions that you all might have. Just in case there is a slight glimmer of hope.
Oh, and one last thing I should mention. I tried to see if I could get the bootloader unlocked but it didn't work. This is the first Nexus I've ever had in my possesion, so I'm not really familiar with the tools available for it. I found WugFresh's Root Toolkit and attempted to Unlock with it. The process seemed to go as it should and I didn't receive any errors on the tablet or in the software. However, in the end, it didn't make any changes to the bootloader.
same problem
I have the same problem as you.
Did you find a solution?
Can anybody help us?
Thanks.
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
eawooten said:
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
Click to expand...
Click to collapse
I have tried factory reset from recovery, no errors while wiping but when device restarts nothing has happened: I only have a 30s-1min of old system with all my data and apps or directly bootloop.
Also I have tried flash factory images with Nexus Tool Kit and directly from bootloader. No errors while flashing, apparently has flashed new image system. When device restarts nothing has happened: bootloop or my old system with data and apps for 30s before restart.
Myself and a few others are having the same problem... please keep us updated if you find anything out.
http://forum.xda-developers.com/showthread.php?t=2588911
A couple of days ago my Nexus 6P suddenly rebooted while in normal use. Now it is stuck in a bootloop ("Please lock the bootloader"-screen -> White "Google" logo -> brief black screen -> repeat).
The device is unlocked, and I am able to enter fastboot mode. Flashing partitions is possible, but I am NOT able to enter recovery. When selecting "Recovery mode" from the menu, the device just goes into the same bootloop. I tried to flash and boot different recovery images (Stock, CM, TWRP) without success. The bootloader and fastboot appear to working normally otherwise.
Does anyone have any idea what is going on?
Thanks
This just happened to me yesterday.. I've tried flashing different recoveries too but no dice.. I reflashed factory image and still the same bootloop..
This happened to me too like a month ago. I was just checking facebook and stuff, when suddenly it rebooted. Didnt think about it at first as I know it reboots some times, but it just got to the "please lock your bootloader" - message and then the white google-logo. Was able to access bootloader but not recovery. So i flashed stock to see if it helped, but it didnt. Got in contact with the store that sold me the phone, and they said it had to be repaired. Obviously I never told them that it was unlocked, never mentioned I saw the "please lock" - message, only the white google logo. So as I had already flashed stock I just locked the bootloader and returned it to the store and a week later I got it back. They had replaced the circuit board so yeah, nothing you can fix by flashing.
So get an RMA on it, or you will have a very pretty and expensive brick
Hope this helps you
Jaggenite said:
This happened to me too like a month ago. I was just checking facebook and stuff, when suddenly it rebooted. Didnt think about it at first as I know it reboots some times, but it just got to the "please lock your bootloader" - message and then the white google-logo. Was able to access bootloader but not recovery. So i flashed stock to see if it helped, but it didnt. Got in contact with the store that sold me the phone, and they said it had to be repaired. Obviously I never told them that it was unlocked, never mentioned I saw the "please lock" - message, only the white google logo. So as I had already flashed stock I just locked the bootloader and returned it to the store and a week later I got it back. They had replaced the circuit board so yeah, nothing you can fix by flashing.
So get an RMA on it, or you will have a very pretty and expensive brick
Hope this helps you
Click to expand...
Click to collapse
Oh my.. I was hoping against hope nobody would say this..
Thanks mate!
I recently successfully restored my Axon 7 (A2017U) to B20 and tried to OEM lock it again. After running "fastboot oem lock", the phone rebooted, but came up with something that said "To start Android, enter your password." I didn't have a password before, so I tried something I found online called default_password to see if it would unlock (which it didn't) & then other passwords to get the phone to wipe itself and essentially perform a factory reset. However, now it is stuck in Safe Mode and says "Decryption unsuccessful: The password you entered is correct but unfortunately your data is corrupt." When I try to wipe the phone, it says it is factory resetting, but then it restarts and goes to a blank screen. (Which I suspect is because TWRP is still installed as a recovery, not stock). In addition, power+volume up no longer works since the phone is oem locked, but power+volume down takes the phone into Factory Test Mode. My computer still recognizes the phone when it shows up in Safe Mode, but I cannot see it in ADB.
Where can I go from here to factory reset the phone? Is it possible to send this to ZTE to fix since it is OEM locked at the moment?
I followed razorblader's advice and successfully got the phone into EDL mode and ran tenfar's tool. However, that made it worse and now the phone just shows ZTE for the second & the screen goes blank.
EDIT: Nevermind, I was running that program without recovery.img/boot.img in the same directory, D'OH! Luckily, I still had comms with the phone after that mistake & I re-ran the program successfully. I can now get into TWRP recovery. However, booting into system still shows the corrupt data message. I'm going to try a factory reset from TWRP and see if that fixes the issue.
OK good news, got my Axon 7 working again, stock + locked & am currently posting this from it. One reason I wanted to relock it however was to get OTAs and right now B27 is showing up. Now before I almost brick my axon again, do I need to flash stock B20 recovery before I'm able to install this update? Also, I'd like to get to B29 eventually, but I'm guessing I need to update to B27 first. (correct me if I'm wrong though)
Hey all.
I've created a problem with my S8, don't know what to do from here.
Simply put, i had the encryption before booting on, always worked fine. I also clear the phones cache once a year.
I went into recovery, and cleared the cache partition, then on reboot it just keeps rebooting, shows the S8 screen, goes black, buzzes twice and repeats.
I've tried factory resetting in recovery, which worked, but still bootlooping. (At the bottom of the Recovery Menu, i also see the message: dm-verity verification failed)
I called Samsung about the issue, they told me to take it to the nearest authorized repair facility, which i did and they said it would be hardware without even diagnosing it. So i took it back home, and tried a few things myself, i loaded up Odin, with the exact firmware version i am on, and it will unpack it all, but always fail. Odin sees the phone fine, and download mode works. Ill provide a picture of it for reference below.
tl;dr cleared cache, sent it into bootloop, tried repair shop and flashing with odin, no avail.
Not looking to void warranty or trip anything also. It is out of its one year warranty period of course, but i've had Samsung honour a S7edge screen and battery at about 1.8 year out of warranty.
Whats my best option? Is the encryption lock preventing Odin from flashing? I have the code, as it is my phone, wondering if there is another way to enter it as the prompt won't come up due to the bootloop
Nortonic said:
Hey all.
I've created a problem with my S8, don't know what to do from here.
Simply put, i had the encryption before booting on, always worked fine. I also clear the phones cache once a year.
I went into recovery, and cleared the cache partition, then on reboot it just keeps rebooting, shows the S8 screen, goes black, buzzes twice and repeats.
I've tried factory resetting in recovery, which worked, but still bootlooping. (At the bottom of the Recovery Menu, i also see the message: dm-verity verification failed)
I called Samsung about the issue, they told me to take it to the nearest authorized repair facility, which i did and they said it would be hardware without even diagnosing it. So i took it back home, and tried a few things myself, i loaded up Odin, with the exact firmware version i am on, and it will unpack it all, but always fail. Odin sees the phone fine, and download mode works. Ill provide a picture of it for reference below.
tl;dr cleared cache, sent it into bootloop, tried repair shop and flashing with odin, no avail.
Not looking to void warranty or trip anything also. It is out of its one year warranty period of course, but i've had Samsung honour a S7edge screen and battery at about 1.8 year out of warranty.
Whats my best option? Is the encryption lock preventing Odin from flashing? I have the code, as it is my phone, wondering if there is another way to enter it as the prompt won't come up due to the bootloop
Click to expand...
Click to collapse
Whats the error displayed in odin mode
kpwnApps said:
Whats the error displayed in odin mode
Click to expand...
Click to collapse
No error other than saying (Successful: 0 / Failed: 1)
Nortonic said:
No error other than saying (Successful: 0 / Failed: 1)
Click to expand...
Click to collapse
Try different cable. Sometimes its cable fault
kpwnApps said:
Try different cable. Sometimes its cable fault
Click to expand...
Click to collapse
Tried 5 different cables, OEM, and off-brand.
I've contacted samsung again.
Hi, I have a Samsung Galaxy A52s 5G that goes into the following loop for two days:
boots up, waits for me to unlock the phone through the draw pattern, I unlock the phone, "Phone Starting" pops up, phone starts, I am able to navigate the phone and phone apps for something like 20 seconds and then it freezes.
Model Number: SM-A528B/DS
The firmware shown in recovery mode is the following: A528BXXS1CVI6
Why I am trying all this
This is my wife's phone. I thought she was backing up photos through google photos and she told me that she was doing it. Unfortunately, she was only uploading them on the local app and the backup was not working since her storage was full for several months. So, if there is a way to access her stuff from any Operating System please let me know. The problem, I think, is that I can't without unlocking the phone (of course).
Note
If I don't unlock the phone, the phone does not freeze but of course, I cannot do anything. Therefore, I suspect it is some thread that starts by default as soon as the phone is unlocked.
What I tried
I tried the following things:
Remove the SD/SIM card tray (just because it was easy)
I tried to boot my phone in Safe mode. I correctly entered in safe mode, the third-party apps were disabled but then the phone froze again.
I connected the phone to a laptop (running Ubuntu 22.04) and entered in recovery mode. Once in recovery mode, I tried basically all the options without any luck so far:
Reboot system now
Reboot to bootloader
Apply update from ADB:
I tried to download a firmware for my phone and then send it through ADB with the following command
`$ ./adb sideload ~/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip`
and I got stuck at
`serving: '/PATH_TO/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip' (~0%)" `
I don't know why
I did not try "Apply update from SD Card" yet
I did not try "Wipe data/factory reset" yet
I tried "Mount /system" but it got me the following error:"Error updating for slotselect"
I tried "Repair apps"
I tried "Run Graphics test"
I tried "Run Locale test"
I tried and then did "./adb reboot recovery" to test that I was able to reboot through adb and it did reboot the phone indeed.
Let me know if you have any ideas on what to try next.
Having a similar issue right here, please notify me what you did afterwards and if you managed to solve it
I am in the same situation and same try outs. Only one slight different. Phone does not start at all. Only "SAMSUNG" and "powered by android" logos. Then starts to bootloop again.
Did you find a solution?
@minidiable did you try to flash with Odin? You should have a try using CSC that avoid erasing data.
In any case, I'm coming back here to give my result after several try-outs and finally going to a Samsung Center.
My phone, entering in recovery mode, had from the begining a message at the bottom saying " E:[libfs_mgr]Error updating for slotselect ".
At Samsung Service Center they told me that this error may probably warn about motherboard failure. And after tearing down the phone and checked it, they changed the moterhboard. Sadly, All data lost. That's all.