[Q] Re-locking Bootloader with TWRP and Root - OnePlus 3 Guides, News, & Discussion

Quick question: will my phone boot with TWRP and root installed if I re-lock my OnePlus 3's Bootloader? I don't plan on flashing any custom ROMs and kernels until the Dash Charge driver is implemented, which is not for a while; however, I still wish to be able to boot into recovery and perform root-related operations on my device. I'm pretty tired of seeing the Secure Boot warning about unlocked Bootloader.
Edit: Whoops, I didn't mean to post in the Discussion and Guides section of the forums... My B; I'll be more careful next time

Can't do it. Your phone will brick itself until you are stock.

Whene i unroot and flash stock recovery can i re lock?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

Related

RAZR i Root 2 (Jellybean 4.1.2)

Since the ICS root files fail to work on Jellybean, needed to work with new files to make it work. This is based off the open-source ChainsDD Superuser 3.2 (RC) x86 version, with an update-binary from the RAZR i to make sure it flashes.
On top of this, I added a live to remove /system/etc/install-recovery.sh. This is because whenever the phone booted, it removed CWM, and thats definitely not something we wanted it to do! So all is well. This file (RAZRiRoot2.zip) is included in the new Jellybean Vodafone (FR) Homemade fastboot of mine also. Its less automated for rooting since the boot.img method is weird with Windows drivers...
Anyway, here we go.
Requirement(s):
Unlocked Bootloader on Jellybean
Download:
http://batakang.com/ftp/RAZRi/RootUtility/RAZRiRoot2.zip
Instructions:
Flash this in CWM to root any Jellybean RAZR i firmware.
nice Bro.
:angel:
I have stock recovery. How can i put CWM in my phone? The flasher tool doesnt seem to work now...
tatazeuz said:
I have stock recovery. How can i put CWM in my phone? The flasher tool doesnt seem to work now...
Click to expand...
Click to collapse
Same here for me
Edit - I was able after some trial and error to boot into CWM using ADB and flash this. The problem is that CWM is lost and wont work after I reboot to bootloader/normal powerup. If I want to ever boot into CWM 'on-the-go' it is now impossible. Each time i wish to use CWM i have to plug in and re-flash using ADB. Flippin' weird if you ask me.
What adb commands did you use?
Sent from my XT890 using xda premium
tatazeuz said:
I have stock recovery. How can i put CWM in my phone? The flasher tool doesnt seem to work now...
Click to expand...
Click to collapse
The flash tool required root. Fastboot it yourself
Sent from my Galaxy Nexus using Tapatalk 2
After fastboot flash recovery cwm.img, how do we boot it? For me it flashes without error then boots to stock recovery.
Sent from my XT890 using xda premium
batwingnz said:
After fastboot flash recovery cwm.img, how do we boot it? For me it flashes without error then boots to stock recovery.
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
You choose Recovery from fastboot, then flash the RAZRiRoot2.zip.
If you boot normally then it will wipe CWM, since the root zip never ran to remove the install-recovery.sh
flash CWM + reroot
batwingnz said:
What adb commands did you use?
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
I have used:
from windows cmd, with USB debugging on
adb reboot bootloader
fastboot.exe flash recovery recovery-razri-tryAtouch.img
fastboot.exe reboot-bootloader
selected recovery and installed the RAZRiRoot2.zip from external storage card.
now rebooted and my Jelly Bean is rooted and CWM remained the recovery
is there any way to get supersu working instead of superuser app? some apps are only working with supersu somehow... e.g. light manager.. light manager needs root to work with some apps, but the superuser app does never recognize light manager attempts.... any idea?
fattymcdirty said:
is there any way to get supersu working instead of superuser app? some apps are only working with supersu somehow... e.g. light manager.. light manager needs root to work with some apps, but the superuser app does never recognize light manager attempts.... any idea?
Click to expand...
Click to collapse
There is no SuperSu x86 binary.
AW: RAZR i Root 2 (Jellybean 4.1.2)
batwingnz said:
After fastboot flash recovery cwm.img, how do we boot it? For me it flashes without error then boots to stock recovery.
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=37518364
Sent from my XT910 using Ocean Avenue [JB]
HSD-Pilot said:
http://forum.xda-developers.com/showthread.php?p=37518364
Sent from my XT910 using Ocean Avenue [JB]
Click to expand...
Click to collapse
HSD-Pilot, thanks for the response. I should've come back and edited post to advised solved using fastboot, have since moved from VFR jellybean to EU Retail jellybean and been able to get root back easily using fastboot boot cwm.img, then flashing razriroot2.zip in cwm.
Only issue so far was force closing contacts app - cleared data for that app alone and it's solved.
I will buy a Razr i and I wanna know if I can first update for Jelly Bean via OTA and after this finally unlock the bootloader and so root this... If it´s possible, it´s better unlock de bootloader before or after JB update?
AW: RAZR i Root 2 (Jellybean 4.1.2)
WendelSchelhan said:
I will buy a Razr i and I wanna know if I can first update for Jelly Bean via OTA and after this finally unlock the bootloader and so root this... If it´s possible, it´s better unlock de bootloader before or after JB update?
Click to expand...
Click to collapse
Yes you can update via OTA first. It doesn't matter if you unlock before or after it. But root after OTA with RAZR I Root 2 through cwm.
Gesendet von meinem Motorola RAZR i - gerootet & unlocked
Good! If I want to unlock the BL on JB, should I use the zip file of this thread or the zip file of the "Unlock the bootloader"? Is someone working in a locked bootloader rooting tool? Because I saw on a brazillian topic a way to root wihout unlock the BL, but only Ice Cream Sandwich..
Thanks!
AW: RAZR i Root 2 (Jellybean 4.1.2)
WendelSchelhan said:
Good! If I want to unlock the BL on JB, should I use the zip file of this thread or the zip file of the "Unlock the bootloader"? Is someone working in a locked bootloader rooting tool? Because I saw on a brazillian topic a way to root wihout unlock the BL, but only Ice Cream Sandwich..
Thanks!
Click to expand...
Click to collapse
The zip file of this thread is only for rooting. To unlock you need adb and fastboot software/driver on your PC. I think you can download this from the unlock thread.
Yes root without unlocked bootloader only work with the old ICS version ( 31002)
Gesendet von meinem Motorola RAZR i - gerootet & unlocked
cupioscire said:
The zip file of this thread is only for rooting. To unlock you need adb and fastboot software/driver on your PC. I think you can download this from the unlock thread.
Yes root without unlocked bootloader only work with the old ICS version ( 31002)
Gesendet von meinem Motorola RAZR i - gerootet & unlocked
Click to expand...
Click to collapse
Probably I will update to Jelly via OTA, wait a little more time (to see if the phone came working well and wait for a rooting tool wihout bootloader unlocked). When you talk about CWM, it´s just install this apllication after unlock boot? So I go to an option like LOAD ROM or something and select the zip file?
AW: RAZR i Root 2 (Jellybean 4.1.2)
Originally Posted by cupioscire<br />
The zip file of this thread is only for rooting. To unlock you need adb and fastboot software/driver on your PC. I think you can download this from the unlock thread. <br />
Yes root without unlocked bootloader only work with the old ICS version ( 31002)<br />
<br />
Gesendet von meinem Motorola RAZR i - gerootet & unlocked
Click to expand...
Click to collapse
<br />
Probably I will update to Jelly via OTA, wait a little more time (to see if the phone came working well and wait for a rooting tool wihout bootloader unlocked). When you talk about CWM, it´s just install this apllication after unlock boot? So I go to an option like LOAD ROM or something and select the zip file?
Click to expand...
Click to collapse
No I mean clockworkmod recovery, a custom recovery which allows you to backup your ROM and install custom ROMs and stuff like this. To install cwm on RAZR I you have to flash a cwm.img via fastboot.
I don't know if rom-manager app support RAZR i, but i don't think so.
And I don't think that there will be a rooting tool for unlocked bootloaders for jelly bean.
Gesendet von meinem Motorola RAZR i - gerootet & unlocked
cupioscire said:
No I mean clockworkmod recovery, a custom recovery which allows you to backup your ROM and install custom ROMs and stuff like this. To install cwm on RAZR I you have to flash a cwm.img via fastboot.
I don't know if rom-manager app support RAZR i, but i don't think so.
And I don't think that there will be a rooting tool for unlocked bootloaders for jelly bean.
Gesendet von meinem Motorola RAZR i - gerootet & unlocked
Click to expand...
Click to collapse
Thanks! My phone actually is a Optimus L7, wich LG haven´t unlocked the bootloader, so I heard about recovery, custom recovery, Clockworkmod and other stuffs, but I have no clever idea of what are these tings (xda video was right, i´m a noob.. haha). Just a few more questions:
1- Fastboot is what we got after pressing the power button with Volume- button, right? It´s like a normal PC bios. How can I use this menu? Look like they are too small to touch, so something like Volume+ to Enter and Volume- to navigate in the options.
2- I need CWM to root, or can I use Fastboot?
3- To flash CWM (or root, if possible) in Fastboot I need to use the computer or I can flash the files in the SD card only using the cell phone?

