Every Vanilla build for some reason bootloop for me since I got in custom ROMs and now it's enforcing A11 gapped roms also started bootlooping for me.
I always used gapps version of ROMs till now to bypass the vanilla bootloop issue. But since A11 has arrived I tried two ROMs which are both SELinux Permissive. And when I tried to go to SELinux enforcing builds of the same ROM, I get bootlooped.
Any solution for this?
Also I use OrangeFox since TWRP never worked for me
Use the last chinese firmware and or flash an other kernel like predator
Related
Okie dokie, I've installed cm13 after a couple hours of fighting with my phone bootlooping because of random garbage happening, (mostly due to GAPPS related issues). Now I'm bootlooping when I install the a new SuperSU binary.
It is to my understanding the cm13 in general is having issues with superSU, with it failing to install normally and then requiring a installation through recovery which causes a bootloop. I know cm13 does not require SuperSU, but I need to install it to force my selinux status to permissive on boot. Anyone have a workaround?
Current ROM file is cm-13.0-20160321-NIGHTLY-vs985.zip
JaXxz said:
Okie dokie, I've installed cm13 after a couple hours of fighting with my phone bootlooping because of random garbage happening, (mostly due to GAPPS related issues). Now I'm bootlooping when I install the a new SuperSU binary.
It is to my understanding the cm13 in general is having issues with superSU, with it failing to install normally and then requiring a installation through recovery which causes a bootloop. I know cm13 does not require SuperSU, but I need to install it to force my selinux status to permissive on boot. Anyone have a workaround?
Current ROM file is cm-13.0-20160321-NIGHTLY-vs985.zip
Click to expand...
Click to collapse
Why don't you just use the makepermissive.zip? Flash it in recovery and it'll set selinux to permissive... https://www.androidfilehost.com/?fid=24052804347784981
...and FWIW I use cm13 based ROMs(RR, AOKP) and flash the older superuser 2.52 zip(and the "makepermissive" zip if selinux is set to enforcing or else it may boot loop) and everything works fine.
startswithPendswithOOH said:
Why don't you just use the makepermissive.zip? Flash it in recovery and it'll set selinux to permissive... https://www.androidfilehost.com/?fid=24052804347784981
...and FWIW I use cm13 based ROMs(RR, AOKP) and flash the older superuser 2.52 zip(and the "makepermissive" zip if selinux is set to enforcing or else it may boot loop) and everything works fine.
Click to expand...
Click to collapse
I'll try that out after I get out of my current bootloop and let you know if it works xd
startswithPendswithOOH said:
Why don't you just use the makepermissive.zip? Flash it in recovery and it'll set selinux to permissive... https://www.androidfilehost.com/?fid=24052804347784981
...and FWIW I use cm13 based ROMs(RR, AOKP) and flash the older superuser 2.52 zip(and the "makepermissive" zip if selinux is set to enforcing or else it may boot loop) and everything works fine.
Click to expand...
Click to collapse
ok it seems to have worked! thanks!
Did you have the issue where it was telling you it had a secure boot error? I flashed CM13, the 35B stack.. which I believe failed because I didn't have the correct modem... and then supersu and ran into the secure boot problem. Finally got it back into recovery mode.. it refused over and over to go in and just restarted itself. Then I reflashed CM13,then gapps, then tried to 35B stack unsuccessfully again and was about to go update my modem and accidently powered the phone up.. now it's running no problem. I've just been super confused on what actually cause the boot issue.
Blindprophet32 said:
Did you have the issue where it was telling you it had a secure boot error? I flashed CM13, the 35B stack.. which I believe failed because I didn't have the correct modem... and then supersu and ran into the secure boot problem. Finally got it back into recovery mode.. it refused over and over to go in and just restarted itself. Then I reflashed CM13,then gapps, then tried to 35B stack unsuccessfully again and was about to go update my modem and accidently powered the phone up.. now it's running no problem. I've just been super confused on what actually cause the boot issue.
Click to expand...
Click to collapse
That happened to me once while I was troubleshooting by myself, I flashed an incompatible SU binary
JaXxz said:
That happened to me once while I was troubleshooting by myself, I flashed an incompatible SU binary
Click to expand...
Click to collapse
Which version did you end up using? Because I haven't flashed SU on the phone because of this issue.
Blindprophet32 said:
Which version did you end up using? Because I haven't flashed SU on the phone because of this issue.
Click to expand...
Click to collapse
Try this one... https://download.chainfire.eu/752/SuperSU/BETA-SuperSU-v2.65-20151226141550.zip
I just tried it on temasek's cm13 3/21 build and it works fine.
Blindprophet32 said:
Which version did you end up using? Because I haven't flashed SU on the phone because of this issue.
Click to expand...
Click to collapse
2.52 beta, an old one but it works if selinux is set to permissive (at least on my phone it worked)
Blindprophet32 said:
Which version did you end up using? Because I haven't flashed SU on the phone because of this issue.
Click to expand...
Click to collapse
The version that caused the "brick" (not sure if its the correct term) was 2.67 stable
startswithPendswithOOH said:
Try this one... https://download.chainfire.eu/752/SuperSU/BETA-SuperSU-v2.65-20151226141550.zip
I just tried it on temasek's cm13 3/21 build and it works fine.
Click to expand...
Click to collapse
Is your selinux status set to enforced or permissive? I might update my binary to that one
Just intall the latest beta (2.68) and it will work.
JaXxz said:
Is your selinux status set to enforced or permissive? I might update my binary to that one
Click to expand...
Click to collapse
Temasek was set to enforcing
Danilo-Sanchez said:
Just intall the latest beta (2.68) and it will work.
Click to expand...
Click to collapse
I tried to install 2.65 and got a secure boot error. Installed 2.67 and got a bootloop. I recently successfully updated my binary from 2.52 through the app. I'm not sure what version it updated me to though
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Check the bootloader compatibilty of these roms, if they r for the mm bootloader it ll not boot untill u upgrade ur bootloader, check the threads from wer u hv downloaded this...
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Exodusche said:
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Click to expand...
Click to collapse
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
check out this thread http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
I use Oxygen_14_OTA_18_all but there's a couple files posted on the bootloader upgrade threads that allow you not too flash the whole firmware just the partions you need to upgrade.
i am having same issue i was on oxygenos 3.1.3 firmware when i started to flash nogut roms every nogut rom works except cm. i flashed official cynogenmod 14.1 thinking that problem must have been solved but it wont boot it just shows oneplus logo. i have waited for 30 minutes but nothing happened if something worked out for you please tell me.
Well I've looked around XDA for soultion and this is it.
CM 14 has some Kernel problems, so only what you have to do is just install new kernel as Arsenic or Black Reactor kernel
I was running the new bootloader on cm13 nightlies and couldn't get it to boot either.
Even after a full wipe and reflash with v7 gapps
Gave up in the end and went back to the last cm13 Nightly
flash arsenic kernel after flashing rom and gapps it will boot. Read the posts in ashwin's official cm 14.1 thread.
Flash Black Reactor (recommended) or Arsenic Kernel.
The zip files that you have for CM are the unofficial ones. So I guess they're from Sarthak Narang. Or at least one of them. Those ROMs require the older bootloader to function. So if you have the newer bootloader, it won't work.
Hey gentlemen,
so the case is. I was on Epic Rom (MIUI 10) and installed Cardinal-AOSP yesterday. I personally didnt liked it.
- Now i cant install Miui 9, 9.5 or 10 only Android 8 based system.
- Even tried installing one of my backups, but no luck here.
- Tried Masik, restart after 30-60 seconds of loading again.
- Flashed lazy-flasher also
My device has TWRP Exclusive 3.2.1-(5/7). What can cause the problems? Hope you can help me out with a solution.
Update: Managed to get Epic rom 8.7.6 almost working, now it says my data is encrypted and i have to reset the phone, and than boots into twrp.
maybe, just maybe ok? you have treble version of oreo rom. and you have to un-treble to use non-treble rom. just try it maybe can help you
Get this rom: https://sourceforge.net/projects/orangefox/files/mido/ (credits to this site:https://forum.xda-developers.com/re.../recovery-orangefox-recovery-project-t3775933) Download the R7 zip flash it and try again.
OKAY, after a day I got út Sáta was corrupted, and was in f2fs state. Had to change it to exFAT4 and then I could install EpicEom by Escobar, wiped everything then installed again. Works like a charm.
All done on TWRP-Exclusive.
I installed the 5.8.020S ROM (Stock EUI) for Le 2 instead of Max 2. Luckily it didn't brick my phone.
When I tried to roll back to Lineage 16.0 (Pie) it didn't work. Tried a bunch of ROMs, Lineage 15 works, some others work but no Pie ROMs. My phone also resets itself on Lineage 15 every few hours for no reason. And the pre-boot screen has changed to a penguin instead of the "Le Eco" one.
Is it possible that when I installed the Stock EUI ROM that the boot partition and kernel were altered and that if I can get those back it will fix all my issues?
Or is it more likely that this is a hardware issue/irreversible?
Any suggestions? Thanks a bunch in advance. : )
Heyyo, boot partition is the kernel partition, so that should be overwritten by new ROM installs so that should be fine.. but yikes! I'd highly recommend using a fastboot ROM installer for EUI ROM for x2 just to ensure your device is as x2 as possible.
You could try this one from cuoco92 and use a PC with fastboot to install it. I believe there is readme files for instructions on how to do so.
https://androidfilehost.com/?fid=889964283620772795
If that fails? I would recommend qfil which will guaranteed reset your device to x2... albeit, with an older x2 developer build based on 5.6 I think? So from there I'd recommend upgrading to EUI ROM based on 5.9 like 19s and up before swapping to a custom ROM if you wanted to go that route.
https://forum.xda-developers.com/le-max-2/how-to/guide-hard-brick-fix-qualcomm-hs-usb-t3492949
Good luck!
It worked! Lineage 16.0 installs and runs just fine!
Also the stock ROM fixed my camera issue (original reason for going to stock) but lineage broke it again. At least I know it's not a hardware issue.
I did the following:
Unlocked bootloader
Installed twrp recovery
Flashed lazy flasher
Flashed rr pie rom
Flashed gapps nano
flashed magisk
My phone began restarting randomly once or twice a day.
I thought magisk was the culprit and flashed magisk uninstaller. Didn't solve the issue. Same happened with Pixel exp CAF and crDroid. On AOSP Extended it shuts off randomly instead of restarting. Now back to Pixel CAF cause reboot is better than shutting down.
I'm using latest version of twrp and roms.
How do I fix this. Pls help.
Edit: added magisk
Edit 2: mentioned gapps
SaraKumar said:
I did the following:
Unlocked bootloader
Installed twrp recovery
Flashed lazy flasher
Flashed rr pie rom
flashed magisk
My phone began restarting randomly once or twice a day.
I thought magisk was the culprit and flashed magisk uninstaller. Didn't solve the issue. Same happened with Pixel exp CAF and crDroid. On AOSP Extended it shuts off randomly instead of restarting. Now back to Pixel CAF cause reboot is better than shutting down.
I'm using latest version of twrp and roms.
How do I fix this. Pls help.
Edit: added magisk
Click to expand...
Click to collapse
There's no need to use Lazy Flasher and that's probably a reason why your phone is broken.
And why didn't you flash GApps?
Noter2017 said:
There's no need to use Lazy Flasher and that's probably a reason why your phone is broken.
And why didn't you flash GApps?
Click to expand...
Click to collapse
Thank you for replying.
Twrp was replaced by stock recovery everytime after I installed the rom zip and restarted the phone.
Someone had suggested lazy flasher in the forum. I don't know what it does but it fixed the problem. Is there a way to remove it? And will the recovery problem come back again if I remove it?
Sorry I forgot to mention gapps, I flashed nano after every rom except Pixel CAF(built in gapps).