Related
Hi,
I've got a RN3, snapdragon version, 3GB of RAM. Unlocked bootloader. TWRP 3.0.2-2
I've been using CM for a while, android 6.0.1 and I've been trying now for a few days to move to Nougat.
I've tried different roms: NitrogenOS, lineage OS, resurrectionRemix.
I've also tried flashing different versions os miui firmware: 7.3.16, 7.3.23, 7.3.30
So, after all that, the result is always the same. The flashing seems successful, the phone boots but then I cannot go through the initial setup screen.
I choose the wifi network but when I try to enter the password, the screen resets every 5 seconds or so. I know it's resetting/reloading because the password I've typed so far goes away and I have to start again. It happens every few seconds and I cannot setup wifi properly.
I tried changing the password to aaaaaaaaaa to make it easy and quick to setup. Once I go through that, it stays for ever in the next screen "checking information" (or something like that). Again, it seems to be reloading this screen every few seconds.
is there something am I missing? Maybe I'm flashing firmware/rom in the wrong order?
I'm back with android 6.0.1 now and the phone works fine.
thanks in advance for your help.
Flash Kenzo Firmware , Rom & Nougat Gapps not MM , next reboot system
Sent from my Redmi Note 3 using Tapatalk
VaibhavKumar07 said:
Flash Kenzo Firmware , Rom & Nougat Gapps not MM , next reboot system
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
thanks @VaibhavKumar07
so, this is exactly what I've tried a few times.
what about wipes and all that stuff?
I don't mind doing a clean install and reinstalling/reconfiguring everything.
I've tried different things, but for example what is mentioned in the thread "CM13/14/14.1/AOSP N firmware for KENZO/KATE [VoLTE][12.1.2017]"
-Reboot to TWRP recovery
-Flash firmware
-Factory reset (data, cache and dalvik-cache)
-Flash your favorite Marshmallow or Nougat ROM
-Reboot your phone
is that still valid for the nightly builds from April 2017?
On Cm firmwares I was unable to get VoLTE working so recommend you to flash Miui beta firmware search in SD Rom or guide section you'll find em if not message me again .
Regarding procedure :
- First flash Twrp 3.1.1.0 from official site cuz that's latest
- Next go & wipe check everything except SD card & OTG
- Flash Firmware
- Flash Rom
- Flash Gapps Arm *64 Android N from Open apps
- Flash Any Add-ons if required like kernel or Sound enhancement mods ( optional )
- Clean cache/dalvik cache
- Reboot
Mention the Rom you're flashing!
Sent from my Redmi Note 3 using Tapatalk
So, I did all that several times, except for flashing the latest twrp version. I'm on 3.0.2-2 because it flashes ok but when rebooting it's back to 3.0.2-2. I'm doing this from fastboot. I'm not only loading, but flushing. It seems to be ok but then it's gone after reboot.
Anyway, I've tried this procedure with 3 different roms:
ResurrectionRemix
LineageOS
Nitrogen OS
flashing latest versions for each rom.
Could the twrp not updating properly have something to do with this issue? does the latest version fix some flashing issues with Nougat?
the thing is that if flashed and boots, but it doesn't run properly as mentioned.
I will try to get latest twrp version working and report back if that makes any difference.
VaibhavKumar07 said:
On Cm firmwares I was unable to get VoLTE working so recommend you to flash Miui beta firmware search in SD Rom or guide section you'll find em if not message me again .
Regarding procedure :
- First flash Twrp 3.1.1.0 from official site cuz that's latest
- Next go & wipe check everything except SD card & OTG
- Flash Firmware
- Flash Rom
- Flash Gapps Arm *64 Android N from Open apps
- Flash Any Add-ons if required like kernel or Sound enhancement mods ( optional )
- Clean cache/dalvik cache
- Reboot
Mention the Rom you're flashing!
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
so, still fighting with this.
i managed to upgrade to twrp 3.1.0-1, all good.
however, i still have the same problem with the initial screen, it keeps reloading every few seconds and can't finish the setup or even skip it.
i've tried different versions of firmware. I've also tried flashing the latest miui rom (dev and global) and then a custom rom.
i've tried different builds (different dates) of the following roms:
nitrogenOS
lineageOS
aospextended
mokee
resurrectionremix
exact same behaviour with all these roms.
what am I doing wrong? i'm on marshmallow and everything works fine, but stuck moving to nougat. do I have to flash something not mentioned already to move from custom MM to custom Nougat?
txutxe said:
so, still fighting with this.
i managed to upgrade to twrp 3.1.0-1, all good.
however, i still have the same problem with the initial screen, it keeps reloading every few seconds and can't finish the setup or even skip it.
i've tried different versions of firmware. I've also tried flashing the latest miui rom (dev and global) and then a custom rom.
i've tried different builds (different dates) of the following roms:
nitrogenOS
lineageOS
aospextended
mokee
resurrectionremix
exact same behaviour with all these roms.
what am I doing wrong? i'm on marshmallow and everything works fine, but stuck moving to nougat. do I have to flash something not mentioned already to move from custom MM to custom Nougat?
Click to expand...
Click to collapse
Try this once (Clean) :
Flash Nitrogen
Reboot
Flash gapps and firmware.
Hope it may work for you.
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
gordonthegopher said:
Formatting /data in TWRP uses up all the blocks, but encryption from Lineage needs 16kb of free space at the end of the partition to store the headers.
Click to expand...
Click to collapse
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Hi guys,
I'm kind of stuck right now because I cannot encrypt my phone anymore and I don't know why. I got my phone last year and installed LOS 14.1 right away. For security reasons I also encrypted it - without any issues whatsoever. When LOS 15.1 came out, I upgraded my phone, with encryption still working. A couple of days back for some reason I decided to do a factory reset. Obviously, the device wasn't encrypted anymore after the reset. I then installed the new nightly of LOS (20180807) and tried to encrypt my phone once again. When I select "Encrypt phone", I need to enter my PIN, the phone restarts and reboots without encryption being started.
What I've done so far:
I've flashed two different TWRP versions: 3.2.3.0 and a customized one (https://forum.xda-developers.com/re...other-development/rom-lineageos-15-0-t3690465).
I've clean installed different LOS versions (unofficial LOS 14.1 and LOS 15.1 starting from the 20180710 release)
I've clean installed Omnirom (current release and a release from 20180107).
I've even flashed MIUI 9 and reinstalled LOS thereafter because some guy in the above mentioned LOS thread wrote, that this did the trick for him.
I've disabled WI-FI and mobile data before trying to encrypt my phone, because I found a blog article stating that this might help.
Nothing helped. The phone just reboots and stays unencrypted.
Do you guys have any additional hints or ideas how I can manage to encrypt my phone once again? Could another TWRP version do the trick? Is TWRP even involved in any kind when it comes to encryption of the OS? Do you think another ROM could be helpful?
Click to expand...
Click to collapse
Try orangewolf recovery ....
Sent from my Redmi Note 4 using Tapatalk
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
shakil002 said:
Try orangewolf recovery ....
Click to expand...
Click to collapse
Thanks for the advice. But I'm afraid it didn't help
CanBostanci said:
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
Click to expand...
Click to collapse
That's the most ****ed up part. For some people it does work, for some not.
There surely must be some ridiculous small detail we're not getting. Like disabling WI-FI while Bluetooth is enabled.
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
parkbank said:
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
Click to expand...
Click to collapse
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
CanBostanci said:
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
Click to expand...
Click to collapse
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
parkbank said:
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
Click to expand...
Click to collapse
I'm looking forward to hear the results. I'm about to become insane because of this encryption issue.
I've flashed both the dev and stable firmware found in this thread. No success
By flashing I mean factory reset, flashing the firmware and then installing LOS. I noticed, that flashing a new firmware while a ROM is still installed leads to some random ****ups.
After a couple of days of flashing, factory resetting, re-flashing, reading and a lot of cursing I finally found a working solution. I've added the fix to my initial post. Hopefully this helps
I was looking for solutions for quite a while and nothing else worked but did this and my device is encrypted again.
Thank you!
parkbank said:
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Click to expand...
Click to collapse
You have save my day "my MIDO" hehehehe
After the 1st PIE Rom the encryption was broken.
Your Step by Step save this and now Syberia 9 was able to encrypt with success :good:
Thank you one more time for sharing.
Thx!
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
Orangefox worked
is there any plan to fix twrp itself?? thx
Thank you. It worked for me to get Havoc OS 9.0 with hardware encryption on my Redmi Note 3 SE.
I bypassed unlocking the bootloader by doing this. Then I installed TWRP 3.1.0.0 from the recovery, did the reset and everything as instructed here, updated it to 3.3.1.0, rebooted, then flashed the Pie ROM and latest gapps without any further wiping.
I use the first link, I've modified the partition size -> did the trick wihtout formating nor loosing datas
Great, thank-You.
Hi, I want to ask, what is this encryption features you been using? can u tell me?
Recently I have been having issues with custom roms where features are either being overwritten or possibly data wipes in recovery are not actually happening. Example Havoc OS 2.3 has call recording feature but never has the feature in settings of the dialer. I always flash open gapps nano and this has always only ever enabled dialer framework for Google contacts restore. I have tried this on every version of recovery available TWRP Unofficial, Official, OrangeFox, and RedFox. In the past issues like this before all this encryption you could just wipe all internal storage and have no worries of remnants. Can you still do this?
Personally I like OrangeFox because DM Verity and Disable Force Encryption happen automatically. But certain roms like DOT OS won't even boot because of reboot to recovery trying to decrypt data partition. The password does not exist because I have already wiped and formatted data partition. The only way out of this is to flash Miui EU stable or Global. Only question is why and how could this happen? (Note: I cannot still get DOT OS to fully boot clean flash at all).
Lastly If vendor firmware exists on it's own partition and not part of system partition, TWRP advanced wipe does not include vendor, why the need to flash it before every Rom if there is no need to update it? After all if dev builds a Rom on 9.3.25 vendor and you have that installed that will be the best vendor firmware to keep because the entire Rom is built/updated on it....correct?
I installed lineageos 15.1 oreo on my nexus 9. I recently restored a backup through twrp on it. Everything was restored except for data on an email client. I cant access mail. When I try to, I get a refresh icon (see image link below). I tried reinstalling, clearing cache and data but that doesnt work. Is there a file I need to tweak for my nexus to be able to access mail again?
deloj said:
I installed lineageos 15.1 oreo on my nexus 9. I recently restored a backup through twrp on it. Everything was restored except for data on an email client. I cant access mail. When I try to, I get a refresh icon (see image link below). I tried reinstalling, clearing cache and data but that doesnt work. Is there a file I need to tweak for my nexus to be able to access mail again?
Click to expand...
Click to collapse
Restored a backup of what? Data is no compatible across roms. Lineage 15 is also not stable. 14.1 is recommended.
deloj said:
I installed lineageos 15.1 oreo on my nexus 9. I recently restored a backup through twrp on it. Everything was restored except for data on an email client. I cant access mail. When I try to, I get a refresh icon (see image link below). I tried reinstalling, clearing cache and data but that doesnt work. Is there a file I need to tweak for my nexus to be able to access mail again?
Click to expand...
Click to collapse
madbat99 said:
Restored a backup of what? Data is no compatible across roms. Lineage 15 is also not stable. 14.1 is recommended.
Click to expand...
Click to collapse
I restored a backup of my nexus 9 as in nandroid. If you say data isnt compatible across roms. But I was able to make a nandroid of 2 of my phones that I restored successfully before.
You also suggested 14.1 for a stable rom. But if I install it and make a nandroid then restore if something goes wrong will I get the same issue I'm having now?
Since I got lineagos 15.1 how do I install 14.1?
.
deloj said:
I restored a backup of my nexus 9 as in nandroid. If you say data isnt compatible across roms. But I was able to make a nandroid of 2 of my phones that I restored successfully before.
You also suggested 14.1 for a stable rom. But if I install it and make a nandroid then restore if something goes wrong will I get the same issue I'm having now?
Since I got lineagos 15.1 how do I install 14.1?
.
Click to expand...
Click to collapse
When I said backup of what, I meant what rom is it a backup of.
I meant data from 1 ROM is not always going to restore correctly on another rom. If it's a backup of the same ROM, it should restore. If it's from another ROM, well, that's hit or miss. And usually not a good idea.
I always start fresh. Maybe restore some apps that I backed up previously with titanium backup. But not usually the whole data partition.
madbat99 said:
When I said backup of what, I meant what rom is it a backup of.
I meant data from 1 ROM is not always going to restore correctly on another rom. If it's a backup of the same ROM, it should restore. If it's from another ROM, well, that's hit or miss. And usually not a good idea.
I always start fresh. Maybe restore some apps that I backed up previously with titanium backup. But not usually the whole data partition.
Click to expand...
Click to collapse
Hi madbat,
I tried to downgrade/ install lineagos 14.1 Nougat on my nexus 9 from lineagos 15.1 Oreo. But after I reboot to system, the word google stays stuck on screen. It doesn’t boot to the rom. These are the steps I took and the zips with it:
1) First wipe : TWRP > swipe to factory reset > adv.wipe cache/data/system/dalvik > Format data > Reboot to Recovery
2) TWRP > Install > Slim Rom 7.12 / open_gapps-arm64-7.1-nano-20190529.zip / > Reboot on Recovery >
3) TWRP > Install > dm verity FED > SR5-SuperSU-v2.82-SR5-20171001224502.zip > wipe cache & dalvik (ONLY!) & Reboot system
I even tried flashing in this order:
slim rom > fire ice custom kernel > dm verity FED zip > SR5-SuperSU-v2.82-SR5-20171001224502.zip > gapps
These are the files I’m trying to install:
Slim-flounder-7.1.2.build.2.0-STABLE-20180124-0018.zip
open_gapps-arm64-7.1-nano-20190529.zip
FIRE-ICE N K10.7 06-01-2018 21-31-18.zip
Disable_Dm-Verity_ForceEncrypt_04.03.19.zip
SR5-SuperSU-v2.82-SR5-20171001224502.zip
What am I doing wrong??????
deloj said:
Hi madbat,
I tried to downgrade/ install lineagos 14.1 Nougat on my nexus 9 from lineagos 15.1 Oreo. But after I reboot to system, the word google stays stuck on screen. It doesn’t boot to the rom. These are the steps I took and the zips with it:
1) First wipe : TWRP > swipe to factory reset > adv.wipe cache/data/system/dalvik > Format data > Reboot to Recovery
2) TWRP > Install > Slim Rom 7.12 / open_gapps-arm64-7.1-nano-20190529.zip / > Reboot on Recovery >
3) TWRP > Install > dm verity FED > SR5-SuperSU-v2.82-SR5-20171001224502.zip > wipe cache & dalvik (ONLY!) & Reboot system
I even tried flashing in this order:
slim rom > fire ice custom kernel > dm verity FED zip > SR5-SuperSU-v2.82-SR5-20171001224502.zip > gapps
These are the files I’m trying to install:
Slim-flounder-7.1.2.build.2.0-STABLE-20180124-0018.zip
open_gapps-arm64-7.1-nano-20190529.zip
FIRE-ICE N K10.7 06-01-2018 21-31-18.zip
Disable_Dm-Verity_ForceEncrypt_04.03.19.zip
SR5-SuperSU-v2.82-SR5-20171001224502.zip
What am I doing wrong??????
Click to expand...
Click to collapse
Try wiping system too. And if it gets stuck, I usually force a reboot by holding power till it reboots. Usually works.
Wait.... SuperSU? There's your problem. Magisk dude.
You see it says 2017? Old.
Why not the latest lineage and magisk?
madbat99 said:
Try wiping system too. And if it gets stuck, I usually force a reboot by holding power till it reboots. Usually works.
Wait.... SuperSU? There's your problem. Magisk dude.
You see it says 2017? Old.
Why not the latest lineage and magisk?
Click to expand...
Click to collapse
You said supersu is my problem. But I tried flashing with only slim rom and gapps, no supersu. Still doesnt work.
Also I'm confused by your last question about why I should install the latest lineage. The latest official lineage is 15.1 and you know I'm having an issue with it. Thats why I want to downgrade to lineage 14.1.
I read that the way to downgrade from lineageos 15.1 to lineagos 14.2 is through ADB. But I'm not sure. What do you suggest?
deloj said:
You said supersu is my problem. But I tried flashing with only slim rom and gapps, no supersu. Still doesnt work.
Also I'm confused by your last question about why I should install the latest lineage. The latest official lineage is 15.1 and you know I'm having an issue with it. Thats why I want to downgrade to lineage 14.1.
I read that the way to downgrade from lineageos 15.1 to lineagos 14.2 is through ADB. But I'm not sure. What do you suggest?
Click to expand...
Click to collapse
Official lineage 15.1? Where? I meant 14.1. that's the last official. Still being built unofficially by the official maintainer. In the official thread.
Running it on my Nexus 9. No problems. No issues. Security patches.
I just don't have the update addiction on my n9. My Moto phone has official pie. So I'm good. My tablet is for media consumption.
I have no idea what is happening with your email. No logs, no nothing. I don't even know what email client you're using. Did you log in to it? Instead of restoring a backup.
All sounds flawed. Experimental ROM, data restore, no original log in.... All suspect.
I'm sure you know why it all causes problems, but don't want to start over.
Sometimes, ya just gotta start over. Flashy flashy, kaboom. We all been there. Data restore is an imperfect process. Sometimes you get to the end of your luck and just have to start over.
madbat99 said:
Official lineage 15.1? Where? I meant 14.1. that's the last official. Still being built unofficially by the official maintainer. In the official thread.
Running it on my Nexus 9. No problems. No issues. Security patches.
I just don't have the update addiction on my n9. My Moto phone has official pie. So I'm good. My tablet is for media consumption.
I have no idea what is happening with your email. No logs, no nothing. I don't even know what email client you're using. Did you log in to it? Instead of restoring a backup.
All sounds flawed. Experimental ROM, data restore, no original log in.... All suspect.
I'm sure you know why it all causes problems, but don't want to start over.
Sometimes, ya just gotta start over. Flashy flashy, kaboom. We all been there. Data restore is an imperfect process. Sometimes you get to the end of your luck and just have to start over.
Click to expand...
Click to collapse
Hi madbat,
I answered your question in this link. Please read it bro. Thanks man:
https://forum.xda-developers.com/ne...e-lineagos-15-1-to-14-1-t3934751#post79642010
.
Hi guys, I need your help.
I've tried to update the rom with the latest beta Omnirom (30/06), directly from TWRP.
All the steps I followed, hoping it's usefull:
- removed the PIN from the system;
- made a full backup (from TWRP);
- installad latest vendor;
- installed latest Omnirom beta;
- wipe caches;
- reboot.
The phone is in bootloop; ufortunately, plus in TWRP the touchscreen is unresponsive and I have to reboot until it works.
I tried to flash just the rom beta or to restore the backup, without success.
EDIT: after flashing a older vendor and, again, Omnirom, the phone booted.
I don't know if it's related or not, but now, every app that I open, I see it in rotated horizontally, also if I have disinibited the rotation!
Any idea?
Thanks a lot,
Nic.
Sup3rN1c said:
Hi guys, I need your help.
I've tried to update the rom with the latest beta Omnirom (30/06), directly from TWRP.
All the steps I followed, hoping it's usefull:
- removed the PIN from the system;
- made a full backup (from TWRP);
- installad latest vendor;
- installed latest Omnirom beta;
- wipe caches;
- reboot.
The phone is in bootloop; ufortunately, plus in TWRP the touchscreen is unresponsive and I have to reboot until it works.
I tried to flash just the rom beta or to restore the backup, without success.
EDIT: after flashing a older vendor and, again, Omnirom, the phone booted.
I don't know if it's related or not, but now, every app that I open, I see it in rotated horizontally, also if I have disinibited the rotation!
Any idea?
Thanks a lot,
Nic.
Click to expand...
Click to collapse
I never recommend dirty flashes.
I would say that your problem is more than likely because you didn't wipe the system clean and start fresh.
Since you've already made backups of your data, I would suggest trying these steps:
Boot to TWRP
Format data, type yes to confirm
Go back to wipe / advanced
Select everything except USB and SD card.
Swipe to wipe.
Go back to the main menu.
Reboot to recovery.
Now flash the latest firmware, ROM, gapps
Also flash DFE if you want to disable the encryption.
Wipe cache when done.
Reboot.
Thank you BentMetal.
As you see from the EDIT, I solved the problem flashing a older vendor and the same updated rom.
For the other problem (screen rotation), solved by disabling display setting (auto rotate) and re-enabling again.
Now I just need to remove the touch screen freezing problem... very annoying.
It's a specific issue about a part of Pocophone who use a different touch screen.
Nic.