Database Develop

XT1068 stock fw fde trouble

Hi,
I've got XT1068, updated to 6.0 Marshmallow. In the past, I got it FDE (full disk encrypted).
Few days ago I unlocked my bootloader to gain root access on my phone using http://forum.xda-developers.com/moto-g-2014/general/simplified-modifying-boot-img-t3317605
everything went as expected, but by unlocking it wiped all userdata, so I wanted to re-encrypt the phone (and the external SD especially). But now, encryption fails, telling me "encryption fails, you have to reset your phone" each time I start the encryption, ending in a userdata-wipe.
So I thought about going back to stock fw.
After locking the bootloader and applying stock 6.0 FW, I tried again to encrypt the phone, but I am still unable to do so.
Can someone help me giving some suggestions, how I can fix that behavior and (mainly) how to get some errors/debug shown?
When selecting "encrypt now", the green android symbol with black background is shown for 5seconds, then the phone reboots, shows the bootscreen with the M, then it restarts again (after ~30minute) and shows after another 20seconds the message that something went wrong encrypting.

Ok it seems that I found out the problem in my case by myself.
Instead of using mfastboot.exe -w to delete the data and cache partition, I used recovery mode to delete userdata. I did it twice, since the first run, returns some errors.
After reset, I started the phone and got the fresh-install screen. I skipped mobile and wifi networking and did not entered google account details. Then I restarted the phone and waited for ~5minutes and tried to encrypt - everything works. Everytime I started encryption without waiting for some time it failed.
I hope I can save someone else some time, since factory reset takes ~15minutes each time you do it.

Strange Encryption behavior

Hello, i have a strange behavior regarding the encryption on the oneplus 3t.
Since i got this phone i always had encryption enabled and with every restart i got a prompt mid boot process to enter the encryption password.
Same behavior when booting into TWRP, yes, my phone is rooted and i'm running freedom os with magisk su so i can bypass safetynet.
For some last days i stopped getting the password prompt, the phone booted right into the os, i figured when choosing the reboot option it only soft resetted and still had the keys in memory.
Tried turning it off and on again, still no password, tried booting into TWRP, and no password.
When going into the safety options it says that the phone is encrypted.
Haven't installed any new applications lately, but i started using the second sim slot since i was on a trip, removed the sim and still no password.
I'll try and wipe and reinstall since new version of freedom os is out.
Does anyone experienced the same thing?
Maybe it's some kind of malware?
Was running Freedom os 2.8 that is based on 4.1.3 but will soon be running Freedom os 2.9.

Beta 10 to 4.1.6 Rollback Nightmare. Help!

When I tried reinstalling Stable OxygenOS 4.1.6, the phone locks up upon install and setup screen. This goes for previous OS versions, as well. It takes force quits, restarts, and numerous install attempts and the phone still locks up. I tried stock recovery, old and new TWRP versions, all of which are clean installs, Nothing. LineageOS and other Hydrogen based roms still lock up, either at the setup screen, or when I try and activate developer options. Every Rom I tried after activating developer options, it doesn't leave the gear icon in the menu, either. It takes a restart (force quit) for it to show up. Also, WiFi doesn't work. Sometimes when I try and install OxygenOS either by sideloading, or through TWRP, the phone locks up at the wifi setup screen. This goes for every version of OxygenOS I tried. Your advice is appreciated. Thanks.

I had some problems last night while switching back and forth between Beta and stable. I could try to help but I'm not a guru at this, so wait for confirmation if you are not sure.
First I think you need the right TWRP version. 3.1.1-2 is the latest one, but I'm using 3.0.4-1 (flashed stableOOS with it) and everything is back to normal for me.
Try a clean flash of stableOOS. TWRP > Advanced wipe, select dalvik,cache,data,system and swipe.
Then install the OS. Don't reboot yet, and instead boot into recovery after going back. I read that this ensures you keep TWRP.
It may say No OS installed, but go ahead. Then boot into system again. This worked for me and I restored my backups

I just went from beta 10 to 4.1.6 and have no issues at all.
I followed the basic procedure, in TWRP (recommend to use the latest bluesparks one from his kernel thread - just TWRP no need for his kernel), I did a factory reset, (in TWRP just swipe to Factory reset from the WIPE screen where it says 'Most of the time this is all you need'), its correct nothing else needed, then flashed the full v416 file, then flashed Magisk 13.2, rebooted to system, that was all. TWRP was not lost with this method.
System booted to stable v4.1.6 and no issues.

Check what format are your partitions fornatted in. Make sure they are f2fs. Otherwise try the debrick tutorial. It helped me fix a lot of bugs on my 3T.

I tried all of the above, and I'm certain under the right circumstances, your advice would work. In the end, I used the unbrick tool which brought it back to it's original locked state, and I'm still running into issues. I wonder if there's a hardware issue somewhere that was the result of using Beta. The OS boots up and I'm finally able to access developer options, but no WiFi and the phone still refuses to restart or power off unless I do a hard shutdown. I've never seen anything like it. Numerous ROMS, recoveries, and sideload installs using the One Plus Recovery, and it still doesn't work.
Thanks for everyone's input, but I feel like this phone is done.

