Database Develop

[Q] Fixed bootloop - Is there anyway to get everything back?

Background info:
Updated Cyanogenmod 12.0 to 12.1 through a nightly update that the OS automatically recommended me do. Upon updating, the phone went into a boot loop. I did a data backup through TWRP and then I wiped the dalvik-cache and cache, but it still bootlooped, so I wiped the data. After wiping the data, the phone booted up just fine. At this point, I'd like to restore my data and I have tried doing so through TWRP, but then it just goes into a bootloop again.
Primary Questions:
Can I restore my data and not get the boot loop? If not, can I go back to Cyanogenmod 12.0 and then restore my data and not get the boot loop? If not, what are my options from here?
Secondary Questions:
What did I do wrong to get the boot loop and how can I prevent this from occurring in the future when updating to a new nightly?

thex2 said:
Background info:
Updated Cyanogenmod 12.0 to 12.1 through a nightly update that the OS automatically recommended me do. Upon updating, the phone went into a boot loop. I did a data backup through TWRP and then I wiped the dalvik-cache and cache, but it still bootlooped, so I wiped the data. After wiping the data, the phone booted up just fine. At this point, I'd like to restore my data and I have tried doing so through TWRP, but then it just goes into a bootloop again.
Primary Questions:
Can I restore my data and not get the boot loop? If not, can I go back to Cyanogenmod 12.0 and then restore my data and not get the boot loop? If not, what are my options from here?
Secondary Questions:
What did I do wrong to get the boot loop and how can I prevent this from occurring in the future when updating to a new nightly?
Click to expand...
Click to collapse
I'm going to answer your second question first, as the second answer shapes the first answer.
Sometimes a ROM needs a wipe before flashing..the reason for this is conflicting data.. Most commonly,.this will happen if going from one ROM to another from a different dev, but can also happen upgrading roms from the same dev.
The conflict will happen due to system settings.. All system settings go in /data/data along with your user app settings. Most settings will go in an sqlite database.
The boot loop problem occurs usually when there is an entry in one or more of these databases that correlates with a setting that no longer exists, or the entry doesn't match the options in a ROM. For example, if your ROM allows you to set screen sleep in 15, 30, 60 seconds only, but your database has your setting set at 45, android doesn't know what to do and boot loops.*
The fix is of course, wiping data.. This is why when restoring using titanium backup on a new ROM, we recommend only restring your user apps and data (using the filters and options) otherwise if you restore system apps and data you're restoring the problem.
The first question, you can restore app a from a nandroid backup using titanium. There is an option in preferences.
*please note, this is just a basic example for illustration purposes. Screen sleep may or may not cause a loop

Thank you for the detailed response. It was very helpful. I have a few more questions for you below.
rootSU said:
Sometimes a ROM needs a wipe before flashing..the reason for this is conflicting data.. Most commonly,.this will happen if going from one ROM to another from a different dev, but can also happen upgrading roms from the same dev.
Click to expand...
Click to collapse
Is there an easy way to predict whether this will occur prior to upgrading? And if so, how?
Can I downgrade back to my old nightly and restore my data to go back to the working setup that I previously had?
Is there a way to get my old OS customizations back from the nandroid backup that I created? For example, my desktop icon positions for my apps, etc..
Is it probable that a new version will come out that's compatible with the old versions settings? For example, you mentioned the screen sleep timer being 15, 30, 60 and then changing to 45 and the boot loop occurs. Do the developers ever recognize this issue occurred and then correct it in the next nightly to allow for 15, 30, 45 and 60 so I could restore my data without the boot loop occurring?

