Hello to all of you! I have international model H960A 32gb. It is rooted from day 3. I have some broblems with wifi not turning on.I have to send it to LG here in Greece to check it out. I relocked once the bootloader and have erased the operation system.Is there any way to inject to the phone its original recovery and an original firmware at this point?? If yes,can you share the way??? Thank you all in advance!!
you should know if you unlock or relock the bootloader the phone does a factory reset...
i dont know what you mean by "inject the original recovery and firmware" since you could unlock it again and flash the KDZ you want on it!
- People here think we are Jesus to take care of every minimal thing would happen to their phones and we dont have to say nothing, if you do sh*t with your phone thats your fault since in every thread "how to..." have a disclaimer and the rules to follow, if you do it wrong is because you are lazy to follow the steps.
by now you are on your own, i say what you need to do, you can unlock the bootloader again and flash whatever you want: KDZ or TWRP.
Before you start attacking me,please make sure that you understand what are you reading... I don t ask for any Jesus to save me. I am just asking an answer. It would be more polite to tell me that you simply don t know what i am talking about,or just DONT ANSWER TH F***** question.
Thank you all again. For getting this more clear .... The question is how can i flash an official rom and recovery AFTER i have relocked my bootloader. I need the bootloader to stay locked.
gioarvdv said:
Before you start attacking me,please make sure that you understand what are you reading... I don t ask for any Jesus to save me. I am just asking an answer. It would be more polite to tell me that you simply don t know what i am talking about,or just DONT ANSWER TH F***** question.
Thank you all again. For getting this more clear .... The question is how can i flash an official rom and recovery AFTER i have relocked my bootloader. I need the bootloader to stay locked.
Click to expand...
Click to collapse
i dont think there is a way to flash without unlocking bootloader.cant you just flash stock rom with unlocked bootloader and then just relock it?it will reset everything again.stock rom and recovery.
jass65 said:
i dont think there is a way to flash without unlocking bootloader.cant you just flash stock rom with unlocked bootloader and then just relock it?it will reset everything again.stock rom and recovery.
Click to expand...
Click to collapse
Issue resolved. Thank you all. How to: 1.relocked bootloader. 2. Enter in download mode. 3. Start LGUP. 4. Started with refurbish option but an error was coming up. 5. Tried upgrade option and worked fine.
P.S: before starting LGUP i installed and run UPPERCUT.
Thank you all again.
Related
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
I got root using the /preinstall method with those 2 .bat files posted yesterday.
From page 30-35 is the guidance I followed from mramirezusa.
Other than that we are in the same boat.. I read puddings will flash relatively safely.http://forum.xda-developers.com/showthread.php?t=1159950&page=30
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
Question #2- Is there a possible way to unlock the new bootloader? yes use pudding
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
hey man first things first. dont panic, you are not stuck. this is temporary at best, in the mean while theres plenty of stuff you can do, sbf is not safe to begin with. so actually be gladd you only got to use RSD one time
first things first, get yourselfed unlocked, pudding will do the trick. once after pudding, you never have to touch RSD
Once you are done with pudding go ahead and get tenfars unlocked cwm
once you are done with that you are free to flash pretty much all the roms, as usually custom roms, or fruit cakes dont have bl, only the rest
enjoy
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
cthomas5714 said:
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
Click to expand...
Click to collapse
Yes but you still can't use any other sbf. I'd use the raw pudding sbf, unlock, then use CWM from here on out. No more rsd
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
snudmusk said:
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
Click to expand...
Click to collapse
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
jruweaver said:
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
Click to expand...
Click to collapse
Agree, just use the pudding only sbf. to unlock , then preinstall to get root.
Make sure to have 50 or so battery so you don't run into the trouble I had with battery being to low to fastboot. Also once you flash pudding you wont be able to boot the phone, don't panic just follow steps to fastboot oem unlock and phone will boot fine afterwards.
Sent from my MB860 using Tapatalk
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Which did you flash? Pudding or 1.8.3 with pudding?
Try connecting your phone to pc select fastboot and finish the pudding instructions (fastboot oem unlock)
It might boot then.
Sent from my MB860 using XDA Premium App
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/show....php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/show....php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Is there a way to root without unlocking the bootloader?
five3zero said:
Is there a way to root without unlocking the bootloader?
Click to expand...
Click to collapse
Yes.
Follow the instructions listed on here:
http://forum.xda-developers.com/showthread.php?p=15023030
The 3rd post has the instructions I followed.
If you have problems be sure to read through the thread as someone else has most likely already had the same issue.
This worked for me.
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Just do: fastboot oem unlock (or whatever tthe code is)
Them: fastboot reboot
Sent from my MB860 using XDA App
Hi everyone, i 'm going to be concise. I own an HTC onex+ international version (it should be no brand) and i would like to unroot it and reset to factory for a warranty issue. I'm extremely noob so i would like, if it's possibile, the fastest, easyest and safest way to do so.
On internet i found several guides about it as http://onexroot.com/one-x-unroot/how-to-unroot-rooted-htc-one-x/ or http://theunlockr.com/2012/12/28/how-to-unroot-the-htc-one-x-2/ BUT i found also an xda tool http://forum.xda-developers.com/showthread.php?t=1870652&nocache=1 that sounds appropriate to me; i read on other forum that i need some kind of extra instrument like boot.img
There are some things to take note of. The boot.img and HBoot image flashing requires users to get their own files as those are device specific and aren’t included
Click to expand...
Click to collapse
actually i have no idea where get it and how use it. I would be very gratefull if some of you could explain to me step by step how to do the unroot.
ps. i just rooted and put inside the cmw under the instruction of friend of mine but i don't really understand how i did it.
thank you in advance.
relock bootloader and install RUU and you are back on Stock
but would you be back on stock for a warranty issue, you didn't must do that.
warranty has nothing to do with your firmware or root or bootloader unlock.
they would be erase all at your phone and flash the RUU
skdubg said:
relock bootloader and install RUU and you are back on Stock
Click to expand...
Click to collapse
thank you for your reply but the problem is that actually i don't know how to relock booloader and what RUU is; that's why i was lokking for a step by step guide. I may follow and understand a little the guide of before but i'm not safe that it works with htc onec+ too.
but would you be back on stock for a warranty issue, you didn't must do that.
warranty has nothing to do with your firmware or root or bootloader unlock.
Click to expand...
Click to collapse
really? i belived that an "unlocked" phone was an enough reason to invalidate the warranty isn't it?
kadakar said:
really? i belived that an "unlocked" phone was an enough reason to invalidate the warranty isn't it?
Click to expand...
Click to collapse
if you dont touch the bootloader it says: LOCKED
if you unlocked bootloader it says: UNLOCKED
if you relocked bootloader it says: RELOCKED
we can never go back to LOCKED (RELOCKED is technical the same like LOCKED, but it shows as RELOCKED) all people can see that the bootloader was touched by the user
so it cant the reason for that
to relock:
boot into bootloader
and execute this command in fastboot:
fastboot oem lock
now you can install your latest RUU (RUU is the Stock Firmware from HTC as *.exe to install from Windows [depends on your CID])
hi i need help. so here is what happened. i have a sprint htc one max. i unlocked the bootloader and rooted the phone. flashed a custom rom on it and had it flashed to page plus and no problems with the phone. when i saw that it could be unlocked. i tried the steps to relock my bootloader and then things when wrong. i relocked my bootloader but now i am stuck in bootloader mode and cant enter recovery. i have been reading in the forums but nothing seems to be a clear solution to me. i tried to install the RUU from sprint and it wont load. i get ERROR 133 (if i am not mistaken) and when i try to find the phone on adb it wont show up. so now i am hoping someone can guide me or show me what i need to do. if not i guess i have a new fancy paper weight hahaha. thanks guys appreciate it.
luisdelvalle1 said:
hi i need help. so here is what happened. i have a sprint htc one max. i unlocked the bootloader and rooted the phone. flashed a custom rom on it and had it flashed to page plus and no problems with the phone. when i saw that it could be unlocked. i tried the steps to relock my bootloader and then things when wrong. i relocked my bootloader but now i am stuck in bootloader mode and cant enter recovery. i have been reading in the forums but nothing seems to be a clear solution to me. i tried to install the RUU from sprint and it wont load. i get ERROR 133 (if i am not mistaken) and when i try to find the phone on adb it wont show up. so now i am hoping someone can guide me or show me what i need to do. if not i guess i have a new fancy paper weight hahaha. thanks guys appreciate it.
Click to expand...
Click to collapse
Does bootloader mode work? If so, you can use the ruu zip on an sd card to fix your phone. You can follow the instructions in my vzw ruu thread for option to. Just make sure you use the Sprint zip instead of mine.
dottat said:
Does bootloader mode work? If so, you can use the ruu zip on an sd card to fix your phone. You can follow the instructions in my vzw ruu thread for option to. Just make sure you use the Sprint zip instead of mine.
Click to expand...
Click to collapse
do you have a link to see how to make the zip file. i was searching and i dont know if i am overlooking it.
:cyclops:
dude. from bootloader, reflash unlock_code.bin you had from htc
then you can flash recovery and restore a backup
japodude said:
dude. from bootloader, reflash unlock_code.bin you had from htc
then you can flash recovery and restore a backup
Click to expand...
Click to collapse
thanks that did it. appreciate it.now i need to see how to unlock the sim on this thing hahaha. ok well now off to read some more
luisdelvalle1 said:
thanks that did it. appreciate it.now i need to see how to unlock the sim on this thing hahaha. ok well now off to read some more
Click to expand...
Click to collapse
i think when you soff it unlocks radio for anysim (i think) otherwise ebay does htc unlock code for a pound!
hey, i unlocked my bootloader in 5.0 and relocked to upgrade to 5.1, now my question is how can i be able to re unlock it again ? i dont have the unlocking code?
where can i find it or is there a way to find it ?
gsser said:
hey, i unlocked my bootloader in 5.0 and relocked to upgrade to 5.1, now my question is how can i be able to re unlock it again ? i dont have the unlocking code?
where can i find it or is there a way to find it ?
Click to expand...
Click to collapse
I think the code is different for each device. Fill out this form:
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
It's really easy to do, and the instructions are clear. Do keep in mind that, of course, all of your data will be wiped. I suggest after unlocking that you install TWRP and SuperSU.
xperia_c4_hater said:
I think the code is different for each device. Fill out this form:
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
It's really easy to do, and the instructions are clear. Do keep in mind that, of course, all of your data will be wiped. I suggest after unlocking that you install TWRP and SuperSU.
Click to expand...
Click to collapse
you should read what people say dude.. i thought that i will not be able to get my unlock code back but i did.
gsser said:
you should read what people say dude.. i thought that i will not be able to get my unlock code back but i did.
Click to expand...
Click to collapse
I don't know what you mean about reading what people say, but I suggest saving your code somewhere safe as a backup, which is what I did. I'm happy to hear you were able to get it back.
xperia_c4_hater said:
I don't know what you mean about reading what people say, but I suggest saving your code somewhere safe as a backup, which is what I did. I'm happy to hear you were able to get it back.
Click to expand...
Click to collapse
i meant: "Do keep in mind that, of course, all of your data will be wiped."
i already said that i have unlocked my bootloader before so this means i know what it will do :'D
Cleaning this up and clarifying as my original post was vague:
It is recommended that you unlock your bootloader before the 7.0 Nougat update. Although it will still be possible the process will be more difficult and risky afterwards.as you will need to use one of the edl mode tools (axon7backup, axom7tool).
The easiest way is to download this kit f you have the A2017U: (I can't speak to other models) (This kit and instructions are thanks to @jcadduono)
https://build.nethunter.com/misc/axon7/AXON7-A2017U-BL-UNLOCK-KIT.zip
https://build.nethunter.com/misc/axon7/INSTRUCTIONS.txt
The basic steps, which the above zip with take you through in detail are:
1. Flash Official B20 , enable OEM UNLOCKING after flashing.
2. Flash BLFastboot zip provided by ZTE when they had unlock method.
3. Enable OEM UNLOCKING in Developers Option
4. Boot to Bootloader
5. type : fastboot oem unlock
6. Done
Note: If you do not have the OEM UNLOCKING flag set in developer options you will get a soft brick. Also bear in mid this will wipe data.
All that being said I've heard Nougat to is going to be great from those in the know. In their words ”Well worth the wait! Hang in there!” from a HIGHLY credible source.
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
lokissmile said:
For anyone looking to bootloader unlock, I've heard that the methods might change when the N update rolls out. It's a major update and although I personally don't have N and can't get a direct answer because those who know for sure are under NDA. I can tell you that the advice given to me is to not re-lock. So if you are thinking of unlocking your bootloader I'd do it soon while the methods are stable. Google confirmed that daydream is certified in an upcoming update so the daydream version of the stock ROM has been through googles QA. Might as well get ready now, we will probably have another surge of custom ROMS shortly after. I'm just sharing what I think is a best practice.
Click to expand...
Click to collapse
OK, so just to make it quick, for everyone, unlock your bootloader sooner than later. It is safe since you can revert it to a locked state at any time later.
lafester said:
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
Click to expand...
Click to collapse
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
lokissmile said:
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
Click to expand...
Click to collapse
No need to bootloader lock an Axon 7 to get SafetyNet (Android Pay, PoGo, etc). Just do it the XDA way. But never relock!!!!
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong?
Regards,
mischa_martin
mischa_martin said:
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong? [emoji14]
Regards,
mischa_martin
Click to expand...
Click to collapse
Read the OP.
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
stevecaboose said:
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
Click to expand...
Click to collapse
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
tzbigworm said:
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
Click to expand...
Click to collapse
@stevecaboose
Unlocking Bootloader = Yes to OTA's.
Modding System and Boot = NO OTA's
hope that clear things up.
Close enough lol!
To be clear, it would be best to unlock before N is pushed out. I have it on good authority that unlocking your bootloader after you update to N will be more difficult and risky. Relocking would put you in the same situation. It's trivial to return to stock system+boot with an unlocked bootloader and TWRP and then the OTA will come through just fine. Or you can just wait for the TWRP flashable N stock ROM.
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
ScaryBugThing said:
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
Click to expand...
Click to collapse
TWRP/BL unlock doesn't affect OTA, ROOT does.
raystef66 said:
TWRP/BL unlock doesn't affect OTA, ROOT does.
Click to expand...
Click to collapse
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
I think the OP was trying to say that it's possible current tools will not work to unlock the bootloader after the 7.x ota is installed.
DrakenFX said:
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
Click to expand...
Click to collapse
I'm not fully agreed with that. You can install OTA's when you receive it, download it, install it when first booted into twrp cache. Only if you're not rooted. When you're rooted first unroot and in principle this should work.
There are several cases on internet about that. Even I did it with an unrooted but TWRP-ed Zopo C2. Received an OTA and installed it.
Im always glad to learn but IMO there are some possibilities to do the ota after all. But I am willing to accept it's a general fact that twrp could affect the normal OTA.
Edit : let's wait and see when B10 is rolling out and if I get a notification about that and if I can install it as a normal OTA(not with SD) with TWRP. Keep you updated:cyclops:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
felipe.vella said:
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
Click to expand...
Click to collapse
1- Download Official B20 from ZTE SITE (look Software Updates for the 6gb variant)
2- look in the forum for the B20fastboot zip file
3- Move both files to your SDCARD.
4- Enable OEM Unlocking under Developers Option
5- boot to stock recovery.
6- Install B20 official update via SDCARD (this will wipe Data)
7- boot and re-enable OEM Unlocking
8- boot to recovery and install B20fastboot zip
9- boot to Bootloader and Unlock bootloader using this command.
Code:
fastboot oem unlock
If I remember correctly will reboot and factory reset the device , you'll need to re-enable OEM UNLOCKING and boot to Bootloader to flash TWRP 3.0.3 USING fastboot commands