LineageOS 16 to 18.1 resulted in boot loop or unstable behavior; no WiFi or cellular

I upgraded my Moto X4 from LineageOS 16 to the latest 18.1 build by following these instructions. When I rebooted, the phone was stuck on the boot screen with the green circles. I installed the latest version of TWRP and reinstalled the 18.1 image. Sometimes the phone stay in the loop, but usually it was get the the home screen.
However, it still doesn't work. Sometimes the phone reboots shortly after arriving on the home screen. Sometimes it has WiFi turned off and is on airplane mode. In that case, it seems stable until I turn either of those on, and then it reboots. Running an app might also cause it to reboot. The touchpad buttons at the bottom of the phone also become unresponsive.
I tried installing the latest LineageOS 17.1 build, and that just stays in the boot loop too.
Like a first rate noob, I didn't make a backup of the v16 installation before the upgrade. I have a backup of the OEM rom that I made in 2019, when I first put LineageOS on the phone, but I'm worried about erasing my data.
I appreciate all suggestions. One thing I considered doing, but have not figured out how to do, is to look through the logs to find out what is making the phone reboot from the home screen. "adb logcat" might be the answer.
Another question I have: Does each "slot" have its own recovery? I think that's the case, and I think I have the newest TWRP in both slots.

kalbfled said:
I upgraded my Moto X4 from LineageOS 16 to the latest 18.1 build by following these instructions. When I rebooted, the phone was stuck on the boot screen with the green circles. I installed the latest version of TWRP and reinstalled the 18.1 image. Sometimes the phone stay in the loop, but usually it was get the the home screen.
However, it still doesn't work. Sometimes the phone reboots shortly after arriving on the home screen. Sometimes it has WiFi turned off and is on airplane mode. In that case, it seems stable until I turn either of those on, and then it reboots. Running an app might also cause it to reboot. The touchpad buttons at the bottom of the phone also become unresponsive.
I tried installing the latest LineageOS 17.1 build, and that just stays in the boot loop too.
Like a first rate noob, I didn't make a backup of the v16 installation before the upgrade. I have a backup of the OEM rom that I made in 2019, when I first put LineageOS on the phone, but I'm worried about erasing my data.
I appreciate all suggestions. One thing I considered doing, but have not figured out how to do, is to look through the logs to find out what is making the phone reboot from the home screen. "adb logcat" might be the answer.
Another question I have: Does each "slot" have its own recovery? I think that's the case, and I think I have the newest TWRP in both slots.
Click to expand...
Click to collapse
Hello,
I have come here from.
Actually upgrading from an older Android to newer Android is almost never very smooth, and hence should be avoided if possible, but if you have done so and currently experiencing boot or device operation problems, then:
1: Open TWRP, and go to 'Wipe'.
2: check ONLY 'cache' and "Dalvik / ART Cache", and uncheck the rest, then proceed by swiping the trigger which reads "Swipe to Wipe".
3: Wait for 3 seconds.
4: Reboot to system.
5: If the system boots now, then reply with written "Solved", else the issue.
Thank you...

Thank you very much for replying. I followed your instructions for both slots on my phone, but neither shows any improvement. The 18.1 slot continues to get to the home screen and then reboot as soon as I try to do anything (or randomly before that); the 17.1 slot continues not to get past the green circles screen.
Although the Lineage website no longer hosts builds for v16, I was able to download the last signed v16 nightly build from Archive.org and to verify the signature using these instructions. I booted to TWRP sideload mode and ran `adb sideload <v16 build>`. Now that isn't working either! It seems to loop at the circles screen for a while. Then it gives me a message about being unable to boot and asks if I want to do a factory reset. I did not try a factor reset because I think that erases my data.

I resolved the issue by following the full installation instruction for Moto X4. I tried it with versions 18 and 17 first, but the rebooting problem continued. Fortunately, it worked this time when I put version 16 on the phone again.

I have version 16 on mine and I don't have the will to try to update. Migrating from version 15 to 16 the first time gave me issues and troubleshooting woes and I don't wish to repeat that process. Pie works good enough for me, F it. Just wish it would receive security updates still, but the devs are done with it.

[Question] Pixel Experience 12+ on my Redmi 9 is rebooting on lock screen.

Hello, it's my first post on this forum so sorry If I made this thread in the wrong place.
I have been trying to install PE 12 (plus edition) using official PE site (https://download.pixelexperience.org/lava).
After many attempts to do so, I ended up installing different TWRP recovery images and wiping everything from my phone.
Then I've tried installing official recovery image from site and I've installed ROM by adb sideload and it worked.
First boot wasn't a problem, but from start phone would sometimes crash when attempting to turn it on (or, attempting to unlock lock screen. I can write my PIN, but then rebooting happens). When it wouldn't crash (it's not happening every time) everything would be working as long as I don't turn it off. I don't know what is causing that behaviour.
Would reinstallation help or is it hardware problem (not enough RAM etc.), or lack of swap partition?
PS: Updating every app on phone doesn't help, as well as removing lock screen (no PIN etc.).
Update: I have installed different ROM from sourceforge dedicated to my phone version (galahad). It is android 11. Works 100% fine.