Database Users

Lost TWRP

Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.

Danokan said:
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Click to expand...
Click to collapse
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232

Amro90 said:
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Click to expand...
Click to collapse
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.

Danokan said:
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Click to expand...
Click to collapse
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.

Amro90 said:
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Click to expand...
Click to collapse
YIKES.
Well.. it got the TWRP recovery loaded alright.
But it won't boot into anything else...light is flashing but screen is black.

HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP

Danokan said:
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Click to expand...
Click to collapse
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.

Hartendief said:
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Click to expand...
Click to collapse
How do you propose I flash it?

SOLVED
FIXED
http://forum.xda-developers.com/showthread.php?t=2448960

Help the learning noob somewhat LG G2 T-Mobile D8o130b

Okay so i have a few questions here its been a while since i have placed a Rom onto my device the last one was a Sprint model of the G2 and i was able to successfully install CM12 nightly onto it.
With my T-Mobile G2 i had used the once click root application to do so and used auto rec from the app store to install TWRP recovery hopefully i didn't do anything wrong at this point. So now i try to boot into recovery using the power and the down key at the same time but when i did this i was prompted with do you want to reset all data or not and i of course i chose no and booted back home.
Yes i have Super Su with granting access so to solve this minor problem. I had the quick boot application here to boot into recovery but another problem persisted. I cant flash anything over it fails every time and i am trying to flash 5.1.1 cm 12 i think with gapps with 5.1 i believe but in doing so still failed it matched up and everything. I thought that maybe i was trying to flash something that's really not compatible with my phone so i tried to use the same rom but different carriers.
It was cm-12-20150406-NIGHTLY-D801.zip and gapps-lp-20150222-signed but still failed to install the rom? is there something im doing wrong? May i have a tutorial step by step on what to do to successfully flash? and why cant i boot into recovery with the button configuration did i do something wrong with that i just want to so that if theirs a boot load epidermic and i need to use that to restore and see what the problem is? just need help please

Tensaz said:
Okay so i have a few questions here its been a while since i have placed a Rom onto my device the last one was a Sprint model of the G2 and i was able to successfully install CM12 nightly onto it.
With my T-Mobile G2 i had used the once click root application to do so and used auto rec from the app store to install TWRP recovery hopefully i didn't do anything wrong at this point so now i try to boot into recovery using the power and the down key at the same time but when i did this i was prompted with do you want to reset all data or not and i of course i chose no and booted back home and yes i have Super Su with granting access so to solve this minor problem i had the quick boot application here to boot into recovery but another problem persisted i cant flash anything over it fails every time and i am trying to flash 5.1.1 cm 12 i think with gapps with 5.1 i believe but in doing so still failed it matched up and everything. I thought that maybe i was trying to flash something that's really not compatible with my phone so i tried to use the same rom but different carriers cm-12-20150406-NIGHTLY-D801.zip and gapps-lp-20150222-signed but still failed to install the rom? is there something im doing wrong? May i have a tutorial step by step on what to do to successfully flash? and why cant i boot into recovery with the button configuration did i do something wrong with that i just want to so that if theirs a boot load epidermic and i need to use that to restore and see what the problem is? just need help please
Click to expand...
Click to collapse
There's no way anyone can read that without any punctuation marks or any paragraph order.
Basically, the data reset function doesn't work when you have a custom recovery, that's how you enter it. But the TWRP version installed is usually old, somewhat like 2.7.0.0, so you need to update it before installing any roms.

If you really do have recovery installed when you get to the screen about erasing data just choose yes and yes and it will just take you to recovery. If that's too scary for you then just boot into recovery using an app like rebooter from the play store.
As far as flashing it sounds like you may have downloaded bad files. If you're using your phone to download the roms maybe try using a pc then transferring to your phone. And DON'T flash roms for a different carrier, you're just asking for trouble.
Sent from my LG-D801

Choristav said:
There's no way anyone can read that without any punctuation marks or any paragraph order.
Basically, the data reset function doesn't work when you have a custom recovery, that's how you enter it. But the TWRP version installed is usually old, somewhat like 2.7.0.0, so you need to update it before installing any roms.
Click to expand...
Click to collapse
I Have version 2.8.6.1