How to Relock Bootloader on the Oneplus 3

There seems to be guides for how to unlock and root the oneplus 3 but no real way that explains how to lock the bootloader again. I just did and will these sets of instructions. I was nervous about doing it since I read a lot about how some people had issues. I did it this way and had no issue. Also, my thoughts were confirmed ahead of time by a pots I found by nightfox7. So here it is laid out.
This is assuming your on a custom rom and/or rooted.
1. download latest oxygenos full rom (full stock rom)
2. flash via TWRP (this shoud replace TWRP with stock recovery)
3. If stock recovery is not replaced be sure to flash it from the bootloader
4. Go ahead and load the full stock rom again vis adb sideload in the stock recovery
4. boot your phone and be sure that your phone is set to usb debugging.
5. boot into bootloader and lock bootloader via the following command
fastboot oem lock
It worked for me. But I'm not responsible if you have problems
GCbard said:
There seems to be guides for how to unlock and root the oneplus 3 but no real way that explains how to lock the bootloader again. I just did and will these sets of instructions. I was nervous about doing it since I read a lot about how some people had issues. I did it this way and had no issue. Also, my thoughts were confirmed ahead of time by a pots I found by nightfox7. So here it is laid out.
This is assuming your on a custom rom and/or rooted.
1. download latest oxygenos full rom (full stock rom)
2. flash via TWRP (this shoud replace TWRP with stock recovery)
3. If stock recovery is not replaced be sure to flash it from the bootloader
4. Go ahead and load the full stock rom again vis adb sideload in the stock recovery
4. boot your phone and be sure that your phone is set to usb debugging.
5. boot into bootloader and lock bootloader via the following command
fastboot oem lock
It worked for me.
Click to expand...
Click to collapse
Thanks, it may be usefull. But are you sure you have to be on stock rom ?
Lowxorx said:
Thanks, it may be usefull. But are you sure you have to be on stock rom ?
Click to expand...
Click to collapse
You can relock without being on stock ROM, but this will brick your phone
2x4 said:
You can relock without being on stock ROM, but this will brick your phone
Click to expand...
Click to collapse
Okay thanks for your answer [emoji6]
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
I'm in the process of returning my op3, I'm on 3.2.6 I think i have stock recovery because my twrp got overridden by a stock one that asks to choose language and has those bubbles as a background, that's stock right?
And will locking bootloader wipe internal storage?
After relocking we go to settings and untick OEM unlock?
xAD3r1ty said:
I'm in the process of returning my op3, I'm on 3.2.6 I think i have stock recovery because my twrp got overridden by a stock one that asks to choose language and has those bubbles as a background, that's stock right?
And will locking bootloader wipe internal storage?
After relocking we go to settings and untick OEM unlock?
Click to expand...
Click to collapse
I think it's stock recovery.
Locking bootloader will erase userdata.
I don't know if you have to uncheck the option after locking your bootloader.
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
@GCbard
hello, how to lock the bootloader on cutom rom, i don't want to be on Stock OOS 9.0.6.
i have flashed HAVOC Q/LOS Q & i want to lock bootloader, how to do that? please support.
rohan164 said:
@GCbard
hello, how to lock the bootloader on cutom rom, i don't want to be on Stock OOS 9.0.6.
i have flashed HAVOC Q/LOS Q & i want to lock bootloader, how to do that? please support.
Click to expand...
Click to collapse
It is not a good practice to lock the bootloader while on a custom ROM. If you face any issues in future, the first requirement to sort out those issues would be an unlocked bootloader. You will be stuck with a locked bootloader.
The forums are full of threads/posts of people on custom ROMs asking how to unlock or bypass the unlocking.