thex2 said:
Thank you for the detailed response. It was very helpful. I have a few more questions for you below.
Click to expand...
Click to collapse
Let's see what I can do
thex2 said:
Is there an easy way to predict whether this will occur prior to upgrading? And if so, how?
Click to expand...
Click to collapse
There are no hard and fast rules.. If you're going from Dev A ROM to Dev B ROM, you will almost certainly have to wipe. Also, between major version updates (5.0 to 5.1 for example) you too will most likely have to wipe
Usually for any upgrade on the same ROM that isn't a major version update (dev a 5.0 to dev a 5.0 base) you usually won't have to wipe, but you may well have to, depending on whether the dev changes things a lot. Always have a titanium and a nandroid backup before updating.
thex2 said:
Can I downgrade back to my old nightly and restore my data to go back to the working setup that I previously had?
Click to expand...
Click to collapse
Yes probably. Restore the full nandroid if you want.
thex2 said:
Is there a way to get my old OS customizations back from the nandroid backup that I created? For example, my desktop icon positions for my apps, etc..
Click to expand...
Click to collapse
It depends which launcher you're using.. If you install a launcher from play store, it is a user app.. So if you're restoring user also using titanium filters, it should restore it fully, including widgets etc. That said, sometimes it doesn't always work out. If the launcher has built in backup, it may be wise to use it.
If the launcher is built into the ROM, its classed as a system app, so even though user apps and system apps both keep their app data in /data/data, it will not be seen with titanium if you're using a filter to shoe only user apps and data.. Work around is backup system and user data without a filter in titanium then when restoring, apply the filter for user apps.. Then once user apps are restored, find the system apps you need to restore data for and restore individually as required. You need to restore as little as possible though to avoid the boot loop.
thex2 said:
Is it probable that a new version will come out that's compatible with the old versions settings? For example, you mentioned the screen sleep timer being 15, 30, 60 and then changing to 45 and the boot loop occurs. Do the developers ever recognize this issue occurred and then correct it in the next nightly to allow for 15, 30, 45 and 60 so I could restore my data without the boot loop occurring?
Click to expand...
Click to collapse
Usually not.. Generally ROM v2 changes from ROM v1.. ROM v3 is usually even further away from ROM v1. If a dev is changing such a setting they are probably doing so for a reason.. Sometimes if the setting is part of a function that the dev decides to remove again ROM v3, its possible. But its best to be prepared and accept that wiping and restoring is a common practice in custom ROM flashing

NON-TREBLE to TREBLE

I'm going to update my Device to Latest version of Havoc OS(which is treble, 08132018). I'm currently on 08012018 build which is non-treble.
I was wondering if what Treble Supported Recovery should I use.
And I also wanted to know if it's possible to keep my Applications and System Data and not having to format System and Data in the update process. I don't really want to lose any data and I certainly don't want to start over from the very start of personalizing my phone and the hassle of having to redownload/reinstall all the apps that I currently have installed right now.
To anyone who will help/guide me through the process of updating, I would be very thankful.
Sent from my Redmi 4X using Tapatalk

Sygnomi said:
I'm going to update my Device to Latest version of Havoc OS(which is treble, 08132018). I'm currently on 08012018 build which is non-treble.
I was wondering if what Treble Supported Recovery should I use.
And I also wanted to know if it's possible to keep my Applications and System Data and not having to format System and Data in the update process. I don't really want to lose any data and I certainly don't want to start over from the very start of personalizing my phone and the hassle of having to redownload/reinstall all the apps that I currently have installed right now.
To anyone who will help/guide me through the process of updating, I would be very thankful.
Sent from my Redmi 4X using Tapatalk
Click to expand...
Click to collapse
Im using redwolf or orangefox for flashing treble roms. You may have app crashes or bootlop when dirty flash treble over non-treble. For user apps i suggest you to use titanium backup. backup your apps with tb flash treble rom then restore your apps. i never tested system apps but you can try it.

q0kHaN said:
Im using redwolf or orangefox for flashing treble roms. You may have app crashes or bootlop when dirty flash treble over non-treble. For user apps i suggest you to use titanium backup. backup your apps with tb flash treble rom then restore your apps. i never tested system apps but you can try it.
Click to expand...
Click to collapse
Thank you for replying!
I don't have to wipe internal storage before flashing the Treble based ROM?
Sent from my Redmi 4X using Tapatalk

Sygnomi said:
Thank you for replying!
I don't have to wipe internal storage before flashing the Treble based ROM?
Sent from my Redmi 4X using Tapatalk
Click to expand...
Click to collapse
if your device dont have encyrption you dont have to wipe internal storage. for treble our device uses cust partition as vendor partition.

How do I upgrade from an rooted and unencrypted OOS 5.0.4 to OOS 9.0.5?

