Getting this error while flashing vbmeta.img from fastbootd
C:\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (9 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Tried:
1. Updated adb & fastboot drivers
2. Used USB 2.0 port
3. Latest platform tools
4. Keeping vbmeta instead vbmeta_a
Abhishek Junghare said:
... while flashing vbmeta.img from fastbootd
4. Keeping vbmeta instead vbmeta_a
Click to expand...
Click to collapse
Did you try flashing from bootloader fastboot rather than fastbootd?
Some partitions won't flash from within userspace fastbootd. I don't recall offhand if this is the case for the vbmeta partition(s).
You are correct though that you should specify vbmeta instead of vbmeta_a as the target partition.
After checking which slot is set to the current slot using;
fastboot getvar current-slot
or
fastboot getvar all
And then setting the current slot, if necessary, using;
fastboot --set-active=a
or
fastboot --set-active=b
My understanding is that the correct practice is to set the active slot with a fastboot command, and then specify only the partition name (without _a or _b) and fastboot will communicate with the bootloader to write the image to the actual partition name (including _a or _b), based on which slot is set as the active slot.
So, maybe try again using bootloader fastboot. Note that I don't have any experience with your device. The other response may be correct such that fastboot isn't active/working on your device at all.
goapy said:
Did you try flashing from bootloader fastboot rather than fastbootd?
Some partitions won't flash from within userspace fastbootd. I don't recall offhand if this is the case for the vbmeta partition(s).
You are correct though that you should specify vbmeta instead of vbmeta_a as the target partition.
After checking which slot is set to the current slot using;
fastboot getvar current-slot
or
fastboot getvar all
And then setting the current slot, if necessary, using;
fastboot --set-active=a
or
fastboot --set-active=b
My understanding is that the correct practice is to set the active slot with a fastboot command, and then specify only the partition name (without _a or _b) and fastboot will communicate with the bootloader to write the image to the actual partition name (including _a or _b), based on which slot is set as the active slot.
So, maybe try again using bootloader fastboot. Note that I don't have any experience with your device. The other response may be correct such that fastboot isn't active/working on your device at all.
Click to expand...
Click to collapse
fastboot getvar current-slot
current-slot:
Finished. Total time: 0.001s
fastboot --set-active=a
fastboot: error: Device does not support slots
I could use DSU Loader to flash GSI into slot b and successfully run it. But here it says it's not supported. And, A52s don't have fastboot mode, only fastbootd mode which I got from patching recovery.img
Arobase40 said:
IMO, Fasboot command not working with Samsung devices !
Click to expand...
Click to collapse
Yep, not working.
What about your TWRP for A52s btw? In progress?
(I'm done. I don't know how to patch images in AP.tar for disabling dm-verity, so can't even test. It's going to boot loop)
{
"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"
}
@Arobase40 @goapy
Fastboot commands are working in Samsung, but not entirely. Don't know what's issue is with slots flashing.
Tried flashing boot.img & recovery.img, same problem for both. Working for non-slot flashing, but failing if I target a slot.
Related
Hi everyone I have some questions if here in the forum we can solve them together
Without offending or underestimating the work of forum members and the people I have quoted, I only try to find solutions​
I have the Chinese version of the Motorola Z2 Play Model XT1710-11, so I wanted to remove the default firmware with ZUI!. by 7.1.1_NZS26.71-36
First try Unlocking the bootloader to work clean following the steps of many sites who recommend working with the unlocked bootloader But unfortunately when I tried to unlock it, it told me a message "BAD KEY", Look for this type of problems in the forum and other sites, according to the problem is because the supplier who I buy it in China, should give me the key, since it is likely that the seller has changed it. Unfortunately the seller does not answer me and I do not think he does.
1. So the first question is: Is it possible to do the flash even if you have this kind of problem?
First I use this command as the flash comes, blocked from the factory by the supplier:
fastboot flashing unlock
Click to expand...
Click to collapse
First of all make a backup of the firmware, and all the elements with the TWRP here: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Thanks to @Junior Passos , for his post, who helped me to do it, and in case someone has this phone model with the same "BAD KEY" problem. and be afraid of damaging it, it was tested and it worked normally.
The first problem in my head was that I did not like the operating system that brought by default my Z2-XT1710-11, because even if it was in Spanish or English there were places in the Chinese system
So, what I wanted was a clean and operable nougat.
I started looking for this exact model on the Internet and in the forum, I did not find a specific topic of this model, but in the comments of someone who had it, its name is: @LunaTheLuminous Who had a problem with their modems, https://forum.xda-developers.com/z2-play/help/fastboot-xt1710-11-china-mobile-modem-t3801969.
I did not have a modem problem because I had done backup, but I wanted to try to get to a clean rom and try to flash with comments from @KirMit from here: https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3. Unfortunately there were not the exact commands that he use, for avoid some kind of brick in my device.
Then I continued looking for the same model, and I found something similar that I decided to try : https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668. The original idea is to try to get a clean Nougat, According to @KirMit he managed to get a Clean nougat by using Two ROM, which I do not know From Here: https://forum.xda-developers.com/showpost.php?p=74833568&postcount=17.
I tried to find a clearer solution, because I had doubts about the exact commands that I use and roms, below in the comments, KirMit explains: that "the best manual is in the post" . I decided to use the @lexie90 tutorial https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668 Thanks with this ROM: "ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
and These commands:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
NOTE: The commands that are In red do not use them, I put them to see, the commands that I use and the ones that you do not have to use
Here I found a problem, because the bootloader has "BAD KEY" I can not close the OEM LOCK, and in the stage of flash recovery and flash boot it showed this message:
"Image signed with key bad key"
Click to expand...
Click to collapse
The flash of the firmware was made, I could go to the Nougat, Stock Running the modem, fingerprint reader, but when I turned on the phone I got a "bad key error message", looking for this type of problem is that the "logo.bin" file was necessary flash it, Unfortunately I could not find the original, but in the forum there are several people who have made their own logo.bin as: https://forum.xda-developers.com/moto-z/themes/logo-bin-to-remove-unlocked-warning-n-t3757030, and https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153 Thanks to @TobiPeter and @flashallthetime .
But when trying to flash it, and since they were from z play, the screen did not look good, therefore after several tests to eliminate this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To delete the message, from the motorola z2 play MODEL: XT1710-11, I did a flash with the logo that I made in the backup of the twrp.
https://drive.google.com/open?id=1OjPxy5k02MrH73SXZoXjI1sZCp83uFAr
With this command:
fastboot flash logo logo.emmc.win
Click to expand...
Click to collapse
2. My question is is there any way to make a flash clean and to install normal without any error with this type of BAD KEY problem?
But I did not just try that Rom, try several Stock Roms which I present to you in this list:
ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_RETAIL_7.1.1_NPSS26.118-19-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_NPSS26.118-19-1-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
CHINESE VERSION XT1710-08
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-36_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-97-41-9_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
Also try to change the command to try to see if there was the error, and use these: https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479, Thanks to @Kacike27 , Always avoiding:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
In the ROM of China I decided to make a full flash using all the commands, as @KirMit said in one of his comments.
https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3
Hi. Use this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
I flashed all using standard set of fastboot commands including modem flashing and erasing. You will boot in Chinese version, but still able to change a language to English in preferences menu (try to find a right menu by logos). It is still Android Nougat 7.1.1 with CH/EN only languages.
After that I flashed this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
But skip modem flashing and erasing. You will have multi language Android Oreo.
Enjoy.
Click to expand...
Click to collapse
Unfortunately I did not succeed the result was the same "bad key" errors and commands ("Image signed with key bad key", FAILED) Etc.
But as you will understand, I was not satisfied with the fact of all these mistakes, which were presented to me along the way, so I decided to do an update to OREO of both version ZUI!!!, and Stock of rom 7.1.1 ALBUS_NPSS26.118-19-4.
Then I followed the instructions in this post by @HTCDevil https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 Thanks!!!
I followed the following commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Following the advice of KirMit, I do not use the commands that are in red
By @KirMit
I confirm, that all is working after update on XT1710-11 (China Mobile), BUT! do not flash all - skip:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
If you want your modems and fingerprint sensor are still working!
Click to expand...
Click to collapse
The process that I did for fastboot, it did not work for me, unfortunately the same mistakes appeared in the previous roms, I have to add that when updating to Oreo, in both versions, ZUI and 7.1.1 (Stock ALBUS_NPSS26.118-19-4.), the fingerprint reader stopped working.
The device, started to "encrypt", when I wanted to downgrade to 7.1.1 ALBUS_NPSS26.118-19-4 or ZUI!!. In the command stage:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
The commands were throwing error, (failed), now the question is:
3.It is possible that I can not flash the Bootloader, nor do the gpt partition, because the device is encrypted or has the oreo bootloader
?
To finish I try to flash with RSD Lite, without any result, due to the error when it goes in :"fastboot flash partition gpt.bin", it can not execute the flash in the gpt, it stays stuck in that stage.
The testing of RSD lite was with the help of the following post:
https://forum.xda-developers.com/showpost.php?p=76454434&postcount=29 by @St.Nogiel
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/addison-factory-stock-images-t3736767/post75236696#post75236696 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194 by @KrisM22
Click to expand...
Click to collapse
end of the tests,
sorry for my English. greetings friends
I got a z2 play in secondhand.
This phone is from china mobile and the previous owner has flashed 7.1.1 .
Now the phone is stuck in 7.1.1 and it does not get get updated to 9.0.
Is there any way this can be done.
I contacted Lenovo and they say that the build number is not in the database .
I installed Oreo from this thread https://forum.xda-developers.com/moto-g5s/development/firmware-motorola-g5s-t3845848 (MONTANA_RETAIL_8.1.0_OPPS28.65-37-2-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) on my reteu G5S, using mfastboot.
The device has never been rooted, nor unlocked. There were no errors, and almost everything works great, except Google Pay. Play store also reports that the device is now not certified. I ran the Play store app "SafetyNet Check" and this reports Failure, due to CTS Profile match failure.. All other subtests of SafetyNet succeeds.
Google Pay is not critical, but it would have been nice to understand why CTS Profile Matchfails - since the device has never been rooted, nor bootloader unlocked. Future OTA updates will likely not fix the issue either, if at all any are offered with the SafetyNet failure.
Any ideas? Could it be because the stock ROM's software channel does not match the device (reteu)?
n808 said:
I installed Oreo from this thread https://forum.xda-developers.com/moto-g5s/development/firmware-motorola-g5s-t3845848 (MONTANA_RETAIL_8.1.0_OPPS28.65-37-2-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) on my reteu G5S, using mfastboot.
The device has never been rooted, nor unlocked. There were no errors, and almost everything works great, except Google Pay. Play store also reports that the device is now not certified. I ran the Play store app "SafetyNet Check" and this reports Failure, due to CTS Profile match failure.. All other subtests of SafetyNet succeeds.
Google Pay is not critical, but it would have been nice to understand why CTS Profile Matchfails - since the device has never been rooted, nor bootloader unlocked. Future OTA updates will likely not fix the issue either, if at all any are offered with the SafetyNet failure.
Any ideas? Could it be because the stock ROM's software channel does not match the device (reteu)?
Click to expand...
Click to collapse
try that:
go settings/apps¬ification/see all/Google Play Store/storage "clear data" and "clear cache"
and press "clear data"
that will reset data of play Store apk
Thankyou!
vaserbanix said:
try that:
go settings/apps¬ification/see all/Google Play Store/storage "clear data" and "clear cache"
and press "clear data"
that will reset data of play Store apk
Click to expand...
Click to collapse
Thanks for the advice. It did not work , though. I think because the Play Store gets its information from the SafetyNet test, which fails for some unknown reason. So after a couple of minutes the Play Store status was back to Device Not Certified. And for the same reason, Google Pay (not Play) will not work either.
{
"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 think I found the answer. I re-did the flashing, and noticed error message for both boot and recovery: Image signed with key bad key,
Since these were not distributed by Motorola, that's to be expected. And this means that SafetyNet will always fail, even though the phone is not rooted or unlocked.
After unlocking it, it is also no longer possible to lock it, since this requires properly signed boot and recovery images.
So this I learned: these so-called stock ROMs aren't really entirely stock, since they were not created by Motorola, are therefore not signed, and will (forever) break your device's ability to work with Google Pay. This is, until Motorola decides to make available stock ROMs themselves for newer devices. They do for some older phones. In other words, unlocking newer Motorola phones is currently an irreversible process.
Only the strictest apps are affected, like Google Pay.
Hopefully last post from me. It is indeed possible to re-lock the phone even though you initially get the "signed with bad key" error. Here are the commands to use (with the Oreo firmware listed in OP).
First:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem reboot
Click to expand...
Click to collapse
Flashing boot and recovery will display "signed with bad key" error.
Then here is the trick to the re-lock. After the above reboot is complete, run these commands, exactly as written.
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash boot boot.img
fastboot oem lock
Click to expand...
Click to collapse
After these succeed, you should get this message: "(bootloader) Lock complete! Flash signed images after reboot if needed". Your phone then reboots, and voila, phone is relocked. The SafetyNet/CTS Mismatch error persists, causing Google Pay to still not work. It is still unknown if it is possible to fix SafetyNet.
Hi, I used Carbon ROM on XT1670, when I wanted to change ROM I ran:
Code:
fastboot -w
And i got this:
{
"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 also tried to remove them:
In TWRP I tried to do something but all I get is something similar to this:
Am I missing something? Thanks for your help.
I've been reading the question and answer forum, apparently it's a problem with the encryption.
I don't have the Moto G5 right now, I can try it in a couple of hours, what other solution could I have anyway?
In twrp go to wipe
Then press the option on the right to format data
Reboot to recovery
Note this is different from wipe data from the advanced wipe menu.
The fastboot command would be
fastboot erase userdata
TheFixItMan said:
In twrp go to wipe
Then press the option on the right to format data
Reboot to recovery
Note this is different from wipe data from the advanced wipe menu.
The fastboot command would be
fastboot erase userdata
Click to expand...
Click to collapse
Hello, good (and bad) news
I did and now I have MTP for TWRP.
But still CMD says "Bootloader is logical @@@ not found"
"@@@" is depending on what you are trying to flash, be it system or recovery.
I was also able to change the filesystem I did it for DATA / CACHE / SYSTEM I went from FAT and then to EXT4 again.
Insert a ROM and it flashed without problems but it starts again in fastboot, the same if I do it with ADB Sideload.
I also tried flashing Stock ROM, everything seems to be written without problem but with the first line of "Bootloader logical ... not found" and again start in fastboot.
It makes me believe that something is still encrypted.
I mean this.
I also tried
Code:
fastboot format:ext4 userdata
But I have this:
Bootloader is logical not found - this is normal output
Why are you trying to change formats? You are going to have issues especially with encryption. Use twrp to format not fastboot if you are messing with formatting but make sure you know what you are doing!
TheFixItMan said:
Bootloader is logical not found - this is normal output
Why are you trying to change formats? You are going to have issues especially with encryption. Use twrp to format not fastboot if you are messing with formatting but make sure you know what you are doing!
Click to expand...
Click to collapse
I flash a rom (no apparent problem, even Stock ROM) but it only boots to fastboot or the robot with an open belly.
What exactly should I do, I will follow step by step, I really need to get it back. Thank you very much for your help.
Hello again, I saw you in another post that apparently has the same problem as me, it is this:
Decryption unsuccessfull
Hi guys, I have a problem with my motorola moto g5. It turns out that I upgraded to android oreo and at the time of associating the fingerprint I asked for a pin for security which I put. En el twrp me pide el pin, el cual ingresa y ya podia...
forum.xda-developers.com
I have the same bugs, do you think I should run the command to decrypt?
Dislekzi4 said:
Ok, I'll get to the point.
I flash a rom (no apparent problem, even Stock ROM) but it only boots to fastboot or the robot with an open belly.
What exactly should I do, I will follow step by step, I really need to get it back. Thank you very much for your help.
Click to expand...
Click to collapse
In twrp format data
That is by selecting wipe
Then the option on the right to format data
Reboot to recovery
Everything should now be mountable
Make sure you are flashing stock rom correctly
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Making sure you are flashing the same or newer firmware version than already on your phone
If your phone keeps booting to recovery (android with an open stomach or twrp) then do this
Boot into twrp then connect phone to PC and in cmd/terminal type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Reboot and your device will boot normally (assuming you have a working rom)
Hi, it work!
Thank you very much for your time and help, I am very grateful, for a moment I thought it was really a hardware problem.
I get device unauthorized. Please check the confirmation dialog on your device. and it won't let me do anything
Rod_Ems said:
I get device unauthorized. Please check the confirmation dialog on your device. and it won't let me do anything
Click to expand...
Click to collapse
Enable adb debugging on your device in dev options
Make sure you are using the latest platform tools
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip
Navigate your cmd window to to the platform tools directory
In cmd type
adb devices
Look on your phone and a window will pop up asking you to confirm authorisation - tick the box to allow always if you want to
Then type
adb devices
And your device is authorised
TheFixItMan said:
In twrp format data
That is by selecting wipe
Then the option on the right to format data
Reboot to recovery
Everything should now be mountable
Make sure you are flashing stock rom correctly
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Making sure you are flashing the same or newer firmware version than already on your phone
If your phone keeps booting to recovery (android with an open stomach or twrp) then do this
Boot into twrp then connect phone to PC and in cmd/terminal type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Reboot and your device will boot normally (assuming you have a working rom)
Click to expand...
Click to collapse
mine show the following error message: device '(null)' not found
danniel_sx said:
mine show the following error message: device '(null)' not found
Click to expand...
Click to collapse
Either
Your phone is not connected to pc
Faulty cable
You haven't installed Motorola USB drivers
You are using the wrong commands
If in fastboot mode type
fastboot devices
If in recovery mode type
adb devices
Your device should be listed if correctly connected
I found a solution, i'm argentinian so sorry if my english is bad
the fastboot menu of the combination power + volume down have no permissions to all modifications
You have to acces to the recovery fastboot menu, to do this, move to "recovery mode" enter here with power
Now if in the screen appears "No command" you have to press power + volume down for 3 sec and press vol up without press the another 2, then release the 3 buttons
Now go to "fastboot" in the recobery mode, and ta daaa. You have permissions
Hi all,
Just wondering if anyone might be able to lend a hand... Im trying to flash back my Pixel C back to stock (currently running TWRP and build from [ROM][UNOFFICIAL][LineageOS]18.
For some reason, when running the flash-all script or manually flashing the Booloader img, it comes back with "writing 'bootloader' failed (remote 'unsupported command')".
The tablet still boots into the Lineage OS (at least its not a brick... yet..) but really like to try and get it back to stock if I can..
if it helps..
{
"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"
}
When running the flash-all bat file:
If you have no working recovery there is no way to fix this problem (at the moment).
Instead, if you have a working recovery, you could use the following fix from adb shell:
fwtool vbnv write dev_boot_fastboot_full_cap 1
See also:
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command" Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock I used TWRP and SuperSU to root and modify the buildprops to enable and get...
forum.xda-developers.com
bernardomarx said:
If you have no working recovery there is no way to fix this problem (at the moment).
Instead, if you have a working recovery, you could use the following fix from adb shell:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Thanks bernardomarx! That seemed to have done the trick!!
Yeah - Luckily TWRP recovery was still accessable, typed in the command within TWRP Terminal. And followed the post you linked to
Essentially after doing the fwtool command in a cmd window:
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
Flashed the bootloader:
fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
I then had to extract the img zip file and manually flash each img file:
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
>fastboot flash vendor vendor.img
Many thanks for entering the details of how you recovered your Pixel C. I had the same problem when un-installing TWRP. I did performed the same steps as you, and the tablet is back up and running!
Many thanks for documenting it here!
DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE
I've just unbricked an RMX3474 (Realme 9 5G with unlocked bootloader) using this method. It was bricked (bootloader boot loop) following a bad downgrade by mistake from RUI4 to RUI3 (there's actually no RUI4 ROM available in .ofp format for the RMX3474GDPR).
QPST/QFIL is a powerful (and therefore dangerous) tool, which is why in my opinion it should be reserved for hard unbrick, i.e. for smartphones that only have access to EDL (Emergency DownLoad) mode. I think its current democratisation is not a good thing. This remains my humble opinion, of course. For a soft bricked smartphone, I'm still looking for a "fastboot" solution. LOL, that's just common sense
So (I call back : unlocked bootloader needed).
1. Download the lastest android-tools : here
2. Download the OTA update for the last stock ROM installed on the smartphone :
2a. realme-ota
2b. Type the command :
Code:
realme-ota -v4 -i IMEI1 IMEI2 --old-method RMX3363 RMX3363_11.firmware.XX_0000_000000000000 RUI_version region
2c. Where : - -i IMEI1 IMEI2 = for your smartphone (optional), firmware = letter of firmware, XX = number of firmware, RUI_version = 2, 3 or 4 and region = your smartphone region
2d. For example, for my smartphone, the last "F" firmware, RUI4 and EUEX region :
Code:
realme-ota -v4 -i IMEI1 IMEI2 --old-method RMX3363 RMX3363_11.F.00_0000_000000000000 4 01000100
2e. Result of the command is : "foreign_my_manifest_RMX3363_11.F.07_3070_202305171723.44.71d53b2c_1_cf16f9cb6b61168cd0959cff607e3b32"
2f. You'll find the download link for the OTA update in the result, just below this line
3. Extract .img files from payload.bin :
3a. payload-dumper-go
3b. Type the command :
Code:
payload-dumper-go /path/to/payload.bin
4. Put all files in the same directory (android-tools & extracted payload .img files)
4a. Example for RMX3363GDPR-F07 :
{
"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"
}
5. Boot your smartphone into bootloader and connect it to the PC USB port
6. You need to enter fastbootd mode (to be authorised to flash critical partitions), so open a terminal and type the following command :
Code:
fastboot reboot fastboot
7. Begin with slot a :
Code:
fastboot --set-active=a
8. Start the flash of the .img files (the number of .img files may vary depending on the smartphone model and the version of OTA update) :
Code:
fastboot flash file1 file1.img
fastboot flash file2 file2.img
fastboot flash file3 file3.img
(... etc)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
9. Switch to slot b :
Code:
fastboot --set-active=b
10. Relaunch the flash of the .img files
11. Switch slot a back to active :
Code:
fastboot --set-active=a
12. Reboot the smartphone :
Code:
fastboot reboot
Note : I had 2 errors during the flashes (1 on slot a, 1 on slot b, not the same). On slot a, "Writing 'modem_a' FAILED (remote: 'Operation not permitted')". On slot b, I can't remember (a problem of insufficient space for a file). I tried several things but couldn't get round these errors. Nevertheless, the smartphone rebooted correctly with RUI4
After that, you can easily patch boot.img and vendor_boot.img (optional) files with Magisk, flash them again via fastboot and obtain root mode.
Have a nice day !