Related
I have am unlocked bootloader with TWRP recovery.
My company forces encryption and I accidentally encrypted my Verizon HTC One. I used it for a while and I wanted to update the ROM. I did a hard reset from TWRP but that did not remove the encryption. I did the advanced wipe and chose every option on the list. Now the phone wont boot up. I can still get into recovery but I can't do anything from recovery. None of the partitions can be mounted so the wipes do not work.
my questions:
Is there a way to remove the encryption from TWRP?
If not, is there a way to remove encryption from fastboot?
I ran these and both failed:
fastboot.exe -w
erasing 'userdata'...
FAILED (remote: not allowed)
fastboot.exe flash zip update.zip
sending 'zip' (1086411 KB)...
OKAY [ 39.503s]
writing 'zip'...
FAILED (remote: not allowed)
What options do I have at this point to restore the phone?
Thanks,
Resolved
To give more information on this, the option "Format Data" under "Wipe" in TWRP would not remove the encryption. It kept giving an error that it could not access /data.
Through fastboot I saw that I could only access and flash /system and /boot. I could do anything with /data and /cache.
I am not certain if this was a TWRP issue or not but for those interested I fixed this by flashing clockwork recovery through fastboot. From clockwork I was able to flash wipe /data and /cache and that took the encryption off. I then flashed the ROM using adb sideloade feature in recovery.
killershot20 said:
I have am unlocked bootloader with TWRP recovery.
My company forces encryption and I accidentally encrypted my Verizon HTC One. I used it for a while and I wanted to update the ROM. I did a hard reset from TWRP but that did not remove the encryption. I did the advanced wipe and chose every option on the list. Now the phone wont boot up. I can still get into recovery but I can't do anything from recovery. None of the partitions can be mounted so the wipes do not work.
my questions:
Is there a way to remove the encryption from TWRP?
If not, is there a way to remove encryption from fastboot?
I ran these and both failed:
fastboot.exe -w
erasing 'userdata'...
FAILED (remote: not allowed)
fastboot.exe flash zip update.zip
sending 'zip' (1086411 KB)...
OKAY [ 39.503s]
writing 'zip'...
FAILED (remote: not allowed)
What options do I have at this point to restore the phone?
Thanks,
Click to expand...
Click to collapse
Hi Guys,
Pixel keeps bootlooping to TWRP. I unlocked bootloader, rooted with the boot-to-root, been using the phone for a few hours, then decided to install TWRP. I booted the img, then in TWRP flashed the zip file. (RC1) Did a wipe/factory reset and it just bootloops into TWRP.
Trying to figure out how to get back to stock. I only have a mac and can't seem to find any good instructions on how to do it. I downloaded the the stock image but I don't know how to flash the whole image through fastboot. Any help how to get out of this bootloop would be appreciated.
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
I was reading through that thread, but I only have access to a mac, and I can't figure out to flash the whole image...
CZ Eddie said:
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Click to expand...
Click to collapse
flo7002 said:
I was reading through that thread, but I only have access to a mac, and I can't figure out to flash the whole image...
Click to expand...
Click to collapse
If you have a MAC then you'll probably want to learn how to create a Windows virtual machine.
Everyone with a MAC should know this.
Just like everyone with a Windows machine should know how to create a Linux virtual machine.
Sorry I can't help beyond giving annoying advice.
CZ Eddie said:
If you have a MAC then you'll probably want to learn how to create a Windows virtual machine.
Everyone with a MAC should know this.
Just like everyone with a Windows machine should know how to create a Linux virtual machine.
Sorry I can't help beyond giving annoying advice.
Click to expand...
Click to collapse
No worries... I guess I should try to install windows on my mac as well...
I tried this command: fastboot -w update image-marlin-nmf26q.zip (and I get this error)
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
fastboot(3918,0xa53391c0) malloc: *** mach_vm_map(size=1603837952) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1602232032 bytes
error: update package missing system.img
flo7002 said:
No worries... I guess I should try to install windows on my mac as well...
I tried this command: fastboot -w update image-marlin-nmf26q.zip (and I get this error)
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
fastboot(3918,0xa53391c0) malloc: *** mach_vm_map(size=1603837952) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1602232032 bytes
error: update package missing system.img
Click to expand...
Click to collapse
Most of that was normal, if you look at step #13 in my thread. I pasted the complete output of what the normal flash looks like for comparison.
The rest doesn't look familiar to me?
CZ Eddie said:
Most of that was normal, if you look at step #13 in my thread. I pasted the complete output of what the normal flash looks like for comparison.
The rest doesn't look familiar to me?
Click to expand...
Click to collapse
I got a little further. I noticed I had an older version of adb/fastboot.
Now it get all the way till the end and then this:
sending 'userdata' (145102 KB)...
OKAY [ 3.197s]
writing 'userdata'...
OKAY [ 2.444s]
erasing 'cache'...
(bootloader) Erasing active slot "_b"
FAILED (remote: Partition table doesn't exist
)
finished. total time: 117.266s
Any clue what's going on there? Should I flash boot.img on both A & B partitions? I haven't messed around with the partitions at all...
flo7002 said:
erasing 'cache'...
(bootloader) Erasing active slot "_b"
Any clue what's going on there? Should I flash boot.img on both A & B partitions? I haven't messed around with the partitions at all...
Click to expand...
Click to collapse
Not sure about those entries.
I do recommend flashing boot.img to both A & B as a cautionary/preventive measure.
flo7002 said:
I got a little further. I noticed I had an older version of adb/fastboot.
Now it get all the way till the end and then this:
sending 'userdata' (145102 KB)...
OKAY [ 3.197s]
writing 'userdata'...
OKAY [ 2.444s]
erasing 'cache'...
(bootloader) Erasing active slot "_b"
FAILED (remote: Partition table doesn't exist
)
finished. total time: 117.266s
Any clue what's going on there? Should I flash boot.img on both A & B partitions? I haven't messed around with the partitions at all...
Click to expand...
Click to collapse
This whole string of outputs is completely normal. Disregard the "erasing active slot" and "failed remote partition table" message.
You should now be able to boot the phone up and it will be completely restored to factory spec, if not, go-to your stock recovery, and delete cache and user data, and try again.
I wouldn't worry about flashing boot.img to the other partition unless your phone still refuses to boot to Android.
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!
Thank you very much. I will try it.
BL1ND4D0 said:
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!
Click to expand...
Click to collapse
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
[email protected] said:
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.
tys0n said:
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.
Click to expand...
Click to collapse
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?
[email protected] said:
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?
Click to expand...
Click to collapse
Did you follow all instructions from twrp thread. like flashing modified vbmeta and wipe data before booting twrp?
Also take a look at the original thread for one vision as it has a newer zip that contains only one modified vbmeta.img instead of two different ones in the older zip that is posted in one action's twrp thread.
I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.
goofball2k said:
I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.
Click to expand...
Click to collapse
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.
[email protected] said:
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.
Click to expand...
Click to collapse
You don't need to modify vbmeta.img. I am using the older version of the root Moto Vision package, which has a vbmeta.img file, and a patched vbmeta.img file.
For the modified boot img, I downloaded the full image from https://mirrors.lolinet.com/firmware/moto/troika/official/
Extract, and then take the boot.img file, you will want that saved to a phone that has Magisk installed.
Follow these instructions to patch
https://www.ytechb.com/how-to-patch-a-file-in-magisk-manager/
Once you have that, you will want that patched file into the fastboot directory on your computer. You will also want the vbmeta and the patched vbmeta img files (from the root moto vision package) in this directory. I have not used the updated version, I am using the older. I don't know about using the newer package which only has 1 vbmeta file.
Put your phone into fastboot mode.
Flash the vbmeta.img file, then the magisk patched boot file, then the vbmeta patched file. Then do a fastboot wipe of the phone.
Reboot the phone.
Set it up again, install magisk manager, then open it, and it should ask to configure. Let it do that, it should reboot and after that, you should be rooted.
[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know
Thank you
binary**# said:
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know
Click to expand...
Click to collapse
Thank you very much for your input.
How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?
Polnareff said:
How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?
Click to expand...
Click to collapse
You aren't flashing, your command is trying to boot from vbmeta.img. You are missing the flashing command.
Red Magic 8 Pro stuck fastboot
It no longer has sideload mode in recovery
Did you somehow change your slot? If you haven't upgraded the firmware, then the 2nd slot is empty, and it will not boot anything.
BoJaXz said:
Did you somehow change your slot? If you haven't upgraded the firmware, then the 2nd slot is empty, and it will not boot anything.
Click to expand...
Click to collapse
I switched both slots, but I can't boot up
Mr.PvT said:
I switched both slots, but I can't boot up
Click to expand...
Click to collapse
What steps did you do before you got stuck in fastboot?
BoJaXz said:
What steps did you do before you got stuck in fastboot?
Click to expand...
Click to collapse
I patched the root boot file then flashed it failed, then I flashed each file in the payload, I deleted the super, the files in the super can't be flashed oddly, are you rooted, can backup the whole partition help me
Thank you
Mr.PvT said:
I patched the root boot file then flashed it failed, then I flashed each file in the payload, I deleted the super, the files in the super can't be flashed oddly, are you rooted, can backup the whole partition help me
Thank you
Click to expand...
Click to collapse
Did you oem unlock before you tried flashing? You may have to flash the whole image
BoJaXz said:
Did you oem unlock before you tried flashing? You may have to flash the whole image
Click to expand...
Click to collapse
I unlocked the bootloader, I flashed all the files in the payload but still can't boot, hang fastboot or boot to the logo and then shut down
I need someone to back up all my partitions, that's the only way I can do it
Mr.PvT said:
I unlocked the bootloader, I flashed all the files in the payload but still can't boot, hang fastboot or boot to the logo and then shut down
I need someone to back up all my partitions, that's the only way I can do it
Click to expand...
Click to collapse
Did you flash boot.img or init_boot.img?
It sounds like you are booting the wrong slot.
BoJaXz said:
Did you flash boot.img or init_boot.img?
It sounds like you are booting the wrong slot.
Click to expand...
Click to collapse
I flashed those 2 files and changed both slots but failed to start the phone
I faced with the problem by locking the bootloader with init_boot.img for magisk. Then I unlocked it again and switched aactive slot to b and then to a in "Fastboot Enhance" tool. After that my phone entered to the system.
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
@Mr.PvT did you ever make any progress with this? I am in the same boat now. Flashed a GSI and tested it out. DIdnt like it so flashed the 3.18 Payload.bin thru Fastboot enhance and am stuck on Bootloader. Cant access anything else as no matter what I choose it boots to bootloader.
DarkestSpawn said:
@Mr.PvT did you ever make any progress with this? I am in the same boat now. Flashed a GSI and tested it out. DIdnt like it so flashed the 3.18 Payload.bin thru Fastboot enhance and am stuck on Bootloader. Cant access anything else as no matter what I choose it boots to bootloader.
Click to expand...
Click to collapse
I also went from a GSI to stock ROM and this worked, some steps may be unnecessary:
In bootloader change active slot to a
Flash all of payload.bin images
Reboot to fastboot and flash all of payload images
Reboot to recovery
Hold volume down for a few seconds to enable sideload
Connect the phone to a pc and ADB sideload NX729J-update.zip
Then wipe data and reboot
Also did your calls and messages work when using the GSI?
edzchen said:
I also went from a GSI to stock ROM and this worked, some steps may be unnecessary:
In bootloader change active slot to a
Flash all of payload.bin images
Reboot to fastboot and flash all of payload images
Reboot to recovery
Hold volume down for a few seconds to enable sideload
Connect the phone to a pc and ADB sideload NX729J-update.zip
Then wipe data and reboot
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
In bootloader:
fastboot flash odm odm.img
target reported max download size of 805306368 bytes
sending 'odm' (1284 KB)...
OKAY [ 0.032s]
writing 'odm'...
FAILED (remote: (odm_a) No such partition)
finished. total time: 0.038s
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system_dlkm system_dlkm.img
target reported max download size of 805306368 bytes
sending 'system_dlkm' (428 KB)...
OKAY [ 0.011s]
writing 'system_dlkm'...
FAILED (remote: (system_dlkm_a) No such partition)
finished. total time: 0.018s
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system_ext system_ext.img
target reported max download size of 805306368 bytes
sending 'system_ext' (730792 KB)...
OKAY [ 17.204s]
writing 'system_ext'...
FAILED (remote: (system_ext_a) No such partition)
finished. total time: 17.211s
Nothing happens when I flash system & vendor.
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash vendor_dlkm vendor_dlkm.img
target reported max download size of 805306368 bytes
sending 'vendor_dlkm' (93564 KB)...
OKAY [ 2.181s]
writing 'vendor_dlkm'...
FAILED (remote: (vendor_dlkm_a) No such partition)
finished. total time: 2.187s
In Fastbootd:
Everything that failed in bootloader, flashed beside system. Could only flash _b slots. Nothing seems to exist for slot a. I did not fastboot format or erase anything to my knowledge unless Fastboot Enhance did so when I flashed the playload.bin thru it without having logs on to watch what it did. If it formated or erased any partitions can they be recreated?
And last when in Recovery:
F:\Files\Downloads\RM8P>adb sideload NX729J-update.zip
loading: 'NX729J-update.zip'
error: closed
DarkestSpawn said:
Everything that failed in bootloader, flashed beside system.
Click to expand...
Click to collapse
What is the error when flashing system?
If it has something to do with not being able to resize the system partition, check this link:
Fix FAILED (remote: 'Not enough space to resize partition')
In this comprehensive tutorial, we will show you the steps to fix the FAILED (remote: 'Not enough space to resize partition') error.
www.droidwin.com
I had this problem too.
Which GSI were u on
edzchen said:
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
edzchen said:
What is the error when flashing system?
If it has something to do with not being able to resize the system partition, check this link:
Fix FAILED (remote: 'Not enough space to resize partition')
In this comprehensive tutorial, we will show you the steps to fix the FAILED (remote: 'Not enough space to resize partition') error.
www.droidwin.com
I had this problem too.
Which GSI were u on
Click to expand...
Click to collapse
I just retried in bootloader with a new outcome this time:
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/6 (786364 KB) OKAY [ 18.742s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
I copied the fastboot.exe from fastboot enchanced to the directory of the extracted payload.bin. Was able to recreate partitions. Am attempting to recover from potential brick.
I tried LineageOS TD-based. Didnt attempt calls or messages. Was just checking out the feel of the rom and its capabilities.
Can someone run this fastboot command in bootloader and fastbootd and save the results in a text file?
fastboot getvar all
Omit the serial number in bootloader and fastbootd's printout.
DarkestSpawn said:
Can someone run this fastboot command in bootloader and fastbootd and save the results in a text file?
fastboot getvar all
Omit the serial number in bootloader and fastbootd's printout.
Click to expand...
Click to collapse
Here you go:
ugene1980 said:
Here you go:
Click to expand...
Click to collapse
So looking thru this, the only difference I have is:
(bootloader) partition-size:userdata: 0x718BCD3000 Mine
(bootloader) partition-size:userdata: 0x35F5CD3000 Yours
as well as:
(bootloader) slot-successful:a:yes Yours
(bootloader) slot-successful:a:no Mine
but thats because it hasnt successfully booted since last flash.
I also need the fastbootd's printout. The one provided was from bootloader. The one from fastbootd will give logical partitions and has slot info.
edzchen said:
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
Did you install carrier serivces from google play, setup APN settings for your carrier and Installing new IMS package: Treble Settings -> IMS features -> install IMS for Qualcomm -> install package. I cant remember if that was in there. Still trying to get booted again
DarkestSpawn said:
Did you install carrier serivces from google play, setup APN settings for your carrier and Installing new IMS package: Treble Settings -> IMS features -> install IMS for Qualcomm -> install package. I cant remember if that was in there. Still trying to get booted again
Click to expand...
Click to collapse
Yeap I did all that but calls and texts only half worked. I could do calls but no audio and I could send texts but couldn't receive. Was the main reason why I switched back to stock
I have a big problem with my device.
After a custom rom update, the device no longer booted and I received the message "your device is corrupted and cannot be trusted .."
After restarting in the bootloader (fastboot mode) I wanted to flash the last factury images
(raven-tq2a.230305.008.e1-factory-def2deef.zip).
During the process, I received the error message:
"Resizing 'vendor_b' FAILED (remote: 'Not enough space to resize partition')"
After a few "attempts to heal" I managed to flash the system in slot a and a reboot started the system.
But the vendor partition in slot b seems to be broken...?
Thank you very much in advance for any help!
Try using the Android flash tool.
Thanks for the tip.
the system boots - I mean the system runs in slot a. But I would really like to know what the error message is all about. Resizing 'vendor_b' FAILED (remote: 'Not enough space to resize partition')
What will happen, when I do an OTA-update and the system tries to install in slot b?
MartinN6 said:
Thanks for the tip.
the system boots - I mean the system runs in slot a. But I would really like to know what the error message is all about. Resizing 'vendor_b' FAILED (remote: 'Not enough space to resize partition')
What will happen, when I do an OTA-update and the system tries to install in slot b?
Click to expand...
Click to collapse
try switching active slot to b and see what happens
thanks for the tip. The device appears to be "healed" again. I first flashed the factury image in slot a. now switched to slot b in the bootloader and flashed the factury image here as well.