Develop Bugs

Need to flash my phone, but have a question...

So here's the scenario. Hopefully I don't leave anything pertinent out...
Galaxy S3 w/Sprint. Phone is rooted but has the stock ROM on it. The phone doesn't need to be rooted, but I figured something like wifi tether might come in handy at some point. I rooted it such a long time ago I honestly don't remember how I did it. However, the screenshots of the Odin program look somewhat familiar so I'm guessing it was something with that.
When I boot into recovery mode, it says CWM-based recovery v5.5.0.4 and has the standard CWM menu.
This, of course, means I can't get the OTA update that came out a few months back.
So, in order to get the stupid prompt to stop bugging me to update, I need to flash the phone with something. I'd be fine using an updated version of the Stock ROM, or would be happy to put something like CM10 on there. I don't want anything experimental so I'd go with the stable version.
This leads me to three questions.
1) What would you recommend as far as a ROM to flash when comparing stock vs CM vs whatever else. I'm fine with the stock feature set and stability is the top priority.
2) When I flash whatever ROM I flash, how much of the phone needs to be wiped? All the apps will have to be reinstalled, but does it also have to wipe things like photos and such?
3) How do I do the flash? All of the tutorials I see assume you're starting with an unrooted phone, which I'm not. Do I just copy the ROM Zip file over, do one of the wipes and then do the install from zip? I'm just looking for the basic steps to follow since I"m already rooted and have a recovery already there.
THANKS for any help so I can finally get this straightened out!!!

1.It depends on your likings. Play with different ROMs.
2.Just a wipe before to flash the ROM.No need to wipe photos and videos.
3.Yep.Put the ROM on your SD card,wipe your phone and then flash it.
Hope that helps
Sent from my GT-I9300 using xda app-developers app

kelemvor33 said:
This leads me to three questions.
1) What would you recommend as far as a ROM to flash when comparing stock vs CM vs whatever else. I'm fine with the stock feature set and stability is the top priority.
2) When I flash whatever ROM I flash, how much of the phone needs to be wiped? All the apps will have to be reinstalled, but does it also have to wipe things like photos and such?
3) How do I do the flash? All of the tutorials I see assume you're starting with an unrooted phone, which I'm not. Do I just copy the ROM Zip file over, do one of the wipes and then do the install from zip? I'm just looking for the basic steps to follow since I"m already rooted and have a recovery already there.
THANKS for any help so I can finally get this straightened out!!!
Click to expand...
Click to collapse
1) The standard answer is: try them all out and see if you like one or the other. But I'll be nice and also say that if you're looking for something stable, I'd recommend The People's ROM. It's a TW-based ROM with a lot of customization, but it's very stable and has a large user base. They're always willing to help someone out (as long as you search before asking).
2) It really depends what you're flashing. I always recommend what I call a "so fresh, so clean-clean flash," which means wiping /data, wiping /system, and cache and dalvik cache. You won't lose your photos, but you will lose all apps and their associated data (save games, etc). The reason I recommend wiping system (which others might not suggest), is that different ROMs have different mods associated with them, and as an end-user of the ROM, you have no idea if your previous ROM is leaving behind files in /system that won't play nicely with your new ROM. So I typically wipe system as well as data and the caches.
3) You're in luck. I have a previous post that explains #3 is pretty good detail. Since you have verified that you have CWM, you can skip the first section where I talk about that. I have quoted it below:
kay131108 said:
ok..can u pls be a little more specific..i if i press the three buttons with volume down is just an android in download mode..so what do i do next?...clockworkmodrecovery
Click to expand...
Click to collapse
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
And lastly, you don't have to lose all your apps. You can use Titanium Backup (TiBu) to restore your apps. You just have to be careful not to restore any system apps, as they tend to not play well between Roms. I have quoted my previous post about TiBu down below so you can review some features/warning about TiBu.
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Click to expand...
Click to collapse

[ROM][Lineage 16.0 Unofficial][Pixel 2 XL/Taimen][06-09-19]