rick09 said:
If you really do have recovery installed when you get to the screen about erasing data just choose yes and yes and it will just take you to recovery. If that's too scary for you then just boot into recovery using an app like rebooter from the play store.
As far as flashing it sounds like you may have downloaded bad files. If you're using your phone to download the roms maybe try using a pc then transferring to your phone. And DON'T flash roms for a different carrier, you're just asking for trouble.
Sent from my LG-D801
Click to expand...
Click to collapse
I used my computer to download the files all together and the problem still persisted.
And that i do know to not flash with different Carrier did it with a s4 without thinking.

Tensaz said:
I used my computer to download the files all together and the problem still persisted.
And that i do know to not flash with different Carrier did it with a s4 without thinking.
Click to expand...
Click to collapse
The problem might be that you are on the wrong bootloader so v30 lollipop. As loki and bump don't work on it it will result into an failed flash. What you can do is flash the right bootloader or easily downgrade bootloader and bootstack with autorec for your phone. Read carefully which one you need for your tmobile d801. If there is an loki error then just flash the jellybean bootloader what you easily can do with autorec.
Sent from my LG-D802 using Tapatalk

wulsic said:
The problem might be that you are on the wrong bootloader so v30 lollipop. As loki and bump don't work on it it will result into an failed flash. What you can do is flash the right bootloader or easily downgrade bootloader and bootstack with autorec for your phone. Read carefully which one you need for your tmobile d801. If there is an loki error then just flash the jellybean bootloader what you easily can do with autorec.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Still a bit noobish how do i do that boot loader thing?

Tensaz said:
Still a bit noobish how do i do that boot loader thing?
Click to expand...
Click to collapse
Well you download the right version for your d801
https://www.androidfilehost.com/?w=files&flid=13763
Then you need to install it
Click on the lollipop and let it do its job. If it asks for root then allow it.
It will probably reboot and you are done. Only need to flash then a newer recovery. Also search bender_007 on xda and leave him a thanks perhaps for his app
Sent from my LG-D802 using Tapatalk

wulsic said:
Well you download the right version for your d801
Then you need to install it
Click on the lollipop and let it do its job. If it asks for root then allow it.
It will probably reboot and you are done. Only need to flash then a newer recovery. Also search bender_007 on xda and leave him a thanks perhaps for his app
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
my god i can flash now awesome thank you now i have one last question if you dont mind telling me since i downgraded my boot loader to kk i think using the auto rec do i need to flash my current 30b boot-stack first before i use my stock restore? or is there an easier way to do so (tried to go into stock but was met with a black screen after lg logo)

Tensaz said:
my god i can flash now awesome thank you now i have one last question if you dont mind telling me since i downgraded my boot loader to kk i think using the auto rec do i need to flash my current 30b boot-stack first before i use my stock restore? or is there an easier way to do so (tried to go into stock but was met with a black screen after lg logo)
Click to expand...
Click to collapse
Well, as far as I know autorec downgrades to jb bootloader, to boot into stock you could find d801 lp modem and d801 lp bootstack/bootloader as it might need kk bootloader
Sent from my LG-D802 using Tapatalk

wulsic said:
Well, as far as I know autorec downgrades to jb bootloader, to boot into stock you could find d801 lp modem and d801 lp bootstack/bootloader as it might need kk bootloader
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
thank you for your help i now have a boot loader for stock that i found and im using auto rec for every time i reboot to cm12 getting the hang of this flashing thing i just want to know if theres any problems with the network service for cm12 at all?

Tensaz said:
thank you for your help i now have a boot loader for stock that i found and im using auto rec for every time i reboot to cm12 getting the hang of this flashing thing i just want to know if theres any problems with the network service for cm12 at all?
Click to expand...
Click to collapse
With cm12 I am not sure but the cause could be perhaps the wrong modem, and or bootloader. I also suggest to check out newer custom roms the only cyanogenmod as some custom roms are already running on lollipop modem and caf. CAF is code aurora forum so kinda it will also have changes specifically for qualcomm devices.
Sent from my LG-D802 using Tapatalk

[SOLVED + GUIDE] ASUS ZenPad 8.0 Z380KL how to solve bootloop

