Hi All,
I flashed crDroid 6 ROM [Android 10] on my OP2 and it was working fine and ROM was awesome, however when I was trying to register my device to my Company Portal, it insisted to enable encryption, the encryption now is stuck on Android Logo since last 6+ hours, i'm afraid to interrupt the process as the device may get bricked and cannot be used. When encryption is in progress will the internal storage be encrypted as well?
How to recover my OP2 back to life.
Thank you,
Regards.
ralamuri said:
Hi All,
I flashed crDroid 6 ROM [Android 10] on my OP2 and it was working fine and ROM was awesome, however when I was trying to register my device to my Company Portal, it insisted to enable encryption, the encryption now is stuck on Android Logo since last 6+ hours, i'm afraid to interrupt the process as the device may get bricked and cannot be used. When encryption is in progress will the internal storage be encrypted as well?
How to recover my OP2 back to life.
Thank you,
Regards.
Click to expand...
Click to collapse
Do you have a backup from your data and internal memory?
Related
Hello,
First of all, sorry for my bad english, i'm french and not very good
Thanks for reading me and the help you give me on xda (even if i never post, i always find my solution on the forums )
I'm actually on CM13 6.0.1 20160810 beta, working quite good since then, but my system is going completely drunk, my sim is not working any more (only my sim), wifi problems etc.
Factory reset is a solution but i have to setup again all my apps, so I want to update to 7.1.1 and then setup all my apps on a new rom without the bugs i used to.
I create this thread because i tried to install MAD Team aosp 7.1.1, stable 7 and also stable 8 and succeeded, but bluetooth is not working...
The problem i have is when i install this rom, bluetooth is written as "Disabled", and when i turn it on, it stays greyed 10 seconds and returns to OFF.
I tried many things :
-install starting from CM13 with factory reset
-install starting from CM13 without factory reset
-install starting from CM13 with format data
-install official 5.1 after factory reset + format data, then install 7.1.1
-factory reset after installing 7.1.1 with all methods over
I'm out of ideas, not finding useful things on the web, even on XDA threads :crying:
It's not hardware problem, my BT works perfectly on CM13 actually, and when I reinstall CM13 after a 7.1.1 fail (with or without restoring my data), it works again...
If you have any idea, i'm desperate :fingers-crossed:
Thanks for your help
I had the same problem the first time I enabled Bluetooth, but rebooted the phone (just one time) worked. Now Bluetooth works perfectly.
Thanks for your quick answer, I tried it this morning but no result.. :crying:
Hello, it's been a while and the update doesn't fix this issue : the clock/time is TOTALLY off, for example now it shows we're in june 2018.. Is there a version that doesn't have this issue? Also backing up with encryption ALWAYS fail (unless you don't backup data partition so far)..
GoJo ^^ said:
Hello, it's been a while and the update doesn't fix this issue : the clock/time is TOTALLY off, for example now it shows we're in june 2018.. Is there a version that doesn't have this issue? Also backing up with encryption ALWAYS fail (unless you don't backup data partition so far)..
Click to expand...
Click to collapse
Format your internal storage don't set pin at lockscreen use patterns instead also download latest twrp from twrp website BTW wrong section of posting read the forum rules
...goodnight
Not having encryption or pin, that's a solution for you? Not for me!
Sent from my Redmi 3S using Tapatalk
I never had any worries with official version of TWRP. Once the clock is set, it remains .... unless you fully discharge the battery, which is not recommended at all.
You will also try the new Shrp_Land project, it seems very interesting and based on last version of TWRP.
Just tried that SkyHawk TWRP and SAME! The clock is OFF, it's still 2018.. This is not an hardware issue, i have other TWRP that displays time correctly, but sadly have some other (worse) issues so i cannot use. I downloaded my TWRP from official website, there must be a reason the clock is crazy.. Please help me find & fix the problem!
Greetings.
Due to events beyond my control, I had to give up my Pixel 3 XL (packing it as I type this)
Until funds become available, I decided to bring the Nexus 6P - with pre-mature battery shutdown issue - back to duty. I have new battery, lens cover, etc. waiting in the wings so it may become my primary whip after all. That is "if" I can undo whatever mistake I made tonight (knocking on wood).
The 6P was unlocked already before being retired (Idon't know if it matters or not). Stock image (I think it was 8.1) with security update from December 2018 I think.
Here's what I think I did tonight that lead to the current situation:
1. installed TWRP 3.3.1
2. along the way wiped one too many partitions - my stupidity
3. thanks to TWRP for warning me that there was no OS so went back, found USB-A to USB-C adapter, copied "PixelExperience_angler-10.0-20191113-2124-OFFICIAL," and used TWRP's "Install" option
First problem is that I noticed in the text log within TWRP that the vendor image was missing
Second problem, or perhaps because of above, after restarting the 6P it never gets out of the welcome screen of Android 10
Third problem, again may be related to #2 in the things I did tonight, when I reboot into TWRP recovery, first thing it does ask is "Mount, Decrypt Data" and "Enter Password" to which I don't know the password. If I select "Cancel" I get to TWRP main menu but I can see that "Internal Storage" is now at 0MB.
I know I did wrong here but is there any way to recover? Since it doesn't boot into Android 10 (just stuck at welcome screen, I guess using ADB on laptop, if it helps, is out of question? Can I fix this through TWRP?
Thank you for any help/advice.
UPDATE: Reading some more threads on XDA & decided to try Lineage. At one point seems to have things working following the directions but the SIM card was not recognized.
Thinking of trying again with Lineage but maybe with Lineage16 instead of 17. But what is the best stable ROM that is plain Android but perhaps based with up-to-date security patching?
Thank you!
ur2punk said:
UPDATE: Reading some more threads on XDA & decided to try Lineage. At one point seems to have things working following the directions but the SIM card was not recognized.
Thinking of trying again with Lineage but maybe with Lineage16 instead of 17. But what is the best stable ROM that is plain Android but perhaps based with up-to-date security patching?
Thank you!
Click to expand...
Click to collapse
I've been running aicp for the past few months, which is 9.0 they still put out weeklies with security updates. Not sure how long they plan on supporting 9.0 though
Lawlrus said:
I've been running aicp for the past few months, which is 9.0 they still put out weeklies with security updates. Not sure how long they plan on supporting 9.0 though
Click to expand...
Click to collapse
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
ur2punk said:
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
Click to expand...
Click to collapse
Yeah I haven't noticed any issues with Sim with this device. You said you had it on a shelf for a while though, if it was before the last update the device got, DEC of 2018 did you DL the ota a d make sure the radio was up to date ?
ur2punk said:
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
Click to expand...
Click to collapse
I had this SIM card issue when I was trying to flash RR, tried twice with same results. Came across a post once about a bug and it said to remove all screen locks, low and behold it worked... weird
redshirt110 said:
I had this SIM card issue when I was trying to flash RR, tried twice with same results. Came across a post once about a bug and it said to remove all screen locks, low and behold it worked... weird
Click to expand...
Click to collapse
Ah yeah, I've seen that before no idea why people have to do that. I've never had my Sim stop working because of a screen lock. I never looked onto why it happens. I always chaulked it up to a not a US problem because most of the people that posted about it seemed to be from a different country lol.
Update!
I thought it would be a good idea for me to try this routine of wipe & install the Android 8.1 again to get myself comfortable with the process. Long story short, I did exactly that:
(- Bootloader was already unlocked)
- TWRP
- flashed/installed Dec 2018 OTA images/zip
- Installed Magisk
Everything seemed to be working fine when I found out ,while on road, that Google Maps don't work after 5 seconds or so (the navigation part). Read up & they suggested safe mode so I did that. Happy to report that it works so it is not the GPS antenna as some had reported. Whew.
Is there any particular image I need to reflash to see if that was the problem? Or should I just reinstall again? At least I'm getting more comfortable with the various commands - LOL.
Thank you!
Hi all,
Is there any Custom ROM running Android 11, with encryption working. I tried PE11 and Crdroid 7.4 and Arrow11.
All are going to boot loop, if encryption is initiated.
I'm looking for a ROM which can do encryption (for work purpose). It will be helpful, if someone can share working custom ROM tested.
Also is this some kernel issue or TWRP settings which is causing encryption to fail?
I would also love encryption. This is one of the persistent issues I have with custom ROMs and why I'm moving to a real Linux phone once they get a bit better.
Hi, after attempting to enable encryption I get an infinite boot loop animation, and after I force a hard reset (keeping the power button pressed) the phone boots back to normal as if nothing happened. This means that encryption was not even started (otherwise it would be needed to format partition again if the process was interrupted).
What are my options here? On previous Android versions, whenever I came across a Rom that didn't support encryption, I would just flash a stock recovery image alongside the custom rom and try encrypting again, successfully. However, there are no Android 11 stock recovery images for this device (it got abandoned in Android 8.1 I believe), so this isn't an option anymore.
Unfortunately this ROM doesn't seem to have a dedicated thread here on XDA and people on their Telegram channel have not been able to provide guidance so far...
Any tips are appreciated!
ROM: PixelExperience Plus 11 (Android 11) version 2021.05.14
Device: Moto G5 Plus (potter, XT1685)
Recovery image: TWRP 3.5.2_9-0-potter
I have found no v11 or v10 roms which work with encryption (even when they say they do). I have not tried many v9; Your answer is to go back to stock 8.1 and everything will work again (but you'll be on v8):
[Oreo][Stock][Rom] TWRP Flashable Stock Builds
About this project This project provides repackaged Stock Oreo roms that can be flashed by TWRP. Modifications from stock are listed below. As we are now moving into the Oreo world, I've decided that now is a good time to make a few changes...
forum.xda-developers.com
edit: note that i'm on xt1687 (usa) model of potter
edit2: I just tried Arrow v10(official) and it encrypts (after a number of reboots; give it time)
bravo97 said:
edit2: I just tried Arrow v10(official) and it encrypts (after a number of reboots; give it time)
Click to expand...
Click to collapse
hi, in the case of PE+ 11, it just goes to reboot the first time and stays in loading android screen forever (waited a couple hours last time), so I think "giving it more time" wouldn't solve it.
Good to know there's some Rom compatible with encryption though, although it's android 10... I also got a hint that crDroid 11 may be compatible with encryption on potter.