Hi all. Since I haven't gotten any word as to when there will be official support, I wanted to go ahead and share a build of Lineage OS 16.0 for our Pixel 2 XL/Taimen. It's a completely stock build. If it's working for enough people, then I'll continue to provide builds until/unless we get official support. If you find an error, please try to post logs via logcat to aid in fixing it (better yet to submit it to the Lineage OS team directly as well).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Steps for First Install:
Flash latest google image
Boot using the latest version of TWRP: https://dl.twrp.me/taimen/twrp-3.2.3-1-taimen.img.html
Wipe cache and data
Flash latest ROM .zip file
Flash the TWRP installer: https://dl.twrp.me/taimen/twrp-pixel2-installer-taimen-3.2.3-1.zip.html
Reboot to recovery
Flash OpenGapps (Android 9.0, ARM 64, probably nano): https://opengapps.org/ or MindTheGapps: https://androidfilehost.com/?fid=3700668719832237178
If desired, flash a custom kernel
If desired, flash Magisk
Reboot and hopefully enjoy
Steps for Updates:
Follow steps 4- 10 above. You can skip steps 1 - 3 (latest Google image, booting with TWRP .img, wiping) and optionally 7 (flashing Gapps).
Latest ROM, 06-09-19:
Download
Old Releases:
Old Download
I usually like to provide updates every ~2 weeks or month to keep up with security updates and/or anything else important. Thanks for trying and God bless .
Special thanks to @draymond1987, @RaymanFX, and all the other developers for their continued hard work.
View changelog up to build date
/.repo/local_manifests/roomservice.xml is attached

A quick note: If you seem to get stuck on the Gapps setup wizard, you can touch each corner of the screen, going clockwise, starting in the top left corner, to skip it. I've seen the data transfer tool have issues lately. You can uninstall it and continue afterwards.

Any known bugs?

pimpdaddy00 said:
Any known bugs?
Click to expand...
Click to collapse
I had an issue at some point where it would shut off when unplugged, but I don't know if it was just something about how my phone is setup. The other thing I encountered was the setup wizard getting stuck before (but fixed after removing the data transfer tool manually later). I'm hoping to see someone else have it working as I know at some point I was able to boot without issue, other than Magisk possibly not working without flashing another custom kernel. Getting any feedback from logs would helpfully tell me what changed and possibly where to fix it at that point.

I checked the channelog and noticed a few minor changes that seemed nice. Overall, I just hope Active Edge gets working in future ROMs lol. Though I know it's difficult. Good job on this!

Can't even get this to boot.

LLStarks said:
Can't even get this to boot.
Click to expand...
Click to collapse
Do you see the lineage OS logo and then blank screen or very shortly after? I've been facing an issue where it looks like com.qualcomm.qti.telephonyservice stops due to not loading a reference properly if I'm not charging. Thanks for letting me know you've had issues.

I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.

LLStarks said:
I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.
Click to expand...
Click to collapse
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722

calsurferpunk said:
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722
Click to expand...
Click to collapse
Thanks a bunch! Flashing now!

Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?

tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
Could try flashing a different gapps package. I always used the mini

tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
I think I went to app info and told it to force stop. If it's on the data transfer utility, I just told it to uninstall (as it seemed to be the culprit for me). I think I either reset/restarted or continued with the pixel setup after that. Either way, just getting to the data transfer utility from within setup or on the apps list and uninstalling it was the trick for me.

Trying this out today for the first time. WiFi calling isn't working, UK EE. Got google apps nano working but had to force quit the setup a few times. Otherwise its looking really nice, thanks!

Hi again all. I just wanted to let all of you who are using this ROM know that I'm planning on updating it very soon. I've been waiting for Google to release security patches for this month, but if I don't see them soon then I'll build with the latest Lineage OS changes anyhow.

On the 2nt or 3rd post is said to tap all for corners of the screen clockwise from top left and it will skip setup, then go into apps and uninstall the data transfer tool. When you do that it will let you move forward with the setup and still let you transfer anyway you want. Hope this helps.

It's amazing! I like it! Thank you so much

