Develop Bugs

Swift won't boot into system - straight back to bootloader fastboot mode

I'm trying to be helpful to someone and failing . I've not seen this issue before.
I have a WileyFox Swift that has been unlocked and has TWRP as custom recovery. Internal storage has an installation zip in it so looks like an attempt has been made to flash it. Can't Restore, not sure if a Backup was done. When powered-on it jumps straight to bootloader - fastboot mode. (Start/Power off/Recovery mode/Restart bootloader). Options all work as expected except Start which goes back to bootloader. I can also connect to the handset via usb and receive a response to 'fastboot devices' and other commands.
From TWRP I have installed Lineage nightly rom and the installation has completed successfully. Same for Gapps but the reboot option jumps straight back to bootloader (no sign of a system splash screen). A 'Fastboot continue' command at this point causes a flickering recovery splash screen and then back into bootloader again. I've been in bootloops before but usually a step further on than this. Anybody seen this before - am I missing something obvious?

Hi
Method 1
-if u want to install lineage os
install lineage and reboot it without installing gapps after that install gapps . Hope it works
Method 2
- if method 1 doesn't work for you you need to download and install stock rom for wileyfox swift by adb (fastboot)
See ya

Thanks for the reply. The problem with finding a stock rom is that the Swift shipped with Cyanogen OS 12 (not CyanogenMod). Cyanogen is no more and all links to their website have gone so it's hard to track them down.
I removed the battery from my Swift earlier today and forgot about it for about one hour- I think this has made the difference as I flashed a CyanogenMod 14 rom, rebooted to system and it worked :good:. Went back and flashed Gapps and it worked again :good:. I have an older OS than I want but am fine for the moment.

Good for you

Applying Magisk to OnePlus 3 on Android Pie results in a soft-brick

Yesterday I took some time to attempt to upgrade my OnePlus to Android Pie after finding out earlier that it's not as simple as just installing an update when your boot loader is unlocked. After a bit of searching I found this guide which I followed to upgrade OxygenOS to version 9.0.5. After some initial problems (I didn't pay enough attention and TWRP was set to auto-reboot which complicated matters a little) I managed to finish the upgrade and the device booted.
After confirming everything worked well I figured I should flash Magisk back onto the device so that I would have root access again. I flashed Magisk 19.3 and tried to boot the phone but it got stuck on the spinning OnePlus logo during boot. Left it running for over an hour, nothing happened so eventually I decided to flash the OTA update and the BL/KM patch again, which made my phone boot again but without Magisk, obviously.
After that I tried flashing Magisk 19.2 and Canary (19.4), both with the same results: a spinning logo, nothing more.
I'm not sure what else I can try. In a particular braindead moment I thought I should just try to take a look at Magisk's log file but of course that's not accessible without root access. I've got a feeling that the patch to the bootloader is causing issues with Magisk's firmware patch but I'm not familiar enough with this kind of problem to figure out what is going on exactly.
Does anyone recognize this problem or can one of you tell me what I could try to get Magisk running again?

I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Here's what I do.
1) flash recovery using fastboot
2) reboot to recovery
3) on home screen of TWRP > reboot > power off
4) wait 5 seconds, turn phone back on and go to TWRP right away
5) flash magisk > TWRP home screen > reboot > power off
6) wait 5 seconds, turn phone back on and go to TWRP directly
7 TWRP home screen > reboot > reboot phone
Should get you to boot

dpj52190 said:
I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Here's what I do.
1) flash recovery using fastboot
2) reboot to recovery
3) on home screen of TWRP > reboot > power off
4) wait 5 seconds, turn phone back on and go to TWRP right away
5) flash magisk > TWRP home screen > reboot > power off
6) wait 5 seconds, turn phone back on and go to TWRP directly
7 TWRP home screen > reboot > reboot phone
Should get you to boot
Click to expand...
Click to collapse
Thanks, I'll give it a go later tonight!

dpj52190 said:
I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Click to expand...
Click to collapse
I tried it just now. Sadly I get the same end result. Thanks anyway though.
I have an ADB log of the crash that happens that causes the phone not to boot, maybe that's familiar to someone around here? I uploaded it here.

Hello can I ask a question why do you need root

