Database Develop

[OFFICIAL] [NIGHTLIES] LineageOS 16.0

{
"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 Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 16.0 thread for the Motorola Moto Z2 Force, codename nash.
Join our Moto Z2 Force Development Discord server!
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Bugs:
Camera Mods don't work
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work.
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Ultrasonic Proximity Sensor doesn't work -- No support present in the OSS Audio HAL. If it was written in, it wouldn't be used by anything in Lineage, as the normal proximity sensor works fine.
Notes:
Official Lineage OS builds for nash ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Technical details on our Treble implementation:
Treble is enabled with VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Download:
LineageOS Updater
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll only find support for these in the Discord linked above.
XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 16.0, ROM for the Moto Z2 Force
Contributors
npjohnson, erfanoabdi, invisiblek
Source Code: https://github.com/LineageOS/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo Firmware
Based On: LineageOS
Version Information
Status: Nightly
Created 2019-03-03
Last Updated 2020-01-12

Reserved

Reserved

Thank you， ota ：）

How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras

7bob said:
How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras
Click to expand...
Click to collapse
Check again.

Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?

zidemizar said:
Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?
Click to expand...
Click to collapse
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.

npjohnson said:
Check again.
Click to expand...
Click to collapse
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?

7bob said:
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?
Click to expand...
Click to collapse
Just follow general guidelines. We already had testers and upgrading from 15.1 to 16.0 didn't cause any issues. Obviously, if you do run into an issue, it is suggested to clean flash first to see if it was a borked update

npjohnson said:
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.
Click to expand...
Click to collapse
Do you have a screenshot showing that it shows under screenlock settings?
Also what gaaps did you use when installing, I used the reccomended mindthegaaps and it kept giving me errors related to pixel apks.

link if image does not work
https://imgur.com/a/1eoVcgk
This is what shows under my screenlock setting, I do not have the setting that allows me to lock the phone using the fingerprint reader, this is from a fresh Lineage 15.1 installation with mindthegaaps, nothing else is installed on it. Had the same issue with lineage 16

Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.

Now I have installed los 16 and it was instructive for me. Learning by doing. After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP? I'm on slot b now and on system_a is nothing. If I want update later, I have to do just flash the zip over TWRP and then reboot it and then maybe flash gapps again, because it's the first update on slot_a? Hope that's works because the encoding problem. Don't have the key.

AmazerG said:
Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.
Click to expand...
Click to collapse
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
allrightlite said:
After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP?.
Click to expand...
Click to collapse
Remove your fingerprint and screen lock method prior to entering TWRP. If you came from a stock ROM you must format data before flashing LOS. Updates can be done automatically with the updater, or manually thru recovery. The latter requires more time with no added benefits. Also encryption is enabled with custom ROMs.

So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done

I have tries at this moment to update over the lineage updater in settings and it's stopping with installation error. After try to reboot to TWRP it's endet up in reboots. But LOS16 stats normally again after press power button a little bit. Now I try again to update. Presumably it isn't working again. I think I will reflash twrp first and try then over this to update. Good idea or what's going wrong on my phone?
I must do new install. All broken. Holy crap. Hope this time I get it working.

7bob said:
So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done
Click to expand...
Click to collapse
what are the steps to update from firmware 8.0 to LineageOS 15.1 or 16, please
unlock bootloader, twrp, magisk (no problem),
My phone locks the boot loader again when I try to install a custom ROM
my firmware (TWRP, magisk)
RETAIL/NASH_RETAIL_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
in any way I thank you :good:

Ok, I have found out how get it working. Updater app not working here, always installation error after end of update process. Don't know why. So now I have a way found out, which seems to be working every update. Go to TWRP, flash los16 new zip and, this is very important (understand it very late xD) don't forget to flash twrp installer zip directly after los 16, because otherwise on the other slot is the stock recovery again. So, after this boot to the other slot with twrp directly from your phone and flash gapps every time, every update. Here I forgot it and nothing of the play store and co. was working anymore. Android Framework ID was away, too. Is there an easier way to update over TWRP or do I have to do so? And what happend to, backup wasn't possible to restore, maybe cause thought encoding?
The new update process with A/B is not easy to understand directly But the rom is a beast, very very good. Why I update and switch to los16? That's easy, because the bluetooth bugs on stock oreo was terrible (and no 8.1-batterie icon ) and lags on few drm videos and here and there. Speed of the UFS-flash going slower and slower, no its 3 times faster again. This phone works really great with LOS16. Very good work! It's not easy to understand all, but I will get it in my brain
Edit: There is another point, which could be interesting. Netflix shows error on start up (15001) and this even though safety net is passed. Hm.. Have downloaded from play store. Maybe older version does do this job, don't know.

Ace42 said:
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
Click to expand...
Click to collapse
Is there anything different between Sprint Z2 force and Tmo ones in terms of hardware such as lack some band or what?

K20 Pro hard stuck in bootloader & No OS Installed & Guides didn't work

Hey,
I am in trouble with the K20 Pro (raphael). The first day I bought the device, I installed EU ROM v10.3.17.0 and used for a while. There was no problem. After that, I installed Magisk-v19.3.zip from TWRP and MagiskManager-v7.3.2.apk when Android booted. I just checked to see root privileges. I saw the ROOTED from the a root checker program. Afterwards, I had to transfer the IMEI number of my old phone to the new phone. Therefore, i updated the both IMEI numbers via COM port using WriteDualIMEI program. (adb shell -> su setprop sys.usb.config diag) Finally, I have a bootloop problem on my phone for 2 days. Android is not booting in any way.
What I have tried until now:
1. Installed xiaomi.eu_multi_HMK20ProMI9TPro_9.8.22_v10-10 on PitchBlack-raphael-2.9.0-20190708-0004 (Endless android booting stuck)
2. Format Data -> "yes" and Wipe Cache & Dalvik & System & Data & Vendor & Internal Storage and then installed xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.17.0.PFKCNXM_v10-9 (bootloop stuck)
3. I don't know in which situations but sometimes I get "No OS Installed! Are you sure you wish to reboot?" error after installing ROM.
4. Only happened once: Android booted and white spinning progress circle appeared at center on screen. After spinning for 60 seconds, it redirected to the TWRP menu.
Current status: I flashed Fastboot ROM (raphaelin_in_global_images_V10.3.5.0.PFKINXM_20190816.0000.00_9.0_in_5d0a303019) on Fastboot via MiFlash 2018..11.15.0. But i got "not catch checkpoint" error when the process is finished. It Redirected to Redmi-Recovery 3.0 screen. At the bottom of the screen, there was a error: NV data is corrupted
Is my device bricked? How can i fix that?
Thanks
Device: K20 Pro (raphael)
TWRP: 3.3.1-2
Fastboot
Unlocked
P.S: I apologize if there are grammatical errors.

Dentrax said:
Hey,
I am in trouble with the K20 Pro (raphael). The first day I bought the device, I installed EU ROM v10.3.17.0 and used for a while. There was no problem. After that, I installed Magisk-v19.3.zip from TWRP and MagiskManager-v7.3.2.apk when Android booted. I just checked to see root privileges. I saw the ROOTED from the a root checker program. Afterwards, I had to transfer the IMEI number of my old phone to the new phone. Therefore, i updated the both IMEI numbers via COM port using WriteDualIMEI program. (adb shell -> su setprop sys.usb.config diag) Finally, I have a bootloop problem on my phone for 2 days. Android is not booting in any way.
What I have tried until now:
1. Installed xiaomi.eu_multi_HMK20ProMI9TPro_9.8.22_v10-10 on PitchBlack-raphael-2.9.0-20190708-0004 (Endless android booting stuck)
2. Format Data -> "yes" and Wipe Cache & Dalvik & System & Data & Vendor & Internal Storage and then installed xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.17.0.PFKCNXM_v10-9 (bootloop stuck)
3. I don't know in which situations but sometimes I get "No OS Installed! Are you sure you wish to reboot?" error after installing ROM.
4. Only happened once: Android booted and white spinning progress circle appeared at center on screen. After spinning for 60 seconds, it redirected to the TWRP menu.
Current status: I flashed Fastboot ROM (raphaelin_in_global_images_V10.3.5.0.PFKINXM_20190816.0000.00_9.0_in_5d0a303019) on Fastboot via MiFlash 2018..11.15.0. But i got "not catch checkpoint" error when the process is finished. It Redirected to Redmi-Recovery 3.0 screen. At the bottom of the screen, there was a error: NV data is corrupted
Is my device bricked? How can i fix that?
Thanks
Device: K20 Pro (raphael)
TWRP: 3.3.1-2
Fastboot
Unlocked
P.S: I apologize if there are grammatical errors.
Click to expand...
Click to collapse
Try to fastboot flash MIUI 10.3.16.0 without locking bootloader.
I have no catch checkpoint error too but It automatically boots into MIUI.

overcustom said:
Try to fastboot flash MIUI 10.3.16.0 without locking bootloader.
I have no catch checkpoint error too but It automatically boots into MIUI.
Click to expand...
Click to collapse
How can i get MIUI Fastboot 10.3.16.0 ROM? I couldn't find here. I found the V10.3.8.0PFKCNXM Fastboot

Why do you play with IMEI numbers?

Dentrax said:
How can i get MIUI Fastboot 10.3.16.0 ROM? I couldn't find here. I found the V10.3.8.0PFKCNXM Fastboot
Click to expand...
Click to collapse
https://www.miui.com/shuaji-393.html
Scroll down and you will see k20 pro link. Just download it. Its from the official MIUI chinese site. You will only get the latest fastboot rom available. Right now its 10.3.16.0

Kollachi said:
Why do you play with IMEI numbers?
Click to expand...
Click to collapse
I just wanted to transfer my old phone's IMEI number.

Dentrax said:
I just wanted to transfer my old phone's IMEI number.
Click to expand...
Click to collapse
Hmm but why? I don't see any sense there.

Kollachi said:
Hmm but why? I don't see any sense there.
Click to expand...
Click to collapse
If the IMEI tax is expensive in your country, it makes sense.

theincognito said:
https://www.miui.com/shuaji-393.html
Scroll down and you will see k20 pro link. Just download it. Its from the official MIUI chinese site. You will only get the latest fastboot rom available. Right now its 10.3.16.0
Click to expand...
Click to collapse
Thank you, but;
Still same Nv data corrupted error. I think, i need to fix my IMEI and EFS partition first. :crying: I've been trying for two days.
{
"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"
}

Finally, I fixed that problem. I copied the EFS to TWRP/BACKUPS/your_serial_number/. i had previously backed up. I used the LR team's TWRP, see here. Thank you @theincognito
I installed this ROM via Fastboot, i don't like it. There are so many dipsh*t CN apps and fonts are weird. It's like I'm using the phone in two languages. I am thinking about to install 10.3.17 EU ROM, is that worthy? Or should i install 9.8.29 Q ? I just want everything to be stable, new and up-to-date. Thanks...

Dentrax said:
Okey, Finally, I fixed that problem. I copied the EFS to TWRP/BACKUPS/your_serial_number/. i had previously backed up. I used the LR team's TWRP, see here. Thank you @theincognito
I installed this ROM via Fastboot, i don't like it. There are so many dipsh*t CN apps and fonts are weird. It's like I'm using the phone in two languages. I am thinking about to install 10.3.17 EU ROM, is that worthy? Or should i install 9.8.29 Q ? I just want everything to be stable, new and up-to-date. Thanks...
Click to expand...
Click to collapse
Install EU. P or Q, its upto you. In my opinion, Q EU is stable enough.

theincognito said:
Install EU. P or Q, its upto you. In my opinion, Q EU is stable enough.
Click to expand...
Click to collapse
Do you mean EU Android Q 9.8.8 ? What is the difference between 10.3.17 and 9.8.8? Version went backwards but the Android is Q. Are the MIUI versions same?

Dentrax said:
Do you mean EU Android Q 9.8.8 ? What is the difference between 10.3.17 and 9.8.8? Version went backwards but the Android is Q. Are the MIUI versions same?
Click to expand...
Click to collapse
I mean, EU 9.8.22 Android Q. 10.3.17 and 9.8.22 are different.

Dentrax said:
Do you mean EU Android Q 9.8.8 ? What is the difference between 10.3.17 and 9.8.8? Version went backwards but the Android is Q. Are the MIUI versions same?
Click to expand...
Click to collapse
9.8.8 is beta rom, released on 201'9'-0'8'-0'8'
10.3.17.0 is stable miui 10 rom.
The reason latest beta rom seems backdated than stable rom because of the naming scheme. Beta roms actually has most recent elements than stable roms.

Dentrax said:
Finally, I fixed that problem. I copied the EFS to TWRP/BACKUPS/your_serial_number/. i had previously backed up. I used the LR team's TWRP, see here. Thank you @theincognito
I installed this ROM via Fastboot, i don't like it. There are so many dipsh*t CN apps and fonts are weird. It's like I'm using the phone in two languages. I am thinking about to install 10.3.17 EU ROM, is that worthy? Or should i install 9.8.29 Q ? I just want everything to be stable, new and up-to-date. Thanks...
Click to expand...
Click to collapse
How do you install the LR teams twrp? stuck in a similar situation with no OS, recovery, and stuck in a fastboot loop. miflash gives checkpoint error

Dentrax said:
If the IMEI tax is expensive in your country, it makes sense.
Click to expand...
Click to collapse
Holy cow excrement?! WTF? Why do they tax that thing when it's basically free for everybody else in the world?

plskillme said:
Holy cow excrement?! WTF? Why do they tax that thing when it's basically free for everybody else in the world?
Click to expand...
Click to collapse
Because, IMEI legal registration fee must be made for each phone that brought from abroad. It's about ~$266. And K20 Pro ~$345, Also %18 VAT, Also %25 Special Consumption Tax, Also %6 TRT Bandrol, And finally the base price $345, which is 1978₺ Turkish Liras, comes to an average of ~4500₺ Liras which is ~$785. I'm buying one for myself, and one for the government. If you take a phone from abroad and try to bring it into the own country, you have to pay ~618₺ Liras free to legal registration which is ~$110. Shortly, iPhone 11 Pro Max 512G ($1499) comes to $2614. Pêrfecto!

No IMEI, MAC, damaged sensors
I have the following problem:
I made a Nandroid backup with TWRP without knowing that I was not able to RESTORE, playing a bit for the system fell into Hard brickeo ... revived from there I only remain without working IMEI, Wifi and sensors. I cannot restore my backup since my TWRP could not, what I already did:
+ Flash Rom stock with MiFlash
+ Flash Persist.img with TWRP
My question is if I can restore that backup with a different TWRP and how can I do without dying since I tried and stayed dead once.

[ROM][RAV*/SOFIA*][11][UNOFFICIAL] PixelExperience (Plus) [AOSP]

{
"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"
}
PixelExperience for [RAV*/SOFIA*]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
Face unlock
Lights
Sound/vibration
Known issues
FM Radio
You tell me
Downloads
Link to Post
Installation
Link to Post
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: 11
Security patch level: November 2021
Build author/Device Maintainer: AbsoluteZeroEdge
Kernel Source: https://github.com/S4muel007/kernel_motorola_trinket
Device Source: https://github.com/ph4n70m-404/device_motorola_sofiar
Vendor Source: https://github.com/ph4n70m-404/vendor_motorola_sofiar
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Contributors
Vache for initial device and vendor sources + TWRP
ph4n70m & Beetle84 for tons of building help
S4muel007 for kernel
Thanks awesome peeps
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2021-11-20
Last Updated 2021-11-21

Download Links
TWRP
TWRP - Credit to Vache
https://drive.google.com/file/d/1SwiiptkODqLTnDF1GRknYrF2g2yPxdJY/view
Pixel Experience
11/20/2021 Build - Initial Build
https://drive.google.com/drive/folders/1pdStP6Rnph19wIu_plpDwjRa124yJvNK?usp=sharing
11/21/2021 Build - Added Moto Camera 2
https://drive.google.com/drive/folders/1dSnZUiuK5TlOEtZU8oQIbjjV-TxJgFyr?usp=sharing

Installation
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
FastbootD
1) Extract rom zip and open cmd prompt in the extracted folder
2) Reboot into fastbootd
Code:
fastboot reboot fastboot
3) Flash images
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
4) Format data
Code:
fastboot -w
5) Reboot, profit.
TWRP
1) Boot to bootloader
2) Flash TWRP (included download above)
Code:
fastboot flash recovery_a twrpfile.img
fastboot flash recovery_b twrpfile.img
3) Flash the rom
4) Format Data (not factory reset)
5) Reboot, Profit
5.1) (Optional) If magisk is desired flash it in TWRP after first boot