Hi again. Here's the latest build of the sources as of today:
https://androidfilehost.com/?fid=11410963190603892886
Something to note is that when I installed it, I simply went to recovery, flashed the new ROM .zip, then flashed the TWRP installation zip again. After that, I rebooted to recovery and installed Magisk again.
For some reason once I booted, the google play store was missing (even though previously having installed OpenGapps along with the previous ROM version). I went back to recovery, reflashed OpenGapps, and it was back again (along with having to go through setup once again, including removing the data transfer tool). Some of the apps (mostly Google's) wouldn't open correctly until I uninstalled and reinstalled them again). My Google account also wasn't present, so I had to add it back as well.
If you come across that same problem, these steps should work, otherwise you might want to just try a fresh install (wiping the old cache and data while in recovery). For anyone who comes up with an easier solution, could you please be sure to share what you did? Everything is still working fine afterwards, but it was just annoying to have to uninstall and add things back. I didn't use the latest OpenGapps, so that might have just been my problem.

I'm unable to complete the setup, since the setup always crashes after adding a google account. It will ask me if I want to select a backup from the cloud or skip, and any option I pick will crash the setup. As a result, Pixel Launcher will not work (maybe that's another issue entirely?) other than that, rom works.

Was wondering if anyone had had any problems with the now playing? I get a pixel ambient services keeps stopping when I ask the assistant but it will tell me the song name. But now playing seams to not work at all. I did try uninstalling the ambient services and reinstall it with no change.

black screen, or not booting after TWRP restore from recovery

Let me start this by saying my most recent device that I just came from was a Galaxy S5 on Android 5, so my knowledge on Android 9 and new tips tricks and methods is a little outdated. But I have a Google variant of the pixel 3XL that has the bootloader unlocked and TWRP installed for the recovery and the phone is rooted. I recently decided to try and restore a backup I had made shortly after rooting the phone. This backup consisted of the data and system partitions along with the vendor image. I had never seen the vendor image or system image as a recovery option to back up in previous versions of Android, again my knowledge being a little outdated. So I wasn't sure if I needed the vendor or system image and had read somewhere that the vendor image was recommended. So my restore consisted of restoring the data in system partitions and the vendor image. But after the phone rebooted it wouldn't boot, just a black screen. I was able to fix this by flashing the factory image without performing the Wipe through fast boot. I believe this successfully brought me me back to the date of which the backup was by looking at my text messages. But my question is; what did I do wrong and why did I get a black screen after performing a restore and have to do an additional step of flashing a factory image to get the phone back in working condition? Should I not select the vendor image as part of my backup or do I need to include the system images well?

teknikalcrysis said:
Let me start this by saying my most recent device that I just came from was a Galaxy S5 on Android 5, so my knowledge on Android 9 and new tips tricks and methods is a little outdated. But I have a Google variant of the pixel 3XL that has the bootloader unlocked and TWRP installed for the recovery and the phone is rooted. I recently decided to try and restore a backup I had made shortly after rooting the phone. This backup consisted of the data and system partitions along with the vendor image. I had never seen the vendor image or system image as a recovery option to back up in previous versions of Android, again my knowledge being a little outdated. So I wasn't sure if I needed the vendor or system image and had read somewhere that the vendor image was recommended. Show my restore consisted of restoring the data in system partitions and the vendor image. But after the phone rebooted it wouldn't boot, just a black screen. I was able to fix this buy flashing the factory image without performing the Wipe through fast boot. I believe this successfully Road me back to the date of which the backup was by looking at my text messages. But my question is is what did I do wrong and why did I get a black screen after performing a restore and have to do an additional step of flashing a factory image to get the phone back in working condition? Should I not select the vendor image as part of my backup or do I need to include the system imagAes well?
Click to expand...
Click to collapse
My experience restoring from twrp hasn't been that great. But you need the system image, not partition, and vendor image.

jd1639 said:
My experience restoring from twrp hasn't been that great. But you need the system image, not partition, and vendor image.
Click to expand...
Click to collapse
Thanks! So to confirm, with the Pixel 3XL I only need to back the System Image and the Vendor Image and leave the Boot, Data, and System Partitions unselected?
Like this..?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

teknikalcrysis said:
Thanks! So to confirm, with the Pixel 3XL I only need to back the System Image and the Vendor Image and leave the Boot, Data, and System Partitions unselected?
Like this..?
Click to expand...
Click to collapse
The only thing I have had any success with is backing up and restoring data only. Anything else and you get into trouble. Nandroids are just not working, especially on 10. Lots of discussion in the dedicated TWRP thread under "Roms, Kernels, Recoveries". Best of luck.