NO TWRP

Hey guys i have question today i flash twrp via odin and after flashing i boot in twrp and make wipe data..Than i reboot to system and set phone configuration...but than i try again boot to twrp and wtf...only stock recovery is there no twrp but knox is tripped 0x1 everytime i reboot to recovery is only stock recovery i have sm n950f exynos i find tutorial here on xda
Any fix, solution or suggestion please
Poslano z mojega SM-N950F z uporabo Tapatalk
What was your stock firmware before you tried to root your device (nougat, Oreo)? Which TWRP version you used? Have you flashed the no-varity-opt-encrypt zip file after flashing TWRP? Which Odin version you have used?
Have you rebooted into TWRP after format data partition?
You see, questions over questions. To help you useful we need much more informations.
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
What was your stock firmware before you tried to root your device (nougat, Oreo)? Which TWRP version you used? Have you flashed the no-varity-opt-encrypt zip file after flashing TWRP? Which Odin version you have used?
Have you rebooted into TWRP after format data partition?
You see, questions over questions. To help you useful we need much more informations.
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
I work with this tutorial https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-note8-efs-backup-t3677038
i root it now but dont know does twrp stay or is gone
i have Oreo N950FXXURCRB9 this is April security patch
Yes i format data partition after that i reboot and set my phone like first time after that i want reboot again to twrp but there no twrp is only stock recovery today i try again but now i after format data partition go back and flash supersu after that i reboot to system and set my phone now i have supersu but nonstop i got security warning something like Security Agent found app which is maybe malware or something like that i think security agent found supersu is possible disable it this warning
The "How to" method from Dr. Ketan isn't the best. It's based on flashing his Rom after flash TWRP and root.
Best "how to" is this from geiti94
https://forum.xda-developers.com/showthread.php?p=73817280
You only need newest TWRP version from zeroblade if you on Oreo firmware and Odin v3.13.1.
For your security warning issue you only need to delete the securityLogAgent.apk in system/app/
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
The "How to" method from Dr. Ketan isn't the best. It's based on flashing his Rom after flash TWRP and root.
Best "how to" is this from geiti94
https://forum.xda-developers.com/showthread.php?p=73817280
You only need newest TWRP version from zeroblade if you on Oreo firmware and Odin v3.13.1.
For your security warning issue you only need to delete the securityLogAgent.apk in system/app/
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
Does i must use dm-verity and force encryption disabler???? Like i say i have now root access and work fine but only dont know does i have twrp im scare to boot in what can i do in case if i again not have twrp and only stock recovery
If you don't have TWRP you need to flash it again. Including format data partition again. And yes, you need the no varity opt encrypt app file!
You could boot into TWRP and check if you can mount data. If you can't, your data partition is still encrypted.
If you want to flash a custom Rom or a flashable zip, you need a custom recovery like TWRP. So i would make this work at first.
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
If you don't have TWRP you need to flash it again. Including format data partition again. And yes, you need the no varity opt encrypt app file!
You could boot into TWRP and check if you can mount data. If you can't, your data partition is still encrypted.
If you want to flash a custom Rom or a flashable zip, you need a custom recovery like TWRP. So i would make this work at first.
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
I download an app from play store named reboot to recovery and when i run it phone shutdown and boot in twrp so thats means i have twrp i see its 3.2.1.0 version but how check does can i mount data partition?
btw i go to twrp than mount and i try mount DATA but twrp wont check it so i think i have encyrpted..so how fix that without lose everything or wipe anything
No. If i know right, you get an error message if mounting data isn't possible
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
No. If i know right, you get an error message if mounting data isn't possible
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
what if i flash dm verify
blinkt88 said:
what if i flash dm verify
Click to expand...
Click to collapse
Normally, on every device boot, the system is checking if data partition is encrypted. If it isn't, it will encrypt it again.
With that zip file, the encryption on boot-check will be disabled.
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
Normally, on every device boot, the system is checking if data partition is encrypted. If it isn't, it will encrypt it again.
With that zip file, the encryption on boot-check will be disabled.
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
So what can i do now to can mount data if i need it..i want flash Zero Camera Mod but i think without mounted data i cant or im wrong means?Any idea?maybe in future i flash custom rom so how fix my problem
Poslano z mojega SM-N950F z uporabo Tapatalk
Try flash what you want. Maybe your data partition is unencrypted and it works.
If not, you need to do the procedure with format data partition again.
Gesendet von meinem SM-N950F mit Tapatalk

