Database Info

[cofface] [3.1.1-0]Twrp recovery for Huawei Nova2

Hi guys,
I made the TWRP from TeamWin official sources for Huawei Nova2 . You can download the img and flash it from fastboot.
Bootloader unlocked required!
Installation:
Unlock bootloader (skip if you have already unlocked it)
Reboot into fastboot mode
Flash using
Code:
HTML:
fastboot flash recovery cofface_pic_al00_recovery_en.img
Reboot
Download:
AndroidFileHost
Bugs:
When device is encrypted you can't see the files into recovery
Let me know if there are others
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc:fingers-crossed:
PAYPAL DONATION LINK
email:[email protected]

Unfortunately It is not working!
After flashing your file there is still the Huawei EMUI Bootloader and no TWRP. Bootloader was unlocked before. Fastboot was working fine.
Any idea?

Problem with Google GAPPS
Hi,
Thank you for your tuto and your ROM
I have bought my nova 2 in china.
Do you know how to install GAPPS. I have tried different version (stock, pico,.. ) but it's no use.
Do you know if I have to change the region first ?
Is it ok with your ROM ?
Regards

Perfect
Perfect, thank you!

Not working
Hello,
TWRP ist not working for me, I still have the EMUI bootloader after flash and reboot.
Boot into TWRP Recovery ("fastboot boot cofface_pic_al00_recovery_en.img") is aborted with:
"FAILED (remote: Command not allowed)"
Is there anything I've done wrong?
Thx!

dr.luther.1517 said:
Perfect, thank you!
Click to expand...
Click to collapse
did it work with your Nova 2?

i have got a demo device ( from germany ). Can some one upload his OEM info for a normal device ?
And yeah... it works

Success
Works very well, Thanks !
But ... while playing with it I lost the stock ROM for my Huawei Nova 2.
Since there is no download source available, could anybody share a stock ROM backup so I could restore using Twrp ?
Thanks !

My Nova 2 (PIC-LX9C432) automatically encrypts the disk after the first run, and then TWRP is unable to read /data partition nor do nandroid backups as a result. Can someone guide on how to disable encryption or get TWRP to decrypt data.
I read elsewhere that newer versions of TWRP are able to decrypt if you set a password / screen lock.

WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034

jusma said:
WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034
Click to expand...
Click to collapse
Perhaps you could get some tips from nova (1) thread there we had the same problems. But so long we have a working twrp with backup possibility.

Hi, i used this Twrp, but did not notice the error mesaje when i "create" a back up for all my data, then when deleting some things, i went off the road and ended deleting the complete operative system, and know i dont seem to be able to find a room for my phone is a huawei p10selfie(in my country) or huawei nova 2 plus (in the rest of the world) model BAC-L03, sry if i dont use the correct words, since english is not my native lenguaje

I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?

iamramanlmc said:
I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?
Click to expand...
Click to collapse
Nova 2i is Mate 10 Lite! https://forum.xda-developers.com/ma...e--roms-kernels-recoveries--other-development

{
"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"
}

[RECOVERY][3.4.0-0][doha]Unofficial TWRP recovery for Moto G8 Plus (Testing)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decrypt works
- Removed TWRP app
- Backup still have some problems use it carefully
- Fastboot boot works
- Touch works
- Vibration works
- Rom Flashing
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Other Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
{
"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"
}
8. Choose the recoveryimgfilename.img
9. Swipe to install
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
TWRP 3.4.0-0 Unofficial by mauronofrio
TWRP 3.4.0-0 Unofficial Installer by mauronofrio
TWRP 3.3.1-23 Unofficial by mauronofrio
TWRP 3.3.1-23 Unofficial Installer by mauronofrio
TWRP 3.3.1-19 Unofficial by mauronofrio
TWRP 3.3.1-19 Unofficial Installer by mauronofrio
TWRP 3.3.1-17 Unofficial by mauronofrio
TWRP 3.3.1-17 Unofficial Installer by mauronofrio
TWRP 3.3.1-16 Unofficial by mauronofrio
TWRP 3.3.1-16 Unofficial Installer by mauronofrio
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_motorola_doha
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
Thanks to @ath0 for hard testing
Thanks to vache for the help with touch fix
Thanks to @Electimon for some tips
Created 2020-02-27

