Hi,
has anybody tried to relock the bootloader?!
i was a little over hasty and unlocked a device. I thought (yeah, i didnt checked it ...) if asus is offering a unlocker, it should be no big deal to lock it again.
But everything i found is for the ZF8, and all i found does not work on the ZF9.
It starts that there is no adb/sideload option in recovery nor have i found a custom recovery.
And every relock command in fastboot is not known by the fastboot environement of the ZF9...
So has anybody found a way?
thx in advance.
Matt
Has anyone found a method to close the bootloader again? I'm thinking of opening it but I'm worried that I won't find a method to close it if necessary.
zero5liters said:
Hi,
has anybody tried to relock the bootloader?!
i was a little over hasty and unlocked a device. I thought (yeah, i didnt checked it ...) if asus is offering a unlocker, it should be no big deal to lock it again.
But everything i found is for the ZF8, and all i found does not work on the ZF9.
It starts that there is no adb/sideload option in recovery nor have i found a custom recovery.
And every relock command in fastboot is not known by the fastboot environement of the ZF9...
So has anybody found a way?
thx in advance.
Matt
Click to expand...
Click to collapse
try "fastboot oem asus-csc_lk". After wipe data.
sakun-ice said:
try "fastboot oem asus-csc_lk". After wipe data.
Click to expand...
Click to collapse
i tried it but without wipe before. And that did not work.
I try it later with wipe. But i do not have hope. because most of the fastboot commands do not work on the ZF9.
I tried to read the commands out of the bootloader but with no luck ...
zero5liters said:
i tried it but without wipe before. And that did not work.
I try it later with wipe. But i do not have hope. because most of the fastboot commands do not work on the ZF9.
I tried to read the commands out of the bootloader but with no luck ...
Click to expand...
Click to collapse
If you haven't tried it, you can try it with:
-fastboot oem asus-back
-fastboot oem asus-csc_lk
-fastboot flashing lock
-fastboot flashing lock_critical
-fastboot oem lock
-fastboot oem lock_critical
-fastboot flash !frp-partition! default_key.bin
-fastboot oem asus-lock
No. Didnt work. 'Command not supported in default implemantation' All of these commands.
I did not try the *critical commands and the "frp partition". I had not time to read me in on that. And i dont want to brick the phone complete.
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
schizophaser said:
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
Click to expand...
Click to collapse
No,
i tried it but fastboot doesnt recognize the command.
But thanks. I now startet the "Repair" @ asus.
schizophaser said:
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
Click to expand...
Click to collapse
Yeah ! works for me too
OTA update working ?
rafik25 said:
OTA update working ?
Click to expand...
Click to collapse
Doesn't seem so. 2050 was released two weeks ago and didn't show up in the updater, so I had to install it manually today.
schizophaser said:
Doesn't seem so. 2050 was released two weeks ago and didn't show up in the updater, so I had to install it manually today.
Click to expand...
Click to collapse
Same, though I expected that since I rooted.
For any one wondering how to update, just take the firmware file from ASUS's site, place it in your phone's internal storage, then either wait a few seconds for the update notification to pop up or restart your phone (you should see it then). Follow the prompts from there.
schizophaser said:
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
Click to expand...
Click to collapse
This command works? Can someone give me a quick guide to close the bootloader? Right now I have twrp and magisk.
sakun-ice said:
This command works? Can someone give me a quick guide to close the bootloader? Right now I have twrp and magisk.
Click to expand...
Click to collapse
1. You can only re-lock the bootloader by going back to the stock firmware/recovery, losing twrp and magisk.
2. Re-locking the bootloader does not re-enable the OTA updates, but might help with Google Pay/SafetyNet attestation if that's broken for some reason.
3. This command works. Just flash the stock firmware and recovery, then do adb reboot bootloader and fastboot oem asus-csc_lk.
schizophaser said:
1. You can only re-lock the bootloader by going back to the stock firmware/recovery, losing twrp and magisk.
2. Re-locking the bootloader does not re-enable the OTA updates, but might help with Google Pay/SafetyNet attestation if that's broken for some reason.
3. This command works. Just flash the stock firmware and recovery, then do adb reboot bootloader and fastboot oem asus-csc_lk.
Click to expand...
Click to collapse
To flash the stock recovery is it enough to install the full zip of the stock ROM from twrp and reboot?
sakun-ice said:
To flash the stock recovery is it enough to install the full zip of the stock ROM from twrp and reboot?
Click to expand...
Click to collapse
Yes, that should be enough.
schizophaser said:
Yes, that should be enough.
Click to expand...
Click to collapse
ok, just one last question. If I have the latest version (2060.113) with TWRP, to leave everything stock what I have to flash is the zip downloaded from ASUS (also 2060.113: https://dlcdnets.asus.com/pub/ASUS/ZenFone/AI2202/ASUS_AI2202-33.0804.2060.113-kernel-src.tar.gz?model=Zenfone%209 ). I have seen that there are other ROMs called RAW, but I don't know exactly which one to install. I'm afraid that when installing the zip from that link something "non-stock" will remain installed and when closing the bootloader the smartphone won't boot.
sakun-ice said:
ok, just one last question. If I have the latest version (2060.113) with TWRP, to leave everything stock what I have to flash is the zip downloaded from ASUS (also 2060.113: https://dlcdnets.asus.com/pub/ASUS/ZenFone/AI2202/ASUS_AI2202-33.0804.2060.113-kernel-src.tar.gz?model=Zenfone%209 ). I have seen that there are other ROMs called RAW, but I don't know exactly which one to install. I'm afraid that when installing the zip from that link something "non-stock" will remain installed and when closing the bootloader the smartphone won't boot.
Click to expand...
Click to collapse
I can't say much about this. I don't think it's going to be a problem, but of course you're doing it at your own risk.
Related
I downloaded some twrp backups and I tried to flash twrp using flashify but I keep getting bootlooped. Idk why it's doing this but in order to get S-OFF I need to get back to stock and the back up is my only chance. My phone bootloops when I've flashed twrp using flashify and I reboot into recovery. Any thoughts on maybe why twrp is making my phone bootloop? Is anyone else having these problems?
That's happened to me a few times as well. What worked for me was to flash twrp through adb or fastboot. You may have to try some older versions of twrp if the current release doesn't work. If I'm remembering correctly I think 2.7.0.1 and 2.8.3.0 worked for me. I believe it depends on what version of android you're currently running. Look here http://teamw.in/project/twrp2/225
To add a bit to what was mentioned above, do fastboot erase cache, and flash TWRP using fastboot.
This solves most issues with TWRP not flashing or booting properly.
Also, make sure you bootloader is UNLOCKED.
iTzz_KAMIKAZE said:
Idk why it's doing this but in order to get S-OFF I need to get back to stock and the back up is my only chance.
Click to expand...
Click to collapse
No, it isn't. You can also relock the bootloader and RUU back to stock.
redpoint73 said:
To add a bit to what was mentioned above, do fastboot erase cache, and flash TWRP using fastboot.
This solves most issues with TWRP not flashing or booting properly.
Also, make sure you bootloader is UNLOCKED.
No, it isn't. You can also relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
So I just tried to flash the recovery using fastboot with no luck. I followed the directions off of TWRP's thread and even tried it a second time running the "fastboot erase cache" first, still with no luck. Now you mentioned me relocking my bootloader and then RUU back to stock, is there a thread I can go to to try that?
iTzz_KAMIKAZE said:
So I just tried to flash the recovery using fastboot with no luck. I followed the directions off of TWRP's thread and even tried it a second time running the "fastboot erase cache" first, still with no luck. Now you mentioned me relocking my bootloader and then RUU back to stock, is there a thread I can go to to try that?
Click to expand...
Click to collapse
Try a couple older TWRP builds, to see if that helps (as recommended in previous post by johnnyutah22).
You can try RUU, you don't need a thread for that. Relocking the bootloader is a single command:
fastboot oem lock
After that, just run the RUU, its a Windows executable, and very self explanatory. You can find the RUUs linked in my Index thread:
http://forum.xda-developers.com/showthread.php?t=2751432
Dear all,
Merry Xmas and Happy New Year
I am new to oneplus x.
I rooted using this method i. e. Without PC.
http://forum.xda-developers.com/oneplus-x/general/guide-root-oneplus-x-twrp-pc-t3251027
Then I use flashify (app from appstore) to flash TWRP.
https://play.google.com/store/apps/...ify&pcampaignid=APPU_1_7mN_VrODMMivmAXCwJnoDg
http://forum.xda-developers.com/one...recovery-twrp-2-8-7-0-touch-recovery-t3252840
Then i flash blu_a Kernel.
http://forum.xda-developers.com/oneplus-x/orig-development/kernel-t3250995
How can i check if my bootloader is unlocked? For other phones, my understanding is that as long as u can flash twrp, bootloader is unlocked.
I think you can only check that with the adb tools on your computer.
Command to check bootloader status: fastboot oem device-info
Click to expand...
Click to collapse
source: https://forums.oneplus.net/threads/bootloader-status-check.52167/#post-2382799
I thought the bootloader needed to be unlocked first before flashing a custom recovery??
At OP, when you flash TWRP via flasify, did you run into any problems??
Just curious really.
Mojar7070 said:
I thought the bootloader needed to be unlocked first before flashing a custom recovery??
At OP, when you flash TWRP via flasify, did you run into any problems??
Just curious really.
Click to expand...
Click to collapse
Maybe i am daring
No issues. Used for few days
My Kernel is flashed via TWRP. I did backup too. No issues
knauji said:
I think you can only check that with the adb tools on your computer.
source: https://forums.oneplus.net/threads/bootloader-status-check.52167/#post-2382799
Click to expand...
Click to collapse
I have issues with drivers for my windows. Have Samsung s2, Asus Zenfone 2 all installed so i use the root without pc method. I suspect my bootloader is unlocked as i can flash twrp.
Any master has any idea?
Gosh... Seems like no one has the answer. Need to check via PC.
You have to go to setting / about phone / 7 times on build number to unlock dev options/
Then settings / dev options
5th line is OEM unlock.
How is yours?
Kéno40 said:
You have to go to setting / about phone / 7 times on build number to unlock dev options/
Then settings / dev options
5th line is OEM unlock.
How is yours?
Click to expand...
Click to collapse
I manually did that before all the process in my 1st post.
I think this is to allow u to unlock, not unlocking the bootloader per se.
with adb/PC ? isn't it ?
check status of bootloader
first go to fastboot mode
first power off the device than Hold Volume Up while Power on the phone
than in adb type: fastboot oem device-info
there it should be flagged as true
My opx was unlocked, installed twrp, now.... Back to stock ROM and bootloader now is locked and i cannot unlocked,
What can i do?
Thx
bébé53 said:
with adb/PC ? isn't it ?
Click to expand...
Click to collapse
I know but my laptop fails to install adb driver for oneplus x because i have too many phones installed. I uninstalled all drivers and tried installing oneplus x one but it fails.
simarjits said:
first go to fastboot mode
first power off the device than Hold Volume Up while Power on the phone
than in adb type: fastboot oem device-info
there it should be flagged as true
Click to expand...
Click to collapse
As per above. I have driver issues on my laptop.
overon37 said:
My opx was unlocked, installed twrp, now.... Back to stock ROM and bootloader now is locked and i cannot unlocked,
What can i do?
Thx
Click to expand...
Click to collapse
Based on my understanding, once unlocked, its difficult to lock back. If its lock now, i doubt you are unlocked at 1st place. Pleaae correct me if i am wrong.
Yes. You are wrong.
I have twrp, so i unlocked, but now, i do not know how is locked, because i didnt, and when i try fastboot oem unlock.... No errors but nothing happend.
When i flashed twrp and try cm 13 i flashed, from twrp, the stock zip, 2.1.3.x
And now say that is locked, and.... Never unlocked
PD. never rooted, but when i flashed yesterday CM 12.1, when i restarted my opx to system from recovery do not ask for root from twrp ¿?, when i flashed stock zip, asked me to root from twrp when i restart to system ¿?
Tiongkia said:
As per above. I have driver issues on my laptop.
Click to expand...
Click to collapse
You have to install adb and fastboot drivers before executing the commands . you can download from here http://forum.xda-developers.com/showthread.php?t=2317790
Cheers :good:
simarjits said:
You have to install adb and fastboot drivers before executing the commands . you can download from here http://forum.xda-developers.com/showthread.php?t=2317790
Cheers :good:
Click to expand...
Click to collapse
As mentioned, i cannot. I tried all methods. I installed too my adb driver on my laptop
Tiongkia said:
As mentioned, i cannot. I tried all methods. I installed too my adb driver on my laptop
Click to expand...
Click to collapse
did you try the Windroid Tool that is here on xda?
Hi, I used fastboot to boot TWRP without flashing it (using fastboot boot twrp.img). Foolishly of me when exit TWRP I was asked to disabled Stock Recovery wich I swiped yes. Now my stock recovery is gone. How do I enable it via TWRP again without having to flash it? or what are my options? phone functionlity was not afected, just the stock recovery.
thanks.
imho you either use twrp OR stock recovery. so in my opinion youve done all right.
Download fastboot image.. extract boot.img from it. Boot in TWRP using fastboot .. then install->install image->boot.img(file you extracted)->flash->choose recovery, not boot when where to flash->done.
If it doesn't work then flash the whole fastboot image with mitool.
h0LLe said:
imho you either use twrp OR stock recovery. so in my opinion youve done all right.
Click to expand...
Click to collapse
dragneelfps said:
Download fastboot image.. extract boot.img from it. Boot in TWRP using fastboot .. then install->install image->boot.img(file you extracted)->flash->choose recovery, not boot when where to flash->done.
If it doesn't work then flash the whole fastboot image with mitool.
Click to expand...
Click to collapse
I ended up flashing the whole image beacuse it bricked when using the command "fastboot oem lock".
any idea why it bricked? i did flash a stock recovery before in order to lock it again.
After rooting it im interested in locking the bootloader again. Maybe I skipped a procedure in order to lock the bootloader again??
Right now im rooted, phone working, stock recovery (since I flashed a fastboot image with SP tools) and unlocked bootloader but I want to lock it without bricking it again.
thanks.
pach33 said:
I ended up flashing the whole image beacuse it bricked when using the command "fastboot oem lock".
any idea why it bricked? i did flash a stock recovery before in order to lock it again.
After rooting it im interested in locking the bootloader again. Maybe I skipped a procedure in order to lock the bootloader again??
Right now im rooted, phone working, stock recovery (since I flashed a fastboot image with SP tools) and unlocked bootloader but I want to lock it without bricking it again. (i lock bootloader for my friend which has redmi 3s)
thanks.
Click to expand...
Click to collapse
To lock bootloader again you must flash stock image via fastboot with "lock bootloader" bat file (it is in stock image flashtool zip). But why U need to lock bootloader? i dont see sense to do it.
dromaczek said:
To lock bootloader again you must flash stock image via fastboot with "lock bootloader" bat file (it is in stock image flashtool zip). But why U need to lock bootloader? i dont see sense to do it.
Click to expand...
Click to collapse
Hi, thanks for the answer, I want to lock it because some features got disabled when unlocking the bootloader, like xiaomis "Find mi Device". I also read that having the bootloader unlocked may compromise your data security.
pach33 said:
Hi, thanks for the answer, I want to lock it because some features got disabled when unlocking the bootloader, like xiaomis "Find mi Device". I also read that having the bootloader unlocked may compromise your data security.
Click to expand...
Click to collapse
:laugh::laugh::laugh::laugh: funniest thing i read on the internet today
chandradeepdey01 said:
:laugh::laugh::laugh::laugh: funniest thing i read on the internet today
Click to expand...
Click to collapse
He write only true! He could "read that having the bootloader unlocked may compromise your data security" :laugh::laugh::laugh::laugh::laugh:
chandradeepdey01 said:
:laugh::laugh::laugh::laugh: funniest thing i read on the internet today
Click to expand...
Click to collapse
dromaczek said:
He write only true! He could "read that having the bootloader unlocked may compromise your data security" :laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
Glad I made you guys laugh. :good: Next time I will better use the noob friendly Q&A.
pach33 said:
Glad I made you guys laugh. :good: Next time I will better use the noob friendly Q&A.
Click to expand...
Click to collapse
Woah, didn't mean to offend you bro. It was sarcasm.
It is replaced not disabled...
I unlocked my mate20 pro, but problem is now i can't relock it , even I use "fastboot oem relock +unlock code"
anybody can help ?
have you tried fastboot oem lock?
you don't have to specify the code
i just tried also and cannot lock
Daniehabazin said:
have you tried fastboot oem lock?
you don't have to specify the code
Click to expand...
Click to collapse
still can't relock..................wait for solution
richard_li said:
still can't relock..................wait for solution
Click to expand...
Click to collapse
Refer to my post here ?
https://forum.xda-developers.com/ma...ocking-bootloader-magisk-root-t3885422/page22
I accidentally relocked the phone by using the hstool method of flashing a full firmware.
it does relock the phone and required me to unlock it again using the fastboot oem unlock code
xeroxide said:
I accidentally relocked the phone by using the hstool method of flashing a full firmware.
it does relock the phone and required me to unlock it again using the fastboot oem unlock code
Click to expand...
Click to collapse
That's interesting. So all your data was wiped when you used the hstool?
Someone else said flashing firmware via dload method also relocks the bootloader.
hmm i'm not sure.
I'll explain the whole situation.
I had just unlocked the bootloader and installed magisk.
after installing magisk, I installed a few modules, one of which made my phone bootloop.
I managed to get back into fastboot mode, use hstool to select my firmware (224) along with the patched hisuite from funkyhuawei.
after my phone recovered, it seems to have been completely reset and locked.
*edit*
I guess I should also add, I've never installed TWRP on this phone, only patched the recovery_ramdis.img for Magisk
xeroxide said:
hmm i'm not sure.
I'll explain the whole situation.
I had just unlocked the bootloader and installed magisk.
after installing magisk, I installed a few modules, one of which made my phone bootloop.
I managed to get back into fastboot mode, use hstool to select my firmware (224) along with the patched hisuite from funkyhuawei.
after my phone recovered, it seems to have been completely reset and locked.
*edit*
I guess I should also add, I've never installed TWRP on this phone, only patched the recovery_ramdis.img for Magisk
Click to expand...
Click to collapse
After locking, can you use the same code to unlock it again ?
EagleEye92 said:
After locking, can you use the same code to unlock it again ?
Click to expand...
Click to collapse
Yes sure
EagleEye92 said:
After locking, can you use the same code to unlock it again ?
Click to expand...
Click to collapse
Yes
ok just an update, while mucking around I accidentally softbricked my phone.
I used the external usb method (where you update using the code *#*#2846579#*#*) and it 100% relock the phone.
*edit*
and yes, the same code works to unlock it again. KEEP THE CODE SAFE!
xeroxide said:
ok just an update, while mucking around I accidentally softbricked my phone.
I used the external usb method (where you update using the code *#*#2846579#*#*) and it 100% relock the phone.
*edit*
and yes, the same code works to unlock it again. KEEP THE CODE SAFE!
Click to expand...
Click to collapse
Can you say me something about the usb method? dont know, what this is. :silly:
ClintP said:
Can you say me something about the usb method? dont know, what this is. :silly:
Click to expand...
Click to collapse
You need an external usb-c drive with some firmware on it.
I initially used v187 from this thread
https://forum.xda-developers.com/mate-20-pro/how-to/firmware-update-187-brings-oem-unlock-t3897301
Since then I downloaded a v206 which works over USB but I cannot recall where I got it from.
Note that you will loose all user data since the phone will be fully wiped.
Also this method requires a phone that is working, as in able to boot and access the dialer and menus.
If I find out where I got the v206 I will post it here as well.
I should also add, maybe it might work with a memory card as well... But this method requires an external source for the firmware since it formats the entire phone
@ xeroxide Thx for your help.
I Try this at the weekend.
If you need to relock your bootloader, this is the process:
Using eRecovery, restore your phone to stock
Once done, boot into recovery and RESET your phone (if you dont, it will not allow you to lock the bootloader)
Boot into fastboot mode (Holding Vol-DOWN, plug in usb cable) , and run the command
fastboot oem relock < bootloader unlock code>
the phone should now ask you that it will wipe your device, confirm,
Enjoy locked phone!
deepsrd said:
If you need to relock your bootloader, this is the process:
Using eRecovery, restore your phone to stock
Once done, boot into recovery and RESET your phone (if you dont, it will not allow you to lock the bootloader)
Boot into fastboot mode (Holding Vol-DOWN, plug in usb cable) , and run the command
fastboot oem relock < bootloader unlock code>
the phone should now ask you that it will wipe your device, confirm,
Enjoy locked phone!
Click to expand...
Click to collapse
Now it works well... i relocked my phone..........but i don't know why i failed last time because i followed exactly the steps...
deepsrd said:
If you need to relock your bootloader, this is the process:
Using eRecovery, restore your phone to stock
Once done, boot into recovery and RESET your phone (if you dont, it will not allow you to lock the bootloader)
Boot into fastboot mode (Holding Vol-DOWN, plug in usb cable) , and run the command
fastboot oem relock < bootloader unlock code>
the phone should now ask you that it will wipe your device, confirm,
Enjoy locked phone!
Click to expand...
Click to collapse
richard_li said:
Now it works well... i relocked my phone..........but i don't know why i failed last time because i followed exactly the steps...
Click to expand...
Click to collapse
it means now relocked and problem solved.........
deepsrd said:
If you need to relock your bootloader, this is the process:
Using eRecovery, restore your phone to stock
Once done, boot into recovery and RESET your phone (if you dont, it will not allow you to lock the bootloader)
Boot into fastboot mode (Holding Vol-DOWN, plug in usb cable) , and run the command
fastboot oem relock < bootloader unlock code>
the phone should now ask you that it will wipe your device, confirm,
Enjoy locked phone!
Click to expand...
Click to collapse
this worked for me thanks loads!
So the story begins when I tried to relock my phone after having issues with my bank app so I tried to lock my rog phone, after trying multiple commands such as fastboot oem lock and others only one worked which was "fastboot oem asus-csc_lk". The command succeeded but it then shows boot_b unbootable and boot_a unbootable. I could no longer run any of the flash commands and can't get back into android. I am still able to run the boot command like "fastboot boot something.img". The flash commands gets phone locked error.
kevinone27 said:
So the story begins when I tried to relock my phone after having issues with my bank app so I tried to lock my rog phone, after trying multiple commands such as fastboot oem lock and others only one worked which was "fastboot oem asus-csc_lk". The command succeeded but it then shows boot_b unbootable and boot_a unbootable. I could no longer run any of the flash commands and can't get back into android. I am still able to run the boot command like "fastboot boot something.img". The flash commands gets phone locked error.
Click to expand...
Click to collapse
Maybe boot to recovery and do a clean flash?
I am unable to boot to recovery or flash
kevinone27 said:
I am unable to boot to recovery or flash
Click to expand...
Click to collapse
Didn't you say you can boot to an image target?
I can run a command that is "fastboot boot recovery.img" but it won't actually boot into said image or just stuck there for days.
kevinone27 said:
I can run a command that is "fastboot boot recovery.img" but it won't actually boot into said image or just stuck there for days.
Click to expand...
Click to collapse
We’re you full stock when you locked?
PM me if you really can't figure it out. I'll try to help you when I'm free (probably tomorrow).
Arealhooman said:
We’re you full stock when you locked?
Click to expand...
Click to collapse
I'm not sure if it's running full stock, but after my attempt at running a custom OS I went and reflashed the stock OS from the official asus support website.
kevinone27 said:
I'm not sure if it's running full stock, but after my attempt at running a custom OS I went and reflashed the stock OS from the official asus support website.
Click to expand...
Click to collapse
It should be 100 percent stock before locking. Can you unlock your BL again?
Unfortunately no, none of my fastboot commands worked (even the oem ones) and I am unable to unlock via apk due to being unable to access my android os.
I saw someone have a similar problem and they said using this tool (free version) and using it to boot into Fastboot help. I doubt it can hurt.
I can not vouch for the software though.
Arealhooman said:
I saw someone have a similar problem and they said using this tool (free version) and using it to boot into Fastboot help. I doubt it can hurt.
Click to expand...
Click to collapse
Thanks, I will give it a try tomorrow.
Arealhooman said:
I saw someone have a similar problem and they said using this tool (free version) and using it to boot into Fastboot help. I doubt it can hurt.
Click to expand...
Click to collapse
I gave the free version a try unfortunately it won't detect the device unless I go to fastboot mode. The free version seems to only have Samsung and requires it to be unlocked.
I also managed to run twrp temporarily on slot_A which probably means that it wasn't fully stock. TWRP isn't able to do much though with the lock state it's currently in.
Is there any other way to bypass the lock state?
My problem is solved, I don't know exactly what happened, but I left my phone in it's endless reboot between slot_a and slot_b until it ran out of battery. After I charged it back from 0% the problem seems to have been fixed, it started the encrypting process and new phone setup.