adb – FAILED (remote: Partition should be flashed in fastbootd) PIXEL 3XL Android 11 FAILED (remote: ‘Operation not permitted’)

Could someone help me with the following problem:

I want to flash my pixel 3XL with AOSP precompiled images in android 11, but it gives me this error:

enter image description here

I have fastboot version 1: 8.1.0 + r23-5 ~ 18.04
and adb version:
Android Debug Bridge version 1.0.39
Version 1: 8.1.0 + r23-5 ~ 18.04

I have a problem when executing fastboot flash on my pixel 3xl, it returns the following error:

Writing sparse ‘system_a’ 4/6 FAILED (remote: ‘Operation not permitted’)

enter image description here

someone help me with this error.

adb – FAILED (remote: Partition should be flashed in fastbootd) PIXEL 3XL Android 11

Could someone help me with the following problem:

I want to flash my pixel 3XL with AOSP precompiled images in android 11, but it gives me this error:

enter image description here

I have fastboot version 1: 8.1.0 + r23-5 ~ 18.04
and adb version:
Android Debug Bridge version 1.0.39
Version 1: 8.1.0 + r23-5 ~ 18.04

Could you help me!?

Can an android phone that is flashed to a trusted safe rom still be malicious?

I’m in the market for a new phone. The cheapest ones with decent specs are from China. Unfortunately I’ve read articles of phones sending data back to China for spying purposes.

The phone I am looking to buy is the Xiaomi Poco X3 NFC which has had their code open sourced https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/surya-q-oss.

I will be flashing it to one of the most trusted sources either Pixel Experience or Lineage OS. Let’s assume that neither of these are malicious.

Then my question is, is it possible, that despite me flashing the software to something safe, that it still is malicious? The reason I ask is because I’m wondering what happens if there is a malicious bootloader and a protected part of the memory or storage that isn’t removed. Then the malicious bootloader could initially load this part of memory / storage and initiate something malicious (ie a program that sends data to china) and then proceed to load the custom image that I’ve flashed. Im trying to understand whether this is even technically possible. If it is, how would I know if this was happening? Since the code is open source, can I check what is on the phone matches the open source code? Does the open source code even matter if there is some hardware that acts maliciously before loading the rest of the software? What would be some clues this was the case (either that something malicious happens initially or that a part of memory / storage is reserved for something malicious)?

adb – Flashed magisk_patched_boot.img as fastboot flash recovery…Phone stuck on Powered by Android

I was trying to root my Micromax Q440 and I tried to follow the steps ie;

1: fastboot flash recovery c:twrp.img
2: fastboot flash boot c:magisk_patched.img

but in the 2nd step, I used recovery instead of boot as a result my phone is currently stuck on “Powered by Android” screen and none of the Power + Volume(up) functions are working.

It also shows Orange State and your device will boot in 5 seconds

Is there a way to recover or this device is gone forever..?

How to force SELinux to permissive even when setenforce 0 is not working and kernel was 100% permissive when flashed?

I don’t know what to do, I’m using Samsung Note 3 (Exynos) – N900 with custom Resurrection Remix 5.8.5 ROM (Android 7.1.2) with it’s own permissive kernel and rooted with Magisk. Yesterday it turned to enforcing status, then SPenCommand stopped working. And when I tried to setenforce 0 in terminal, it gave me error: invalid argument. I don’t want to flash phone again, backup takes a lot of time, as well as restoring, because I have very old PC and I flashed it on friend’s laptop who is now 50 miles away and won’t come just because of this (my computer still uses USB 1.1 interface – I know it’s garbage but its working for 15 years stable. Any suggestions how to do it on phone itself, would be helpful. Please help me somebody 🙂

rom flashing – When installing new ROM through fastboot, which .img files must be flashed, with what arguments, and in what order?

I own a Oneplus 7T, which runs Android 10 and therefore has no working TWRP to flash ROMs with. It’s bootloader is unlocked and is rooted.

When installing a new ROM, whether it is a custom ROM or an update to the current ROM, I install them by extracting the ROM zip, extracting payload.bin, and flashing certain .img files in fastboot, following the instructions found here under the ‘Manual Flash’ section.

However, I’d like to understand more about this process. The instructions flash less .img files than were extracted. For example, in the recent Oneplus 7T OOS 10.0.11 update, the the number of .img files extracted (31) is less than what was flashed according to the instructions (19). Furthermore, the instructions passed the arguments --disable-verity when flashing two of the .imgs, but not the others.

Therefore, I’m wondering:

  1. What does each .img file do?
  2. Which files must be flashed and in what order?
  3. Why are certain files flashed with certain arguments?

rom flashing – What is the purpose of A and B partition slots when both are flashed?

I recently played with LineageOS Flash tutorials (or adb sideloading tutorials), but I think my question is more general.

In my device there are A and B partitions for everything but that userdata Partition (and maybe something else). I understand that the purpose is to provide additional security against brick. If something goes wrong during the blinking process, there is the other slot.

Now, Every tool and manual procedure I've seen flashes both A and B. Doesn't it make the whole concept unusable? What is the win of A and B slots if we continue to bet both equally?

TWRP: After flashing LOS 16.0 on Samsung S5, no operating system flashed

I want to install LOS 16.0 on my Samsung S5 SM-G901F. According to the LOS installation wiki, I did the following on an ArchLinux operating system:

  • installation of TWRP 3.2.3-0 with heimdall
  • swipe -> format data
  • wipe -> advanced wipe (all partitions have been deleted)
  • Advanced ADB Sideload: AdB Sideload Lineage 16.0-20200106-nightly-kccat6-signed.zip (I tried the last 3 builds)

I checked all hashes and they are fine.

I noticed a difference in the progress bar between the TWRP and the terminal: the TWRP announced 100% progress, while the adb command stopped at 47%. After debugging, however, I realized that the installation script was running completely.

When I try to restart on the system partition, I finally get the error message "No operating system flashed, do you really want to restart?".

Do you have an idea to really flash LOS?
Thanks a lot!