[N950F Dual Sim] How to Root properly

Hi, Good Day Everyone...
After the second failure of installing Magisk, i've kinda frustrating, Just want to move from my N9208 quickly. I have latest Oreo Rom installed on my N950F Dual Sim (N950FXXS3CRDB). Waiting a week for the next try is really pain.... (Right i will wait for the next week to try again :crying
I've searching some of tutorial, but it's weird doesn't work. I think i did wrong Step on process. Please help in details for this.
what I did:
1. Boot to Download Mode
2. using Odin 3.12.3 install twrp-3.1.1-0-greatlte_V3.tar ( is this wrong? because there are Odin 3.13.1 and twrp 3.2.1.0 version out there)
3. before start Flashing, (in Odin, Auto Reboot and F. Reset Time is ticked) i hold Vol down + Bixby Button + Power Button and then click Start on Odin.
4. After that, i successfully get into TWRP
5. in this step, i confused, what should i choose, Read only or Swipe to allow Modification? two times i choose Read Only
6. after this, i did Format Data, and then back to Main Menu, and Select Reboot -> to Recovery
7. after re-Enter TWRP, i still not sure, Read only or Swipe to allow Modification? i still click Read Only
8. and then i Install Magisk-v16.0.zip (there is Magisk-v16.3.zip out there again... i wonder if this causing the problem)
9. after this, i reboot to system... i think i've been Successful. After a first setup, Magisk icon are there. but, Root not detected. When i try do install from inside Magisk app, i download the magisk, and when i try to get back into TWRP, only official binaries is happened...
which step i've missed?
on some tutorial, they said we must swipe to allow modification on step 5, the other said we must keep Read Only
Other thing i've read, they said we need to flash fix mount data from dr.ketan everytime , afteri flashed something on TWRP
How to properly install Magisk and got Root and safely get in to TWRP anytime we need to? PLease Guide me. I think it should help anyone with the same problem.
Big Thanks in Advance...
you forgot to install dm-no-verity before root with Magisk. and you should use the most recent TWRP version 3.2.1.0 that supports Oreo as well as Nougat
vriend80 said:
Hi, Good Day Everyone...
After the second failure of installing Magisk, i've kinda frustrating, Just want to move from my N9208 quickly. I have latest Oreo Rom installed on my N950F Dual Sim (N950FXXS3CRDB). Waiting a week for the next try is really pain.... (Right i will wait for the next week to try again :crying
I've searching some of tutorial, but it's weird doesn't work. I think i did wrong Step on process. Please help in details for this.
what I did:
1. Boot to Download Mode
2. using Odin 3.12.3 install twrp-3.1.1-0-greatlte_V3.tar ( is this wrong? because there are Odin 3.13.1 and twrp 3.2.1.0 version out there)
3. before start Flashing, (in Odin, Auto Reboot and F. Reset Time is ticked) i hold Vol down + Bixby Button + Power Button and then click Start on Odin.
4. After that, i successfully get into TWRP
5. in this step, i confused, what should i choose, Read only or Swipe to allow Modification? two times i choose Read Only
6. after this, i did Format Data, and then back to Main Menu, and Select Reboot -> to Recovery
7. after re-Enter TWRP, i still not sure, Read only or Swipe to allow Modification? i still click Read Only
8. and then i Install Magisk-v16.0.zip (there is Magisk-v16.3.zip out there again... i wonder if this causing the problem)
9. after this, i reboot to system... i think i've been Successful. After a first setup, Magisk icon are there. but, Root not detected. When i try do install from inside Magisk app, i download the magisk, and when i try to get back into TWRP, only official binaries is happened...
which step i've missed?
on some tutorial, they said we must swipe to allow modification on step 5, the other said we must keep Read Only
Other thing i've read, they said we need to flash fix mount data from dr.ketan everytime , afteri flashed something on TWRP
How to properly install Magisk and got Root and safely get in to TWRP anytime we need to? PLease Guide me. I think it should help anyone with the same problem.
Big Thanks in Advance...
Click to expand...
Click to collapse
Me myself, i select always "swipe to allow modifications"
Since you are on Oreo use Odin 3.13.1 and TWRP 3.2.1-2 by Tkkg1994:
https://forum.xda-developers.com/showpost.php?p=76514731&postcount=741
After you format data with the "yes" command and reboot into recovery you need to flash the
No verity opt encrypt zip from here (use the latest 6.0):
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Also you need the RMM state fix! (IMPORTANT)
You will find the flashable zip file here:
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
After that flash magisk.zip or SuperSU.zip to root your device.
After first boot in setup wizard uncheck diagnostic data.
Then enable the developer options and check if the OEM Toogle is available and enabled! (IMPORTANT) with rooted device this toggle must available and enabled all the time! If not, you will get in jail again after a phone reboot.
Gesendet von meinem SM-N950F mit Tapatalk
khoanb1 said:
you forgot to install dm-no-verity before root with Magisk. and you should use the most recent TWRP version 3.2.1.0 that supports Oreo as well as Nougat
Click to expand...
Click to collapse
Logel said:
Me myself, i select always "swipe to allow modifications"
Since you are on Oreo use Odin 3.13.1 and TWRP 3.2.1-2 by Tkkg1994:
https://forum.xda-developers.com/showpost.php?p=76514731&postcount=741
After you format data with the "yes" command and reboot into recovery you need to flash the
No verity opt encrypt zip from here (use the latest 6.0):
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Also you need the RMM state fix! (IMPORTANT)
You will find the flashable zip file here:
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
After that flash magisk.zip or SuperSU.zip to root your device.
After first boot in setup wizard uncheck diagnostic data.
Then enable the developer options and check if the OEM Toogle is available and enabled! (IMPORTANT) with rooted device this toggle must available and enabled all the time! If not, you will get in jail again after a phone reboot.
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
Ah, i forgot to mention that i did flash dm verity on step 8 before flash Magisk.
But i didn't use rmm fix, i just read about that too.
Big thank you for explaining this in details.
A few more question:
1. should i Reboot to twrp after flash dm-verity and rmm fix too? Or is it ok to flash it in a single shot ( dm-verity -> rmmfix -> Magisk ) ?
2. When all is done, i think we can go into system right now, and make sure oem unlock toggle showing and always switched on. So i must not reboot if the toggle not show up?
3. What is get in jail means? Is that means Wait for another week?
4. So i don't need mount data fix from dr.ketan?
Thank you so much @Logel for the explanation
vriend80 said:
Ah, i forgot to mention that i did flash dm verity on step 8 before flash Magisk.
But i didn't use rmm fix, i just read about that too.
Big thank you for explaining this in details.
A few more question:
1. should i Reboot to twrp after flash dm-verity and rmm fix too? Or is it ok to flash it in a single shot ( dm-verity -> rmmfix -> Magisk ) ?
2. When all is done, i think we can go into system right now, and make sure oem unlock toggle showing and always switched on. So i must not reboot if the toggle not show up?
3. What is get in jail means? Is that means Wait for another week?
4. So i don't need mount data fix from dr.ketan?
Thank you so much @Logel for the explanation
Click to expand...
Click to collapse
1. You should can flash it in a single shot
2. No. Don't reboot if you don't see the OEM Toggle. See answer for point 3
3. Correct. In jail means, you can't reboot your phone. You will get a black screen with a red information line and the only way is to flash a stick Rom again. And after flash a stock Rom in most cases you have to wait again 168 hours until the OEM Toggle is visible again.
4. Nope. You have all fixed by yourself [emoji6][emoji106]
5. If you don't see the OEM Toggle you can use the phone. You only may not reboot it for the next 168 hours! After that time the OEM Toggle should be visible again. Now you can enable the toggle and reboot as often you want
Sent from my SM-N950F using Tapatalk
Is the info in this thread also valid for the N950N?
Thanks...
rljuss said:
Is the info in this thread also valid for the N950N?
Thanks...
Click to expand...
Click to collapse
yes it's the same since N950N and N950F are both Exynos variants
Logel said:
1. You should can flash it in a single shot
2. No. Don't reboot if you don't see the OEM Toggle. See answer for point 3
3. Correct. In jail means, you can't reboot your phone. You will get a black screen with a red information line and the only way is to flash a stick Rom again. And after flash a stock Rom in most cases you have to wait again 168 hours until the OEM Toggle is visible again.
4. Nope. You have all fixed by yourself [emoji6][emoji106]
5. If you don't see the OEM Toggle you can use the phone. You only may not reboot it for the next 168 hours! After that time the OEM Toggle should be visible again. Now you can enable the toggle and reboot as often you want
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Wahhh, Excellent Explanations... Thank you very Much @Logel for the answers... I just need to read this carefully and slowly before proceeding the third chance. :good:
Hi @Logel ,
Today my Oem Unlock Button is re appear. I just don't want to fail again.
I want to ask, what is Samsung AntiRoot Removal? is that necessary to use in Root Process?
Thank you in Advance
Good morning
What is Samsung anti root removal? I think i never heard it before
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
Good morning
What is Samsung anti root removal? I think i never heard it before
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
oh, i think i shouldn't use it.
thank you for confirmation. Preparing to root for the third times... :laugh:
Good luck, mate ?
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
Good luck, mate ?
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
@Logel ,
I've Just Done Installing TWRP and Magisk.
this is first Boot, already initial setup, and then, when i open Magisk, it's not installed. what happened?
Oem Unlock is Visible right Now. i need to install Magisk 16.0 again.
when i was on first try two weeks ago, after reboot i got jailed when trying to install Magisk 16.0 again. Please look at my Attachment.
Thank you @Logel
Sorry for late answer. I was busy.
If your OEM toggle is visible and unlocked (like in your ss) all is fine. Also if you have flushed the RMM state fix you are safe.
Now you should can reboot as often you want!
I always use supersu instead magisk, so i can't really tell you what to do. I would recommend to reboot into twrp recovery and flash the magisk zip again.
Have you flashed a custom Rom?
It looks a bit strange. You haven't magisk installed, but you successful passed safetyNet.
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
Sorry for late answer. I was busy.
If your OEM toggle is visible and unlocked (like in your ss) all is fine. Also if you have flushed the RMM state fix you are safe.
Now you should can reboot as often you want!
I always use supersu instead magisk, so i can't really tell you what to do. I would recommend to reboot into twrp recovery and flash the magisk zip again.
Have you flashed a custom Rom?
It looks a bit strange. You haven't magisk installed, but you successful passed safetyNet.
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
Hi, I'm not using Custom ROM, i'm using Stock ROM. i Think i'll try re-flash Magisk and see what will happen.
Thank you so Much @Logel for your Help
Just want to Report, i successfully installed Magisk an now it's rooted.
Now i'll try Systemless Xposed INstaller, hope this work.
Thanks again Mate @Logel for your Help
Update:
Install Systemless xposed on my N950F DS cause reboot immediately after first reboot. i Think it's not safe to use systemless xposed right now.
updtae 2:
Right Now, I'am using Xposed Installer without a problem.

