Last night I received a notification and when I went to swipe it away the screen wasn't responding so I restarted the phone. It has been in a bootloop ever since. I'm currently on the last release of aicp from the telegram group. I have wiped the cache and system partitions, tried installing rom with and without magisk as well as tried dirty flashing another rom only to end up with the same results or bootlooping back into TWRP. O do not want to lose any data at all of possible. But any help will be appreciated. TIA!
Related
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
I was using RR N since its beginnings and wanted to go back to stock, so I flashed NPJS25.93 through fastboot and everything was just fine. However, an update notification kept popping up but I wasn't able to update the device (when trying to update, after download finished it restarted, but process would fail). Given the annoyance of the notification and pop up screen, I decided to go back to RR N... I flashed TWRP3.2.1 64 bits (because I was waiting for a more stable 64 bits Oreo RR) and tried to flash RR N for the meantime... For my surprise, after clearing system, dalvik, data and cache partitions, flashing process wouldn't finish... the progress bar would keep the animation, but the actual progress would stop at about 6mm of the end of the bar (I estimate 90-95 %). I left the device for lie an hour but nothing... So I reflashed stock N through fastboot and tried all over again... The same thing happened three times...
After failing to flash RR N I just decided to stay on stock N, but wanted root, so I reflashed TWRP and flashed ElementalX kernel to later flash super su... However, to my surprise, ever since flashing TWRP, whenever I reboot my device, it boots into recovery, and in order to reboot into the rom, I must reboot into bootloader first and then select either QCOM or BP TOOLS (I know bp tools is for fixing baseband, but don't know what qcom does). I have now flashed latest 64 bits RR O (15/09/18) cause I still can't flash RR N, but the rebooting into recovery persists...
Any ideas on how I could fix this?
I had flashed first 32 bits RR O but I tried to flashed magisk after the first boot and due to the rebooting into recovery issue, magisk never became functional in the rom (I would open the app and it would remain in the mask screen until a message of "Magisk stopped working" showed up). Something similar happened with SuperSu, but this time, I would never get it installed.
Good day! I am here asking for a few help as I seem to have trouble getting my phone back to life.
Earlier, I tried flashing android 9.0 pie beta rom I found on a certain group here locally in my country. The rom's link is as follows https://drive.google.com/file/d/15egbHONHGgm0AnvFYm2PCOmSyz0_utRR/view?fbclid=IwAR0I_akz9JcbpZxzitLNfm9OM2a-HH7FiDIDEHPM0-5wj0vIsuvz1TunrQQ. I came from Pixel Experience 9.0 Pie. I downloaded the rom above and rebooted my phone to fastboot mode without clearing data, etc through twrp first. Then I flashed the rom directly using Mi Flash. Once finished, the phone was not booting up properly and resulted in bootloop. Then, I downloaded the official stock rom and had it flashed directly to my phone. However, to no success, I only keep getting bootlooped. I then again tried to boot into fastboot and unlocked oem and flashed twrp and cleared dalvik, system, data and reinstalled pixel experience. Still no joy as upon rebooting, still bootloop.
Can anyone please help or assist on what further actions should I do? I'll greatly appreciate all the help I can get. Thank you!
**Update**
So I tried flashing the AEX Rom using this link https://forum.xda-developers.com/mi-a1/development/rom-aospextended-rom-v4-6-t3757436 and I can see the AEX logo and it stucks up there and just freezes my device.
First install 8.1 with MI Flash
https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533
Necrodaemon said:
First install 8.1 with MI Flash
https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533
Click to expand...
Click to collapse
You sir, just earned a fan! A million thanks!
As the title says, i can't to seen successfully boot any android pie/android 10 based rom on max pro m1.
>bootloader already unofficially unlocked.
but during erasing process, i accidentally booted into recovery from where i booted into system , where encryption started again.
>so i booted back to twrp, format data then flashed decrypt.zip
> then flashed havoc 9.0 based rom, gapps then >wipe from twrp itself.
> rom boots fine after boot logo,but after welcome screen, google loading screen comes after which screen goes blank black and finally shutdowns after few minutes.
>tried force shutdown, multiple times, data wipe,format data,decrypt.zip after mountung vendor as well.
Still same issue, just after rom boot logo finished loading, the phone just goes blank black.
what should i do ? Asked many threads,telegram groups, nobody is replying /helping, everyone is just ignoring it.
Same problem here but goes off when connected to WiFi. Please reply If anyone got a fix for this
CHGR1999 said:
Same problem here but goes off when connected to WiFi. Please reply If anyone got a fix for this
Click to expand...
Click to collapse
my problem is solved by flashing stock pie which was twrp flashable .
akhil17kr said:
my problem is solved by flashing stock pie which was twrp flashable .
Click to expand...
Click to collapse
So you don't use havoc anymore? Or did you first flash stock, update to pie, then flash havoc? I'm stuck too... Won't let me flash havoc, need to get firmware 16 or something.
Try factory reset or wipe data
i got the same issue and still can't not flash any custom rom, the same thing happen to my phone when i flash any custom rom 8 9 or 10, i changed recovery already but it didn't work
So, here is what happened. I was using my OnePlus 5 running rooted OxygenOS 10.0.1. When I tried opening a few apps, they kept force-closing on me. So I rebooted the device, but it stuck on the OxygenOS boot animation. I have access to TWRP and flashed the OS again, but it still gives me the same result. I also flashed the Magisk uninstaller, but that didn't change anything.
I am not entirely sure what went wrong, as everything was fine just a few hours ago. I would appreciate your help in resolving this situation.
Had this problem to, only thing that worked was factory reset in TWRP and start from scratch. Somehow data for corrupt