Reserved

I would like to try this but I have a question:
Is this rom for sofia or sofiar? The title of the post says sofia but the download link says sofiar.
which is it? I have the U.S. retail version of the Moto G Power, which is sofia.

classic757 said:
I would like to try this but I have a question:
Is this rom for sofia or sofiar? The title of the post says sofia but the download link says sofiar.
which is it? I have the U.S. retail version of the Moto G Power, which is sofia.
Click to expand...
Click to collapse
Yes it should work,
In the title it shows rav*/sofia* for wildcards meaning any rav*, or sofia* device

AbsoluteZeroEdge said:
Yes it should work,
In the title it shows rav*/sofia* for wildcards meaning any rav*, or sofia* device
Click to expand...
Click to collapse
Okay thank you. If I give it a try I will let you know how it goes.

I originally installed Beetle84's Havoc Rom, which he/she no longer supports, on my Moto G Power 2020 XT2041-4 using FlashbootD, but, soon, my battery life diminished until it barely lasted a day. So, I tried to flash the new Lineage 18.1, but it failed and I had to Rescue my device. It's now running the stock Android 11 (A!11) Rom. Other Cooks have suggested that I can't flash another Rom until I downgrade the device to A10, which I haven't been able to do. I wanted to try Vache's Moto Flash Tool, but I can't find instructions online. Do I have to downgrade to A10 to flash this Rom? If not, can I just follow the above instructions which are similar to Beetle84's instructions I successfully followed when I flashed his Havoc A11 Rom? Also, how does this Rom compare to Havoc?
Thanks

