I installed Dual Boot Patcher and was using Exodus on Data slot. Afterwards I uninstalled the app after wiping the secondary ROM but I am not able to update Oxygen OS. Everytime I dirty flash the full zip of updated Oxygen it gets stuck at bootanimation and keeps on showing bootanimation till around 30 minutes. Although I am able to flash the current version of Oxygen OS but the incremental updates also show the same behavior.
I have 0 experience with dual patcher but maybe you can try this.
Clean flash
If it changes something in your recovery, flash new twrp recovery trough fastboot
Hey guys,
Today I tried to go from the Android N developer preview back to Cyanogen Mod 13 (which I had been running before). I tried installing through TWRP 3.0.0.0 but for some reason whenever I install CM I get stuck in a boot loop at the screen that just says Google but multiple times I've been able to flash back to the Android N Preview. I've flashed my phone many times before and I tried a bunch of different stuff (formatting the userdata partition before flashing to decrypt the phone, wiping and not wiping the davlik cache before and after flashing, multiple snapshots of cm13 etc.) but I can't seem to break that bootloop. I ended up going to Android N after I broke something on CM so I used the opportunity to try out Nougat before I flashed back to CM so I didn't have any back ups (I thought I did but i only backed up apps and app data, not a whole solid backup from TWRP or something). Right now I'm entirely stable on Android N but missing XPosed a little so any help would be appreciated.
Alex
touchmywillis said:
Hey guys,
Today I tried to go from the Android N developer preview back to Cyanogen Mod 13 (which I had been running before). I tried installing through TWRP 3.0.0.0 but for some reason whenever I install CM I get stuck in a boot loop at the screen that just says Google but multiple times I've been able to flash back to the Android N Preview. I've flashed my phone many times before and I tried a bunch of different stuff (formatting the userdata partition before flashing to decrypt the phone, wiping and not wiping the davlik cache before and after flashing, multiple snapshots of cm13 etc.) but I can't seem to break that bootloop. I ended up going to Android N after I broke something on CM so I used the opportunity to try out Nougat before I flashed back to CM so I didn't have any back ups (I thought I did but i only backed up apps and app data, not a whole solid backup from TWRP or something). Right now I'm entirely stable on Android N but missing XPosed a little so any help would be appreciated.
Alex
Click to expand...
Click to collapse
Are you flashing the corresponding vendor image? If you do not flash the correct vendor image you will boot loop. I have gone from N to Marshmallow and reverse without issue.
santque said:
Are you flashing the corresponding vendor image? If you do not flash the correct vendor image you will boot loop. I have gone from N to Marshmallow and reverse without issue.
Click to expand...
Click to collapse
No I wasn't, I couldn't very easily find much information on how to flash the vendor image so right now I'm reverting back to Marshmallow via the OTA opt out, that should do the trick right? If not, I know where to find the vendor image but how do I flash it? just fastboot flash vendor.img or what?
Thanks for your help!
touchmywillis said:
No I wasn't, I couldn't very easily find much information on how to flash the vendor image so right now I'm reverting back to Marshmallow via the OTA opt out, that should do the trick right? If not, I know where to find the vendor image but how do I flash it? just fastboot flash vendor.img or what?
Thanks for your help!
Click to expand...
Click to collapse
There are two ways you can flash a vendor image. Either through TWRP's 'Install' menu or using the 'fastboot flash vendor vendor.img' command.
You can grab hold of the vendor image corresponding to the build number from here: https://www.androidfilehost.com/?w=files&flid=49333
Thanks to BeansTown106 for the vendor uploads.
Can't Flash CM13
Tried flashing stock rom throught ODIN then flashed CM13 on TWRP(wiped Data, System, Factory Reset with -r thingy)
but every time i try to flash its stucked on "Patching system unconditionally". I've also tried to let it sit for more than 24 hrs
Tried to flash ResurrectionRemix(5.1.1) by Dreamstar and it didnt took long(Still "patching system image unconditionally)
I know i shouldn't complain/discuss about ETA's
But isn't it odd that it hasn't finished flashing after 1 day?
bump. pls help
Basically, I got my Phone to TWRP and it won't go any further than Patching System Unconditionally.
I checked the MD5 on several ROMs, (Resurrection Remix 5.7.4 and 5.8.1 , Zephyr 7.1.1, Slim 2.0, Tipsy and Cyanogenmod 13) they all hang at Patching System Image Unconditionally.
I have done the following: Flashed to stock firmware and installed TWRP 3.0.2 with Odin, Tried several different OS's Wiped multiple times.
I don't know what my next step is. Please help me. Thanks.
I figured it out. I just kept repeating the steps until it worked.
Same problem here. Repeated several times, checked the hashes of the files, tried TRWP 3.1 and 3.0, lineageos 14, RR, aicp... all stuck in this same point... :/ only got to install cgm 13
Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?
Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.
I have now also tried flashing the stock boot.img, but no difference.
I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work
"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?
After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.
Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.
If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead
It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?
Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far
You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.
https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?
I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578
Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP
Yeah, I tried with Gapps, and I never rooted before first trying to boot.
As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%
Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation
Bump. I am also stuck in this state