TWRP 3.3.1-17 Motorola Moto G8 Plus (doha) by mauronofrio:
- Fixed touch for focaltech panels.
TWRP 3.3.1-17 Unofficial by mauronofrio
TWRP 3.3.1-17 Unofficial Installer by mauronofrio

Rom updates

TWRP 3.3.1-19 Motorola Moto G8 Plus (doha) by mauronofrio:
- Fixed Rom flashing;
- Partially fixed format data.
TWRP 3.3.1-19 Unofficial by mauronofrio
TWRP 3.3.1-19 Unofficial Installer by mauronofrio

sorry for my bad English..
so... if I want to stay in the stock rom and install TWRP, the only way is to root with magisk?
and after that the stock ROM rooted with magisk will be stable to daily use?

Hello thanks for the TWRP recovery port. It works great!
Now, a few days after I flashed it. Motorola pushed a firmware or security update . I didn't install it yet but I would like to. I think I have to go back to stock recovery in order to install the update. Might you have a guide on how to do this? I already have the stock rom downloaded but I don't know how to get the stock recovery

When flashing the installer or using the "Install Recovery Ramdisk" method, the touchscreen won't work

Hello,
I've got a Moto G8 Plus which I rooted using Magisk after unlocking the bootloader. It works just fine as it is, but I would like to install TWRP so I can have a backup of it. However, I'm afraid of installing TWRP and breaking something or losing the root.
Can I flash this version of TWRP over a Moto G8 Plus already rooted with Magisk without losing root or breaking Magisk or something else?

irex102 said:
Hello thanks for the TWRP recovery port. It works great!
Now, a few days after I flashed it. Motorola pushed a firmware or security update . I didn't install it yet but I would like to. I think I have to go back to stock recovery in order to install the update. Might you have a guide on how to do this? I already have the stock rom downloaded but I don't know how to get the stock recovery
Click to expand...
Click to collapse
That is just a security update let it be it will **** things up trust me