v12xke said:
The only thing I have had any success with is backing up and restoring data only. Anything else and you get into trouble. Nandroids are just not working, especially on 10. Lots of discussion in the dedicated TWRP thread under "Roms, Kernels, Recoveries". Best of luck.
Click to expand...
Click to collapse
Thank you! I'm on Android 9... The device came with 10, but I used a factory image to downgrade back to 9 because I had read that the restore option in Titanium Backup wasn't working and I need that to migrate most of my stuff from my old device to the new pixel 3xl...I'll stay off the 10 train until custom recovery and certain bugs like that get worked out....
I'll experiment around with twrp Android backups and restores... That makes sense about the data only partition. That might serve my need with backups and restores, I'll try it ..#TrialAndError

Only thing that ever worked for me was data. TWRP, even on 9, had issues with system and vendor. Google kind of locked those partitions down, even more so in Android 10.

teknikalcrysis said:
...
I need that to migrate most of my stuff from my old device to the new pixel 3xl...I'll stay off the 10 train until custom recovery and certain bugs like that get worked out....
...
Click to expand...
Click to collapse
Just pointing out that depending on the age of the old device, using Google backup does a petty good job getting settings and data to new devices during initial setup.

ktmom said:
Just pointing out that depending on the age of the old device, using Google backup does a petty good job getting settings and data to new devices during initial setup.
Click to expand...
Click to collapse
Yeah but it doesn't transfer the data associated with each app like titanium backup tho, correct?

teknikalcrysis said:
Yeah but it doesn't transfer the data associated with each app like titanium backup tho, correct?
Click to expand...
Click to collapse
Depends on the app. System settings are restored. There is nothing preventing the use of TiBu on A10. You shouldn't be restoring system with TiBu anyway.

ktmom said:
Depends on the app. System settings are restored. There is nothing preventing the use of TiBu on A10. You shouldn't be restoring system with TiBu anyway.
Click to expand...
Click to collapse
I know that titanium backup isn't for system backup/restores just user app data..but I thought I had read on a thread here some where that on Android 10, Titanium Backup was performing backups correctly but not restores...I could be wrong tho

teknikalcrysis said:
I know that titanium backup isn't for system backup/restores just user app data..but I thought I had read on a thread here some where that on Android 10, Titanium Backup was performing backups correctly but not restores...I could be wrong tho
Click to expand...
Click to collapse
I thought that was resolved with the TiBu 8.4.0 update ¯\_(ツ)_/¯

ktmom said:
I thought that was resolved with the TiBu 8.4.0 update ¯\_(ツ)_/¯
Click to expand...
Click to collapse
Okay, I guess I didn't come across that bit of info.. probably didn't read far enough...my last phone was a Galaxy S5 on Android 5...so I've got a lot of catching up to do when it come to the latest knowledge...I'd tried to cram all the knowledge I could before I got my hands on my new Pixel 3xl but I haven't absorbed it all yet...
The TiBu issue and not having a fully working recovery (as far as I had read) was the two main reasons why I didn't stay with Android 10 and downgraded back to 9 as soon as I got the device

[OFFICIAL] LineageOS 18.1 for the Moto G7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto G7
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Moto G7.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
river
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_sdm632

I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.

NTGDeveloper said:
I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.
Click to expand...
Click to collapse
In my case, at the moment it is working well, I am still testing it.
You should try to report the bug:
"Find any? Report them according to this guide"

NTGDeveloper said:
I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.
Click to expand...
Click to collapse
Only on really really old devices like bacon , etc.

npjohnson said:
Only on really really old devices like bacon , etc.
Click to expand...
Click to collapse
Thanks for letting me know. I decided to go with a clean flash anyway just because I think my encryption on my data partition was preventing boot and restoring from a 17.1 nandroid backup broke the system completely. So far, the ROM is very good and I'm happy that I'm now on Android 11!

I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.

PMDPhD said:
I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.
Click to expand...
Click to collapse
Why aren't you using the .zip? Because the linage recovery doesn't do .IMG files I would guess. The .zip is on the twrp , also the .zip can be flashed with magisk

One thing I'm starting to hate about 18.1 is they dropped the option to Kill App by holding back button in developer settings. This may actually be a deal breaker for me, I dont think I can make it without this feature.. Shiat!

