So i ticked the oem unlock and my phone reeboted, after the the wipe the option is nkt there anymore and when i try to flash twrp with odin i get this "Only Official released binaries are allowed to be flashed(RECOVERY)"
Fmikati said:
So i ticked the oem unlock and my phone reeboted, after the the wipe the option is nkt there anymore and when i try to flash twrp with odin i get this "Only Official released binaries are allowed to be flashed(RECOVERY)"
Click to expand...
Click to collapse
Same thing happened with me. I switched on the OEM unlock and did the factory reset. After that the OEM unlock was gone. However, 7 days later (This morning) the OEM switch is back and it is switched on, which means I can go ahead and root now, so you will need to wait the additional 7 days and then you should be good
Thanks for the reply, let me know if the root works and which/who's method did you use.
tfaletau said:
Same thing happened with me. I switched on the OEM unlock and did the factory reset. After that the OEM unlock was gone. However, 7 days later (This morning) the OEM switch is back and it is switched on, which means I can go ahead and root now, so you will need to wait the additional 7 days and then you should be good
Click to expand...
Click to collapse
Fmikati said:
Thanks for the reply, let me know if the root works and which/who's method did you use.
Click to expand...
Click to collapse
OK, so I was able to flash TWRP using ODIN - Use the guide by @dr.ketan
He has a zip you can download and flash after flashing TWRP, but I did not use that, I immediately flashed the TGP ROM, which has an Aroma installer and includes Magisk root, then before rebooting, I flashed the RMMstate_bypass. The ROM loaded fine, but I was getting systemui fcs, which was due to setting up intelliscan. I disabled that, but still had systemui fcs, so I needed to reboot. I checked developer options and the OEM unlock switch was gone again, however, I had to reboot. When I did, the rom rebooted fine and worked perfectly. Since then, I have rebooted more than 10 times with no issue. The OEM unlock option is still not available, but that does not matter as it is obviously unlocked. Bottome line, you should see the OEM unlock again after 7 days and you should be able to root.
Related
I haven't used my Nexus in about a month and the last time I used it, I had flashed a new rom with the wrong gapps. It was a fresh factory reset and whenever it booted up, I would get error messages and I wouldn't be able to do the initial set up. At the time, this was nothing I couldn't fix, but I had to put it aside because I was busy.
Fast forward to present day, I completely forgot about it. I locked the device, flashed stock recovery and did another factory reset. Now whenever I try to turn it on I get stuck at a black screen with error messages (I can't do initial setup). I can't install a new rom because the device is locked and I can't unlock it because it's OEM locked and I can't get into the OS.
Am I screwed or can I still pull off a miracle?
Wug's Nexus Root Toolkit! There are tons of video tutorials on YouTube that should help.
Sent from my Nexus 6 using Tapatalk
Go_Radio said:
I haven't used my Nexus in about a month and the last time I used it, I had flashed a new rom with the wrong gapps. It was a fresh factory reset and whenever it booted up, I would get error messages and I wouldn't be able to do the initial set up. At the time, this was nothing I couldn't fix, but I had to put it aside because I was busy.
Fast forward to present day, I completely forgot about it. I locked the device, flashed stock recovery and did another factory reset. Now whenever I try to turn it on I get stuck at a black screen with error messages (I can't do initial setup). I can't install a new rom because the device is locked and I can't unlock it because it's OEM locked and I can't get into the OS.
Am I screwed or can I still pull off a miracle?
Click to expand...
Click to collapse
Hi, Go_Radio...
Probably screwed ... sorry, I don't mean to be glib or flippant. I've experienced something similar myself, late last year, and I had to return my Nexus 9 for a replacement, so I know what a pain in the backside this problem is.
-----
But to be clear, if I read and understand your post correctly, you're looking to run fastboot flash commands (either directly yourself, or allow a toolkit to run them for you) in order to either...
----
a) Fastboot Flash back to Google Factory Stock.
~ or ~
b) Fastboot Flash TWRP, and via TWRP, flash some Custom ROM.
----
...but cannot do either...
...because the bootloader is locked, and attempts unlock it with fastboot oem unlock fail.
And it fails because the option in SETTINGS>>DEVELOPER OPTIONS>>OEM unlocking (allow the bootloader to be unlocked) has not be enabled, or has been disabled.
This damnable nuisance problem, at the moment, can only be resolved in one of two ways... Either by returning your device for repair or replacement...
Or by the method described here...
[INFO] Nexus 6 / Nexus 9 Enable OEM Unlock [GUIDE] Unlock via TWRP/CWM
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
...unfortunately for this to work, you do need TWRP installed, in order for the necessary files to be copied over to your Nexus 9, as the stock recovery doesn't allow for ADB connections (I know, I've tried )
And since Android won't boot, for whatever reason, you're locked out, and you can't enable the 'Allow OEM unlocking' setting in Developer Options in order to allow the bootloader to be unlocked, in order to fastboot flash TWRP. You're caught in a Catch 22 situation .
I wish I had some better options for you... .
Rgrds,
Ged.
I've tried the official unlock and it says can't verify. I tried every tutorial to get around that, activated SIM, going on i.mi.com, etc. I even contacted support US, Hong Kong support, and India support and they all gave me the same garbage auto replies.
I've tried unofficial unlock (2 different methods I believe) and none of them worked. I'm losing my mind.
Does anyone know if there's a different or updated method for Kate? Last time I tried to unlock was 2.5 weeks ago
Somewhere along the line of flashing fastboot roms my network started bugging out. It constantly connects and disconnects, and there's no LTE. I don't think I've ever loaded a bad rom so I don't know how this happened but I think I can troubleshoot that if I can at least get a custom recovery on this stupid thing.
Thanks in advance
I had problems at first too.i flashed global beta thru updater on phone.went to dev options then mi unlock status and linked phone to my account.unlocked first try after that.
marcukial said:
I had problems at first too.i flashed global beta thru updater on phone.went to dev options then mi unlock status and linked phone to my account.unlocked first try after that.
Click to expand...
Click to collapse
By Global beta do you mean global dev?
I'll give it another try
I just gave up and used this method: https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
You might need to flash an older version of MIUI. I think I used 6.11.3 - currently running Resurrection Remix 5.8.0 with Radon Kernel with locked Bootloader without a problem (well, other than the typical Nougat bugs)
Endzeitkind said:
I just gave up and used this method: https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
You might need to flash an older version of MIUI. I think I used 6.11.3 - currently running Resurrection Remix 5.8.0 with Radon Kernel with locked Bootloader without a problem (well, other than the typical Nougat bugs)
Click to expand...
Click to collapse
I found a 6.11.3 fastboot rom but when going to flash it says it cant find flash_all_except_storage.bat. And I looked that up and apparently it means it's not a fastboot rom, which is false because the other roms ive flashed didnt hvae storage.bat either.
Mi PCsuite also isnt pulling up the phone in recovery mode so that's useless.
Im about to throw this phone in the garbage honestly. Ive tried just about everything.
I tried the method you mentioned about replacing the recovery image but it didnt work at all
EDIT: Found another rom that works with the updater, but it gave me an error saying its an older version of MIUI. seriously this is pretty ridiculous
rasheemo said:
I've tried the official unlock and it says can't verify. I tried every tutorial to get around that, activated SIM, going on i.mi.com, etc. I even contacted support US, Hong Kong support, and India support and they all gave me the same garbage auto replies.
I've tried unofficial unlock (2 different methods I believe) and none of them worked. I'm losing my mind.
Does anyone know if there's a different or updated method for Kate? Last time I tried to unlock was 2.5 weeks ago
Somewhere along the line of flashing fastboot roms my network started bugging out. It constantly connects and disconnects, and there's no LTE. I don't think I've ever loaded a bad rom so I don't know how this happened but I think I can troubleshoot that if I can at least get a custom recovery on this stupid thing.
Thanks in advance
Click to expand...
Click to collapse
follow this thread.
http://xiaomitips.com/guide/unlock-redmi-note-3-bootloader-without-official-permission/
I have unlocked bootloaders of my 2 phones (1 kenzo, 1 kate), in process of unlocking I was getting error while flashing it was giving me the error of "no system storage" (Not remembered whole message).
when that error occurs to me I got stucked on bootloop then I get jumped directly to "step 18" in both device's unlocking.
in the end I was done an additional step which was about to flash recovery through fastboot.
To flash TWRP recovery through fastboot
just execute the below command if you get your unlocked you device bootloader.
"fastboot flash recovery filename.img"
then just get into recovery mode and flash your desired custom rom.
I have follwed same procedure twice and it worked for me, hope so that it'll help you.
Best Of Luck.
https://forum.xda-developers.com/redmi-note-3/how-to/bootloader-unlock-snapdragon-t3530395
follow this.
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Whoa! the unlock tool is out!
Is there any chance someone can make a root guide? I really want to buy Zenfone 3 Ultra but I wouldn't do it without root method out there. Any help is appreciated.
Were waiting on a dev to compile TWRP for us then we can get root
Trying to root ZU680KL
Hi!
I have unlocked my ZU680KL with the Asus unlock tool. Bootloader shows 'unlocked'.
Then I unpacked the stock boot.img (from WW_13.6.15.21_20161215, this what I have installed) and using Vim I set:*ro.secure=0, ro.adb.secure=0, and*ro.debuggable=1 in default.prop.
Repacked the new boot.img and flashed it with 'fastboot flash boot new-boot.img'.
'adb shell getprop' indicates that the new setting was applied.
Yet in the stock recovery mode I cannot install SuperSU-v2.79.zip and no adb devices are seen in recovery mode.
What else is needed? Do I have to edit something in the stock recovery or must wait for custom TWRP?
I was following the basic instructions found here:
https://machiry.wordpress.com/2012/10/26/getting-root-access-on-android-the-actual-way/
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
hillg001 said:
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
Click to expand...
Click to collapse
Any news?
https://forum.xda-developers.com/ze...t-zenfone-3-ultra-7-0-ww14-1010-1703-t3612108
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
when the ultra 3 first came out, many suggested waiting for a boot loader unlocker, & not updating any Android versions, because an unlock program might not work on subsequent Android versions. Is that the case? ... or does the unlocker work on the newest Android version too.
Thanks
.
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
I have just downloaded the zip, made the APK and installed it on my Zenfone 3 Ultra.
When I run the app, after clicking all the "are you sure..." acknowledgements, the app does not succeed in unlocking the bootloader. The error message indicates an unknown or perhaps network error, and suggests I "try again later..."
Running WW_14.1010.1804.75_20180612
Anybody else seeing this?
Ideas??
Reading on the ASUS blogs, they indicate it isn't supported anymore (no surprise), but shouldn't it still work??
heroxbd said:
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
Click to expand...
Click to collapse
Note the links above no longer work. Yes, you can get to the page, but the unlocker isn't there any more.
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
Does anybody know which version(s) of the stock ROM this works with? I've tried a couple, and all of them just yield the "unknown error" when running the unlocker.
If you know of a stock ROM version this works with, please post a URL for where I can find it (as it's proven really hard to find specific versions...)
Thanks in advance.
agree it no longer works. getting the unknown error...wait message that everyone else is getting. there are other XDA threads that indicate the same.
Keeping bootloader locked. Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even the SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
-
jrchester said:
Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even and SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
Click to expand...
Click to collapse
How did you do that? Can I get more details?
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hi Madlzz:
Checkout my XDA post here for more details on how I did this:
unlocking bootloader zenfone ultra
Hi all ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago, my friend wanted to see if my phone could be charged with a dash charger, where others wouldnt my battery was already low and overnight it ran out and when i...
forum.xda-developers.com
- John
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
lucy1983 said:
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
Click to expand...
Click to collapse
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
jrchester said:
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
Click to expand...
Click to collapse
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
lucy1983 said:
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
Click to expand...
Click to collapse
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
jrchester said:
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
Click to expand...
Click to collapse
You can install Magisk 24 without any problems. For me it doesn't break safetynet and play store says "certified". Even without enabling zigisk.
Hey guys:
I did unlock bootloader unload/root according to this guide.
First Wifi worked.
Then I did try to figure out OTA issues, could not uninstall Magisk, so temporary flashed stock image back.
From here on out - no matter, if stock, or Magisk_patched image: No chance to turn WiFi on.
In the WiFi-Menu, if I touch "turn on", it will show for one second: Turning Wi-Fi on", and then just return to the WiFi off-setting...
I did do factory reset from recovery - no success, flashed again (stock and patched) - no success.
I can't figure it out! Anybody an idea?
Are you sure that you are using correct boot.img version? It must be the same version as your system - build number and EU/GB variant must match.
Yes. I did, unless I had an older Version on a different slot and somehow did change slots and started messing around there. Could be an explanation.
Got tired of messing with it. Did download the whole stock rom, flashed it and will stay "unrooted" for now. Not worth the hassle to me.
BUT: What a mess that these manufacturers make it so hard to have working and rooted phone.
My guess would be that you flashed incorrect stock boot image.
Also how come that you couldn't uninstall Magisk?
Rooting is pretty straightforward, even if Mi A3 has a slight complication with missing "fastboot boot" command support, but otherwise it's nothing special. Take the correct boot.img, patch it, flash it and you're done.
First take your phone into fastboot mode. write fastboot set_active a .unzip stock rom and you will see flash_all.bat click it and you will succesfully have brand new rom with no issue. Note:If anything bad happens or goes wrong im not responsible. Its all your decision to do it
_mysiak_ said:
My guess would be that you flashed incorrect stock boot image.
Also how come that you couldn't uninstall Magisk?
Rooting is pretty straightforward, even if Mi A3 has a slight complication with missing "fastboot boot" command support, but otherwise it's nothing special. Take the correct boot.img, patch it, flash it and you're done.
Click to expand...
Click to collapse
Magisk said: no backup. tht's why I did install the original boot.img back, and this is where the WiFi-issue started.
I wanted to go this route, but did not manage it after several hours, so gave up and went stock:
https://forum.xda-developers.com/mi-a3/how-to/guide-create-manual-backup-stock-boot-t3988345
WorstCases said:
Magisk said: no backup. tht's why I did install the original boot.img back, and this is where the WiFi-issue started.
I wanted to go this route, but did not manage it after several hours, so gave up and went stock:
https://forum.xda-developers.com/mi-a3/how-to/guide-create-manual-backup-stock-boot-t3988345
Click to expand...
Click to collapse
Yeah, you need to create first backup manually. The guide works perfectly, I tested all methods (otherwise I wouldn't mention them ). What issues did you have?
The system is probably installed in b partition, you need to set partition a as active and reinstall rom via mi flashtool
Hello. guys! My smartphone: Samsung Galaxy J4(2018), j4lte. I trying to flash custom recovery TWRP. I have already unlocked the bootloader in settings, and have been waiting over two weeks for it to physically unlock. But the bootloader itself does not want to be unlocked physically. And more, I will add. I have this thing, I press a keyboard shortcut to go into download mode, my phone turns on and immediately turns off. To enter download mode, I need to go into the built-in recovery and select "reboot to download mode" there. But then, I don't have a warning that a custom system might put the phone at risk of breaking. And there are no lines that indicate the status of the bootloader, for example, is it unlocked or not.
My version Android: 10
Download Mode: U8
I use program for flashing: Odin, current version
Damn i have the same issue with the Note8, lez hope that soemone ansers that cuz reinstalling the Stock dosent help with this when try to install TWRP
NikitaSav said:
Hello. guys! My smartphone: Samsung Galaxy J4(2018), j4lte. I trying to flash custom recovery TWRP. I have already unlocked the bootloader in settings, and have been waiting over two weeks for it to physically unlock. But the bootloader itself does not want to be unlocked physically. And more, I will add. I have this thing, I press a keyboard shortcut to go into download mode, my phone turns on and immediately turns off. To enter download mode, I need to go into the built-in recovery and select "reboot to download mode" there. But then, I don't have a warning that a custom system might put the phone at risk of breaking. And there are no lines that indicate the status of the bootloader, for example, is it unlocked or not.
My version Android: 10
Download Mode: U8
I use program for flashing: Odin, current version
Click to expand...
Click to collapse
Did you install smasung multi disabler?
DavidxxxD said:
Did you install smasung multi disabler?
Click to expand...
Click to collapse
oh no **** guess im just dumby ^_°
DavidxxxD said:
Did you install smasung multi disabler?
Click to expand...
Click to collapse
tho crap how im supposed to install it? odin dosent want it and i cant use since ivent got TWRP on it wich i can not install because it says, as u guesst: Only official binaries can be installed no matter WHAT I DO -.- hate samsung by now
NikitaSav said:
Hello. guys! My smartphone: Samsung Galaxy J4(2018), j4lte. I trying to flash custom recovery TWRP. I have already unlocked the bootloader in settings, and have been waiting over two weeks for it to physically unlock. But the bootloader itself does not want to be unlocked physically. And more, I will add. I have this thing, I press a keyboard shortcut to go into download mode, my phone turns on and immediately turns off. To enter download mode, I need to go into the built-in recovery and select "reboot to download mode" there. But then, I don't have a warning that a custom system might put the phone at risk of breaking. And there are no lines that indicate the status of the bootloader, for example, is it unlocked or not.
My version Android: 10
Download Mode: U8
I use program for flashing: Odin, current version
Click to expand...
Click to collapse
And this version of Odin? https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
joke19 said:
А эта версия Одина? https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Click to expand...
Click to collapse
I have RMM Prenormal
C7TJFVB7-CAZ said:
hate samsung by now
Click to expand...
Click to collapse
Same here, reinstalling full stock should fix it. Also try combiation firmware if that doesn't work. Does your device have a vbmeta partition?
DavidxxxD said:
Same here, reinstalling full stock should fix it. Also try combiation firmware if that doesn't work. Does your device have a vbmeta partition?
Click to expand...
Click to collapse
combination file not working on Binary 8/9 on Samsung Galaxy J4
I've had the same issue on a J330F after Android 9 update - tried to modify, got stuck in the same red text. I don't remember any info from odin mode, but It booted fine again after flashing the same version over it. Though I had to wait 24 hours before trying to modify again. Not sure what's going on in your case, but Samsung security can be real pain, that's for sure.
I wouldn't get any of their newer models to mess around with, compatibility is good and there are reliable methods, but generally everything works better on more generic Qualcomm devices. Just take a look at most MSM845 devices from around 2019 - big diffrence in terms of compatibilty, many of them are supported by newer versions of Linux than what is included with Android, some can even boot Windows 11.
DavidxxxD said:
I've had the same issue on a J330F after Android 9 update - tried to modify, got stuck in the same red text. I don't remember any info from odin mode, but It booted fine again after flashing the same version over it. Though I had to wait 24 hours before trying to modify again. Not sure what's going on in your case, but Samsung security can be real pain, that's for sure.
I wouldn't get any of their newer models to mess around with, compatibility is good and there are reliable methods, but generally everything works better on more generic Qualcomm devices. Just take a look at most MSM845 devices from around 2019 - big diffrence in terms of compatibilty, many of them are supported by newer versions of Linux than what is included with Android, some can even boot Windows 11.
Click to expand...
Click to collapse
I have Android 10
I try all, that i can to try
Same problem
After unlocking your bootloader, you have to allow your device to boot again:
Helix-one said:
I AM NOT RESPONSIBLE FOR ANY DAMAGES DONE BY YOUR MISHAPS
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some cirumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Voila! Your bootloader now accepts unofficial images in download mode.
Click to expand...
Click to collapse
After flashing TWRP, you may need to wipe data and flash Multidisabler
V0latyle said:
After unlocking your bootloader, you have to allow your device to boot again:
After flashing TWRP, you may need to wipe data and flash Multidisabler
Click to expand...
Click to collapse
I cant even flash TWRP
Kgstate said:
I cant even flash TWRP
Click to expand...
Click to collapse
When you're in Download Mode, look for something that says "KG: Checking". If this says "Prenormal" you won't be able to flash custom binaries, and need to do as I described - boot the device, connect to the Internet, wait for the OEM unlocking toggle to become visible again.
V0latyle said:
When you're in Download Mode, look for something that says "KG: Checking". If this says "Prenormal" you won't be able to flash custom binaries, and need to do as I described - boot the device, connect to the Internet, wait for the OEM unlocking toggle to become visible again.
Click to expand...
Click to collapse
Editing date to make it 7 days later and Connecting the internet just worked, thank you for your help!