Database Users

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

Help Please [SM-T377P]

So at some point when wiping/flashing LOS 15.1 something got messed up & it just keeps rebooting before the boot screen loads. It doesn't matter what I flash now, it does the same thing, all except for the firmware file from Updato. That booted into 7.1.1 (though it took a while), I tried flashing LOS after but it still goes right back to the reboot loop. Any help would be much appreciated.
[edit]
So I found a full backup & got that restored using TWRP 2.8.7.0, that booted up only to tell me to put my sim card in, no clue where that is, never used it (used tablet). I flashed 3.2.3, LOS 15.1 & 16.0 so far, neither will boot, they just get stuck on the boot screen. LOS 14.1 just reboots before the boot screen.

I've tried to use the Bootimage Debug Addition patch from here to grab some logs but it doesn't seem to be working, any help would really be appreciated.

So I take it I'm just out of luck then?

Problems with CustomRoms after failed Android Full-disk encryption

Hi, I tried to encrypt my Mi A1 with Android’s full-disk encryption. Unfortunately something went wrong, so I tried to flash a Rom. First I tried a dirty flash with the official LOS 15.1 (20190224). But the Display went crazy. So I head to flash the stock Rom through fastboot. After this my Mi A1 worked. Next I tried a clean flash with the same LOS-Rom, but I get the same result. I also tried some other versions of LOS, but I get also the same result. I also tried to flash LOS 16.0 (20190301) and also AospExtended v6.3(20190213). The result after flashing those Custom Roms is that the Display stays black, but not like the phone is off. It looks like the display is active but black. I had also tried LOS for microg 15.1(20190310) but the result was the same as flashing LOS 15.1
When I flash LOS 15.1 or the other Roms with the same result and I boot in TWRP the Display there also went crazy.
Sometime when I format or flash something with TWRP I get the message ,,Failed to mount ‘/system’ (Permission denied). But I always get the same result after flashing.
I hope someone could help me.

same to me
just recovey my phone with mi flash y culdnt get a costom rom again

You need to correct youe version of TWRP recovery
Infact, you need to try different versions to see which one works for uh...
Try booting into recovery IMG from Fast boot again and again if uh are really troubled by a permanent recovery.

Maybe soft-bricked my pixel c.

I attempted to install Lineage OS on my Pixel C. When I attempt to sideload Lineage OS, I get an error that says "Updater process ended with signal: 7" and it acts like I have no system image installed and just keeps boot-looping. I tried to flash back to stock, but I keep getting an error that says "error: Cannot generate image for userdata". I have re-downloaded all of the images, and retried over and over again, to no avail. Any advice is appreciated!

Well, I finally got my tablet to boot again. I extracted the factory image and individually flashed each component (boot, cache, recovery, vendor, system - in that order) and I'm back to a clean install of the stock android. I went back and flashed twrp (successfully), and tried to sideload Lineage again per the instructions on their website, and got the same result. If I can't figure this out, I may be going back to just stock android.

Is it your first attempt at a custom rom?
Have you flashed a recent kernel, bootloader is unlocked etc?
edit: lol, last reply was from May..

Hey, I guess I haven't been on here in a while, and never saw your reply to this. It is not my first attempt at a custom rom. Bootloader is unlocked, and kernel is up to date (or was in May). I ended up staying on stock android since I had no trouble getting it to work. Best I can recall, I think I read that there was a conflict between TWRP and the kernel version I was on. Around the same time, I tried to flash LineageOS to my Essential PH-1, and had similar issues, and ended up just staying with stock android. I've been flashing custom roms since cyanogenmod was available on my Nexus One (I think that was on cupcake), and while I'm not an expert, I'm pretty comfortable with the process, so I went back to my Moto N6, and was able to flash LineageOS to that without a problem. I know that the Pixel C and PH-1 both have the whole A/B slot architecture, and I wonder if I wasn't managing that correctly, but I've gone through a couple of custom roms on my Pixel C over the years without having that problem, so I just don't know. Right now I'm fine with stock (rooted) Android, but the bug is sure to bite me again soon, so we'll see what happens then.

I recently downgraded to Lineage 15.1 (official) from 16 and had some issues.
Short story to make it work was; installed the April version of the official factory/ota image like you did to overcome version conflicts.
(booting to TWRP.img after getting to the correct recovery menu by pressing power+volume up).
In TWRP; As the \data folder was encrypted I had to format that first (advanced wipe) and used adb to push files to \sdcard.
I flashed the Lineage 15.1 zip, gapps and Magisks before rebooting.
As that build enforces encryption of \data at first boot you may need to use "default_password" to load TWRP with access to \data in the future.
Hope this helps

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.