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
.
Related
Hi;
So i recently installed CyanogenMod 13.0 on to my Samsung S4 GT-I9505 using the first download link on:
https://download.cyanogenmod.org/?device=jfltexx --> cm-13.0-20160102-NIGHTLY-jfltexx.zip
That all installed fine, but i wanted to get the Google apps installed aswell, which is where i am having some issues.
I have been trying to install the following package:
http://opengapps.org/?api=6.0&variant=nano
but have also tried to install quite a few others as well, and all have exactly the same issue. Basically after the apps have been installed and i boot the device up, i get various error messages like:
unfortunately, Setup Wizard has stopped
unfortunately, google play services has stopped
Any help on fixing this would be much appreciated, as nothing seems to download from the play store thats included in Cyanogen, they just say "your download will begin shortly" but never does.
Thanks in advance
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
audacityandrouge said:
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
Click to expand...
Click to collapse
Thanks for the reply, i gave that a try and it seems to be stuck on a loop now with "installing app # of 22" . it completes the installation and then reboots, after about 5 minutes on the Cyanogen boot screen, it goes back to installing apps again.
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
audacityandrouge said:
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
Click to expand...
Click to collapse
Yeah, i did. Tried it multiple times now
That's about the limit of my ability right there, hopefully someone with more experience than me can point you in the right direction. Good luck.
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
es0tericcha0s said:
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
Click to expand...
Click to collapse
Ive tried that multiple times using twrp (i always wipe everything before i flash CM13 and gapps), i still get the exact same issue. The second the phone boots, i get all these "unfortunately ******** has stopped".
Perhaps try installing 12.1 with gapps, get it all updated then upgrade to 13. I did the accidental upgrade to 13 but have had no issues whatsoever.
Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
I normally flash a new rom in this order if the new rom is in my Download folder:
- TWRP Wipe advanced, tick System,Data,Cache.
-Back
-Install, go to sdcard/Download
-Select rom.zip
-after finish go back
-Select gapps64.zip
-after finish installing I press clean Dalvik and Cache
- Reboot system.
Wait a while and install as new device.
This should work.
With a normal update of a rom I simply install the update without wiping my system.
johhnyhotrocks said:
Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
Click to expand...
Click to collapse
If you're using opengapps, they are having trouble booting on a fresh install on slim and LineageOS. Try an older build of slim or lineage, boot up and set up, then update to newest build.
Solution
johhnyhotrocks said:
Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
Click to expand...
Click to collapse
I had the same issue with my NEXUS 9 wifi, but this solution mentioned here worked for me!
I am using:
lineage-14.1-20180920-nightly-flounder-signed
open_gapps-arm64-7.1-mini-20180923
Vendor Version: n9f27m
wanderweg you are my hero!
Mods make this stickie in the first posts....
If the system doesn't start after flashing with gapps just do this...
After flashing, mount system from TWRP, go to the "Advanced" tab, click on Terminal and type the following command:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Just killed 2 days trying to figure it out and that's all it was.
P.S. Maybe roms can be updated to include the fix?
MOCKBA said:
wanderweg you are my hero!
Mods make this stickie in the first posts....
If the system doesn't start after flashing with gapps just do this...
After flashing, mount system from TWRP, go to the "Advanced" tab, click on Terminal and type the following command:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Just killed 2 days trying to figure it out and that's all it was.
P.S. Maybe roms can be updated to include the fix?
Click to expand...
Click to collapse
It's a gapps issue not a ROM issue. Every now and then the setup wizard is weird in opengapps.
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?
HI
after some wrong uninstalling service from my clean miui 9.6.25 global
i tried to restore rom by usual way from twrp.
but when done the pocophono never run to boot only logo screen(waiting atleast 15min which ofcourse is not normal).
has anyone faced that?
do i need to flash ENCRYPT disabler again after restore?:silly:
Come on......!!! cant be only me???!!!heheheh
TWRP is for lifesaver not to trouble as all know
I've found this too.
Encryption shouldn't matter.
Try restoring only one partition at a time to see which is causing the error. I think it's Userdata in my case, but Userdata Image may work.
I've not bothered to investigate why this happens yet.
ok
i will try mate.
thank u!
i will come backup for update
My phone had latest Miui9, then I installed Twrp and backup the Miui9 rom by Twrp.
then I flashed Miui 10, back up it with TWRP.
Then try to restore my Miui 9 Twrp backup, after done the phone boot to Fast boot mode only.
Even tried restore Miui10 still it would boot to fastboot mode only. Flash new rom and reboot it will ask for encryption password.
The fix is need to format data (Wipe > Format data > type yes, after flashed the rom), and reboot it should work.
Yeah, restoring MIUI backups is a real pain... Because of that, I always flash the ROM zip file first, then restore the data only, reboot and it works.
mario123m said:
Yeah, restoring MIUI backups is a real pain... Because of that, I always flash the ROM zip file first, then restore the data only, reboot and it works.
Click to expand...
Click to collapse
so steps:
1st flashing miui rom.zip
2nd restore files with twrp backup file?
and all works perfect????
data? system? image system? which please
first time i hear this method...hehehe
pin\password asking after?
miui account find device e.t.c?
I switch ROMs pretty often and MIUI never booted after restoring.
There's a simple workaround: just reflash MIUI whenever you restored.
emmanuelo7 said:
so steps:
1st flashing miui rom.zip
2nd restore files with twrp backup file?
and all works perfect????
data? system? image system? which please
first time i hear this method...hehehe
pin\password asking after?
miui account find device e.t.c?
Click to expand...
Click to collapse
Install MIUI zip (with the same system you backed up), then go to restore and just restore data and nothing else. If you used Magisk before, flash it too after restoring. Then reboot. I don't know about Global ROMs as I always use Xiaomi.eu but I think it should work the same way. Oh, and never backup data with a password/pin/fingerprint set because it will not recognise it after reboot and you will have to use TWRP to delete locksettings from /data/system which adds unnecessary steps to this tedious procedure. Good luck.
thank u bro!
mario123m said:
Install MIUI zip (with the same system you backed up), then go to restore and just restore data and nothing else. If you used Magisk before, flash it too after restoring. Then reboot. I don't know about Global ROMs as I always use Xiaomi.eu but I think it should work the same way. Oh, and never backup data with a password/pin/fingerprint set because it will not recognise it after reboot and you will have to use TWRP to delete locksettings from /data/system which adds unnecessary steps to this tedious procedure. Good luck.
Click to expand...
Click to collapse
Hi, I'm having the same issue.
I get a PIN code. How can I bypass it?
How can I avoid it in the future?
Thanks!
if password promt during boot u have no option other than format data
only lockscreen can be deleted via twrp
I had the same problem in my pocophone and solved it like this:
1. Advanced wipe all data except Internal storage (so you do not lose your data)
1.1 Flash or boot twrp again
2. Install the official rom using the way you know
3. Starts android the first time but without doing the initial configuration of android (I'm not sure if this is necessary but it costs nothing to do it)
4. Through twrp, restores the data but only the options Boot and Data, dont select System
And that's it. I hope it works for you.
I was trying different combinations and I realized that it is the system folder that has a problem when you make the restoring, don't know why.
I was using pocophone with MIUI 10.2.2
mario123m said:
Install MIUI zip (with the same system you backed up), then go to restore and just restore data and nothing else. If you used Magisk before, flash it too after restoring. Then reboot. I don't know about Global ROMs as I always use Xiaomi.eu but I think it should work the same way. Oh, and never backup data with a password/pin/fingerprint set because it will not recognise it after reboot and you will have to use TWRP to delete locksettings from /data/system which adds unnecessary steps to this tedious procedure. Good luck.
Click to expand...
Click to collapse
Thanks a lot!
Hi there,
I've reinstalled my Lineage OS in May and have recently installed the latest upgrade. Today, I was using my phone just fine before a subway trip, then after it was stuck in a boot loop (lineage OS circles). My guess is that I accidentally restarted it.
What is the procedure to repair the phone without loosing the data?
I tried:
- Reinstalling recovery, lineage, MindTheGApps in that order
- Wiping the cache partition, wiping the dalvik cache
So far I have not seen any progress. Am I missing something?
I really want to avoid wiping my data as I just set the phone up two months ago.
Did you try dirty flashing the ROM zip by only Wiping the System partition but not Data? I use NikGApps and its not necessary to reflash it during a dirty flash but I flash the latest GApps build in any case. I pretty much use crDroid exclusively and dirty flashing works reliably. Not encrypted though.
Ok, so I did the following
Action -- What I think it does
Install TWRP recovery via fastboot -- to selectively wipe partitions
Wipe System -- to remove system files from the previous update
Wipe Cache & Dalvik cache -- to remove cache files that have previously been written on startup
Install lineage os -- to install a clean OS
Install MindTheGapps -- to install the Google subsystem
System reboot
Files used:
twrp-3.6.2_9-0-beryllium.img
lineage-19.1-20220618-nightly-beryllium-signed.zip
MindTheGapps-12.1.0-arm64-20220605_112439.zip
Again with:
lineage-19.1-20220716-recovery-beryllium.img
lineage-19.1-20220716-nightly-beryllium-signed.zip
MindTheGapps-12.1.0-arm64-20220605_112439.zip
Still caught in the boot loop.
I feel a bit lost here.
I did nothing special. Just installed the newest Lineage OS from the GUI and then apparently accidentally restarted it (or it crashed). This should be a common use case. I would expect there to be a guide or wiki that explains and solves this. But from my own Google searches I mostly see recommendations in the line of try wiping and reinstalling.
I am pretty sure, my data is encrypted. Does this mean I am screwed? (i.e., all not backup-ed data is lost?) Was flashing a new Lineage OS & GApps the step that doomed me?
Before the bootloop did you have TWRP installed instead of LOS recovery? Flashing the OTA update via TWRP can be problematic.
I had recovery installed. I reinstalled the Image from Lineage recovery. After this didn't work I tried it with TWRP.
Did you try flashing the build you were using before the bootloop occurred? No clue otherwise how to resolve this. Hopefully someone else can help you out.
Yes, first I tried installing only MindTheGapps, then lineageOS (last version I had) + MindTheGapps. And I tried a number of recent releases.
I also tried the most recent version and now I cannot install earlier versions anymore: "Current SPL: 2022-07-05 Target SPL: 2022-06-05 this is considered a downgrade".
I gave up. Reinstalled everything. Lost a ton of messages for which I did not have the right backup.
Depressing. Nothing I did was special. So I can expect this to happen anytime. I will improve my backup. But still, in the long term I need to find something that is reliable.
Thanks @amn1987 for the suggestions.
Use Swift Backup for backing up apps and their data, SMS, call logs etc. on a regular basis. Works very reliably. You can backup messages to Google Drive as well. Probably can schedule the backups.