Hello, can anyone share a complete proper tested process to relock Oneplus 11 bootloader after updating to OOS 13.1
Aka9413 said:
Hello, can anyone share a complete proper tested process to relock Oneplus 11 bootloader after updating to
Click to expand...
Click to collapse
Hi, check out this tutorial.
Aka9413 said:
Hello, can anyone share a complete proper tested process to relock Oneplus 11 bootloader after updating to OOS 13.1
Click to expand...
Click to collapse
i have not done it, buts its probably 'fastboot flashing lock' without the quotes
Also, it will wipe your data
kevp75 said:
i have not done it, buts its probably 'fastboot flashing lock' without the quotes
Also, it will wipe your data
Click to expand...
Click to collapse
Locking or Unlocking your bootloader will always format your device.
I just tried to do "fastboot oem lock" and it failed.
FAILED (remote: unknown command)
finished. total time: 0.002s
If someone has successfully done it, let me know.
maamdroid said:
I just tried to do "fastboot oem lock" and it failed.
FAILED (remote: unknown command)
finished. total time: 0.002s
If someone has successfully done it, let me know.
Click to expand...
Click to collapse
try
fastboot flashing lock
kevp75 said:
try
fastboot flashing lock
Click to expand...
Click to collapse
That worked.
I wasn't on my main machine, so I also updated to make sure to have the latest fastboot. Just used the portable version from here: https://forum.xda-developers.com/t/tool-windows-adb-fastboot-february-2023.3944288/
I think my issue was I was on an old version of fastboot.
Edit: I fixed the below issue by doing a factory reset. I setup the phone after the first "lock" reset it does and I had the issue. After a factory reset from within android, all is working well.
I am though no longer able to set a screen lock. Any ideas other than flashing the beta?
Screen lock was already charged. Try again with the new screen lock.
{
"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"
}
maamdroid said:
That worked.
I wasn't on my main machine, so I also updated to make sure to have the latest fastboot. Just used the portable version from here: https://forum.xda-developers.com/t/tool-windows-adb-fastboot-february-2023.3944288/
I think my issue was I was on an old version of fastboot.
Edit: I fixed the below issue by doing a factory reset. I setup the phone after the first "lock" reset it does and I had the issue. After a factory reset from within android, all is working well.
I am though no longer able to set a screen lock. Any ideas other than flashing the beta?
Screen lock was already charged. Try again with the new screen lock.
View attachment 5922405
Click to expand...
Click to collapse
I personally havent seen that, however, there are some threads here that address it... basically to fix, you have to disable... reunlock ... disable... relock... disable
Related
{
"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"
}
Has anyone seen this message? I can't get out of fastboot !
t3n0r10 said:
View attachment 5445229Has anyone seen this message? I can't get out of fastboot !
Click to expand...
Click to collapse
Looks something you’d get when you have no boot image flashed. Which is why you keep going back to fastboot. What happens when you fastboot flash the kernel?
freebee269 said:
Looks something you’d get when you have no boot image flashed. Which is why you keep going back to fastboot. What happens when you fastboot flash the kernel?
Click to expand...
Click to collapse
Weird though. This is my wife's phone. So I'm sure she hasn't tried to flash anything. She woke up this morning to a dead phone and charged it, after trying to turn it on she got this screen.
t3n0r10 said:
Weird though. This is my wife's phone. So I'm sure she hasn't tried to flash anything. She woke up this morning to a dead phone and charged it, after trying to turn it on she got this screen.
Click to expand...
Click to collapse
Have you already fixed it?
Official Google Pixel Update and Software Repair
or
SDK Platform Tools
Pixel 6 Pro Factory Images
roirraW edor ehT said:
Have you already fixed it?
Official Google Pixel Update and Software Repair
or
SDK Platform Tools
Pixel 6 Pro Factory Images
Click to expand...
Click to collapse
Not yet, both google's and manual way give me the same message:
FAILED (remote: 'failed to get lock state -1')
t3n0r10 said:
Not yet, both google's and manual way give me the same message:
FAILED (remote: 'failed to get lock state -1')
Click to expand...
Click to collapse
It's means that OEM Unlock toggle it's disabled under developer option.
Polishow said:
It's means that OEM Unlock toggle it's disabled under developer option.
Click to expand...
Click to collapse
Those toggles are either 0 or 1 right? Not -1
Anyways I can't get to the Settings menu. I'm stuck in fastboot. Tried running the unlock commands but the same error
After trying different things ended up calling at&t and they're sending a replacement.
Hi, recently i flash the stock rom for my Nokia 6.1 but when i finished and rebooting i got reboot to download mode and i tried to force shutdown and reboot it goes to same result. And i check the current slot and i get this:
Code:
fastboot getvar current-slot
current-slot:
finished. total time: 0.004s
Now i switch slot but when i switch both it both get error. So how can i fix this, is it my phone bricked? Thanks.
alprtewwqfr said:
Hi, recently i flash the stock rom for my Nokia 6.1 but when i finished and rebooting i got reboot to download mode and i tried to force shutdown and reboot it goes to same result. And i check the current slot and i get this:
Code:
fastboot getvar current-slot
current-slot:
finished. total time: 0.004s
Now i switch slot but when i switch both it both get error. So how can i fix this, is it my phone bricked? Thanks.
Click to expand...
Click to collapse
You have unlocked bootloader ? If not unlock it and fix your mobile. Search Google " Nokia bootloader unlock" unlock the bootloader and then flash the firmware or any other custom rom
I use techmesto free unlock bootloader but i get unknown bootloader type
zuhaibsarwar said:
You have unlocked bootloader ? If not unlock it and fix your mobile. Search Google " Nokia bootloader unlock" unlock the bootloader and then flash the firmware or any other custom rom
Click to expand...
Click to collapse
alprtewwqfr said:
I use techmesto free unlock bootloader but i get cannot flash bootloader images
Click to expand...
Click to collapse
why not . do you have telegram etc ?
windows3600pro said:
why not . do you have telegram etc ?
Click to expand...
Click to collapse
Yes i have Telegram
Note: if you guys wondering what's going on here is my cmd of "fastboot getvar all":
{
"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"
}
As you guys can see i didn't have any partition type and size and idk what to do.
alprtewwqfr said:
Note: if you guys wondering what's going on here is my cmd of "fastboot getvar all":
View attachment 5578615
As you guys can see i didn't have any partition type and size and idk what to do.
Click to expand...
Click to collapse
Download partition resizer of Raghu varma for Nokia 6.1 and Nokia 6.1 Plus and repartition partitions
zuhaibsarwar said:
Download partition resizer of Raghu varma for Nokia 6.1 and Nokia 6.1 Plus and repartition partitions
Click to expand...
Click to collapse
No it need an unlocked bootloader but i have a locked bootloader!
Good morning all.
I've a problem during the flashing of TWRP.img
- adb-Driver installed
- Mi A2 lite booted into fastboot
- computer and phone can't connect
- phone aborted the fastboot mode after some minutes
Phone Mi A2 lite latest Stock ROM
Computer windows 11 pro
Code:
C:\Users\Username>fastboot boot "D:\Username\Downloads\twrp-3.5.2_9-2-daisy-unofficial.img"
downloading 'boot.img'...
OKAY [ 0.643s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.665s
Have you enabled bootloader unlocking in developer options?
Tech0308 said:
Have you enabled bootloader unlocking in developer options?
Click to expand...
Click to collapse
OEM Unlock
(Allow bootloader unlock)
yes, i did
{
"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"
}
And then run fastboot flashing unlock?
It'll erase your data unless you keep volume down button held while running this command
Tech0308 said:
And then run fastboot flashing unlock?
It'll erase your data unless you keep volume down button held while running this command
Click to expand...
Click to collapse
this command doesn't work, i'll get the output of all aviable commands, that's all
Ahh sorry I meant fastboot oem unlock here's the link to a guide, use the first half for what you want, the instructions are valid and still work
Thread '[GUIDE] How to enable Camera2 API persistently and keep bootloader locked' https://forum.xda-developers.com/t/guide-how-to-enable-camera2-api-persistently-and-keep-bootloader-locked.3851414/
Tech0308 said:
Ahh sorry I meant fastboot oem unlock here's the link to a guide, use the first half for what you want, the instructions are valid and still work
Thread '[GUIDE] How to enable Camera2 API persistently and keep bootloader locked' https://forum.xda-developers.com/t/guide-how-to-enable-camera2-api-persistently-and-keep-bootloader-locked.3851414/
Click to expand...
Click to collapse
thank you, that's it
Sooo, some people (like me ) tried to downgrade their Moto G30 to android 11, ok, but, when the bootloader get locked, the problems start
My device is on an bootloop, "no valid operating system coud be found.", I've tried stock a11/12 through LMSA and fastboot, TinyFastboot, even Blankflash, none of these methods worked, I can put the device on EDL mode, go to fastboot, and just this, can't even go to recovery mode after bl locked what can I do to solve this? help pls
{
"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"
}
better restore firmware i think it is having issues with firmware
skntechnology said:
better restore firmware i think it is having issues with firmware
Click to expand...
Click to collapse
tried this, but LMSA stops at 50% and fastboot says Permission denied
did you try unlocking bootloader before? since obviously locked bootloader won't let you flash images until it's unlocked
jan6 said:
did you try unlocking bootloader before? since obviously locked bootloader won't let you flash images until it's unlocked
Click to expand...
Click to collapse
yep, flashed stocl a11 with unlocked bootloader, then i locked to sell it
raphable said:
yep, flashed stocl a11 with unlocked bootloader, then i locked to sell it
Click to expand...
Click to collapse
I meant, did you unlock before the permission denied ones:
raphable said:
tried this, but LMSA stops at 50% and fastboot says Permission denied
View attachment 5584949
Click to expand...
Click to collapse
The bootloader locked?, If so, the phone is totally dead. I'm sorry to say this, I tried many ways to fix it, but none worked.
If you manage to repair the Hard Brick create another thread, it will be very useful for other people.
raphable said:
Sooo, some people (like me ) tried to downgrade their Moto G30 to android 11, ok, but, when the bootloader get locked, the problems start
My device is on an bootloop, "no valid operating system coud be found.", I've tried stock a11/12 through LMSA and fastboot, TinyFastboot, even Blankflash, none of these methods worked, I can put the device on EDL mode, go to fastboot, and just this, can't even go to recovery mode after bl locked what can I do to solve this? help pls
View attachment 5584943
Click to expand...
Click to collapse
do you found any solution,?
Has anyone heard anything abt this cause i just downgraded mine to a11 cause i had had enough of the oversaturated colours. so i cam on here to check for custom roms and nthn was here and do i saw this thread and luckily cause i was abt to lock the bootloader.
is there any fix to this please help i am stuck with same error for motorola g32
Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"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"
}
You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk
So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse