Develop Bugs

AT&T Note 5 Oem Unlock in Dev Settings

I don't normally post in the forums however I figured this may be important.
Lets hope that this time we may be able to get our bootloaders 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"
}

Saw same, subscribed to thread!
Searching for the exact phrase, not much out there I found other than a G4 question regarding the same...

Copied and pasted this from a source I found..
For those new to “OEM unlock,” just know that this is a part of the command used to unlock a Nexus phone’s bootloader. After installing the Android SDK, plugging your phone into a computer, opening adb, and rebooting to the bootloader, a simple command in adb of “fastboot oem unlock” will start the process of phone freedom.

It's a command used in fastboot unfortunately samsung phones don't have a fastboot they have a recovery that you can use adb in and they have odin mode that as far as I can tell fastboot doesn't work in. So I am unsure of how we would test this.
Sent from my SAMSUNG-SM-N920A using Tapatalk

My understanding is that this is hard built into the developer mode, so stock vanilla Google phones like nexus and I'm guessing probably the moto lines are the only phones for which this will work. Basically, you're telling the phone whether to ignore the command altogether or to actually execute the command when it's toggled on. Think of this like the following: oem unlock toggle : permit execution of 'oem unlock' command :: USB enabled toggle :: being able to use the adb command
As @51ngular1ty said above, Sam phones have a completely different recovery architecture, so they respond to different commands/software.

51ngular1ty said:
It's a command used in fastboot unfortunately samsung phones don't have a fastboot they have a recovery that you can use adb in and they have odin mode that as far as I can tell fastboot doesn't work in. So I am unsure of how we would test this.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
Fastboot is a commandline tool used through adb. You plug you phone in while its on and you can use adb commands but you have yo enable it in the dev settings

unable to install or launch TWRP

Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"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"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma

Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.

Facing the same issue. Tried everything but no success.

No Partition on my phone??? (Is it my phone bricked?)

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!

Question POCO F4 - system has been destroyed - it's dificult

I am using a Poco F4 5G device.
The problem started when I tried to partition my device to install Windows 11. I followed the tutorial on https://renegade-project.tech/en/install, and at first, everything seemed to be going smoothly. The problem arose when I attempted to partition the device. There were some explanations that I did not read carefully because I was feeling very sleepy. In the first explanation, I clicked "Ignore," and in the second explanation, I clicked "Cancel."
{
"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"
}
After I rebooted the system, I received an error message that said "System has been destroyed." Initially, I did not panic because I was used to dealing with such problems. However, after trying several methods that I usually use, none of them worked:
Installing a new TWRP
Using VB Meta
Flashing using PowerShell
Flashing using Mi Flash
when i try boot via twrp again :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img target reported max download size of 805306368 bytes sending 'recovery' (196608 KB)... OKAY [ 7.306s] writing 'recovery'... FAILED (remote: Flashing is not allowed in Lock State) finished. total time: 7.317s
Perhaps someone here has experienced the same problem and can provide some guidance.

ok so the problem is being generated because you haven't unlocked you bootloader, it's locked
you have to unlock it first

maybe your phone's bl got locked while u were installing miui, if it was unlocked earlier

Ok so, i looked into it, the brick happend cause the project you tried installing on poco f4 was made for poco f1

No, I had already unlocked it before I did it."

muzadidil said:
No, I had already unlocked it before I did it."
Click to expand...
Click to collapse
Your SOC Qualcomm Snapdragon 870 Chipset is not supported by this project.
The bootloader was locked following your unsuccessful tests.

Question How to relock bootloader on Oneplus 11 CPH2447

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