jhford said:
I originally installed Beetle84's Havoc Rom, which he/she no longer supports, on my Moto G Power 2020 XT2041-4 using FlashbootD, but, soon, my battery life diminished until it barely lasted a day. So, I tried to flash the new Lineage 18.1, but it failed and I had to Rescue my device. It's now running the stock Android 11 (A!11) Rom. Other Cooks have suggested that I can't flash another Rom until I downgrade the device to A10, which I haven't been able to do. I wanted to try Vache's Moto Flash Tool, but I can't find instructions online. Do I have to downgrade to A10 to flash this Rom? If not, can I just follow the above instructions which are similar to Beetle84's instructions I successfully followed when I flashed his Havoc A11 Rom? Also, how does this Rom compare to Havoc?
Thanks
Click to expand...
Click to collapse
unfortunately yes you have to downgrade to a10 for the rom to boot
for downgrade instructions it's rather self explanatory. just drop ur stock 10 firmware zip in the firmware folder and start the flash
after u downgraded just use the installation guide above
And for how it compares, Not sure. It's basically AOSP but with google apps, It's like havoc but more bare and made for pixel fans that want the pure pixel experience
if u want more features I would definitely point u towards ph4n70m's havoc build

AbsoluteZeroEdge said:
unfortunately yes you have to downgrade to a10 for the rom to boot
for downgrade instructions it's rather self explanatory. just drop ur stock 10 firmware zip in the firmware folder and start the flash
after u downgraded just use the installation guide above
And for how it compares, Not sure. It's basically AOSP but with google apps, It's like havoc but more bare and made for pixel fans that want the pure pixel experience
if u want more features I would definitely point u towards ph4n70m's havoc build
Click to expand...
Click to collapse
Thank you, but I don't understand this: "just drop ur stock 10 firmware zip in the firmware folder and start the flash." So, can you please give me specific downgrade instructions. I've tried and failed at least 6 times.

