XT1941-4 stuck in bootloader with flashing locked - Motorola One Questions & Answers

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?

Related

Unlock Nexus Q

Unlocking Your Nexus Q
To unlock your device
1. cd to platform-tools
2. Reboot to the bootloader - adb reboot bootloader
3. Unlock your device* (with fastboot tool type): fastboot oem unlock
*You will have to accept and erase all the user data on the tablet.
*You must run this as sudo in Linux
Credits to FadedLite (very similar steps)
Figuring out the rooting next
If you just need "su"....
1. Download su from your busybox installation from say Galaxy Nexus.
2. Download the modified clockworksmod for Nexus Q that this guy put together:
bliny.net/blog/post/How-to-Root-Nexus-Q-%28Temporarily%29.asp
3. Boot into that recovery image will give you write access to /system
4. adb push su into /system/xbin/su
Did you already have your nexus Q in debug mode? I do not have the slider button on my Nexus 7 to put it into debug mode. It's not recognized in "adb devices" or "fastboot devices"
EDIT ***
I found out that the USB Debugging menu in the Nexus Q app shows up when you turn on Developer Options in the Settings > Developer Options menu of Jellybean on the Nexus 7. You might want to test this as well on your variety of devices.
Just me that thinks this thing needs google TV?
nevermind it worked now
Stuck in oem unlock
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
took me a few tries to get it but it needs to be entered within five seconds of the first command
enriquealo said:
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
Click to expand...
Click to collapse
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
silfa718 said:
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
Click to expand...
Click to collapse
the easiest way, assuming you are running windows, is to enter the comands once, and then just use the up arrow key to do it again. also, you may want to be sure its not already unlocked "fastboot getvar unlocked" will return "yes" if unlocked

Xiaomi MI A3 stuck on bootloader

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).

PLEASE help me! Google Pixel 2 got stuck in bootloader!

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

partition table broken

Hi all,
when installing lineage 18.1 I successfully screwed up my MOTO G8. When rebooting after all installalation steps being successfull, it says
​No valid operation system could be found. The device will not boot.​
Booting to fastboot again I tried to flash again, but this time I get
​fastboot set_active a​Setting current slot to 'a' FAILED (remote: '')
fastboot: error: Command failed​​Trying to to flash something does not work as well, e.g.
fastboot flash recovery recovery.img​ending 'recovery' (24924 KB) OKAY [ 0.752s]​Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed​​Apperently the partition table appears to be broken. Can I restore it?
badkey212 said:
Hi all,
when installing lineage 18.1 I successfully screwed up my MOTO G8. When rebooting after all installalation steps being successfull, it says
​No valid operation system could be found. The device will not boot.​
Booting to fastboot again I tried to flash again, but this time I get
​fastboot set_active a​Setting current slot to 'a' FAILED (remote: '')​fastboot: error: Command failed​​Trying to to flash something does not work as well, e.g.
​fastboot flash recovery recovery.img​ending 'recovery' (24924 KB) OKAY [ 0.752s]​Writing 'recovery' (bootloader) Invalid partition name recovery​FAILED (remote: '')​fastboot: error: Command failed​​Apperently the partition table appears to be broken. Can I restore it?
Click to expand...
Click to collapse
Does the bootloader say "flashing_locked" now?
Try
Code:
fastboot flash partition gpt.bin
sd_shadow said:
Does the bootloader say "flashing_locked" now?
Try
Code:
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
That helped, thank you!

Question I did "fastboot erase system" and bricked how can I save myself?

I ran the command in the title and now I can't get out of fastboot and can't get into fastbootd.
I am an amateur and don't even know what this command means. I just wanted to install LineageOS on my xiaomi redmi note 10 je with GSI. I tried to install the downloaded img file for GSI with the command fastboot flash system lineage-19.1-202206130-UNOFFICIAL-arm64_bvS.img but it didn't work. How do I get it to work with MIUI or whatever it is for now? Please.
In case you're wondering, I got the above GSI file from https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
i_plevra said:
I ran the command in the title and now I can't get out of fastboot and can't get into fastbootd.
I am an amateur and don't even know what this command means. I just wanted to install LineageOS on my xiaomi redmi note 10 je with GSI. I tried to install the downloaded img file for GSI with the command fastboot flash system lineage-19.1-202206130-UNOFFICIAL-arm64_bvS.img but it didn't work. How do I get it to work with MIUI or whatever it is for now? Please.
In case you're wondering, I got the above GSI file from https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
Click to expand...
Click to collapse
hello ... if you are currently on fastboot mode and your pc can detect it then you can use MiFlash Tool to install MIUI again...
if you have adb & fastboot (and drivers) installed run fastboot devices with the phone connected , if your phone is recognized then go ahead
one question ... your phone came with Global MIUI or other MIUI Region? (India , EEA , Indonesia , etc)
and please DO NOT RUN commands that you don't know about.. fastboot erase commands are common to hard brick phones
you must ask before running any command
if your pc have all the drivers , i assume u have it coz u ran the command . for gsi , u need to disable vbmeta 1st , later you can flash and boot the los18/19.1 gsi . fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img get vbmeta.img through official MIUI fastboot rom.
alonsoj636 said:
hello ... if you are currently on fastboot mode and your pc can detect it then you can use MiFlash Tool to install MIUI again...
if you have adb & fastboot (and drivers) installed run fastboot devices with the phone connected , if your phone is recognized then go ahead
one question ... your phone came with Global MIUI or other MIUI Region? (India , EEA , Indonesia , etc)
and please DO NOT RUN commands that you don't know about.. fastboot erase commands are common to hard brick phones
you must ask before running any command
Click to expand...
Click to collapse
This smartphone is a Japan-only model for a company called au, but probably a global version is available. The size is a little different but the base is redmi note 10 5g I just checked and it seems to be 5g I'm not confident I'll use miflash. It's a hassle to borrow a phone from a family member, stick a sim in it and have to receive an authentication SMS.
pihpih95 said:
if your pc have all the drivers , i assume u have it coz u ran the command . for gsi , u need to disable vbmeta 1st , later you can flash and boot the los18/19.1 gsi . fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img get vbmeta.img through official MIUI fastboot rom.
Click to expand...
Click to collapse
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
now I can't use Windows for some reasons so am using m1 mac, this pc can't use the miflash so am trying GSI boot in a while
i_plevra said:
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
Click to expand...
Click to collapse
big problem...
your device is locked which means that flashing anything (vbmeta , recovery) or use MiFlash Tool will not be possible because unlocked bootloader is compulsory
i_plevra said:
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
Click to expand...
Click to collapse
do you still have mi recovery, or only have fastboot?
LR7875 said:
do you still have mi recovery, or only have fastboot?
Click to expand...
Click to collapse
if mi recovery means the recovery mode, fastboot reboot recovery and fastboot reboot bootloader just make appear the fastboot display.
i_plevra said:
if mi recovery means the recovery mode, fastboot reboot recovery and fastboot reboot bootloader just make appear the fastboot display.
Click to expand...
Click to collapse
and does fastboot oem unlock or fastboot oem unlock_critical work
LR7875 said:
and does fastboot oem unlock or fastboot oem unlock_critical work
Click to expand...
Click to collapse
both were same result.
fastboot oem unlock_critical
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
have u apply to unlock bootloader through official method ?
i_plevra said:
both were same result.
fastboot oem unlock_critical
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...oken-verify-failed-reboot-the-device.4300755/ this is for redmi note 10 pro but is worth to read. maybe it can help

Categories

Resources