Hi,
Has anyone been able to successfully relock their bootloader after erasing and flashing stock firmware?
The fastboot command "fastboot oem lock" returns:
"FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
Maybe you reboot on wrong fastboot mode, or Try use latest adb fastboot
YusukeYuu said:
Maybe you reboot on wrong fastboot mode, or Try use latest adb fastboot
Click to expand...
Click to collapse
Unfortunately I think Sony my have blocked the ability to relock the bootloader
I am using latest 'platform-tools_r33.0.3-windows' and I've also installed specific Sony fastboot driver from Sony Developers.
I am booting into default 'fastbootd' mode.
So this command aint work ?
fastboot oem lock
Yes that is correct, it seems that Sony have sealed up the ability to relock ourselves
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rasseru16 said:
Yes that is correct, it seems that Sony have sealed up the ability to relock ourselves
Click to expand...
Click to collapse
maybe need to use the same serial number that you used to unlock the bootloader
Sakuma_Eitarou said:
maybe need to use the same serial number that you used to unlock the bootloader
Click to expand...
Click to collapse
How do you mean. I am using the same phone I used to unlock so the serial number should remain the same?
rasseru16 said:
How do you mean. I am using the same phone I used to unlock so the serial number should remain the same?
Click to expand...
Click to collapse
yes
if you save that number
Weird, my xperia 1 iii can relock
rasseru16 said:
Yes that is correct, it seems that Sony have sealed up the ability to relock ourselves
View attachment 5720029
View attachment 5720033
Click to expand...
Click to collapse
Try selecting reboot to bootloader first before using the command
YusukeYuu said:
Weird, my xperia 1 iii can relock
Click to expand...
Click to collapse
Did you also update to Android 12 bootloader?
rasseru16 said:
Did you also update to Android 12 bootloader?
Click to expand...
Click to collapse
Yes
You have to reuse the code you used to unlock the bootloader, for example : fastboot oem lock C46...09
fastbooking said:
You have to reuse the code you used to unlock the bootloader, for example : fastboot oem lock C46...09
Click to expand...
Click to collapse
Will give that a go
fastbooking said:
You have to reuse the code you used to unlock the bootloader, for example : fastboot oem lock C46...09
Click to expand...
Click to collapse
Unfortunately, I still receive the same error, oh well I guess only Sony can repair it and relock the bootloader.
You need to go on bootloader not fastbootd mode
YusukeYuu said:
You need to go on bootloader not fastbootd mode
Click to expand...
Click to collapse
If I select 'Reboot to bootloader' the screen is black and I need to specify which driver to install, seeing as that mode isn't fastboot I am trying to understand how it would relock the bootloader?
Thanks
rasseru16 said:
If I select 'Reboot to bootloader' the screen is black and I need to specify which driver to install, seeing as that mode isn't fastboot I am trying to understand how it would relock the bootloader?
Thanks
Click to expand...
Click to collapse
Yes, the screen will go black, but you can use the fastboot command as long as the notification turns blue.
YusukeYuu said:
Yes, the screen will go black, but you can use the fastboot command as long as the notification turns blue.
Click to expand...
Click to collapse
Ok thanks, I cannot get the notification icon to turn blue am I doing something wrong? :/
You should have read my Guides.
fastboot reboot fastboot is the only command You'll need to switch between fastboot and fastbootd.
But just turn off Your Phone. Hold Volume Up and Connect USB. Blue LED and Done
fastboot oem lock
Done
Do a Software Repair with Xperia Companion after. Just liike told in My Guides. Enjoy
Related
Xperia Neo 4.0.2.A.0.62 downgrade 4.0.2.A.42 and root. Install drivers and fastboot software. Command fastboot.exe -i 0x0fce getvar version status 0.3, next command fastboot.exe -i 0x0fce oem unlock 0xKEY (key instruction unlockbootloader.sonymobile) status failed...
Shaolin' said:
Xperia Neo 4.0.2.A.0.62 downgrade 4.0.2.A.42 and root. Install drivers and fastboot software. Command fastboot.exe -i 0x0fce getvar version status 0.3, next command fastboot.exe -i 0x0fce oem unlock 0xKEY (key instruction unlockbootloader.sonymobile) status failed...
Click to expand...
Click to collapse
I would try these things:
1) try again
2) use another USB port
3) use another cable
4) use another computer
Good luck!
How about calling *#*#7378423#*#* and check for bootloader unlock allowed?
alvinwong_1234 said:
How about calling *#*#7378423#*#* and check for bootloader unlock allowed?
Click to expand...
Click to collapse
Rooting Status:
Bootloader unlock allowed: Yes
yogodo said:
I would try these things:
1) try again
2) use another USB port
3) use another cable
4) use another computer
Good luck!
Click to expand...
Click to collapse
Use Ubuntu 11.10 install android SDK and use fastboot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Shaolin' said:
Xperia Neo 4.0.2.A.0.62 downgrade 4.0.2.A.42 and root. Install drivers and fastboot software. Command fastboot.exe -i 0x0fce getvar version status 0.3, next command fastboot.exe -i 0x0fce oem unlock 0xKEY (key instruction unlockbootloader.sonymobile) status failed...
Click to expand...
Click to collapse
Is that the exact command you used ? Did you replace key with the key you got from Sony
Sent from my MT11i using Tapatalk
And I do believe you don't use last number
Sent from my MT15i using Tapatalk
He again asked for the key was the same.
Perhaps you'd contact SE support and see what's the official response. Better than guessing
kormatoes said:
And I do believe you don't use last number
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
imei removed character to the right
I have the same problem but i don't have ubuntu and don't know how to use it....any other solution that can be done in Windows7???
mohamedawad said:
I have the same problem but i don't have ubuntu and don't know how to use it....any other solution that can be done in Windows7???
Click to expand...
Click to collapse
fastboot.exe -i 0x0fce getvar version status 0.3 ?
lock fastboot
i have a branded phone, and my bootloader and fastboot is lock following the instruction in sony web page, i saw that my phone under bootloader lock it say :no. thats mean that i can unlocl my phone following the previous steps, is there another way to unlock my phone and unlock the bootloader because i want to install different roms. thank you
arcaneck said:
i have a branded phone, and my bootloader and fastboot is lock following the instruction in sony web page, i saw that my phone under bootloader lock it say :no. thats mean that i can unlocl my phone following the previous steps, is there another way to unlock my phone and unlock the bootloader because i want to install different roms. thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1558206
Shaolin' said:
fastboot.exe -i 0x0fce getvar version status 0.3 ?
Click to expand...
Click to collapse
yes, the phone was properly connected in fastboot mode and drivers are ok, and i get the 0.3 response as well
What i should do if i have Rooting Status:
Bootloader unlock allowed: No ?
Are there any other ways?
KinKeid said:
What i should do if i have Rooting Status:
Bootloader unlock allowed: No ?
Are there any other ways?
Click to expand...
Click to collapse
You need to use SETool2 paid method like me,comtact somrone like Jinx13.There is no free way
Shaolin' said:
Xperia Neo 4.0.2.A.0.62 downgrade 4.0.2.A.42 and root. Install drivers and fastboot software. Command fastboot.exe -i 0x0fce getvar version status 0.3, next command fastboot.exe -i 0x0fce oem unlock 0xKEY (key instruction unlockbootloader.sonymobile) status failed...
Click to expand...
Click to collapse
a common mistake that may be happen through this method is that your inputing all 15 numbers of your IMEI in SE official site.
only first 14 numbers must be inputed and last one not,if you give all 15 numbers it gives you wrong code and may be your problem was due to that
Good Luck
another common problem was when just direct pasting the KEY and sometimes when you type the KEY manually and you didn't press capslock.
alvinwong_1234 said:
How about calling *#*#7378423#*#* and check for bootloader unlock allowed?
Click to expand...
Click to collapse
it shows allowed as rooting status....but in cmd it fails plzzz help wat went wrong...........
Hello, I need help.
I have had my nexus 9 bricked for like 6 months or more..
I tried to upgrade to Android 6 developer preview 3..
It doesn't boot.. I see the alert that the device may be corrupt and that things..
I tried to find a OTA but there isn't one for
6.0/MPA44I/2172151 to ->???
After it didn't worked I *as stup*id* did:
fastboot erase system
fastboot oem lock
I think my system partition is corrupt and my bootloader is locked.
I can't do anything, I tried to sideload android N from developer. android. com /intl/es/preview/download-ota.html
BUt nope..
Please help..
I replied to you on the other threads but you have supplied more information here.
"fastboot erase system" probably didn't do anything as your bootloader is locked.
Last thing to try, if you haven't done so already is to try sideloading
volantis MPA44I from MPZ79M
That link gotten from here.
If that doesn't work. You don't have a soft brick but an expensive paperweight!
corkiejp said:
I replied to you on the other threads but you have supplied more information here.
"fastboot erase system" probably didn't do anything as your bootloader is locked.
Last thing to try, if you haven't done so already is to try sideloading
volantis MPA44I from MPZ79M
That link gotten from here.
If that doesn't work. You don't have a soft brick but an expensive paperweight!
Click to expand...
Click to collapse
Hey, I will try.
I did fastboot erase system before lock
At least I can say that I've tried ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ignaciouy said:
Hey, I will try.
I did fastboot erase system before lock
Click to expand...
Click to collapse
I read that as "fastboot oem unlock", did the update process brick your tablet.
Are did you issue the commands 6 months ago and that is why your device is bricked?
corkiejp said:
I read that as "fastboot oem unlock", did the update process brick your tablet.
Are did you issue the commands 6 months ago and that is why your device is bricked?
Click to expand...
Click to collapse
Kinda, I'm 100% sure that it's because I removed the system partition. and then oem lock
r ur bootloader soff and unlocked?
lusamuerstan said:
r ur bootloader soff and unlocked?
Click to expand...
Click to collapse
My bootloader is locked.
I can't boot in Android (probably there's nothing on system partition.) and I wasn't able to install Android N because my recovery is too old
ignaciouy said:
My bootloader is locked.
I can't boot in Android (probably there's nothing on system partition.) and I wasn't able to install Android N because my recovery is too old
Click to expand...
Click to collapse
what recocery u have.
Sent from my Nexus 9 using Tapatalk
How to see that?
I have the Android M developer preview 3
Still think you have an expensive paperweight.
Have you tried the command "fastboot oem unlock" since you locked the device?
Can you boot a newer stock recovery.img or TWRP.img with
"fastboot boot <name of recovery.img>"
On the odd chance that actually boots, try sideloading Android N OTA again.
Even if it boots, your corrupted system.img might prevent the OTA from been applied.
Note: Try the above commands with your device in bootloader mode.
corkiejp said:
Have you tried the command "fastboot oem unlock" since you locked the device?
Can you boot a newer stock recovery.img or TWRP.img with
"fastboot boot <name of recovery.img>"
On the odd chance that actually boots, try sideloading Android N OTA again.
Even if it boots, your corrupted system.img might prevent the OTA from been applied.
Note: Try the above commands with your device in bootloader mode.
Click to expand...
Click to collapse
That doesn't work, I already tried...
If I replace the motherboard the tablet should work, no?
I think its better to buy a motherboard Instead of getting a new one
ignaciouy said:
That doesn't work, I already tried...
If I replace the motherboard the tablet should work, no?
I think its better to buy a motherboard Instead of getting a new one
Click to expand...
Click to collapse
I wouldn't waste money on a new motherboard as you storage is corrupted, so you would still be faced with trying to get a working system on it.
Write it off as a lesson learned!
corkiejp said:
I wouldn't waste money on a new motherboard as you storage is corrupted, so you would still be faced with trying to get a working system on it.
Write it off as a lesson learned!
Click to expand...
Click to collapse
Mhm, isn't the storage on the motherboard?
https://es.ifixit.com/Guide/Nexus+9+Motherboard+Replacement/43015
can you flash latest marshmallow factory image?..or it stuck during flash the img
Sent from my Nexus 9 using Tapatalk
Can you unlock the bootloader again? Chances are "OEM unlocking" option is still toggled and open.
No, I can't unlock my bootloader.
I tried sideloading Android N, and it doesnt work.
Probably because my keys are dev-key? I have no idea.
Rip nexus ((
Hello! I'm kind of affraid to root my phone (I do it with my previous phons but this is something else, I'm affraid to brick it), so I want to post the steps I understand I must do to root to confirm and go for it with a relief mood. :laugh::laugh::laugh:
I have a Le Max X829
1 - Go to developer options, active debug mode and oem unlock mode
2 - Turn off the phone. Put it on recovery? Leave it off? (how can I access?) and go to ADB on Windows (I have W7). Execute command: fastboot devices to see if the devices is recognized, if it's execute fastboot oem unlock (name of the TWRP image) [I have to put the file on the phone or isn't neccesary?). Enter the command and wait. I'll lost everything that I have on the phone right? (that happen when I unlock the bootloader on my Moto E)
3 - Once is done, unplug the phone from the computer and turn it on. Install magisk manager and put magisk installer and uninstaller on the internal storage. Reboot the phone to TWRP and install Magisk
4 - Boot the phone and done
Is everything ok in that way? Is the way to root the phone? I want to do it to use Greenify properly, to use L-Speed or Helix
Fastboot command works only on bootloader mode, power on with volume down pressed, but its good you follow this guide.
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
Beackman said:
Fastboot command works only on bootloader mode, power on with volume down pressed, but its good you follow this guide.
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
Click to expand...
Click to collapse
thanks Beackman, so I have to be in bootloader mode instead of recovery, thanks!
I'll lost apps and photos if I unlock the bootloader right?
AgustinH said:
I'll lost apps and photos if I unlock the bootloader right?
Click to expand...
Click to collapse
Yes, for unlock bootloader the memory is wiped, so make a full backup first.
Beackman said:
Yes, for unlock bootloader the memory is wiped, so make a full backup first.
Click to expand...
Click to collapse
ok, and how can I do a backup, through stock recovery?
AgustinH said:
ok, and how can I do a backup, through stock recovery?
Click to expand...
Click to collapse
If you can boot into android make a backup of your internal data, photos, music etc.
If not, maybe, over the stock recovey you can do it, i never tested with stock recovery.
Beackman said:
If you can boot into android make a backup of your internal data, photos, music etc.
If not, maybe, over the stock recovey you can do it, i never tested with stock recovery.
Click to expand...
Click to collapse
ok Beackman, one more question, once I unlock the bootloader, install TWRP, when I turn on the phone it will be like a factory reset? I mean, I have to configure wifi, google accounts, etc?
AgustinH said:
ok Beackman, one more question, once I unlock the bootloader, install TWRP, when I turn on the phone it will be like a factory reset? I mean, I have to configure wifi, google accounts, etc?
Click to expand...
Click to collapse
Yep.
I didn't do nothing yet, but I see the oem info through fastboot and this appear. Does it mean that I don't have to unlock the bootloader, the bootloader is already unlocked?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AgustinH said:
I didn't do nothing yet, but I see the oem info through fastboot and this appear. Does it mean that I don't have to unlock the bootloader, the bootloader is already unlocked?
Click to expand...
Click to collapse
Yes already unlocked, just jump for part of flashing TWRP and so on.
I have a XT1941-4 that is stuck in the Bootloader. Whenever I press 'START' it says that the device can't be verified and will boot in 5 seconds, but it never actually boots. Is there anything I can do as a noob to get this phone to work again?
you could flash motorola's stock rom to the phone using fastboot on your pc or using motorola rescue and smart assistant. https://www.getdroidtips.com/motorola-rescue-and-smart-assistand-tool/
applesucksLmao said:
you could flash motorola's stock rom to the phone using fastboot on your pc or using motorola rescue and smart assistant. https://www.getdroidtips.com/motorola-rescue-and-smart-assistand-tool/
Click to expand...
Click to collapse
I have tried to go ahead with this tool. It recognises my device but failed at around 50% at step Fastboot Flash before. I just ran it again and its stuck at that step now. Any way to fix this?
ogruendel said:
I have tried to go ahead with this tool. It recognises my device but failed at around 50% at step Fastboot Flash before. I just ran it again and its stuck at that step now. Any way to fix this?
Click to expand...
Click to collapse
Failed after 6 minutes at ~70%
send pictures of the "fail" and the phone screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
applesucksLmao said:
send pictures of the "fail" and the phone screen
Click to expand...
Click to collapse
Just added them to the thread
delete the first photo, as it contains your IMEI number. Have you tried to manually flash the image, and also, are you using the original oem cable?
applesucksLmao said:
delete the first photo, as it contains your IMEI number. Have you tried to manually flash the image, and also, are you using the original oem cable?
Click to expand...
Click to collapse
Deleted the first image. I don't know how to manually flash an image or where to get this image to begin with. I am also not using the cable that came with the phone. I will try to find it and see if that works
Edit: Come to think of it I believe this cable broke a while ago
Ok, so, to help u i gotta get some info first. What country was the phone purchased at/where do u live and use it? Is it updated to android 10? What did u do to that happen?
applesucksLmao said:
Ok, so, to help u i gotta get some info first. What country was the phone purchased at/where do u live and use it? Is it updated to android 10? What did u do to that happen?
Click to expand...
Click to collapse
I bought the phone here in Germany where I live. I believe it was a display unit. I think it had Android 10 on it. I rooted it but when a message popped up saying there was an update available, that wouldn't go away I tried to unroot it and now we're here.
ogruendel said:
I bought the phone here in Germany where I live. I believe it was a display unit. I think it had Android 10 on it. I rooted it but when a message popped up saying there was an update available, that wouldn't go away I tried to unroot it and now we're here.
Click to expand...
Click to collapse
how did you try to unroot it?
applesucksLmao said:
how did you try to unroot it?
Click to expand...
Click to collapse
That was a year ago. I can't remember a lot.
ogruendel said:
That was a year ago. I can't remember a lot.
Click to expand...
Click to collapse
I am able to boot into TWRP. When I'm in TWRP only adb works, when I'm not in TWRP only fastboot works
ogruendel said:
That was a year ago. I can't remember a lot.
Click to expand...
Click to collapse
so you tried to unroot it a year ago and it just happened or its dead for 1 year?
enter fastboot then type this command in cmd
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot reboot
then try to use Rescue and Smart Assistant
best of luck
Hucin44 said:
enter fastboot then type this command in cmd
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot reboot
then try to use Rescue and Smart Assistant
best of luck
Click to expand...
Click to collapse
When running fastboot erase userdata I get (bootloader) Permission denied
ogruendel said:
When running fastboot erase userdata I get (bootloader) Permission denied
Click to expand...
Click to collapse
go to twrp and format data from the wipe section
applesucksLmao said:
go to twrp and format data from the wipe section
Click to expand...
Click to collapse
i mean the slider
applesucksLmao said:
i mean the slider
Click to expand...
Click to collapse
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Wiping data without wiping /data/media ...
Done.
Updating partition details...
...done
when you try to open download it shows 3 options resatrt , continue , unlock bootloader i pressed down key long for unlock bootloader screen turns black for few seconds then the device restarts and while using adb adb devices it does not show device but while tryoing fastbootdevices it show the id , while try to unlock the bootloader it fails
fastboot getvar unlocked
Yes or No
tom.android said:
fastboot getvar unlocked
Yes or No
Click to expand...
Click to collapse
Is this a code?
DARK002s said:
Is this a code?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DARK002s said:
when you try to open download it shows 3 options resatrt , continue , unlock bootloader i pressed down key long for unlock bootloader screen turns black for few seconds then the device restarts and while using adb adb devices it does not show device but while tryoing fastbootdevices it show the id , while try to unlock the bootloader it fails
Click to expand...
Click to collapse
1. ADB doesn't work in Download nor fastboot. ADB only works while booted into the OS
2. Have you enabled OEM unlock in Developer Options?
tom.android said:
View attachment 5676935
Click to expand...
Click to collapse
Failed
iBowToAndroid said:
1. ADB doesn't work in Download nor fastboot. ADB only works while booted into the OS
2. Have you enabled OEM unlock in Developer Options?
Click to expand...
Click to collapse
I was trying in fastboot mode
DARK002s said:
Failed
Click to expand...
Click to collapse
You didn't installed fastboot driver in your computer?
and didn't have TWRP in you tab?
If not all side , you can't use fastboot command for turn back oem unlock.
I saw error : Remote ...not found
I'd run above command from my tab a7 lite.
DARK002s said:
I was trying in fastboot mode
Click to expand...
Click to collapse
1. You don't unlock the bootloader via fastboot. So there's no use in even being in fastboot mode
2. You didn't answer re OEM Unlock
iBowToAndroid said:
1. You don't unlock the bootloader via fastboot. So there's no use in even being in fastboot mode
2. You didn't answer re OEM Unlock
Click to expand...
Click to collapse
It is not opening in adb it say unauthorised failed
DARK002s said:
It is not opening in adb it say unauthorised failed
Click to expand...
Click to collapse
ADB is not involved in unlocking the bootlaoder, whatsoever. You're not making any sense
iBowToAndroid said:
ADB is not involved in unlocking the bootlaoder, whatsoever. You're not making any sense
Click to expand...
Click to collapse
now unlocked bootloader what do delete through twrp like data , and should i flash vbmeta img before deleting files ? or befroe installing gsi???
DARK002s said:
now unlocked bootloader what do delete through twrp like data , and should i flash vbmeta img before deleting files ? or befroe installing gsi???
Click to expand...
Click to collapse
iBowToAndroid said:
ADB is not involved in unlocking the bootlaoder, whatsoever. You're not making any sense
Click to expand...
Click to collapse
twrp not showing up after flashing