Is it safe to lock my bootloader with these status?
{
"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"
}
I unlocked my bootloader to install PixelExperience, but after failing, getting stuck on fastboot, and flashing global stock rom I realized its not worth the hassle. I found a guide online which uses Minimal ADB and fastboot and typing fastboot oem lock on CMD, with the device info above, will i run in any problems?
Shoeless03 said:
Is it safe to lock my bootloader with these status?
View attachment 5311563
I unlocked my bootloader to install PixelExperience, but after failing, getting stuck on fastboot, and flashing global stock rom I realized its not worth the hassle. I found a guide online which uses Minimal ADB and fastboot and typing fastboot oem lock on CMD, with the device info above, will i run in any problems?
Click to expand...
Click to collapse
It depends if nothing more has changed in your device, if you have the same ROM which it came with or if you re-flash it the stock recovery I mean to re-lock bootloader all have to be as it came totally stock.
Shoeless03 said:
Is it safe to lock my bootloader with these status?
View attachment 5311563
I unlocked my bootloader to install PixelExperience, but after failing, getting stuck on fastboot, and flashing global stock rom I realized its not worth the hassle. I found a guide online which uses Minimal ADB and fastboot and typing fastboot oem lock on CMD, with the device info above, will i run in any problems?
Click to expand...
Click to collapse
As much as i know relocking can be easily done by flashing stock miui rom from mi flash tool just keep flash lock option and it will relock your bootloader and status that are present here won't affect anything while flashing.
Related
Hello,
So I'm trying to install the twrp recovery on the p7. adb is able to see my phone and I can use all the commands. With fastboot on the other hand I cant flash images on there. I can use the fastboot reboot command but I cant use the fastboot flash command. Also when I try using fastboot devices I get a question mark.
{
"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"
}
Thanks in advance,
stoutrouge
stoutrouge said:
Hello,
So I'm trying to install the twrp recovery on the p7. adb is able to see my phone and I can use all the commands. With fastboot on the other hand I cant flash images on there. I can use the fastboot reboot command but I cant use the fastboot flash command. Also when I try using fastboot devices I get a question mark.
Thanks in advance,
stoutrouge
Click to expand...
Click to collapse
Root the phone again. hw suite uninstall the program and reinstall it.
I had the same thing yesterday.
Bootloader unlocked?
I dont think thats root is the Problem. In fastboot mode, root it doesent metter
87insane said:
Bootloader unlocked?
I dont think thats root is the Problem. In fastboot mode, root it doesent metter
Click to expand...
Click to collapse
Yes, it could be bootloader problem. As I can see you have rom version 126 and AFAIK bootloader was unlocked by default from rom 133.
Before the question comes ...
1. Update Rom to b133 with full Rom and local update or dload method.
2. Check your bootloader and if its unlocked (i think after update it is) flash twrp/cwm.......
Hi XDA,
So basically, I'm an idiot.
I unlocked bootloader, flashed a custom ROM, then relocked bootloader on the ROM. Now stuck in eternal looping.
This has locked the phone down to fastboot only. Can use the command line on fastboot to execute commands,
{
"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"
}
When you attempt to start, it just flashes the oneplus logo on and off over and over while vibrating:
I've tried these commands, permission denied on every one.
Cheers for any help.
As you've figured out by now, you can't run unsigned code like LineageOS with locked bootloader, only Oneplus signed code.
You will have to restore the phone with the Qualcomm tool, aka unbrick tool as found in that thread in this forum.
Skickat från min ONEPLUS A3003 via Tapatalk
Why did you try to lock the bootloader with a custom ROM installed? You can only lock the bootloader with the phone fully stock (stock ROM, recovery, etc.).
It seems you should research the meaning and purpose of the bootloader lock/unlock concept, before further messing with the phone.
redpoint73 said:
Why did you try to lock the bootloader with a custom ROM installed? You can only lock the bootloader with the phone fully stock (stock ROM, recovery, etc.).
It seems you should research the meaning and purpose of the bootloader lock/unlock concept, before further messing with the phone.
Click to expand...
Click to collapse
Thanks, I'm aware of this now. After bricking my phone.
Try this method
https://www.androidexplained.com/oneplus-3-unbrick-return-stock/
have you tried to install the Stock recovery (link: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3t.img ) via fastboot?
Code:
fastboot flash recovery [reco.img]
From stock recovery you can flash stock OxygenOS and restore your phone.
I don't know if you can flash recovery with locked bootloader, but give it a chanche, just to try.
Hello, I made a mistake on closing my oem unlocked with the rooted rog 3 android 12 and now i have entered CSC Fastboot mode
{
"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"
}
I have tried things like doing this method where I have to flash the Raw rom but it didnt work because I keep on getting this
I have also triedusing the unbrick/bricked method but whenever I open the edl cmd, it keeps on closing.
I have also tried these 3 cmd fastboot commands but it didnt work
I have also tried flashing these 3 image file, (boot, recovery, and dtbo) from the unbrick/ brick xda but i keep on getting this
I have tried thses methods but it didnt work or I dont know the commands. Pls, I need help
You will be in CSC FB mode only, as long as your bootloader is locked. Unlocking your bootloader again will bring you back in the right Fastboot mode. EDL mode should work however, don't know why you have trouble with it...
Andrologic said:
You will be in CSC FB mode only, as long as your bootloader is locked. Unlocking your bootloader again will bring you back in the right Fastboot mode. EDL mode should work however, don't know why you have trouble with it...
Click to expand...
Click to collapse
hello, i did all the proccedure to get out of csc fastboot but after I used the flashall.bat, it installed the qssi.userdebug.m1 rom and i cant get out because the rog unlock isnt working/compatible even though it is rog 3... pls help. many thanks
Hi guys, something is wrong with my bootloader i assume. I cant get in recovery or the system. Only in fastboot. The only way to get into PixelExperience is by giving the phone the command: fastboot continue. How can I reflash the bootloader? fastboot flashing unlock_critical is an unknown command btw
{
"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"
}
Larsos099 said:
Hi guys, something is wrong with my bootloader i assume. I cant get in recovery or the system. Only in fastboot. The only way to get into PixelExperience is by giving the phone the command: fastboot continue. How can I reflash the bootloader? fastboot flashing unlock_critical is an unknown command btw
View attachment 5883583
Click to expand...
Click to collapse
Try to flash stock ROM via miflash
Or if unlocked, in fastboot flash recovery and reboot to recovery. Then flash custom rom
Reinstall latest Xiaomi USB drivers into your Windows. That simple thing fixed an annoying blank response with "fastboot devices."
Larsos099 said:
Hi guys, something is wrong with my bootloader i assume. I cant get in recovery or the system. Only in fastboot. The only way to get into PixelExperience is by giving the phone the command: fastboot continue. How can I reflash the bootloader? fastboot flashing unlock_critical is an unknown command btw
View attachment 5883583
Click to expand...
Click to collapse
only possible with EDL
So I wanted to do a fresh install after experiencing some issues. But doing a factory reset in recovery mode didn't completely fix my issues because play store stated that my device wasn't certified. The state of my phone at that time was; unlocked bootloader, no root and developer options disabled. If having the bootloader unlocked makes the device not certified then thats news to me.
But I thought whatever, Ill root the phone. Using the boot extracted from payload.bin from the full ota with the same version and patched that in magisk. Booted using the patched image without flashing and patched the stock boot from magisk.
That resulted in a bootloop, flashing the stock boot didn't resolve the issue. Tried both slots. I then tried to flash the full firmware in fastboot/fastbootd and that resulted in fastbootd being not bootable anymore for the current slot. I then tried in the other slot to flash the firmware by resizing all logical partitions and that ofcourse resulted in that fastbootd is no longer accesible in any slot, recovery is unaccesible and fastboot restarts every 5s back to fastboot. As some sort of last measure I locked the bootloader again which didnt help and now I cant flash anything.
So now to the real issue. I know that EDL is my only solution now and I have gathered all the tools and firmware needed. I can boot it into EDL with some driver errors
{
"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"
}
The problem is that even in edl mode the phone reboots after 5s to fastboot.