OP, I just upgraded the battery in my OP3 and, due to some software quirks with a certain custom ROM, decided to switch to Havoc which I liked a lot on my OP6. I flashed Magisk with no issue. Here are the steps I took:
Starting with unlocked BL
Boot into the newest official version of TWRP via fastboot.
Flash OOS 9.0.5 and boot into it, completing device setup.
Reboot into OnePlus recovery, then from within, reboot into fastboot
Flash TWRP to recovery in fastboot, then shut down device (do not attempt to fastboot reboot recovery, it will boot into OOS and overwrite TWRP)
Boot device, use volume key to interrupt startup, boot into recovery (TWRP)
Follow installation instructions from Havoc thread, do not wipe cache/dalvik after flashing, do not boot before flashing all zips (I flashed ROM -> gapps -> Magisk in that order)
OP, I'm not familiar with OOS's current status. My recommendation is to try a different ROM to see whether it is a compatibility issue with the ROM itself. Alternatively, try flashing OOS then Magisk one after the other in TWRP without interruptions, like I did. From the wording of your OP it sounds like you booted into the newly flashed OOS, then flashed Magisk after, which may be the source of your problems.

kallum7 said:
Hello can I ask a question why do you need root
Click to expand...
Click to collapse
I work on an app that uses location data and it's pretty convenient to be able to test it on a real device but with a joystick instead of real location data. To make matters more complicated it's my personal phone and I use that to play Pokémon Go too. Without cheating I might add, the root is not for PG but because I do want to be able to play it on the same phone that I use to test my app I need Magisk to hide the fact that it's rooted or the game won't start.
LunarisDream said:
OP, I just upgraded the battery in my OP3 and, due to some software quirks with a certain custom ROM, decided to switch to Havoc which I liked a lot on my OP6.
Click to expand...
Click to collapse
Thanks for the suggestion but I'd rather keep using OOS on this phone as long as I don't have a new phone for daily use. I don't really want to modify this thing too much without having a replacement ready in the likely case that I screw something up.
OP, I'm not familiar with OOS's current status. My recommendation is to try a different ROM to see whether it is a compatibility issue with the ROM itself. Alternatively, try flashing OOS then Magisk one after the other in TWRP without interruptions, like I did. From the wording of your OP it sounds like you booted into the newly flashed OOS, then flashed Magisk after, which may be the source of your problems.
Click to expand...
Click to collapse
I tried both flashing the OTA, the modded firmware and Magisk in one go and separately after confirming that the OTA/FW were working. Sadly both methods resulted in the same problem.

If anyone's wondering I did a clean flash and factory reset, then installed Magisk again after that. Everything's working again now. Thanks for trying to help!

LineageOS 16.0 OnePlus6T (fajita) Won't Boot/Update Slot A

Hello everyone!
This is my first post to XDA so hopefully it's not a repeat of sorts. I am currently running LineageOS 16.0 from February 2 on my OnePlus6T (A6013) and am having issues with the OTA updates. Whenever I try to install an update the phone simply reboots to the bootloader and each time I hit Start reboots to the bootloader. I find if I basically try every combination of booting to the system from the recovery or bootloader, booting to the recovery and back to the bootloader, etc. over and over again it to finally boot to the system (I think I simply get it to fail so many times it switches slots). I checked through ADB and it seems like slot B works but A is the one which won't boot. Is there an easy way for me to copy slot B into A? Or is this normal for custom ROMs? I reinstalled Lineage a couple of weeks ago thinking I could fix this but to no avail. I am also running the Lineage recovery on both slots as TWRP seems to be unable to decrypt (which I think is an issue for everyone).
Thank you for any help,
Noah

Can't boot to one of my slots, Twrp/custom rom won't load on it

Hi everyone not sure where to start but I'm having issues.
Since last year I was using DU v13.1 along with twrp, no problems. I decided to update to DU v13.5. I wanted a fresh install, so I flashed the August pie stock rom, then proceeded with the usual.. Boot in temporary twrp, install rom and twrp, reboot etc. Something went wrong somewhere.
Now it seems like only one slot is working, and it only boots into stock rom. I have reflashed the stock factory image and tried dueces script several times. Each time I get the exact same thing
To try and explain exactly what's happening, Twrp will temp boot up if I have one slot set active, but if I manually set the other slot active through fastboot and reboot, Twrp will hang at it's logo screen and not boot. If I am on Twrp on the working slot and try to switch active slots within Twrp and reboot, it says no OS installed and gets stuck. I've seen the 'your device is corrupt' message a few times as well which never happened before. So I switch back to the slot that boots, flash stock, temp boot Twrp, wipe system/data/cache, install DU 13.5 and the Twrp zip, reboot to recovery and hit the problem where it won't load Twrp on the opposite slot. I go to bootloader, switch back manually to the opposite slot and it won't load the custom rom. Switch back manually to the working slot and it'll boot onto stock rom and work fine.
I have rechecked if my bootloader is unlocked by trying the fastboot commands and both standard and critical come back as saying already unlocked, however if I look at 'getvar all' it says 'oem unlocked_no'. I don't know if this is something of note? In developer settings it says bootloader is already unlocked but is greyed out. Obviously I've lost root at this point too.
So at this point I'm going round in circles trying to reflash stock and repeating all the next steps but nothing is fixing.
I'm stumped at this point, don't know what else to try, so if anyone could help it'd be very appreciated!

Question OP 9 Pro stuck on infinite loop using LineageOS

Hi all,
I'm coming back to Android after an absence and would like to run Lineage on a new US unlocked 9P. I followed the directions in the Lineage OS website and unfortunately the phone now is stuck in a constant animation of the blue circle moving left over the arc, and there isn't much I think I will be able to do about it until the battery runs out.
Here's what I did as per the directions:
-got and installed adb and fastboot from the Windows zips from Google
-added the install location to the path enviro variable
-installed the Universal ADB driver from Github
-activated USB debugging and OEM unlocking on the phone
-got the phone repeatedly into fastboot mode but then got stuck since 'fastboot devices' didn't show anything
-got bailed out by another thread here that one needs to check for updates with phone connected and Win will download the relevant USB drivers. Thanks!
-unlocked the bootloader
-downloaded and flashed the 18.1-20210803 recovery img
-sideloaded the copy-partitions 20210323 zip and it got stuck at 47% just like the website said
-did the factory reset
-sideloaded the the LOS 2020210803 zip to the phone and rebooted
When I rebooted it just plays the animation I mentioned at the beginning, so it looks like it's stuck in a permaloop.
I should mentioned that after I flashed recovery and booted into the normal Oxygen mode it would take much longer to boot so perhaps there was something already creating the loop.
I am grateful for any assistance.
Thanks,

How long have you left it? First install of Lineage spins for ages

I think I left it for an hour or so. Thanks for the info - I just turned it on and will let it spin for a while and see what happens.

I let it run until the battery died. I fully recharged it and am letting it run again. Same result of blue circle tracing arc to the left.

Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!

lexcimer said:
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
Click to expand...
Click to collapse
Everytime you flash a new rom you need to wipe data after

Anytime that happens you just go back into recovery and wipe data a few times and it should work after that.

It would've been due to encryption. Each time you flash a new rom you need to wipe userdata which removes your lock and also removes encryption. If you try to install a rom without doing this first, the rom cannot access that partition, because it doesn't yet know the unlock code/pattern, which is why it just gets stuck trying to do so.

Thank you to the 3 posters above, and I appreciate DJ Sub's explanation, makes sense in hindsight and I'll keep it in mind for the future.
PS - I'm glad to be back to the Android modding community, it's refreshing to be able to steer what OS my phone is running

I had the same problem (also a couple of different boot loop problems) when flashing LineageOS.
I did many things, so can't say for sure which one helped me to fix that, but the things I did were:
Restore from boot loop via MSM tool flashing EU image.
Updating that OxygeneOS to the latest using internal updater.
Repeating the LOS installation process several times in different conditions to isolate the source of the problem. I was changing LineageOS package, OpenGapps package, etc.
One of the problems I've found was that latest OpenGapps package (July 28th if I'm correct) was causing the boot loop on first start (very similar to what you're describing):
Phone tries to boot showing the LOS animation.
It goes for several minutes.
Then the phone vibrates, reboots and it continues from the start.
If I'm not mistaken, it was fixed by using the version from July 24th. The latest package also were removed from the OpenGapps page later AFAIR.
Second problem was after the successful boot. The phone was rebooting from the first setup wizard, booting to recovery (or some other partition) and proposing to make a factory reset.
Not sure which of my steps solved this, but I was updating back to the last LOS package watching closely that I'm flashing the same slot on each step and also making sure that slots are properly copied from one to another with the corresponding script.
Even in the most stable setup I was probably having some setup wizard loop problems, so I was skipping account setup steps and doing that manually later.
I'd say that installing LOS on OnePlus 9 Pro was most difficult and problematic installation in my experience and I did that a lot previously: HTC Wildfire S, THL 5000, Zuk Z1, Xiaomi Mi 5s, Xiaomi Mi 9T (Redmi K20) and several other devices.