Database Info

CM 13 on XT1031 -- boot loop

I'm trying to install Cyanogenmod 13 on a Moto G -- according to the person who sold me the device, it was a XT1031, but I haven't actually verified this is the correct model. (Edit: I took off the rear case and verified that it was the XT1031 model.)
I'm using these instructions: https://wiki.cyanogenmod.org/w/Install_CM_for_falcon
I have adb and fastboot installed and working properly on OS X.
I used the Motorola Bootloader Unlock process to unlock the bootloader.
I installed the TWRP recovery image and am able to enter that recovery app. Specifically, twrp-3.0.2-0-falcon.img
The first time I tried to install Cyanogenmod from TWRP, I got error code 7 saying that my bootloader version, 4113, was not correct.
script aborted: This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader 0x4113.
This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader 0x4113.
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard/cm-13.0-20161006-NIGHTLY-falcon.zip'
Click to expand...
Click to collapse
Subsequently, I downloaded (https://www.mediafire.com/folder/nd7xvjndir52j/motoboot#tf9bzbdkxwkn3) and installed motoboot_4118.zip successfully, allowing the CM13 installation to complete.
However, when I reboot normally, the device is permanently stuck at the animated Cyanogenmod logo screen. (I left the device in that state overnight with no changes, so it's not just being slow.) This is consistent for the latest nightly build of CM13 and the latest stable build.
This comment (http://forum.xda-developers.com/showpost.php?p=65319505&postcount=7) suggested going into Recovery and wiping some stuff before installing CM, so I tried this by going into TWRP, choosing Advanced Wipe, and selecting the System, Data, and Cache checkboxes, and wiping, and then re-installing CM. However, this did not resolve my boot loop problem.

urjhnbnreaf said:
I'm trying to install Cyanogenmod 13 on a Moto G -- according to the person who sold me the device, it was a XT1031, but I haven't actually verified this is the correct model. (Edit: I took off the rear case and verified that it was the XT1031 model.)
I'm using these instructions: https://wiki.cyanogenmod.org/w/Install_CM_for_falcon
I have adb and fastboot installed and working properly on OS X.
I used the Motorola Bootloader Unlock process to unlock the bootloader.
I installed the TWRP recovery image and am able to enter that recovery app. Specifically, twrp-3.0.2-0-falcon.img
The first time I tried to install Cyanogenmod from TWRP, I got error code 7 saying that my bootloader version, 4113, was not correct.
Subsequently, I downloaded (https://www.mediafire.com/folder/nd7xvjndir52j/motoboot#tf9bzbdkxwkn3) and installed motoboot_4118.zip successfully, allowing the CM13 installation to complete.
However, when I reboot normally, the device is permanently stuck at the animated Cyanogenmod logo screen. (I left the device in that state overnight with no changes, so it's not just being slow.) This is consistent for the latest nightly build of CM13 and the latest stable build.
This comment (http://forum.xda-developers.com/showpost.php?p=65319505&postcount=7) suggested going into Recovery and wiping some stuff before installing CM, so I tried this by going into TWRP, choosing Advanced Wipe, and selecting the System, Data, and Cache checkboxes, and wiping, and then re-installing CM. However, this did not resolve my boot loop problem.
Click to expand...
Click to collapse
I have the exact same problem on the same phone (XT1031) and have gone through the same steps except I'm still at the 41.1A boot loader.
The other thing worth mentioning is now the phone shows up with "fastboot devices" but adb can not find it so I had to load different firmware using USB OTG flash drive.
===
I got it booting. I think the issue was I had to install the CyanogenMod Recovery from https://download.cyanogenmod.org/?device=falcon. Once I installed CyanogenMod Recovery ( cm-13.0-20161008-NIGHTLY-falcon-recovery.img) in place of TWRP and then installed cm-13.0-20161008-NIGHTLY-falcon.zip via USB OTG it booted up.

nooky1 said:
I have the exact same problem on the same phone (XT1031) and have gone through the same steps except I'm still at the 41.1A boot loader.
The other thing worth mentioning is now the phone shows up with "fastboot devices" but adb can not find it so I had to load different firmware using USB OTG flash drive.
===
I got it booting. I think the issue was I had to install the CyanogenMod Recovery from (snip). Once I installed CyanogenMod Recovery ( cm-13.0-20161008-NIGHTLY-falcon-recovery.img) in place of TWRP and then installed cm-13.0-20161008-NIGHTLY-falcon.zip via USB OTG it booted up.
Click to expand...
Click to collapse
Can you explain how you installed CM from CM Recovery? I can't seem to find an appropriate option. When I select Apply Update => Apply from ADB, it won't let me select the "ADB Sideload" option, and adb says that my device is offline.
Note: Whenever I flash the "recovery" partition with the nightly or stable build of CM13 Recovery while in Fastboot Flash Mode, I get a "Mismatched partition size (recovery) message" in the console window.

I was able to get CM13 installed and started finally.
One change I made was to install CM13 Recovery, do a factory reset from there. Stuff broke, including the ability to use adb, so I went back to twrp-3.0.2-0-falcon.img. There I tried installing CM13 one more time, and it worked this time.
Unfortunately, I can't say exactly what made it work this time around, but I'd speculate that it was the "factory reset" operation that did it.

OP6 won't get past bootloader after upgrading from 16 to 17.1

I decided it was finally time to upgrade to the newer LineageOS 17.1 branch nightlies from my previous installation of 16, rebooted to recovery and sideloaded lineage-17.1-20201013-nightly-enchilada-signed.zip onto it from https://download.lineageos.org/enchilada .
After doing so it appears the recovery successfully updated, it has a new purple skin it didn't have before, however the actual ROM won't start. Instead it goes to fastboot mode and asks whether I want to Start/Restart/Recovery/etc, but I can only get into fastboot or recovery mode.
I've tried flashing older nightlies, but even with 20200922 the issue was still there. I did notice there was a ton of updates in that specific release so I wonder if anything is broken in there.. unfortunately that's also the oldest available nightly so without compiling my own there's no way I can test whether older ones are functional, unless someone here has an older version available perhaps.
I did notice doing adb sideload only makes it go to 47% before the phone goes to installing it, however maybe that's normal, I haven't used it in a while so I don't know for sure. I tried using ADB to push an image onto /tmp, however the new recovery only seems to have 'Apply from ADB' as option so I can't actually install it from there.
Does anyone have any ideas I could try, or perhaps an older LineageOS nightly from before 09-22 laying around somewhere? Any help or suggestions much appreciated!
PPS: Of course I forgot to mention but I also did a factory reset, but that did not help. unsure what else to try besides compiling a rom myself or trying other roms from the forums here, though I'd very much prefer having LineageOS..

I found the reason. I had to install the official Oneplus 6 ROM first, probably to get the right vendor binaries/kernel modules/drivers.
This is what I did:
- fastboot boot TWRP ( TWRP can be found here https://twrp.me/oneplus/oneplus6.html )
- wipe -> advanced wipe -> all the things (technically optional but if you want to get rid of GApps etc this is needed)
- adb sideload official OnePlus 6 'Oxygen' ROM ( https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727 )
- reboot, fastboot boot TWRP
- run the 'copy partitions' zip from https://androidfilehost.com/?fid=8889791610682929240 to copy Oxygen to the other A/B partition
- Install latest build from https://download.lineageos.org/enchilada
- reboot, optionally boot TWRP again and install GApps, also optionally install TWRP, reboot, enjoy.
PS: Please note that after this you shouldn't switch A/B partition without first flashing another nightly or something over it, i.e fastboot boot twrp and install latest lineageos again, otherwise you'll end up booting the vanilla Oxygen rom

TWRP 3.5.0 Installation Silently Fails

Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU

Same question here. It seems that you can only boot from TWRP, not install it.

Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.

OnePlus 6 - LineageOS install trouble

SOLVED: The solution was simply to use LineageOS recovery instead of TWRP.
Followed the install directions on the lineageOS website as I had beforehand, except I didn't substitute LineageOS Recovery for TWRP this time.
---------------------------------------------------------------------------------------------------------
Hello everyone. New member, first-time poster, long-time lurker.
I've been trying to install LineageOS 17.1 onto my (new-to-me) OnePlus 6 (A6003) but for some reason, once I finish the install process, the phone will not boot system but instead falls back to recovery mode.
*Edit:
Files used-
OOS 10.3.12 (OnePlus6Oxygen_22.J.55_OTA_055_all_2107132218_71d1c06b31fc)
LineageOS 17.1 (lineage-17.1-20210420-nightly-enchilada-signed)
TWRP (twrp-3.5.2_9-0-enchilada)
*
Here's what I've done:
- Unlocked the bootloader and enabled USB debugging
- ran adb reboot bootloader, then flashed TWRP.img and sideloaded the TWRP.zip and rebooted to recovery to make sure TWRP was installed (idk why)
**I was under the impression I needed to flash OOS.zip to both slots (along with TWRP) before I tried to sideload LineageOS, so I attempted that but OOS wouldnt sideload, so i thought my sideload was messed up. I later realized OOS.zip was too big to be sideloaded (tried to make adb.exe large address aware to no avail)**
- I then pushed OOS and TWRP zips to /sdcard/ on the device
- Clicked install, navigated to OOS.zip, installed, hit the back arrow, installed TWRP, rebooted to recovery to change slots
- Clicked install, navigated to OOS.zip, installed, hit the back arrow, installed TWRP, rebooted to system to check things out. Both slots are now 10.3.12
- booted back into twrp
- Clicked install, navigated to LineageOS 17.1, installed, hit the back arrow, installed TWRP, rebooted to recovery to change to slot B.
- For some reason, slots didnt change, so I manually changed to slot B.
- Clicked install, files now looked different in slot B (encrypted I guess?) and the files I had placed on the phone were gone.
- Instead of installing the same way, I ADB sideloaded LineageOS, hit the back arrow, then sideloaded twrp.
- Attempted to boot system, phone tries to boot into system, but instead boots into recovery mode.
Swapped slots, same problem.
I'm not sure what I'm doing wrong, but if someone could give me some guidance, it would be much appreciated.
Thank you!

TreasureSeeker said:
Hello everyone. New member, first-time poster, long-time lurker.
I've been trying to install LineageOS 17.1 onto my (new-to-me) OnePlus 6 (A6003) but for some reason, once I finish the install process, the phone will not boot system but instead falls back to recovery mode.
Here's what I've done:
- Unlocked the bootloader and enabled USB debugging
- ran adb reboot bootloader, then flashed TWRP.img and sideloaded the TWRP.zip and rebooted to recovery to make sure TWRP was installed (idk why)
**I was under the impression I needed to flash OOS.zip to both slots (along with TWRP) before I tried to sideload LineageOS, so I attempted that but OOS wouldnt sideload, so i thought my sideload was messed up. I later realized OOS.zip was too big to be sideloaded (tried to make adb.exe large address aware to no avail)**
- I then pushed OOS and TWRP zips to /sdcard/ on the device
- Clicked install, navigated to OOS.zip, installed, hit the back arrow, installed TWRP, rebooted to recovery to change slots
- Clicked install, navigated to OOS.zip, installed, hit the back arrow, installed TWRP, rebooted to system to check things out. Both slots are now 10.3.12
- booted back into twrp
- Clicked install, navigated to LineageOS 17.1, installed, hit the back arrow, installed TWRP, rebooted to recovery to change to slot B.
- For some reason, slots didnt change, so I manually changed to slot B.
- Clicked install, files now looked different in slot B (encrypted I guess?) and the files I had placed on the phone were gone.
- Instead of installing the same way, I ADB sideloaded LineageOS, hit the back arrow, then sideloaded twrp.
- Attempted to boot system, phone tries to boot into system, but instead boots into recovery mode.
Swapped slots, same problem.
I'm not sure what I'm doing wrong, but if someone could give me some guidance, it would be much appreciated.
Thank you!
Click to expand...
Click to collapse
Hello!
LineageOS 18.1 is the latest stable official version. If that suits you, you should repost in the dedicated thread for help

duttyend said:
Hello!
LineageOS 18.1 is the latest stable official version. If that suits you, you should repost in the dedicated thread for help
Click to expand...
Click to collapse
Hey, thanks for replying! I opted for LOS17.1 because I didn't want to upgrade to android 11 but at this point I am willing to do whatever to get this phone running Lineage so I will move this post there like just suggested if I don't receive help here

That sideloading and slot copying stuff sounds intense. Can you try getting it back to the state where you have TWRP installed (the way you did that sounds right, you need to either "install" the zip or flash the img through the advanced menu for it to stick) and 10.3.12 applied to each slot (you can do this in TWRP by dragging the.zips from your computer to phone internal storage, no terminal needed)?
After that it's simply a matter of dragging the ROM zip to internal storage and installing it from TWRP if I'm not mistaken. The LineageOS guide looks weirdly complicated – though you might as well be safe and follow the slot copying steps before flashing the ROM as well. Though for convenience I'd still do it by dragging it from the computer not by adb.
(BTW disclaimer I haven't messed with roms a lot on OP6. If you need LineageOS specific advice best place would prolly be where other poster suggested.)

Issues installing LineageOS

Hello and thanks for taking the time to read my post,
after two years I am back at it with android and costum roms. I got an oeplus 6 and started working on it.
Using Linux (POP_OS!) I installed adb and fastboot via apt install.
from there I basically followed this guide: https://wiki.lineageos.org/devices/enchilada/install
Every step was going as it was described but I am struggling with the last step.
The output gets stuck at 47%(the output to the terminal) , than I get an error message on the phone. The terminal shows total xfer. 1.00x.
Those were to be expected according to the wiki, but when I press the return arrow it aborts the installation and I can reboot into a stock system.
What am I doing wrong? I am on the latest update (Android 11), I downloaded the latest nightly.
I also tried to get TWRP on it and then flashing the CROM from there:The TWRP logo is shown but it isnt switching to the swipe so I am stuck. If (TWRP latest, the corresponding installer zip is on my internal storage) i use the older versions I get to QUALCOMM CRASHDUMP mode.

levibuko said:
Hello and thanks for taking the time to read my post,
after two years I am back at it with android and costum roms. I got an oeplus 6 and started working on it.
Using Linux (POP_OS!) I installed adb and fastboot via apt install.
from there I basically followed this guide: https://wiki.lineageos.org/devices/enchilada/install
Every step was going as it was described but I am struggling with the last step.
The output gets stuck at 47%(the output to the terminal) , than I get an error message on the phone. The terminal shows total xfer. 1.00x.
Those were to be expected according to the wiki, but when I press the return arrow it aborts the installation and I can reboot into a stock system.
What am I doing wrong? I am on the latest update (Android 11), I downloaded the latest nightly.
I also tried to get TWRP on it and then flashing the CROM from there:The TWRP logo is shown but it isnt switching to the swipe so I am stuck. If (TWRP latest, the corresponding installer zip is on my internal storage) i use the older versions I get to QUALCOMM CRASHDUMP mode.
Click to expand...
Click to collapse
I was able to install it! I switched to an earlier nightly but I think the difference was that I clicked on apply update -> apply from adb before issuing the command from the terminal.
Now I have a follow up question: how is it these days with root (still magsik?) and can I still instal TWRP( if so, how? I am stuck since the slider is not coming for me)