This is just a simple patched boot.img so you can re-do magisk after the update to 9.0.7 if you don't care for bothering with TWRP.
Instructions are the same as the others:
adb reboot bootloader
fastboot boot patched_boot-9.0.7.img
Open the Magisk Manager App and click install. When prompted, choose Direct Install.
Profit!
Download Link: Google Drive: https://drive.google.com/file/d/13RDdihjVwt1oXlaxasRXqu75_QlFJV2T/view?usp=sharing
If you Need Magisk Manager, you can grab it from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.1/MagiskManager-v6.0.1.apk
Thanks! Works like a charm
Thank you sir. Got me back rooted after the local upgrade to 9.0.7 on my tmo variant
Glad it helped!
Dameon87 said:
Glad it helped!
Click to expand...
Click to collapse
Yea seriously way easier than that root program. Done in under 5minutes. No fuss no muss
I'm completely unrooted and stock. Do I have to unlock bootloader to flash this to use Magisk?
Fade2 said:
I'm completely unrooted and stock. Do I have to unlock bootloader to flash this to use Magisk?
Click to expand...
Click to collapse
Yes
Any confirmation for this working on the T-Mo variant? I am bootloader unlocked with TWRP and Magisk root already.
Dameon87 said:
This is just a simple patched boot.img so you can re-do magisk after the update to 9.0.7 if you don't care for bothering with TWRP.
Instructions are the same as the others:
adb reboot bootloader
fastboot boot patched_boot-9.0.7.img
Open the Magisk Manager App and click install. When prompted, choose Direct Install.
Profit!
Download Link: Google Drive: https://drive.google.com/file/d/13RDdihjVwt1oXlaxasRXqu75_QlFJV2T/view?usp=sharing
If you Need Magisk Manager, you can grab it from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.1/MagiskManager-v6.0.1.apk
Click to expand...
Click to collapse
how do u get the stock boot.img for 9.0.7 6t international
tswb said:
how do u get the stock boot.img for 9.0.7 6t international
Click to expand...
Click to collapse
Can either grab it from the Payload.bin file after extraction, or use dd to pull it.
treetolber said:
Any confirmation for this working on the T-Mo variant? I am bootloader unlocked with TWRP and Magisk root already.
Click to expand...
Click to collapse
Post #3?
guspeed said:
Post #3?
Click to expand...
Click to collapse
It works fine on the T-Mobile or International.
In almost every case things will work on both unless otherwise noted.
@Dameon87 is there any way you could possibly throw an OOS 9.0.7 stock kernel zip together if it's not too much to ask?
Thanks!
I'll stick with the TWRP method.. after this messed up my phone with no internet at all in wifi or modem I had to go hunt down stock boot image.
Stock Boot Image are found here.. https://forums.oneplus.com/threads/...ta-oxygen-os-repo-of-oxygen-os-builds.941780/
strictlyphat said:
Thank you sir. Got me back rooted after the local upgrade to 9.0.7 on my tmo variant
Click to expand...
Click to collapse
So you had the t-mob variant.
then you unlocked bootloader and flashed 9.0.6 giving you the international variant.
How did you upgrade to 9.0.7?? Surely not OTA right?
CCJ22 said:
So you had the t-mob variant.
then you unlocked bootloader and flashed 9.0.6 giving you the international variant.
How did you upgrade to 9.0.7?? Surely not OTA right?
Click to expand...
Click to collapse
Local upgrade.
I have a question.. nothing to do with this thread. I tried making my own thread but the xda app won't let me.. however here is my question.. I just tried updating my greenify module for magisk and it said install fails.. reason is because my API is 28 and the max should be 27??? It also told me to downgrade to a different Android.... Anyone ever year such a thing?? And is there a fix for this???
anthony10126 said:
I have a question.. nothing to do with this thread. I tried making my own thread but the xda app won't let me.. however here is my question.. I just tried updating my greenify module for magisk and it said install fails.. reason is because my API is 28 and the max should be 27??? It also told me to downgrade to a different Android.... Anyone ever year such a thing?? And is there a fix for this???
Click to expand...
Click to collapse
You should address your issue on the greenify4magisk thread. The dev posted explaining the reason for the issue you encounter at the last page. I don't think greenify is needed for OnePlus 6T. 1+6T has a feature called Adaptive Battery which looks like it trying to do the same thing as greenify.
TheKnux said:
@Dameon87 is there any way you could possibly throw an OOS 9.0.7 stock kernel zip together if it's not too much to ask?
Click to expand...
Click to collapse
Dear,
I have created a stock kernel from 9.0.7 as per in the attachment.
Thanks.
Related
I've been searching the forum for a while, but most of the rooting guide are based on earlier version. Do i need to downgrade before rooting?
Gemichi said:
I've been searching the forum for a while, but most of the rooting guide are based on earlier version. Do i need to downgrade before rooting?
Click to expand...
Click to collapse
Yes you would need to downgrade, but since you have a T-Mobile version it's most likely not possible due to anti rollback
Sent from my iPhone using Tapatalk
hyelton said:
Yes you would need to downgrade, but since you have a T-Mobile version it's most likely not possible due to anti rollback
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
guess I'll need to wait till someone figure out a way to root 20r then...
Gemichi said:
guess I'll need to wait till someone figure out a way to root 20r then...
Click to expand...
Click to collapse
yes theres is... since hyelton already told you no downgrade.. that means no flashing 20i...
so youll be using the same procedure the same steps except flash 20i kdz.. youll will be doing all this on 20r.. so follow instructons . usiong same procedure just skip the flash 20i kdz.
https://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
raptorddd said:
yes theres is... since hyelton already told you no downgrade.. that means no flashing 20i...
so youll be using the same procedure the same steps except flash 20i kdz.. youll will be doing all this on 20r.. so follow instructons . usiong same procedure just skip the flash 20i kdz.
https://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Click to expand...
Click to collapse
sorry I haven't get on here for a while. Now my phone got updated to 20v, does the same method work? I saw your post about rooting on a 20r?
Gemichi said:
sorry I haven't get on here for a while. Now my phone got updated to 20v, does the same method work? I saw your post about rooting on a 20r?
Click to expand...
Click to collapse
yes, same thread, just do the steps about OEM Unlocking and Root. i would grab the most recent twrp image from here (3.1.1-1) and the latest SuperSU here (2.82 TWRP Installable Zip)
you will also need adb and fastboot tools on your pc, get that here, latest version is 1.4.3
or you can just flash twrp and then flash an already rooted system image for 20v from @MicroMod777 found here
Midnight_Rider said:
yes, same thread, just do the steps about OEM Unlocking and Root. i would grab the most recent twrp image from here (3.1.1-1) and the latest SuperSU here (2.82 TWRP Installable Zip)
you will also need adb and fastboot tools on your pc, get that here, latest version is 1.4.3
or you can just flash twrp and then flash an already rooted system image for 20v from @MicroMod777 found here
Click to expand...
Click to collapse
Thanks, I'll try to root it, hoping I can tweak more settings to get more battery life out of it. SOT is worst than everyone @[email protected]
Gemichi said:
Thanks, I'll try to root it, hoping I can tweak more settings to get more battery life out of it. SOT is worst than everyone @[email protected]
Click to expand...
Click to collapse
Did this work for you?
brt309 said:
Did this work for you?
Click to expand...
Click to collapse
Unfortunately (or fortunately) I traded it in for the s8 since I dropped it. Thought I was time to get rid of it before it loses any value. So I wasn't able to try it out...
Gemichi said:
Unfortunately (or fortunately) I traded it in for the s8 since I dropped it. Thought I was time to get rid of it before it loses any value. So I wasn't able to try it out...
Click to expand...
Click to collapse
Thanks, I just got my Note 8 I will keep my LG as a backup.
brt309 said:
Did this work for you?
Click to expand...
Click to collapse
I'm gonna try this in the morning I'm on 20v.
Hello Gentlemen,
I've recently got a OP3T running OOS 4.1.6 and i've been wanting to unlock the bootloader and root it. I've done my bit of a research and i'm little confused on what version of TWRP and SuperSU should i be using ? Do i still need to do the DM-Vertity bit? I'm considering just flashing:
TWRP: twrp-3.1.1-2-oneplus3t.img
SuperSU: SuperSU-v2.82-201705271822.zip
Would anyone be kind enough to point me to the latest guide for OP3T for OOS 4.1.6 ? Apologies,if this has been asked before.
Thanks!
Unlock your bootloader with fastboot oem unlock, then flash this version of TWRP:
https://drive.google.com/file/d/0B0pr-ZA5b-1peEVyVmpsbGZTbnM/view
Then you can flash either SuperSU: https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Or Magisk (which I'd personally reccomend): http://tiny.cc/latestmagisk
starsky135 said:
Unlock your bootloader with fastboot oem unlock, then flash this version of TWRP:
https://drive.google.com/file/d/0B0pr-ZA5b-1peEVyVmpsbGZTbnM/view
Then you can flash either SuperSU: https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Or Magisk (which I'd personally reccomend): http://tiny.cc/latestmagisk
Click to expand...
Click to collapse
Thanks mate. How is that TWRP you mentioned different from the other one for OP3T ?
Do i also need to flash the dm-verity disabler or is it not required if i flash the latest TWRP/SuperSU ?
Fermats_theorem said:
Thanks mate. How is that TWRP you mentioned different from the other one for OP3T ?
Do i also need to flash the dm-verity disabler or is it not required if i flash the latest TWRP/SuperSU ?
Click to expand...
Click to collapse
Could you link me to the TWRP you found? And I didn't have to flash dm-verity disabler while flashing it on my 3T with 4.1.6. Just be aware that all personal data is lost when the bootloader is unlocked.
starsky135 said:
Could you link me to the TWRP you found? And I didn't have to flash dm-verity disabler while flashing it on my 3T with 4.1.6. Just be aware that all personal data is lost when the bootloader is unlocked.
Click to expand...
Click to collapse
Hello mate,
This is what i've downloaded for TWRP.
https://dl.twrp.me/oneplus3t/twrp-3.1.1-2-oneplus3t.img.html
Fermats_theorem said:
Thanks mate. How is that TWRP you mentioned different from the other one for OP3T ?
Do i also need to flash the dm-verity disabler or is it not required if i flash the latest TWRP/SuperSU ?
Click to expand...
Click to collapse
Fermats_theorem said:
Hello mate,
This is what i've downloaded for TWRP.
https://dl.twrp.me/oneplus3t/twrp-3.1.1-2-oneplus3t.img.html
Click to expand...
Click to collapse
I'm not sure of the exact differences, but I think the blu_spark one I sent you might have fixed the dm-verity issues. I know that the one I sent you has no problems with dm-verity, so I'd go with that one just to be safe. There seem to be a lot of people bricking their phones by flashing the wrong one and I know this one works because I just flashed it yesterday.
starsky135 said:
I'm not sure of the exact differences, but I think the blu_spark one I sent you might have fixed the dm-verity issues. I know that the one I sent you has no problems with dm-verity, so I'd go with that one just to be safe. There seem to be a lot of people bricking their phones by flashing the wrong one and I know this one works because I just flashed it yesterday.
Click to expand...
Click to collapse
Do you have One Plus 3 or 3T ?
Fermats_theorem said:
Hello Gentlemen,
I've recently got a OP3T running OOS 4.1.6 and i've been wanting to unlock the bootloader and root it. I've done my bit of a research and i'm little confused on what version of TWRP and SuperSU should i be using ? Do i still need to do the DM-Vertity bit? I'm considering just flashing:
TWRP: twrp-3.1.1-2-oneplus3t.img
SuperSU: SuperSU-v2.82-201705271822.zip
Would anyone be kind enough to point me to the latest guide for OP3T for OOS 4.1.6 ? Apologies,if this has been asked before.
Thanks!
Click to expand...
Click to collapse
I got my phone 1 week ago and I just followed the guide here.
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
It seems quite straightforward.
Can't see what seems not clear for you.
Unleashed by ONEPLUS 3T rooted
Fermats_theorem said:
I've done my bit of a research and i'm little confused on what version of TWRP and SuperSU should i be using ?
Click to expand...
Click to collapse
Typically, you want to use the latest files available. So in this case, yes that would be TWRP 3.1.1-2 and SuperSU 2.82 (or alternately Magisk 13.3, totally a matter of preference SuperSU versus Magisk).
There are some cases, where a new version may have some bugs. But I haven't heard of any of these particular versions.
Using versions that are a little bit older may still work. But anything that is too old, will sometimes cause problems. Especially when Android versions have changed, root methods updated, etc.
Thanks folks, i've unlocked the bootloader and rooted it. After flashing the recovery it was asking me for the password and it couldn't access the internal storage. I flashed dm verity and Magisk via sideload though.
Now, I'm wondering what ROM do i try ? I'm looking at Freedom OS + Franco / ElementalX. I need a OOS based rom with a good battery backup. Any suggestions would be appreciated
Central project page
https://forum.xda-developers.com/xperia-xz2/development/recovery-twrp-3-3-1-0-t4074305
11.06.2020
Switch to TWRP 3.4.0
sodp twrp 2020-06 security patch level
stock twrp 2020-05 security patch level for firmware 52.1.A.2.1
Now both twrp should work without a ROM being installed (empty system/vendor/oem partitions) and still be able to decrypt your userdata.
Also the stock twrp touch should now always work instead of playing russian roulette.
Click to expand...
Click to collapse
13.06.2020
Thanks to the fixes in 3.4.0 we got now a TWRP with the following enhancements for STOCK and SODP:
- This TWRP will work with future 10.0 ROMs, you don't need a new build matching the security patch level of your ROM.
- You can install this TWRP again with the buildin ramdisk patcher. Please follow the installation instructions.
Click to expand...
Click to collapse
Please test and report back if you got any touch / decryption problems.
14.06.2020
Reuploaded the stock TWRP with a later touch kernel modules initialization.
Hopefully fixing the randomly happening not working touch.
Click to expand...
Click to collapse
did it work on sov39?
02.03.2021
Reuploaded the SODP TWRP with a workaround for Android 11 compatibility.
Click to expand...
Click to collapse
afandi.s said:
did it work on sov39?
Click to expand...
Click to collapse
Official only international models are unlockable.
MartinX3 said:
Official only international models are unlockable.
Click to expand...
Click to collapse
I have a japanese xz3 and the bl is unlocked
Alex5699 said:
I have a japanese xz3 and the bl is unlocked
Click to expand...
Click to collapse
Does the twrp work?
i never get one to fully work , i have fastboot boot one before to try and install a rom but i get bootloop. im stock rooted and remove bloatware thats it
Alex5699 said:
i never get one to fullow work , i have fastboot boot one before to try and install a rom but i get bootloop. im stock rooted and remove bloatware thats it
Click to expand...
Click to collapse
I made the same experience
Removing system apps -> bootloop
Maybe deactivating vbmeta will fix it.
Maybe in the misc partition is a good bootloop reason or in the ADB logcat.
I never researched it and just deactivated bloat apps.
MartinX3 said:
I made the same experience
Removing system apps -> bootloop
Maybe deactivating vbmeta will fix it.
Maybe in the misc partition is a good bootloop reason or in the ADB logcat.
I never researched it and just deactivated bloat apps.
Click to expand...
Click to collapse
you get bootloop if you use a system app remover app, you will have to use a root explore to remove those apps by deleting the folder or the apk thats inside it
have you tried it?, It work in sov39?, I have sov39 ubl yes like u..
FeLaks said:
have you tried it?, It work in sov39?, I have sov39 ubl yes like u..
Click to expand...
Click to collapse
Mine working on so-01l docomo but cant flash any custom rom because it always report error 1
FeLaks said:
have you tried it?, It work in sov39?, I have sov39 ubl yes like u..
Click to expand...
Click to collapse
How did you unlock your bootloader?
SaqibxNaeem said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
I bought it already got something like that, sorry if it doesn't help
SaqibxNaeem said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
Im using qunlocktool n credits from nugsm
Sir i did unlock my bootloader of sony xz3(sov39) and i have unlock Bl from sony website too
I have global rom install in it (H8416) 52.1.A.3.92
My android version is 10. Now i want to flash twrp but no idea which i have to flash or is there any TWRP which have no errors?
Kindly help
What errors?
MartinX3 said:
What errors?
Click to expand...
Click to collapse
When i flash twrp it says no folder found
HI all,
This isn't my first rodeo but I struggled to find a boot.img that I could patch in Magisk to get root especially since I do not believe the 2217 factory image has been released.
Anyhow, the following one worked for me and my TMO OnePlus Pro 10 NE2217 is rooted: Oxygen OS NE2213_11_A.12 Patched boot image.zip
Big thank you everyone who posted in the NE2215 and NE 2213 thread and dladz for posting the patched boot image.
Mario
mariojohn said:
HI all,
This isn't my first rodeo but I struggled to find a boot.img that I could patch in Magisk to get root especially since I do not believe the 2217 factory image has been released.
Anyhow, the following one worked for me and my TMO OnePlus Pro 10 NE2217 is rooted: Oxygen OS NE2213_11_A.12 Patched boot image.zip
Big thank you everyone who posted in the NE2215 and NE 2213 thread and dladz for posting the patched boot image.
Mario
Click to expand...
Click to collapse
More than welcome mate, glad you're sorted
How's it been? All ok?
Can I get that patched boot image zip file? I thought we could because oneplus hadn't release the bootloader for unlocking yet?
I'm sure there's a command to pull the boot image from a live device. I just can't remember it, think it's the same as the persist image pull but not sure, so if you don't have a full firmware to pull from then that could be the way forward.
jeffsga88 said:
You can just use the global patched boot.img and boot into it from fastboot and then go into Magisk and do direct install. There's no need for the T-Mobile specific boot.img to get root. I will post A.06 and A.07 unmodified boot.imgs later when I have a chance though, just can't right now.
Click to expand...
Click to collapse
Based on the posts in this thread, I don't think you need an NE2217 specific boot.img.. but this is just me remembering from seeing it on the forum.
Prant said:
Based on the posts in this thread, I don't think you need an NE2217 specific boot.img.. but this is just me remembering from seeing it on the forum.
Click to expand...
Click to collapse
Personally I'd always stick with my firmwares boot image, but hey if it works then brilliant
Have you try converting it to International?
DrakenFX said:
Have you try converting it to International?
Click to expand...
Click to collapse
I did but now I keep getting this app is disabled based on security strategy during the setup. Any ideas?
Thanks all for this post I was successful in rooting my T-Mobile OnePlus 10 pro.
Scararms said:
Thanks all for this post I was successful in rooting my T-Mobile OnePlus 10 pro.
Click to expand...
Click to collapse
Ok, call me slow, you said you were successful?? Can I ask how or where the directions are? How did you unlock the bootloader? Did you use the ne2213 boot.img? If so can i ask where you got it?
Thank you very much!
Frustrated_AF said:
Ok, call me slow, you said you were successful?? Can I ask how or where the directions are? How did you unlock the bootloader? Did you use the ne2213 boot.img? If so can i ask where you got it?
Thank you very much!
Click to expand...
Click to collapse
I have that boot image in my root / magisk guide.
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
Frustrated_AF said:
Ok, call me slow, you said you were successful?? Can I ask how or where the directions are? How did you unlock the bootloader? Did you use the ne2213 boot.img? If so can i ask where you got it?
Thank you very much!
Click to expand...
Click to collapse
I went the OnePlus unlock bootloader page for T-Mobile to get the unlock.bin then using the boot image from NE2213 i made a magisk boot image the flash it.
Is it possible to switch from ne2211 to ne2213
Using Oxygen updater with advanced mode
Yes!
Just download the NE2213 image from oxygen updater and using the OPLocalUpgrade.apk flash it.
zopostyle said:
Yes!
Just download the NE2213 image from oxygen updater and using the OPLocalUpgrade.apk flash it.
Click to expand...
Click to collapse
I install magisk app in my phone and install safety net module
I want to remove it and relock bootloader
After installing the new ROM or before
Can you help me in it
Abdelrahman_morshed said:
I install magisk app in my phone and install safety net module
I want to remove it and relock bootloader
After installing the new ROM or before
Can you help me in it
Click to expand...
Click to collapse
I would not relock the bootloader, there is no reason to.
Then just flash a full image.
zopostyle said:
I would not relock the bootloader, there is no reason to.
Then just flash a full image.
Click to expand...
Click to collapse
The reason to relock bootloader is many bank application doesn't work as see my phone is rooted due to bootloader unlocked
Abdelrahman_morshed said:
The reason to relock bootloader is many bank application doesn't work as see my phone is rooted due to bootloader unlocked
Click to expand...
Click to collapse
The problem is not the bootloader unlocked. Its the root.
Mine is unlocked and I can do anything..
Anyways, if you really wat to relock, You need to do it after flash the new image, otherwise if something goes wrong you'll brick your device.
zopostyle said:
The problem is not the bootloader unlocked. Its the root.
Mine is unlocked and I can do anything..
Click to expand...
Click to collapse
It's say application doesn't work on rooted phone
And this was before installing magisk app or root
Just after flashing the ROM
May be the rom is not stock rom
So where I can find a stock ROM to flash it ?
Abdelrahman_morshed said:
It's say application doesn't work on rooted phone
And this was before installing magisk app or root
Just after flashing the ROM
May be the rom is not stock rom
So where I can find a stock ROM to flash it ?
Click to expand...
Click to collapse
In oxygen updater, there you can find links to flash the full image.
Maybe you need to flash it using: https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
zopostyle said:
In oxygen updater, there you can find links to flash the full image.
Maybe you need to flash it using: https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Click to expand...
Click to collapse
Thanks for your help
But Oxygen updater give me the same Indian ROM and I want to change to global ROM
Download this package: https://oxygenos.oneplus.net/2354_sign_NE2213_11_A_OTA_0120_all_9f570f_01000100.zip
And apply it using this apk https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Source: https://oxygenupdater.com/article/346/
zopostyle said:
Download this package: https://oxygenos.oneplus.net/2354_sign_NE2213_11_A_OTA_0120_all_9f570f_01000100.zip
And apply it using this apk https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Source: https://oxygenupdater.com/article/346/
Click to expand...
Click to collapse
Thank you very much for your help
IAM grateful
If I install this ROM I will receive updates normally or I must download it manually
Yes, it will work as it it's original.
oficial updates and so on.
zopostyle said:
Yes, it will work as it it's original.
oficial updates and so on.
Click to expand...
Click to collapse
Thank you very much
Do you need to Reset phone when crossing from NE2215 to NE2213? Or will transit/update without the need to factory reset?
wmfreakrom said:
Do you need to Reset phone when crossing from NE2215 to NE2213? Or will transit/update without the need to factory reset?
Click to expand...
Click to collapse
It should be needed to factory reset during the process.
Has anyone done it and can give some certain feedback? Thanks
I’m using the updater on an NE2211 and downloading the NE2215 full package, but when I go to local install, it says verification failed. I tried to download the local updater Apk, but it saves as a .ZIP and asks me to extract 1,200 files. Don’t think that’s right, but I don’t know.
SwissNix said:
I’m using the updater on an NE2211 and downloading the NE2215 full package, but when I go to local install, it says verification failed. I tried to download the local updater Apk, but it saves as a .ZIP and asks me to extract 1,200 files. Don’t think that’s right, but I don’t know.
Click to expand...
Click to collapse
Disregard.
Abdelrahman_morshed said:
The reason to relock bootloader is many bank application doesn't work as see my phone is rooted due to bootloader unlocked
Click to expand...
Click to collapse
You should never relock bootloader if any non-stock is installed. This will surely brick the device.
If you restore EVERYTHING back to stock (recovery, ROM, etc.), then you can relock the bootloader.