DISCLAIMER: Any guides/suggestions/workarounds posted here are to be taken at your own risk. Any bricks/lockouts/otherwise unusable devices are your own responsibility. No support will be provided, unless someone takes it upon themselves to help you out.
Situation:
Updates to Google's SafetyNet is checking for unlocked bootloader, if your bootloader is unlocked, SafetyNet will error, preventing you from being able to use Android Pay, even if you're on a stock, unrooted, but otherwise unlocked bootloader.
Problem:
Many of you might feel that you won't ever give up your custom ROMs, Mods, Xposed, etc., that you've grown to love and accept as the norm in the community (heck, that's why I've been using Nexus forever!), and some of you might even feel that you won't let Google dictate whats allowed/disallow on your device, and might try combination of solutions to try and get one up on Google, by locking your bootloader, and experiment trying to get Android Pay to work on a Custom ROM/etc.
Danger:
There is a very real risk that you might brick your device if you lock your bootloader while not using stock firmware.
Discussion:
I've been a member of this community for a while now, and while not a programmer, developer myself, I am more tech savvy then most of the people I surround myself with. Given this, I wanted to try and give back by proposing this thread, a place where many of you, more experienced, and less experienced, than myself can share their concerns, thoughts, solutions, theories, as how to safely get Android Pay working with our beloved custom ROMs/Mods with the new Google updates.
So please, feel free to brainstorm/propose/ponder below your thoughts/suggestions/theories/solutions to the above state issue. I will try and update this first post with anything that we determine below as safe course of this adventure(misadventure?).
I'll first link to some light reading by @Chainfire - http://forum.xda-developers.com/showpost.php?p=68424605&postcount=2 to give you an idea why all of this is happening.
Solutions/Theories/Tests:
Hoping I didn't just make a useless thread, on Chainfire's suhide thread, http://forum.xda-developers.com/apps/supersu/suhide-t3450396
did release (2016.10.07 - v0.54 - RELEASE NOTES- Fix for latest SafetyNet update) bypass unlocked bootloader check?
Ok, forward and onward.
Some of my concerns with locked bootloader:
1. - With a locked bootloader, a custom recovery (TWRP), and a custom ROM, a few things can go wrong, like ROM not booting, with OEM unlocking disallowed in developer options. Provided that you didn't set a pattern/work to boot device, (PIN is what I believe TWRP will only allow to unlock your partitions), or didn't set a lock at all, you should be able to boot into TWRP and format userdata/all partitions, flash another ROM, boot, check "OEM Unlocking" and be able to perform bootloader unlock command, correct?
2. What would happen in the same scenario as above, but if you had a stock bootloader, would it be more difficult to flash a ROM? would you be able to flash anything at all? Or even boot TWRP with a locked bootloader?
3. In my conversation with @Lawlrus in another thread, he mentioned that as long as you have debugging enabled on your ROM, you should be ok, I fail to see the point of this, because if you can boot into your ROM, can't you just toggle OEM unlocking in the first place?
A. A solution to keeping bootloader locked + having and updating a custom ROM?
1. Flash favorite ROM, set it up as you wish, install whatever you want, configure it as you want.
2. Enjoy ROM
3. Time to update ROM - Backup app data/messages using Titanium, or even Google's backup, whatever floats your boat.
4. Reboot into custom recovery, make a backup (without password/pin lock preferably).
5. Reboot into bootloader, unlock bootloader (this will wipe your data).
6. Restore nandroid backup (recovery backup you just made)
7. Flash updated ROM/Root/Mods/GApps/Whatever..
8. Relock bootloader.
9. Use Android Pay.
10. Profit.
What am I not seeing with this approach?
@Shemploo
You're correct you can just flip the switch. The point of it was being if you can't boot the ROM up due to it bootlooping for some reason
Lawlrus said:
@Shemploo
You're correct you can just flip the switch. The point of it was being if you can't boot the ROM up due to it bootlooping for some reason
Click to expand...
Click to collapse
If you're not able to boot into ROM, having debugging enabled before it fails to boot has no bearing on ADB if you can access the custom recovery, IIRC.
In other words, being able to boot into a custom recovery like TWRP even with locked bootloader will give you ADB access to your partitions, provided that you didn't encrypt/lock your Android, and forgot the password.
Also, I think ADB would be very useful to have your PC communicate with TWRP for pulling/pushing files, which is important if you need to load a ROM in via TWRP so you can get back into your ROM, and check "OEM unlocking" allowing you to reboot into bootloader and use the bootloader unlock command.
I believe that TWRP ADB works irregardless of whether you have enabled debugging in OS, or not. The debugging in OS is only there for the OS's benefit.
Related
Hi all,
The original credits for the root go to SuperPichu for the following post: http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
I simply "modified" his process, to make it even more "hassle free"
The process will wipe your data, so remember to backup it.
Besides, I'm not responsible if warranty voids or whatever. Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it. The fastboot unlock procedure has been taken directly by the NVidia Developer's site, so they actually expect the users to do that - but what you will do next, it's all your responsability
So, the overall procedure looks like:
Download&Install the "Mini" ADB/Fastboot from here: http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 (remember to say yes to create the link on the desktop - it will be useful later)
Download&Install NVIDIA ADB Drivers from the official Nvidia site: http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip
Enable "Developer Mode" on the Nvidia Tablet (Settings -> About tablet -> Tap many times (5+) the "Build number" until the Developer Mode is activated
Developer Mode -> Enable USB Debugging
Copy the CWM image and SuperSU (rename it to supersu.zip) where you installed the Mini ADB/Fastboot (default: C:\Program Files\Minimal ADB and Fastboot)
Click the link created by the Mini ADB/Fastboot installation. It should open a DOS console already at the install folder.
(In the Windows console) Type "adb reboot bootloader"
From the rebooted tab, select "Load fastboot protocol" with Volume Keys and push the power switch to confirm
(In the Windows console) Type "fastboot oem unlock"
[ATTENTION: This step will wipe your device] Press the "Volume Down" button to select, with the "Power" button, the "Unlock bootloader" option on device
(In the Windows console) Type "fastboot flash recovery recovery.img"
On the tablet, select "recovery reboot"
You should be now on CWM. Simply select "install zip from file" -> install from sideload
In the console, type "adb sideload supersu.zip"
On CWM select "reboot system", CWM will ask to keep root => say yes
Enjoy your rooted tablet
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
Well first off I havent had any issues with ota updates on CWM (took kitkat otas). Second, if you really don't want a custom recovery why not just obtain root then flash back the stock recovery??
wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
To be honest with you, I haven't updated yet - but the OTA seems to work (i.e. it's currently saying that my Firmware is up-to-date, no errors). Just wait a couple of weeks (NVIDIA released a firmware update every month until now :good: ) and I'll let you know if it works
Btw, even if I loose the the root/CWM, it's not a great deal to install it again
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Good to know. ?But we should be able to flash the ota zips via recovery and flash super su and possibly recovery (locked bootloaders, ota can overwrite recovery) just like we did to update to lolli. I usually see zips before I see the ota anyways.
sandrodjay said:
Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it.
Click to expand...
Click to collapse
I have contacted NVIDIA today, asking steps to move back to Kitkat. I was given instructions to unlock the bootloader, and was assured it will not void the warranty. The assistant was being meticulous regarding this, since she asked around for her colleagues' advice before giving me the information.
So if I ever need to send in for warranty, all I have to do is reflash the factory image to get rid of the root and I'll be all set. If they make a fuss about me having an unlocked bootloader, I'll have a chat transcript to back me up. You guys may want to do the same too.
Thank you worked great!
An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Just took 5.0.1 (wasn't rooted or anything). So I was thinking if I flash the CWM, then do a stock backup, then proceeed to root I should be able to restore the backup when a new OTA comes out since it will be unrooted and stock. Then I can update, install recovery if needed, make another unrooted stock backup, for the next time then reroot, right?
Should work, but after restoring your stock backup you will need the stock Recovery too to update ota.
Hi
There is no need to flash the custom recovery if you don't want to. Just do a fastboot boot recovery <recovery.img>. I did that because i didn't want to change to another recovery.
After the reboot you will revert to stock recovery.
\Sorenjul
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)
Help
Anyone else not able to download supersu.zip the page wont load
Granger77 said:
Anyone else not able to download supersu.zip the page wont load
Click to expand...
Click to collapse
NM sorry just went it opened instantly, maybe to much traffic
eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!
root method LTE compatible
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.
Driver issues
I cant for the life of me get my win 7 64bit pc to install the drivers I've tried uninstall and going through manually with the naked driver method and it still says the device doesnt need it his tutorial is for win 8 am I missing something, I'm losing my mind over here I want this thing rooted so bad I'm losing sleep, and google has been useless
cyraxx84 said:
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!
Click to expand...
Click to collapse
Ty for info and reply.
Bogdacutu said:
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)
Click to expand...
Click to collapse
Got it. Thanks!
oleg77 said:
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.
Click to expand...
Click to collapse
Same here. I got mine on sale with the controlller. I suspect its the same on both wifi only and LTE version.
Can i follow this guide to unlock and root 5.0.1?
My device is European L04, currently running North Africa release (the earliest Marshmallow build uploaded) - L04_2016_0316_0900 (B820)
I'd like to unlock the bootloader and root my Honor 6. I've never done it (on this particular device), because I've read enough here to know it's slightly more risky than on other devices, especially when you plan to update the stock rom soon, so I preferred to wait until I have the last important update the device is likely to receive - Android 6.0.
What I want to know (some of the answers are in the topics which I listed below):
MultiTool - I've seen reports of bricks when using MultiTool with EMUI4/Marshmallow - why does it happen? My understanding is that MultiTool is a bundle of adb/fastboot and some recovery images for older Android versions, so my theory is that instead of using MultiTool, I should simply get the proper recovery for Marshmallow and flash it manually with fastboot, right?
unlocking bootloader, rooting, flashing recovery - I think I understand the process; in a nutshell: 'fastboot oem unlock X', 'fastboot flash recovery imagename.img', then flash the proper SU.zip in recovery. Where do I find the code, the Marshmallow recovery image, the SU.zip file?
will recovery backup in TWRP work without any problems?
what is the procedure to go back to stock completely after rooting? Unroot, (then wipe if it's needed?) so I am able to safely flash stock firmware again (since, from what I know, flashing stock on a rooted phone makes itself brick permanently, right? or is it just a soft-brick and it can be fixed?)
is there anything else I should know before proceeding?
What I found so far:
http://forum.xda-developers.com/showpost.php?p=66615082&postcount=502 - two recovery images, TWRP and another one (stock?) for the Marshmallow release
http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060/page50 some rooting instructions for the L02 beta, see posts 494 and 498; no idea whether this is applicable to final Marshmallow or L04 at all
http://forum.xda-developers.com/honor-6/general/huawei-honor-6-plus-unlock-bootloader-id-t3357259 an app to get the unlock code, seems a bit shady to me though on the first glance
http://forum.xda-developers.com/honor-6/development/honor-6-rooting-method-t2962795 alternate methods for bootloader (through a website or by email), in case the app won't work; also, detailed instructions on unlocking and rooting
Basically, I need to know whether my procedure is more or less right before I proceed. I think the information is quite hard to find and the risks are quite high, so I'd like to make a promise - when I'm done rooting it and I know the correct process, I'm going to make a "Update to Marshmallow, unlock, root" how-to thread for all the people that will need it in the future.
Another two questions...
1. Where do I get proper SuperSU for Marshmallow? I get a boot loop (yeah, I know I have to wait and I did, but it's a pretty obvious bootloop from watching the logcat content, and nothing new happens...) after flashing http://download.chainfire.eu/supersu-stable (2.65).
2. I have unlocked my bootloader and installed TWRP, so recovery and fastboot are functional. I didn't make a backup before flashing the zip and now I'm in a bootloop. How do I restore working Marshmallow? I assume I can either beg somebody to upload a TWRP backup for my H60-L04, or somehow flash the stock over what I have now. Can I simply use manual update from SD? Can I somehow flash Marshmallow again with fastboot? I'm too scared of bricking my device right now so I guess I'll brace myself for a few days without a phone until somebody helps me :/
I just flashed the Marshmallow release I had before the bootloop (I used Huawei Update Extractor and flashed boot, cust, system and recovery with fastboot; then open up Huawei recovery and factory reset for good measure, I'm not sure it was even needed) and the device is working. I'll restore my stuff, install TWRP, make a backup then try out your ZIP. Thanks
edit: thanks again - your zip works indeed. So after the initial hurdles, now I've got working root and a reasonable way of restoring in case I screw something up along the way.
Before making a new topic with the tutorial I have a few more questions.
First of all, why exactly we weren't supposed to update the rooted devices? I'm not currently interested in OTAs (it's pretty obvious that it needs a functional Huawei recovery, and you need to unroot cause an update can make a mess in a rooted system, making it bootloop for example), but can we flash extracted images with fastboot on rooted devices? Logically, we should be able to... How about sdcard update method?
Can we flash Marshmallow on Kitkat? (fastboot, sdcard, local update methods?) Or do we need to update to Lollipop along the way?
Can I flash stock roms in general (evenbetween different Android versions) by using fastboot with {boot, cust, recovery, system} images only? There's a lot of images that you can extract with Huawei Update Extractor - why there's so many if they're not needed?
Hey guys,
I tried out the Android Concept MM when it first came out and i was a huge fan and insanely satisfied due to it's stock-like android experience, however the only thing keeping me away from using it is lack of root and xposed, however i was wondering can i just make a pre-rooted ftf with the ftf of the concept with recroot 4? like i would with a normal Marshmallow ftf or am i completely wrong?
I would appreciate the help thanks!
Concept ROM uses dm-verify, so it's unrootable on locked bootloader. However I've managed to root it on unlocked bootloader before somehow. I'll try to explain as best as I can:
1. Download and flash concept FTF http://forum.xda-developers.com/z3/...arshmallow-t3229030/post66825447#post66825447 (this is latest one I could find)
2. OTA update to the latest version if you want
3. Download Systemless SuperSU zip and place it on SD card https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
4. Flash recovery via fastboot (it needs unlocked bootloader) (for recovery I used this one) : http://forum.xda-developers.com/z3/development/z3-twrp-2-8-7-0-d6603-t3273996
5. Don't leave fastboot mode! Navigate with volume keys to "recovery mode" and click power button to enter it.
6. Flash SuperSu you downloaded earlier and then reboot.
7. Done, enjoy your rooted Concept.
Nojus33 said:
Concept ROM uses dm-verify, so it's unrootable on locked bootloader. However I've managed to root it on unlocked bootloader before somehow. I'll try to explain as best as I can:
1. Download and flash concept FTF http://forum.xda-developers.com/z3/...arshmallow-t3229030/post66825447#post66825447 (this is latest one I could find)
2. OTA update to the latest version if you want
3. Download Systemless SuperSU zip and place it on SD card https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
4. Flash recovery via fastboot (it needs unlocked bootloader) (for recovery I used this one) : http://forum.xda-developers.com/z3/development/z3-twrp-2-8-7-0-d6603-t3273996
5. Don't leave fastboot mode! Navigate with volume keys to "recovery mode" and click power button to enter it.
6. Flash SuperSu you downloaded earlier and then reboot.
7. Done, enjoy your rooted Concept.
Click to expand...
Click to collapse
Thanks but damn that sucks, i don't really wanna' lose DRM keys plus i still have 1 year of warranty left.
Also, (http://forum.xda-developers.com/z3/development/rom-zyxxos-5-1-1-v1-0-pure-stable-fast-t3229169) ZyxxOS requires a unlocked bootloader, however is there anyway i can replace the boot.img with one that's utilized on a locked bootloader ROM or will that not work
Salaminator said:
Thanks but damn that sucks, i don't really wanna' lose DRM keys plus i still have 1 year of warranty left.
Also, (http://forum.xda-developers.com/z3/development/rom-zyxxos-5-1-1-v1-0-pure-stable-fast-t3229169) ZyxxOS requires a unlocked bootloader, however is there anyway i can replace the boot.img with one that's utilized on a locked bootloader ROM or will that not work
Click to expand...
Click to collapse
Well, ZyxxOS has Sony's Concept based kernel. The developer itself at first thought it will work on locked bootloader, but it didn't. You could try to flash original Concept .2099 kernel, but I don't think it will work.
As for DRM, you can easily backup them before unlocking, but it's up to you.
Nojus33 said:
Well, ZyxxOS has Sony's Concept based kernel. The developer itself at first thought it will work on locked bootloader, but it didn't. You could try to flash original Concept .2099 kernel, but I don't think it will work.
As for DRM, you can easily backup them before unlocking, but it's up to you.
Click to expand...
Click to collapse
I'm confused with the effect DRM has but is there anyway to avoid them? Like if i backup do i just restore them after unlocking my bootloader?
Ideally, i wanted to run a AOSP like ROM and i hoped to remove all Sony stuff etc from Concept, However i'm just reluctant to unlocking my bootloader
This is probably the stupidest idea ever, I have close to no knowledge however what happens if i put Stock Sony 6.0.1 Kernel which has already obtained recovery without unlocking bootloader and flash SuperSU via that?
Alternatively, is there anyway to convert Our current Stock 6.0.1 into True Stock Android
Salaminator said:
I'm confused with the effect DRM has but is there anyway to avoid them? Like if i backup do i just restore them after unlocking my bootloader?
Ideally, i wanted to run a AOSP like ROM and i hoped to remove all Sony stuff etc from Concept, However i'm just reluctant to unlocking my bootloader
This is probably the stupidest idea ever, I have close to no knowledge however what happens if i put Stock Sony 6.0.1 Kernel which has already obtained recovery without unlocking bootloader and flash SuperSU via that?
Alternatively, is there anyway to convert Our current Stock 6.0.1 into True Stock Android
Click to expand...
Click to collapse
Maybe, but this is beyond my knowlege. Sorry.
EDIT: Or just use concept haha
Nojus33 said:
Maybe, but this is beyond my knowlege. Sorry.
EDIT: Or just use concept haha
Click to expand...
Click to collapse
Looking into Android 6.0 Complications from this article (http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/)
It states the following:
If you want root today, on Android Marshmallow (6.0), you’re going to need to use a modified boot image. While it remains to be seen if this remains true indefinitely, it looks likely to be the case for some time – SELinux changes make it much harder to get root access without modifying the boot image. And as modifying the boot image requires an unlocked bootloader
Click to expand...
Click to collapse
So i'm assuming Z3 Has SELinux thus preventing us from editting the boot image for Marshmallow Concept hence leaving us with the only option to unlock out bootloader?
Lastly: Is there a potential to convert Stock Sony ROM into an AOSP looking/feeling rom?
So I've been looking into this, it seems it's possible to use flashify which allows you to flash .img files if your bootloader is locked and you have root you can flash twrp this way. Flashify can also make backup of stock recovery and install it, the reason i'm interested in this is security, as unlocked bootloaders have lots of risks.
Another post i was reading a person suggested, different manufacturers have different ways they implement locked bootloaders so some phones recovery might be protected and can't flash twrp while locked others may differ, I'm not sure. I currently have a Samsung S7 Edge, some people suggested issues around possible hard bricks, suggesting it's more likely to happen with a locked bootloader, then others saying fastboot wouldn't be able to recovery the device if installing a rom failed.
Someone pointed this out about my OEM unlock not been able to enable it to recover, tho odin doesn't require that to be turned on to flash back the stock firmware from download mode so that should fix that. I want to know the risks involved if flashify flashing twrp, kernels and roms while bootloader is locked is likely to work fine, i have seen posts of people who have done it most the comments seem like they could be assumptions best guesses around this type of thing. I can't find much on it.
What i'm thinking is find an exploit to get root, while locked flash twrp with flashify use twrp to flash xposed maybe? then restore stock recovery after flashing all the things i need, so if i loose the phone bootloader is locked and they don't have clear access to twrp, i think magisk is impossible as that modifys the boot which is the locked bootloader i believe so don't know which things magisk or others will or won't work.
Appreciate all reply's.
Thanks.
So I've seen a few posts in the past, where someone has suggested rooting then locking the bootloader and other things like this. But now days do all phones delete data when they unlock the bootloader, if yes do some manufacturers not delete the data when you choose to relock the bootloader?
What i want is to know which brands if any would be possible for me to, unlock the bootloader flash twrp flash xposed other files root ect restore the stock recovery and then relock the bootloader keeping the changes i have made, for security reasons unlocked bootloaders are risky.
The next question is if this is possible if something messes up while it's locked, i won't have twrp to recover it, how would i fix this is this a issue for bricking the device? will fastboot always work to flash stock firmware files if the manufacturer provides them? i'm assuming that would be the only way to solve this? does fastboot need something like OEM unlock turned on in the system to be able to flash firmware to recover? if it does i wouldn't be able to fix that.
Samsung doesn't require OEM unlock to be turned on to flash through odin, but because of all samsung phones using dm-vertity even if the bootloader doesn't delete everything locking it, dm-verity would detect the changes and prevent using the phone in that state.
Appreciate all suggestions.
Thanks.