Related
I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?
wheelbarrel said:
I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?
Click to expand...
Click to collapse
If it's a Verizon one probably not. If it's a Google store pixel, Yes just unlock it again. It will wipe again.
Why did you relock it in the first place
KittyRgnarok said:
Why did you relock it in the first place
Click to expand...
Click to collapse
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T
KittyRgnarok said:
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T
Click to expand...
Click to collapse
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!
b00ster23 said:
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!
Click to expand...
Click to collapse
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones
KittyRgnarok said:
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones
Click to expand...
Click to collapse
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...
b00ster23 said:
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...
Click to expand...
Click to collapse
Tru Tru
wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)
Poebat said:
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)
Click to expand...
Click to collapse
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
Ah. I figured that might be the case.
b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
I mean almost every custom kernel for pixel og has proper safety net support
I appreciate all your input everyone! Unfortunately I am going to have to wait until it's time to buy a Pixel 2 lol, which is getting close
This is proof you should read EVERYTHING first lol
XDA today published an article about a vulnerability in the OnePlus 6 bootloader that allows the booting of a custom boot.img image without unlocking the bootloader. This is of course a huge security risk but I'm sure OnePlus will patch it in an upcoming update. In the mean time, let's have some fun!
Back in the good old days of the Nexus 4, it was possible to install an app that would write boot config data to the device from userland, with root, to toggle the bootloader between the locked and unlocked states. The object of this post? Do this as a community for the OnePlus 6!
Why do this?
There are two major gains to being able to do this:
Security: once a device is rooted we'd be able to re-lock the bootloader to prevent tampering or unauthorised images from being booted whilst keeping the perks of being rooted
Netflix HD: Widevine L1 keys aren't accessible when the Bootloader is unlocked. This way, we may be able to get our Widevine keys accessible again to get HD Netflix with root
I attempted to reverse some of the bootloader on my own a few weeks back but didn't have much luck. With this vulnerability, my thoughts are that we could dump the data partitions with a locked device (that is exploited using this trick) and compare them with an unlocked device. This might give us the magic data that the bootloader uses to determine whether a device is locked or unlocked. Then, in theory, we should be able to toggle this data from userland. The only caveat to this is that I don't know whether the unlock state is stored somewhere in the TrustZone or if it is written to the flash like they did back in the Nexus days.
I honestly have no idea whether this will work, but surely it's worth a shot? Just for reference, I recommend we look at diffing following partitions before and after locking:
param
sec
sti
ssd
frp
config
misc
We should also, to ensure there is no confusion, stick to OOS 5.1.5 stock + Magisk for root. Images of the above partitions can be obtained using dd.
If anybody has any further tips on bootloaders that either proves that this won't work, or perhaps can suggest other places this lock data could be stored, please do let me know!
NB: getting this data will involve at least one full data wipe of the phone so it might take time to dump the data, switch lock state then dump it again.
I also strongly suspect that we might hit the issue of Android Verified Boot noticing that the device is locked (but has a modified boot image when rooted). This would depend on whether the Android security checks are implemented as per the Android Verified Boot specification.
Who's in?
Couldn't you just hide Netflix HD from root detection in Magisk?
dgunn said:
Couldn't you just hide Netflix HD from root detection in Magisk?
Click to expand...
Click to collapse
No. With an unlocked bootloader the device is switched to Widevine level 3 instead of level 1. This means no HD playback in Netflix (and I believe Amazon) regardless of Magisk hide status. This may be the new normal for all unlocked devices with the Qualcomm SD 845 or newer.
blackthund3r;76765953[* said:
Security: once a device is rooted we'd be able to re-lock the bootloader to prevent tampering or unauthorised images from being booted whilst keeping the perks of being rooted
Click to expand...
Click to collapse
Are you sure about this? On Nexus 4 days Android didn't check at boot that all partitions were correct in order to boot, since some version ago it does (DM-verity). Are you sure you can re-lock the phone with root (system or boot modified) and still boot normally to userspace?
RusherDude said:
Are you sure about this? On Nexus 4 days Android didn't check at boot that all partitions were correct in order to boot, since some version ago it does (DM-verity). Are you sure you can re-lock the phone with root (system or boot modified) and still boot normally to userspace?
Click to expand...
Click to collapse
Well, I can confirm that with SafetyNet test passing, and Magisk hide enabled for Netflix, I can not get HD streaming.
This is highly interesting. I will be following that threat constantly. Thanks for opening that discussion.
So does this vulnerability allow flashing or booting of TWRP through fastboot without unlocking the bootloader. I am interested in keeping Netflix HD and gaining root access, but don't want to brick the device. I know that under normal circumstances you always unlock the bootloader before flashing any mods, but was curious of some devs thoughts on it.
Interesting read. You can root the device without unlocked bootloader
https://www.androidcentral.com/oneplus-6-bootloader-vulnerability-lets-anyone-access-your-phone?amp
the question is can we keep opened this feature and force to be opened.
Unfortunately oneplus bootloader doesn‘t support EIO mode,so it can't be boot if anything modified.
akaHardison said:
Unfortunately oneplus bootloader doesn‘t support EIO mode,so it can't be boot if anything modified.
Click to expand...
Click to collapse
Not true booted a magisk patched boot image and installed some modules
Is there Maby another methode to root hold safety net for widevine lv3
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
joemossjr said:
Not true booted a magisk patched boot image and installed some modules
Click to expand...
Click to collapse
And did you also installed magisk to the boot img?!
Widevine L1 + V4A would make me very happy. Perhaps we should add a financial incentive like a bug bounty? I would certainly contribute some loot for this noble cause!
Since some people with OP5s and OP5Ts sent there phone to OP for L1 with the bootloader unlocked, I wonder if OP would consider offering a similar service. Even if it wasn't completely free I would probably do it unless it required re-locking the bootloader...
Hi, ever since bootloader unlock in my Zenfone 6 fingerprint crashes all apps that use it (like Settings or OneTimeInit). Currently running pure stock. If I relock it with asus-back it returns to life, however I'd like to keep this state after unlock too. After second lock I've removed all phone security in case something blocked fp reader from there but no luck. Any ideas?
Also, is there any way to unlock the bootloader n-th time without using that apk unlocker/without internet conenction? I know the relock command but things that unlock it like asus-go don't work.
Probably downgrading to pie and then upgrading to Q will fix it according to https://forum.xda-developers.com/zenfone-6-2019/help/relocked-zenfone-6-lockscreen-t4033321
Oh, I will downgrade it to Pie allright. Just bricked my phone and messed up dm verity on locked bootloader. I prefer Samsungs to play with...
Edit: You were right. I've unlocked it on Pie and works great. I don't know why xda search couldn't find that thread for me. Thank you.
So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.
Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
I like to think I'm quite tech savvy but the guides for the P7Pro have gone over my head :/
Connorsdad said:
Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Click to expand...
Click to collapse
Not unless you want to brick your device. You need to be completely stock before relocking your bootloader (unless using avbroot, but you should have a deep understanding about how it works beforehand).
Connorsdad said:
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
Click to expand...
Click to collapse
Pixel Flasher will work fine for updating.
Lughnasadh said:
Not unless you want to brick your device.
Click to expand...
Click to collapse
Huh, learn something new every day I guess...
Lughnasadh said:
Not unless you want to brick your device. You need to be completely stock before relocking your bootloader (unless using avbroot, but you should have a deep understanding about how it works beforehand).
Pixel Flasher will work fine for updating.
Click to expand...
Click to collapse
Awesome, thanks a lot for your reply, much appreciated.
never ever* lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
* exception
alecxs said:
never ever lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
Click to expand...
Click to collapse
And you can't flash a factory image to fix a phone on your own when it's soft bricked. It might have to go to a shop for repairs.
Connorsdad said:
Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
I like to think I'm quite tech savvy but the guides for the P7Pro have gone over my head :/
Click to expand...
Click to collapse
AFAIK, relocking the bootloader requires wiping the device -- much like unlocking does -- and if you're unwilling to set everything (including anything on your /sdcard internal storage, not to mention all apps and their settings & system settings) back up from scratch (as any good complete backups require root access), this might not be what you wish to do.
And, if you had managed to successfully relock the bootloader, you could simply run the in-system update (OTA) that would update without wiping -- or even manually applying OTA from the recovery.
But there are hardly any benefits in re-locking the bootloader (after unlocking it) -- even if one was to a paranoid degree of security; which is the only major reason to (I can point you to the discussions that had taken place on it here, if you wish). If you don't want to run into any issues, you could simply run the stock ROM without root and be hardly impacted by it; with the added benefit of having the option to advanced recovery options and/or rooting options open to you in the future if need be...
alecxs said:
never ever lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
Click to expand...
Click to collapse
*it just occurs to me you meant to never lock bootloader because it limits options; not the risk of hard-bricking the device -- in which I wrote the following with that assumption. I'll leave the following comment as it is still sound advice, but I apologize in advanced that it doesn't quite relate to what you meant...
I mean, I feel doing Google's official Android Flash Tool is a safe enough method; it wouldn't do well if Google's own tool bricked their devices using their tool...at the very least the tool ensures that the stock factory firmware flashed matches the bootloader version and automates the fastboot commands so when re-locking the bootloader, it has the least potential to brick the device...
Exactly. there is no official flash tool from google, that's why I personally won't recommend to keep bootloader locked. If it's bricked with no working recovery mode, not even repair shop can fix it. all you can do is RMA to google get new device. no edl mode or anything else will help, fastboot is the official flashing method.
If you're referring to the "Android Flash Tool" that's no flash tool at all. I haven't tested it, but to me it looks like a WebUSB browser plugin. Reading the requirements it works with adb commands, usb-debugging and fully booted android is required. Therefore cannot unbrick devices.
Doesn't unlocking the bootloader break saftynet so then you have to root to use gpay?
iRhyiku said:
Doesn't unlocking the bootloader break saftynet so then you have to root to use gpay?
Click to expand...
Click to collapse
I'll just chime in here because I have recently unlocked my bootloader but I haven't been able to root it yet and I haven't had any issues with safety net.
Trippyy Doee said:
I'll just chime in here because I have recently unlocked my bootloader but I haven't been able to root it yet and I haven't had any issues with safety net.
Click to expand...
Click to collapse
Interesting, I thought unlocking would break it. I'll have to unlock then for the extra safty!
iRhyiku said:
Interesting, I thought unlocking would break it. I'll have to unlock then for the extra safty!
Click to expand...
Click to collapse
That's of course another aspect. Good point. If you rely on SafetyNet or it's successor Play integrity, do not unlock bootloader. AFAIR the latter one can't be cheated.
simplepinoi177 said:
But there are hardly any benefits in re-locking the bootloader (after unlocking it)
Click to expand...
Click to collapse
There are some benefits like some banking apps, streaming apps and games beginning to work. So it really depends on what is important for the user. I don't like flashing random mods to make apps work on rooted/ bootloader unlocked devices, primarily banking apps.