So recently I've been thinking of upgrading my phone from Oreo to Pie now that it is available and has had a few updates.
Now I haven't updated my phone in a while. The last time was around the summer of 2018. The OxygenOS version my 3T currently is running is 5.0.4 and my TWRP is on version 3.2.3-0.
A while back I was using the custom ROM 'FreedomOS' (for anyone that still remembers) but that ROM hit it's EOL point last year.
After FreedomOS went EOL I switched to stock ROM following this guide to stay decrypted: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Since I switched back to stock I haven't touched the system or recovery at all besides updating Magisk now and then.
Now the question I'm having is how do I update my phone to the latest Pie version of OxygenOS? Which is version 9.0.5 as of writing this post.
Preferably I would like to upgrade with a dirty flash to keep my data (if I run into issues after I'll clean flash) and I also want to stay dencrypted and have Magisk as root.

For your own sakes don't do that. You probably won't be happy unless you want to update to have bigger numer in info screen. (Well if you would like to update to have bigger number in info screen I would suggest editing some conf file to achieve that.)

it's here all the the time, just follow the guide
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119

First of all, both of you thanks for the replies.
wojtek007pl said:
For your own sakes don't do that. You probably won't be happy unless you want to update to have bigger numer in info screen. (Well if you would like to update to have bigger number in info screen I would suggest editing some conf file to achieve that.)
Click to expand...
Click to collapse
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
BrahmaGandhi said:
it's here all the the time, just follow the guide
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I've read through the thread a bit and notices this: "Important Note: If your device’s Bootloader is Unlocked, then installing this firmware will factory reset your phone as this is a firmware upgrade. All your personal data and app data will be wiped clean! So backup before flashing!"
Does this mean it will actually reset the entire phone and will wipe all of my apps and files? Is there not a way to dirty flash this new version without losing my apps and such?
Now also in the "Custom ROM" part it says the following: "3. Format Data partition - system will be encrypted (this is a must else system will not boot the new Android version)"
As my device is unencrypted at the moment do I need to let it encrypt for OOS 9 to actually boot up? Or can I just follow the steps in this guide and follow procedure 1 to stay unencrypted? https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324

allard1997 said:
First of all, both of you thanks for the replies.
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
Click to expand...
Click to collapse
In simple words phone is slower and hotter. Battery isn't better too (battery life for me was decreased from 5 to 3, 3.5 hours screen on time). You can find more on Oneplus forums.

allard1997 said:
First of all, both of you thanks for the replies.
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
I've read through the thread a bit and notices this: "Important Note: If your device’s Bootloader is Unlocked, then installing this firmware will factory reset your phone as this is a firmware upgrade. All your personal data and app data will be wiped clean! So backup before flashing!"
Does this mean it will actually reset the entire phone and will wipe all of my apps and files? Is there not a way to dirty flash this new version without losing my apps and such?
Now also in the "Custom ROM" part it says the following: "3. Format Data partition - system will be encrypted (this is a must else system will not boot the new Android version)"
As my device is unencrypted at the moment do I need to let it encrypt for OOS 9 to actually boot up? Or can I just follow the steps in this guide and follow procedure 1 to stay unencrypted? https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324
Click to expand...
Click to collapse
i personally would suggest you to stay on oreo or jump to pie custom roms, just skip the oos 9.0.5..
the only thing that really fast and smooth just the face unlock feature :laugh:
as far as i know when you flashed stock oos your data will always be (re)encrypted, unless you do the firmware's patch things like you did before.
jumping (upgrade) from diff. android version it's better to do a clean flash (4 wipes, exclude int. storage will be saved)...and it's mandatory required (from stock to any custom roms). except when you forced to format data you'll lost all data in your phone, for sure.
and if you want to stay unencrypted and disable dm verity for good, it's better to do all that stuffs while on stock oos before you jump onto custom roms.
for more details and assistance i suggest you post on the main thread.

TWRP DATA backup - How does it work

Im on Superior OS - Android 10.
I wanted to know how does TWRP DATA backup work, and where can I have problems?
I was thinking of giving a try to Pixel Experience 10.
If I backup just DATA usign TWRP, install pixel, gapps, magisk and after that I restore DATA, will the rom work perfectly and I will have all my configuration, settings, etc; or it just will work perfectly if I restore it to a clean installation of Superior OS.
Following that question.
May I go and try Havoc - Android 9, and restore DATA from Android 10? Will there be any problems?
And the last one.
If I go from Android 9 to 10, may I restore DATA?
Thanks!

When changing operating systems it's always best to re-install all apps.

I believe TWRP backup doesn't backup apps & data. Stuff like photos, music etc will not be backed up. You'll need to back those up separately. If you use Titanium, that would do more but reinstall your apps from their source and then restore data.
Sent from my Galaxy Tab S5e using XDA Labs

TWRP absolutely backups and restores data... But you only want to do this to the same OS version. You will likely get a bunch of force closes, and instability if you attempt to restore to different version.
A fresh install is always recommended, but you may want to check out the app called "Migrate" - YMMV.

jhedfors said:
TWRP absolutely backups and restores data... But you only want to do this to the same OS version. You will likely get a bunch of force closes, and instability if you attempt to restore to different version.
A fresh install is always recommended, but you may want to check out the app called "Migrate" - YMMV.
Click to expand...
Click to collapse
I would add, "same OS version" yes, but even custom 10 to another custom 10, I would strongly advise re-installing everything.

The problem is that you don't know what the environment is in an operating system and each app looks at its environment while it is installing and sets itself up appropriately.
So you have problems and you waste your own and others' time trying to shoot needless problems just in the hope of saving a few minutes.
You might think, "well, this custom 10 is like that custom 10" but unless you compare the full build trees and sources, you really don't have the faintest idea. They are different, because, well, they ARE different!

Setup EU ROM with locked bootloader on K20 Pro Global ROM

Hi,
I read a tons of topics here, but more I read more it become unclear to me. I need your help to understand how it works, please.
Step-by-step:
I have bought my Redmi K20 Pro from AliExpress 1.5 years ago with Global ROM installed and unlocked bootloader initially
At the time when I was in Europe the biggest disadvantage using the device was that I couldn't set Google Pay to my device. Now I am in Indonesia and Google Pay is not commonly used here, so it's not the big problem now, but anyway, I would like to fix it.
Currently I am doing a lot of work in Instagram, and the huge problem I realized that my device doesn't work properly with Instagram stories. If I use in-app camera to record the story it looks laggy SO MUCH. Also if I am trying to upload pre-recorded video using native camera app to instagram story, video is still laggy and furthermore it's quality is horrible. Seems like it's compressed from 1080p to 360p. Just weeks ago another problem appears that uploading the videos > 15sec the Instagram app doesn't split it to the blocks (where you can add some notes/text/graphics separately to each block) but uploading as a multiple stories with a same graphics and text I selected before uploading. There are tons of complains about it and seems related exactly to this phone model, but still no solutions.
What I want to do is:
install EU ROM with a hope that Instagram will work properly there
Lock bootloader to setup Google Pay
Checking this forum and other resources I found the info that it's not always possible safely migrate to EU from GLOBAL. Furthermore, many people do not recommend to lock bootloader if it was unlocked.
The questions are:
Is it possible to do what I want safely? Migrate to EU ROM and lock bootloader
will EU ROM help me with instagram issue?
how can I do it?
can ROM migration somehow change the IMEI code? My device is registered in Indonesia, and according to new laws here, if the IMEA changes, I will need to register it again, and it could be a problem
Thank in advice. :angel:

I would suggest you to flash the best custom miui rom out there: Xiaomi EU. Visit the below link and read the rom features section to get an idea.
https://xiaomi.eu/community/threads/miui-12-0-stable-release.56191/
I'm suggesting this because, you can keep your bootloader unlocked and SafetyNet passes by default (Google Pay). Instagram will work properly and fyi, changing roms doesn't change IMEI unless you dont mess it up. Instead of TWRP, use OrangeFox recovery:
https://orangefox.download/device/raphael
BACKUP First before proceeding.
This is the download link for latest stable custom miui eu rom 12.0.5.0:
https://sourceforge.net/projects/xi...MI9TPro_V12.0.5.0.QFKCNXM_v12-10.zip/download

Thanks for your reply
Siddk007 said:
I'm suggesting this because, you can keep your bootloader unlocked and SafetyNet passes by default (Google Pay). Instagram will work properly and fyi, changing roms doesn't change IMEI unless you dont mess it up. Instead of TWRP, use OrangeFox recovery:
Click to expand...
Click to collapse
The instructions in a link you provided above are about TWRP usage. Should I just replace all steps related to TWRP with OrangeFox?
Also, there are some steps to unlock the bootloader. Should I skip it because bootloader is already unlocked in my case?
Siddk007 said:
BACKUP First before proceeding.
Click to expand...
Click to collapse
Is there some specific backup tool or I can still use my Google Account backup options? Is there any way to keep all my apps (or at least settings) after new ROM installed?

romahaaa said:
Thanks for your reply
The instructions in a link you provided above are about TWRP usage. Should I just replace all steps related to TWRP with OrangeFox? - YES
Also, there are some steps to unlock the bootloader. Should I skip it because bootloader is already unlocked in my case? - YES, skip it
Is there some specific backup tool or I can still use my Google Account backup options? Is there any way to keep all my apps (or at least settings) after new ROM installed?
Click to expand...
Click to collapse
- first of all copy all the files on your phone's internal storage to a pc/laptop.
- Google backup should work, but i'm not sure.
- Better to reinstall all the apps and set it up since, the rom is totally fresh and latest.
installation steps:
remove any password/pin if set.
After flashing orangefox recovery,
wipe system, data, cache, dalvik, vendor.
install rom. wait for atleast 15 mins to boot.
btw, is your system is encrypted?

Siddk007 said:
btw, is your system is encrypted?
Click to expand...
Click to collapse
Just checked - yes, it's encrypted. As I understand I need to disable it? Should I do it only for installation and after set it back encrypted?
Also, from the other instructions people recommend to logout from Mi account/Google account and remove pin code and fingerprints before flash operations.

romahaaa said:
Just checked - yes, it's encrypted. As I understand I need to disable it? Should I do it only for installation and after set it back encrypted?
Also, from the other instructions people recommend to logout from Mi account/Google account and remove pin code and fingerprints before flash operations.
Click to expand...
Click to collapse
If you want to disable it, you will have to format your data which will wipe your phone completely. Or you can leave it encrypted.
Yes, remove google/mi account and remove pin/password before flash.

Siddk007 said:
If you want to disable it, you will have to format your data which will wipe your phone completely. Or you can leave it encrypted..
Click to expand...
Click to collapse
Don't see any reason to disable it then if it's possible to change a ROM keeping that setting.
Will try run the process today-tomorrow

So, I did it spending tons of time.
Unfortunately Google Play app is still not visible in GooglePlay store, probably because of unlocked bootloader.
The tons of instructions I didn't find any detailed but simple enough. Here are some easy steps:
1. Make sure you got all suitable software and drivers installed. This needed to run terminal `fastboot` command, what is a part of google `developer_tools` package. In my case I had it before. To check, does it exist or not you can just run `adb -devices` in terminal and it shoul show you the list of android device connected by USB
2. Create a local backup using MIUI Back up and restore menu in settings. Same created backup folder on you PC
3. Remove all locks/fingerprints
4. Logout from Google account. I couldn't logout from Mi account, but that didn't affect somehow
5. Start flashing:
5.1. download Orange Fox and extract. We need only .img file from the archive
5.2. run `fastboot flash reboot` to allow device start in boot mode
5.2. run `flash recovery <path to recovery.img from Orange Fox>`
5.3. after completed, hold Volume - and power button until MI logo appear
5.4. copy Orange Fox zip archive to device internal storage, run the installation and reboot
5.5. crete a backup in Orange Fox
5.5. while in Orange Fox bootloader copy ROM zip archive to internal storage. Wipe the data: data, cache, dalvik. Wipe system and vendor if only you are sure what are you doing. I wiped because it's needed for "clean" install in my case. DONT reboot after.
5.6. Run ROM installation. After completed and you are still loaded automatically to Orange Fox, this means you need to format data partition. Select Menu > Partitions > Data in Orange Fox. Reboot. MIUI setup will start