jhford said:
Thank you, but I don't understand this: "just drop ur stock 10 firmware zip in the firmware folder and start the flash." So, can you please give me specific downgrade instructions. I've tried and failed at least 6 times.
Click to expand...
Click to collapse
Well, in moto flash tool's root directory it has a firmware folder to place your device's stock firmware for it to flash, after that is done open up the tool and select the stock 10 package u placed

AbsoluteZeroEdge said:
Well, in moto flash tool's root directory it has a firmware folder to place your device's stock firmware for it to flash, after that is done open up the tool and select the stock 10 package u placed
Click to expand...
Click to collapse
I have done that both zipped and unzipped several times and it has always failed. Maybe I downloaded the wrong firmware. I got it from lolinet. Do you have a link for the correct A10 firmware for Moto G Power 2020 XT2041-4?
BTW, since I'm now stock A11, I used Nova Launcher v6.x - new.version 7.x is incompatible with many of my widgets - today.to make the UI look identical to my rooted and rommed Nexus 7 2013 deb tablets, and it's pretty livable. Plus, Android Auto now works perfectly and never did when the phone was rooted and rommed. Food for thought.
[Edit] I flashed Vache's TWRP. I'd be pretty happy if I could make a Nandroid backup of my current stock setup. Have you done that?
Thanks again