Droid4200 said:
Why aren't you using the .zip? Because the linage recovery doesn't do .IMG files I would guess. The .zip is on the twrp , also the .zip can be flashed with magisk
Click to expand...
Click to collapse
I am very new to Lineage OS Recovery. Always used the .IMG files with TWRP. I don't know how to flash a recovery in Lineage Recovery at all, and could not find any instructions anywhere. I did not know I could flash a recovery as a .Zip. I also just realized that my initial question is kind of moot because there is an option in the built in updater in Lineage OS 18.1 to flash both the update and recovery, so my Lineage OS Recovery is already the latest version from 4-4-21, and I won't have to figure out how to flash it. Though it would be useful to know in general.

PMDPhD said:
I am very new to Lineage OS Recovery. Always used the .IMG files with TWRP. I don't know how to flash a recovery in Lineage Recovery at all, and could not find any instructions anywhere. I did not know I could flash a recovery as a .Zip. I also just realized that my initial question is kind of moot because there is an option in the built in updater in Lineage OS 18.1 to flash both the update and recovery, so my Lineage OS Recovery is already the latest version from 4-4-21, and I won't have to figure out how to flash it. Though it would be useful to know in general.
Click to expand...
Click to collapse
Yes the zip makes it so much easier now. If you use the lineageos built in update process you will lose TWRP, download the zip and you can very quicky just reboot to recovery after a lineageos update, then install the twrp.zip . you will lose root so you just reinstall majisk(if you use majisk, it'll keep your modules and settings). There may be a twrp retain script, but I haven't messed with them yet, the reinstall of twrp and majisk is pretty fast (plus I'm used to doing it the old way, sort of like you with the .IMG)

Mostly seems pretty good. Broke "LawnChair2" launcher, but, that seems to be a problem of LawnChair going dormant; Hyperion is working o-k so far as a replacement, with some hassles converting. The OK Google voice activation for Assistant still doesn't work and I can't find any fixes, but that was true on 17.1 also. I *hate* the zooming wallpaper effect, makes it very hard to exactly position wallpaper vs. icons. That is an Android 11 "feature" though, so no getting around it...

Hi there. I upgraded 17.1 to 18.1 recently. Seems working fine on first day until I installed vanced app (i think).
Now, every time the screen go off and when it back on, i see glitches and bad palette color. And can't fix it without a reboot (and then when the screen go off the screen glitches comes back)
Maybe is related with Vanced and microG, any one has this issue too?

TomOehser said:
Mostly seems pretty good. Broke "LawnChair2" launcher, but, that seems to be a problem of LawnChair going dormant; Hyperion is working o-k so far as a replacement, with some hassles converting. The OK Google voice activation for Assistant still doesn't work and I can't find any fixes, but that was true on 17.1 also. I *hate* the zooming wallpaper effect, makes it very hard to exactly position wallpaper vs. icons. That is an Android 11 "feature" though, so no getting around it...
Click to expand...
Click to collapse
New issue - seems I get into a situation where the notification light and a notification sound are coming without any notifications - even if "use notification light" is disabled... mystified at what is doing this so far, trying to figure it out. Also, Lawnchair mysteriously seems to be working...

FoxShadow said:
Hi there. I upgraded 17.1 to 18.1 recently. Seems working fine on first day until I installed vanced app (i think).
Now, every time the screen go off and when it back on, i see glitches and bad palette color. And can't fix it without a reboot (and then when the screen go off the screen glitches comes back)
Maybe is related with Vanced and microG, any one has this issue too?
Click to expand...
Click to collapse
The display glitches with the messed up color palette might be the same bug from 17.1. To fix that I had to change the Color mode from Saturated to Boosted and it stopped.
Settings > Display > Advanced > Color
Might be a different path in Android 11, though.
Basically if the inverted color thing happens again, going to that setting and switch it to a different Color type will reset the colors back to normal without restarting. After doing that once or twice it hasn't happened after. Again, on 17.1, can't speak to 18.1 yet.

Working fine after a week of daily use. Upgrade from 17.1 was simple by following the instructions.
The only issue I had was with Magisk. When I installed version 22.0 after upgrading successfully to 18.1, the device would get stuck on the LineageOS boot logo. After removing all modules using adb ("adb wait-for-device shell magisk --remove-modules", then boot the device), things got back to normal. Reinstalling the modules in Magisk did not create any more issues.
Overall, a very good ROM. Thanks for the effort of creating and maintaining it.

I have an issue with "Do Not Disturb" schedules not turning off. They turn on fine but are still running the following day after the supposed end-time. I'm getting round it with Tasker, so it's not a big deal.
Thanks for maintaining the ROM and updating to version 11.

PMDPhD said:
I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.
Click to expand...
Click to collapse
much easier - Updater app in Settings, three dot menu, "Update recovery alongside OS"

kelue said:
The display glitches with the messed up color palette might be the same bug from 17.1. To fix that I had to change the Color mode from Saturated to Boosted and it stopped.
Settings > Display > Advanced > Color
Might be a different path in Android 11, though.
Basically if the inverted color thing happens again, going to that setting and switch it to a different Color type will reset the colors back to normal without restarting. After doing that once or twice it hasn't happened after. Again, on 17.1, can't speak to 18.1 yet.
Click to expand...
Click to collapse
Thank you! I will try that next time. I had to go back to 17.1 by now, that never happend to me on 17.1

FoxShadow said:
Thank you! I will try that next time. I had to go back to 17.1 by now, that never happend to me on 17.1
Click to expand...
Click to collapse
For me, if it happens, it happens shortly after booting, then a quick reset by changing the color setting will fix it, and it won't happen again until the next reboot. I noticed it happen once after plugging the charger in a minute or so after boot so maybe it's hardware related, I don't know.

Messed up TWRP - stuck on decrypting

So, recently, my Magisk stopped working. I thought I fixed it with seveal steps, including updating Magisk and TWRP, and it worked fine at first, but after one of restarts TWRP started requesting encryption password and doesn't boot into system. Entering system pass/pin doesn't let me into TWRP either, it's stuck on "Attempting to decrypt FBE for User 0".
I haven't done anything related to flashing in 1.5 year so I'm kind of lost now. What would be the best way to recover from this without losing any data? I assume some ADB actions, but what do I need to do exactly?

One more note that I thought was irrelevant: I installed Viper in Magisk. Didn't expect such patch could do this, but after some googling I found 2 people having simila issue afte installing that. Please help! Would replacing boot image to MIUI's help in that case?

Try flashing stock boot image then. Google it

That does not help. If it was as easy as googling I'd have it fixed a long time ago. I don't want to lose any data, to remind. But tried flashing original boot.img as it doesn't mes with data and it didn't halp. Any othe ideas?
EDIT: ok, after desperately flashing back both TWRP and boot.img repeatedly and trying to get into TWRP it somehow did something and I got into the system at least to do some fresh backups with Titanium and potentially other apps. I have no clue how to proceed though as I need Magisk to work. Well, the first thing will be to ty to uninstall Viper. But not sure it was the cause in the first place and I'm too afraid to restart. Any clues on what may be the culpit and how to poceed in the safest way?
EDIT2: nvm, ofc I can't really do a full backup using Titanium since Magisk got disabled after flashing original boot.img. Neither uninstall the Viper module. So even more not sure what to do now. Would temporarily disabling the password help?
EDIT3: "google it" type of advice forced me to brick even further as trying to install Magisk/dm-verity now ended up with bootloop. Also, interestingly, older TWRP doesn't have this decyption issue, more info: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1610

"Decryption issue", eh. I bet you are using 12.0.7/12.0.8/12.5.1. Some folk at Xiaomi decides to do a different approach on encryption, rendering encryption issue. This issue has been solved in a newer version of TWRP except for 12.5.1. But do tell me your current MIUI version.
Use MiFlash to flash your CURRENT version of MIUI (or something above or below, I don't care. Just don't downgrade from 12.0.7, you'll face even more headaches) with "Flash all except data" command. Your device will fine, your data will also intact. I've done this dozen of times.
Another piece of advice: don't carry over your magisk module if you're planning to install a stock boot. Install everything freshly.

Destroy666x said:
That does not help. If it was as easy as googling I'd have it fixed a long time ago. I don't want to lose any data, to remind. But tried flashing original boot.img as it doesn't mes with data and it didn't halp. Any othe ideas?
EDIT: ok, after desperately flashing back both TWRP and boot.img repeatedly and trying to get into TWRP it somehow did something and I got into the system at least to do some fresh backups with Titanium and potentially other apps. I have no clue how to proceed though as I need Magisk to work. Well, the first thing will be to ty to uninstall Viper. But not sure it was the cause in the first place and I'm too afraid to restart. Any clues on what may be the culpit and how to poceed in the safest way?
EDIT2: nvm, ofc I can't really do a full backup using Titanium since Magisk got disabled after flashing original boot.img. Neither uninstall the Viper module. So even more not sure what to do now. Would temporarily disabling the password help?
EDIT3: "google it" type of advice forced me to brick even further as trying to install Magisk/dm-verity now ended up with bootloop. Also, interestingly, older TWRP doesn't have this decyption issue, more info: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1610
Click to expand...
Click to collapse
Sorry, I apologize for that

kekesed97 said:
"Decryption issue", eh. I bet you are using 12.0.7/12.0.8/12.5.1. Some folk at Xiaomi decides to do a different approach on encryption, rendering encryption issue. This issue has been solved in a newer version of TWRP except for 12.5.1. But do tell me your current MIUI version.
Use MiFlash to flash your CURRENT version of MIUI (or something above or below, I don't care. Just don't downgrade from 12.0.7, you'll face even more headaches) with "Flash all except data" command. Your device will fine, your data will also intact. I've done this dozen of times.
Another piece of advice: don't carry over your magisk module if you're planning to install a stock boot. Install everything freshly.
Click to expand...
Click to collapse
Thanks for reply. MIUI 11.0.6.0. Thinking about upgrading to 12 but won't that lose data? I read that flashing ROMs in general results in data loss, does flashing current one differ because it's basically the same system? And I guess because of that option. Do I need MiFlash for it or is that also available in any othe tool?
Also, to make sure we undestand data in the same way, by data I mean the following:
- app data, obvious
- app permissions, annoying to set up if lost as I have lots of apps
- notification settings, similarly as above
- other system settings, not as annoying but still some work
Would love to keep all of these.

Destroy666x said:
Thanks for reply. MIUI 11.0.6.0. Thinking about upgrading to 12 but won't that lose data? I read that flashing ROMs in general results in data loss, does flashing current one differ because it's basically the same system? And I guess because of that option. Do I need MiFlash for it or is that also available in any othe tool?
Click to expand...
Click to collapse
Official upgrades won't lose your data (dirty flashable, as the name suggest "update"). In that case, use fastboot upgrade. I will recommend to hold to somewhere in 12.0.5 or 12.0.6, because if you messed up something, you can still downgrade to many versions, maybe up to initial version?
I did many downgrades before because I have tripped AVB many times, something like <newer A10 version available> -> installed magisk and TWRP -> AVB tripped -> <some A9 MIUI via miflash> -> fastboot update via mi flash pro to <same newer A10 version available> -> rinse and repeat until I got a stable system. Without costing any data. But with headaches, indeed.
Mi Flash is also another option. Make sure you choose the "flash_all_except_data". Or else, more unnecessary headaches.
Destroy666x said:
Also, to make sure we undestand data in the same way, by data I mean the following:
- app data, obvious
- app permissions, annoying to set up if lost as I have lots of apps
- notification settings, similarly as above
- other system settings, not as annoying but still some work
Would love to keep all of these.
Click to expand...
Click to collapse
1. App and app data will stay
2. I guess app permission is also stay. But do confirm, since I never had any issue except when I enable/disable MIUI optimizations
3. Personalization will stay

kekesed97 said:
fastboot upgrade
Click to expand...
Click to collapse
Could you be more specific what this exactly means and how to do it without reflashing data? Googling this results in many unrelated to eachother things.
Asking because I had poblems wih Mi Flash before, so would be great to have a reliable alternative just in case.

Destroy666x said:
Could you be more specific what this exactly means and how to do it without reflashing data? Googling this results in many unrelated to eachother things.
Asking because I had poblems wih Mi Flash before, so would be great to have a reliable alternative just in case.
Click to expand...
Click to collapse
Oopsie! Swapped fastboot with recovery rom, ehehe.
Use recovery rom (the 2 gb one). This will require stock boot, stock recovery, mi account, and internet connection. Flashing is done via MiFlash Pro (Just click that "Flash in Recovery" botton or go to recovery tab).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Figure 1: Mi Flash Pro main interface
Or use Mi Flash by loading fastboot rom (the 4gb one) to Mi Flash, and select "flash_all_except_data".
Figure 2: Mi Flash with "flash_all_except_data" enabled

Oh ok, I see, recovery ROM, downloadable easily from MIUI website, is something you upload though recovery and fastboot ROM through fastboot/MiFlash. Found them here https://c.mi.com/oc/miuidownload/detail?guide=2 along with MiFlash 2020 version (is this the latest version?) but how do I find older ROM versions, e.g. my 11.0.6.0? The MIUI website seems to be a total mess, honestly. And I don't trust random Google results, bunch of them seem like virus traps redirecing to Mediafire and similar upload websites.
Is this also the official MiFlash Pro website? https://miflashpro.com/
EDIT: yes, it seems, also found https://xiaomiflashtool.com/ for the other app's latest version

Here for a streamlined versions or here if you need betas
Mi flash is included in mi flash pro if you want all in one solution. It also have miui downloader embedded

Ok thanks. Now I wanted to backup data through older TWRP 3.3.1 that decrypts correctly, just in case, but it fails because it can't copy `/data/misc_ce/10`:
Code:
I:Error adding file '/data/misc_ce/10' to '/external_sd/TWRP/BACKUPS/mfaajbdu5s79pfhy/2021-07-28--04-07-40_PPR1180610011/data.ext4.win007'
Error creating backup.
I:ERROR tarList for thread ID 0
Any clue what this folder is about and how to get around this? Any other way to backup with this level of access?
From what I see it's something about additional user, maybe from the MIUI functionality, but 0 clue if deleting this is safe.

Destroy666x said:
Ok thanks. Now I wanted to backup data through older TWRP 3.3.1 that decrypts correctly, just in case, but it fails because it can't copy `/data/misc_ce/10`:
Code:
I:Error adding file '/data/misc_ce/10' to '/external_sd/TWRP/BACKUPS/mfaajbdu5s79pfhy/2021-07-28--04-07-40_PPR1180610011/data.ext4.win007'
Error creating backup.
I:ERROR tarList for thread ID 0
Any clue what this folder is about and how to get around this? Any other way to backup with this level of access?
From what I see it's something about additional user, maybe from the MIUI functionality, but 0 clue if deleting this is safe.
Click to expand...
Click to collapse
No idea.
SP Flash tools have low level access to your device, including read back in the correct memory region.

kekesed97 said:
No idea.
SP Flash tools have low level access to your device, including read back in the correct memory region.
Click to expand...
Click to collapse
Fixed that: https://forum.xda-developers.com/t/...ils-because-of-data-misc_ce-10-error.4311899/ and have a backup.
Unfortunately, flashing the recovery ROM = still bootloop. Would flashing the fastboot one be any different if I choose to keep data? Would it flash someting extra?
I read that reading these logs may also help with debugging, but not sue what to look for.
Kernel log (/proc/lastkmsg): https://pastebin.com/T2xBBRvi - some error looking lines at the end, but non-comprehensible. Can I use them somehow futher?
dmesg log: https://ghostbin.com/paste/vyBDk - don't really see anything here, but it's quite long and not sure what to look for
logcat: https://ghostbin.com/paste/PSh7f - lots of "avc" errors
EDIT: well, I tried the fastboot one too, recovery got replaced with stock is the only diffeence I noticed, So I guess that means the data is 100% corrupt and the culprit. How would installing Magisk and the dm-verity/forceencypt zip corrupt the data though? Since that's the only thing I did before he bootloop started happening. Does dm-verity/forceencrypt even affect data? I think Magisk does, but this is really weird anyways. Maybe when I tried to install it on the TWRP with broken encryption it caused some file system failure? Does anyone know which /data dirs does the Magisk zip mess with? Maybe deleting those would help
EDIT2: ran Magisk as uninstall.zip in back installed TWRP 3.3.1, which apparently deletes its data files, but nope, didn't do anything.

I'm sorry I don't have the knowledge to go deeper.