Develop Bugs

[Q] Layman's questions regaring installing new ROM!

I am following this forum closely since few months, and think I should do more with with my Defy now! I have already rooted my phone but I am still on stock Eclair. I really, really want to try CM7 but though I am quite tech-savvy, there are some things which I am still unable to get into my head! So I need someone to help me, in plain English, with the following:
1 If I install CM7, or any ROM, and then decide to go back to stock, can I?
2. I guess I can using a nandroid backup, right? BTW, what is nandroid backup?!
3. AFAIK, nandroid backs up the current ROM so that if things go wrong it can be reverted, right? If yes, how to perform a nandroid backup on Defy? How easy is it? How much of space does it take in the SD card?
4. What is sbf, recovery etc.? Why are they needed? What are the specific versions I need based on my phone:
{
"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"
}
Offtopic:
5. If I perform a 'Factory Reset', will I lose root?
Please help me understand all these; from what I have read so far everything seems so confusing!!

1. CM7 requires Froyo(2.2) based SBF in order to install. So you must be on official Froyo(released via your phone over OTA by your network) or have flashed Froyo. Once you FLash or upgrade your phone through either of these methods, you cannot downgrade back to 2.1. In the case of official it is not problem, and because official 2.2 is being rolled out, you can probably safely upgrade by flashing one of the stable official SBF's from any of the versions offered on the forums, you probably want to look for ROM users from your country to get an idea if the SBF the ROM is based on works in your region without much hassle.
2. Others will need to answer the Nandroid thing, I know as much as I use Nandroids to make a back up of MY phones state as a way to go back to how my phone was prior to me messing with it, but I am not clear on how you can use a Nandroid from another persons phone on your own. I always just flashed the latest SBF that was Deblured. I am currently using the most recent "Nordic" SBF and CM7, I flashed the SBF and installed the CM7 zip file from recovery.
3. See #2
4. SBF as far as I know is the actual firmware that the phone uses, this set of code tells the phone what does what when it comes to the phones hardware. The files have a base Android on them that they work from which can be with Blur or without Blur(Motorolas GUI shell for Android). So some SBF's come with 2.1, some with 2.2 and soon 2.3.
The Android version is the software side of things, and this can vary depending on how the ROM you are using is made(I think) This is why your SBF will have different numbers associated with it(because these SBF's vary from carrier to carrier and from country to country, some have Blur, some do not, some are set up for particular GSM ranges for 3G etc) and your Android will have a separate number.
It is a bit confusing and my knowledge is kind of limited so I may in fact me kind of mixed up on some of these things. Take what I say with a grain of salt.
Recovery is a small app that allows you to use a custom recovery(which is not included with Motorola phones) which is a method to insall ROMs. You need to root and install recovery to start making real changes to your phone.
Hope some of this information helps, I have bricked my phone quite a few times learning how to modify it and I would suggest going ahead and trying things and making a few mistakes so you know how to unfuck your gear as some of the kind contributors have mentioned before.
Fear not, go forth and flash that little bugger to it's full potential.

abhi.eternal said:
I am following this forum closely since few months, and think I should do more with with my Defy now! I have already rooted my phone but I am still on stock Eclair. I really, really want to try CM7 but though I am quite tech-savvy, there are some things which I am still unable to get into my head! So I need someone to help me, in plain English, with the following:
1 If I install CM7, or any ROM, and then decide to go back to stock, can I?
2. I guess I can using a nandroid backup, right? BTW, what is nandroid backup?!
3. AFAIK, nandroid backs up the current ROM so that if things go wrong it can be reverted, right? If yes, how to perform a nandroid backup on Defy? How easy is it? How much of space does it take in the SD card?
4. What is sbf, recovery etc.? Why are they needed? What are the specific versions I need based on my phone:
Offtopic:
5. If I perform a 'Factory Reset', will I lose root?
Please help me understand all these; from what I have read so far everything seems so confusing!!
Click to expand...
Click to collapse
i'm new too but not new to Android...
1. Yes. And you can downgrade to 2.1 again. I did!
2. The clue is in the name, all your phones current data, apps and rom are stored on the nand memory within your Defy. The Nandroid backup takes a snapshot of all this data and stores the information from each partition on your sdcard.
3. Nandroid backup is easy. I recommend the 2nd init auto installer...that also installs recovery (custom) and is needed for cm7. Backups vary in size...mine are usually around 450mb.
4. SBF's are just official rom files, in a format readable/flashable with RSD Lite. You are on the same version as i started on. The order i went in was...
Code:
1. Root.
2. Install 2nd init. recovery installer. http://forum.xda-developers.com/showthread.php?t=1032212
3. Boot into recovery and select Backup/Restore and make a backup.
4. Download a 2.2 fixed sbf like the nordic one.
5. Download CM7. (Place in same directory as your nand backup. sdcard/clockworkmod/backups.)
6. Boot into 2nd init menu and select to boot 2nd init by default.
7. Select custom recovery and restore the cm7 nandroid.
7.5. Wipe data from custom recovery.
8. Reboot Defy while holding volume up.
9. Plug in usb and start up RDS Lite. Select fixed sbf you downloaded and press start. Once finished it will boot into CM7. (I had to pull battery after RDS Lite finished)
5. I don't think you lose root as i'm sure superuser is installed to system partition which isn't wiped when factory reset.

Oh also just for future reference. If you ever mess up (no recovery possible) or need to restore for warranty just look for the 2.51 full sbf for your region or operator and flash it with RDS Lite. You end up with a factory fresh phone and can start again

just the kind of post i need this, just one question,
you say backup/restore, I have installed 2init, but I cant see this option. Does this have a different name, or am I totally looking at the wrong menu?

ahh got it, i just needed to mess first

really stumped,
I am trying to install the leaked froyo uk build. I have installed the moto drivers and the rsd lite.
I put the .sbf in the rsd lite and connect my phone.
It sees my phone fine, but when I try to flash it just fails straight away.
I have tried enable/disabled usb debugging , but that makes no difference. Have tried wipe, but again no change,
what am I doing wrong?
Thanks in advance

Do you not get an error message? What is your current rom?

Jakethepeg said:
really stumped,
I am trying to install the leaked froyo uk build. I have installed the moto drivers and the rsd lite.
I put the .sbf in the rsd lite and connect my phone.
It sees my phone fine, but when I try to flash it just fails straight away.
I have tried enable/disabled usb debugging , but that makes no difference. Have tried wipe, but again no change,
what am I doing wrong?
Thanks in advance
Click to expand...
Click to collapse
For flashing with RSD you MUST be in bootloader mode.
Hold down volume up as you boot the phone, you will get some white text on a black screen. After this, plug your phone in via USB to your comp, once RSD reads it, load the sbf, and then start the flashing process and wait until it is completely finished and either boots your phone, or instructs you to boot manually.
The text on the phone will change as the process starts.

Hi Erra
thanks for that, I have been trying to flash in bootloader mode but I still get the message unable to flash.
Ephumuris, I am using stock uk 2.51

Are you using the latest version of RSD Lite?

You installed the motorola drivers?
Sent from my Defy on CM7.

Jakethepeg said:
really stumped,
I am trying to install the leaked froyo uk build. I have installed the moto drivers and the rsd lite.
I put the .sbf in the rsd lite and connect my phone.
It sees my phone fine, but when I try to flash it just fails straight away.
I have tried enable/disabled usb debugging , but that makes no difference. Have tried wipe, but again no change,
what am I doing wrong?
Thanks in advance
Click to expand...
Click to collapse
Would RSD Lite even recognize the phone without drivers installed?

From where can we get the latest version of RSD Lite?

Ok tried again, for the first time, managed to make a nandroid backup, (something that also wouldnt work ).
Still getting an error though, when I try and flash, interestingly though, my rsd lite, doesn't seem to be able to load roms, with their full name, (i have to shorten it to uk.sbf or something along those lines).
Tried to flash the froyo uk tmoby leaked rom (11 version), and the error message I get is Failed flashing process (0x7100); phone connected.
Version I am on for rsd lite is 4.9 multiflash/ multi flex.
Thanks again for all your help and patience
Feel such a noob with this, I never had this many issues with my old xm5800
the version of rsd lite is compatible with 2.51 isnt it?
Or do i need to grab an older version, just noticed this got released in march.

ephumuris said:
i'm new too but not new to Android...
1. Yes. And you can downgrade to 2.1 again. I did!
2. The clue is in the name, all your phones current data, apps and rom are stored on the nand memory within your Defy. The Nandroid backup takes a snapshot of all this data and stores the information from each partition on your sdcard.
3. Nandroid backup is easy. I recommend the 2nd init auto installer...that also installs recovery (custom) and is needed for cm7. Backups vary in size...mine are usually around 450mb.
4. SBF's are just official rom files, in a format readable/flashable with RSD Lite. You are on the same version as i started on. The order i went in was...
Code:
1. Root.
2. Install 2nd init. recovery installer. http://forum.xda-developers.com/showthread.php?t=1032212
3. Boot into recovery and select Backup/Restore and make a backup.
4. Download a 2.2 fixed sbf like the nordic one.
5. Download CM7. (Place in same directory as your nand backup. sdcard/clockworkmod/backups.)
6. Boot into 2nd init menu and select to boot 2nd init by default.
7. Select custom recovery and restore the cm7 nandroid.
8. Reboot Defy while holding volume up.
9. Plug in usb and start up RDS Lite. Select fixed sbf you downloaded and press start. Once finished it will boot into CM7. (I had to pull battery after RDS Lite finished)
5. I don't think you lose root as i'm sure superuser is installed to system partition which isn't wiped when factory reset.
Click to expand...
Click to collapse
When is the time to do full wipe??

Oops i missed that. Straight after the step of restoring the cm7 nandroid.
Step 7.5. Wipe data from custom recovery.

How to install cyanogenmod on HTC One M8?

Hi,
I searched online for 2 hours but I see a lot of mixed, outdated articles, videos. For example Hasoon's app link doesn't work, or the cyanogenmod installer link for your phone is giving me 404.
I don't want to do something stupid so can someone tell me or show me a guide on how to install this?
My phone is from Rogers (contract ended). I just want a fast and light weight android without bloatware and nice features.
Will I have to find a cyanogenmod release from someone who use Rogers, or can you use the same build on that's built for M8 regardless of your phone company?
Thanks a lot.

Have you done anything to the phone yet (unlock bootloader, s-off, root, etc.) or still just fully stock?
Is the phone currently on Lollipop? You'll want updated hboot to run current CM12.1.
Don't bother with toolkits and the like. The toolkits haven't been updated in over a year, contain obsolete files, and that will cause you more problems than anything. The steps are not that hard to do "manually", and that is a much better learning process. The toolkits shortcut that learning process; putting you in a position to get into a jam, with no knowledge of how to get out of it.

Thanks a lot for replying. I unlocked the bootloader, s is off, but I don't know how to root. I think it's superSU right? If so, I assume I will do this by installing this zip after I flash the cyan mod?
I downloaded these to my phone:
{
"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"
}
I assume I just have to format/adv format everything and install these zip files using TWRP, right? If so, that wasn't hard
But I have another problem. I don't have an SD card or OTG cable to store these zip files outside the phone. I have usb flash memory/stick, HDDs but AFAIK I need OTG cable to use them with my phone.
Also another thing that concerns me is the new Android version is coming next week, right? So should I wait for it and use that cyan mod?
Are you able to get OTA updates with cyan as easily without having to flash your phone every time?
Thanks again

lachdanan said:
Thanks a lot for replying. I unlocked the bootloader, s is off, but I don't know how to root. I think it's superSU right? If so, I assume I will do this by installing this zip after I flash the cyan mod?
Click to expand...
Click to collapse
No need to flash SuperSU to root after flashing CM.
Go into Developer's Options in phone's settings (may need to tap version number 7 times to make Dev Options appear) then turn on root there.
lachdanan said:
I assume I just have to format/adv format everything and install these zip files using TWRP, right? If so, that wasn't hard
Click to expand...
Click to collapse
Before doing anything, make a TWRP backup of your current (presumably stock Sense) ROM.
Then backup any user data you want to keep, by method of your choice (Titanium Backup, cloud, copy to PC, etc).
Then do a wipe. I would only recommend the default Wipe option (user data, cache and Dalvik) in TWRP. Right in TWRP, it says "most of the time, this is the only wipe you will need" (or words close to that effect) and it says that for good reason.
You certainly don't want to wipe "everything". If you wipe internal storage, you will lose the TWRP backup I just told you to make. Plus you will wipe the ROM and gapps zips you are going to flash, if you put them on internal storage.
Some folks swear by wiping system when flashing ROMs. I don't like this, since if for some reason the ROM fails to flash, you are then stuck with no OS (although you will have a TWRP backup, that I just told you to make). If you run into problems, you can always wipe system later and flash again. But honestly, after many ROM flashes on several different devices, and I've never once had to wipe system, that I recall. Unless of course the ROM instructions require to wipe system. If that is the case, follow the instructions.
After default wipe, flash the ROM, and flash gapps. Then reboot.
lachdanan said:
But I have another problem. I don't have an SD card or OTG cable to store these zip files outside the phone. I have usb flash memory/stick, HDDs but AFAIK I need OTG cable to use them with my phone.
Click to expand...
Click to collapse
I don't follow what the problem is. It looks like you have the files on a PC. Just connect your phone by USB, then copy and past the files to the phone's internal storage.
Don't know why you want to store the files "outside the phone" (and not on the PC) unless you are talking about wiping internal storage. Again, it isn't necessary to do that.
lachdanan said:
Also another thing that concerns me is the new Android version is coming next week, right? So should I wait for it and use that cyan mod?
Click to expand...
Click to collapse
It usually takes a bit of time for a new Android version to be ported over to a respective device. Than a bit more time, for it to be fairly stable. So its up to you, but I say why wait. You can always flash again when CM13 (or whatever its going to be called) is released on the M8.
One of the things about flashing ROMs, is it can be addictive. So if you have the urge and time to do it now, just do it!
lachdanan said:
Are you able to get OTA updates with cyan as easily without having to flash your phone every time?
Click to expand...
Click to collapse
I actually don't use CM on the M8, so check the CM thread for any discussion on this.
Even if OTA updates aren't functional (no idea if they are or not), you can often download and "dirty flash" new updates (like nightlies). Dirty flash, means you just wipe cache and Dalvik and flash the ROM, keeping user data. Its very fast, since you don't need to setup the phone again.
Although, sometimes a dirty flash won't work, and you need to do a full flash. When CM13 comes out, you will probably need to do a full wipe before flashing it. And likewise, you probably won't want to do an OTA update to CM13 either.

Thanks a lot man, you cleared many of my questions. Regarding the storage, sorry they are already on my phone, so the phone has internal storage and another separate storage? I thought HTC One M8 had a single storage inside so if you delete things, everything is deleted.
But since you said don't delete system, then this is not an issue?
Also by system, does it mean actual stock android system files? Won't these files conflict with CM's own system files? Or if they are bloated with time, usage etc, then this will leave these unnecessary files behind?
Thanks again

lachdanan said:
Regarding the storage, sorry they are already on my phone, so the phone has internal storage and another separate storage? I thought HTC One M8 had a single storage inside so if you delete things, everything is deleted.
Click to expand...
Click to collapse
Nope, the storage is actually partitioned into something like 41 separate partitions: system, hboot, recovery, radio, data, boot, and (of course) many more.
So when you say you want to wipe "everything" I said you don't want to do this, and I really mean it.
Plus, one of the Advanced wipe options in TWRP is the removable SD, which most folks will not want wiped, most of the time.
So again, use the default wipe option in TWRP. Only pick the Advanced options, if you know exactly what you are doing, and fully understand the result of wiping that selection.
The "default" TWRP wipe just wipes user data, cache and Dalvik. Internal storage (which is data/media) is actually not touched, and that is most likely where you placed the ROM and gapps files (plus its the default location for TWRP backups, Titanium Backup and some other things).
lachdanan said:
But since you said don't delete system, then this is not an issue?
Click to expand...
Click to collapse
Correct.
lachdanan said:
Also by system, does it mean actual stock android system files?
Click to expand...
Click to collapse
If you are still on the stock ROM (haven't flashed any ROM yet, was I assume is the case) then YES, system partition is where the actual stock ROM (stock Android system files) are currently located.
lachdanan said:
Won't these files conflict with CM's own system files? Or if they are bloated with time, usage etc, then this will leave these unnecessary files behind?
Click to expand...
Click to collapse
Nope, when a ROM is successfully flashed, it will wipe system, then install the new ROM on the system partition.
This is another reason why I say its not necessary to manually wipe system in TWRP. It will happen anyway when you flash the ROM. But if for some reason the ROM fails to flash (not unheard of, for various reasons), you will still have have a working phone if you didn't wipe system.

Thanks. I made a stupid mistake before reading your last post, now it seems like my phone's data storage is completely empty I restarted into bootloader and added TWRP to it again using Windows. But then I chose restart on that bootloader menu and now the phone screen is stuck in HTC android boot screen. I couldn't turn the phone off or restart. Do you know how to fix this?

I managed to fix it and now I am in cyan Looks really good, I will be customizing it now but it feels snappy
Thanks again man

[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.

[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.