Database Users

New soak test Motorola Moto Maxx RetBr

FIRST UNLOCK UR BOOTLOADER AND MAKE A NANDROID OR TWRP BACKUP
IF SOMETHING GOES WRONG U ARE SAFE
here we go
another soak is out for Motorola Moto Maxx XT1225 version Retail Brasil
Got 3 updates files
AFTER EACH INSTALL BOOT UP UR PHONE THEN GO AGAIN IN RECOVERY MODE
READ CAREFULLY THE GUIDE
SOAK 1 U MUST BE IN KITKAT 4.4.4 TO INSTALL THIS UPDATE
SOAK 2 : THIS U MUST INSTALL AFTER U INSTALL THE SOAK 1
SOAK 3
INSTALL THIS AFTER U INSTALLED SOAK 1 AND SOAK 2
[MOD EDIT:]SHAME SHAME SHAME. Signing an NDA means you're agreeing to not share details of the special program you are in.
This has been removed at the request of Motorola due to your negligence in violating the terms of your agreement.
let us know what is new
enjoy
hit thanks if helped

u already installed it right? No problems or brick danger?
Edit: Status 7 error.

feCorrea said:
u already installed it right? No problems or brick danger?
Edit: Status 7 error.
Click to expand...
Click to collapse
Same here.
Status 7.
BR Lollipop, stock, unrooted.

Can't say for BR but on MX firmware you need to have 22.34.7 installed before applying this (22.34.11) update.
Both updates installed without any issues.
HTH
Peter

same error
Same here, error 7 flashing this update.. In moto maxx Mexico with ROM Brazil..

PLGVIE said:
Can't say for BR but on MX firmware you need to have 22.34.7 installed before applying this (22.34.11) update.
Both updates installed without any issues.
HTH
Peter
Click to expand...
Click to collapse
Can u make a TWRP backup of your ROM n put it up? Its tiresome to restore everything n take the update every time there is one...