jhford said:
I have done that both zipped and unzipped several times and it has always failed. Maybe I downloaded the wrong firmware. I got it from lolinet. Do you have a link for the correct A10 firmware for Moto G Power 2020 XT2041-4?
BTW, since I'm now stock A11, I used Nova Launcher v6.x - new.version 7.x is incompatible with many of my widgets - today.to make the UI look identical to my rooted and rommed Nexus 7 2013 deb tablets, and it's pretty livable. Plus, Android Auto now works perfectly and never did when the phone was rooted and rommed. Food for thought.
[Edit] I flashed Vache's TWRP. I'd be pretty happy if I could make a Nandroid backup of my current stock setup. Have you done that?
Thanks again
Click to expand...
Click to collapse
What's Moto Flash Tool's output? And I can't really decide the correct firmware for you phone, u need to see what software channel your phone is and select it here: https://mirrors.lolinet.com/firmware/motorola/sofia/official/
for nandroid backup well I'm not really sure, haven't done one before. a quick google search should do something for you.

AbsoluteZeroEdge said:
What's Moto Flash Tool's output? And I can't really decide the correct firmware for you phone, u need to see what software channel your phone is and select it here: https://mirrors.lolinet.com/firmware/motorola/sofia/official/
for nandroid backup well I'm not really sure, haven't done one before. a quick google search should do something for you.
Click to expand...
Click to collapse
Here's how I used Moto Flash Tool (MFT). Pasted A10 firmware in firmware folder. Connected phone in bootloader mode. Double clicked the MFT exe. A blank DOS window popped up and disappeared. That's it.

