Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
unlock it using flash tool, just press unlock wait and enter the code.. done
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
try using different usb cable/ different port.
Had same problem....some driver was missing
Sent from my C5503 using xda app-developers app
I've finally gotten flash tool to work, however now it gives me an error saying that my device cannot be officially unlocked,
EDIT: i'm pretty sure i've unlocked the bootloader now, as flashtool had me enter an unlock code and my device has had all of its data reset.
however my issues continue as now flashtool utterly refuses to pick up my device. I have re-installed all drivers, flashtool, etc but still nothing.
sometimes it may have conflicts when flashtool and other tools use their own instance of adb or fastboot. I think the best thing to do now is reinstalling regular drivers normally. don't forget to enable usb debugging...
this may be useful :
Code:
[I]ADB_PATH[/I]\adb kill-server
exit
create a text file, paste this code then save it as ADB - Kill.cmd
Hi all,
A few days ago I installed a custom ROM, which broke my android pay. I tried to re-lock the bootloader to fix this via the fastboot oem lock command, and i'm now stuck in a bootloop.
I can get the phone to boot into fastboot mode, and it shows up as such when checking via command prompt. I also have a backup of the phone I made a few days ago. I've tried to unlock the phone using the fastboot oem unlock command, but get the following error:
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.008s
I bought the phone second hand with an unlocked bootloader, if that makes a difference? I've set up a new Mi account and applied for an unlock code.
Does anyone have any tips on how to proceed? Thanks in advance!
Stupid thing to think relocking your bootloader would fix android pay while still on that custom rom, whe have hacks for that you know >> magisk14/15.2
Do you still have twrp? also try to flash stock images from xiaomi themselves, here.
that should at least get you booting again.
Hi,
Thanks for replying, i'll download the global stable version. Is it a case of sideloading this once complete? I still have TWRP installed if it makes a difference, I just can't reach it :/
Yes I do feel pretty stupid, and thanks for the link to magisk - hadn't heard of it until now but i'll definitely be using when/if I get my Mi back up and running. Is there anyway to unlock the bootloader other than the Mi Unlock app?
Thanks!
EDIT: Okay, so i tried flashing via the MiFlash tool and got the following error:
FAILED: Remote device is locked. Cannot erase.
Any idea of where to go from here?
So, I fixed it! In the off chance anyone is as unlucky/stupid/trigger happy as me, and finds themselves in teh same situation, here's the solution:
If you can't get it into EDL mode because you can't switch it off (mine kept rebooting), follow this video:
https://www.youtube.com/watch?v=ED96PJ-qYMM
It's in a foreign language but is clear enough - take the back off, unscrew the cover and short the pins he shows you after disconnecting the battery, then plug into your computer.
Your phone will pop up as a Qualcommdevice under the ports section of Device Manager. You should then be able to flash via MiFlash as per usual.
Phew, hairy there but sorted in the end. I'll now wait for the unlock code from Xiaomi, and do a bit more reading in future!
A much easier way to solve this problem
You don't have to follow any long tutorial. Nor do you have to open your phone up. Just power it into fastboot mode, download the mi unlock tool that you used the first time to unlock your bootloader and unlock your device once again. Then you can use miflash to flash the fastboot rom on your device and it won't throw up any errors. Once that's done, just reflash the custom recovery. Install the custom rom, use magisk for root and you're good to go. Safety net won't be tripped and android pay will still work. No need to rip your phone apart to fix it.
Hey!
So i'm making this post after battling over 4 days with my friends old oneplus 3t.
All started maybe year ago when my friend asked me for help because his oneplus had suddenly gone into a bootloop kind of state (he told me that the phone was in his pocket working fine and when he tried to use it next time it started acting up.) Before i could even help him he had already bought new iphone, so the oneplus stayed in his drawer until last week when i remembered it and started to try to fix it.
So first thing that i noticed was this message "The dm-verity is not started in enforcing mode and may not work properly", the message eventually went away and i got to a recovery mode and thought that this is gonna be easy, hooked the phone to pc and started adb and tried to sideload the official rom from oneplus site, but everytime i tried it went to maybe 47 %or 66% and failed eventually. So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
Downloaded Oneplus 3T unbrick tool v3.0, and qualcomm drivers (turned windows driver signature off) everything went great and the green text came in oneplus unbrick tool and i proceeded to start the phone in excitement and the circling bootlogo started and it just stayed there, nothing, and after while shut down.
Things tried now:
-Sideloading (many times with different roms) no success.
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
- Unbricktool v3.0 (Works like a charm everytime, but phone doesent still boot to os) no success
-recovery (wiped cache and all data many times) no success
My friend never flashed anything to this device, he doesn't even now how to do this kind of stuff.
Phone not dropped even once, is in a perfect condition and has all the original stickers even.
I have grown obsessed to fixing this phone, so any help is greatly appreciated :laugh:
onlyoneplusproblems said:
So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
Click to expand...
Click to collapse
I haven't personally ever had to use the unbrick tool, so I can't help too much with the core problem. But what I can say, is that the steps I've quoted above (trying to flash recovery partition, etc.) are going to fail by design, since the bootloader is locked. This is the very purpose of the locked bootloader. The expected result is "remote: not allowed".
And as far as I am aware, you have to have a working OS and have "OEM unlocking" first toggled on, in the phone Developer settings. Otherwise (again, by design) the "fastboot oem unlock" command is going to fail.
Spontaneous failure of the phone to boot to OS, and dm-verity warning, to me probably indicates the OS has become corrupt/damaged. The damage is showing as a change to the system, therefore the dm-verity warning. Normally, I would tell you to flash the stock recovery image. But of course you have already tried that. Probably difficult to determine for sure. but spontaneous failure, and failure to flash recovery image (multiple times) may indicate a hardware failure such as bad emmc.
has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
small update:
after updating to 52.0.A.8.50, I made "factory settings" to reset it to the old version.
But when I restart without wifi, I find build 52.0.A.8.50 again
And now the OEM unlock option, which was usable before, has turned gray !! Mystery for me.
Obviously he wants me to update to 52.0.A.8.85 !!!
SOLVED INFORMATION:
I was wrong in writing IMEI of my device, and I put a wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
bibibabi said:
has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
Click to expand...
Click to collapse
Try .131 vor wait for September
For wait for Q, maybe Sony will remove more DRM TA protection like it did with P
if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble
bibibabi said:
if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble
Click to expand...
Click to collapse
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions
MartinX3 said:
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions
Click to expand...
Click to collapse
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.
bibibabi said:
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.
Click to expand...
Click to collapse
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.
MartinX3 said:
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.
Click to expand...
Click to collapse
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.
bibibabi said:
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.
Click to expand...
Click to collapse
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you
MartinX3 said:
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you
Click to expand...
Click to collapse
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.
bibibabi said:
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.
Click to expand...
Click to collapse
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]
MartinX3 said:
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]
Click to expand...
Click to collapse
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work
bibibabi said:
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work
Click to expand...
Click to collapse
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole
MartinX3 said:
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole
Click to expand...
Click to collapse
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR
bibibabi said:
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR
Click to expand...
Click to collapse
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA
MartinX3 said:
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA
Click to expand...
Click to collapse
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone
bibibabi said:
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone
Click to expand...
Click to collapse
Should be impossible without a computer for initial installation
MartinX3 said:
Should be impossible without a computer for initial installation
Click to expand...
Click to collapse
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.
bibibabi said:
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.
Click to expand...
Click to collapse
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)
MartinX3 said:
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)
Click to expand...
Click to collapse
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?
bibibabi said:
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?
Click to expand...
Click to collapse
Please use the August .131 firmware and my matching stock twrp
I've been an android developers for years and years now and even have made my own ROMs, but this phone....this phone is testing me. I unlocked it months ago to install an original Android 11 ROM, but it was awful and lacked support for even the most basic functionality, so I flashed the stock image back. That alone was a nightmare and I don't remember how I managed it. That being said, the Asus Android 11 update is rolling out OTA and can be downloaded directly from their site. I downloaded it and put it in the root directory, where it is found on start-up, but when I tell it to install, it fails after a few seconds and doesn't give me any explanation for it. I thought it may be that the bootloader is unlocked, so I've been trying to re-lock it for weeks with no success. I managed to get the damn fastbootd mode recognised by my computer and it sees the phone, but when I give it any relock command I receive this error:
"FAILED (remote: Command not supported in default implementation)"I have no clue what to make of that or what it even means. My only guess is that the commands I'm using aren't supported in the latest version of the tools. I've tried the following commands:
fastrboot oem asus-lock
fastboot oem lock
fastboot oem asus_csk_lk
fastboot flashing lock
fastboot oem relock (I don't think that's a real command, but I was irritated and figured it was worth a shot)
I'm at a total loss. All I want is to get Android 11 to the damn thing and the OTA isn't coming through to my phone. The phone itself is an international model I bought from China back before it was released in the US. IDK if that's causing a problem, but at this point I'm out of ideas. I'd also note that normal fastboot, found by going to the bootloader instead of "adb reboot fastboot" doesn't even allow the computer to recognise the phone and when I try to install the fastboot driver via device manager, it outright refuses to install it. There's no apparent way to get it to install the driver anyway. I AM able to get it to install the driver and see the phone while in fastbootd mode.
Anyone got any ideas?
fastrboot oem asus-lock
This worked for me on tencent phone converted to ww firmware. I had no troubles with updating to 11 from 10 as well. I had also no troubles to flash raw firmware with bootloader unlocked.
Waiting now for new ww firmware as CN has been already released couple days ago.. If they didn't fix thing I'm annoyed with I going back to 10!
Try different cable. Had guy from reddit with same problem like yours and simple new cable sorted everything
fastboot oem asus_csk_lk should do it.
I think you may be in the wrong fastboot mode You need to be in the bootloader. Try powering off and boot with Vol UP + Power until you land on the bootloader page (don't navigate to Fastboot from the bootloader menu, just stay on the bootloader menu. Doing 'fastboot reboot bootloader' should also do the trick but suggest trying with the physical buttons.