Hi
I started to encrypt my mi6 6 hours ago but now it is stucked on a black screen which shows "encrypting, don't reboot your device". Encrypting should lasts a couple of hours generelly and i had a lot of free space and no huge file. What should i do? If i reboot manually i will certainly lose all my data.
I had miui 9 eu weekly 7.11.16 with Magisk and twrp 3.1.1.
Has anyone of you succefully encrypt his device?
Hi,
Unfortunately it appears that there is no way to recover at this point.
Check my thread: https://forum.xda-developers.com/mi-6/help/miui-9-encryption-t3710299
Related
I just installed the bump'd TWRP and CM12 on my G3. I'm trying to encrypt it, since I need it that way for my work email/calendar, but I'm running into a problem with it.
I charge the phone fully and plug it in as required, then go to Settings/Security/Encrypt Phone. I enter my PIN and start the process, but all it does is flash the green android on a black background with what looks like a gear in the middle of it, then goes straight to the Cyanogen boot splash screen, where it sticks until I pull the battery to restart it.
Has anyone else had this problem? Or, does anyone have an idea of what I might be able to try?
jtguf87 said:
I just installed the bump'd TWRP and CM12 on my G3. I'm trying to encrypt it, since I need it that way for my work email/calendar, but I'm running into a problem with it.
I charge the phone fully and plug it in as required, then go to Settings/Security/Encrypt Phone. I enter my PIN and start the process, but all it does is flash the green android on a black background with what looks like a gear in the middle of it, then goes straight to the Cyanogen boot splash screen, where it sticks until I pull the battery to restart it.
Has anyone else had this problem? Or, does anyone have an idea of what I might be able to try?
Click to expand...
Click to collapse
I am having the same problem. Unfortunately, I have not gotten any answer. Sorry I couldn't help, but at least we're not alone.
same here, have had same issue with multiple dailies. do you think this is with twrp or cm12?
I've managed, with the latest CM12.1, to encrypt my LG G3 (d855)....However...TWRP cannot decrypt the partitions so you cannot flash anymore updates until TWRP is updated....
Shakinghead said:
I've managed, with the latest CM12.1, to encrypt my LG G3 (d855)....However...TWRP cannot decrypt the partitions so you cannot flash anymore updates until TWRP is updated....
Click to expand...
Click to collapse
How did you do it? I've tried to encrypt with 27/08/2015 nightly and I couldn't. It said encryption failed and I had to wipe it.
I'm using the 26/08 (UK date format) build - This is the one that broke Chrome. I just encrypted the phone using the settings. I've been trying every couple of weeks for sometime. In the past I get the CM logo and nothing happens. If I remove the battery then the phone boots OK...so clearly the encryption hadn't started. This time I left it and walked away. 30 mins later I went back to the phone and it was prompting for the encryption password after boot....So all good for me....except TWRP cannot decrypt the encrypted partitions...
I am using the D855 model.
I'm having similar issues. I was able to encrypt after installing the Resurrection Remix v5.5.5 but now TWRP shows internal storage as 0mb and throws out a bunch of mount errors. So can't backup or load anything new through TWRP now.
The only way I was able to change ROMs was to flash the stock ROM through the LG flashtool, thereby unrooting the phone and then starting the whole process from scratch. It's a big pain because everytime I do that I need to get admin approval to setup my work email and then need to encrypt again , which locks me into the existing ROM again!
Ughh!! Can't wait for a solution top this problem.
Hi there, I have the above device with unlocked bootloader. It was rooted but I had a problem where the tablet kept rebooting but only after it loaded Android. No amount of following guides fixed it and Recovery and Fastboot were throwing g up problems whenever I tried to flash anything.
Eventually, I managed somehow to switch it on to Chinese update cycle I think and update the ROM with the latest official Chinese EMUI through multiple reboot loops (it downloaded about 10% of the update each time before crashing and getting the next chunk of download next time).
So I'm currently on the latest Chinese ROM running android 5.1.1 and it started working again. However the ROM came without gapps included so I flashed TWRP and installed gapps and I'm back to the reboot cycle. It lasted a long time before restarting again though so I'm guessing it's to do with gapps trying to update.
So I'm back to square one again. Any ideas? Is there any kind of log I can provide to help diagnose? I still have TWRP and have access to that without the bootloop starting again..
How did you rooted it?
I have unlocked bootloader on 10.2.2 but any ROM even MIUI won't encrypt as part of adding my work profile.
MIUI says encrypting but after many hours it doesn't ever complete. Other ROMS the device starts encrypt process but just restarts.
Thx
Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
dm-verity device corrupted Force Dump
Kernel_restart
Click to expand...
Click to collapse
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?
Which specific model do you have, region? Which twrp was used?
Werchio said:
Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?
Click to expand...
Click to collapse
TWRP?! There are no working twrps for 7T series.
gpz1100 said:
Which specific model do you have, region? Which twrp was used?
Click to expand...
Click to collapse
Oneplus 7, EU region (guacamoleb). TWRP that I have managed to boot into is 3.3.1-70.
Aswin08 said:
TWRP?! There are no working twrps for 7T series.
Click to expand...
Click to collapse
My bad. It is a Oneplus 7 Guacamoleb, TWRP version is 3.3.1-70
Oneplus 7T Qualcomm CrashDump Mode
Hi Everyone,
My OnePlus 7T got stuck in QUALCOMM CRASHDUMP MODE.
First, i wanted to know the reason why this crash is happening as i can see many users reporting the same in many forums.
Note : It is my brand new phone purchased 2 days back.
Thanks !!
Restor your firmware with the msmtool
Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" .
Now ADB,Fastbootd and Windows 10 / Mac OSx do not see my device, let alone recognize
It's possible that your phone is corrupted. Double freezer bag phone, express all excess air out from bag, zip both bags tightly, stick phone in freezer for 1 hr to deplete battery, then try buttons and msmtool
Hi all,
I'm coming back to Android after an absence and would like to run Lineage on a new US unlocked 9P. I followed the directions in the Lineage OS website and unfortunately the phone now is stuck in a constant animation of the blue circle moving left over the arc, and there isn't much I think I will be able to do about it until the battery runs out.
Here's what I did as per the directions:
-got and installed adb and fastboot from the Windows zips from Google
-added the install location to the path enviro variable
-installed the Universal ADB driver from Github
-activated USB debugging and OEM unlocking on the phone
-got the phone repeatedly into fastboot mode but then got stuck since 'fastboot devices' didn't show anything
-got bailed out by another thread here that one needs to check for updates with phone connected and Win will download the relevant USB drivers. Thanks!
-unlocked the bootloader
-downloaded and flashed the 18.1-20210803 recovery img
-sideloaded the copy-partitions 20210323 zip and it got stuck at 47% just like the website said
-did the factory reset
-sideloaded the the LOS 2020210803 zip to the phone and rebooted
When I rebooted it just plays the animation I mentioned at the beginning, so it looks like it's stuck in a permaloop.
I should mentioned that after I flashed recovery and booted into the normal Oxygen mode it would take much longer to boot so perhaps there was something already creating the loop.
I am grateful for any assistance.
Thanks,
How long have you left it? First install of Lineage spins for ages
I think I left it for an hour or so. Thanks for the info - I just turned it on and will let it spin for a while and see what happens.
I let it run until the battery died. I fully recharged it and am letting it run again. Same result of blue circle tracing arc to the left.
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
lexcimer said:
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
Click to expand...
Click to collapse
Everytime you flash a new rom you need to wipe data after
Anytime that happens you just go back into recovery and wipe data a few times and it should work after that.
It would've been due to encryption. Each time you flash a new rom you need to wipe userdata which removes your lock and also removes encryption. If you try to install a rom without doing this first, the rom cannot access that partition, because it doesn't yet know the unlock code/pattern, which is why it just gets stuck trying to do so.
Thank you to the 3 posters above, and I appreciate DJ Sub's explanation, makes sense in hindsight and I'll keep it in mind for the future.
PS - I'm glad to be back to the Android modding community, it's refreshing to be able to steer what OS my phone is running
I had the same problem (also a couple of different boot loop problems) when flashing LineageOS.
I did many things, so can't say for sure which one helped me to fix that, but the things I did were:
Restore from boot loop via MSM tool flashing EU image.
Updating that OxygeneOS to the latest using internal updater.
Repeating the LOS installation process several times in different conditions to isolate the source of the problem. I was changing LineageOS package, OpenGapps package, etc.
One of the problems I've found was that latest OpenGapps package (July 28th if I'm correct) was causing the boot loop on first start (very similar to what you're describing):
Phone tries to boot showing the LOS animation.
It goes for several minutes.
Then the phone vibrates, reboots and it continues from the start.
If I'm not mistaken, it was fixed by using the version from July 24th. The latest package also were removed from the OpenGapps page later AFAIR.
Second problem was after the successful boot. The phone was rebooting from the first setup wizard, booting to recovery (or some other partition) and proposing to make a factory reset.
Not sure which of my steps solved this, but I was updating back to the last LOS package watching closely that I'm flashing the same slot on each step and also making sure that slots are properly copied from one to another with the corresponding script.
Even in the most stable setup I was probably having some setup wizard loop problems, so I was skipping account setup steps and doing that manually later.
I'd say that installing LOS on OnePlus 9 Pro was most difficult and problematic installation in my experience and I did that a lot previously: HTC Wildfire S, THL 5000, Zuk Z1, Xiaomi Mi 5s, Xiaomi Mi 9T (Redmi K20) and several other devices.