Cant update cos have 4.4.4 rights???
I have 5.0.2 Br installed, but when i try to flash it through recovery it says that i have something like 4.4.4 test.... and cant install.
Dont know what to do =(

These are the versions its looking for to qualify for the update:
LXG22.33-12.11
LXG22.33-12.13
If you modified your build.prop, it won't work. If you have modified any files under /system, it will not work. If you modified your kernel, it will not work.
Code:
getprop("ro.build.fingerprint") == "motorola/quark_retbr/quark_umts:5.0.2/LXG22.33-12.11/11:user/release-keys" ||
getprop("ro.build.fingerprint") == "motorola/quark_retbr/quark_umts:5.0.2/LXG22.33-12.13/13:user/release-keys" ||
abort("Package expects build fingerprint of motorola/quark_retbr/quark_umts:5.0.2/LXG22.33-12.11/11:user/release-keys or motorola/quark_retbr/quark_umts:5.0.2/LXG22.33-12.13/13:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
getprop("ro.product.device") == "quark_umts" || abort("This package is for \"quark_umts\" devices; this is a \"" + getprop("ro.product.device") + "\".");

adrynalyne said:
These are the versions its looking for to qualify for the update:
LXG22.33-12.11
LXG22.33-12.13
If you modified your build.prop, it won't work. If you have modified any files under /system, it will not work.
Code:
getprop("ro.build.fingerprint") == "motorola/quark_retbr/quark_umts:5.0.2/LXG22.33-12.11/11:user/release-keys" ||
getprop("ro.build.fingerprint") == "motorola/quark_retbr/quark_umts:5.0.2/LXG22.33-12.13/13:user/release-keys" ||
abort("Package expects build fingerprint of motorola/quark_retbr/quark_umts:5.0.2/LXG22.33-12.11/11:user/release-keys or motorola/quark_retbr/quark_umts:5.0.2/LXG22.33-12.13/13:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
getprop("ro.product.device") == "quark_umts" || abort("This package is for \"quark_umts\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Click to expand...
Click to collapse
I think i had installed xposed boot =( what am i to do now? flash lollipop again?

fillonov said:
I think i had installed xposed boot =( what am i to do now? flash lollipop again?
Click to expand...
Click to collapse
xposed doesn't modify any system files as far as I know.
Look closely at the error.
You have a unique oppurtunity due to root and twrp. We can strip out the parts that fail from installing and bypass that.
But I need an exact error to do that for you.
Heck, I can even remove the update check, but you stand a strong chance of a soft brick.

poncespr said:
Same here.
Status 7.
BR Lollipop, stock, unrooted.
Click to expand...
Click to collapse
Same here, BR, stock unroote, and bootloader locked, Status 7 error errtime...

adrynalyne said:
xposed doesn't modify any system files as far as I know.
Look closely at the error.
You have a unique oppurtunity due to root and twrp. We can strip out the parts that fail from installing and bypass that.
But I need an exact error to do that for you.
Heck, I can even remove the update check, but you stand a strong chance of a soft brick.
Click to expand...
Click to collapse
Yeah, I've been contemplating editing the updater-script, so it'd install through TWRP on top of LXG22-33-12.7 (the "first" 5.0.2 OTA posted here on XDA).

Please do not install yet
there are 3 updates to install in order
please read the op
thanks

How to make screen on tpwr? I can screen error
Sent from my XT1225 using XDA Free mobile app

fillonov said:
How to make screen on tpwr? I can screen error
Sent from my XT1225 using XDA Free mobile app
Click to expand...
Click to collapse
read the first post

@danger2u I was able to flash SOAK 3, with only updating SOAK 1 (didn't flash SOAK 2). It seems that SOAK 3's build requirement is either SOAK 1 or SOAK 2.
EDIT: by the way, SOAK 1 and SOAK 3's filenames are identical. The link in SOAK 1 is 21.6MB, while SOAK 3 is 17.7MB.

I can just tell you how I installed the updates (always rooted with TWRP flashed); For me it worked fairly well without issues but YMMV and there might be easier or better ways:
1> in TWRP: restore TWRP KK Backup (which I made after having received and rooted my telephone but there are "clean" backups available at XDA, AFAIR Chazzmatt posted his')
2> Factory reset
3> Remove root (in SU-App)
4> Flash KK (recovery + boot + radio).img, and sparcechunks by fastboot (from RETLA_XT1225_4.4.4_KXG21.50-9_cid12_subsidy-DEFAULT_CFC.xml.zip)
5a> from stock recovery (install from SD card) Lollipop 5.02 : Blur_Version.21.11.9.quark_retla.retla.en.01.zip
5b> from stock recovery (install from SD card) 1st update: Blur_Version.22.34.7.quark_retla.retla.en.01.zip
5b> from stock recovery (install from SD card) 2nd update: Blur_Version.22.34.11.quark_retla.retla.en.01.zip
That's for MX firmware, BR might be different!
kind rgds
Peter

hidea said:
@danger2u I was able to flash SOAK 3, with only updating SOAK 1 (didn't flash SOAK 2). It seems that SOAK 3's build requirement is either SOAK 1 or SOAK 2.
EDIT: by the way, SOAK 1 and SOAK 3's filenames are identical. The link in SOAK 1 is 21.6MB, while SOAK 3 is 17.7MB.
Click to expand...
Click to collapse
please do not install until the guide is complete

danger2u said:
please do not install until the guide is complete
Click to expand...
Click to collapse
i have to wait until the 3 files are uploaded? or can i flash these file 1 and 3?

feCorrea said:
i have to wait until the 3 files are uploaded? or can i flash these file 1 and 3?
Click to expand...
Click to collapse
wait untill all 3 are complete

Has anyone tried yo install russian flyme Roms with integrated TWRP?

Has anyone tried russian flyme twrp roms? There are 3 Roms in their link, but i don't know how to install it.

any link please ?

I can't put links because i have less than 10 post.
I'm sorry.

Write emmaus.pro in google. There are twrp for mx4 and custom roms, flyme and cm12.

I have Flyme 4.5.7i on my MX4 flashed by TWRP recovery.
(original my mx4 was A edition, and I was unlock bootloader and flash custom recovery with instructions found on xda forum)
Instructions How To Edit Official Flyme Rom to be flashed with TWRP:
---------------------------------------------------------------------------------------
1. Unzip update.zip in empty folder
2. Go in folder with unpacking files and delete uboot.img and logo.img
3. Go in META-INF folder and from here delete imei.dat and machine_match
4. Go in COM/GOOGLE/ANDROID folder and edit updater.script
Remove this :
getprop("ro.product.device") == "mx4" || getprop("ro.product.device") == "mx4" || getprop("ro.product.device") == "M460A" || abort("This package is for "mx4" devices; this is a "" + getprop("ro.product.device") + "".");
package_extract_file("META-INF/machine_match", "/tmp/machine_match");
set_perm(0, 0, 0755, "/tmp/machine_match");
package_extract_file("META-INF/imei.dat", "/tmp/imei.dat");
if (run_program("/tmp/machine_match", "/tmp/imei.dat") != "0") then
ui_print("machine not match");
delete(/tmp/imei.dat);
abort();
endif;
delete(/tmp/imei.dat);
And remove this :
assert(package_extract_file("logo.img", "/tmp/logo.img"),
write_raw_image("/tmp/logo.img", "logo"),
delete("/tmp/logo.img"));
assert(package_extract_file("uboot.img", "/tmp/uboot.img"),
write_raw_image("/tmp/uboot.img", "uboot"),
delete("/tmp/uboot.img"));
Save edited file.
5. Pack again files in .zip arhive (any name except update.zip)
6. Remove or rename any update.zip original file from root sd card
Now you can flash rom with twrp recovery and now you have latest Flyme rom but still have unlocked bootloader and twrp recovery.
I find this instructions on russian forums, and I try it and everything works fine.
You can try it on your responsibility.

Ok, thanks. Where have you downloaded twrp recovery?
Now i have philz 6 recovery, if i flash modded flyme ROM, can i flash it with philz?

I'm pretty sure that if you do a clean install (formating /system /data and /cache) Flyme will reinstall stock recovery. You need to delete recovery-from-boot.p and all install-recovery.sh and install-recovery-original.sh from system file

TWRP (uncompiled and recompiled by myself to change splash screen (it now fit the screen) http://www.mediafire.com/download/26b963db1k489db/new-recovery.img

Can i flash it trough flashify app?

I was flash twrp with fastboot

You can via flashify but fastboot is safer

PERFECT ! I worked hard to make it graphically perfect : http://www.mediafire.com/download/z3ssqo6lnyvwki7/TWRPr4.img
Just flash it with "fastboot flash recovery TWRPr4.img"

Are the russian flyme roms modded to can flash it vía twrp?

yes you can flash them Russians have ported this TWRP and are making some good stuff on flyme rom

Ok, i will try those Roms. Thankyou so much.

furious.builder said:
I'm pretty sure that if you do a clean install (formating /system /data and /cache) Flyme will reinstall stock recovery. You need to delete recovery-from-boot.p and all install-recovery.sh and install-recovery-original.sh from system file
Click to expand...
Click to collapse
I can't understand you. If is already tried that you can flash modded flyme Roma from twrp, why you say that flyme will reinstall stock recovery?
Are you sure?

I'm talking about stock Flyme not modded Flyme Stock flyme contains scripts like recovery-from-boot.p and install-recovery.sh in system.new.dat which reinstall stock recovery, it's what it does to my MX4, but modded flyme certainly don't have these scripts

Understood. Thanks!

furious.builder said:
PERFECT ! I worked hard to make it graphically perfect : http://www.mediafire.com/download/z3ssqo6lnyvwki7/TWRPr4.img
Just flash it with "fastboot flash recovery TWRPr4.img"
Click to expand...
Click to collapse
Is there any risk of brick flashing twrp vía fastboot?
I have seen many mx4 bricked flashing custom recovery with flashify.

Via fastboot there is nearly no risks because if it's flashed it will boot, and if there is something wrong during unlock fastboot has not been unlock so it will not flash, but don't use the one from my link, there is a newer from emmaus.pro

OxygenOS 3.1.0 (Marshmallow) Community Build for OnePlus X

New build is available to download.
Download link http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_3.1.0_community_build/
for those who stuck in boot, flash this recovery through fastboot . https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img Credits: pwseo
For getting to fastboot menu, 1) press power button untill phone has been powered off.
2) first press volume up button then power button until fastboot mode is shown.
3)Use the following command to flash the recovery. (Note:adb and fastboot should be installed first. get it here:http://forum.xda-developers.com/showthread.php?t=2317790)
fastboot flash recovery opx_oos3_recovery.img
Click to expand...
Click to collapse
source https://forums.oneplus.net/threads/oxygenos-3-1-0-marshmallow-community-build-for-oneplus-x.460857/

I can't install it through BluSpark TWRP v.37.
The error is something like this: This package is for "OnePlus" devices; this is a "ONE".
Anybody know how to fix this without replacing TWRP with stock OP Recovery? Thanks

I read the thread, i think need to flash stock Recovery before flashing

motherninja said:
I can't install it through BluSpark TWRP v.37.
The error is something like this: This package is for "OnePlus" devices; this is a "ONE".
Anybody know how to fix this without replacing TWRP with stock OP Recovery? Thanks
Click to expand...
Click to collapse
You can flash it thorough official twrp or stock recovery

You can also keep your recovery, but you have to slightly modify your package.
1. Unzip package.
2. Go to META-INF\com\google\android\
3. Edit updater-script with notepad++, or just with any text editor.
You should see "getprop("ro.build.product") == "OnePlus" || abort("This package is for \"OnePlus\" devices; this is a \"" + getprop("ro.build.product") + "\".");"
4. You can delete this line or change getprop("ro.build.product") == "OnePlus" to getprop("ro.build.product") == "One". In my case I had to change it into getprop("ro.build.product") == "onyx".
5. Save it and zip whole package.
6. Flash it and enjoy

My advice is, DO NOT flash this update yet...
Now I cannot back to TWRP anymore... Anyone have a workaround for this?

Still waiting for a solution. :/

Waiting for opinions before flash hehe

motherninja said:
My advice is, DO NOT flash this update yet...
Now I cannot back to TWRP anymore... Anyone have a workaround for this?
Click to expand...
Click to collapse
U need to flash TWRP from ADB from PC, Think this is the only way now
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
hotlinksxz said:
Waiting for opinions before flash hehe
Click to expand...
Click to collapse
Same here ...till some one compile the ROM which can be flash through TWRP

maybe i will wait for bug fix before flash..this is the first oos 3 for opx so it will be buggy
Sent from my ONE E1003 using XDA-Developers mobile app

kethsawant said:
U need to flash TWRP from ADB from PC, Think this is the only way now
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
Same here ...till some one compile the ROM which can be flash through TWRP
Click to expand...
Click to collapse
No, you cannot simply do that anymore. Look at the OPX forums at forums.oneplus.net, as advised by @pwseo, you need to follow the Mega Unbrick Guide first to fully restore your OPX to its original Lolipop FW, after that you are free to install TWRP again.

Any update on VOLTE?

Root
With Kingroot YouTube can get root, maybe with flashfire you can install twrp?
Edit: Can't install twrp but can install xposed.

Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.

Danish66 said:
Any update on VOLTE?
Click to expand...
Click to collapse
+1
Yes Guys..Can someone share any info here on this topic in the latest Oxygen OS build ??

motherninja said:
No, you cannot simply do that anymore. Look at the OPX forums at forums.oneplus.net, as advised by @pwseo, you need to follow the Mega Unbrick Guide first to fully restore your OPX to its original Lolipop FW, after that you are free to install TWRP again.
Click to expand...
Click to collapse
hmm same here,cant get into recovery,twrp needs to be updated by the devs i think
also directly booting into twrp fails too,"dtb " not found

gahehe said:
Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.
Click to expand...
Click to collapse
How u did it?
Mind sharing step by step?
Thanks in advance.

gahehe said:
Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.
Click to expand...
Click to collapse
With twrp? How?

If you're using stock recovery, just wipe data & cache and flash it.
If you're using TWRP, please do a Factory Reset then wipe system, data, cache, ART cache (very important, you will have many bugs on your device such as not recognize SIM card, Wifi not working... if you don't clean install). Then flash this ROM and reboot twice.
If you encountered error "This package is for "OnePlus" devices; this is a "ONE"." after select the ZIP, please extract the ROM, open the file META-INF/com/google/android/updater-script then remove the first line:
Code:
getprop("ro.build.product") == "OnePlus" || abort("This package is for "OnePlus" devices; this is a "" + getprop("ro.build.product") + "".");
Save the file, re-ZIP the ROM and flash it. Ta-da!

gahehe said:
If you're using stock recovery, just wipe data & cache and flash it.
If you're using TWRP, please do a Factory Reset then wipe system, data, cache, ART cache (very important, you will have many bugs on your device such as not recognize SIM card, Wifi not working... if you don't clean install). Then flash this ROM and reboot twice.
If you encountered error "This package is for "OnePlus" devices; this is a "ONE"." after select the ZIP, please extract the ROM, open the file META-INF/com/google/android/updater-script then remove the first line:
Code:
getprop("ro.build.product") == "OnePlus" || abort("This package is for "OnePlus" devices; this is a "" + getprop("ro.build.product") + "".");
Save the file, re-ZIP the ROM and flash it. Ta-da!
Click to expand...
Click to collapse
But you won't be able to boot back into twrp, so it's kinda useless. Better to have stock recovery than not being able to boot back into twrp=p
Unless you were able to flash supersu with twrp before booting the rom and not being able to boot back into twrp. Was that the case?

LineageOS 14.1 for SM-J500Y

Hi there,
I was wondering if there are any plans to develop a ROM for the J500Y model, because so far I couldn't find one.
Best,
andreas301

Flash the J500F-M-G version, see if it boots, report on forum thread

I'm currently running ResurrectionRemix v5.8.3 (7.1.2) on my J500Y. First I downloaded the ROM for "J500F-M-G" on my PC and then extracted it using WinRAR, then I opened the file > META-INF > com > google > android, then I opened the updater-script using Notepad++, I then removed the assert line (looks like this, can be a bit longer on certain ROMs:
Code:
assert(getprop("ro.product.device") == "j5lte" || getprop("ro.build.product") == "j5lte" || abort("E3004: This package is for device: j5lte; this device is " + getprop("ro.product.device") + "."););
) then I rezipped it and moved it onto my phone then flashed it using TWRP (MAKE SURE YOU ARE ON A LOLLIPOP ROM/BOOTLOADER BEFORE FLASHING, I used the J500F version of TWRP just to make sure it flashed, not sure if it was a necessary step, but if flashing it using the J500Y TWRP after removing the assert lines doesn't work, then try again after flashing the J500F TWRP using Odin) this should work with almost every nougat ROM that can run on the J500F variant, so far I haven't even needed to remove the assert line when flashing a marshmallow custom ROM so there is always that if you still can't get nougat working for you for some reason.

Stuck without an OS [OnePlus 5]

I recently bought an unlocked OnePlus 5 128GB and decided I wanted to root it and install another ROM. So, I did the standard flash of TWRP 3.2.3 for Cheeseburger and also successfully installed Magisk and Substratum. I found myself in an infinite boot screen after applying a Substratum theme so decided to factory reset the phone and start from scratch.
However, I stupidly managed to wipe the phone's OS as well as everything on it when going to factory reset, so now I'm just stuck in TWRP. I cannot install the stock OP5 ROM from the official OnePlus website and have also tried several others such as LineageOS. I've tried all the instructions on this thread to get back to stock but I always receive the dreaded:
Code:
Updater process ended with ERROR: 7
I get this even with the STOCK OnePlus 5 ROM, so there are no "assert" lines in the "updater-script" file like in LineageOS's ROM:
Code:
assert(getprop("ro.product.device") == "cheeseburger" || getprop("ro.build.product") == "cheeseburger" ||
getprop("ro.product.device") == "OnePlus5" || getprop("ro.build.product") == "OnePlus5" ||
getprop("ro.product.device") == "oneplus5" || getprop("ro.build.product") == "oneplus5" || abort("E3004: This package is for device: cheeseburger,OnePlus5,oneplus5; this device is " + getprop("ro.product.device") + "."););
assert(oneplus.file_exists("/dev/block/bootdevice/by-name/vendor") == "1" || abort("Error: Vendor partition doesn't exist!"););
assert(oneplus.verify_modem("2018-11-06 18:11:36") == "1" || abort("Error: This package requires firmware version 5.1.7 or newer. Please upgrade firmware and retry!"););
I've spent the last 4 hours looking for fixes, but they usually tell me to do the following, none of which has worked:
- Update TWRP (I have the latest version)
- Remove "assert" lines from "updater-script" file (Which invalidates the .zip files in non-stock ROMS)
- Use Blu_Spark (Can only find zip downloads, not .img files like everywhere tells me to use; they don't install as recovery menus when fastbooted, it just stays on the OnePlus logo when rebooting into it)
I'm completely stumped and am left with a softbricked OnePlus 5 that's only functionality is booting into fastboot or recovery/TWRP. Can anyone help here?

VampMarcie said:
I recently bought an unlocked OnePlus 5 128GB and decided I wanted to root it and install another ROM. So, I did the standard flash of TWRP 3.2.3 for Cheeseburger and also successfully installed Magisk and Substratum. I found myself in an infinite boot screen after applying a Substratum theme so decided to factory reset the phone and start from scratch.
However, I stupidly managed to wipe the phone's OS as well as everything on it when going to factory reset, so now I'm just stuck in TWRP. I cannot install the stock OP5 ROM from the official OnePlus website and have also tried several others such as LineageOS. I've tried all the instructions on this thread to get back to stock but I always receive the dreaded:
I get this even with the STOCK OnePlus 5 ROM, so there are no "assert" lines in the "updater-script" file like in LineageOS's ROM:
I've spent the last 4 hours looking for fixes, but they usually tell me to do the following, none of which has worked:
- Update TWRP (I have the latest version)
- Remove "assert" lines from "updater-script" file (Which invalidates the .zip files in non-stock ROMS)
- Use Blu_Spark (Can only find zip downloads, not .img files like everywhere tells me to use; they don't install as recovery menus when fastbooted, it just stays on the OnePlus logo when rebooting into it)
I'm completely stumped and am left with a softbricked OnePlus 5 that's only functionality is booting into fastboot or recovery/TWRP. Can anyone help here?
Click to expand...
Click to collapse
Error 7 identifies a corrupt os file. Download 5.1.4 and 5.1.7 again without any download manager and remove compatibilit.zip with 7zip on PC.
Use this recovery by flashing it with your current one https://forum.xda-developers.com/on...rdstuck-bootloop-please-t3896101/post78818108
Then follow this instructions https://forum.xda-developers.com/on...rdstuck-bootloop-please-t3896101/post78818624
Report detailed back :good:

remove compatibilit.zip with 7zip on PC
Click to expand...
Click to collapse
I've looked into the files in the 5.1.4 update for the OP5 including the "system.new.dat" file but can't find any "compatibilit.zip" in it. It also won't install as it is.
I flashed the recovery "boot.img" file using fastboot but all I get is a static light blue LED and a black screen. Using "adb devices" doesn't show anything connected.

VampMarcie said:
I've looked into the files in the 5.1.4 update for the OP5 including the "system.new.dat" file but can't find any "compatibilit.zip" in it. It also won't install as it is.
I flashed the recovery "boot.img" file using fastboot but all I get is a static light blue LED and a black screen. Using "adb devices" doesn't show anything connected.
Click to expand...
Click to collapse
Ah, my bad, too fast. The removal of the compatibility.zip is only necessary on Pie builds!
Which boot.img did you flashed? The linked one codeworkx twrp?you wrote you're able to boot your current twrp so you can flash the other twrp with it.

I flashed this one you linked in your comment -- is this the right one?

VampMarcie said:
I flashed this one you linked in your comment -- is this the right one?
Click to expand...
Click to collapse
Sorry, use this one please https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
The other one was the kernel...

strongst said:
Sorry, use this one please https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
The other one was the kernel...
Click to expand...
Click to collapse
I can't get into fastboot to install the recovery software now because I installed that kernel as the recovery...what now?
EDIT: Managed to install TWRP but it flashed the TWRP logo then went back to the OnePlus logo screen.
EDIT #2: In TWRP and installing 5.1.4 is working!
EDIT #3: Phone is booting, will give it some time and update later.

SUCCESS! In summary, here's what I did:
1) Boot into fastboot (POWER + VOL UP)
2) fastboot flash recovery twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
3) fastboot boot twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
4) Wipe system, data & cache using TWRP
5) Install 5.1.4, then Magisk, then format internal storage
6) Boot OS
Thank you so much; you're a lifesaver, strongst!

VampMarcie said:
SUCCESS! In summary, here's what I did:
1) Boot into fastboot (POWER + VOL UP)
2) fastboot flash recovery twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
3) fastboot boot twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
4) Wipe system, data & cache using TWRP
5) Install 5.1.4, then Magisk, then format internal storage
6) Boot OS
Thank you so much; you're a lifesaver, strongst!
Click to expand...
Click to collapse
Glad to help you