jhford said:
Here's how I used Moto Flash Tool (MFT). Pasted A10 firmware in firmware folder. Connected phone in bootloader mode. Double clicked the MFT exe. A blank DOS window popped up and disappeared. That's it.
Click to expand...
Click to collapse
make sure it's in a path with no spaces, i recommend putting it in a folder with of course no spaces again on any drive's root

AbsoluteZeroEdge said:
make sure it's in a path with no spaces, i recommend putting it in a folder with of course no spaces again on any drive's root
Click to expand...
Click to collapse
I followed you suggestion and only moved the folder to the root of C:\ that hosts the exe and the firmware, etc. folders. I double clicked the exe and for the first time, a usable batch file DOS window opened. So, it appears that I have a working setup. However, I'm going to think about rooting/romming this phone again, because I don't want to lose Android Auto (AA) again. But AA only works with a USB wired connection in my car, and I ordered an AAWireless device which should obviate the wired connection and allow my rooted/rommed phone to connect. I'll test it, and, if so, I'll flash your Rom Immediately.
Thanks for putting up with me.

I flashed this rom to my retail Moto G Power (2020) that was purchased from Google Fi. I make it to the Google logo screen on boot and it just sits there with the progress bar perpetually scrolling. Any advice?

NobleX13 said:
I flashed this rom to my retail Moto G Power (2020) that was purchased from Google Fi. I make it to the Google logo screen on boot and it just sits there with the progress bar perpetually scrolling. Any advice?
Click to expand...
Click to collapse
First boot usually takes a while, if it hasn't booted within 10 minutes it's stuck. Make sure you did a Format and not only a Wipe as well

Thanks. Upon further inspection when I executed a fastboot -w it wiped the data partition but did not format it. I'll try this again as time permits.
AbsoluteZeroEdge said:
First boot usually takes a while, if it hasn't booted within 10 minutes it's stuck. Make sure you did a Format and not only a Wipe as well
Click to expand...
Click to collapse

NobleX13 said:
Thanks. Upon further inspection when I executed a fastboot -w it wiped the data partition but did not format it. I'll try this again as time permits.
Click to expand...
Click to collapse
Yeah, fastboot -w usually has problems. Good luck!