Hi there,
Thanks for your efforts puling together a TWRP for our phones!
I've got a question because I'm not quite clear about your response to the previous question about the security update. I've been using the stock recovery, rooted with Magisk and went through the whole process of accepting the security update and then re-rooted etc.
Will I wind up F'ing up my phone if I go to install your TWRP since I've already accepted the security update? Or would I be better off just compiling TWRP on my own ( it'll be my first foray into that area ) taking that route instead?
Any and all opinions welcome

Hamaruka said:
When flashing the installer or using the "Install Recovery Ramdisk" method, the touchscreen won't work
Click to expand...
Click to collapse
Same issue here. Works only when I fastboot boot off my laptop.

did not work for my phone, Moto G8 Power purchased 4/17/2020 fully unlocked bootloader, no root, attempted to boot to img, failed to boot.
[email protected]
sorry im doing a lot of research and looking, i basically accidentally soft bricked my phone, my wife and i have the exact same phone, and i cant seem to pull the factory images from it, nor can i make the various versions of OEM recovery images or boot loaders function on the phone.
maybe im just doing something wrong. pardon the typos.

FoxDroid1214 said:
did not work for my phone, Moto G8 Power purchased 4/17/2020 fully unlocked bootloader, no root, attempted to boot to img, failed to boot.
[email protected]
sorry im doing a lot of research and looking, i basically accidentally soft bricked my phone, my wife and i have the exact same phone, and i cant seem to pull the factory images from it, nor can i make the various versions of OEM recovery images or boot loaders function on the phone.
maybe im just doing something wrong. pardon the typos.
Click to expand...
Click to collapse
I have played a little with Moto G8 Plus (XT2019-1). And i'm not worried about brick it. Have done a few times, but always recovered with blankflash.. After blankflash it will start bootloader, and then i can flash stock firmware. I found Stock FW and also blankflash on lolinet. I prefer using Fastboot for flashing. Don't need TWRP for flashing. Have locked, and Unlocked bootloader many times..
If needed, i can make a description on how to use blankflash as it can be hard to get started..
Check lolinet for stock FW and blankflash.. You need to know code name for your phone..
mirrors.lolinet.com/firmware/moto/

can i flash latest magisk straight through twrp? or does it have to be the patch boot process?

Allright, I installed successfully TWRP (install to ramdisk) and Magisk, rooted phone is fine etc, but when I boot into recovery again touch does not work and I am stuck in bootloop into recovery until I flash both again. Any hints?

hendrack said:
Allright, I installed successfully TWRP (install to ramdisk) and Magisk, rooted phone is fine etc, but when I boot into recovery again touch does not work and I am stuck in bootloop into recovery until I flash both again. Any hints?
Click to expand...
Click to collapse
Seems a common bug, i need someone with which test this thing

What would testing imply?

My guess would be: flashing experimental twrp, praying it doesn't brick your phone, reading logs?

mauronofrio said:
Seems a common bug, i need someone with which test this thing
Click to expand...
Click to collapse
The same error any solution?

I could help by flashing the recoverys and submitting the logs but beyond that I'm helpless

[ROM][OFFICIAL] LineageOS 17.1 [evert]

{
"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"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Introduction:
This is the Official LineageOS 17.1 thread for the Moto G6 Plus, codename evert.
Information:
Official Wiki || https://wiki.lineageos.org/devices/evert
Installation
How-to || https://wiki.lineageos.org/devices/evert/install
Downloads:
Builds || https://download.lineageos.org/evert
XDA:DevDB Information
LineageOS 17.1, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Android Pie (9.0) Stock Firmware

Reserved

Reserved

what's wrong with my phone and how do I fix it when installing lineage17.1 ....? Because I always lose IMEI and Wi-Fi and I can never recover (is restarting alone too) only on 17.0..(only lineage 17.0 I can recover IMEI and Wi-Fi) And going back to stock 9 I also can't...
Thanks for the project and support!
(Google Translator)

SamuelYNWA said:
what's wrong with my phone and how do I fix it when installing lineage17.1 ....? Because I always lose IMEI and Wi-Fi and I can never recover (is restarting alone too) only on 17.0..(only lineage 17.0 I can recover IMEI and Wi-Fi) And going back to stock 9 I also can't...
Thanks for the project and support!
(Google Translator)
Click to expand...
Click to collapse
Sounds to me like your /persist partition is full.
Check this thread for more info, including how to fix it so you can get back to flashing ROMs or stock or whatever you want [emoji6]

Thaaaaaaankssss.
It worked

Okay, tried to upgrade, while I tried from the default Android Recovery that came with LOS 16, I got this error:
Code:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch)
E:Error in /sideload/package.zip (Status 1)
So then I tried to boot TWRP from an image through ADB and did the ADB sideload from there. It seemed to have gone well, with the exception at the end, where it complained that it could not find the /cache partition. (I've chose in TWRP to wipe the Dalvik and normal cache, so I assumed it wasn't a big problem).
After rebooting, I noticed the phone was stuck at the boot animation (the one with the swiping circle) and did not progress from it after leaving it 20+ minutes. I then tried to boot into recovery, and I did notice the new Lineage recovery. I tried doing an ADB sideload from there, but that also gave me an error with the signature mismatch. I then booted yet again into TWRP to try to install the zip file through TWRP directly as I have downloaded the zip files to the phone storage. While trying to access the phone's storage (data partition), I noticed all the folders and files had garbled filenames (random strings of letters and numbers). So then I went on to download the zip file again on an mSD card, and tried installing it through TWRP, and after restarting, I still am stuck at the boot logo.
Considering the filenames in the data partition were garbled, I assume it has something to do with the fact that the data on the phone was previously encrypted, and the upgrade didn't take that into account. Also noticed that on the second time I booted into TWRP, it no longer asked for the encryption pattern/PIN as it did prior to the upgrade.
Are there any steps I can take to fix this?
EDIT: If it requires wiping the data partition, is there some method of recovering the data?

Any big changes from the unofficial (at the time) 03/12 build? (I think that's the one I flashed last week)

From stock g6+ RETEU XT1926-3_EVERT_RETEU_DS_9.0_PPWS29.116-20-16
Steps taken:
0. fastboot set_active a
1. fastboot flash boot_a lineage-17.1-20200403-recovery-evert.img
2. Reboot to new recovery
3. adb sideload copy-partitions.zip
3. Factory Reset / Wipe Data + Wipe System from Recovery
4. adb sideload lineage-17.1-20200403-nightly-evert-signed.zip
5. reboot from recovery
Failed Result:
At this point usb-c cable is still connected and lineage continues to load
After asking for simcard pin and proceeding through lineage initial setup (date time etc.) cellular radio is disconnected and unable to connect no matter what. The IMEI is in place, the sim is detected and unlocked with pin code. Tested with single and dual sims in all configurations, phone purchased new in Germany, Vodafone.de sims.
The wifi works fine.
Almost immediately after unplugging the usb-c cable the shutting down spin dialogue appears and the phone reboots to recovery "Can't load Android system. Your data ma......"
Eventually the phone boots again but if the usb-c cable is not connected it shuts itself down within 30 seconds of booting, and the modems continue refusing to connect.
After reflashing the stock rom XT1926-3_EVERT_RETEU_DS_9.0_PPWS29.116-20-16 everything works fine as normal, stability and connectivity returns.
Same thing happens if open_gapps-arm64-10.0-nano-20200403.zip is sideloaded.
Any tips?

dm-verity" warning at boot
Hello to you,
Is there a way to get rid of dm verity warning at boot after flashing lineage os v17.1, rom works verry good,
Have not seen any problems yet, using with minimal google gapps.
Thank you

Hi there. First, I'd like to thanks to Jleeblanch for the great job of bring the experience of Android 10 to the oldschool Moto G6 Plus!
The ROM is awesome, I really like it. The only feature that is not working for me is the mobile network (mobile data). The first release (April's 1) had the bug of the sound calling that wasn't working, but it was done after the nightly update. So, could you please fix the mobile data bug?
Thank you in advance. Great job!

riancarlos18 said:
Hi there. First, I'd like to thanks to Jleeblanch for the great job of bring the experience of Android 10 to the oldschool Moto G6 Plus!
The ROM is awesome, I really like it. The only feature that is not working for me is the mobile network (mobile data). The first release (April's 1) had the bug of the sound calling that wasn't working, but it was done after the nightly update. So, could you please fix the mobile data bug?
Thank you in advance. Great job!
Click to expand...
Click to collapse
Try changing your preferred network type. When i flashed my phone it said "Global" and had no signal, but then i changed it to GSM/WCDMA/LTE and everything it's working except for VoLTE

La rom está perfectamente funcionando , aunque no inicia si se instala pixel gapps

hmillos said:
Try changing your preferred network type. When i flashed my phone it said "Global" and had no signal, but then i changed it to GSM/WCDMA/LTE and everything it's working except for VoLTE
Click to expand...
Click to collapse
I've tried to change the network type to GSM/WCDMA/LTE, but it didn't work, among others, but it all fails. After that, I did an update to April's 4 nightly version that just came out (with the change "sdm660-common: Force enable mobile network settings v2"), but nothing happens here. My G6 Plus stills lacking the mobile data.
Thank you for trying to help. Still waiting for a solution :good:

andoruB said:
Okay, tried to upgrade, while I tried from the default Android Recovery that came with LOS 16, I got this error:
So then I tried to boot TWRP from an image through ADB and did the ADB sideload from there. It seemed to have gone well, with the exception at the end, where it complained that it could not find the /cache partition. (I've chose in TWRP to wipe the Dalvik and normal cache, so I assumed it wasn't a big problem).
After rebooting, I noticed the phone was stuck at the boot animation (the one with the swiping circle) and did not progress from it after leaving it 20+ minutes. I then tried to boot into recovery, and I did notice the new Lineage recovery. I tried doing an ADB sideload from there, but that also gave me an error with the signature mismatch. I then booted yet again into TWRP to try to install the zip file through TWRP directly as I have downloaded the zip files to the phone storage. While trying to access the phone's storage (data partition), I noticed all the folders and files had garbled filenames (random strings of letters and numbers). So then I went on to download the zip file again on an mSD card, and tried installing it through TWRP, and after restarting, I still am stuck at the boot logo.
Considering the filenames in the data partition were garbled, I assume it has something to do with the fact that the data on the phone was previously encrypted, and the upgrade didn't take that into account. Also noticed that on the second time I booted into TWRP, it no longer asked for the encryption pattern/PIN as it did prior to the upgrade.
Are there any steps I can take to fix this?
EDIT: If it requires wiping the data partition, is there some method of recovering the data?
Click to expand...
Click to collapse
Try to wipe/format data/
Those numbers and that **** it means that all your OS is encrypted in your device, solution? Try to use ADB Sideload and install everything you need, Bootlogo, gapps, magisk, etc,

Boot problem
ORWPBE0I0lcloXXWctG2 said:
From stock g6+ RETEU XT1926-3_EVERT_RETEU_DS_9.0_PPWS29.116-20-16
Steps taken:
0. fastboot set_active a
1. fastboot flash boot_a lineage-17.1-20200403-recovery-evert.img
2. Reboot to new recovery
3. adb sideload copy-partitions.zip
3. Factory Reset / Wipe Data + Wipe System from Recovery
4. adb sideload lineage-17.1-20200403-nightly-evert-signed.zip
5. reboot from recovery
Failed Result:
At this point usb-c cable is still connected and lineage continues to load
After asking for simcard pin and proceeding through lineage initial setup (date time etc.) cellular radio is disconnected and unable to connect no matter what. The IMEI is in place, the sim is detected and unlocked with pin code. Tested with single and dual sims in all configurations, phone purchased new in Germany, Vodafone.de sims.
The wifi works fine.
Almost immediately after unplugging the usb-c cable the shutting down spin dialogue appears and the phone reboots to recovery "Can't load Android system. Your data ma......"
Eventually the phone boots again but if the usb-c cable is not connected it shuts itself down within 30 seconds of booting, and the modems continue refusing to connect.
After reflashing the stock rom XT1926-3_EVERT_RETEU_DS_9.0_PPWS29.116-20-16 everything works fine as normal, stability and connectivity returns.
Same thing happens if open_gapps-arm64-10.0-nano-20200403.zip is sideloaded.
Any tips?
Click to expand...
Click to collapse
I did the same as you, after flashing lineage os 171, i flashed minimal google gapps, then teset the phone from within recovery. I came from stock pie eu version, dual sim phone. I have used lineage recovery to flash lineage os v17.1, no problems at all with rom, only boot message is nerving.

charwed said:
I did the same as you, after flashing lineage os 171, i flashed minimal google gapps, then teset the phone from within recovery. I came from stock pie eu version, dual sim phone. I have used lineage recovery to flash lineage os v17.1, no problems at all with rom, only boot message is nerving.
Click to expand...
Click to collapse
Out of curiosity which 17.1 build did you flash exactly? 20200403? Did you use nano or micro gapps? XT1926-3 is your model no?
I had 2, what appeared to be separate problems:
the usb-c disconnect shutdown which is independent of sims card configuration
the 2x modems not enabling
Neither of which were present when re-flashing stock eu retail, and I went back and forth 3 times to confirm.
I can't understand if it was a problem with the modem partition or other firmware partitions, as those don't get touched when you sideload Lineage? Only Boot + System correct?

ORWPBE0I0lcloXXWctG2 said:
Out of curiosity which 17.1 build did you flash exactly? 20200403? Did you use nano or micro gapps? XT1926-3 is your model no?
I had 2, what appeared to be separate problems:
the usb-c disconnect shutdown which is independent of sims card configuration
the 2x modems not enabling
Neither of which were present when re-flashing stock eu retail, and I went back and forth 3 times to confirm.
I can't understand if it was a problem with the modem partition or other firmware partitions, as those don't get touched when you sideload Lineage? Only Boot + System correct?
Click to expand...
Click to collapse
did you flash the copy-partitions.zip ?

Info about flashed rom
i have used the one dated april 4
from the official lineage website, now i have updated to
lineage_evert-userdebug 10 QQ2A.200305.003 dfee070f5c. i did used the
minimal gapps beta. package. from the cyanogenmod website. i did flashed copy partitions AB after flashing lineage recovery from the official lineage website.

hmillos said:
did you flash the copy-partitions.zip ?
Click to expand...
Click to collapse
Yep, the first thing I did after entering the recovery, and it appeared to succeed each time.
I saw in the changes from 0403 to 0404 version:
sdm660-common: Update to clean Jasmine qti-telephony-common android_device_motorola_sdm660-common
sdm660-common: Force enable mobile network settings v2 android_device_motorola_sdm660-common
Sounds like it could be related, so maybe that fixed it, will test later.

[SOLVED] Poco X3 NFC - Bootloop after Wiping & Flashing Custom ROM

Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you

DrakMC said:
Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you
Click to expand...
Click to collapse
You didn't explain your Problem quite well. Does it reboot to fastboot or does it reboot to system? (aka a Bootloop). if it reboots to system, here's what to do:
Boot into a custom recovery (twrp/Orangefox) and flash the required recovery MIUI ROM mentioned in your custom ROM's thread instructions.
Flash the custom ROM/Gapps, followed by Formatting /data using the Advanced Options in the wipe menu.
Reboot.
If you can't find the format option (which is mandatory before a new boot of a custom ROM), you can use this command while in fastboot mode:
Code:
fastboot erase userdata
Formatting /data is required for Encrypted devices to reset the encryption key and avoid a Bootloop. Please refer to this thread for more Custom ROM flashing instructions. If all else fails, you could EDL flash your device through MI flash tool/Command line, this process costs money (you need an Authorized Xiaomi Account) to complete.

Thank you very much for your help!
Slim K said:
Does it reboot to fastboot or does it reboot to system? (aka a Bootloop).
Click to expand...
Click to collapse
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)

DrakMC said:
Thank you very much for your help!
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)
Click to expand...
Click to collapse
Again, when I say FORMAT, I meant formatting by typing ”yes".
Also, you haven't looked at the ArrowOS thread close enough, see:
{
"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"
}
It says latest R firmware, basically V12.0.7.0.RJGEUXM. Another point I mentioned is the fact that a recovery MIUI is flashable through TWRP/Orangefox and not Fastboot/Mi flash tool, It comes in a .zip archive.
Regarding returning to stock, have you tried booting into stock recovery after fastboot flash and factory resetting? That could work.

Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
I'm using TWRP 3.5.2_10-1-surya.

DrakMC said:
Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
View attachment 5307411
I'm using TWRP 3.5.2_10-1-surya.
Click to expand...
Click to collapse
Error 1 just means a mismatch between the underlying stock and the newly flashed ROM, just ignore it and flash ArrowOS, Format data and reboot. If it still doesn't work, then return to stock through fastboot. (I never encountered so many problems as you did)

I followed your instructions. When I turn on smartphone, the Poco logo is displayed, then the ArrowOS animation will appear and freezes. After a while, the mobile phone restarts and this is repeated over and over again. (If I flash MIUI using the Mi Flash Tool, I also have a bootloop.)

I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!

just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!

sevachcomunist4 said:
just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!
Click to expand...
Click to collapse
You're welcome! I'm glad I could help someone! It took me about 40+ hours to resolve this issue before trying all possible methods.

DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
please give me link

DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.

DP FH said:
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.
Click to expand...
Click to collapse
You are welcome. I'm glad I could help someone.
I was whole week without the phone until I've fixed it. It took me over 40 hours to fix the issue.

screen not registering inputs after update to LineageOS 19.1

So I performed the upgrade from LineageOS 18.1 to LineageOS 19.1 via the following links: https://wiki.lineageos.org/devices/instantnoodle/fw_update & https://wiki.lineageos.org/devices/instantnoodle/install
All seemed well with no problems, but now when I boot up the device (instantnoodle) It starts up normally but then the screen does not register inputs.
So I can't get past the pin for my SIM or the startup screen you get when first startup LineageOS 19.1
What I have done is go back to recovery and did a Factory reset and format all data.
But this did not make things better..
Does anyone have an idea if there is a work around for this problem?

baseballbatboy26 said:
So I performed the upgrade from LineageOS 18.1 to LineageOS 19.1 via the following links: https://wiki.lineageos.org/devices/instantnoodle/fw_update & https://wiki.lineageos.org/devices/instantnoodle/install
All seemed well with no problems, but now when I boot up the device (instantnoodle) It starts up normally but then the screen does not register inputs.
So I can't get past the pin for my SIM or the startup screen you get when first startup LineageOS 19.1
What I have done is go back to recovery and did a Factory reset and format all data.
But this did not make things better..
Does anyone have an idea if there is a work around for this problem?
Click to expand...
Click to collapse
SOLVED. Used the newest OTA Update

my oneplus 8t screen not respond to touch after installing lineageOS 19 today

meowXda said:
my oneplus 8t screen not respond to touch after installing lineageOS 19 today
Click to expand...
Click to collapse
Which method of flashing did you utilize before installing the ROM, e.g., fastboot, TWRP, OrangeFox, etc?

rodken said:
Which method of flashing did you utilize before installing the ROM, e.g., fastboot, TWRP, OrangeFox, etc?
Click to expand...
Click to collapse
I followed the steps provided by the lineage os official website.

meowXda said:
I followed the steps provided by the lineage os official website.
Click to expand...
Click to collapse
Boot into TWRP instead of LOS Recovery
-- Factory Reset, then Format data / factory reset
-- Reflash ROM
You can always revert to a previous build to test for firmware issues.

rodken said:
Boot into TWRP instead of LOS Recovery
-- Factory Reset, then Format data / factory reset
-- Reflash ROM
You can always revert to a previous build to test for firmware issues.
Click to expand...
Click to collapse
I'm unable to turn off my phone now, because touchscreen doesn't work, only the physical buttons work

rodken said:
Boot into TWRP instead of LOS Recovery
-- Factory Reset, then Format data / factory reset
-- Reflash ROM
You can always revert to a previous build to test for firmware issues.
Click to expand...
Click to collapse
Do you have any instructions article or vlog about this

I wanted to get rid of the oxygen os because there was too many bugs..

meowXda said:
I wanted to get rid of the oxygen os because there was too many bugs..
Click to expand...
Click to collapse
Only the physical buttons work on your device which makes your device a candidate for a complete restore via MSM.
Code:
Boot into TWRP
type: fastboot boot twrp.img

rodken said:
Only the physical buttons work on your device which makes your device a candidate for a complete restore via MSM.
Code:
Boot into TWRP
type: fastboot boot twrp.img
Click to expand...
Click to collapse
Is it a bricked phone right?

meowXda said:
Is it a bricked phone right?
Click to expand...
Click to collapse
What does MSM stands for?

meowXda said:
my oneplus 8t screen not respond to touch after installing lineageOS 19 today
Click to expand...
Click to collapse
I would have to assume that you meant Lineage OS 19.1 for Kebab?

meowXda said:
What does MSM stands for?
Click to expand...
Click to collapse
If you are not familiar with the MSM Tool
-- Refer to this guide.

meowXda said:
Is it a bricked phone right?
Click to expand...
Click to collapse
Your device is not bricked
-- Hard bricked devices will show few or no signs of life. A hard bricked device does not power on or show any vendor logo
-- A "soft bricked" device may show signs of life, but fails to boot or may display an error screen
-- Soft bricked devices can usually be fixed

rodken said:
Your device is not bricked
-- Hard bricked devices will show few or no signs of life. A hard bricked device does not power on or show any vendor logo
-- A "soft bricked" device may show signs of life, but fails to boot or may display an error screen
-- Soft bricked devices can usually be fixed
Click to expand...
Click to collapse
{
"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"
}

rodken said:
Your device is not bricked
-- Hard bricked devices will show few or no signs of life. A hard bricked device does not power on or show any vendor logo
-- A "soft bricked" device may show signs of life, but fails to boot or may display an error screen
-- Soft bricked devices can usually be fixed
Click to expand...
Click to collapse
Can I flash my device with other rom such as PE without going back to oxygen os.

meowXda said:
Can I flash my device with other rom such as PE without going back to oxygen os.
Click to expand...
Click to collapse
If you are thinking about immediately flashing another Custom ROM without rectifying your current issue, you might be in for a rude awakening.
-- Usually, you can flash another Custom ROM by performing a complete factory reset.
-- In your case, start fresh and somewhat new from OOS
-- Remember not to flash a Custom ROM on top of another Custom ROM without clearing the cobwebs.
-- Read, proof-read and read a third time the installation instructions from the developer of each ROM.
OCD Moment: I find myself factory resetting three times between flashing different Custom ROMs

rodken said:
If you are thinking about immediately flashing another Custom ROM without rectifying your current issue, you might be in for a rude awakening.
-- Usually, you can flash another Custom ROM by performing a complete factory reset.
-- In your case, start fresh and somewhat new from OOS
-- Remember not to flash a Custom ROM on top of another Custom ROM without clearing the cobwebs.
-- Read, proof-read and read a third time the installation instructions from the developer of each ROM.
OCD Moment: I find myself factory resetting three times between flashing different Custom ROMs
Click to expand...
Click to collapse
I found that my touchscreen won't work even in the recovery mode(lineage os 19 recovery mode)

rodken said:
If you are thinking about immediately flashing another Custom ROM without rectifying your current issue, you might be in for a rude awakening.
-- Usually, you can flash another Custom ROM by performing a complete factory reset.
-- In your case, start fresh and somewhat new from OOS
-- Remember not to flash a Custom ROM on top of another Custom ROM without clearing the cobwebs.
-- Read, proof-read and read a third time the installation instructions from the developer of each ROM.
OCD Moment: I find myself factory resetting three times between flashing different Custom ROMs
Click to expand...
Click to collapse
I don't if it's the problem with lineageos or my phone itself