I have a Redmi Note 3 (INDIAN VARIANT Kenzo/Snapdragon variant running on Marshmellow 6.0.1 with MIUI Global 10.2) on which I performed an bootloader unlocking procedure via the tool XiaoMiTool V2 from xdahttps://forum.xda-developers.com/android/software-hacking/tool-miunlocktool-unlock-bootloader-t3782444 since the official method kept denying me for some reason
I also want to let you know that during the procedure i left the oem unlocking option disabled (off) and ran the tool
So after the device's bootloader was unlocked (ss attached)
{
"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 noticed that the OEM unlocking option was still active (meaning I can flip the button and it will just ask for the pass and warn me and enable the option: again ss attached)
Isn't supposed to grayed out ?
So my question is is my device properly unlocked? OR Did I mess up with procedure ? I know i could dial *#*#7378423#*#* (which doesn't work in miui devices) or using fastboot method mentioned here https://android.stackexchange.com/questions/73567/how-to-check-if-your-bootloader-is-unlocked and i got like
What does this mean ?
Any help is highly appreciated and thank you in advance
Once you enable the OEM unlocking in Developer options, in Android's system file build.prop the unlock ability flag is set to 1, what basically is requirement to start the bootloader-unlock procedure, what typically is carried out via Fastboot.
Typically you run
Code:
fastboot OEM get-bootinfo
to check if the bootloader is unlocked.
jwoegerbauer said:
Once you enable the OEM unlocking in Developer options, in Android's system file build.prop the unlock ability flag is set to 1, what basically is requirement to start the bootloader-unlock procedure, what typically is carried out via Fastboot.
Typically you run
Code:
fastboot OEM get-bootinfo
to check if the bootloader is unlocked.
Click to expand...
Click to collapse
Thank you for your prompt reply but i ran this command and it said incorrect command (meaning no such command)
monstervishnu said:
Thank you for your prompt reply but i ran this command and it said incorrect command (meaning no such command)
Click to expand...
Click to collapse
Implementations of Fastboot are different. Some subcommand may be supported, others not: that depends on OEM/Carrier.
Related
I've just purchased a Xperia X with FW 34.0.A.2.292 installed. I'd like to root thid device and found instructions on this thread . I've downloaded the kernel file, successfully installed all required ADB Drivers from here and followed the instructions. Unfortunately i allways get the following error message:
{
"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"
}
[/url][/IMG]
I've also tried to use flashtool but get the same error message in flashtool.
Any ideas how to proceed?
allow OEM unlock option under development options
Thanks, i have no OEM unlock option allowed, still getting the same error message. Does this require an unlocked bootloader?
Mr.Ash said:
Thanks, i have no OEM unlock option allowed, still getting the same error message. Does this require an unlocked bootloader?
Click to expand...
Click to collapse
yes it does
Ah OK. What's the best way to backup the Xperia DRM keys before unlocking the bootloader, and how to restore them afterwards?
it's currently not possible to backup DRM-keys so you will lose them. there are kernels with DRM-fix which will restore the lost functions after unlocking
i got a problem, checked OEM unlock, deactive my xperia function, but bootloader status still "not allow", idk but when i deactive "my xperia" its not need to use my google account(not like my other Z4), i thing cause of its so bootloader cant be turned : yes
Lavievn said:
i got a problem, checked OEM unlock, deactive my xperia function, but bootloader status still "not allow", idk but when i deactive "my xperia" its not need to use my google account(not like my other Z4), i thing cause of its so bootloader cant be turned : yes
Click to expand...
Click to collapse
Did you buy your Xperia sim-unlocked? If not, it probably comes locked by carrier and this won't let you to unlock the bootloader.
Hello.
How are you?
I have a phone Redmi 4x and I planned to root it. So after I purchased it , I checked if the bootloader is unlocked with two methods, from pc and from Setting menu and at both places , it seem unlocked.
I saw the device has no recovery mode installed.
So can someone please confirm if the bootloader is unlocked or no?
If you can't access recovery, that does not mean your bootloader is locked, they're 2 different partitions.
In fastboot, do "fastboot oem unlock" and see what that tells you.
alnix said:
Hello.
How are you?
I have a phone Redmi 4x and I planned to root it. So after I purchased it , I checked if the bootloader is unlocked with two methods, from pc and from Setting menu and at both places , it seem unlocked.
I saw the device has no recovery mode installed.
So can someone please confirm if the bootloader is unlocked or no?
Click to expand...
Click to collapse
Bootloader locked or not, recovery mode is always accessible. If you can't nail the button combination, use a method that will always word - adb
open adb
type:
Code:
adb devices
confirms your phone drivers are installed.
Code:
adb reboot recovery
you ll boot to recovery. If you can't see anything means stock recovery doesnt have an interface. Then just flash another recovery.
To check bootloader:
Code:
fastboot oem device-info
To unlock bootloader :
Code:
fastboot oem unlock
reboot:
Code:
fastboot reboot
to temporarily flash a recover.img :
Code:
fastboot boot "path/to/recovery.img"
Thats everything you need to solve your problem.
Hit thanks if it helped
ramiabouzahra said:
If you can't access recovery, that does not mean your bootloader is locked, they're 2 different partitions.
In fastboot, do "fastboot oem unlock" and see what that tells you.
Click to expand...
Click to collapse
What is it suppossed to tell when it is unlocked?
I have a photo of it but I do not know how to post it in here
alnix said:
What is it suppossed to tell when it is unlocked?
I have a photo of it but I do not know how to post it in here
Click to expand...
Click to collapse
upload it some where
then beside the post box , press `go advanced`
you must see a pic symbol in the toolbox
-Hope- said:
upload it some where
then beside the post box , press `go advanced`
you must see a pic symbol in the toolbox
Click to expand...
Click to collapse
I added it in here
{
"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"
}
alnix said:
I added it in here
Click to expand...
Click to collapse
Here the link https://photos.app.goo.gl/J2I4sKPYstkSLs3h2
https://photos.app.goo.gl/J2I4sKPYstkSLs3h2
alnix said:
Here the link https://photos.app.goo.gl/J2I4sKPYstkSLs3h2
Click to expand...
Click to collapse
Greetings, I own a tablet that has MT6592 Chipset. It has CPU (Cortex A7) and GPU(Mali-450).
It runs on kitkat 4.4.2. I want to flash a Custom ROM on it.
I have the Custom ROM File, but i am unable to unlock the bootloader to install TWRP(Easy TWRP maker).
Using ADB i tried to unlock the bootloader.
I typed in the command : fastboot oem unlock ,
Then i get a message on my screen saying, "Press Volume up to unlock (This will void warranty)"
When i do so, it shows a fail message.
Image 1:
{
"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"
}
So any help would be appreciable
PS: I tried consequently 5 times, still no hope.
Image 2:
Reyscode said:
Greetings, I own a tablet that has MT6592 Chipset. It has CPU (Cortex A7) and GPU(Mali-450).
It runs on kitkat 4.4.2. I want to flash a Custom ROM on it.
I have the Custom ROM File, but i am unable to unlock the bootloader to install TWRP(Easy TWRP maker).
Using ADB i tried to unlock the bootloader.
I typed in the command : fastboot oem unlock ,
Then i get a message on my screen saying, "Press Volume up to unlock (This will void warranty)"
When i do so, it shows a fail message.
Image 1:
So any help would be appreciable
PS: I tried consequently 5 times, still no hope.
Image 2:
Click to expand...
Click to collapse
Try fastboot OEM unlock-go and see if it works
Ashley david said:
Try fastboot OEM unlock-go and see if it works
Click to expand...
Click to collapse
I still get the same fail message. Please give me a another solution. I need to unlock the bootloader to install twrp and then flash Custom ROM
Reyscode said:
I still get the same fail message. Please give me a another solution. I need to unlock the bootloader to install twrp and then flash Custom ROM
Click to expand...
Click to collapse
I think you haven't installed correct fastboot drivers.
This "bug" is known at some MTK-devices. There are some solutions for a few devices, by using patched boot.img, but none for this. Did you find a solution yet?
Hello everyone,
well i bought a CAT S62Pro phone. I am trying to root it ... i am really frustrated now
what have i done ?
- i have latest OTA update - Android 11:
https://android.googleapis.com/packages/ota-api/package/38947871c996a7ed4c023b912f5de87bd416ad89.zip
- i installed it;
- unpacked payload.bin, Installed magisk and patched the boot.img...
Now i am stuck:
- OEM unlock is not present in dev. options menu (have not seen it in A10 either)
- fastoot oem unlock commands are not working. I am getting messeges like:
C:\Users\SzczeGr\Desktop\platform-tools>fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
- some system properties
[sys.oem_unlock_allowed]: [0]
[ro.oem_unlock_supported]: [1]
I can not flash stuff in EDL mode - i dont have proper FIrehose/sahara programmer.
I have some questions:
- does anybody have firehose/sahara and those .xml files to flash stuff in EDL mode ?
- does anybody know how to repack payload.bin and create OTA update package ? It may be the fastest way to root it. Step by step guide would be OK.
- how to edit/create firehose programmer ? is it possible ?
- does anybody have an idea how to unlock bootloader ???? Stack overflow, firehose or hack or something ?
Any help would be cool.
Thank you in advance....
This needs more attention, Phone is crippled with dog**** software and UI choices. So much potential wasted its a real shame.
FU cat
maybe one of these firehose programmers work, so you can unlock
https://github.com/bkerler/Loaders/tree/main/qualcomm/factory/sdm660
if your firmware is :
Cat/S62Pro/S62Pro:11/RKQ1.210406.002/1.014.01
boot and recovery are here :
cat s62pro boot recovery.zip
{
"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"
}
drive.google.com
If you have the "Allow OEM unlock" toggle in developer options, switch it on, then
adb reboot fastboot
Click to expand...
Click to collapse
Bootloader unlock is achieved with
fastboot flashing unlock
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Follow instructions on the phone to unlock bootloader.... After reboot, and until you run the bootloader lock command, you will get a warning that the bootloader is unlocked and data on the device can't be verified at power on, before boot logo...
This is where I'm stuck... I have the latest firmware on S62(not Pro) and I can't find a means to get boot.img to patch and flash. There isn't a loader for edl, fastboot is only for writing to, not read back of partitions, and I can't find the OTA update .zip with a payload.bin to extract the boot.img from... If anyone can help it would be greatly appreciated
Some helpful info
Model HW version
Cat S62 Q190_V1
SW version
LTE S02111.11_N_S62_1.009.04
Android version
11
Build number
LTE S02111.11_N_S62 1.009.04
Any updates?
Geek8066 said:
Any updates?
Click to expand...
Click to collapse
Nein
I need a way to unlock the bootloader tab11 blacview I have tried all the commands for fastboot oem unlock and fastboot flashing unlock and all of them failed I need help to unlock the bootloader and root
{
"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"
}
Use a computer with ADB
[TOOL][WINDOWS] ADB & Fastboot++ | February 2023
NFO: • Versions: Installer, Portable & ADBKit • Android Debug Bridge & Fastboot updated to latest v1.0.41 (Version 34.0.0-9570255, February 2023) Features: • Installation Folder chooseable (Installer) • Desktop & Start Menu Shortcuts (Installer)...
forum.xda-developers.com
joke19 said:
Use a computer with ADB
[TOOL][WINDOWS] ADB & Fastboot++ | February 2023
NFO: • Versions: Installer, Portable & ADBKit • Android Debug Bridge & Fastboot updated to latest v1.0.41 (Version 34.0.0-9570255, February 2023) Features: • Installation Folder chooseable (Installer) • Desktop & Start Menu Shortcuts (Installer)...
forum.xda-developers.com
Click to expand...
Click to collapse
The same problem did not work, it appears to me after writing the opening command, an unknown command
U enable OEM unlock over Developer options and usb debugging
joke19 said:
U enable OEM unlock over Developer options and usb debugging
Click to expand...
Click to collapse
Yes, of course, I activate the Allow unlock bootloader and flash usb errors
joke19 said:
U enable OEM unlock over Developer options and usb debugging
Click to expand...
Click to collapse
I found this method, but the last step, when I understand it well, is where to get the vbmeta file from to flash it on the version of my device, especially as it is according to what its owner said that he tested it on the linux system and he has no idea if it works on Windows. If you know the vb.meta file, please let me know. What is his job and where did he get it?