Question How to root Redmi Note 11?

Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
{
"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"
}

The first step is to unlock your bootloader which usually takes a week. Do that first, then you can browse more and wait for answers while you wait

I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img

parker_04 said:
Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
View attachment 5807325
Click to expand...
Click to collapse

notBradPitt said:
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img
Click to expand...
Click to collapse
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.

parker_04 said:
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.
Click to expand...
Click to collapse
I think this sums it pretty well: https://forum.xda-developers.com/t/installing-miui-eu-rom-and-root.4426937/
- Backing up data: Back up your data so it won't be lost during bootloader unlock
- Unlock bootloader: allows you to flash into your phone
- Flashing Xiaomi.eu (optional): Their ROM is based on MIUI Global/China which has way more features than region based ROMs and no bloatware. Cons is you have to manually update it and you can't update system apps (as they're also modified to disable ads). Pros is, you know the version you just flashed and the boot.img is also there.
- Finding boot.img: This is the file you want to patch if you want to root your phone. You can find this by extracting the fastboot ROM and it should be inside. In case of stock MIUI, you have to download the exact version that you have right now on https://xiaomifirmwareupdater.com/ , get the flashboot version, extract, and boot.img should be inside
The rest should be explained in the post above and I think this will also help in installation of Magisk https://topjohnwu.github.io/Magisk/install.html

@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download

parker_04 said:
@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download
Click to expand...
Click to collapse
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)

notBradPitt said:
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)
Click to expand...
Click to collapse
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.

parker_04 said:
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.
Click to expand...
Click to collapse
No problem How do you like it? Have you proceeded with root yet?

notBradPitt said:
No problem How do you like it? Have you proceeded with root yet?
Click to expand...
Click to collapse
It's nice.
Xiaomi eu is certainly cleaner than stock. Adless and bloatless. It has new features although some of the stock's features are missing. Play Store is jittery for unknown reasons.
And when I try to open a file in another app, the app list appears quite late and it's laggy too. But that's all and I don't mind it.
Thanks again for recommending it.

notBradPitt said:
Have you proceeded with root yet?
Click to expand...
Click to collapse
Yeah. Rooting with magisk is so easy. And it's uninstallation is easy too.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?

creepystaircase66 said:
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?
Click to expand...
Click to collapse
Yes, data is only needed when you request for permission

Assuming you have unlocked the bootloader
Step by Step Guide:
1. Download Magisk APK and install it
2. Patch your Recovery (Stock, TWRP, Skyhawk, etc) in magisk app and copy the patched img to Computer
3. Switch it off, then boot to bootloader, and type "fastboot flash boot recovery_patched.img" where recovery_patched.img is your file name.
4. Reboot (Might take longer than usual) and open magisk to confirm the the result of actions.

[SM-A600FN] AOSP 12 / TWRP / Rooting issues