Relocking the bootloader after Android 10 update

Hi all,
I unlocked the bootloader of my Mi A2 (6GB/128GB model) many patches ago to enable Camera2API.
The guide I used can be found here: https://forum-xda--developers-com.c...to/how-to-enabling-cam2-gcam-android-t3868766
Now that I have Android 10 (stock with the latest update via OTA) the Camera2API corrupts my stock Mi cam, so I planned on doing a factory reset.
However, that does still leave my bootloader unlocked. Is there a safe and simple way to relock my bootloader?
I've heard some stories about bricking the device, so I wanted to ask you guys to see if it's safe.
Thanks in advance!
What did you do? I'm in the same situation
Enviado desde mi Mi A2 mediante Tapatalk
RemmyDZ said:
Hi all,
I unlocked the bootloader of my Mi A2 (6GB/128GB model) many patches ago to enable Camera2API.
The guide .....
However, that does still leave my bootloader unlocked. Is there a safe and simple way to relock my bootloader?
I've heard some stories about bricking the device, so I wanted to ask you guys to see if it's safe.
Thanks in advance!
Click to expand...
Click to collapse
okay i want to do that too but im still waiting for next patch because i need stock cam as well
but if you have stock rom fully installed then you dont have to worry about getting bricked because relocking will hurt only in case of custom rom installed!!
It's safe to relock bootloader ONLY if you are on:
- Stock ROM
- Stock boot image
- No Magisk or other mod.
Then, you can type
Code:
fastboot flashing lock
in Fastboot Mode, then confirm from your phone using physical buttons (Volume Down + Power).
Remember that this process wipe everything from your phone, like a factory reset. Backup your data first!
MentalBreach said:
It's safe to relock bootloader ONLY if you are on:
- Stock ROM
- Stock boot image
- No Magisk or other mod.
Then, you can type
Code:
fastboot flashing lock
in Fastboot Mode, then confirm from your phone using physical buttons (Volume Down + Power).
Remember that this process wipe everything from your phone, like a factory reset. Backup your data first!
Click to expand...
Click to collapse
Did you update with bootloader unlocked ? I haven't unlocked critical bootloader.
Because I am afraid of bricking the phone while updating to android 10 with bootloader unlocked and camera api2 enabled.
Please help me! Should I locked the bootloader ?
In fact, I tried to lock with command "fast OEM lock" but it failed.
I did not mod the device except enabling api2.

Categories

Resources