Hi Guys, i think that i have softbricked mi Zenpad :silly:
So, i have used KingRoot in order to have root permission, after i have use super_me or something like this in order to change KingUser app with SuperSu app, but after the reboot it has gone in bootloop
I have tried to reset it using standard recovery (by ASUS) but it doesn't works, it is still in bootloop.
Can you help me ? (again :laugh
Thanks to a Jappanase blog i was able to unbrick my tablet and install CM 13.0 without have a funcrional rom: {Mod edit}
------------------------------------------------------------------------
How to solve:
1_ Download the following zips in a folder
Code:
[URL="https://vasy.ru/TWRP/P024/"]https://vasy.ru/TWRP/P024/[/URL] TWRP
[URL="http://4pda.ru/pages/go/?u=http%3A%2...zip&e=48313529"]http://4pda.ru/pages/go/?u=http%3A%2...zip&e=48313529[/URL] CM 13.0
[URL="http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico"]http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico[/URL] G APPS
[URL="http://d-h.st/8FqR#"]http://d-h.st/8FqR#[/URL] ADB and other utilities . Thanks to @backwardastep
2_ Move CM 13.0 and G APPS in a sd card and insert it into the tablet
3_ Unzip z380klroot_w_xposed
4_ move the TWRP.img in the "z380klroot_w_xposed" folder
5_ open cmd on Windows and move in the z380klroot folder. Type:
Code:
cd C:\Users\XXX\Desktop\z380klroot_w_xposed
6_ Connect the tablet
7_ Then type:
Code:
fastboot boot twrpxx.xx.xx.img
the tablet will start to looking for a device
8_ Press power + "volume +" in order to put the tablet in recovery (you can also put the tablet in recovery mode before the point 7)
9_ Then it should boot a temporany TWRP
10_ From TWRP wipe all data and install first CM 13.0 and GAPPS as usual
Now you have a working CM 13.0
PS. i noted in the Andmen blog's that exist also an Resurrection Remix
Code:
[URL="https://mega.nz/#F!3JtglKKJ!JIL2MZnzTg1vgW8mLLd8kA"]https://mega.nz/#F!3JtglKKJ!JIL2MZnzTg1vgW8mLLd8kA[/URL]

Custom Kernel CM-13.0
For Asus P024 cm13 Z380KL
NEOX_P024-cm13-v1.0-U700-zram

The problem is twrp can't be touch, the display seems locked

bangdes said:
The problem is twrp can't be touch, the display seems locked
Click to expand...
Click to collapse
yeah, i have exaclty the same problem: http://forum.xda-developers.com/and...z380kl-unrootable-t3213933/page3#post69032596
i'm kinda of stuck :silly:

How do you flash back to ASUS's stock ROM? I downloaded 4.8.0_WW off 4PDA but it gives me an error when trying to flash it via TWRP. Any ideas?

xDark_ said:
How do you flash back to ASUS's stock ROM? I downloaded 4.8.0_WW off 4PDA but it gives me an error when trying to flash it via TWRP. Any ideas?
Click to expand...
Click to collapse
You cannot flash the stock rom from twrp.
Stock roms work only with stock recovery

giorgiofolle said:
You cannot flash the stock rom from twrp.
Stock roms work only with stock recovery
Click to expand...
Click to collapse
So I would have to reflash the stock recovery and use that to flash stock? If I use ASUS's FlashTool would that reset everything back to stock?
Sent from my Samsung SM-G930T using XDA Labs

xDark_ said:
So I would have to reflash the stock recovery and use that to flash stock? If I use ASUS's FlashTool would that reset everything back to stock?
Sent from my Samsung SM-G930T using XDA Labs
Click to expand...
Click to collapse
1. yes, you should flash before the stock recovery and then the stock rom
2. I don't know, i have never used asus flash tool, but i think that you should have anyway the stock recovery file
Again, i repeat, if someone know how copy the stock recovery, i can do it. My tablet have still the stock one and i could copy and post here !

I've tried to flash recovery image in adb fastboot and stock rom in asus flash tool but it doesn't work
Sent from my GT-I9300 using XDA-Developers mobile app

giorgiofolle said:
1. yes, you should flash before the stock recovery and then the stock rom
2. I don't know, i have never used asus flash tool, but i think that you should have anyway the stock recovery file
Again, i repeat, if someone know how copy the stock recovery, i can do it. My tablet have still the stock one and i could copy and post here !
Click to expand...
Click to collapse
bangdes said:
I've tried to flash recovery image in adb fastboot and stock rom in asus flash tool but it doesn't work
Sent from my GT-I9300 using XDA-Developers mobile app
Click to expand...
Click to collapse
Gonna try this:
{Mod edit}
(use GTranslate)
Do you have a link to the stock recovery @bangdes?
Edit: I flashed this (https://www.asus.com/zentalk/tw/thread-147621-3-1.html) and now I just get an ASUS logo that eventually goes to the "Powered by Android" screen. Gonna try flashing stock now.
Edit 2: Gave me an error 7. Gonna try charging it up and flashing it again while I research what's up.
Edit 3: tried booting TWRP over stock recovery and adb sideloading it. finished saying total xfer: 1.09x and booted me to a black screen once I tried rebooting (TWRP gave me a No OS warning) saying it couldn't find drivers for Qualcomm HD-9008. ****, I think I just hard bricked my tablet yet again. Rebooted into driver signature disabled mode and it says "unknown device". Can't even turn off the damn thing.

xDark_ said:
Gonna try this:
{Mod edit}
(use GTranslate)
Do you have a link to the stock recovery @bangdes?
Edit: I flashed this (https://www.asus.com/zentalk/tw/thread-147621-3-1.html) and now I just get an ASUS logo that eventually goes to the "Powered by Android" screen. Gonna try flashing stock now.
Edit 2: Gave me an error 7. Gonna try charging it up and flashing it again while I research what's up.
Edit 3: tried booting TWRP over stock recovery and adb sideloading it, booted me to a black screen once I tried rebooting saying it couldn't find drivers for Qualcomm HD-9008. ****, I think I just hard bricked my tablet yet again. Rebooted into driver signature disabled mode and it says "unknown device". Can't even turn off the damn thing.
Click to expand...
Click to collapse
my z380kl is latest (2016) version and cannot enter to recovery stock, or maybe the stock recovery doesn't exist.. it's weird

bangdes said:
my z380kl is latest (2016) version and cannot enter to recovery stock, or maybe the stock recovery doesn't exist.. it's weird
Click to expand...
Click to collapse
The stock recovery is just an Asus logo I think. That's what it is for me with the flashed recovery using the link above.
Sent from my Samsung SM-G930T using XDA Labs

I've tried thousand time and no luck, I found the stock recovery from 4pda. But I forgot the link

Ok, lil update. Found out a potential unbricking method:
{Mod edit}
Also this thread is just dedicated to this brick: {Mod edit}}
And here's a few others who have the same issue: {Mod edit}
According to a guy who natively speaks Russian, this is a hardbrick that can't be repaired without sending it in to the OEM.
Kinda wish I had a little birdie that could fly into the ASUS office (I've been there, actually pretty nice. Lounge chairs with tablets and phones on display to play with while you wait, and a TV that was playing Finding Nemo in Chinese. Plus staff was nice enough, I just played dumb about what happened lol) and just tell me what exactly I can do to fix this. Even worse, the one year warranty is almost up so I'm gonna have to fork over cash if I send it in to be repaired AGAIN. This makes me want to send this tablet off to repair and sell it off for a NVIDIA Shield or something, Jesus. I got burned by Asus with the ZF2 and yet I still fell into this trap. Same with Samsung, I guess I'm just a masochist or something. Anyways, currently juggling fixing/rooting my S7 along with school work, so it'll be a few days or so until I can start experimenting with this. On a sidenote, damn the OPO is good. Still flies after three years of daily usage

Back to factory firmware
I found pretty good guide here to help restore the z380KL back to factory firmware.
{Mod edit}

squall77 said:
I found pretty good guide here to help restore the z380KL back to factory firmware.
{Mod edit}
Click to expand...
Click to collapse
If you're going to spam, at least make an unbricking tutorial.

xDark_ said:
If you're going to spam, at least make an unbricking tutorial.
Click to expand...
Click to collapse
I apologize if it looks like a spam, I am just suggesting that you should at least try to restore the stock system partition before trying to flash stock rom using TWRP as it does not work with the custom ROM system partition. As far as I have tried I couldn't boot into stock recovery, maybe it doesn't have one on my model. I can only boot into fastboot.
Best bet is to try to boot into custom recovery and restore the stock system partition from a backup file and then flash the stock rom and see whether it works.

squall77 said:
I apologize if it looks like a spam, I am just suggesting that you should at least try to restore the stock system partition before trying to flash stock rom using TWRP as it does not work with the custom ROM system partition. As far as I have tried I couldn't boot into stock recovery, maybe it doesn't have one on my model. I can only boot into fastboot.
Best bet is to try to boot into custom recovery and restore the stock system partition from a backup file and then flash the stock rom and see whether it works.
Click to expand...
Click to collapse
No, I'm asking you that if you're going to spam your own site then at least make a tutorial that's useful, not just a tutorial everyone who wants to flash CM13 already knows how to do.

hi, pls help.
never got to step 9.
after type fastboot boot twrpxx.xx.xx.img, stuck at waiting devices

hafizhans said:
hi, pls help.
never got to step 9.
after type fastboot boot twrpxx.xx.xx.img, stuck at waiting devices
Click to expand...
Click to collapse
Can you boot into ADB normally? Like type in adb devices before you type in any commands

"set warranty bit recovery" sm-t350

Just got this tablet today 2nd hand. Installed twrp, wiped tablet, got it set up. I went into twrp to back everything up and now when i reboot into system i get this message:
"set warranty bit recovery "
and it boots back into twrp.
Is tried powering the device down and and then restarting but it keeps going into twrp.
It looks like i can flash the stock firmware in odin to fix this, but does anyone know can i just flash the custom kernel (in odin) that's available for the T350? Would that be enough.
Thanks
Sent from my Nexus 6 using XDA-Developers mobile app

So flashing the kernel found on this site for the 350 works if anyone comes across this error. I flashed it in odin (as opposed to twrp)
Sent from my Nexus 6 using XDA-Developers mobile app

rrrrrrredbelly said:
Just got this tablet today 2nd hand. Installed twrp, wiped tablet, got it set up. I went into twrp to back everything up and now when i reboot into system i get this message:
"set warranty bit recovery "
and it boots back into twrp.
Is tried powering the device down and and then restarting but it keeps going into twrp.
It looks like i can flash the stock firmware in odin to fix this, but does anyone know can i just flash the custom kernel (in odin) that's available for the T350? Would that be enough.
Thanks
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
If you installed the CF-Autoroot for your SM-T350 (I have this device) then it will softbrick your device, I do not know the cause, but I tried it. Also if you install TWRP for SM-T350, install the Lollipop version! The Marshmallow version is not compatible with 3rd party apps yet but the Lollipop version does. If you want to install SuperSU, then install from here: https://download.chainfire.eu/1012/SuperSU/SR3-SuperSU-v2.78-SR3-20161103171345.zip
YOU HAVE TO FLASH IT IN TWRP! INSTALL LOLLIPOP VERSION TWRP BEFORE YOU FLASH!!! ALSO, IF TWRP ASKS YOU TO INSTALL ROOT, DON'T LET IT!
Happy Flashing and Hope I helped.

Please help me get my S6 Edge Plus (SM-G928F) out of TWRP Recovery

Heyy guys, this is my first time posting a new thread
Unfortunately, my phone is stuck in TWRP recovery. When it was still working I downloaded Flashify. I don't remember what but when it restarted the phone, it stayed in TWRP recovery and never went back to normal. I tried wiping my phone several times and still won't go back. Then I pressed the option Change or Repair System File or something like that. But I put the wrong option on that menu and now it is completely stuck on the TWRP startup screen , I can't enter TWRP at all.
I tried everything that I possibly could. I even tried flashing a different version of TWRP and Philz Touch but still didn't budge. If y'all have any possible solutions, please speak up. My phone has been like this for about 6 days :crying:
I'm downloading the stock firmware of my model SM-G928F (G928FXXSBPIB). That's the only thing that I think that could possibly make it work. Do y'all think the same or is there something else I could do?

Go in download mode and flash that stock firmware that you downloaded.

Tahseen I said:
Go in download mode and flash that stock firmware that you downloaded.
Click to expand...
Click to collapse
Flashing the stock rom worked:victory:

Garxth said:
Flashing the stock rom worked:victory:
Click to expand...
Click to collapse
Ok so now if you want to root your phone. first install twrp and make sure oem is unlocked. Then when you boot into twrp make sure you dont select that option at the start otherwise you will keep booting into twrp continuously. Next flash cf auto root and then go back into twrp and enable that option that was disabled before you rooted your phone. You should be fully rooted with no errors.