I'm currently using this device: https://www.androidtv-guide.com/pay-tv-provider/myrepublic-stb/
Now I'm using Android 11 and wanna flash to latest firmware. But I'.stucking at step that need booloader unlocked, they showed the error like that:
{
"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"
}
Moreover, the USB Burning Tool for Amlogic chip did not detect my device before, I've tried connect many times but not success.
boylklk9515 said:
the USB Burning Tool for Amlogic chip did not detect my device before, I've tried connect many times but not success.
Click to expand...
Click to collapse
Note that a device running a newer SoC like the Amlogic S905Y4 will not have worldcup burn mode, so such a connection is not possible in any case.
boylklk9515 said:
wanna flash to latest firmware
Click to expand...
Click to collapse
What firmware do you intend to flash? You could easily brick the device by flashing incompatible firmware.
boylklk9515 said:
But I'.stucking at step that need booloader unlocked, they showed the error like that:
Click to expand...
Click to collapse
Your image above does not show what commands you are typing, and in what context.
There are multiple types of fastboot connections. Such as a userspace fastbootd connection, and a bootloader fastboot connection. There is another type of connection, adnl, that uses the android drivers, so it also can be mistaken for a fastboot connection when really it is not.
The image you posted is insufficient to determine what type of connection you had, and which commands you entered.
Functioner said:
Note that a device running a newer SoC like the Amlogic S905Y4 will not have worldcup burn mode, so such a connection is not possible in any case.
What firmware do you intend to flash? You could easily brick the device by flashing incompatible firmware.
Your image above does not show what commands you are typing, and in what context.
There are multiple types of fastboot connections. Such as a userspace fastbootd connection, and a bootloader fastboot connection. There is another type of connection, adnl, that uses the android drivers, so it also can be mistaken for a fastboot connection when really it is not.
The image you posted is insufficient to determine what type of connection you had, and which commands you entered.
Click to expand...
Click to collapse
thanks for your reply.
Functioner said:
Note that a device running a newer SoC like the Amlogic S905Y4 will not have worldcup burn mode, so such a connection is not possible in any case.
What firmware do you intend to flash? You could easily brick the device by flashing incompatible firmware.
Your image above does not show what commands you are typing, and in what context.
There are multiple types of fastboot connections. Such as a userspace fastbootd connection, and a bootloader fastboot connection. There is another type of connection, adnl, that uses the android drivers, so it also can be mistaken for a fastboot connection when really it is not.
The image you posted is insufficient to determine what type of connection you had, and which commands you entered.
Click to expand...
Click to collapse
thanks for your reply.
But what is "worldcup burn mode".
I've tried connect my device to the UBT, but unsuccessful, then I tried to connect to 'fastbootd' mode and used the adb command to unlock bootloader, and the result shown above.
boylklk9515 said:
But what is "worldcup burn mode".
Click to expand...
Click to collapse
When you said: "the USB Burning Tool for Amlogic chip did not detect my device before".
The type of connection that would have been used to connect to v2 of the "USB Burning Tool for Amlogic chip" would have been a worldcup burn mode connection. The Amlogic S905Y4 chip used in the SDMC DV9135 does not have the ability to make this type of connection.
boylklk9515 said:
I've tried connect my device to the UBT, but unsuccessful, then I tried to connect to 'fastbootd' mode and used the adb command to unlock bootloader, and the result shown above.
Click to expand...
Click to collapse
I'll assume that "UBT" means "USB".
The bootloader cannot be unlocked in fastbootd mode.
It only can be unlocked in bootloader fastboot mode. This mode can be accessed by selecting the "reboot to bootloader" option in the recovery menu. Or, by typing "adb reboot bootloader" from a booted system with adb shell access.
Again, be careful in what firmware you choose to flash to this device. You can easily brick the device if you flash third party firmware. Only versions of the original factory firmware should be used.
Functioner said:
When you said: "the USB Burning Tool for Amlogic chip did not detect my device before".
The type of connection that would have been used to connect to v2 of the "USB Burning Tool for Amlogic chip" would have been a worldcup burn mode connection. The Amlogic S905Y4 chip used in the SDMC DV9135 does not have the ability to make this type of connection.
I'll assume that "UBT" means "USB".
The bootloader cannot be unlocked in fastbootd mode.
It only can be unlocked in bootloader fastboot mode. This mode can be accessed by selecting the "reboot to bootloader" option in the recovery menu. Or, by typing "adb reboot bootloader" from a booted system with adb shell access.
Again, be careful in what firmware you choose to flash to this device. You can easily brick the device if you flash third party firmware. Only versions of the original factory firmware should be used.
Click to expand...
Click to collapse
Thanks, let me try later and feedback you soon.
Do you use whatapps/telegram, can I have your number?
boylklk9515 said:
Do you use whatapps/telegram
Click to expand...
Click to collapse
No, I don't use either of those. I'd rather go down in a plane crash than use those apps.
Functioner said:
There is another type of connection, adnl, that uses the android drivers, so it also can be mistaken for a fastboot connection when really it is not.
Click to expand...
Click to collapse
Do you know any way to enter adnl mode?
Functioner said:
No, I don't use either of those. I'd rather go down in a plane crash than use those apps.
Click to expand...
Click to collapse
Here are some commands that I used on adb to unlock the bootloader
Microsoft Windows [Version 10.0.22000.2057]
(c) Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\adb
C:\adb>fastboot devices
SDMC25112200092660 fastboot
C:\adb>fastboot flashing unlock
...
FAILED (remote: locked device)
finished. total time: 0.003s
C:\adb>fastboot oem unlock
...
FAILED (remote: secure boot device)
finished. total time: 0.004s
C:\adb>
The are two FAILED (in bold lines), said that my device is not accepted to unlock bootloader
My I try unlock bootloader by flashing other "boot.img" ?
boylklk9515 said:
Here are some commands that I used on adb to unlock the bootloader
C:\adb>fastboot devices
SDMC25112200092660 fastboot
Click to expand...
Click to collapse
Enter the fastboot command:
fastboot getvar all
and report what it shows
boylklk9515 said:
My I try unlock bootloader by flashing other "boot.img" ?
Click to expand...
Click to collapse
No. If you somehow manage to install a modified boot partition with the bootloader still locked, the device won't boot at all, and might be more difficult to recover.
Functioner said:
Enter the fastboot command:
fastboot getvar all
and report what it shows
No. If you somehow manage to install a modified boot partition with the bootloader still locked, the device won't boot at all, and might be more difficult to recover.
Click to expand...
Click to collapse
Here are the result
It looks like you are in fastbootD, not the bootloader version of fastboot.
to check, enter the fastboot command:
fastboot reboot bootloader
wait for the device to reboot and connect to fastboot again, and then enter the fastboot command:
fastboot getvar all
(again), and report if the output is any different than what you posted before
Functioner said:
It looks like you are in fastbootD, not the bootloader version of fastboot.
to check, enter the fastboot command:
fastboot reboot bootloader
wait for the device to reboot and connect to fastboot again, and then enter the fastboot command:
fastboot getvar all
(again), and report if the output is any different than what you posted before
Click to expand...
Click to collapse
here is the result like this
further result which the following commands
Code:
fastboot oem unlock
fastboot flashing unlock
boylklk9515 said:
further result which the following commands
Code:
fastboot oem unlock
fastboot flashing unlock
View attachment 5937145
Click to expand...
Click to collapse
The commands you tried usually work.
SDMC must have changed their bootloader some for this particular DV9135 model, since it is an operator tier model.
It's interesting that you have the folder structure:
\DV9135\DV9135_ATV11_RELEASE
on your windows pc.
Do you have the firmware extracted in the "DV9135_ATV11_RELEASE" folder?
Functioner said:
The commands you tried usually work.
SDMC must have changed their bootloader some for this particular DV9135 model, since it is an operator tier model.
It's interesting that you have the folder structure:
\DV9135\DV9135_ATV11_RELEASE
on your windows pc.
Do you have the firmware extracted in the "DV9135_ATV11_RELEASE" folder?
Click to expand...
Click to collapse
Shared by my friend, but what exactly happened with my device?
What can I do next to unlock the bootloader?
boylklk9515 said:
Shared by my friend
Click to expand...
Click to collapse
Exactly what was shared by your friend. Be precise.
boylklk9515 said:
but what exactly happened with my device?
What can I do next to unlock the bootloader?
Click to expand...
Click to collapse
If you have a copy of the firmware, it would go a long way in understanding what is going on.
Based on what you've posted, the bootloader restricts "oem" commands in fastboot based on the secureboot fuse setting.
And the unlock ability flag is 0, which is why "flashing unlock" doesn't work in fastboot.
You can check the value of the unlock ability setting:
fastboot flashing get_unlock_ability
(be sure to run this fastboot command in the bootloader version of fastboot, not fastbootD)
The result might be something like this:
(bootloader) get_unlock_ability: 0
Functioner said:
Exactly what was shared by your friend. Be precise.
If you have a copy of the firmware, it would go a long way in understanding what is going on.
Based on what you've posted, the bootloader restricts "oem" commands in fastboot based on the secureboot fuse setting.
And the unlock ability flag is 0, which is why "flashing unlock" doesn't work in fastboot.
You can check the value of the unlock ability setting:
fastboot flashing get_unlock_ability
(be sure to run this fastboot command in the bootloader version of fastboot, not fastbootD)
The result might be something like this:
(bootloader) get_unlock_ability: 0
Click to expand...
Click to collapse
I've tried and the result was:
so, my device was locked on fastboot mode and can not do anything
I've read something about ARM by this article: https://review.trustedfirmware.org/...329cabdd6e75c78e81f4e/docs/firmware-design.md
and it said :
Code:
The cold boot path in this implementation of the ARM Trusted Firmware is divided into five steps (in order of execution):
Boot Loader stage 1 (BL1) AP Trusted ROM
Boot Loader stage 2 (BL2) Trusted Boot Firmware
Boot Loader stage 3-1 (BL3-1) EL3 Runtime Firmware
Boot Loader stage 3-2 (BL3-2) Secure-EL1 Payload (optional)
Boot Loader stage 3-3 (BL3-3) Non-trusted Firmware
So, may it have anyway to replace thee "boot.img" and "bootloader.img" on the device to unlock the bootloader?
Do you use telegram?
You've ignored my question about exactly what was shared by "your friend" and whether or not you (or your friend) have a copy of the firmware in that "DV9135_ATV11_RELEASE" folder. I won't reply to this thread anymore if you don't answer these questions.
As I said before, 'android verified boot' (avb) checks the contents of the partition that contains "boot.img".
If you do what you describe as "replace thee "boot.img" with a copy that fails verification (while the device is still locked), it won't boot.
The bootloader is most certainly encrypted. It is unlikely that you could ever find what you describe as "bootloader.img" that could ever even boot on this device.
Flashing a bootloader that won't start results in a bricked device.
Functioner said:
You've ignored my question about exactly what was shared by "your friend" and whether or not you (or your friend) have a copy of the firmware in that "DV9135_ATV11_RELEASE" folder. I won't reply to this thread anymore if you don't answer these questions.
As I said before, 'android verified boot' (avb) checks the contents of the partition that contains "boot.img".
If you do what you describe as "replace thee "boot.img" with a copy that fails verification (while the device is still locked), it won't boot.
The bootloader is most certainly encrypted. It is unlikely that you could ever find what you describe as "bootloader.img" that could ever even boot on this device.
Flashing a bootloader that won't start results in a bricked device.
Click to expand...
Click to collapse
that is the folder has the firmware tool of dv9135, but nothing can be done if the bootloader in not unlocked. And exactly its mine.
Do you have the firmware extracted in the "DV9135_ATV11_RELEASE" folder?
Click to expand...
Click to collapse
Yes, I have
Related
C:\Android\sdk\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.053s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.076s
C:\Android\sdk\platform-tools>fastboot flashing unlock ...
(bootloader) Device already : unlocked!
OKAY [ 0.012s]
finished. total time: 0.013s
I have both oem unlock and usb debugging checked on the developer options plus i was able to unlock the devices oem through fastboot. I opened the command prompt in androids/sdk/platform tools but nothing happens just repeats recovery failed. What am I doing wrong? (My goal is to download twrp onto my lg V10)
I am having the same problem and it's driving me nuts. Any solution yet?
Which device are you on? lg has locked the fastboot commands. Until we have root you can't flash recovery. That's if installed the official ota marshmallow(6.0.1) from your carrier you lose root and you CANNOT downgrade doing so will BRICK!! your device because there is no (5.1) lollipop kdz for our device . So therefore we are stuck until the developers find a way to root it. So Be patient...
Sent from my LG-H901 using XDA-Developers mobile app
DAMN sent my v10 to lg for repair and got it back with official 6.0 on it. i'm getting the same remote unknown command error when using fastboot. Hopefully a fix soon!
I'm on the official 6.0 - not 6.0.1 referenced above. Any chance I can root? Screenshot shows my software info
{
"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"
}
Sent from my LG-H901 using XDA Free mobile app
Same here. Any Solution? Also i read we can get FM Radio in h901. Is that possible? Please let me know. Thanks
Hi,
-Atlas__ said:
I have both oem unlock and usb debugging checked on the developer options plus i was able to unlock the devices oem through fastboot. I opened the command prompt in androids/sdk/platform tools but nothing happens just repeats recovery failed. What am I doing wrong? (My goal is to download twrp onto my lg V10)
Click to expand...
Click to collapse
disabling the "OEM unlock" option will probably solve your problem. It is only needed to unlock the bootloader and can be disabled afterwards. This did the trick for me.
you need to unlock the bootloader
this is what i did to get past it on my brand new tmobile v10 (H901)
if not in the bootloader pass the command
Code:
adb reboot bootloader
now pass
Code:
fastboot oem unlock
now continue to install twrp
you may need to use [/code]fastboot boot {path to image}[/code]
then transfer the twrp img to the phone via mtp (use mounts >enable mtp to do the transfer) disable mtp when done
and then install it again inside twrp using the install image option, just make sure you install it to recovery and NOT BOOT as that is a 1 way trip to brick ville
Has there been any development on this issue? I just picked up a refurb H901 with MM on it, and I get the same error.
I was able to unlock the bootloader, but I can't boot to the TWRP image (fastboot boot twrp.img), nor can I flash the recovery img to recovery from the stock (unlocked) bootloader (fastboot flash recovery twrp.img).
Thanks! I'm on H90120j
Seconded, I have bootloader unlock but get the same error message when flashing TWRP. Going to try Hünstetten suggestion.
No luck after disabling OEM Unlock and retrying, still get the failed message.
Alright guys i figured it out. Use the command "fastboot boot [recoveryfilename.img]"
then once in twrp, flash twrp again and flash super user. Thats how i solved my problem. Also make sure that the recovery files is in your internal storage as well as the adb file on your computer
remember to open the command prompt from inside the adb folder
plz sand pix on instal recovery,myh901 not instal recovery
krixxux said:
Alright guys i figured it out. Use the command "fastboot boot [recoveryfilename.img]"
then once in twrp, flash twrp again and flash super user. Thats how i solved my problem. Also make sure that the recovery files is in your internal storage as well as the adb file on your computer
remember to open the command prompt from inside the adb folder
Click to expand...
Click to collapse
I am also getting Failure with both boatloader commands. Is there an update to this fix, or additional info? Thank you.
dogfyter said:
I am also getting Failure with both boatloader commands. Is there an update to this fix, or additional info? Thank you.
Click to expand...
Click to collapse
install "Minimal ADB and Fastboot" - search here on the V10 forum or google, and then in V10 section here you find the TWRP for V10, download the zip and extract the img to Minimal ADB and Fastboot main folder.
Then you open Minimal ADB and with USB debbuging on and the phone connected type:
adb reboot bootloader
- hit enter
- wait till the phone ask your permission from adb, for this keep the screen on and check the box in that window, then it will enter bootloader
- when in bootloader type in Minimal ADB:
fastboot flash recovery twrp-3.0.2.0-0-h960a.img
- and you done (note the twrp-3.0.2.0-0-h960a.img is the file of my TWRP img and yours can be different but i assume you download it from V10 section here so it will be the same after extracting it.)
- to enter TWRP just take the battery out after done all commands and put back in, keep your finger in volume down and power at same time, when LG logo appears release and put the finger back in power button.
- then a window will show up to restore defaults - ignore this saying yes to both, use volume rocker and power to confirm twice asked.
and thats it... if you want help see this:
https://forum.xda-developers.com/lg-v10/development/recovery-twrp-v3-0-2-0-unofficial-t3387783
I appreciate the effort. After the "adb reboot bootloader" command I get the "error: no devices/emulators found" response.
Keep in my my phone does reboot after typing the "fastboot reboot" command. I also have usb debugging acknowledged in the MM OS whenever I plug the usb in.
So I proceeded to the next step "fastboot flash recovery twrp... img" anyway and I get the same "Failed... " msg.
I think my V10 days will be short lived.
dogfyter said:
I appreciate the effort. After the "adb reboot bootloader" command I get the "error: no devices/emulators found" response.
Keep in my my phone does reboot after typing the "fastboot reboot" command. I also have usb debugging acknowledged in the MM OS whenever I plug the usb in.
So I proceeded to the next step "fastboot flash recovery twrp... img" anyway and I get the same "Failed... " msg.
I think my V10 days will be short lived.
Click to expand...
Click to collapse
try: fastboot reboot-bootloader
with " - " between reboot and bootloader.
OR
with your phone powered off put the finger on volume down and then connect usb and they will be in fastboot mode, before that try the command above mentioned.
sun_is_shinning said:
try: fastboot reboot-bootloader
with " - " between reboot and bootloader.
OR
with your phone powered off put the finger on volume down and then connect usb and they will be in fastboot mode, before that try the command above mentioned.
Click to expand...
Click to collapse
Thanks again, Sun. I tried both and ways and got the same failure results. My amateur opinion is that when I installed LG Bridge on my PC (looking for drivers) it updated a tamper proof boot loader on my phone. But, who knows. Have a great day.
dogfyter said:
Thanks again, Sun. I tried both and ways and got the same failure results. My amateur opinion is that when I installed LG Bridge on my PC (looking for drivers) it updated a tamper proof boot loader on my phone. But, who knows. Have a great day.
Click to expand...
Click to collapse
i never read something like that about "tamper proof bootloader", you did some update in LG bridge?
- are u sure you have bootloader unlocked?! this is strange...i never saw something like your problem.
sun_is_shinning said:
i never read something like that about "tamper proof bootloader", you did some update in LG bridge?
- are u sure you have bootloader unlocked?! this is strange...i never saw something like your problem.
Click to expand...
Click to collapse
I just verified the bootloader is unlocked. Since I unlocked it the next boatloader menu only provides the two options for how to exit bootloader. There are no menu options for "quick guidance" (ie, flash, erase, or reboot).
All attempts end with "FAILED (remote: unknown command)".
I do not know what that means so, I can only guess. Thanks again tho.
late response
sun_is_shinning said:
i never read something like that about "tamper proof bootloader", you did some update in LG bridge?
- are u sure you have bootloader unlocked?! this is strange...i never saw something like your problem.
Click to expand...
Click to collapse
I figured out it had nothing to do with lg bridge. I was having driver issues with windows 8.1. So after trying to follow another to install android sdk I had issues with that not installing properly. The thread suggested re-configuring files I could not even find/did not install. So I just gave up and got a different phone. Thanks again for trying.
Hi
I recently upgraded a Honor 5c to Nougat(which works)NRD90M test keys build. I did this through Flashfire to try and preserve root. It failed(what a surprise).
The device is recognised now with 'fastboot devices', by running ADB using root in Linux.
I can get into bootloader screen using fastboot and have unlocked the phone AGAIN to be sure. BUT, cannot flash TWRP which is vital. The error now is:
Sending 'boot.img' (24464 KB) OKAY [ 0.869s]
Booting FAILED (remote: 'Command not allowed') fastboot: error: Command failed
This suggests the phone is locked which is absurd. I think this is a permission problem within Android, it that possible?
It doesn't matter how I'm going to root, if I can't communicate the whole thing is usesless.
The same issue continues with ADB in Win10
Any thoughts hear, because I've trawled Google.
thanks
To clarify things: ADB and Fastboot are 2 completly different things. Fastboot deals with device's bootloader, whereas ADB deals with device's Android OS.
Run this command sequence
Code:
fastboot devices
fastboot getvar all 2>%TEMP%\phoneinfo.txt
fastboot reboot
type "%TEMP%\phoneinfo.txt" | more
which will get you a list of various variables on the phone with model and such useful things.
jwoegerbauer said:
To clarify things: ADB and Fastboot are 2 completly different things. Fastboot deals with device's bootloader, whereas ADB deals with device's Android OS.
Run this command sequence
Code:
fastboot devices
fastboot getvar all 2>%TEMP%\phoneinfo.txt
fastboot reboot
type "%TEMP%\phoneinfo.txt" | more
which will get you a list of various variables on the phone with model and such useful things.
Click to expand...
Click to collapse
Excuse if this format is incorrect
Thanks for that.
ADB and Fastboot are 2 completly different things
Click to expand...
Click to collapse
Sure
fastboot devices
Click to expand...
Click to collapse
MQH4C17330000094 fastboot
fastboot getvar all 2>%TEMP%\phoneinfo.txt
Click to expand...
Click to collapse
Returns to prompt
fastboot reboot
Click to expand...
Click to collapse
Works
type "%TEMP%\phoneinfo.txt" | more
Click to expand...
Click to collapse
getvar:all FAILED (remote: 'Command not allowed')
Finished. Total time: 0.005s
Same thing again
Cliff
cliffhanger54 said:
getvar:all FAILED (remote: 'Command not allowed')
Click to expand...
Click to collapse
That a Fastboot cmd does not work ( e.g. error Command not allowed ) is not unusual because Fastboot is different from version to version and also depends on how OEM/Carrier implemented it.
Again:
Bootloader and Android OS are different things, as this is same on PC where UEFI/BIOS and Windows OS are different things, too. A device's bootloader doesn't depend on any permissions granted within device's OS. A bootloader is a kind of software that runs as soon as you start up your phone. It tells the phone which programs are loading in order to make your phone run smoothly. This software packages all the instructions that are supposed to boot the Android OS, and initializes hardware and serves as security checkpoint.
Don't mix things up.
BTW:
Whether device's bootloader is unlockable / is already unlocked or not is stored in system file named build.prop.
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then unlocking bootloader is supported otherwise it's not.
or
Code:
fastboot devices
fastboot oem device-info
If "Device unlocked: true" is shown then bootloader is unlockedd.
jwoegerbauer said:
That a Fastboot cmd does not work ( e.g. error Command not allowed ) is not unusual because Fastboot is different from version to version and also depends on how OEM/Carrier implemented it.
Again:
Bootloader and Android OS are different things, as this is same on PC where UEFI/BIOS and Windows OS are different things, too. A device's bootloader doesn't depend on any permissions granted within device's OS. A bootloader is a kind of software that runs as soon as you start up your phone. It tells the phone which programs are loading in order to make your phone run smoothly. This software packages all the instructions that are supposed to boot the Android OS, and initializes hardware and serves as security checkpoint.
Don't mix things up.
BTW:
Whether device's bootloader is unlockable / is already unlocked or not is stored in system file named build.prop.
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then unlocking bootloader is supported otherwise it's not.
or
Code:
fastboot devices
fastboot oem device-info
If "Device unlocked: true" is shown then bootloader is unlockedd.
Click to expand...
Click to collapse
Thanks again for answering. I understand what you say. I've used Linux for 20 years and understand the differences. But where does this leave us/me. I should be able to flash TWRP into the recovery partition surely? Or are we dependent on software versions here as you say? It would be relatively easy in Linux and of course Android is based on it.
cliffhanger54 said:
I should be able to flash TWRP into the recovery partition surely?
Click to expand...
Click to collapse
TWRP completely removes device's default /recovery partition if it exists ( exists only on A-only Android devices), TWRP creates its own in device's /boot partition.
To flash TWRP on A-only ( or on current active boot slot if it's an A/B ) device
Code:
fastboot devices
fastboot flash boot <PATH_ON_PC_TO_YOUR_TWRP_IMAGE_HERE>
jwoegerbauer said:
TWRP completely removes device's default /recovery partition if it exists ( exists only on A-only Android devices), TWRP creates its own in device's /boot partition.
To flash TWRP on A-only ( or on current active boot slot if it's an A/B ) device
Code:
fastboot devices
fastboot flash boot <PATH_ON_PC_TO_YOUR_TWRP_IMAGE_HERE>
Click to expand...
Click to collapse
Thanks I think I've tried this one. I do get a different response though:
'fastboot: error: cannot get boot partition size'
I've seen suggestions that formating the boot partition is required - sounds extreme.
Why not simply re-flash device's Stock ROM to restore it to its original state ?
:good:
Sukrus said:
:good:
Click to expand...
Click to collapse
Yes wouldn't that be great. Have tried that from the beginning when I couldn't flash TWRP.
Put the Update.app on the SDcard, reboot the phone, hold down the buttons(tried them all), Bingo, it always takes me to eRecovery and how useless that is.
I have backups of Marshmallow with TWRP and Flashfire, which is why I took the flash TWRP route.
Wish I'd never upgaded now, although was forced to because of banking.
thanks
@cliffhanger54
I have noticed that current thread basically is a duplicate of this thread you started on XDA some days ago, too.
jwoegerbauer said:
@cliffhanger54
I have noticed that current thread basically is a duplicate of this thread you started on XDA some days ago, too.
Click to expand...
Click to collapse
Yes, couldn't really get anyone to answer, needed more info. Apologies. Will cease other question
Cliff
cliffhanger54 said:
Yes, couldn't really get anyone to answer, needed more info. Apologies. Will cease other question
Cliff
Click to expand...
Click to collapse
Right. After many attempts at other things I became convinced this was a locked bootloader problem despite the phone saying it was unlocked. Anyway have persisted in unlocking the phone several times and am now at a screen saying 'Your device is unlocked' but it also says 'you device is booting now'. But that's as far as it goes. If I turn the phone off it comes back to this screen and holding the power button+-volume also comes back to this screen, i.e I can't turn it off. How do I get back to the bootloader/fastboot mode or is this a genuine brick?
thanks
Cliff
cliffhanger54 said:
Right. After many attempts at other things I became convinced this was a locked bootloader problem despite the phone saying it was unlocked. Anyway have persisted in unlocking the phone several times and am now at a screen saying 'Your device is unlocked' but it also says 'you device is booting now'. But that's as far as it goes. If I turn the phone off it comes back to this screen and holding the power button+-volume also comes back to this screen, i.e I can't turn it off. How do I get back to the bootloader/fastboot mode or is this a genuine brick?
thanks
Cliff
Click to expand...
Click to collapse
Okay finally solved it. Let the battery run down as all I was getting was a bootloop. I was then able to get into fastboot mode with the necessary keys. From here i flashed TWRP but this required numerous attempts with different versions, finally got '3.1.1 venus' to load and the rest was straight forward!
thanks to everyone
Hello I have a xiaomi mi mix 3 5g that I never removed the bootloader on, as it had the stock EU firmware on. It has recently been updated to to MIUI12. however the battery went low and went all weird and now constantly reboots.
I can get to fastboot by holding down the power and volume down, I have also tried a wipe device by holding down the power and up. From what I have read I i cant re-install fastboot firmware without and unlocked bootloader. (can someone confirm that this is correct) as its not clear.
***I have now confirmed this I have tried to install firmware using xiaomi flash tool and fails with the following
"Error: erasing boot Failed remote erase is not allowed in locked state. so this confirms it.
Also I cant unlock the bootloader as it wont boot. Does any body have any idea of what I can do with this phone? any help would be apprciated
thanks
The error I get when trying the mi unlock tool
Couldn't Unlock
Please add your account in MIUI;s Settings > Developer options > Mi Unlock Status
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
jwoegerbauer said:
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
Click to expand...
Click to collapse
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
sivhead said:
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
Click to expand...
Click to collapse
How to flash firmware to any Xiaomi smartphone is described here.
jwoegerbauer said:
How to flash firmware to any Xiaomi smartphone is described ["]here[/url].
Click to expand...
Click to collapse
I have already tried that method When I flash using the flash tool I get the error "Error: erasing boot Failed remote erase is not allowed in locked state" My bootloader is not unlocked is this method supposed to be work with a locked bootloader. Bit of chicken and egg situation. I cant unlock the bootloader as I cant boot the device and I cant reflash software as I don't have an unlocked bootloader.
AFAIK you always are allowed to flash an original firmware image without unlocking the phone's bootloader.
If you can access the device by means of ADB try to flash the Stock ROM via ADB:
Code:
adb devices
adb reboot sideload
adb sideload <LOCATION_OF_STOCK_ROM_ZIP_FILE_HERE>
C:\adb>adb devices
List of devices attached
f625af1 sideload
C:\adb>adb sideload miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip
loading: 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip'
* cannot read 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip' *
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
jwoegerbauer said:
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
Click to expand...
Click to collapse
tried that same error cannot read rom.zip
sivhead said:
tried that same error cannot read rom.zip
Click to expand...
Click to collapse
C:\adb>adb sideload c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip
loading: 'c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip'* failed to read command: No error
I also thought its worth mentioning that I have never registered the device with mi connect
Also enable usb debugging is not enabled.
aqnd THe bootloader is locked .
Man I wish I would have unlocked the bootloader when I got it and put a custom rom on. then I wouldnt be in this situation. how ironic that I wanted to keep it stock
so I am at a loose end
EDIT: I was able to unlock my bootloader by just trying to use the fastboot "unlock bootloader" command several times. Thanks a lot SubwayChamp for helping me through this, I was also able to root my phone. Wasn't able to install a custom recovery, though.
I have a Multilaser H phone. It is a phone from a national brand, "Multilaser" here in Brazil.
For some reason, Multilaser does not want to provide the bootloader "unlock.img" file.
For context, the Multilaser H is just a white label of the Lenovo Z6 Lite/Lenovo K10 Note.
I downloaded the Z6 Lite unlock bootloader file and it has an "unlock_bootloader.img". I tried running the Z6 Bootloader Unlocker on the Multilaser H but it just didn't work. I really want to flash a custom ROM on my phone and I've tried all sorts of things, even trying to sideload another ROM but with the locked bootloader it's impossible. And no, I can't just buy a new phone, unfortunately. This one is more than capable of running Android 10 or even 11 but Multilaser just does not release it so I'm stuck on 9.
Is there any way to make that "unlock_bootloader.img" file that the Z6 Lite tool uses to unlock the phone for MY phone? Like, generate it? Because apparently the company doesn't want to provide it for us. The stock ROM I have here does have the "recovery.img" file.
Can I unlock my bootloader or somehow make a file similar to unlock_bootloader.img that allows me to do that? I have no idea how it works exactly but I'm assuming the "unlock.bootloader.img" is specific for the Z6 Lite and allows it to unlock the bootloader.
Here's how the Z6 Lite Tools folder looks like by the way
{
"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"
}
AlNexus said:
I have a Multilaser H phone. It is a phone from a national brand, "Multilaser" here in Brazil.
For some reason, Multilaser does not want to provide the bootloader "unlock.img" file.
For context, the Multilaser H is just a white label of the Lenovo Z6 Lite/Lenovo K10 Note.
I downloaded the Z6 Lite unlock bootloader file and it has an "unlock_bootloader.img". I tried running the Z6 Bootloader Unlocker on the Multilaser H but it just didn't work. I really want to flash a custom ROM on my phone and I've tried all sorts of things, even trying to sideload another ROM but with the locked bootloader it's impossible. And no, I can't just buy a new phone, unfortunately. This one is more than capable of running Android 10 or even 11 but Multilaser just does not release it so I'm stuck on 9.
Is there any way to make that "unlock_bootloader.img" file that the Z6 Lite tool uses to unlock the phone for MY phone? Like, generate it? Because apparently the company doesn't want to provide it for us. The stock ROM I have here does have the "recovery.img" file.
Can I unlock my bootloader or somehow make a file similar to unlock_bootloader.img that allows me to do that? I have no idea how it works exactly but I'm assuming the "unlock.bootloader.img" is specific for the Z6 Lite and allows it to unlock the bootloader.
Here's how the Z6 Lite Tools folder looks like by the way
View attachment 5457515
Click to expand...
Click to collapse
Do you mean you tried something like this? https://www.gizdev.com/twrp-root-lenovo-z6-youth/ running the bootloader_unlock.bat? What does unlock_bootloader.img do?
Try with these commands apart to know the bootloader status
fastboot oem device-infoor fastboot getvar unlocked
Maybe you can try with simple commands to unlock it, in case you are wrong and the OEM doesn't care bootloader being unlocked:
fastboot oem unlock or fastboot oem unlock-go or
fastboot flashing unlock You should enable USB debugging and OEM unlock toggle must be available under this section, otherwise neither of those will work.
And if this device totattly rebranded from the Z6 Lite, or it has a MediaTek processor?
SubwayChamp said:
Do you mean you tried something like this? https://www.gizdev.com/twrp-root-lenovo-z6-youth/ running the bootloader_unlock.bat? What does unlock_bootloader.img do?
Try with these commands apart to know the bootloader status
fastboot oem device-infoor fastboot getvar unlocked
Maybe you can try with simple commands to unlock it, in case you are wrong and the OEM doesn't care bootloader being unlocked:
fastboot oem unlock or fastboot oem unlock-go or
fastboot flashing unlock You should enable USB debugging and OEM unlock toggle must be available under this section, otherwise neither of those will work.
And if this device totattly rebranded from the Z6 Lite, or it has a MediaTek processor?
Click to expand...
Click to collapse
When I try those commands it just says "Waiting for device..." and there's nothing on my phone. The FastBoot screen is identical to the Z6 Lite one. And the device is totally rebranded apparently, maybe something there and here, but it has the same CPU, RAM and storage.
AlNexus said:
When I try those commands it just says "Waiting for device..." and there's nothing on my phone. The FastBoot screen is identical to the Z6 Lite one. And the device is totally rebranded apparently, maybe something there and here, but it has the same CPU, RAM and storage.
Click to expand...
Click to collapse
OK, we're just trying to figure it out if your device can be really unlocked or not, so you need to walk through these steps to be sure.
"Waiting for device..." means that your device is not being detected, you need to install properly the fastboot drivers for Lenovo otherwise you can´t do what you need, the first step is this. With your device on, enable USB debugging in developer options, and unlock OEM toggle, when you enabled USB debugging you will see a pop-up message asking for "allow always", then tap on it.
As per to know if the model is identical you should download an app from Google Play, something like Device Info and see the specs, if this device has MediaTek instead of Qualcomm there could be a workaround.
SubwayChamp said:
OK, we're just trying to figure it out if your device can be really unlocked or not, so you need to walk through these steps to be sure.
"Waiting for device..." means that your device is not being detected, you need to install properly the fastboot drivers for Lenovo otherwise you can´t do what you need, the first step is this. With your device on, enable USB debugging in developer options, and unlock OEM toggle, when you enabled USB debugging you will see a pop-up message asking for "allow always", then tap on it.
As per to know if the model is identical you should download an app from Google Play, something like Device Info and see the specs, if this device has MediaTek instead of Qualcomm there could be a workaround.
Click to expand...
Click to collapse
I installed the drivers. Here is the output of the 3 commands:
Code:
PS C:\Users\alnexus> fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
PS C:\Users\alnexus> fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.002s
PS C:\Users\alnexus> fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
It says "unlocked: no". Also it is Qualcomm, SDM710.
EDIT: Yeah it's probably impossible to unlock. Damn it, why do companies do this? Lock us in this crappy system and we can't even install another OS? I bought the phone, let me do whatever I want with it.
AlNexus said:
I installed the drivers. Here is the output of the 3 commands:
PS C:\Users\alnexus> fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
PS C:\Users\alnexus> fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.002s
PS C:\Users\alnexus> fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
It says "unlocked: no". Also it is Qualcomm, SDM710.
EDIT: Yeah it's probably impossible to unlock. Damn it, why do companies do this? Lock us in this crappy system and we can't even install another OS? I bought the phone, let me do whatever I want with it.
Click to expand...
Click to collapse
And is there an OEM unlock toggle? If not or even being one, if OEM doesn't want to be unlocked there’s not much to do.
And what happen running the unlock.bat from the Z6 lite now that you installed properly the fastboot drivers?
Also check what is in the unlock.bat script, open it with Notepad++ and see which command is executed.
SubwayChamp said:
And is there an OEM unlock toggle? If not or even being one, if OEM doesn't want to be unlocked there’s not much to do.
And what happen running the unlock.bat from the Z6 lite now that you installed properly the fastboot drivers?
Also check what is in the unlock.bat script, open it with Notepad++ and see which command is executed.
Click to expand...
Click to collapse
Yes, there is an OEM unlock toggle. I enabled it.
Great idea, I'll try that, but my hopes are absolutely 0.
Here's the UNLOCK BOOTLOADER.bat (unlock.bat) script content:
Code:
@echo off
TITLE Bootloader Unlocker
color 3f
CLS
ECHO. ============================================================================
echo.
echo. Press any key
echo.
echo. ============================================================================
pause >nul
CLS
adb devices
echo.
echo Reboot mode bootloader
echo.
adb reboot bootloader
CLS
echo.
echo Firmware bootloader...
echo.
echo.
fastboot flash unlock unlock_bootloader.img
pause
CLS
echo.
echo Unlocking bootloader...
echo.
echo.
fastboot oem unlock-go
pause
CLS
echo.
echo Unlock complete, wait for reboot
echo.
fastboot %* reboot
pause
Yeah, didn't work ):
AlNexus said:
Yeah, didn't work ):
View attachment 5458091
Click to expand...
Click to collapse
WHAT
I TRIED USING THE UNLOCK BOOTLOADER COMMANDQ MULTIPLE TIMES AND IH AVE UNLOCKED THE BOOTLOADER
I hope it doesn't brick my phone now lol. Sorry, I couldn't contain my excitement...
AlNexus said:
WHAT
I TRIED USING THE UNLOCK BOOTLOADER COMMANDQ MULTIPLE TIMES AND IH AVE UNLOCKED THE BOOTLOADER
I hope it doesn't brick my phone now lol. Sorry, I couldn't contain my excitement...View attachment 5458109
Click to expand...
Click to collapse
When I try using that it just hangs on "downloading 'boot.img"...
Should I wait?
When I tried fastboot flash recovery twrp.img it said sending 'recovery' and said FAILED (remote: Requested download size is more than max allowed)
AlNexus said:
View attachment 5458111
When I try using that it just hangs on "downloading 'boot.img"...
Should I wait?
When I tried fastboot flash recovery twrp.img it said sending 'recovery' and said FAILED (remote: Requested download size is more than max allowed)
Click to expand...
Click to collapse
it seems that sometimes when I try using "fastboot flash recovery twrp.img" it just "restarts" the phone. The phone goes to a splash screen and it says in the top corner "press any key to shutdown" and disconnects from the computer. "fastboot boot" just hangs on downloading 'boot.img'.
Oops, that just happened with fastboot boot too.
and it showed the splash screen with "press any key to shutdown" in the corner
AlNexus said:
it seems that sometimes when I try using "fastboot flash recovery twrp.img" it just "restarts" the phone. The phone goes to a splash screen and it says in the top corner "press any key to shutdown" and disconnects from the computer. "fastboot boot" just hangs on downloading 'boot.img'.
Oops, that just happened with fastboot boot too.
View attachment 5458129 and it showed the splash screen with "press any key to shutdown" in the corner
Click to expand...
Click to collapse
You also could try fastboot flashing unlock_critical
First, be sure to get the firmware at hands, in case something goes wrong.
Regards the TWRP version, are you sure it is for your device?
Maybe you need to port from the Z6 Lite, making minimal changes.
In a different approach, you could patch your boot image with Magisk and flash it to the boot partition.
"Too many links..." error is probably that you have attached to your PC more than one Android device/emulator/USB hub or something, check that, end the process with adb kill-server and restart again with adb start-server or go straight to the command, ADB will start automatically.
SubwayChamp said:
You also could try fastboot flashing unlock_critical
First, be sure to get the firmware at hands, in case something goes wrong.
Regards the TWRP version, are you sure it is for your device?
Maybe you need to port from the Z6 Lite, making minimal changes.
In a different approach, you could patch your boot image with Magisk and flash it to the boot partition.
"Too many links..." error is probably that you have attached to your PC more than one Android device/emulator/USB hub or something, check that, end the process with adb kill-server and restart again with adb start-server or go straight to the command, ADB will start automatically.
Click to expand...
Click to collapse
I'll try that. I don't know how to port but I don't think it should be too hard. Thanks for the tips, I'll also try to patch my boot image.
AlNexus said:
I'll try that. I don't know how to port but I don't think it should be too hard. Thanks for the tips, I'll also try to patch my boot image.
Click to expand...
Click to collapse
Patching the boot image doesn't work either. Stuck on "sending 'recovery' forever. I had also gotten
Code:
fastboot flash recovery magisk_patched.img
Sending 'recovery' (65536 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
before. I'll try with another USB cable. Wonder if it could be the drivers; I have already installed the device drivers from Google and Lenovo.
I had a different output on Linux, but Magisk App doesn't say "Installed".
EDIT: I tried to flash "twrp.img" (I know it's dangerous without a backup) and it said the same thing, except the phone doesn't seem to have TWRP installed.
It says finished but nothing actually happens or changes in the phone.
EDIT 2: When I try fastboot boot recovery.img it says FAILED (remote: 'unknown command')
AlNexus said:
View attachment 5458349
Patching the boot image doesn't work either. Stuck on "sending 'recovery' forever. I had also gotten
Code:
fastboot flash recovery magisk_patched.img
Sending 'recovery' (65536 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
before. I'll try with another USB cable. Wonder if it could be the drivers; I have already installed the device drivers from Google and Lenovo.
Click to expand...
Click to collapse
I guess you patched it the boot image from your stock ROM, then it is to flash it to the boot partition, not to the recovery partition, the usage would be fastboot flash boot patchedboot.img this is to achieve root, if rooted you could do more things.
I'm assuming that you opened the fastboot commands from within the directory where there are the images files.
SubwayChamp said:
I guess you patched it the boot image from your stock ROM, then it is to flash it to the boot partition, not to the recovery partition, the usage would be fastboot flash boot patchedboot.img this is to achieve root, if rooted you could do more things.
I'm assuming that you opened the fastboot commands from within the directory where there are the images files.
Click to expand...
Click to collapse
Yes, I did.
You saved my day. Thanks a lot, I got it rooted by using fastboot flash boot magisk_patched.img. Having root is infinitely better than having nothing.
I should mark the whole topic as "solved" now. Thanks so much
AlNexus said:
Yes, I did.
You saved my day. Thanks a lot, I got it rooted by using fastboot flash boot magisk_patched.img. Having root is infinitely better than having nothing.
I should mark the whole topic as "solved" now. Thanks so much
Click to expand...
Click to collapse
Good to hear that.
Now you can follow with searching these topics:
- How to back up android partitions. (to get the complete images -firmware- so you can restore it if something goes wrong). This is just an example: https://github.com/for2ando/dump-android-partitions
- How to port TWRP recovery for my device, from the Z6 Lite can be used as base. Something like this: https://forum.hovatek.com/thread-26277.html
And lastly, to change for a different featured ROM:
- How to flash a GSI.
first of i apologise if i have bad english
ok so i had this device for some time and decited to root it (my first time rooting a phone). And i need to unlock bootloader to flash stuff and i have all necessary things on my pc (platform tools,drivers,) everything seems to be working but as soon as i get into bootloader the only command that works is "fastboot devices" Any other commands dont work. I tried everything online and this is my only other thing left to do. I've been researching for 2 days at this point and i am almost certain that the commands are disabled by the company itself (like huawei) did anybody else ever root/unlock bootloader for this device because i didnt find any actual root guide for the particular device (besides from the auto generated ones like https://rootguia.com/how-to-flash-caterpillar-cat-s31/ https://mobilewithdrivers.com/unlock-bootloader/cat-s31-16gb-2gb-ram )
The exact error is:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
(and this error is for every single command that uses fastboot besides from fastboot devices. Adb works just fine)
I tried:
reinstalling drivers
installing drivers that are "prepared" for the cat s31
changing cable
changing port to usb 2.0
reinstalling platform tools (from official google site)
checking device manager for the device (it shows up as android bootloader interface)
trying alternative oem unlock commands (fastboot oem unlock, fastboot flashing unlock and 2 other commands that i cant remember rn)
having oem unlocking and usb debugging enabled from the developer options
in my opinion the only explanation is the commands being disabled by default and even if it was it wouldnt be known if it was since most people dont root or purchase this device
please help me out here
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
aIecxs said:
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
Click to expand...
Click to collapse
sorry i forgot to mention im running android 8.1 oreo on this device and devinfo partition method will not work according to what i read
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
aIecxs said:
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
Click to expand...
Click to collapse
what do you mean by dump phone into edl mode do i download one of these https://ministryofsolutions.com/2022/01/cat-s31-edl-firmware-android-8-1-official-rom.html and install it from recovery mode and try to get it in edl mode and will it not work if i dont dump
just extract that ROM you found
aIecxs said:
just extract that ROM you found
Click to expand...
Click to collapse
and do what. im new to the rooting stuff
find the file aboot.mbn (or similar) and analyze for fastboot commands
aIecxs said:
find the file aboot.mbn (or similar) and analyze for fastboot command
Click to expand...
Click to collapse
so i downloaded the file and these are the things in the firmware file (attachement)
i cant find a file that looks or resambles aboot.mbn
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
aIecxs said:
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
Click to expand...
Click to collapse
sooo turns out win11 strings commands are kinda different or broken (probably not im just dumb) i just used notepad with ctrl+f and couldnt find anything besides the text that says are you sure you want to unlock bootloader but that is probably not related since i didnt find any commands or anything. So im actually going to attach the emmc_appsboot.mbn i know it looks sketchy you dont have to download it its totally understandable but if you do please do give it a check and respond. I want to get this done one way or another its 1 am i want to sleep ;(
could it be true that they made a truly un unlockable unrootable device
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
Click to expand...
Click to collapse
trust me i have tried many many many many times and only got a
FAILED (remote: 'unknown command')
fastboot: error: Command failed
edit: the only place oem unlock is mentioned is a text that says oem unlock not allowed which might be default text by android or whatever but cat devs somehow messed it up somehow??
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
Click to expand...
Click to collapse
just saw the edit i will check now
nope nothing related no oem unlock no fastboot no flashing no flash nothing is mentioned ill attach it if you want to look
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
aIecxs said:
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
Click to expand...
Click to collapse
from recovery using the flash firmware with adb option??
edit: i meant apply update from adb
edit2: what if i hard reset from recovery would that reset the firmware?
edl firmware cannot flashed from recovery. power off phone, press both volume keys and plug in usb-cable. check VID/PID from windows device manager. if you see device ID (05c6:9008) the phone is in EDL mode. you can now use EDL tool (post #2) and backup current ROM. then you can flash other ROM.
aIecxs said:
It's edl firmware cannot flashed from recovery
Click to expand...
Click to collapse
so what do i download that can be flashed from recovery