Database Users

[OP5] Error 7 when Installing LineageOS in TWRP

Hello,
Long story short. Moving from OP3T -> OP5, and I'd like to install LineageOS, or more preferably, the "new" MicroG (https://lineage.microg.org/).
Installed the latest TWRP according to the steps in this guide; https://wiki.lineageos.org/devices/cheeseburger/install
TWRP installed and everything transferred to the phone. Wiped the Cache, system and data. But trying to install i get an "Error 7" or more specifically: "Updater process Ended with ERROR: 7".
I have tried two versions of microG from (https://download.lineage.microg.org/cheeseburger/) and the latest "Normal" LineageOS. Same result. Also tried wiping the Dalvik Cache. Same error.
Any ideas?
Thanks for any help!

Update:
Downladed the latest OxygenOS from: https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
and that installed fine in TWRP. Still would like microG Lineage Though...

try multirom twrp

more_than_hater said:
try multirom twrp
Click to expand...
Click to collapse
Tried. Same Error.

You need to flash latest firmware

So this is strange....
I tried installing the latest AISOP, just for trying. And the installation process worked fine, but I got all sort of errors when android was starting - so i did a complete wipe and tried microG again... and it worked. So microG is installed now with "normal" TWRP.

This was happening to me while updating from OOS 5.0.0 to OOS 5.0.2, the culprit was twrp bluespark. Flashed the other twrp latest version and it resolved my issue.

after flash lineage 14, twrp can't go into system.

I have one XT1570(china version with dual sim), falsh lineage 14.1( the latest nightly one) , gapps with twrp, after flash both of them, I click "reboot", then "system". it can't go inside the system, still show with twrp ui.
Now I tried few times, still the same.
But if click "reboot", then "bootloader", after screen goes up, press power button"start", it looks the initiation of android system, but it last for hours, still loading screen.
Any suggestion for this problem?
Thanks.

Los 14.1 is for Marschmallow, one(?) build is for Nougat.
Xt1570 - Lolipop, if you didn't flashed any upper stock rom. @tigerszheng

the original one is Android 7.0 Nougat™ NPH25.200-15, I think this is the previous rom, but when I do factory reset, it boots into twrp directly.
Since I originally want to flash the lineageos 14.1 for clark, so I download the lineage-14.1-20171106-nightly-clark-signed.zip, and the gapps*.zip,
that's the content I used to flash with twrp, but the problem seems that the rom doesn't work properly. or maybe because the xt1570 default to boot into the recovery(twrp)?
not sure about what's the problem of this?
Thanks.

Try AOSP ext. for 7 modem:
https://forum.xda-developers.com/moto-x-style/development/collection-random-projects-t3662970
@tigerszheng

Oneplus2 Stuck on Animation

I have a US Oneplus2 that is stuck on the animation when it boots. I can get into TWRP and Fastboot, latest TWRP works and can also use an older version that I had.
I made a TWRP backup that I pulled off onto another computer. I then installed OOS 3.5.1 (I think) to do some testing. Once I was done testing, I decided I wanted the latest lineage as my backup was a 6 month old version of the latest at that time. I used TWRP to wipe the data, cache, and system to then install the latest Lineage 14.1 11/24/17 and gapps mini and micro (tested both). It gets to the lineage boot animation and the ball goes back and forth forever. I have left it over night and it's still going. I have rebooted the device, installed lineage several times, moved to 12/1/17 today with the same results.
After messing with it for hours and days, I decided to just put the TWRP backup back on the phone and then update from there. Well... my custom animation is load but the animation is also going forever.
Looking for some help on what might be wrong with the phone, thanks.

Make sure everything is formatted as ext4 and update firmware to 3.6.1 just to rule it out.
I would use the latest twrp.
I go to format tick all the boxes and clear everything then go to reboot > recovery. Once back in twrp copy the ROM and gapps across from pc install ROM and gapps together, wipe cache and dalvik reboot.

I'm in the process of doing that now.
The TWRP that I'm using is 3.1.1-0 which looks to be the latest. I am working with OOS 3.5.8 but will look at downloading 3.6.1. I am working to get Lineage 14.1 on there once everything is stable.
I ran into another weird is when using the qualcomm recovery tool:
My method is to enable ADB, enable OEM Unlock, enable Advanced Reboot.
Reboot into fastboot
Fastboot oem unlock: is successful
Fastboot reboot
I then go through renabling ADB and Advanced Reboot, OEM Unlock is still enabled.
I then reboot into fastboot
Fastboot flash recovery twrp-3.1.1-0-oneplus2.img
This completes successfully and then I fastboot reboot.
I have tried several times to get into TWRP but I keep getting the stock recovery.
I have tried to reflash recovery but nothing ever changes.
Is there possibly something wrong with the OEM unlock that says it was successful?
How do I go about troubleshooting this?

Ok, I fixed that and install OOS 3.6.1 and then was able to install TWRP 3.1.1-0.
I then wanted to install Lineage 14.1:
I then formatted Cache, System, Data, Dalvik... everything but internal. Should I wipe internal as well?
I copied over linage 14.1 and open_gapps for the same build micro.
I now am back to getting the Lineage Boot animation.
Thanks for helping since I'm trying to get Lineage to boot.

cyrus104 said:
Ok, I fixed that and install OOS 3.6.1 and then was able to install TWRP 3.1.1-0.
I then wanted to install Lineage 14.1:
I then formatted Cache, System, Data, Dalvik... everything but internal. Should I wipe internal as well?
I copied over linage 14.1 and open_gapps for the same build micro.
I now am back to getting the Lineage Boot animation.
Thanks for helping since I'm trying to get Lineage to boot.
Click to expand...
Click to collapse
Internal doesn't really matter to be honest, did you check they data and system are formatted as ext4.
It is in twrp advanced wipe options.
Did it ever boot ?

I did doubt check the data and system are formatted as ext4.
I let it sit for 3-4 hours and didn't see any progress.

Try a different rom. There are a lot of lineage based roms around.

I tried that and am getting the same results. Even if I flash a full TWRP backup from a time when I had it known to be working it happens.

I've tested this with 3 different roms now. My latest attempt has been to update TWRP to 3.2.1 and then install lineage 14.1 20171208. I also tested with Paranoid and Carbon because they were near the top of my list not because I know anything about them.
The phone just never gets past the boot animation. If I reboot to recovery is there a log I can pull to see what the issue is?
Thanks

Would like to see if anyone has any thoughts. If I run OOS I can use the phone but as of right now I can't use any other rom.
Is there any advanced fastboot or wipes that can be done to get it to boot. Is there any type of debugging that will show me what's happening when it tries to boot.

Just trying to bump this, I really need a way to debug this problem. Besides running OOS, I have a feeling this device is bricked and the mega unbrick guide doesn't work.
Also looks like if I try to put Kali on top of the base 3.5.8, the phone goes into the animation loop. So any change after OOS on the device puts it into an animation loop.
Is there a way the system or boot locked? Even thought I can TWRP anything onto the phone without errors.

Hey!
I've got the same issue it seems, phone just sticks to boot animation when flashing any other ROM than OOS 3.6.1.
Any update?
EDIT :
problem was with the persist.img
Flashed a different firm file and it was resolved

cyrus104 said:
I have a US Oneplus2 that is stuck on the animation when it boots. I can get into TWRP and Fastboot, latest TWRP works and can also use an older version that I had.
I made a TWRP backup that I pulled off onto another computer. I then installed OOS 3.5.1 (I think) to do some testing. Once I was done testing, I decided I wanted the latest lineage as my backup was a 6 month old version of the latest at that time. I used TWRP to wipe the data, cache, and system to then install the latest Lineage 14.1 11/24/17 and gapps mini and micro (tested both). It gets to the lineage boot animation and the ball goes back and forth forever. I have left it over night and it's still going. I have rebooted the device, installed lineage several times, moved to 12/1/17 today with the same results.
After messing with it for hours and days, I decided to just put the TWRP backup back on the phone and then update from there. Well... my custom animation is load but the animation is also going forever.
Looking for some help on what might be wrong with the phone, thanks.
Click to expand...
Click to collapse
OOS does not refuse to boot if a mountable partition is corrupt. This is not the case with lineage. If a mountable partition is corrupt and the corresponding fstab entry does not allow lineage to format and somehow mount it then init never proceeds
Try flashing this file: https://glassrom.botstack.host/firmware/oos-3.6.1-firmware-signed.zip and try again
Note that this file reboots the device after the flash is done so don't use twrp queue to flash this file. Flash this file last
---------- Post added at 17:45 ---------- Previous post was at 17:34 ----------
Alternatively this is a method I don't recommend to beginners because they accidentally give twrp logs to devs without realising it
You can get logs by making the forcing the device to "crash" through the power button
Here's how it's done: you boot the non-booting ROM and wait for about a minute. Then press power + volume down while it's on the bootanimation. You have to hold it until you see the oneplus logo and boot to twrp
TWRP's kernel will recover the last booted kernel's log from ram and place it in /sys/fs/pstore
First you have to open the log yourself to check if it's valid. The file is console-ramoops-0. All other log files in that location are invalid for your specific issue
Now for an ordinary user this is hard. They can't tell if the log is a recovery log or a ROM log. Since we're dealing with official lineageos we assume selinux would be enforcing
You want to search for this string "permissive=1". On Linux just do cat console-ramoops-0 | grep "audit" (quotes are part of the command)
If you're on windows then you can download Linux and get the logs. Stop bothering me
If you see the string "permissive=1" in the log you have accidentally fetched a recovery log
Go back and boot again and wait for about a minute if selinux is permissive
The string should read
"permissive=0"
That means selinux is enforcing and this is indeed a ROM log
Send this log here

Hello,
Was this problem ever solved? I am experiencing the very same thing with every single ROM i have tried so far. TWRP is installed, I can install all ROMS but when I try to boot the phone, it just won't get passed the booting animation.
Thank you

Problem with installing Lineage OS 15.1 on G530FZ

Everything works here: https://forum.xda-developers.com/gr.../cyanogenmod-14-0-galaxy-grand-prime-t3462500
I install a system with this thread and I have a problem: https://forum.xda-developers.com/gr...nofficial-lineageos-15-0-grand-prime-t3703797
I do everything as instructed. After installing the newest version of Lineage and Gapps I do reboot to system. I see a blue logo moving for a few minutes, but then instead of the welcome screen the phone restarts to TWRP. With 14,1 version everything is ok.

SM-T580 flash with LineageOS 16 stuck on lineage logo loop

I installed TWRP 3.1.1 using the ODIN patched version and was successful. I had let the system boot into the samsung original stock from where you see "HI" then I rebooted it into TWRP to attempt flashing and I got the /data partition couldn't be wiped. So I ran some of the other repair functions in TWRP and that appear to have fixed it. I then flashed with the latest LineageOS, Gsap, and Magistk20. When it boots up the LineageOS I'm stuck on the Lineage Splash screen. I've let it run over night and it has't changed anything. Any advice?

I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.

secretwolf98 said:
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
Click to expand...
Click to collapse
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.

dizzymon said:
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
Click to expand...
Click to collapse
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.

Possible corrupted file
secretwolf98 said:
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Click to expand...
Click to collapse
So far you're quite correct I personally have three SM-T580's and they all seem to work just a little bit different. Might I suggest doing an MD5 Sumcheck? The device shouldn't be getting into a bootloop unless there was something wrong with the files, or the device.