I wanted to get my A6 working again to use as our home unit for my son to use sometimes.
I saw there is AOSP 12 for the A6 available so I decided to get android 12 on my A6 (was still on the stock Android 10).
However, I have been busy for days now and still have not succeeded. In fact: I just flashed stock Android 10 on my A6 again.
I used a guide to get AOSP 12 op my A6. necessary step 1: flash TWRP.
That was in fact the only step that worked directly.
Step 2 was flashing some other files RMM, no encrypt). And then came in Magisk v18.1 (especially this version to prevent my a6 from boot loop).
But then the trouble started. It didn't work. I don't know where exactly, but I encountered an error 8 and ran into 'cannot mount /data' errors.
I finally fixed this (wiping /data and changing file system tot fat or exfat and after wiping, changing it back) and continued.
Then I still ran into error 1 errors. I found out it had something to do with boot.img and "was very easy to fix". I only needed boot.img. The suggested methods all didnt work (twrp backup of /boot didn't give me anything usable). ADB didnt'work (device unauthorized) and something more. I read somewhere else that rooting wasn't needed, I could flash AOSP12 without rooting so I flashed the AOSP 12 img file with TWRP. After succesfully flashing.... it didn't work. So for now, I flashed Android 10 stock again, but I'm more then frustrated that I didnt succeed in flashing AOSP 12 and starting it properly.
I simply cannot understand that it can be so hard to get where you want to be. And I don't understand people make statements in guides that it is "really simple" to fix an issue (only 4 steps or so) but forget to mention it might me more or less difficult to get the needed file (boot.img) to do so.
One other page had a guide to flash AOSP 12 using ADB. I only need system.img and vbmeta.img. But they don't tell where to get those .img files....
Am I just dumb and stupid or do these guides lack some essential info?

Probably the only way to have Android 12 on A600FN is to use Generic System Images. However it's not perfectly stable. Android 11 probably still will be more comfortable in everyday usage. To flash GSI on A600FN follow this guide. Just remember to choose image in right architecture (it needs to be arm32_binder64). Root isn't needed for that at all. What's more, some GSI's are prerooted already. But if you need Magisk, then use latest version.
Btw, after flashing custom recovery you didn't need such messing with partitions - you need just to do FORMAT (not wipe) /data partition (and reboot custom recovery after that).

Thanks for replying. I am still wondering why we need arm32 as the a6 has/uses arm64 instruction set, isn't it?
I will look for Android 11.
I had to mess around so much because everything didn't work as it should be, according to the guides. I guess Murphy's Law had a great time messing with me and my growing frustration. I flashed TWRP now. I immediately checked if just formatting would be enough but when I try to , I get an error message: unable to mount /data.
That is why I changed it to fat and back. (after that it worked).
update: Flashed android 11 and its working fine now.

DutchArjo said:
Thanks for replying. I am still wondering why we need arm32 as the a6 has/uses arm64 instruction set, isn't it?
Click to expand...
Click to collapse
Yes, exynos 7870 has 64-bit intructions. but it needs 64-bit vendor to run arm64 system images. Samsung's stock firmware works on arm32_binder64 vendor on A600FN. There are available unofficial arm64 vendors for A600FN, but they are definitely less stable than the stock one.

Excuse me uhm is there any latest custom kernel for my andriod 10 a600g? Canu send link pleasd wanna have my phone performance to the fullest

John072021 said:
Excuse me uhm is there any latest custom kernel for my andriod 10 a600g? Canu send link pleasd wanna have my phone performance to the fullest
Click to expand...
Click to collapse
Just try H-Kernel for A600X or Ares for A600X:
Kernels - 7870 - Google Drive
drive.google.com

Thankyou that help a lot, would you suggest a gsi rom for my a600g? Does not matter what andriod version it is 10,11,12 just a stable rom for everyday usage, Thanks

Radical and jynx os not really stable on a600g, i would really appreciate if you would help me,

John072021 said:
Radical and jynx os not really stable on a600g, i would really appreciate if you would help me,
Click to expand...
Click to collapse
For me really stable was Lineage R mod (arm32_binder64) and it should be still okay, but you can try to use any still maintained Android 11 (arm32_binder64) with that vendor. List of GSI's:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Just try various Android 11 GSI projects.

A64? Same with arm32_binder64?

I cant really find like: a64_agN-lite
My devices says i only had a partition

John072021 said:
A64? Same with arm32_binder64?
Click to expand...
Click to collapse
Yes, A64 = arm32_binder64. arm64 needs different vendor files.
John072021 said:
I cant really find like: a64_agN-lite
My devices says i only had a partition
Click to expand...
Click to collapse
Use A/B build. So this one should work fine:
https://sourceforge.net/projects/treblerom/files/LiR/2022.03.25/lir-v316-220325-a64-bgZ-lite.img.xz/download

{
"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 got it

Is your device a600fn?

Yes, I have A600FN.
John072021 said:
i got it
Click to expand...
Click to collapse
Then decompress and flash as system image in custom recovery. Flash of course also vendor linked above.

I just want to make suke, mine is a600g? Is it tested? In a600g?
How did you install fox recovery in your a6fn?

John072021 said:
I just want to make suke, mine is a600g? Is it tested? In a600g?
Click to expand...
Click to collapse
Should work fine also on A600G - just test yourself. Make backup in recovery of partitions system, data, vendor, boot. In case something won't work properly just restore that backup in recovery.
John072021 said:
How did you install fox recovery in your a6fn?
Click to expand...
Click to collapse
Just flash OrangeFox zip file in TWRP and reboot to recovery again. But you can use your TWRP if it is in version higher than 3.4.0-0.