I was testing the "fastboot" command in bootloader mode today and I got stuck in bootloader after I ran the command "fastboot flashing lock".
My device won't boot into system nor will RECOVERY MODE work.
Code:
$ fastboot reboot
Rebooting OKAY [ 0.007s]
Finished. Total time: 0.007s
I tried to unlock OEM or BOOTLOADER and got two "FAILED".
Code:
$ fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
I checked the device info and it returned
Code:
$ fastboot oem device-info
(bootloader) Verity mode: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
Install stock Android also won't work
Code:
$ ./flash-all.sh
Sending 'bootloader_b' (38728 KB) OKAY [ 0.829s]
Writing 'bootloader_b' FAILED (remote: 'Operation is not allowed in Lock State')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Sending 'radio_b' (60428 KB) OKAY [ 1.566s]
Writing 'radio_b' FAILED (remote: 'Operation is not allowed in Lock State')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.001s
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00122-1708311414
Serial Number........: HT7B91A03213
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
What else can I do? Could anybody PLEASE help me solve this problem, I am so desperate...:crying::crying::crying:
@ayewilling
Your phone obviousy runs an Android version that has A/B-system-partition layout, has AVB enabled, and furthermore it seems phone's boot-loader is locked.
My POV: You at 1st thing of all things should become familiar with HOW FASTBOOT WORKS, WHAT YOU CAN MANAGE WITH IT.
Anyway, running the command sequence
Code:
fastboot devices
fastboot reboot
should boot phone in normal mode.
jwoegerbauer said:
@ayewilling
Your phone obviousy runs an Android version that has A/B-system-partition layout, has AVB enabled, and furthermore it seems phone's boot-loader is locked.
My POV: You at 1st thing of all things should become familiar with HOW FASTBOOT WORKS, WHAT YOU CAN MANAGE WITH IT.
Anyway, running the command sequence
Code:
fastboot devices
fastboot reboot
should boot phone in normal mode.
Click to expand...
Click to collapse
Thanks for your relpy!
I have tried several fastboot commands, and it dosen't seem work for me.
"fastboot devices" lists my device, however, "fastboot reboot" still boot my device into FASTBOOT MODE, NOT the NORMAL MODE.
Here is the output
Code:
$ fastboot devices
HT7B91A03213 fastboot
$ fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
I flashed the stock Android 8.1 and it worked fine, until yesterday I locked the OEM and bootloader
The point is WHY my device cannot boot in normal mode, which I guess may have something to do with the lock status of bootloader.
@ayewilling
An universal version of Fastboot does not exist: each OEM/Carrier implement a Fastboot that's suitable to the device's chipset. My guess is that the Fastboot driver you use isn't suitable.
The Google Pixel 2 is based on a Qualcomm chipset. My recommendation is to install and use the matching USB drivers ( incl. ADB / Fastboot ):
{
"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"
}
jwoegerbauer said:
@ayewilling
An universal version of Fastboot does not exist: each OEM/Carrier implement a Fastboot that's suitable to the device's chipset. My guess is that the Fastboot driver you use isn't suitable.
The Google Pixel 2 is based on a Qualcomm chipset. My recommendation is to install and use the matching USB drivers ( incl. ADB / Fastboot ):
Click to expand...
Click to collapse
Hum! I'll give it a try!
Look forward to good news！
0
Hello ayewilling your problem is fixed or not ??
Seppppx said:
Wrong! fastboot/adb is made by google, thus it works on Google phones. And a lot of times you can get fastboot and adb to work with generic drivers from google.
---------- Post added at 12:17 PM ---------- Previous post was at 12:11 PM ----------
@ayewilling
On what rom did you lock the bootloader?
If it's a rom like lineageos which uses userdebug builds you can disable AVB by doing
"fastboot oem disable_dm_verity"
The locked bootloader shouldn't be a problem as Pixels support locking the bootloader on unknown signing keys. You should then be able to unlock it in your rom afterwards.
Click to expand...
Click to collapse
Hello seppppx sir I was
Seppppx said:
Wrong! fastboot/adb is made by google, thus it works on Google phones. And a lot of times you can get fastboot and adb to work with generic drivers from google.
---------- Post added at 12:17 PM ---------- Previous post was at 12:11 PM ----------
@ayewilling
On what rom did you lock the bootloader?
If it's a rom like lineageos which uses userdebug builds you can disable AVB by doing
"fastboot oem disable_dm_verity"
The locked bootloader shouldn't be a problem as Pixels support locking the bootloader on unknown signing keys. You should then be able to unlock it in your rom afterwards.
Click to expand...
Click to collapse
jwoegerbauer said:
@ayewilling
Your phone obviousy runs an Android version that has A/B-system-partition layout, has AVB enabled, and furthermore it seems phone's boot-loader is locked.
My POV: You at 1st thing of all things should become familiar with HOW FASTBOOT WORKS, WHAT YOU CAN MANAGE WITH IT.
Anyway, running the command sequence
Code:
fastboot devices
fastboot reboot
should boot phone in normal mode.
Click to expand...
Click to collapse
Hello sir my device is on same problem how I recover my device Sir plz help me
Seppppx said:
Wrong! fastboot/adb is made by google, thus it works on Google phones. And a lot of times you can get fastboot and adb to work with generic drivers from google.
---------- Post added at 12:17 PM ---------- Previous post was at 12:11 PM ----------
@ayewilling
On what rom did you lock the bootloader?
If it's a rom like lineageos which uses userdebug builds you can disable AVB by doing
"fastboot oem disable_dm_verity"
The locked bootloader shouldn't be a problem as Pixels support locking the bootloader on unknown signing keys. You should then be able to unlock it in your rom afterwards.
Click to expand...
Click to collapse
Hello sir my device is on same problem how I fix this plz help me sir
Related
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
ikolbyi said:
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
Click to expand...
Click to collapse
Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. You lack experience. Take care, there's brick there's no way to recover
Enviado de meu BLA-L29 usando o Tapatalk
ChaseRxx said:
Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. You lack experience. Take care, there's brick there's no way to recover
Enviado de meu BLA-L29 usando o Tapatalk
Click to expand...
Click to collapse
"Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. "
- The reason for the post asking for help.
"You lack experience. Take care, there's brick there's no way to recover"
- Why bother post an insult, silence would have been more professional.
ikolbyi said:
"Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. "
- The reason for the post asking for help.
"You lack experience. Take care, there's brick there's no way to recover"
- Why bother post an insult, silence would have been more professional.
Click to expand...
Click to collapse
GL!
Enviado de meu BLA-L29 usando o Tapatalk
ikolbyi said:
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
Click to expand...
Click to collapse
Check for all drivers and also is your bootloader unlocked cuz it says there remote: Command not allowed that probably means that something is probably blocking it on the phone side
LLoTE said:
Check for all drivers and also is your bootloader unlocked cuz it says there remote: Command not allowed that probably means that something is probably blocking it on the phone side
Click to expand...
Click to collapse
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
ikolbyi said:
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
Click to expand...
Click to collapse
Welp
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
ikolbyi said:
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
Click to expand...
Click to collapse
You need to first unlock the bootloader it's not as simple as that search online how to unlock it
LLoTE said:
Welp
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
You need to first unlock the bootloader it's not as simple as that search online how to unlock it
Click to expand...
Click to collapse
okay - steps?
ikolbyi said:
okay - steps?
Click to expand...
Click to collapse
Search on YouTube or on google idk how exactly my friend had a mate 10 pro i didnt
LLoTE said:
Search on YouTube or on google idk how exactly my friend had a mate 10 pro i didnt
Click to expand...
Click to collapse
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
ikolbyi said:
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
Click to expand...
Click to collapse
Yea man post are really disinformational im sorry ill ask my friend how he unlocked it
LLoTE said:
Yea man post are really disinformational im sorry ill ask my friend how he unlocked it
Click to expand...
Click to collapse
Thank you. I'm new at this and learning.
ikolbyi said:
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
Click to expand...
Click to collapse
look at this one
Toggling OEM unlocking in developer options is not enough, as that simply enables the ability to unlock your bootloader within fastboot. You need to retrieve a bootloader unlock code either directly from Huawei or a third party. I believe there is a guide for it in the guides sub-forum.
LLoTE said:
look at this one
Click to expand...
Click to collapse
I did't need to download the tool but the second half the video answered my questions. I was able to obtain the 'key' from Huawei outlined in the video then in fastboot mode:
"adb oem unlock <the key from Huawei>"
And it unlocked my bootloader reformatting it. Now step 2 - editing the file.
ikolbyi said:
I did't need to download the tool but the second half the video answered my questions. I was able to obtain the 'key' from Huawei outlined in the video then in fastboot mode:
"adb oem unlock <the key from Huawei>"
And it unlocked my bootloader reformatting it. Now step 2 - editing the file.
Click to expand...
Click to collapse
And how will you edit it? You'll root the phone or?
LLoTE said:
And how will you edit it? You'll root the phone or?
Click to expand...
Click to collapse
Now that the boot loader is unlocked, I edited the /vendor/build.prop file using this method:
with phone in fastboot mode (from laptop computer connected to phone via USB , phone in developer mode)
adb reboot bootloader
Next step was to install TWRP:
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
fastboot reboot (immediately unplug phone from USB and hold down the high volume button until you see Huawei logo)
When in TWRP manually mount /vendor then reconnected device to USB connected to computer.
executed the following commands:
adb pull /vendor/build.prop C:\downloads\build.prop
/vendor/build.prop: 1 file pulled. 0.1 MB/s (4065 bytes in 0.026s)
adb push C:\downloads\build.prop /vendor/build.prop
C:\downloads\build.prop: 1 file pushed. 0.2 MB/s (4097 bytes in 0.018s)
it worked. I added the line "ro.config.hw_volte_dyn=false"
reboot and it came up with the feature.
Your missing piece helped me get this completed, thank you LLoTE
ikolbyi said:
Now that the boot loader is unlocked, I edited the /vendor/build.prop file using this method:
with phone in fastboot mode (from laptop computer connected to phone via USB , phone in developer mode)
adb reboot bootloader
Next step was to install TWRP:
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
fastboot reboot (immediately unplug phone from USB and hold down the high volume button until you see Huawei logo)
When in TWRP manually mount /vendor then reconnected device to USB connected to computer.
executed the following commands:
adb pull /vendor/build.prop C:\downloads\build.prop
/vendor/build.prop: 1 file pulled. 0.1 MB/s (4065 bytes in 0.026s)
adb push C:\downloads\build.prop /vendor/build.prop
C:\downloads\build.prop: 1 file pushed. 0.2 MB/s (4097 bytes in 0.018s)
it worked. I added the line "ro.config.hw_volte_dyn=false"
reboot and it came up with the feature.
Your missing piece helped me get this completed, thank you LLoTE
Click to expand...
Click to collapse
No problem man
Hi,
Tried to flash my Acer Iconia B3-A30. Before I start with flashing i tried some commands. The "fastboot reboot" doesn't work for me.
Every Time i try
Code:
platform-tools>fastboot reboot
Rebooting FAILED (remote: 'not support on security')
fastboot: error: Command failed
bootloader is unlocked:
Code:
platform-tools>fastboot getvar unlocked
unlocked: yes
Finished. Total time: 0.003s
but i found the secure state in the getvar info's:
Code:
platform-tools>fastboot getvar secure
secure: no
Finished. Total time: 0.004s
is it ritght?
I hope u can help me. Because my tablet stuck on boot image. Recovery doesent boot anymore.. etc.
Same problem here. Did you figure it out?
Hi
I'm stuck in my Xiaomi MI A3 bootloader, can't boot to recovery and system.
After flashing my stock firmware.
Here is my oem device info
PS C:\platform-tools> ./fastboot oem device-info (bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
Finished. Total time: 0.006s
PS C:\platform-tools> ./fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s
Thank you
bgsebiosjr said:
Hi
PS C:\platform-tools> ./fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s
Thank you
Click to expand...
Click to collapse
Change current-slot to 'a' and reboot.
PS C:\platform-tools> ./fastboot flashing get_unlock_ability (bootloader) get_unlock_ability: 0
OKAY [ 0.002s]
Finished. Total time: 0.005s
PS C:\platform-tools> ./fastboot flashing unlock FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
PS C:\platform-tools> ./fastboot set_active a Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
PS C:\platform-tools>
How can i use EDL?
Sapper Morton said:
Since your bootloader is locked, and there's no proper system.img in slot B, you must change it to slot A; however it's not possible in locked state, first check if it's possible to unlock, by running:
Code:
fastboot flashing get_unlock_ability
If the output is 0, you cannot unlock, and EDL is a must, otherwise, the output will be 1, therefore, unlock is possible, then proceed with the following steps:
Code:
fastboot flashing unlock
Code:
fastboot set_active a
Code:
fastboot flashing lock
As explained above, it's not possible to change slot without unlocking the bootloader.
Click to expand...
Click to collapse
msatyanarayana said:
Change current-slot to 'a' and reboot.
Click to expand...
Click to collapse
PS C:\platform-tools> ./fastboot set_active a Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
PS C:\platform-tools>
Not allowed in Lock State.
Is there any way to oem unlock without going to Debugging Mode -> OEM enable?
I can't boot my system and recovery.
bgsebiosjr said:
Not allowed in Lock State.
Is there any way to oem unlock without going to Debugging Mode -> OEM enable?
I can't boot my system and recovery.
Click to expand...
Click to collapse
EDL mode and authorized Mi account. You should contact your nearest Xiaomi service center or use some online service (you might need to open your phone yourself in such case).
Need advice. My goal is to flash GSI ROM onto this thing. The treble app says it is supported. (type A)
However, the usual commands for unlocking bootloader seem to indicate it is either already unlocked but not telling me or locked and not unlockable..?
This is a unisoc SC9863a
baseband: FM_BASE_18B_W19.08.1_P11 | SC9863a_modem | 04-26-2019 MARLIN2_17A_RLS1_W19.17.7 | sharkl3_cm4 | 04-28-2019
kernel: 4.4.147+ (20190703)
build number: PPR1 180610.011
android: 9 pie
WIKO/W-V800-EEA/W-V800
9/PPR1.180610.011/08018
unrooted > MTK-su and several oneroot options not working (although they might on oreo if I can find the factory rom)
OEM unlocking enabled in developer options
In fastboot you get:
fastboot flashing unlock > FAILED (remote: Not implemet.)
fastboot oem unlock > FAILED (remote: unknown cmd.)
fastboot oem get_unlock_data > FAILED (remote: unknown cmd.)
fastboot flashing unlock_critical > FAILED (remote: Not implement.)
I tried following this process: (from here (Mod Edit: Link removed)
./fastboot oem get_identifier_token
./signidentifier_unlockbootloader.sh XXXXXXXXXXXXXXX rsa4096_vbmeta.pem signature.bin
./fastboot flashing unlock_bootloader signature.bin
last command returns with: "downloading 'unlock_message'...
OKAY [ 0.001s]
unlocking bootloader...
FAILED (remote: Unlock bootloader fail.)
finished. total time: 0.104s"
additional questions:
Can I just flash a certain recovery somehow?
Do I have to try something complicated like this: (Mod Edit: Link removed)
Have you got root on your view 3 lite?
go0 said:
In fastboot you get:
fastboot flashing unlock > FAILED (remote: Not implemet.)
fastboot oem unlock > FAILED (remote: unknown cmd.)
fastboot oem get_unlock_data > FAILED (remote: unknown cmd.)
fastboot flashing unlock_critical > FAILED (remote: Not implement.)
Click to expand...
Click to collapse
Indicates the FastBoot implemented in device's bootloader doesn't support these subcommands. Obviously OEM/Carrier doesn't want that device's bootloader gets unlocked.
anonym6x6 said:
Have you got root on your view 3 lite?
Click to expand...
Click to collapse
If oreo exists for this and you know where to get it, let me know and I'll try.
If I can get root, what would you recommend trying to unlock bootloader?
jwoegerbauer said:
Indicates the FastBoot implemented in device's bootloader doesn't support these subcommands. Obviously OEM/Carrier doesn't want that device's bootloader gets unlocked.
Click to expand...
Click to collapse
OK...
I have a Motorola XT1941-4, which I have from some time ago which is currently not able to be used. I wanted to try and fix it but cannot get any progress done. The problem I'm having is as follows: Whenever I boot the phone it goes right into the bootloader and at the bottom it says flashing_locked. I' able to communicate with the phone via fastboot and am able to boot into TWRP with fastboot boot twrp.img and when I am in TWRP the phone is also recognized in ADB. However I cannot get the phone to boot into Android. Is there anything I can do to fix this?
ogruendel said:
I have a Motorola XT1941-4, which I have from some time ago which is currently not able to be used. I wanted to try and fix it but cannot get any progress done. The problem I'm having is as follows: Whenever I boot the phone it goes right into the bootloader and at the bottom it says flashing_locked. I' able to communicate with the phone via fastboot and am able to boot into TWRP with fastboot boot twrp.img and when I am in TWRP the phone is also recognized in ADB. However I cannot get the phone to boot into Android. Is there anything I can do to fix this?
Click to expand...
Click to collapse
Have you tried to blankflash it?
FilipeET said:
Have you tried to blankflash it?
Click to expand...
Click to collapse
How would I go about doing that?
ogruendel said:
How would I go about doing that?
Click to expand...
Click to collapse
I'll leave the Motorola qboot utility in this reply.
Start device in fastboot mode, and
run the following command:
Code:
fastboot oem blankflash
fastboot oem blankflash
after that, extract and run the Unbrick.bat that I'll leave in this reply, your phone should be on a black screen when running the command, but after running the "Unbrick.bat" it should restart to the unlocked bootloader!
but before running it, verify if your phone codename is "deen"
FilipeET said:
I'll leave the Motorola qboot utility in this reply.
Start device in fastboot mode, and
run the following command:
Code:
fastboot oem blankflash
fastboot oem blankflash
after that, extract and run the Unbrick.bat that I'll leave in this reply, your phone should be on a black screen when running the command, but after running the "Unbrick.bat" it should restart to the unlocked bootloader!
but before running it, verify if your phone codename is "deen"
Click to expand...
Click to collapse
Sorry for the late reply, I had issues with my computer and then forgot about this... I've tried running the command fastboot oem blankflash but I get
Code:
(bootloader) command restricted
FAILED (remote: '')
fastboot: error: Command failed
ogruendel said:
Sorry for the late reply, I had issues with my computer and then forgot about this... I've tried running the command fastboot oem blankflash but I get
Code:
(bootloader) command restricted
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Try to switch the slot,
Code:
fastboot set_active other
FilipeET said:
Try to switch the slot,
Code:
fastboot set_active other
Click to expand...
Click to collapse
I've tried this command, however this also fails with the message
Code:
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
What appears when you start the phone? could you send me a picture? Have you tried starting the recovery? Tried to use Lenovo Moto Smart Assistant?
have you tried unlocking the bootloader again?
ogruendel said:
I've tried this command, however this also fails with the message
Code:
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
What appears when you start the phone? could you send me a picture? Have you tried starting the recovery? Tried to use Lenovo Moto Smart Assistant?
have you tried unlocking the bootloader again?
I saw that you put in the post that you can start twrp, try changing the slot there in Reboot > Switch to slot B,
if it is in slot b: Reboot > Switch to slot A.
FilipeET said:
What appears when you start the phone? could you send me a picture? Have you tried starting the recovery? Tried to use Lenovo Moto Smart Assistant?
have you tried unlocking the bootloader again?
I saw that you put in the post that you can start twrp, try changing the slot there in Reboot > Switch to slot B,
if it is in slot b: Reboot > Switch to slot A.
Click to expand...
Click to collapse
What appears when you start the phone?
Click to expand...
Click to collapse
https://imgur.com/a/Veg48Bs
Have you tried starting the recovery? Tried to use Lenovo Moto Smart Assistant?
Click to expand...
Click to collapse
Yes, however when I start the program it detects that a phone is connected but tells me "RSA detected, that your device flash is locked. [...]"
Have you tried unlocking the bootloader aagin?
Click to expand...
Click to collapse
Yes, I have. I remember when trying this before and following the steps on the official Motorola website, I would receive a new unlock code, however when I run fastboot oem get_unlock_data now and enter the output into the Motorola website it comes up with an error telling me that my device does not qualify for bootloader unlocking.
I saw that you put in the post that you can start twrp, try changing the slot there in Reboot > Switch to slot B,
if it is in slot b: Reboot > Switch to slot A.
Click to expand...
Click to collapse
I did this but the behaviour is the same. Commands come back with the same errors etc.
I saw the image, your phone can be unlocked, its says flashing_unlocked, so, he got unlocked 1 time, Just run "fastboot flashing unlock" ir "fastboot oem unlock"
ogruendel said:
https://imgur.com/a/Veg48Bs
Yes, however when I start the program it detects that a phone is connected but tells me "RSA detected, that your device flash is locked. [...]"
Yes, I have. I remember when trying this before and following the steps on the official Motorola website, I would receive a new unlock code, however when I run fastboot oem get_unlock_data now and enter the output into the Motorola website it comes up with an error telling me that my device does not qualify for bootloader unlocking.
I did this but the behaviour is the same. Commands come back with the same errors etc.
Click to expand...
Click to collapse
FilipeET said:
I saw the image, your phone can be unlocked, its says flashing_unlocked, so, he got unlocked 1 time, Just run "fastboot flashing unlock" ir "fastboot oem unlock"
Click to expand...
Click to collapse
When running
Code:
fastboot flashing unlock
two times (adb tells me to) it comes back with
Code:
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.002s]
Finished. Total time: 0.002s
Although the first part looks like the command failed, the OKAY in the end kind of contradicts that. The problem here is that I obviously cannot access the OS to enable OEM Unlocking in the Developer settings.
When running
Code:
fastboot oem unlock
the output says
Code:
(bootloader) invalid boot state
OKAY [ 0.001s]
Finished. Total time: 0.002s
ogruendel said:
When running
Code:
fastboot flashing unlock
two times (adb tells me to) it comes back with
Code:
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.002s]
Finished. Total time: 0.002s
Although the first part looks like the command failed, the OKAY in the end kind of contradicts that. The problem here is that I obviously cannot access the OS to enable OEM Unlocking in the Developer settings.
When running
Code:
fastboot oem unlock
the output says
Code:
(bootloader) invalid boot state
OKAY [ 0.001s]
Finished. Total time: 0.002s
Click to expand...
Click to collapse
Can you start the recovery?
FilipeET said:
Can you start the recovery?
Click to expand...
Click to collapse
If by starting the recovery you mean using the Motorola Smart Assistant, then no. The behaviour is the same as it was before. If you mean something else, please let me know
Try this:
fastboot flash partition gpt.bin
FilipeET said:
Try this:
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
When running this the output again looks kind of weird, both looking like it failed and it working.
Code:
(bootloader) is-logical:partition: not found
(bootloader) is-logical:partition: not found
(bootloader) is-logical:partition: not found
Warning: skip copying partition image avb footer (partition partition size: 0, partition image size: 46592).
Sending 'partition' (45 KB) OKAY [ 0.168s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.081s]
Finished. Total time: 0.591s
ogruendel said:
When running this the output again looks kind of weird, both looking like it failed and it working.
Code:
(bootloader) is-logical:partition: not found
(bootloader) is-logical:partition: not found
(bootloader) is-logical:partition: not found
Warning: skip copying partition image avb footer (partition partition size: 0, partition image size: 46592).
Sending 'partition' (45 KB) OKAY [ 0.168s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.081s]
Finished. Total time: 0.591s
Click to expand...
Click to collapse
try to start the phone now
FilipeET said:
try to start the phone now
Click to expand...
Click to collapse
When trying to start it now, it bootloops on this screen for a while.
{
"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 left it on there and went to do something else and when I came back it showed this.
ogruendel said:
When trying to start it now, it bootloops on this screen for a while.
View attachment 5936813
I left it on there and went to do something else and when I came back it showed this.
View attachment 5936815
Click to expand...
Click to collapse
Oh!!! Flash the stock rom now!
If it doesn't flash the stock rom, blank flash it.
You flashed the partition scheme, so it needs to be "UnHardBricked"
FilipeET said:
Oh!!! Flash the stock rom now!
If it doesn't flash the stock rom, blank flash it.
You flashed the partition scheme, so it needs to be "UnHardBricked"
Click to expand...
Click to collapse
Is there some central place for stock roms that I can trust or do I have to look for them on various different websites?
Edit: I think I was able to download the stock ROM directly from the Rescue Assistant. Also which commands do I need to run in order to flash the stock rom?